[Kernel-packages] [Bug 1857764] Re: [nvidia] Brightness control is not working since last update
installed in Vaio vpceh25en having Nvidia Geforce 410M and brightness controller not working neither from slider nor from the keyboard. Also, the display looks dull and pixelated. -- 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/1857764 Title: [nvidia] Brightness control is not working since last update Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: The brightness control is not working since last update ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Dec 28 10:14:13 2019 DistUpgraded: 2019-10-22 22:53:56,942 DEBUG inhibit gnome-session idle DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 390.129, 5.0.0-32-generic, x86_64: installed nvidia, 390.129, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:1bc0] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:1bc0] InstallationDate: Installed on 2019-01-28 (334 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: ASUSTeK COMPUTER INC. GL703VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=eba46c54-e23c-4792-ac66-515a492a45d9 ro quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2019-10-23 (66 days ago) dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL703VD.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL703VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL703VD.307:bd03/14/2018:svnASUSTeKCOMPUTERINC.:pnGL703VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL703VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL703VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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/1857764/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1857764] Re: [nvidia] Brightness control is not working since last update
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Confirmed -- 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/1857764 Title: [nvidia] Brightness control is not working since last update Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: The brightness control is not working since last update ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Dec 28 10:14:13 2019 DistUpgraded: 2019-10-22 22:53:56,942 DEBUG inhibit gnome-session idle DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 390.129, 5.0.0-32-generic, x86_64: installed nvidia, 390.129, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:1bc0] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:1bc0] InstallationDate: Installed on 2019-01-28 (334 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: ASUSTeK COMPUTER INC. GL703VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=eba46c54-e23c-4792-ac66-515a492a45d9 ro quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2019-10-23 (66 days ago) dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL703VD.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL703VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL703VD.307:bd03/14/2018:svnASUSTeKCOMPUTERINC.:pnGL703VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL703VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL703VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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/1857764/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880101] 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 1880101 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 ** Changed in: linux (Ubuntu Trusty) 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/1880101 Title: tsc test in monotonic_time failed on Trusty Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Trusty: Incomplete Bug description: Issue found on Trusty 3.13.0-170-generic and 3.13.0-177.228 with amd64 node "gonzo" As this can be reproduced in the kernel from -updates, this is not a regression Test failed with: TestFail: FAIL: tsc_lfence-worst-warp=-7848 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1880101/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880101] [NEW] tsc test in monotonic_time failed on Trusty
Public bug reported: Issue found on Trusty 3.13.0-170-generic and 3.13.0-177.228 with amd64 node "gonzo" As this can be reproduced in the kernel from -updates, this is not a regression Test failed with: TestFail: FAIL: tsc_lfence-worst-warp=-7848 ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Trusty) Importance: Undecided Status: Incomplete ** Tags: 3.13 amd64 monotonic-time sru-20200518 trusty ** Tags added: 3.13 amd64 monotonic-time sru-20200518 trusty ** Description changed: - Issue found on Trusty 3.13.0-170-generic and 3.13.0-177.228 with node - "gonzo" + Issue found on Trusty 3.13.0-170-generic and 3.13.0-177.228 with amd64 + node "gonzo" As this can be reproduced in the kernel from -updates, this is not a regression Test failed with: - TestFail: FAIL: tsc_lfence-worst-warp=-7848 + TestFail: FAIL: tsc_lfence-worst-warp=-7848 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1880101 Title: tsc test in monotonic_time failed on Trusty Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Trusty: Incomplete Bug description: Issue found on Trusty 3.13.0-170-generic and 3.13.0-177.228 with amd64 node "gonzo" As this can be reproduced in the kernel from -updates, this is not a regression Test failed with: TestFail: FAIL: tsc_lfence-worst-warp=-7848 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1880101/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880005] Re: Shutdown/Poweroff Failed with Kernel 5.0.3-53
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 ** This bug has been marked a duplicate of bug 1879997 HP-255-G7-Notebook-PC 5.3.0-51-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1880005 Title: Shutdown/Poweroff Failed with Kernel 5.0.3-53 Status in linux package in Ubuntu: Incomplete Bug description: I have installed Linux Mint Mate 19.3 (Tricia, 64-bits). When I upgraded the Kernel to version 5.3.0-53, the on / off function failed, the screen is off but the laptop is still working, the light of manual shutdown button is still lit. There is no problem with the previous version of the kernel: 5.3.0-51. My laptop is Lenovo YOGA 530-14ARR with precessor AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx × 8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879997] Re: HP-255-G7-Notebook-PC 5.3.0-51-generic
Ubuntu-5.3.0-54.48 will fix it:
commit adfa5c21954fc496c64b5c492bd95d9e18c0d33f
Author: Prike Liang
Date: Mon Apr 13 21:41:14 2020 +0800
drm/amdgpu: fix the hw hang during perform system reboot and reset
BugLink: https://bugs.launchpad.net/bugs/1876321
commit b2a7e9735ab2864330be9d00d7f38c961c28de5d upstream.
The system reboot failed as some IP blocks enter power gate before perform
hw resource destory. Meanwhile use unify interface to set device CGPG to
ungate
state can simplify the amdgpu poweroff or reset ungate guard.
Fixes: 487eca11a321ef ("drm/amdgpu: fix gfx hang during suspend with video
playback (v2)")
Signed-off-by: Prike Liang
Tested-by: Mengbing Wang
Tested-by: Paul Menzel
Acked-by: Alex Deucher
Signed-off-by: Alex Deucher
Cc: sta...@vger.kernel.org
Signed-off-by: Greg Kroah-Hartman
Signed-off-by: Kamal Mostafa
Signed-off-by: Kleber Sacilotto de Souza
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1879997
Title:
HP-255-G7-Notebook-PC 5.3.0-51-generic
Status in linux package in Ubuntu:
Incomplete
Bug description:
HP-255-G7-Notebook-PC System wont reboot or shutdown after kernel
5.3.0-53 update
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879997/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880103] [NEW] Awaking problem after suspend mode still happens
Public bug reported: 101 kernel seems to be better than 99, when the problem happened almost every time. Nevertheless, it happened again with 2+days uptime and suspending over night. Maybe it depends on my wireless keyboard? I tried Alt+SysRq reisub twice, but it didn't work. Mint Cinnamon 19.1, desktop. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "log messages_" https://bugs.launchpad.net/bugs/1880103/+attachment/5375514/+files/log%20messages_ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1880103 Title: Awaking problem after suspend mode still happens Status in linux package in Ubuntu: New Bug description: 101 kernel seems to be better than 99, when the problem happened almost every time. Nevertheless, it happened again with 2+days uptime and suspending over night. Maybe it depends on my wireless keyboard? I tried Alt+SysRq reisub twice, but it didn't work. Mint Cinnamon 19.1, desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880103/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877088] Re: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf
** Changed in: ubuntu-z-systems Status: Triaged => Incomplete -- 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: Incomplete Status in linux-base package in Ubuntu: New Bug description: When testing development kernels I usually rely on the installkernel script either through the "make install" target of the Kernel source or manually. This used to work great on Ubuntu on Z. On Ubuntu 20.04 (freshly installed up to date) this fails however because /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the wrong kernel/initrd combination rendering the system unbootable. (with the correct modules already copied to /usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/) # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. run-parts: executing /etc/kernel/postinst.d/zz-zipl 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. # ls -l /boot total 178364 -rw--- 1 root root135168 May 6 11:52 bootmap -rw-r--r-- 1 root root 90471 Apr 29 15:34 config-5.4.0-29-generic lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img -> initrd.img-5.4.0-29-generic <== should point to new version -rw-r--r-- 1 root root 19663996 May 6 11:42 initrd.img-5.4.0-29-generic -rw-r--r-- 1 root root 125339494 May 6 11:52 initrd.img-5.7.0-rc4-06500-gb67ea026badd lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img.old -> initrd.img-5.4.0-29-generic -rw--- 1 root root 3087920 Apr 29 15:34 System.map-5.4.0-29-generic -rw-r--r-- 1 root root 4031691 May 6 11:52 System.map-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 4031691 May 6 11:49 System.map-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root37 May 6 11:52 vmlinuz -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw--- 1 root root 8086072 Apr 29 15:54 vmlinuz-5.4.0-29-generic -rw-r--r-- 1 root root 9080832 May 6 11:52 vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 9080832 May 6 11:49 vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root41 May 6 11:52 vmlinuz.old -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879680] Re: Touchpad not detected on Wortmann 1460p
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7-rc6/ ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879680 Title: Touchpad not detected on Wortmann 1460p Status in linux package in Ubuntu: Incomplete Bug description: The Touchpad is not detected on any Ubuntu Live or installed Version from 16.04 to 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gabi 1399 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 20 12:52:57 2020 InstallationDate: Installed on 2020-05-19 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Wortmann_AG 1220615;1470142 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=/dev/mapper/vgubuntu-root ro i8042.reset quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/01/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 52.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: A35 dmi.board.vendor: EA dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: EA dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr52.10:bd06/01/2018:svnWortmann_AG:pn1220615;1470142:pvr1460P;1470142:rvnEA:rnA35:rvrType2-BoardVersion:cvnEA:ct10:cvrChassisVersion: dmi.product.family: NB-TERRA;MOBILE-B;14 dmi.product.name: 1220615;1470142 dmi.product.sku: 4039407048694 dmi.product.version: 1460P;1470142 dmi.sys.vendor: Wortmann_AG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879680/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879612] Re: Wifi looses connection more often after the upgrade
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7-rc6/ ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879612 Title: Wifi looses connection more often after the upgrade Status in linux package in Ubuntu: Incomplete Bug description: I upgraded my ubuntu to 20.04 LTS. After the upgrade I keep seeing the wifi issues. More often it keeps getting disconnected and I will have to go on Airplane mode to re enable the connectivity. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: raghavendra 2046 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-02 (230 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=c6751bdb-dd90-489c-9932-b52487fb6eea ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/03/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.26 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 183E dmi.board.vendor: Hewlett-Packard dmi.board.version: 56.32 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.26:bd06/03/2014:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr07921020561610100:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: B3H81PA#ACJ dmi.product.version: 07921020561610100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879613] Re: Computer hung when resuming from suspend
No I don't think so. It's catch 22... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879613 Title: Computer hung when resuming from suspend Status in linux package in Ubuntu: Incomplete Bug description: The computer seemingly hung when resuming from suspend and failed to show the login screen. Switching to Ctr+Alt+F2 was showing a lot of disk errors. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vadi 3100 F pulseaudio /dev/snd/controlC1: vadi 3100 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Unity:Unity7:ubuntu Date: Wed May 20 07:01:51 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2012-03-23 (2979 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=20aa0109-67bb-46a0-95c6-626f0f0487eb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880103] 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 1880103 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/1880103 Title: Awaking problem after suspend mode still happens Status in linux package in Ubuntu: Incomplete Bug description: 101 kernel seems to be better than 99, when the problem happened almost every time. Nevertheless, it happened again with 2+days uptime and suspending over night. Maybe it depends on my wireless keyboard? I tried Alt+SysRq reisub twice, but it didn't work. Mint Cinnamon 19.1, desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880103/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879680] Re: Touchpad not detected on Wortmann 1460p
** Tags added: hwe-touchpad -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879680 Title: Touchpad not detected on Wortmann 1460p Status in linux package in Ubuntu: Incomplete Bug description: The Touchpad is not detected on any Ubuntu Live or installed Version from 16.04 to 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gabi 1399 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 20 12:52:57 2020 InstallationDate: Installed on 2020-05-19 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Wortmann_AG 1220615;1470142 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=/dev/mapper/vgubuntu-root ro i8042.reset quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/01/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 52.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: A35 dmi.board.vendor: EA dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: EA dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr52.10:bd06/01/2018:svnWortmann_AG:pn1220615;1470142:pvr1460P;1470142:rvnEA:rnA35:rvrType2-BoardVersion:cvnEA:ct10:cvrChassisVersion: dmi.product.family: NB-TERRA;MOBILE-B;14 dmi.product.name: 1220615;1470142 dmi.product.sku: 4039407048694 dmi.product.version: 1460P;1470142 dmi.sys.vendor: Wortmann_AG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879680/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879575] Re: Missing driver for rtl8822be in 20.04
Does cold boot help this issue? ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879575 Title: Missing driver for rtl8822be in 20.04 Status in linux package in Ubuntu: Incomplete Bug description: Wifi adapter can't find avaiable connections in new kernel. Upgraded from 19.04 to 19.10 and then to 20.04 on Lenovo Legion y530 which comes with realtek wifi adapter. lspci shows the pci adapter but not found in lshw -C network. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: manish 1950 F pulseaudio /dev/snd/controlC0: manish 1950 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-07-06 (318 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81FV NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=a67f2402-8ada-4a31-8500-4ce7031521e2 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-18 (1 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/18/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8JCN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion Y530-15ICH dmi.modalias: dmi:bvnLENOVO:bvr8JCN43WW:bd07/18/2018:svnLENOVO:pn81FV:pvrLenovoLegionY530-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLenovoLegionY530-15ICH: dmi.product.family: Legion Y530-15ICH dmi.product.name: 81FV dmi.product.sku: LENOVO_MT_81FV_BU_idea_FM_Legion Y530-15ICH dmi.product.version: Lenovo Legion Y530-15ICH dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879575/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878899] Re: Call trace from __video_do_ioctl
Bus 008 Device 015: ID 046d:08af Logitech, Inc. QuickCam Easy/Cool Bus 008 Device 013: ID 046d:0892 Logitech, Inc. OrbiCam Both used by OBS Studio, which then sent its output to a v4l2loobback device, module parameters: /sbin/modprobe v4l2loopback devices=1 video_nr=10 card_label="OBS Cam" exclusive_caps=1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878899 Title: Call trace from __video_do_ioctl Status in linux package in Ubuntu: Incomplete Bug description: [92420.303133] [ cut here ] [92420.303141] WARNING: CPU: 2 PID: 259541 at drivers/media/v4l2-core/v4l2-ioctl.c:1069 v4l_querycap+0x8f/0xa0 [videodev] [92420.303141] Modules linked in: btrfs xor zstd_compress raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs gspca_zc3xx joydev snd_seq_dummy iptable_mangle xt_CHECKSUM iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c xt_tcpudp bridge stp llc iptable_filter bpfilter v4l2loopback(OE) binfmt_misc nls_iso8859_1 uvcvideo gspca_vc032x gspca_main videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev snd_usb_audio snd_usbmidi_lib mc snd_seq_midi snd_seq_midi_event snd_rawmidi edac_mce_amd kvm_amd ccp snd_hda_codec_realtek snd_seq snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel kvm snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep snd_seq_device snd_pcm input_leds serio_raw k10temp fam15h_power snd_timer snd soundcore mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 uas usb_storage dm_crypt amdgpu amd_iommu_v2 gpu_sched hid_generic usbhid hid crct10dif_pclmul crc32_pclmul [92420.303167] ghash_clmulni_intel radeon i2c_algo_bit ttm aesni_intel drm_kms_helper crypto_simd syscopyarea cryptd sysfillrect sysimgblt glue_helper fb_sys_fops ahci libahci i2c_piix4 drm r8169 realtek video [92420.303174] CPU: 2 PID: 259541 Comm: teams Tainted: GW OE 5.4.0-29-lowlatency #33-Ubuntu [92420.303175] Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./G1.Sniper A88X-CF, BIOS F7 01/08/2014 [92420.303182] RIP: 0010:v4l_querycap+0x8f/0xa0 [videodev] [92420.303183] Code: 00 00 80 48 b9 00 00 20 00 00 00 20 00 48 0b 4b 54 21 d6 39 f2 75 13 48 89 4b 54 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 0b eb d0 <0f> 0b 48 89 4b 54 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 1f 44 00 00 [92420.303184] RSP: 0018:b4aa44dd7c78 EFLAGS: 00010202 [92420.303186] RAX: RBX: b4aa44dd7d88 RCX: 8520800185208001 [92420.303187] RDX: 85008003 RSI: 85008001 RDI: [92420.303188] RBP: b4aa44dd7ca0 R08: R09: 000a [92420.303188] R10: R11: R12: 994f4e421000 [92420.303189] R13: 994f4de6bf00 R14: 994f4c191940 R15: c0f2e360 [92420.303191] FS: 7f47f2ffd700() GS:994f5fb0() knlGS: [92420.303192] CS: 0010 DS: ES: CR0: 80050033 [92420.303193] CR2: 7f482c0e1000 CR3: 0003d0084000 CR4: 000406e0 [92420.303194] Call Trace: [92420.303201] __video_do_ioctl+0x1a7/0x410 [videodev] [92420.303204] ? default_send_IPI_single+0x20/0x40 [92420.303206] ? resched_curr+0x62/0xe0 [92420.303213] video_usercopy+0x2ad/0x690 [videodev] [92420.303220] ? v4l_s_fmt+0x670/0x670 [videodev] [92420.303224] ? wake_up_q+0x40/0x70 [92420.303230] video_ioctl2+0x15/0x20 [videodev] [92420.303237] v4l2_ioctl+0x4c/0x60 [videodev] [92420.303238] do_vfs_ioctl+0x405/0x660 [92420.303240] ? __fget+0x77/0xa0 [92420.303242] ksys_ioctl+0x67/0x90 [92420.303244] __x64_sys_ioctl+0x1a/0x20 [92420.303246] do_syscall_64+0x57/0x190 [92420.303248] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [92420.303249] RIP: 0033:0x7f489773737b [92420.303251] Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48 [92420.303252] RSP: 002b:7f47f2ff77e8 EFLAGS: 0246 ORIG_RAX: 0010 [92420.303254] RAX: ffda RBX: 7f4824026900 RCX: 7f489773737b [92420.303255] RDX: 7f47f2ff78b0 RSI: 80685600 RDI: 0046 [92420.303256] RBP: 80685600 R08: R09: 5645ec03ee68 [92420.303257] R10: 0048 R11: 0246 R12: 0046 [92420.303258] R13: 7f47f2ff78b0 R14: 0015 R15: 7f485b666039 [92420.303260] ---[ end trace 6e9a5041142fdaab ]--- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-lowlatency 5.4.0.29.34 ProcVersionSignature: Ubuntu 5.4.0-29.33-lowlatency 5.4.30 Uname: Linux 5.4.0-29-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture:
[Kernel-packages] [Bug 1870140] Re: Laptop freeze after unplug power-AC (USB-C)
It'll be fixed by Ubuntu-5.4.0-32.36. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1870140 Title: Laptop freeze after unplug power-AC (USB-C) Status in linux package in Ubuntu: Confirmed Bug description: ## Power adapter plugged in, charging goes well [ 1018.621820] asus_wmi: Unknown key cf pressed ## Power adapter unplugged, after few moments system freeze [ 567.444810] BUG: kernel NULL pointer dereference, address: 0080 [ 567.444819] #PF: supervisor read access in kernel mode [ 567.444823] #PF: error_code(0x) - not-present page [ 567.444827] PGD 0 P4D 0 [ 567.444834] Oops: [#1] PREEMPT SMP PTI [ 567.444841] CPU: 0 PID: 2873 Comm: kworker/0:0 Not tainted 5.5.11-151.current #1 [ 567.444845] Hardware name: ASUSTeK COMPUTER INC. UX370UAR/UX370UAR, BIOS UX370UAR.310 04/17/2019 [ 567.444857] Workqueue: events ucsi_handle_connector_change [typec_ucsi] [ 567.444868] RIP: 0010:ucsi_displayport_remove_partner+0xa/0x20 [typec_ucsi] [ 567.444874] Code: 38 00 c7 43 28 00 00 00 00 48 83 c7 10 5b e9 6d cd 75 e1 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 48 85 ff 74 0f <48> 8b 47 78 48 c7 00 00 00 00 00 c6 40 3d 00 c3 66 0f 1f 44 00 00 [ 567.444878] RSP: 0018:c9477df0 EFLAGS: 00010202 [ 567.444883] RAX: 0008 RBX: 88844685c418 RCX: 000efd00 [ 567.444886] RDX: RSI: 0001 RDI: 0008 [ 567.444889] RBP: R08: R09: c9477ce0 [ 567.444892] R10: 888443e9f218 R11: 88844edeb478 R12: 88844685c418 [ 567.444895] R13: 0001 R14: 88844685c2a8 R15: [ 567.444900] FS: () GS:88844ec0() knlGS: [ 567.444903] CS: 0010 DS: ES: CR0: 80050033 [ 567.444906] CR2: 0080 CR3: 0240a006 CR4: 003606f0 [ 567.444909] Call Trace: [ 567.444921] ucsi_unregister_altmodes+0x7b/0x90 [typec_ucsi] [ 567.444930] ucsi_unregister_partner.part.0+0x13/0x30 [typec_ucsi] [ 567.444938] ucsi_handle_connector_change+0x231/0x310 [typec_ucsi] [ 567.444949] ? kmem_cache_free+0x22a/0x290 [ 567.444960] process_one_work+0x1e1/0x3d0 [ 567.444968] worker_thread+0x4a/0x3d0 [ 567.444976] kthread+0xfb/0x130 [ 567.444983] ? process_one_work+0x3d0/0x3d0 [ 567.444988] ? kthread_park+0x90/0x90 [ 567.444998] ret_from_fork+0x35/0x40 [ 567.445006] Modules linked in: typec_displayport hidp rfcomm ccm cmac fuse snd_hda_codec_hdmi joydev snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio bnep intel_rapl_msr snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi iTCO_wdt hid_multitouch iTCO_vendor_support mei_hdcp iwlmvm intel_rapl_common snd_soc_core mac80211 snd_compress libarc4 x86_pkg_temp_thermal intel_powerclamp snd_pcm_dmaengine uvcvideo ac97_bus coretemp videobuf2_vmalloc videobuf2_memops i915 snd_hda_intel videobuf2_v4l2 snd_intel_dspcfg iwlwifi kvm_intel videobuf2_common hid_sensor_accel_3d i2c_algo_bit videodev snd_hda_codec btusb hid_sensor_trigger kvm industrialio_triggered_buffer snd_hda_core drm_kms_helper kfifo_buf btrtl btbcm syscopyarea snd_hwdep sysfillrect btintel industrialio asus_nb_wmi irqbypass mc wmi_bmof asus_wmi evdev sysimgblt hid_sensor_iio_common bluetooth cfg80211 sparse_keymap snd_pcm fb_sys_fops i2c_i801 ucsi_acpi snd_timer [ 567.445072] typec_ucsi efivars snd soundcore spi_pxa2xx_platform mei_me dw_dmac rfkill thermal typec i2c_designware_platform mei i2c_designware_core drm elan_i2c ac tpm_tis tpm_tis_core pinctrl_sunrisepoint tpm pinctrl_intel rng_core asus_wireless acpi_pad button hid_sensor_hub hid_generic intel_ishtp_hid xhci_pci serio_raw xhci_hcd intel_ish_ipc usbcore intel_ishtp usb_common wmi i2c_hid hid battery video [ 567.445112] CR2: 0080 [ 567.445117] ---[ end trace a50cf550f0b4969a ]--- [ 567.445126] RIP: 0010:ucsi_displayport_remove_partner+0xa/0x20 [typec_ucsi] [ 567.445132] Code: 38 00 c7 43 28 00 00 00 00 48 83 c7 10 5b e9 6d cd 75 e1 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 48 85 ff 74 0f <48> 8b 47 78 48 c7 00 00 00 00 00 c6 40 3d 00 c3 66 0f 1f 44 00 00 [ 567.445136] RSP: 0018:c9477df0 EFLAGS: 00010202 [ 567.445140] RAX: 0008 RBX: 88844685c418 RCX: 000efd00 [ 567.445143] RDX: RSI: 0001 RDI: 0008 [ 567.445146] RBP: R08: R09: c9477ce0 [ 567.445149] R10: 888443e9f218 R11: 88844edeb478 R12: 88844685c418 [ 567.445152] R13: 0001 R14: 88844685c2a8 R15: [ 567.445156] FS: () GS:88844ec0(
[Kernel-packages] [Bug 1880119] [NEW] System hangs on shut down Kernel 5.3.0-53
Public bug reported: System does not shut down properly with this Kernel: Kernel 5.3.0-51 seems to work OK This is on a system running Mint 19.3 and "ubuntu-bug linux" is not working. Attached is version.log and the output of inxi ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "version and inxi output" https://bugs.launchpad.net/bugs/1880119/+attachment/5375547/+files/version.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1880119 Title: System hangs on shut down Kernel 5.3.0-53 Status in linux package in Ubuntu: New Bug description: System does not shut down properly with this Kernel: Kernel 5.3.0-51 seems to work OK This is on a system running Mint 19.3 and "ubuntu-bug linux" is not working. Attached is version.log and the output of inxi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879612] Re: Wifi looses connection more often after the upgrade
I see a few "wlo1: deauthenticating from by local choice (Reason: 3=DEAUTH_LEAVING)". Could you attach the whole journal log? $ journalctl -b > journal.log And attach it here. We might have to enable verbose log for NetworkManager/wpasupplicant, but let's what do we have so far. ** Tags added: hwe-networking-wifi ** Summary changed: - Wifi looses connection more often after the upgrade + Ralink RT5390 [1814:539f] Subsystem [103c:1774] Wifi looses connection more often after the upgrade -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879612 Title: Ralink RT5390 [1814:539f] Subsystem [103c:1774] Wifi looses connection more often after the upgrade Status in linux package in Ubuntu: Incomplete Bug description: I upgraded my ubuntu to 20.04 LTS. After the upgrade I keep seeing the wifi issues. More often it keeps getting disconnected and I will have to go on Airplane mode to re enable the connectivity. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: raghavendra 2046 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-02 (230 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=c6751bdb-dd90-489c-9932-b52487fb6eea ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/03/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.26 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 183E dmi.board.vendor: Hewlett-Packard dmi.board.version: 56.32 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.26:bd06/03/2014:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr07921020561610100:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: B3H81PA#ACJ dmi.product.version: 07921020561610100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880119] Re: System hangs on shut down Kernel 5.3.0-53
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 ** This bug has been marked a duplicate of bug 1879997 HP-255-G7-Notebook-PC 5.3.0-51-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1880119 Title: System hangs on shut down Kernel 5.3.0-53 Status in linux package in Ubuntu: New Bug description: System does not shut down properly with this Kernel: Kernel 5.3.0-51 seems to work OK This is on a system running Mint 19.3 and "ubuntu-bug linux" is not working. Attached is version.log and the output of inxi --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: toni 1676 F pulseaudio /dev/snd/controlC1: toni 1676 F pulseaudio /dev/snd/controlC0: toni 1676 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=UUID=d0307c73-ce08-4c07-bb9b-1cf668a42a00 InstallationDate: Installed on 2019-07-25 (301 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190711 IwConfig: enp8s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B450M S2H Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic root=UUID=c5a03a46-cc90-417d-97fc-906910b14c02 ro idle=nomwait quiet splash processor.max_cstate=5 vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-53-generic N/A linux-backports-modules-5.3.0-53-generic N/A linux-firmware1.173.18 RfKill: Tags: tricia Uname: Linux 5.3.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm backup cdrom dip lp lpadmin messagebus plugdev sambashare saned scanner ssh sudo vboxusers _MarkForUpload: True dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: B450M S2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MS2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MS2H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450M S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880119] ProcModules.txt
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1880119/+attachment/5375558/+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/1880119 Title: System hangs on shut down Kernel 5.3.0-53 Status in linux package in Ubuntu: New Bug description: System does not shut down properly with this Kernel: Kernel 5.3.0-51 seems to work OK This is on a system running Mint 19.3 and "ubuntu-bug linux" is not working. Attached is version.log and the output of inxi --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: toni 1676 F pulseaudio /dev/snd/controlC1: toni 1676 F pulseaudio /dev/snd/controlC0: toni 1676 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=UUID=d0307c73-ce08-4c07-bb9b-1cf668a42a00 InstallationDate: Installed on 2019-07-25 (301 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190711 IwConfig: enp8s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B450M S2H Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic root=UUID=c5a03a46-cc90-417d-97fc-906910b14c02 ro idle=nomwait quiet splash processor.max_cstate=5 vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-53-generic N/A linux-backports-modules-5.3.0-53-generic N/A linux-firmware1.173.18 RfKill: Tags: tricia Uname: Linux 5.3.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm backup cdrom dip lp lpadmin messagebus plugdev sambashare saned scanner ssh sudo vboxusers _MarkForUpload: True dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: B450M S2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MS2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MS2H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450M S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880119] CRDA.txt
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1880119/+attachment/5375550/+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/1880119 Title: System hangs on shut down Kernel 5.3.0-53 Status in linux package in Ubuntu: New Bug description: System does not shut down properly with this Kernel: Kernel 5.3.0-51 seems to work OK This is on a system running Mint 19.3 and "ubuntu-bug linux" is not working. Attached is version.log and the output of inxi --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: toni 1676 F pulseaudio /dev/snd/controlC1: toni 1676 F pulseaudio /dev/snd/controlC0: toni 1676 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=UUID=d0307c73-ce08-4c07-bb9b-1cf668a42a00 InstallationDate: Installed on 2019-07-25 (301 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190711 IwConfig: enp8s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B450M S2H Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic root=UUID=c5a03a46-cc90-417d-97fc-906910b14c02 ro idle=nomwait quiet splash processor.max_cstate=5 vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-53-generic N/A linux-backports-modules-5.3.0-53-generic N/A linux-firmware1.173.18 RfKill: Tags: tricia Uname: Linux 5.3.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm backup cdrom dip lp lpadmin messagebus plugdev sambashare saned scanner ssh sudo vboxusers _MarkForUpload: True dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: B450M S2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MS2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MS2H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450M S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880119] ProcCpuinfo.txt
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1880119/+attachment/5375554/+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/1880119 Title: System hangs on shut down Kernel 5.3.0-53 Status in linux package in Ubuntu: New Bug description: System does not shut down properly with this Kernel: Kernel 5.3.0-51 seems to work OK This is on a system running Mint 19.3 and "ubuntu-bug linux" is not working. Attached is version.log and the output of inxi --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: toni 1676 F pulseaudio /dev/snd/controlC1: toni 1676 F pulseaudio /dev/snd/controlC0: toni 1676 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=UUID=d0307c73-ce08-4c07-bb9b-1cf668a42a00 InstallationDate: Installed on 2019-07-25 (301 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190711 IwConfig: enp8s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B450M S2H Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic root=UUID=c5a03a46-cc90-417d-97fc-906910b14c02 ro idle=nomwait quiet splash processor.max_cstate=5 vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-53-generic N/A linux-backports-modules-5.3.0-53-generic N/A linux-firmware1.173.18 RfKill: Tags: tricia Uname: Linux 5.3.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm backup cdrom dip lp lpadmin messagebus plugdev sambashare saned scanner ssh sudo vboxusers _MarkForUpload: True dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: B450M S2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MS2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MS2H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450M S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880119] UdevDb.txt
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1880119/+attachment/5375560/+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/1880119 Title: System hangs on shut down Kernel 5.3.0-53 Status in linux package in Ubuntu: New Bug description: System does not shut down properly with this Kernel: Kernel 5.3.0-51 seems to work OK This is on a system running Mint 19.3 and "ubuntu-bug linux" is not working. Attached is version.log and the output of inxi --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: toni 1676 F pulseaudio /dev/snd/controlC1: toni 1676 F pulseaudio /dev/snd/controlC0: toni 1676 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=UUID=d0307c73-ce08-4c07-bb9b-1cf668a42a00 InstallationDate: Installed on 2019-07-25 (301 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190711 IwConfig: enp8s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B450M S2H Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic root=UUID=c5a03a46-cc90-417d-97fc-906910b14c02 ro idle=nomwait quiet splash processor.max_cstate=5 vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-53-generic N/A linux-backports-modules-5.3.0-53-generic N/A linux-firmware1.173.18 RfKill: Tags: tricia Uname: Linux 5.3.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm backup cdrom dip lp lpadmin messagebus plugdev sambashare saned scanner ssh sudo vboxusers _MarkForUpload: True dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: B450M S2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MS2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MS2H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450M S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880119] ProcCpuinfoMinimal.txt
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1880119/+attachment/537/+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/1880119 Title: System hangs on shut down Kernel 5.3.0-53 Status in linux package in Ubuntu: New Bug description: System does not shut down properly with this Kernel: Kernel 5.3.0-51 seems to work OK This is on a system running Mint 19.3 and "ubuntu-bug linux" is not working. Attached is version.log and the output of inxi --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: toni 1676 F pulseaudio /dev/snd/controlC1: toni 1676 F pulseaudio /dev/snd/controlC0: toni 1676 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=UUID=d0307c73-ce08-4c07-bb9b-1cf668a42a00 InstallationDate: Installed on 2019-07-25 (301 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190711 IwConfig: enp8s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B450M S2H Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic root=UUID=c5a03a46-cc90-417d-97fc-906910b14c02 ro idle=nomwait quiet splash processor.max_cstate=5 vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-53-generic N/A linux-backports-modules-5.3.0-53-generic N/A linux-firmware1.173.18 RfKill: Tags: tricia Uname: Linux 5.3.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm backup cdrom dip lp lpadmin messagebus plugdev sambashare saned scanner ssh sudo vboxusers _MarkForUpload: True dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: B450M S2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MS2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MS2H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450M S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880119] Re: System hangs on shut down Kernel 5.3.0-53
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 apport information ** Tags added: apport-collected tricia ** Description changed: System does not shut down properly with this Kernel: Kernel 5.3.0-51 seems to work OK This is on a system running Mint 19.3 and "ubuntu-bug linux" is not working. Attached is version.log and the output of inxi + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.14 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC2: toni 1676 F pulseaudio + /dev/snd/controlC1: toni 1676 F pulseaudio + /dev/snd/controlC0: toni 1676 F pulseaudio + CurrentDesktop: X-Cinnamon + DistroRelease: Linux Mint 19.3 + HibernationDevice: RESUME=UUID=d0307c73-ce08-4c07-bb9b-1cf668a42a00 + InstallationDate: Installed on 2019-07-25 (301 days ago) + InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190711 + IwConfig: + enp8s0no wireless extensions. + + lono wireless extensions. + MachineType: Gigabyte Technology Co., Ltd. B450M S2H + Package: linux (not installed) + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic root=UUID=c5a03a46-cc90-417d-97fc-906910b14c02 ro idle=nomwait quiet splash processor.max_cstate=5 vt.handoff=1 + ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 + RelatedPackageVersions: + linux-restricted-modules-5.3.0-53-generic N/A + linux-backports-modules-5.3.0-53-generic N/A + linux-firmware1.173.18 + RfKill: + + Tags: tricia + Uname: Linux 5.3.0-53-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm backup cdrom dip lp lpadmin messagebus plugdev sambashare saned scanner ssh sudo vboxusers + _MarkForUpload: True + dmi.bios.date: 11/27/2019 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: F50 + dmi.board.asset.tag: Default string + dmi.board.name: B450M S2H + dmi.board.vendor: Gigabyte Technology Co., Ltd. + dmi.board.version: x.x + dmi.chassis.asset.tag: Default string + dmi.chassis.type: 3 + dmi.chassis.vendor: Default string + dmi.chassis.version: Default string + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MS2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MS2H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: + dmi.product.family: Default string + dmi.product.name: B450M S2H + dmi.product.sku: Default string + dmi.product.version: Default string + dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1880119/+attachment/5375549/+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/1880119 Title: System hangs on shut down Kernel 5.3.0-53 Status in linux package in Ubuntu: New Bug description: System does not shut down properly with this Kernel: Kernel 5.3.0-51 seems to work OK This is on a system running Mint 19.3 and "ubuntu-bug linux" is not working. Attached is version.log and the output of inxi --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: toni 1676 F pulseaudio /dev/snd/controlC1: toni 1676 F pulseaudio /dev/snd/controlC0: toni 1676 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=UUID=d0307c73-ce08-4c07-bb9b-1cf668a42a00 InstallationDate: Installed on 2019-07-25 (301 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190711 IwConfig: enp8s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B450M S2H Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic root=UUID=c5a03a46-cc90-417d-97fc-906910b14c02 ro idle=nomwait quiet splash processor.max_cstate=5 vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-53-generic N/A linux-backports-modules-5.3.0-53-generic N/A linux-firmware1.173.18 RfKill: Tags: tricia Uname: Linux 5.3.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm backup cdrom dip lp lpadmin messagebus plugdev sambashare saned scanner ssh sudo vboxusers _MarkForUpload: True dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: B450M S2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.
[Kernel-packages] [Bug 1880119] Lsusb.txt
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1880119/+attachment/5375553/+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/1880119 Title: System hangs on shut down Kernel 5.3.0-53 Status in linux package in Ubuntu: New Bug description: System does not shut down properly with this Kernel: Kernel 5.3.0-51 seems to work OK This is on a system running Mint 19.3 and "ubuntu-bug linux" is not working. Attached is version.log and the output of inxi --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: toni 1676 F pulseaudio /dev/snd/controlC1: toni 1676 F pulseaudio /dev/snd/controlC0: toni 1676 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=UUID=d0307c73-ce08-4c07-bb9b-1cf668a42a00 InstallationDate: Installed on 2019-07-25 (301 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190711 IwConfig: enp8s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B450M S2H Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic root=UUID=c5a03a46-cc90-417d-97fc-906910b14c02 ro idle=nomwait quiet splash processor.max_cstate=5 vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-53-generic N/A linux-backports-modules-5.3.0-53-generic N/A linux-firmware1.173.18 RfKill: Tags: tricia Uname: Linux 5.3.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm backup cdrom dip lp lpadmin messagebus plugdev sambashare saned scanner ssh sudo vboxusers _MarkForUpload: True dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: B450M S2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MS2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MS2H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450M S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880119] CurrentDmesg.txt
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1880119/+attachment/5375551/+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/1880119 Title: System hangs on shut down Kernel 5.3.0-53 Status in linux package in Ubuntu: New Bug description: System does not shut down properly with this Kernel: Kernel 5.3.0-51 seems to work OK This is on a system running Mint 19.3 and "ubuntu-bug linux" is not working. Attached is version.log and the output of inxi --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: toni 1676 F pulseaudio /dev/snd/controlC1: toni 1676 F pulseaudio /dev/snd/controlC0: toni 1676 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=UUID=d0307c73-ce08-4c07-bb9b-1cf668a42a00 InstallationDate: Installed on 2019-07-25 (301 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190711 IwConfig: enp8s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B450M S2H Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic root=UUID=c5a03a46-cc90-417d-97fc-906910b14c02 ro idle=nomwait quiet splash processor.max_cstate=5 vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-53-generic N/A linux-backports-modules-5.3.0-53-generic N/A linux-firmware1.173.18 RfKill: Tags: tricia Uname: Linux 5.3.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm backup cdrom dip lp lpadmin messagebus plugdev sambashare saned scanner ssh sudo vboxusers _MarkForUpload: True dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: B450M S2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MS2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MS2H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450M S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880119] Lspci.txt
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1880119/+attachment/5375552/+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/1880119 Title: System hangs on shut down Kernel 5.3.0-53 Status in linux package in Ubuntu: New Bug description: System does not shut down properly with this Kernel: Kernel 5.3.0-51 seems to work OK This is on a system running Mint 19.3 and "ubuntu-bug linux" is not working. Attached is version.log and the output of inxi --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: toni 1676 F pulseaudio /dev/snd/controlC1: toni 1676 F pulseaudio /dev/snd/controlC0: toni 1676 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=UUID=d0307c73-ce08-4c07-bb9b-1cf668a42a00 InstallationDate: Installed on 2019-07-25 (301 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190711 IwConfig: enp8s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B450M S2H Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic root=UUID=c5a03a46-cc90-417d-97fc-906910b14c02 ro idle=nomwait quiet splash processor.max_cstate=5 vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-53-generic N/A linux-backports-modules-5.3.0-53-generic N/A linux-firmware1.173.18 RfKill: Tags: tricia Uname: Linux 5.3.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm backup cdrom dip lp lpadmin messagebus plugdev sambashare saned scanner ssh sudo vboxusers _MarkForUpload: True dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: B450M S2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MS2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MS2H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450M S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880119] ProcEnviron.txt
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1880119/+attachment/5375556/+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/1880119 Title: System hangs on shut down Kernel 5.3.0-53 Status in linux package in Ubuntu: New Bug description: System does not shut down properly with this Kernel: Kernel 5.3.0-51 seems to work OK This is on a system running Mint 19.3 and "ubuntu-bug linux" is not working. Attached is version.log and the output of inxi --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: toni 1676 F pulseaudio /dev/snd/controlC1: toni 1676 F pulseaudio /dev/snd/controlC0: toni 1676 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=UUID=d0307c73-ce08-4c07-bb9b-1cf668a42a00 InstallationDate: Installed on 2019-07-25 (301 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190711 IwConfig: enp8s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B450M S2H Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic root=UUID=c5a03a46-cc90-417d-97fc-906910b14c02 ro idle=nomwait quiet splash processor.max_cstate=5 vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-53-generic N/A linux-backports-modules-5.3.0-53-generic N/A linux-firmware1.173.18 RfKill: Tags: tricia Uname: Linux 5.3.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm backup cdrom dip lp lpadmin messagebus plugdev sambashare saned scanner ssh sudo vboxusers _MarkForUpload: True dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: B450M S2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MS2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MS2H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450M S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880119] ProcInterrupts.txt
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1880119/+attachment/5375557/+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/1880119 Title: System hangs on shut down Kernel 5.3.0-53 Status in linux package in Ubuntu: New Bug description: System does not shut down properly with this Kernel: Kernel 5.3.0-51 seems to work OK This is on a system running Mint 19.3 and "ubuntu-bug linux" is not working. Attached is version.log and the output of inxi --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: toni 1676 F pulseaudio /dev/snd/controlC1: toni 1676 F pulseaudio /dev/snd/controlC0: toni 1676 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=UUID=d0307c73-ce08-4c07-bb9b-1cf668a42a00 InstallationDate: Installed on 2019-07-25 (301 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190711 IwConfig: enp8s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B450M S2H Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic root=UUID=c5a03a46-cc90-417d-97fc-906910b14c02 ro idle=nomwait quiet splash processor.max_cstate=5 vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-53-generic N/A linux-backports-modules-5.3.0-53-generic N/A linux-firmware1.173.18 RfKill: Tags: tricia Uname: Linux 5.3.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm backup cdrom dip lp lpadmin messagebus plugdev sambashare saned scanner ssh sudo vboxusers _MarkForUpload: True dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: B450M S2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MS2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MS2H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450M S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880119] PulseList.txt
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1880119/+attachment/5375559/+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/1880119 Title: System hangs on shut down Kernel 5.3.0-53 Status in linux package in Ubuntu: New Bug description: System does not shut down properly with this Kernel: Kernel 5.3.0-51 seems to work OK This is on a system running Mint 19.3 and "ubuntu-bug linux" is not working. Attached is version.log and the output of inxi --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: toni 1676 F pulseaudio /dev/snd/controlC1: toni 1676 F pulseaudio /dev/snd/controlC0: toni 1676 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=UUID=d0307c73-ce08-4c07-bb9b-1cf668a42a00 InstallationDate: Installed on 2019-07-25 (301 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190711 IwConfig: enp8s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B450M S2H Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic root=UUID=c5a03a46-cc90-417d-97fc-906910b14c02 ro idle=nomwait quiet splash processor.max_cstate=5 vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-53-generic N/A linux-backports-modules-5.3.0-53-generic N/A linux-firmware1.173.18 RfKill: Tags: tricia Uname: Linux 5.3.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm backup cdrom dip lp lpadmin messagebus plugdev sambashare saned scanner ssh sudo vboxusers _MarkForUpload: True dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: B450M S2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MS2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MS2H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450M S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880119] WifiSyslog.txt
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1880119/+attachment/5375561/+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/1880119 Title: System hangs on shut down Kernel 5.3.0-53 Status in linux package in Ubuntu: New Bug description: System does not shut down properly with this Kernel: Kernel 5.3.0-51 seems to work OK This is on a system running Mint 19.3 and "ubuntu-bug linux" is not working. Attached is version.log and the output of inxi --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: toni 1676 F pulseaudio /dev/snd/controlC1: toni 1676 F pulseaudio /dev/snd/controlC0: toni 1676 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=UUID=d0307c73-ce08-4c07-bb9b-1cf668a42a00 InstallationDate: Installed on 2019-07-25 (301 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190711 IwConfig: enp8s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B450M S2H Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic root=UUID=c5a03a46-cc90-417d-97fc-906910b14c02 ro idle=nomwait quiet splash processor.max_cstate=5 vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-53-generic N/A linux-backports-modules-5.3.0-53-generic N/A linux-firmware1.173.18 RfKill: Tags: tricia Uname: Linux 5.3.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm backup cdrom dip lp lpadmin messagebus plugdev sambashare saned scanner ssh sudo vboxusers _MarkForUpload: True dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: B450M S2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MS2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MS2H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450M S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867591] Re: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch
Thanks for suggestion but I do not feel comfortable drop a line from a patch before perfectly understanding everything in drivers. If Hisilicon can help on backporting or test case, that will be much helpful. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867591 Title: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch Status in kunpeng920: Incomplete Status in kunpeng920 ubuntu-18.04-hwe series: Incomplete Status in kunpeng920 ubuntu-20.04 series: Incomplete Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] roce patchset have merged into mainline 5.6rc2 kernel. [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] crypto: hisilicon/sec2 - Add pbuffer mode for SEC driver crypto: hisilicon/sec2 - Update IV and MAC operation crypto: hisilicon/sec2 - Add iommu status check crypto: hisilicon/sec2 - Add workqueue for SEC driver. crypto: hisilicon - Use one workqueue per qm instead of per qp crypto: hisilicon - qm depends on UACCE crypto: hisilicon - remove redundant assignment of pointer ctx hisilicon - register zip engine to uacce hisilicon - Remove module_param uacce_mode uacce: add uacce driver uacce: Add documents for uacce crypto: hisilicon - Fix duplicate print when qm occur multiple errors crypto: hisilicon - Unify error detect process into qm crypto: hisilicon - Configure zip RAS error type crypto: hisilicon - Unify hardware error init/uninit into QM To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1867591/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880125] [NEW] v3d driver clock problem forces OpenGL to use software rendering
Public bug reported: release: 32-bit ubuntu 20.04 running on a raspberry pi 4 package: linux-raspi 5.4.0.1008.8 I made the configuration change described in: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1876862 and am running a kernel with v3d on a raspberry pi 4. Unfortunately, OpenGL is still not using the GPU; it's using the software renderer, llvmpipe. Setting LIBGL_DEBUG=verbose and running an OpenGL program shows that OpenGL can't open any /dev/dri/renderD* device. Looking in /dev/dri, there are no device files that begin with "render," indicating the v3d driver isn't starting up properly. Adding debugging code to the kernel, I find that: (1) drivers/gpu/drm/v3d/v3d_drv.c:v3d_platform_drm_probe() fails because it can't get a clock - devm_clk_get() returns an error. (2) in drivers/clk/clk.c:of_clk_get_hw(), the call to of_parse_clkspec() for the v3d driver yields a desired clock source of "firmware-clocks". (3) drivers/clk/clk.c:of_clk_get_hw_from_clkspec() fails because it can only find six clock providers (aux@7e215000, cprman@7e101000, clock@7ef0, clk-108M, clk-usb, clk-osc) none of which match the requested "firmware-clocks". The solution is to add a clock definition to the kernel source and a corresponding change to the device tree, but I'm not familiar enough with either to create that solution myself. In the raspbian kernel source tree, drivers/clk/bcm/clk-raspberrypi.c defines BCM2835_CLOCK_V3D, but there is no corresponding definition in the ubuntu source tree. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Tags: device-tree kernel-bug opengl raspberry-pi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1880125 Title: v3d driver clock problem forces OpenGL to use software rendering Status in linux-raspi package in Ubuntu: New Bug description: release: 32-bit ubuntu 20.04 running on a raspberry pi 4 package: linux-raspi 5.4.0.1008.8 I made the configuration change described in: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1876862 and am running a kernel with v3d on a raspberry pi 4. Unfortunately, OpenGL is still not using the GPU; it's using the software renderer, llvmpipe. Setting LIBGL_DEBUG=verbose and running an OpenGL program shows that OpenGL can't open any /dev/dri/renderD* device. Looking in /dev/dri, there are no device files that begin with "render," indicating the v3d driver isn't starting up properly. Adding debugging code to the kernel, I find that: (1) drivers/gpu/drm/v3d/v3d_drv.c:v3d_platform_drm_probe() fails because it can't get a clock - devm_clk_get() returns an error. (2) in drivers/clk/clk.c:of_clk_get_hw(), the call to of_parse_clkspec() for the v3d driver yields a desired clock source of "firmware-clocks". (3) drivers/clk/clk.c:of_clk_get_hw_from_clkspec() fails because it can only find six clock providers (aux@7e215000, cprman@7e101000, clock@7ef0, clk-108M, clk-usb, clk-osc) none of which match the requested "firmware-clocks". The solution is to add a clock definition to the kernel source and a corresponding change to the device tree, but I'm not familiar enough with either to create that solution myself. In the raspbian kernel source tree, drivers/clk/bcm/clk-raspberrypi.c defines BCM2835_CLOCK_V3D, but there is no corresponding definition in the ubuntu source tree. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880125/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875252] Re: Ubuntu 20.04 LTS update causing no sound coming from built-in speakers
I have a similar problem: https://bugs.launchpad.net/ubuntu/+bug/1879973 URL for the patch: https://launchpad.net/~kaihengfeng/+archive/ubuntu /fix-lp1869819 This patch didn't fix my built-in speaker and microphone. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875252 Title: Ubuntu 20.04 LTS update causing no sound coming from built-in speakers Status in linux package in Ubuntu: Confirmed Bug description: After updating to Ubuntu 20.04 LTS, the only way of hearing audio is through headphones. The sound settings tab doesn't even show any other output option other than "Dummy output" . I have already checked other versions and everything works perfectly when I downgrade to Ubuntu 19.10, so I think this is a version related bug. Just to reiterate my laptop is a DELL Inspiron 14 3420.The sound card showing in alsamixer window is HDA Intel PCH, and the chip is Cirrus Logic CS4213. I have looked up solutions online for 2 days and none has worked. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: george 1499 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 26 19:04:06 2020 InstallationDate: Installed on 2020-04-26 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Inspiron 3420 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=ec9a2552-c1da-44bd-9967-5be8bc6da075 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-26 (0 days ago) dmi.bios.date: 09/28/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 04XGDT dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA05:bd09/28/2012:svnDellInc.:pnInspiron3420:pvrNotSpecified:rvnDellInc.:rn04XGDT:rvrA05:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3420 dmi.product.sku: To be filled by O.E.M. dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded
That's certainly incorrect, lvm2 was fixed in focal (and hence groovy). That only leaves xenial, but updating xenial close to its EOL for something as unusual as this seems unneccessary. The supported configuration for raid1 is mdadm after all, not removing mdadm and the meta packages that depend on it and using lvm's raid support. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1509717 Title: Wily LVM-RAID1 – md: personality for level 1 is not loaded Status in linux package in Ubuntu: Invalid Status in lvm2 package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in lvm2 source package in Bionic: Fix Released Status in linux source package in Cosmic: Invalid Status in lvm2 source package in Cosmic: Won't Fix Status in linux source package in Disco: Invalid Status in lvm2 source package in Disco: Won't Fix Status in linux source package in Eoan: Invalid Status in lvm2 source package in Eoan: Fix Released Status in lvm2 package in Debian: Incomplete Bug description: [Impact] system does not boot after converting lvm volume to raid1 w/o having mdadm installed. [Test case] 1. Install server with subiquity to LVM 2. Add second disk to it 3. Run pvcreate /dev/vdb 4. Run vgextend ubuntu-vg /dev/vdb 5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv Reboot and check that it still boots. 6. Remove mdadm 7. Upgrade to lvm2 from proposed Reboot and check that it still boots. 8. Downgrade lvm2 to release Reboot and check that it fails to boot [Regression potential] Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier. [Original bug report] After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot. I get the following message each time LVM tries to activate a raid1 LV: md: personality for level 1 is not loaded! Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879575] Re: Missing driver for rtl8822be in 20.04
It wasn't missing driver, the new driver rtw88 is now responsible of driven RTL8822BE, not the staging driver rtl8822be that existed for some time (v4.14 ~ v5.1)[1]. In the old age, rtl8822be has a parameter "aspm" and users may disable it to work-around this issue, and that is not possible so far with the new rtw88 driver. Can you have a try on https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879575? Let's proof that's the root cause first. You should run following commands to install kernel packages: $ sudo add-apt-repository ppa:vicamo/ppa-1879575 $ sudo apt install \ linux-modules-extra-5.4.0-33-generic=5.4.0-33.37+lp1879575 \ linux-modules-5.4.0-33-generic=5.4.0-33.37+lp1879575 \ linux-image-unsigned-5.4.0-33-generic=5.4.0-33.37+lp1879575 Note this ppa build may take several hours from now to finish. Reboot into the new kernel and attach system journal either it works or not: $ journalctl -b > journal.log Please attach that journal.log file as attachment here. By the way, I have also one RTL8822BE chip, but it works just fine in Focal. [1]: https://cateee.net/lkddb/web-lkddb/R8822BE.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879575 Title: Missing driver for rtl8822be in 20.04 Status in linux package in Ubuntu: Incomplete Bug description: Wifi adapter can't find avaiable connections in new kernel. Upgraded from 19.04 to 19.10 and then to 20.04 on Lenovo Legion y530 which comes with realtek wifi adapter. lspci shows the pci adapter but not found in lshw -C network. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: manish 1950 F pulseaudio /dev/snd/controlC0: manish 1950 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-07-06 (318 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81FV NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=a67f2402-8ada-4a31-8500-4ce7031521e2 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-18 (1 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/18/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8JCN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion Y530-15ICH dmi.modalias: dmi:bvnLENOVO:bvr8JCN43WW:bd07/18/2018:svnLENOVO:pn81FV:pvrLenovoLegionY530-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLenovoLegionY530-15ICH: dmi.product.family: Legion Y530-15ICH dmi.product.name: 81FV dmi.product.sku: LENOVO_MT_81FV_BU_idea_FM_Legion Y530-15ICH dmi.product.version: Lenovo Legion Y530-15ICH dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879575/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879575] Re: Missing driver for rtl8822be in 20.04
** Tags added: hwe-networking-wifi ** Summary changed: - Missing driver for rtl8822be in 20.04 + rtl8822be not initialized: rtw_pci: Refused to change power state, currently in D3 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879575 Title: rtl8822be not initialized: rtw_pci: Refused to change power state, currently in D3 Status in linux package in Ubuntu: Incomplete Bug description: Wifi adapter can't find avaiable connections in new kernel. Upgraded from 19.04 to 19.10 and then to 20.04 on Lenovo Legion y530 which comes with realtek wifi adapter. lspci shows the pci adapter but not found in lshw -C network. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: manish 1950 F pulseaudio /dev/snd/controlC0: manish 1950 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-07-06 (318 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81FV NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=a67f2402-8ada-4a31-8500-4ce7031521e2 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-18 (1 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/18/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8JCN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion Y530-15ICH dmi.modalias: dmi:bvnLENOVO:bvr8JCN43WW:bd07/18/2018:svnLENOVO:pn81FV:pvrLenovoLegionY530-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLenovoLegionY530-15ICH: dmi.product.family: Legion Y530-15ICH dmi.product.name: 81FV dmi.product.sku: LENOVO_MT_81FV_BU_idea_FM_Legion Y530-15ICH dmi.product.version: Lenovo Legion Y530-15ICH dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879575/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880076] Re: ubuntu 20.4 - retransmitts with r8169
** Tags added: hwe-networking-ethernet -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1880076 Title: ubuntu 20.4 - retransmitts with r8169 Status in linux package in Ubuntu: Confirmed Bug description: Hi, i run some network-tests (iperf3) and noticed massive retransmitts in ubuntu 20.4 with kernel 5.4.0-29. I'm using module r8169 for network- adapter 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) if i boot my ubuntu 18.4 and did same iperf-test (same hardware, same network configuration, other client is not rebooted) i have not these retransmitts. root@bpi-r2:~# iperf3 -c 192.168.0.21 Connecting to host 192.168.0.21, port 5201 [ 5] local 192.168.0.11 port 35702 connected to 192.168.0.21 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 14.2 MBytes 119 Mbits/sec 337 14.1 KBytes [ 5] 1.00-2.00 sec 14.9 MBytes 125 Mbits/sec 331 14.1 KBytes [ 5] 2.00-3.00 sec 15.1 MBytes 126 Mbits/sec 296 19.8 KBytes [ 5] 3.00-4.00 sec 14.7 MBytes 124 Mbits/sec 314 14.1 KBytes [ 5] 4.00-5.00 sec 12.8 MBytes 107 Mbits/sec 259 14.1 KBytes [ 5] 5.00-6.01 sec 67.4 MBytes 560 Mbits/sec 137362 KBytes [ 5] 6.01-7.00 sec 111 MBytes 940 Mbits/sec0366 KBytes [ 5] 7.00-8.00 sec 112 MBytes 941 Mbits/sec0409 KBytes [ 5] 8.00-9.00 sec 112 MBytes 940 Mbits/sec0421 KBytes [ 5] 9.00-10.00 sec 112 MBytes 936 Mbits/sec0426 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 586 MBytes 491 Mbits/sec 1674 sender [ 5] 0.00-10.01 sec 585 MBytes 491 Mbits/sec receiver iperf Done. 2: enp3s0: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether e4:b9:7a:f7:c4:8b brd ff:ff:ff:ff:ff:ff inet 192.168.0.21/24 brd 192.168.0.255 scope global dynamic noprefixroute enp3s0 valid_lft 171856sec preferred_lft 171856sec inet6 fe80::781a:829f:5030:ad6a/64 scope link noprefixroute valid_lft forever preferred_lft forever $ ethtool -S enp3s0 NIC statistics: tx_packets: 571053 rx_packets: 1184934 tx_errors: 0 rx_errors: 0 rx_missed: 1919 <<< align_errors: 0 tx_single_collisions: 0 tx_multi_collisions: 0 unicast: 1184926 broadcast: 6 multicast: 2 tx_aborted: 0 tx_underrun: 0 2: enp3s0: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether e4:b9:7a:f7:c4:8b brd ff:ff:ff:ff:ff:ff RX: bytes packets errors dropped overrun mcast 1785166133 1184970 0 0 0 2 TX: bytes packets errors dropped carrier collsns 39395440 570500 0 0 0 0 on the other side i see dropped packets, maybe flowcontrol-related? ethtool reports "Link partner advertised pause frame use: Symmetric" but maybe flowcontrol is not working... also driver reports flowcontrol is enabled... $ dmesg | grep r8169 [0.939358] libphy: r8169: probed [0.939491] r8169 :03:00.0 eth0: RTL8168h/8111h, e4:b9:7a:f7:c4:8b, XID 541, IRQ 128 [0.939492] r8169 :03:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko] [0.986853] r8169 :03:00.0 enp3s0: renamed from eth0 [3.478981] Generic FE-GE Realtek PHY r8169-300:00: attached PHY driver [Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-300:00, irq=IGNORE) [3.591124] r8169 :03:00.0 enp3s0: Link is Down [7.171198] r8169 :03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control rx/tx ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: frank 1427 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME-Flashback:GNOME Date: Fri May 22 06:49:34 2020 InstallationDate: Installed on 2020-04-27 (24 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Del
[Kernel-packages] [Bug 1879633] Re: Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable
** Tags added: hwe-needs-driver -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879633 Title: Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Incomplete Status in linux source package in Groovy: Incomplete Bug description: TBD. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1879633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879752] Re: test_bpf of ubuntu_kernel_selftests.net ADT test failure with linux 4.4.0-180.210
** Description changed: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux/20200520_161352_2051b@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20200520_160450_cdd7c@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux/20200520_152728_5aa07@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/linux/20200520_151052_5aa07@/log.gz The test_bpf testcase what it does is only loading the test_bpf module, which reports the following error: - May 20 16:57:21 autopkgtest kernel: [ 88.143826] test_bpf: #250 BPF_MAXINSNS: ld_abs+vlan_push/pop + May 20 16:57:21 autopkgtest kernel: [ 88.143826] test_bpf: #250 BPF_MAXINSNS: ld_abs+vlan_push/pop jited:1 ret -12 != 3055 FAIL (1 times) This is cased by upstream commit 636c2628086e "net: skbuff: Remove errornous length validation in skb_vlan_pop()" which we applied from stable upstream v4.4.223. The fix is upstream commit 0d906b1e8d40 "bpf, test: fix ld_abs + vlan - push/pop stress test". + push/pop stress test" applied to v4.9. ** Description changed: - Testing failed on: - amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux/20200520_161352_2051b@/log.gz - i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20200520_160450_cdd7c@/log.gz - ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux/20200520_152728_5aa07@/log.gz - s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/linux/20200520_151052_5aa07@/log.gz + [Impact] + Testcase test_bpf of ubuntu_kernel_selftests.net regressed on xenial/linux 4.4.0-180.210. - The test_bpf testcase what it does is only loading the test_bpf module, + What the test_bpf testcase does is only loading the test_bpf module, which reports the following error: May 20 16:57:21 autopkgtest kernel: [ 88.143826] test_bpf: #250 BPF_MAXINSNS: ld_abs+vlan_push/pop jited:1 ret -12 != 3055 FAIL (1 times) This is cased by upstream commit 636c2628086e "net: skbuff: Remove errornous length validation in skb_vlan_pop()" which we applied from stable upstream v4.4.223. - The fix is upstream commit 0d906b1e8d40 "bpf, test: fix ld_abs + vlan - push/pop stress test" applied to v4.9. + [Fix] + The fix is upstream commit 0d906b1e8d40 "bpf, test: fix ld_abs + vlan push/pop stress test" from v4.9 which can cherry-picked to xenial. + + [Test case] + Load the test_bpf module, it should return no errors. + + [Regression potential] + Low. The fix changes only a bpf test module and was tested to fix the reported issue. + + + Original bug report: + - + Testing failed on: + amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux/20200520_161352_2051b@/log.gz + i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20200520_160450_cdd7c@/log.gz + ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux/20200520_152728_5aa07@/log.gz + s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/linux/20200520_151052_5aa07@/log.gz ** Changed in: linux (Ubuntu Xenial) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879752 Title: test_bpf of ubuntu_kernel_selftests.net ADT test failure with linux 4.4.0-180.210 Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: [Impact] Testcase test_bpf of ubuntu_kernel_selftests.net regressed on xenial/linux 4.4.0-180.210. What the test_bpf testcase does is only loading the test_bpf module, which reports the following error: May 20 16:57:21 autopkgtest kernel: [ 88.143826] test_bpf: #250 BPF_MAXINSNS: ld_abs+vlan_push/pop jited:1 ret -12 != 3055 FAIL (1 times) This is cased by upstream commit 636c2628086e "net: skbuff: Remove errornous length validation in skb_vlan_pop()" which we applied from stable
[Kernel-packages] [Bug 1879752] Re: test_bpf of ubuntu_kernel_selftests.net ADT test failure with linux 4.4.0-180.210
SRU request: https://lists.ubuntu.com/archives/kernel-team/2020-May/110146.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879752 Title: test_bpf of ubuntu_kernel_selftests.net ADT test failure with linux 4.4.0-180.210 Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: [Impact] Testcase test_bpf of ubuntu_kernel_selftests.net regressed on xenial/linux 4.4.0-180.210. What the test_bpf testcase does is only loading the test_bpf module, which reports the following error: May 20 16:57:21 autopkgtest kernel: [ 88.143826] test_bpf: #250 BPF_MAXINSNS: ld_abs+vlan_push/pop jited:1 ret -12 != 3055 FAIL (1 times) This is cased by upstream commit 636c2628086e "net: skbuff: Remove errornous length validation in skb_vlan_pop()" which we applied from stable upstream v4.4.223. [Fix] The fix is upstream commit 0d906b1e8d40 "bpf, test: fix ld_abs + vlan push/pop stress test" from v4.9 which can cherry-picked to xenial. [Test case] Load the test_bpf module, it should return no errors. [Regression potential] Low. The fix changes only a bpf test module and was tested to fix the reported issue. Original bug report: - Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux/20200520_161352_2051b@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20200520_160450_cdd7c@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux/20200520_152728_5aa07@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/linux/20200520_151052_5aa07@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1879752/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875252] Re: Ubuntu 20.04 LTS update causing no sound coming from built-in speakers
@Alexander (klimat-88) The fix is for HDA Intel soundcard built-in audio. Couldn't find what is your soundcard from your bug report. Wait for the coders to respond to your bug report. As far as I know, you may try undoing all these: "options snd-hda-intel dmic_detect=0" to /etc/modprobe.d/alsa-base.con, add "blacklist snd_soc_skl" And then apply the patch. Or uninstall and reinstall PulseAudio. Then enable "Pre-released updates (focal-proposed)" under the tab 'Developer Options' in Software & Updates. Then update the cache before closing Software & Updates. Open Software Updater, fetch and apply updates. Reboot. Try if the audio works now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875252 Title: Ubuntu 20.04 LTS update causing no sound coming from built-in speakers Status in linux package in Ubuntu: Confirmed Bug description: After updating to Ubuntu 20.04 LTS, the only way of hearing audio is through headphones. The sound settings tab doesn't even show any other output option other than "Dummy output" . I have already checked other versions and everything works perfectly when I downgrade to Ubuntu 19.10, so I think this is a version related bug. Just to reiterate my laptop is a DELL Inspiron 14 3420.The sound card showing in alsamixer window is HDA Intel PCH, and the chip is Cirrus Logic CS4213. I have looked up solutions online for 2 days and none has worked. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: george 1499 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 26 19:04:06 2020 InstallationDate: Installed on 2020-04-26 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Inspiron 3420 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=ec9a2552-c1da-44bd-9967-5be8bc6da075 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-26 (0 days ago) dmi.bios.date: 09/28/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 04XGDT dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA05:bd09/28/2012:svnDellInc.:pnInspiron3420:pvrNotSpecified:rvnDellInc.:rn04XGDT:rvrA05:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3420 dmi.product.sku: To be filled by O.E.M. dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875252] Re: Ubuntu 20.04 LTS update causing no sound coming from built-in speakers
For the rest of the affected souls here: The patch that I mentioned above has now been incorporated into the Focal proposed updates. To fetch it to your system before it is released in the stable channel, do the following: Enable "Pre-released updates (focal-proposed)" under the tab 'Developer Options' in Software & Updates. Then update the cache before closing Software & Updates. Open Software Updater, fetch, and apply the PulseAudio/dependencies updates (pulseaudio 1:13.99.1-1ubuntu3.3). Reboot. The audio should be working fine now. Voila. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875252 Title: Ubuntu 20.04 LTS update causing no sound coming from built-in speakers Status in linux package in Ubuntu: Confirmed Bug description: After updating to Ubuntu 20.04 LTS, the only way of hearing audio is through headphones. The sound settings tab doesn't even show any other output option other than "Dummy output" . I have already checked other versions and everything works perfectly when I downgrade to Ubuntu 19.10, so I think this is a version related bug. Just to reiterate my laptop is a DELL Inspiron 14 3420.The sound card showing in alsamixer window is HDA Intel PCH, and the chip is Cirrus Logic CS4213. I have looked up solutions online for 2 days and none has worked. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: george 1499 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 26 19:04:06 2020 InstallationDate: Installed on 2020-04-26 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Inspiron 3420 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=ec9a2552-c1da-44bd-9967-5be8bc6da075 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-26 (0 days ago) dmi.bios.date: 09/28/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 04XGDT dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA05:bd09/28/2012:svnDellInc.:pnInspiron3420:pvrNotSpecified:rvnDellInc.:rn04XGDT:rvrA05:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3420 dmi.product.sku: To be filled by O.E.M. dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879489] Re: After updating to the kernel 4.15.0-101-generic dmessg contains an error message
What's the last kernel version doesn't have this issue? ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879489 Title: After updating to the kernel 4.15.0-101-generic dmessg contains an error message Status in linux package in Ubuntu: Incomplete Bug description: System:Kernel: 4.15.0-101-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin dm: LightDM Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic Machine: Type: Laptop System: Dell product: Inspiron 13-5378 Network: Device-1: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter vendor: Dell driver: ath10k_pci v: kernel port: f040 bus ID: 01:00.0 chip ID: 168c:003e IF: wlp1s0 state: up mac: Device-2: Atheros type: USB driver: btusb bus ID: 1-6:3 chip ID: 0cf3:e007 [ 2046.326644] WARNING: CPU: 1 PID: 16 at /build/linux-sgQT9w/linux-4.15.0/net/core/dev.c:5675 net_rx_action+0x2cb/0x3a0 [ 2046.326647] Modules linked in: ccm rfcomm arc4 bnep snd_hda_codec_hdmi snd_hda_codec_realtek pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp dell_laptop snd_soc_sst_ipc dell_smm_hwmon snd_soc_acpi snd_soc_core snd_hda_codec_generic snd_compress ac97_bus btusb snd_pcm_dmaengine btrtl btbcm btintel snd_hda_intel bluetooth snd_hda_codec snd_hda_core ecdh_generic snd_hwdep hid_multitouch intel_rapl snd_pcm x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel nls_iso8859_1 kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_seq_midi pcbc snd_seq_midi_event ath10k_pci ath10k_core snd_rawmidi aesni_intel ath aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf snd_seq mac80211 snd_seq_device snd_timer [ 2046.326696] cfg80211 dell_wmi dell_smbios dcdbas joydev input_leds dell_wmi_descriptor wmi_bmof serio_raw snd soundcore shpchp mei_me idma64 virt_dma mei intel_lpss_pci intel_lpss hid_sensor_rotation hid_sensor_incl_3d hid_sensor_magn_3d hid_sensor_accel_3d hid_sensor_gyro_3d hid_sensor_trigger industrialio_triggered_buffer kfifo_buf hid_sensor_iio_common industrialio intel_pch_thermal nf_log_ipv6 processor_thermal_device intel_soc_dts_iosf xt_hl ip6t_rt intel_vbtn int3403_thermal soc_button_array intel_hid sparse_keymap nf_conntrack_ipv6 nf_defrag_ipv6 ip6t_REJECT int3402_thermal nf_reject_ipv6 int340x_thermal_zone nf_log_ipv4 nf_log_common xt_LOG acpi_pad xt_limit int3400_thermal acpi_thermal_rel mac_hid xt_tcpudp xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ipt_REJECT nf_reject_ipv4 [ 2046.326735] ip6table_filter ip6_tables sch_fq_codel nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat parport_pc nf_conntrack_ftp nf_conntrack libcrc32c ppdev iptable_filter lp parport ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq dm_mirror dm_region_hash dm_log hid_sensor_custom hid_sensor_hub intel_ishtp_hid hid_generic usbhid psmouse i915 i2c_algo_bit drm_kms_helper ahci syscopyarea sysfillrect libahci sysimgblt fb_sys_fops intel_ish_ipc intel_ishtp drm i2c_hid wmi hid video pinctrl_sunrisepoint [ 2046.326773] CPU: 1 PID: 16 Comm: ksoftirqd/1 Tainted: G O 4.15.0-101-generic #102-Ubuntu [ 2046.326775] Hardware name: Dell Inc. Inspiron 13-5378/05C3PP, BIOS 1.21.1 08/25/2017 [ 2046.326782] RIP: 0010:net_rx_action+0x2cb/0x3a0 [ 2046.326784] RSP: 0018:b6c781977de8 EFLAGS: 00010297 [ 2046.326787] RAX: 0044 RBX: 0040 RCX: 8d867a621e68 [ 2046.326789] RDX: 8d837f806000 RSI: fe01 RDI: c0c3b820 [ 2046.326791] RBP: b6c781977e58 R08: 0002 R09: [ 2046.326793] R10: 26b4 R11: 0001 R12: [ 2046.326794] R13: R14: 0003 R15: 8d867a627b60 [ 2046.326797] FS: () GS:8d869048() knlGS: [ 2046.326799] CS: 0010 DS: ES: CR0: 80050033 [ 2046.326802] CR2: 0e6fcca63008 CR3: 00034ae0a001 CR4: 003606e0 [ 2046.326803] Call Trace: [ 2046.326812] ? __switch_to_asm+0x41/0x70 [ 2046.326819] __do_softirq+0xe4/0x2d4 [ 2046.326826] run_ksoftirqd+0x22/0x60 [ 2046.326832] smpboot_thread_fn+0xfc/0x170 [ 2046.326836] kthread+0x121/0x140 [ 2046.326840] ? sort_range+0x30/0x30 [ 2046.326844] ? kthread_create_worker_on_cpu+0x70/0x70 [ 2046.326849] ret_from_fork+0x35/0x40 [ 2046.326851] Code: 24 08 49 83 c4 18 89 d9 44 89 f2 4c 89 fe e8 bd 1f 39 00 4d 8b 14 24 4d 85 d2 75 e1 4c 8b 65 90 44 89 f0 39 c3 0f 8d 85 fe ff ff <0f> 0b 39 c3 0f 8f 83 fe ff ff 49 8b 47 10 a8 04 75 74 49 83 7f [ 2046.326890] ---[ end trace e7d0683
[Kernel-packages] [Bug 1878899] Re: Call trace from __video_do_ioctl
Can you please try linux-generic kernel instead of linux-lowlatency? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878899 Title: Call trace from __video_do_ioctl Status in linux package in Ubuntu: Incomplete Bug description: [92420.303133] [ cut here ] [92420.303141] WARNING: CPU: 2 PID: 259541 at drivers/media/v4l2-core/v4l2-ioctl.c:1069 v4l_querycap+0x8f/0xa0 [videodev] [92420.303141] Modules linked in: btrfs xor zstd_compress raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs gspca_zc3xx joydev snd_seq_dummy iptable_mangle xt_CHECKSUM iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c xt_tcpudp bridge stp llc iptable_filter bpfilter v4l2loopback(OE) binfmt_misc nls_iso8859_1 uvcvideo gspca_vc032x gspca_main videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev snd_usb_audio snd_usbmidi_lib mc snd_seq_midi snd_seq_midi_event snd_rawmidi edac_mce_amd kvm_amd ccp snd_hda_codec_realtek snd_seq snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel kvm snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep snd_seq_device snd_pcm input_leds serio_raw k10temp fam15h_power snd_timer snd soundcore mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 uas usb_storage dm_crypt amdgpu amd_iommu_v2 gpu_sched hid_generic usbhid hid crct10dif_pclmul crc32_pclmul [92420.303167] ghash_clmulni_intel radeon i2c_algo_bit ttm aesni_intel drm_kms_helper crypto_simd syscopyarea cryptd sysfillrect sysimgblt glue_helper fb_sys_fops ahci libahci i2c_piix4 drm r8169 realtek video [92420.303174] CPU: 2 PID: 259541 Comm: teams Tainted: GW OE 5.4.0-29-lowlatency #33-Ubuntu [92420.303175] Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./G1.Sniper A88X-CF, BIOS F7 01/08/2014 [92420.303182] RIP: 0010:v4l_querycap+0x8f/0xa0 [videodev] [92420.303183] Code: 00 00 80 48 b9 00 00 20 00 00 00 20 00 48 0b 4b 54 21 d6 39 f2 75 13 48 89 4b 54 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 0b eb d0 <0f> 0b 48 89 4b 54 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 1f 44 00 00 [92420.303184] RSP: 0018:b4aa44dd7c78 EFLAGS: 00010202 [92420.303186] RAX: RBX: b4aa44dd7d88 RCX: 8520800185208001 [92420.303187] RDX: 85008003 RSI: 85008001 RDI: [92420.303188] RBP: b4aa44dd7ca0 R08: R09: 000a [92420.303188] R10: R11: R12: 994f4e421000 [92420.303189] R13: 994f4de6bf00 R14: 994f4c191940 R15: c0f2e360 [92420.303191] FS: 7f47f2ffd700() GS:994f5fb0() knlGS: [92420.303192] CS: 0010 DS: ES: CR0: 80050033 [92420.303193] CR2: 7f482c0e1000 CR3: 0003d0084000 CR4: 000406e0 [92420.303194] Call Trace: [92420.303201] __video_do_ioctl+0x1a7/0x410 [videodev] [92420.303204] ? default_send_IPI_single+0x20/0x40 [92420.303206] ? resched_curr+0x62/0xe0 [92420.303213] video_usercopy+0x2ad/0x690 [videodev] [92420.303220] ? v4l_s_fmt+0x670/0x670 [videodev] [92420.303224] ? wake_up_q+0x40/0x70 [92420.303230] video_ioctl2+0x15/0x20 [videodev] [92420.303237] v4l2_ioctl+0x4c/0x60 [videodev] [92420.303238] do_vfs_ioctl+0x405/0x660 [92420.303240] ? __fget+0x77/0xa0 [92420.303242] ksys_ioctl+0x67/0x90 [92420.303244] __x64_sys_ioctl+0x1a/0x20 [92420.303246] do_syscall_64+0x57/0x190 [92420.303248] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [92420.303249] RIP: 0033:0x7f489773737b [92420.303251] Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48 [92420.303252] RSP: 002b:7f47f2ff77e8 EFLAGS: 0246 ORIG_RAX: 0010 [92420.303254] RAX: ffda RBX: 7f4824026900 RCX: 7f489773737b [92420.303255] RDX: 7f47f2ff78b0 RSI: 80685600 RDI: 0046 [92420.303256] RBP: 80685600 R08: R09: 5645ec03ee68 [92420.303257] R10: 0048 R11: 0246 R12: 0046 [92420.303258] R13: 7f47f2ff78b0 R14: 0015 R15: 7f485b666039 [92420.303260] ---[ end trace 6e9a5041142fdaab ]--- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-lowlatency 5.4.0.29.34 ProcVersionSignature: Ubuntu 5.4.0-29.33-lowlatency 5.4.30 Uname: Linux 5.4.0-29-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 15 12:52:50 2020 HibernationDevice: RESUME=UUID=2ac5f511-9e86-402d-b41b-405dabdb7861 InstallationDate: Installed on 2014-04-14 ( days ago) Installati
[Kernel-packages] [Bug 1866852] Re: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor
** Tags added: id-5ec69e0b06c8b66fbed30567 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866852 Title: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor Status in grub2 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Status in grub2 source package in Focal: Confirmed Status in linux source package in Focal: Invalid Status in grub2 source package in Groovy: Confirmed Status in linux source package in Groovy: Invalid Bug description: I'm running focal devel and the latest kernel (see proc version below) Linux version 5.4.0-18-generic (buildd@lgw01-amd64-034) (gcc version 9.2.1 20200306 (Ubuntu 9.2.1-31ubuntu3)) #22-Ubuntu SMP Sat Mar 7 18:13:06 UTC 2020 Dock Monitor is supported very well with multiple usb devices plugged on the monitor. However on reboot I face a black screen with no ability to enter my FDE password. Both my Laptop screen and the attached usb-c display nothing I have to hard power off and reboot without the USB-C monitor plugged in. Otherwise A reboot cycle with the usb-c unplugged works perfectly. Also I tried to run ubuntu-bug linux or ubuntu-bug linux-image-generic without success. I would be happy to provide much more debugging information. I will attach then to the launchpad Bug # --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mclemenceau 2988 F pulseaudio /dev/snd/controlC0: mclemenceau 2988 F pulseaudio /dev/snd/controlC1: mclemenceau 2988 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-05 (64 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP HP Spectre x360 Convertible 13-ae0xx NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-18-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.186 Tags: focal Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-01-23 (47 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/14/2018 dmi.bios.vendor: AMI dmi.bios.version: F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83B9 dmi.board.vendor: HP dmi.board.version: 56.41 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.21:bd06/14/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.41:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-ae0xx dmi.product.sku: 2TV18AS#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1866852/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879017] Re: dd caused systemd-udevd call trace
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7-rc6/ Particularly, https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b849dd84b6ccfe32622988b79b7b073861fcf9f7 ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879017 Title: dd caused systemd-udevd call trace Status in linux package in Ubuntu: Incomplete Bug description: Using dd to copy an image onto sdcard seems to cause a kernel stack trace. dd seems to hang. [ 3747.220647] INFO: task systemd-udevd:2451 blocked for more than 483 seconds. [ 3747.220652] Tainted: P IOE 5.4.0-29-generic #33-Ubuntu [ 3747.220654] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3747.220656] systemd-udevd D0 2451 1 0x4124 [ 3747.220660] Call Trace: [ 3747.220670] __schedule+0x2e3/0x740 [ 3747.220673] schedule+0x42/0xb0 [ 3747.220675] schedule_preempt_disabled+0xe/0x10 [ 3747.220678] __mutex_lock.isra.0+0x182/0x4f0 [ 3747.220683] ? exact_lock+0x11/0x20 [ 3747.220685] __mutex_lock_slowpath+0x13/0x20 [ 3747.220687] mutex_lock+0x2e/0x40 [ 3747.220692] __blkdev_get+0x78/0x550 [ 3747.220694] blkdev_get+0x3d/0x140 [ 3747.220697] ? blkdev_get_by_dev+0x50/0x50 [ 3747.220699] blkdev_open+0x8f/0xa0 [ 3747.220704] do_dentry_open+0x143/0x3a0 [ 3747.220706] vfs_open+0x2d/0x30 [ 3747.220710] do_last+0x194/0x900 [ 3747.220713] path_openat+0x8d/0x290 [ 3747.220716] do_filp_open+0x91/0x100 [ 3747.220720] ? __alloc_fd+0x46/0x150 [ 3747.220722] do_sys_open+0x17e/0x290 [ 3747.220724] __x64_sys_openat+0x20/0x30 [ 3747.220729] do_syscall_64+0x57/0x190 [ 3747.220735] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 3747.220738] RIP: 0033:0x7f18e48a1d1b [ 3747.220745] Code: Bad RIP value. [ 3747.220746] RSP: 002b:7ffd19e936a0 EFLAGS: 0246 ORIG_RAX: 0101 [ 3747.220748] RAX: ffda RBX: 7ffd19e937b0 RCX: 7f18e48a1d1b [ 3747.220749] RDX: 000a0800 RSI: 558d7f09f470 RDI: ff9c [ 3747.220750] RBP: 558d7f09f470 R08: 558d7d4740c0 R09: [ 3747.220751] R10: R11: 0246 R12: 000a0800 [ 3747.220752] R13: 558d7f0b2920 R14: 7ffd19e93778 R15: 0001 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: js11209 F pulseaudio /dev/snd/controlC1: js11209 F pulseaudio /dev/snd/controlC0: js11209 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Fri May 15 22:44:18 2020 InstallationDate: Installed on 2020-02-02 (103 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) MachineType: Dell Inc. Precision WorkStation T7500 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=93fc02c6-baa4-4282-96d7-ea5ad53b0c78 ro ipv6.disable=1 elevator=deadline splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A18 dmi.board.name: 0D881F dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA18:bd10/15/2018:svnDellInc.:pnPrecisionWorkStationT7500:pvr:rvnDellInc.:rn0D881F:rvrA05:cvnDellInc.:ct7:cvr: dmi.product.name: Precision WorkStation T7500 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878919] Re: kworker/0:1+kacpid uses 100% of one CPU core
Did this issue happen to 16.04.1? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878919 Title: kworker/0:1+kacpid uses 100% of one CPU core Status in linux package in Ubuntu: Incomplete Bug description: At some point, kworker/0:1+kacpid starts using 100% of one CPU's core; this can be seen in the top command. I captured some performance data via the following command: $ perf record -g -a sleep 10 Then, perf report gives the following: Samples: 75K of event 'cycles', Event count (approx.): 44710762967 Children Self Command Shared Object Symbol + 65,46% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] ret_from_fork + 65,46% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] kthread + 65,46% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] worker_thread + 65,44% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] process_one_work + 65,44% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] acpi_os_execute_deferred + 65,33% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ev_asynch_execute_gpe_method + 65,32% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ns_evaluate + 65,26% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ps_execute_method + 65,16% 0,06% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ps_parse_aml + 61,00% 0,94% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ps_parse_loop + 37,83% 0,75% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ds_exec_end_op + 18,33% 0,04% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ds_evaluate_name_path + 16,12% 0,23% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ns_lookup + 15,79% 0,20% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ns_search_and_enter + 15,23%14,99% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ns_search_one_scope + 14,38% 0,00% swapper [kernel.kallsyms] [k] secondary_startup_64 + 14,38% 0,02% swapper [kernel.kallsyms] [k] cpu_startup_entry + 14,31% 0,12% swapper [kernel.kallsyms] [k] do_idle + 13,79% 0,00% swapper [kernel.kallsyms] [k] start_secondary + 12,92% 0,03% swapper [kernel.kallsyms] [k] call_cpuidle + 12,89% 0,00% swapper [kernel.kallsyms] [k] cpuidle_enter + 12,85% 0,05% swapper [kernel.kallsyms] [k] cpuidle_enter_state + 12,35% 2,15% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ut_update_object_reference + 12,05% 0,28% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_resolve_to_value + 10,40% 0,04% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_resolve_node_to_value +9,90% 0,44% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ds_create_operand +9,50% 0,05% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_read_data_from_field +9,39% 0,06% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_field_datum_io +9,26% 0,12% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_access_region +9,23% 0,08% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ps_get_next_namepath +9,15% 1,28% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ut_update_ref_count.part.0 +9,01% 0,08% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ev_address_space_dispatch +8,96% 0,14% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_extract_from_field +8,78% 7,70% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_system_memory_space_handler +7,81% 0,22% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ut_remove_reference +6,63% 6,43% swapper [kernel.kallsyms] [k] intel_idle +5,31% 0,68% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ps_create_op +5,12% 0,08% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ut_add_reference +4,89% 0,07% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ds_delete_result_if_not_used +4,71% 0,09% kworker/0:1+kac [kernel.kallsyms]
[Kernel-packages] [Bug 1878919] Re: kworker/0:1+kacpid uses 100% of one CPU core
Disable misbehaved ACPI GPE as a temporary workaround: https://unix.stackexchange.com/questions/242013/disable-gpe-acpi-interrupts-on-boot ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878919 Title: kworker/0:1+kacpid uses 100% of one CPU core Status in linux package in Ubuntu: Incomplete Bug description: At some point, kworker/0:1+kacpid starts using 100% of one CPU's core; this can be seen in the top command. I captured some performance data via the following command: $ perf record -g -a sleep 10 Then, perf report gives the following: Samples: 75K of event 'cycles', Event count (approx.): 44710762967 Children Self Command Shared Object Symbol + 65,46% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] ret_from_fork + 65,46% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] kthread + 65,46% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] worker_thread + 65,44% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] process_one_work + 65,44% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] acpi_os_execute_deferred + 65,33% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ev_asynch_execute_gpe_method + 65,32% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ns_evaluate + 65,26% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ps_execute_method + 65,16% 0,06% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ps_parse_aml + 61,00% 0,94% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ps_parse_loop + 37,83% 0,75% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ds_exec_end_op + 18,33% 0,04% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ds_evaluate_name_path + 16,12% 0,23% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ns_lookup + 15,79% 0,20% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ns_search_and_enter + 15,23%14,99% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ns_search_one_scope + 14,38% 0,00% swapper [kernel.kallsyms] [k] secondary_startup_64 + 14,38% 0,02% swapper [kernel.kallsyms] [k] cpu_startup_entry + 14,31% 0,12% swapper [kernel.kallsyms] [k] do_idle + 13,79% 0,00% swapper [kernel.kallsyms] [k] start_secondary + 12,92% 0,03% swapper [kernel.kallsyms] [k] call_cpuidle + 12,89% 0,00% swapper [kernel.kallsyms] [k] cpuidle_enter + 12,85% 0,05% swapper [kernel.kallsyms] [k] cpuidle_enter_state + 12,35% 2,15% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ut_update_object_reference + 12,05% 0,28% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_resolve_to_value + 10,40% 0,04% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_resolve_node_to_value +9,90% 0,44% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ds_create_operand +9,50% 0,05% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_read_data_from_field +9,39% 0,06% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_field_datum_io +9,26% 0,12% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_access_region +9,23% 0,08% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ps_get_next_namepath +9,15% 1,28% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ut_update_ref_count.part.0 +9,01% 0,08% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ev_address_space_dispatch +8,96% 0,14% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_extract_from_field +8,78% 7,70% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_system_memory_space_handler +7,81% 0,22% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ut_remove_reference +6,63% 6,43% swapper [kernel.kallsyms] [k] intel_idle +5,31% 0,68% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ps_create_op +5,12% 0,08% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ut_add_reference +
[Kernel-packages] [Bug 1878918] Re: Button power don’t shutdown
Did it happen under 19.10? ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878918 Title: Button power don’t shutdown Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 20.04 LTS Release: 20.04 I realized that since I updated the system to version 20.04 it is not responding when I press the shutdown button on my notebook, even though in the power management in the settings it is to shut down when I press it. When I put it to suspend, he responds, but when I put it off he does nothing ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: neto 1092 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri May 15 10:19:38 2020 InstallationDate: Installed on 2020-02-28 (76 days ago) InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C/532U3C ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=7949306b-901a-4602-8b3f-ce5078d80526 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-09 (5 days ago) dmi.bios.date: 07/22/2015 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P13ABH dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP530U3C-AD5BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP13ABH:bd07/22/2015:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C/532U3C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP530U3C-AD5BR:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 530U3C/530U4C/532U3C dmi.product.sku: System SKUNumber dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879690] Re: Docker registry doesn't stay up and keeps restarting
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- eoan' to 'verification-done-eoan'. If the problem still exists, change the tag 'verification-needed-eoan' to 'verification-failed-eoan'. 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-eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879690 Title: Docker registry doesn't stay up and keeps restarting Status in linux package in Ubuntu: Incomplete Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: [Impact] The change applied for bug 1857257 and its followup fix bug 1876645, which were released on focal and eoan -updates, introduced a regression on overlayfs, breaking docker snap. [Test case] See original bug report. [Fix] While we don't have a final fix the solution for now is to revert the following commits: UBUNTU: SAUCE: overlayfs: fix shitfs special-casing UBUNTU: SAUCE: overlayfs: use shiftfs hacks only with shiftfs as underlay [Regression potential] Low. Reverting these two commits will introduce back the issue reported on bug 1857257, but will fix the other use cases which was broken by the latest release. Original bug report. --- Tested kernels: Focal 5.4.0-31.35 Eoan 5.3.0-53.47 To reproduce: 1) Spin up a cloud image 2) snap install docker 3) auth_folder=/var/snap/docker/common/auth 4) mkdir -p $auth_folder 5) docker run --entrypoint htpasswd registry:2 -Bbn user passwd > $auth_folder/htpasswd 6) docker run -d -p 5000:5000 --restart=always --name registry \ -v $auth_folder:/auth \ -e "REGISTRY_AUTH=htpasswd" \ -e "REGISTRY_AUTH_HTPASSWD_REALM=Registry Realm" \ -e REGISTRY_AUTH_HTPASSWD_PATH=/auth/htpasswd \ registry:2 On a good kernel 'docker ps' shows something like: # docker ps CONTAINER IDIMAGE COMMAND CREATED STATUS PORTSNAMES a346b65b4509registry:2 "/entrypoint.sh /etc…" 14 seconds ago Up 12 seconds 0.0.0.0:5000->5000/tcp registry On a bad kernel: docker ps CONTAINER IDIMAGE COMMAND CREATED STATUSPORTS NAMES 0322374f1b1dregistry:2 "/entrypoint.sh /etc…" 5 seconds ago Restarting (2) 1 second ago registry Note status 'Restarting' on the bad kernel. This seems to be introduce by any of the following commits: b3bdda24f1bc UBUNTU: SAUCE: overlayfs: fix shitfs special-casing 6f18a8434050 UBUNTU: SAUCE: overlayfs: use shiftfs hacks only with shiftfs as underlay 629edd70891c UBUNTU: SAUCE: shiftfs: record correct creator credentials cfaa482afb97 UBUNTU: SAUCE: shiftfs: fix dentry revalidation Kernels that don't have these commits seem fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879690/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878480] Re: Centrino Wireless-N 1000 [Condor Peak]
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7-rc6/ If latest kernel doesn't work then we need to do kernel bisection... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878480 Title: Centrino Wireless-N 1000 [Condor Peak] Status in linux package in Ubuntu: Incomplete Bug description: After upgrade to 20.04 my wireless starts to be very unstable, it goes from 65mbs to 1mbs. I need to reenable wirless ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic 5.4.0.29.34 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: miguel 2846 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 13 20:57:07 2020 HibernationDevice: RESUME=UUID=0f71c458-758c-439d-9dd0-b7ddcd620218 MachineType: Alienware M14xR1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=fcba8370-4563-4d59-8a53-f1a70ebb8e1d ro quiet splash nouveau.blacklist=1 nvidia-drm.modeset=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2011 dmi.bios.vendor: Alienware dmi.bios.version: A08 dmi.board.name: M14xR1 dmi.board.vendor: Alienware dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A08 dmi.modalias: dmi:bvnAlienware:bvrA08:bd12/24/2011:svnAlienware:pnM14xR1:pvrA08:rvnAlienware:rnM14xR1:rvrA08:cvnAlienware:ct8:cvrA08: dmi.product.family: 103C_5335KV dmi.product.name: M14xR1 dmi.product.sku: xxx123x#ABA dmi.product.version: A08 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878480/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878749] Re: Kernel bug when running btrfs balance
Hmm, could you please try 20.04? I wonder how you made rootfs Btrfs? ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878749 Title: Kernel bug when running btrfs balance Status in linux package in Ubuntu: Incomplete Bug description: syslog extract: May 15 00:38:28 rpi4 kernel: [ 1464.345380] kernel BUG at /build/linux-raspi2-5.3-5IVhed/linux-raspi2-5.3-5.3.0/fs/btrfs/relocation.c:4729! May 15 00:38:28 rpi4 kernel: [ 1464.355281] Internal error: Oops - BUG: 0 [#1] SMP May 15 00:38:28 rpi4 kernel: [ 1464.360141] Modules linked in: xt_nat iptable_nat dm_crypt nls_ascii algif_skcipher af_alg ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 xt_comment btsdio nf_log_ipv4 nf_log_common bluetooth bcm2835_v4l2(CE) xt_LOG ecdh_generic bcm2835_mmal_vchiq(CE) ecc vc_sm_cma(CE) xt_multiport v4l2_common xt_recent videobuf2_vmalloc videobuf2_memops brcmfmac videobuf2_v4l2 brcmutil videobuf2_common cfg80211 videodev xt_limit xt_tcpudp raspberrypi_hwmon mc xt_addrtype rpivid_mem spidev uio_pdrv_genirq uio xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 sch_fq_codel nf_defrag_ipv4 iptable_filter bpfilter iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear broadcom bcm_phy_lib hid_generic May 15 00:38:28 rpi4 kernel: [ 1464.360198] usbhid mdio_bcm_unimac crct10dif_ce sdhci_iproc genet gpio_regulator phy_generic fixed uas usb_storage aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 May 15 00:38:28 rpi4 kernel: [ 1464.464074] CPU: 0 PID: 8225 Comm: btrfs-balance Tainted: G C E 5.3.0-1023-raspi2 #25~18.04.1-Ubuntu May 15 00:38:28 rpi4 kernel: [ 1464.474482] Hardware name: Raspberry Pi 4 Model B Rev 1.2 (DT) May 15 00:38:28 rpi4 kernel: [ 1464.480395] pstate: 2045 (nzCv daif +PAN -UAO) May 15 00:38:28 rpi4 kernel: [ 1464.485330] pc : btrfs_reloc_cow_block+0x34c/0x3a0 [btrfs] May 15 00:38:28 rpi4 kernel: [ 1464.490928] lr : __btrfs_cow_block+0x368/0x600 [btrfs] May 15 00:38:28 rpi4 kernel: [ 1464.496133] sp : 13b437b0 May 15 00:38:28 rpi4 kernel: [ 1464.499487] x29: 13b437b0 x28: May 15 00:38:28 rpi4 kernel: [ 1464.504870] x27: 0001 x26: 0001 May 15 00:38:28 rpi4 kernel: [ 1464.510253] x25: 9c0ac32c4a80 x24: 9c0bb321c618 May 15 00:38:28 rpi4 kernel: [ 1464.515634] x23: 0001 x22: 9c0b63242a50 May 15 00:38:28 rpi4 kernel: [ 1464.521016] x21: 9c0b23e51ef0 x20: 9c0b4f111000 May 15 00:38:28 rpi4 kernel: [ 1464.526399] x19: 9c0b74bb5000 x18: May 15 00:38:28 rpi4 kernel: [ 1464.531780] x17: x16: 40af26f8be78 May 15 00:38:28 rpi4 kernel: [ 1464.537163] x15: x14: May 15 00:38:28 rpi4 kernel: [ 1464.542545] x13: x12: May 15 00:38:28 rpi4 kernel: [ 1464.547926] x11: x10: 9c0b10e83a40 May 15 00:38:28 rpi4 kernel: [ 1464.553308] x9 : 9c0aca004750 x8 : 40af2775b9e7 May 15 00:38:28 rpi4 kernel: [ 1464.558690] x7 : 9c0b578814e1 x6 : 9c0b578814e0 May 15 00:38:28 rpi4 kernel: [ 1464.564071] x5 : 9c0b552b59c0 x4 : 9c0b552b59c0 May 15 00:38:28 rpi4 kernel: [ 1464.569452] x3 : 9c0b63242a50 x2 : 00096be7 May 15 00:38:28 rpi4 kernel: [ 1464.574833] x1 : x0 : 012e979b4000 May 15 00:38:28 rpi4 kernel: [ 1464.580216] Call trace: May 15 00:38:28 rpi4 kernel: [ 1464.582735] btrfs_reloc_cow_block+0x34c/0x3a0 [btrfs] May 15 00:38:28 rpi4 kernel: [ 1464.587979] __btrfs_cow_block+0x368/0x600 [btrfs] May 15 00:38:28 rpi4 kernel: [ 1464.592869] btrfs_cow_block+0x100/0x218 [btrfs] May 15 00:38:28 rpi4 kernel: [ 1464.597583] btrfs_search_slot+0x560/0x930 [btrfs] May 15 00:38:28 rpi4 kernel: [ 1464.602475] do_relocation+0x408/0x5b8 [btrfs] May 15 00:38:28 rpi4 kernel: [ 1464.607014] relocate_tree_blocks+0x4f8/0x5c0 [btrfs] May 15 00:38:28 rpi4 kernel: [ 1464.612170] relocate_block_group+0x3dc/0x638 [btrfs] May 15 00:38:28 rpi4 kernel: [ 1464.617325] btrfs_relocate_block_group+0x18c/0x2d8 [btrfs] May 15 00:38:28 rpi4 kernel: [ 1464.623009] btrfs_relocate_chunk+0x48/0xe0 [btrfs] May 15 00:38:28 rpi4 kernel: [ 1464.627988] __btrfs_balance+0x864/0xa38 [btrfs] May 15 00:38:28 rpi4 kernel: [ 1464.632703] btrfs_balance+0x434/0x748 [btrfs] May 15 00:38:28 rpi4 kernel: [ 1464.637301] balance_kthread+0x38/0x70 [btrfs] May 15 00:38:28 rpi4
[Kernel-packages] [Bug 1880103] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1880103/+attachment/5375615/+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/1880103 Title: Awaking problem after suspend mode still happens Status in linux package in Ubuntu: Incomplete Bug description: 101 kernel seems to be better than 99, when the problem happened almost every time. Nevertheless, it happened again with 2+days uptime and suspending over night. Maybe it depends on my wireless keyboard? I tried Alt+SysRq reisub twice, but it didn't work. Mint Cinnamon 19.1, desktop. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0c: waldi 1668 F...m pulseaudio /dev/snd/controlC2: waldi 1668 F pulseaudio /dev/snd/controlC0: waldi 1668 F pulseaudio /dev/snd/controlC1: waldi 1668 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=018b3f92-7678-b1d9-8157-f8388f5198a2 InstallationDate: Installed on 2019-02-27 (449 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. enp6s0no wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=e74e78ea-7a9d-41a9-839b-e32c0343041f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-101-generic N/A linux-backports-modules-4.15.0-101-generic N/A linux-firmware 1.173.18 RfKill: Tags: tessa Uname: Linux 4.15.0-101-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 01/18/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX2 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.:bvr0501:bd01/18/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX2: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/1880103/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880103] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1880103/+attachment/5375613/+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/1880103 Title: Awaking problem after suspend mode still happens Status in linux package in Ubuntu: Incomplete Bug description: 101 kernel seems to be better than 99, when the problem happened almost every time. Nevertheless, it happened again with 2+days uptime and suspending over night. Maybe it depends on my wireless keyboard? I tried Alt+SysRq reisub twice, but it didn't work. Mint Cinnamon 19.1, desktop. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0c: waldi 1668 F...m pulseaudio /dev/snd/controlC2: waldi 1668 F pulseaudio /dev/snd/controlC0: waldi 1668 F pulseaudio /dev/snd/controlC1: waldi 1668 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=018b3f92-7678-b1d9-8157-f8388f5198a2 InstallationDate: Installed on 2019-02-27 (449 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. enp6s0no wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=e74e78ea-7a9d-41a9-839b-e32c0343041f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-101-generic N/A linux-backports-modules-4.15.0-101-generic N/A linux-firmware 1.173.18 RfKill: Tags: tessa Uname: Linux 4.15.0-101-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 01/18/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX2 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.:bvr0501:bd01/18/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX2: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/1880103/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880103] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1880103/+attachment/5375624/+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/1880103 Title: Awaking problem after suspend mode still happens Status in linux package in Ubuntu: Incomplete Bug description: 101 kernel seems to be better than 99, when the problem happened almost every time. Nevertheless, it happened again with 2+days uptime and suspending over night. Maybe it depends on my wireless keyboard? I tried Alt+SysRq reisub twice, but it didn't work. Mint Cinnamon 19.1, desktop. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0c: waldi 1668 F...m pulseaudio /dev/snd/controlC2: waldi 1668 F pulseaudio /dev/snd/controlC0: waldi 1668 F pulseaudio /dev/snd/controlC1: waldi 1668 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=018b3f92-7678-b1d9-8157-f8388f5198a2 InstallationDate: Installed on 2019-02-27 (449 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. enp6s0no wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=e74e78ea-7a9d-41a9-839b-e32c0343041f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-101-generic N/A linux-backports-modules-4.15.0-101-generic N/A linux-firmware 1.173.18 RfKill: Tags: tessa Uname: Linux 4.15.0-101-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 01/18/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX2 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.:bvr0501:bd01/18/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX2: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/1880103/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880103] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1880103/+attachment/5375618/+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/1880103 Title: Awaking problem after suspend mode still happens Status in linux package in Ubuntu: Incomplete Bug description: 101 kernel seems to be better than 99, when the problem happened almost every time. Nevertheless, it happened again with 2+days uptime and suspending over night. Maybe it depends on my wireless keyboard? I tried Alt+SysRq reisub twice, but it didn't work. Mint Cinnamon 19.1, desktop. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0c: waldi 1668 F...m pulseaudio /dev/snd/controlC2: waldi 1668 F pulseaudio /dev/snd/controlC0: waldi 1668 F pulseaudio /dev/snd/controlC1: waldi 1668 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=018b3f92-7678-b1d9-8157-f8388f5198a2 InstallationDate: Installed on 2019-02-27 (449 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. enp6s0no wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=e74e78ea-7a9d-41a9-839b-e32c0343041f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-101-generic N/A linux-backports-modules-4.15.0-101-generic N/A linux-firmware 1.173.18 RfKill: Tags: tessa Uname: Linux 4.15.0-101-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 01/18/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX2 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.:bvr0501:bd01/18/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX2: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/1880103/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877871] Re: [radeon] X windows hangs following upgrade from 18.04 to 20.04
https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/2020-05-20/ Download and install the following deb: linux-image-unsigned-5.7.0-994-generic_5.7.0-994.202005192206_amd64.deb linux-modules-5.7.0-994-generic_5.7.0-994.202005192206_amd64.deb -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877871 Title: [radeon] X windows hangs following upgrade from 18.04 to 20.04 Status in linux package in Ubuntu: Incomplete Bug description: Following an upgrade from 18.04 to 20.04 when I boot, X windows comes to a point where I get a white background with a bunch of colored dots. Nothing progresses from there. I can boot successfully by pressing escape after booting, going to advanced options, booting to 5.4.0-29 recovery mode. When that menu appears, I select "root". I press Enter for maintenance. When the root prompt appears I immediately type EXIT to return to the menu and then RESUME followed by OK. The system then starts the desktop properly. I would be happy to provide boot logs and/or Xorg.0.logs if desired. It appears to me that there are out of memory errors occurring along with some addressing issues. I am on an HP EliteBook 8570w laptop 15.6 G memory. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.19 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 10 10:22:37 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-22 (595 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-05-09 09:07:41.355959 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877871/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880103] Re: Awaking problem after suspend mode still happens
apport information ** Tags added: apport-collected tessa ** Description changed: - 101 kernel seems to be better than 99, when the problem happened almost - every time. Nevertheless, it happened again with 2+days uptime and - suspending over night. Maybe it depends on my wireless keyboard? I tried - Alt+SysRq reisub twice, but it didn't work. Mint Cinnamon 19.1, desktop. + 101 kernel seems to be better than 99, when the problem happened almost every time. Nevertheless, it happened again with 2+days uptime and suspending over night. Maybe it depends on my wireless keyboard? I tried Alt+SysRq reisub twice, but it didn't work. Mint Cinnamon 19.1, desktop. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.14 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/pcmC2D0c: waldi 1668 F...m pulseaudio + /dev/snd/controlC2: waldi 1668 F pulseaudio + /dev/snd/controlC0: waldi 1668 F pulseaudio + /dev/snd/controlC1: waldi 1668 F pulseaudio + CurrentDesktop: X-Cinnamon + DistroRelease: Linux Mint 19.1 + HibernationDevice: RESUME=UUID=018b3f92-7678-b1d9-8157-f8388f5198a2 + InstallationDate: Installed on 2019-02-27 (449 days ago) + InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 + IwConfig: + lono wireless extensions. + + enp6s0no wireless extensions. + + enp5s0no wireless extensions. + MachineType: System manufacturer System Product Name + Package: linux (not installed) + ProcFB: 0 radeondrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=e74e78ea-7a9d-41a9-839b-e32c0343041f ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-101-generic N/A + linux-backports-modules-4.15.0-101-generic N/A + linux-firmware 1.173.18 + RfKill: + + Tags: tessa + Uname: Linux 4.15.0-101-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers + _MarkForUpload: True + dmi.bios.date: 01/18/2012 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 0501 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: P8H61-M LX2 + 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.:bvr0501:bd01/18/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX2: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 ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1880103/+attachment/5375612/+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/1880103 Title: Awaking problem after suspend mode still happens Status in linux package in Ubuntu: Incomplete Bug description: 101 kernel seems to be better than 99, when the problem happened almost every time. Nevertheless, it happened again with 2+days uptime and suspending over night. Maybe it depends on my wireless keyboard? I tried Alt+SysRq reisub twice, but it didn't work. Mint Cinnamon 19.1, desktop. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0c: waldi 1668 F...m pulseaudio /dev/snd/controlC2: waldi 1668 F pulseaudio /dev/snd/controlC0: waldi 1668 F pulseaudio /dev/snd/controlC1: waldi 1668 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=018b3f92-7678-b1d9-8157-f8388f5198a2 InstallationDate: Installed on 2019-02-27 (449 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. enp6s0no wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=e74e78ea-7a9d-41a9-839b-e32c0343041f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-101-generic N/A linux-backports-modules-4.15.0-101-generic N/A linux-firmware 1.173.18 RfKill: Tags: tessa Uname: Linux 4.15.0-101-generic x86_64 UpgradeStatus: No upgrade log presen
[Kernel-packages] [Bug 1880103] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1880103/+attachment/5375622/+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/1880103 Title: Awaking problem after suspend mode still happens Status in linux package in Ubuntu: Incomplete Bug description: 101 kernel seems to be better than 99, when the problem happened almost every time. Nevertheless, it happened again with 2+days uptime and suspending over night. Maybe it depends on my wireless keyboard? I tried Alt+SysRq reisub twice, but it didn't work. Mint Cinnamon 19.1, desktop. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0c: waldi 1668 F...m pulseaudio /dev/snd/controlC2: waldi 1668 F pulseaudio /dev/snd/controlC0: waldi 1668 F pulseaudio /dev/snd/controlC1: waldi 1668 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=018b3f92-7678-b1d9-8157-f8388f5198a2 InstallationDate: Installed on 2019-02-27 (449 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. enp6s0no wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=e74e78ea-7a9d-41a9-839b-e32c0343041f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-101-generic N/A linux-backports-modules-4.15.0-101-generic N/A linux-firmware 1.173.18 RfKill: Tags: tessa Uname: Linux 4.15.0-101-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 01/18/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX2 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.:bvr0501:bd01/18/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX2: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/1880103/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880103] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1880103/+attachment/5375619/+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/1880103 Title: Awaking problem after suspend mode still happens Status in linux package in Ubuntu: Incomplete Bug description: 101 kernel seems to be better than 99, when the problem happened almost every time. Nevertheless, it happened again with 2+days uptime and suspending over night. Maybe it depends on my wireless keyboard? I tried Alt+SysRq reisub twice, but it didn't work. Mint Cinnamon 19.1, desktop. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0c: waldi 1668 F...m pulseaudio /dev/snd/controlC2: waldi 1668 F pulseaudio /dev/snd/controlC0: waldi 1668 F pulseaudio /dev/snd/controlC1: waldi 1668 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=018b3f92-7678-b1d9-8157-f8388f5198a2 InstallationDate: Installed on 2019-02-27 (449 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. enp6s0no wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=e74e78ea-7a9d-41a9-839b-e32c0343041f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-101-generic N/A linux-backports-modules-4.15.0-101-generic N/A linux-firmware 1.173.18 RfKill: Tags: tessa Uname: Linux 4.15.0-101-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 01/18/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX2 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.:bvr0501:bd01/18/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX2: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/1880103/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880103] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1880103/+attachment/5375620/+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/1880103 Title: Awaking problem after suspend mode still happens Status in linux package in Ubuntu: Incomplete Bug description: 101 kernel seems to be better than 99, when the problem happened almost every time. Nevertheless, it happened again with 2+days uptime and suspending over night. Maybe it depends on my wireless keyboard? I tried Alt+SysRq reisub twice, but it didn't work. Mint Cinnamon 19.1, desktop. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0c: waldi 1668 F...m pulseaudio /dev/snd/controlC2: waldi 1668 F pulseaudio /dev/snd/controlC0: waldi 1668 F pulseaudio /dev/snd/controlC1: waldi 1668 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=018b3f92-7678-b1d9-8157-f8388f5198a2 InstallationDate: Installed on 2019-02-27 (449 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. enp6s0no wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=e74e78ea-7a9d-41a9-839b-e32c0343041f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-101-generic N/A linux-backports-modules-4.15.0-101-generic N/A linux-firmware 1.173.18 RfKill: Tags: tessa Uname: Linux 4.15.0-101-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 01/18/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX2 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.:bvr0501:bd01/18/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX2: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/1880103/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880103] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1880103/+attachment/5375614/+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/1880103 Title: Awaking problem after suspend mode still happens Status in linux package in Ubuntu: Incomplete Bug description: 101 kernel seems to be better than 99, when the problem happened almost every time. Nevertheless, it happened again with 2+days uptime and suspending over night. Maybe it depends on my wireless keyboard? I tried Alt+SysRq reisub twice, but it didn't work. Mint Cinnamon 19.1, desktop. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0c: waldi 1668 F...m pulseaudio /dev/snd/controlC2: waldi 1668 F pulseaudio /dev/snd/controlC0: waldi 1668 F pulseaudio /dev/snd/controlC1: waldi 1668 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=018b3f92-7678-b1d9-8157-f8388f5198a2 InstallationDate: Installed on 2019-02-27 (449 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. enp6s0no wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=e74e78ea-7a9d-41a9-839b-e32c0343041f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-101-generic N/A linux-backports-modules-4.15.0-101-generic N/A linux-firmware 1.173.18 RfKill: Tags: tessa Uname: Linux 4.15.0-101-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 01/18/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX2 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.:bvr0501:bd01/18/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX2: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/1880103/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880103] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1880103/+attachment/5375621/+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/1880103 Title: Awaking problem after suspend mode still happens Status in linux package in Ubuntu: Incomplete Bug description: 101 kernel seems to be better than 99, when the problem happened almost every time. Nevertheless, it happened again with 2+days uptime and suspending over night. Maybe it depends on my wireless keyboard? I tried Alt+SysRq reisub twice, but it didn't work. Mint Cinnamon 19.1, desktop. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0c: waldi 1668 F...m pulseaudio /dev/snd/controlC2: waldi 1668 F pulseaudio /dev/snd/controlC0: waldi 1668 F pulseaudio /dev/snd/controlC1: waldi 1668 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=018b3f92-7678-b1d9-8157-f8388f5198a2 InstallationDate: Installed on 2019-02-27 (449 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. enp6s0no wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=e74e78ea-7a9d-41a9-839b-e32c0343041f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-101-generic N/A linux-backports-modules-4.15.0-101-generic N/A linux-firmware 1.173.18 RfKill: Tags: tessa Uname: Linux 4.15.0-101-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 01/18/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX2 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.:bvr0501:bd01/18/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX2: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/1880103/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880103] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1880103/+attachment/5375623/+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/1880103 Title: Awaking problem after suspend mode still happens Status in linux package in Ubuntu: Incomplete Bug description: 101 kernel seems to be better than 99, when the problem happened almost every time. Nevertheless, it happened again with 2+days uptime and suspending over night. Maybe it depends on my wireless keyboard? I tried Alt+SysRq reisub twice, but it didn't work. Mint Cinnamon 19.1, desktop. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0c: waldi 1668 F...m pulseaudio /dev/snd/controlC2: waldi 1668 F pulseaudio /dev/snd/controlC0: waldi 1668 F pulseaudio /dev/snd/controlC1: waldi 1668 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=018b3f92-7678-b1d9-8157-f8388f5198a2 InstallationDate: Installed on 2019-02-27 (449 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. enp6s0no wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=e74e78ea-7a9d-41a9-839b-e32c0343041f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-101-generic N/A linux-backports-modules-4.15.0-101-generic N/A linux-firmware 1.173.18 RfKill: Tags: tessa Uname: Linux 4.15.0-101-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 01/18/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX2 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.:bvr0501:bd01/18/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX2: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/1880103/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880103] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1880103/+attachment/5375616/+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/1880103 Title: Awaking problem after suspend mode still happens Status in linux package in Ubuntu: Incomplete Bug description: 101 kernel seems to be better than 99, when the problem happened almost every time. Nevertheless, it happened again with 2+days uptime and suspending over night. Maybe it depends on my wireless keyboard? I tried Alt+SysRq reisub twice, but it didn't work. Mint Cinnamon 19.1, desktop. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0c: waldi 1668 F...m pulseaudio /dev/snd/controlC2: waldi 1668 F pulseaudio /dev/snd/controlC0: waldi 1668 F pulseaudio /dev/snd/controlC1: waldi 1668 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=018b3f92-7678-b1d9-8157-f8388f5198a2 InstallationDate: Installed on 2019-02-27 (449 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. enp6s0no wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=e74e78ea-7a9d-41a9-839b-e32c0343041f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-101-generic N/A linux-backports-modules-4.15.0-101-generic N/A linux-firmware 1.173.18 RfKill: Tags: tessa Uname: Linux 4.15.0-101-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 01/18/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX2 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.:bvr0501:bd01/18/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX2: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/1880103/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880103] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1880103/+attachment/5375617/+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/1880103 Title: Awaking problem after suspend mode still happens Status in linux package in Ubuntu: Incomplete Bug description: 101 kernel seems to be better than 99, when the problem happened almost every time. Nevertheless, it happened again with 2+days uptime and suspending over night. Maybe it depends on my wireless keyboard? I tried Alt+SysRq reisub twice, but it didn't work. Mint Cinnamon 19.1, desktop. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0c: waldi 1668 F...m pulseaudio /dev/snd/controlC2: waldi 1668 F pulseaudio /dev/snd/controlC0: waldi 1668 F pulseaudio /dev/snd/controlC1: waldi 1668 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=018b3f92-7678-b1d9-8157-f8388f5198a2 InstallationDate: Installed on 2019-02-27 (449 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. enp6s0no wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=e74e78ea-7a9d-41a9-839b-e32c0343041f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-101-generic N/A linux-backports-modules-4.15.0-101-generic N/A linux-firmware 1.173.18 RfKill: Tags: tessa Uname: Linux 4.15.0-101-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 01/18/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX2 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.:bvr0501:bd01/18/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX2: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/1880103/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879185] Re: fails with kernel 5.3 on linux mint, HP-Laptop-14-cm0xxx
I'm running Linux Mint 19.3 Mate. I'm willing to put up a VirtualBox VM in 20.04, but really can't do a reinstall right now, as there's about a weeks' worth of custom updates. (I write application software for numerical stuff, but can't pretend knowledge of kernel / module level stuff.) However, am willing to try what I can. Prof. J C Nash -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879185 Title: fails with kernel 5.3 on linux mint, HP-Laptop-14-cm0xxx Status in linux package in Ubuntu: Incomplete Bug description: I reset the previous kernel to be able to post, because it is very difficult to work like this, this happens randomly, intermittently with each application or without having anything open. It happened from the last update to kernel 5.3, I suppose that it is the very new laptop since in another partition I have Kali and it happens the same. I appreciate your help, I list the characteristics of this laptop :roll: ydhm@ydhm-HP-Laptop-14-cm0xxx:~$ inxi -Fxz System: Host: ydhm-HP-Laptop-14-cm0xxx Kernel: 5.0.0-32-generic x86_64 bits: 64 compiler: gcc v: 7.4.0 Desktop: Xfce 4.14.1 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic Machine: Type: Laptop System: HP product: HP Laptop 14-cm0xxx v: N/A serial: Mobo: HP model: 84A2 v: 84.24 serial: UEFI: AMI v: F.42 date: 07/03/2019 Battery: ID-1: BAT0 charge: 28.9 Wh condition: 40.8/40.8 Wh (100%) model: Hewlett-Packard Primary status: Charging CPU: Topology: Dual Core model: AMD Ryzen 3 2200U with Radeon Vega Mobile Gfx bits: 64 type: MT MCP arch: Zen L2 cache: 1024 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 19962 Speed: 1433 MHz min/max: 1600/2500 MHz Core speeds (MHz): 1: 1400 2: 1398 3: 1490 4: 1441 Graphics: Device-1: AMD Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] vendor: Hewlett-Packard driver: amdgpu v: kernel bus ID: 04:00.0 Display: x11 server: X.Org 1.20.5 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa resolution: 1366x768~60Hz OpenGL: renderer: AMD RAVEN (DRM 3.27.0 5.0.0-32-generic LLVM 9.0.0) v: 4.5 Mesa 19.2.8 direct render: Yes Audio: Device-1: AMD vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 04:00.1 Device-2: AMD vendor: Hewlett-Packard driver: N/A bus ID: 04:00.5 Device-3: AMD vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 04:00.6 Sound Server: ALSA v: k5.0.0-32-generic Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Hewlett-Packard driver: r8169 v: kernel port: f000 bus ID: 02:00.0 IF: eno1 state: down mac: Device-2: Realtek vendor: Hewlett-Packard driver: N/A port: e000 bus ID: 03:00.0 Device-3: D-Link DWA-125 Wireless N 150 Adapter(rev.A3) [Ralink RT5370] type: USB driver: rt2800usb bus ID: 1-3:3 IF: wlxacf1df084ac8 state: up mac: Drives: Local Storage: total: 931.51 GiB used: 23.91 GiB (2.6%) ID-1: /dev/sda vendor: HGST (Hitachi) model: HTS541010B7E610 size: 931.51 GiB Partition: ID-1: / size: 139.20 GiB used: 21.62 GiB (15.5%) fs: ext4 dev: /dev/sda5 Sensors: System Temperatures: cpu: 45.1 C mobo: N/A gpu: amdgpu temp: 45 C Fan Speeds (RPM): N/A Info: Processes: 199 Uptime: 27m Memory: 3.38 GiB used: 1.18 GiB (35.0%) Init: systemd runlevel: 5 Compilers: gcc: 7.5.0 Shell: bash v: 4.4.20 inxi: 3.0.32 / ydhm@ydhm-HP-Laptop-14-cm0xxx:~$ rfkill list all 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no / ydhm@ydhm-HP-Laptop-14-cm0xxx:~$ mokutil --sb-state SecureBoot disabled Platform is in Setup Mode Ps: I also don't have wifi and bluetooth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879185/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded
Sorry, I didn't actually test Focal and Groovy. Xenial will be supported for about a year, so I think it worth to fix it there as well; however it's relative what worth to fix and what not, as most users probably left Xenial behind already or applied a workaround if they were ever affected by this issue. On the other hand it can be a real pain if you don't know about this and just happen to convert your root LV to raid1 and then your system doesn't boot. "The supported configuration for raid1 is mdadm after all, not removing mdadm and the meta packages that depend on it and using lvm's raid support." I don't know where LVM over DM-RAID is defined as the "supported configuration" as opposed to RAID1 over LVM. I always thought about them as equal alternatives for slightly different use cases. My rule of thumb is when you can afford to get identical sized disks and mirror everything, go with LVM over DM-RAID. If you can't guarantee to have identical sized disks and need a more dynamic solution, then RAID1 over LVM (i.e. using LVM's raid1 support) is more suitable. I recommend the former in productive server environments and the latter in smaller SOHO, home servers and personal computers. If one of my disks goes bye-bye, I wouldn't want to reinstall my system or lose my documents, so I have my / and /home LVs in raid1. However I couldn't care less about my Steam library because I can just re-download the games anytime, so I don't have it mirrored, as I'd rather not want it to use twice the precious disk space. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1509717 Title: Wily LVM-RAID1 – md: personality for level 1 is not loaded Status in linux package in Ubuntu: Invalid Status in lvm2 package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in lvm2 source package in Bionic: Fix Released Status in linux source package in Cosmic: Invalid Status in lvm2 source package in Cosmic: Won't Fix Status in linux source package in Disco: Invalid Status in lvm2 source package in Disco: Won't Fix Status in linux source package in Eoan: Invalid Status in lvm2 source package in Eoan: Fix Released Status in lvm2 package in Debian: Incomplete Bug description: [Impact] system does not boot after converting lvm volume to raid1 w/o having mdadm installed. [Test case] 1. Install server with subiquity to LVM 2. Add second disk to it 3. Run pvcreate /dev/vdb 4. Run vgextend ubuntu-vg /dev/vdb 5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv Reboot and check that it still boots. 6. Remove mdadm 7. Upgrade to lvm2 from proposed Reboot and check that it still boots. 8. Downgrade lvm2 to release Reboot and check that it fails to boot [Regression potential] Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier. [Original bug report] After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot. I get the following message each time LVM tries to activate a raid1 LV: md: personality for level 1 is not loaded! Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded
There are two things: - On servers, ubuntu-server depends on mdadm, so removing mdadm also removes ubuntu-server package, which means it's not really supported - In general, the installers don't offer installing like that. I don't know why we did not have a task for xenial. ** Description changed: [Impact] system does not boot after converting lvm volume to raid1 w/o having mdadm installed. [Test case] - 1. Install server with subiquity to LVM + 1. Install server to LVM 2. Add second disk to it 3. Run pvcreate /dev/vdb 4. Run vgextend ubuntu-vg /dev/vdb - 5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv + 5. Run lvconvert -m1 --type raid1 ubuntu-vg/ubuntu-lv Reboot and check that it still boots. 6. Remove mdadm 7. Upgrade to lvm2 from proposed Reboot and check that it still boots. 8. Downgrade lvm2 to release Reboot and check that it fails to boot [Regression potential] Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier. [Original bug report] After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot. I get the following message each time LVM tries to activate a raid1 LV: md: personality for level 1 is not loaded! Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1509717 Title: Wily LVM-RAID1 – md: personality for level 1 is not loaded Status in linux package in Ubuntu: Invalid Status in lvm2 package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in lvm2 source package in Bionic: Fix Released Status in linux source package in Cosmic: Invalid Status in lvm2 source package in Cosmic: Won't Fix Status in linux source package in Disco: Invalid Status in lvm2 source package in Disco: Won't Fix Status in linux source package in Eoan: Invalid Status in lvm2 source package in Eoan: Fix Released Status in lvm2 package in Debian: Incomplete Bug description: [Impact] system does not boot after converting lvm volume to raid1 w/o having mdadm installed. [Test case] 1. Install server to LVM 2. Add second disk to it 3. Run pvcreate /dev/vdb 4. Run vgextend ubuntu-vg /dev/vdb 5. Run lvconvert -m1 --type raid1 ubuntu-vg/ubuntu-lv Reboot and check that it still boots. 6. Remove mdadm 7. Upgrade to lvm2 from proposed Reboot and check that it still boots. 8. Downgrade lvm2 to release Reboot and check that it fails to boot [Regression potential] Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier. [Original bug report] After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot. I get the following message each time LVM tries to activate a raid1 LV: md: personality for level 1 is not loaded! Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879185] Re: fails with kernel 5.3 on linux mint, HP-Laptop-14-cm0xxx
Please follow this one: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877871/comments/8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879185 Title: fails with kernel 5.3 on linux mint, HP-Laptop-14-cm0xxx Status in linux package in Ubuntu: Incomplete Bug description: I reset the previous kernel to be able to post, because it is very difficult to work like this, this happens randomly, intermittently with each application or without having anything open. It happened from the last update to kernel 5.3, I suppose that it is the very new laptop since in another partition I have Kali and it happens the same. I appreciate your help, I list the characteristics of this laptop :roll: ydhm@ydhm-HP-Laptop-14-cm0xxx:~$ inxi -Fxz System: Host: ydhm-HP-Laptop-14-cm0xxx Kernel: 5.0.0-32-generic x86_64 bits: 64 compiler: gcc v: 7.4.0 Desktop: Xfce 4.14.1 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic Machine: Type: Laptop System: HP product: HP Laptop 14-cm0xxx v: N/A serial: Mobo: HP model: 84A2 v: 84.24 serial: UEFI: AMI v: F.42 date: 07/03/2019 Battery: ID-1: BAT0 charge: 28.9 Wh condition: 40.8/40.8 Wh (100%) model: Hewlett-Packard Primary status: Charging CPU: Topology: Dual Core model: AMD Ryzen 3 2200U with Radeon Vega Mobile Gfx bits: 64 type: MT MCP arch: Zen L2 cache: 1024 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 19962 Speed: 1433 MHz min/max: 1600/2500 MHz Core speeds (MHz): 1: 1400 2: 1398 3: 1490 4: 1441 Graphics: Device-1: AMD Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] vendor: Hewlett-Packard driver: amdgpu v: kernel bus ID: 04:00.0 Display: x11 server: X.Org 1.20.5 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa resolution: 1366x768~60Hz OpenGL: renderer: AMD RAVEN (DRM 3.27.0 5.0.0-32-generic LLVM 9.0.0) v: 4.5 Mesa 19.2.8 direct render: Yes Audio: Device-1: AMD vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 04:00.1 Device-2: AMD vendor: Hewlett-Packard driver: N/A bus ID: 04:00.5 Device-3: AMD vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 04:00.6 Sound Server: ALSA v: k5.0.0-32-generic Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Hewlett-Packard driver: r8169 v: kernel port: f000 bus ID: 02:00.0 IF: eno1 state: down mac: Device-2: Realtek vendor: Hewlett-Packard driver: N/A port: e000 bus ID: 03:00.0 Device-3: D-Link DWA-125 Wireless N 150 Adapter(rev.A3) [Ralink RT5370] type: USB driver: rt2800usb bus ID: 1-3:3 IF: wlxacf1df084ac8 state: up mac: Drives: Local Storage: total: 931.51 GiB used: 23.91 GiB (2.6%) ID-1: /dev/sda vendor: HGST (Hitachi) model: HTS541010B7E610 size: 931.51 GiB Partition: ID-1: / size: 139.20 GiB used: 21.62 GiB (15.5%) fs: ext4 dev: /dev/sda5 Sensors: System Temperatures: cpu: 45.1 C mobo: N/A gpu: amdgpu temp: 45 C Fan Speeds (RPM): N/A Info: Processes: 199 Uptime: 27m Memory: 3.38 GiB used: 1.18 GiB (35.0%) Init: systemd runlevel: 5 Compilers: gcc: 7.5.0 Shell: bash v: 4.4.20 inxi: 3.0.32 / ydhm@ydhm-HP-Laptop-14-cm0xxx:~$ rfkill list all 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no / ydhm@ydhm-HP-Laptop-14-cm0xxx:~$ mokutil --sb-state SecureBoot disabled Platform is in Setup Mode Ps: I also don't have wifi and bluetooth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879185/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861284] Re: Build and ship a signed wireguard.ko
** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Eoan) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861284 Title: Build and ship a signed wireguard.ko Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: In Progress Bug description: .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861284/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876165] Re: Binder and ashmem drivers are missing from aws-edge kernel
** Also affects: linux-aws (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-aws (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux-aws (Ubuntu Bionic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- 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/1876165 Title: Binder and ashmem drivers are missing from AWS kernel Status in linux-aws package in Ubuntu: In Progress Status in linux-aws source package in Eoan: In Progress Status in linux-aws source package in Focal: In Progress Bug description: For quite a while the Ubuntu kernel now ships the Ashmem and Binder drivers as part of linux-modules-extra-*. They were available on previous linux-aws kernels but seem to have dropped with the 5.3.0 based edge kernel. See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849493 for a similar bug report I filed in the past for the GCP kernels. Can we get both ashmem and binder enabled and added to linux-aws-edge as they are used for Anbox Cloud? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1876165/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878377] Re: USB keyboard doesn't work with rpi3 (armhf)
** No longer affects: linux-raspi2 (Ubuntu Focal) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1878377 Title: USB keyboard doesn't work with rpi3 (armhf) Status in pi2-kernel-snap: New Status in snapd: New Status in linux-raspi package in Ubuntu: New Status in linux-raspi source package in Focal: New Bug description: Testing armhf image (ubuntu-core-20-armhf+raspi.img.xz) which download from http://cdimage.ubuntu.com/ubuntu-core/20/beta/20200512.3/ on Raspberry pi 3B After booting into system, the screen shows "Press enter to configure", press enter key on USB keyboard no respond. Try to connect USB keyboard via USB hub also doesn't work. To manage notifications about this bug go to: https://bugs.launchpad.net/pi2-kernel-snap/+bug/1878377/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876165] Re: Binder and ashmem drivers are missing from aws-edge kernel
This needs to be enabled for {eoan,focal}/linux-aws, and then for the
bionic/linux-aws-5.3 and bionic/linux-aws-5.4 derivatives.
** No longer affects: linux-aws (Ubuntu Bionic)
** Summary changed:
- Binder and ashmem drivers are missing from aws-edge kernel
+ Binder and ashmem drivers are missing from AWS kernel
** Also affects: linux-aws (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-aws (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: linux-aws (Ubuntu Eoan)
Status: New => In Progress
** Changed in: linux-aws (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-aws (Ubuntu Eoan)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
** Changed in: linux-aws (Ubuntu Focal)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
** Also affects: linux-aws-5.3 (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-aws-5.3 (Ubuntu Eoan)
** No longer affects: linux-aws-5.3 (Ubuntu Focal)
** Also affects: linux-aws (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux-aws-5.3 (Ubuntu Bionic)
Importance: Undecided
Status: New
** No longer affects: linux-aws (Ubuntu Bionic)
** Changed in: linux-aws-5.3 (Ubuntu)
Status: New => In Progress
** Changed in: linux-aws-5.3 (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux-aws-5.3 (Ubuntu)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
** Changed in: linux-aws-5.3 (Ubuntu Bionic)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
--
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/1876165
Title:
Binder and ashmem drivers are missing from AWS kernel
Status in linux-aws package in Ubuntu:
In Progress
Status in linux-aws-5.3 package in Ubuntu:
In Progress
Status in linux-aws-5.3 source package in Bionic:
In Progress
Status in linux-aws source package in Eoan:
In Progress
Status in linux-aws source package in Focal:
In Progress
Bug description:
For quite a while the Ubuntu kernel now ships the Ashmem and Binder
drivers as part of linux-modules-extra-*. They were available on
previous linux-aws kernels but seem to have dropped with the 5.3.0
based edge kernel.
See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849493 for a
similar bug report I filed in the past for the GCP kernels.
Can we get both ashmem and binder enabled and added to linux-aws-edge
as they are used for Anbox Cloud?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1876165/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877871] Re: [radeon] X windows hangs following upgrade from 18.04 to 20.04
I installed both of the packages in reverse order due to dependencies. On reboot, the screen behaved the same, hanging with a white background. The latest boot log is attached. Thanks for the continued effort. ** Attachment added: "vmlinuz-5.7.0-994-generic boot.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877871/+attachment/5375666/+files/vmlinuz-5.7.0-994-generic%20boot.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877871 Title: [radeon] X windows hangs following upgrade from 18.04 to 20.04 Status in linux package in Ubuntu: Incomplete Bug description: Following an upgrade from 18.04 to 20.04 when I boot, X windows comes to a point where I get a white background with a bunch of colored dots. Nothing progresses from there. I can boot successfully by pressing escape after booting, going to advanced options, booting to 5.4.0-29 recovery mode. When that menu appears, I select "root". I press Enter for maintenance. When the root prompt appears I immediately type EXIT to return to the menu and then RESUME followed by OK. The system then starts the desktop properly. I would be happy to provide boot logs and/or Xorg.0.logs if desired. It appears to me that there are out of memory errors occurring along with some addressing issues. I am on an HP EliteBook 8570w laptop 15.6 G memory. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.19 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 10 10:22:37 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-22 (595 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-05-09 09:07:41.355959 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877871/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861284] Re: Build and ship a signed wireguard.ko
** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861284 Title: Build and ship a signed wireguard.ko Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: Fix Committed Bug description: .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861284/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861284] Re: Build and ship a signed wireguard.ko
** Changed in: linux (Ubuntu Eoan) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861284 Title: Build and ship a signed wireguard.ko Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: Fix Committed Bug description: .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861284/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879987] Re: machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.
I tested with debian buster and I wasn't able to reproduce (w/o quiet parameter) I'm not yet too sure if it's a pure initramfs-tools or something introduced by a package hooks. I first thought that plymouth could have beeb a potential candidate, but I disabled it and even purge it and problem persisted. - Eric -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879987 Title: machine get stuck at boot if specified 'console=ttyS* ' doesn't exist. Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: kernel get stucks at boot if console=ttyS* is specified in the kernel cmdline and that serial HW isn't available on the system. Reproduced with: 4.4 (from Xenial), 4.15 (from Bionic), 5.4 (native, Focal) and 5.7-next (mainline) Removing the non-existent 'console=ttyS*' parameter fixes the situation. I tested it using KVM/qemu, but it has been brought to my attention that it was reproducible in VMware as well. I think it is safe to say that it is unlikely to be specifics to a certain virtualization technology type. Didn't test on baremetal yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879987/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864061] Re: PCI/internal sound card not detected
I am still affected by this bug on focal with intel gpu/hda on kernel 5.4.0-26 Adding the value to /etc/modprobe.d/alsa-base.conf does not help me Linux Ashen-One 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ➜ ~ lspci -v 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 05) Subsystem: Acer Incorporated [ALI] Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers Flags: bus master, fast devsel, latency 0 Capabilities: Kernel driver in use: skl_uncore 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 05) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 122 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 4000-4fff [size=4K] Memory behind bridge: a300-a3ff [size=16M] Prefetchable memory behind bridge: 9000-a1ff [size=288M] Capabilities: Kernel driver in use: pcieport 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] HD Graphics 630 Flags: bus master, fast devsel, latency 0, IRQ 131 Memory at a200 (64-bit, non-prefetchable) [size=16M] Memory at b000 (64-bit, prefetchable) [size=256M] I/O ports at 5000 [size=64] Expansion ROM at 000c [virtual] [disabled] [size=128K] Capabilities: Kernel driver in use: i915 Kernel modules: i915 00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31) (prog-if 30 [XHCI]) Subsystem: Acer Incorporated [ALI] 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller Flags: bus master, medium devsel, latency 0, IRQ 126 Memory at a430 (64-bit, non-prefetchable) [size=64K] Capabilities: Kernel driver in use: xhci_hcd 00:14.2 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Thermal Subsystem (rev 31) Subsystem: Acer Incorporated [ALI] 100 Series/C230 Series Chipset Family Thermal Subsystem Flags: bus master, fast devsel, latency 0, IRQ 18 Memory at a432a000 (64-bit, non-prefetchable) [size=4K] Capabilities: Kernel driver in use: intel_pch_thermal Kernel modules: intel_pch_thermal 00:15.0 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Serial IO I2C Controller #0 (rev 31) Subsystem: Acer Incorporated [ALI] 100 Series/C230 Series Chipset Family Serial IO I2C Controller Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at a432b000 (64-bit, non-prefetchable) [size=4K] Capabilities: Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:15.1 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Serial IO I2C Controller #1 (rev 31) Subsystem: Acer Incorporated [ALI] 100 Series/C230 Series Chipset Family Serial IO I2C Controller Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at a432c000 (64-bit, non-prefetchable) [size=4K] Capabilities: Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 (rev 31) Subsystem: Acer Incorporated [ALI] 100 Series/C230 Series Chipset Family MEI Controller Flags: bus master, fast devsel, latency 0, IRQ 136 Memory at a432d000 (64-bit, non-prefetchable) [size=4K] Capabilities: Kernel driver in use: mei_me Kernel modules: mei_me 00:17.0 SATA controller: Intel Corporation HM170/QM170 Chipset SATA Controller [AHCI Mode] (rev 31) (prog-if 01 [AHCI 1.0]) Subsystem: Acer Incorporated [ALI] HM170/QM170 Chipset SATA Controller [AHCI Mode] Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 127 Memory at a4328000 (32-bit, non-prefetchable) [size=8K] Memory at a433 (32-bit, non-prefetchable) [size=256] I/O ports at 5080 [size=8] I/O ports at 5088 [size=4] I/O ports at 5060 [size=32] Memory at a432e000 (32-bit, non-prefetchable) [size=2K] Capabilities: Kernel driver in use: ahci Kernel modules: ahci 00:1c.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #3 (rev f1) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 123 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 I/O behind bridge: [disabled] Memory behind bridge: a420-a42f [size=1M] Prefetc
[Kernel-packages] [Bug 1876165] Re: Binder and ashmem drivers are missing from AWS kernel
https://lists.ubuntu.com/archives/kernel-team/2020-May/110153.html -- 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/1876165 Title: Binder and ashmem drivers are missing from AWS kernel Status in linux-aws package in Ubuntu: In Progress Status in linux-aws-5.3 package in Ubuntu: In Progress Status in linux-aws-5.3 source package in Bionic: In Progress Status in linux-aws source package in Eoan: In Progress Status in linux-aws source package in Focal: In Progress Bug description: For quite a while the Ubuntu kernel now ships the Ashmem and Binder drivers as part of linux-modules-extra-*. They were available on previous linux-aws kernels but seem to have dropped with the 5.3.0 based edge kernel. See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849493 for a similar bug report I filed in the past for the GCP kernels. Can we get both ashmem and binder enabled and added to linux-aws-edge as they are used for Anbox Cloud? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1876165/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879185] Re: fails with kernel 5.3 on linux mint, HP-Laptop-14-cm0xxx
I installed linux-modules-5.7.0-994-generic_5.7.0-994.202005192206_amd64.deb then linux-image-unsigned-5.7.0-994-generic_5.7.0-994.202005192206_amd64.deb (because of dependency, has to be that order), and then rebooted and selected the 994 version (I have vmlinuz-5.3.0-51-generic as default, and can also choose -53- if desired). It booted fine, and shut down seemingly correctly. Do you want me to run any diagnostics or logs? JN -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879185 Title: fails with kernel 5.3 on linux mint, HP-Laptop-14-cm0xxx Status in linux package in Ubuntu: Incomplete Bug description: I reset the previous kernel to be able to post, because it is very difficult to work like this, this happens randomly, intermittently with each application or without having anything open. It happened from the last update to kernel 5.3, I suppose that it is the very new laptop since in another partition I have Kali and it happens the same. I appreciate your help, I list the characteristics of this laptop :roll: ydhm@ydhm-HP-Laptop-14-cm0xxx:~$ inxi -Fxz System: Host: ydhm-HP-Laptop-14-cm0xxx Kernel: 5.0.0-32-generic x86_64 bits: 64 compiler: gcc v: 7.4.0 Desktop: Xfce 4.14.1 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic Machine: Type: Laptop System: HP product: HP Laptop 14-cm0xxx v: N/A serial: Mobo: HP model: 84A2 v: 84.24 serial: UEFI: AMI v: F.42 date: 07/03/2019 Battery: ID-1: BAT0 charge: 28.9 Wh condition: 40.8/40.8 Wh (100%) model: Hewlett-Packard Primary status: Charging CPU: Topology: Dual Core model: AMD Ryzen 3 2200U with Radeon Vega Mobile Gfx bits: 64 type: MT MCP arch: Zen L2 cache: 1024 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 19962 Speed: 1433 MHz min/max: 1600/2500 MHz Core speeds (MHz): 1: 1400 2: 1398 3: 1490 4: 1441 Graphics: Device-1: AMD Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] vendor: Hewlett-Packard driver: amdgpu v: kernel bus ID: 04:00.0 Display: x11 server: X.Org 1.20.5 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa resolution: 1366x768~60Hz OpenGL: renderer: AMD RAVEN (DRM 3.27.0 5.0.0-32-generic LLVM 9.0.0) v: 4.5 Mesa 19.2.8 direct render: Yes Audio: Device-1: AMD vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 04:00.1 Device-2: AMD vendor: Hewlett-Packard driver: N/A bus ID: 04:00.5 Device-3: AMD vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 04:00.6 Sound Server: ALSA v: k5.0.0-32-generic Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Hewlett-Packard driver: r8169 v: kernel port: f000 bus ID: 02:00.0 IF: eno1 state: down mac: Device-2: Realtek vendor: Hewlett-Packard driver: N/A port: e000 bus ID: 03:00.0 Device-3: D-Link DWA-125 Wireless N 150 Adapter(rev.A3) [Ralink RT5370] type: USB driver: rt2800usb bus ID: 1-3:3 IF: wlxacf1df084ac8 state: up mac: Drives: Local Storage: total: 931.51 GiB used: 23.91 GiB (2.6%) ID-1: /dev/sda vendor: HGST (Hitachi) model: HTS541010B7E610 size: 931.51 GiB Partition: ID-1: / size: 139.20 GiB used: 21.62 GiB (15.5%) fs: ext4 dev: /dev/sda5 Sensors: System Temperatures: cpu: 45.1 C mobo: N/A gpu: amdgpu temp: 45 C Fan Speeds (RPM): N/A Info: Processes: 199 Uptime: 27m Memory: 3.38 GiB used: 1.18 GiB (35.0%) Init: systemd runlevel: 5 Compilers: gcc: 7.5.0 Shell: bash v: 4.4.20 inxi: 3.0.32 / ydhm@ydhm-HP-Laptop-14-cm0xxx:~$ rfkill list all 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no / ydhm@ydhm-HP-Laptop-14-cm0xxx:~$ mokutil --sb-state SecureBoot disabled Platform is in Setup Mode Ps: I also don't have wifi and bluetooth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879185/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879690] Re: Docker registry doesn't stay up and keeps restarting
I noticed something unexpected with the kernel in -proposed: /proc/version_signature reverts the upstream patchlevel to 5.4.34. If there's a mistake and it's really reverting all the upstream SRU patches, I may have a problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879690 Title: Docker registry doesn't stay up and keeps restarting Status in linux package in Ubuntu: Incomplete Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: [Impact] The change applied for bug 1857257 and its followup fix bug 1876645, which were released on focal and eoan -updates, introduced a regression on overlayfs, breaking docker snap. [Test case] See original bug report. [Fix] While we don't have a final fix the solution for now is to revert the following commits: UBUNTU: SAUCE: overlayfs: fix shitfs special-casing UBUNTU: SAUCE: overlayfs: use shiftfs hacks only with shiftfs as underlay [Regression potential] Low. Reverting these two commits will introduce back the issue reported on bug 1857257, but will fix the other use cases which was broken by the latest release. Original bug report. --- Tested kernels: Focal 5.4.0-31.35 Eoan 5.3.0-53.47 To reproduce: 1) Spin up a cloud image 2) snap install docker 3) auth_folder=/var/snap/docker/common/auth 4) mkdir -p $auth_folder 5) docker run --entrypoint htpasswd registry:2 -Bbn user passwd > $auth_folder/htpasswd 6) docker run -d -p 5000:5000 --restart=always --name registry \ -v $auth_folder:/auth \ -e "REGISTRY_AUTH=htpasswd" \ -e "REGISTRY_AUTH_HTPASSWD_REALM=Registry Realm" \ -e REGISTRY_AUTH_HTPASSWD_PATH=/auth/htpasswd \ registry:2 On a good kernel 'docker ps' shows something like: # docker ps CONTAINER IDIMAGE COMMAND CREATED STATUS PORTSNAMES a346b65b4509registry:2 "/entrypoint.sh /etc…" 14 seconds ago Up 12 seconds 0.0.0.0:5000->5000/tcp registry On a bad kernel: docker ps CONTAINER IDIMAGE COMMAND CREATED STATUSPORTS NAMES 0322374f1b1dregistry:2 "/entrypoint.sh /etc…" 5 seconds ago Restarting (2) 1 second ago registry Note status 'Restarting' on the bad kernel. This seems to be introduce by any of the following commits: b3bdda24f1bc UBUNTU: SAUCE: overlayfs: fix shitfs special-casing 6f18a8434050 UBUNTU: SAUCE: overlayfs: use shiftfs hacks only with shiftfs as underlay 629edd70891c UBUNTU: SAUCE: shiftfs: record correct creator credentials cfaa482afb97 UBUNTU: SAUCE: shiftfs: fix dentry revalidation Kernels that don't have these commits seem fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879690/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878919] Re: kworker/0:1+kacpid uses 100% of one CPU core
I have the same problem on 20.04 on a ThinkPad P50. It started when I upgrade from 19.10. It started after some time of being running. I did a new installation of the 20.04 and the problem persists but now only after wake up and if I put it to sleep and wake up again it stops. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878919 Title: kworker/0:1+kacpid uses 100% of one CPU core Status in linux package in Ubuntu: Incomplete Bug description: At some point, kworker/0:1+kacpid starts using 100% of one CPU's core; this can be seen in the top command. I captured some performance data via the following command: $ perf record -g -a sleep 10 Then, perf report gives the following: Samples: 75K of event 'cycles', Event count (approx.): 44710762967 Children Self Command Shared Object Symbol + 65,46% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] ret_from_fork + 65,46% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] kthread + 65,46% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] worker_thread + 65,44% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] process_one_work + 65,44% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] acpi_os_execute_deferred + 65,33% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ev_asynch_execute_gpe_method + 65,32% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ns_evaluate + 65,26% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ps_execute_method + 65,16% 0,06% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ps_parse_aml + 61,00% 0,94% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ps_parse_loop + 37,83% 0,75% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ds_exec_end_op + 18,33% 0,04% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ds_evaluate_name_path + 16,12% 0,23% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ns_lookup + 15,79% 0,20% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ns_search_and_enter + 15,23%14,99% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ns_search_one_scope + 14,38% 0,00% swapper [kernel.kallsyms] [k] secondary_startup_64 + 14,38% 0,02% swapper [kernel.kallsyms] [k] cpu_startup_entry + 14,31% 0,12% swapper [kernel.kallsyms] [k] do_idle + 13,79% 0,00% swapper [kernel.kallsyms] [k] start_secondary + 12,92% 0,03% swapper [kernel.kallsyms] [k] call_cpuidle + 12,89% 0,00% swapper [kernel.kallsyms] [k] cpuidle_enter + 12,85% 0,05% swapper [kernel.kallsyms] [k] cpuidle_enter_state + 12,35% 2,15% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ut_update_object_reference + 12,05% 0,28% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_resolve_to_value + 10,40% 0,04% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_resolve_node_to_value +9,90% 0,44% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ds_create_operand +9,50% 0,05% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_read_data_from_field +9,39% 0,06% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_field_datum_io +9,26% 0,12% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_access_region +9,23% 0,08% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ps_get_next_namepath +9,15% 1,28% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ut_update_ref_count.part.0 +9,01% 0,08% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ev_address_space_dispatch +8,96% 0,14% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_extract_from_field +8,78% 7,70% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_system_memory_space_handler +7,81% 0,22% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ut_remove_reference +6,63% 6,43% swapper [kernel.kallsyms] [k] intel_idle +5,31% 0,68% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ps_create_op +5,12% 0,08% kworker/0:1+kac
[Kernel-packages] [Bug 1865471] Re: USB 3.1 Gen 1 not work after using suspend
"pcie_aspm=off" on grub or enter the console don't help. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865471 Title: USB 3.1 Gen 1 not work after using suspend Status in linux package in Ubuntu: Incomplete Bug description: Good morning. I use "suspend"(settings -> energy -> When the shutdown...) on 18.04. Each wake up, USB ports 3.1 Gen 1 don't work (only those on the motherboard on the back of the case). --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: christophe 1648 F pulseaudio /dev/snd/controlC2: christophe 1648 F pulseaudio /dev/snd/controlC0: christophe 1648 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-02-18 (14 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. enp6s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-A320M-S2H (rev. 1.x) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=9757d7ed-95dd-47d2-a3a7-80be35d05879 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-40-generic N/A linux-backports-modules-5.3.0-40-generic N/A linux-firmware1.173.15 RfKill: Tags: bionic Uname: Linux 5.3.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: A320M-S2H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/28/2019:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: A320M-S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1865471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877388] Re: If DVD drive is present system very often fails to start-up
OK, I've installed those (at first I kept trying and failing to install https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7-rc5/linux-image- unsigned-5.7.0-050700rc5-generic_5.7.0-050700rc5.202005101931_amd64.deb , but it worked once I installed https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.7-rc5/linux- modules-5.7.0-050700rc5-generic_5.7.0-050700rc5.202005101931_amd64.deb first ) What next? Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877388 Title: If DVD drive is present system very often fails to start-up Status in linux package in Ubuntu: Incomplete Bug description: Whenever I power down, upon next boot the system just hangs with Ubuntu at the bottom of the screen and the circle above going around and around forever. It happens nearly every ime I power down, but not every single time. Rebooting rather that powering down works quite often. At first when thing hung I would just hard power off by holding down the power key. Then I'd use the live usb I installed with to run Disks app. More often than not the vfat W95 FAT32 partition at sda1 was damaged. The first repair would fail. The second repair would succeed. And then I'd be able to boot into my system again. After chatting about it a little with EriC^^ in #ubuntu on IRC I learned how to do Alt+Fn+PrtSc S, U, B or S, U, O. Sometimes just doing either of those on the hang screen would result in it booting up fine next time. Sometimes not. After installing 20.04 (a fresh install on a brand new Samsung 860 EVO 1TB sdd hard drive) I copied back all the files in my home direct that I'd backed from 18.04, including hidden files. This confused Firefox so I had to delete related folders and then unintall and reinstall to stop Firefox being confused. This might have nothing whatsoever to do with this issue, just mentioning it just in case something else is similarly confused. EriC^^ suggested I try adding another user and seeing if the issue went away. On the first test (and some but not all subsequent tests) it did seem that TestUser could power down and reboot fine. But actually it didn't seem that different. I powered down, rebooted, used live usb to repair Disk over and over again for hours trying to find a pattern as to when it happened and when it didn't, but failed to find any fixed pattern. Eventually at one point it was taking a while to power down (or reboot, I forget) and so I hit Esc and spotted that it had failed to unmount /cdrom ... ... so then I thought I'd try completely removing my DVD/CDRW drive and that made the issue go away. Before filing this I put the DVD drive back in (but haven't since rebooted), so not sure if apport has picked up it's details or not? Perhaps I'll need to re-file the bug after booting with it present? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: plymouth 0.9.4git20200323-0ubuntu6 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 7 15:09:23 2020 DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth InstallationDate: Installed on 2020-04-26 (11 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 147e:2016 Upek Biometric Touchchip/Touchstrip Fingerprint Sensor Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M |__ Port 3: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M MachineType: LENOVO 4384WCV ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=9ce94e7a-53bd-4507-ae31-93a2392b2da2 ro quiet splash vt.handoff=7 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=9ce94e7a-53bd-4507-ae31-93a2392b2da2 ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2010 dmi.bios.vendor: LENOVO dmi.bios.ve
[Kernel-packages] [Bug 1879690] Re: Docker registry doesn't stay up and keeps restarting
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879690 Title: Docker registry doesn't stay up and keeps restarting Status in linux package in Ubuntu: Incomplete Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: [Impact] The change applied for bug 1857257 and its followup fix bug 1876645, which were released on focal and eoan -updates, introduced a regression on overlayfs, breaking docker snap. [Test case] See original bug report. [Fix] While we don't have a final fix the solution for now is to revert the following commits: UBUNTU: SAUCE: overlayfs: fix shitfs special-casing UBUNTU: SAUCE: overlayfs: use shiftfs hacks only with shiftfs as underlay [Regression potential] Low. Reverting these two commits will introduce back the issue reported on bug 1857257, but will fix the other use cases which was broken by the latest release. Original bug report. --- Tested kernels: Focal 5.4.0-31.35 Eoan 5.3.0-53.47 To reproduce: 1) Spin up a cloud image 2) snap install docker 3) auth_folder=/var/snap/docker/common/auth 4) mkdir -p $auth_folder 5) docker run --entrypoint htpasswd registry:2 -Bbn user passwd > $auth_folder/htpasswd 6) docker run -d -p 5000:5000 --restart=always --name registry \ -v $auth_folder:/auth \ -e "REGISTRY_AUTH=htpasswd" \ -e "REGISTRY_AUTH_HTPASSWD_REALM=Registry Realm" \ -e REGISTRY_AUTH_HTPASSWD_PATH=/auth/htpasswd \ registry:2 On a good kernel 'docker ps' shows something like: # docker ps CONTAINER IDIMAGE COMMAND CREATED STATUS PORTSNAMES a346b65b4509registry:2 "/entrypoint.sh /etc…" 14 seconds ago Up 12 seconds 0.0.0.0:5000->5000/tcp registry On a bad kernel: docker ps CONTAINER IDIMAGE COMMAND CREATED STATUSPORTS NAMES 0322374f1b1dregistry:2 "/entrypoint.sh /etc…" 5 seconds ago Restarting (2) 1 second ago registry Note status 'Restarting' on the bad kernel. This seems to be introduce by any of the following commits: b3bdda24f1bc UBUNTU: SAUCE: overlayfs: fix shitfs special-casing 6f18a8434050 UBUNTU: SAUCE: overlayfs: use shiftfs hacks only with shiftfs as underlay 629edd70891c UBUNTU: SAUCE: shiftfs: record correct creator credentials cfaa482afb97 UBUNTU: SAUCE: shiftfs: fix dentry revalidation Kernels that don't have these commits seem fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879690/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878484] Re: kernel panic on i915
It still crashes on 5.4.0-31-generic #35-Ubuntu I'm still looking for that damm __i915_schedule+0x261/0x350, still haven't been able to pinpoint that to code. [ 9640.917215] BUG: kernel NULL pointer dereference, address: 00e0 [ 9640.917262] #PF: supervisor read access in kernel mode [ 9640.917277] #PF: error_code(0x) - not-present page [ 9640.917289] PGD 0 P4D 0 [ 9640.917310] Oops: [#1] SMP PTI [ 9640.917336] CPU: 2 PID: 1397 Comm: Xorg Tainted: P O 5.4.0-31-generic #35-Ubuntu [ 9640.917351] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./N3700-ITX, BIOS P2.00 04/16/2018 [ 9640.917585] RIP: 0010:__i915_schedule+0x261/0x350 [i915] [ 9640.917605] Code: ff a8 08 0f 84 a0 00 00 00 45 3b b4 24 18 04 00 00 7e 50 49 8b 84 24 d8 03 00 00 48 8b 00 48 85 c0 74 40 48 8b b3 30 ff ff ff <48> 39 70 60 74 33 45 89 b4 24 18 04 00 00 8b 80 60 01 00 00 be 00 [ 9640.917619] RSP: 0018:c100f9e0 EFLAGS: 00010002 [ 9640.917635] RAX: 0080 RBX: 9d871d4dfab0 RCX: 9d871d4dfab0 [ 9640.917647] RDX: 9d871d4dfad0 RSI: 9d882b71d180 RDI: 9d871d4dfab0 [ 9640.917660] RBP: c100fa78 R08: c100f9c0 R09: 9d871d4dc420 [ 9640.917673] R10: R11: 0208 R12: 9d8834dec000 [ 9640.917687] R13: c100f9f0 R14: 1000 R15: c100fa00 [ 9640.917702] FS: 7f283650ba80() GS:9d883830() knlGS: [ 9640.917715] CS: 0010 DS: ES: CR0: 80050033 [ 9640.917727] CR2: 00e0 CR3: 000272a98000 CR4: 001006e0 [ 9640.917740] Call Trace: [ 9640.917946] ? intel_compute_aligned_offset+0x120/0x170 [i915] [ 9640.918001] i915_schedule+0x2d/0x50 [i915] [ 9640.918053] __fence_set_priority+0x6b/0x90 [i915] [ 9640.918238] fence_set_priority+0x23/0x60 [i915] [ 9640.918374] i915_gem_object_wait_priority+0x13e/0x170 [i915] [ 9640.918429] intel_prepare_plane_fb+0x1ab/0x2d0 [i915] [ 9640.918464] drm_atomic_helper_prepare_planes+0x94/0x120 [drm_kms_helper] [ 9640.918518] intel_atomic_commit+0xc2/0x2b0 [i915] [ 9640.918574] drm_atomic_nonblocking_commit+0x4d/0x60 [drm] [ 9640.918592] drm_atomic_helper_page_flip+0x63/0xa0 [drm_kms_helper] [ 9640.918617] drm_mode_page_flip_ioctl+0x59d/0x630 [drm] [ 9640.918641] ? drm_mode_cursor2_ioctl+0x10/0x10 [drm] [ 9640.918661] drm_ioctl_kernel+0xae/0xf0 [drm] [ 9640.918682] drm_ioctl+0x234/0x3d0 [drm] [ 9640.918706] ? drm_mode_cursor2_ioctl+0x10/0x10 [drm] [ 9640.918719] do_vfs_ioctl+0x407/0x670 [ 9640.918730] ? fput+0x13/0x15 [ 9640.918741] ? __sys_recvmsg+0x88/0xa0 [ 9640.918748] ksys_ioctl+0x67/0x90 [ 9640.918754] __x64_sys_ioctl+0x1a/0x20 [ 9640.918763] do_syscall_64+0x57/0x190 [ 9640.918773] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 9640.918781] RIP: 0033:0x7f283686937b [ 9640.918788] Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48 [ 9640.918794] RSP: 002b:7ffce75d29b8 EFLAGS: 0246 ORIG_RAX: 0010 [ 9640.918799] RAX: ffda RBX: 7ffce75d29f0 RCX: 7f283686937b [ 9640.918804] RDX: 7ffce75d29f0 RSI: c01864b0 RDI: 000e [ 9640.918808] RBP: c01864b0 R08: 000dac7e R09: 006c [ 9640.918813] R10: 000e R11: 0246 R12: 55d8a2a4e040 [ 9640.918817] R13: 000e R14: 000dac7e R15: 0002 [ 9640.918823] Modules linked in: bnep wireguard(O) ip6_udp_tunnel udp_tunnel binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) input_leds joydev nls_iso8859_1 snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep snd_pcm intel_rapl_msr mei_hdcp snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq intel_rapl_common intel_powerclamp coretemp kvm_intel snd_seq_device kvm snd_timer punit_atom_debug intel_cstate snd hci_uart mei_txe btqca btrtl mei btbcm btintel soundcore intel_xhci_usb_role_switch roles bluetooth ecdh_generic ecc mac_hid rfkill_gpio acpi_pad intel_int0002_vgpio sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 dm_crypt netconsole hid_logitech_hidpp hid_logitech_dj hid_generic usbhid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel uas usb_storage i915 aesni_intel crypto_simd i2c_algo_bit cryptd glue_helper drm_kms_helper i2c_i801 [ 9640.918894] syscopyarea sysfillrect lpc_ich sysimgblt r8169 fb_sys_fops realtek drm ahci libahci video i2c_hid hid [ 9640.918920] CR2: 00e0 [ 9640.918934] ---[ end trace afb51e7987093d9b ]--- [ 9640.918999] RIP: 0010:__i915_schedule+0x261/0x350 [i915] [ 9640.919004] Code: ff a8 08 0f 84 a0 00 00 00 45 3b b4 24 18 04 00 00 7e 50 49 8b 84 24 d8 03 00 00 48 8b 00 48 85 c0 74 40 48 8b b3 30 ff ff ff <48> 39 7
[Kernel-packages] [Bug 1860724] Re: QLogic Direct-Connect host can't discover SCSI-FC or NVMe/FC devices
I am still seeing this with Ubuntu 20.04 LTS -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860724 Title: QLogic Direct-Connect host can't discover SCSI-FC or NVMe/FC devices Status in linux package in Ubuntu: Confirmed Bug description: My QLogic direct-connect host can't seem to SANboot or see any SCSI-FC devices in general. I'm also not able to discover any NVMe devices. I'm running with Ubuntu 20.04 kernel-5.4.0-9-generic. There are the HBAs I'm running with: root@ICTM1610S01H4:~# cat /sys/class/fc_host/host*/symbolic_name QLE2742 FW:v8.08.231 DVR:v10.01.00.19-k QLE2742 FW:v8.08.231 DVR:v10.01.00.19-k QLE2692 FW:v8.08.231 DVR:v10.01.00.19-k QLE2692 FW:v8.08.231 DVR:v10.01.00.19-k lsscsi and multipath -ll don't seem to see my SCSI devices: root@ICTM1610S01H4:/opt/iop/linux/scratch# multipath -ll root@ICTM1610S01H4:/opt/iop/linux/scratch# lsscsi [0:0:0:0]cd/dvd KVM vmDisk-CD0.01 /dev/sr0 [1:0:0:0]cd/dvd HL-DT-ST DVDRAM GUD0N PF02 /dev/sr1 [3:0:0:0]diskATA ST1000NX0313 SNA3 /dev/sda It doesn't appear to be a configuration/hardware issue as installing Ubuntu 18.04 on the same exact server is able to SANboot and see my SCSI devices. root@ICTM1610S01H4:/opt/iop/linux/scratch# lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 root@ICTM1610S01H4:/opt/iop/linux/scratch# apt-cache policy linux-image-generic linux-image-generic: Installed: 5.4.0.9.11 Candidate: 5.4.0.9.11 Version table: *** 5.4.0.9.11 500 500 http://repomirror-ict.eng.netapp.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-generic 5.4.0.9.11 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 23 11:32 seq crw-rw 1 root audio 116, 33 Jan 23 11:32 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 23 15:04:42 2020 InstallationDate: Installed on 2020-01-23 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200107) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: FUJITSU PRIMERGY RX2540 M4 PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=9b9e6b1a-b8d9-4d9c-8782-36729d7f88a4 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/25/2019 dmi.bios.vendor: FUJITSU // American Megatrends Inc. dmi.bios.version: V5.0.0.12 R1.35.0 for D3384-A1x dmi.board.name: D3384-A1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D3384-A13 WGS04 GS04 dmi.chassis.asset.tag: System Asset Tag dmi.chassis.type: 23 dmi.chassis.vendor: FUJITSU dmi.chassis.version: RX2540M4R4 dmi.modalias: dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.12R1.35.0forD3384-A1x:bd06/25/2019:svnFUJITSU:pnPRIMERGYRX2540M4:pvr:rvnFUJITSU:rnD3384-A1:rvrS26361-D3384-A13WGS04GS04:cvnFUJITSU:ct23:cvrRX2540M4R4: dmi.product.family: SERVER dmi.product.name: PRIMERGY RX2540 M4 dmi.product.sku: S26361-K1567-Vxxx dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860724/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878726] Re: Live USB Installer not working Samsung Notebook 9 Pro 15"
@kaihengfeng, not sure how to capture dmesg, as the boot process never completes preventing me from accessing a command line. Also, I am unable to switch to another TTY session. Can you please provide guidance or direct me to a article that explains how to capture the log? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878726 Title: Live USB Installer not working Samsung Notebook 9 Pro 15" Status in linux package in Ubuntu: Incomplete Bug description: Live USB made from ubuntu-20.04-desktop-amd64 fails to boot. System hangs with watchdog: BUG: soft lockup - CPU# and rcu: INFO: rcu_sched self-detected stall on CPU. System specs: Intel(R) i7-7500U running AMD discrete graphics Have tested the Live USB on other systems with no problems, appears to be hardware related with the Samsung Notebook 9 Pro and other systems (Dell, etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878726/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860724] Re: QLogic Direct-Connect host can't discover SCSI-FC or NVMe/FC devices
I've never used a complex setup like this, so I have to ask, are we sure it's kernel bug? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860724 Title: QLogic Direct-Connect host can't discover SCSI-FC or NVMe/FC devices Status in linux package in Ubuntu: Confirmed Bug description: My QLogic direct-connect host can't seem to SANboot or see any SCSI-FC devices in general. I'm also not able to discover any NVMe devices. I'm running with Ubuntu 20.04 kernel-5.4.0-9-generic. There are the HBAs I'm running with: root@ICTM1610S01H4:~# cat /sys/class/fc_host/host*/symbolic_name QLE2742 FW:v8.08.231 DVR:v10.01.00.19-k QLE2742 FW:v8.08.231 DVR:v10.01.00.19-k QLE2692 FW:v8.08.231 DVR:v10.01.00.19-k QLE2692 FW:v8.08.231 DVR:v10.01.00.19-k lsscsi and multipath -ll don't seem to see my SCSI devices: root@ICTM1610S01H4:/opt/iop/linux/scratch# multipath -ll root@ICTM1610S01H4:/opt/iop/linux/scratch# lsscsi [0:0:0:0]cd/dvd KVM vmDisk-CD0.01 /dev/sr0 [1:0:0:0]cd/dvd HL-DT-ST DVDRAM GUD0N PF02 /dev/sr1 [3:0:0:0]diskATA ST1000NX0313 SNA3 /dev/sda It doesn't appear to be a configuration/hardware issue as installing Ubuntu 18.04 on the same exact server is able to SANboot and see my SCSI devices. root@ICTM1610S01H4:/opt/iop/linux/scratch# lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 root@ICTM1610S01H4:/opt/iop/linux/scratch# apt-cache policy linux-image-generic linux-image-generic: Installed: 5.4.0.9.11 Candidate: 5.4.0.9.11 Version table: *** 5.4.0.9.11 500 500 http://repomirror-ict.eng.netapp.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-generic 5.4.0.9.11 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 23 11:32 seq crw-rw 1 root audio 116, 33 Jan 23 11:32 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 23 15:04:42 2020 InstallationDate: Installed on 2020-01-23 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200107) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: FUJITSU PRIMERGY RX2540 M4 PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=9b9e6b1a-b8d9-4d9c-8782-36729d7f88a4 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/25/2019 dmi.bios.vendor: FUJITSU // American Megatrends Inc. dmi.bios.version: V5.0.0.12 R1.35.0 for D3384-A1x dmi.board.name: D3384-A1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D3384-A13 WGS04 GS04 dmi.chassis.asset.tag: System Asset Tag dmi.chassis.type: 23 dmi.chassis.vendor: FUJITSU dmi.chassis.version: RX2540M4R4 dmi.modalias: dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.12R1.35.0forD3384-A1x:bd06/25/2019:svnFUJITSU:pnPRIMERGYRX2540M4:pvr:rvnFUJITSU:rnD3384-A1:rvrS26361-D3384-A13WGS04GS04:cvnFUJITSU:ct23:cvrRX2540M4R4: dmi.product.family: SERVER dmi.product.name: PRIMERGY RX2540 M4 dmi.product.sku: S26361-K1567-Vxxx dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860724/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867686] Re: FC hosts become unresponsive during array upgrade
Is this dupe of #1860724? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867686 Title: FC hosts become unresponsive during array upgrade Status in linux package in Ubuntu: Confirmed Bug description: While running automated array upgrade, my FC hosts become unresponsive and / or stop logging . Sometimes the host stop logging to /var/log/syslog, but I can still SSH into the host. Sometimes I try to SSH to the host in the middle of the test and it'll prompt me for a username that I then input, but it hangs there indefinitely and I have to power cycle the host. Other times my host becomes completely unresponsive and I can't SSH into the host and have to power cycle in order to gain access again. I thought the host might be crashing, but I'm not seeing any file get generated in /var/crash. I also thought my hosts might be going to sleep or hibernating, but I ran "sudo systemctl mask sleep.target suspend.target hibernate.target hybrid- sleep.target" and am not seeing any improvements. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867686/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878718] Re: HP ZBook 15 G6 display key (Fn+F1) autorepeats too fast to be usable
a) When I do a short press, then immediately after a release, the next option is selected (the dialog does not have time to appear even). b) When I do a long press, then the options start to circle very quickly until I release the key (see the screencast) I think the bug is caused by this: When you do Super+K, you hold Super and press K repeatedly to switch the options. After you release the Super key, the option is confirmed. When you use the fn key, there is just one key, so after releasing, it immediately selects the option. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878718 Title: HP ZBook 15 G6 display key (Fn+F1) autorepeats too fast to be usable Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: New Bug description: Steps to reproduce: 1. Press the functional button for switching output to displays (joint, mirror, bulit-in, external) 2. The dialog is invoked What is expected: I should be able to select the desired option and confirm it What happened instead: While the functional button for invoking the dialog is pressed, it iterates extremely fast over the options. I cannot control it. After releasing the key, the currently selected option is confirmed, which is effectively random. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 15 01:28:30 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117GLM [Quadro T2000 Mobile / Max-Q] [10de:1fb8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU117GLM [Quadro T2000 Mobile / Max-Q] [103c:8611] InstallationDate: Installed on 2020-05-11 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ZBook 15 G6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=9895584a-6648-494d-9d91-e64ba192dd95 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/25/2019 dmi.bios.vendor: HP dmi.bios.version: R92 Ver. 01.02.01 dmi.board.name: 860F dmi.board.vendor: HP dmi.board.version: KBC Version 65.23.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR92Ver.01.02.01:bd09/25/2019:svnHP:pnHPZBook15G6:pvr:rvnHP:rn860F:rvrKBCVersion65.23.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook 15 dmi.product.name: HP ZBook 15 G6 dmi.product.sku: 6CJ09AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878718/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879658] Re: Cannot create ipvlans with > 1500 MTU on recent Bionic kernels
Test kernel has been tested successfully so far by original reporter and has fixed the Docker breakage and so on. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879658 Title: Cannot create ipvlans with > 1500 MTU on recent Bionic kernels Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: [IMPACT] Setting an MTU larger than the default 1500 results in an error on the recent (4.15.0-92+) Bionic/Xenial -hwe kernels when attempting to create ipvlan interfaces: # ip link add test0 mtu 9000 link eno1 type ipvlan mode l2 RTNETLINK answers: Invalid argument This breaks Docker and other applications which use a Jumbo MTU (9000) when using ipvlans. The bug is caused by the following recent commit to Bionic & Xenial-hwe; which is pulled in via the stable patchset below, which enforces a strict min/max MTU when MTUs are being set up via rtnetlink for ipvlans: Breaking commit: --- Ubuntu-hwe-4.15.0-92.93~16.04.1 * Bionic update: upstream stable patchset 2020-02-21 (LP: #1864261) * net: rtnetlink: validate IFLA_MTU attribute in rtnl_create_link() The above patch applies checks of dev->min_mtu and dev->max_mtu to avoid a malicious user from crashing the kernel with a bad value. It was patching the original patchset to centralize min/max MTU checking from various different subsystems of the networking kernel. However, in that patchset, the max_mtu had not been set to the largest phys (64K) or jumbo (9000 bytes), and defaults to 1500. The recent commit above which enforces strict bounds checking for MTU size exposes the bug of the max mtu not being set correctly for the ipvlan driver (this has been previously fixed in bonding, teaming drivers). Fix: --- This was fixed in the upstream kernel as of v4.18-rc2 for ipvlans, but was not backported to Bionic along with other patches. The missing commit in the Bionic backport: ipvlan: use ETH_MAX_MTU as max mtu commit 548feb33c598dfaf9f8e066b842441ac49b84a8a [Test Case] 1. Install any kernel earlier than 4.15.0-92 (Bionic/Xenial-hwe) 2. # ip link add test1 mtu 9000 link eno1 type ipvlan mode l2 (where test1 eno1 is the physical interface you are adding the ipvlan on) 3. # ip link ... 14: test1@eno1: mtu 9000 qdisc noop state DOWN mode DEFAULT group default qlen 1000 ... // check that your test1 ipvlan is created with mtu 9000 4. Install 4.15.0-92 kernel or later 5. # ip link add test1 mtu 9000 link eno1 type ipvlan mode l2 RTNETLINK answers: Invalid argument 6. With the above fix commit backported to the xenial-hwe/Bionic, the jumbo mtu ipvlan creation works again, identical to before 92. [Regression Potential] This commit is in upstream mainline as of v4.18-rc2, and hence is already in Cosmic and later, i.e. all post Bionic releases currently. Hence there's low regression potential here. It only impacts ipvlan functionality, and not other networking systems, so core systems should not be affected by this. And affects on setup so it either works or doesn't. Patch is trivial. It only impacts Bionic/Xenial-hwe 4.15.0-92 onwards versions (where the latent bug got exposed). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879658/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860724] Re: QLogic Direct-Connect host can't discover SCSI-FC or NVMe/FC devices
I believe it's a bug with the inbox Qlogic driver -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860724 Title: QLogic Direct-Connect host can't discover SCSI-FC or NVMe/FC devices Status in linux package in Ubuntu: Confirmed Bug description: My QLogic direct-connect host can't seem to SANboot or see any SCSI-FC devices in general. I'm also not able to discover any NVMe devices. I'm running with Ubuntu 20.04 kernel-5.4.0-9-generic. There are the HBAs I'm running with: root@ICTM1610S01H4:~# cat /sys/class/fc_host/host*/symbolic_name QLE2742 FW:v8.08.231 DVR:v10.01.00.19-k QLE2742 FW:v8.08.231 DVR:v10.01.00.19-k QLE2692 FW:v8.08.231 DVR:v10.01.00.19-k QLE2692 FW:v8.08.231 DVR:v10.01.00.19-k lsscsi and multipath -ll don't seem to see my SCSI devices: root@ICTM1610S01H4:/opt/iop/linux/scratch# multipath -ll root@ICTM1610S01H4:/opt/iop/linux/scratch# lsscsi [0:0:0:0]cd/dvd KVM vmDisk-CD0.01 /dev/sr0 [1:0:0:0]cd/dvd HL-DT-ST DVDRAM GUD0N PF02 /dev/sr1 [3:0:0:0]diskATA ST1000NX0313 SNA3 /dev/sda It doesn't appear to be a configuration/hardware issue as installing Ubuntu 18.04 on the same exact server is able to SANboot and see my SCSI devices. root@ICTM1610S01H4:/opt/iop/linux/scratch# lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 root@ICTM1610S01H4:/opt/iop/linux/scratch# apt-cache policy linux-image-generic linux-image-generic: Installed: 5.4.0.9.11 Candidate: 5.4.0.9.11 Version table: *** 5.4.0.9.11 500 500 http://repomirror-ict.eng.netapp.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-generic 5.4.0.9.11 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 23 11:32 seq crw-rw 1 root audio 116, 33 Jan 23 11:32 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 23 15:04:42 2020 InstallationDate: Installed on 2020-01-23 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200107) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: FUJITSU PRIMERGY RX2540 M4 PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=9b9e6b1a-b8d9-4d9c-8782-36729d7f88a4 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/25/2019 dmi.bios.vendor: FUJITSU // American Megatrends Inc. dmi.bios.version: V5.0.0.12 R1.35.0 for D3384-A1x dmi.board.name: D3384-A1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D3384-A13 WGS04 GS04 dmi.chassis.asset.tag: System Asset Tag dmi.chassis.type: 23 dmi.chassis.vendor: FUJITSU dmi.chassis.version: RX2540M4R4 dmi.modalias: dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.12R1.35.0forD3384-A1x:bd06/25/2019:svnFUJITSU:pnPRIMERGYRX2540M4:pvr:rvnFUJITSU:rnD3384-A1:rvrS26361-D3384-A13WGS04GS04:cvnFUJITSU:ct23:cvrRX2540M4R4: dmi.product.family: SERVER dmi.product.name: PRIMERGY RX2540 M4 dmi.product.sku: S26361-K1567-Vxxx dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860724/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867686] Re: FC hosts become unresponsive during array upgrade
I don't believe so as I am able to discover SCSI devices on my Emulex fabric-attached, Emulex direct-connect, and Qlogic fabric-attached hosts before starting this test. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867686 Title: FC hosts become unresponsive during array upgrade Status in linux package in Ubuntu: Confirmed Bug description: While running automated array upgrade, my FC hosts become unresponsive and / or stop logging . Sometimes the host stop logging to /var/log/syslog, but I can still SSH into the host. Sometimes I try to SSH to the host in the middle of the test and it'll prompt me for a username that I then input, but it hangs there indefinitely and I have to power cycle the host. Other times my host becomes completely unresponsive and I can't SSH into the host and have to power cycle in order to gain access again. I thought the host might be crashing, but I'm not seeing any file get generated in /var/crash. I also thought my hosts might be going to sleep or hibernating, but I ran "sudo systemctl mask sleep.target suspend.target hibernate.target hybrid- sleep.target" and am not seeing any improvements. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867686/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871917] Re: Unable to boot 20.04 installer on Dell XPS 15 9560
Same issue on XPS 9560, 8GB USB stick. Created in Rufus from ubuntu-20.04-desktop-amd64.iso, both ISO and DD mode behave the same. Can't install 20.04 as a result. No way to collect the logs, because the laptop shuts down after disks checks and there is no interaction other than Ctrl+C to cancel disk checks and speed this up. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871917 Title: Unable to boot 20.04 installer on Dell XPS 15 9560 Status in linux package in Ubuntu: Confirmed Bug description: I tried to boot the 20.04 nightly image (focal-desktop-amd64.iso 2020-04-05 11:06 ) as well as an older one (a week ago) on my Dell XPS 15 9560, and I got the same error message each time. The live system performs a filesystem check while showing a progress bar on a screen with dell and ubuntu logo, then the linux console shows with following error: sd 2:0:0:0: [sda] tag#0 access beyond end of device blk_update_request: I/O error, dev sda, sector 30529408 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 sd 2:0:0:0: [sda] tag#0 access beyond end of device blk_update_request: I/O error, dev sda, sector 30529408 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Buffer I/O error on dev sda, logical block 3816176 async page read This happens with two different 16GB usb sticks on the Dell XPS 15. They both worked fine on an old samsung netbook. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871917/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873506] Re: ubuntu/focal64 fails to mount Vagrant shared folders
** Changed in: cloud-images Assignee: (unassigned) => John Chittum (jchittum) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873506 Title: ubuntu/focal64 fails to mount Vagrant shared folders Status in cloud-images: Confirmed Status in linux package in Ubuntu: In Progress Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: SRU Justification Impact: When our kernel packaging was updated to build the virtualbox guest packages by downloading the dkms package, the modules were accidentally moved to linux-modules-extra instead of linux-modules. This has caused the modules to go missing in our Vagrant images. Fix: Move the modules back to linux-modules. Test Case: Build the kernel packages and confirm that the vboxguest and vboxsf drivers are now in linux-modules rather than linux-modules- extra. Regression Potential: Since linux-modules is required, anyone who is using the vbox drivers will continue to have them after this change. Therefore the risk of regression is extremely low. --- Attempting to `vagrant up` using the `ubuntu/focal64` box fails to mount the `/vagrant` shared folder. `ubuntu/bionic64` works as expected. Here is the Vagrant error message: Vagrant was unable to mount VirtualBox shared folders. This is usually because the filesystem "vboxsf" is not available. This filesystem is made available via the VirtualBox Guest Additions and kernel module. Please verify that these guest additions are properly installed in the guest. This is not a bug in Vagrant and is usually caused by a faulty Vagrant box. For context, the command attempted was: mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant The error output from the command was: : No such device To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1873506/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880213] [NEW] ext2 build failure on 4.4.0-180.210
Public bug reported: [Impact] Build failure when building ext2 fs/ext2/xattr.c:828:18: error: 'ext2_xattr_cache' undeclared (first use in this function) atomic_read(&ext2_xattr_cache->c_entry_count)); [Fix] The fix is upstream commit 32302085a8d90859c40cf1a5e8313f575d06ec75 "ext2: fix debug reference to ext2_xattr_cache" [Test case] Enable CONFIG_EXT2_FS and build kernel [Regression potential] Low, fix is changing the contents of a print to a string literal. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-snapdragon (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: linux-snapdragon (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-snapdragon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1880213 Title: ext2 build failure on 4.4.0-180.210 Status in linux package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux source package in Xenial: New Status in linux-snapdragon source package in Xenial: New Bug description: [Impact] Build failure when building ext2 fs/ext2/xattr.c:828:18: error: 'ext2_xattr_cache' undeclared (first use in this function) atomic_read(&ext2_xattr_cache->c_entry_count)); [Fix] The fix is upstream commit 32302085a8d90859c40cf1a5e8313f575d06ec75 "ext2: fix debug reference to ext2_xattr_cache" [Test case] Enable CONFIG_EXT2_FS and build kernel [Regression potential] Low, fix is changing the contents of a print to a string literal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
