[Kernel-packages] [Bug 1895550] 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 1895550 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/1895550 Title: Ubuntu 18.04.5 release for Raspberry Pi 4 does not boot Status in linux package in Ubuntu: Incomplete Bug description: I have a Raspberry Pi 4 Model B. I downloaded and flashed the image `ubuntu-18.04.5-preinstalled-server-arm64+raspi4.img` (md5 = b75105bf4e27cbcc44dc471becc8907d), which is the currently recommended release for this hardware on the Ubuntu.com website. Booting reaches this point where it tries to do something with the SD card, then fails: [4.352613] random: fast init done [4.414200] mmc0: new ultra high speed DDR50 SDHC card at address [4.423077] mmcblk0: mmc0: SC32G 29.7 GiB [4.431244] mmc1: new high speed SDIO card at address 0001 [4.437267] mmcblk0: p1 p2 Afterwards, about once per minute, it outputs an error message like this: [ 28.006460] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: [ 28.012484] rcu: 1-...0: (7 ticks this GP) idle=1d6/1/0x4000 softirq=80/81 fqs=7 [ 28.021231] (detected by 3, t=5893 jiffies, g=-379, q=2) [ 28.026710] Task dump for CPU 1: [ 28.029984] swapper/0 R running task0 1 0 0x002a [ 28.037143] Call trace: [ 28.039636] __switch_to+0xcc/0x208 [ 28.043179] console_unlock+0x4f8/0x600 [ 28.047076] rcu: rcu_sched kthread starved for 1001 jiffies! g-379 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=3 [ 28.057405] rcu: RCU grace-period kthread stack dump: [ 28.062529] rcu_sched I010 2 0x0028 [ 28.068098] Call trace: [ 28.070580] __switch_to+0xcc/0x208 [ 28.074123] __schedule+0x2c4/0x7b0 [ 28.077663] schedule+0x38/0xa8 [ 28.080851] schedule_timeout+0x1a0/0x378 [ 28.084920] rcu_gp_kthread+0x688/0xa10 [ 28.088813] kthread+0x124/0x128 [ 28.092089] ret_from_fork+0x10/0x1c I made 2 or 3 attempts at this and each time it failed in the same way. The only modifications I made to the filesystem were to the `user- data` and `network-config` files for headless setup. I do not believe these modifications are relevant. I downloaded and flashed the previous release, `ubuntu-18.04.4 -preinstalled-server-arm64+raspi4.img`, and that release booted successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895550] Re: Ubuntu 18.04.5 release for Raspberry Pi 4 does not boot
Sending to the kernel team but not sure it belongs with them. ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895550 Title: Ubuntu 18.04.5 release for Raspberry Pi 4 does not boot Status in linux package in Ubuntu: New Bug description: I have a Raspberry Pi 4 Model B. I downloaded and flashed the image `ubuntu-18.04.5-preinstalled-server-arm64+raspi4.img` (md5 = b75105bf4e27cbcc44dc471becc8907d), which is the currently recommended release for this hardware on the Ubuntu.com website. Booting reaches this point where it tries to do something with the SD card, then fails: [4.352613] random: fast init done [4.414200] mmc0: new ultra high speed DDR50 SDHC card at address [4.423077] mmcblk0: mmc0: SC32G 29.7 GiB [4.431244] mmc1: new high speed SDIO card at address 0001 [4.437267] mmcblk0: p1 p2 Afterwards, about once per minute, it outputs an error message like this: [ 28.006460] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: [ 28.012484] rcu: 1-...0: (7 ticks this GP) idle=1d6/1/0x4000 softirq=80/81 fqs=7 [ 28.021231] (detected by 3, t=5893 jiffies, g=-379, q=2) [ 28.026710] Task dump for CPU 1: [ 28.029984] swapper/0 R running task0 1 0 0x002a [ 28.037143] Call trace: [ 28.039636] __switch_to+0xcc/0x208 [ 28.043179] console_unlock+0x4f8/0x600 [ 28.047076] rcu: rcu_sched kthread starved for 1001 jiffies! g-379 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=3 [ 28.057405] rcu: RCU grace-period kthread stack dump: [ 28.062529] rcu_sched I010 2 0x0028 [ 28.068098] Call trace: [ 28.070580] __switch_to+0xcc/0x208 [ 28.074123] __schedule+0x2c4/0x7b0 [ 28.077663] schedule+0x38/0xa8 [ 28.080851] schedule_timeout+0x1a0/0x378 [ 28.084920] rcu_gp_kthread+0x688/0xa10 [ 28.088813] kthread+0x124/0x128 [ 28.092089] ret_from_fork+0x10/0x1c I made 2 or 3 attempts at this and each time it failed in the same way. The only modifications I made to the filesystem were to the `user- data` and `network-config` files for headless setup. I do not believe these modifications are relevant. I downloaded and flashed the previous release, `ubuntu-18.04.4 -preinstalled-server-arm64+raspi4.img`, and that release booted successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895550] [NEW] Ubuntu 18.04.5 release for Raspberry Pi 4 does not boot
You have been subscribed to a public bug: I have a Raspberry Pi 4 Model B. I downloaded and flashed the image `ubuntu-18.04.5-preinstalled-server-arm64+raspi4.img` (md5 = b75105bf4e27cbcc44dc471becc8907d), which is the currently recommended release for this hardware on the Ubuntu.com website. Booting reaches this point where it tries to do something with the SD card, then fails: [4.352613] random: fast init done [4.414200] mmc0: new ultra high speed DDR50 SDHC card at address [4.423077] mmcblk0: mmc0: SC32G 29.7 GiB [4.431244] mmc1: new high speed SDIO card at address 0001 [4.437267] mmcblk0: p1 p2 Afterwards, about once per minute, it outputs an error message like this: [ 28.006460] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: [ 28.012484] rcu: 1-...0: (7 ticks this GP) idle=1d6/1/0x4000 softirq=80/81 fqs=7 [ 28.021231] (detected by 3, t=5893 jiffies, g=-379, q=2) [ 28.026710] Task dump for CPU 1: [ 28.029984] swapper/0 R running task0 1 0 0x002a [ 28.037143] Call trace: [ 28.039636] __switch_to+0xcc/0x208 [ 28.043179] console_unlock+0x4f8/0x600 [ 28.047076] rcu: rcu_sched kthread starved for 1001 jiffies! g-379 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=3 [ 28.057405] rcu: RCU grace-period kthread stack dump: [ 28.062529] rcu_sched I010 2 0x0028 [ 28.068098] Call trace: [ 28.070580] __switch_to+0xcc/0x208 [ 28.074123] __schedule+0x2c4/0x7b0 [ 28.077663] schedule+0x38/0xa8 [ 28.080851] schedule_timeout+0x1a0/0x378 [ 28.084920] rcu_gp_kthread+0x688/0xa10 [ 28.088813] kthread+0x124/0x128 [ 28.092089] ret_from_fork+0x10/0x1c I made 2 or 3 attempts at this and each time it failed in the same way. The only modifications I made to the filesystem were to the `user-data` and `network-config` files for headless setup. I do not believe these modifications are relevant. I downloaded and flashed the previous release, `ubuntu-18.04.4 -preinstalled-server-arm64+raspi4.img`, and that release booted successfully. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Ubuntu 18.04.5 release for Raspberry Pi 4 does not boot https://bugs.launchpad.net/bugs/1895550 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880076] Re: ubuntu 20.4 - retransmitts with r8169
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1880076 Title: ubuntu 20.4 - retransmitts with r8169 Status in linux package in Ubuntu: Expired 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
[Kernel-packages] [Bug 1895918] [NEW] linux-oem 4.15.0-1097.107 ADT test failure with linux-oem 4.15.0-1097.107
Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/linux-oem/20200917_024821_f018f@/log.gz 02:04:01 DEBUG| [stdout] selftests: rtnetlink.sh 02:04:01 DEBUG| [stdout] 02:04:01 DEBUG| [stdout] PASS: policy routing 02:04:01 DEBUG| [stdout] PASS: route get 02:04:06 DEBUG| [stdout] PASS: preferred_lft addresses have expired 02:04:06 DEBUG| [stdout] PASS: tc htb hierarchy 02:04:06 DEBUG| [stdout] PASS: gre tunnel endpoint 02:04:06 DEBUG| [stdout] PASS: bridge setup 02:04:08 DEBUG| [stdout] PASS: ipv6 addrlabel 02:04:08 DEBUG| [stdout] PASS: set ifalias d78a4e6e-399a-48fd-90f7-4e3b7a095c6a for test-dummy0 02:04:08 DEBUG| [stdout] PASS: vrf 02:04:09 DEBUG| [stdout] PASS: vxlan 02:04:09 DEBUG| [stdout] FAIL: can't add fou port , skipping test 02:04:09 DEBUG| [stdout] PASS: macsec 02:04:09 DEBUG| [stdout] not ok 1..10 selftests: rtnetlink.sh [FAIL] 02:04:09 DEBUG| [stdout] make[1]: Leaving directory '/tmp/autopkgtest.8CYYaI/build.hsO/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' 02:04:09 DEBUG| [stdout] make: Leaving directory '/tmp/autopkgtest.8CYYaI/build.hsO/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' ** Affects: linux-oem (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure ** Description changed: Testing failed on: - amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/linux-oem/20200917_024821_f018f@/log.gz + amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/linux-oem/20200917_024821_f018f@/log.gz + + + 02:04:01 DEBUG| [stdout] selftests: rtnetlink.sh + 02:04:01 DEBUG| [stdout] + 02:04:01 DEBUG| [stdout] PASS: policy routing + 02:04:01 DEBUG| [stdout] PASS: route get + 02:04:06 DEBUG| [stdout] PASS: preferred_lft addresses have expired + 02:04:06 DEBUG| [stdout] PASS: tc htb hierarchy + 02:04:06 DEBUG| [stdout] PASS: gre tunnel endpoint + 02:04:06 DEBUG| [stdout] PASS: bridge setup + 02:04:08 DEBUG| [stdout] PASS: ipv6 addrlabel + 02:04:08 DEBUG| [stdout] PASS: set ifalias d78a4e6e-399a-48fd-90f7-4e3b7a095c6a for test-dummy0 + 02:04:08 DEBUG| [stdout] PASS: vrf + 02:04:09 DEBUG| [stdout] PASS: vxlan + 02:04:09 DEBUG| [stdout] FAIL: can't add fou port , skipping test + 02:04:09 DEBUG| [stdout] PASS: macsec + 02:04:09 DEBUG| [stdout] not ok 1..10 selftests: rtnetlink.sh [FAIL] + 02:04:09 DEBUG| [stdout] make[1]: Leaving directory '/tmp/autopkgtest.8CYYaI/build.hsO/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' + 02:04:09 DEBUG| [stdout] make: Leaving directory '/tmp/autopkgtest.8CYYaI/build.hsO/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1895918 Title: linux-oem 4.15.0-1097.107 ADT test failure with linux-oem 4.15.0-1097.107 Status in linux-oem package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/linux-oem/20200917_024821_f018f@/log.gz 02:04:01 DEBUG| [stdout] selftests: rtnetlink.sh 02:04:01 DEBUG| [stdout] 02:04:01 DEBUG| [stdout] PASS: policy routing 02:04:01 DEBUG| [stdout] PASS: route get 02:04:06 DEBUG| [stdout] PASS: preferred_lft addresses have expired 02:04:06 DEBUG| [stdout] PASS: tc htb hierarchy 02:04:06 DEBUG| [stdout] PASS: gre tunnel endpoint 02:04:06 DEBUG| [stdout] PASS: bridge setup 02:04:08 DEBUG| [stdout] PASS: ipv6 addrlabel 02:04:08 DEBUG| [stdout] PASS: set ifalias d78a4e6e-399a-48fd-90f7-4e3b7a095c6a for test-dummy0 02:04:08 DEBUG| [stdout] PASS: vrf 02:04:09 DEBUG| [stdout] PASS: vxlan 02:04:09 DEBUG| [stdout] FAIL: can't add fou port , skipping test 02:04:09 DEBUG| [stdout] PASS: macsec 02:04:09 DEBUG| [stdout] not ok 1..10 selftests: rtnetlink.sh [FAIL] 02:04:09 DEBUG| [stdout] make[1]: Leaving directory '/tmp/autopkgtest.8CYYaI/build.hsO/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' 02:04:09 DEBUG| [stdout] make: Leaving directory '/tmp/autopkgtest.8CYYaI/build.hsO/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1895918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post
[Kernel-packages] [Bug 1895916] [NEW] package nvidia-dkms-440-server 440.95.01-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-440-server package post-installation script subprocess
Public bug reported: Could not install nvidia graphic s dirver 440. System specs: Ubuntu installed in 256GB ssd Description:Ubuntu 20.04.1 LTS Release:20.04 Processor: AMD® Ryzen 7 4800h with radeon graphics × 16 Graphics: AMD® Renoir / AMD® Renoir ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-440-server 440.95.01-0ubuntu0.20.04.1 Uname: Linux 5.8.9-050809-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Sep 17 08:17:57 2020 ErrorMessage: installed nvidia-dkms-440-server package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2020-09-16 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: nvidia-graphics-drivers-440-server Title: package nvidia-dkms-440-server 440.95.01-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-440-server package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-440-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440-server in Ubuntu. https://bugs.launchpad.net/bugs/1895916 Title: package nvidia-dkms-440-server 440.95.01-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-440-server package post- installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-440-server package in Ubuntu: New Bug description: Could not install nvidia graphic s dirver 440. System specs: Ubuntu installed in 256GB ssd Description: Ubuntu 20.04.1 LTS Release: 20.04 Processor: AMD® Ryzen 7 4800h with radeon graphics × 16 Graphics: AMD® Renoir / AMD® Renoir ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-440-server 440.95.01-0ubuntu0.20.04.1 Uname: Linux 5.8.9-050809-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Sep 17 08:17:57 2020 ErrorMessage: installed nvidia-dkms-440-server package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2020-09-16 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: nvidia-graphics-drivers-440-server Title: package nvidia-dkms-440-server 440.95.01-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-440-server package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440-server/+bug/1895916/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895905] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1895905/+attachment/5411518/+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/1895905 Title: lubuntu groovy; flashing of sddm greeter Status in linux package in Ubuntu: Confirmed Bug description: Lubuntu groovy QA-test install. On reboot, the login greeter (sddm) screen isn't nice, with areas of the screen flashing white/black/white/black (maybe white & black each second like a ":" might flash on the clock, only the ":" on the clock is static) likely package at fault should be xserver-xorg-video-nouveau Photo can be seen at https://photos.app.goo.gl/SYPytVxtkKBEj9NY8 The - drop down for session (not selected Lubuntu) - language drop down (not US flag) - white/black on login picture (not grey name) flashes black & white on a cycle... The top panel items will eventually stop flashing (ie. session & layout) but time or certain actions cause the flashing white then black in cycle to occur again. ** Expected Result No flashing, its irritating & potentially a problem for some with certain health conditions. ** Not new issue, it's occurred in the past hp dx6120mt (pentium 4, 3gb, winfast clone of nvidia 7600gt) I've had this issue before on eoan on hp dx6120 i believe but cannot find bug report. The bug was likely not filed as that box was i386 & support was being dropped when I noticed it so I didn't see any point. It's not new, and no doubt relates to Nvidia cards, and I'm convinced I've filed this before on dx6120 so if not eoan, disco, but I've not yet found it. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-18-generic 5.8.0-18.19 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guiverc1095 F pulseaudio /dev/snd/controlC0: guiverc1095 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Sep 17 11:13:50 2020 InstallationDate: Installed on 2021-09-17 (-365 days ago) InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916) IwConfig: lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 990 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic root=UUID=c29a66dc-4cfc-4dc1-9fe7-3c9d8a8ab4a1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-18-generic N/A linux-backports-modules-5.8.0-18-generic N/A linux-firmware1.190 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A20 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA20:bd05/05/2017:br4.6:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guiverc 950 F pulseaudio /dev/snd/controlC0: guiverc 950 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-09-17 (-365 days ago) InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916) IwConfig: lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching
[Kernel-packages] [Bug 1895905] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1895905/+attachment/5411515/+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/1895905 Title: lubuntu groovy; flashing of sddm greeter Status in linux package in Ubuntu: Confirmed Bug description: Lubuntu groovy QA-test install. On reboot, the login greeter (sddm) screen isn't nice, with areas of the screen flashing white/black/white/black (maybe white & black each second like a ":" might flash on the clock, only the ":" on the clock is static) likely package at fault should be xserver-xorg-video-nouveau Photo can be seen at https://photos.app.goo.gl/SYPytVxtkKBEj9NY8 The - drop down for session (not selected Lubuntu) - language drop down (not US flag) - white/black on login picture (not grey name) flashes black & white on a cycle... The top panel items will eventually stop flashing (ie. session & layout) but time or certain actions cause the flashing white then black in cycle to occur again. ** Expected Result No flashing, its irritating & potentially a problem for some with certain health conditions. ** Not new issue, it's occurred in the past hp dx6120mt (pentium 4, 3gb, winfast clone of nvidia 7600gt) I've had this issue before on eoan on hp dx6120 i believe but cannot find bug report. The bug was likely not filed as that box was i386 & support was being dropped when I noticed it so I didn't see any point. It's not new, and no doubt relates to Nvidia cards, and I'm convinced I've filed this before on dx6120 so if not eoan, disco, but I've not yet found it. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-18-generic 5.8.0-18.19 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guiverc1095 F pulseaudio /dev/snd/controlC0: guiverc1095 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Sep 17 11:13:50 2020 InstallationDate: Installed on 2021-09-17 (-365 days ago) InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916) IwConfig: lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 990 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic root=UUID=c29a66dc-4cfc-4dc1-9fe7-3c9d8a8ab4a1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-18-generic N/A linux-backports-modules-5.8.0-18-generic N/A linux-firmware1.190 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A20 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA20:bd05/05/2017:br4.6:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guiverc 950 F pulseaudio /dev/snd/controlC0: guiverc 950 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-09-17 (-365 days ago) InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916) IwConfig: lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matc
[Kernel-packages] [Bug 1895905] Re: lubuntu groovy; flashing of sddm greeter
I'll note https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1865837 "Lubuntu 20.04 qa-test install; flashing at sddm greeter when mouse at top panel (pre-login)" which reads very similar, maybe even same cause (similar pattern at least in flashing), but occurs different positions on the screen. This was not the duplicate I'm hunting for... ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895905 Title: lubuntu groovy; flashing of sddm greeter Status in linux package in Ubuntu: Confirmed Bug description: Lubuntu groovy QA-test install. On reboot, the login greeter (sddm) screen isn't nice, with areas of the screen flashing white/black/white/black (maybe white & black each second like a ":" might flash on the clock, only the ":" on the clock is static) likely package at fault should be xserver-xorg-video-nouveau Photo can be seen at https://photos.app.goo.gl/SYPytVxtkKBEj9NY8 The - drop down for session (not selected Lubuntu) - language drop down (not US flag) - white/black on login picture (not grey name) flashes black & white on a cycle... The top panel items will eventually stop flashing (ie. session & layout) but time or certain actions cause the flashing white then black in cycle to occur again. ** Expected Result No flashing, its irritating & potentially a problem for some with certain health conditions. ** Not new issue, it's occurred in the past hp dx6120mt (pentium 4, 3gb, winfast clone of nvidia 7600gt) I've had this issue before on eoan on hp dx6120 i believe but cannot find bug report. The bug was likely not filed as that box was i386 & support was being dropped when I noticed it so I didn't see any point. It's not new, and no doubt relates to Nvidia cards, and I'm convinced I've filed this before on dx6120 so if not eoan, disco, but I've not yet found it. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-18-generic 5.8.0-18.19 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guiverc1095 F pulseaudio /dev/snd/controlC0: guiverc1095 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Sep 17 11:13:50 2020 InstallationDate: Installed on 2021-09-17 (-365 days ago) InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916) IwConfig: lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 990 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic root=UUID=c29a66dc-4cfc-4dc1-9fe7-3c9d8a8ab4a1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-18-generic N/A linux-backports-modules-5.8.0-18-generic N/A linux-firmware1.190 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A20 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA20:bd05/05/2017:br4.6:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guiverc 950 F pulseaudio /dev/snd/controlC0: guiverc 950 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-09-17 (-365 days ago) InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916) IwConfig: lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus
[Kernel-packages] [Bug 1895905] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1895905/+attachment/5411510/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895905 Title: lubuntu groovy; flashing of sddm greeter Status in linux package in Ubuntu: Confirmed Bug description: Lubuntu groovy QA-test install. On reboot, the login greeter (sddm) screen isn't nice, with areas of the screen flashing white/black/white/black (maybe white & black each second like a ":" might flash on the clock, only the ":" on the clock is static) likely package at fault should be xserver-xorg-video-nouveau Photo can be seen at https://photos.app.goo.gl/SYPytVxtkKBEj9NY8 The - drop down for session (not selected Lubuntu) - language drop down (not US flag) - white/black on login picture (not grey name) flashes black & white on a cycle... The top panel items will eventually stop flashing (ie. session & layout) but time or certain actions cause the flashing white then black in cycle to occur again. ** Expected Result No flashing, its irritating & potentially a problem for some with certain health conditions. ** Not new issue, it's occurred in the past hp dx6120mt (pentium 4, 3gb, winfast clone of nvidia 7600gt) I've had this issue before on eoan on hp dx6120 i believe but cannot find bug report. The bug was likely not filed as that box was i386 & support was being dropped when I noticed it so I didn't see any point. It's not new, and no doubt relates to Nvidia cards, and I'm convinced I've filed this before on dx6120 so if not eoan, disco, but I've not yet found it. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-18-generic 5.8.0-18.19 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guiverc1095 F pulseaudio /dev/snd/controlC0: guiverc1095 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Sep 17 11:13:50 2020 InstallationDate: Installed on 2021-09-17 (-365 days ago) InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916) IwConfig: lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 990 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic root=UUID=c29a66dc-4cfc-4dc1-9fe7-3c9d8a8ab4a1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-18-generic N/A linux-backports-modules-5.8.0-18-generic N/A linux-firmware1.190 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A20 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA20:bd05/05/2017:br4.6:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guiverc 950 F pulseaudio /dev/snd/controlC0: guiverc 950 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-09-17 (-365 days ago) InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916) IwConfig: lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching
[Kernel-packages] [Bug 1895905] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1895905/+attachment/5411514/+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/1895905 Title: lubuntu groovy; flashing of sddm greeter Status in linux package in Ubuntu: Confirmed Bug description: Lubuntu groovy QA-test install. On reboot, the login greeter (sddm) screen isn't nice, with areas of the screen flashing white/black/white/black (maybe white & black each second like a ":" might flash on the clock, only the ":" on the clock is static) likely package at fault should be xserver-xorg-video-nouveau Photo can be seen at https://photos.app.goo.gl/SYPytVxtkKBEj9NY8 The - drop down for session (not selected Lubuntu) - language drop down (not US flag) - white/black on login picture (not grey name) flashes black & white on a cycle... The top panel items will eventually stop flashing (ie. session & layout) but time or certain actions cause the flashing white then black in cycle to occur again. ** Expected Result No flashing, its irritating & potentially a problem for some with certain health conditions. ** Not new issue, it's occurred in the past hp dx6120mt (pentium 4, 3gb, winfast clone of nvidia 7600gt) I've had this issue before on eoan on hp dx6120 i believe but cannot find bug report. The bug was likely not filed as that box was i386 & support was being dropped when I noticed it so I didn't see any point. It's not new, and no doubt relates to Nvidia cards, and I'm convinced I've filed this before on dx6120 so if not eoan, disco, but I've not yet found it. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-18-generic 5.8.0-18.19 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guiverc1095 F pulseaudio /dev/snd/controlC0: guiverc1095 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Sep 17 11:13:50 2020 InstallationDate: Installed on 2021-09-17 (-365 days ago) InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916) IwConfig: lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 990 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic root=UUID=c29a66dc-4cfc-4dc1-9fe7-3c9d8a8ab4a1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-18-generic N/A linux-backports-modules-5.8.0-18-generic N/A linux-firmware1.190 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A20 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA20:bd05/05/2017:br4.6:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guiverc 950 F pulseaudio /dev/snd/controlC0: guiverc 950 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-09-17 (-365 days ago) InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916) IwConfig: lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp.
[Kernel-packages] [Bug 1895905] Re: lubuntu groovy; flashing of sddm greeter
apport information ** Tags added: apport-collected ** Description changed: Lubuntu groovy QA-test install. On reboot, the login greeter (sddm) screen isn't nice, with areas of the screen flashing white/black/white/black (maybe white & black each second like a ":" might flash on the clock, only the ":" on the clock is static) likely package at fault should be xserver-xorg-video-nouveau Photo can be seen at https://photos.app.goo.gl/SYPytVxtkKBEj9NY8 The - drop down for session (not selected Lubuntu) - language drop down (not US flag) - white/black on login picture (not grey name) flashes black & white on a cycle... The top panel items will eventually stop flashing (ie. session & layout) but time or certain actions cause the flashing white then black in cycle to occur again. ** Expected Result No flashing, its irritating & potentially a problem for some with certain health conditions. ** Not new issue, it's occurred in the past hp dx6120mt (pentium 4, 3gb, winfast clone of nvidia 7600gt) I've had this issue before on eoan on hp dx6120 i believe but cannot find bug report. The bug was likely not filed as that box was i386 & support was being dropped when I noticed it so I didn't see any point. It's not new, and no doubt relates to Nvidia cards, and I'm convinced I've filed this before on dx6120 so if not eoan, disco, but I've not yet found it. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-18-generic 5.8.0-18.19 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guiverc1095 F pulseaudio /dev/snd/controlC0: guiverc1095 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Sep 17 11:13:50 2020 InstallationDate: Installed on 2021-09-17 (-365 days ago) InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916) IwConfig: lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 990 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic root=UUID=c29a66dc-4cfc-4dc1-9fe7-3c9d8a8ab4a1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-18-generic N/A linux-backports-modules-5.8.0-18-generic N/A linux-firmware1.190 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A20 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA20:bd05/05/2017:br4.6:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu45 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: guiverc 950 F pulseaudio + /dev/snd/controlC0: guiverc 950 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: LXQt + CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted + DistroRelease: Ubuntu 20.10 + InstallationDate: Installed on 2021-09-17 (-365 days ago) + InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916) + IwConfig: + lono wireless extensions. + + eno1 no wireless extensions. + Lsusb: + Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver + Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub + Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: Dell Inc. OptiPlex 990 + Package: linux (not installed) + ProcFB: 0 nouveaudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic root=UUID=c29a66dc-4cfc-4dc1-9fe7-3c9d8a8ab4a1 ro quiet splash vt.handof
[Kernel-packages] [Bug 1895905] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1895905/+attachment/5411513/+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/1895905 Title: lubuntu groovy; flashing of sddm greeter Status in linux package in Ubuntu: Confirmed Bug description: Lubuntu groovy QA-test install. On reboot, the login greeter (sddm) screen isn't nice, with areas of the screen flashing white/black/white/black (maybe white & black each second like a ":" might flash on the clock, only the ":" on the clock is static) likely package at fault should be xserver-xorg-video-nouveau Photo can be seen at https://photos.app.goo.gl/SYPytVxtkKBEj9NY8 The - drop down for session (not selected Lubuntu) - language drop down (not US flag) - white/black on login picture (not grey name) flashes black & white on a cycle... The top panel items will eventually stop flashing (ie. session & layout) but time or certain actions cause the flashing white then black in cycle to occur again. ** Expected Result No flashing, its irritating & potentially a problem for some with certain health conditions. ** Not new issue, it's occurred in the past hp dx6120mt (pentium 4, 3gb, winfast clone of nvidia 7600gt) I've had this issue before on eoan on hp dx6120 i believe but cannot find bug report. The bug was likely not filed as that box was i386 & support was being dropped when I noticed it so I didn't see any point. It's not new, and no doubt relates to Nvidia cards, and I'm convinced I've filed this before on dx6120 so if not eoan, disco, but I've not yet found it. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-18-generic 5.8.0-18.19 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guiverc1095 F pulseaudio /dev/snd/controlC0: guiverc1095 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Sep 17 11:13:50 2020 InstallationDate: Installed on 2021-09-17 (-365 days ago) InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916) IwConfig: lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 990 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic root=UUID=c29a66dc-4cfc-4dc1-9fe7-3c9d8a8ab4a1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-18-generic N/A linux-backports-modules-5.8.0-18-generic N/A linux-firmware1.190 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A20 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA20:bd05/05/2017:br4.6:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guiverc 950 F pulseaudio /dev/snd/controlC0: guiverc 950 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-09-17 (-365 days ago) InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916) IwConfig: lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matc
[Kernel-packages] [Bug 1895905] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1895905/+attachment/5411516/+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/1895905 Title: lubuntu groovy; flashing of sddm greeter Status in linux package in Ubuntu: Confirmed Bug description: Lubuntu groovy QA-test install. On reboot, the login greeter (sddm) screen isn't nice, with areas of the screen flashing white/black/white/black (maybe white & black each second like a ":" might flash on the clock, only the ":" on the clock is static) likely package at fault should be xserver-xorg-video-nouveau Photo can be seen at https://photos.app.goo.gl/SYPytVxtkKBEj9NY8 The - drop down for session (not selected Lubuntu) - language drop down (not US flag) - white/black on login picture (not grey name) flashes black & white on a cycle... The top panel items will eventually stop flashing (ie. session & layout) but time or certain actions cause the flashing white then black in cycle to occur again. ** Expected Result No flashing, its irritating & potentially a problem for some with certain health conditions. ** Not new issue, it's occurred in the past hp dx6120mt (pentium 4, 3gb, winfast clone of nvidia 7600gt) I've had this issue before on eoan on hp dx6120 i believe but cannot find bug report. The bug was likely not filed as that box was i386 & support was being dropped when I noticed it so I didn't see any point. It's not new, and no doubt relates to Nvidia cards, and I'm convinced I've filed this before on dx6120 so if not eoan, disco, but I've not yet found it. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-18-generic 5.8.0-18.19 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guiverc1095 F pulseaudio /dev/snd/controlC0: guiverc1095 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Sep 17 11:13:50 2020 InstallationDate: Installed on 2021-09-17 (-365 days ago) InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916) IwConfig: lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 990 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic root=UUID=c29a66dc-4cfc-4dc1-9fe7-3c9d8a8ab4a1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-18-generic N/A linux-backports-modules-5.8.0-18-generic N/A linux-firmware1.190 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A20 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA20:bd05/05/2017:br4.6:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guiverc 950 F pulseaudio /dev/snd/controlC0: guiverc 950 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-09-17 (-365 days ago) InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916) IwConfig: lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate
[Kernel-packages] [Bug 1895905] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1895905/+attachment/5411520/+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/1895905 Title: lubuntu groovy; flashing of sddm greeter Status in linux package in Ubuntu: Confirmed Bug description: Lubuntu groovy QA-test install. On reboot, the login greeter (sddm) screen isn't nice, with areas of the screen flashing white/black/white/black (maybe white & black each second like a ":" might flash on the clock, only the ":" on the clock is static) likely package at fault should be xserver-xorg-video-nouveau Photo can be seen at https://photos.app.goo.gl/SYPytVxtkKBEj9NY8 The - drop down for session (not selected Lubuntu) - language drop down (not US flag) - white/black on login picture (not grey name) flashes black & white on a cycle... The top panel items will eventually stop flashing (ie. session & layout) but time or certain actions cause the flashing white then black in cycle to occur again. ** Expected Result No flashing, its irritating & potentially a problem for some with certain health conditions. ** Not new issue, it's occurred in the past hp dx6120mt (pentium 4, 3gb, winfast clone of nvidia 7600gt) I've had this issue before on eoan on hp dx6120 i believe but cannot find bug report. The bug was likely not filed as that box was i386 & support was being dropped when I noticed it so I didn't see any point. It's not new, and no doubt relates to Nvidia cards, and I'm convinced I've filed this before on dx6120 so if not eoan, disco, but I've not yet found it. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-18-generic 5.8.0-18.19 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guiverc1095 F pulseaudio /dev/snd/controlC0: guiverc1095 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Sep 17 11:13:50 2020 InstallationDate: Installed on 2021-09-17 (-365 days ago) InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916) IwConfig: lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 990 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic root=UUID=c29a66dc-4cfc-4dc1-9fe7-3c9d8a8ab4a1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-18-generic N/A linux-backports-modules-5.8.0-18-generic N/A linux-firmware1.190 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A20 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA20:bd05/05/2017:br4.6:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guiverc 950 F pulseaudio /dev/snd/controlC0: guiverc 950 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-09-17 (-365 days ago) InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916) IwConfig: lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching
[Kernel-packages] [Bug 1895905] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1895905/+attachment/5411517/+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/1895905 Title: lubuntu groovy; flashing of sddm greeter Status in linux package in Ubuntu: Confirmed Bug description: Lubuntu groovy QA-test install. On reboot, the login greeter (sddm) screen isn't nice, with areas of the screen flashing white/black/white/black (maybe white & black each second like a ":" might flash on the clock, only the ":" on the clock is static) likely package at fault should be xserver-xorg-video-nouveau Photo can be seen at https://photos.app.goo.gl/SYPytVxtkKBEj9NY8 The - drop down for session (not selected Lubuntu) - language drop down (not US flag) - white/black on login picture (not grey name) flashes black & white on a cycle... The top panel items will eventually stop flashing (ie. session & layout) but time or certain actions cause the flashing white then black in cycle to occur again. ** Expected Result No flashing, its irritating & potentially a problem for some with certain health conditions. ** Not new issue, it's occurred in the past hp dx6120mt (pentium 4, 3gb, winfast clone of nvidia 7600gt) I've had this issue before on eoan on hp dx6120 i believe but cannot find bug report. The bug was likely not filed as that box was i386 & support was being dropped when I noticed it so I didn't see any point. It's not new, and no doubt relates to Nvidia cards, and I'm convinced I've filed this before on dx6120 so if not eoan, disco, but I've not yet found it. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-18-generic 5.8.0-18.19 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guiverc1095 F pulseaudio /dev/snd/controlC0: guiverc1095 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Sep 17 11:13:50 2020 InstallationDate: Installed on 2021-09-17 (-365 days ago) InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916) IwConfig: lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 990 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic root=UUID=c29a66dc-4cfc-4dc1-9fe7-3c9d8a8ab4a1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-18-generic N/A linux-backports-modules-5.8.0-18-generic N/A linux-firmware1.190 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A20 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA20:bd05/05/2017:br4.6:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guiverc 950 F pulseaudio /dev/snd/controlC0: guiverc 950 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-09-17 (-365 days ago) InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916) IwConfig: lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matc
[Kernel-packages] [Bug 1895905] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1895905/+attachment/5411512/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895905 Title: lubuntu groovy; flashing of sddm greeter Status in linux package in Ubuntu: Confirmed Bug description: Lubuntu groovy QA-test install. On reboot, the login greeter (sddm) screen isn't nice, with areas of the screen flashing white/black/white/black (maybe white & black each second like a ":" might flash on the clock, only the ":" on the clock is static) likely package at fault should be xserver-xorg-video-nouveau Photo can be seen at https://photos.app.goo.gl/SYPytVxtkKBEj9NY8 The - drop down for session (not selected Lubuntu) - language drop down (not US flag) - white/black on login picture (not grey name) flashes black & white on a cycle... The top panel items will eventually stop flashing (ie. session & layout) but time or certain actions cause the flashing white then black in cycle to occur again. ** Expected Result No flashing, its irritating & potentially a problem for some with certain health conditions. ** Not new issue, it's occurred in the past hp dx6120mt (pentium 4, 3gb, winfast clone of nvidia 7600gt) I've had this issue before on eoan on hp dx6120 i believe but cannot find bug report. The bug was likely not filed as that box was i386 & support was being dropped when I noticed it so I didn't see any point. It's not new, and no doubt relates to Nvidia cards, and I'm convinced I've filed this before on dx6120 so if not eoan, disco, but I've not yet found it. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-18-generic 5.8.0-18.19 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guiverc1095 F pulseaudio /dev/snd/controlC0: guiverc1095 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Sep 17 11:13:50 2020 InstallationDate: Installed on 2021-09-17 (-365 days ago) InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916) IwConfig: lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 990 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic root=UUID=c29a66dc-4cfc-4dc1-9fe7-3c9d8a8ab4a1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-18-generic N/A linux-backports-modules-5.8.0-18-generic N/A linux-firmware1.190 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A20 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA20:bd05/05/2017:br4.6:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guiverc 950 F pulseaudio /dev/snd/controlC0: guiverc 950 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-09-17 (-365 days ago) InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916) IwConfig: lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching
[Kernel-packages] [Bug 1895905] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1895905/+attachment/5411519/+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/1895905 Title: lubuntu groovy; flashing of sddm greeter Status in linux package in Ubuntu: Confirmed Bug description: Lubuntu groovy QA-test install. On reboot, the login greeter (sddm) screen isn't nice, with areas of the screen flashing white/black/white/black (maybe white & black each second like a ":" might flash on the clock, only the ":" on the clock is static) likely package at fault should be xserver-xorg-video-nouveau Photo can be seen at https://photos.app.goo.gl/SYPytVxtkKBEj9NY8 The - drop down for session (not selected Lubuntu) - language drop down (not US flag) - white/black on login picture (not grey name) flashes black & white on a cycle... The top panel items will eventually stop flashing (ie. session & layout) but time or certain actions cause the flashing white then black in cycle to occur again. ** Expected Result No flashing, its irritating & potentially a problem for some with certain health conditions. ** Not new issue, it's occurred in the past hp dx6120mt (pentium 4, 3gb, winfast clone of nvidia 7600gt) I've had this issue before on eoan on hp dx6120 i believe but cannot find bug report. The bug was likely not filed as that box was i386 & support was being dropped when I noticed it so I didn't see any point. It's not new, and no doubt relates to Nvidia cards, and I'm convinced I've filed this before on dx6120 so if not eoan, disco, but I've not yet found it. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-18-generic 5.8.0-18.19 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guiverc1095 F pulseaudio /dev/snd/controlC0: guiverc1095 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Sep 17 11:13:50 2020 InstallationDate: Installed on 2021-09-17 (-365 days ago) InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916) IwConfig: lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 990 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic root=UUID=c29a66dc-4cfc-4dc1-9fe7-3c9d8a8ab4a1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-18-generic N/A linux-backports-modules-5.8.0-18-generic N/A linux-firmware1.190 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A20 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA20:bd05/05/2017:br4.6:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guiverc 950 F pulseaudio /dev/snd/controlC0: guiverc 950 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-09-17 (-365 days ago) InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916) IwConfig: lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching
[Kernel-packages] [Bug 1895905] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1895905/+attachment/5411508/+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/1895905 Title: lubuntu groovy; flashing of sddm greeter Status in linux package in Ubuntu: Confirmed Bug description: Lubuntu groovy QA-test install. On reboot, the login greeter (sddm) screen isn't nice, with areas of the screen flashing white/black/white/black (maybe white & black each second like a ":" might flash on the clock, only the ":" on the clock is static) likely package at fault should be xserver-xorg-video-nouveau Photo can be seen at https://photos.app.goo.gl/SYPytVxtkKBEj9NY8 The - drop down for session (not selected Lubuntu) - language drop down (not US flag) - white/black on login picture (not grey name) flashes black & white on a cycle... The top panel items will eventually stop flashing (ie. session & layout) but time or certain actions cause the flashing white then black in cycle to occur again. ** Expected Result No flashing, its irritating & potentially a problem for some with certain health conditions. ** Not new issue, it's occurred in the past hp dx6120mt (pentium 4, 3gb, winfast clone of nvidia 7600gt) I've had this issue before on eoan on hp dx6120 i believe but cannot find bug report. The bug was likely not filed as that box was i386 & support was being dropped when I noticed it so I didn't see any point. It's not new, and no doubt relates to Nvidia cards, and I'm convinced I've filed this before on dx6120 so if not eoan, disco, but I've not yet found it. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-18-generic 5.8.0-18.19 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guiverc1095 F pulseaudio /dev/snd/controlC0: guiverc1095 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Sep 17 11:13:50 2020 InstallationDate: Installed on 2021-09-17 (-365 days ago) InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916) IwConfig: lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 990 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic root=UUID=c29a66dc-4cfc-4dc1-9fe7-3c9d8a8ab4a1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-18-generic N/A linux-backports-modules-5.8.0-18-generic N/A linux-firmware1.190 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A20 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA20:bd05/05/2017:br4.6:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guiverc 950 F pulseaudio /dev/snd/controlC0: guiverc 950 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-09-17 (-365 days ago) InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916) IwConfig: lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching
[Kernel-packages] [Bug 1895905] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1895905/+attachment/5411521/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895905 Title: lubuntu groovy; flashing of sddm greeter Status in linux package in Ubuntu: Confirmed Bug description: Lubuntu groovy QA-test install. On reboot, the login greeter (sddm) screen isn't nice, with areas of the screen flashing white/black/white/black (maybe white & black each second like a ":" might flash on the clock, only the ":" on the clock is static) likely package at fault should be xserver-xorg-video-nouveau Photo can be seen at https://photos.app.goo.gl/SYPytVxtkKBEj9NY8 The - drop down for session (not selected Lubuntu) - language drop down (not US flag) - white/black on login picture (not grey name) flashes black & white on a cycle... The top panel items will eventually stop flashing (ie. session & layout) but time or certain actions cause the flashing white then black in cycle to occur again. ** Expected Result No flashing, its irritating & potentially a problem for some with certain health conditions. ** Not new issue, it's occurred in the past hp dx6120mt (pentium 4, 3gb, winfast clone of nvidia 7600gt) I've had this issue before on eoan on hp dx6120 i believe but cannot find bug report. The bug was likely not filed as that box was i386 & support was being dropped when I noticed it so I didn't see any point. It's not new, and no doubt relates to Nvidia cards, and I'm convinced I've filed this before on dx6120 so if not eoan, disco, but I've not yet found it. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-18-generic 5.8.0-18.19 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guiverc1095 F pulseaudio /dev/snd/controlC0: guiverc1095 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Sep 17 11:13:50 2020 InstallationDate: Installed on 2021-09-17 (-365 days ago) InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916) IwConfig: lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 990 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic root=UUID=c29a66dc-4cfc-4dc1-9fe7-3c9d8a8ab4a1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-18-generic N/A linux-backports-modules-5.8.0-18-generic N/A linux-firmware1.190 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A20 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA20:bd05/05/2017:br4.6:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guiverc 950 F pulseaudio /dev/snd/controlC0: guiverc 950 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-09-17 (-365 days ago) InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916) IwConfig: lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching
[Kernel-packages] [Bug 1895905] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1895905/+attachment/5411511/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895905 Title: lubuntu groovy; flashing of sddm greeter Status in linux package in Ubuntu: Confirmed Bug description: Lubuntu groovy QA-test install. On reboot, the login greeter (sddm) screen isn't nice, with areas of the screen flashing white/black/white/black (maybe white & black each second like a ":" might flash on the clock, only the ":" on the clock is static) likely package at fault should be xserver-xorg-video-nouveau Photo can be seen at https://photos.app.goo.gl/SYPytVxtkKBEj9NY8 The - drop down for session (not selected Lubuntu) - language drop down (not US flag) - white/black on login picture (not grey name) flashes black & white on a cycle... The top panel items will eventually stop flashing (ie. session & layout) but time or certain actions cause the flashing white then black in cycle to occur again. ** Expected Result No flashing, its irritating & potentially a problem for some with certain health conditions. ** Not new issue, it's occurred in the past hp dx6120mt (pentium 4, 3gb, winfast clone of nvidia 7600gt) I've had this issue before on eoan on hp dx6120 i believe but cannot find bug report. The bug was likely not filed as that box was i386 & support was being dropped when I noticed it so I didn't see any point. It's not new, and no doubt relates to Nvidia cards, and I'm convinced I've filed this before on dx6120 so if not eoan, disco, but I've not yet found it. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-18-generic 5.8.0-18.19 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guiverc1095 F pulseaudio /dev/snd/controlC0: guiverc1095 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Sep 17 11:13:50 2020 InstallationDate: Installed on 2021-09-17 (-365 days ago) InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916) IwConfig: lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 990 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic root=UUID=c29a66dc-4cfc-4dc1-9fe7-3c9d8a8ab4a1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-18-generic N/A linux-backports-modules-5.8.0-18-generic N/A linux-firmware1.190 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A20 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA20:bd05/05/2017:br4.6:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guiverc 950 F pulseaudio /dev/snd/controlC0: guiverc 950 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-09-17 (-365 days ago) InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916) IwConfig: lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching
[Kernel-packages] [Bug 1895905] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1895905/+attachment/5411509/+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/1895905 Title: lubuntu groovy; flashing of sddm greeter Status in linux package in Ubuntu: Confirmed Bug description: Lubuntu groovy QA-test install. On reboot, the login greeter (sddm) screen isn't nice, with areas of the screen flashing white/black/white/black (maybe white & black each second like a ":" might flash on the clock, only the ":" on the clock is static) likely package at fault should be xserver-xorg-video-nouveau Photo can be seen at https://photos.app.goo.gl/SYPytVxtkKBEj9NY8 The - drop down for session (not selected Lubuntu) - language drop down (not US flag) - white/black on login picture (not grey name) flashes black & white on a cycle... The top panel items will eventually stop flashing (ie. session & layout) but time or certain actions cause the flashing white then black in cycle to occur again. ** Expected Result No flashing, its irritating & potentially a problem for some with certain health conditions. ** Not new issue, it's occurred in the past hp dx6120mt (pentium 4, 3gb, winfast clone of nvidia 7600gt) I've had this issue before on eoan on hp dx6120 i believe but cannot find bug report. The bug was likely not filed as that box was i386 & support was being dropped when I noticed it so I didn't see any point. It's not new, and no doubt relates to Nvidia cards, and I'm convinced I've filed this before on dx6120 so if not eoan, disco, but I've not yet found it. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-18-generic 5.8.0-18.19 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guiverc1095 F pulseaudio /dev/snd/controlC0: guiverc1095 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Sep 17 11:13:50 2020 InstallationDate: Installed on 2021-09-17 (-365 days ago) InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916) IwConfig: lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 990 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic root=UUID=c29a66dc-4cfc-4dc1-9fe7-3c9d8a8ab4a1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-18-generic N/A linux-backports-modules-5.8.0-18-generic N/A linux-firmware1.190 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A20 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA20:bd05/05/2017:br4.6:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guiverc 950 F pulseaudio /dev/snd/controlC0: guiverc 950 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-09-17 (-365 days ago) InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916) IwConfig: lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching
[Kernel-packages] [Bug 1895905] Re: lubuntu groovy; flashing of sddm greeter
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1895905 ** Tags added: iso-testing -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895905 Title: lubuntu groovy; flashing of sddm greeter Status in linux package in Ubuntu: Incomplete Bug description: Lubuntu groovy QA-test install. On reboot, the login greeter (sddm) screen isn't nice, with areas of the screen flashing white/black/white/black (maybe white & black each second like a ":" might flash on the clock, only the ":" on the clock is static) likely package at fault should be xserver-xorg-video-nouveau Photo can be seen at https://photos.app.goo.gl/SYPytVxtkKBEj9NY8 The - drop down for session (not selected Lubuntu) - language drop down (not US flag) - white/black on login picture (not grey name) flashes black & white on a cycle... The top panel items will eventually stop flashing (ie. session & layout) but time or certain actions cause the flashing white then black in cycle to occur again. ** Expected Result No flashing, its irritating & potentially a problem for some with certain health conditions. ** Not new issue, it's occurred in the past hp dx6120mt (pentium 4, 3gb, winfast clone of nvidia 7600gt) I've had this issue before on eoan on hp dx6120 i believe but cannot find bug report. The bug was likely not filed as that box was i386 & support was being dropped when I noticed it so I didn't see any point. It's not new, and no doubt relates to Nvidia cards, and I'm convinced I've filed this before on dx6120 so if not eoan, disco, but I've not yet found it. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-18-generic 5.8.0-18.19 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guiverc1095 F pulseaudio /dev/snd/controlC0: guiverc1095 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Sep 17 11:13:50 2020 InstallationDate: Installed on 2021-09-17 (-365 days ago) InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916) IwConfig: lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 990 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic root=UUID=c29a66dc-4cfc-4dc1-9fe7-3c9d8a8ab4a1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-18-generic N/A linux-backports-modules-5.8.0-18-generic N/A linux-firmware1.190 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A20 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA20:bd05/05/2017:br4.6:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758512] Re: No virtual terminals (CTRL+ALT+F?) when no user logged in; erratic behaviour when user logged in.
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1758512 Title: No virtual terminals (CTRL+ALT+F?) when no user logged in; erratic behaviour when user logged in. Status in gdm3 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: As of today's 18.04 version, on a dell xps-13 (the old i7-4500U one), to reproduce: - boot Ubuntu - Press Ctrl+Alt+F2 (or F3 or...) Expected behaviour: virtual console should appear with login prompt. Actual behaviour: nothing happens. When a user is logged in, Ctrl+Alt+F3 switches to terminal tty3... However, hitting first Ctrl+Alt+F1 and, subsequently, hitting Ctrl+Alt+F3 does not show tty3, and remains at the graphical login screen but keyboard and mouse are unresponsive until either Ctrl+Alt+F1 or Ctrl+Alt+F? are pressed, being ? the virtual terminal the ubuntu session is running at. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 24 10:11:26 2018 InstallationDate: Installed on 2014-05-05 (1418 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to bionic on 2018-03-22 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1758512/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868519] Re: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenMoveCursor() from xf86MoveCursor() from miPointerMoveNoEvent() from miPointerSetPosition() from positionSprite()
If you experience multiple problems then please ensure each one has a separate bug open. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1868519 Title: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenMoveCursor() from xf86MoveCursor() from miPointerMoveNoEvent() from miPointerSetPosition() from positionSprite() Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-440 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nvidia-graphics-drivers. This problem was most recently seen with package version 2:1.20.7-2ubuntu2, the problem page at https://errors.ubuntu.com/problem/5a9ed7ea32a1d20e4222dbe8712aa9640b42a73c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1868519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894338] Re: [Dell Inspiron 7570][Samsung Earphones Tuned by AKG] Volume control buttons don't work
If you run sudo evtest and choose 11, then press the button on the headset, does the keycode show in the evtest output steadily? If it does, it means the driver could work well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894338 Title: [Dell Inspiron 7570][Samsung Earphones Tuned by AKG] Volume control buttons don't work Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Invalid Bug description: My earphones are the one coming with Samsung Galaxy S8 (here: https://www.samsung.com/us/mobile/mobile-accessories/phones/samsung- earphones-tuned-by-akg--gray-eo-ig955bsegus) and on my Ubuntu 18.04 (dual-boot with Windows 10, Secure Boot enabled) Trying to set the volume from my earphones' controls doesn't work, no modification on the volume, the sound bar on Ubuntu doesn't appear in order to indicate volume change. I would like to change the master volume, or whatever my common laptop controls do when I up/down the volume controls on my earphones, like it happens on Windows 10. Why does the erroneous behavior of being unable to set volume from my earphones happen? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.10 ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18 Uname: Linux 4.15.0-115-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jason 3523 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 4 23:29:52 2020 InstallationDate: Installed on 2018-09-28 (706 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=el_GR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/17/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.0 dmi.board.name: 02P5YY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.0:bd02/17/2020:svnDellInc.:pnInspiron7570:pvr:rvnDellInc.:rn02P5YY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7570 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-09-28 (718 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic hid_multitouch wmi_bmof dell_wmi snd_hda_intel snd_intel_dspcfg soundwire_intel soundwire_generic_allocation snd_soc_core dell_laptop ledtrig_audio snd_compress soundwire_cadence soundwire_bus dell_smbios snd_hda_codec dell_wmi_descriptor snd_hwdep dcdbas snd_hda_core snd_pcm x86_pkg_temp_thermal intel_powerclamp iwlmvm snd_seq_midi snd_seq_midi_event iwlwifi snd_rawmidi i915 snd_seq snd_seq_device i2c_algo_bit snd_timer drm_kms_helper syscopyarea sysfillrect sysimgblt snd fb_sys_fops drm int3403_thermal soundcore wmi intel_lpss_pci int3402_thermal processor_thermal_device int3400_thermal int340x_thermal_zone intel_soc_dts_iosf acpi_thermal_rel mei_me intel_lpss intel_pch_thermal mfd_core mei efivarfs xhci_pci xhci_hcd i2c_hid Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=el_GR.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 5.9.0-rc3+ x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895905] Re: lubuntu groovy; flashing of sddm greeter
** Description changed: - I'll add detail later - likely package should be xserver-xorg-video-nouveau + Lubuntu groovy QA-test install. + + On reboot, the login greeter (sddm) screen isn't nice, with areas of the + screen flashing white/black/white/black (maybe white & black each second + like a ":" might flash on the clock, only the ":" on the clock is + static) + + likely package at fault should be xserver-xorg-video-nouveau + + Photo can be seen at + + https://photos.app.goo.gl/SYPytVxtkKBEj9NY8 + + The + - drop down for session (not selected Lubuntu) + - language drop down (not US flag) + - white/black on login picture (not grey name) + + flashes black & white on a cycle... + + The top panel items will eventually stop flashing (ie. session & layout) + but time or certain actions cause the flashing white then black in cycle + to occur again. + + ** Expected Result + + No flashing, its irritating & potentially a problem for some with + certain health conditions. + + + ** Not new issue, it's occurred in the past + + hp dx6120mt (pentium 4, 3gb, winfast clone of nvidia 7600gt) I've had this issue before on eoan on hp dx6120 i believe but cannot - find bug report (likely not filed as that box was i386 & support was - being dropped when I noticed it; ie. pre-release) + find bug report. The bug was likely not filed as that box was i386 & + support was being dropped when I noticed it so I didn't see any point. + + It's not new, and no doubt relates to Nvidia cards, and I'm convinced + I've filed this before on dx6120 so if not eoan, disco, but I've not yet + found it. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-18-generic 5.8.0-18.19 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: guiverc1095 F pulseaudio - /dev/snd/controlC0: guiverc1095 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: guiverc1095 F pulseaudio + /dev/snd/controlC0: guiverc1095 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Sep 17 11:13:50 2020 InstallationDate: Installed on 2021-09-17 (-365 days ago) InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916) IwConfig: - lono wireless extensions. - - eno1 no wireless extensions. + lono wireless extensions. + + eno1 no wireless extensions. Lsusb: - Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver - Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub - Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver + Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub + Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 990 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic root=UUID=c29a66dc-4cfc-4dc1-9fe7-3c9d8a8ab4a1 ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.8.0-18-generic N/A - linux-backports-modules-5.8.0-18-generic N/A - linux-firmware1.190 + linux-restricted-modules-5.8.0-18-generic N/A + linux-backports-modules-5.8.0-18-generic N/A + linux-firmware1.190 RfKill: - + SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A20 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA20:bd05/05/2017:br4.6:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895905 Title: lubuntu groovy; flashing of sddm greeter Status in linux package in Ubuntu: Incomplete Bug description: Lubuntu groovy QA-test install. On reboot, the login greeter (sddm) screen isn't nice, with areas of the screen flashing white/bla
[Kernel-packages] [Bug 1894605] Re: gtp: unable to associate contextes to interfaces
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => William Breathitt Gray (vilhelm-gray)
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => William Breathitt Gray (vilhelm-gray)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894605
Title:
gtp: unable to associate contextes to interfaces
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Bionic:
In Progress
Status in linux source package in Focal:
In Progress
Status in linux source package in Groovy:
Fix Committed
Bug description:
[Impact]
When a user dump pdp contextes, it cannot associate them with existing
gtp interfaces. Thus, the dump is unusable.
This problem has been fixed in the upstream commit b274e47d9e3f ("gtp: add
GTPA_LINK info to msg sent to userspace"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b274e47d9e3f
[Test Case]
Create several gtp interfaces and setup PDP contextes on them. Perform
a dump with the genl command GTP_CMD_GETPDP.
[Regression Potential]
The patch affects only the gtp driver and is quite trivial. Thus, the
potential regressions are limited to this area and low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894605/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895905] 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 1895905 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/1895905 Title: lubuntu groovy; flashing of sddm greeter Status in linux package in Ubuntu: Incomplete Bug description: Lubuntu groovy QA-test install. On reboot, the login greeter (sddm) screen isn't nice, with areas of the screen flashing white/black/white/black (maybe white & black each second like a ":" might flash on the clock, only the ":" on the clock is static) likely package at fault should be xserver-xorg-video-nouveau Photo can be seen at https://photos.app.goo.gl/SYPytVxtkKBEj9NY8 The - drop down for session (not selected Lubuntu) - language drop down (not US flag) - white/black on login picture (not grey name) flashes black & white on a cycle... The top panel items will eventually stop flashing (ie. session & layout) but time or certain actions cause the flashing white then black in cycle to occur again. ** Expected Result No flashing, its irritating & potentially a problem for some with certain health conditions. ** Not new issue, it's occurred in the past hp dx6120mt (pentium 4, 3gb, winfast clone of nvidia 7600gt) I've had this issue before on eoan on hp dx6120 i believe but cannot find bug report. The bug was likely not filed as that box was i386 & support was being dropped when I noticed it so I didn't see any point. It's not new, and no doubt relates to Nvidia cards, and I'm convinced I've filed this before on dx6120 so if not eoan, disco, but I've not yet found it. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-18-generic 5.8.0-18.19 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guiverc1095 F pulseaudio /dev/snd/controlC0: guiverc1095 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Sep 17 11:13:50 2020 InstallationDate: Installed on 2021-09-17 (-365 days ago) InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916) IwConfig: lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 990 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic root=UUID=c29a66dc-4cfc-4dc1-9fe7-3c9d8a8ab4a1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-18-generic N/A linux-backports-modules-5.8.0-18-generic N/A linux-firmware1.190 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A20 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA20:bd05/05/2017:br4.6:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895905] [NEW] lubuntu groovy; flashing of sddm greeter
Public bug reported: I'll add detail later likely package should be xserver-xorg-video-nouveau I've had this issue before on eoan on hp dx6120 i believe but cannot find bug report (likely not filed as that box was i386 & support was being dropped when I noticed it; ie. pre-release) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-18-generic 5.8.0-18.19 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guiverc1095 F pulseaudio /dev/snd/controlC0: guiverc1095 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Sep 17 11:13:50 2020 InstallationDate: Installed on 2021-09-17 (-365 days ago) InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916) IwConfig: lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 990 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic root=UUID=c29a66dc-4cfc-4dc1-9fe7-3c9d8a8ab4a1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-18-generic N/A linux-backports-modules-5.8.0-18-generic N/A linux-firmware1.190 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A20 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA20:bd05/05/2017:br4.6:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895905 Title: lubuntu groovy; flashing of sddm greeter Status in linux package in Ubuntu: Incomplete Bug description: I'll add detail later likely package should be xserver-xorg-video-nouveau I've had this issue before on eoan on hp dx6120 i believe but cannot find bug report (likely not filed as that box was i386 & support was being dropped when I noticed it; ie. pre-release) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-18-generic 5.8.0-18.19 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guiverc1095 F pulseaudio /dev/snd/controlC0: guiverc1095 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Sep 17 11:13:50 2020 InstallationDate: Installed on 2021-09-17 (-365 days ago) InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916) IwConfig: lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 990 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic root=UUID=c29a66dc-4cfc-4dc1-9fe7-3c9d8a8ab4a1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-18-generic N/A linux-backports-modules-5.8.0-18-generic N/A linux-firmware1.190 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A20 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vend
[Kernel-packages] [Bug 1890223] Re: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-42-generic
Hello Eko, my guess is the process that had the debconf database locked was asking you to enroll a new secure boot key. By killing it rather than configuring a key, you can't install self-built kernel modules. I suggest looking at the "Manual Method" section of https://wiki.ubuntu.com/UEFI/SecureBoot/DKMS 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/1890223 Title: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-42-generic Status in linux package in Ubuntu: Incomplete Bug description: I use Ubuntu 20.04 in HP laptop and updated Linux kernel to version 5.4.0-42-generic after that Wifi Menu can't find on Settings and Wifi Adapter cannot detect so I use bluetooth tethering to connect to the internet. I think the problem in driver package. I try to install driver with find information from many site such as documentation or stackoverflow but still failed. Can you help me to resolve this. Thankyou very much and I appreciated for it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ekoadin 32543 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 IwConfig: lono wireless extensions. bnep0 no wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0 Bus 001 Device 002: ID 25a7:fa23 Compx 2.4G Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Notebook Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=aba06a00-074b-4a90-8880-854f890802cf ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/18/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.82 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80A3 dmi.board.vendor: HP dmi.board.version: 91.1E dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.82:bd08/18/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A3:rvr91.1E:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion Notebook dmi.product.sku: P3V63PA#AR6 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm3067 F pulseaudio ekoadin6063 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: usb0 no wireless extensions. lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0 Bus 001 Device 003: ID 04e8:6864 Samsung Electronics Co., Ltd GT-I9070 (network tethering, USB debugging enabled) Bus 001 Device 002: ID 25a7:fa23 Compx 2.4G Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Notebook Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=aba06a00-074b-4a90-8880-854f890802cf ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A WifiSyslog: Sep 01 20:09:09 ekoadin-ubuntu kernel: Lockdown: systemd-logind: hibernation is restricted; see
[Kernel-packages] [Bug 1893956] Re: Intel x710 LOMs do not work on Focal
** Description changed: [IMPACT] - The latest Intel based LOMs do not work fully on Focal. + The Intel x710-TM4 is one of the latest 10GbE controllers from intel using the i40e driver. This particular 4 port comes in a 2x2 arrangement: 2x SFP+ and 2x RJ-45. This card is enabled in 5.4 via the inbox version of the i40e driver, and hwinfo does show both sides of the card but the kernel only sees the two SFP+ ports and cannot address or use the two copper ports. These devices have up to 4 ports, but only two seem to work and this has been seen on at least two different systems using LOMs based on this. - We've discovered via testing that while the i40e driver in 5.4 fails, - the version in 5.8 works, so that's the point to start patching. + This is currently blocking certification for one of our hardware + partners. + [FIX] This list of Patches enables the latest X710 controller fully: * 3df5b9a6a9ec i40e: enable X710 support * d80a476f4a12 i40e: Fix LED blinking flow for X710T*L devices These are all clean cherry picks from 5.5 into 5.4 My tree with these can be found here: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1893956-update-i40e-intel-lom [TESTCASE] i40e should load successfully, all ports on Carlsville x710 LOM should be visible and configurable. Test kernels have been verified by the vendor reporting the issue that all network ports on the LOM are accessible and pass traffic at expected speeds. [REGRESSION RISK] Should be pretty low. This is a small patch set to a single driver that only enables a newer chipset. ** Description changed: [IMPACT] The Intel x710-TM4 is one of the latest 10GbE controllers from intel using the i40e driver. This particular 4 port comes in a 2x2 arrangement: 2x SFP+ and 2x RJ-45. This card is enabled in 5.4 via the inbox version of the i40e driver, and hwinfo does show both sides of the card but the kernel only sees the two SFP+ ports and cannot address or use the two copper ports. These devices have up to 4 ports, but only two seem to work and this has been seen on at least two different systems using LOMs based on this. This is currently blocking certification for one of our hardware partners. - [FIX] This list of Patches enables the latest X710 controller fully: * 3df5b9a6a9ec i40e: enable X710 support * d80a476f4a12 i40e: Fix LED blinking flow for X710T*L devices These are all clean cherry picks from 5.5 into 5.4 My tree with these can be found here: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1893956-update-i40e-intel-lom [TESTCASE] i40e should load successfully, all ports on Carlsville x710 LOM should - be visible and configurable. + be visible, configurable, and can pass traffic at full speed. Test kernels have been verified by the vendor reporting the issue that all network ports on the LOM are accessible and pass traffic at expected speeds. [REGRESSION RISK] Should be pretty low. This is a small patch set to a single driver that only enables a newer chipset. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1893956 Title: Intel x710 LOMs do not work on Focal Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: In Progress Bug description: [IMPACT] The Intel x710-TM4 is one of the latest 10GbE controllers from intel using the i40e driver. This particular 4 port comes in a 2x2 arrangement: 2x SFP+ and 2x RJ-45. This card is enabled in 5.4 via the inbox version of the i40e driver, and hwinfo does show both sides of the card but the kernel only sees the two SFP+ ports and cannot address or use the two copper ports. These devices have up to 4 ports, but only two seem to work and this has been seen on at least two different systems using LOMs based on this. This is currently blocking certification for one of our hardware partners. [FIX] This list of Patches enables the latest X710 controller fully: * 3df5b9a6a9ec i40e: enable X710 support * d80a476f4a12 i40e: Fix LED blinking flow for X710T*L devices These are all clean cherry picks from 5.5 into 5.4 My tree with these can be found here: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1893956-update-i40e-intel-lom [TESTCASE] i40e should load successfully, all ports on Carlsville x710 LOM should be visible, configurable, and can pass traffic at full speed. Test kernels have been verified by the vendor reporting the issue that all network ports on the LOM are accessible and pass traffic at expected speeds. [REGRESSION RISK] Should be pretty low. This is a small patch set to a single driver that only enables a newer chipset. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1895202] Re: touchpad suddenly not detected, appearing as PS/2 mouse in devices
Same issue. Lenovo Thinkpad X1. Looks like it started with kernel version
5.4.0-45 and remains in 5.4.0-47. With 5.4.0-42 trackpad is listed as
↳ SynPS/2 Synaptics TouchPad
in xinput, with 5.4.0-45 and 5.4.0-47 it shows as
↳ Synaptics TM3418-002
according to Xorg.0.log same driver is loaded in 5.4.0-{42,45,47}
LoadModule: "synaptics"
(II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
but neither the touchpad, the touchpad buttons, nor the trackpoint work.
But "synclient" sees the trackpad and prints out all the properties.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1895202
Title:
touchpad suddenly not detected, appearing as PS/2 mouse in devices
Status in linux package in Ubuntu:
Confirmed
Bug description:
I can't even recall making any upgrades. Lenovo X1 Extreme.
~ xinput --list
⎡ Virtual core pointerid=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4[slave pointer
(2)]
⎜ ↳ Synaptics TM3418-002id=12 [slave pointer
(2)]
⎜ ↳ PS/2 Generic Mouse id=13 [slave pointer
(2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard id=5[slave
keyboard (3)]
↳ Power Buttonid=6[slave
keyboard (3)]
↳ Video Bus id=7[slave
keyboard (3)]
↳ Sleep Buttonid=8[slave
keyboard (3)]
↳ Integrated Camera: Integrated C id=9[slave
keyboard (3)]
↳ AT Raw Set 2 keyboard id=10 [slave
keyboard (3)]
↳ ThinkPad Extra Buttons id=11 [slave
keyboard (3)]
➜ ~ cat /var/log/Xorg.0.log | grep -i synaptics
[12.190] (II) config/udev: Adding input device Synaptics TM3418-002
(/dev/input/event7)
[12.190] (**) Synaptics TM3418-002: Applying InputClass "libinput
touchpad catchall"
[12.190] (II) Using input driver 'libinput' for 'Synaptics TM3418-002'
[12.190] (**) Synaptics TM3418-002: always reports core events
[12.192] (II) event7 - Synaptics TM3418-002: is tagged by udev as:
Touchpad
[12.193] (II) event7 - Synaptics TM3418-002: device is a touchpad
[12.194] (II) event7 - Synaptics TM3418-002: device removed
[12.194] (II) XINPUT: Adding extended input device "Synaptics TM3418-002"
(type: TOUCHPAD, id 12)
[12.194] (**) Synaptics TM3418-002: (accel) selected scheme none/0
[12.194] (**) Synaptics TM3418-002: (accel) acceleration factor: 2.000
[12.194] (**) Synaptics TM3418-002: (accel) acceleration threshold: 4
[12.195] (II) event7 - Synaptics TM3418-002: is tagged by udev as:
Touchpad
[12.195] (II) event7 - Synaptics TM3418-002: device is a touchpad
[12.196] (II) config/udev: Adding input device Synaptics TM3418-002
(/dev/input/mouse0)
[34.235] (II) event7 - Synaptics TM3418-002: device removed
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-47-generic 5.4.0-47.51
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ole2093 F pulseaudio
/dev/snd/controlC0: ole2093 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 10 21:45:53 2020
InstallationDate: Installed on 2019-03-30 (530 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
MachineType: LENOVO 20MFCTO1WW
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic
root=UUID=37b4f683-cd0d-4eb9-b05a-973790230aa4 ro i8042.reset quiet splash
vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.4.0-47-generic N/A
linux-backports-modules-5.4.0-47-generic N/A
linux-firmware1.187.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/15/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: N2EET48W (1.30 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20MFCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrN2EET48W(1.30):bd05/15/2020:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Extreme
dmi.product.name: 20MFCTO1WW
[Kernel-packages] [Bug 1887716] Re: 10G-BaseT fails to Canonical Certification pxe boot
*** This bug is a duplicate of bug 1893956 *** https://bugs.launchpad.net/bugs/1893956 ** This bug is no longer a duplicate of bug 1887703 [Regression] 5.4 is not identifying all ports on Intel x710-TM4 10GbE controller ** This bug has been marked a duplicate of bug 1893956 Intel x710 LOMs do not work on 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/1887716 Title: 10G-BaseT fails to Canonical Certification pxe boot Status in linux package in Ubuntu: Incomplete Bug description: 10G-BaseT unable to run pxe boot. use 10G-SFP able to pxe boot and deployed successful. Even logged, ip addr only show interface 10G-SFP x 2, 10G-BaseT are not present. Attached sosreport-usable-sloth-1-2020-07-15-telgxfb.tar.xz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887716/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887703] Re: [Regression] 5.4 is not identifying all ports on Intel x710-TM4 10GbE controller
*** This bug is a duplicate of bug 1893956 *** https://bugs.launchpad.net/bugs/1893956 ** This bug has been marked a duplicate of bug 1893956 Intel x710 LOMs do not work on Focal ** Tags removed: blocks-hwcert-server -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887703 Title: [Regression] 5.4 is not identifying all ports on Intel x710-TM4 10GbE controller Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Bug description: [IMPACT] The Intel x710-TM4 is one of the latest 10GbE controllers from intel using the i40e driver. This particular 4 port comes in a 2x2 arrangement: 2x SFP+ and 2x RJ-45. This card is enabled in 5.4 via the inbox version of the i40e driver, and hwinfo does show both sides of the card but the kernel only sees the two SFP+ ports and cannot address or use the two copper ports. This is currently blocking certification for one of our hardware partners. After some investigation we see this works in a more recent version of the driver. Intel suggests the commit in FIXES from 5.5 should make this work. This is a regression from the i40e driver in Bionic (5.3 HWE) that, per the tester, does show all four ports. [FIXES] 3df5b9a6a9ec3c1e4431bf1db3426b54dc92dd91 i40e: enable X710 support I have a branch here: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1887703-i40e-enable-x710 [TESTING] Boot system, verify four ports are visible and can be addressed and pass data. [IMPACT] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887703/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
Hello nikita-tomilov... your solution worked and the trackpad is working, but the issue i realised was that there was no kernel header associated with the kernel and as as result VirtualBox cannot run VMs. I was asking if anyone can help me with the guide to generate a kernel header for the installed kernel. root@14-IIL:~# uname -a Linux 14-IIL 5.9.0-rc4+ #1 SMP Wed Sep 9 20:08:29 CST 2020 x86_64 x86_64 x86_64 GNU/Linux Kind regards -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1861610 Title: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL' Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [SRU Justification] [Impact] Touchpad function unavailable on some platforms with new ELAN touchpad HIDs. [Fix] https://lore.kernel.org/linux-input/000201d5a8bd$9fead3f0$dfc07bd0$@emc.com.tw/ required to match these currently unsupported IDs. [Test Case] 1. check if platform is affected, e.g. with ELAN0634: $ sudo acpidump | grep -C3 ELAN 2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46 INT1p.IDAD..SBF 2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F SSBFI.[.B.TPD2._ 2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00 ADR..IDAD..HID2. 2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08 ._HID.ELAN0634.. 2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55 _CID.PNP0C50.._U 2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11 ID..K._DSM..<.h. 2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D ..https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895891] [NEW] Xenial update: v4.4.236 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v4.4.236 upstream stable release from git://git.kernel.org/ HID: core: Correctly handle ReportSize being zero HID: core: Sanitize event code and type when mapping input perf record/stat: Explicitly call out event modifiers in the documentation mm, page_alloc: remove unnecessary variable from free_pcppages_bulk hwmon: (applesmc) check status earlier. ceph: don't allow setlease on cephfs s390: don't trace preemption in percpu macros xen/xenbus: Fix granting of vmalloc'd memory dmaengine: of-dma: Fix of_dma_router_xlate's of_dma_xlate handling batman-adv: Avoid uninitialized chaddr when handling DHCP batman-adv: bla: use netif_rx_ni when not in interrupt context dmaengine: at_hdmac: check return value of of_find_device_by_node() in at_dma_xlate() netfilter: nf_tables: incorrect enum nft_list_attributes definition netfilter: nf_tables: fix destination register zeroing dmaengine: pl330: Fix burst length if burst size is smaller than bus width bnxt_en: Check for zero dir entries in NVRAM. fix regression in "epoll: Keep a reference on files added to the check list" tg3: Fix soft lockup when tg3_reset_task() fails. iommu/vt-d: Serialize IOMMU GCMD register modifications thermal: ti-soc-thermal: Fix bogus thermal shutdowns for omap4430 include/linux/log2.h: add missing () around n in roundup_pow_of_two() btrfs: drop path before adding new uuid tree entry btrfs: Remove redundant extent_buffer_get in get_old_root btrfs: Remove extraneous extent_buffer_get from tree_mod_log_rewind btrfs: set the lockdep class for log tree extent buffers uaccess: Add non-pagefault user-space read functions uaccess: Add non-pagefault user-space write function btrfs: fix potential deadlock in the search ioctl net: qmi_wwan: MDM9x30 specific power management net: qmi_wwan: support "raw IP" mode net: qmi_wwan: should hold RTNL while changing netdev type net: qmi_wwan: ignore bogus CDC Union descriptors Add Dell Wireless 5809e Gobi 4G HSPA+ Mobile Broadband Card (rev3) to qmi_wwan qmi_wwan: Added support for Gemalto's Cinterion PHxx WWAN interface qmi_wwan: add support for Quectel EC21 and EC25 NET: usb: qmi_wwan: add support for Telit LE922A PID 0x1040 drivers: net: usb: qmi_wwan: add QMI_QUIRK_SET_DTR for Telit PID 0x1201 usb: qmi_wwan: add D-Link DWM-222 A2 device ID net: usb: qmi_wwan: add Telit ME910 support net: usb: qmi_wwan: add Telit 0x1050 composition ALSA: ca0106: fix error code handling ALSA: pcm: oss: Remove superfluous WARN_ON() for mulaw sanity check dm cache metadata: Avoid returning cmd->bm wild pointer on error dm thin metadata: Avoid returning cmd->bm wild pointer on error net: refactor bind_bucket fastreuse into helper net: initialize fastreuse on inet_inherit_port checkpatch: fix the usage of capture group ( ... ) mm/hugetlb: fix a race between hugetlb sysctl handlers cfg80211: regulatory: reject invalid hints net: usb: Fix uninit-was-stored issue in asix_read_phy_addr() ALSA: firewire-digi00x: add support for console models of Digi00x series ALSA: firewire-digi00x: exclude Avid Adrenaline from detection ALSA; firewire-tascam: exclude Tascam FE-8 from detection fs/affs: use octal for permissions affs: fix basic permission bits to actually work ravb: Fixed to be able to unload modules net: ethernet: mlx4: Fix memory allocation in mlx4_buddy_init() bnxt_en: Failure to update PHY is not fatal condition. bnxt: don't enable NAPI until rings are ready net: usb: dm9601: Add USB ID of Keenetic Plus DSL sctp: not disable bh in the whole sctp_get_port_local() net: disable netpoll on fresh napis Linux 4.4.236 UBUNTU: upstream stable to v4.4.236 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Xenial) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by
[Kernel-packages] [Bug 1893956] Re: Intel x710 LOMs do not work on Focal
** Description changed: [IMPACT] The latest Intel based LOMs do not work fully on Focal. These devices have up to 4 ports, but only two seem to work and this has been seen on at least two different systems using LOMs based on this. We've discovered via testing that while the i40e driver in 5.4 fails, the version in 5.8 works, so that's the point to start patching. [FIX] This list of Patches enables the latest X710 controller fully: * 3df5b9a6a9ec i40e: enable X710 support * d80a476f4a12 i40e: Fix LED blinking flow for X710T*L devices These are all clean cherry picks from 5.5 into 5.4 My tree with these can be found here: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1893956-update-i40e-intel-lom [TESTCASE] i40e should load successfully, all ports on Carlsville x710 LOM should be visible and configurable. Test kernels have been verified by the vendor reporting the issue that all network ports on the LOM are accessible and pass traffic at expected speeds. + + [REGRESSION RISK] + Should be pretty low. This is a small patch set to a single driver that only enables a newer chipset. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1893956 Title: Intel x710 LOMs do not work on Focal Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: In Progress Bug description: [IMPACT] The latest Intel based LOMs do not work fully on Focal. These devices have up to 4 ports, but only two seem to work and this has been seen on at least two different systems using LOMs based on this. We've discovered via testing that while the i40e driver in 5.4 fails, the version in 5.8 works, so that's the point to start patching. [FIX] This list of Patches enables the latest X710 controller fully: * 3df5b9a6a9ec i40e: enable X710 support * d80a476f4a12 i40e: Fix LED blinking flow for X710T*L devices These are all clean cherry picks from 5.5 into 5.4 My tree with these can be found here: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1893956-update-i40e-intel-lom [TESTCASE] i40e should load successfully, all ports on Carlsville x710 LOM should be visible and configurable. Test kernels have been verified by the vendor reporting the issue that all network ports on the LOM are accessible and pass traffic at expected speeds. [REGRESSION RISK] Should be pretty low. This is a small patch set to a single driver that only enables a newer chipset. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893956/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887674] Re: Introduce the new NVIDIA 450-server and the 450 UDA series
I've run through our CUDA gpgpu testing using the 450-server driver packages on the following release/kernel combinatoins: ## Bionic Kernel: 4.15.0-118-generic Driver: 450.51.06-0ubuntu0.18.04.2 CUDA: 11.0 Update 1 ## Bionic HWE Kernel: 5.4.0-48-generic Driver: 450.51.06-0ubuntu0.18.04.2 CUDA: 11.0 Update 1 ## Focal Kernel: 5.4.0-48-generic Driver: 450.51.06-0ubuntu0.20.04.2 CUDA: 11.0 Update 1 Both were run on cloud VMs with Tesla M60 and Tesla T4 GPUs. No issues were found. This completes the verification testing for the 450-server drivers for both bionic and focal. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1887674 Title: Introduce the new NVIDIA 450-server and the 450 UDA series Status in OEM Priority Project: New Status in linux package in Ubuntu: Triaged Status in linux-restricted-modules package in Ubuntu: Triaged Status in nvidia-graphics-drivers-450 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450 source package in Bionic: In Progress Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux-restricted-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450 source package in Focal: In Progress Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893956] Re: Intel x710 LOMs do not work on Focal
** Summary changed: - Intel NIC LOMs do not work on Focal + Intel x710 LOMs do not work on 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/1893956 Title: Intel x710 LOMs do not work on Focal Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: In Progress Bug description: [IMPACT] The latest Intel based LOMs do not work fully on Focal. These devices have up to 4 ports, but only two seem to work and this has been seen on at least two different systems using LOMs based on this. We've discovered via testing that while the i40e driver in 5.4 fails, the version in 5.8 works, so that's the point to start patching. [FIX] This list of Patches enables the latest X710 controller fully: * 3df5b9a6a9ec i40e: enable X710 support * d80a476f4a12 i40e: Fix LED blinking flow for X710T*L devices These are all clean cherry picks from 5.5 into 5.4 My tree with these can be found here: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1893956-update-i40e-intel-lom [TESTCASE] i40e should load successfully, all ports on Carlsville x710 LOM should be visible and configurable. Test kernels have been verified by the vendor reporting the issue that all network ports on the LOM are accessible and pass traffic at expected speeds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893956/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868519] Re: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenMoveCursor() from xf86MoveCursor() from miPointerMoveNoEvent() from miPointerSetPosition() from positionSprite()
HP OMEN by HP Laptop 17-cb0xxx 450 driver did not solve my problems -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1868519 Title: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenMoveCursor() from xf86MoveCursor() from miPointerMoveNoEvent() from miPointerSetPosition() from positionSprite() Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-440 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nvidia-graphics-drivers. This problem was most recently seen with package version 2:1.20.7-2ubuntu2, the problem page at https://errors.ubuntu.com/problem/5a9ed7ea32a1d20e4222dbe8712aa9640b42a73c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1868519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895881] Re: Focal update: v5.4.65 upstream stable release
** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.4.65 upstream stable release + from git://git.kernel.org/ -v5.4.65 upstream stable release -from git://git.kernel.org/ + ipv4: Silence suspicious RCU usage warning + ipv6: Fix sysctl max for fib_multipath_hash_policy + netlabel: fix problems with mapping removal + net: usb: dm9601: Add USB ID of Keenetic Plus DSL + sctp: not disable bh in the whole sctp_get_port_local() + taprio: Fix using wrong queues in gate mask + tipc: fix shutdown() of connectionless socket + net: disable netpoll on fresh napis + Linux 5.4.65 + UBUNTU: upstream stable to v5.4.65 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895881 Title: Focal update: v5.4.65 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.65 upstream stable release from git://git.kernel.org/ ipv4: Silence suspicious RCU usage warning ipv6: Fix sysctl max for fib_multipath_hash_policy netlabel: fix problems with mapping removal net: usb: dm9601: Add USB ID of Keenetic Plus DSL sctp: not disable bh in the whole sctp_get_port_local() taprio: Fix using wrong queues in gate mask tipc: fix shutdown() of connectionless socket net: disable netpoll on fresh napis Linux 5.4.65 UBUNTU: upstream stable to v5.4.65 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895881/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895880] Re: Focal update: v5.4.64 upstream stable release
** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.4.64 upstream stable release + from git://git.kernel.org/ -v5.4.64 upstream stable release -from git://git.kernel.org/ + HID: quirks: Always poll three more Lenovo PixArt mice + drm/msm/dpu: Fix scale params in plane validation + tty: serial: qcom_geni_serial: Drop __init from qcom_geni_console_setup + drm/msm: add shutdown support for display platform_driver + hwmon: (applesmc) check status earlier. + nvmet: Disable keep-alive timer when kato is cleared to 0h + drm/msm: enable vblank during atomic commits + habanalabs: validate FW file size + habanalabs: check correct vmalloc return code + drm/msm/a6xx: fix gmu start on newer firmware + ceph: don't allow setlease on cephfs + drm/omap: fix incorrect lock state + cpuidle: Fixup IRQ state + nbd: restore default timeout when setting it to zero + s390: don't trace preemption in percpu macros + drm/amd/display: Reject overlay plane configurations in multi-display scenarios + drivers: gpu: amd: Initialize amdgpu_dm_backlight_caps object to 0 in amdgpu_dm_update_backlight_caps + drm/amd/display: Retry AUX write when fail occurs + drm/amd/display: Fix memleak in amdgpu_dm_mode_config_init + xen/xenbus: Fix granting of vmalloc'd memory + fsldma: fix very broken 32-bit ppc ioread64 functionality + dmaengine: of-dma: Fix of_dma_router_xlate's of_dma_xlate handling + batman-adv: Avoid uninitialized chaddr when handling DHCP + batman-adv: Fix own OGM check in aggregated OGMs + batman-adv: bla: use netif_rx_ni when not in interrupt context + dmaengine: at_hdmac: check return value of of_find_device_by_node() in at_dma_xlate() + rxrpc: Keep the ACK serial in a var in rxrpc_input_ack() + rxrpc: Make rxrpc_kernel_get_srtt() indicate validity + MIPS: mm: BMIPS5000 has inclusive physical caches + MIPS: BMIPS: Also call bmips_cpu_setup() for secondary cores + mmc: sdhci-acpi: Fix HS400 tuning for AMDI0040 + netfilter: nf_tables: add NFTA_SET_USERDATA if not null + netfilter: nf_tables: incorrect enum nft_list_attributes definition + netfilter: nf_tables: fix destination register zeroing + net: hns: Fix memleak in hns_nic_dev_probe + net: systemport: Fix memleak in bcm_sysport_probe + ravb: Fixed to be able to unload modules + net: arc_emac: Fix memleak in arc_mdio_probe + dmaengine: pl330: Fix burst length if burst size is smaller than bus width + gtp: add GTPA_LINK info to msg sent to userspace + net: ethernet: ti: cpsw: fix clean up of vlan mc entries for host port + bnxt_en: Don't query FW when netif_running() is false. + bnxt_en: Check for zero dir entries in NVRAM. + bnxt_en: Fix PCI AER error recovery flow + bnxt_en: Fix possible crash in bnxt_fw_reset_task(). + bnxt_en: fix HWRM error when querying VF temperature + xfs: fix boundary test in xfs_attr_shortform_verify + bnxt: don't enable NAPI until rings are ready + media: vicodec: add missing v4l2_ctrl_request_hdl_put() + media: cedrus: Add missing v4l2_ctrl_request_hdl_put() + selftests/bpf: Fix massive output from test_maps + net: dsa: mt7530: fix advertising unsupported 1000baseT_Half + netfilter: nfnetlink: nfnetlink_unicast() reports EAGAIN instead of ENOBUFS + nvmet-fc: Fix a missed _irqsave version of spin_lock in 'nvmet_fc_fod_op_done()' + nvme: fix controller instance leak + cxgb4: fix thermal zone device registration + perf tools: Correct SNOOPX field offset + net: ethernet: mlx4: Fix memory allocation in mlx4_buddy_init() + fix regression in "epoll: Keep a reference on files added to the check list" + net: gemini: Fix another missing clk_disable_unprepare() in probe + MIPS: add missing MSACSR and upper MSA initialization + xfs: fix xfs_bmap_validate_extent_raw when checking attr fork of rt files + perf jevents: Fix suspicious code in fixregex() + tg3: Fix soft lockup when tg3_reset_task() fails. + x86, fakenuma: Fix invalid starting node ID + iommu/vt-d: Serialize IOMMU GCMD register modifications + thermal: ti-soc-thermal: Fix bogus thermal shutdowns for omap4430 + thermal: qcom-spmi-temp-alarm: Don't suppress negative temp +
[Kernel-packages] [Bug 1895879] Re: Focal update: v5.4.63 upstream stable release
** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.4.63 upstream stable release + from git://git.kernel.org/ -v5.4.63 upstream stable release -from git://git.kernel.org/ + HID: core: Correctly handle ReportSize being zero + HID: core: Sanitize event code and type when mapping input + perf record/stat: Explicitly call out event modifiers in the documentation + drm/sched: Fix passing zero to 'PTR_ERR' warning v2 + drm/etnaviv: fix TS cache flushing on GPUs with BLT engine + KVM: arm64: Add kvm_extable for vaxorcism code + KVM: arm64: Survive synchronous exceptions caused by AT instructions + KVM: arm64: Set HCR_EL2.PTW to prevent AT taking synchronous exception + dt-bindings: mmc: tegra: Add tmclk for Tegra210 and later + arm64: tegra: Add missing timeout clock to Tegra194 SDMMC nodes + arm64: tegra: Add missing timeout clock to Tegra186 SDMMC nodes + arm64: tegra: Add missing timeout clock to Tegra210 SDMMC + sdhci: tegra: Remove SDHCI_QUIRK_DATA_TIMEOUT_USES_SDCLK for Tegra210 + sdhci: tegra: Remove SDHCI_QUIRK_DATA_TIMEOUT_USES_SDCLK for Tegra186 + scsi: target: tcmu: Fix size in calls to tcmu_flush_dcache_range + scsi: target: tcmu: Optimize use of flush_dcache_page + Linux 5.4.63 + UBUNTU: upstream stable to v5.4.63 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895879 Title: Focal update: v5.4.63 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.63 upstream stable release from git://git.kernel.org/ HID: core: Correctly handle ReportSize being zero HID: core: Sanitize event code and type when mapping input perf record/stat: Explicitly call out event modifiers in the documentation drm/sched: Fix passing zero to 'PTR_ERR' warning v2 drm/etnaviv: fix TS cache flushing on GPUs with BLT engine KVM: arm64: Add kvm_extable for vaxorcism code KVM: arm64: Survive synchronous exceptions caused by AT instructions KVM: arm64: Set HCR_EL2.PTW to prevent AT taking synchronous exception dt-bindings: mmc: tegra: Add tmclk for Tegra210 and later arm64: tegra: Add missing timeout clock to Tegra194 SDMMC nodes arm64: tegra: Add missing timeout clock to Tegra186 SDMMC nodes arm64: tegra: Add missing timeout clock to Tegra210 SDMMC sdhci: tegra: Remove SDHCI_QUIRK_DATA_TIMEOUT_USES_SDCLK for Tegra210 sdhci: tegra: Remove SDHCI_QUIRK_DATA_TIMEOUT_USES_SDCLK for Tegra186 scsi: target: tcmu: Fix size in calls to tcmu_flush_dcache_range scsi: target: tcmu: Optimize use of flush_dcache_page Linux 5.4.63 UBUNTU: upstream stable to v5.4.63 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895879/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893956] Re: Intel NIC LOMs do not work on Focal
** Description changed: - [IMPACT] The latest Intel based LOMs do not work fully on Focal. These devices have up to 4 ports, but only two seem to work and this has been seen on at least two different systems using LOMs based on this. We've discovered via testing that while the i40e driver in 5.4 fails, the version in 5.8 works, so that's the point to start patching. [FIX] This list of Patches enables the latest X710 controller fully: * 3df5b9a6a9ec i40e: enable X710 support * 3fd8ed563958 i40e: Add UDP segmentation offload support * 621650cabee5 i40e: Refactoring VF MAC filters counting to make more reliable * d80a476f4a12 i40e: Fix LED blinking flow for X710T*L devices * cdb89f15bd46 i40e: allow ethtool to report SW and FW versions in recovery mode * ff9246571a2e i40e: Fix for persistent lldp support * a3e09ded6a6d i40e: Extract detection of HW flags into a function * 0514db37dd78 i40e: Extend PHY access with page change flag These are all clean cherry picks from 5.5. My tree with these can be found here: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1893956-update-i40e-intel-lom [TESTCASE] + + i40e should load successfully, all ports on Carlsville x710 LOM should + be visible and configurable. ** Description changed: [IMPACT] The latest Intel based LOMs do not work fully on Focal. These devices have up to 4 ports, but only two seem to work and this has been seen on at least two different systems using LOMs based on this. We've discovered via testing that while the i40e driver in 5.4 fails, the version in 5.8 works, so that's the point to start patching. [FIX] This list of Patches enables the latest X710 controller fully: * 3df5b9a6a9ec i40e: enable X710 support - * 3fd8ed563958 i40e: Add UDP segmentation offload support - * 621650cabee5 i40e: Refactoring VF MAC filters counting to make more reliable * d80a476f4a12 i40e: Fix LED blinking flow for X710T*L devices - * cdb89f15bd46 i40e: allow ethtool to report SW and FW versions in recovery mode - * ff9246571a2e i40e: Fix for persistent lldp support - * a3e09ded6a6d i40e: Extract detection of HW flags into a function - * 0514db37dd78 i40e: Extend PHY access with page change flag - These are all clean cherry picks from 5.5. + These are all clean cherry picks from 5.5 into 5.4 My tree with these can be found here: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1893956-update-i40e-intel-lom [TESTCASE] i40e should load successfully, all ports on Carlsville x710 LOM should be visible and configurable. + + Test kernels have been verified by the vendor reporting the issue that + all network ports on the LOM are accessible and pass traffic at expected + speeds. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1893956 Title: Intel NIC LOMs do not work on Focal Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: In Progress Bug description: [IMPACT] The latest Intel based LOMs do not work fully on Focal. These devices have up to 4 ports, but only two seem to work and this has been seen on at least two different systems using LOMs based on this. We've discovered via testing that while the i40e driver in 5.4 fails, the version in 5.8 works, so that's the point to start patching. [FIX] This list of Patches enables the latest X710 controller fully: * 3df5b9a6a9ec i40e: enable X710 support * d80a476f4a12 i40e: Fix LED blinking flow for X710T*L devices These are all clean cherry picks from 5.5 into 5.4 My tree with these can be found here: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1893956-update-i40e-intel-lom [TESTCASE] i40e should load successfully, all ports on Carlsville x710 LOM should be visible and configurable. Test kernels have been verified by the vendor reporting the issue that all network ports on the LOM are accessible and pass traffic at expected speeds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893956/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895881] [NEW] Focal update: v5.4.65 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.65 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Focal) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895881 Title: Focal update: v5.4.65 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.65 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895881/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895879] [NEW] Focal update: v5.4.63 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.63 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Focal) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895879 Title: Focal update: v5.4.63 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.63 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895879/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895880] [NEW] Focal update: v5.4.64 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.64 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Focal) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895880 Title: Focal update: v5.4.64 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.64 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895880/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893820] Re: DPLL2 override remains enabled after warm boot of Linux
Hello Timo. I completed my testing using the generic_5.8.0 (2020-08-25 05:38) and generic_5.9.0 (current/2020-09-15 02:44) kernel files that you linked me. The steps I used were as follows: 1. Download the kernel files (linux-image, linux-module) to a removable USB 2. Boot to target Ubuntu 20.04 environment using the EFI Ubuntu GRUB location 3. Copy the kernel files to the Ubuntu Desktop 4. Run "sudo dpkg -i" targeting the kernel files 5. Perform a warm reboot back into Ubuntu, followed by a device power off (Shutdown) 6. Repeat the test sequence used to show the failure, to determine if the new kernel files solves this issue a. Power on the device b. Boot to target Ubuntu 20.04 environment using the EFI Ubuntu GRUB location c. Perform a 'Restart' action in Ubuntu d. Allow the device to boot into Windows 10 (no Boot Menu selection was required, Win10 loads natively using Windows Boot Manager) e. Use the Start Menu to put the device to S3 Sleep Expected: The environment is able to enter the S3 Sleep state without issue using the new kernel files Actual: The environment experiences a WHEA_UNCORRECTABLE_ERROR BSOD event Did I perform this re-test correctly? If so, what are the next steps for this issue? Thank you. ** Attachment added: "Installing Linux Kernel Files" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893820/+attachment/5411381/+files/wm_ubuntu_kernel_install.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1893820 Title: DPLL2 override remains enabled after warm boot of Linux Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu Version Target: 18.04.1 LTS (bootable Ubuntu USB stick) Package Version Target: Unknown Expected: Windows S3 Sleep actions with two DisplayPort monitors using Intel integrated graphics should be able to work without issue after entering a Windows OS from a previously loaded Ubuntu session Actual: Windows S3 Sleep actions with two DisplayPort monitors using Intel integrated graphics will result in a BSOD event if a Windows OS is loaded after an Ubuntu OS session that was ended by a warm reboot action Description: Using a dual-boot Ubuntu/Windows 10 desktop computer environment with two native DisplayPort MB connections to the Intel integrated graphics solution and two DisplayPort monitors it was observed that performing a Windows S3 Sleep action will cause a "WHEA uncorrectable error" BSOD event if the first OS loaded is Linux and the second OS Windows is loaded using a warm boot action. Investigating this BSOD event further it was determined that this issue is specific to the "Linux->warm boot->Windows->S3 Sleep" sequence as long as two DisplayPort monitors are connected to the desktop computer's DisplayPort MB connections. A deeper investigation of the cause of the BSOD identified that upon unloading Linux the DPLL2 override bit remains enabled and will cause a subsequent Windows desktop environment to be vulnerable to failure if it makes use of two DisplayPort-connected monitors. This issue can be reproduced using OEM hardware from either of Lenovo, HP, or Dell. This issue was first observed on the Q270/Q370 Intel chipset and the Intel 530/630 Graphics hardware. Calvin Hartwell of Canonical has been made aware of this issue and been provided issue details and video evidence. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893820/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895873] Re: Bionic update: upstream stable patchset 2020-09-16
** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + upstream stable patchset 2020-09-16 -upstream stable patchset 2020-09-16 -from git://git.kernel.org/ + Ported from the following upstream stable releases: + v4.14.196, v4.19.143 + + from git://git.kernel.org/ + + net: Fix potential wrong skb->protocol in skb_vlan_untag() + tipc: fix uninit skb->data in tipc_nl_compat_dumpit() + ipvlan: fix device features + gre6: Fix reception with IP6_TNL_F_RCV_DSCP_COPY + ALSA: pci: delete repeated words in comments + ASoC: tegra: Fix reference count leaks. + mfd: intel-lpss: Add Intel Emmitsburg PCH PCI IDs + arm64: dts: qcom: msm8916: Pull down PDM GPIOs during sleep + powerpc/xive: Ignore kmemleak false positives + media: pci: ttpci: av7110: fix possible buffer overflow caused by bad DMA value in debiirq() + blktrace: ensure our debugfs dir exists + scsi: target: tcmu: Fix crash on ARM during cmd completion + iommu/iova: Don't BUG on invalid PFNs + drm/amdkfd: Fix reference count leaks. + drm/radeon: fix multiple reference count leak + drm/amdgpu: fix ref count leak in amdgpu_driver_open_kms + drm/amd/display: fix ref count leak in amdgpu_drm_ioctl + drm/amdgpu: fix ref count leak in amdgpu_display_crtc_set_config + drm/amdgpu/display: fix ref count leak when pm_runtime_get_sync fails + scsi: lpfc: Fix shost refcount mismatch when deleting vport + selftests/powerpc: Purge extra count_pmc() calls of ebb selftests + omapfb: fix multiple reference count leaks due to pm_runtime_get_sync + PCI: Fix pci_create_slot() reference count leak + rtlwifi: rtl8192cu: Prevent leaking urb + mips/vdso: Fix resource leaks in genvdso.c + cec-api: prevent leaking memory through hole in structure + f2fs: fix use-after-free issue + drm/nouveau/drm/noveau: fix reference count leak in nouveau_fbcon_open + drm/nouveau: Fix reference count leak in nouveau_connector_detect + locking/lockdep: Fix overflow in presentation of average lock-time + scsi: iscsi: Do not put host in iscsi_set_flashnode_param() + ceph: fix potential mdsc use-after-free crash + scsi: fcoe: Memory leak fix in fcoe_sysfs_fcf_del() + EDAC/ie31200: Fallback if host bridge device is already initialized + media: davinci: vpif_capture: fix potential double free + KVM: arm64: Fix symbol dependency in __hyp_call_panic_nvhe + powerpc/spufs: add CONFIG_COREDUMP dependency + USB: sisusbvga: Fix a potential UB casued by left shifting a negative value + efi: provide empty efi_enter_virtual_mode implementation + Revert "ath10k: fix DMA related firmware crashes on multiple devices" + media: gpio-ir-tx: improve precision of transmitted signal due to scheduling + nvme-fc: Fix wrong return value in __nvme_fc_init_request() + null_blk: fix passing of REQ_FUA flag in null_handle_rq + i2c: rcar: in slave mode, clear NACK earlier + usb: gadget: f_tcm: Fix some resource leaks in some error paths + jbd2: make sure jh have b_transaction set in refile/unfile_buffer + ext4: don't BUG on inconsistent journal feature + jbd2: abort journal if free a async write error metadata buffer + fs: prevent BUG_ON in submit_bh_wbc() + spi: stm32: fix stm32_spi_prepare_mbr in case of odd clk_rate + s390/cio: add cond_resched() in the slow_eval_known_fn() loop + scsi: ufs: Fix possible infinite loop in ufshcd_hold + scsi: ufs: Improve interrupt handling for shared interrupts + scsi: ufs: Clean up completed request without interrupt notification + net: gianfar: Add of_node_put() before goto statement + powerpc/perf: Fix soft lockups due to missed interrupt accounting + HID: i2c-hid: Always sleep 60ms after I2C_HID_PWR_ON commands + btrfs: fix space cache memory leak after transaction abort + fbcon: prevent user font height or width change from causing potential out-of-bounds access + USB: lvtest: return proper error code in probe + vt: defer kfree() of vc_screenbuf in vc_do_resize()
[Kernel-packages] [Bug 1895873] [NEW] Bionic update: upstream stable patchset 2020-09-16
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-09-16 from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Bionic) 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/1895873 Title: Bionic update: upstream stable patchset 2020-09-16 Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-09-16 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895873/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
Thank you @christian. I marked the Xenial test cases under this same bug, though can open a new bug and update the hint bug references if needed. I'll check back to see when/if ddstreet/rbalint have a chance to review. For the test results you're posting, I was wondering where you're getting those results from and an explanation of the results? xenial amd64 boot-and-services (F 45% f 0% S 0% B 5% => P 50%/) .FF...BFF.F. boot-smoke (F 80% f 0% S 0% B 5% => P 15%/) F.FF..BF systemd-fsckd (F 65% f 0% S 0% B 5% => P 30%/) FF.FFF.F..B.FF.F ppc64el no failures s390x no failures In the above, what does the F, f, B, & . stand for? Am I correct to assume the P *% is the pass rate? F for fail? Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration Status in build-essential package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in iputils package in Ubuntu: Invalid Status in kbd package in Ubuntu: Invalid Status in linux-meta package in Ubuntu: Invalid Status in ntpsec package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: Invalid Status in linux-meta source package in Bionic: New Status in systemd source package in Bionic: New Status in build-essential source package in Focal: Confirmed Status in linux-meta source package in Focal: New Status in qemu source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in util-linux source package in Focal: Confirmed Bug description: Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B 0% => P 47%/) FFF.FFF.FF....F. timedated (F 2% S 0% B 0% => P 97%/) ...F upstream (F 17% S 0% B 0% => P 82%/) .F..F.F.FFF...F. systemd-fsckd (F 32% S 0% B 0% => P 67%/) FFF..FF..F.FF..F root-unittests (F 10% S 0% B 0% => P 90%/) FFF...F. arm64 tests-in-lxd (F 40% S 0% B 2% => P 57%/) F.B...FFF.FF..F..F.FFF.F logind (F 2% S 0% B 2% => P 95%/) ..B...F. upstream (F 22% S 0% B 2% => P 75%/) ...F.FB.F.F.F..FFF.F root-unittests (F 12% S 0% B 2% => P 85%/) ..B.F...F.FF...F (I'm sure LP will make this unreadable, but is
[Kernel-packages] [Bug 1891773] Re: kcompactd0 and btrfs-transaction keep deadlocking with each other
I have same problem on two computers One old i5-2500 running Ubuntu 18.04 - 4.15.0-115-generic with btrfs mounted on /home One new Ryzen 9 3900X (was) running 18.04 - 4.15.117-generic with btrfs on / and /home New one I upgraded yesterday to 20.04 and it is now on 5.4.0-47-generic. I hope issue is gone since this machine is important. Both are running also VMs. New one is running Virtualbox VMs and Old one is running one KVM VM. On the old one I still have 112 and 66 kernel versions. But prior to 115 I didn't use KVM on this computer. Not sure if virtualization is also trigger for the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891773 Title: kcompactd0 and btrfs-transaction keep deadlocking with each other Status in linux package in Ubuntu: Confirmed Bug description: Example 1: [346911.187920] INFO: task kcompactd0:53 blocked for more than 120 seconds. [346911.187938] Not tainted 4.15.0-112-generic #113-Ubuntu [346911.187951] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [346911.187968] kcompactd0 D053 2 0x8000 [346911.187969] Call Trace: [346911.187973] __schedule+0x24e/0x880 [346911.187986] ? btree_releasepage+0x42/0x50 [btrfs] [346911.187987] schedule+0x2c/0x80 [346911.187988] io_schedule+0x16/0x40 [346911.187989] __lock_page+0xff/0x140 [346911.187990] ? page_cache_tree_insert+0xe0/0xe0 [346911.187992] migrate_pages+0x91f/0xb80 [346911.187993] ? __ClearPageMovable+0x10/0x10 [346911.187994] ? isolate_freepages_block+0x3b0/0x3b0 [346911.187995] compact_zone+0x681/0x950 [346911.187995] kcompactd_do_work+0xfe/0x2a0 [346911.187996] ? __switch_to_asm+0x35/0x70 [346911.187997] ? __switch_to_asm+0x41/0x70 [346911.187998] kcompactd+0x86/0x1c0 [346911.187999] ? kcompactd+0x86/0x1c0 [346911.188001] ? wait_woken+0x80/0x80 [346911.188002] kthread+0x121/0x140 [346911.188003] ? kcompactd_do_work+0x2a0/0x2a0 [346911.188003] ? kthread_create_worker_on_cpu+0x70/0x70 [346911.188004] ret_from_fork+0x35/0x40 [346911.188015] INFO: task btrfs-transacti:858 blocked for more than 120 seconds. [346911.188031] Not tainted 4.15.0-112-generic #113-Ubuntu [346911.188043] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [346911.188060] btrfs-transacti D0 858 2 0x8000 [346911.188061] Call Trace: [346911.188062] __schedule+0x24e/0x880 [346911.188063] ? bit_wait+0x60/0x60 [346911.188063] schedule+0x2c/0x80 [346911.188064] io_schedule+0x16/0x40 [346911.188065] bit_wait_io+0x11/0x60 [346911.188066] __wait_on_bit+0x4c/0x90 [346911.188066] ? bit_wait+0x60/0x60 [346911.188067] out_of_line_wait_on_bit+0x90/0xb0 [346911.188068] ? bit_waitqueue+0x40/0x40 [346911.188080] lock_extent_buffer_for_io+0x100/0x2a0 [btrfs] [346911.188090] btree_write_cache_pages+0x1b8/0x420 [btrfs] [346911.188092] ? native_sched_clock_from_tsc+0x30/0x70 [346911.188092] ? update_load_avg+0x423/0x780 [346911.188101] btree_writepages+0x5d/0x70 [btrfs] [346911.188102] do_writepages+0x4b/0xe0 [346911.188102] ? enqueue_task_fair+0xb6/0x300 [346911.188111] ? merge_state.part.47+0x44/0x130 [btrfs] [346911.188112] __filemap_fdatawrite_range+0xcf/0x100 [346911.188113] ? __filemap_fdatawrite_range+0xcf/0x100 [346911.188114] filemap_fdatawrite_range+0x13/0x20 [346911.188122] btrfs_write_marked_extents+0x68/0x140 [btrfs] [346911.188129] btrfs_write_and_wait_marked_extents.constprop.20+0x4f/0x90 [btrfs] [346911.188136] btrfs_commit_transaction+0x696/0x910 [btrfs] [346911.188143] ? btrfs_commit_transaction+0x696/0x910 [btrfs] [346911.188144] ? wait_woken+0x80/0x80 [346911.188151] transaction_kthread+0x18d/0x1b0 [btrfs] [346911.188152] kthread+0x121/0x140 [346911.188158] ? btrfs_cleanup_transaction+0x570/0x570 [btrfs] [346911.188159] ? kthread_create_worker_on_cpu+0x70/0x70 [346911.188160] ret_from_fork+0x35/0x40 Example 2: 2020-08-11T20:23:03.533+01:00 kernel: INFO: task kcompactd0:53 blocked for more than 120 seconds. 2020-08-11T20:23:03.533+01:00 kernel: Not tainted 4.15.0-112-generic #113-Ubuntu 2020-08-11T20:23:03.533+01:00 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. 2020-08-11T20:23:03.533+01:00 kernel: kcompactd0 D053 2 0x8000 2020-08-11T20:23:03.533+01:00 kernel: Call Trace: 2020-08-11T20:23:03.533+01:00 kernel: __schedule+0x24e/0x880 2020-08-11T20:23:03.533+01:00 kernel: ? btree_releasepage+0x42/0x50 [btrfs] 2020-08-11T20:23:03.533+01:00 kernel: schedule+0x2c/0x80 2020-08-11T20:23:03.533+01:00 kernel: io_schedule+0x16/0x40 2020-08-11T20:23:03.533+01:00 kernel: __lock_page+0xff/0x140 2020-08-11T20:23:03.533+01:00 kernel: ? page_cache_tree_insert+0xe0/0xe0
[Kernel-packages] [Bug 1890223] Re: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-42-generic
After that, i running sudo apt install bcmwl-kernel-source. The output is here : Reading package lists... Done Building dependency tree Reading state information... Done bcmwl-kernel-source is already the newest version (6.30.223.271+bdcom-0ubuntu5). The following packages were automatically installed and are no longer required: fonts-font-awesome libfprint-2-tod1 linux-headers-5.4.0-42 linux-headers-5.4.0-42-generic linux-image-5.4.0-42-generic linux-modules-5.4.0-42-generic linux-modules-extra-5.4.0-42-generic linux-modules-nvidia-440-5.4.0-42-generic oxygen-icon-theme Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Y Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu5) ... Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.4.0-47-generic Building for architecture x86_64 Building initial module for 5.4.0-47-generic Done. wl.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.4.0-47-generic/updates/dkms/ depmod... DKMS: install completed. modprobe: ERROR: could not insert 'wl': Operation not permitted modprobe: ERROR: ../libkmod/libkmod-module.c:990 command_do() Error running install command '/sbin/modprobe --ignore-install wl ' for module wl: retcode 1 modprobe: ERROR: could not insert 'wl': Invalid argument update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.136ubuntu6.2) ... update-initramfs: Generating /boot/initrd.img-5.4.0-47-generic Wifi settings just still not available, is there any other way? Thank you ** Attachment added: "Screenshot from 2020-09-16 23-07-15.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890223/+attachment/5411364/+files/Screenshot%20from%202020-09-16%2023-07-15.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890223 Title: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-42-generic Status in linux package in Ubuntu: Incomplete Bug description: I use Ubuntu 20.04 in HP laptop and updated Linux kernel to version 5.4.0-42-generic after that Wifi Menu can't find on Settings and Wifi Adapter cannot detect so I use bluetooth tethering to connect to the internet. I think the problem in driver package. I try to install driver with find information from many site such as documentation or stackoverflow but still failed. Can you help me to resolve this. Thankyou very much and I appreciated for it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ekoadin 32543 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 IwConfig: lono wireless extensions. bnep0 no wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0 Bus 001 Device 002: ID 25a7:fa23 Compx 2.4G Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Notebook Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=aba06a00-074b-4a90-8880-854f890802cf ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/18/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.82 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80A3 dmi.board.vendor: HP dmi.board.version: 91.1E dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.82:bd08/18/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A3:rvr91.1E:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion Notebook dmi.product.sku: P3V63PA#AR6 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8
[Kernel-packages] [Bug 1890223] Re: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-42-generic
I have found a way to check a locked process. Using this command: sudo fuser -v /var/cache/debconf/config.dat sudo kill PID ** Attachment added: "Screenshot from 2020-09-16 21-48-11.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890223/+attachment/5411363/+files/Screenshot%20from%202020-09-16%2021-48-11.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890223 Title: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-42-generic Status in linux package in Ubuntu: Incomplete Bug description: I use Ubuntu 20.04 in HP laptop and updated Linux kernel to version 5.4.0-42-generic after that Wifi Menu can't find on Settings and Wifi Adapter cannot detect so I use bluetooth tethering to connect to the internet. I think the problem in driver package. I try to install driver with find information from many site such as documentation or stackoverflow but still failed. Can you help me to resolve this. Thankyou very much and I appreciated for it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ekoadin 32543 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 IwConfig: lono wireless extensions. bnep0 no wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0 Bus 001 Device 002: ID 25a7:fa23 Compx 2.4G Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Notebook Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=aba06a00-074b-4a90-8880-854f890802cf ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/18/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.82 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80A3 dmi.board.vendor: HP dmi.board.version: 91.1E dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.82:bd08/18/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A3:rvr91.1E:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion Notebook dmi.product.sku: P3V63PA#AR6 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm3067 F pulseaudio ekoadin6063 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: usb0 no wireless extensions. lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0 Bus 001 Device 003: ID 04e8:6864 Samsung Electronics Co., Ltd GT-I9070 (network tethering, USB debugging enabled) Bus 001 Device 002: ID 25a7:fa23 Compx 2.4G Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Notebook Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=aba06a00-074b-4a90-8880-854f890802cf ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A WifiSyslog: Sep 01 20:09:09 ekoadin-ubuntu kernel: Lockdown: systemd-logind: hibernation is
[Kernel-packages] [Bug 1887490] Re: Add/Backport EPYC-v3 and EPYC-Rome CPU model
If I understand the comments correctly this should be irrellevant for groovy/devel using a v5.8 base. ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887490 Title: Add/Backport EPYC-v3 and EPYC-Rome CPU model Status in libvirt package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Focal: Incomplete Status in linux source package in Focal: Confirmed Status in qemu source package in Focal: Incomplete Bug description: Qemu in focal has already support for most (except amd-stibp) flags of this model. Please backport the following patches: https://github.com/qemu/qemu/commit/a16e8dbc043720abcb37fc7dca313e720b4e0f0c https://github.com/qemu/qemu/commit/143c30d4d346831a09e59e9af45afdca0331e819 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1887490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895718] Re: Fix non-working NVMe after S3
** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Groovy) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1895718 Title: Fix non-working NVMe after S3 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Confirmed Status in linux-oem-5.6 source package in Focal: Confirmed Status in linux source package in Groovy: Confirmed Status in linux-oem-5.6 source package in Groovy: Won't Fix Bug description: [Impact] KIOXIA NVMe has a 10% chance to stop working after S3. [Fix] Enable ACS quirk on Intel CML root port. [Test] With the patch applied, KIOXIA NVMe always works after S3. [Regression Potential] ACS works at hardware level, so I can't really assess the risk of regression. Since Intel confirmed CML also needs ACS quirk, we can only trust them. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1895718/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895669] Re: Add more support to Lenovo ThinkStation P620
This bug was fixed in the package alsa-ucm-conf - 1.2.2-1ubuntu5 --- alsa-ucm-conf (1.2.2-1ubuntu5) groovy; urgency=medium * d/p/0001-ucm2-USB-Audio-Add-more-support-to-Lenovo-ThinkStati.patch Add MixerElem and proper PCM assignment to Lenovo P620 Main and Rear audio, respectively (LP: #1895669) -- Kai-Heng Feng Tue, 15 Sep 2020 21:19:16 +0800 ** Changed in: alsa-ucm-conf (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1895669 Title: Add more support to Lenovo ThinkStation P620 Status in HWE Next: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Groovy: Fix Released Bug description: [Impact] After upgrading the audio device firmware and doing more testing, we found some new audio issue on Lenovo P620: 1) Rear mic doesn't work. 2) Front and rear mic/line-in don't use hardware gain to control capture volume. [Fix] For 1), add proper PCM stream assignment to the rear microphone. For 2), add MixerElem to let alsa-lib and PulseAudio to pick correct mixer to change HW gain. [Test] With the new UCM applied, rear mic starts to work, and PulseAudio can control the hardware gain. [Regression Potential] The system hasn't hit the market so there's no chance to regression any system in the wild. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1895669/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895833] Re: unblock restrictions on alsa (max id of card and sample rate for alsa Loopback)
Bugs in Ubuntu are never filed against the distribution as a whole, but rather, individual components/packages. Removed affecting Ubuntu. ** No longer affects: ubuntu -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1895833 Title: unblock restrictions on alsa (max id of card and sample rate for alsa Loopback) Status in ALSA Libraries: New Status in Alsa utilities: New Status in alsa-lib package in Ubuntu: New Status in alsa-utils package in Ubuntu: New Bug description: SRU Justification: [Impact] kernel, alsa-lib, alsa-utils We are using more and more cards recognized as sound peripherals. When the number of loopback and hardware cards exceeds 32, we can no longer use them. Also some new devices are already using 384khz but the limitation is for alsa Loopback. I thinks we must increse CONFIG_SND_MAX_CARDS to 256 and change 192000 sample rate value fixed in aloop.c to 384000 or 768000 to provide an additional margin in alsa Loopback. [Test Case] sudo add-apt-repository -y universe apt-get update && sudo apt-get upgrade -y sudo apt-get install alsa alsa-* shutdown -r now sudo modprobe snd-aloop sudo echo snd-aloop >> /etc/modules sudo adduser $(whoami) audio shutdown -r now sudo apt-get install -y apt-get install alsa alsa-utils libasound2-dev sudo apt-get install -y screen build-essential initramfs-tools fakeroot debconf-utils dpkg-dev debhelper bin86 flex bison pkgconf dkms python3-docutils \ libudev-dev mt-st cpufrequtils libpci-dev libssl-dev libiberty-dev libcap-dev asciidoc default-jdk libncurses-dev \ kernel-package kernel-wedge libnvpair1linux libuutil1linux libzfs2linux libzpool2linux zfs-dkms zfs-zed zfsutils-linux \ crash makedumpfile libncurses5 libncurses5-dev libelf-dev binutils-dev kexec-tools screen mkdir ~/megamod cd ~/megamod git clone git://kernel.ubuntu.com/ubuntu/ubuntu-focal.git cd ubuntu-focal sed -i 's/SNDRV_PCM_RATE_CONTINUOUS | SNDRV_PCM_RATE_8000_192000,/SNDRV_PCM_RATE_CONTINUOUS,/g' ./sound/drivers/aloop.c sed -i 's/192000/768000/g' ./sound/drivers/aloop.c grep -rnl './' -e "CONFIG_SND_MAX_CARDS=32" | xargs -i@ sed -i 's/CONFIG_SND_MAX_CARDS=32/CONFIG_SND_MAX_CARDS=256/g' @ search and replace 32 by 256 in and ./debian.master/config/annotations for CONFIG_SND_MAX_CARDS fakeroot debian/rules clean fakeroot debian/rules binary dpkg -i ../linux*5.4.0-*.deb shutdown -r now sudo systemctl disable hv-kvp-daemon.service echo "options snd-aloop \" >> /etc/modprobe.d/alsa-base.conf echo "index=10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45 \" >> /etc/modprobe.d/alsa-base.conf echo "id=lp0,lp1,lp2,lp3,lp4,lp5,lp6,lp7,lp8,lp9,lp10,lp11,lp12,lp13,lp14,lp15,lp16,lp17,lp18,lp19,lp20,lp21,lp22,lp23,lp24,lp25,lp26,lp27,lp28,lp29,lp30,lp31,lp32,lp33,lp34,lp35 \" >> /etc/modprobe.d/alsa-base.conf echo "enable=1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1 \" >> /etc/modprobe.d/alsa-base.conf echo "pcm_substreams=2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2" >> /etc/modprobe.d/alsa-base.conf sudo su sudo mkdir /usr/src/alsa cd /usr/src/alsa git clone git://git.alsa-project.org/alsa-lib.git alsa-lib cd /usr/src/alsa/alsa-lib ./gitcompile --with-max-cards=256 make install cp /usr/lib/libasound* /usr/lib/x86_64-linux-gnu/ cd /usr/src/alsa git clone git://git.alsa-project.org/alsa-utils.git alsa-utils cd /usr/src/alsa/alsa-utils ./gitcompile --with-max-cards=256 make install shutdown -r now [Regression Potential] * The regression can be considered as low, because this is because it's functional since 16.04 [Other] * This requires a patch to be included into the kernel, alsa-lib and alsa-utils package. - please see [Test Case] description for more details. * changes can be made independently and have no impact on others [Patch] In /sound/drivers/aloop.c: L555 .rates =SNDRV_PCM_RATE_CONTINUOUS | SNDRV_PCM_RATE_8000_192000, to L555 .rates =SNDRV_PCM_RATE_CONTINUOUS, In /sound/drivers/aloop.c: L557 .rate_max = 192000, to L557 .rate_max = 768000, In /sound/drivers/aloop.c: L557 uinfo->value.integer.max = 192000; to L557 uinfo->value.integer.max = 768000; In /debian.master/config/config.common.ubuntu L9069 CONFIG_SND_MAX_CARDS=32 to L9069 CONFIG_SND_MAX_CARDS=256 and update debian.master/rules.d/hooks.mk For alsa-lib and alsa-util, package can be simply update with ./gitcompile --with-max-cards=256 Thanks everybody To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-lib/+bug/1895833/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1895833] Re: unblock restrictions on alsa (max id of card and sample rate for alsa Loopback)
** Also affects: alsa-lib Importance: Undecided Status: New ** Also affects: alsa-utils Importance: Undecided Status: New ** Also affects: alsa-lib (Ubuntu) Importance: Undecided Status: New ** Also affects: alsa-utils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1895833 Title: unblock restrictions on alsa (max id of card and sample rate for alsa Loopback) Status in ALSA Libraries: New Status in Alsa utilities: New Status in Ubuntu: New Status in alsa-lib package in Ubuntu: New Status in alsa-utils package in Ubuntu: New Bug description: SRU Justification: [Impact] kernel, alsa-lib, alsa-utils We are using more and more cards recognized as sound peripherals. When the number of loopback and hardware cards exceeds 32, we can no longer use them. Also some new devices are already using 384khz but the limitation is for alsa Loopback. I thinks we must increse CONFIG_SND_MAX_CARDS to 256 and change 192000 sample rate value fixed in aloop.c to 384000 or 768000 to provide an additional margin in alsa Loopback. [Test Case] sudo add-apt-repository -y universe apt-get update && sudo apt-get upgrade -y sudo apt-get install alsa alsa-* shutdown -r now sudo modprobe snd-aloop sudo echo snd-aloop >> /etc/modules sudo adduser $(whoami) audio shutdown -r now sudo apt-get install -y apt-get install alsa alsa-utils libasound2-dev sudo apt-get install -y screen build-essential initramfs-tools fakeroot debconf-utils dpkg-dev debhelper bin86 flex bison pkgconf dkms python3-docutils \ libudev-dev mt-st cpufrequtils libpci-dev libssl-dev libiberty-dev libcap-dev asciidoc default-jdk libncurses-dev \ kernel-package kernel-wedge libnvpair1linux libuutil1linux libzfs2linux libzpool2linux zfs-dkms zfs-zed zfsutils-linux \ crash makedumpfile libncurses5 libncurses5-dev libelf-dev binutils-dev kexec-tools screen mkdir ~/megamod cd ~/megamod git clone git://kernel.ubuntu.com/ubuntu/ubuntu-focal.git cd ubuntu-focal sed -i 's/SNDRV_PCM_RATE_CONTINUOUS | SNDRV_PCM_RATE_8000_192000,/SNDRV_PCM_RATE_CONTINUOUS,/g' ./sound/drivers/aloop.c sed -i 's/192000/768000/g' ./sound/drivers/aloop.c grep -rnl './' -e "CONFIG_SND_MAX_CARDS=32" | xargs -i@ sed -i 's/CONFIG_SND_MAX_CARDS=32/CONFIG_SND_MAX_CARDS=256/g' @ search and replace 32 by 256 in and ./debian.master/config/annotations for CONFIG_SND_MAX_CARDS fakeroot debian/rules clean fakeroot debian/rules binary dpkg -i ../linux*5.4.0-*.deb shutdown -r now sudo systemctl disable hv-kvp-daemon.service echo "options snd-aloop \" >> /etc/modprobe.d/alsa-base.conf echo "index=10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45 \" >> /etc/modprobe.d/alsa-base.conf echo "id=lp0,lp1,lp2,lp3,lp4,lp5,lp6,lp7,lp8,lp9,lp10,lp11,lp12,lp13,lp14,lp15,lp16,lp17,lp18,lp19,lp20,lp21,lp22,lp23,lp24,lp25,lp26,lp27,lp28,lp29,lp30,lp31,lp32,lp33,lp34,lp35 \" >> /etc/modprobe.d/alsa-base.conf echo "enable=1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1 \" >> /etc/modprobe.d/alsa-base.conf echo "pcm_substreams=2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2" >> /etc/modprobe.d/alsa-base.conf sudo su sudo mkdir /usr/src/alsa cd /usr/src/alsa git clone git://git.alsa-project.org/alsa-lib.git alsa-lib cd /usr/src/alsa/alsa-lib ./gitcompile --with-max-cards=256 make install cp /usr/lib/libasound* /usr/lib/x86_64-linux-gnu/ cd /usr/src/alsa git clone git://git.alsa-project.org/alsa-utils.git alsa-utils cd /usr/src/alsa/alsa-utils ./gitcompile --with-max-cards=256 make install shutdown -r now [Regression Potential] * The regression can be considered as low, because this is because it's functional since 16.04 [Other] * This requires a patch to be included into the kernel, alsa-lib and alsa-utils package. - please see [Test Case] description for more details. * changes can be made independently and have no impact on others [Patch] In /sound/drivers/aloop.c: L555 .rates =SNDRV_PCM_RATE_CONTINUOUS | SNDRV_PCM_RATE_8000_192000, to L555 .rates =SNDRV_PCM_RATE_CONTINUOUS, In /sound/drivers/aloop.c: L557 .rate_max = 192000, to L557 .rate_max = 768000, In /sound/drivers/aloop.c: L557 uinfo->value.integer.max = 192000; to L557 uinfo->value.integer.max = 768000; In /debian.master/config/config.common.ubuntu L9069 CONFIG_SND_MAX_CARDS=32 to L9069 CONFIG_SND_MAX_CARDS=256 and update debian.master/rules.d/hooks.mk For alsa-lib and alsa-util, package can be simply update with ./gitcompile --with-max-cards=256
[Kernel-packages] [Bug 1895612] Re: Dynamically set AD5593R channel modes
** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895612 Title: Dynamically set AD5593R channel modes Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Bug description: [Impact] On Advantech UNO-420 development platform, we need a generic way to set the pin mode. Upstream would like us to leverage ACPI override method to change the modes, but in Ubuntu core, we can't generate a new initramfs and boot up with the generated initramfs. [Fix] Add a module parameter to assign pin modes while loading ad5593r driver. [Test] Verified on Advantech UNO-420 platform. [Regression Potential] Low, it checks the length of the passed parameter, and checks every bytes in it to make sure it's a valid argument. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893820] Re: DPLL2 override remains enabled after warm boot of Linux
or use wget: wget https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel- next/current/amd64/linux-image-unsigned-5.8.0-050800drmintelnext20200825 generic_5.8.0-050800drmintelnext20200825.202008242209_amd64.deb wget https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel- next/current/amd64/linux- modules-5.8.0-050800drmintelnext20200825-generic_5.8.0-050800drmintelnext20200825.202008242209_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/1893820 Title: DPLL2 override remains enabled after warm boot of Linux Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu Version Target: 18.04.1 LTS (bootable Ubuntu USB stick) Package Version Target: Unknown Expected: Windows S3 Sleep actions with two DisplayPort monitors using Intel integrated graphics should be able to work without issue after entering a Windows OS from a previously loaded Ubuntu session Actual: Windows S3 Sleep actions with two DisplayPort monitors using Intel integrated graphics will result in a BSOD event if a Windows OS is loaded after an Ubuntu OS session that was ended by a warm reboot action Description: Using a dual-boot Ubuntu/Windows 10 desktop computer environment with two native DisplayPort MB connections to the Intel integrated graphics solution and two DisplayPort monitors it was observed that performing a Windows S3 Sleep action will cause a "WHEA uncorrectable error" BSOD event if the first OS loaded is Linux and the second OS Windows is loaded using a warm boot action. Investigating this BSOD event further it was determined that this issue is specific to the "Linux->warm boot->Windows->S3 Sleep" sequence as long as two DisplayPort monitors are connected to the desktop computer's DisplayPort MB connections. A deeper investigation of the cause of the BSOD identified that upon unloading Linux the DPLL2 override bit remains enabled and will cause a subsequent Windows desktop environment to be vulnerable to failure if it makes use of two DisplayPort-connected monitors. This issue can be reproduced using OEM hardware from either of Lenovo, HP, or Dell. This issue was first observed on the Q270/Q370 Intel chipset and the Intel 530/630 Graphics hardware. Calvin Hartwell of Canonical has been made aware of this issue and been provided issue details and video evidence. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893820/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895669] Re: Add more support to Lenovo ThinkStation P620
** Changed in: alsa-ucm-conf (Ubuntu Groovy) Importance: Undecided => High ** Changed in: alsa-ucm-conf (Ubuntu Groovy) Status: Confirmed => Fix Committed ** Changed in: alsa-ucm-conf (Ubuntu Groovy) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) ** Changed in: alsa-ucm-conf (Ubuntu Focal) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) ** Changed in: alsa-ucm-conf (Ubuntu Focal) Importance: Undecided => High ** Changed in: alsa-ucm-conf (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1895669 Title: Add more support to Lenovo ThinkStation P620 Status in HWE Next: New Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in alsa-ucm-conf source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Groovy: Fix Committed Bug description: [Impact] After upgrading the audio device firmware and doing more testing, we found some new audio issue on Lenovo P620: 1) Rear mic doesn't work. 2) Front and rear mic/line-in don't use hardware gain to control capture volume. [Fix] For 1), add proper PCM stream assignment to the rear microphone. For 2), add MixerElem to let alsa-lib and PulseAudio to pick correct mixer to change HW gain. [Test] With the new UCM applied, rear mic starts to work, and PulseAudio can control the hardware gain. [Regression Potential] The system hasn't hit the market so there's no chance to regression any system in the wild. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1895669/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881109] Re: [Ubuntu 20.04] LPAR crashes in block layer under high stress. Might be triggered by scsi errors.
In other words it's reasonable to retry on a latest Ubuntu 20.04 kernel (after sudo apt update && sudo apt full-upgrade and a reboot) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881109 Title: [Ubuntu 20.04] LPAR crashes in block layer under high stress. Might be triggered by scsi errors. Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: We can reproduce a crash in the block layer with lots of stress on lots of SCSI disks (on an XIV storage server). We seem to have several scsi stalls in the logs/errors (needs to be analyzed further) but in the end we do crash with this this calltrace. [20832.901147] Failing address: 7fe00dea8000 TEID: 7fe00dea8403 [20832.901159] Fault in home space mode while using kernel ASCE. [20832.901171] AS:01d3cccf400b R2:03fd0020800b R3:03fd0020c007 S:03fc1cc78800 P:0400 [20832.901264] Oops: 0011 ilc:2 [#1] SMP [20832.901280] Modules linked in: vhost_net vhost macvtap macvlan tap xfs xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink ip6table_filter ip6_tables iptable_filter bpfilter bridge aufs overlay dm_service_time dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua s390_trng chsc_sch eadm_sch vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio 8021q garp mrp stp llc sch_fq_codel drm drm_panel_orientation_quirks i2c_core ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear dm_mirror dm_region_hash dm_log qeth_l2 pkey zcrypt crc32_vx_s390 ghash_s390 prng aes_s390 des_s390 libdes sha3_512_s390 sha3_256_s390 sha512_s390 sha256_s390 sha1_s390 sha_common zfcp scsi_transport_fc dasd_eckd_mod dasd_mod qeth qdio ccwgroup [20832.901516] CPU: 29 PID: 389709 Comm: CPU 0/KVM Kdump: loaded Not tainted 5.4.0-29-generic #33-Ubuntu [20832.901530] Hardware name: IBM 8561 T01 708 (LPAR) [20832.901542] Krnl PSW : 0404e0018000 01d3cbd559be (try_to_wake_up+0x4e/0x700) [20832.901575]R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI:0 EA:3 [20832.901744] Krnl GPRS: 03fc917cd988 7fe0 7fe0001e 0003 [20832.901750] 004c 040003fd005a4600 0003 [20832.901753]0003 7fe00dea8454 7fe00dea7b00 [20832.901754]03f44bd9b300 01d3cc587088 7fe0021c7ae0 7fe0021c7a60 [20832.901767] Krnl Code: 01d3cbd559b2: 41902954la %r9,2388(%r2) 01d3cbd559b6: 582003acl %r2,940 #01d3cbd559ba: a718lhi %r1,0 >01d3cbd559be: ba129000cs %r1,%r2,0(%r9) 01d3cbd559c2: a77401c9brc 7,01d3cbd55d54 01d3cbd559c6: e310b0080004lg %r1,8(%r11) 01d3cbd559cc: b9800018ngr %r1,%r8 01d3cbd559d0: a774001fbrc 7,01d3cbd55a0e [20832.901784] Call Trace: [20832.901816] ([<01d3cc57e0ac>] cleanup_critical+0x0/0x474) [20832.901823] [<01d3cc1d16ba>] rq_qos_wake_function+0x8a/0xa0 [20832.901827] [<01d3cbd74bde>] __wake_up_common+0x9e/0x1b0 [20832.901829] [<01d3cbd750e4>] __wake_up_common_lock+0x94/0xe0 [20832.901830] [<01d3cbd7515a>] __wake_up+0x2a/0x40 [20832.901835] [<01d3cc1e8640>] wbt_done+0x90/0xe0 [20832.901837] [<01d3cc1d17be>] __rq_qos_done+0x3e/0x60 [20832.901841] [<01d3cc1bd5b0>] blk_mq_free_request+0xe0/0x140 [20832.901848] [<01d3cc35fc60>] dm_softirq_done+0x140/0x230 [20832.901849] [<01d3cc1bbfbc>] blk_done_softirq+0xbc/0xe0 [20832.901850] [<01d3cc57e710>] __do_softirq+0x100/0x360 [20832.901853] [<01d3cbd2525e>] irq_exit+0x9e/0xc0 [20832.901856] [<01d3cbcb0b18>] do_IRQ+0x78/0xb0 [20832.901859] [<01d3cc57dc28>] ext_int_handler+0x128/0x12c [20832.901860] [<01d3cc57d306>] sie_exit+0x0/0x46 [20832.901866] ([<01d3cbce944a>] __vcpu_run+0x27a/0xc30) [20832.901870] [<01d3cbcf29a8>] kvm_arch_vcpu_ioctl_run+0x2d8/0x840 [20832.901875] [<01d3cbcdd242>] kvm_vcpu_ioctl+0x282/0x770 [20832.901880] [<01d3cbf85f66>] do_vfs_ioctl+0x376/0x690 [20832.901881] [<01d3cbf86304>] ksys_ioctl+0x84/0xb0 [20832.901883] [<01d3cbf8639a>] __s390x_sys_ioctl+0x2a/0x40 [20832.901885] [<01d3cc57d5f2>] system_call+0x2a6/0x2c8 [20832.901885] Last
[Kernel-packages] [Bug 1881109] Re: [Ubuntu 20.04] LPAR crashes in block layer under high stress. Might be triggered by scsi errors.
Yes, the kernel(s) were the significant set (of about 30) zFCP related patches were applied to, already landed in focal (-updates) respectively the groovy kernel (indicated by the Fix Released status at LP 1887124 - https://bugs.launchpad.net/ubuntu-z-systems/+bug/1887124) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881109 Title: [Ubuntu 20.04] LPAR crashes in block layer under high stress. Might be triggered by scsi errors. Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: We can reproduce a crash in the block layer with lots of stress on lots of SCSI disks (on an XIV storage server). We seem to have several scsi stalls in the logs/errors (needs to be analyzed further) but in the end we do crash with this this calltrace. [20832.901147] Failing address: 7fe00dea8000 TEID: 7fe00dea8403 [20832.901159] Fault in home space mode while using kernel ASCE. [20832.901171] AS:01d3cccf400b R2:03fd0020800b R3:03fd0020c007 S:03fc1cc78800 P:0400 [20832.901264] Oops: 0011 ilc:2 [#1] SMP [20832.901280] Modules linked in: vhost_net vhost macvtap macvlan tap xfs xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink ip6table_filter ip6_tables iptable_filter bpfilter bridge aufs overlay dm_service_time dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua s390_trng chsc_sch eadm_sch vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio 8021q garp mrp stp llc sch_fq_codel drm drm_panel_orientation_quirks i2c_core ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear dm_mirror dm_region_hash dm_log qeth_l2 pkey zcrypt crc32_vx_s390 ghash_s390 prng aes_s390 des_s390 libdes sha3_512_s390 sha3_256_s390 sha512_s390 sha256_s390 sha1_s390 sha_common zfcp scsi_transport_fc dasd_eckd_mod dasd_mod qeth qdio ccwgroup [20832.901516] CPU: 29 PID: 389709 Comm: CPU 0/KVM Kdump: loaded Not tainted 5.4.0-29-generic #33-Ubuntu [20832.901530] Hardware name: IBM 8561 T01 708 (LPAR) [20832.901542] Krnl PSW : 0404e0018000 01d3cbd559be (try_to_wake_up+0x4e/0x700) [20832.901575]R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI:0 EA:3 [20832.901744] Krnl GPRS: 03fc917cd988 7fe0 7fe0001e 0003 [20832.901750] 004c 040003fd005a4600 0003 [20832.901753]0003 7fe00dea8454 7fe00dea7b00 [20832.901754]03f44bd9b300 01d3cc587088 7fe0021c7ae0 7fe0021c7a60 [20832.901767] Krnl Code: 01d3cbd559b2: 41902954la %r9,2388(%r2) 01d3cbd559b6: 582003acl %r2,940 #01d3cbd559ba: a718lhi %r1,0 >01d3cbd559be: ba129000cs %r1,%r2,0(%r9) 01d3cbd559c2: a77401c9brc 7,01d3cbd55d54 01d3cbd559c6: e310b0080004lg %r1,8(%r11) 01d3cbd559cc: b9800018ngr %r1,%r8 01d3cbd559d0: a774001fbrc 7,01d3cbd55a0e [20832.901784] Call Trace: [20832.901816] ([<01d3cc57e0ac>] cleanup_critical+0x0/0x474) [20832.901823] [<01d3cc1d16ba>] rq_qos_wake_function+0x8a/0xa0 [20832.901827] [<01d3cbd74bde>] __wake_up_common+0x9e/0x1b0 [20832.901829] [<01d3cbd750e4>] __wake_up_common_lock+0x94/0xe0 [20832.901830] [<01d3cbd7515a>] __wake_up+0x2a/0x40 [20832.901835] [<01d3cc1e8640>] wbt_done+0x90/0xe0 [20832.901837] [<01d3cc1d17be>] __rq_qos_done+0x3e/0x60 [20832.901841] [<01d3cc1bd5b0>] blk_mq_free_request+0xe0/0x140 [20832.901848] [<01d3cc35fc60>] dm_softirq_done+0x140/0x230 [20832.901849] [<01d3cc1bbfbc>] blk_done_softirq+0xbc/0xe0 [20832.901850] [<01d3cc57e710>] __do_softirq+0x100/0x360 [20832.901853] [<01d3cbd2525e>] irq_exit+0x9e/0xc0 [20832.901856] [<01d3cbcb0b18>] do_IRQ+0x78/0xb0 [20832.901859] [<01d3cc57dc28>] ext_int_handler+0x128/0x12c [20832.901860] [<01d3cc57d306>] sie_exit+0x0/0x46 [20832.901866] ([<01d3cbce944a>] __vcpu_run+0x27a/0xc30) [20832.901870] [<01d3cbcf29a8>] kvm_arch_vcpu_ioctl_run+0x2d8/0x840 [20832.901875] [<01d3cbcdd242>] kvm_vcpu_ioctl+0x282/0x770 [20832.901880] [<01d3cbf85f66>] do_vfs_ioctl+0x376/0x690 [20832.901881] [<01d3cbf86304>] ksys_ioctl+0x84/0xb0 [20832.901883]
[Kernel-packages] [Bug 1881109] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-09-16 09:02 EDT--- @CAN: Will the patch mentioned in LP comment #8 be used to build the kernel referenced above made it into the regular Ubuntu kernel? Many thx in advance -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881109 Title: [Ubuntu 20.04] LPAR crashes in block layer under high stress. Might be triggered by scsi errors. Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: We can reproduce a crash in the block layer with lots of stress on lots of SCSI disks (on an XIV storage server). We seem to have several scsi stalls in the logs/errors (needs to be analyzed further) but in the end we do crash with this this calltrace. [20832.901147] Failing address: 7fe00dea8000 TEID: 7fe00dea8403 [20832.901159] Fault in home space mode while using kernel ASCE. [20832.901171] AS:01d3cccf400b R2:03fd0020800b R3:03fd0020c007 S:03fc1cc78800 P:0400 [20832.901264] Oops: 0011 ilc:2 [#1] SMP [20832.901280] Modules linked in: vhost_net vhost macvtap macvlan tap xfs xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink ip6table_filter ip6_tables iptable_filter bpfilter bridge aufs overlay dm_service_time dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua s390_trng chsc_sch eadm_sch vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio 8021q garp mrp stp llc sch_fq_codel drm drm_panel_orientation_quirks i2c_core ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear dm_mirror dm_region_hash dm_log qeth_l2 pkey zcrypt crc32_vx_s390 ghash_s390 prng aes_s390 des_s390 libdes sha3_512_s390 sha3_256_s390 sha512_s390 sha256_s390 sha1_s390 sha_common zfcp scsi_transport_fc dasd_eckd_mod dasd_mod qeth qdio ccwgroup [20832.901516] CPU: 29 PID: 389709 Comm: CPU 0/KVM Kdump: loaded Not tainted 5.4.0-29-generic #33-Ubuntu [20832.901530] Hardware name: IBM 8561 T01 708 (LPAR) [20832.901542] Krnl PSW : 0404e0018000 01d3cbd559be (try_to_wake_up+0x4e/0x700) [20832.901575]R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI:0 EA:3 [20832.901744] Krnl GPRS: 03fc917cd988 7fe0 7fe0001e 0003 [20832.901750] 004c 040003fd005a4600 0003 [20832.901753]0003 7fe00dea8454 7fe00dea7b00 [20832.901754]03f44bd9b300 01d3cc587088 7fe0021c7ae0 7fe0021c7a60 [20832.901767] Krnl Code: 01d3cbd559b2: 41902954la %r9,2388(%r2) 01d3cbd559b6: 582003acl %r2,940 #01d3cbd559ba: a718lhi %r1,0 >01d3cbd559be: ba129000cs %r1,%r2,0(%r9) 01d3cbd559c2: a77401c9brc 7,01d3cbd55d54 01d3cbd559c6: e310b0080004lg %r1,8(%r11) 01d3cbd559cc: b9800018ngr %r1,%r8 01d3cbd559d0: a774001fbrc 7,01d3cbd55a0e [20832.901784] Call Trace: [20832.901816] ([<01d3cc57e0ac>] cleanup_critical+0x0/0x474) [20832.901823] [<01d3cc1d16ba>] rq_qos_wake_function+0x8a/0xa0 [20832.901827] [<01d3cbd74bde>] __wake_up_common+0x9e/0x1b0 [20832.901829] [<01d3cbd750e4>] __wake_up_common_lock+0x94/0xe0 [20832.901830] [<01d3cbd7515a>] __wake_up+0x2a/0x40 [20832.901835] [<01d3cc1e8640>] wbt_done+0x90/0xe0 [20832.901837] [<01d3cc1d17be>] __rq_qos_done+0x3e/0x60 [20832.901841] [<01d3cc1bd5b0>] blk_mq_free_request+0xe0/0x140 [20832.901848] [<01d3cc35fc60>] dm_softirq_done+0x140/0x230 [20832.901849] [<01d3cc1bbfbc>] blk_done_softirq+0xbc/0xe0 [20832.901850] [<01d3cc57e710>] __do_softirq+0x100/0x360 [20832.901853] [<01d3cbd2525e>] irq_exit+0x9e/0xc0 [20832.901856] [<01d3cbcb0b18>] do_IRQ+0x78/0xb0 [20832.901859] [<01d3cc57dc28>] ext_int_handler+0x128/0x12c [20832.901860] [<01d3cc57d306>] sie_exit+0x0/0x46 [20832.901866] ([<01d3cbce944a>] __vcpu_run+0x27a/0xc30) [20832.901870] [<01d3cbcf29a8>] kvm_arch_vcpu_ioctl_run+0x2d8/0x840 [20832.901875] [<01d3cbcdd242>] kvm_vcpu_ioctl+0x282/0x770 [20832.901880] [<01d3cbf85f66>] do_vfs_ioctl+0x376/0x690 [20832.901881] [<01d3cbf86304>] ksys_ioctl+0x84/0xb0 [20832.901883] [<01d3cbf8639a>]
[Kernel-packages] [Bug 1856010] Re: xfrm_policy.sh / pmtu.sh / udpgso_bench.sh from net in ubuntu_kernel_selftests will fail if running the whole suite
** Tags added: focal ** Tags added: sru-20200831 -- 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/1856010 Title: xfrm_policy.sh / pmtu.sh / udpgso_bench.sh from net in ubuntu_kernel_selftests will fail if running the whole suite Status in ubuntu-kernel-tests: Triaged Status in linux-aws package in Ubuntu: New Bug description: These 3 tests will fail with timeout when running the whole "net" test in ubuntu_kernel_selftests: * not ok 12 selftests: net: xfrm_policy.sh # TIMEOUT * not ok 16 selftests: net: pmtu.sh # TIMEOUT * not ok 19 selftests: net: udpgso_bench.sh # TIMEOUT However they will pass if you run them manually: So there must be some test in net that will cause this. From the test result it looks like the test was executed in the following sequence: ok 1 selftests: net: reuseport_bpf ok 2 selftests: net: reuseport_bpf_cpu ok 3 selftests: net: reuseport_bpf_numa ok 4 selftests: net: reuseport_dualstack # Successok 5 selftests: net: reuseaddr_conflict ok 6 selftests: net: tls ok 7 selftests: net: run_netsocktests ok 8 selftests: net: run_afpackettests ok 9 selftests: net: test_bpf.sh ok 10 selftests: net: netdevice.sh ok 11 selftests: net: rtnetlink.sh not ok 12 selftests: net: xfrm_policy.sh # TIMEOUT not ok 13 selftests: net: test_blackhole_dev.sh # exit=1 ok 14 selftests: net: fib_tests.sh ok 15 selftests: net: fib-onlink-tests.sh not ok 16 selftests: net: pmtu.sh # TIMEOUT ok 17 selftests: net: udpgso.sh not ok 18 selftests: net: ip_defrag.sh # exit=255 not ok 19 selftests: net: udpgso_bench.sh # TIMEOUT ok 20 selftests: net: fib_rule_tests.sh not ok 21 selftests: net: msg_zerocopy.sh # exit=1 ok 22 selftests: net: psock_snd.sh ok 23 selftests: net: udpgro_bench.sh ok 24 selftests: net: udpgro.sh ok 25 selftests: net: test_vxlan_under_vrf.sh ok 26 selftests: net: reuseport_addr_any.sh ok 27 selftests: net: test_vxlan_fdb_changelink.sh ok 28 selftests: net: so_txtime.sh ok 29 selftests: net: ipv6_flowlabel.sh ok 30 selftests: net: tcp_fastopen_backup_key.sh ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-1009-aws 5.3.0-1009.10 ProcVersionSignature: User Name 5.3.0-1009.10-aws 5.3.13 Uname: Linux 5.3.0-1009-aws aarch64 ApportVersion: 2.20.11-0ubuntu8.3 Architecture: arm64 Date: Wed Dec 11 06:42:39 2019 Ec2AMI: ami-047cec24582f6ae0d Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2c Ec2InstanceType: a1.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable SourcePackage: linux-aws UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1856010/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893820] Re: DPLL2 override remains enabled after warm boot of Linux
dpkg only works with local files, not over the network.. you need to download them first, and the url to the directory is https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel- next/current/amd64/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1893820 Title: DPLL2 override remains enabled after warm boot of Linux Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu Version Target: 18.04.1 LTS (bootable Ubuntu USB stick) Package Version Target: Unknown Expected: Windows S3 Sleep actions with two DisplayPort monitors using Intel integrated graphics should be able to work without issue after entering a Windows OS from a previously loaded Ubuntu session Actual: Windows S3 Sleep actions with two DisplayPort monitors using Intel integrated graphics will result in a BSOD event if a Windows OS is loaded after an Ubuntu OS session that was ended by a warm reboot action Description: Using a dual-boot Ubuntu/Windows 10 desktop computer environment with two native DisplayPort MB connections to the Intel integrated graphics solution and two DisplayPort monitors it was observed that performing a Windows S3 Sleep action will cause a "WHEA uncorrectable error" BSOD event if the first OS loaded is Linux and the second OS Windows is loaded using a warm boot action. Investigating this BSOD event further it was determined that this issue is specific to the "Linux->warm boot->Windows->S3 Sleep" sequence as long as two DisplayPort monitors are connected to the desktop computer's DisplayPort MB connections. A deeper investigation of the cause of the BSOD identified that upon unloading Linux the DPLL2 override bit remains enabled and will cause a subsequent Windows desktop environment to be vulnerable to failure if it makes use of two DisplayPort-connected monitors. This issue can be reproduced using OEM hardware from either of Lenovo, HP, or Dell. This issue was first observed on the Q270/Q370 Intel chipset and the Intel 530/630 Graphics hardware. Calvin Hartwell of Canonical has been made aware of this issue and been provided issue details and video evidence. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893820/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895640] Re: BlueZ 5.55 release
This bug was fixed in the package bluez - 5.55-0ubuntu1 --- bluez (5.55-0ubuntu1) groovy; urgency=medium * New upstream release 5.55 (LP: #1895640) - Fix issue with handling security level for HoG. - Fix issue with handling HIDSDPDisable attribute. - Fix issue with handling HID virtual cable unplug. - Fix issue with handling HID channel disconnect order. - Fix issue with handling AVDTP delay reporting states. - Fix issue with handling AVRCP notification events. - Fix issue with handling AVRCP list player attributes. - Fix issue with handling AVRCP category 1 player settings. - Fix issue with handling AVRCP media player passthrough bitmask. - Fix issue with handling HFP 1.7 default features. - Fix issue with handling GATT disconnecting handling. - Fix issue with handling GATT database hash. - Fix issue with handling service changed characteristic. - Fix issue with handling read of multiple characteristic values. - Fix issue with handling Just-Works auto-accept pairing. - Fix issue with handling authentication of bonded devices. - Fix issue with handling L2CAP streaming mode for AVDTP. - Fix issue with handling SysEx parser for MIDI support. - Fix issue with handling configured scan parameter values. - Fix issue with handling temporary devices removal. - Fix issue with handling advertising flags. -- Daniel van Vugt Tue, 15 Sep 2020 17:17:32 +0800 ** Changed in: bluez (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1895640 Title: BlueZ 5.55 release Status in bluez package in Ubuntu: Fix Released Bug description: https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.55.tar.xz https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?h=5.55 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1895640/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894780] Re: Oops and hang when starting LVM snapshots on 5.4.0-47
** Description changed: + [Impact] + kmemcaches will fail to be created after they have just been removed but not completely ripped out. This will cause some drivers (like lvm snapshots) to properly work and cause kernel traces to go on the logs. + + [Test case] + See comment #9. + + [Regression potential] + The fix reverts a commit, so we go back to a state of a previously released kernel, where a leak was possible. The regression here, though, is better than the impact that will also lead to a different leak and prevent users from correctly using LVM snapshots. + + = + One of my bionic servers with HWE 5.4.0 hangs on boot (apparently while starting LVM snapshots) after upgrading from Linux 5.4.0-42 to 5.4.0-47, with the following trace: [ 29.126292] kobject_add_internal failed for :a-152 with -EEXIST, don't try to register things with the same name in the same directory. [ 29.138854] BUG: kernel NULL pointer dereference, address: 0020 [ 29.145977] #PF: supervisor read access in kernel mode [ 29.145979] #PF: error_code(0x) - not-present page [ 29.145981] PGD 0 P4D 0 [ 29.158800] Oops: [#1] SMP NOPTI [ 29.162468] CPU: 6 PID: 2532 Comm: lvm Not tainted 5.4.0-46-generic #50~18.04.1-Ubuntu [ 29.170378] Hardware name: Supermicro AS -2023US-TR4/H11DSU-iN, BIOS 1.3 07/15/2019 [ 29.178038] RIP: 0010:free_percpu+0x120/0x1f0 [ 29.183786] Code: 43 64 48 01 d0 49 39 c4 0f 83 71 ff ff ff 65 8b 05 a5 4e bc 58 48 8b 15 0e 4e 20 01 48 98 48 8b 3c c2 4c 01 e7 e8 f0 97 02 00 <48> 8b 58 20 48 8b 53 38 e9 48 ff ff ff f3 c3 48 8b 43 38 48 89 45 [ 29.202530] RSP: 0018:a2f69c3d38e8 EFLAGS: 00010046 [ 29.209204] RAX: RBX: 92202ff397c0 RCX: a880a000 [ 29.216336] RDX: cf35c0f24f2cc3c0 RSI: 43817c451b92afcb RDI: [ 29.223469] RBP: a2f69c3d3918 R08: R09: a74a5300 [ 29.230609] R10: a2f69c3d3820 R11: R12: cf35c0f24f14c3c0 [ 29.237745] R13: cf362fb2a054c3c0 R14: 0287 R15: 0008 [ 29.244878] FS: 7f93a04b0900() GS:913faed8() knlGS: [ 29.252961] CS: 0010 DS: ES: CR0: 80050033 [ 29.258707] CR2: 0020 CR3: 003fa9d9 CR4: 003406e0 [ 29.265883] Call Trace: [ 29.268346] __kmem_cache_release+0x1a/0x30 [ 29.273913] __kmem_cache_create+0x4f9/0x550 [ 29.278192] ? __kmalloc_node+0x1eb/0x320 [ 29.282205] ? kvmalloc_node+0x31/0x80 [ 29.285962] create_cache+0x120/0x1f0 [ 29.291003] kmem_cache_create_usercopy+0x17d/0x270 [ 29.295882] kmem_cache_create+0x16/0x20 [ 29.300152] dm_bufio_client_create+0x1af/0x3f0 [dm_bufio] [ 29.305644] ? snapshot_map+0x5e0/0x5e0 [dm_snapshot] [ 29.310693] persistent_read_metadata+0x1ed/0x500 [dm_snapshot] [ 29.316627] ? _cond_resched+0x19/0x40 [ 29.320384] snapshot_ctr+0x79e/0x910 [dm_snapshot] [ 29.325276] dm_table_add_target+0x18d/0x370 [ 29.329552] table_load+0x12a/0x370 [ 29.333045] ctl_ioctl+0x1e2/0x590 [ 29.336450] ? retrieve_status+0x1c0/0x1c0 [ 29.340551] dm_ctl_ioctl+0xe/0x20 [ 29.343958] do_vfs_ioctl+0xa9/0x640 [ 29.347547] ? ksys_semctl.constprop.19+0xf7/0x190 [ 29.352337] ksys_ioctl+0x75/0x80 [ 29.355663] __x64_sys_ioctl+0x1a/0x20 [ 29.359421] do_syscall_64+0x57/0x190 [ 29.363094] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 29.368144] RIP: 0033:0x7f939f0286d7 [ 29.371732] Code: b3 66 90 48 8b 05 b1 47 2d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 81 47 2d 00 f7 d8 64 89 01 48 [ 29.390478] RSP: 002b:7ffe918df168 EFLAGS: 0202 ORIG_RAX: 0010 [ 29.398045] RAX: ffda RBX: 561c107f672c RCX: 7f939f0286d7 [ 29.405175] RDX: 561c1107c610 RSI: c138fd09 RDI: 0009 [ 29.412309] RBP: 7ffe918df220 R08: 7f939f59d120 R09: 7ffe918defd0 [ 29.419442] R10: 561c1107c6c0 R11: 0202 R12: 7f939f59c4e6 [ 29.426623] R13: 7f939f59c4e6 R14: 7f939f59c4e6 R15: 7f939f59c4e6 [ 29.433778] Modules linked in: dm_snapshot dm_bufio dm_zero nls_iso8859_1 ipmi_ssif input_leds amd64_edac_mod edac_mce_amd joydev kvm_amd kvm ccp k10temp ipmi_si ipmi_devintf ipmi_msghandler mac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi sunrpc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ib_uverbs ib_core bcache crc64
[Kernel-packages] [Bug 1894780] Re: Oops and hang when starting LVM snapshots on 5.4.0-47
After reverting commit 79ffe7107b13042c69c4a06394175362121b06b5
(upstream commit d38a2b7a9c939e6d7329ab92b96559ccebf7b135) ("mm:
memcg/slab: fix memory leak at non-root kmem_cache destroy"), things
seem to go back to normal.
The probable reason this one causes a problem is because it has:
@@ -326,6 +326,14 @@ int slab_unmergeable(struct kmem_cache *s)
if (s->refcount < 0)
return 1;
+#ifdef CONFIG_MEMCG_KMEM
+ /*
+* Skip the dying kmem_cache.
+*/
+ if (s->memcg_params.dying)
+ return 1;
+#endif
+
return 0;
}
So, this causes the same-sized slab to become unmergeable, and when a
new slab is created, it will fail creating the sysfs entry.
I haven't investigated why memcg is at play here, and why this one would
be dying, that would involve memcgs being removed during the operation.
But not allowing merges will certainly cause problems here.
The other issue is that this memcg code has been totally
replaced/discarded on 5.9, so it will make things interesting trying to
upstream a proper fix here.
But considering the commit fix a leak and here we will have a different
leak and failures to create slabs, the revert is preferable for now.
Cascardo.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894780
Title:
Oops and hang when starting LVM snapshots on 5.4.0-47
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Focal:
New
Bug description:
One of my bionic servers with HWE 5.4.0 hangs on boot (apparently
while starting LVM snapshots) after upgrading from Linux 5.4.0-42 to
5.4.0-47, with the following trace:
[ 29.126292] kobject_add_internal failed for :a-152 with -EEXIST,
don't try to register things with the same name in the same directory.
[ 29.138854] BUG: kernel NULL pointer dereference, address:
0020
[ 29.145977] #PF: supervisor read access in kernel mode
[ 29.145979] #PF: error_code(0x) - not-present page
[ 29.145981] PGD 0 P4D 0
[ 29.158800] Oops: [#1] SMP NOPTI
[ 29.162468] CPU: 6 PID: 2532 Comm: lvm Not tainted 5.4.0-46-generic
#50~18.04.1-Ubuntu
[ 29.170378] Hardware name: Supermicro AS -2023US-TR4/H11DSU-iN, BIOS 1.3
07/15/2019
[ 29.178038] RIP: 0010:free_percpu+0x120/0x1f0
[ 29.183786] Code: 43 64 48 01 d0 49 39 c4 0f 83 71 ff ff ff 65 8b 05 a5
4e bc 58 48 8b 15 0e 4e 20 01 48 98 48 8b 3c c2 4c 01 e7 e8 f0 97 02 00 <48> 8b
58 20 48 8b 53 38 e9 48 ff ff ff f3 c3 48 8b 43 38 48 89 45
[ 29.202530] RSP: 0018:a2f69c3d38e8 EFLAGS: 00010046
[ 29.209204] RAX: RBX: 92202ff397c0 RCX:
a880a000
[ 29.216336] RDX: cf35c0f24f2cc3c0 RSI: 43817c451b92afcb RDI:
[ 29.223469] RBP: a2f69c3d3918 R08: R09:
a74a5300
[ 29.230609] R10: a2f69c3d3820 R11: R12:
cf35c0f24f14c3c0
[ 29.237745] R13: cf362fb2a054c3c0 R14: 0287 R15:
0008
[ 29.244878] FS: 7f93a04b0900() GS:913faed8()
knlGS:
[ 29.252961] CS: 0010 DS: ES: CR0: 80050033
[ 29.258707] CR2: 0020 CR3: 003fa9d9 CR4:
003406e0
[ 29.265883] Call Trace:
[ 29.268346] __kmem_cache_release+0x1a/0x30
[ 29.273913] __kmem_cache_create+0x4f9/0x550
[ 29.278192] ? __kmalloc_node+0x1eb/0x320
[ 29.282205] ? kvmalloc_node+0x31/0x80
[ 29.285962] create_cache+0x120/0x1f0
[ 29.291003] kmem_cache_create_usercopy+0x17d/0x270
[ 29.295882] kmem_cache_create+0x16/0x20
[ 29.300152] dm_bufio_client_create+0x1af/0x3f0 [dm_bufio]
[ 29.305644] ? snapshot_map+0x5e0/0x5e0 [dm_snapshot]
[ 29.310693] persistent_read_metadata+0x1ed/0x500 [dm_snapshot]
[ 29.316627] ? _cond_resched+0x19/0x40
[ 29.320384] snapshot_ctr+0x79e/0x910 [dm_snapshot]
[ 29.325276] dm_table_add_target+0x18d/0x370
[ 29.329552] table_load+0x12a/0x370
[ 29.333045] ctl_ioctl+0x1e2/0x590
[ 29.336450] ? retrieve_status+0x1c0/0x1c0
[ 29.340551] dm_ctl_ioctl+0xe/0x20
[ 29.343958] do_vfs_ioctl+0xa9/0x640
[ 29.347547] ? ksys_semctl.constprop.19+0xf7/0x190
[ 29.352337] ksys_ioctl+0x75/0x80
[ 29.355663] __x64_sys_ioctl+0x1a/0x20
[ 29.359421] do_syscall_64+0x57/0x190
[ 29.363094] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 29.368144] RIP: 0033:0x7f939f0286d7
[ 29.371732] Code: b3 66 90 48 8b 05 b1 47 2d 00 64 c7 00 26 00 00 00 48
c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d
01 f0 ff ff 73 01 c3 48 8b 0d 81 47 2d 00 f7 d8 64 89 01 48
[ 29.390478] RSP: 002b:7ffe918df168 EFLAGS: 0202 ORIG_RAX:
0010
[ 29.398045] RAX:
[Kernel-packages] [Bug 1895794] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895794 Title: [i915] Plugging an external monitor on USB-C port does not show up. Need to reboot each time Status in linux package in Ubuntu: Confirmed Bug description: Whenever I plug an external monitor (Dell P2720DC) on my ThinkPad X1 (8th gen.) with Ubuntu 20.04, it is not directly recognized. I need to reboot the system so that it can find the monitor. Here is an extract of dmesg: [87389.923632] usb 1-5: new high-speed USB device number 33 using xhci_hcd [87390.072891] usb 1-5: New USB device found, idVendor=413c, idProduct=8442, bcdDevice= 1.00 [87390.072897] usb 1-5: New USB device strings: Mfr=0, Product=0, SerialNumber=1 [87390.072901] usb 1-5: SerialNumber: E9021071FBE1 [87390.073934] hub 1-5:1.0: USB hub found [87390.074047] hub 1-5:1.0: 6 ports detected [87390.367780] usb 1-5.5: new high-speed USB device number 34 using xhci_hcd [87390.472473] usb 1-5.5: New USB device found, idVendor=0451, idProduct=82ff, bcdDevice= 2.00 [87390.472479] usb 1-5.5: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [87390.475022] hid-generic 0003:0451:82FF.0014: hiddev0,hidraw1: USB HID v1.11 Device [HID 0451:82ff] on usb-:00:14.0-5.5/input0 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 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: Unity Date: Wed Sep 16 09:40:10 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics [17aa:22be] InstallationDate: Installed on 2020-08-24 (22 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20U9004PFR ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=4a93b148-f388-4849-9a18-9e0e4d32c97a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2WET19W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20U9004PFR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2WET19W(1.09):bd07/01/2020:svnLENOVO:pn20U9004PFR:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9004PFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 8 dmi.product.name: 20U9004PFR dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8 dmi.product.version: ThinkPad X1 Carbon Gen 8 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 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/1895794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895803] Re: uvcvideo: add mapping for HEVC payloads
** Also affects: linux (Ubuntu Groovy) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: In Progress ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux (Ubuntu Groovy) Status: In Progress => Confirmed ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Jesse Sung (wenchien) ** Changed in: hwe-next Assignee: (unassigned) => Jesse Sung (wenchien) ** Changed in: hwe-next Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895803 Title: uvcvideo: add mapping for HEVC payloads Status in HWE Next: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: In Progress Status in linux source package in Focal: Confirmed Status in linux source package in Groovy: Confirmed Bug description: == Impact == Add mapping for HEVC so that uvcvideo can support the format. == Fixes == The commit "media: uvcvideo: Add mapping for HEVC payloads", which is already in the maintainer tree: https://patchwork.kernel.org/patch/11577395/ https://git.linuxtv.org/media_tree.git/commit/?id=40b222b56ea81aa636a4aa7a84939786369e726b For 4.15 we also need the "media: videodev2.h: Add v4l2 definition for HEVC" from mainline. == Regression Potential == Low since the patch only introduces a new format. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1895803/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894338] Re: [Dell Inspiron 7570][Samsung Earphones Tuned by AKG] Volume control buttons don't work
The result of my experiments using that testing kernel was: the headset volume up/down button worked, but only when a manual keyboard volume up/down stroke preceded. I speculate that this has got to do with some auto-disabling of the internal laptop port after some time (probable, because a very slight hissing sound when no sound is playing on system stops after ~30sec of such a "no sound" on Windows too and then the same required manual keyboard up/down stroke is required before the jack gets "re-enabled" (I guess?) and receiving headset up/down volume controls successfully). However, you may know better of such stuff. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894338 Title: [Dell Inspiron 7570][Samsung Earphones Tuned by AKG] Volume control buttons don't work Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Invalid Bug description: My earphones are the one coming with Samsung Galaxy S8 (here: https://www.samsung.com/us/mobile/mobile-accessories/phones/samsung- earphones-tuned-by-akg--gray-eo-ig955bsegus) and on my Ubuntu 18.04 (dual-boot with Windows 10, Secure Boot enabled) Trying to set the volume from my earphones' controls doesn't work, no modification on the volume, the sound bar on Ubuntu doesn't appear in order to indicate volume change. I would like to change the master volume, or whatever my common laptop controls do when I up/down the volume controls on my earphones, like it happens on Windows 10. Why does the erroneous behavior of being unable to set volume from my earphones happen? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.10 ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18 Uname: Linux 4.15.0-115-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jason 3523 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 4 23:29:52 2020 InstallationDate: Installed on 2018-09-28 (706 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=el_GR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/17/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.0 dmi.board.name: 02P5YY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.0:bd02/17/2020:svnDellInc.:pnInspiron7570:pvr:rvnDellInc.:rn02P5YY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7570 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-09-28 (718 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic hid_multitouch wmi_bmof dell_wmi snd_hda_intel snd_intel_dspcfg soundwire_intel soundwire_generic_allocation snd_soc_core dell_laptop ledtrig_audio snd_compress soundwire_cadence soundwire_bus dell_smbios snd_hda_codec dell_wmi_descriptor snd_hwdep dcdbas snd_hda_core snd_pcm x86_pkg_temp_thermal intel_powerclamp iwlmvm snd_seq_midi snd_seq_midi_event iwlwifi snd_rawmidi i915 snd_seq snd_seq_device i2c_algo_bit snd_timer drm_kms_helper syscopyarea sysfillrect sysimgblt snd fb_sys_fops drm int3403_thermal soundcore wmi intel_lpss_pci int3402_thermal processor_thermal_device int3400_thermal int340x_thermal_zone intel_soc_dts_iosf acpi_thermal_rel mei_me intel_lpss intel_pch_thermal mfd_core mei efivarfs xhci_pci xhci_hcd i2c_hid Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=el_GR.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 5.9.0-rc3+ x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894338] Re: [Dell Inspiron 7570][Samsung Earphones Tuned by AKG] Volume control buttons don't work
And output of "sudo evtest" with me selecting the 11 device (yes, I booted it by temporarily disabling SecureBoot) No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0: Lid Switch /dev/input/event1: Power Button /dev/input/event2: Sleep Button /dev/input/event3: Power Button /dev/input/event4: AT Translated Set 2 keyboard /dev/input/event5: SynPS/2 Synaptics TouchPad /dev/input/event6: Dell WMI hotkeys /dev/input/event7: DELL07EA:00 06CB:7E92 Mouse /dev/input/event8: DELL07EA:00 06CB:7E92 Touchpad /dev/input/event9: Video Bus /dev/input/event10: Video Bus /dev/input/event11: HDA Intel PCH Headset Jack /dev/input/event12: HDA Intel PCH Headphone Mic /dev/input/event13: HDA Intel PCH HDMI/DP,pcm=3 /dev/input/event14: HDA Intel PCH HDMI/DP,pcm=7 /dev/input/event15: HDA Intel PCH HDMI/DP,pcm=8 /dev/input/event16: HDA Intel PCH HDMI/DP,pcm=9 /dev/input/event17: HDA Intel PCH HDMI/DP,pcm=10 Select the device event number [0-17]: 11 Input driver version is 1.0.1 Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0 Input device name: "HDA Intel PCH Headset Jack" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 114 (KEY_VOLUMEDOWN) Event code 115 (KEY_VOLUMEUP) Event code 164 (KEY_PLAYPAUSE) Event code 582 (KEY_VOICECOMMAND) Event type 5 (EV_SW) Event code 2 (SW_HEADPHONE_INSERT) state 0 Event code 4 (SW_MICROPHONE_INSERT) state 0 Properties: Testing ... (interrupt to exit) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894338 Title: [Dell Inspiron 7570][Samsung Earphones Tuned by AKG] Volume control buttons don't work Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Invalid Bug description: My earphones are the one coming with Samsung Galaxy S8 (here: https://www.samsung.com/us/mobile/mobile-accessories/phones/samsung- earphones-tuned-by-akg--gray-eo-ig955bsegus) and on my Ubuntu 18.04 (dual-boot with Windows 10, Secure Boot enabled) Trying to set the volume from my earphones' controls doesn't work, no modification on the volume, the sound bar on Ubuntu doesn't appear in order to indicate volume change. I would like to change the master volume, or whatever my common laptop controls do when I up/down the volume controls on my earphones, like it happens on Windows 10. Why does the erroneous behavior of being unable to set volume from my earphones happen? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.10 ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18 Uname: Linux 4.15.0-115-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jason 3523 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 4 23:29:52 2020 InstallationDate: Installed on 2018-09-28 (706 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=el_GR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/17/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.0 dmi.board.name: 02P5YY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.0:bd02/17/2020:svnDellInc.:pnInspiron7570:pvr:rvnDellInc.:rn02P5YY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7570 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-09-28 (718 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic hid_multitouch wmi_bmof dell_wmi snd_hda_intel snd_intel_dspcfg soundwire_intel soundwire_generic_allocation snd_soc_core dell_laptop ledtrig_audio snd_compress soundwire_cadence soundwire_bus dell_smbios snd_hda_codec dell_wmi_descriptor snd_hwdep dcdbas snd_hda_core snd_pcm x86_pkg_temp_thermal intel_powerclamp iwlmvm snd_seq_midi snd_seq_midi_event iwlwifi snd_rawmidi i915 snd_seq snd_seq_device i2c_algo_bit snd_timer drm_kms_helper syscopyarea sysfillrect sysimgblt snd fb_sys_fops drm int3403_thermal soundcore wmi intel_lpss_pci int3402_thermal processor_thermal_device int3400_thermal int340x_thermal_zone intel_soc_dts_iosf acpi_thermal_rel mei_me intel_lpss intel_pch_thermal mfd_core mei efivarfs xhci_pci
[Kernel-packages] [Bug 1894338] Re: [Dell Inspiron 7570][Samsung Earphones Tuned by AKG] Volume control buttons don't work
apport information ** Tags added: apport-collected ** Description changed: My earphones are the one coming with Samsung Galaxy S8 (here: https://www.samsung.com/us/mobile/mobile-accessories/phones/samsung- earphones-tuned-by-akg--gray-eo-ig955bsegus) and on my Ubuntu 18.04 (dual-boot with Windows 10, Secure Boot enabled) Trying to set the volume from my earphones' controls doesn't work, no modification on the volume, the sound bar on Ubuntu doesn't appear in order to indicate volume change. I would like to change the master volume, or whatever my common laptop controls do when I up/down the volume controls on my earphones, like it happens on Windows 10. Why does the erroneous behavior of being unable to set volume from my earphones happen? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.10 ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18 Uname: Linux 4.15.0-115-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jason 3523 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 4 23:29:52 2020 InstallationDate: Installed on 2018-09-28 (706 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=el_GR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/17/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.0 dmi.board.name: 02P5YY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.0:bd02/17/2020:svnDellInc.:pnInspiron7570:pvr:rvnDellInc.:rn02P5YY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7570 dmi.sys.vendor: Dell Inc. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.17 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2018-09-28 (718 days ago) + InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) + NonfreeKernelModules: snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic hid_multitouch wmi_bmof dell_wmi snd_hda_intel snd_intel_dspcfg soundwire_intel soundwire_generic_allocation snd_soc_core dell_laptop ledtrig_audio snd_compress soundwire_cadence soundwire_bus dell_smbios snd_hda_codec dell_wmi_descriptor snd_hwdep dcdbas snd_hda_core snd_pcm x86_pkg_temp_thermal intel_powerclamp iwlmvm snd_seq_midi snd_seq_midi_event iwlwifi snd_rawmidi i915 snd_seq snd_seq_device i2c_algo_bit snd_timer drm_kms_helper syscopyarea sysfillrect sysimgblt snd fb_sys_fops drm int3403_thermal soundcore wmi intel_lpss_pci int3402_thermal processor_thermal_device int3400_thermal int340x_thermal_zone intel_soc_dts_iosf acpi_thermal_rel mei_me intel_lpss intel_pch_thermal mfd_core mei efivarfs xhci_pci xhci_hcd i2c_hid + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=el_GR.UTF-8 + SHELL=/bin/bash + Tags: bionic + Uname: Linux 5.9.0-rc3+ x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1894338/+attachment/5411272/+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/1894338 Title: [Dell Inspiron 7570][Samsung Earphones Tuned by AKG] Volume control buttons don't work Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Invalid Bug description: My earphones are the one coming with Samsung Galaxy S8 (here: https://www.samsung.com/us/mobile/mobile-accessories/phones/samsung- earphones-tuned-by-akg--gray-eo-ig955bsegus) and on my Ubuntu 18.04 (dual-boot with Windows 10, Secure Boot enabled) Trying to set the volume from my earphones' controls doesn't work, no modification on the volume, the sound bar on Ubuntu doesn't appear in order to indicate volume change. I would like to change the master volume, or whatever my common laptop controls do when I up/down the volume controls on my earphones, like it happens on Windows 10. Why does the erroneous behavior of being unable to set volume from my earphones happen? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.10 ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18 Uname: Linux 4.15.0-115-generic x86_64 ApportVersion:
[Kernel-packages] [Bug 1895794] Re: Plugging an external monitor on USB-C port does not show up. Need to reboot each time
** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Summary changed: - Plugging an external monitor on USB-C port does not show up. Need to reboot each time + [i915] Plugging an external monitor on USB-C port does not show up. Need to reboot each time -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895794 Title: [i915] Plugging an external monitor on USB-C port does not show up. Need to reboot each time Status in linux package in Ubuntu: New Bug description: Whenever I plug an external monitor (Dell P2720DC) on my ThinkPad X1 (8th gen.) with Ubuntu 20.04, it is not directly recognized. I need to reboot the system so that it can find the monitor. Here is an extract of dmesg: [87389.923632] usb 1-5: new high-speed USB device number 33 using xhci_hcd [87390.072891] usb 1-5: New USB device found, idVendor=413c, idProduct=8442, bcdDevice= 1.00 [87390.072897] usb 1-5: New USB device strings: Mfr=0, Product=0, SerialNumber=1 [87390.072901] usb 1-5: SerialNumber: E9021071FBE1 [87390.073934] hub 1-5:1.0: USB hub found [87390.074047] hub 1-5:1.0: 6 ports detected [87390.367780] usb 1-5.5: new high-speed USB device number 34 using xhci_hcd [87390.472473] usb 1-5.5: New USB device found, idVendor=0451, idProduct=82ff, bcdDevice= 2.00 [87390.472479] usb 1-5.5: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [87390.475022] hid-generic 0003:0451:82FF.0014: hiddev0,hidraw1: USB HID v1.11 Device [HID 0451:82ff] on usb-:00:14.0-5.5/input0 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 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: Unity Date: Wed Sep 16 09:40:10 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics [17aa:22be] InstallationDate: Installed on 2020-08-24 (22 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20U9004PFR ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=4a93b148-f388-4849-9a18-9e0e4d32c97a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2WET19W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20U9004PFR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2WET19W(1.09):bd07/01/2020:svnLENOVO:pn20U9004PFR:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9004PFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 8 dmi.product.name: 20U9004PFR dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8 dmi.product.version: ThinkPad X1 Carbon Gen 8 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 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/1895794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895803] Re: uvcvideo: add mapping for HEVC payloads
** Tags added: oem-priority originate-from-1877920 presidio -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895803 Title: uvcvideo: add mapping for HEVC payloads Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: == Impact == Add mapping for HEVC so that uvcvideo can support the format. == Fixes == The commit "media: uvcvideo: Add mapping for HEVC payloads", which is already in the maintainer tree: https://patchwork.kernel.org/patch/11577395/ https://git.linuxtv.org/media_tree.git/commit/?id=40b222b56ea81aa636a4aa7a84939786369e726b For 4.15 we also need the "media: videodev2.h: Add v4l2 definition for HEVC" from mainline. == Regression Potential == Low since the patch only introduces a new format. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1895803/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895794] [NEW] Plugging an external monitor on USB-C port does not show up. Need to reboot each time
You have been subscribed to a public bug: Whenever I plug an external monitor (Dell P2720DC) on my ThinkPad X1 (8th gen.) with Ubuntu 20.04, it is not directly recognized. I need to reboot the system so that it can find the monitor. Here is an extract of dmesg: [87389.923632] usb 1-5: new high-speed USB device number 33 using xhci_hcd [87390.072891] usb 1-5: New USB device found, idVendor=413c, idProduct=8442, bcdDevice= 1.00 [87390.072897] usb 1-5: New USB device strings: Mfr=0, Product=0, SerialNumber=1 [87390.072901] usb 1-5: SerialNumber: E9021071FBE1 [87390.073934] hub 1-5:1.0: USB hub found [87390.074047] hub 1-5:1.0: 6 ports detected [87390.367780] usb 1-5.5: new high-speed USB device number 34 using xhci_hcd [87390.472473] usb 1-5.5: New USB device found, idVendor=0451, idProduct=82ff, bcdDevice= 2.00 [87390.472479] usb 1-5.5: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [87390.475022] hid-generic 0003:0451:82FF.0014: hiddev0,hidraw1: USB HID v1.11 Device [HID 0451:82ff] on usb-:00:14.0-5.5/input0 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 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: Unity Date: Wed Sep 16 09:40:10 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics [17aa:22be] InstallationDate: Installed on 2020-08-24 (22 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20U9004PFR ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=4a93b148-f388-4849-9a18-9e0e4d32c97a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2WET19W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20U9004PFR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2WET19W(1.09):bd07/01/2020:svnLENOVO:pn20U9004PFR:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9004PFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 8 dmi.product.name: 20U9004PFR dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8 dmi.product.version: ThinkPad X1 Carbon Gen 8 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal thinkpadx1 ubuntu usbc -- Plugging an external monitor on USB-C port does not show up. Need to reboot each time https://bugs.launchpad.net/bugs/1895794 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894338] Re: [Dell Inspiron 7570][Samsung Earphones Tuned by AKG] Volume control buttons don't work
@hui.wang I cannot boot that kernel, since GRUB tells me that it "has invalid signature". -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894338 Title: [Dell Inspiron 7570][Samsung Earphones Tuned by AKG] Volume control buttons don't work Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Invalid Bug description: My earphones are the one coming with Samsung Galaxy S8 (here: https://www.samsung.com/us/mobile/mobile-accessories/phones/samsung- earphones-tuned-by-akg--gray-eo-ig955bsegus) and on my Ubuntu 18.04 (dual-boot with Windows 10, Secure Boot enabled) Trying to set the volume from my earphones' controls doesn't work, no modification on the volume, the sound bar on Ubuntu doesn't appear in order to indicate volume change. I would like to change the master volume, or whatever my common laptop controls do when I up/down the volume controls on my earphones, like it happens on Windows 10. Why does the erroneous behavior of being unable to set volume from my earphones happen? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.10 ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18 Uname: Linux 4.15.0-115-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jason 3523 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 4 23:29:52 2020 InstallationDate: Installed on 2018-09-28 (706 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=el_GR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/17/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.0 dmi.board.name: 02P5YY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.0:bd02/17/2020:svnDellInc.:pnInspiron7570:pvr:rvnDellInc.:rn02P5YY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7570 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893115] Re: Focal update: v5.4.61 upstream stable release
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1893115
Title:
Focal update: v5.4.61 upstream stable release
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Focal:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.4.61 upstream stable release
from git://git.kernel.org/
Documentation/llvm: add documentation on building w/ Clang/LLVM
Documentation/llvm: fix the name of llvm-size
net: wan: wanxl: use allow to pass CROSS_COMPILE_M68k for rebuilding firmware
net: wan: wanxl: use $(M68KCC) instead of $(M68KAS) for rebuilding firmware
x86/boot: kbuild: allow readelf executable to be specified
kbuild: remove PYTHON2 variable
kbuild: remove AS variable
kbuild: replace AS=clang with LLVM_IAS=1
kbuild: support LLVM=1 to switch the default tools to Clang/LLVM
drm/vgem: Replace opencoded version of drm_gem_dumb_map_offset()
gfs2: Improve mmap write vs. punch_hole consistency
gfs2: Never call gfs2_block_zero_range with an open transaction
perf probe: Fix memory leakage when the probe point is not found
khugepaged: khugepaged_test_exit() check mmget_still_valid()
khugepaged: adjust VM_BUG_ON_MM() in __khugepaged_enter()
bcache: avoid nr_stripes overflow in bcache_device_init()
btrfs: export helpers for subvolume name/id resolution
btrfs: don't show full path of bind mounts in subvol=
btrfs: return EROFS for BTRFS_FS_STATE_ERROR cases
btrfs: add wrapper for transaction abort predicate
ALSA: hda/realtek: Add quirk for Samsung Galaxy Flex Book
ALSA: hda/realtek: Add quirk for Samsung Galaxy Book Ion
can: j1939: transport: j1939_session_tx_dat(): fix use-after-free read in
j1939_tp_txtimer()
can: j1939: socket: j1939_sk_bind(): make sure ml_priv is allocated
UBUNTU: [Config] update config for SPI_DYNAMIC
spi: Prevent adding devices below an unregistering controller
romfs: fix uninitialized memory leak in romfs_dev_read()
kernel/relay.c: fix memleak on destroy relay channel
uprobes: __replace_page() avoid BUG in munlock_vma_page()
mm: include CMA pages in lowmem_reserve at boot
mm, page_alloc: fix core hung in free_pcppages_bulk()
RDMA/hfi1: Correct an interlock issue for TID RDMA WRITE request
ext4: fix checking of directory entry validity for inline directories
jbd2: add the missing unlock_buffer() in the error path of
jbd2_write_superblock()
scsi: zfcp: Fix use-after-free in request timeout handlers
drm/amdgpu/display: use GFP_ATOMIC in dcn20_validate_bandwidth_internal
drm/amd/display: Fix EDID parsing after resume from suspend
drm/amd/display: fix pow() crashing when given base 0
kthread: Do not preempt current task if it is going to call schedule()
opp: Enable resources again if they were disabled earlier
scsi: ufs: Add DELAY_BEFORE_LPM quirk for Micron devices
scsi: target: tcmu: Fix crash in tcmu_flush_dcache_range on ARM
media: budget-core: Improve exception handling in budget_register()
rtc: goldfish: Enable interrupt in set_alarm() when necessary
media: vpss: clean up resources in init
Input: psmouse - add a newline when printing 'proto' by sysfs
MIPS: Fix unable to reserve memory for Crash kernel
m68knommu: fix overwriting of bits in ColdFire V3 cache control
svcrdma: Fix another Receive buffer leak
xfs: fix inode quota reservation checks
drm/ttm: fix offset in VMAs with a pg_offs in ttm_bo_vm_access
jffs2: fix UAF problem
ceph: fix use-after-free for fsc->mdsc
swiotlb-xen: use vmalloc_to_page on vmalloc virt addresses
cpufreq: intel_pstate: Fix cpuinfo_max_freq when MSR_TURBO_RATIO_LIMIT is 0
scsi: libfc: Free skb in fc_disc_gpn_id_resp() for valid cases
virtio_ring: Avoid loop when vq is broken in virtqueue_poll
media: camss: fix memory leaks on error handling paths in probe
tools/testing/selftests/cgroup/cgroup_util.c: cg_read_strcmp: fix null
pointer dereference
xfs: Fix UBSAN null-ptr-deref in xfs_sysfs_init
alpha: fix annotation of io{read,write}{16,32}be()
fs/signalfd.c: fix inconsistent return codes for signalfd4
ext4: fix potential negative array index in do_split()
ext4: don't allow overlapping system zones
netfilter: nf_tables: nft_exthdr: the presence return value should be
little-endian
spi: stm32: fixes suspend/resume management
ASoC: q6afe-dai: mark all widgets registers as
[Kernel-packages] [Bug 1888202] Re: package zfsutils-linux 0.8.3-1ubuntu12.1 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status
@Erik, can you provide a full list of packages that you have installed so we can figure this one out? apt list --installed Thanks. ** Changed in: zfs-linux (Ubuntu) Status: Won't Fix => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1888202 Title: package zfsutils-linux 0.8.3-1ubuntu12.1 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 Status in zfs-linux package in Ubuntu: Incomplete Bug description: the upgrade process assumes ZFS-utils is not configured and has exit code 1 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: zfsutils-linux 0.8.3-1ubuntu12.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 AptOrdering: gir1.2-webkit2-4.0:amd64: Install gir1.2-javascriptcoregtk-4.0:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jul 20 10:22:00 2020 ErrorMessage: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-05-15 (1526 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: zfs-linux Title: package zfsutils-linux 0.8.3-1ubuntu12.1 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-05-24 (56 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1888202/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895803] Re: uvcvideo: add mapping for HEVC payloads
** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => 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/1895803 Title: uvcvideo: add mapping for HEVC payloads Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: == Impact == Add mapping for HEVC so that uvcvideo can support the format. == Fixes == The commit "media: uvcvideo: Add mapping for HEVC payloads", which is already in the maintainer tree: https://patchwork.kernel.org/patch/11577395/ https://git.linuxtv.org/media_tree.git/commit/?id=40b222b56ea81aa636a4aa7a84939786369e726b For 4.15 we also need the "media: videodev2.h: Add v4l2 definition for HEVC" from mainline. == Regression Potential == Low since the patch only introduces a new format. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895803/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895803] 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 1895803 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 Bionic) 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/1895803 Title: uvcvideo: add mapping for HEVC payloads Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: == Impact == Add mapping for HEVC so that uvcvideo can support the format. == Fixes == The commit "media: uvcvideo: Add mapping for HEVC payloads", which is already in the maintainer tree: https://patchwork.kernel.org/patch/11577395/ https://git.linuxtv.org/media_tree.git/commit/?id=40b222b56ea81aa636a4aa7a84939786369e726b For 4.15 we also need the "media: videodev2.h: Add v4l2 definition for HEVC" from mainline. == Regression Potential == Low since the patch only introduces a new format. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895803/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895803] [NEW] uvcvideo: add mapping for HEVC payloads
Public bug reported: == Impact == Add mapping for HEVC so that uvcvideo can support the format. == Fixes == The commit "media: uvcvideo: Add mapping for HEVC payloads", which is already in the maintainer tree: https://patchwork.kernel.org/patch/11577395/ https://git.linuxtv.org/media_tree.git/commit/?id=40b222b56ea81aa636a4aa7a84939786369e726b For 4.15 we also need the "media: videodev2.h: Add v4l2 definition for HEVC" from mainline. == Regression Potential == Low since the patch only introduces a new format. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: New ** Affects: linux (Ubuntu Bionic) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Jesse Sung (wenchien) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895803 Title: uvcvideo: add mapping for HEVC payloads Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Bug description: == Impact == Add mapping for HEVC so that uvcvideo can support the format. == Fixes == The commit "media: uvcvideo: Add mapping for HEVC payloads", which is already in the maintainer tree: https://patchwork.kernel.org/patch/11577395/ https://git.linuxtv.org/media_tree.git/commit/?id=40b222b56ea81aa636a4aa7a84939786369e726b For 4.15 we also need the "media: videodev2.h: Add v4l2 definition for HEVC" from mainline. == Regression Potential == Low since the patch only introduces a new format. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895803/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 hey guys had a kernel update just a few minutes ago... at first, suddenly bluetooth stoped working rebooted still nothing (almost drove me nuts) then, don't know why, figured, I'd shut down and boot up again and guess what... bluetooth was back AND THE HSP/HFP IS NOW WORKING ! OS: PopOS 20.04 kernel: 5.4.0-7642-generic laptop: Dell XPS15 headset: Bose QC (first edition) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895669] Re: Add more support to Lenovo ThinkStation P620
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-ucm-conf (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1895669 Title: Add more support to Lenovo ThinkStation P620 Status in HWE Next: New Status in alsa-ucm-conf package in Ubuntu: Confirmed Status in alsa-ucm-conf source package in Focal: Confirmed Status in alsa-ucm-conf source package in Groovy: Confirmed Bug description: [Impact] After upgrading the audio device firmware and doing more testing, we found some new audio issue on Lenovo P620: 1) Rear mic doesn't work. 2) Front and rear mic/line-in don't use hardware gain to control capture volume. [Fix] For 1), add proper PCM stream assignment to the rear microphone. For 2), add MixerElem to let alsa-lib and PulseAudio to pick correct mixer to change HW gain. [Test] With the new UCM applied, rear mic starts to work, and PulseAudio can control the hardware gain. [Regression Potential] The system hasn't hit the market so there's no chance to regression any system in the wild. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1895669/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895669] Re: Add more support to Lenovo ThinkStation P620
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-ucm-conf (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1895669 Title: Add more support to Lenovo ThinkStation P620 Status in HWE Next: New Status in alsa-ucm-conf package in Ubuntu: Confirmed Status in alsa-ucm-conf source package in Focal: Confirmed Status in alsa-ucm-conf source package in Groovy: Confirmed Bug description: [Impact] After upgrading the audio device firmware and doing more testing, we found some new audio issue on Lenovo P620: 1) Rear mic doesn't work. 2) Front and rear mic/line-in don't use hardware gain to control capture volume. [Fix] For 1), add proper PCM stream assignment to the rear microphone. For 2), add MixerElem to let alsa-lib and PulseAudio to pick correct mixer to change HW gain. [Test] With the new UCM applied, rear mic starts to work, and PulseAudio can control the hardware gain. [Regression Potential] The system hasn't hit the market so there's no chance to regression any system in the wild. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1895669/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889342] Re: Thunderbolt Dock Loses Monitors
hi rhpot1991, Would you please try oem5.6 again?! the new version is released. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1889342 Title: Thunderbolt Dock Loses Monitors Status in linux package in Ubuntu: In Progress Bug description: After a suspend or locking the only way to regain external monitors is to unplug and replug the thunderbolt dock back in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 2682 F pulseaudio /dev/snd/controlC0: john 2682 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 00:22:26 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 InstallationDate: Installed on 2020-07-13 (15 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9300 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-42-generic root=UUID=5e141eb0-e03b-4c39-b826-f94e0d2715ea ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.11 dmi.board.name: 0WX9VX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893752] 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 1893752 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 Focal) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1893752 Title: Get the extended DPCD according to the related field in the DPCD registers. Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.6 package in Ubuntu: New Status in linux source package in Focal: Incomplete Status in linux-oem-5.6 source package in Focal: In Progress Bug description: [Impact] Connect the 4K@60Hz monitor on WD19, the monitor can't light. [Fix] As per DP spec, at first check DP_EXTENDED_RECEIVER_CAP_FIELD_PRESENT. If DP_EXTENDED_RECEIVER_CAP_FIELD_PRESENT is 1, read the DP_DP13_DPCD_REV to get the faster capability. If DP_EXTENDED_RECEIVER_CAP_FIELD_PRESENT is 0, read DP_DPCD_REV. [Test] With the patches, connect 4K@60Hz monitor on WD19, the machine can output the video to the monitor and the monitor can light. [Regression] low, Just get one more DPCD from the extended register, compare them and get the faster one. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1893752/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893752] Re: Get the extended DPCD according to the related field in the DPCD registers.
** Changed in: linux (Ubuntu Focal) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu Groovy) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu Focal) Status: Invalid => New ** Changed in: linux (Ubuntu Groovy) Status: Invalid => New ** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: New => In Progress ** No longer affects: linux-oem-5.6 (Ubuntu Groovy) ** No longer affects: linux (Ubuntu Groovy) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1893752 Title: Get the extended DPCD according to the related field in the DPCD registers. Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.6 package in Ubuntu: New Status in linux source package in Focal: Incomplete Status in linux-oem-5.6 source package in Focal: In Progress Bug description: [Impact] Connect the 4K@60Hz monitor on WD19, the monitor can't light. [Fix] As per DP spec, at first check DP_EXTENDED_RECEIVER_CAP_FIELD_PRESENT. If DP_EXTENDED_RECEIVER_CAP_FIELD_PRESENT is 1, read the DP_DP13_DPCD_REV to get the faster capability. If DP_EXTENDED_RECEIVER_CAP_FIELD_PRESENT is 0, read DP_DPCD_REV. [Test] With the patches, connect 4K@60Hz monitor on WD19, the machine can output the video to the monitor and the monitor can light. [Regression] low, Just get one more DPCD from the extended register, compare them and get the faster one. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1893752/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895449] Re: Internet disconnected unexpectly + Xorg freeze while watching html5 video in Chrome
hi Mike Could you simply "apt install linux-oem-5.6" instead!? Then check the issue again. 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/1895449 Title: Internet disconnected unexpectly + Xorg freeze while watching html5 video in Chrome Status in linux package in Ubuntu: In Progress Bug description: A few issues: 1)With Intel(R) Wireless-AC 9560, under kernel 5.4 for Ubuntu 20.04.1, the system sometimes gets disconnected with the network and I get the following error in syslog: iwlwifi: BIOS contains WGDS but no WRDS It is unclear if this is the cause of the problem, but this is likely related to kernel. 2) Watching HTML5 videos on Chrome with Nvidia GPU (440 driver) will sometimes cause xorg freeze. The exact cause is unknown. (Mouse, control all freeze for 5-10 seconds) 3) After Wake up from sleep got the following error on screen sof-audio-pci error: no reply expected, received 0x0 iwlwifi: BIOS contains WGDS but no WRDS 4) After wake up from a long sleep session, sometimes chrome will not render web page correctly or even freeze. It is unclear if its a Chrome problem, or a Nvidia problem, or a Kernel Problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-47-generic 5.4.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gao1931 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Sep 13 09:14:36 2020 InstallationDate: Installed on 2020-08-25 (19 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Inspiron 7591 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=421f18c3-a8c8-4cf4-9b7b-5a7442595b1b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-47-generic N/A linux-backports-modules-5.4.0-47-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/30/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0JKGD4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd06/30/2020:svnDellInc.:pnInspiron7591:pvr:rvnDellInc.:rn0JKGD4:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7591 dmi.product.sku: 0923 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-09-07T23:43:13.736867 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895449/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895449] Re: Internet disconnected unexpectly + Xorg freeze while watching html5 video in Chrome
** Changed in: linux (Ubuntu) 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/1895449 Title: Internet disconnected unexpectly + Xorg freeze while watching html5 video in Chrome Status in linux package in Ubuntu: In Progress Bug description: A few issues: 1)With Intel(R) Wireless-AC 9560, under kernel 5.4 for Ubuntu 20.04.1, the system sometimes gets disconnected with the network and I get the following error in syslog: iwlwifi: BIOS contains WGDS but no WRDS It is unclear if this is the cause of the problem, but this is likely related to kernel. 2) Watching HTML5 videos on Chrome with Nvidia GPU (440 driver) will sometimes cause xorg freeze. The exact cause is unknown. (Mouse, control all freeze for 5-10 seconds) 3) After Wake up from sleep got the following error on screen sof-audio-pci error: no reply expected, received 0x0 iwlwifi: BIOS contains WGDS but no WRDS 4) After wake up from a long sleep session, sometimes chrome will not render web page correctly or even freeze. It is unclear if its a Chrome problem, or a Nvidia problem, or a Kernel Problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-47-generic 5.4.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gao1931 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Sep 13 09:14:36 2020 InstallationDate: Installed on 2020-08-25 (19 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Inspiron 7591 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=421f18c3-a8c8-4cf4-9b7b-5a7442595b1b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-47-generic N/A linux-backports-modules-5.4.0-47-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/30/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0JKGD4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd06/30/2020:svnDellInc.:pnInspiron7591:pvr:rvnDellInc.:rn0JKGD4:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7591 dmi.product.sku: 0923 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-09-07T23:43:13.736867 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895449/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1891151] Re: md: improve IO accounting
For 5.8 this is a simple backport with one conflict caused by function
md_make_request() renamed to md_submit_bio(). Then it can be easily
cherry picked to 5.4 but will need a change to use
generic_{start,end}_io_acct() instead of disk_{start,end}_io_acct(). I
can send you the backported patches if you wish.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1891151
Title:
md: improve IO accounting
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Focal:
Confirmed
Status in linux source package in Groovy:
Confirmed
Bug description:
[IMPACT]
Currently reported IO stats may be incorrect or missing.
This adds correct statistics about in-flight IOs and IO processing time,
interpreted e.g. in iostat as await, svctm, aqu-sz and %util.
[FIX]
Commit:
41d2d848 md: improve io stats accounting
This isn't a clean cherry pick to either 5.8 or 5.4, so some backport
work is necessary.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891151/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895789] [NEW] rfkill hangs when turn on/off bluetooth
Public bug reported: Turn on/off leads to a kernel panic related to rfkill Hardware ID: 201712-26024 OS: 20.04 Desktop Kernel: 5.4.0-48-generic Step to reproduce: 1. Click on/off in the bluetooth settings for a few time 2. Oberserve kernel message as following [ 126.914032] [ cut here ] [ 126.914034] kernel BUG at mm/slub.c:306! [ 126.914041] invalid opcode: [#1] SMP PTI [ 126.914044] CPU: 6 PID: 4741 Comm: gsd-rfkill Tainted: P OE 5.4.0-48-generic #52-Ubuntu [ 126.914045] Hardware name: Dell Inc. XPS 13 9370/0173S1, BIOS 1.13.1 07/08/2020 [ 126.914050] RIP: 0010:__slab_free+0x189/0x330 [ 126.914052] Code: 00 48 89 c7 fa 66 0f 1f 44 00 00 f0 49 0f ba 2c 24 00 72 65 4d 3b 6c 24 20 74 11 49 0f ba 34 24 00 57 9d 0f 1f 44 00 00 eb 9f <0f> 0b 49 3b 5c 24 28 75 e8 48 8b 44 24 28 49 89 4c 24 28 49 89 44 [ 126.914054] RSP: 0018:b46f42d73c90 EFLAGS: 00010246 [ 126.914056] RAX: 9c6931960a00 RBX: 80200015 RCX: 9c6931960a00 [ 126.914057] RDX: 9c6931960a00 RSI: e19511c65800 RDI: 9c695bff9340 [ 126.914058] RBP: b46f42d73d28 R08: 0001 R09: a4d1b6be [ 126.914059] R10: 9c6931960a00 R11: 0001 R12: e19511c65800 [ 126.914060] R13: 9c6931960a00 R14: 9c695bff9340 R15: 9c695bff9340 [ 126.914062] FS: 7fbd905bf840() GS:9c695e58() knlGS: [ 126.914063] CS: 0010 DS: ES: CR0: 80050033 [ 126.914064] CR2: 7fc51ed2 CR3: 0003e6012002 CR4: 003606e0 [ 126.914066] DR0: DR1: DR2: [ 126.914067] DR3: DR6: fffe0ff0 DR7: 0400 [ 126.914068] Call Trace: [ 126.914072] ? finish_wait+0x59/0x70 [ 126.914075] ? wait_woken+0x80/0x80 [ 126.914078] ? kfree_skbmem+0x4e/0x60 [ 126.914080] kmem_cache_free+0x288/0x2b0 [ 126.914085] ? btusb_shutdown_intel_new+0x36/0x60 [btusb] [ 126.914087] kfree_skbmem+0x4e/0x60 [ 126.914089] kfree_skb+0x3a/0xa0 [ 126.914092] btusb_shutdown_intel_new+0x36/0x60 [btusb] [ 126.914108] hci_dev_do_close+0x40c/0x520 [bluetooth] [ 126.914121] hci_rfkill_set_block+0x56/0xa0 [bluetooth] [ 126.914124] rfkill_set_block+0x9b/0x150 [ 126.914127] rfkill_fop_write+0x136/0x1e0 [ 126.914130] __vfs_write+0x1b/0x40 [ 126.914131] vfs_write+0xb9/0x1a0 [ 126.914134] ksys_write+0xb1/0xe0 [ 126.914136] __x64_sys_write+0x1a/0x20 [ 126.914139] do_syscall_64+0x57/0x190 [ 126.914142] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 126.914144] RIP: 0033:0x7fbd9097021f [ 126.914146] Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 59 65 f8 ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2d 44 89 c7 48 89 44 24 08 e8 8c 65 f8 ff 48 [ 126.914147] RSP: 002b:7fffd6047f00 EFLAGS: 0293 ORIG_RAX: 0001 [ 126.914149] RAX: ffda RBX: 7fbd905bf7c0 RCX: 7fbd9097021f [ 126.914150] RDX: 0008 RSI: 5581c4fe4dd0 RDI: 0008 [ 126.914151] RBP: 7fffd6047f50 R08: R09: 000b [ 126.914152] R10: 5581c4fd3dc8 R11: 0293 R12: 0001 [ 126.914153] R13: 7fffd6047fb0 R14: R15: 5581c4fd6020 [ 126.914155] Modules linked in: thunderbolt veth nft_masq nft_chain_nat uhid rfcomm vboxnetadp(OE) xt_CHECKSUM vboxnetflt(OE) xt_MASQUERADE xt_tcpudp vboxdrv(OE) bridge stp llc zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) ebtable_filter ebtables ip6table_raw ip6table_mangle ip6table_nat ip6table_filter ip6_tables iptable_raw iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c iptable_filter bpfilter nf_tables nfnetlink ccm aufs cmac algif_hash algif_skcipher af_alg overlay bnep hid_logitech_hidpp typec_displayport hid_logitech_dj hid_apple binfmt_misc ftdi_sio usbserial snd_usb_audio snd_usbmidi_lib mei_hdcp intel_rapl_msr snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_intel_dspcfg snd_hda_codec x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_core dell_laptop ledtrig_audio snd_hwdep kvm_intel joydev snd_pcm snd_seq_midi snd_seq_midi_event dell_wmi kvm crct10dif_pclmul dell_smbios [ 126.914188] dcdbas snd_rawmidi nls_iso8859_1 cdc_ether ghash_clmulni_intel usbnet aesni_intel r8152 crypto_simd mii snd_seq iwlmvm cryptd glue_helper snd_seq_device intel_wmi_thunderbolt wmi_bmof dell_wmi_descriptor rapl snd_timer intel_cstate mac80211 btusb btrtl btbcm uvcvideo input_leds btintel libarc4 videobuf2_vmalloc bluetooth serio_raw videobuf2_memops videobuf2_v4l2 videobuf2_common videodev iwlwifi ecdh_generic cdc_acm mc ecc i915 snd cfg80211 soundcore rtsx_pci_ms mei_me memstick drm_kms_helper hid_multitouch mei ucsi_acpi typec_ucsi i2c_algo_bit fb_sys_fops processor_thermal_device intel_xhci_usb_role_switch syscopyarea
[Kernel-packages] [Bug 1895789] [NEW] rfkill hangs when turn on/off bluetooth
You have been subscribed to a public bug: Turn on/off leads to a kernel panic related to rfkill Hardware ID: 201712-26024 OS: 20.04 Desktop Kernel: 5.4.0-48-generic Step to reproduce: 1. Click on/off in the bluetooth settings for a few time 2. Oberserve kernel message as following [ 126.914032] [ cut here ] [ 126.914034] kernel BUG at mm/slub.c:306! [ 126.914041] invalid opcode: [#1] SMP PTI [ 126.914044] CPU: 6 PID: 4741 Comm: gsd-rfkill Tainted: P OE 5.4.0-48-generic #52-Ubuntu [ 126.914045] Hardware name: Dell Inc. XPS 13 9370/0173S1, BIOS 1.13.1 07/08/2020 [ 126.914050] RIP: 0010:__slab_free+0x189/0x330 [ 126.914052] Code: 00 48 89 c7 fa 66 0f 1f 44 00 00 f0 49 0f ba 2c 24 00 72 65 4d 3b 6c 24 20 74 11 49 0f ba 34 24 00 57 9d 0f 1f 44 00 00 eb 9f <0f> 0b 49 3b 5c 24 28 75 e8 48 8b 44 24 28 49 89 4c 24 28 49 89 44 [ 126.914054] RSP: 0018:b46f42d73c90 EFLAGS: 00010246 [ 126.914056] RAX: 9c6931960a00 RBX: 80200015 RCX: 9c6931960a00 [ 126.914057] RDX: 9c6931960a00 RSI: e19511c65800 RDI: 9c695bff9340 [ 126.914058] RBP: b46f42d73d28 R08: 0001 R09: a4d1b6be [ 126.914059] R10: 9c6931960a00 R11: 0001 R12: e19511c65800 [ 126.914060] R13: 9c6931960a00 R14: 9c695bff9340 R15: 9c695bff9340 [ 126.914062] FS: 7fbd905bf840() GS:9c695e58() knlGS: [ 126.914063] CS: 0010 DS: ES: CR0: 80050033 [ 126.914064] CR2: 7fc51ed2 CR3: 0003e6012002 CR4: 003606e0 [ 126.914066] DR0: DR1: DR2: [ 126.914067] DR3: DR6: fffe0ff0 DR7: 0400 [ 126.914068] Call Trace: [ 126.914072] ? finish_wait+0x59/0x70 [ 126.914075] ? wait_woken+0x80/0x80 [ 126.914078] ? kfree_skbmem+0x4e/0x60 [ 126.914080] kmem_cache_free+0x288/0x2b0 [ 126.914085] ? btusb_shutdown_intel_new+0x36/0x60 [btusb] [ 126.914087] kfree_skbmem+0x4e/0x60 [ 126.914089] kfree_skb+0x3a/0xa0 [ 126.914092] btusb_shutdown_intel_new+0x36/0x60 [btusb] [ 126.914108] hci_dev_do_close+0x40c/0x520 [bluetooth] [ 126.914121] hci_rfkill_set_block+0x56/0xa0 [bluetooth] [ 126.914124] rfkill_set_block+0x9b/0x150 [ 126.914127] rfkill_fop_write+0x136/0x1e0 [ 126.914130] __vfs_write+0x1b/0x40 [ 126.914131] vfs_write+0xb9/0x1a0 [ 126.914134] ksys_write+0xb1/0xe0 [ 126.914136] __x64_sys_write+0x1a/0x20 [ 126.914139] do_syscall_64+0x57/0x190 [ 126.914142] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 126.914144] RIP: 0033:0x7fbd9097021f [ 126.914146] Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 59 65 f8 ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2d 44 89 c7 48 89 44 24 08 e8 8c 65 f8 ff 48 [ 126.914147] RSP: 002b:7fffd6047f00 EFLAGS: 0293 ORIG_RAX: 0001 [ 126.914149] RAX: ffda RBX: 7fbd905bf7c0 RCX: 7fbd9097021f [ 126.914150] RDX: 0008 RSI: 5581c4fe4dd0 RDI: 0008 [ 126.914151] RBP: 7fffd6047f50 R08: R09: 000b [ 126.914152] R10: 5581c4fd3dc8 R11: 0293 R12: 0001 [ 126.914153] R13: 7fffd6047fb0 R14: R15: 5581c4fd6020 [ 126.914155] Modules linked in: thunderbolt veth nft_masq nft_chain_nat uhid rfcomm vboxnetadp(OE) xt_CHECKSUM vboxnetflt(OE) xt_MASQUERADE xt_tcpudp vboxdrv(OE) bridge stp llc zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) ebtable_filter ebtables ip6table_raw ip6table_mangle ip6table_nat ip6table_filter ip6_tables iptable_raw iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c iptable_filter bpfilter nf_tables nfnetlink ccm aufs cmac algif_hash algif_skcipher af_alg overlay bnep hid_logitech_hidpp typec_displayport hid_logitech_dj hid_apple binfmt_misc ftdi_sio usbserial snd_usb_audio snd_usbmidi_lib mei_hdcp intel_rapl_msr snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_intel_dspcfg snd_hda_codec x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_core dell_laptop ledtrig_audio snd_hwdep kvm_intel joydev snd_pcm snd_seq_midi snd_seq_midi_event dell_wmi kvm crct10dif_pclmul dell_smbios [ 126.914188] dcdbas snd_rawmidi nls_iso8859_1 cdc_ether ghash_clmulni_intel usbnet aesni_intel r8152 crypto_simd mii snd_seq iwlmvm cryptd glue_helper snd_seq_device intel_wmi_thunderbolt wmi_bmof dell_wmi_descriptor rapl snd_timer intel_cstate mac80211 btusb btrtl btbcm uvcvideo input_leds btintel libarc4 videobuf2_vmalloc bluetooth serio_raw videobuf2_memops videobuf2_v4l2 videobuf2_common videodev iwlwifi ecdh_generic cdc_acm mc ecc i915 snd cfg80211 soundcore rtsx_pci_ms mei_me memstick drm_kms_helper hid_multitouch mei ucsi_acpi typec_ucsi i2c_algo_bit fb_sys_fops processor_thermal_device
[Kernel-packages] [Bug 1893752] Re: Get the extended DPCD according to the related field in the DPCD registers.
** Tags added: oem-priority originate-from-1880831 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1893752 Title: Get the extended DPCD according to the related field in the DPCD registers. Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.6 package in Ubuntu: New Status in linux source package in Focal: Incomplete Status in linux-oem-5.6 source package in Focal: New Status in linux source package in Groovy: Incomplete Status in linux-oem-5.6 source package in Groovy: New Bug description: [Impact] Connect the 4K@60Hz monitor on WD19, the monitor can't light. [Fix] As per DP spec, at first check DP_EXTENDED_RECEIVER_CAP_FIELD_PRESENT. If DP_EXTENDED_RECEIVER_CAP_FIELD_PRESENT is 1, read the DP_DP13_DPCD_REV to get the faster capability. If DP_EXTENDED_RECEIVER_CAP_FIELD_PRESENT is 0, read DP_DPCD_REV. [Test] With the patches, connect 4K@60Hz monitor on WD19, the machine can output the video to the monitor and the monitor can light. [Regression] low, Just get one more DPCD from the extended register, compare them and get the faster one. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1893752/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893752] Re: Get the right configuration according to the related field of dpcd
** Description changed: [Impact] + Connect the 4K@60Hz monitor on WD19, the monitor can't light. [Fix] + As per DP spec, at first check DP_EXTENDED_RECEIVER_CAP_FIELD_PRESENT. + If DP_EXTENDED_RECEIVER_CAP_FIELD_PRESENT is 1, read the DP_DP13_DPCD_REV to get the faster capability. If DP_EXTENDED_RECEIVER_CAP_FIELD_PRESENT is 0, read DP_DPCD_REV. [Test] + With the patches, connect 4K@60Hz monitor on WD19, the machine can output the video to the monitor and the monitor can light. [Regression] + low, Just get one more DPCD from the extended register, compare them and get the faster one. ** Summary changed: - Get the right configuration according to the related field of dpcd + Get the extended DPCD according to the related field in the DPCD registers. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1893752 Title: Get the extended DPCD according to the related field in the DPCD registers. Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.6 package in Ubuntu: New Status in linux source package in Focal: Incomplete Status in linux-oem-5.6 source package in Focal: New Status in linux source package in Groovy: Incomplete Status in linux-oem-5.6 source package in Groovy: New Bug description: [Impact] Connect the 4K@60Hz monitor on WD19, the monitor can't light. [Fix] As per DP spec, at first check DP_EXTENDED_RECEIVER_CAP_FIELD_PRESENT. If DP_EXTENDED_RECEIVER_CAP_FIELD_PRESENT is 1, read the DP_DP13_DPCD_REV to get the faster capability. If DP_EXTENDED_RECEIVER_CAP_FIELD_PRESENT is 0, read DP_DPCD_REV. [Test] With the patches, connect 4K@60Hz monitor on WD19, the machine can output the video to the monitor and the monitor can light. [Regression] low, Just get one more DPCD from the extended register, compare them and get the faster one. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1893752/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
And on Bionic we only need to do so for amd64 Here is a new MP for Bionic: https://code.launchpad.net/~paelzer/britney/hints-ubuntu-bionic-disable-systemd-v2/+merge/390793 ** Branch linked: lp:~paelzer/britney/hints-ubuntu-bionic-disable- systemd-v2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration Status in build-essential package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in iputils package in Ubuntu: Invalid Status in kbd package in Ubuntu: Invalid Status in linux-meta package in Ubuntu: Invalid Status in ntpsec package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: Invalid Status in linux-meta source package in Bionic: New Status in systemd source package in Bionic: New Status in build-essential source package in Focal: Confirmed Status in linux-meta source package in Focal: New Status in qemu source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in util-linux source package in Focal: Confirmed Bug description: Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B 0% => P 47%/) FFF.FFF.FF....F. timedated (F 2% S 0% B 0% => P 97%/) ...F upstream (F 17% S 0% B 0% => P 82%/) .F..F.F.FFF...F. systemd-fsckd (F 32% S 0% B 0% => P 67%/) FFF..FF..F.FF..F root-unittests (F 10% S 0% B 0% => P 90%/) FFF...F. arm64 tests-in-lxd (F 40% S 0% B 2% => P 57%/) F.B...FFF.FF..F..F.FFF.F logind (F 2% S 0% B 2% => P 95%/) ..B...F. upstream (F 22% S 0% B 2% => P 75%/) ...F.FB.F.F.F..FFF.F root-unittests (F 12% S 0% B 2% => P 85%/) ..B.F...F.FF...F (I'm sure LP will make this unreadable, but is is nice in monospace) Whatever the root cause is - the success rate of these has reduced so much that the (even formerly questionable) practice of retry-until- success won't work anymore. I have run the two tests in a local VM and systemd-fsckd works there while tests-in-lxd seems to trip over the old flaky fellow being "boot-and-services". We had the discussion in the past, but I think I need to again bring up the suggestion to skip "tests-in-lxd" and "systemd-fsckd" until they
[Kernel-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
The problem with Xenial is that there it isn't just flaky "systemd- fsckd" much more seems to be broken. I'll revise my Bionic MP, but for Xenial I'd like to hear from ddstreet/rbalint how they think we should go on there ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration Status in build-essential package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in iputils package in Ubuntu: Invalid Status in kbd package in Ubuntu: Invalid Status in linux-meta package in Ubuntu: Invalid Status in ntpsec package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: Invalid Status in linux-meta source package in Bionic: New Status in systemd source package in Bionic: New Status in build-essential source package in Focal: Confirmed Status in linux-meta source package in Focal: New Status in qemu source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in util-linux source package in Focal: Confirmed Bug description: Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B 0% => P 47%/) FFF.FFF.FF....F. timedated (F 2% S 0% B 0% => P 97%/) ...F upstream (F 17% S 0% B 0% => P 82%/) .F..F.F.FFF...F. systemd-fsckd (F 32% S 0% B 0% => P 67%/) FFF..FF..F.FF..F root-unittests (F 10% S 0% B 0% => P 90%/) FFF...F. arm64 tests-in-lxd (F 40% S 0% B 2% => P 57%/) F.B...FFF.FF..F..F.FFF.F logind (F 2% S 0% B 2% => P 95%/) ..B...F. upstream (F 22% S 0% B 2% => P 75%/) ...F.FB.F.F.F..FFF.F root-unittests (F 12% S 0% B 2% => P 85%/) ..B.F...F.FF...F (I'm sure LP will make this unreadable, but is is nice in monospace) Whatever the root cause is - the success rate of these has reduced so much that the (even formerly questionable) practice of retry-until- success won't work anymore. I have run the two tests in a local VM and systemd-fsckd works there while tests-in-lxd seems to trip over the old flaky fellow being "boot-and-services". We had the discussion in the past, but I think I need to again bring up the suggestion to skip "tests-in-lxd" and "systemd-fsckd" until they are on reasonable success
