[Kernel-packages] [Bug 1877088] Autopkgtest regression report (linux-base/4.5ubuntu1.3)
All autopkgtests for the newly accepted linux-base (4.5ubuntu1.3) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-hwe-5.4/5.4.0-72.80~18.04.1 (i386) linux-hwe-5.0/5.0.0-65.71 (i386) linux-oem-osp1/5.0.0-1071.77 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-base [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-base in Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf Status in Ubuntu on IBM z Systems: In Progress Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux-base source package in Hirsute: Fix Released Bug description: [Impact] * initrd link is not updated when using installkernel or "make install" from kernel sources. This leads to boot failure after installing a new kernel with mentioned methods because the kernel does not match initrd. * It's a regression because for Focal it was working before. * Issue was reproduced also on Bionic. * The proposed fixed by Stefan Bader adds a hook in /etc/kernel/postinst.d/ so installkernel will relink the initrd. The kernel DEB packages should not be affected. * The solution from Stefan (first patch) was tested by the bug reporter (niklas.schne...@ibm.com). [Test Plan] * Build a kernel * sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot * Check if /boot/initrd or /initrd symlink to the new initrd [Where problems could occur] * Installing kernel via: installkernel or "make install", so mostly kernel developer environments [Other info from developer] When testing development kernels I usually rely on the installkernel script either through the "make install" target of the Kernel source or manually. This used to work great on Ubuntu on Z. On Ubuntu 20.04 (freshly installed up to date) this fails however because /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the wrong kernel/initrd combination rendering the system unbootable. (with the correct modules already copied to /usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/) # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. run-parts: executing /etc/kernel/postinst.d/zz-zipl 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. # ls -l /boot total 178364 -rw--- 1 root root135168 May 6 11:52 bootmap -rw-r--r-- 1 root root 90471 Apr 29 15:34 config-5.4.0-29-generic lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img -> initrd.img-5.4.0-29-generic <== should point to new version -rw-r--r-- 1 root root 19663996 May 6 11:42 initrd.img-5.4.0-29-generic -rw-r--r-- 1 root root 125339494 May 6 11:52 initrd.img-5.7.0-rc4-06500-gb67ea026badd lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img.old -> initrd.img-5.4.0-29-generic -rw--- 1 root root 3087920 Apr 29 15:34 System.map-5.4.0-29-generic -rw-r--r-- 1 root root 4031691 May 6 11:52 System.map-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 4031691 May 6 11:49 System.map-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root37 May 6 11:52 vmlinuz -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw--- 1 root root 8086072 Apr 29 15:54 vmlinuz-5.4.0-29-generic -rw-r--r-- 1 root root 9080832 May 6 11:52 vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 9080832 May 6 11:49 vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root41 May 6 11:52 vmlinuz.old -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old To
[Kernel-packages] [Bug 1915704] Re: Specific pointing device disappear/disconnect when standby
[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/1915704 Title: Specific pointing device disappear/disconnect when standby Status in linux package in Ubuntu: Expired Bug description: Ubuntu 20.10 groovy (x86-64) Cinnamon 4.6.7 Kernel 5.8.0-43-generic I installed Ubuntu while using a Microsft mise. This one works great with no problem. The buttons are old and used out, so I changed it with a Trust with RGB. The Trust mouse seems disconnected when going to standby (need keyboard, since mouse seems disconnected to show password prompt). The only way to get the mouse back to work, is to disconnect and reconnect it. What's narrow in this, is that I've tried again with the old pointing device (from Microsoft), and this one still is recognised in standby, and I'm able to click to open the password prompt. I've read this repport: https://bugs.launchpad.net/ubuntu/+bug/1573454 But it seems not totaly the same, since I've the problem with a pointer and not the other one. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/gpus/:01:00.0' .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.32.03 Sun Dec 27 19:00:34 UTC 2020 GCC version: gcc version 10.2.0 (Ubuntu 10.2.0-13ubuntu1) ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: X-Cinnamon Date: Mon Feb 15 12:07:10 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 460.32.03, 5.8.0-43-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK107 [GeForce GTX 650] [10de:0fc6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GK107 [GeForce GTX 650] [19da:1288] MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=1768f602-2494-474b-970a-2f71d61fca4b ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/21/2020 dmi.bios.release: 14.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1403 dmi.board.asset.tag: Default string dmi.board.name: PRIME B460-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1403:bd07/21/2020:br14.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB460-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS 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.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/1915704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1916340] Re: Logitech G920 Driving Force don't work when using external USB hub
[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/1916340 Title: Logitech G920 Driving Force don't work when using external USB hub Status in linux package in Ubuntu: Expired Bug description: I bought a USB hubs that allow to switch ON and OFF every USB port separately. Idea is not to connect and disconnect all the time unnecessary USB peripheral devices like cameras, and especially Logitech G920 Driving Force gaming wheel. I want to notice there is no hardware problem – the wheel is fully functional thru the USB hub under Windows 10. The following is the output of the lsusb and dmesg -w commands in the following situation: 1. No hub connected to PC 2. USB hub connected to PC, USB ports on the hub all switched off. 3. USB hub connected to PC, Logitech G920 Driving Force connected and switched on thru the USB hub 4. After connecting Logitech G920 Driving Force directly to PC(the wheel is working): From what I see when the wheel is connected thru the USB hub HID++ force feedback module is not loading. 1.No hub connected to PC: lsusb Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 006: ID 1532:021e Razer USA, Ltd Bus 001 Device 005: ID 1532:005c Razer USA, Ltd Bus 001 Device 004: ID 046d:082b Logitech, Inc. Webcam C170 Bus 001 Device 003: ID 1532:0514 Razer USA, Ltd Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 2.USB HUB connected to PC, USB ports on hub switched off: lsusb Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 005: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 006: ID 1532:021e Razer USA, Ltd Bus 001 Device 005: ID 1532:005c Razer USA, Ltd Bus 001 Device 004: ID 046d:082b Logitech, Inc. Webcam C170 Bus 001 Device 003: ID 1532:0514 Razer USA, Ltd Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 3.After switching on Logitech G920 Driving Force THRU USB hub: lsusb Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 007: ID 046d:c261 Logitech, Inc. Bus 003 Device 005: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 006: ID 1532:021e Razer USA, Ltd Bus 001 Device 005: ID 1532:005c Razer USA, Ltd Bus 001 Device 004: ID 046d:082b Logitech, Inc. Webcam C170 Bus 001 Device 003: ID 1532:0514 Razer USA, Ltd Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub dmesg -w [ 7127.803087] usb 3-1.4: new full-speed USB device number 7 using xhci_hcd [ 7127.929279] usb 3-1.4: New USB device found, idVendor=046d, idProduct=c261, bcdDevice=96.01 [ 7127.929284] usb 3-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 7127.929287] usb 3-1.4: Product: G920 Driving Force Racing Wheel for Xbox One [ 7127.929302] usb 3-1.4: Manufacturer: Logitech [ 7127.929305] usb 3-1.4: SerialNumber: 0bf1c8867e46 4.Connecting Logitech G920 Driving Force directly, without USB hub: lsusb Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 009: ID 046d:c262 Logitech, Inc. G920 Driving Force Racing Wheel for Xbox One Bus 003 Device 005: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 003 Device
[Kernel-packages] [Bug 1908264] Re: Disable Atari partition support for cloud kernels
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- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. 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-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1908264 Title: Disable Atari partition support for cloud kernels Status in linux-aws package in Ubuntu: In Progress Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-4.15 package in Ubuntu: Invalid Status in linux-gcp package in Ubuntu: New Status in linux-gke package in Ubuntu: New Status in linux-gkeop package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-aws source package in Xenial: Fix Committed Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-4.15 source package in Xenial: Invalid Status in linux-aws source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Invalid Status in linux-azure-4.15 source package in Bionic: Fix Released Status in linux-gcp source package in Bionic: Fix Committed Status in linux-oracle source package in Bionic: Fix Committed Status in linux-aws source package in Focal: Fix Released Status in linux-azure source package in Focal: Fix Released Status in linux-azure-4.15 source package in Focal: Invalid Status in linux-gcp source package in Focal: Fix Committed Status in linux-gke source package in Focal: Fix Committed Status in linux-gkeop source package in Focal: Fix Committed Status in linux-oracle source package in Focal: Fix Committed Status in linux-aws source package in Groovy: Fix Committed Status in linux-azure source package in Groovy: Fix Released Status in linux-azure-4.15 source package in Groovy: Invalid Status in linux-gcp source package in Groovy: Fix Committed Status in linux-oracle source package in Groovy: Fix Committed Status in linux-aws source package in Hirsute: In Progress Status in linux-azure source package in Hirsute: Fix Released Status in linux-azure-4.15 source package in Hirsute: Invalid Status in linux-gcp source package in Hirsute: New Status in linux-oracle source package in Hirsute: New Bug description: [Impact] Atari partition tables have very broad specifications, and can spontaneously show up on uncleared disks with "garbage" data. There have been reports of misinterpreted AHDI partition tables before (see [0] and [1]), usually as an unintended side-effect of using non-zeroed disks. Users of this specific partition scheme are unlikely to be on AWS instances, so we should disable them. [0] https://lore.kernel.org/linux-block/1467736712-11825-1-git-send-email-kris...@linux.vnet.ibm.com/ [1] https://mail-index.netbsd.org/port-atari/1995/11/19/0001.html [Test Case] Ensure that CONFIG_ATARI_PARTITION is not set in /boot/config-$(uname -r) [Fix] Unset CONFIG_ATARI_PARTITION in debian.aws/config/config.common.ubuntu [Regression Potential] There could be unexpected dependencies on Atari partitions that are impacted by this change. Considering Atari hardware hasn't been produced in a long time, and is unlikely to be used in AWS instances, the regression potential should be very low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1908264/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908264] Re: Disable Atari partition support for cloud kernels
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-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1908264 Title: Disable Atari partition support for cloud kernels Status in linux-aws package in Ubuntu: In Progress Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-4.15 package in Ubuntu: Invalid Status in linux-gcp package in Ubuntu: New Status in linux-gke package in Ubuntu: New Status in linux-gkeop package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-aws source package in Xenial: Fix Committed Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-4.15 source package in Xenial: Invalid Status in linux-aws source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Invalid Status in linux-azure-4.15 source package in Bionic: Fix Released Status in linux-gcp source package in Bionic: Fix Committed Status in linux-oracle source package in Bionic: Fix Committed Status in linux-aws source package in Focal: Fix Released Status in linux-azure source package in Focal: Fix Released Status in linux-azure-4.15 source package in Focal: Invalid Status in linux-gcp source package in Focal: Fix Committed Status in linux-gke source package in Focal: Fix Committed Status in linux-gkeop source package in Focal: Fix Committed Status in linux-oracle source package in Focal: Fix Committed Status in linux-aws source package in Groovy: Fix Committed Status in linux-azure source package in Groovy: Fix Released Status in linux-azure-4.15 source package in Groovy: Invalid Status in linux-gcp source package in Groovy: Fix Committed Status in linux-oracle source package in Groovy: Fix Committed Status in linux-aws source package in Hirsute: In Progress Status in linux-azure source package in Hirsute: Fix Released Status in linux-azure-4.15 source package in Hirsute: Invalid Status in linux-gcp source package in Hirsute: New Status in linux-oracle source package in Hirsute: New Bug description: [Impact] Atari partition tables have very broad specifications, and can spontaneously show up on uncleared disks with "garbage" data. There have been reports of misinterpreted AHDI partition tables before (see [0] and [1]), usually as an unintended side-effect of using non-zeroed disks. Users of this specific partition scheme are unlikely to be on AWS instances, so we should disable them. [0] https://lore.kernel.org/linux-block/1467736712-11825-1-git-send-email-kris...@linux.vnet.ibm.com/ [1] https://mail-index.netbsd.org/port-atari/1995/11/19/0001.html [Test Case] Ensure that CONFIG_ATARI_PARTITION is not set in /boot/config-$(uname -r) [Fix] Unset CONFIG_ATARI_PARTITION in debian.aws/config/config.common.ubuntu [Regression Potential] There could be unexpected dependencies on Atari partitions that are impacted by this change. Considering Atari hardware hasn't been produced in a long time, and is unlikely to be used in AWS instances, the regression potential should be very low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1908264/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922582] Re: linux-azure: Enable CONFIG_FPGA_MGR_XILINX_SPI for Azure cloud kernel
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-azure in Ubuntu. https://bugs.launchpad.net/bugs/1922582 Title: linux-azure: Enable CONFIG_FPGA_MGR_XILINX_SPI for Azure cloud kernel Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-4.15 package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Invalid Status in linux-azure-4.15 source package in Bionic: Fix Committed Status in linux-azure source package in Focal: Fix Committed Status in linux-azure-4.15 source package in Focal: Invalid Status in linux-azure source package in Groovy: Fix Committed Status in linux-azure-4.15 source package in Groovy: Invalid Status in linux-azure source package in Hirsute: Fix Released Status in linux-azure-4.15 source package in Hirsute: Invalid Bug description: [SRU Justification] Microsoft Azure clouds support the use of a Xilinx FPGA to accelerate machine learning and other high performance tasks. The master kernels have had this option since the beginning. The lack of this option for Azure appears to have been an oversight. [Fix] Enable CONFIG_FPGA=m and CONFIG_FPGA_MGR_XILINX_SPI=m. Add these modules to the inclusion list. [Test Plan] modprobe xilinx-spi [Where problems could occur] The chances for regression are minimal as all additions are modules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1922582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925983] BOT: Examined VarLogDistupgradeApttermlog.gz
update-initramfs: deferring update (hook will be called later) Failed to symbolic-link boot/initrd.img-3.13.0-32-generic to initrd.img:File exists at /var/lib/dpkg/info/linux-image-3.13.0-32-generic.postinst line 629. dpkg: error processing package linux-image-3.13.0-32-generic (--configure): Failed to symbolic-link boot/initrd.img-3.13.0-32-generic to initrd.img:File exists at /var/lib/dpkg/info/linux-image-3.13.0-32-generic.postinst line 629. dpkg: error processing package linux-image-3.13.0-32-generic (--configure): subprocess installed post-installation script returned error exit status 17 ** Tags added: varlogdistupgradeapttermlog-examined -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925983 Title: package linux-image-3.13.0-32-generic 3.13.0-32.57 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 Status in linux package in Ubuntu: Confirmed Bug description: happened during update ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: don2065 F pulseaudio CurrentDmesg: [ 36.463703] init: plymouth-upstart-bridge main process (1265) killed by TERM signal [ 49.032303] audit_printk_skb: 33 callbacks suppressed [ 49.032310] type=1400 audit(1619223910.017:31): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=1432 comm="apparmor_parser" [ 49.032323] type=1400 audit(1619223910.017:32): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=1432 comm="apparmor_parser" Date: Fri Apr 23 19:43:03 2021 DuplicateSignature: package:linux-image-3.13.0-32-generic:3.13.0-32.57:subprocess installed post-installation script returned error exit status 17 ErrorMessage: subprocess installed post-installation script returned error exit status 17 HibernationDevice: RESUME=UUID=b50cbcf1-78a2-4fbd-b1a3-49e89bb971ff InstallationDate: Installed on 2021-04-22 (1 days ago) InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 (20140807.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Acer Aspire 5515 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-170-generic root=UUID=c2638057-e033-4024-9294-64edc75af499 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.17 SourcePackage: linux Title: package linux-image-3.13.0-32-generic 3.13.0-32.57 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 UpgradeStatus: Upgraded to trusty on 2021-04-24 (0 days ago) dmi.bios.date: 12/03/2008 dmi.bios.vendor: Acer dmi.bios.version: V1.00 dmi.board.name: Nile dmi.board.vendor: Acer dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrV1.00:bd12/03/2008:svnAcer:pnAspire5515:pvrV1.00:rvnAcer:rnNile:rvrN/A:cvnAcer:ct10:cvrN/A: dmi.product.name: Aspire 5515 dmi.product.version: V1.00 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925983] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925983 Title: package linux-image-3.13.0-32-generic 3.13.0-32.57 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 Status in linux package in Ubuntu: Confirmed Bug description: happened during update ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: don2065 F pulseaudio CurrentDmesg: [ 36.463703] init: plymouth-upstart-bridge main process (1265) killed by TERM signal [ 49.032303] audit_printk_skb: 33 callbacks suppressed [ 49.032310] type=1400 audit(1619223910.017:31): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=1432 comm="apparmor_parser" [ 49.032323] type=1400 audit(1619223910.017:32): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=1432 comm="apparmor_parser" Date: Fri Apr 23 19:43:03 2021 DuplicateSignature: package:linux-image-3.13.0-32-generic:3.13.0-32.57:subprocess installed post-installation script returned error exit status 17 ErrorMessage: subprocess installed post-installation script returned error exit status 17 HibernationDevice: RESUME=UUID=b50cbcf1-78a2-4fbd-b1a3-49e89bb971ff InstallationDate: Installed on 2021-04-22 (1 days ago) InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 (20140807.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Acer Aspire 5515 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-170-generic root=UUID=c2638057-e033-4024-9294-64edc75af499 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.17 SourcePackage: linux Title: package linux-image-3.13.0-32-generic 3.13.0-32.57 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 UpgradeStatus: Upgraded to trusty on 2021-04-24 (0 days ago) dmi.bios.date: 12/03/2008 dmi.bios.vendor: Acer dmi.bios.version: V1.00 dmi.board.name: Nile dmi.board.vendor: Acer dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrV1.00:bd12/03/2008:svnAcer:pnAspire5515:pvrV1.00:rvnAcer:rnNile:rvrN/A:cvnAcer:ct10:cvrN/A: dmi.product.name: Aspire 5515 dmi.product.version: V1.00 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715552] Re: VMWare does not start
These instructions worked as well for me with VMWare Player 12.5.9 after upgrading to Ubuntu 18.04.5 LTS Desktop with Linux kernel 4.15, thanks! However, I'm now prepping for further upgrade to the latest Ubuntu 21.04 (kernel 5.11), and there seems to be more problems! The distro's shared libraries are now further updated, so after manually building the vmmon.ko and vmnet.ko for the new kernel using the vmware-host-modules project, starting the VMware services successfully, and adding the soft link on libz.so.1, when I try to launch vmplayer I get the following output and then a segmentation fault: ubuntu@ubuntu:~$ vmplayer Gtk-Message: Failed to load module "atk-bridge": /lib/x86_64-linux-gnu/libatspi.so.0: undefined symbol: g_type_add_instance_private (vmware-modconfig:53428): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita", /usr/share/themes/Yaru/gtk-2.0/main.rc:775: error: unexpected identifier `direction', expected character `}' (vmware-modconfig:53428): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita", /usr/share/themes/Yaru/gtk-2.0/hacks.rc:28: error: invalid string constant "normal_entry", expected valid string constant Gtk-Message: Failed to load module "canberra-gtk-module": libcanberra-gtk-module.so: cannot open shared object file: No such file or directory /usr/bin/vmplayer: line 106: 53428 Segmentation fault (core dumped) "$BINDIR"/vmware-modconfig --appname="VMware Player" --icon="vmware-player" ubuntu@ubuntu:~$ I suspect there's another shared libraries that now needs to be redirected to the distro, but I'm really not clear how to figure out the dependency tree, as VMware uses this 'appLoader' application to launch it's actual binaries and masks the environment and what it is actually doing. Unfortunately, as others have mentioned, upgrading VMware to 14 or later is not an option for me, as my CPU is from before 2011 without Intel EPT / AMD NPT, and 12.5.9 happens to be the last version that works on these. So this problem is going to keep cropping up for some people for a very long time! Any help resolving the dependencies between VMware's references and/or shipped libraries and Ubuntu's latest would be greatly appreciated! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1715552 Title: VMWare does not start Status in linux package in Ubuntu: Confirmed Bug description: Under Ubuntu 17.10 beta VMWare 12.5.7 cannot be started: /usr/lib/vmware/bin/vmware-modconfig: Relink `/lib/x86_64-linux- gnu/libbsd.so.0' with `/lib/x86_64-linux-gnu/librt.so.1' for IFUNC symbol `clock_gettime' Works under Ubuntu 17.04 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.12.0-13-generic 4.12.0-13.14 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wolf 9336 F pulseaudio /dev/snd/controlC0: wolf 9336 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 07:53:43 2017 HibernationDevice: RESUME=UUID=88d69bc7-ac96-42c6-bf6d-5c912964a63b InstallationDate: Installed on 2017-09-05 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) MachineType: Apple Inc. MacBookPro12,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.12.0-13-generic N/A linux-backports-modules-4.12.0-13-generic N/A linux-firmware 1.167 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B33.1706181928 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B33.1706181928:bd06/18/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715552/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864764] Re: [EGL] enable intel_idle for Eagle Stream
** Tags added: egl
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1864764
Title:
[EGL] enable intel_idle for Eagle Stream
Status in intel:
Fix Released
Status in linux package in Ubuntu:
Incomplete
Bug description:
Description:
Enable Intel_idle for eagle stream.
Target Kernel: 5.6
Target Release: 20.10
Commit Ids:
bc94638886ab21f8247d3f7f39573d3feb7d8284("ACPI: processor: Export
function to claim _CST control")
987c785319b99e32602f7f86cfae3cf9b81e402b("ACPI: processor: Introduce
acpi_processor_evaluate_cst()")
aa659a3fca79abd9a3ca3ddc535db631b01c9a02("ACPI: processor: Clean up
acpi_processor_evaluate_cst()")
239ed06d0eefc4ee351af69bd64742ada56c4bdb("ACPI: processor: Make
ACPI_PROCESSOR_CSTATE depend on ACPI_PROCESSOR")
77fb4e0a559a960eb36d0b2c50c781c5492577eb("ACPI: processor: Export
acpi_processor_evaluate_cst()")
9f3d6daf61e5156139cd05643f7f1c2a9b7b49b0("intel_idle: Refactor
intel_idle_cpuidle_driver_init()")
18734958e9bfbc055805d110a38dc76307eba742("intel_idle: Use ACPI _CST
for processor models without C-state tables")
75a80267410e38ab76c4ceb39753f96d72113781("cpuidle: Allow idle states
to be disabled by default")
bff8e60a86f4960133f90ad9add9adeb082b8154("intel_idle: Allow ACPI _CST
to be used for selected known processors")
4ec32d9e8e5b6d6eb4913938665d8a2388fa("intel_idle: Add module
parameter to prevent ACPI _CST from being used")
e6d4f08a677654385869ba0c39d7c9ceec47e5c5("intel_idle: Use ACPI _CST on
server systems")
a3299182216397a0b943d2549d1997f4eba2bdd2("Documentation: admin-guide:
PM: Add intel_idle document")
To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1864764/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925983] [NEW] package linux-image-3.13.0-32-generic 3.13.0-32.57 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17
Public bug reported: happened during update ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: don2065 F pulseaudio CurrentDmesg: [ 36.463703] init: plymouth-upstart-bridge main process (1265) killed by TERM signal [ 49.032303] audit_printk_skb: 33 callbacks suppressed [ 49.032310] type=1400 audit(1619223910.017:31): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=1432 comm="apparmor_parser" [ 49.032323] type=1400 audit(1619223910.017:32): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=1432 comm="apparmor_parser" Date: Fri Apr 23 19:43:03 2021 DuplicateSignature: package:linux-image-3.13.0-32-generic:3.13.0-32.57:subprocess installed post-installation script returned error exit status 17 ErrorMessage: subprocess installed post-installation script returned error exit status 17 HibernationDevice: RESUME=UUID=b50cbcf1-78a2-4fbd-b1a3-49e89bb971ff InstallationDate: Installed on 2021-04-22 (1 days ago) InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 (20140807.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Acer Aspire 5515 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-170-generic root=UUID=c2638057-e033-4024-9294-64edc75af499 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.17 SourcePackage: linux Title: package linux-image-3.13.0-32-generic 3.13.0-32.57 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 UpgradeStatus: Upgraded to trusty on 2021-04-24 (0 days ago) dmi.bios.date: 12/03/2008 dmi.bios.vendor: Acer dmi.bios.version: V1.00 dmi.board.name: Nile dmi.board.vendor: Acer dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrV1.00:bd12/03/2008:svnAcer:pnAspire5515:pvrV1.00:rvnAcer:rnNile:rvrN/A:cvnAcer:ct10:cvrN/A: dmi.product.name: Aspire 5515 dmi.product.version: V1.00 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package dist-upgrade i386 need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925983 Title: package linux-image-3.13.0-32-generic 3.13.0-32.57 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 Status in linux package in Ubuntu: New Bug description: happened during update ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: don2065 F pulseaudio CurrentDmesg: [ 36.463703] init: plymouth-upstart-bridge main process (1265) killed by TERM signal [ 49.032303] audit_printk_skb: 33 callbacks suppressed [ 49.032310] type=1400 audit(1619223910.017:31): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=1432 comm="apparmor_parser" [ 49.032323] type=1400 audit(1619223910.017:32): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=1432 comm="apparmor_parser" Date: Fri Apr 23 19:43:03 2021 DuplicateSignature: package:linux-image-3.13.0-32-generic:3.13.0-32.57:subprocess installed post-installation script returned error exit status 17 ErrorMessage: subprocess installed post-installation script returned error exit status 17 HibernationDevice: RESUME=UUID=b50cbcf1-78a2-4fbd-b1a3-49e89bb971ff InstallationDate: Installed on 2021-04-22 (1 days ago) InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 (20140807.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux
[Kernel-packages] [Bug 1925981] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925981 Title: 20.04.02 introduces noise into the audio channel when using YouTube Status in linux package in Ubuntu: Confirmed Bug description: My hardware: HDMI output to TV/Monitor. Optical cable to Phonak TVLink. Bluetooth to compilot. ComPilot to hearing aids. Browsing YouTube with Google Chrome. Works fine with 18.04. Tried Ubuntu MATE 20.04.02. High level of noise with 20.04. When reboot to 18.04 noise goes away. Not Hardware. Just bad code in 20.04.02 audio. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-142-generic 4.15.0-142.146 ProcVersionSignature: Ubuntu 4.15.0-142.146-generic 4.15.18 Uname: Linux 4.15.0-142-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robert 6819 F pulseaudio /dev/snd/controlC0: robert 6819 F pulseaudio CurrentDesktop: MATE Date: Fri Apr 23 19:30:35 2021 InstallationDate: Installed on 2019-12-22 (488 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-142-generic root=UUID=ae6f5cdd-0c3b-48a9-8449-da1027511bec ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-142-generic N/A linux-backports-modules-4.15.0-142-generic N/A linux-firmware 1.173.20 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925981/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925981] [NEW] 20.04.02 introduces noise into the audio channel when using YouTube
Public bug reported: My hardware: HDMI output to TV/Monitor. Optical cable to Phonak TVLink. Bluetooth to compilot. ComPilot to hearing aids. Browsing YouTube with Google Chrome. Works fine with 18.04. Tried Ubuntu MATE 20.04.02. High level of noise with 20.04. When reboot to 18.04 noise goes away. Not Hardware. Just bad code in 20.04.02 audio. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-142-generic 4.15.0-142.146 ProcVersionSignature: Ubuntu 4.15.0-142.146-generic 4.15.18 Uname: Linux 4.15.0-142-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robert 6819 F pulseaudio /dev/snd/controlC0: robert 6819 F pulseaudio CurrentDesktop: MATE Date: Fri Apr 23 19:30:35 2021 InstallationDate: Installed on 2019-12-22 (488 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-142-generic root=UUID=ae6f5cdd-0c3b-48a9-8449-da1027511bec ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-142-generic N/A linux-backports-modules-4.15.0-142-generic N/A linux-firmware 1.173.20 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925981 Title: 20.04.02 introduces noise into the audio channel when using YouTube Status in linux package in Ubuntu: New Bug description: My hardware: HDMI output to TV/Monitor. Optical cable to Phonak TVLink. Bluetooth to compilot. ComPilot to hearing aids. Browsing YouTube with Google Chrome. Works fine with 18.04. Tried Ubuntu MATE 20.04.02. High level of noise with 20.04. When reboot to 18.04 noise goes away. Not Hardware. Just bad code in 20.04.02 audio. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-142-generic 4.15.0-142.146 ProcVersionSignature: Ubuntu 4.15.0-142.146-generic 4.15.18 Uname: Linux 4.15.0-142-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robert 6819 F pulseaudio /dev/snd/controlC0: robert 6819 F pulseaudio CurrentDesktop: MATE Date: Fri Apr 23 19:30:35 2021 InstallationDate: Installed on 2019-12-22 (488 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-142-generic root=UUID=ae6f5cdd-0c3b-48a9-8449-da1027511bec ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-142-generic N/A linux-backports-modules-4.15.0-142-generic N/A linux-firmware 1.173.20 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage
[Kernel-packages] [Bug 1925979] [NEW] 450.119 crashes lxde desktop (specifically lxpanel)
Public bug reported: Ubuntu 18.04 with LXDE desktop, GeForce GTX 1050 Ti card Installed 450.119 over 450.102 today and rebooted. Upon logging in, lxpanel crashed making desktop unusable. Restored clonezilla clone of system with 450.102 drivers, all is well again. ** Affects: nvidia-graphics-drivers-450 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1925979 Title: 450.119 crashes lxde desktop (specifically lxpanel) Status in nvidia-graphics-drivers-450 package in Ubuntu: New Bug description: Ubuntu 18.04 with LXDE desktop, GeForce GTX 1050 Ti card Installed 450.119 over 450.102 today and rebooted. Upon logging in, lxpanel crashed making desktop unusable. Restored clonezilla clone of system with 450.102 drivers, all is well again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1925979/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925482] Re: Ubuntu 21.04 won't boot with NVMe enabled on Parallels Desktop 16
Thank you Dominik! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925482 Title: Ubuntu 21.04 won't boot with NVMe enabled on Parallels Desktop 16 Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to boot Ubuntu 21.04 with the NVMe option in Parallels Desktop 16 and it crashes with an kernel panic after unsuccessfully trying to boot from the virtual NVMe drive. On contrary Ubuntu 20.10 and the latest point release of Ubuntu 20.04 on the 5.8 Linux kernel will boot without any problems in the same virtualization software and with NVMe enabled. If I decide to disable NVMe and boot with the SATA option, Ubuntu 21.04 will boot flawlessly. This seems to be a big regression from the previous releases. Release: Ubuntu 21.04 on the latest available kernel Package version: 5.11.0-16.17 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dominikbabic 1220 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-20 (1 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp0s5no wireless extensions. MachineType: Parallels Software International Inc. Parallels Virtual Platform NonfreeKernelModules: prl_fs_freeze prl_fs prl_eth prl_vid prl_tg Package: linux (not installed) ProcFB: 0 prldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=78783e94-d66a-49e8-947b-69dde4dbfe19 ro quiet splash nvme_load=YES nvme_core.default_ps_max_latency_us=0 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 RfKill: Tags: hirsute Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-04-20 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2021 dmi.bios.release: 16.5 dmi.bios.vendor: Parallels Software International Inc. dmi.bios.version: 16.5.0 (49183) dmi.board.name: Parallels Virtual Platform dmi.board.vendor: Parallels Software International Inc. dmi.board.version: None dmi.chassis.type: 2 dmi.chassis.vendor: Parallels Software International Inc. dmi.ec.firmware.release: 16.5 dmi.modalias: dmi:bvnParallelsSoftwareInternationalInc.:bvr16.5.0(49183):bd04/02/2021:br16.5:efr16.5:svnParallelsSoftwareInternationalInc.:pnParallelsVirtualPlatform:pvrNone:rvnParallelsSoftwareInternationalInc.:rnParallelsVirtualPlatform:rvrNone:cvnParallelsSoftwareInternationalInc.:ct2:cvr: dmi.product.family: Parallels VM dmi.product.name: Parallels Virtual Platform dmi.product.sku: Undefined dmi.product.version: None dmi.sys.vendor: Parallels Software International Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925482] Re: Ubuntu 21.04 won't boot with NVMe enabled on Parallels Desktop 16
I was able to boot from SATA without reinstallation in Parallels and I'll try the PPAs later. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925482 Title: Ubuntu 21.04 won't boot with NVMe enabled on Parallels Desktop 16 Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to boot Ubuntu 21.04 with the NVMe option in Parallels Desktop 16 and it crashes with an kernel panic after unsuccessfully trying to boot from the virtual NVMe drive. On contrary Ubuntu 20.10 and the latest point release of Ubuntu 20.04 on the 5.8 Linux kernel will boot without any problems in the same virtualization software and with NVMe enabled. If I decide to disable NVMe and boot with the SATA option, Ubuntu 21.04 will boot flawlessly. This seems to be a big regression from the previous releases. Release: Ubuntu 21.04 on the latest available kernel Package version: 5.11.0-16.17 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dominikbabic 1220 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-20 (1 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp0s5no wireless extensions. MachineType: Parallels Software International Inc. Parallels Virtual Platform NonfreeKernelModules: prl_fs_freeze prl_fs prl_eth prl_vid prl_tg Package: linux (not installed) ProcFB: 0 prldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=78783e94-d66a-49e8-947b-69dde4dbfe19 ro quiet splash nvme_load=YES nvme_core.default_ps_max_latency_us=0 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 RfKill: Tags: hirsute Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-04-20 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2021 dmi.bios.release: 16.5 dmi.bios.vendor: Parallels Software International Inc. dmi.bios.version: 16.5.0 (49183) dmi.board.name: Parallels Virtual Platform dmi.board.vendor: Parallels Software International Inc. dmi.board.version: None dmi.chassis.type: 2 dmi.chassis.vendor: Parallels Software International Inc. dmi.ec.firmware.release: 16.5 dmi.modalias: dmi:bvnParallelsSoftwareInternationalInc.:bvr16.5.0(49183):bd04/02/2021:br16.5:efr16.5:svnParallelsSoftwareInternationalInc.:pnParallelsVirtualPlatform:pvrNone:rvnParallelsSoftwareInternationalInc.:rnParallelsVirtualPlatform:rvrNone:cvnParallelsSoftwareInternationalInc.:ct2:cvr: dmi.product.family: Parallels VM dmi.product.name: Parallels Virtual Platform dmi.product.sku: Undefined dmi.product.version: None dmi.sys.vendor: Parallels Software International Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925482] Re: Ubuntu 21.04 won't boot with NVMe enabled on Parallels Desktop 16
Hey Dominik, thanks a lot for the log, it's really helpful. It seems there's a null pointer in a struct req member...my investigation continues. Can I ask you for 2 more tests? In fact..make it 3, if not a big issue for you. I'd like to ask you for mainline kernels testing, we have packages for the versions I need: (a) https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.12-rc8/ (b) https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.11/ (c) https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.10/ Basically the test is to determine if it is already fixed upstream, and when the issue was possibly introduced - this would help a lot. You could just boot the guest in SATA-mode and install (a), then reboot - if everything is fine, NVMe-boot the guest and see if it reproduces the issue. Repeat that for (b) and (c) - that is much appreciated! Thanks, Guilherme -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925482 Title: Ubuntu 21.04 won't boot with NVMe enabled on Parallels Desktop 16 Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to boot Ubuntu 21.04 with the NVMe option in Parallels Desktop 16 and it crashes with an kernel panic after unsuccessfully trying to boot from the virtual NVMe drive. On contrary Ubuntu 20.10 and the latest point release of Ubuntu 20.04 on the 5.8 Linux kernel will boot without any problems in the same virtualization software and with NVMe enabled. If I decide to disable NVMe and boot with the SATA option, Ubuntu 21.04 will boot flawlessly. This seems to be a big regression from the previous releases. Release: Ubuntu 21.04 on the latest available kernel Package version: 5.11.0-16.17 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dominikbabic 1220 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-20 (1 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp0s5no wireless extensions. MachineType: Parallels Software International Inc. Parallels Virtual Platform NonfreeKernelModules: prl_fs_freeze prl_fs prl_eth prl_vid prl_tg Package: linux (not installed) ProcFB: 0 prldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=78783e94-d66a-49e8-947b-69dde4dbfe19 ro quiet splash nvme_load=YES nvme_core.default_ps_max_latency_us=0 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 RfKill: Tags: hirsute Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-04-20 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2021 dmi.bios.release: 16.5 dmi.bios.vendor: Parallels Software International Inc. dmi.bios.version: 16.5.0 (49183) dmi.board.name: Parallels Virtual Platform dmi.board.vendor: Parallels Software International Inc. dmi.board.version: None dmi.chassis.type: 2 dmi.chassis.vendor: Parallels Software International Inc. dmi.ec.firmware.release: 16.5 dmi.modalias: dmi:bvnParallelsSoftwareInternationalInc.:bvr16.5.0(49183):bd04/02/2021:br16.5:efr16.5:svnParallelsSoftwareInternationalInc.:pnParallelsVirtualPlatform:pvrNone:rvnParallelsSoftwareInternationalInc.:rnParallelsVirtualPlatform:rvrNone:cvnParallelsSoftwareInternationalInc.:ct2:cvr: dmi.product.family: Parallels VM dmi.product.name: Parallels Virtual Platform dmi.product.sku: Undefined dmi.product.version: None dmi.sys.vendor: Parallels Software International Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925482] Re: Ubuntu 21.04 won't boot with NVMe enabled on Parallels Desktop 16
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925482 Title: Ubuntu 21.04 won't boot with NVMe enabled on Parallels Desktop 16 Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to boot Ubuntu 21.04 with the NVMe option in Parallels Desktop 16 and it crashes with an kernel panic after unsuccessfully trying to boot from the virtual NVMe drive. On contrary Ubuntu 20.10 and the latest point release of Ubuntu 20.04 on the 5.8 Linux kernel will boot without any problems in the same virtualization software and with NVMe enabled. If I decide to disable NVMe and boot with the SATA option, Ubuntu 21.04 will boot flawlessly. This seems to be a big regression from the previous releases. Release: Ubuntu 21.04 on the latest available kernel Package version: 5.11.0-16.17 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dominikbabic 1220 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-20 (1 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp0s5no wireless extensions. MachineType: Parallels Software International Inc. Parallels Virtual Platform NonfreeKernelModules: prl_fs_freeze prl_fs prl_eth prl_vid prl_tg Package: linux (not installed) ProcFB: 0 prldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=78783e94-d66a-49e8-947b-69dde4dbfe19 ro quiet splash nvme_load=YES nvme_core.default_ps_max_latency_us=0 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 RfKill: Tags: hirsute Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-04-20 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2021 dmi.bios.release: 16.5 dmi.bios.vendor: Parallels Software International Inc. dmi.bios.version: 16.5.0 (49183) dmi.board.name: Parallels Virtual Platform dmi.board.vendor: Parallels Software International Inc. dmi.board.version: None dmi.chassis.type: 2 dmi.chassis.vendor: Parallels Software International Inc. dmi.ec.firmware.release: 16.5 dmi.modalias: dmi:bvnParallelsSoftwareInternationalInc.:bvr16.5.0(49183):bd04/02/2021:br16.5:efr16.5:svnParallelsSoftwareInternationalInc.:pnParallelsVirtualPlatform:pvrNone:rvnParallelsSoftwareInternationalInc.:rnParallelsVirtualPlatform:rvrNone:cvnParallelsSoftwareInternationalInc.:ct2:cvr: dmi.product.family: Parallels VM dmi.product.name: Parallels Virtual Platform dmi.product.sku: Undefined dmi.product.version: None dmi.sys.vendor: Parallels Software International Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923859] Re: Remove an unused file
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- groovy' to 'verification-done-groovy'. If the problem still exists, change the tag 'verification-needed-groovy' to 'verification-failed- groovy'. 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-groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1923859 Title: Remove an unused file Status in linux package in Ubuntu: Invalid Status in linux-aws package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-aws source package in Focal: Fix Committed Status in linux source package in Groovy: Invalid Status in linux-aws source package in Groovy: Fix Committed Bug description: [Impact] debian.aws-20.10/scripts/helpers/copy-files is unused and can be confusing, especially for derivatives. The eye of Sauron (in the form of apw) has cast its baleful glare on this bit of cruft. [Test Plan] Perform a successful build [Where problems could occur] Any regressions will be noted at build time. [Other Info] None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923859/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1751497] Re: Bionic daily build - nouveau: Direct firmware load for nouveau/nve7_fuc084 failed with error -2
Just updated to 21.04 today and still getting this error. name -a ; cat /etc/os-release ; dmesg |grep nouveau Linux fedora 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux NAME="Ubuntu" VERSION="21.04 (Hirsute Hippo)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 21.04" VERSION_ID="21.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=hirsute UBUNTU_CODENAME=hirsute [Fri Apr 23 10:35:55 2021] fb0: switching to nouveaufb from VESA VGA [Fri Apr 23 10:35:55 2021] nouveau :01:00.0: vgaarb: deactivate vga console [Fri Apr 23 10:35:55 2021] nouveau :01:00.0: NVIDIA G98 (298200a2) [Fri Apr 23 10:35:55 2021] nouveau :01:00.0: bios: version 62.98.29.00.00 [Fri Apr 23 10:35:55 2021] nouveau :01:00.0: bios: M0203T not found [Fri Apr 23 10:35:55 2021] nouveau :01:00.0: bios: M0203E not matched! [Fri Apr 23 10:35:55 2021] nouveau :01:00.0: fb: 512 MiB DDR2 [Fri Apr 23 10:35:56 2021] nouveau :01:00.0: DRM: VRAM: 512 MiB [Fri Apr 23 10:35:56 2021] nouveau :01:00.0: DRM: GART: 1048576 MiB [Fri Apr 23 10:35:56 2021] nouveau :01:00.0: DRM: TMDS table version 2.0 [Fri Apr 23 10:35:56 2021] nouveau :01:00.0: DRM: DCB version 4.0 [Fri Apr 23 10:35:56 2021] nouveau :01:00.0: DRM: DCB outp 00: 02000300 0028 [Fri Apr 23 10:35:56 2021] nouveau :01:00.0: DRM: DCB outp 01: 01000302 0030 [Fri Apr 23 10:35:56 2021] nouveau :01:00.0: DRM: DCB outp 02: 04011310 0028 [Fri Apr 23 10:35:56 2021] nouveau :01:00.0: DRM: DCB conn 00: 1030 [Fri Apr 23 10:35:56 2021] nouveau :01:00.0: DRM: DCB conn 01: 0100 [Fri Apr 23 10:35:56 2021] nouveau :01:00.0: DRM: MM: using M2MF for buffer copies [Fri Apr 23 10:35:56 2021] nouveau :01:00.0: DRM: allocated 1920x1080 fb: 0x7, bo 675ec200 [Fri Apr 23 10:35:56 2021] fbcon: nouveaudrmfb (fb0) is primary device [Fri Apr 23 10:35:56 2021] nouveau :01:00.0: [drm] fb0: nouveaudrmfb frame buffer device [Fri Apr 23 10:35:56 2021] [drm] Initialized nouveau 1.3.1 20120801 for :01:00.0 on minor 0 [Fri Apr 23 10:37:54 2021] nouveau :01:00.0: Direct firmware load for nouveau/nv98_fuc084 failed with error -2 [Fri Apr 23 10:37:54 2021] nouveau :01:00.0: Direct firmware load for nouveau/nv98_fuc084d failed with error -2 [Fri Apr 23 10:37:54 2021] nouveau :01:00.0: msvld: unable to load firmware data [Fri Apr 23 10:37:54 2021] nouveau :01:00.0: msvld: init failed, -19 [Fri Apr 23 10:38:08 2021] nouveau :01:00.0: Direct firmware load for nouveau/nv98_fuc084 failed with error -2 [Fri Apr 23 10:38:08 2021] nouveau :01:00.0: Direct firmware load for nouveau/nv98_fuc084d failed with error -2 [Fri Apr 23 10:38:08 2021] nouveau :01:00.0: msvld: unable to load firmware data [Fri Apr 23 10:38:08 2021] nouveau :01:00.0: msvld: init failed, -19 [Fri Apr 23 10:38:17 2021] nouveau :01:00.0: Direct firmware load for nouveau/nv98_fuc084 failed with error -2 [Fri Apr 23 10:38:17 2021] nouveau :01:00.0: Direct firmware load for nouveau/nv98_fuc084d failed with error -2 [Fri Apr 23 10:38:17 2021] nouveau :01:00.0: msvld: unable to load firmware data [Fri Apr 23 10:38:17 2021] nouveau :01:00.0: msvld: init failed, -19 *-display description: VGA compatible controller product: G98 [GeForce 8400 GS Rev. 2] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: vga_controller bus_master cap_list rom configuration: driver=nouveau latency=0 resources: irq:30 memory:fd00-fdff memory:d000-dfff memory:fa00-fbff ioport:d800(size=128) memory:c-d dpkg -l |egrep 'nouveau|nvidia' ii libdrm-nouveau2:amd64 2.4.104-1build1 amd64Userspace interface to nouveau-specific kernel DRM services -- runtime ii nouveau-firmware 20091212-0ubuntu1 all Firmware for nVidia graphics cards ii xserver-xorg-video-nouveau1:1.0.17-1 amd64X.Org X server -- Nouveau display driver -- 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/1751497 Title: Bionic daily build - nouveau: Direct firmware load for nouveau/nve7_fuc084 failed with error -2 Status in linux package in Ubuntu: Expired Status in linux-firmware package in Ubuntu: Won't Fix Bug
[Kernel-packages] [Bug 1925964] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1925964 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925964 Title: HP NC364T NIC with 20.04.2 LTS Issues Status in linux package in Ubuntu: Incomplete Bug description: This NIC is a 4 Port Copper 1GB Intel 82571B/82571GB Gigabit Ethernet Controller with a Dual Chipset where each Chipset controls 2 ports each (ie (1 Chipset - 2 Ports) * 2). In the latest 20.04.2 LTS, the OS is mapping the ports incorrectly, causing only 2 of the 4 total ports to be allocated via DMESG: thannock@nwtools04-usdc7:~$ lspci 00:00.0 Host bridge: Intel Corporation 5000P Chipset Memory Controller Hub (rev b1) 00:02.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 2 (rev b1) 00:03.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 3 (rev b1) 00:04.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 4-5 (rev b1) 00:05.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 5 (rev b1) 00:06.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 6 (rev b1) 00:07.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 7 (rev b1) 00:10.0 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev b1) 00:10.1 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev b1) 00:10.2 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev b1) 00:11.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev b1) 00:13.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev b1) 00:15.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev b1) 00:16.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev b1) 00:1d.0 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #1 (rev 09) 00:1d.1 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #2 (rev 09) 00:1d.2 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #3 (rev 09) 00:1d.3 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #4 (rev 09) 00:1d.7 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset EHCI USB2 Controller (rev 09) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d9) 00:1f.0 ISA bridge: Intel Corporation 631xESB/632xESB/3100 Chipset LPC Interface Controller (rev 09) 00:1f.1 IDE interface: Intel Corporation 631xESB/632xESB IDE Controller (rev 09) 01:03.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] ES1000 (rev 02) 01:04.0 System peripheral: Compaq Computer Corporation Integrated Lights Out Controller (rev 03) 01:04.2 System peripheral: Compaq Computer Corporation Integrated Lights Out Processor (rev 03) 01:04.4 USB controller: Hewlett-Packard Company Integrated Lights-Out Standard Virtual USB Controller 01:04.6 IPMI Interface: Hewlett-Packard Company Integrated Lights-Out Standard KCS Interface 02:00.0 PCI bridge: Broadcom EPB PCI-Express to PCI-X Bridge (rev c3) 03:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme II BCM5708 Gigabit Ethernet (rev 12) 04:00.0 PCI bridge: Broadcom EPB PCI-Express to PCI-X Bridge (rev c3) 05:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme II BCM5708 Gigabit Ethernet (rev 12) 06:00.0 PCI bridge: Broadcom EPB PCI-Express to PCI-X Bridge (rev b4) 07:04.0 PCI bridge: Broadcom BCM5785 [HT1000] PCI/PCI-X Bridge (rev b2) 07:08.0 RAID bus controller: Hewlett-Packard Company Smart Array E200i (SAS Controller) 09:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Upstream Port (rev 01) 09:00.3 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express to PCI-X Bridge (rev 01) 0a:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E1 (rev 01) 0a:01.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E2 (rev 01) 0a:02.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E3 (rev 01) 0b:00.0 PCI bridge: Microsemi / PMC / IDT PES12N3A 12-lane 3-Port PCI Express Switch (rev 0e) 0c:02.0 PCI bridge: Microsemi / PMC / IDT PES12N3A 12-lane
[Kernel-packages] [Bug 1908264] Re: Disable Atari partition support for cloud kernels
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- groovy' to 'verification-done-groovy'. If the problem still exists, change the tag 'verification-needed-groovy' to 'verification-failed- groovy'. 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-groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1908264 Title: Disable Atari partition support for cloud kernels Status in linux-aws package in Ubuntu: In Progress Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-4.15 package in Ubuntu: Invalid Status in linux-gcp package in Ubuntu: New Status in linux-gke package in Ubuntu: New Status in linux-gkeop package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-aws source package in Xenial: Fix Committed Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-4.15 source package in Xenial: Invalid Status in linux-aws source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Invalid Status in linux-azure-4.15 source package in Bionic: Fix Released Status in linux-gcp source package in Bionic: Fix Committed Status in linux-oracle source package in Bionic: Fix Committed Status in linux-aws source package in Focal: Fix Released Status in linux-azure source package in Focal: Fix Released Status in linux-azure-4.15 source package in Focal: Invalid Status in linux-gcp source package in Focal: Fix Committed Status in linux-gke source package in Focal: Fix Committed Status in linux-gkeop source package in Focal: Fix Committed Status in linux-oracle source package in Focal: Fix Committed Status in linux-aws source package in Groovy: Fix Committed Status in linux-azure source package in Groovy: Fix Released Status in linux-azure-4.15 source package in Groovy: Invalid Status in linux-gcp source package in Groovy: Fix Committed Status in linux-oracle source package in Groovy: Fix Committed Status in linux-aws source package in Hirsute: In Progress Status in linux-azure source package in Hirsute: Fix Released Status in linux-azure-4.15 source package in Hirsute: Invalid Status in linux-gcp source package in Hirsute: New Status in linux-oracle source package in Hirsute: New Bug description: [Impact] Atari partition tables have very broad specifications, and can spontaneously show up on uncleared disks with "garbage" data. There have been reports of misinterpreted AHDI partition tables before (see [0] and [1]), usually as an unintended side-effect of using non-zeroed disks. Users of this specific partition scheme are unlikely to be on AWS instances, so we should disable them. [0] https://lore.kernel.org/linux-block/1467736712-11825-1-git-send-email-kris...@linux.vnet.ibm.com/ [1] https://mail-index.netbsd.org/port-atari/1995/11/19/0001.html [Test Case] Ensure that CONFIG_ATARI_PARTITION is not set in /boot/config-$(uname -r) [Fix] Unset CONFIG_ATARI_PARTITION in debian.aws/config/config.common.ubuntu [Regression Potential] There could be unexpected dependencies on Atari partitions that are impacted by this change. Considering Atari hardware hasn't been produced in a long time, and is unlikely to be used in AWS instances, the regression potential should be very low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1908264/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922582] Re: linux-azure: Enable CONFIG_FPGA_MGR_XILINX_SPI for Azure cloud kernel
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- groovy' to 'verification-done-groovy'. If the problem still exists, change the tag 'verification-needed-groovy' to 'verification-failed- groovy'. 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-groovy -- 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/1922582 Title: linux-azure: Enable CONFIG_FPGA_MGR_XILINX_SPI for Azure cloud kernel Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-4.15 package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Invalid Status in linux-azure-4.15 source package in Bionic: Fix Committed Status in linux-azure source package in Focal: Fix Committed Status in linux-azure-4.15 source package in Focal: Invalid Status in linux-azure source package in Groovy: Fix Committed Status in linux-azure-4.15 source package in Groovy: Invalid Status in linux-azure source package in Hirsute: Fix Released Status in linux-azure-4.15 source package in Hirsute: Invalid Bug description: [SRU Justification] Microsoft Azure clouds support the use of a Xilinx FPGA to accelerate machine learning and other high performance tasks. The master kernels have had this option since the beginning. The lack of this option for Azure appears to have been an oversight. [Fix] Enable CONFIG_FPGA=m and CONFIG_FPGA_MGR_XILINX_SPI=m. Add these modules to the inclusion list. [Test Plan] modprobe xilinx-spi [Where problems could occur] The chances for regression are minimal as all additions are modules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1922582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925241] Re: Disable CONFIG_DELL_SMBIOS_SMM, CONFIG_DELL_UART_BACKLIGHT, CONFIG_I2C_AMD_MP2
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- groovy' to 'verification-done-groovy'. If the problem still exists, change the tag 'verification-needed-groovy' to 'verification-failed- groovy'. 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-groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1925241 Title: Disable CONFIG_DELL_SMBIOS_SMM, CONFIG_DELL_UART_BACKLIGHT, CONFIG_I2C_AMD_MP2 Status in linux package in Ubuntu: Invalid Status in linux-gcp package in Ubuntu: In Progress Status in linux-gcp-5.8 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-gcp source package in Focal: Invalid Status in linux-gcp-5.8 source package in Focal: In Progress Status in linux source package in Groovy: Invalid Status in linux-gcp source package in Groovy: Fix Committed Status in linux-gcp-5.8 source package in Groovy: Invalid Status in linux source package in Hirsute: Invalid Status in linux-gcp source package in Hirsute: In Progress Status in linux-gcp-5.8 source package in Hirsute: Invalid Bug description: SRU Justification: Enforcement annotations indicate that these config options should never have been set. [Impact] Disable these options for hardware that does not exist in the Google cloud fabric. There should be no impact to existing users. [Fix] CONFIG_DELL_SMBIOS_SMM=n CONFIG_DELL_UART_BACKLIGHT=n CONFIG_I2C_AMD_MP2=n [Test Plan] Boot a GCP instance and ensure there are no new kernel log errors. [Where problems could occur] Regression potential should be low since this HW does not exists in a GCP guest instance. [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925241/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925964] Re: HP NC364T NIC with 20.04.2 LTS Issues
** Package changed: 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/1925964 Title: HP NC364T NIC with 20.04.2 LTS Issues Status in linux package in Ubuntu: New Bug description: This NIC is a 4 Port Copper 1GB Intel 82571B/82571GB Gigabit Ethernet Controller with a Dual Chipset where each Chipset controls 2 ports each (ie (1 Chipset - 2 Ports) * 2). In the latest 20.04.2 LTS, the OS is mapping the ports incorrectly, causing only 2 of the 4 total ports to be allocated via DMESG: thannock@nwtools04-usdc7:~$ lspci 00:00.0 Host bridge: Intel Corporation 5000P Chipset Memory Controller Hub (rev b1) 00:02.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 2 (rev b1) 00:03.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 3 (rev b1) 00:04.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 4-5 (rev b1) 00:05.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 5 (rev b1) 00:06.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 6 (rev b1) 00:07.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 7 (rev b1) 00:10.0 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev b1) 00:10.1 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev b1) 00:10.2 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev b1) 00:11.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev b1) 00:13.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev b1) 00:15.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev b1) 00:16.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev b1) 00:1d.0 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #1 (rev 09) 00:1d.1 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #2 (rev 09) 00:1d.2 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #3 (rev 09) 00:1d.3 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #4 (rev 09) 00:1d.7 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset EHCI USB2 Controller (rev 09) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d9) 00:1f.0 ISA bridge: Intel Corporation 631xESB/632xESB/3100 Chipset LPC Interface Controller (rev 09) 00:1f.1 IDE interface: Intel Corporation 631xESB/632xESB IDE Controller (rev 09) 01:03.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] ES1000 (rev 02) 01:04.0 System peripheral: Compaq Computer Corporation Integrated Lights Out Controller (rev 03) 01:04.2 System peripheral: Compaq Computer Corporation Integrated Lights Out Processor (rev 03) 01:04.4 USB controller: Hewlett-Packard Company Integrated Lights-Out Standard Virtual USB Controller 01:04.6 IPMI Interface: Hewlett-Packard Company Integrated Lights-Out Standard KCS Interface 02:00.0 PCI bridge: Broadcom EPB PCI-Express to PCI-X Bridge (rev c3) 03:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme II BCM5708 Gigabit Ethernet (rev 12) 04:00.0 PCI bridge: Broadcom EPB PCI-Express to PCI-X Bridge (rev c3) 05:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme II BCM5708 Gigabit Ethernet (rev 12) 06:00.0 PCI bridge: Broadcom EPB PCI-Express to PCI-X Bridge (rev b4) 07:04.0 PCI bridge: Broadcom BCM5785 [HT1000] PCI/PCI-X Bridge (rev b2) 07:08.0 RAID bus controller: Hewlett-Packard Company Smart Array E200i (SAS Controller) 09:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Upstream Port (rev 01) 09:00.3 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express to PCI-X Bridge (rev 01) 0a:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E1 (rev 01) 0a:01.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E2 (rev 01) 0a:02.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E3 (rev 01) 0b:00.0 PCI bridge: Microsemi / PMC / IDT PES12N3A 12-lane 3-Port PCI Express Switch (rev 0e) 0c:02.0 PCI bridge: Microsemi / PMC / IDT PES12N3A 12-lane 3-Port PCI Express Switch (rev 0e) 0c:04.0 PCI bridge: Microsemi / PMC / IDT PES12N3A 12-lane 3-Port PCI Express Switch (rev 0e) 0d:00.0 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller (Copper) (rev 06) 0d:00.1 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller (Copper) (rev 06) 0e:00.0 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller (Copper) (rev 06) 0e:00.1 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller
[Kernel-packages] [Bug 1925964] [NEW] HP NC364T NIC with 20.04.2 LTS Issues
You have been subscribed to a public bug: This NIC is a 4 Port Copper 1GB Intel 82571B/82571GB Gigabit Ethernet Controller with a Dual Chipset where each Chipset controls 2 ports each (ie (1 Chipset - 2 Ports) * 2). In the latest 20.04.2 LTS, the OS is mapping the ports incorrectly, causing only 2 of the 4 total ports to be allocated via DMESG: thannock@nwtools04-usdc7:~$ lspci 00:00.0 Host bridge: Intel Corporation 5000P Chipset Memory Controller Hub (rev b1) 00:02.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 2 (rev b1) 00:03.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 3 (rev b1) 00:04.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 4-5 (rev b1) 00:05.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 5 (rev b1) 00:06.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 6 (rev b1) 00:07.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 7 (rev b1) 00:10.0 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev b1) 00:10.1 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev b1) 00:10.2 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev b1) 00:11.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev b1) 00:13.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev b1) 00:15.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev b1) 00:16.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev b1) 00:1d.0 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #1 (rev 09) 00:1d.1 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #2 (rev 09) 00:1d.2 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #3 (rev 09) 00:1d.3 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #4 (rev 09) 00:1d.7 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset EHCI USB2 Controller (rev 09) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d9) 00:1f.0 ISA bridge: Intel Corporation 631xESB/632xESB/3100 Chipset LPC Interface Controller (rev 09) 00:1f.1 IDE interface: Intel Corporation 631xESB/632xESB IDE Controller (rev 09) 01:03.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] ES1000 (rev 02) 01:04.0 System peripheral: Compaq Computer Corporation Integrated Lights Out Controller (rev 03) 01:04.2 System peripheral: Compaq Computer Corporation Integrated Lights Out Processor (rev 03) 01:04.4 USB controller: Hewlett-Packard Company Integrated Lights-Out Standard Virtual USB Controller 01:04.6 IPMI Interface: Hewlett-Packard Company Integrated Lights-Out Standard KCS Interface 02:00.0 PCI bridge: Broadcom EPB PCI-Express to PCI-X Bridge (rev c3) 03:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme II BCM5708 Gigabit Ethernet (rev 12) 04:00.0 PCI bridge: Broadcom EPB PCI-Express to PCI-X Bridge (rev c3) 05:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme II BCM5708 Gigabit Ethernet (rev 12) 06:00.0 PCI bridge: Broadcom EPB PCI-Express to PCI-X Bridge (rev b4) 07:04.0 PCI bridge: Broadcom BCM5785 [HT1000] PCI/PCI-X Bridge (rev b2) 07:08.0 RAID bus controller: Hewlett-Packard Company Smart Array E200i (SAS Controller) 09:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Upstream Port (rev 01) 09:00.3 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express to PCI-X Bridge (rev 01) 0a:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E1 (rev 01) 0a:01.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E2 (rev 01) 0a:02.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E3 (rev 01) 0b:00.0 PCI bridge: Microsemi / PMC / IDT PES12N3A 12-lane 3-Port PCI Express Switch (rev 0e) 0c:02.0 PCI bridge: Microsemi / PMC / IDT PES12N3A 12-lane 3-Port PCI Express Switch (rev 0e) 0c:04.0 PCI bridge: Microsemi / PMC / IDT PES12N3A 12-lane 3-Port PCI Express Switch (rev 0e) 0d:00.0 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller (Copper) (rev 06) 0d:00.1 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller (Copper) (rev 06) 0e:00.0 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller (Copper) (rev 06) 0e:00.1 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller (Copper) (rev 06) 14:00.0 Ethernet controller: Intel Corporation 82598EB 10-Gigabit AF Dual Port Network Connection (rev 01) 14:00.1 Ethernet controller: Intel Corporation 82598EB 10-Gigabit AF Dual Port Network Connection (rev 01) thannock@nwtools04-usdc7:~$ lspci -v (ie ONLY NC364T captured) 0d:00.0 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit Ethernet
[Kernel-packages] [Bug 1923062] Re: NVIDIA CVE-2021-1076 CVE-2021-1077
This bug was fixed in the package nvidia-graphics-drivers-390 - 390.143-0ubuntu0.20.10.1 --- nvidia-graphics-drivers-390 (390.143-0ubuntu0.20.10.1) groovy; urgency=medium * New upstream release (LP: #1923062). * debian/templates/dkms_nvidia.conf.in: - Drop buildfix_kernel_5.11.patch. -- Alberto Milone Fri, 09 Apr 2021 16:55:21 +0200 ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Groovy) Status: In Progress => Fix Released ** Changed in: nvidia-graphics-drivers-450 (Ubuntu Groovy) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1923062 Title: NVIDIA CVE-2021-1076 CVE-2021-1077 Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Focal: Fix Released Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-390 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Released Bug description: Here is the list of the affected drivers: 418-server - CVE-2021-1076 460, 450, 460-server, 450-server - CVE-2021-1076 CVE-2021-1077 390 - CVE-2021-1076 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1923062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923062] Re: NVIDIA CVE-2021-1076 CVE-2021-1077
This bug was fixed in the package nvidia-graphics-drivers-450 - 450.119.03-0ubuntu0.20.10.1 --- nvidia-graphics-drivers-450 (450.119.03-0ubuntu0.20.10.1) groovy; urgency=medium * New upstream release (LP: #1923062). * debian/templates/dkms_nvidia.conf.in: - Drop buildfix_kernel_5.11.patch. -- Alberto Milone Fri, 09 Apr 2021 16:21:52 +0200 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1923062 Title: NVIDIA CVE-2021-1076 CVE-2021-1077 Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Focal: Fix Released Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-390 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Released Bug description: Here is the list of the affected drivers: 418-server - CVE-2021-1076 460, 450, 460-server, 450-server - CVE-2021-1076 CVE-2021-1077 390 - CVE-2021-1076 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1923062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925768] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1925768 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925768 Title: Losing Wifi connection when USB-C Hub was plugged-in Status in linux package in Ubuntu: Incomplete Bug description: Hello Ubuntu community, I have a problem with my system: when i connect my new USB-C hub to my Intel Nuc, my wifi-connection get disconnected and try to reconnect to my Wifi. The System cannot connect until i disconnect my USB-C hub. I also tries do disable the cable-connection-Ports without success. I always receive the message: could not connect to wifi... My OS: Ubuntu 20.04.2 LTS always up to date. Here is my Nuc: https://www.notebooksbilliger.de/intel+nuc+kit+nuc8i3bek2+388252?gclid=Cj0KCQjw4ImEBhDFARIsAGOTMj_in7Zc6RBlqYMqtxrxwSDscYZsqcbmHjb9JM_ipyPl3cFjDsigaDsaAqOpEALw_wcB_id=Cj0KCQjw4ImEBhDFARIsAGOTMj_in7Zc6RBlqYMqtxrxwSDscYZsqcbmHjb9JM_ipyPl3cFjDsigaDsaAqOpEALw_wcB:G:s_kwcid=AL!8069!3!504856654760!!!g!626707857982!=6004 Link to my Adapter: https://www.amazon.de/1-Adapter-USB-C-Stromversorgung-RJ45-Gigabit- Ethernet-TF-Kartenleser-5-mm- Audiobuchse/dp/B08N424Y25/ref=sr_1_4?__mk_de_DE=%C3%85M%C3%85%C5%BD%C3%95%C3%91=1=usb+c+hub=1619169213=8-4 Best Regards Miro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925768] Re: Losing Wifi connection when USB-C Hub was plugged-in
** Project changed: ubuntu-cdimage => 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/1925768 Title: Losing Wifi connection when USB-C Hub was plugged-in Status in linux package in Ubuntu: Incomplete Bug description: Hello Ubuntu community, I have a problem with my system: when i connect my new USB-C hub to my Intel Nuc, my wifi-connection get disconnected and try to reconnect to my Wifi. The System cannot connect until i disconnect my USB-C hub. I also tries do disable the cable-connection-Ports without success. I always receive the message: could not connect to wifi... My OS: Ubuntu 20.04.2 LTS always up to date. Here is my Nuc: https://www.notebooksbilliger.de/intel+nuc+kit+nuc8i3bek2+388252?gclid=Cj0KCQjw4ImEBhDFARIsAGOTMj_in7Zc6RBlqYMqtxrxwSDscYZsqcbmHjb9JM_ipyPl3cFjDsigaDsaAqOpEALw_wcB_id=Cj0KCQjw4ImEBhDFARIsAGOTMj_in7Zc6RBlqYMqtxrxwSDscYZsqcbmHjb9JM_ipyPl3cFjDsigaDsaAqOpEALw_wcB:G:s_kwcid=AL!8069!3!504856654760!!!g!626707857982!=6004 Link to my Adapter: https://www.amazon.de/1-Adapter-USB-C-Stromversorgung-RJ45-Gigabit- Ethernet-TF-Kartenleser-5-mm- Audiobuchse/dp/B08N424Y25/ref=sr_1_4?__mk_de_DE=%C3%85M%C3%85%C5%BD%C3%95%C3%91=1=usb+c+hub=1619169213=8-4 Best Regards Miro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925768] [NEW] Losing Wifi connection when USB-C Hub was plugged-in
You have been subscribed to a public bug: Hello Ubuntu community, I have a problem with my system: when i connect my new USB-C hub to my Intel Nuc, my wifi-connection get disconnected and try to reconnect to my Wifi. The System cannot connect until i disconnect my USB-C hub. I also tries do disable the cable-connection-Ports without success. I always receive the message: could not connect to wifi... My OS: Ubuntu 20.04.2 LTS always up to date. Here is my Nuc: https://www.notebooksbilliger.de/intel+nuc+kit+nuc8i3bek2+388252?gclid=Cj0KCQjw4ImEBhDFARIsAGOTMj_in7Zc6RBlqYMqtxrxwSDscYZsqcbmHjb9JM_ipyPl3cFjDsigaDsaAqOpEALw_wcB_id=Cj0KCQjw4ImEBhDFARIsAGOTMj_in7Zc6RBlqYMqtxrxwSDscYZsqcbmHjb9JM_ipyPl3cFjDsigaDsaAqOpEALw_wcB:G:s_kwcid=AL!8069!3!504856654760!!!g!626707857982!=6004 Link to my Adapter: https://www.amazon.de/1-Adapter-USB-C-Stromversorgung-RJ45-Gigabit- Ethernet-TF-Kartenleser-5-mm- Audiobuchse/dp/B08N424Y25/ref=sr_1_4?__mk_de_DE=%C3%85M%C3%85%C5%BD%C3%95%C3%91=1=usb+c+hub=1619169213=8-4 Best Regards Miro ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: connection hub problem usb-c wifi with -- Losing Wifi connection when USB-C Hub was plugged-in https://bugs.launchpad.net/bugs/1925768 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 1910562] Re: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34
Hi Sergio. First of all, thank you (and anyone else involved) for your time investigating in the issue. > Could you please try to run the command several times, specifying the different chip I did not find how to specify a certain chip with the 'sensors' command after reading the man page. But I'm sure the problem happens when sensors tries to read the temperature from the AMD discrete graphics card, because when the console output of sensors reaches this section during the scan: amdgpu-pci-0100 Adapter: PCI adapter [ --> HERE IT HANGS FOR 2 SECS <-- ] vddgfx:1.05 V edge: +42.0°C (crit = +94.0°C, hyst = -273.1°C) power1:7.11 W (cap = 35.00 W) it hangs for a couple of seconds and two things happens: 1. the fans start spinning 2. I see an drm related warning appearing in the dmesg logs: [ 41.397707] [drm] PCIE GART of 256M enabled (table at 0x00F4). [ 42.609649] [drm:dce110_edp_wait_for_hpd_ready [amdgpu]] *ERROR* dce110_edp_wait_for_hpd_ready: wait timed out! [ 43.213733] [drm:dce110_edp_wait_for_hpd_ready [amdgpu]] *ERROR* dce110_edp_wait_for_hpd_ready: wait timed out! [ 43.242390] [drm] UVD and UVD ENC initialized successfully. [ 43.352370] [drm] VCE initialized successfully. [ 43.358578] amdgpu :01:00.0: [drm] Cannot find any crtc or sizes Could it be that scanning the amdgpu-pci-0100 causes the AMD card to reset and this is related to the fans starting ? > you were able to reproduce this problem not only in Ubuntu, but also in other distributions. Is that correct ? I was able to reproduce on Ubuntu 20.04 with all 5.8 kernels available and with a 5.10.0-14 kernel installed from Hirsute beta repositories. However today I made some tests again using my stable 20.04 and also the just released final Hirsute 21.04 from a live USB. Below the results of running the 'sensors' command in terminal, ordered by Ubuntu version and kernel: 1. 20.04, 5.4.0-59-generic #65-Ubuntu SMP - everything ok - no fans spinning - no dmesg warinings - no sensors hanging during scan: amdgpu-pci-0100 Adapter: PCI adapter vddgfx: N/A edge: N/A (crit = +94.0°C, hyst = -273.1°C) power1: N/A (cap = 35.00 W) 2. 20.04, 5.8.0-50-generic #56~20.04.1-Ubuntu SMP - problem present - fans spinning - sensors hangs during output when reaching amd section: amdgpu-pci-0100 Adapter: PCI adapter [ 2 SECS ] vddgfx:1.05 V edge: +38.0°C (crit = +94.0°C, hyst = -273.1°C) power1:7.12 W (cap = 35.00 W) - dmesg warnings appearing when fans start: [ 41.397707] [drm] PCIE GART of 256M enabled (table at 0x00F4). [ 42.609649] [drm:dce110_edp_wait_for_hpd_ready [amdgpu]] *ERROR* dce110_edp_wait_for_hpd_ready: wait timed out! [ 43.213733] [drm:dce110_edp_wait_for_hpd_ready [amdgpu]] *ERROR* dce110_edp_wait_for_hpd_ready: wait timed out! [ 43.242390] [drm] UVD and UVD ENC initialized successfully. [ 43.352370] [drm] VCE initialized successfully. [ 43.358578] amdgpu :01:00.0: [drm] Cannot find any crtc or sizes 3. USB/Live 21.04, 5.11.0-16-generic #17-Ubuntu SMP - problem present - fans spinning - sensors hangs during output when reaching amd section: amdgpu-pci-0100 Adapter: PCI adapter [ 2 SECS ] vddgfx:1.05 V edge: +38.0°C (crit = +94.0°C, hyst = -273.1°C) power1:7.12 W (cap = 35.00 W) - dmesg warnings appearing when fans start (slightly different from 5.8.0-50): [ 301.476682] [drm] PCIE GART of 256M enabled (table at 0x00F4). [ 301.681312] [drm] UVD and UVD ENC initialized successfully. [ 301.791290] [drm] VCE initialized successfully. [ 301.797151] amdgpu :01:00.0: [drm] Cannot find any crtc or sizes [ 302.099911] drm_dp_i2c_do_msg: 14 callbacks suppressed [ 302.196470] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon [ 302.196534] [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D [ 303.115752] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon [ 303.115829] [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D So the only kernel without this problem is the old 5.4, but I suspect that with that kernel the sensor real measurement is not happening because there are no voltage/temps readings but only N/A (maybe it was not yet implemented and this is only a stub/dummy output) > If it is, do you think you could test a pristine Linux kernel (from > https://kernel.org)? I'll try as soon as possible and report back the results. In the meantime, thanks again and please feel free to ask any more questions/tests. Regards, Gabriele. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910562 Title: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34 Status in linux package in Ubuntu: Incomplete Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Status in
[Kernel-packages] [Bug 1925008] Re: no memory hot-plugging in cloud-images
Patch submitted: https://lists.ubuntu.com/archives/kernel- team/2021-April/119497.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1925008 Title: no memory hot-plugging in cloud-images Status in cloud-images: Invalid Status in linux package in Ubuntu: Fix Released Status in linux-kvm package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in linux-kvm source package in Focal: In Progress Status in linux source package in Groovy: Fix Released Status in linux-kvm source package in Groovy: In Progress Status in linux source package in Hirsute: Fix Released Status in linux-kvm source package in Hirsute: In Progress Bug description: SRU Justification [Impact] Memory hot-plugging is not working with public cloud-images. Error with dmesg shows: [ 184.544535] acpi PNP0C80:00: Enumeration failure checking kernel configuration: root@ubuntu:/boot# uname -r 5.4.0-1038-kvm root@ubuntu:/boot# grep CONFIG_ACPI_HOTPLUG_MEMORY config-5.4.0-1038-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set Obviously the necessary kernel configuration for ACPI memory hotplug is missing. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20210415 --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1038-kvm root=PARTUUID=a204284f-e3de-498d-a306-c4e7f6b62831 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 5.4.0-1038.39-kvm 5.4.101 RelatedPackageVersions: linux-restricted-modules-5.4.0-1038-kvm N/A linux-backports-modules-5.4.0-1038-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1038-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.7 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.7 dmi.sys.vendor: QEMU [Test Plan] Boot a kernel with CONFIG_ACPI_HOTPLUG_MEMORY enabled. Check that requested memory has been added. [Where problems could occur] Adding memory could fail, or cause other configurations issues. Regressions seem unlikely since this config option is enabled in all cloud kernels except linux-azure. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925843] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925843 Title: Linux 5.8.0-49+ fails to resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: Expected Result: System resumes from suspend and displays the log in screen to unlock the computer. Actual Result: System displays a black screen with a flashing cursor in the upper left and cannot be interacted with. Hard reboot is required to get back to a working system. Additional information: When I boot my computer with 5.8.0-48, the system resumes from suspend as expected. Both 5.8.0-49 and 5.8.0-50 fail to resume from suspend. This problem began after I updated from 20.04 to 20.10 using the Software Updater on 4-19-21. I was using the latest kernel available for 20.04 at that time (5.8.0-48, I think) before updating. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-50-generic 5.8.0-50.56 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steven 1268 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 23 12:54:52 2021 InstallationDate: Installed on 2020-09-01 (234 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:58eb Realtek Semiconductor Corp. HP Wide Vision HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP OMEN by HP Laptop 15-ce0xx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=208c1c0d-3e9e-43da-ba24-0d1cd92b5ad0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.release: 15.23 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.23 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 838F dmi.board.vendor: HP dmi.board.version: 40.28 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.28 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.23:bd10/30/2020:br15.23:efr40.28:svnHP:pnOMENbyHPLaptop15-ce0xx:pvr:rvnHP:rn838F:rvr40.28:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 15-ce0xx dmi.product.sku: 1KV78UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925843/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910562] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1910562/+attachment/5491552/+files/acpidump.txt ** Changed in: linux-signed-hwe-5.8 (Ubuntu) Status: Invalid => 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/1910562 Title: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34 Status in linux package in Ubuntu: Incomplete Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Status in lm-sensors package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Bug description: After updating via apt dist-upgrade from kernel 5.4.0-59 to kernel 5.8.0-34 the fan on my machine started switching on (for an instant) and off every 10 seconds even when idle with CPU at 48/50°C. Switching back to previous kernel solves temporary the problem, i.e. fans are always off with light desktop work. The new behavior is really annoying and I guess not healthy for the fans. I'm on latest Dell bios, with every other package updated. Di something in the thermal policies change between those two kernels? Is it possible to go back to previous behavior ? Thanks in advance for help Machine: Dell Precison 7540, intel i7-9750 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 17:14:54 2021 InstallationDate: Installed on 2020-05-06 (246 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gabriele 2370 F pulseaudio /dev/snd/controlC1: gabriele 2370 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-06 (352 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision 7540 Package: lm-sensors 1:3.6.0-2ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=c39f518b-f5c9-47c5-8e7f-42d970d2dedb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.11 Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 01/08/2021 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.2 dmi.board.name: 0XMC3F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.2:bd01/08/2021:br1.11:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0XMC3F:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7540 dmi.product.sku: 0926 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910562/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910562] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1910562/+attachment/5491551/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910562 Title: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34 Status in linux package in Ubuntu: Incomplete Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Status in lm-sensors package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Bug description: After updating via apt dist-upgrade from kernel 5.4.0-59 to kernel 5.8.0-34 the fan on my machine started switching on (for an instant) and off every 10 seconds even when idle with CPU at 48/50°C. Switching back to previous kernel solves temporary the problem, i.e. fans are always off with light desktop work. The new behavior is really annoying and I guess not healthy for the fans. I'm on latest Dell bios, with every other package updated. Di something in the thermal policies change between those two kernels? Is it possible to go back to previous behavior ? Thanks in advance for help Machine: Dell Precison 7540, intel i7-9750 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 17:14:54 2021 InstallationDate: Installed on 2020-05-06 (246 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gabriele 2370 F pulseaudio /dev/snd/controlC1: gabriele 2370 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-06 (352 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision 7540 Package: lm-sensors 1:3.6.0-2ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=c39f518b-f5c9-47c5-8e7f-42d970d2dedb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.11 Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 01/08/2021 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.2 dmi.board.name: 0XMC3F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.2:bd01/08/2021:br1.11:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0XMC3F:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7540 dmi.product.sku: 0926 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910562/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910562] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1910562/+attachment/5491550/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910562 Title: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34 Status in linux package in Ubuntu: Incomplete Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Status in lm-sensors package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Bug description: After updating via apt dist-upgrade from kernel 5.4.0-59 to kernel 5.8.0-34 the fan on my machine started switching on (for an instant) and off every 10 seconds even when idle with CPU at 48/50°C. Switching back to previous kernel solves temporary the problem, i.e. fans are always off with light desktop work. The new behavior is really annoying and I guess not healthy for the fans. I'm on latest Dell bios, with every other package updated. Di something in the thermal policies change between those two kernels? Is it possible to go back to previous behavior ? Thanks in advance for help Machine: Dell Precison 7540, intel i7-9750 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 17:14:54 2021 InstallationDate: Installed on 2020-05-06 (246 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gabriele 2370 F pulseaudio /dev/snd/controlC1: gabriele 2370 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-06 (352 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision 7540 Package: lm-sensors 1:3.6.0-2ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=c39f518b-f5c9-47c5-8e7f-42d970d2dedb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.11 Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 01/08/2021 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.2 dmi.board.name: 0XMC3F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.2:bd01/08/2021:br1.11:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0XMC3F:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7540 dmi.product.sku: 0926 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910562/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910562] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1910562/+attachment/5491549/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910562 Title: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34 Status in linux package in Ubuntu: Incomplete Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Status in lm-sensors package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Bug description: After updating via apt dist-upgrade from kernel 5.4.0-59 to kernel 5.8.0-34 the fan on my machine started switching on (for an instant) and off every 10 seconds even when idle with CPU at 48/50°C. Switching back to previous kernel solves temporary the problem, i.e. fans are always off with light desktop work. The new behavior is really annoying and I guess not healthy for the fans. I'm on latest Dell bios, with every other package updated. Di something in the thermal policies change between those two kernels? Is it possible to go back to previous behavior ? Thanks in advance for help Machine: Dell Precison 7540, intel i7-9750 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 17:14:54 2021 InstallationDate: Installed on 2020-05-06 (246 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gabriele 2370 F pulseaudio /dev/snd/controlC1: gabriele 2370 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-06 (352 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision 7540 Package: lm-sensors 1:3.6.0-2ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=c39f518b-f5c9-47c5-8e7f-42d970d2dedb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.11 Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 01/08/2021 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.2 dmi.board.name: 0XMC3F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.2:bd01/08/2021:br1.11:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0XMC3F:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7540 dmi.product.sku: 0926 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910562/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910562] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1910562/+attachment/5491548/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910562 Title: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34 Status in linux package in Ubuntu: Incomplete Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Status in lm-sensors package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Bug description: After updating via apt dist-upgrade from kernel 5.4.0-59 to kernel 5.8.0-34 the fan on my machine started switching on (for an instant) and off every 10 seconds even when idle with CPU at 48/50°C. Switching back to previous kernel solves temporary the problem, i.e. fans are always off with light desktop work. The new behavior is really annoying and I guess not healthy for the fans. I'm on latest Dell bios, with every other package updated. Di something in the thermal policies change between those two kernels? Is it possible to go back to previous behavior ? Thanks in advance for help Machine: Dell Precison 7540, intel i7-9750 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 17:14:54 2021 InstallationDate: Installed on 2020-05-06 (246 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gabriele 2370 F pulseaudio /dev/snd/controlC1: gabriele 2370 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-06 (352 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision 7540 Package: lm-sensors 1:3.6.0-2ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=c39f518b-f5c9-47c5-8e7f-42d970d2dedb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.11 Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 01/08/2021 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.2 dmi.board.name: 0XMC3F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.2:bd01/08/2021:br1.11:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0XMC3F:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7540 dmi.product.sku: 0926 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910562/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910562] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1910562/+attachment/5491547/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910562 Title: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34 Status in linux package in Ubuntu: Incomplete Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Status in lm-sensors package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Bug description: After updating via apt dist-upgrade from kernel 5.4.0-59 to kernel 5.8.0-34 the fan on my machine started switching on (for an instant) and off every 10 seconds even when idle with CPU at 48/50°C. Switching back to previous kernel solves temporary the problem, i.e. fans are always off with light desktop work. The new behavior is really annoying and I guess not healthy for the fans. I'm on latest Dell bios, with every other package updated. Di something in the thermal policies change between those two kernels? Is it possible to go back to previous behavior ? Thanks in advance for help Machine: Dell Precison 7540, intel i7-9750 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 17:14:54 2021 InstallationDate: Installed on 2020-05-06 (246 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gabriele 2370 F pulseaudio /dev/snd/controlC1: gabriele 2370 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-06 (352 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision 7540 Package: lm-sensors 1:3.6.0-2ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=c39f518b-f5c9-47c5-8e7f-42d970d2dedb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.11 Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 01/08/2021 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.2 dmi.board.name: 0XMC3F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.2:bd01/08/2021:br1.11:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0XMC3F:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7540 dmi.product.sku: 0926 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910562/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910562] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1910562/+attachment/5491546/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910562 Title: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34 Status in linux package in Ubuntu: Incomplete Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Status in lm-sensors package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Bug description: After updating via apt dist-upgrade from kernel 5.4.0-59 to kernel 5.8.0-34 the fan on my machine started switching on (for an instant) and off every 10 seconds even when idle with CPU at 48/50°C. Switching back to previous kernel solves temporary the problem, i.e. fans are always off with light desktop work. The new behavior is really annoying and I guess not healthy for the fans. I'm on latest Dell bios, with every other package updated. Di something in the thermal policies change between those two kernels? Is it possible to go back to previous behavior ? Thanks in advance for help Machine: Dell Precison 7540, intel i7-9750 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 17:14:54 2021 InstallationDate: Installed on 2020-05-06 (246 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gabriele 2370 F pulseaudio /dev/snd/controlC1: gabriele 2370 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-06 (352 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision 7540 Package: lm-sensors 1:3.6.0-2ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=c39f518b-f5c9-47c5-8e7f-42d970d2dedb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.11 Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 01/08/2021 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.2 dmi.board.name: 0XMC3F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.2:bd01/08/2021:br1.11:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0XMC3F:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7540 dmi.product.sku: 0926 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910562/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910562] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1910562/+attachment/5491545/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910562 Title: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34 Status in linux package in Ubuntu: Incomplete Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Status in lm-sensors package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Bug description: After updating via apt dist-upgrade from kernel 5.4.0-59 to kernel 5.8.0-34 the fan on my machine started switching on (for an instant) and off every 10 seconds even when idle with CPU at 48/50°C. Switching back to previous kernel solves temporary the problem, i.e. fans are always off with light desktop work. The new behavior is really annoying and I guess not healthy for the fans. I'm on latest Dell bios, with every other package updated. Di something in the thermal policies change between those two kernels? Is it possible to go back to previous behavior ? Thanks in advance for help Machine: Dell Precison 7540, intel i7-9750 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 17:14:54 2021 InstallationDate: Installed on 2020-05-06 (246 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gabriele 2370 F pulseaudio /dev/snd/controlC1: gabriele 2370 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-06 (352 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision 7540 Package: lm-sensors 1:3.6.0-2ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=c39f518b-f5c9-47c5-8e7f-42d970d2dedb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.11 Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 01/08/2021 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.2 dmi.board.name: 0XMC3F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.2:bd01/08/2021:br1.11:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0XMC3F:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7540 dmi.product.sku: 0926 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910562/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910562] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1910562/+attachment/5491544/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910562 Title: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34 Status in linux package in Ubuntu: Incomplete Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Status in lm-sensors package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Bug description: After updating via apt dist-upgrade from kernel 5.4.0-59 to kernel 5.8.0-34 the fan on my machine started switching on (for an instant) and off every 10 seconds even when idle with CPU at 48/50°C. Switching back to previous kernel solves temporary the problem, i.e. fans are always off with light desktop work. The new behavior is really annoying and I guess not healthy for the fans. I'm on latest Dell bios, with every other package updated. Di something in the thermal policies change between those two kernels? Is it possible to go back to previous behavior ? Thanks in advance for help Machine: Dell Precison 7540, intel i7-9750 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 17:14:54 2021 InstallationDate: Installed on 2020-05-06 (246 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gabriele 2370 F pulseaudio /dev/snd/controlC1: gabriele 2370 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-06 (352 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision 7540 Package: lm-sensors 1:3.6.0-2ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=c39f518b-f5c9-47c5-8e7f-42d970d2dedb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.11 Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 01/08/2021 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.2 dmi.board.name: 0XMC3F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.2:bd01/08/2021:br1.11:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0XMC3F:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7540 dmi.product.sku: 0926 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910562/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910562] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1910562/+attachment/5491543/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910562 Title: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34 Status in linux package in Ubuntu: Incomplete Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Status in lm-sensors package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Bug description: After updating via apt dist-upgrade from kernel 5.4.0-59 to kernel 5.8.0-34 the fan on my machine started switching on (for an instant) and off every 10 seconds even when idle with CPU at 48/50°C. Switching back to previous kernel solves temporary the problem, i.e. fans are always off with light desktop work. The new behavior is really annoying and I guess not healthy for the fans. I'm on latest Dell bios, with every other package updated. Di something in the thermal policies change between those two kernels? Is it possible to go back to previous behavior ? Thanks in advance for help Machine: Dell Precison 7540, intel i7-9750 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 17:14:54 2021 InstallationDate: Installed on 2020-05-06 (246 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gabriele 2370 F pulseaudio /dev/snd/controlC1: gabriele 2370 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-06 (352 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision 7540 Package: lm-sensors 1:3.6.0-2ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=c39f518b-f5c9-47c5-8e7f-42d970d2dedb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.11 Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 01/08/2021 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.2 dmi.board.name: 0XMC3F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.2:bd01/08/2021:br1.11:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0XMC3F:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7540 dmi.product.sku: 0926 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910562/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910562] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1910562/+attachment/5491540/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910562 Title: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34 Status in linux package in Ubuntu: Incomplete Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Status in lm-sensors package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Bug description: After updating via apt dist-upgrade from kernel 5.4.0-59 to kernel 5.8.0-34 the fan on my machine started switching on (for an instant) and off every 10 seconds even when idle with CPU at 48/50°C. Switching back to previous kernel solves temporary the problem, i.e. fans are always off with light desktop work. The new behavior is really annoying and I guess not healthy for the fans. I'm on latest Dell bios, with every other package updated. Di something in the thermal policies change between those two kernels? Is it possible to go back to previous behavior ? Thanks in advance for help Machine: Dell Precison 7540, intel i7-9750 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 17:14:54 2021 InstallationDate: Installed on 2020-05-06 (246 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gabriele 2370 F pulseaudio /dev/snd/controlC1: gabriele 2370 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-06 (352 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision 7540 Package: lm-sensors 1:3.6.0-2ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=c39f518b-f5c9-47c5-8e7f-42d970d2dedb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.11 Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 01/08/2021 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.2 dmi.board.name: 0XMC3F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.2:bd01/08/2021:br1.11:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0XMC3F:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7540 dmi.product.sku: 0926 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910562/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910562] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1910562/+attachment/5491539/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910562 Title: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34 Status in linux package in Ubuntu: Incomplete Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Status in lm-sensors package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Bug description: After updating via apt dist-upgrade from kernel 5.4.0-59 to kernel 5.8.0-34 the fan on my machine started switching on (for an instant) and off every 10 seconds even when idle with CPU at 48/50°C. Switching back to previous kernel solves temporary the problem, i.e. fans are always off with light desktop work. The new behavior is really annoying and I guess not healthy for the fans. I'm on latest Dell bios, with every other package updated. Di something in the thermal policies change between those two kernels? Is it possible to go back to previous behavior ? Thanks in advance for help Machine: Dell Precison 7540, intel i7-9750 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 17:14:54 2021 InstallationDate: Installed on 2020-05-06 (246 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gabriele 2370 F pulseaudio /dev/snd/controlC1: gabriele 2370 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-06 (352 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision 7540 Package: lm-sensors 1:3.6.0-2ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=c39f518b-f5c9-47c5-8e7f-42d970d2dedb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.11 Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 01/08/2021 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.2 dmi.board.name: 0XMC3F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.2:bd01/08/2021:br1.11:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0XMC3F:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7540 dmi.product.sku: 0926 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910562/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910562] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1910562/+attachment/5491542/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910562 Title: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34 Status in linux package in Ubuntu: Incomplete Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Status in lm-sensors package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Bug description: After updating via apt dist-upgrade from kernel 5.4.0-59 to kernel 5.8.0-34 the fan on my machine started switching on (for an instant) and off every 10 seconds even when idle with CPU at 48/50°C. Switching back to previous kernel solves temporary the problem, i.e. fans are always off with light desktop work. The new behavior is really annoying and I guess not healthy for the fans. I'm on latest Dell bios, with every other package updated. Di something in the thermal policies change between those two kernels? Is it possible to go back to previous behavior ? Thanks in advance for help Machine: Dell Precison 7540, intel i7-9750 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 17:14:54 2021 InstallationDate: Installed on 2020-05-06 (246 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gabriele 2370 F pulseaudio /dev/snd/controlC1: gabriele 2370 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-06 (352 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision 7540 Package: lm-sensors 1:3.6.0-2ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=c39f518b-f5c9-47c5-8e7f-42d970d2dedb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.11 Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 01/08/2021 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.2 dmi.board.name: 0XMC3F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.2:bd01/08/2021:br1.11:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0XMC3F:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7540 dmi.product.sku: 0926 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910562/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910562] Re: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34
apport information ** Tags added: apport-collected ** Description changed: After updating via apt dist-upgrade from kernel 5.4.0-59 to kernel 5.8.0-34 the fan on my machine started switching on (for an instant) and off every 10 seconds even when idle with CPU at 48/50°C. Switching back to previous kernel solves temporary the problem, i.e. fans are always off with light desktop work. The new behavior is really annoying and I guess not healthy for the fans. I'm on latest Dell bios, with every other package updated. Di something in the thermal policies change between those two kernels? Is it possible to go back to previous behavior ? Thanks in advance for help Machine: Dell Precison 7540, intel i7-9750 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 17:14:54 2021 InstallationDate: Installed on 2020-05-06 (246 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.16 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: gabriele 2370 F pulseaudio + /dev/snd/controlC1: gabriele 2370 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-05-06 (352 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + MachineType: Dell Inc. Precision 7540 + Package: lm-sensors 1:3.6.0-2ubuntu1 + PackageArchitecture: amd64 + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=c39f518b-f5c9-47c5-8e7f-42d970d2dedb ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 + RelatedPackageVersions: + linux-restricted-modules-5.8.0-50-generic N/A + linux-backports-modules-5.8.0-50-generic N/A + linux-firmware1.187.11 + Tags: focal + Uname: Linux 5.8.0-50-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo vboxusers wireshark + _MarkForUpload: True + dmi.bios.date: 01/08/2021 + dmi.bios.release: 1.11 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.11.2 + dmi.board.name: 0XMC3F + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 10 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.11.2:bd01/08/2021:br1.11:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0XMC3F:rvrA00:cvnDellInc.:ct10:cvr: + dmi.product.family: Precision + dmi.product.name: Precision 7540 + dmi.product.sku: 0926 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1910562/+attachment/5491534/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910562 Title: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34 Status in linux package in Ubuntu: Incomplete Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Status in lm-sensors package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Bug description: After updating via apt dist-upgrade from kernel 5.4.0-59 to kernel 5.8.0-34 the fan on my machine started switching on (for an instant) and off every 10 seconds even when idle with CPU at 48/50°C. Switching back to previous kernel solves temporary the problem, i.e. fans are always off with light desktop work. The new behavior is really annoying and I guess not healthy for the fans. I'm on latest Dell bios, with every other package updated. Di something in the thermal policies change between those two kernels? Is it possible to go back to previous behavior ? Thanks in advance for help Machine: Dell Precison 7540, intel i7-9750 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 17:14:54 2021 InstallationDate: Installed on 2020-05-06 (246 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh
[Kernel-packages] [Bug 1910562] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1910562/+attachment/5491541/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910562 Title: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34 Status in linux package in Ubuntu: Incomplete Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Status in lm-sensors package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Bug description: After updating via apt dist-upgrade from kernel 5.4.0-59 to kernel 5.8.0-34 the fan on my machine started switching on (for an instant) and off every 10 seconds even when idle with CPU at 48/50°C. Switching back to previous kernel solves temporary the problem, i.e. fans are always off with light desktop work. The new behavior is really annoying and I guess not healthy for the fans. I'm on latest Dell bios, with every other package updated. Di something in the thermal policies change between those two kernels? Is it possible to go back to previous behavior ? Thanks in advance for help Machine: Dell Precison 7540, intel i7-9750 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 17:14:54 2021 InstallationDate: Installed on 2020-05-06 (246 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gabriele 2370 F pulseaudio /dev/snd/controlC1: gabriele 2370 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-06 (352 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision 7540 Package: lm-sensors 1:3.6.0-2ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=c39f518b-f5c9-47c5-8e7f-42d970d2dedb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.11 Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 01/08/2021 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.2 dmi.board.name: 0XMC3F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.2:bd01/08/2021:br1.11:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0XMC3F:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7540 dmi.product.sku: 0926 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910562/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910562] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1910562/+attachment/5491538/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910562 Title: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34 Status in linux package in Ubuntu: Incomplete Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Status in lm-sensors package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Bug description: After updating via apt dist-upgrade from kernel 5.4.0-59 to kernel 5.8.0-34 the fan on my machine started switching on (for an instant) and off every 10 seconds even when idle with CPU at 48/50°C. Switching back to previous kernel solves temporary the problem, i.e. fans are always off with light desktop work. The new behavior is really annoying and I guess not healthy for the fans. I'm on latest Dell bios, with every other package updated. Di something in the thermal policies change between those two kernels? Is it possible to go back to previous behavior ? Thanks in advance for help Machine: Dell Precison 7540, intel i7-9750 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 17:14:54 2021 InstallationDate: Installed on 2020-05-06 (246 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gabriele 2370 F pulseaudio /dev/snd/controlC1: gabriele 2370 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-06 (352 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision 7540 Package: lm-sensors 1:3.6.0-2ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=c39f518b-f5c9-47c5-8e7f-42d970d2dedb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.11 Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 01/08/2021 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.2 dmi.board.name: 0XMC3F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.2:bd01/08/2021:br1.11:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0XMC3F:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7540 dmi.product.sku: 0926 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910562/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910562] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1910562/+attachment/5491537/+files/Dependencies.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910562 Title: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34 Status in linux package in Ubuntu: Incomplete Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Status in lm-sensors package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Bug description: After updating via apt dist-upgrade from kernel 5.4.0-59 to kernel 5.8.0-34 the fan on my machine started switching on (for an instant) and off every 10 seconds even when idle with CPU at 48/50°C. Switching back to previous kernel solves temporary the problem, i.e. fans are always off with light desktop work. The new behavior is really annoying and I guess not healthy for the fans. I'm on latest Dell bios, with every other package updated. Di something in the thermal policies change between those two kernels? Is it possible to go back to previous behavior ? Thanks in advance for help Machine: Dell Precison 7540, intel i7-9750 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 17:14:54 2021 InstallationDate: Installed on 2020-05-06 (246 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gabriele 2370 F pulseaudio /dev/snd/controlC1: gabriele 2370 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-06 (352 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision 7540 Package: lm-sensors 1:3.6.0-2ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=c39f518b-f5c9-47c5-8e7f-42d970d2dedb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.11 Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 01/08/2021 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.2 dmi.board.name: 0XMC3F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.2:bd01/08/2021:br1.11:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0XMC3F:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7540 dmi.product.sku: 0926 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910562/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910562] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1910562/+attachment/5491536/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910562 Title: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34 Status in linux package in Ubuntu: Incomplete Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Status in lm-sensors package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Bug description: After updating via apt dist-upgrade from kernel 5.4.0-59 to kernel 5.8.0-34 the fan on my machine started switching on (for an instant) and off every 10 seconds even when idle with CPU at 48/50°C. Switching back to previous kernel solves temporary the problem, i.e. fans are always off with light desktop work. The new behavior is really annoying and I guess not healthy for the fans. I'm on latest Dell bios, with every other package updated. Di something in the thermal policies change between those two kernels? Is it possible to go back to previous behavior ? Thanks in advance for help Machine: Dell Precison 7540, intel i7-9750 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 17:14:54 2021 InstallationDate: Installed on 2020-05-06 (246 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gabriele 2370 F pulseaudio /dev/snd/controlC1: gabriele 2370 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-06 (352 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision 7540 Package: lm-sensors 1:3.6.0-2ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=c39f518b-f5c9-47c5-8e7f-42d970d2dedb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.11 Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 01/08/2021 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.2 dmi.board.name: 0XMC3F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.2:bd01/08/2021:br1.11:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0XMC3F:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7540 dmi.product.sku: 0926 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910562/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910562] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1910562/+attachment/5491535/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910562 Title: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34 Status in linux package in Ubuntu: Incomplete Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Status in lm-sensors package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Bug description: After updating via apt dist-upgrade from kernel 5.4.0-59 to kernel 5.8.0-34 the fan on my machine started switching on (for an instant) and off every 10 seconds even when idle with CPU at 48/50°C. Switching back to previous kernel solves temporary the problem, i.e. fans are always off with light desktop work. The new behavior is really annoying and I guess not healthy for the fans. I'm on latest Dell bios, with every other package updated. Di something in the thermal policies change between those two kernels? Is it possible to go back to previous behavior ? Thanks in advance for help Machine: Dell Precison 7540, intel i7-9750 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 17:14:54 2021 InstallationDate: Installed on 2020-05-06 (246 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gabriele 2370 F pulseaudio /dev/snd/controlC1: gabriele 2370 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-06 (352 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision 7540 Package: lm-sensors 1:3.6.0-2ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=c39f518b-f5c9-47c5-8e7f-42d970d2dedb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.11 Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 01/08/2021 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.2 dmi.board.name: 0XMC3F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.2:bd01/08/2021:br1.11:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0XMC3F:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7540 dmi.product.sku: 0926 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910562/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918698] Re: Stale firmware symlink
Tested linux-firmware 1.190.4. Looks good. ** Tags added: verification-done-groovy -- 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/1918698 Title: Stale firmware symlink Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Groovy: Fix Committed Bug description: [Impact] On Groovy with linux-firmware 1.190.3: lrwxrwxrwx 1 root root 54 Jan 7 15:40 brcmfmac43455-sdio.raspberrypi,3-model-a-plus.txt -> brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt That link target is wrong and doesn't exist, it should be without the 'brcm/' prefix. [Test Case] $ ls -la /lib/firmware/brcm/brcmfmac43455* [Fix] The upstream fix is: commit a9993f8d3b241f70a691a5b81bf2cdb442c0e184 Author: Takashi Iwai Date: Tue Sep 8 12:16:56 2020 +0200 brcm: Fix a stale symlink for RPi3 model b+ The symlink for brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt was wrongly listed with the same subdirectory brcm, and this resulted in a stale symlink. Fix it. Signed-off-by: Takashi Iwai Signed-off-by: Josh Boyer [Where Problems Could Occur] Firmware is now loaded on Pi 3A+ at boot which didn't happen before so theoretically that could crash the kernel if it's buggy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1918698/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925843] [NEW] Linux 5.8.0-49+ fails to resume from suspend
Public bug reported: Expected Result: System resumes from suspend and displays the log in screen to unlock the computer. Actual Result: System displays a black screen with a flashing cursor in the upper left and cannot be interacted with. Hard reboot is required to get back to a working system. Additional information: When I boot my computer with 5.8.0-48, the system resumes from suspend as expected. Both 5.8.0-49 and 5.8.0-50 fail to resume from suspend. This problem began after I updated from 20.04 to 20.10 using the Software Updater on 4-19-21. I was using the latest kernel available for 20.04 at that time (5.8.0-48, I think) before updating. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-50-generic 5.8.0-50.56 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steven 1268 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 23 12:54:52 2021 InstallationDate: Installed on 2020-09-01 (234 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:58eb Realtek Semiconductor Corp. HP Wide Vision HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP OMEN by HP Laptop 15-ce0xx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=208c1c0d-3e9e-43da-ba24-0d1cd92b5ad0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.release: 15.23 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.23 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 838F dmi.board.vendor: HP dmi.board.version: 40.28 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.28 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.23:bd10/30/2020:br15.23:efr40.28:svnHP:pnOMENbyHPLaptop15-ce0xx:pvr:rvnHP:rn838F:rvr40.28:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 15-ce0xx dmi.product.sku: 1KV78UA#ABA dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925843 Title: Linux 5.8.0-49+ fails to resume from suspend Status in linux package in Ubuntu: New Bug description: Expected Result: System resumes from suspend and displays the log in screen to unlock the computer. Actual Result: System displays a black screen with a flashing cursor in the upper left and cannot be interacted with. Hard reboot is required to get back to a working system. Additional information: When I boot my computer with 5.8.0-48, the system resumes from suspend as expected. Both 5.8.0-49 and 5.8.0-50 fail to resume from suspend. This problem began after I updated from 20.04 to 20.10 using the Software Updater on 4-19-21. I was using the latest kernel available for 20.04 at that time (5.8.0-48, I think) before updating. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-50-generic 5.8.0-50.56 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steven 1268 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 23 12:54:52 2021 InstallationDate: Installed on 2020-09-01 (234 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:58eb Realtek Semiconductor Corp. HP Wide Vision HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP OMEN by HP Laptop 15-ce0xx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine:
[Kernel-packages] [Bug 1922792] Re: Bluez should notify users when they need to reboot to apply changes on Raspberry Pi
> Thanks for the details. You did address the part about upstreaming the change to Debian. How important is that notification in practice? If feels like we should have bluez preinstall on the raspi images if that's not the case, and if it's pre-install is that really worth the packaging overhead to have to carry a delta over Debian? Just to give a bit of context here, the bluetooth situation on the pi is somewhat complicated and there's compromises that we make between the desktop and server images: The bluetooth module on the Pi is controlled via a UART. Two UARTs are available on the Pi (there's more on the Pi 4, but it's the same situation for the bits we're talking about here): * the PL011 which is full featured (buffers, flow-control, etc.), and * the mini-UART which is ... not. Furthermore, the mini-UART's baud rate is tied to the GPU's clock, so if that floats then the mini-UART's baud rate floats too On models of Pi with a bluetooth module (everything except the Pi 2, the CM3/3+ and some models of the CM4), the PL011 is used to talk to the bluetooth module and by default the mini-UART is disabled. This is the configuration we use on the desktop images as we make the assumption a serial console is less important on something which almost certainly has a monitor, and this configuration permits the GPU clock to float (important for something relying upon graphical acceleration). On the server images, we assume that the serial console *is* important, and so this is enabled by default. We don't *disable* the bluetooth module, but we don't pre-install the packages for it either. This means that the PL011 is tied to the bluetooth module by default (but unused), and the mini-UART to the serial console. Because the mini-UART is in use, the GPU's clock is locked to the base speed. This is a compromise because all the alternatives are nastier in some way for some of the typical use cases: * If the server image is used without a graphical environment, and without bluetooth, this is fine (this is the default). The GPU's clock doesn't really matter in this scenario and the serial console will still work reliably. * If the server image is used without a graphical environment, but with bluetooth, all the user needs to do is install pi-bluetooth and reboot (personally I don't think the reboot warning is terribly necessary; like knowing to install pi-bluetooth in the first place, it's fairly widespread knowledge and tends to be part of first-time setup steps anyway). This again leaves the GPU's clock locked (but without a graphical environment that doesn't really matter), the serial console still works, and bluetooth works. * If the server image is used with a graphical environment, without bluetooth, the user needs to either disable the serial console (if they don't want it, this is a one-line change in the boot configuration), or alternatively add the line "dtoverlay=disable-bt" to the boot configuration which disables the bluetooth module entirely, allowing the serial console to use the "full" PL011 UART. Either option unlocks the GPU's clock. * If the server image is used with a graphical environment, with bluetooth, that's effectively the same as the desktop setup and we assume that in this scenario the user would disable the serial console (which means the mini-UART is no longer used and the GPU's clock can float again); again, a one-line change in the boot configuration. So the compromise is to ship an image which, with either zero steps or one step can be moved to one of the scenarios above, with hardware working acceptably for that scenario. We could default to, for example, shipping the server image with both serial console *and* bluetooth enabled, but that complicates moving to a GPU clock unlocked scenario as it involves either disabling the serial console (easy) or removing bluetooth (quite a bit harder, especially if the pi-bluetooth package is now depended on by a meta-package, and also still involves disabling the hardware module with the dtoverlay). Anyway, for the above reasons I don't foresee that we're likely to ship bluetooth enabled server images anytime soon. As to how necessary a reboot warning is -- I'd consider it "nice to have but by no means critical" (it's not hardware enablement after all). If we want to keep the delta minimal, I've no objections. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1922792 Title: Bluez should notify users when they need to reboot to apply changes on Raspberry Pi Status in bluez package in Ubuntu: In Progress Status in bluez package in Debian: New Bug description: In the case of upgrading or installing bluez for the first time on certain raspberry pi devices, a reboot may be required to apply the changes. We should add a check for this scenario in the postinst script. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1925452] Re: [Ubuntu 21.04]: net/mlx5: Fix HW spec violation configuring uplink (mandatory for 20.04)
Hi Frank, I think the patch did not apply cleanly on 5.10 an earlier, so we need the backport here for groovy and 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/1925452 Title: [Ubuntu 21.04]: net/mlx5: Fix HW spec violation configuring uplink (mandatory for 20.04) Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: New Status in linux source package in Groovy: New Status in linux source package in Hirsute: In Progress Bug description: With the 5.4.0-48 update for Ubuntu 20.04, the commit "net/mlx5e: Modify uplink state on interface up/down" was integrated which contains a regression for mlx5 adapters with older adapter firmware. This is the second bugfix to repair the regression, required to operate the adapter in switchdev mode. The first part was integrated via Bug 192185 - LP1921104. This is the upstream fix required to be backported to Ubuntu 20.04: https://github.com/torvalds/linux/commit/1a73704c82ed4ee95532ac04645d02075bd1ce3d ---Additional Hardware Info--- Mellanox ConnectX network adapter ---uname output--- 5.4.0-73-generic ---Steps to Reproduce--- enable switchdev mode try to ping external host Backports need to be provide for 21.04, 20.10 and 20.04 (if not cleanly applyable)! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1925452/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925008] Re: no memory hot-plugging in cloud-images
** Description changed: + SRU Justification + + [Impact] + Memory hot-plugging is not working with public cloud-images. Error with dmesg shows: [ 184.544535] acpi PNP0C80:00: Enumeration failure checking kernel configuration: root@ubuntu:/boot# uname -r 5.4.0-1038-kvm root@ubuntu:/boot# grep CONFIG_ACPI_HOTPLUG_MEMORY config-5.4.0-1038-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set Obviously the necessary kernel configuration for ACPI memory hotplug is missing. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20210415 - --- + --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: - + ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=C.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C.UTF-8 + SHELL=/bin/bash ProcFB: - + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1038-kvm root=PARTUUID=a204284f-e3de-498d-a306-c4e7f6b62831 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 5.4.0-1038.39-kvm 5.4.101 RelatedPackageVersions: - linux-restricted-modules-5.4.0-1038-kvm N/A - linux-backports-modules-5.4.0-1038-kvm N/A - linux-firmware N/A + linux-restricted-modules-5.4.0-1038-kvm N/A + linux-backports-modules-5.4.0-1038-kvm N/A + linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1038-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.7 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.7 dmi.sys.vendor: QEMU + + [Test Plan] + + Boot a kernel with CONFIG_ACPI_HOTPLUG_MEMORY enabled. Check that + requested memory has been added. + + [Where problems could occur] + + Adding memory could fail, or cause other configurations issues. + Regressions seem unlikely since this config option is enabled in all + cloud kernels except linux-azure. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1925008 Title: no memory hot-plugging in cloud-images Status in cloud-images: Invalid Status in linux package in Ubuntu: Fix Released Status in linux-kvm package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in linux-kvm source package in Focal: In Progress Status in linux source package in Groovy: Fix Released Status in linux-kvm source package in Groovy: In Progress Status in linux source package in Hirsute: Fix Released Status in linux-kvm source package in Hirsute: In Progress Bug description: SRU Justification [Impact] Memory hot-plugging is not working with public cloud-images. Error with dmesg shows: [ 184.544535] acpi PNP0C80:00: Enumeration failure checking kernel configuration: root@ubuntu:/boot# uname -r 5.4.0-1038-kvm root@ubuntu:/boot# grep CONFIG_ACPI_HOTPLUG_MEMORY config-5.4.0-1038-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set Obviously the necessary kernel configuration for ACPI memory hotplug is missing. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20210415 --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno
[Kernel-packages] [Bug 1925819] [NEW] No longer able to set Fan speed, Graphics Clock Offset and Memory Transfer Rate Offset
Public bug reported: Hi Gzys, It's not anymore possible to enable/change GPU Fan since the upgrade from 460.56-0 to 460.73.0 # nvidia-settings --verbose=all -a "[gpu:0]/GPUFanControlState=1" -a "[fan:0]/GPUTargetFanSpeed=100" Attribute 'GPUFanControlState' (Jupiter:1[gpu:0]) assigned value 1. Similar issue: https://bbs.archlinux.org/viewtopic.php?id=265445 https://bbs.archlinux.org/viewtopic.php?id=265636 https://forums.developer.nvidia.com/t/465-24-02-no-longer-able-to-set- graphics-clock-offset-and-memory-transfer-rate-offset/175640 ## Nvidia ==NVSMI LOG== Timestamp : Fri Apr 23 16:53:19 2021 Driver Version: 460.73.01 CUDA Version : 11.2 Attached GPUs : 1 GPU :01:00.0 Product Name : GeForce GTX 1050 Ti Product Brand : GeForce Display Mode : Enabled Display Active: Enabled Persistence Mode : Disabled MIG Mode Current : N/A Pending : N/A Accounting Mode : Disabled Accounting Mode Buffer Size : 4000 Driver Model Current : N/A Pending : N/A Serial Number : N/A GPU UUID : GPU-9ebfdd9d-e64b-df93-5b1c-b2134113294d Minor Number : 0 VBIOS Version : 86.07.39.00.54 MultiGPU Board: No Board ID : 0x100 GPU Part Number : N/A Inforom Version Image Version : G001..01.04 OEM Object: 1.1 ECC Object: N/A Power Management Object : N/A GPU Operation Mode Current : N/A Pending : N/A GPU Virtualization Mode Virtualization Mode : None Host VGPU Mode: N/A IBMNPU Relaxed Ordering Mode : N/A PCI Bus : 0x01 Device: 0x00 Domain: 0x Device Id : 0x1C8210DE Bus Id: :01:00.0 Sub System Id : 0x372A1458 GPU Link Info PCIe Generation Max : 3 Current : 3 Link Width Max : 16x Current : 8x Bridge Chip Type : N/A Firmware : N/A Replays Since Reset : 0 Replay Number Rollovers : 0 Tx Throughput : 2000 KB/s Rx Throughput : 1000 KB/s Fan Speed : 0 % Performance State : P0 Clocks Throttle Reasons Idle : Active Applications Clocks Setting : Not Active SW Power Cap : Not Active HW Slowdown : Not Active HW Thermal Slowdown : Not Active HW Power Brake Slowdown : Not Active Sync Boost: Not Active SW Thermal Slowdown : Not Active Display Clock Setting : Not Active FB Memory Usage Total : 4032 MiB Used : 525 MiB Free : 3507 MiB BAR1 Memory Usage Total : 256 MiB Used : 5 MiB Free : 251 MiB Compute Mode : Default Utilization Gpu : 13 % Memory: 10 % Encoder : 0 % Decoder : 0 % Encoder Stats Active Sessions : 0 Average FPS : 0 Average Latency : 0 FBC Stats Active Sessions : 0 Average FPS : 0 Average Latency : 0 Ecc Mode Current : N/A Pending : N/A ECC Errors Volatile Single Bit Device Memory
[Kernel-packages] [Bug 1925685] Re: [SRU] Patch for flicker and glitching on certain hardware, intel framebuffer,
Hi Kai-Heng, We built a combined patch (attached) from that commit and our initial patch and tested, and it seems to work even better. We tested on only one system, but we intend to test on all the glitchy systems to ensure it is stable. That said, the commit you pointed out seems to work well in combination with our initial patch. ** Patch added: "Intel-developed patch to fix framebuffer flicker/glitching combined with presented commit" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925685/+attachment/5491421/+files/drm-intel-both.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925685 Title: [SRU] Patch for flicker and glitching on certain hardware, intel framebuffer, Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Groovy: Confirmed Status in linux source package in Hirsute: Confirmed Bug description: Filing this with my Kubuntu Focus (kfocus.org) OEM hat on: [Impact] We are having screen flickering and glitching issues with some of our hardware upon wake from suspend. We have worked with our ODM to figure out a fix for this. They had reported there were no issues when running Windows on the same hardware. As such, we tested, and found that this issue first began as a regression in kernel 5.0 (did not exist in kernel 4.18 per our tests). We identified a patch via https://gitlab.freedesktop.org/drm/intel/-/issues/272 in which this has been solved. Per our testing by recompiling the kernel, this completely fixes our hardware issue. As of 4-21, this fix has been merged into the Linux kernel per Timo Aaltonen, and will be included in the kernel in the 5.13 release. Our hardware ships with Kubuntu 20.04 LTS, which means the 5.13 kernel will not see these machines, at least in the forseeable future. As such, we request that this patch be added to the kernel. Per our testing, this patch is straightforward to add and works flawlessly. Until this is fixed, we have a whole batch of hardware we cannot sell, so, as an OEM, this is a high priority. [Test Plan] * Install Kubuntu on an affected Kubuntu Focus M2 computer (not in the hands of customers at this time) * Notice screen glitching/flickering after wake-from-suspend. * Install kernel compiled with the attached patch. Boot from patched kernel. * Suspend laptop, resume. No glitches. [Where problems could occur] * Although this solves the problem for us and has been confirmed to work with the Intel developers that developed this patch, it could cause another display type to have problems. This is unlikely as it has been vetted by Intel and by the mainline Linux kernel developers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925008] Re: no memory hot-plugging in cloud-images
We tested the kernel release 5.4.0-1040-kvm and it looks much more better now. Memory gets added automaticly to the system. Also all events are visible now: monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[14203.153504] add /devices/system/memory/memory56 (memory) KERNEL[14203.153549] add /devices/system/memory/memory57 (memory) KERNEL[14203.153557] add /devices/system/memory/memory58 (memory) KERNEL[14203.153564] add /devices/system/memory/memory59 (memory) KERNEL[14203.153571] add /devices/system/memory/memory60 (memory) KERNEL[14203.153578] add /devices/system/memory/memory61 (memory) KERNEL[14203.153585] add /devices/system/memory/memory62 (memory) KERNEL[14203.153592] add /devices/system/memory/memory63 (memory) KERNEL[14203.158264] online /devices/system/memory/memory56 (memory) UDEV [14203.158904] add /devices/system/memory/memory56 (memory) KERNEL[14203.159596] online /devices/system/memory/memory58 (memory) UDEV [14203.159619] add /devices/system/memory/memory58 (memory) UDEV [14203.160208] online /devices/system/memory/memory58 (memory) KERNEL[14203.160232] online /devices/system/memory/memory60 (memory) UDEV [14203.160391] add /devices/system/memory/memory60 (memory) UDEV [14203.160688] online /devices/system/memory/memory56 (memory) UDEV [14203.161505] online /devices/system/memory/memory60 (memory) KERNEL[14203.161745] online /devices/system/memory/memory62 (memory) UDEV [14203.161818] add /devices/system/memory/memory62 (memory) KERNEL[14203.162450] online /devices/system/memory/memory63 (memory) UDEV [14203.162561] add /devices/system/memory/memory63 (memory) UDEV [14203.162769] online /devices/system/memory/memory62 (memory) UDEV [14203.163352] online /devices/system/memory/memory63 (memory) KERNEL[14203.172589] online /devices/system/memory/memory61 (memory) UDEV [14203.172722] add /devices/system/memory/memory61 (memory) UDEV [14203.173936] online /devices/system/memory/memory61 (memory) KERNEL[14203.180667] online /devices/system/memory/memory59 (memory) UDEV [14203.180817] add /devices/system/memory/memory59 (memory) UDEV [14203.182015] online /devices/system/memory/memory59 (memory) KERNEL[14203.188645] online /devices/system/memory/memory57 (memory) UDEV [14203.188715] add /devices/system/memory/memory57 (memory) UDEV [14203.189542] online /devices/system/memory/memory57 (memory) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1925008 Title: no memory hot-plugging in cloud-images Status in cloud-images: Invalid Status in linux package in Ubuntu: Fix Released Status in linux-kvm package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in linux-kvm source package in Focal: In Progress Status in linux source package in Groovy: Fix Released Status in linux-kvm source package in Groovy: In Progress Status in linux source package in Hirsute: Fix Released Status in linux-kvm source package in Hirsute: In Progress Bug description: Memory hot-plugging is not working with public cloud-images. Error with dmesg shows: [ 184.544535] acpi PNP0C80:00: Enumeration failure checking kernel configuration: root@ubuntu:/boot# uname -r 5.4.0-1038-kvm root@ubuntu:/boot# grep CONFIG_ACPI_HOTPLUG_MEMORY config-5.4.0-1038-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set Obviously the necessary kernel configuration for ACPI memory hotplug is missing. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20210415 --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1038-kvm root=PARTUUID=a204284f-e3de-498d-a306-c4e7f6b62831 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 5.4.0-1038.39-kvm 5.4.101
[Kernel-packages] [Bug 1923062] Re: NVIDIA CVE-2021-1076 CVE-2021-1077
This bug was fixed in the package nvidia-graphics-drivers-460-server - 460.73.01-0ubuntu0.20.04.1 --- nvidia-graphics-drivers-460-server (460.73.01-0ubuntu0.20.04.1) focal; urgency=medium * New upstream release (LP: #1923062). * debian/templates/dkms_nvidia.conf.in: - Drop buildfix_kernel_5.11.patch. -- Alberto Milone Fri, 09 Apr 2021 16:09:14 +0200 ** Changed in: nvidia-graphics-drivers-460-server (Ubuntu Focal) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1923062 Title: NVIDIA CVE-2021-1076 CVE-2021-1077 Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Focal: Fix Released Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-390 source package in Groovy: In Progress Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450 source package in Groovy: In Progress Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Released Bug description: Here is the list of the affected drivers: 418-server - CVE-2021-1076 460, 450, 460-server, 450-server - CVE-2021-1076 CVE-2021-1077 390 - CVE-2021-1076 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1923062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877088] Please test proposed package
Hello bugproxy, or anyone else affected, Accepted linux-base into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- base/4.5ubuntu1.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- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf Status in Ubuntu on IBM z Systems: In Progress Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux-base source package in Hirsute: Fix Released Bug description: [Impact] * initrd link is not updated when using installkernel or "make install" from kernel sources. This leads to boot failure after installing a new kernel with mentioned methods because the kernel does not match initrd. * It's a regression because for Focal it was working before. * Issue was reproduced also on Bionic. * The proposed fixed by Stefan Bader adds a hook in /etc/kernel/postinst.d/ so installkernel will relink the initrd. The kernel DEB packages should not be affected. * The solution from Stefan (first patch) was tested by the bug reporter (niklas.schne...@ibm.com). [Test Plan] * Build a kernel * sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot * Check if /boot/initrd or /initrd symlink to the new initrd [Where problems could occur] * Installing kernel via: installkernel or "make install", so mostly kernel developer environments [Other info from developer] When testing development kernels I usually rely on the installkernel script either through the "make install" target of the Kernel source or manually. This used to work great on Ubuntu on Z. On Ubuntu 20.04 (freshly installed up to date) this fails however because /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the wrong kernel/initrd combination rendering the system unbootable. (with the correct modules already copied to /usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/) # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. run-parts: executing /etc/kernel/postinst.d/zz-zipl 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. # ls -l /boot total 178364 -rw--- 1 root root135168 May 6 11:52 bootmap -rw-r--r-- 1 root root 90471 Apr 29 15:34 config-5.4.0-29-generic lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img -> initrd.img-5.4.0-29-generic <== should point to new version -rw-r--r-- 1 root root 19663996 May 6 11:42 initrd.img-5.4.0-29-generic -rw-r--r-- 1 root root 125339494 May 6 11:52 initrd.img-5.7.0-rc4-06500-gb67ea026badd lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img.old -> initrd.img-5.4.0-29-generic -rw--- 1 root root 3087920 Apr 29 15:34 System.map-5.4.0-29-generic -rw-r--r-- 1 root root 4031691
[Kernel-packages] [Bug 1877088] Re: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf
Hello bugproxy, or anyone else affected, Accepted linux-base into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- base/4.5ubuntu3.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-base (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-base (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf Status in Ubuntu on IBM z Systems: In Progress Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux-base source package in Hirsute: Fix Released Bug description: [Impact] * initrd link is not updated when using installkernel or "make install" from kernel sources. This leads to boot failure after installing a new kernel with mentioned methods because the kernel does not match initrd. * It's a regression because for Focal it was working before. * Issue was reproduced also on Bionic. * The proposed fixed by Stefan Bader adds a hook in /etc/kernel/postinst.d/ so installkernel will relink the initrd. The kernel DEB packages should not be affected. * The solution from Stefan (first patch) was tested by the bug reporter (niklas.schne...@ibm.com). [Test Plan] * Build a kernel * sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot * Check if /boot/initrd or /initrd symlink to the new initrd [Where problems could occur] * Installing kernel via: installkernel or "make install", so mostly kernel developer environments [Other info from developer] When testing development kernels I usually rely on the installkernel script either through the "make install" target of the Kernel source or manually. This used to work great on Ubuntu on Z. On Ubuntu 20.04 (freshly installed up to date) this fails however because /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the wrong kernel/initrd combination rendering the system unbootable. (with the correct modules already copied to /usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/) # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. run-parts: executing /etc/kernel/postinst.d/zz-zipl 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. # ls -l /boot total 178364 -rw--- 1 root root135168 May 6 11:52 bootmap -rw-r--r-- 1 root root 90471 Apr 29 15:34 config-5.4.0-29-generic lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img -> initrd.img-5.4.0-29-generic <== should point to new version -rw-r--r-- 1 root root 19663996 May 6 11:42 initrd.img-5.4.0-29-generic -rw-r--r-- 1 root root 125339494 May 6 11:52 initrd.img-5.7.0-rc4-06500-gb67ea026badd lrwxrwxrwx 1 root root27 May 6 11:40
[Kernel-packages] [Bug 1925783] Re: installed linux-firmware package post-installation script subprocess returned error exit status 1
It is odd that you have so many marked manually installed. Unless you actually installed those packages manually, they should be marked as automatically installed. We do keep a few kernels installed, so that it's possible to boot back to a previous kernel if an update causes problems, but it shouldn't be that many, and to my understanding that doesn't involve marking packages as manually installed anyhow. So I'm not sure how that might have happened. It should be safe to mark 5.8.0-50, assuming you have the linux- lowlatency package installed. With it being the current kernel in groovy-updates the linux-lowlatency meta package will depend on it and prevent it from being removed. -- 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/1925783 Title: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in linux-firmware package in Ubuntu: New Bug description: I've got update from KDE Discover and it showed an error "installed linux-firmware package post-installation script subprocess returned error exit status 1". However, i didn't took a detailed look at it. When i tried to apt install a package, this error showed up: Selecting previously unselected package ndisc6. (Reading database ... 409324 files and directories currently installed.) Preparing to unpack .../ndisc6_1.0.4-1ubuntu1_amd64.deb ... Unpacking ndisc6 (1.0.4-1ubuntu1) ... Setting up initramfs-tools (0.136ubuntu6.4) ... update-initramfs: deferring update (trigger activated) Setting up linux-firmware (1.187.11) ... update-initramfs: Generating /boot/initrd.img-5.8.0-50-lowlatency I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgkubuntu-swap_1) I: Set the RESUME variable to override this. Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 update-initramfs: failed for /boot/initrd.img-5.8.0-50-lowlatency with 1. dpkg: error processing package linux-firmware (--configure): installed linux-firmware package post-installation script subprocess returned error exit status 1 Setting up ndisc6 (1.0.4-1ubuntu1) ... update-alternatives: using /usr/bin/rltraceroute6 to provide /usr/bin/traceroute6 (traceroute6) in auto mode Processing triggers for man-db (2.9.1-1) ... Processing triggers for initramfs-tools (0.136ubuntu6.4) ... update-initramfs: Generating /boot/initrd.img-5.8.0-50-lowlatency I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgkubuntu-swap_1) I: Set the RESUME variable to override this. Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 update-initramfs: failed for /boot/initrd.img-5.8.0-50-lowlatency with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: linux-firmware initramfs-tools E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.11 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-lowlatency 5.8.18 Uname: Linux 5.8.0-50-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lyubo 260326 F pulseaudio /dev/snd/pcmC0D0p: lyubo 260326 F...m pulseaudio /dev/snd/timer: lyubo 260326 f pulseaudio CasperMD5CheckResult: skip Date: Fri Apr 23 14:01:02 2021 Dependencies: InstallationDate: Installed on 2020-12-27 (116 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b5f7 Chicony Electronics Co., Ltd HD WebCam Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Bus 001 Device 005: ID 275d:0ba6 USB OPTICAL MOUSE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A515-51G PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-lowlatency root=/dev/mapper/vgkubuntu-root ro quiet splash lockdown=confidentiality vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-50-lowlatency N/A linux-backports-modules-5.8.0-50-lowlatency N/A linux-firmware 1.187.11 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/03/2019 dmi.bios.release: 2.2
[Kernel-packages] [Bug 1925386] Re: Upgrade from 460.32.03-0ubuntu2 to 460.73.01-0ubuntu1 fails
Cool, thank you for reconsidering! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1925386 Title: Upgrade from 460.32.03-0ubuntu2 to 460.73.01-0ubuntu1 fails Status in nvidia-graphics-drivers-460-server package in Ubuntu: Triaged Bug description: ubuntu@dgx-1-exotic-skunk-201710-25896:~$ sudo apt install nvidia-dkms-460-server nvidia-utils-460-server Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: nvidia-kernel-common-460-server Suggested packages: nvidia-driver-460-server The following packages will be upgraded: nvidia-dkms-460-server nvidia-kernel-common-460-server nvidia-utils-460-server 3 upgraded, 0 newly installed, 0 to remove and 37 not upgraded. Need to get 424 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu hirsute-proposed/restricted amd64 nvidia-dkms-460-server amd64 460.73.01-0ubuntu1 [42.8 kB] Get:2 http://archive.ubuntu.com/ubuntu hirsute-proposed/restricted amd64 nvidia-kernel-common-460-server amd64 460.73.01-0ubuntu1 [18.4 kB] Get:3 http://archive.ubuntu.com/ubuntu hirsute-proposed/restricted amd64 nvidia-utils-460-server amd64 460.73.01-0ubuntu1 [363 kB] Fetched 424 kB in 2s (220 kB/s) (Reading database ... 87065 files and directories currently installed.) Preparing to unpack .../nvidia-dkms-460-server_460.73.01-0ubuntu1_amd64.deb ... Removing all DKMS Modules Done. Unpacking nvidia-dkms-460-server (460.73.01-0ubuntu1) over (460.32.03-0ubuntu2) ... Preparing to unpack .../nvidia-kernel-common-460-server_460.73.01-0ubuntu1_amd64 .deb ... Unpacking nvidia-kernel-common-460-server (460.73.01-0ubuntu1) over (460.32.03-0 ubuntu2) ... Preparing to unpack .../nvidia-utils-460-server_460.73.01-0ubuntu1_amd64.deb ... Unpacking nvidia-utils-460-server (460.73.01-0ubuntu1) over (460.32.03-0ubuntu2) ... Setting up nvidia-kernel-common-460-server (460.73.01-0ubuntu1) ... update-initramfs: deferring update (trigger activated) Setting up nvidia-utils-460-server (460.73.01-0ubuntu1) ... Setting up nvidia-dkms-460-server (460.73.01-0ubuntu1) ... update-initramfs: deferring update (trigger activated) Loading new nvidia-srv-460.73.01 DKMS files... Building for 5.11.0-16-generic Building for architecture x86_64 Building initial module for 5.11.0-16-generic Error! Application of patch disable_fstack-clash-protection_fcf-protection.patch failed. Check /var/lib/dkms/nvidia-srv/460.73.01/build/ for more information. dpkg: error processing package nvidia-dkms-460-server (--configure): installed nvidia-dkms-460-server package post-installation script subprocess re turned error exit status 6 Processing triggers for man-db (2.9.4-2) ... Processing triggers for initramfs-tools (0.139ubuntu3) ... update-initramfs: Generating /boot/initrd.img-5.11.0-16-generic W: Possible missing firmware /lib/firmware/ast_dp501_fw.bin for module ast Errors were encountered while processing: nvidia-dkms-460-server needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) ubuntu@dgx-1-exotic-skunk-201710-25896:~$ ls /var/lib/dkms/nvidia-srv/460.73.01/build/ dkms.conf patches ubuntu@dgx-1-exotic-skunk-201710-25896:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460-server/+bug/1925386/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919177] Re: Azure: issues with accelerated networking on Hirsute
** Changed in: cloud-init (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1919177
Title:
Azure: issues with accelerated networking on Hirsute
Status in cloud-init:
Incomplete
Status in cloud-init package in Ubuntu:
Incomplete
Status in linux-azure package in Ubuntu:
New
Status in systemd package in Ubuntu:
New
Bug description:
[General]
On Azure, when provisioning a Hirsute VM with Accelerated Networking
enabled, sometimes part of the cloud-init configuration is not
applied.
Especially, in those cases, the public SSH key is not setup properly.
[how to reproduce]
Start a VM with AN enabled:
```
az vm create --name "$VM_NAME --resource-group "$GROUP" --location "UK South"
--image
'Canonical:0001-com-ubuntu-server-hirsute-daily:21_04-daily-gen2:latest' --size
Standard_F8s_v2 --admin-username ubuntu --ssh-key-value "$SSH_KEY"
--accelerated-networking
```
After a moment, try to SSH: if you succeed, delete and recreate a new
VM.
[troubleshooting]
To be able to connect into the VM, run:
az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
```
In "/run/cloud-init/instance-data.json", I can see:
```
"publicKeys": [
{
"keyData": "",
"path": "/home/ubuntu/.ssh/authorized_keys"
}
],
```
as expected.
[workaround]
As mentioned, Azure allows the user to run command into the VM without
SSH connection. To do so, one can use the Azure CLI:
az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
This example uses "ssh-import-id" but it's also possible to just echo
a given public key into /home/ubuntu/.ssh/authorized_keys
NOTE: this will only solves the SSH issue, I do not know if this bug
affects other things. If so the user would have to apply those things
manually.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1919177/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921452] Please test proposed package
Hello Shengyao, or anyone else affected, Accepted alsa-lib into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa- lib/1.2.2-2.1ubuntu2.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1921452 Title: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB- Audio.pcm.iec958_device Status in OEM Priority Project: In Progress Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Committed Status in alsa-lib source package in Groovy: Fix Committed Status in alsa-lib source package in Hirsute: Fix Released Bug description: [Impact] On Cmedia Audio, unusable SPDIF can be selected as output from PulseAudio. [Fix] Disable IEC958 (SPDIF) through ALSA UCM. [Test] With the UCM applied, `pactl` and audio panel in gnome-control-center no longer have SPDIF option. [Where problems will occur] "Cmedia Audio" is the sound card name of this usb audio dongle, and this string is got from usb string descriptor, that is to say the "Cmedia Audio" is hard-coded in the firmware of that usb dongle. Not all Cmedia usb audio dongle use "Cmedia Audio", most of the dongles don't set string descriptor, then the audio driver sets a generic name "USB Audio Device" for them, if a dongle has string descriptor, it may have different string like "C-Media USB Headphone Set", and all dongles I met before don't have SPDIF interface. So If this SRU could introduce regression, it will happen on a Cmedia usb audio dongle which also hard-codes the "Cmedia Audio" in the string descriptor and it has SPDIF interface on it, after this SRU, users couldn't find the SPDIF playback device from the gnome-sound-setting. But this regression chance is very low since it is very rare a cmedia usb audio dongle uses "Cmedia Audio" in the string descriptor and it is very rare a usb audio dongle has SPDIF interface. So far we haven't met such a cmedia usb audio dongle. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1921452/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921452] Re: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB-Audio.pcm.iec958_device
Hello Shengyao, or anyone else affected, Accepted alsa-lib into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa- lib/1.2.3.2-1ubuntu3.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. 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: alsa-lib (Ubuntu Groovy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-groovy ** Changed in: alsa-lib (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1921452 Title: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB- Audio.pcm.iec958_device Status in OEM Priority Project: In Progress Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Committed Status in alsa-lib source package in Groovy: Fix Committed Status in alsa-lib source package in Hirsute: Fix Released Bug description: [Impact] On Cmedia Audio, unusable SPDIF can be selected as output from PulseAudio. [Fix] Disable IEC958 (SPDIF) through ALSA UCM. [Test] With the UCM applied, `pactl` and audio panel in gnome-control-center no longer have SPDIF option. [Where problems will occur] "Cmedia Audio" is the sound card name of this usb audio dongle, and this string is got from usb string descriptor, that is to say the "Cmedia Audio" is hard-coded in the firmware of that usb dongle. Not all Cmedia usb audio dongle use "Cmedia Audio", most of the dongles don't set string descriptor, then the audio driver sets a generic name "USB Audio Device" for them, if a dongle has string descriptor, it may have different string like "C-Media USB Headphone Set", and all dongles I met before don't have SPDIF interface. So If this SRU could introduce regression, it will happen on a Cmedia usb audio dongle which also hard-codes the "Cmedia Audio" in the string descriptor and it has SPDIF interface on it, after this SRU, users couldn't find the SPDIF playback device from the gnome-sound-setting. But this regression chance is very low since it is very rare a cmedia usb audio dongle uses "Cmedia Audio" in the string descriptor and it is very rare a usb audio dongle has SPDIF interface. So far we haven't met such a cmedia usb audio dongle. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1921452/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922599] Re: fails to create a new context
Simon, Gary, can you confirm if the issue goes away with
460.73.01-0ubuntu0.20.04.1 (now in focal-updates)?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1922599
Title:
fails to create a new context
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
Confirmed
Bug description:
With the 460 driver on a 5.11 kernel, I'm unable to initialize a new
context.
ubuntu@blanka:~$ cat foo.c
#include
#include
#include
int main(){
int ret;
assert (cuInit(0) == 0);
CUcontext ctx;
CUdevice device;
assert(cuDeviceGet(,0) == 0 );
ret = cuCtxCreate(, 0, device);
printf("cuCtxCreate returned %d\n", ret);
return 0;
}
$ sudo ./foo
cuCtxCreate returned 1
This works fine with the 450 driver.
$ cat /proc/version
Linux version 5.11.0-13-generic (buildd@lgw01-amd64-035) (gcc (Ubuntu
10.2.1-23ubuntu1) 10.2.1 20210312, GNU ld (GNU Binutils for Ubuntu) 2.36.1)
#14-Ubuntu SMP Fri Mar 19 16:55:27 UTC 2021
$ dpkg -l | grep nvidia-cuda-dev
ii nvidia-cuda-dev:amd64 11.2.1-2
amd64NVIDIA CUDA
development files
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460-server/+bug/1922599/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] Re: touchpad not detected
solved thanks to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893663 Touchpad works fine after applying the change explained there: this work https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893663/comments/12 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925386] Re: Upgrade from 460.32.03-0ubuntu2 to 460.73.01-0ubuntu1 fails
We have that kind of versioned dependency on the nvidia-kernel-common package. I suppose I could do the same for the nvidia-kernel-source package. ** Changed in: nvidia-graphics-drivers-460-server (Ubuntu) Status: Invalid => Triaged ** Changed in: nvidia-graphics-drivers-460-server (Ubuntu) Importance: Undecided => Low ** Changed in: nvidia-graphics-drivers-460-server (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1925386 Title: Upgrade from 460.32.03-0ubuntu2 to 460.73.01-0ubuntu1 fails Status in nvidia-graphics-drivers-460-server package in Ubuntu: Triaged Bug description: ubuntu@dgx-1-exotic-skunk-201710-25896:~$ sudo apt install nvidia-dkms-460-server nvidia-utils-460-server Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: nvidia-kernel-common-460-server Suggested packages: nvidia-driver-460-server The following packages will be upgraded: nvidia-dkms-460-server nvidia-kernel-common-460-server nvidia-utils-460-server 3 upgraded, 0 newly installed, 0 to remove and 37 not upgraded. Need to get 424 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu hirsute-proposed/restricted amd64 nvidia-dkms-460-server amd64 460.73.01-0ubuntu1 [42.8 kB] Get:2 http://archive.ubuntu.com/ubuntu hirsute-proposed/restricted amd64 nvidia-kernel-common-460-server amd64 460.73.01-0ubuntu1 [18.4 kB] Get:3 http://archive.ubuntu.com/ubuntu hirsute-proposed/restricted amd64 nvidia-utils-460-server amd64 460.73.01-0ubuntu1 [363 kB] Fetched 424 kB in 2s (220 kB/s) (Reading database ... 87065 files and directories currently installed.) Preparing to unpack .../nvidia-dkms-460-server_460.73.01-0ubuntu1_amd64.deb ... Removing all DKMS Modules Done. Unpacking nvidia-dkms-460-server (460.73.01-0ubuntu1) over (460.32.03-0ubuntu2) ... Preparing to unpack .../nvidia-kernel-common-460-server_460.73.01-0ubuntu1_amd64 .deb ... Unpacking nvidia-kernel-common-460-server (460.73.01-0ubuntu1) over (460.32.03-0 ubuntu2) ... Preparing to unpack .../nvidia-utils-460-server_460.73.01-0ubuntu1_amd64.deb ... Unpacking nvidia-utils-460-server (460.73.01-0ubuntu1) over (460.32.03-0ubuntu2) ... Setting up nvidia-kernel-common-460-server (460.73.01-0ubuntu1) ... update-initramfs: deferring update (trigger activated) Setting up nvidia-utils-460-server (460.73.01-0ubuntu1) ... Setting up nvidia-dkms-460-server (460.73.01-0ubuntu1) ... update-initramfs: deferring update (trigger activated) Loading new nvidia-srv-460.73.01 DKMS files... Building for 5.11.0-16-generic Building for architecture x86_64 Building initial module for 5.11.0-16-generic Error! Application of patch disable_fstack-clash-protection_fcf-protection.patch failed. Check /var/lib/dkms/nvidia-srv/460.73.01/build/ for more information. dpkg: error processing package nvidia-dkms-460-server (--configure): installed nvidia-dkms-460-server package post-installation script subprocess re turned error exit status 6 Processing triggers for man-db (2.9.4-2) ... Processing triggers for initramfs-tools (0.139ubuntu3) ... update-initramfs: Generating /boot/initrd.img-5.11.0-16-generic W: Possible missing firmware /lib/firmware/ast_dp501_fw.bin for module ast Errors were encountered while processing: nvidia-dkms-460-server needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) ubuntu@dgx-1-exotic-skunk-201710-25896:~$ ls /var/lib/dkms/nvidia-srv/460.73.01/build/ dkms.conf patches ubuntu@dgx-1-exotic-skunk-201710-25896:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460-server/+bug/1925386/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1925799/+attachment/5491383/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1925799/+attachment/5491382/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1925799/+attachment/5491380/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1925799/+attachment/5491381/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1925799/+attachment/5491379/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1925799/+attachment/5491378/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1925799/+attachment/5491376/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1925799/+attachment/5491377/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1925799/+attachment/5491375/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1925799/+attachment/5491374/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1925799/+attachment/5491373/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1925799/+attachment/5491372/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1925799/+attachment/5491371/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1925799/+attachment/5491370/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1925799/+attachment/5491369/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1925799/+attachment/5491367/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1925799/+attachment/5491368/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1925799/+attachment/5491366/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1925799/+attachment/5491365/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1925799/+attachment/5491364/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] [NEW] touchpad not detected
Public bug reported: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-collected focal fujitsu groovy i2c-hid touchpad ** Tags added: apport-collected groovy ** Description changed: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu50.5 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: fred 1391 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.10 + InstallationDate: Installed on 2021-04-21 (1 days ago) + InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) + MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 + RelatedPackageVersions: + linux-restricted-modules-5.8.0-50-generic N/A + linux-backports-modules-5.8.0-50-generic N/A + linux-firmware1.190.3 + 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: 06/19/2020 + dmi.bios.release: 2.12 + dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED + dmi.bios.version: Version 2.12 + dmi.board.name: FJNB2DA + dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED + dmi.board.version: A2 + dmi.chassis.type: 31 + dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED + dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: + dmi.product.family: LIFEBOOK-JR + dmi.product.name: FMVWE2U38T + dmi.product.sku: SK00 + dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T
[Kernel-packages] [Bug 1925783] Re: installed linux-firmware package post-installation script subprocess returned error exit status 1
Thanks Mr. Forshee, that was the problem. Before you close this bug, could i ask a clarification question. I followed the steps here: https://help.ubuntu.com/community/RemoveOldKernels apt-mark showauto 'linux-image-.*' showed: linux-image-lowlatency-hwe-20.04 And apt-mark showmanual 'linux-image-.*' showed: linux-image-5.8.0-43-lowlatency linux-image-5.8.0-45-lowlatency linux-image-5.8.0-48-lowlatency linux-image-5.8.0-49-lowlatency linux-image-5.8.0-50-lowlatency What i did was i marked all but linux-image-5.8.0-50-lowlatency as autoinstalled and then sudo apt autoremove --purge. My questions are: 1. Should i also mark linux-image-5.8.0-50-lowlatency as autoinstalled; 2. Do you think it is normal/correct to have so many linux-image-* packages marked as manually installed? I don't remember setting all of these/installing them manually. I believe in the past i have purged old linux-image-* packages which were some 5.4-lowlatency and then installed linux-image-lowlatency-hwe-20.04, but IMO all these linux-image-* packages should've been automatically removed as part of the numerous previous kernel updates i received. -- 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/1925783 Title: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in linux-firmware package in Ubuntu: New Bug description: I've got update from KDE Discover and it showed an error "installed linux-firmware package post-installation script subprocess returned error exit status 1". However, i didn't took a detailed look at it. When i tried to apt install a package, this error showed up: Selecting previously unselected package ndisc6. (Reading database ... 409324 files and directories currently installed.) Preparing to unpack .../ndisc6_1.0.4-1ubuntu1_amd64.deb ... Unpacking ndisc6 (1.0.4-1ubuntu1) ... Setting up initramfs-tools (0.136ubuntu6.4) ... update-initramfs: deferring update (trigger activated) Setting up linux-firmware (1.187.11) ... update-initramfs: Generating /boot/initrd.img-5.8.0-50-lowlatency I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgkubuntu-swap_1) I: Set the RESUME variable to override this. Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 update-initramfs: failed for /boot/initrd.img-5.8.0-50-lowlatency with 1. dpkg: error processing package linux-firmware (--configure): installed linux-firmware package post-installation script subprocess returned error exit status 1 Setting up ndisc6 (1.0.4-1ubuntu1) ... update-alternatives: using /usr/bin/rltraceroute6 to provide /usr/bin/traceroute6 (traceroute6) in auto mode Processing triggers for man-db (2.9.1-1) ... Processing triggers for initramfs-tools (0.136ubuntu6.4) ... update-initramfs: Generating /boot/initrd.img-5.8.0-50-lowlatency I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgkubuntu-swap_1) I: Set the RESUME variable to override this. Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 update-initramfs: failed for /boot/initrd.img-5.8.0-50-lowlatency with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: linux-firmware initramfs-tools E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.11 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-lowlatency 5.8.18 Uname: Linux 5.8.0-50-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lyubo 260326 F pulseaudio /dev/snd/pcmC0D0p: lyubo 260326 F...m pulseaudio /dev/snd/timer: lyubo 260326 f pulseaudio CasperMD5CheckResult: skip Date: Fri Apr 23 14:01:02 2021 Dependencies: InstallationDate: Installed on 2020-12-27 (116 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b5f7 Chicony Electronics Co., Ltd HD WebCam Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Bus 001 Device 005: ID 275d:0ba6 USB OPTICAL MOUSE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A515-51G PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-lowlatency root=/dev/mapper/vgkubuntu-root ro quiet splash lockdown=confidentiality vt.handoff=7 PulseList: Error: command
[Kernel-packages] [Bug 1922599] Re: fails to create a new context
I hit the same issue as morphis has encountered with the exact same
version nvidia drivers package on 5.4 kernel as well.
```
$ apt -qq list | grep "nvidia-.*-460-server"
libnvidia-cfg1-460-server/focal-updates,focal-security,now
460.32.03-0ubuntu0.20.04.2 amd64 [installed,automatic]
libnvidia-common-460-server/focal-updates,focal-updates,focal-security,focal-security,now
460.32.03-0ubuntu0.20.04.2 all [installed,automatic]
libnvidia-compute-460-server/focal-updates,focal-security,now
460.32.03-0ubuntu0.20.04.2 amd64 [installed,automatic]
libnvidia-compute-460-server/focal-updates 460.32.03-0ubuntu0.20.04.2 i386
libnvidia-decode-460-server/focal-updates,focal-security,now
460.32.03-0ubuntu0.20.04.2 amd64 [installed,automatic]
libnvidia-decode-460-server/focal-updates 460.32.03-0ubuntu0.20.04.2 i386
libnvidia-encode-460-server/focal-updates,focal-security,now
460.32.03-0ubuntu0.20.04.2 amd64 [installed,automatic]
libnvidia-encode-460-server/focal-updates 460.32.03-0ubuntu0.20.04.2 i386
libnvidia-extra-460-server/focal-updates,focal-security,now
460.32.03-0ubuntu0.20.04.2 amd64 [installed,automatic]
libnvidia-extra-460-server/focal-updates 460.32.03-0ubuntu0.20.04.2 i386
libnvidia-fbc1-460-server/focal-updates,focal-security,now
460.32.03-0ubuntu0.20.04.2 amd64 [installed,automatic]
libnvidia-fbc1-460-server/focal-updates 460.32.03-0ubuntu0.20.04.2 i386
libnvidia-gl-460-server/focal-updates,focal-security,now
460.32.03-0ubuntu0.20.04.2 amd64 [installed,automatic]
libnvidia-gl-460-server/focal-updates 460.32.03-0ubuntu0.20.04.2 i386
libnvidia-ifr1-460-server/focal-updates,focal-security,now
460.32.03-0ubuntu0.20.04.2 amd64 [installed,automatic]
libnvidia-ifr1-460-server/focal-updates 460.32.03-0ubuntu0.20.04.2 i386
nvidia-compute-utils-460-server/focal-updates,focal-security,now
460.32.03-0ubuntu0.20.04.2 amd64 [installed,automatic]
nvidia-dkms-460-server/focal-updates,focal-security,now
460.32.03-0ubuntu0.20.04.2 amd64 [installed,automatic]
nvidia-driver-460-server/focal-updates,focal-security,now
460.32.03-0ubuntu0.20.04.2 amd64 [installed]
nvidia-headless-460-server/focal-updates,focal-security
460.32.03-0ubuntu0.20.04.2 amd64
nvidia-headless-no-dkms-460-server/focal-updates,focal-security
460.32.03-0ubuntu0.20.04.2 amd64
nvidia-kernel-common-460-server/focal-updates,focal-security,now
460.32.03-0ubuntu0.20.04.2 amd64 [installed,automatic]
nvidia-kernel-source-460-server/focal-updates,focal-security,now
460.32.03-0ubuntu0.20.04.2 amd64 [installed,automatic]
nvidia-utils-460-server/focal-updates,focal-security,now
460.32.03-0ubuntu0.20.04.2 amd64 [installed,automatic]
$ uname -r
5.4.0-72-generic
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.2 LTS
Release:20.04
Codename: focal
```
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1922599
Title:
fails to create a new context
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
Confirmed
Bug description:
With the 460 driver on a 5.11 kernel, I'm unable to initialize a new
context.
ubuntu@blanka:~$ cat foo.c
#include
#include
#include
int main(){
int ret;
assert (cuInit(0) == 0);
CUcontext ctx;
CUdevice device;
assert(cuDeviceGet(,0) == 0 );
ret = cuCtxCreate(, 0, device);
printf("cuCtxCreate returned %d\n", ret);
return 0;
}
$ sudo ./foo
cuCtxCreate returned 1
This works fine with the 450 driver.
$ cat /proc/version
Linux version 5.11.0-13-generic (buildd@lgw01-amd64-035) (gcc (Ubuntu
10.2.1-23ubuntu1) 10.2.1 20210312, GNU ld (GNU Binutils for Ubuntu) 2.36.1)
#14-Ubuntu SMP Fri Mar 19 16:55:27 UTC 2021
$ dpkg -l | grep nvidia-cuda-dev
ii nvidia-cuda-dev:amd64 11.2.1-2
amd64NVIDIA CUDA
development files
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460-server/+bug/1922599/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922599] Re: fails to create a new context
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-460-server (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1922599
Title:
fails to create a new context
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
Confirmed
Bug description:
With the 460 driver on a 5.11 kernel, I'm unable to initialize a new
context.
ubuntu@blanka:~$ cat foo.c
#include
#include
#include
int main(){
int ret;
assert (cuInit(0) == 0);
CUcontext ctx;
CUdevice device;
assert(cuDeviceGet(,0) == 0 );
ret = cuCtxCreate(, 0, device);
printf("cuCtxCreate returned %d\n", ret);
return 0;
}
$ sudo ./foo
cuCtxCreate returned 1
This works fine with the 450 driver.
$ cat /proc/version
Linux version 5.11.0-13-generic (buildd@lgw01-amd64-035) (gcc (Ubuntu
10.2.1-23ubuntu1) 10.2.1 20210312, GNU ld (GNU Binutils for Ubuntu) 2.36.1)
#14-Ubuntu SMP Fri Mar 19 16:55:27 UTC 2021
$ dpkg -l | grep nvidia-cuda-dev
ii nvidia-cuda-dev:amd64 11.2.1-2
amd64NVIDIA CUDA
development files
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460-server/+bug/1922599/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922599] Re: fails to create a new context
Executing a cudaDeviceSynchronize() instead of using cuCtxCreate gives
"all CUDA-capable devices are busy or unavailable" which seems to hint
to something incorrectly setup in the system.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1922599
Title:
fails to create a new context
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
Confirmed
Bug description:
With the 460 driver on a 5.11 kernel, I'm unable to initialize a new
context.
ubuntu@blanka:~$ cat foo.c
#include
#include
#include
int main(){
int ret;
assert (cuInit(0) == 0);
CUcontext ctx;
CUdevice device;
assert(cuDeviceGet(,0) == 0 );
ret = cuCtxCreate(, 0, device);
printf("cuCtxCreate returned %d\n", ret);
return 0;
}
$ sudo ./foo
cuCtxCreate returned 1
This works fine with the 450 driver.
$ cat /proc/version
Linux version 5.11.0-13-generic (buildd@lgw01-amd64-035) (gcc (Ubuntu
10.2.1-23ubuntu1) 10.2.1 20210312, GNU ld (GNU Binutils for Ubuntu) 2.36.1)
#14-Ubuntu SMP Fri Mar 19 16:55:27 UTC 2021
$ dpkg -l | grep nvidia-cuda-dev
ii nvidia-cuda-dev:amd64 11.2.1-2
amd64NVIDIA CUDA
development files
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460-server/+bug/1922599/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922599] Re: fails to create a new context
I can reproduce this here on the focal 5.4 kernel (5.4.0-72-generic)
with 460.32.03 (deb 460.32.03-0ubuntu0.20.04.2) too.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1922599
Title:
fails to create a new context
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
Confirmed
Bug description:
With the 460 driver on a 5.11 kernel, I'm unable to initialize a new
context.
ubuntu@blanka:~$ cat foo.c
#include
#include
#include
int main(){
int ret;
assert (cuInit(0) == 0);
CUcontext ctx;
CUdevice device;
assert(cuDeviceGet(,0) == 0 );
ret = cuCtxCreate(, 0, device);
printf("cuCtxCreate returned %d\n", ret);
return 0;
}
$ sudo ./foo
cuCtxCreate returned 1
This works fine with the 450 driver.
$ cat /proc/version
Linux version 5.11.0-13-generic (buildd@lgw01-amd64-035) (gcc (Ubuntu
10.2.1-23ubuntu1) 10.2.1 20210312, GNU ld (GNU Binutils for Ubuntu) 2.36.1)
#14-Ubuntu SMP Fri Mar 19 16:55:27 UTC 2021
$ dpkg -l | grep nvidia-cuda-dev
ii nvidia-cuda-dev:amd64 11.2.1-2
amd64NVIDIA CUDA
development files
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460-server/+bug/1922599/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925783] Re: installed linux-firmware package post-installation script subprocess returned error exit status 1
Do you have a separate /boot partition? If so, check whether or not it's full. You may need to remove some old kernel packages you are no longer using. -- 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/1925783 Title: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in linux-firmware package in Ubuntu: New Bug description: I've got update from KDE Discover and it showed an error "installed linux-firmware package post-installation script subprocess returned error exit status 1". However, i didn't took a detailed look at it. When i tried to apt install a package, this error showed up: Selecting previously unselected package ndisc6. (Reading database ... 409324 files and directories currently installed.) Preparing to unpack .../ndisc6_1.0.4-1ubuntu1_amd64.deb ... Unpacking ndisc6 (1.0.4-1ubuntu1) ... Setting up initramfs-tools (0.136ubuntu6.4) ... update-initramfs: deferring update (trigger activated) Setting up linux-firmware (1.187.11) ... update-initramfs: Generating /boot/initrd.img-5.8.0-50-lowlatency I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgkubuntu-swap_1) I: Set the RESUME variable to override this. Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 update-initramfs: failed for /boot/initrd.img-5.8.0-50-lowlatency with 1. dpkg: error processing package linux-firmware (--configure): installed linux-firmware package post-installation script subprocess returned error exit status 1 Setting up ndisc6 (1.0.4-1ubuntu1) ... update-alternatives: using /usr/bin/rltraceroute6 to provide /usr/bin/traceroute6 (traceroute6) in auto mode Processing triggers for man-db (2.9.1-1) ... Processing triggers for initramfs-tools (0.136ubuntu6.4) ... update-initramfs: Generating /boot/initrd.img-5.8.0-50-lowlatency I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgkubuntu-swap_1) I: Set the RESUME variable to override this. Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 update-initramfs: failed for /boot/initrd.img-5.8.0-50-lowlatency with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: linux-firmware initramfs-tools E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.11 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-lowlatency 5.8.18 Uname: Linux 5.8.0-50-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lyubo 260326 F pulseaudio /dev/snd/pcmC0D0p: lyubo 260326 F...m pulseaudio /dev/snd/timer: lyubo 260326 f pulseaudio CasperMD5CheckResult: skip Date: Fri Apr 23 14:01:02 2021 Dependencies: InstallationDate: Installed on 2020-12-27 (116 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b5f7 Chicony Electronics Co., Ltd HD WebCam Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Bus 001 Device 005: ID 275d:0ba6 USB OPTICAL MOUSE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A515-51G PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-lowlatency root=/dev/mapper/vgkubuntu-root ro quiet splash lockdown=confidentiality vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-50-lowlatency N/A linux-backports-modules-5.8.0-50-lowlatency N/A linux-firmware 1.187.11 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/03/2019 dmi.bios.release: 2.2 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.02 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Charmander_KL dmi.board.vendor: KBL dmi.board.version: V2.02 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.02 dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:br2.2:efr1.17:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-51G
