[Kernel-packages] [Bug 1848417] Re: btrfs/172 from ubuntu_xfstests_btrfs failed on B/D
** Summary changed: - btrfs/172 from ubuntu_xfstests_btrfs failed on D + btrfs/172 from ubuntu_xfstests_btrfs failed on B/D ** Tags added: 4.15 bionic ** Tags added: sru-20200316 ** 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/1848417 Title: btrfs/172 from ubuntu_xfstests_btrfs failed on B/D Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Status in linux source package in Disco: Confirmed Bug description: Issue found on node amd64 node "kili" btrfs/172 - output mismatch (see /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/172.out.bad) --- tests/btrfs/172.out2019-10-16 10:51:13.104701643 + +++ /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/172.out.bad 2019-10-16 11:12:14.297724635 + @@ -1,2 +1,5 @@ QA output created by 172 +fallocate: No space left on device +fallocate: No space left on device +fallocate: No space left on device Silence is golden ... (Run 'diff -u /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/172.out /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/172.out.bad' to see the entire diff) $ diff -u /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/172.out /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/172.out.bad --- /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/172.out 2019-10-16 10:51:13.104701643 + +++ /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/172.out.bad 2019-10-16 11:12:14.297724635 + @@ -1,2 +1,5 @@ QA output created by 172 +fallocate: No space left on device +fallocate: No space left on device +fallocate: No space left on device Silence is golden Syslog: Oct 16 11:12:12 kili ubuntu: run xfstest btrfs/172 Oct 16 11:12:12 kili kernel: [ 1871.836387] run fstests btrfs/172 at 2019-10-16 11:12:12 Oct 16 11:12:12 kili kernel: [ 1872.017295] BTRFS info (device sdb1): disk space caching is enabled Oct 16 11:12:12 kili kernel: [ 1872.017299] BTRFS info (device sdb1): has skinny extents Oct 16 11:12:12 kili kernel: [ 1872.020831] BTRFS info (device sdb1): enabling ssd optimizations Oct 16 11:12:12 kili kernel: [ 1872.126224] BTRFS: device fsid 319cee42-25fa-4cac-8de6-5230ebedf99f devid 1 transid 5 /dev/sdb2 Oct 16 11:12:12 kili kernel: [ 1872.151545] BTRFS info (device sdb2): max_inline at 0 Oct 16 11:12:12 kili kernel: [ 1872.151550] BTRFS info (device sdb2): setting nodatacow, compression disabled Oct 16 11:12:12 kili kernel: [ 1872.151552] BTRFS info (device sdb2): disk space caching is enabled Oct 16 11:12:12 kili kernel: [ 1872.151553] BTRFS info (device sdb2): has skinny extents Oct 16 11:12:12 kili kernel: [ 1872.151555] BTRFS info (device sdb2): flagging fs with big metadata feature Oct 16 11:12:12 kili kernel: [ 1872.158799] BTRFS info (device sdb2): enabling ssd optimizations Oct 16 11:12:12 kili kernel: [ 1872.159342] BTRFS info (device sdb2): checking UUID tree Oct 16 11:12:14 kili systemd[1894]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dtest.mount: Succeeded. Oct 16 11:12:14 kili systemd[1]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dtest.mount: Succeeded. Oct 16 11:12:14 kili systemd[1]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded. Oct 16 11:12:14 kili systemd[1894]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded. Oct 16 11:12:14 kili kernel: [ 1873.906816] BTRFS info (device sdb2): disk space caching is enabled Oct 16 11:12:14 kili kernel: [ 1873.906819] BTRFS info (device sdb2): has skinny extents Oct 16 11:12:14 kili kernel: [ 1873.909937] BTRFS info (device sdb2): enabling ssd optimizations Oct 16 11:12:14 kili systemd[1894]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded. Oct 16 11:12:14 kili systemd[1]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-31-generic 5.0.0-31.33 ProcVersionSignature: User Name 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 16 10:41 seq crw-rw 1 root audio 116, 33 Oct 16 10:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
[Kernel-packages] [Bug 1848418] Re: btrfs/182 from ubuntu_xfstests_btrfs failed on B/D
** Summary changed: - btrfs/182 from ubuntu_xfstests_btrfs failed on D + btrfs/182 from ubuntu_xfstests_btrfs failed on B/D ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: 4.15 bionic sru-20200316 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848418 Title: btrfs/182 from ubuntu_xfstests_btrfs failed on B/D Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Status in linux source package in Disco: Confirmed Bug description: Issue found on node amd64 node "kili" btrfs/182 - output mismatch (see /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/182.out.bad) --- tests/btrfs/182.out2019-10-16 10:51:13.104701643 + +++ /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/182.out.bad 2019-10-16 11:12:32.817591531 + @@ -1,2 +1,4 @@ QA output created by 182 +ERROR: error during balancing '/home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch': No space left on device +There may be more info in syslog - try dmesg | tail Silence is golden ... (Run 'diff -u /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/182.out /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/182.out.bad' to see the entire diff) $ diff -u /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/182.out /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/182.out.bad --- /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/182.out 2019-10-16 10:51:13.104701643 + +++ /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/182.out.bad 2019-10-16 11:12:32.817591531 + @@ -1,2 +1,4 @@ QA output created by 182 +ERROR: error during balancing '/home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch': No space left on device +There may be more info in syslog - try dmesg | tail Silence is golden Syslog: Oct 16 11:12:28 kili ubuntu: run xfstest btrfs/182 Oct 16 11:12:28 kili kernel: [ 1887.982615] run fstests btrfs/182 at 2019-10-16 11:12:28 Oct 16 11:12:28 kili kernel: [ 1888.168789] BTRFS info (device sdb1): disk space caching is enabled Oct 16 11:12:28 kili kernel: [ 1888.168791] BTRFS info (device sdb1): has skinny extents Oct 16 11:12:28 kili kernel: [ 1888.171922] BTRFS info (device sdb1): enabling ssd optimizations Oct 16 11:12:28 kili kernel: [ 1888.254332] BTRFS: device fsid 31ebd16f-0464-4373-b2d9-d3beef4d1bf4 devid 1 transid 5 /dev/sdb2 Oct 16 11:12:28 kili kernel: [ 1888.274317] BTRFS info (device sdb2): disk space caching is enabled Oct 16 11:12:28 kili kernel: [ 1888.274319] BTRFS info (device sdb2): has skinny extents Oct 16 11:12:28 kili kernel: [ 1888.274320] BTRFS info (device sdb2): flagging fs with big metadata feature Oct 16 11:12:28 kili kernel: [ 1888.282340] BTRFS info (device sdb2): enabling ssd optimizations Oct 16 11:12:28 kili kernel: [ 1888.286045] BTRFS info (device sdb2): checking UUID tree Oct 16 11:12:32 kili kernel: [ 1892.268108] BTRFS info (device sdb2): balance: start -m -s Oct 16 11:12:32 kili kernel: [ 1892.268284] BTRFS info (device sdb2): relocating block group 1048576 flags system Oct 16 11:12:32 kili kernel: [ 1892.272632] BTRFS info (device sdb2): found 1 extents Oct 16 11:12:32 kili kernel: [ 1892.275676] BTRFS info (device sdb2): 2 enospc errors during balance Oct 16 11:12:32 kili kernel: [ 1892.275678] BTRFS info (device sdb2): balance: ended with status: -28 Oct 16 11:12:32 kili systemd[1894]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dtest.mount: Succeeded. Oct 16 11:12:32 kili systemd[1]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dtest.mount: Succeeded. Oct 16 11:12:32 kili systemd[1]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded. Oct 16 11:12:32 kili systemd[1894]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded. Oct 16 11:12:32 kili kernel: [ 1892.433637] BTRFS info (device sdb2): disk space caching is enabled Oct 16 11:12:32 kili kernel: [ 1892.433639] BTRFS info (device sdb2): has skinny extents Oct 16 11:12:32 kili kernel: [ 1892.437048] BTRFS info (device sdb2): enabling ssd optimizations Oct 16 11:12:32 kili systemd[1894]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded. Oct 16 11:12:32 kili systemd[1]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded. ProblemTy
[Kernel-packages] [Bug 1869656] [NEW] generic/102 from ubuntu_xfstests_btrfs failed on B
Public bug reported: generic/102- output mismatch (see /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/102.out.bad) --- tests/generic/102.out 2020-03-28 21:59:25.662678431 + +++ /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/102.out.bad 2020-03-28 23:25:57.173907799 + @@ -1,21 +1,14 @@ QA output created by 102 wrote 838860800/838860800 bytes at offset 0 XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec) -wrote 838860800/838860800 bytes at offset 0 -XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec) -wrote 838860800/838860800 bytes at offset 0 -XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec) ... (Run 'diff -u /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/102.out /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/102.out.bad' to see the entire diff) ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Tags: 4.15 bionic sru-20200316 ubuntu-xfstests-btrfs ** Tags added: 4.15 bionic sru-20200316 ubuntu-xfstests-btrfs ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** 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/1869656 Title: generic/102 from ubuntu_xfstests_btrfs failed on B Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Bug description: generic/102- output mismatch (see /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/102.out.bad) --- tests/generic/102.out 2020-03-28 21:59:25.662678431 + +++ /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/102.out.bad 2020-03-28 23:25:57.173907799 + @@ -1,21 +1,14 @@ QA output created by 102 wrote 838860800/838860800 bytes at offset 0 XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec) -wrote 838860800/838860800 bytes at offset 0 -XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec) -wrote 838860800/838860800 bytes at offset 0 -XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec) ... (Run 'diff -u /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/102.out /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/102.out.bad' to see the entire diff) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1869656/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850439] Re: No sound on ASUS UX534FT
@Kai-Heng Feng I just enabled the proposed packages and updated all. It didn't help. Still no sound through internal speakers on ASUS UX534FT -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869657] [NEW] generic/089 from ubuntu_xfstests_btrfs failed on B
Public bug reported: generic/089- output mismatch (see /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/089.out.bad) --- tests/generic/089.out 2020-03-28 21:59:25.662678431 + +++ /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/089.out.bad 2020-03-28 23:11:13.045714612 + @@ -2,12 +2,3366 @@ completed 50 iterations completed 50 iterations completed 50 iterations +can't rename t_mtab.tmp to t_mtab: No space left on device +can't rename t_mtab.tmp to t_mtab: No space left on device +can't rename t_mtab.tmp to t_mtab: No space left on device +can't rename t_mtab.tmp to t_mtab: No space left on device ... (Run 'diff -u /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/089.out /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/089.out.bad' to see the entire diff) ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Tags: 4.15 bionic sru-20200316 ubuntu-xfstests-btrfs ** Tags added: 4.15 bionic sru-20200316 ubuntu-xfstests-btrfs ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** 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/1869657 Title: generic/089 from ubuntu_xfstests_btrfs failed on B Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Bug description: generic/089- output mismatch (see /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/089.out.bad) --- tests/generic/089.out 2020-03-28 21:59:25.662678431 + +++ /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/089.out.bad 2020-03-28 23:11:13.045714612 + @@ -2,12 +2,3366 @@ completed 50 iterations completed 50 iterations completed 50 iterations +can't rename t_mtab.tmp to t_mtab: No space left on device +can't rename t_mtab.tmp to t_mtab: No space left on device +can't rename t_mtab.tmp to t_mtab: No space left on device +can't rename t_mtab.tmp to t_mtab: No space left on device ... (Run 'diff -u /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/089.out /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/089.out.bad' to see the entire diff) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1869657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848422] Re: btrfs/193 from ubuntu_xfstests_btrfs failed on B/D
** Summary changed: - btrfs/193 from ubuntu_xfstests_btrfs failed on D + btrfs/193 from ubuntu_xfstests_btrfs failed on B/D ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: sru-20200316 ** Tags added: 4.15 bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848422 Title: btrfs/193 from ubuntu_xfstests_btrfs failed on B/D Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Status in linux source package in Disco: Confirmed Bug description: Issue found on node amd64 node "kili" btrfs/193 - output mismatch (see /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/193.out.bad) --- tests/btrfs/193.out2019-10-16 10:51:13.104701643 + +++ /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/193.out.bad 2019-10-16 11:16:44.831139679 + @@ -4,5 +4,4 @@ wrote 4096/4096 bytes at offset 268435456 XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec) fallocate: Disk quota exceeded -wrote 201326592/201326592 bytes at offset 0 -XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec) +pwrite: Disk quota exceeded ... (Run 'diff -u /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/193.out /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/193.out.bad' to see the entire diff) $ diff -u /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/193.out /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/193.out.bad --- /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/193.out 2019-10-16 10:51:13.104701643 + +++ /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/193.out.bad 2019-10-16 11:16:44.831139679 + @@ -4,5 +4,4 @@ wrote 4096/4096 bytes at offset 268435456 XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec) fallocate: Disk quota exceeded -wrote 201326592/201326592 bytes at offset 0 -XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec) +pwrite: Disk quota exceeded Syslog: Oct 16 11:16:43 kili ubuntu: run xfstest btrfs/193 Oct 16 11:16:43 kili kernel: [ 2143.183330] run fstests btrfs/193 at 2019-10-16 11:16:43 Oct 16 11:16:43 kili kernel: [ 2143.463462] BTRFS: device fsid 1f04a683-4df8-4adb-9cac-13a57fb79aa0 devid 1 transid 5 /dev/sdb2 Oct 16 11:16:43 kili kernel: [ 2143.483470] BTRFS info (device sdb2): disk space caching is enabled Oct 16 11:16:43 kili kernel: [ 2143.483474] BTRFS info (device sdb2): has skinny extents Oct 16 11:16:43 kili kernel: [ 2143.483475] BTRFS info (device sdb2): flagging fs with big metadata feature Oct 16 11:16:43 kili kernel: [ 2143.487752] BTRFS info (device sdb2): enabling ssd optimizations Oct 16 11:16:43 kili kernel: [ 2143.488327] BTRFS info (device sdb2): checking UUID tree Oct 16 11:16:43 kili kernel: [ 2143.493619] BTRFS info (device sdb2): qgroup scan completed (inconsistency flag cleared) Oct 16 11:16:43 kili kernel: [ 2143.496960] BTRFS info (device sdb2): qgroup scan completed (inconsistency flag cleared) Oct 16 11:16:44 kili systemd[1894]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dtest.mount: Succeeded. Oct 16 11:16:44 kili systemd[1]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dtest.mount: Succeeded. Oct 16 11:16:44 kili systemd[1]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded. Oct 16 11:16:44 kili systemd[1894]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded. Oct 16 11:16:44 kili kernel: [ 2144.448728] BTRFS info (device sdb2): disk space caching is enabled Oct 16 11:16:44 kili kernel: [ 2144.448730] BTRFS info (device sdb2): has skinny extents Oct 16 11:16:44 kili kernel: [ 2144.452303] BTRFS info (device sdb2): enabling ssd optimizations Oct 16 11:16:44 kili systemd[1894]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded. Oct 16 11:16:44 kili systemd[1]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-31-generic 5.0.0-31.33 ProcVersionSignature: User Name 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 16 10:41 seq crw-rw 1 root audio 116, 33 Oct 16 10:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersi
[Kernel-packages] [Bug 1869660] [NEW] btrfs/186 from ubuntu_xfstests_btrfs failed on B
Public bug reported: btrfs/186 - output mismatch (see /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/186.out.bad) --- tests/btrfs/186.out2020-03-28 21:59:25.634678045 + +++ /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/186.out.bad 2020-03-28 22:34:58.104793939 + @@ -9,6 +9,4 @@ 0110592 At subvol sv File content in the new filesystem: -000 ea ea ea ea ea ea ea ea ea ea ea ea ea ea ea ea -* -0110592 +000 ... (Run 'diff -u /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/186.out /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/186.out.bad' to see the entire diff) ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: Incomplete ** Tags: 4.15 amd64 bionic sru-20200316 ubuntu-xfstests-btrfs ** Tags added: 4.15 amd64 bionic sru-20200316 ubuntu-xfstests-btrfs ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** 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/1869660 Title: btrfs/186 from ubuntu_xfstests_btrfs failed on B Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: btrfs/186 - output mismatch (see /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/186.out.bad) --- tests/btrfs/186.out2020-03-28 21:59:25.634678045 + +++ /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/186.out.bad 2020-03-28 22:34:58.104793939 + @@ -9,6 +9,4 @@ 0110592 At subvol sv File content in the new filesystem: -000 ea ea ea ea ea ea ea ea ea ea ea ea ea ea ea ea -* -0110592 +000 ... (Run 'diff -u /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/186.out /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/186.out.bad' to see the entire diff) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1869660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848421] Re: btrfs/187 from ubuntu_xfstests_btrfs failed on D
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: 4.15 bionic sru-20200316 ** Summary changed: - btrfs/187 from ubuntu_xfstests_btrfs failed on D + btrfs/187 from ubuntu_xfstests_btrfs failed on B/D -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848421 Title: btrfs/187 from ubuntu_xfstests_btrfs failed on B/D Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Status in linux source package in Disco: Confirmed Bug description: Issue found on node amd64 node "kili" btrfs/187 - output mismatch (see /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/187.out.bad) --- tests/btrfs/187.out2019-10-16 10:51:13.104701643 + +++ /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/187.out.bad 2019-10-16 11:16:39.519207382 + @@ -1,3 +1,6 @@ QA output created by 187 Create a readonly snapshot of 'SCRATCH_MNT' in 'SCRATCH_MNT/snap1' Create a readonly snapshot of 'SCRATCH_MNT' in 'SCRATCH_MNT/snap2' +[ 2109.330631] BTRFS error (device sdb2): parent transid verify failed on 18814697472 wanted 396 found 415 +[ 2113.554514] BTRFS error (device sdb2): parent transid verify failed on 19921420288 wanted 423 found 445 +[ 2117.693224] BTRFS error (device sdb2): parent transid verify failed on 20514979840 wanted 446 found 458 ... (Run 'diff -u /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/187.out /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/187.out.bad' to see the entire diff) $ diff -u /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/187.out /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/187.out.bad --- /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/187.out 2019-10-16 10:51:13.104701643 + +++ /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/187.out.bad 2019-10-16 11:16:39.519207382 + @@ -1,3 +1,6 @@ QA output created by 187 Create a readonly snapshot of 'SCRATCH_MNT' in 'SCRATCH_MNT/snap1' Create a readonly snapshot of 'SCRATCH_MNT' in 'SCRATCH_MNT/snap2' +[ 2109.330631] BTRFS error (device sdb2): parent transid verify failed on 18814697472 wanted 396 found 415 +[ 2113.554514] BTRFS error (device sdb2): parent transid verify failed on 19921420288 wanted 423 found 445 +[ 2117.693224] BTRFS error (device sdb2): parent transid verify failed on 20514979840 wanted 446 found 458 Please find the attachment for the syslog. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-31-generic 5.0.0-31.33 ProcVersionSignature: User Name 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 16 10:41 seq crw-rw 1 root audio 116, 33 Oct 16 10:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Oct 17 04:33:53 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S2600WTT PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=72dbdd83-0e2a-4fdd-99ca-70869e30b925 ro RelatedPackageVersions: linux-restricted-modules-5.0.0-31-generic N/A linux-backports-modules-5.0.0-31-generic N/A linux-firmware1.178.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/19/2015 dmi.bios.vendor: Intel Corporation dmi.bios.version: SE5C610.86B.01.01.1008.031920151331 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: S2600WTT dmi.board.vendor: Intel Corporation dmi.board.version: G92187-350 dmi.chassis.asset.tag: dmi.chassis.type: 23 dmi.chassis.vendor: ... dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorporation:bvrSE5C610.86B.01.01.1008.031920151331:bd03/19/2015:svnIntelCorporation:pnS2600WTT:pvr:rvnIntelCorporation:rnS2600WTT:rvrG92187-350:cvn...
[Kernel-packages] [Bug 1869656] 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 1869656 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/1869656 Title: generic/102 from ubuntu_xfstests_btrfs failed on B Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: generic/102- output mismatch (see /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/102.out.bad) --- tests/generic/102.out 2020-03-28 21:59:25.662678431 + +++ /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/102.out.bad 2020-03-28 23:25:57.173907799 + @@ -1,21 +1,14 @@ QA output created by 102 wrote 838860800/838860800 bytes at offset 0 XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec) -wrote 838860800/838860800 bytes at offset 0 -XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec) -wrote 838860800/838860800 bytes at offset 0 -XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec) ... (Run 'diff -u /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/102.out /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/102.out.bad' to see the entire diff) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1869656/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869657] 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 1869657 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/1869657 Title: generic/089 from ubuntu_xfstests_btrfs failed on B Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: generic/089- output mismatch (see /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/089.out.bad) --- tests/generic/089.out 2020-03-28 21:59:25.662678431 + +++ /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/089.out.bad 2020-03-28 23:11:13.045714612 + @@ -2,12 +2,3366 @@ completed 50 iterations completed 50 iterations completed 50 iterations +can't rename t_mtab.tmp to t_mtab: No space left on device +can't rename t_mtab.tmp to t_mtab: No space left on device +can't rename t_mtab.tmp to t_mtab: No space left on device +can't rename t_mtab.tmp to t_mtab: No space left on device ... (Run 'diff -u /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/089.out /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/089.out.bad' to see the entire diff) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1869657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869660] 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 1869660 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/1869660 Title: btrfs/186 from ubuntu_xfstests_btrfs failed on B Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: btrfs/186 - output mismatch (see /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/186.out.bad) --- tests/btrfs/186.out2020-03-28 21:59:25.634678045 + +++ /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/186.out.bad 2020-03-28 22:34:58.104793939 + @@ -9,6 +9,4 @@ 0110592 At subvol sv File content in the new filesystem: -000 ea ea ea ea ea ea ea ea ea ea ea ea ea ea ea ea -* -0110592 +000 ... (Run 'diff -u /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/186.out /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/186.out.bad' to see the entire diff) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1869660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850439] Re: No sound on ASUS UX534FT
Alright, can you please attach `dmesg` and `sudo lspci -vvnn`, 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/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen
** Changed in: linux Status: Unknown => 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/1767654 Title: [Intel Braswell] Cursor gets stuck on left side of the screen Status in Linux: New Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When moving the cursor to the left side of the screen, it stops close to the edge. The cursor still moves over in the area but invisible until I move it out of the area. When it doesn't do this, glitching occurs on the screen where the cursor is until I log out. And on screen cast it shows the cursor going to the side of the screen and moving. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 09:49:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060] InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 initrd=boot\initrd.img-4.15.0-20-generic SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2017 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-408 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1767654/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863824] Re: ThinkPad X1 Yoga not deactivating keyboard & trackpad when going on tablet mode
Does this also happen to the default Ubuntu Gnome desktop? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863824 Title: ThinkPad X1 Yoga not deactivating keyboard & trackpad when going on tablet mode Status in kubuntu-meta package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: My 4th gen ThinkPad X1 Yoga is unusable as a tablet because it won't deactivate the keyboard and trackpad when I flip it to tablet mode. It's also the same when I try it on Kubuntu 20.04. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.18.0 KDE Frameworks Version: 5.67.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-29-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz Memory: 15.3 GiB of RAM ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: kubuntu-desktop 1.387 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: KDE Date: Tue Feb 18 20:33:35 2020 InstallationDate: Installed on 2020-01-19 (30 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: kubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: KDE Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-25 (29 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200120) Package: linux-firmware 1.186 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Tags: focal focal Uname: Linux 5.4.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yamiyuki 3578 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-19 (69 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20SA0002US NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=8644acd5-759a-4daa-a34c-75ad3f4c5c12 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-03-21 (7 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET19W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20SA0002US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2QET19W(1.13):bd01/15/2020:svnLENOVO:pn20SA0002US:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20SA0002US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 4th dmi.product.name: 20SA0002US dmi.product.sku: LENOVO_MT_20SA_BU_Think_FM_ThinkPad X1 Yoga 4th dmi.product.version: ThinkPad X1 Yoga 4th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1863824/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860764] Re: Line out audio device is missing after resume-from-suspend
Can you please identify from what kernel version did the regression start? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860764 Title: Line out audio device is missing after resume-from-suspend Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: this problem happened after i updated system when i power on after sleeping i have problem with sounds. it doesn't work. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob2511 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (362 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Tags: eoan Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (79 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob1897 F pulseaudio /dev/snd/controlC2: rob1897 F pulseaudio /dev/snd/controlC1: rob1897 F pulseaudio /dev/snd/pcmC1D0p: rob1897 F...m pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (428 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=574eb112-448b-4cfc-bed7-2c5a1ba42abf ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.183.4 RfKill: Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (145 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860764/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869570] Re: watchdog: BUG: soft lockup - CPU#11 stuck for 197s! [swapper/11:0]
Can you please enable proposed [1] and test linux kernel 5.4.0-20? [1] https://wiki.ubuntu.com/Testing/EnableProposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1869570 Title: watchdog: BUG: soft lockup - CPU#11 stuck for 197s! [swapper/11:0] Status in linux package in Ubuntu: Confirmed Bug description: System did not boot at all after upgrade to latest kernel version ProblemType: KernelOops DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-18-generic 5.4.0-18.22 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1134 F pulseaudio kettlitz 1697 F pulseaudio Date: Sun Mar 29 12:43:22 2020 Failure: oops InstallationDate: Installed on 2020-03-03 (26 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 004: ID 0c45:671d Microdia Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5530 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=f025082e-5dfa-4fa8-89d7-ef587d8b380d ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#11 stuck for 197s! [swapper/11:0] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 066WMR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn066WMR:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865471] Re: USB 3.1 Gen 1 not work after using suspend
Wondering if it's a regression. Can you please test older kernel like v4.4 from https://kernel.ubuntu.com/~kernel-ppa/mainline/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865471 Title: USB 3.1 Gen 1 not work after using suspend Status in linux package in Ubuntu: Incomplete Bug description: Good morning. I use "suspend"(settings -> energy -> When the shutdown button...) on 18.04. Each wake up, ONLY USB ports 3.1 Gen 1 of motherboard back panel don't work. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: christophe 1648 F pulseaudio /dev/snd/controlC2: christophe 1648 F pulseaudio /dev/snd/controlC0: christophe 1648 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-02-18 (14 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. enp6s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-A320M-S2H (rev. 1.x) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=9757d7ed-95dd-47d2-a3a7-80be35d05879 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-40-generic N/A linux-backports-modules-5.3.0-40-generic N/A linux-firmware1.173.15 RfKill: Tags: bionic Uname: Linux 5.3.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: A320M-S2H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/28/2019:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: A320M-S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1865471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869555] Re: 5.3.0-42-generic - Thinkpad 470p lock up and reboot
Please update BIOS, if the MCE error persists, please contact hardwire vendor. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1869555 Title: 5.3.0-42-generic - Thinkpad 470p lock up and reboot Status in linux package in Ubuntu: Incomplete Bug description: linux-image-5.3.0-42-generic makes a Thinkpad 470p lock up and reboot. Happens intermittently. Random reboots go away when regressing to kernel version 5.3.0-40-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869555/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869549] Re: Whenever a sound needs to be played the screen blanks out
before.txt attached to this ** Attachment added: "before running dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869549/+attachment/5343243/+files/before.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/1869549 Title: Whenever a sound needs to be played the screen blanks out Status in linux package in Ubuntu: Incomplete Bug description: Whenever a sound needs to be played the screen blanks out for a second, then the screen comes back on, and the sound plays. Examples of sounds are when I press Tab on the terminal, and there are no possible completions, or when I press the down button on the terminal, and there are no further lines below, then it blanks out, comes back, and then plays the "ding" tone telling me there are no further completions or lines. However, after one blank-out, if I keep pressing the down button, the sounds play normally without blanking out for a short time. After that period, it repeats again on doing something that would cause the sound to be played again. I'm on a relatively new HP Pavilion CS3006TX, running 20.04 Focal Fossa (Development branch) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:06:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1) ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 29 09:05:04 2020 DistUpgraded: 2020-03-28 14:50:01,253 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-42-generic, x86_64: installed nvidia, 435.21, 5.4.0-18-generic, x86_64: installed virtualbox, 6.1.4, 5.3.0-42-generic, x86_64: installed virtualbox, 6.1.4, 5.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:86e2] Subsystem: Hewlett-Packard Company GP108M [GeForce MX250] [103c:86e2] InstallationDate: Installed on 2019-11-30 (119 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:03bc Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Wide Vision HD Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Laptop 15-cs3xxx ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5ee3ea75-c293-4350-b4ea-e81ef28c7f78 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-03-28 (0 days ago) dmi.bios.date: 08/23/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.03 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 86E2 dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.03:bd08/23/2019:svnHP:pnHPPavilionLaptop15-cs3xxx:pvrType1ProductConfigId:rvnHP:rn86E2:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cs3xxx dmi.product.sku: 8LX85PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.
[Kernel-packages] [Bug 1869549] Re: Whenever a sound needs to be played the screen blanks out
(For your information, the diff between them is nothing) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1869549 Title: Whenever a sound needs to be played the screen blanks out Status in linux package in Ubuntu: Incomplete Bug description: Whenever a sound needs to be played the screen blanks out for a second, then the screen comes back on, and the sound plays. Examples of sounds are when I press Tab on the terminal, and there are no possible completions, or when I press the down button on the terminal, and there are no further lines below, then it blanks out, comes back, and then plays the "ding" tone telling me there are no further completions or lines. However, after one blank-out, if I keep pressing the down button, the sounds play normally without blanking out for a short time. After that period, it repeats again on doing something that would cause the sound to be played again. I'm on a relatively new HP Pavilion CS3006TX, running 20.04 Focal Fossa (Development branch) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:06:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1) ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 29 09:05:04 2020 DistUpgraded: 2020-03-28 14:50:01,253 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-42-generic, x86_64: installed nvidia, 435.21, 5.4.0-18-generic, x86_64: installed virtualbox, 6.1.4, 5.3.0-42-generic, x86_64: installed virtualbox, 6.1.4, 5.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:86e2] Subsystem: Hewlett-Packard Company GP108M [GeForce MX250] [103c:86e2] InstallationDate: Installed on 2019-11-30 (119 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:03bc Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Wide Vision HD Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Laptop 15-cs3xxx ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5ee3ea75-c293-4350-b4ea-e81ef28c7f78 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-03-28 (0 days ago) dmi.bios.date: 08/23/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.03 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 86E2 dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.03:bd08/23/2019:svnHP:pnHPPavilionLaptop15-cs3xxx:pvrType1ProductConfigId:rvnHP:rn86E2:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cs3xxx dmi.product.sku: 8LX85PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notificatio
[Kernel-packages] [Bug 1869645] Re: WiFi adapter RTL8723DE unrecognised in 20.04 daily build
** Also affects: linux-meta-oem-5.4 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1869645 Title: WiFi adapter RTL8723DE unrecognised in 20.04 daily build Status in kernel-package package in Ubuntu: New Status in linux-firmware package in Ubuntu: New Status in linux-meta-oem-5.4 package in Ubuntu: New Status in linux-oem-5.4 package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: WiFi card not recognized in Ubuntu 20.04 daily build on both Live-OS & installed-OS. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.15 [origin: unknown] ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Mar 30 09:55:22 2020 InstallationDate: Installed on 2020-03-29 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200324) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1869645/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869549] Re: Whenever a sound needs to be played the screen blanks out
I also wish to update the bug. Whenever any sound needs to start playing, the screen goes blank. Even when I play a video I paused a few moments earlier on YouTube, the screen goes blank, and then it comes back on, with the audio and video both working perfectly. It even happened in Vi when I pressed [esc] + [:] too quickly for it to register. I think it might have something to do with Nvidia graphics maybe? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1869549 Title: Whenever a sound needs to be played the screen blanks out Status in linux package in Ubuntu: Incomplete Bug description: Whenever a sound needs to be played the screen blanks out for a second, then the screen comes back on, and the sound plays. Examples of sounds are when I press Tab on the terminal, and there are no possible completions, or when I press the down button on the terminal, and there are no further lines below, then it blanks out, comes back, and then plays the "ding" tone telling me there are no further completions or lines. However, after one blank-out, if I keep pressing the down button, the sounds play normally without blanking out for a short time. After that period, it repeats again on doing something that would cause the sound to be played again. I'm on a relatively new HP Pavilion CS3006TX, running 20.04 Focal Fossa (Development branch) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:06:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1) ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 29 09:05:04 2020 DistUpgraded: 2020-03-28 14:50:01,253 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-42-generic, x86_64: installed nvidia, 435.21, 5.4.0-18-generic, x86_64: installed virtualbox, 6.1.4, 5.3.0-42-generic, x86_64: installed virtualbox, 6.1.4, 5.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:86e2] Subsystem: Hewlett-Packard Company GP108M [GeForce MX250] [103c:86e2] InstallationDate: Installed on 2019-11-30 (119 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:03bc Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Wide Vision HD Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Laptop 15-cs3xxx ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5ee3ea75-c293-4350-b4ea-e81ef28c7f78 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-03-28 (0 days ago) dmi.bios.date: 08/23/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.03 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 86E2 dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.03:bd08/23/2019:svnHP:pnHPPavilionLaptop15-cs3xxx:pvrType1ProductConfigId:rvnHP:rn86E2:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cs3xxx dmi.product.sku: 8LX85PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-co
[Kernel-packages] [Bug 1869549] Re: Whenever a sound needs to be played the screen blanks out
after.txt attached here ** Attachment added: "after running dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869549/+attachment/5343244/+files/after.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/1869549 Title: Whenever a sound needs to be played the screen blanks out Status in linux package in Ubuntu: Incomplete Bug description: Whenever a sound needs to be played the screen blanks out for a second, then the screen comes back on, and the sound plays. Examples of sounds are when I press Tab on the terminal, and there are no possible completions, or when I press the down button on the terminal, and there are no further lines below, then it blanks out, comes back, and then plays the "ding" tone telling me there are no further completions or lines. However, after one blank-out, if I keep pressing the down button, the sounds play normally without blanking out for a short time. After that period, it repeats again on doing something that would cause the sound to be played again. I'm on a relatively new HP Pavilion CS3006TX, running 20.04 Focal Fossa (Development branch) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:06:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1) ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 29 09:05:04 2020 DistUpgraded: 2020-03-28 14:50:01,253 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-42-generic, x86_64: installed nvidia, 435.21, 5.4.0-18-generic, x86_64: installed virtualbox, 6.1.4, 5.3.0-42-generic, x86_64: installed virtualbox, 6.1.4, 5.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:86e2] Subsystem: Hewlett-Packard Company GP108M [GeForce MX250] [103c:86e2] InstallationDate: Installed on 2019-11-30 (119 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:03bc Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Wide Vision HD Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Laptop 15-cs3xxx ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5ee3ea75-c293-4350-b4ea-e81ef28c7f78 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-03-28 (0 days ago) dmi.bios.date: 08/23/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.03 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 86E2 dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.03:bd08/23/2019:svnHP:pnHPPavilionLaptop15-cs3xxx:pvrType1ProductConfigId:rvnHP:rn86E2:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cs3xxx dmi.product.sku: 8LX85PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917
[Kernel-packages] [Bug 1860764] Re: Line out audio device is missing after resume-from-suspend
So right now it works well. I retested several times. Why ?. I don't know. You can close the problem -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860764 Title: Line out audio device is missing after resume-from-suspend Status in linux package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Invalid Bug description: this problem happened after i updated system when i power on after sleeping i have problem with sounds. it doesn't work. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob2511 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (362 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Tags: eoan Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (79 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob1897 F pulseaudio /dev/snd/controlC2: rob1897 F pulseaudio /dev/snd/controlC1: rob1897 F pulseaudio /dev/snd/pcmC1D0p: rob1897 F...m pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (428 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=574eb112-448b-4cfc-bed7-2c5a1ba42abf ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.183.4 RfKill: Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (145 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860764/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860800] Re: Ubuntu 19.10 doesn't shutdown
Can you please see if reboot works when there's no previous suspend attempt? I can see this after system resume from suspend: [ 3403.666188] PM: dpm_run_callback(): usb_dev_resume+0x0/0x20 returns -5 [ 3403.666191] PM: Device 2-1.8 failed to resume async: error -5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860800 Title: Ubuntu 19.10 doesn't shutdown Status in linux package in Ubuntu: Confirmed Bug description: Hello guys, I can't shutdown Ubuntu 19.10. When I try, the shutdown screen appears. The first two dots below the ubuntu logo, turn orange and then it freezes. Reboot works fine. The debug-shell is no use, because at the freeze point I can't type in commands. When I press ESC to see what's going on during shutdown, the last message to appear ist "[Some weird number] reboot: power down. Last time I pressed ESC during shutdown the "weird number" was 85.270119. I also tried to shutdown with the terminal commands "sudo shutdown now", "sudo shutdown -P now", "sudo shutdown -h now", "poweroff" and "sudo poweroff -f". All of them had the effect as describe above except the command "sudo poweroff -f". After I typed in the command, I authenticated and following messages appeared: "Powering off...". At this point it freezed. I could still see the desktop and every visible window, but I couldn't perform any actions; not even keyboard shortcuts worked. It also did not help to change 'GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"' in /etc/default/grub to 'GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=force"' and run "update-grub". Once the following command combo did work: "sudo swapoff -a && systemctl poweroff", but the I reinstalled Ubuntu and now it doesn't work any more. In the application "Additional Drivers" I selected the proprietary and tested driver of NVIDIA, but I can't to this for my WLAN-Card (correct word?), because the "Additional Drivers" says it's not working, but my WLAN works fine. I've got only Bluetooth problems. The displayed name of the WLAN-Card is: "Intel Corporation: Wireless 7260 (Dual Band Wireless-AC 7260)". I also tried to manually install a driver it didn't help. When I wake up the laptop, a black screen appears with some error messages, but only for a very short time so I can't make a photo of it. I tried once and the text was unreadable. I have the latest BIOS and my Computer model is MSI PX60 2QD. It doesn't work with Arch Linux either. Thanks for your help :) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leonard1724 F pulseaudio /dev/snd/controlC1: leonard1724 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-18 (7 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. PX60 2QD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=04df7493-393f-447e-bfb3-3dc43c2ee645 ro quiet splash acpi=force vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 Tags: eoan Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16H6IMS.110 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16H6 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.B dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16H6IMS.110:bd11/03/2015:svnMicro-StarInternationalCo.,Ltd.:pnPX602QD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H6:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: PX60 2QD dmi.product.sku: To be filled by O.E.M. dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860800/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More h
[Kernel-packages] [Bug 1860764] Re: Line out audio device is missing after resume-from-suspend
** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: pulseaudio (Ubuntu) Status: New => 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/1860764 Title: Line out audio device is missing after resume-from-suspend Status in linux package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Invalid Bug description: this problem happened after i updated system when i power on after sleeping i have problem with sounds. it doesn't work. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob2511 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (362 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Tags: eoan Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (79 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob1897 F pulseaudio /dev/snd/controlC2: rob1897 F pulseaudio /dev/snd/controlC1: rob1897 F pulseaudio /dev/snd/pcmC1D0p: rob1897 F...m pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (428 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=574eb112-448b-4cfc-bed7-2c5a1ba42abf ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.183.4 RfKill: Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (145 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860764/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824228] Re: ept test fails in kvm_unit_tests
** Tags added: sru-20200316 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1824228 Title: ept test fails in kvm_unit_tests Status in ubuntu-kernel-tests: New Status in linux-azure package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-azure source package in Disco: New Status in linux-kvm source package in Disco: New Status in linux-oracle source package in Disco: New Status in linux-azure source package in Eoan: New Status in linux-kvm source package in Eoan: New Status in linux-oracle source package in Eoan: New Bug description: Reproducible: Yes, Series: cosmic Kernel: "linux-azure 4.18.0-1015.15" Steps: 1.) apt-get install -y build-essential cpu-checker qemu-kvm git gcc-multilib 2.) git clone --depth=1 https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git 3.) cd kvm-unit-tests; ./configure; make 4.) sudo TESTNAME=ept TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu host,host-phys-bits,+vmx -m 2560 -append "ept_access*" timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/vmx.flat -smp 1 -cpu host,host-phys-bits,+vmx -m 2560 -append ept_access* # -initrd /tmp/tmp.RcwfbGP5Ou enabling apic paging enabled cr0 = 80010011 cr3 = 477000 cr4 = 20 Test suite: ept_access_test_not_present Test suite: ept_access_test_read_only Test suite: ept_access_test_write_only Test suite: ept_access_test_read_write Test suite: ept_access_test_execute_only Test suite: ept_access_test_read_execute Test suite: ept_access_test_write_execute Test suite: ept_access_test_read_write_execute Test suite: ept_access_test_reserved_bits Test suite: ept_access_test_ignored_bits Test suite: ept_access_test_paddr_not_present_ad_disabled Test suite: ept_access_test_paddr_not_present_ad_enabled Host skipping test: EPT AD bits not supported. Test suite: ept_access_test_paddr_read_only_ad_disabled EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x008b - ''''''''''''''1000'1011 - 139 RHS: 0x008a - ''''''''''''''1000'1010 - 138 STACK: 40f328 40f8fb 40fb0b 40ff49 401577 4039d0 400312 EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x008b - ''''''''''''''1000'1011 - 139 RHS: 0x008a - ''''''''''''''1000'1010 - 138 STACK: 40f328 40f8fb 40fb0b 40ff62 401577 4039d0 400312 EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x008b - ''''''''''''''1000'1011 - 139 RHS: 0x008a - ''''''''''''''1000'1010 - 138 STACK: 40f328 40f8fb 40fb0b 40ff7b 401577 4039d0 400312 EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x008b - ''''''''''''''1000'1011 - 139 RHS: 0x008a - ''''''''''''''1000'1010 - 138 STACK: 40f328 40f8fb 40fb0b 40ffa8 401577 4039d0 400312 Test suite: ept_access_test_paddr_read_only_ad_enabled Host skipping test: EPT AD bits not supported. Test suite: ept_access_test_paddr_read_write Test suite: ept_access_test_paddr_read_write_execute Test suite: ept_access_test_paddr_read_execute_ad_disabled EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x00ab - ''''''''''''''1010'1011 - 171 RHS: 0x00aa - ''''''''''''''1010'1010 - 170 STACK: 40f328 40f8fb 40fb0b 40fde3 401577 4039d0 400312 EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x00ab - ''''''''''''''1010'1011 - 171 RHS: 0x00aa - ''''''''''''''1010'1010 - 170 STACK: 40f328 40f8fb 40fb0b 40fdfc 401577 4039d0 400312 EPT_VLT_RD expected FAIL: x86/vmx_tests
[Kernel-packages] [Bug 1859380] Re: Sleep doesn't work on my ThinkPad X1 Yoga with Kubuntu 20.04
Sorry for the belated response. According to the log, there's no suspend attempt. Probably the lid close status isn't right. If you have another system, can you please SSH to the system and check "/proc/acpi/button/lid/LID0/state"? And before that, please update all packages. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859380 Title: Sleep doesn't work on my ThinkPad X1 Yoga with Kubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: Sleep button doesn't work at all, and when I close the lid, the screen goes black, but there's a cursor, and it doesn't respond. Had to force shut down. Operating System: Kubuntu 20.04 KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.12.5 Kernel Version: 5.4.0-9-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz Memory: 15.3 GiB of RAM ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: kubuntu-desktop 1.392 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: KDE Date: Sun Jan 12 19:24:55 2020 InstallationDate: Installed on 2020-01-03 (9 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: kubuntu-meta UpgradeStatus: Upgraded to focal on 2020-01-12 (0 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-25 (9 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200120) IwConfig: wlp0s20f3 no wireless extensions. lono wireless extensions. enp0s31f6 no wireless extensions. MachineType: LENOVO 20SA0002US Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=d3ea3aaf-4630-491b-8315-c7efa5381fdf ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 RelatedPackageVersions: linux-restricted-modules-5.4.0-12-generic N/A linux-backports-modules-5.4.0-12-generic N/A linux-firmware1.186 Tags: focal Uname: Linux 5.4.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET19W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20SA0002US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2QET19W(1.13):bd01/15/2020:svnLENOVO:pn20SA0002US:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20SA0002US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 4th dmi.product.name: 20SA0002US dmi.product.sku: LENOVO_MT_20SA_BU_Think_FM_ThinkPad X1 Yoga 4th dmi.product.version: ThinkPad X1 Yoga 4th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859380/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839912] Re: test_map in ubuntu_bpf failed with "Allowed update sockmap '0:3' not in ESTABLISHED"
Found on 4.15.0-1037.41-oracle ** Tags added: sru-20200316 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839912 Title: test_map in ubuntu_bpf failed with "Allowed update sockmap '0:3' not in ESTABLISHED" Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: This is at lease a test case regression with the proposed kernel: selftests: test_maps Allowed update sockmap '0:3' not in ESTABLISHED not ok 1..3 selftests: test_maps [FAIL] But with older kernel: selftests: test_maps test_maps: OK ok 1..3 selftests: test_maps [PASS] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-58-generic 4.15.0-58.64 ProcVersionSignature: User Name 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 13 03:42 seq crw-rw 1 root audio 116, 33 Aug 13 03:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Aug 13 03:52:52 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.family: To be filled by O.E.M. dmi.product.name: S1200RP dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1839912/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827982] Re: hyperv_stimer in ubuntu_kvm_unit_tests failed on B-KVM / Oracle-4.15
With 4.15.0-1037.41 Oracle Failed with VM.Standard2.16 Passed with VM.Standard2.1 ** Tags added: sru-20200316 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1827982 Title: hyperv_stimer in ubuntu_kvm_unit_tests failed on B-KVM / Oracle-4.15 Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Bug description: Test timeouted. # TESTNAME=hyperv_stimer TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_stimer.flat -smp 2 -cpu kvm64,hv_vpindex,hv_time,hv_synic,hv_stimer -device hyperv-testdev timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/hyperv_stimer.flat -smp 2 -cpu kvm64,hv_vpindex,hv_time,hv_synic,hv_stimer -device hyperv-testdev # -initrd /tmp/tmp.ouYfwUEdq5 qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 enabling apic cpus = 2 qemu-system-x86_64: terminating on signal 15 from pid 2224 (timeout) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1032-kvm 4.15.0-1032.32 ProcVersionSignature: User Name 4.15.0-1032.32-kvm 4.15.18 Uname: Linux 4.15.0-1032-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue May 7 03:39:16 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1827982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827980] Re: hyperv_synic in ubuntu_kvm_unit_tests failed on B-KVMhyperv_stimer
With 4.15.0-1037.41 Oracle Failed with VM.Standard2.16 Passed with VM.Standard2.1 ** Summary changed: - hyperv_synic in ubuntu_kvm_unit_tests failed on B-KVM + hyperv_synic in ubuntu_kvm_unit_tests failed on B-KVMhyperv_stimer ** Summary changed: - hyperv_synic in ubuntu_kvm_unit_tests failed on B-KVMhyperv_stimer + hyperv_synic in ubuntu_kvm_unit_tests failed on B-KVM / Oracle-4.15 ** Tags added: sru-20200316 ** Tags added: oracle ** Tags added: 4.15 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1827980 Title: hyperv_synic in ubuntu_kvm_unit_tests failed on B-KVM / Oracle-4.15 Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Bug description: Test timeout. # TESTNAME=hyperv_synic TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_synic.flat -smp 2 -cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/hyperv_synic.flat -smp 2 -cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev # -initrd /tmp/tmp.LeYhxJZmHV qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 enabling apic ncpus = 2 prepare qemu-system-x86_64: terminating on signal 15 from pid 1658 (timeout) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1032-kvm 4.15.0-1032.32 ProcVersionSignature: User Name 4.15.0-1032.32-kvm 4.15.18 Uname: Linux 4.15.0-1032-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue May 7 03:36:32 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1827980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831449] Re: memory in ubuntu_kvm_unit_tests fails
With 4.15.0-1037.41 Oracle Failed with VM.Standard2.16 Passed with VM.Standard2.1 ** Tags added: sru-20200316 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1831449 Title: memory in ubuntu_kvm_unit_tests fails Status in ubuntu-kernel-tests: Triaged Status in linux-kvm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Bug description: Need to run this on oracle manually to get the full output: TESTNAME=memory TIMEOUT=90s ACCEL= ./x86/run x86/memory.flat -smp 1 -cpu host FAIL memory (8 tests, 2 unexpected failures) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831449/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862114] Re: pty03 from pty in ubuntu_ltp failed on Eoan
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862114 Title: pty03 from pty in ubuntu_ltp failed on Eoan Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Released Bug description: == Justification == The test case pty03 from pty in ubuntu_ltp is failing with kernel NULL pointer dereference: [ 951.306823] BUG: kernel NULL pointer dereference, address: 0020 [ 951.309960] #PF: supervisor write access in kernel mode [ 951.312130] #PF: error_code(0x0002) - not-present page [ 951.314227] PGD 0 P4D 0 [ 951.315278] Oops: 0002 [#1] SMP PTI [ 951.316705] CPU: 1 PID: 39102 Comm: pty03 Not tainted 5.4.0-12-generic #15-Ubuntu [ 951.319737] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 951.322713] RIP: 0010:queue_work_on+0x1b/0x50 [ 951.352494] Call Trace: [ 951.353244] slip_write_wakeup+0x25/0x30 [slip] [ 951.354600] tty_wakeup+0x5b/0x70 [ 951.355539] pty_unthrottle+0x19/0x30 [ 951.356560] tty_unthrottle+0x42/0x60 [ 951.357566] __tty_perform_flush+0x87/0x90 [ 951.358768] n_tty_ioctl_helper+0xcc/0x150 [ 951.359955] n_tty_ioctl+0x2d/0x100 [ 951.360930] tty_ioctl+0x3c0/0x8e0 [ 951.361882] ? __switch_to_asm+0x34/0x70 [ 951.363049] ? __switch_to_asm+0x40/0x70 [ 951.364191] ? __switch_to_asm+0x34/0x70 [ 951.365261] ? __switch_to_asm+0x40/0x70 [ 951.366382] ? __switch_to_asm+0x34/0x70 [ 951.367452] ? __switch_to_asm+0x40/0x70 [ 951.368523] ? __switch_to_asm+0x34/0x70 [ 951.369693] ? __switch_to_asm+0x40/0x70 [ 951.370829] ? __switch_to_asm+0x34/0x70 [ 951.371923] ? __switch_to_asm+0x40/0x70 [ 951.372998] ? __switch_to_asm+0x34/0x70 [ 951.374097] ? __switch_to_asm+0x40/0x70 [ 951.375183] ? __switch_to_asm+0x34/0x70 [ 951.376288] ? __switch_to_asm+0x40/0x70 [ 951.377390] ? __switch_to+0x110/0x470 [ 951.378863] do_vfs_ioctl+0x407/0x670 [ 951.380269] ? __schedule+0x2eb/0x740 [ 951.381761] ksys_ioctl+0x67/0x90 [ 951.383076] __x64_sys_ioctl+0x1a/0x20 [ 951.384510] do_syscall_64+0x57/0x190 [ 951.385896] entry_SYSCALL_64_after_hwframe+0x44/0xa9 == Fixes == Indicated by the test case, this issue can be fixed by: * 0ace17d5 (can, slip: Protect tty->disc_data in write_wakeup and close with RCU) This patch can be cherry-picked into all of our kernels. == Test == Test kernels could be found here: https://people.canonical.com/~phlin/kernel/lp-1862114-pty03/ Tested on KVM nodes and the patched kernels work as expected, there will be no more kernel null pointer dereference issue, and the test can finish properly. == Regression potential == Low, changes limited to two specific drivers for serial line TTY. This issue can be reproduced quite easily and the patched kernels show positive results. == Original Bug Report == startup='Thu Feb 6 02:45:23 2020' tst_test.c:1215: INFO: Timeout per run is 0h 05m 00s pty03.c:101: INFO: Creating PTY with SLIP line discipline Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Cannot kill test processes! Congratulation, likely test hit a kernel bug. Exitting uncleanly... tag=pty03 stime=1580957123 dur=350 exit=exited stat=1 core=no cu=0 cs=0 This is a new test case, so it's not a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1862114/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869549] Re: Whenever a sound needs to be played the screen blanks out
To find out if it's caused by the Nvidia driver you would need to uninstall the Nvidia driver. ** Tags added: nvidia ** Summary changed: - Whenever a sound needs to be played the screen blanks out + [nvidia] Whenever a sound needs to be played the screen blanks out ** Also affects: nvidia-graphics-drivers-435 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-435 (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/1869549 Title: [nvidia] Whenever a sound needs to be played the screen blanks out Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers-435 package in Ubuntu: Invalid Bug description: Whenever a sound needs to be played the screen blanks out for a second, then the screen comes back on, and the sound plays. Examples of sounds are when I press Tab on the terminal, and there are no possible completions, or when I press the down button on the terminal, and there are no further lines below, then it blanks out, comes back, and then plays the "ding" tone telling me there are no further completions or lines. However, after one blank-out, if I keep pressing the down button, the sounds play normally without blanking out for a short time. After that period, it repeats again on doing something that would cause the sound to be played again. I'm on a relatively new HP Pavilion CS3006TX, running 20.04 Focal Fossa (Development branch) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:06:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1) ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 29 09:05:04 2020 DistUpgraded: 2020-03-28 14:50:01,253 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-42-generic, x86_64: installed nvidia, 435.21, 5.4.0-18-generic, x86_64: installed virtualbox, 6.1.4, 5.3.0-42-generic, x86_64: installed virtualbox, 6.1.4, 5.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:86e2] Subsystem: Hewlett-Packard Company GP108M [GeForce MX250] [103c:86e2] InstallationDate: Installed on 2019-11-30 (119 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:03bc Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Wide Vision HD Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Laptop 15-cs3xxx ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5ee3ea75-c293-4350-b4ea-e81ef28c7f78 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-03-28 (0 days ago) dmi.bios.date: 08/23/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.03 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 86E2 dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.03:bd08/23/2019:svnHP:pnHPPavilionLaptop15-cs3xxx:pvrType1ProductConfigId:rvnHP:rn86E2:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cs3xxx dmi.product.sku: 8LX85PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1 version.libgl1-mesa-glx
[Kernel-packages] [Bug 1869549] Re: [nvidia] Whenever a sound needs to be played the screen blanks out
Oh. Actually this looks like a "feature". To turn it off go to: Settings > Universal Access > Visual Alerts = OFF ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: nvidia-graphics-drivers-435 (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1869549 Title: [nvidia] Whenever a sound needs to be played the screen blanks out Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers-435 package in Ubuntu: Invalid Bug description: Whenever a sound needs to be played the screen blanks out for a second, then the screen comes back on, and the sound plays. Examples of sounds are when I press Tab on the terminal, and there are no possible completions, or when I press the down button on the terminal, and there are no further lines below, then it blanks out, comes back, and then plays the "ding" tone telling me there are no further completions or lines. However, after one blank-out, if I keep pressing the down button, the sounds play normally without blanking out for a short time. After that period, it repeats again on doing something that would cause the sound to be played again. I'm on a relatively new HP Pavilion CS3006TX, running 20.04 Focal Fossa (Development branch) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:06:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1) ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 29 09:05:04 2020 DistUpgraded: 2020-03-28 14:50:01,253 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-42-generic, x86_64: installed nvidia, 435.21, 5.4.0-18-generic, x86_64: installed virtualbox, 6.1.4, 5.3.0-42-generic, x86_64: installed virtualbox, 6.1.4, 5.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:86e2] Subsystem: Hewlett-Packard Company GP108M [GeForce MX250] [103c:86e2] InstallationDate: Installed on 2019-11-30 (119 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:03bc Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Wide Vision HD Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Laptop 15-cs3xxx ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5ee3ea75-c293-4350-b4ea-e81ef28c7f78 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-03-28 (0 days ago) dmi.bios.date: 08/23/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.03 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 86E2 dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.03:bd08/23/2019:svnHP:pnHPPavilionLaptop15-cs3xxx:pvrType1ProductConfigId:rvnHP:rn86E2:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cs3xxx dmi.product.sku: 8LX85PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 vers
[Kernel-packages] [Bug 1869645] Re: WiFi adapter RTL8723DE unrecognised in 20.04 daily build
*** This bug is a duplicate of bug 1780590 *** https://bugs.launchpad.net/bugs/1780590 It's in focal-proposed now, so maybe test the pending image. ** This bug has been marked a duplicate of bug 1780590 Add support for Realtek 8723DE wireless adapter -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1869645 Title: WiFi adapter RTL8723DE unrecognised in 20.04 daily build Status in kernel-package package in Ubuntu: New Status in linux-firmware package in Ubuntu: New Status in linux-meta-oem-5.4 package in Ubuntu: New Status in linux-oem-5.4 package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: WiFi card not recognized in Ubuntu 20.04 daily build on both Live-OS & installed-OS. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.15 [origin: unknown] ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Mar 30 09:55:22 2020 InstallationDate: Installed on 2020-03-29 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200324) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1869645/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827979] Re: pcid in ubuntu_kvm_unit_tests failed on B-KVM / X-4.15-oracle
Failed on VM.Standard2.16 / VM.Standard2.1 with 4.15.0-1037.41 Oracle ** Tags added: sru-20200316 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1827979 Title: pcid in ubuntu_kvm_unit_tests failed on B-KVM / X-4.15-oracle Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Bug description: FAIL pcid (3 tests, 1 unexpected failures) # TESTNAME=pcid TIMEOUT=90s ACCEL= ./x86/run x86/pcid.flat -smp 1 -cpu qemu64,+pcid timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/pcid.flat -smp 1 -cpu qemu64,+pcid # -initrd /tmp/tmp.a4xQyF7juj qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.8001H:ECX.svm [bit 2] enabling apic PASS: CPUID consistency PASS: Test on PCID when disabled FAIL: Test on INVPCID when disabled SUMMARY: 3 tests, 1 unexpected failures ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1032-kvm 4.15.0-1032.32 ProcVersionSignature: User Name 4.15.0-1032.32-kvm 4.15.18 Uname: Linux 4.15.0-1032-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue May 7 03:31:38 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1827979/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869672] [NEW] kdump kernel can't be loaded using kernel 4.15.0-76
Public bug reported: Thank you for reading this report. This may caused by bugs in kernel, not in kdump. If so, I will report this to kernel team. I need your comment to solve this. [Impact] * Kdump kernel can't be loaded using linux kernel 4.15.0-76. [Environment] Description:Ubuntu 18.04.4 LTS Release:18.04 uname: Linux ubuntu 4.15.0-76-generic #86-Ubuntu SMP Fri Jan 17 17:24:28 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Secure boot is enabled. Versions: * kexec-tools/bionic-updates,now 1:2.0.16-1ubuntu1.1 * kdump-tools/bionic-updates,now 1:1.6.5-1ubuntu1~18.04.4 [Test case] 1)After OS booted, run systemctl status kdump-tools shows these messages below: ● kdump-tools.service - Kernel crash dump capture service Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor preset: enabled) Active: active (exited) since Fri 2020-03-27 16:40:31 JST; 5min ago Process: 895 ExecStart=/etc/init.d/kdump-tools start (code=exited, status=0/SUCCESS) Main PID: 895 (code=exited, status=0/SUCCESS) Mar 27 16:40:31 ubuntu systemd[1]: Starting Kernel crash dump capture service... Mar 27 16:40:31 ubuntu kdump-tools[895]: Starting kdump-tools: * Creating symlink /var/lib/kdump/vmlinuz Mar 27 16:40:31 ubuntu kdump-tools[895]: * Creating symlink /var/lib/kdump/initrd.img Mar 27 16:40:31 ubuntu kdump-tools[895]: kexec_file_load failed: Exec format error Mar 27 16:40:31 ubuntu kdump-tools[895]: * failed to load kdump kernel Mar 27 16:40:31 ubuntu systemd[1]: Started Kernel crash dump capture service. 2)Run kexec directly: $ sudo /sbin/kexec -p --command-line="/boot/vmlinuz-4.15.0-76-generic root=UUID=29a89ad8-8923-435e-a88c-aaf5cb379568 ro mce=ignore_ce reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb ata_piix.prefer_ms_hyperv=0" --initrd=/boot/initrd.img-4.15.0-76-generic /boot/vmlinuz-4.15.0-64-generic Then,these messages are shown: Cannot open /proc/kcore: Operation not permitted Cannot read /proc/kcore: Operation not permitted Cannot load /boot/vmlinuz-4.15.0-76-generic On dmesg, these messages are shown: [ 538.524718] Lockdown: /proc/kcore is restricted; see man kernel_lockdown.7 3) Changing OS kernel to older one(I used 4.15.0-64), kdump kernel can be loaded. $ sudo systemctl status kdump-tools ● kdump-tools.service - Kernel crash dump capture service Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor preset: enabled) Active: active (exited) since Wed 2020-03-25 13:39:03 JST; 5 days ago Main PID: 832 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4915) CGroup: /system.slice/kdump-tools.service Mar 25 13:39:02 ctrl-edgen systemd[1]: Starting Kernel crash dump capture service... Mar 25 13:39:02 ctrl-edgen kdump-tools[832]: Starting kdump-tools: * Creating symlink /var/lib/kdump/vmlinuz Mar 25 13:39:02 ctrl-edgen kdump-tools[832]: * Creating symlink /var/lib/kdump/initrd.img Mar 25 13:39:03 ctrl-edgen kdump-tools[832]: * loaded kdump kernel Mar 25 13:39:03 ctrl-edgen kdump-tools[938]: loaded kdump kernel Mar 25 13:39:03 ctrl-edgen systemd[1]: Started Kernel crash dump capture service. ** Affects: makedumpfile (Ubuntu) Importance: Undecided Status: New ** Description changed: Thank you for reading this report. This may caused by bugs in kernel, not in kdump. If so, I will report this to kernel team. I need your comment to solve this. [Impact] * Kdump kernel can't be loaded using linux kernel 4.15.0-76. [Environment] Description:Ubuntu 18.04.4 LTS Release:18.04 uname: Linux ubuntu 4.15.0-76-generic #86-Ubuntu SMP Fri Jan 17 17:24:28 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Secure boot is enabled. + Versions: + * kexec-tools/bionic-updates,now 1:2.0.16-1ubuntu1.1 + * kdump-tools/bionic-updates,now 1:1.6.5-1ubuntu1~18.04.4 + [Test case] 1)After OS booted, run systemctl status kdump-tools shows these messages below: ● kdump-tools.service - Kernel crash dump capture service -Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor preset: enabled) -Active: active (exited) since Fri 2020-03-27 16:40:31 JST; 5min ago - Process: 895 ExecStart=/etc/init.d/kdump-tools start (code=exited, status=0/SUCCESS) - Main PID: 895 (code=exited, status=0/SUCCESS) + Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor preset: enabled) + Active: active (exited) since Fri 2020-03-27 16:40:31 JST; 5min ago + Process: 895 ExecStart=/etc/init.d/kdump-tools start (code=exited, status=0/SUCCESS) + Main PID: 895 (code=exited, status=0/SUCCESS) Mar 27 16:40:31 ubuntu systemd[1]: Starting Kernel crash dump capture service... Mar 27 16:40:31 ubuntu kdump-tools[895]: Starting kdump-tools: * Creating symlink /var/lib/kdump/vmlinuz Mar 27 16:40:31 ubuntu kdump-tools[895]: * Creating symlink /var/lib/kdump/initrd.img Mar 27 16:40:31 ubuntu kdump-tools
[Kernel-packages] [Bug 1850439] Re: No sound on ASUS UX534FT
** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+attachment/5343262/+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/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850439] Re: No sound on ASUS UX534FT
** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+attachment/5343261/+files/dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1850439] Re: No sound on ASUS UX534FT
I added the outputs to the bug. Is there anything else i can do to help? Op ma 30 mrt. 2020 om 09:41 schreef Kai-Heng Feng < kai.heng.f...@canonical.com>: > Alright, can you please attach `dmesg` and `sudo lspci -vvnn`, thanks. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1850439 > > Title: > No sound on ASUS UX534FT > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > Hi, > > after instal Ubuntu in dual boot alongside Windows 10, I've realised > there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- > AA024R in Ubuntu. In Windows there is no problem. Found this topic > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had > the same problem with driver for Realtek ALC294 which is also mine > sound card. But even with this fix it is not working on UX534FT. Can > you please add fix also for this newer model? > > Description: Ubuntu 18.04.3 LTS > Release: 18.04 > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 > ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 > Uname: Linux 5.0.0-32-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7.7 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Tue Oct 29 15:11:25 2019 > InstallationDate: Installed on 2019-10-29 (0 days ago) > InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 > (20190805) > SourcePackage: linux-signed-hwe > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845678] Re: Lenovo ThinkPad X1 Carbon 7th Generation built-in microphone doesn't work
Hi, I wanted to give a bit of feedback after a few days using the laptop with kernel 43 and the experimental libasound packages from Hui's ppa. As far as I can tell, the microphone works flawlessly. Sound output to speakers and HDMI works too. With one notable drawback : the internal speaker volume, even when maxed out in alsamixer and gnome settings is very weak, much weaker than when using the snd_hda driver. I think this is related to https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/comments/28 and one should be aware of it before switching to sof. Plugging a BT headset correctly switches output to the headset and joining a google meet visio conference in firefox switches the microphone too. As reported in https://bugs.launchpad.net/ubuntu/+source/alsa- lib/+bug/1859754/comments/86 the chrome snap seems to do something different from firefox ending up in crashing the BT headset when joining a google meet visio. installed packages ii libasound2:amd64 1.1.9-0ubuntu1.2testucm amd64shared library for ALSA applications ii libasound2-data1.1.9-0ubuntu1.2testucm all Configuration files and profiles for ALSA drivers ii libasound2-plugins:amd64 1.1.9-0ubuntu1 amd64ALSA library additional plugins ii linux-firmware 1.183.5 all Firmware for Linux kernel drivers ii linux-image-5.3.0-43-generic 5.3.0-43.36 amd64Signed kernel image generic ii linux-modules-5.3.0-43-generic 5.3.0-43.36 amd64Linux kernel extra modules for version 5.3.0 on 64 bit x86 SMP ii linux-modules-extra-5.3.0-43-generic 5.3.0-43.36 amd64Linux kernel extra modules for version 5.3.0 on 64 bit x86 SMP -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845678 Title: Lenovo ThinkPad X1 Carbon 7th Generation built-in microphone doesn't work Status in linux package in Ubuntu: Confirmed Bug description: The built-in microphone in my Lenovo ThinkPad X1 Carbon 7th Generation doesn't work. A microphone on a headset plugged into the 3.5mm jack works fine. This is probably relevant: https://bugzilla.kernel.org/show_bug.cgi?id=201251 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-12-generic 5.3.0-12.13 ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0 Uname: Linux 5.3.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jik3746 F pulseaudio /dev/snd/pcmC0D0p: jik3746 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 27 11:13:25 2019 InstallationDate: Installed on 2019-09-12 (14 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20QD001VUS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-12-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-12-generic N/A linux-backports-modules-5.3.0-12-generic N/A linux-firmware1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-20 (7 days ago) dmi.bios.date: 07/04/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET30W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QD001VUS 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:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QD001VUS dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845678/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850439] Re: No sound on ASUS UX534FT
The above are the logs with proposed packages and upgrade. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850439] Re: No sound on ASUS UX534FT
UX533FTC ** Attachment added: "lspci.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+attachment/5343267/+files/lspci.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850439] Re: No sound on ASUS UX534FT
UX533FTC ** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+attachment/5343266/+files/dmesg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834085]
Just to note that I have exactly the same issue, Apple Magic Trackpad 1 on Ubuntu 18.04 LTS, kernel 5.3.0-42-generic. Happy to provide more info as needed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834085 Title: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I recently got an Apple's Magic Trackpad. I paired it with Ubuntu 18.04.2 LTS and worked out of the box, no special drivers needed. However, I experience frequent disconnections that last a few seconds (5-15 seconds usually), which are quite annoying, as the cursor stops responding during that interval. The trackpad connects by itself after that period. That usually happens every 20-40 minutes. I use the onboard bluetooth device of my laptop. I also have, at the same time, two more bluetooth devices (keyboard and mouse) and they do not experience that issue, just the trackpad. On ocassion I use bluetooth headphones which work just fine. First of all: Using the command "bluetoothctl" I get the following every time I experience a disconnection: [CHG] Device F4:1B:A1:33:F9:8D Connected: no [CHG] Device F4:1B:A1:33:F9:8D Connected: yes Checking "dmesg" I can see more information: (if I am not mistaken, this shows 4 disconnections) [ 1609.070538] magicmouse 0005:05AC:030E.0007: unknown main item tag 0x0 [ 1609.070797] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0007/input/input23 [ 1609.071460] magicmouse 0005:05AC:030E.0007: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 1676.917377] NET: Registered protocol family 38 [ 1872.815348] magicmouse 0005:05AC:030E.0008: unknown main item tag 0x0 [ 1872.815559] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008/input/input24 [ 1872.816248] magicmouse 0005:05AC:030E.0008: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3101.682671] magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 [ 3101.683100] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 [ 3101.683673] magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3110.683360] magicmouse 0005:05AC:030E.000A: unknown main item tag 0x0 [ 3110.683929] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:1024/0005:05AC:030E.000A/input/input26 [ 3110.684487] magicmouse 0005:05AC:030E.000A: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 And this is what journalctl -b shows at the moment of the disconnection/reconnection: de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: removing device Apple Wireless Trackpad de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option "fd" "64" (1,63 m)˜ de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - Apple Wireless Trackpad: device removed de juny 13 21:37:49 TM1703 gnome-shell[5071]: g_array_unref: assertion 'array' failed de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) UnloadModule: "libinput" de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) systemd-logind: releasing fd for 13:80 de juny 13 21:37:49 TM1703 upowerd[1271]: unhandled action 'unbind' on /sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 de juny 13 21:37:50 TM1703 kernel: input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/mouse1) de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) No input driver specified, ignoring this device. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) This device may have been added with another device file. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/event16) de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Apple Wireless Trackpa
[Kernel-packages] [Bug 1664072]
I see it TCP: wlan0: Driver has suspect GRO implementation, TCP performance may be compromised. [4.287544] iwlwifi :01:00.0: firmware: direct-loading firmware iwlwifi-8000C-36.ucode [4.289638] iwlwifi :01:00.0: loaded firmware version 36.8fd77bb3.0 op_mode iwlmvm [4.484488] iwlwifi :01:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208 [4.562788] iwlwifi :01:00.0: base HW address: 28:16:ad:81:b2:8a [4.653536] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs' root@debian:~# uname -a Linux debian 5.4.0-4-amd64 #1 SMP Debian 5.4.19-1 (2020-02-13) x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1664072 Title: TCP: wlp1s0: Driver has suspect GRO implementation, TCP performance may be compromised. Status in Linux: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux package in Debian: Confirmed Bug description: dmesg: [ 7578.057461] TCP: wlp1s0: Driver has suspect GRO implementation, TCP performance may be compromised. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.9.0-15-generic 4.9.0-15.16 ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5 Uname: Linux 4.9.0-15-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: caravena 2378 F...m pulseaudio /dev/snd/controlC0: caravena 2378 F pulseaudio CurrentDesktop: GNOME Date: Sun Feb 12 19:34:40 2017 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2015-07-26 (567 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.9.0-15-generic root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.9.0-15-generic N/A linux-backports-modules-4.9.0-15-generic N/A linux-firmware1.162 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2016-10-29 (106 days ago) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1664072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848771]
This is still broken as of 5.5.10 Probably the only way to get this fixed is via a 3rd party kernel developer like Ubuntu/Fedora/GalliumOS or something because currently it seems to be ignored by the mainline kernel devs. I still haven't had time to bisect the issue and have my kernel pinned at 4.19.66. I think by far the easiest way to find the problem is by comparing 4.19.66 to 4.19.67 and see what changed. Anyone tried the latest GalliumOS? What kernel does it use? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848771 Title: Reboot after resume from suspend (deep) Status in linux package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Invalid Bug description: After upgrading to Kubuntu Eoan (19.10) yesterday, my laptop crashes after resume from suspending. This is regardless the way of suspending (closing lid, selecting suspend from sddm, systemctl suspend). The journal shows: ferry@chromium:~$ journalctl -b -1 -e .. sddm[1106]: Message received from greeter: Suspend NetworkManager[836]: manager: sleep: sleep requested (sleeping: no enabled: yes) NetworkManager[836]: device (60:73:BC:BA:B8:68): state change: disconnected -> unmanaged (reason ' NetworkManager[836]: device (60:73:BC:23:8F:3E): state change: disconnected -> unmanaged (reason ' NetworkManager[836]: device (p2p-dev-wlp1s0): state change: disconnected -> unmanaged (reason 'sle NetworkManager[836]: manager: NetworkManager state is now ASLEEP systemd[1]: Reached target Sleep. systemd[1]: Starting Suspend... systemd-sleep[1238]: Suspending system... kernel: PM: suspend entry (deep) On resume (keypress, open lid) resume starts but immediately crashes and reboots. The laptop is an Acer 720p Chromebook with Chromium replaced and working fine with Kubuntu since 5 years or so. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Fri Oct 18 18:45:53 2019 InstallationDate: Installed on 2017-07-13 (826 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868442] Re: Missing wireless network interface after kernel 5.3.0-43 upgrade with eoan
@Rustin, it's currently committed to eoan master-next tree, but not yet released to eoan-proposed. Please stay tuned and wait for message like comment #14. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868442 Title: Missing wireless network interface after kernel 5.3.0-43 upgrade with eoan Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: I updated to latest kernel: initrd.img-5.3.0-43-generic and find that bluetooth is enabled and no wireless connection. When I stop bluetooth I go into airplane mode. I cannot find any wireless connection in network or wireless connection setup in settings. ifconfig shows there is no wireless interface setup. When I go back to kernel 5.3.0-42 everything is working correctly. I am using an HP laptop. I can see the wireless network controller with lshw: lshw -C network *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: eno1 version: 15 serial: b4:b6:86:e7:67:29 size: 100Mbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 duplex=full firmware=rtl8168h-2_0.0.2 02/26/15 ip=192.168.1.108 latency=0 link=yes multicast=yes port=MII speed=100Mbit/s resources: irq:38 ioport:e000(size=256) memory:fe904000-fe904fff memory:fe90-fe903fff *-network description: Network controller product: Dual Band Wireless-AC 3168NGW [Stone Peak] vendor: Intel Corporation physical id: 0 bus info: pci@:03:00.0 version: 10 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: driver=iwlwifi latency=0 resources: irq:43 memory:fe80-fe801fff lspci |grep Network 03:00.0 Network controller: Intel Corporation Dual Band Wireless-AC 3168NGW [Stone Peak] (rev 10) iwconfig lo no wireless extensions. eno1 no wireless extensions. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-43-generic 5.3.0-43.36 ProcVersionSignature: Ubuntu 5.3.0-43.36-generic 5.3.18 Uname: Linux 5.3.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rustin 1684 F pulseaudio Date: Sun Mar 22 05:43:04 2020 InstallationDate: Installed on 2018-11-30 (478 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: HP HP Pavilion Laptop 17-ar0xx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-43-generic root=UUID=29898130-1fa9-464b-88cf-ed44cfd58f76 ro pcie_aspm=force acpi_backlight=vendor 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.3.0-43-generic N/A linux-backports-modules-5.3.0-43-generic N/A linux-firmware1.183.5 RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/12/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8357 dmi.board.vendor: HP dmi.board.version: 37.34 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.22:bd01/12/2018:svnHP:pnHPPavilionLaptop17-ar0xx:pvr:rvnHP:rn8357:rvr37.34:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 17-ar0xx dmi.product.sku: 1KU52UA#ABA dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rustin 1600 F pulseaudio /dev/snd/controlC0: rustin 1600 F pulseaudio DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2018-11-30 (480 d
[Kernel-packages] [Bug 1866734] Re: All PS/2 ports on PS/2 Serial add-in bracket are not working after S3
Verified version 5.4.0-20.24 in focal-proposed. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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/1866734 Title: All PS/2 ports on PS/2 Serial add-in bracket are not working after S3 Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Eoan: New Status in linux-oem source package in Eoan: New Status in linux-oem-osp1 source package in Eoan: Fix Released Status in linux source package in Focal: Fix Committed Bug description: [Impact] PS/2 ports on PS/2 Serial add-in card do not work after S3. [Fix] The i8042 controller selftest fails while resuming, adding retry fix this issue. [Test] Verified on the target machine, the ps/2 keyboard keeps working after S3 test 30 times. [Regression Potential] Low, there is a retry logic in controller selftest, but it returns directly if it fails to communicate with the controller. This commit make it retry 5 times before return fails. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1866734/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848771]
Is there anything we can do to further diagnose this 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/1848771 Title: Reboot after resume from suspend (deep) Status in linux package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Invalid Bug description: After upgrading to Kubuntu Eoan (19.10) yesterday, my laptop crashes after resume from suspending. This is regardless the way of suspending (closing lid, selecting suspend from sddm, systemctl suspend). The journal shows: ferry@chromium:~$ journalctl -b -1 -e .. sddm[1106]: Message received from greeter: Suspend NetworkManager[836]: manager: sleep: sleep requested (sleeping: no enabled: yes) NetworkManager[836]: device (60:73:BC:BA:B8:68): state change: disconnected -> unmanaged (reason ' NetworkManager[836]: device (60:73:BC:23:8F:3E): state change: disconnected -> unmanaged (reason ' NetworkManager[836]: device (p2p-dev-wlp1s0): state change: disconnected -> unmanaged (reason 'sle NetworkManager[836]: manager: NetworkManager state is now ASLEEP systemd[1]: Reached target Sleep. systemd[1]: Starting Suspend... systemd-sleep[1238]: Suspending system... kernel: PM: suspend entry (deep) On resume (keypress, open lid) resume starts but immediately crashes and reboots. The laptop is an Acer 720p Chromebook with Chromium replaced and working fine with Kubuntu since 5 years or so. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Fri Oct 18 18:45:53 2019 InstallationDate: Installed on 2017-07-13 (826 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848771]
Hi, Is it possible to recompile the kernel on latest kernel without "CONFIG_TCG_TPM" , and apply the following debug patch from https://patchwork.kernel.org/patch/11464059/ and check: echo test_resume > /sys/power/disk echo disk > /sys/power/state and wait for 5 seconds to see if it could resume automatically? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848771 Title: Reboot after resume from suspend (deep) Status in linux package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Invalid Bug description: After upgrading to Kubuntu Eoan (19.10) yesterday, my laptop crashes after resume from suspending. This is regardless the way of suspending (closing lid, selecting suspend from sddm, systemctl suspend). The journal shows: ferry@chromium:~$ journalctl -b -1 -e .. sddm[1106]: Message received from greeter: Suspend NetworkManager[836]: manager: sleep: sleep requested (sleeping: no enabled: yes) NetworkManager[836]: device (60:73:BC:BA:B8:68): state change: disconnected -> unmanaged (reason ' NetworkManager[836]: device (60:73:BC:23:8F:3E): state change: disconnected -> unmanaged (reason ' NetworkManager[836]: device (p2p-dev-wlp1s0): state change: disconnected -> unmanaged (reason 'sle NetworkManager[836]: manager: NetworkManager state is now ASLEEP systemd[1]: Reached target Sleep. systemd[1]: Starting Suspend... systemd-sleep[1238]: Suspending system... kernel: PM: suspend entry (deep) On resume (keypress, open lid) resume starts but immediately crashes and reboots. The laptop is an Acer 720p Chromebook with Chromium replaced and working fine with Kubuntu since 5 years or so. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Fri Oct 18 18:45:53 2019 InstallationDate: Installed on 2017-07-13 (826 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868551] Re: Screen freezes : NULL pointer dereference i915_active_acquire since Linux 5.4
With the above patch, I still have the screen freeze but without Kernel oops.
I will compile and my own Linux Kernel 4.15 (18.04 LTS) for Ubuntu 20.04 (soon
LTS) as
Intel Graphics i915 is unusable on my Dell XPS 13 connected to external
screen and XFCE4
i915 :00:02.0: GPU HANG: ecode 9:1:0x, hang on rcs0
i915 :00:02.0: Resetting rcs0 for hang on rcs0
[drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out:
{request: 0001, RESET_CTL: 0001}
i915 :00:02.0: Resetting chip for hang on rcs0
[drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out:
{request: 0001, RESET_CTL: 0001}
[drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out:
{request: 0001, RESET_CTL: 0001}
Asynchronous wait on fence i915:xfwm4[1901]:57922 timed out
(hint:intel_atomic_commit_ready+0x0/0x54 [i915])
Asynchronous wait on fence i915:xfwm4[1901]:57922 timed out
(hint:intel_atomic_commit_ready+0x0/0x54 [i915])
i915 :00:02.0: Resetting rcs0 for hang on rcs0
i915 :00:02.0: Resetting rcs0 for hang on rcs0
...
i915 :00:02.0: GPU recovery timed out, cancelling all in-flight rendering.
i915 :00:02.0: Resetting chip for hang on rcs0
i915 :00:02.0: Resetting rcs0 for hang on rcs0
i915 :00:02.0: Resetting rcs0 for hang on rcs0
Asynchronous wait on fence i915:xfwm4[1901]:57926 timed out
(hint:intel_atomic_commit_ready+0x0/0x54 [i915])
Asynchronous wait on fence i915:xfwm4[1901]:57926 timed out
(hint:intel_atomic_commit_ready+0x0/0x54 [i915])
i915 :00:02.0: Resetting rcs0 for hang on rcs0
i915 :00:02.0: Resetting rcs0 for hang on rcs0
...
i915 :00:02.0: GPU recovery timed out, cancelling all in-flight rendering.
i915 :00:02.0: Resetting chip for hang on rcs0
i915 :00:02.0: Resetting rcs0 for hang on rcs0
[drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out:
{request: 0001, RESET_CTL: 0001}
i915 :00:02.0: Resetting chip for hang on rcs0
[drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out:
{request: 0001, RESET_CTL: 0001}
[drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out:
{request: 0001, RESET_CTL: 0001}
i915 :00:02.0: Resetting rcs0 for hang on rcs0
i915 :00:02.0: Resetting rcs0 for hang on rcs0
Asynchronous wait on fence i915:xfwm4[1901]:5792a timed out
(hint:intel_atomic_commit_ready+0x0/0x54 [i915])
Asynchronous wait on fence i915:xfwm4[1901]:5792a timed out
(hint:intel_atomic_commit_ready+0x0/0x54 [i915])
i915 :00:02.0: Resetting rcs0 for hang on rcs0
i915 :00:02.0: Resetting rcs0 for hang on rcs0
...
i915 :00:02.0: GPU recovery timed out, cancelling all in-flight rendering.
i915 :00:02.0: Resetting chip for hang on rcs0
i915 :00:02.0: Resetting rcs0 for hang on rcs0
...
Asynchronous wait on fence i915:xfwm4[1901]:5792e timed out
(hint:intel_atomic_commit_ready+0x0/0x54 [i915])
Asynchronous wait on fence i915:xfwm4[1901]:5792e timed out
(hint:intel_atomic_commit_ready+0x0/0x54 [i915])
i915 :00:02.0: Resetting rcs0 for hang on rcs0
i915 :00:02.0: Resetting rcs0 for hang on rcs0
...
i915 :00:02.0: GPU recovery timed out, cancelling all in-flight rendering.
i915 :00:02.0: Resetting chip for hang on rcs0
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
i915 :00:02.0: Resetting rcs0 for hang on rcs0
i915 :00:02.0: Resetting rcs0 for hang on rcs0
Asynchronous wait on fence i915:xfwm4[1901]:57932 timed out
(hint:intel_atomic_commit_ready+0x0/0x54 [i915])
Asynchronous wait on fence i915:xfwm4[1901]:57932 timed out
(hint:intel_atomic_commit_ready+0x0/0x54 [i915])
i915 :00:02.0: Resetting rcs0 for hang on rcs0
i915 :00:02.0: Resetting rcs0 for hang on rcs0
...
i915 :00:02.0: Resetting rcs0 for hang on rcs0
i915 :00:02.0: GPU recovery timed out, cancelling all in-flight rendering.
i915 :00:02.0: Resetting chip for hang on rcs0
i915 :00:02.0: GPU recovery timed out, cancelling all in-flight rendering.
i915 :00:02.0: Resetting chip for hang on rcs0
i915 :00:02.0: Resetting rcs0 for hang on rcs0
Asynchronous wait on fence i915:xfwm4[1901]:57936 timed out
(hint:intel_atomic_commit_ready+0x0/0x54 [i915])
Asynchronous wait on fence i915:xfwm4[1901]:57936 timed out
(hint:intel_atomic_commit_ready+0x0/0x54 [i915])
i915 :00:02.0: Resetting rcs0 for hang on rcs0
i915 :00:02.0: Resetting rcs0 for hang on rcs0
...
i915 :00:02.0: GPU recovery timed out, cancelling all in-flight rendering.
i915 :00:02.0: Resetting chip for hang on rcs0
i915 :00:02.0: Resetting rcs0 for hang on rcs0
i915 :00:02.0: Resetting rcs0 for hang on rcs0
Asynchronous wait on fence i915:xfwm4[1901]:57938 timed out
(hint:intel_atomic_commit_ready+0x0/0x54 [i915])
Asynchronous wait on fence i915:xfwm4[1901]:57938 timed out
(hint:intel_atomic_commit_ready+0x0/0x54 [i915])
i915 :00:02.0: Rese
[Kernel-packages] [Bug 1374084] Re: Bluetooth: hci0 SCO packet for unknown connection handle 41
Launchpad has imported 2 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=85161. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2014-09-25T18:39:53+00:00 caravena wrote: Open bug in launchpad.net https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1374084 "[63716.030347] input: 00:1E:7C:22:33:21 as /devices/virtual/input/input13 [63721.787306] Bluetooth: hci0 SCO packet for unknown connection handle 41 [63721.787316] Bluetooth: hci0 SCO packet for unknown connection handle 41 [63814.034162] Bluetooth: hci0 SCO packet for unknown connection handle 35 [63814.034176] Bluetooth: hci0 SCO packet for unknown connection handle 35 [63814.034183] Bluetooth: hci0 SCO packet for unknown connection handle 35" Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1374084/comments/2 On 2020-03-08T06:27:06+00:00 info wrote: https://dankvapecenter.com/product/west-coast-cure-pens-1000mg- cartridge/ Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1374084/comments/3 ** Changed in: linux Status: Unknown => Confirmed ** Changed in: linux Importance: Unknown => 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/1374084 Title: Bluetooth: hci0 SCO packet for unknown connection handle 41 Status in Linux: Confirmed Status in linux package in Ubuntu: Triaged Bug description: [63716.030347] input: 00:1E:7C:22:33:21 as /devices/virtual/input/input13 [63721.787306] Bluetooth: hci0 SCO packet for unknown connection handle 41 [63721.787316] Bluetooth: hci0 SCO packet for unknown connection handle 41 [63814.034162] Bluetooth: hci0 SCO packet for unknown connection handle 35 [63814.034176] Bluetooth: hci0 SCO packet for unknown connection handle 35 [63814.034183] Bluetooth: hci0 SCO packet for unknown connection handle 35 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-17-generic 3.16.0-17.23 [modified: boot/vmlinuz-3.16.0-17-generic] ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 Uname: Linux 3.16.0-17-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: caravena 2110 F...m pulseaudio /dev/snd/controlC0: caravena 2110 F pulseaudio CurrentDesktop: GNOME Date: Thu Sep 25 15:36:47 2014 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2014-09-25 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-17-generic.efi.signed root=UUID=0fb75fae-baa3-428b-ace4-498e69ff7fb6 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-17-generic N/A linux-backports-modules-3.16.0-17-generic N/A linux-firmware 1.134 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1374084/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845632] Re: After dist-upgrade, s390x running X-fips/B-fips kernel will boot into generic kernel
** Tags added: sru-20200316 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845632 Title: After dist-upgrade, s390x running X-fips/B-fips kernel will boot into generic kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Issue found on s390x KVM Steps: 1. Deploy a s390x KVM with Xenial 2. Enable -proposed 3. Enable FIPS ppa 4. Install the FIPS kernel with linux-fips meta package 5. reboot 6. dist-upgrade 7. reboot The system will boot into the correct fips kernel on step 5, but it will boot into the generic kernel in proposed on step 7. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1845632/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869694] [NEW] Support SMO8840 as LIS2DH12
Public bug reported: === Impact === According to ST, HID SMO8840 is for LIS2DH12. In Ubuntu kernel, support for this ID is missing in Bionic, and it's mapped to LNG2DM in D/E/F. === Fix === * e43d110cdc20 - iio: st_sensors: remap SMO8840 to LIS2DH12 This is in mainline kernel 5.6, and also 4.19, 5.4, and 5.5 stable trees. === Risk of Regression === Low. Hans de Goede@redhat, who originally mapped SMO8840 to LNG2DM, confirmed the patch works for his Lenovo Ideapad Miix 320: https://lore.kernel.org/linux-iio/20200224095426.25681-1-jesse.s...@canonical.com/T/#u ** Affects: hwe-next Importance: Undecided Assignee: Jesse Sung (wenchien) Status: Fix Released ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: In Progress ** Affects: linux (Ubuntu Bionic) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: In Progress ** Affects: linux (Ubuntu Disco) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: In Progress ** Affects: linux (Ubuntu Eoan) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: In Progress ** Affects: linux (Ubuntu Focal) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: In Progress ** Tags: oem-priority originate-from-1844631 presidio ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: In Progress ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Jesse Sung (wenchien) ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => Jesse Sung (wenchien) ** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => Jesse Sung (wenchien) ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Disco) Status: New => In Progress ** Changed in: linux (Ubuntu Eoan) Status: New => In Progress ** Tags added: oem-priority originate-from-1844631 presidio ** Changed in: hwe-next Status: New => Fix Released ** Changed in: hwe-next 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/1869694 Title: Support SMO8840 as LIS2DH12 Status in HWE Next: Fix Released Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Bug description: === Impact === According to ST, HID SMO8840 is for LIS2DH12. In Ubuntu kernel, support for this ID is missing in Bionic, and it's mapped to LNG2DM in D/E/F. === Fix === * e43d110cdc20 - iio: st_sensors: remap SMO8840 to LIS2DH12 This is in mainline kernel 5.6, and also 4.19, 5.4, and 5.5 stable trees. === Risk of Regression === Low. Hans de Goede@redhat, who originally mapped SMO8840 to LNG2DM, confirmed the patch works for his Lenovo Ideapad Miix 320: https://lore.kernel.org/linux-iio/20200224095426.25681-1-jesse.s...@canonical.com/T/#u To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1869694/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866581] Re: The voice recording function cannot work while connecting a headset on a Dell machine
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1046.51 --- linux-oem-osp1 (5.0.0-1046.51) bionic; urgency=medium * bionic/linux-oem-osp1: 5.0.0-1046.51 -proposed tracker (LP: #1869295) * The voice recording function cannot work while connecting a headset on a Dell machine (LP: #1866581) - SAUCE: ALSA: hda/realtek - Add Headset Mic supported -- Timo Aaltonen Fri, 27 Mar 2020 07:31:46 +0200 ** Changed in: linux-oem-osp1 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866581 Title: The voice recording function cannot work while connecting a headset on a Dell machine Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Committed Status in linux-oem-osp1 source package in Eoan: Invalid Status in linux source package in Focal: Incomplete Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [Impact] The headset mic can't record any sound on this machine. [Fix] The headset-mic is set to ctia mode by hardware. we need to apply an existing quirk. [Test Case] boot the system, plug the headset, it could record the sound via headset mic. [Regression Risk] Low, this patch is specific to 2 dell machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1866581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798400]
The premise is that my ignorance on BT is complete. After some investigation, it is my understanding that RFCOMM channels are to RFCOMM communication a bit like ports in TCP and UDP, with the main difference that while there are really a lot of TCP/UDP ports and some of them are reserved as "well known ports", the number of channels in RFCOMM is extremely limited, so that there cannot be well known ports. Furthermore, I understand that no one should "hardwire" RFCOMM channels and that channels should be released whenever not strictly needed. If this understanding from myself is correct, there may be issues both in LibO and in PA. >From my understanding: - LibO and the Impress remote should not hardwire RFCOMM channel 3. I understand that they should dynamically allocate a channel and make it discoverable via SDP. - Impress should not keep binded to an RFCOMM channel all the time. There should be a visible option to switch on and off the binding (probably there should be a couple of impress remote related options in the "Slide Show -> Slide Show Settings" window, including one to fire up the BT rfcomm binding). - PA should probably similarly not hardwire channel 3 for its HSP role, but here the situation seems more complex, because it may be the case that PA needs to strive for compatibility with devices that do not play to the rules. - PA should probably have a DBUS interface to switch on and off the RFCOMM binding, so that to use an application needing RFCOMM channel 3, one does not need to take down the whole of PA. I have opened a bug on PA too. See it at https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/827. That report is bad, because when I made it my understanding of BT was even poorer than it is now. In any case, it seems to me that the current issue could be fixed completely on the LibO side, by dynamically allocating the channel and by letting the app running on the phone discover it via SDP. -- 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/1798400 Title: [upstream] Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: Confirmed Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dm
[Kernel-packages] [Bug 1798400] Re: [upstream] Regression: cannot use impress remote over bluetooth with ubuntu bionic
** Bug watch added: PulseAudio #827 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/827 -- 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/1798400 Title: [upstream] Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: Confirmed Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868210] Re: [SRU] Load ucm on Lenovo notebooks based on bios version
One of users verified the debdiff on eoan, it worked as expected. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845678/comments/26 thx. -- 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/1868210 Title: [SRU] Load ucm on Lenovo notebooks based on bios version Status in HWE Next: New Status in alsa-lib package in Ubuntu: Invalid Status in alsa-lib source package in Bionic: Confirmed Status in alsa-lib source package in Eoan: Confirmed Status in alsa-lib source package in Focal: Invalid Bug description: This SRU is not backported from upstream of alsa-lib and this SRU is not going to be submitted to upstream. That is because the latest alsa-lib already supports ucm2, and with ucm2 all machines could share one ucm, so latest alsa-lib does not have this problem. This problem is only specific to the alsa-lib in Bionic and Eoan. [Impact] On some Lenovo notebooks, UCM files are not loaded and mic can't be used. [Fix] UCM was loaded based on cardlongname, but that can't cover all configs of the same model. Lenovo suggested to load ucm by the first 3 letters of /sys/devices/virtual/dmi/id/bios_version, so that all configs could use just one ucm. [Test Case] After applying this patch, install the testing alsa-lib on Lenovo X1C7 and Dell vostro 5390, which are all machines with the DMIC connected to PCH. After system bootup, check the /usr/share/alsa/ucm/ for the presence of LENOVO-BIOSID-xxx directories. Lenovo X1C7 should load the N2H/*.conf and verify the audio functionalities. The Dell machine should still load the ucm by cardname, and it should work as good as before. [Regression Potential] low, just add some new UCMs and let Lenovo machine find the UCM by bios_version if it fails by cardlongname. I've already tested the change on Lenovo and Dell machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1868210/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845678] Re: Lenovo ThinkPad X1 Carbon 7th Generation built-in microphone doesn't work
Thanks Jean, your feedback is helpful to SRU the fix of this bug: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1868210 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845678 Title: Lenovo ThinkPad X1 Carbon 7th Generation built-in microphone doesn't work Status in linux package in Ubuntu: Confirmed Bug description: The built-in microphone in my Lenovo ThinkPad X1 Carbon 7th Generation doesn't work. A microphone on a headset plugged into the 3.5mm jack works fine. This is probably relevant: https://bugzilla.kernel.org/show_bug.cgi?id=201251 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-12-generic 5.3.0-12.13 ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0 Uname: Linux 5.3.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jik3746 F pulseaudio /dev/snd/pcmC0D0p: jik3746 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 27 11:13:25 2019 InstallationDate: Installed on 2019-09-12 (14 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20QD001VUS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-12-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-12-generic N/A linux-backports-modules-5.3.0-12-generic N/A linux-firmware1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-20 (7 days ago) dmi.bios.date: 07/04/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET30W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QD001VUS 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:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QD001VUS dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845678/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1860800] Re: Ubuntu 19.10 doesn't shutdown
Reboot always works :) Do you have the same problem? On 30/03/2020 10:21, Kai-Heng Feng wrote: > Can you please see if reboot works when there's no previous suspend > attempt? > > I can see this after system resume from suspend: > [ 3403.666188] PM: dpm_run_callback(): usb_dev_resume+0x0/0x20 returns -5 > [ 3403.666191] PM: Device 2-1.8 failed to resume async: error -5 > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860800 Title: Ubuntu 19.10 doesn't shutdown Status in linux package in Ubuntu: Confirmed Bug description: Hello guys, I can't shutdown Ubuntu 19.10. When I try, the shutdown screen appears. The first two dots below the ubuntu logo, turn orange and then it freezes. Reboot works fine. The debug-shell is no use, because at the freeze point I can't type in commands. When I press ESC to see what's going on during shutdown, the last message to appear ist "[Some weird number] reboot: power down. Last time I pressed ESC during shutdown the "weird number" was 85.270119. I also tried to shutdown with the terminal commands "sudo shutdown now", "sudo shutdown -P now", "sudo shutdown -h now", "poweroff" and "sudo poweroff -f". All of them had the effect as describe above except the command "sudo poweroff -f". After I typed in the command, I authenticated and following messages appeared: "Powering off...". At this point it freezed. I could still see the desktop and every visible window, but I couldn't perform any actions; not even keyboard shortcuts worked. It also did not help to change 'GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"' in /etc/default/grub to 'GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=force"' and run "update-grub". Once the following command combo did work: "sudo swapoff -a && systemctl poweroff", but the I reinstalled Ubuntu and now it doesn't work any more. In the application "Additional Drivers" I selected the proprietary and tested driver of NVIDIA, but I can't to this for my WLAN-Card (correct word?), because the "Additional Drivers" says it's not working, but my WLAN works fine. I've got only Bluetooth problems. The displayed name of the WLAN-Card is: "Intel Corporation: Wireless 7260 (Dual Band Wireless-AC 7260)". I also tried to manually install a driver it didn't help. When I wake up the laptop, a black screen appears with some error messages, but only for a very short time so I can't make a photo of it. I tried once and the text was unreadable. I have the latest BIOS and my Computer model is MSI PX60 2QD. It doesn't work with Arch Linux either. Thanks for your help :) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leonard1724 F pulseaudio /dev/snd/controlC1: leonard1724 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-18 (7 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. PX60 2QD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=04df7493-393f-447e-bfb3-3dc43c2ee645 ro quiet splash acpi=force vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 Tags: eoan Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16H6IMS.110 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16H6 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.B dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16H6IMS.110:bd11/03/2015:svnMicro-StarInternationalCo.,Ltd.:pnPX602QD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H6:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: PX60 2QD dmi.product.sku: To be filled by O.E.M. dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860800/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1722478]
The bug is still present in 5.3 (from Ubuntu). I haven't had a chance to check upstream yet. Is any maintainer monitoring this ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1722478 Title: Two-finger scrolling and click-and-drag no longer works after resuming from suspend Status in Linux: Confirmed Status in kmod package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I own a Thinkpad T440p onto which I have had Debian 9 running without hardware issues. I have recently installed Ubuntu 17.10 final beta to test it out, but two-finger scrolling does not work at the moment. It used to work out-of-the-box from the final beta iso, but a subsequent update broke it. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghislain 10620 F pulseaudio /dev/snd/controlC0: ghislain 10620 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 10 09:20:01 2017 HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e InstallationDate: Installed on 2017-10-05 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: LENOVO 20AN00C1UK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET83WW (2.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AN00C1UK dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AN00C1UK dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1722478/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806437]
Any update on this? I'm currently running into this issue as 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/1806437 Title: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello, dmesg: [ 15.390738] acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2769 F pulseaudio /dev/snd/pcmC0D0p: caravena 2769 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 12:49:26 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (0 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806437/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846016]
FWIW this has regressed in 5.5 - tracked in Bug 206395 -- 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/1846016 Title: Intel Wireless AC 3168 on Eoan complaints FW error in SYNC CMD GEO_TX_POWER_LIMIT Status in Linux: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem package in Ubuntu: Confirmed Status in linux-oem-osp1 package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux-oem source package in Disco: Fix Released Status in linux-oem-osp1 source package in Disco: Fix Released Status in linux source package in Eoan: Fix Committed Status in linux-oem source package in Eoan: Fix Released Status in linux-oem-osp1 source package in Eoan: Fix Released Bug description: I have ubuntu 19.10 Eoan Ermine development version. Cannot boot since yesterday. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-firmware 1.182 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Mon Sep 30 20:57:08 2019 Dependencies: InstallationDate: Installed on 2019-07-23 (68 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: Upgraded to eoan on 2019-09-27 (2 days ago) -- Also found on Ubuntu-certified HP EliteDesk 800 G3 DM. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1846016/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806437]
Still seeing this in Ubuntu 20 daily. Mar 24 22:56:31 buntu kernel: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) Mar 24 22:56:31 buntu kernel: wmi_bus wmi_bus-PNP0C14:03: WQBC data block query control method not found Mar 24 22:56:31 buntu kernel: acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806437 Title: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello, dmesg: [ 15.390738] acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2769 F pulseaudio /dev/snd/pcmC0D0p: caravena 2769 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 12:49:26 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (0 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806437/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863627] Re: Intel Dual Band Wireless AC 9560 [8086:9df0] subsystem id [8086:0034] kernel oops in __iwl_mvm_mac_stop
Launchpad has imported 7 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=204785. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2019-09-05T18:06:59+00:00 L.Bonnaud wrote: Hi, I used Wi-Fi for some time then disabled Wi-Fi with NetworkManager. Here is my Wi-Fi adapter: $ lspci [...] 02:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a) This caused the following WARNING in the kernel logs: [24004.175187] wlan0: deauthenticating from 18:8b:9d:39:72:cf by local choice (Reason: 3=DEAUTH_LEAVING) [24004.202438] [ cut here ] [24004.202442] UMAC scan UID 1 status was not cleaned [24004.202527] WARNING: CPU: 2 PID: 1063 at drivers/net/wireless/intel/iwlwifi/mvm/mac80211.c:1434 __iwl_mvm_mac_stop+0x129/0x130 [iwlmvm] [24004.202529] Modules linked in: usbhid ccm xt_conntrack xt_MASQUERADE iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_CHECKSUM iptable_mangle xt_tcpudp iptable_filter bpfilter bridge stp llc dummy overlay bnep binfmt_misc snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic mei_hdcp dell_rbtn snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec intel_rapl snd_hda_core x86_pkg_temp_thermal nls_iso8859_1 snd_hwdep intel_powerclamp coretemp kvm_intel kvm irqbypass snd_pcm arc4 i915 snd_seq_midi snd_seq_midi_event crct10dif_pclmul crc32_pclmul ghash_clmulni_intel dell_laptop ledtrig_audio joydev dell_smm_hwmon aesni_intel snd_rawmidi iwlmvm drm_kms_helper snd_seq mac80211 aes_x86_64 crypto_simd cryptd glue_helper intel_cstate intel_rapl_perf uvcvideo dell_wmi videobuf2_vmalloc input_leds dell_smbios [24004.202580] videobuf2_memops snd_seq_device videobuf2_v4l2 intel_wmi_thunderbolt serio_raw iwlwifi dcdbas snd_timer wmi_bmof dell_wmi_descriptor videobuf2_common drm btusb btrtl snd btbcm videodev btintel cfg80211 bluetooth i2c_algo_bit fb_sys_fops soundcore mei_me syscopyarea ecdh_generic sysfillrect media mei hid_multitouch sysimgblt ecc idma64 virt_dma intel_pch_thermal intel_xhci_usb_role_switch roles ucsi_acpi typec_ucsi rtsx_pci_ms processor_thermal_device memstick intel_soc_dts_iosf typec dell_smo8800 int3403_thermal acpi_pad mac_hid int340x_thermal_zone int3400_thermal intel_hid acpi_thermal_rel sparse_keymap sch_fq_codel nf_tables parport_pc nfnetlink ppdev lp parport ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq libcrc32c hid_generic rtsx_pci_sdmmc nvme e1000e i2c_i801 nvme_core ahci rtsx_pci intel_lpss_pci libahci intel_lpss i2c_hid wmi hid video [24004.202648] CPU: 2 PID: 1063 Comm: NetworkManager Not tainted 5.2.11-050211-generic #201908290731 [24004.202650] Hardware name: Dell Inc. Latitude 5590/0VYDFF, BIOS 1.10.1 07/19/2019 [24004.202668] RIP: 0010:__iwl_mvm_mac_stop+0x129/0x130 [iwlmvm] [24004.202672] Code: 8c 04 00 00 74 0e 42 c7 84 a3 b4 1b 00 00 00 00 00 00 eb c0 44 89 e6 48 c7 c7 70 0e e7 c0 c6 05 4d 8c 04 00 01 e8 93 a8 a6 d4 <0f> 0b eb d8 0f 1f 00 0f 1f 44 00 00 55 48 89 e5 41 56 41 55 41 54 [24004.202675] RSP: 0018:b381c2acbc30 EFLAGS: 00010286 [24004.202678] RAX: RBX: 8b3f194a1628 RCX: 0006 [24004.202680] RDX: 0007 RSI: 0096 RDI: 8b3f1e317440 [24004.202682] RBP: b381c2acbc40 R08: 05ea R09: 0004 [24004.202684] R10: R11: 0001 R12: 0001 [24004.202686] R13: 8b3f194a1690 R14: 8b3f194a1628 R15: 8b3f194a0f88 [24004.202689] FS: 7f1d2ae16bc0() GS:8b3f1e30() knlGS: [24004.202692] CS: 0010 DS: ES: CR0: 80050033 [24004.202694] CR2: 7f281dc98000 CR3: 0003fef50002 CR4: 003606e0 [24004.202696] DR0: DR1: DR2: [24004.202698] DR3: DR6: fffe0ff0 DR7: 0400 [24004.202700] Call Trace: [24004.202720] iwl_mvm_mac_stop+0xe2/0x100 [iwlmvm] [24004.202759] drv_stop+0x39/0x100 [mac80211] [24004.202805] ieee80211_stop_device+0x46/0x50 [mac80211] [24004.202840] ieee80211_do_stop+0x583/0x810 [mac80211] [24004.202872] ieee80211_stop+0x1a/0x20 [mac80211] [24004.202878] __dev_close_many+0xa5/0x120 [24004.202882] dev_close_many+0x91/0x150 [24004.202887] dev_close.part.0+0x4a/0x70 [24004.202890] dev_close+0x18/0x20 [24004.202928] cfg80211_shutdown_all_interfaces+0x77/0xd0 [cfg80211] [24004.202951] cfg80211_rfkill_set_block+0x26/0x30 [cfg80211] [24004.202956] rfkill_set_block+0x9b/0x150 [24004.202960] rfkill_fop_write+0x136/0x1e0 [24004.202967] __vfs_write
[Kernel-packages] [Bug 1609750]
I can get sound to work with a 5.4 kernel - but it's still not great... I haven't found a UCM file that let's it just work yet. What does work is using the alsactl -f downloaded/asound.state.txt bit and then VLC is able to play sound with Audio device set to chtmax98090, Direct hardware device without any conversions. Should this just work without any ucm/alsa restore? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1609750 Title: Audio not working on Acer Chromebook R11 Status in linux: Confirmed Status in linux package in Ubuntu: In Progress Status in pulseaudio package in Ubuntu: Invalid Bug description: Audio is not working at all on Acer Chromebook R11 (codename CYAN). It's a Intel Braswell platform. snd_hda_intel messages seem normal, but Pulseaudio does not detect sound hardware. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: pulseaudio 1:9.0-1.1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 Uname: Linux 4.4.0-33-generic x86_64 ApportVersion: 2.20.3-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Thu Aug 4 14:12:03 2016 InstallationDate: Installed on 2016-07-22 (13 days ago) InstallationMedia: PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2016 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Cyan dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE --- ApportVersion: 2.20.3-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=53fe7902-c347-4ff8-945d-a3e3de773a08 InstallationDate: Installed on 2016-07-22 (13 days ago) InstallationMedia: Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Cyan Package: linux-image-4.4.0-33-generic 4.4.0-33.52 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic root=UUID=742e4082-264a-4459-93df-9ec07b41d5e8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-33-generic N/A linux-backports-modules-4.4.0-33-generic N/A linux-firmware1.159 Tags: yakkety Uname: Linux 4.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2016 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Cyan dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1609750/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1609750]
I spoke to soon, trying out the galliumos-baytrail deb on Lubuntu gave me some better success. Right now, it appears I have working sound on every reboot with just this file from that package:https://github.com/GalliumOS/galliumos-baytrail/blob/master/etc/pulse/default.pa (this may depend on having saved asound.state first (or possibly put into /var/lib/alsa/ by package) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1609750 Title: Audio not working on Acer Chromebook R11 Status in linux: Confirmed Status in linux package in Ubuntu: In Progress Status in pulseaudio package in Ubuntu: Invalid Bug description: Audio is not working at all on Acer Chromebook R11 (codename CYAN). It's a Intel Braswell platform. snd_hda_intel messages seem normal, but Pulseaudio does not detect sound hardware. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: pulseaudio 1:9.0-1.1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 Uname: Linux 4.4.0-33-generic x86_64 ApportVersion: 2.20.3-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Thu Aug 4 14:12:03 2016 InstallationDate: Installed on 2016-07-22 (13 days ago) InstallationMedia: PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2016 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Cyan dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE --- ApportVersion: 2.20.3-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=53fe7902-c347-4ff8-945d-a3e3de773a08 InstallationDate: Installed on 2016-07-22 (13 days ago) InstallationMedia: Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Cyan Package: linux-image-4.4.0-33-generic 4.4.0-33.52 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic root=UUID=742e4082-264a-4459-93df-9ec07b41d5e8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-33-generic N/A linux-backports-modules-4.4.0-33-generic N/A linux-firmware1.159 Tags: yakkety Uname: Linux 4.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2016 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Cyan dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1609750/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869549] Re: [nvidia] Whenever a sound needs to be played the screen blanks out
No, it's not that Visual Alerts Feature. I tested out that flash feature, and it looks nothing like the error I was encountering. I also noticed a new thing. After I last messaged you, I put my laptop into sleep mode. Now when I opened the computer, I find that I can't reproduce the error. This is good, but I'm unable to figure out what is going on. So, effectively, a "Workaround" is found... I'll send you a video of the error taken from my phone camera soon, and I will also send you a screen recording of when I reproduce the error and also show you what happens when I use the visual alert feature (to convince you that it is different). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1869549 Title: [nvidia] Whenever a sound needs to be played the screen blanks out Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers-435 package in Ubuntu: Invalid Bug description: Whenever a sound needs to be played the screen blanks out for a second, then the screen comes back on, and the sound plays. Examples of sounds are when I press Tab on the terminal, and there are no possible completions, or when I press the down button on the terminal, and there are no further lines below, then it blanks out, comes back, and then plays the "ding" tone telling me there are no further completions or lines. However, after one blank-out, if I keep pressing the down button, the sounds play normally without blanking out for a short time. After that period, it repeats again on doing something that would cause the sound to be played again. I'm on a relatively new HP Pavilion CS3006TX, running 20.04 Focal Fossa (Development branch) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:06:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1) ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 29 09:05:04 2020 DistUpgraded: 2020-03-28 14:50:01,253 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-42-generic, x86_64: installed nvidia, 435.21, 5.4.0-18-generic, x86_64: installed virtualbox, 6.1.4, 5.3.0-42-generic, x86_64: installed virtualbox, 6.1.4, 5.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:86e2] Subsystem: Hewlett-Packard Company GP108M [GeForce MX250] [103c:86e2] InstallationDate: Installed on 2019-11-30 (119 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:03bc Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Wide Vision HD Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Laptop 15-cs3xxx ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5ee3ea75-c293-4350-b4ea-e81ef28c7f78 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-03-28 (0 days ago) dmi.bios.date: 08/23/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.03 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 86E2 dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.03:bd08/23/2019:svnHP:pnHPPavilionLaptop15-cs3xxx:pvrType1ProductConfigId:rvnHP:rn86E2:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cs3xxx dmi.product.sku: 8LX85PA#ACJ
[Kernel-packages] [Bug 1868113] Re: [Ubuntu 20.04] Striding RQ as Default for ConnectX-4
** Also affects: ubuntu-release-notes Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Status: Incomplete => Triaged ** Changed in: ubuntu-release-notes Assignee: (unassigned) => Frank Heimes (fheimes) ** Changed in: ubuntu-release-notes Status: New => Confirmed ** Changed in: ubuntu-z-systems Status: Triaged => 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/1868113 Title: [Ubuntu 20.04] Striding RQ as Default for ConnectX-4 Status in Release Notes for Ubuntu: Confirmed Status in Ubuntu on IBM z Systems: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: ello, Within our Network Performance runs in the RoCE Express 2(.1) area, we noticed a performance regression with streaming workloads which could be mitigated by using an ethtool setting. The Commit which switched the default value from "Striding RQ" to "Legacy RQ" for ConnectX-4 devices (RoCE Express 2(.1)) is attached here: commit 5ffd81943d7a57423f204cd5844bf430b5634472 (refs/bisect/bad) Author: Tariq Toukan Date: Tue Feb 20 15:17:54 2018 +0200 net/mlx5e: RX, Always prefer Linear SKB configuration Prefer the linear SKB configuration of Legacy RQ over the non-linear one of Striding RQ. This implies that ConnectX-4 LX now uses legacy RQ by default, as it does not support the linear configuration of Striding RQ. Signed-off-by: Tariq Toukan Signed-off-by: Saeed Mahameed diff --git a/drivers/net/ethernet/mellanox/mlx5/core/en_main.c b/drivers/net/ethernet/mellanox/mlx5/core/en_main.c index 2c634e50d051..333d4ed52b94 100644 --- a/drivers/net/ethernet/mellanox/mlx5/core/en_main.c +++ b/drivers/net/ethernet/mellanox/mlx5/core/en_main.c @@ -4405,9 +4405,16 @@ void mlx5e_build_nic_params(struct mlx5_core_dev *mdev, MLX5E_SET_PFLAG(params, MLX5E_PFLAG_RX_CQE_COMPRESS, params->rx_cqe_compress_def); /* RQ */ - if (mlx5e_striding_rq_possible(mdev, params)) - MLX5E_SET_PFLAG(params, MLX5E_PFLAG_RX_STRIDING_RQ, - !slow_pci_heuristic(mdev)); + /* Prefer Striding RQ, unless any of the following holds: +* - Striding RQ configuration is not possible/supported. +* - Slow PCI heuristic. +* - Legacy RQ would use linear SKB while Striding RQ would use non-linear. +*/ + if (!slow_pci_heuristic(mdev) && + mlx5e_striding_rq_possible(mdev, params) && + (mlx5e_rx_mpwqe_is_linear_skb(mdev, params) || +!mlx5e_rx_is_linear_skb(mdev, params))) + MLX5E_SET_PFLAG(params, MLX5E_PFLAG_RX_STRIDING_RQ, true); mlx5e_set_rq_type(mdev, params); mlx5e_init_rq_type_params(mdev, params); We have modified the upstream-kernel to allow us running of measurements and compare differences between Legacy RQ vs Striding RQ. Here is an example below: Kernel used: 5.4.0-rc7 The measurements run on a dedicated machine (z14) using uperf with streaming profiles (MTU size 1500). Example throughput drop: (traffic via a shared card, i.e. client and server using VFs from the same ConnectX-4) -- | |Legacy RQ| Striding RQ | -- |str-writex30k (1 connection) |24.62Gb/s| 33.47Gb/s| -- Additionaly, two tests with transactional workload using the ethtool proposed switch: -- | |Legacy RQ| Striding RQ | -- | rr1c-200x30k---1 | 4.12Gb/s|5.66Gb/s| -- | rr1c-200x30k--10 |15.10Gb/s| 20.77Gb/s| -- As concluded in the communication with Mellanox, there is a possibility to use a simple ethtool command to switch between the queuing methods, allowing us to avoid kernel code changes: ethtool --set-priv-flags DEVNAME rx_striding_rq on (To list the available settings you may use: ethtool --show-priv-flags DEVNAME) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1868113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1865471] Re: USB 3.1 Gen 1 not work after using suspend
I preferred tested using a live-USB Ubuntu 14.04 (kernel 4-4-0-112-generic) and a live-USB Ubuntu 12.04 (kernel 3.13). Wake up after Suspend : USB ports 3.1 Gen 1 of motherboard back panel don't work. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865471 Title: USB 3.1 Gen 1 not work after using suspend Status in linux package in Ubuntu: Incomplete Bug description: Good morning. I use "suspend"(settings -> energy -> When the shutdown button...) on 18.04. Each wake up, ONLY USB ports 3.1 Gen 1 of motherboard back panel don't work. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: christophe 1648 F pulseaudio /dev/snd/controlC2: christophe 1648 F pulseaudio /dev/snd/controlC0: christophe 1648 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-02-18 (14 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. enp6s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-A320M-S2H (rev. 1.x) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=9757d7ed-95dd-47d2-a3a7-80be35d05879 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-40-generic N/A linux-backports-modules-5.3.0-40-generic N/A linux-firmware1.173.15 RfKill: Tags: bionic Uname: Linux 5.3.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: A320M-S2H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/28/2019:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: A320M-S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1865471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863222] Re: Sync hwdata 0.333-1 (main) from Debian unstable (main)
** Changed in: hwdata (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to hwdata in Ubuntu.
https://bugs.launchpad.net/bugs/1863222
Title:
Sync hwdata 0.333-1 (main) from Debian unstable (main)
Status in hwdata package in Ubuntu:
Fix Released
Status in hwdata package in Debian:
Fix Released
Bug description:
Please sync hwdata 0.333-1 (main) from Debian unstable (main)
It has updated packaging and newer IDs useful for the new LTS.
Explanation of the Ubuntu delta and why it can be dropped:
* debian/rules:
- don't install deprecated changelog
The Ubuntu delta can be dropped because it's already in the Debian
package.
Changelog entries since current focal version 0.317-0ubuntu2:
hwdata (0.333-1) unstable; urgency=medium
* New upstream release: (Closes: #947191)
- pnp.ids: update Goldstar to LG Electronics (Closes: #95)
-- Pino Toscano Thu, 12 Mar 2020 06:45:31 +0100
hwdata (0.290-2) unstable; urgency=medium
* Take over the maintainership from Noël Köthe, with his permission.
Thanks for maintaining hwdata so far!
* Add the configuration for the CI on salsa.
* Stop shipping, and installing, a ChangeLog file generated from the
upstream Git repository, as it is not useful.
* Move the installation of pnp.ids to a hwdata.install file, instead of
copying it manually.
* Move the symlinks creation to a hwdata.links file, instead of passing
them as arguments of dh_link.
* Stop patching usb.ids, as we do not ship it anyway.
* Switch source format to "3.0 (quilt)".
* Bump the debhelper compatibility to 12:
- switch the debhelper build dependency to debhelper-compat 12
- remove debian/compat
* Rewrite rules to the dh sequencer, with no specific buildsystem.
* Remove dirs file, as the right directories are automatically created.
* Stop using the ${shlibs:Depends} substvar, as it does not exist in
arch:all binaries.
* Upstream moved to GitHub, so:
- switch Homepage to https://github.com/vcrhonek/hwdata
- switch watch file to GitHub tags
* Add Vcs-* fields.
* Remove README.build, as we do not ship usb.ids.
* Remove trailing whitespaces in changelog.
* Bump Standards-Version to 4.5.0, no changes required.
* Mark hwdata as Multi-Arch: foreign.
* Set Rules-Requires-Root: no.
-- Pino Toscano Fri, 06 Mar 2020 20:47:41 +0100
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1863222/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847832] Re: Backport ZoL pull request 9203 into the official packages.
This bug was fixed in the package zfs-linux - 0.8.1-1ubuntu14.4
---
zfs-linux (0.8.1-1ubuntu14.4) eoan; urgency=medium
* Fix deadlock in 'zfs rollback' (LP: #1847832)
- Upstream ZFS fix e7a2fa70c3b0 ("Fix deadlock in 'zfs rollback')
minor backport, wiggle and context adjustments.
-- Colin Ian King Tue, 10 Mar 2020 17:45:23
+
** Changed in: zfs-linux (Ubuntu Eoan)
Status: Fix Committed => Fix Released
--
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/1847832
Title:
Backport ZoL pull request 9203 into the official packages.
Status in zfs-linux package in Ubuntu:
In Progress
Status in zfs-linux source package in Eoan:
Fix Released
Bug description:
== SRU Justification, EOAN ==
ZFS can deadlock, this can be sometimes triggered with a zfs rollback
- "the zfs_resume_fs() code path may cause zfs to spawn new threads as
it reinstantiates the suspended fs's zil. When a new thread is
spawned, the kernel may attempt to free memory for that thread by
freeing some unreferenced inodes. If it happens to select inodes that
are a a part of the suspended fs a deadlock will occur because freeing
inodes requires holding the fs's z_teardown_inactive_lock which is
still held from the suspend."
== The Fix ==
Backport of ZFS upstream commit
e7a2fa70c3b0d8c8cee2b484038bb5623c7c1ea9 ("Fix deadlock in 'zfs
rollback'")
The backport is relatively simple context wiggle.
== Test Case ==
This is hard to trigger so testing is non-trivial. To check for
regressions we run the entire Ubuntu ZFS regression test suite.
Without the fix rollbacks can very occasionally trip this issue. With
the test, it's not possible.
== Regression Potential ==
The fix adds in an extra z_suspended flag to track suspended state and
adds an extra reference to stop the kernel from free'ing inodes on a
suspected file system. The changes are small and are well-used in
upstream ZFS so I believe if a regression was to have occurred it
would have been found by the regression testing.
- Original Bug Report Below ---
Hopefully this is the correct bug tracker to report this on.
Recently, I ran into a bug in ZFS as shipped in Ubuntu 19.10 that
caused the kernel to deadlock and the system to eventually hang.
I was advised by a ZFS on Linux project maintainer that this was a bug
that was fixed in 0.8.2.
The relevant pull request is here:
https://github.com/zfsonlinux/zfs/pull/9203
It would probably be a good idea to backport that pull request into
19.10's build of ZFS.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1847832/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833281]
On HP Stream 7 Tablet (1GB RAM) there was similar regression, but it started since Linux 4.12 instead of 4.10. Last year I tried bisect and several workarounds such as autostart cleanup, sysctl tweaks, zram, etc. But in the end it's seems like Linux 5.5.8 solved issue, at least in this particular use-case (device with 1GB RAM) 5.5.8 makes swapping perform like it was with 4.11. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833281 Title: System freeze when memory is put on SWAP in Linux >4.10.x Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I'm reporting this since it's reproduceable the 70% of the time. Summary: In different circumstances, when the systems starts to swap out RAM memory, even small amounts, the system becomes completely unusuable and the screen freezes up, no mouse movement, no TTY access or SSH access can be made, only SYSRQ keys seem to do something (only reboot, so REISUB worked so far though, OOM is useless since the memory/swap is not even full) The I/O Disk led is stuck to 100% in ALL the following cases when this happens. So far: - This happens even when only ZRAM is enabled, and no swap partition is used. - Happens when ZSWAP is used with a swap partition - Happens also when a partition without zram or zswap is used - Maybe it's AMD specific? However, I'm not experiencing this on my laptop using the same tests. My laptop is an Intel one, while my desktop is an AMD Ryzen platform. Here are the specs: CPU: AMD Ryzen 5 1600 no OC GPU: AMD RX 580 8GB SSD: Crucial MX500 500GB MOBO: MSI B350M Grenade RAM: 8GB HyperX Kingston 2667Mhz Ubuntu version: 18.04 LTS, backports repo enabled Kernel version: 4.18.0-18, official ubuntu repo Bios settings: Default Additional info: Maybe I'm not 100% sure, but I noticed when using the 5.0.0-17 generic kernel, the lockups seem to still happen, but they recover eventually. Happened only a few times though... But will always be frozen for at least 30 seconds, differently from my intel laptop where those do occur. The SSD make is the same. I bought two of these, they got also the same amount of RAM. In my laptop those do not occur at all. Swapping memory even huge quantities like 1GB or more, do not produce any issues. Tests made: For testing this behaviour I tried: - Compiling the chromium-browser source code (takes up a lot of system RAM) - Used the "stress" command, using a specific amount of memory to decide how many it will be swapped, and here I noticed that even small quantities like a couple of megabytes will cause the system to freeze the 70% of the times Example: "stress --vm 1 --vm-bytes=7G" What should happen: I expect system slowdowns when swapping out memory since I do not have enough RAM, but unlikely when using Windows or my laptop with the same Linux version, not a completely unusuable environment. The swap partition is in both cases on an SSD. Reproduceability: 70% of the times Additional info again: I'm not sure this is due to any hardware failure, my SSD health is fine, as my CPU and RAM. As I said swapping in Windows works fine... --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: haru 2076 F pulseaudio /dev/snd/controlC2: haru 2076 F pulseaudio /dev/snd/controlC0: haru 2076 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME DistroRelease: Ubuntu 18.04 IwConfig: enp24s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-17-generic root=UUID=75d45574-7169-4653-aea3-9f95087f0806 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-17.18~18.04.1-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-17-generic N/A linux-backports-modules-5.0.0-17-generic N/A linux-firmware1.173.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo video WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.K0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR (MS-7A37) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.c
[Kernel-packages] [Bug 1833281]
Another resource, quite long but has a tl;dr, and reviewed by some of the cgroups/resource control folks: https://chrisdown.name/2018/01/02/in-defence-of-swap.html I'll use somewhat technically sloppy language, but hopefully a useful metaphor: there's incidental swap and heavy swap. Incidental swap is when some file or anonymous page really isn't needed, and it's good to evict it to free up memory. But in the case of heavy swap (or even reclaim), not at all incidental, it becomes a serious performance impediment. The reality is that there are some tasks that just take gobs of memory and swap isn't a good substitute. But some swap is useful for freeing up memory for things that need to stay in memory. I'm finding for the incidental swap need, swap-on-ZRAM is quite useful. You are exchanging an IO bound task for a memory+CPU task; also it forces such pages to be pinned into memory. So there's no free lunch. Conservative use would be a ZRAM device around 1/4 of RAM up to a max of 50% RAM. It's not bad or wrong to use more, it's just that some workloads, like the webkitgtk example, have such significant need that it'll actually turn 1/2 of memory into swap, which in effect means you have 50% less RAM for that task. It actually makes the problem worse. Really, the near term is a) build with flags that cause fewer resources to be used in the firist place, or b) build in a systemd user session and limit resources that way, or c) buy more RAM, or d) use conventional swap partition, possibly with zswap to leave the most frequent pages in a small RAM cache pool, that's big enough for the task to eventually complete and just suffer with the ensuing lack of GUI responsiveness. Anyway, it's a bit complicated. And lots of moving parts. And probably needs more sophisticate use of perf and maybe even bpf could be useful in figuring where the various bottlenecks are. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833281 Title: System freeze when memory is put on SWAP in Linux >4.10.x Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I'm reporting this since it's reproduceable the 70% of the time. Summary: In different circumstances, when the systems starts to swap out RAM memory, even small amounts, the system becomes completely unusuable and the screen freezes up, no mouse movement, no TTY access or SSH access can be made, only SYSRQ keys seem to do something (only reboot, so REISUB worked so far though, OOM is useless since the memory/swap is not even full) The I/O Disk led is stuck to 100% in ALL the following cases when this happens. So far: - This happens even when only ZRAM is enabled, and no swap partition is used. - Happens when ZSWAP is used with a swap partition - Happens also when a partition without zram or zswap is used - Maybe it's AMD specific? However, I'm not experiencing this on my laptop using the same tests. My laptop is an Intel one, while my desktop is an AMD Ryzen platform. Here are the specs: CPU: AMD Ryzen 5 1600 no OC GPU: AMD RX 580 8GB SSD: Crucial MX500 500GB MOBO: MSI B350M Grenade RAM: 8GB HyperX Kingston 2667Mhz Ubuntu version: 18.04 LTS, backports repo enabled Kernel version: 4.18.0-18, official ubuntu repo Bios settings: Default Additional info: Maybe I'm not 100% sure, but I noticed when using the 5.0.0-17 generic kernel, the lockups seem to still happen, but they recover eventually. Happened only a few times though... But will always be frozen for at least 30 seconds, differently from my intel laptop where those do occur. The SSD make is the same. I bought two of these, they got also the same amount of RAM. In my laptop those do not occur at all. Swapping memory even huge quantities like 1GB or more, do not produce any issues. Tests made: For testing this behaviour I tried: - Compiling the chromium-browser source code (takes up a lot of system RAM) - Used the "stress" command, using a specific amount of memory to decide how many it will be swapped, and here I noticed that even small quantities like a couple of megabytes will cause the system to freeze the 70% of the times Example: "stress --vm 1 --vm-bytes=7G" What should happen: I expect system slowdowns when swapping out memory since I do not have enough RAM, but unlikely when using Windows or my laptop with the same Linux version, not a completely unusuable environment. The swap partition is in both cases on an SSD. Reproduceability: 70% of the times Additional info again: I'm not sure this is due to any hardware failure, my SSD health is fine, as my CPU and RAM. As I said swapping in Windows works fine... --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/co
[Kernel-packages] [Bug 1847832] Update Released
The verification of the Stable Release Update for zfs-linux has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
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/1847832
Title:
Backport ZoL pull request 9203 into the official packages.
Status in zfs-linux package in Ubuntu:
In Progress
Status in zfs-linux source package in Eoan:
Fix Released
Bug description:
== SRU Justification, EOAN ==
ZFS can deadlock, this can be sometimes triggered with a zfs rollback
- "the zfs_resume_fs() code path may cause zfs to spawn new threads as
it reinstantiates the suspended fs's zil. When a new thread is
spawned, the kernel may attempt to free memory for that thread by
freeing some unreferenced inodes. If it happens to select inodes that
are a a part of the suspended fs a deadlock will occur because freeing
inodes requires holding the fs's z_teardown_inactive_lock which is
still held from the suspend."
== The Fix ==
Backport of ZFS upstream commit
e7a2fa70c3b0d8c8cee2b484038bb5623c7c1ea9 ("Fix deadlock in 'zfs
rollback'")
The backport is relatively simple context wiggle.
== Test Case ==
This is hard to trigger so testing is non-trivial. To check for
regressions we run the entire Ubuntu ZFS regression test suite.
Without the fix rollbacks can very occasionally trip this issue. With
the test, it's not possible.
== Regression Potential ==
The fix adds in an extra z_suspended flag to track suspended state and
adds an extra reference to stop the kernel from free'ing inodes on a
suspected file system. The changes are small and are well-used in
upstream ZFS so I believe if a regression was to have occurred it
would have been found by the regression testing.
- Original Bug Report Below ---
Hopefully this is the correct bug tracker to report this on.
Recently, I ran into a bug in ZFS as shipped in Ubuntu 19.10 that
caused the kernel to deadlock and the system to eventually hang.
I was advised by a ZFS on Linux project maintainer that this was a bug
that was fixed in 0.8.2.
The relevant pull request is here:
https://github.com/zfsonlinux/zfs/pull/9203
It would probably be a good idea to backport that pull request into
19.10's build of ZFS.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1847832/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806681]
Any update on this? I'm currently running into this 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/1806681 Title: hp_wmi: query 0xd returned error 0x5 Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello, dmesg: [ 18.296366] hp_wmi: query 0xd returned error 0x5 Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2739 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Dec 4 09:05:38 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (1 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806681/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833281]
I primarily test by building webkitgtk [1], and I experience the same loss of system responsiveness whether / is ext4 or Btrfs. But I do see a difference in top and iotop. https://drive.google.com/open?id=12jpQeskPsvHmfvDjWSPOwIWSz09JIUlk This is an extreme case of refaulting, it's out of memory and swap, and since kswapd and btrfs threads are using a lot of CPU I'm guessing the faults are a mix of anonymous pages and file pages. At this point the system is really lost which is why the UX is the same with ext4 and btrfs; but behind the scenes it does seem more is going on. There might be other workloads which aren't as extreme, thereby exposing the difference. Two possible sources of the heavy CPU for btrfs threads: decompression, and checksumming. If it's true there is near constant reclaim happening, it's not just a simple minimum 4K read but rather a 128K minimum because all Btrfs compressed files use 128K extent size; is then decompressed, and then requires reading csum tree and computing csum on the read to compare. Ordinarily this is cheap but in this situation possibly it's resulting in a lot of extra congestion, but this is the limit of my knowledge so it's just speculation. Btrfs write amplification is a known issue (wandering trees problem). But that appears to not be the issue in this example. It might be this problem is better dealt with by cgroupsv2 to protect certain tasks from reclaim, and thus reduce the problem on any file system. But Btrfs alone (for now) does have more sophisticated cgroupvs2 IO isolation control as well. https://www.spinics.net/lists/cgroups/msg24743.html The upstream GNOME and KDE developers are aware of the loss of responsiveness problem and have done quite a lot of preliminary work in GNOME 3.34 with more work on the way. https://blogs.gnome.org/benzea/2019/10/01/gnome-3-34-is-now-managed-using-systemd/ You can today take advantage of this cgroupsv2 work by running resource hungry tasks as a systemd user unit in Fedora 31. https://blogs.gnome.org/benzea/2019/10/01/gnome-3-34-is-now-managed-using-systemd/#comment-14833 I expect in the next 6-12 months (it's a guesstimate) there will be additional work in GNOME to protect the user session or what I vaguely call the "GUI stack" from reclaim, and thus improve its responsiveness at the expense of the resource hungry process. [1] first two lines; set -j to RAM in GiB +2 GiB; i.e. if you have 8G RAM, use -j 10; more jobs makes the problem happen faster. https://trac.webkit.org/wiki/BuildingGtk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833281 Title: System freeze when memory is put on SWAP in Linux >4.10.x Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I'm reporting this since it's reproduceable the 70% of the time. Summary: In different circumstances, when the systems starts to swap out RAM memory, even small amounts, the system becomes completely unusuable and the screen freezes up, no mouse movement, no TTY access or SSH access can be made, only SYSRQ keys seem to do something (only reboot, so REISUB worked so far though, OOM is useless since the memory/swap is not even full) The I/O Disk led is stuck to 100% in ALL the following cases when this happens. So far: - This happens even when only ZRAM is enabled, and no swap partition is used. - Happens when ZSWAP is used with a swap partition - Happens also when a partition without zram or zswap is used - Maybe it's AMD specific? However, I'm not experiencing this on my laptop using the same tests. My laptop is an Intel one, while my desktop is an AMD Ryzen platform. Here are the specs: CPU: AMD Ryzen 5 1600 no OC GPU: AMD RX 580 8GB SSD: Crucial MX500 500GB MOBO: MSI B350M Grenade RAM: 8GB HyperX Kingston 2667Mhz Ubuntu version: 18.04 LTS, backports repo enabled Kernel version: 4.18.0-18, official ubuntu repo Bios settings: Default Additional info: Maybe I'm not 100% sure, but I noticed when using the 5.0.0-17 generic kernel, the lockups seem to still happen, but they recover eventually. Happened only a few times though... But will always be frozen for at least 30 seconds, differently from my intel laptop where those do occur. The SSD make is the same. I bought two of these, they got also the same amount of RAM. In my laptop those do not occur at all. Swapping memory even huge quantities like 1GB or more, do not produce any issues. Tests made: For testing this behaviour I tried: - Compiling the chromium-browser source code (takes up a lot of system RAM) - Used the "stress" command, using a specific amount of memory to decide how many it will be swapped, and here I noticed that even small quantities like a couple of megabytes will cause the system to freeze the 70% of the times Example: "stres
[Kernel-packages] [Bug 1845797]
This issue persists for me, on a C930 with 5.4.21. Adding `snd_hda_intel.dmic_detect=0` has no effect for me: there is sound, but only from the two front speakers. The rest of the speakers don't work. Here's my alsa info, if it helps: http://alsa- project.org/db/?f=ab906a5a6eeeddc4926a6ad543c2d42d7a21ecdf Let me know if there's a way I can help debug this. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845797 Title: Microphone not detected Lenovo Yoga S940 Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 19.10 as well as 19.04 do not detect the microphone in Lenovo Yoga S940 Attached the screen of gnome sound control panel. Inxi output: System:Host: Kernel: 5.3.0-13-generic x86_64 bits: 64 Desktop: Gnome 3.34.0 Distro: Ubuntu 19.10 (Eoan Ermine) Machine: Type: Laptop System: LENOVO product: 81Q7 v: Lenovo Yoga S940-14IWL serial: Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN serial: UEFI: LENOVO v: AKCN34WW date: 06/12/2019 CPU: Topology: Quad Core model: Intel Core i7-8565U bits: 64 type: MT MCP L2 cache: 8192 KiB Speed: 1161 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 1161 2: 1195 3: 1848 4: 976 5: 1041 6: 1209 7: 1061 8: 2229 Audio: Device-1: Intel Cannon Point-LP High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.3.0-13-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniele2239 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-09-12 (17 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81Q7 Package: pulseaudio 1:13.0-1ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 RelatedPackageVersions: linux-restricted-modules-5.3.0-13-generic N/A linux-backports-modules-5.3.0-13-generic N/A linux-firmware1.182 Tags: eoan Uname: Linux 5.3.0-13-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-09-21 (8 days ago) UserGroups: adm cdrom dip docker lpadmin microk8s plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/12/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AKCN34WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga S940-14IWL dmi.modalias: dmi:bvnLENOVO:bvrAKCN34WW:bd06/12/2019:svnLENOVO:pn81Q7:pvrLenovoYogaS940-14IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS940-14IWL: dmi.product.family: Yoga S940-14IWL dmi.product.name: 81Q7 dmi.product.sku: LENOVO_MT_81Q7_BU_idea_FM_Yoga S940-14IWL dmi.product.version: Lenovo Yoga S940-14IWL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1845797/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833281]
Christoph, your issue is different. Please fill separate bugreport. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833281 Title: System freeze when memory is put on SWAP in Linux >4.10.x Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I'm reporting this since it's reproduceable the 70% of the time. Summary: In different circumstances, when the systems starts to swap out RAM memory, even small amounts, the system becomes completely unusuable and the screen freezes up, no mouse movement, no TTY access or SSH access can be made, only SYSRQ keys seem to do something (only reboot, so REISUB worked so far though, OOM is useless since the memory/swap is not even full) The I/O Disk led is stuck to 100% in ALL the following cases when this happens. So far: - This happens even when only ZRAM is enabled, and no swap partition is used. - Happens when ZSWAP is used with a swap partition - Happens also when a partition without zram or zswap is used - Maybe it's AMD specific? However, I'm not experiencing this on my laptop using the same tests. My laptop is an Intel one, while my desktop is an AMD Ryzen platform. Here are the specs: CPU: AMD Ryzen 5 1600 no OC GPU: AMD RX 580 8GB SSD: Crucial MX500 500GB MOBO: MSI B350M Grenade RAM: 8GB HyperX Kingston 2667Mhz Ubuntu version: 18.04 LTS, backports repo enabled Kernel version: 4.18.0-18, official ubuntu repo Bios settings: Default Additional info: Maybe I'm not 100% sure, but I noticed when using the 5.0.0-17 generic kernel, the lockups seem to still happen, but they recover eventually. Happened only a few times though... But will always be frozen for at least 30 seconds, differently from my intel laptop where those do occur. The SSD make is the same. I bought two of these, they got also the same amount of RAM. In my laptop those do not occur at all. Swapping memory even huge quantities like 1GB or more, do not produce any issues. Tests made: For testing this behaviour I tried: - Compiling the chromium-browser source code (takes up a lot of system RAM) - Used the "stress" command, using a specific amount of memory to decide how many it will be swapped, and here I noticed that even small quantities like a couple of megabytes will cause the system to freeze the 70% of the times Example: "stress --vm 1 --vm-bytes=7G" What should happen: I expect system slowdowns when swapping out memory since I do not have enough RAM, but unlikely when using Windows or my laptop with the same Linux version, not a completely unusuable environment. The swap partition is in both cases on an SSD. Reproduceability: 70% of the times Additional info again: I'm not sure this is due to any hardware failure, my SSD health is fine, as my CPU and RAM. As I said swapping in Windows works fine... --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: haru 2076 F pulseaudio /dev/snd/controlC2: haru 2076 F pulseaudio /dev/snd/controlC0: haru 2076 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME DistroRelease: Ubuntu 18.04 IwConfig: enp24s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-17-generic root=UUID=75d45574-7169-4653-aea3-9f95087f0806 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-17.18~18.04.1-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-17-generic N/A linux-backports-modules-5.0.0-17-generic N/A linux-firmware1.173.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo video WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.K0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR (MS-7A37) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.K0:bd01/22/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A37:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350MMORTAR(MS-7A37):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct4:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.na
[Kernel-packages] [Bug 1239459]
Excellent Blog! I would like to thank for the efforts you have made in writing this post. I am hoping the same best work from you in the future as well. I wanted to thank you for this websites! Thanks for sharing. Great websites! https://preactivator.com/express-vpn-crack/";>Express VPN Activation Code -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1239459 Title: 1814:3290 [Asus X200CA] wifi doesn't connect or disconnects after few seconds Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: With the new 3.11.0-12-generic kernel, wifi has problems to connect with many errors like these: Oct 13 23:50:03 ubuntotto kernel: [ 1186.580726] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:50:03 ubuntotto kernel: [ 1186.740659] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:50:04 ubuntotto kernel: [ 1186.900544] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:50:04 ubuntotto kernel: [ 1187.060571] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:50:04 ubuntotto kernel: [ 1187.096576] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 0 Oct 13 23:50:05 ubuntotto kernel: [ 1188.280106] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:50:05 ubuntotto kernel: [ 1188.440128] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:51:06 ubuntotto kernel: [ 1249.560697] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:51:06 ubuntotto kernel: [ 1249.720644] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:51:07 ubuntotto kernel: [ 1249.880590] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:51:07 ubuntotto kernel: [ 1250.040543] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-12-generic 3.11.0-12.19 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrea 1791 F pulseaudio Date: Sun Oct 13 23:45:04 2013 HibernationDevice: RESUME=UUID=297ef090-5420-41f6-8439-f1254f3e9e15 InstallationDate: Installed on 2013-10-12 (1 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: ASUSTeK COMPUTER INC. X200CA MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=088f2a7d-b78f-4bdd-a184-754b70a3184a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-10-13 (0 days ago) dmi.bios.date: 09/18/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X200CA.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X200CA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX200CA.208:bd09/18/2013:svnASUSTeKCOMPUTERINC.:pnX200CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X200CA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1239459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1239459]
Mar 20 17:50:08 Cerberus NetworkManager[870]: (wlan0): supplicant interface state: authenticating -> associating Mar 20 17:50:08 Cerberus wpa_supplicant[887]: wlan0: Associated with 00:1e:e5:8e:c6:72 Mar 20 17:50:08 Cerberus kernel: [ 2241.170390] wlan0: RX AssocResp from 00:1e:e5:8e:c6:72 (capab=0x431 status=0 aid=6) Mar 20 17:50:08 Cerberus kernel: [ 2241.170673] wlan0: associated Mar 20 17:50:08 Cerberus NetworkManager[870]: (wlan0): supplicant interface state: associating -> associated Mar 20 17:50:10 Cerberus NetworkManager[870]: (wlan0): supplicant interface state: associated -> 4-way handshake Mar 20 17:50:10 Cerberus wpa_supplicant[887]: wlan0: WPA: Key negotiation completed with 00:1e:e5:8e:c6:72 [PTK=CCMP GTK=CCMP] Mar 20 17:50:10 Cerberus wpa_supplicant[887]: wlan0: CTRL-EVENT-CONNECTED - Connection to 00:1e:e5:8e:c6:72 completed (reauth) [id=0 id_str=] Mar 20 17:50:10 Cerberus NetworkManager[870]: (wlan0): supplicant interface state: 4-way handshake -> completed Mar 20 17:50:12 Cerberus whoopsie[1104]: online Mar 20 17:50:13 Cerberus whoopsie[1104]: online Mar 20 17:50:20 Cerberus kernel: [ 2254.047434] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Mar 20 17:50:21 Cerberus kernel: [ 2254.207399] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Mar 20 17:50:52 Cerberus kernel: [ 2285.074635] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Mar 20 17:50:54 Cerberus kernel: [ 2287.074559] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Mar 20 17:50:54 Cerberus kernel: [ 2287.234576] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush My card is a RT2790: lshw -c Network *-network Beschreibung: Kabellose Verbindung Produkt: RT2790 Wireless 802.11n 1T/2R PCIe Hersteller: Ralink corp. Physische ID: 0 Bus-Informationen: pci@:03:00.0 Logischer Name: wlan0 Version: 00 Seriennummer: xx:xx:xx:xx:xx:xx Breite: 32 bits Takt: 33MHz Fähigkeiten: pm msi pciexpress bus_master cap_list ethernet physical wireless Konfiguration: broadcast=yes driver=rt2800pci driverversion=3.11.0-18-generic firmware=0.34 ip=192.168.1.210 latency=0 link=yes multicast=yes wireless=IEEE 802.11bgn Ressourcen: irq:17 memory:f650-f650 https://hdlicense.com/on1-photo-raw-crack/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1239459 Title: 1814:3290 [Asus X200CA] wifi doesn't connect or disconnects after few seconds Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: With the new 3.11.0-12-generic kernel, wifi has problems to connect with many errors like these: Oct 13 23:50:03 ubuntotto kernel: [ 1186.580726] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:50:03 ubuntotto kernel: [ 1186.740659] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:50:04 ubuntotto kernel: [ 1186.900544] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:50:04 ubuntotto kernel: [ 1187.060571] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:50:04 ubuntotto kernel: [ 1187.096576] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 0 Oct 13 23:50:05 ubuntotto kernel: [ 1188.280106] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:50:05 ubuntotto kernel: [ 1188.440128] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:51:06 ubuntotto kernel: [ 1249.560697] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:51:06 ubuntotto kernel: [ 1249.720644] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:51:07 ubuntotto kernel: [ 1249.880590] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:51:07 ubuntotto kernel: [ 1250.040543] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-12-generic 3.11.0-12.19 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrea 1791 F pulseaudio Date: Sun Oct 13 23:45:04 2013 HibernationDevice: RESUME=UUID=297ef090-5420-41f6-8439-f1254f3e9e15 InstallationDate: Installed on 2013-10-12 (1 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: ASUSTeK COMPUTER INC. X200CA MarkForUpload: Tr
[Kernel-packages] [Bug 1239459]
Thank you because you have been willing to share information with us. we will always appreciate all you have done here because I know you are very concerned with our. https://haxsoft.com/driverdoc-crack-full-keys/";>Driver Doc Crack 2020 Free Download -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1239459 Title: 1814:3290 [Asus X200CA] wifi doesn't connect or disconnects after few seconds Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: With the new 3.11.0-12-generic kernel, wifi has problems to connect with many errors like these: Oct 13 23:50:03 ubuntotto kernel: [ 1186.580726] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:50:03 ubuntotto kernel: [ 1186.740659] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:50:04 ubuntotto kernel: [ 1186.900544] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:50:04 ubuntotto kernel: [ 1187.060571] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:50:04 ubuntotto kernel: [ 1187.096576] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 0 Oct 13 23:50:05 ubuntotto kernel: [ 1188.280106] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:50:05 ubuntotto kernel: [ 1188.440128] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:51:06 ubuntotto kernel: [ 1249.560697] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:51:06 ubuntotto kernel: [ 1249.720644] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:51:07 ubuntotto kernel: [ 1249.880590] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:51:07 ubuntotto kernel: [ 1250.040543] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-12-generic 3.11.0-12.19 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrea 1791 F pulseaudio Date: Sun Oct 13 23:45:04 2013 HibernationDevice: RESUME=UUID=297ef090-5420-41f6-8439-f1254f3e9e15 InstallationDate: Installed on 2013-10-12 (1 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: ASUSTeK COMPUTER INC. X200CA MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=088f2a7d-b78f-4bdd-a184-754b70a3184a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-10-13 (0 days ago) dmi.bios.date: 09/18/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X200CA.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X200CA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX200CA.208:bd09/18/2013:svnASUSTeKCOMPUTERINC.:pnX200CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X200CA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1239459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1239459]
It seems that the rt3290 wireless chipset acts very flaky under 3.11.1, my last kernel before this one was 3.10.3 and it didn't have this problem. I'm currently compiling 3.10.10 to see if it works again there as reported in the arch linux forums. Revelant forum topic where I found other users with the problem: https://digitejarat.trade/waste-engine-oil-recycling-plant-in-iran/ By flaky I mean that after a while it just refuses to connect, this is some dmesg output: [4.949297] wlp1s0f0: authenticate with 5c:7d:5e:de:b6:04 [4.961762] wlp1s0f0: send auth to 5c:7d:5e:de:b6:04 (try 1/3) [4.963279] wlp1s0f0: authenticated [4.964933] wlp1s0f0: associate with 5c:7d:5e:de:b6:04 (try 1/3) [4.970465] wlp1s0f0: RX AssocResp from 5c:7d:5e:de:b6:04 (capab=0x431 status=0 aid=1) [4.970563] wlp1s0f0: associated [ 28.285869] fuse init (API version 7.22) [ 29.967936] EXT4-fs (sda3): re-mounted. Opts: data=ordered,commit=0 [ 29.983555] EXT4-fs (sda1): re-mounted. Opts: data=ordered,commit=0 [ 30.020684] EXT4-fs (sda4): re-mounted. Opts: data=ordered,commit=0 [ 31.468349] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 32.031587] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 32.058518] cfg80211: Calling CRDA for country: GB [ 32.264907] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 32.398225] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 33.482380] wlp1s0f0: authenticate with 5c:7d:5e:de:b6:04 [ 33.621406] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 33.628168] wlp1s0f0: send auth to 5c:7d:5e:de:b6:04 (try 1/3) [ 34.324623] wlp1s0f0: send auth to 5c:7d:5e:de:b6:04 (try 2/3) [ 35.324464] wlp1s0f0: send auth to 5c:7d:5e:de:b6:04 (try 3/3) [ 36.334424] wlp1s0f0: authentication with 5c:7d:5e:de:b6:04 timed out [ 36.504382] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 37.137655] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush [ 37.270932] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1239459 Title: 1814:3290 [Asus X200CA] wifi doesn't connect or disconnects after few seconds Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: With the new 3.11.0-12-generic kernel, wifi has problems to connect with many errors like these: Oct 13 23:50:03 ubuntotto kernel: [ 1186.580726] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:50:03 ubuntotto kernel: [ 1186.740659] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:50:04 ubuntotto kernel: [ 1186.900544] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:50:04 ubuntotto kernel: [ 1187.060571] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:50:04 ubuntotto kernel: [ 1187.096576] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 0 Oct 13 23:50:05 ubuntotto kernel: [ 1188.280106] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:50:05 ubuntotto kernel: [ 1188.440128] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:51:06 ubuntotto kernel: [ 1249.560697] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:51:06 ubuntotto kernel: [ 1249.720644] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:51:07 ubuntotto kernel: [ 1249.880590] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:51:07 ubuntotto kernel: [ 1250.040543] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-12-generic 3.11.0-12.19 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrea 1791 F pulseaudio Date: Sun Oct 13 23:45:04 2013 HibernationDevice: RESUME=UUID=297ef090-5420-41f6-8439-f1254f3e9e15 InstallationDate: Installed on 2013-10-12 (1 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: ASUSTeK COMPUTER INC. X200CA MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=088f2a7d-b78f-4bdd-a184-754b70a3184a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-
[Kernel-packages] [Bug 1239459]
Many times users face My Yahoo Email Was Hacked and want to get the proper solution of Yahoo Mail Forget Password then they are at the right place. Yahoo Account Recovery Wizard is a very and quick way by which users can get Yahoo Account Recovery in few seconds with the help of Yahoo Account Recovery Tool. https://mail-customer-support.com/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1239459 Title: 1814:3290 [Asus X200CA] wifi doesn't connect or disconnects after few seconds Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: With the new 3.11.0-12-generic kernel, wifi has problems to connect with many errors like these: Oct 13 23:50:03 ubuntotto kernel: [ 1186.580726] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:50:03 ubuntotto kernel: [ 1186.740659] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:50:04 ubuntotto kernel: [ 1186.900544] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:50:04 ubuntotto kernel: [ 1187.060571] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:50:04 ubuntotto kernel: [ 1187.096576] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 0 Oct 13 23:50:05 ubuntotto kernel: [ 1188.280106] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:50:05 ubuntotto kernel: [ 1188.440128] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:51:06 ubuntotto kernel: [ 1249.560697] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:51:06 ubuntotto kernel: [ 1249.720644] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:51:07 ubuntotto kernel: [ 1249.880590] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:51:07 ubuntotto kernel: [ 1250.040543] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-12-generic 3.11.0-12.19 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrea 1791 F pulseaudio Date: Sun Oct 13 23:45:04 2013 HibernationDevice: RESUME=UUID=297ef090-5420-41f6-8439-f1254f3e9e15 InstallationDate: Installed on 2013-10-12 (1 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: ASUSTeK COMPUTER INC. X200CA MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=088f2a7d-b78f-4bdd-a184-754b70a3184a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-10-13 (0 days ago) dmi.bios.date: 09/18/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X200CA.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X200CA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX200CA.208:bd09/18/2013:svnASUSTeKCOMPUTERINC.:pnX200CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X200CA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1239459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1239459]
The word schizophrenia is taken from the Greek word schism meaning split and Freni meaning Minds indicating that, Schizophrenia is a type of brain disorder in which a persona got effected on how he acts or thinks the world around him. Read more about it here schizophrenia symptoms https://www.medicallyinfo.com/mental-disease/schizophrenia-types-symptoms/";>schizophrenia symptoms -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1239459 Title: 1814:3290 [Asus X200CA] wifi doesn't connect or disconnects after few seconds Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: With the new 3.11.0-12-generic kernel, wifi has problems to connect with many errors like these: Oct 13 23:50:03 ubuntotto kernel: [ 1186.580726] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:50:03 ubuntotto kernel: [ 1186.740659] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:50:04 ubuntotto kernel: [ 1186.900544] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:50:04 ubuntotto kernel: [ 1187.060571] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:50:04 ubuntotto kernel: [ 1187.096576] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 0 Oct 13 23:50:05 ubuntotto kernel: [ 1188.280106] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:50:05 ubuntotto kernel: [ 1188.440128] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:51:06 ubuntotto kernel: [ 1249.560697] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:51:06 ubuntotto kernel: [ 1249.720644] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:51:07 ubuntotto kernel: [ 1249.880590] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:51:07 ubuntotto kernel: [ 1250.040543] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-12-generic 3.11.0-12.19 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrea 1791 F pulseaudio Date: Sun Oct 13 23:45:04 2013 HibernationDevice: RESUME=UUID=297ef090-5420-41f6-8439-f1254f3e9e15 InstallationDate: Installed on 2013-10-12 (1 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: ASUSTeK COMPUTER INC. X200CA MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=088f2a7d-b78f-4bdd-a184-754b70a3184a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-10-13 (0 days ago) dmi.bios.date: 09/18/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X200CA.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X200CA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX200CA.208:bd09/18/2013:svnASUSTeKCOMPUTERINC.:pnX200CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X200CA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1239459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868113] Comment bridged from LTC Bugzilla
--- Comment From danijel.so...@de.ibm.com 2020-03-30 08:43 EDT--- Hi, I think this suggestion is fine, let us do it as the first step. We may discuss later on what our options are in regards of enabling architecture-specific tunings in distros. Cheers, Danijel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868113 Title: [Ubuntu 20.04] Striding RQ as Default for ConnectX-4 Status in Release Notes for Ubuntu: Confirmed Status in Ubuntu on IBM z Systems: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: ello, Within our Network Performance runs in the RoCE Express 2(.1) area, we noticed a performance regression with streaming workloads which could be mitigated by using an ethtool setting. The Commit which switched the default value from "Striding RQ" to "Legacy RQ" for ConnectX-4 devices (RoCE Express 2(.1)) is attached here: commit 5ffd81943d7a57423f204cd5844bf430b5634472 (refs/bisect/bad) Author: Tariq Toukan Date: Tue Feb 20 15:17:54 2018 +0200 net/mlx5e: RX, Always prefer Linear SKB configuration Prefer the linear SKB configuration of Legacy RQ over the non-linear one of Striding RQ. This implies that ConnectX-4 LX now uses legacy RQ by default, as it does not support the linear configuration of Striding RQ. Signed-off-by: Tariq Toukan Signed-off-by: Saeed Mahameed diff --git a/drivers/net/ethernet/mellanox/mlx5/core/en_main.c b/drivers/net/ethernet/mellanox/mlx5/core/en_main.c index 2c634e50d051..333d4ed52b94 100644 --- a/drivers/net/ethernet/mellanox/mlx5/core/en_main.c +++ b/drivers/net/ethernet/mellanox/mlx5/core/en_main.c @@ -4405,9 +4405,16 @@ void mlx5e_build_nic_params(struct mlx5_core_dev *mdev, MLX5E_SET_PFLAG(params, MLX5E_PFLAG_RX_CQE_COMPRESS, params->rx_cqe_compress_def); /* RQ */ - if (mlx5e_striding_rq_possible(mdev, params)) - MLX5E_SET_PFLAG(params, MLX5E_PFLAG_RX_STRIDING_RQ, - !slow_pci_heuristic(mdev)); + /* Prefer Striding RQ, unless any of the following holds: +* - Striding RQ configuration is not possible/supported. +* - Slow PCI heuristic. +* - Legacy RQ would use linear SKB while Striding RQ would use non-linear. +*/ + if (!slow_pci_heuristic(mdev) && + mlx5e_striding_rq_possible(mdev, params) && + (mlx5e_rx_mpwqe_is_linear_skb(mdev, params) || +!mlx5e_rx_is_linear_skb(mdev, params))) + MLX5E_SET_PFLAG(params, MLX5E_PFLAG_RX_STRIDING_RQ, true); mlx5e_set_rq_type(mdev, params); mlx5e_init_rq_type_params(mdev, params); We have modified the upstream-kernel to allow us running of measurements and compare differences between Legacy RQ vs Striding RQ. Here is an example below: Kernel used: 5.4.0-rc7 The measurements run on a dedicated machine (z14) using uperf with streaming profiles (MTU size 1500). Example throughput drop: (traffic via a shared card, i.e. client and server using VFs from the same ConnectX-4) -- | |Legacy RQ| Striding RQ | -- |str-writex30k (1 connection) |24.62Gb/s| 33.47Gb/s| -- Additionaly, two tests with transactional workload using the ethtool proposed switch: -- | |Legacy RQ| Striding RQ | -- | rr1c-200x30k---1 | 4.12Gb/s|5.66Gb/s| -- | rr1c-200x30k--10 |15.10Gb/s| 20.77Gb/s| -- As concluded in the communication with Mellanox, there is a possibility to use a simple ethtool command to switch between the queuing methods, allowing us to avoid kernel code changes: ethtool --set-priv-flags DEVNAME rx_striding_rq on (To list the available settings you may use: ethtool --show-priv-flags DEVNAME) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1868113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1865130] Re: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!
On Sun, Mar 29, 2020 at 06:35:08AM -, knossos456 wrote: > Question to maintainer : > 1.173.17 proposed (main) > When will this release go to real updates, 7 days are gone. We generally don't release SRU updates over weekends (including Friday), so it will probably get released today. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1865130 Title: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Eoan: Fix Committed Bug description: === SRU Justification === [Impact] Firmware update of radeon/oland_rlc.bin breaks some radeon cards. [Fix] Revert the new firmware. [Regression Potential] Low. The old firmware has been used for a long time. === Original Bug Report === when trying > DRI_PRIME=1 glxgears , the result in dmesg is as following [ +0.91] radeon :01:00.0: WB enabled [ +0.02] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x8c00 and cpu addr 0x8ac2d26f [ +0.01] radeon :01:00.0: fence driver on ring 1 use gpu addr 0x8c04 and cpu addr 0xa848de20 [ +0.01] radeon :01:00.0: fence driver on ring 2 use gpu addr 0x8c08 and cpu addr 0x1e4494a9 [ +0.01] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x8c0c and cpu addr 0x98a9748e [ +0.01] radeon :01:00.0: fence driver on ring 4 use gpu addr 0x8c10 and cpu addr 0xb6ff734d [ +0.000212] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0x6b4da526 [ +0.100566] radeon :01:00.0: failed VCE resume (-110). [ +0.179115] [drm] ring test on 0 succeeded in 1 usecs [ +0.04] [drm] ring test on 1 succeeded in 1 usecs [ +0.04] [drm] ring test on 2 succeeded in 1 usecs [ +0.06] [drm] ring test on 3 succeeded in 3 usecs [ +0.04] [drm] ring test on 4 succeeded in 3 usecs [ +1.171892] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015643] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015509] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015572] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015514] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015405] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015442] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015416] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015388] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015379] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +0.019924] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, giving up!!! [ +0.40] radeon :01:00.0: failed initializing UVD (-1). [ +0.60] [drm] ib test on ring 0 succeeded in 0 usecs [ +0.51] [drm] ib test on ring 1 succeeded in 0 usecs [ +0.32] [drm] ib test on ring 2 succeeded in 0 usecs [ +0.52] [drm] ib test on ring 3 succeeded in 0 usecs [ +0.29] [drm] ib test on ring 4 succeeded in 0 usecs Also it affects the boot time. the used OpenGL renderer is: "OpenGL renderer string: AMD OLAND (DRM 2.50.0, 5.3.0-40-generic, LLVM 9.0.0)" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Feb 28 11:50:50 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.3.0-28-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.3.0-40-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3801] Subsystem: Lenovo Mars [Radeon HD 8670A/86
[Kernel-packages] [Bug 1808389] Re: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6
While using 5.3.0-42-generic, problem remains on my 8265. ** Attachment added: "dmesg -T | grep wifi" https://bugs.launchpad.net/ubuntu/+bug/1808389/+attachment/5343335/+files/iwlwifi.dmesg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1808389 Title: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6 Status in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in The Bionic Beaver: Confirmed Status in linux-firmware source package in Bionic: Fix Released Status in The Cosmic Cuttlefish: Confirmed Status in linux-firmware source package in Cosmic: Fix Released Bug description: SRU Justification: === [Impact] repeated crashes of the Intel 8265 wireless card on a Lenovo X1 Gen6. [Fix] New iwlwifi firmware fix it. [Test] Bug reporter verified with positive result. [Regression Potential] Upstream fix, low risk. Bug reporter confirms fix. Original bug report: = Seeing repeated crashes of the Intel 8265 wireless card on a Lenovo X1 Gen6. Firmware: 36.7596afd4.0 Dec 13 11:53:36 james-x1 kernel: [ 856.840159] wlp2s0: send auth to 60:38:e0:70:a2:11 (try 1/3) Dec 13 11:53:36 james-x1 kernel: [ 856.844875] iwlwifi :02:00.0: Microcode SW error detected. Restarting 0x200. Dec 13 11:53:36 james-x1 kernel: [ 856.845015] iwlwifi :02:00.0: Start IWL Error Log Dump: Dec 13 11:53:36 james-x1 kernel: [ 856.845018] iwlwifi :02:00.0: Status: 0x0100, count: 6 Dec 13 11:53:36 james-x1 kernel: [ 856.845021] iwlwifi :02:00.0: Loaded firmware version: 36.7596afd4.0 Dec 13 11:53:36 james-x1 kernel: [ 856.845024] iwlwifi :02:00.0: 0x1006 | ADVANCED_SYSASSERT Dec 13 11:53:36 james-x1 kernel: [ 856.845026] iwlwifi :02:00.0: 0x02F0 | trm_hw_status0 Dec 13 11:53:36 james-x1 kernel: [ 856.845029] iwlwifi :02:00.0: 0x | trm_hw_status1 Dec 13 11:53:36 james-x1 kernel: [ 856.845031] iwlwifi :02:00.0: 0x000248DC | branchlink2 Dec 13 11:53:36 james-x1 kernel: [ 856.845034] iwlwifi :02:00.0: 0x0003A7DA | interruptlink1 Dec 13 11:53:36 james-x1 kernel: [ 856.845036] iwlwifi :02:00.0: 0x | interruptlink2 Dec 13 11:53:36 james-x1 kernel: [ 856.845039] iwlwifi :02:00.0: 0xFEDA | data1 Dec 13 11:53:36 james-x1 kernel: [ 856.845041] iwlwifi :02:00.0: 0xDEADBEEF | data2 Dec 13 11:53:36 james-x1 kernel: [ 856.845044] iwlwifi :02:00.0: 0xDEADBEEF | data3 Dec 13 11:53:36 james-x1 kernel: [ 856.845046] iwlwifi :02:00.0: 0x0007E1DC | beacon time Dec 13 11:53:36 james-x1 kernel: [ 856.845048] iwlwifi :02:00.0: 0x003B0850 | tsf low Dec 13 11:53:36 james-x1 kernel: [ 856.845051] iwlwifi :02:00.0: 0x | tsf hi Dec 13 11:53:36 james-x1 kernel: [ 856.845053] iwlwifi :02:00.0: 0x | time gp1 Dec 13 11:53:36 james-x1 kernel: [ 856.845055] iwlwifi :02:00.0: 0x003B0852 | time gp2 Dec 13 11:53:36 james-x1 kernel: [ 856.845058] iwlwifi :02:00.0: 0x0001 | uCode revision type Dec 13 11:53:36 james-x1 kernel: [ 856.845060] iwlwifi :02:00.0: 0x0024 | uCode version major Dec 13 11:53:36 james-x1 kernel: [ 856.845063] iwlwifi :02:00.0: 0x7596AFD4 | uCode version minor Dec 13 11:53:36 james-x1 kernel: [ 856.845065] iwlwifi :02:00.0: 0x0230 | hw version Dec 13 11:53:36 james-x1 kernel: [ 856.845068] iwlwifi :02:00.0: 0x18489000 | board version Dec 13 11:53:36 james-x1 kernel: [ 856.845070] iwlwifi :02:00.0: 0x0501001C | hcmd Dec 13 11:53:36 james-x1 kernel: [ 856.845072] iwlwifi :02:00.0: 0x00023008 | isr0 Dec 13 11:53:36 james-x1 kernel: [ 856.845075] iwlwifi :02:00.0: 0x000D | isr1 Dec 13 11:53:36 james-x1 kernel: [ 856.845077] iwlwifi :02:00.0: 0x08001802 | isr2 Dec 13 11:53:36 james-x1 kernel: [ 856.845080] iwlwifi :02:00.0: 0x0041FDC0 | isr3 Dec 13 11:53:36 james-x1 kernel: [ 856.845082] iwlwifi :02:00.0: 0x | isr4 Dec 13 11:53:36 james-x1 kernel: [ 856.845084] iwlwifi :02:00.0: 0x00580118 | last cmd Id Dec 13 11:53:36 james-x1 kernel: [ 856.845087] iwlwifi :02:00.0: 0x | wait_event Dec 13 11:53:36 james-x1 kernel: [ 856.845089] iwlwifi :02:00.0: 0x76DD | l2p_control Dec 13 11:53:36 james-x1 kernel: [ 856.845091] iwlwifi :02:00.0: 0x0020 | l2p_duration Dec 13 11:53:36 james-x1 kernel: [ 856.845094] iwlwifi :02:00.0: 0x | l2p_mhvalid Dec 13 11:53:36 james-x1 kernel: [ 856.845096] iwlwifi :02:00.0: 0x00A0 | l2p_addr_match Dec 13 11:53:36 james-x1 kernel: [ 856.845099] iwlwifi :02:00.0: 0x000D | lmpm_pmg_sel Dec 13 11:53:36 james-x1 kernel: [ 856.845101] iwlwifi :02:00.0: 0x22040707 | timestamp Dec 13 11:53:36 james-x1 kernel: [
[Kernel-packages] [Bug 1865130] Re: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!
Also no one has verified the -proposed package on eoan yet. Is anyone affected running eoan and able to verify the fix there? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1865130 Title: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Eoan: Fix Committed Bug description: === SRU Justification === [Impact] Firmware update of radeon/oland_rlc.bin breaks some radeon cards. [Fix] Revert the new firmware. [Regression Potential] Low. The old firmware has been used for a long time. === Original Bug Report === when trying > DRI_PRIME=1 glxgears , the result in dmesg is as following [ +0.91] radeon :01:00.0: WB enabled [ +0.02] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x8c00 and cpu addr 0x8ac2d26f [ +0.01] radeon :01:00.0: fence driver on ring 1 use gpu addr 0x8c04 and cpu addr 0xa848de20 [ +0.01] radeon :01:00.0: fence driver on ring 2 use gpu addr 0x8c08 and cpu addr 0x1e4494a9 [ +0.01] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x8c0c and cpu addr 0x98a9748e [ +0.01] radeon :01:00.0: fence driver on ring 4 use gpu addr 0x8c10 and cpu addr 0xb6ff734d [ +0.000212] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0x6b4da526 [ +0.100566] radeon :01:00.0: failed VCE resume (-110). [ +0.179115] [drm] ring test on 0 succeeded in 1 usecs [ +0.04] [drm] ring test on 1 succeeded in 1 usecs [ +0.04] [drm] ring test on 2 succeeded in 1 usecs [ +0.06] [drm] ring test on 3 succeeded in 3 usecs [ +0.04] [drm] ring test on 4 succeeded in 3 usecs [ +1.171892] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015643] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015509] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015572] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015514] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015405] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015442] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015416] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015388] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015379] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +0.019924] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, giving up!!! [ +0.40] radeon :01:00.0: failed initializing UVD (-1). [ +0.60] [drm] ib test on ring 0 succeeded in 0 usecs [ +0.51] [drm] ib test on ring 1 succeeded in 0 usecs [ +0.32] [drm] ib test on ring 2 succeeded in 0 usecs [ +0.52] [drm] ib test on ring 3 succeeded in 0 usecs [ +0.29] [drm] ib test on ring 4 succeeded in 0 usecs Also it affects the boot time. the used OpenGL renderer is: "OpenGL renderer string: AMD OLAND (DRM 2.50.0, 5.3.0-40-generic, LLVM 9.0.0)" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Feb 28 11:50:50 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.3.0-28-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.3.0-40-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3801] Subsystem: Lenovo Mars [Radeon HD 8670A/8670M/8750M] [17aa:3801] InstallationDate: Installed on 2019-09-17 (163 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Ma
[Kernel-packages] [Bug 1247712] Re: Unable to install Broadcom STA wireless driver on Precise 3.8 / 3.11 / 3.13 kernel via jockey-gtk
** Also affects: jockey (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: bcmwl (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: linux-lts-trusty (Ubuntu Saucy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1247712 Title: Unable to install Broadcom STA wireless driver on Precise 3.8 / 3.11 / 3.13 kernel via jockey-gtk Status in Jockey: Invalid Status in bcmwl package in Ubuntu: Invalid Status in jockey package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: In Progress Status in bcmwl source package in Precise: Invalid Status in jockey source package in Precise: Won't Fix Status in linux-lts-trusty source package in Precise: In Progress Status in bcmwl source package in Saucy: New Status in jockey source package in Saucy: New Status in linux-lts-trusty source package in Saucy: New Status in bcmwl source package in Trusty: Invalid Status in jockey source package in Trusty: In Progress Status in linux-lts-trusty source package in Trusty: In Progress Status in bcmwl package in Baltix: Invalid Bug description: SRU request: Please accept jockey_0.9.7-0ubuntu7.15 into precise-proposed. [Impact] Kernel versions higher than 3.8 fail to rebind the Broadcom device to the driver thus compromising system stability. While rebinding is a nice feature it can't come at the cost of system stability. For this reason we'll disable this feature when dealing with Linux >= 3.8 and preserve it in the other cases. [Test Case] Install and reboot into Linux 3.8 or higher (linux-lts-saucy or linux- lts-trusty), then use Jockey to install the broadcom wireless driver. Jockey will hang and the system will probably hang on shutdown. [Regression Potential] It should be minimal i.e. there won't be device rebinding on the livecd. This, however, shouldn't be an issue since the open broadcom driver should already work out of the box. Furthermore the test suite now covers this test case. == Description == CID: 201303-13027 Dell Inspiron 5535 CID: 201012-6925 Dell Latitude E6320 CID: 201208-11536 Dell Latitude 6430u Affected chipsets: Broadcom 4365 Broadcom 4313 [14e4:4727] (rev 01) Broadcom 43132 The bcmwl (6.20.155.1+bdcom-0ubuntu0.0.2) cannot be installed on 12.04.4 (3.11.0-15), 12.04.3 (3.8.0-29) Steps: 1. Install Ubuntu 12.04.3 (or 12.04.4) + update 2. Boot to desktop 3. Install the Broadcom STA wireless driver via jockey-gtk Driver cannot be installed, jockey-gtk will stuck at "Downloading and installing driver" The last message from jockey.jog is: unbind/rebind on driver /sys/module/wl/drivers/pci:wl: device :02:00.0 Error message could be found in dmesg: Nov 3 21:34:14 201012-6925 kernel: [ 528.104653] wlc_lcnphy_rx_gain_tbl_free_entry = 5 Nov 3 21:34:14 201012-6925 kernel: [ 528.104863] BUG: unable to handle kernel paging request at a045d020 Nov 3 21:34:14 201012-6925 kernel: [ 528.104906] IP: [] 0xa045d01f Nov 3 21:34:14 201012-6925 kernel: [ 528.104936] PGD 1c0f067 PUD 1c13063 PMD 2ea40067 PTE 0 Nov 3 21:34:14 201012-6925 kernel: [ 528.104967] Oops: 0010 [#1] SMP Nov 3 21:34:14 201012-6925 kernel: [ 528.104988] Modules linked in: lib80211_crypt_tkip(F) wl(POF) lib80211(F) rfcomm(F) bnep(F) bluetooth(F) snd_hda_codec_hdmi(F) snd_hda_codec_idt(F) coretemp(F) kvm_intel(F) arc4(F) kvm(F) joydev(F) ghash_clmulni_intel(F) aesni_intel(F) ablk_helper(F) cryptd(F) lrw(F) mac80211(F) snd_hda_intel(F) brcmutil(F) snd_hda_codec(F) snd_hwdep(F) snd_pcm(F) i915(F) snd_seq_midi(F) snd_rawmidi(F) snd_seq_midi_event(F) snd_seq(F) aes_x86_64(F) snd_timer(F) snd_seq_device(F) cfg80211(F) snd(F) cordic(F) drm_kms_helper(F) drm(F) mei(F) psmouse(F) soundcore(F) xts(F) ppdev(F) gf128mul(F) parport_pc(F) i2c_algo_bit(F) dell_laptop(F) dcdbas(F) dell_wmi(F) video(F) lpc_ich(F) serio_raw(F) mac_hid(F) sparse_keymap(F) snd_page_alloc(F) wmi(F) microcode(F) lp(F) parport(F) ahci(F) libahci(F) sdhci_pci(F) sdhci(F) e1000e(F) [last unloaded: bcma] Nov 3 21:34:14 201012-6925 kernel: [ 528.105424] CPU 0 Nov 3 21:34:14 201012-6925 kernel: [ 528.105438] Pid: 2695, comm: jockey-backend Tainted: PF O 3.8.0-33-generic #48~precise1-Ubuntu Dell Inc. Latitude E6320/ Nov 3 21:34:14 201012-6925 kernel: [ 528.105493] RIP: 0010:[] [] 0xa045d01f Nov 3 21:34:14 201012-6925 kernel: [ 528.105533] RSP: 0018:88001b405d50 EFLAGS: 00010282 Nov 3 21:34:14 201012-6925 kernel: [ 528.105558] RAX: 0001 RBX: 880031788000 RCX: Nov 3 21:34:14 201012-6925 kernel: [ 528.105590] RDX: RSI: a0861ec0 RDI: 880031788000 Nov 3 21:34:14 201012-6925 kernel: [ 528.105623] RBP: 880
[Kernel-packages] [Bug 1864073] Re: seccomp_bpf fails Eoan 5.3 in ubuntu_kernel_selftests
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-aws (Ubuntu)
Status: New => Confirmed
--
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/1864073
Title:
seccomp_bpf fails Eoan 5.3 in ubuntu_kernel_selftests
Status in ubuntu-kernel-tests:
Triaged
Status in linux-aws package in Ubuntu:
Confirmed
Status in linux-aws source package in Eoan:
Confirmed
Bug description:
Cloud: AWS
Kernel: 5.3.0-1012.13
Test: ubuntu_kernel_selftests
The following is observed from the autotest failure.
02/19 21:33:08 DEBUG| utils:0153| [stdout] Estimated seccomp overhead per
syscall: 42 ns
02/19 21:33:08 DEBUG| utils:0153| [stdout] ok 1..2 selftests: seccomp:
seccomp_benchmark [PASS]
02/19 21:33:08 DEBUG| utils:0153| [stdout] make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/seccomp'
02/19 21:33:08 DEBUG| utils:0153| [stdout] make: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
02/19 21:33:08 INFO |ubuntu_ker:0179| == Summary ===
02/19 21:33:08 INFO |ubuntu_ker:0056| Sub test case: seccomp_bpf failed.
02/19 21:33:08 ERROR| test:0414| Exception escaping from test:
Traceback (most recent call last):
File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
_call_test_function(self.execute, *p_args, **p_dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 823, in
_call_test_function
return func(*args, **dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
postprocess_profiled_run, args, dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 212, in
_call_run_once
self.run_once(*args, **dargs)
File
"/home/ubuntu/autotest/client/tests/ubuntu_kernel_selftests/ubuntu_kernel_selftests.py",
line 188, in run_once
raise error.TestError('Test failed for ' + test_name)
TestError: Test failed for seccomp
When the test is run standalone we can get a little more information.
[==] Running 75 tests from 1 test cases.
[ RUN ] global.mode_strict_support
[ OK ] global.mode_strict_support
[ RUN ] global.mode_strict_cannot_call_prctl
[ OK ] global.mode_strict_cannot_call_prctl
[ RUN ] global.no_new_privs_support
[ OK ] global.no_new_privs_support
[ RUN ] global.mode_filter_support
[ OK ] global.mode_filter_support
[ RUN ] global.mode_filter_without_nnp
[ OK ] global.mode_filter_without_nnp
[ RUN ] global.filter_size_limits
[ OK ] global.filter_size_limits
[ RUN ] global.filter_chain_limits
[ OK ] global.filter_chain_limits
[ RUN ] global.mode_filter_cannot_move_to_strict
[ OK ] global.mode_filter_cannot_move_to_strict
[ RUN ] global.mode_filter_get_seccomp
[ OK ] global.mode_filter_get_seccomp
[ RUN ] global.ALLOW_all
[ OK ] global.ALLOW_all
[ RUN ] global.empty_prog
[ OK ] global.empty_prog
[ RUN ] global.log_all
[ OK ] global.log_all
[ RUN ] global.unknown_ret_is_kill_inside
[ OK ] global.unknown_ret_is_kill_inside
[ RUN ] global.unknown_ret_is_kill_above_allow
[ OK ] global.unknown_ret_is_kill_above_allow
[ RUN ] global.KILL_all
[ OK ] global.KILL_all
[ RUN ] global.KILL_one
[ OK ] global.KILL_one
[ RUN ] global.KILL_one_arg_one
[ OK ] global.KILL_one_arg_one
[ RUN ] global.KILL_one_arg_six
[ OK ] global.KILL_one_arg_six
[ RUN ] global.KILL_thread
[ OK ] global.KILL_thread
[ RUN ] global.KILL_process
[ OK ] global.KILL_process
[ RUN ] global.arg_out_of_range
[ OK ] global.arg_out_of_range
[ RUN ] global.ERRNO_valid
[ OK ] global.ERRNO_valid
[ RUN ] global.ERRNO_zero
[ OK ] global.ERRNO_zero
[ RUN ] global.ERRNO_capped
[ OK ] global.ERRNO_capped
[ RUN ] global.ERRNO_order
[ OK ] global.ERRNO_order
[ RUN ] TRAP.dfl
[ OK ] TRAP.dfl
[ RUN ] TRAP.ign
[ OK ] TRAP.ign
[ RUN ] TRAP.handler
[ OK ] TRAP.handler
[ RUN ] precedence.allow_ok
[ OK ] precedence.allow_ok
[ RUN ] precedence.kill_is_highest
[ OK ] precedence.kill_is_highest
[ RUN ] precedence.kill_is_highest_in_any_order
[ OK ] precedence.kill_is_highest_in_any_order
[ RUN ] precedence.trap_is_second
[ OK ] precedence.trap_is_second
[ RUN ] precedence.trap_is_second_in_any_order
[ OK ] precedence.trap_is_second_in_any_order
[ RUN ] precedence.errno_is_third
[ OK ] precedence.errno_is_third
[ RUN ]
[Kernel-packages] [Bug 1864073] Re: seccomp_bpf fails Eoan 5.3 in ubuntu_kernel_selftests
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-aws (Ubuntu Eoan)
Status: New => Confirmed
--
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/1864073
Title:
seccomp_bpf fails Eoan 5.3 in ubuntu_kernel_selftests
Status in ubuntu-kernel-tests:
Triaged
Status in linux-aws package in Ubuntu:
Confirmed
Status in linux-aws source package in Eoan:
Confirmed
Bug description:
Cloud: AWS
Kernel: 5.3.0-1012.13
Test: ubuntu_kernel_selftests
The following is observed from the autotest failure.
02/19 21:33:08 DEBUG| utils:0153| [stdout] Estimated seccomp overhead per
syscall: 42 ns
02/19 21:33:08 DEBUG| utils:0153| [stdout] ok 1..2 selftests: seccomp:
seccomp_benchmark [PASS]
02/19 21:33:08 DEBUG| utils:0153| [stdout] make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/seccomp'
02/19 21:33:08 DEBUG| utils:0153| [stdout] make: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
02/19 21:33:08 INFO |ubuntu_ker:0179| == Summary ===
02/19 21:33:08 INFO |ubuntu_ker:0056| Sub test case: seccomp_bpf failed.
02/19 21:33:08 ERROR| test:0414| Exception escaping from test:
Traceback (most recent call last):
File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
_call_test_function(self.execute, *p_args, **p_dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 823, in
_call_test_function
return func(*args, **dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
postprocess_profiled_run, args, dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 212, in
_call_run_once
self.run_once(*args, **dargs)
File
"/home/ubuntu/autotest/client/tests/ubuntu_kernel_selftests/ubuntu_kernel_selftests.py",
line 188, in run_once
raise error.TestError('Test failed for ' + test_name)
TestError: Test failed for seccomp
When the test is run standalone we can get a little more information.
[==] Running 75 tests from 1 test cases.
[ RUN ] global.mode_strict_support
[ OK ] global.mode_strict_support
[ RUN ] global.mode_strict_cannot_call_prctl
[ OK ] global.mode_strict_cannot_call_prctl
[ RUN ] global.no_new_privs_support
[ OK ] global.no_new_privs_support
[ RUN ] global.mode_filter_support
[ OK ] global.mode_filter_support
[ RUN ] global.mode_filter_without_nnp
[ OK ] global.mode_filter_without_nnp
[ RUN ] global.filter_size_limits
[ OK ] global.filter_size_limits
[ RUN ] global.filter_chain_limits
[ OK ] global.filter_chain_limits
[ RUN ] global.mode_filter_cannot_move_to_strict
[ OK ] global.mode_filter_cannot_move_to_strict
[ RUN ] global.mode_filter_get_seccomp
[ OK ] global.mode_filter_get_seccomp
[ RUN ] global.ALLOW_all
[ OK ] global.ALLOW_all
[ RUN ] global.empty_prog
[ OK ] global.empty_prog
[ RUN ] global.log_all
[ OK ] global.log_all
[ RUN ] global.unknown_ret_is_kill_inside
[ OK ] global.unknown_ret_is_kill_inside
[ RUN ] global.unknown_ret_is_kill_above_allow
[ OK ] global.unknown_ret_is_kill_above_allow
[ RUN ] global.KILL_all
[ OK ] global.KILL_all
[ RUN ] global.KILL_one
[ OK ] global.KILL_one
[ RUN ] global.KILL_one_arg_one
[ OK ] global.KILL_one_arg_one
[ RUN ] global.KILL_one_arg_six
[ OK ] global.KILL_one_arg_six
[ RUN ] global.KILL_thread
[ OK ] global.KILL_thread
[ RUN ] global.KILL_process
[ OK ] global.KILL_process
[ RUN ] global.arg_out_of_range
[ OK ] global.arg_out_of_range
[ RUN ] global.ERRNO_valid
[ OK ] global.ERRNO_valid
[ RUN ] global.ERRNO_zero
[ OK ] global.ERRNO_zero
[ RUN ] global.ERRNO_capped
[ OK ] global.ERRNO_capped
[ RUN ] global.ERRNO_order
[ OK ] global.ERRNO_order
[ RUN ] TRAP.dfl
[ OK ] TRAP.dfl
[ RUN ] TRAP.ign
[ OK ] TRAP.ign
[ RUN ] TRAP.handler
[ OK ] TRAP.handler
[ RUN ] precedence.allow_ok
[ OK ] precedence.allow_ok
[ RUN ] precedence.kill_is_highest
[ OK ] precedence.kill_is_highest
[ RUN ] precedence.kill_is_highest_in_any_order
[ OK ] precedence.kill_is_highest_in_any_order
[ RUN ] precedence.trap_is_second
[ OK ] precedence.trap_is_second
[ RUN ] precedence.trap_is_second_in_any_order
[ OK ] precedence.trap_is_second_in_any_order
[ RUN ] precedence.errno_is_third
[ OK ] precedence.errno_is_third
[ RUN
[Kernel-packages] [Bug 1864073] Re: seccomp_bpf fails Eoan 5.3 in ubuntu_kernel_selftests
Observed on Azure, 5.3, 2020.03.16 kernels.
** Tags added: sru-20200316
--
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/1864073
Title:
seccomp_bpf fails Eoan 5.3 in ubuntu_kernel_selftests
Status in ubuntu-kernel-tests:
Triaged
Status in linux-aws package in Ubuntu:
Confirmed
Status in linux-aws source package in Eoan:
Confirmed
Bug description:
Cloud: AWS
Kernel: 5.3.0-1012.13
Test: ubuntu_kernel_selftests
The following is observed from the autotest failure.
02/19 21:33:08 DEBUG| utils:0153| [stdout] Estimated seccomp overhead per
syscall: 42 ns
02/19 21:33:08 DEBUG| utils:0153| [stdout] ok 1..2 selftests: seccomp:
seccomp_benchmark [PASS]
02/19 21:33:08 DEBUG| utils:0153| [stdout] make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/seccomp'
02/19 21:33:08 DEBUG| utils:0153| [stdout] make: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
02/19 21:33:08 INFO |ubuntu_ker:0179| == Summary ===
02/19 21:33:08 INFO |ubuntu_ker:0056| Sub test case: seccomp_bpf failed.
02/19 21:33:08 ERROR| test:0414| Exception escaping from test:
Traceback (most recent call last):
File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
_call_test_function(self.execute, *p_args, **p_dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 823, in
_call_test_function
return func(*args, **dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
postprocess_profiled_run, args, dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 212, in
_call_run_once
self.run_once(*args, **dargs)
File
"/home/ubuntu/autotest/client/tests/ubuntu_kernel_selftests/ubuntu_kernel_selftests.py",
line 188, in run_once
raise error.TestError('Test failed for ' + test_name)
TestError: Test failed for seccomp
When the test is run standalone we can get a little more information.
[==] Running 75 tests from 1 test cases.
[ RUN ] global.mode_strict_support
[ OK ] global.mode_strict_support
[ RUN ] global.mode_strict_cannot_call_prctl
[ OK ] global.mode_strict_cannot_call_prctl
[ RUN ] global.no_new_privs_support
[ OK ] global.no_new_privs_support
[ RUN ] global.mode_filter_support
[ OK ] global.mode_filter_support
[ RUN ] global.mode_filter_without_nnp
[ OK ] global.mode_filter_without_nnp
[ RUN ] global.filter_size_limits
[ OK ] global.filter_size_limits
[ RUN ] global.filter_chain_limits
[ OK ] global.filter_chain_limits
[ RUN ] global.mode_filter_cannot_move_to_strict
[ OK ] global.mode_filter_cannot_move_to_strict
[ RUN ] global.mode_filter_get_seccomp
[ OK ] global.mode_filter_get_seccomp
[ RUN ] global.ALLOW_all
[ OK ] global.ALLOW_all
[ RUN ] global.empty_prog
[ OK ] global.empty_prog
[ RUN ] global.log_all
[ OK ] global.log_all
[ RUN ] global.unknown_ret_is_kill_inside
[ OK ] global.unknown_ret_is_kill_inside
[ RUN ] global.unknown_ret_is_kill_above_allow
[ OK ] global.unknown_ret_is_kill_above_allow
[ RUN ] global.KILL_all
[ OK ] global.KILL_all
[ RUN ] global.KILL_one
[ OK ] global.KILL_one
[ RUN ] global.KILL_one_arg_one
[ OK ] global.KILL_one_arg_one
[ RUN ] global.KILL_one_arg_six
[ OK ] global.KILL_one_arg_six
[ RUN ] global.KILL_thread
[ OK ] global.KILL_thread
[ RUN ] global.KILL_process
[ OK ] global.KILL_process
[ RUN ] global.arg_out_of_range
[ OK ] global.arg_out_of_range
[ RUN ] global.ERRNO_valid
[ OK ] global.ERRNO_valid
[ RUN ] global.ERRNO_zero
[ OK ] global.ERRNO_zero
[ RUN ] global.ERRNO_capped
[ OK ] global.ERRNO_capped
[ RUN ] global.ERRNO_order
[ OK ] global.ERRNO_order
[ RUN ] TRAP.dfl
[ OK ] TRAP.dfl
[ RUN ] TRAP.ign
[ OK ] TRAP.ign
[ RUN ] TRAP.handler
[ OK ] TRAP.handler
[ RUN ] precedence.allow_ok
[ OK ] precedence.allow_ok
[ RUN ] precedence.kill_is_highest
[ OK ] precedence.kill_is_highest
[ RUN ] precedence.kill_is_highest_in_any_order
[ OK ] precedence.kill_is_highest_in_any_order
[ RUN ] precedence.trap_is_second
[ OK ] precedence.trap_is_second
[ RUN ] precedence.trap_is_second_in_any_order
[ OK ] precedence.trap_is_second_in_any_order
[ RUN ] precedence.errno_is_third
[ OK ] precedence.errno_is_third
[ RUN ] precedence.errno_is_third_in_any_order
[ OK ] precedence
[Kernel-packages] [Bug 1796385]
Thanks ... I reviewed log files this morning and had a look at output from journalclt. Appears the system is good to go. I guess going through and blowing out the machine and re-seating everything into their slots helped. Thanks you for your assistance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796385 Title: watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112] Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I can use the system for a while, then at random, the screen blinks and freezes. Must reboot. Seems to happen both with Wayland and Xorg. ProblemType: KernelOops DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: greg 2039 F pulseaudio /dev/snd/controlC1: greg 2039 F pulseaudio Date: Tue Oct 2 15:56:23 2018 Failure: oops InstallationDate: Installed on 2018-09-28 (7 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Default string ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=ce06b10d-2a7f-49db-a15b-85554d9a7e4d ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: X99-UD4-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF23:bd06/07/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99-UD4-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1796385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849844] Re: seccomp test in ubuntu_kernel_selftests failed to build on D amd64
*** This bug is a duplicate of bug 1864073 ***
https://bugs.launchpad.net/bugs/1864073
Disco is EOL
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Changed in: ubuntu-kernel-tests
Status: New => Invalid
** Changed in: linux (Ubuntu Disco)
Status: Incomplete => 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/1849844
Title:
seccomp test in ubuntu_kernel_selftests failed to build on D amd64
Status in ubuntu-kernel-tests:
Invalid
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Disco:
Invalid
Bug description:
Test failed to build with the proposed Disco kernel with:
undefined reference to `BIT'
ubuntu@moe:~/ubuntu-disco/tools/testing/selftests$ sudo make run_tests
make[1]: Entering directory
'/home/ubuntu/ubuntu-disco/tools/testing/selftests/seccomp'
gcc -Wl,-no-as-needed -Wall seccomp_bpf.c -lpthread -o seccomp_bpf
seccomp_bpf.c: In function ‘user_notification_continue’:
seccomp_bpf.c:3074:26: warning: overflow in conversion from ‘long int’ to
‘__s32’ {aka ‘int’} changes value from ‘116983961184613’ to ‘1936943461’
[-Woverflow]
#define USER_NOTIF_MAGIC 116983961184613L
^~~~
seccomp_bpf.c:3535:15: note: in expansion of macro ‘USER_NOTIF_MAGIC’
resp.error = USER_NOTIF_MAGIC;
^~~~
/usr/bin/ld: /tmp/cc5Df3dg.o: in function `user_notification_continue':
seccomp_bpf.c:(.text+0x2e226): undefined reference to `BIT'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:12: seccomp_bpf] Error 1
make[1]: Leaving directory
'/home/ubuntu/ubuntu-disco/tools/testing/selftests/seccomp'
make: *** [Makefile:91: all] Error 2
Note that bug 1849281 looks like a different issue.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-33-generic 5.0.0-33.35
ProcVersionSignature: User Name 5.0.0-33.35-generic 5.0.21
Uname: Linux 5.0.0-33-generic x86_64
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 25 13:38 seq
crw-rw 1 root audio 116, 33 Oct 25 13:38 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CurrentDmesg: [ 484.024237] systemd-journald[391]: /dev/kmsg buffer overrun,
some messages lost.
Date: Fri Oct 25 13:50:36 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-33-generic
root=UUID=36e162f3-41b5-4487-a6dc-09ba4e37d3bf ro console=tty1 console=ttyS0
RelatedPackageVersions:
linux-restricted-modules-5.0.0-33-generic N/A
linux-backports-modules-5.0.0-33-generic N/A
linux-firmware1.178.5
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.10.2-1ubuntu1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-bionic
dmi.modalias:
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-bionic
dmi.sys.vendor: QEMU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1849844/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849844] Re: seccomp test in ubuntu_kernel_selftests failed to build on D amd64
*** This bug is a duplicate of bug 1864073 ***
https://bugs.launchpad.net/bugs/1864073
seccomp_bpf bugs shall be tracked in 1864073
** This bug has been marked a duplicate of bug 1864073
seccomp_bpf fails Eoan 5.3 in ubuntu_kernel_selftests
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849844
Title:
seccomp test in ubuntu_kernel_selftests failed to build on D amd64
Status in ubuntu-kernel-tests:
Invalid
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Disco:
Invalid
Bug description:
Test failed to build with the proposed Disco kernel with:
undefined reference to `BIT'
ubuntu@moe:~/ubuntu-disco/tools/testing/selftests$ sudo make run_tests
make[1]: Entering directory
'/home/ubuntu/ubuntu-disco/tools/testing/selftests/seccomp'
gcc -Wl,-no-as-needed -Wall seccomp_bpf.c -lpthread -o seccomp_bpf
seccomp_bpf.c: In function ‘user_notification_continue’:
seccomp_bpf.c:3074:26: warning: overflow in conversion from ‘long int’ to
‘__s32’ {aka ‘int’} changes value from ‘116983961184613’ to ‘1936943461’
[-Woverflow]
#define USER_NOTIF_MAGIC 116983961184613L
^~~~
seccomp_bpf.c:3535:15: note: in expansion of macro ‘USER_NOTIF_MAGIC’
resp.error = USER_NOTIF_MAGIC;
^~~~
/usr/bin/ld: /tmp/cc5Df3dg.o: in function `user_notification_continue':
seccomp_bpf.c:(.text+0x2e226): undefined reference to `BIT'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:12: seccomp_bpf] Error 1
make[1]: Leaving directory
'/home/ubuntu/ubuntu-disco/tools/testing/selftests/seccomp'
make: *** [Makefile:91: all] Error 2
Note that bug 1849281 looks like a different issue.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-33-generic 5.0.0-33.35
ProcVersionSignature: User Name 5.0.0-33.35-generic 5.0.21
Uname: Linux 5.0.0-33-generic x86_64
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 25 13:38 seq
crw-rw 1 root audio 116, 33 Oct 25 13:38 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CurrentDmesg: [ 484.024237] systemd-journald[391]: /dev/kmsg buffer overrun,
some messages lost.
Date: Fri Oct 25 13:50:36 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-33-generic
root=UUID=36e162f3-41b5-4487-a6dc-09ba4e37d3bf ro console=tty1 console=ttyS0
RelatedPackageVersions:
linux-restricted-modules-5.0.0-33-generic N/A
linux-backports-modules-5.0.0-33-generic N/A
linux-firmware1.178.5
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.10.2-1ubuntu1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-bionic
dmi.modalias:
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-bionic
dmi.sys.vendor: QEMU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1849844/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1443924]
Excellent Blog! I would like to thank for the efforts you have made in writing this post. I am hoping the same best work from you in the future as well. I wanted to thank you for this websites! Thanks for sharing. Great websites! https://preactivator.com/express-vpn-crack/";>Express VPN Activation Code -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1443924 Title: 1814:0201 ieee80211 phy0: rt2x00queue_flush_queue:Warning - Queue 0 failed to flush Status in Linux: Fix Released Status in linux package in Ubuntu: Triaged Bug description: Philips i386 PC with rt2x00 pci is suffering loss of WiFi connectivity after installing 15.04 Beta. The system did work correctly with older Ubuntu versions (like 12.04) and had this problem show up after upgrading to Trusty (as I already reported in bug #1318837). Using Trusty the problem went away when switching from the stock 3.13.0-XX-generic kernel to builds of newer kernels (like 3.14.1-031401). Now the same problem shows up again after installing Vivid Beta. It seems to be the same problem reported for other Ubuntu releases (see bugs #1318837 and #1383555) and also the same problem of this upstream kernel bug: https://bugzilla.kernel.org/show_bug.cgi?id=61621 Someone on kernel's bug mentions turning off MSI interrupts and I can confirm it did change the situation: - normally the system looses WiFi connectivity mere seconds after boot (eg. can't ping anything after boot) - if I boot with "pci=nomsi" the system will remain connected to the WiFi for a much longer period (eg. I am able to apt-get install something after boot) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-extra-3.19.0-13-generic 3.19.0-13.13 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic i686 ApportVersion: 2.17-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luca 1997 F pulseaudio CurrentDesktop: LXDE Date: Tue Apr 14 14:19:19 2015 HibernationDevice: RESUME=UUID=cbd1e136-ffc4-48b9-b2aa-c15264b9b132 MachineType: Freeline Freeline Series ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-13-generic root=UUID=6110f881-b32b-426d-910a-c63b355c179c ro quiet splash vt.handoff=7 pci=nomsi RelatedPackageVersions: linux-restricted-modules-3.19.0-13-generic N/A linux-backports-modules-3.19.0-13-generic N/A linux-firmware 1.143 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2004 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: Freeline Series dmi.board.vendor: Freeline dmi.board.version: Ver1.0 dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd10/29/2004:svnFreeline:pnFreelineSeries:pvrVer1.0:rvnFreeline:rnFreelineSeries:rvrVer1.0:cvn:ct3:cvr: dmi.product.name: Freeline Series dmi.product.version: Ver1.0 dmi.sys.vendor: Freeline To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1443924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1443924]
Thank you because you have been willing to share information with us. we will always appreciate all you have done here because I know you are very concerned with our. https://haxsoft.com/driverdoc-crack-full-keys/";>Driver Doc Crack 2020 Free Download -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1443924 Title: 1814:0201 ieee80211 phy0: rt2x00queue_flush_queue:Warning - Queue 0 failed to flush Status in Linux: Fix Released Status in linux package in Ubuntu: Triaged Bug description: Philips i386 PC with rt2x00 pci is suffering loss of WiFi connectivity after installing 15.04 Beta. The system did work correctly with older Ubuntu versions (like 12.04) and had this problem show up after upgrading to Trusty (as I already reported in bug #1318837). Using Trusty the problem went away when switching from the stock 3.13.0-XX-generic kernel to builds of newer kernels (like 3.14.1-031401). Now the same problem shows up again after installing Vivid Beta. It seems to be the same problem reported for other Ubuntu releases (see bugs #1318837 and #1383555) and also the same problem of this upstream kernel bug: https://bugzilla.kernel.org/show_bug.cgi?id=61621 Someone on kernel's bug mentions turning off MSI interrupts and I can confirm it did change the situation: - normally the system looses WiFi connectivity mere seconds after boot (eg. can't ping anything after boot) - if I boot with "pci=nomsi" the system will remain connected to the WiFi for a much longer period (eg. I am able to apt-get install something after boot) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-extra-3.19.0-13-generic 3.19.0-13.13 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic i686 ApportVersion: 2.17-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luca 1997 F pulseaudio CurrentDesktop: LXDE Date: Tue Apr 14 14:19:19 2015 HibernationDevice: RESUME=UUID=cbd1e136-ffc4-48b9-b2aa-c15264b9b132 MachineType: Freeline Freeline Series ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-13-generic root=UUID=6110f881-b32b-426d-910a-c63b355c179c ro quiet splash vt.handoff=7 pci=nomsi RelatedPackageVersions: linux-restricted-modules-3.19.0-13-generic N/A linux-backports-modules-3.19.0-13-generic N/A linux-firmware 1.143 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2004 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: Freeline Series dmi.board.vendor: Freeline dmi.board.version: Ver1.0 dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd10/29/2004:svnFreeline:pnFreelineSeries:pvrVer1.0:rvnFreeline:rnFreelineSeries:rvrVer1.0:cvn:ct3:cvr: dmi.product.name: Freeline Series dmi.product.version: Ver1.0 dmi.sys.vendor: Freeline To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1443924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
