[Kernel-packages] [Bug 1896726] Re: [UBUNTU 20.04.1] qemu (secure guest) crash due to gup_fast / dynamic page table folding issue
Thx for testing, that definitely gives even more confidence ...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1896726
Title:
[UBUNTU 20.04.1] qemu (secure guest) crash due to gup_fast / dynamic
page table folding issue
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
Incomplete
Status in linux source package in Groovy:
In Progress
Bug description:
Justification:
==
Secure KVM guest (using secure execution on Ubuntu Server 20.04 for s390x)
crashes happen from time to time during boot.
Such crashed guests ("reason=crashed" in the libvirt log) end up in hutoff
state instead of crashed state ( preserve is set).
The crash points to a kernel memory management problem, addressed by the
following patch/fix.
The modifications touch common memory management code,
but it will have no effect to architectures other than s390x.
This is ensured by the fact that only s390 provides / implements the new
helper functions.
And for s390x, this is actually a critical (and carefully tested) fix for a
(previous) regression, so it can hardly get any more regressive.
The patch landed upstream in linux-next, is in depth discussed
at LKML https://lkml.kernel.org/r/20190418100218.0a4afd51@mschwideX1
and here
https://lore.kernel.org/linux-arch/patch.git-943f1e5dcff2.your-ad-here.call-01599856292-ext-8676@work.hours/
and will soon land via the regular upstream stable release update for kernel
5.4 in focal, too.
The process already started:
https://lore.kernel.org/stable/patch-1.thread-41918b.git-41918be365c0.your-ad-here.call-01600439945-ext-8991@work.hours/
Hence this cherry-pick from the upstream patch should be added to groovy
to avoid any potential regression in case the patch landed in focal via the
upstream release update process,
but is not in groovy and someones upgrades from focal to groovy.
__
Secure Execution with Ubuntu 20.04, secure guest crash during boot
from time to time, crashed guest went into Shufoff state instead of
Crashed state (preserve is set), so I can't get a dump.
libvirt log file:
2020-04-21T16:35:39.382999Z qemu-system-s390x: Guest says index 19608 is
available
2020-04-21 16:35:44.831+: shutting down, reason=crashed
---uname output---
Linux ubu204uclg1002 5.4.0-25-generic #29-Ubuntu SMP Fri Apr 17 15:05:32 UTC
2020 s390x s390x s390x GNU/Linux
Machine Type = z15 8561
---Debugger---
A debugger is not configured
---Steps to Reproduce---
I have a setup with 72 KVM guests which I can start in secure or non-secure
mode. Starting all of them in secure mode back to back results in a number of
guests (4..8) in Shutoff state and reason=crashed in the libvirt log. I can
manually start the guest again no problem. Different guests are failing.
Host and guests are on latest Ubuntu 20.04.
The supposed fix (kernel memory management) has landed in Andrew Mortons mm
tree
https://lore.kernel.org/mm-commits/20200916003608.ib4ln%25a...@linux-foundation.org/T/#u
Please note: while this was found with secure execution, the bug is
actually present for non-KVM workloads as well.
The complete patch is this:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=a338e69ba37286c0fc300ab7e6fa0227e6ca68b1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1896726/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897664] Re: Touchpad is not detected.
Please remove "acpi_osi=" kernel parameter and retest. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1897664 Title: Touchpad is not detected. Status in linux package in Ubuntu: Incomplete Bug description: After some kernel update on Ubuntu LTS 20 the touchpad was not detected. Laptop model - Lenovo Legion Y540. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shivanshu 4310 F pulseaudio /dev/snd/controlC1: shivanshu 4310 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 29 08:59:30 2020 MachineType: LENOVO 81SY ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=cde879a6-91ea-4acc-b31a-59db4b57ed42 ro acpi_osi= acpi_backlight=intel RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: BHCN38WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion Y540-15IRH-PG0 dmi.modalias: dmi:bvnLENOVO:bvrBHCN38WW:bd05/19/2020:svnLENOVO:pn81SY:pvrLenovoLegionY540-15IRH-PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrLenovoLegionY540-15IRH-PG0: dmi.product.family: Legion Y540-15IRH-PG0 dmi.product.name: 81SY dmi.product.sku: LENOVO_MT_81SY_BU_idea_FM_Legion Y540-15IRH-PG0 dmi.product.version: Lenovo Legion Y540-15IRH-PG0 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897664/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896726] Comment bridged from LTC Bugzilla
--- Comment From pa...@de.ibm.com 2020-09-29 00:26 EDT---
(In reply to comment #163)
> Hi Gerald, I wasn't aware that you already started to work on/with upstream
> stable - that's great!
>
> I had a look at the backport at
> https://lore.kernel.org/stable/patch-1.thread-41918b.git-41918be365c0.your-
> ad-here.call-01600439945-ext-8991@work.hours/ and it applied cleanly on
> current focal master-next.
> So I've built a patched focal kernel - in addition to the above groovy
> kernel - and share it here as well for any further testing:
> https://people.canonical.com/~fheimes/lp1896726/
>
I've tested the provided focal kernel. It passes my tests.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1896726
Title:
[UBUNTU 20.04.1] qemu (secure guest) crash due to gup_fast / dynamic
page table folding issue
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
Incomplete
Status in linux source package in Groovy:
In Progress
Bug description:
Justification:
==
Secure KVM guest (using secure execution on Ubuntu Server 20.04 for s390x)
crashes happen from time to time during boot.
Such crashed guests ("reason=crashed" in the libvirt log) end up in hutoff
state instead of crashed state ( preserve is set).
The crash points to a kernel memory management problem, addressed by the
following patch/fix.
The modifications touch common memory management code,
but it will have no effect to architectures other than s390x.
This is ensured by the fact that only s390 provides / implements the new
helper functions.
And for s390x, this is actually a critical (and carefully tested) fix for a
(previous) regression, so it can hardly get any more regressive.
The patch landed upstream in linux-next, is in depth discussed
at LKML https://lkml.kernel.org/r/20190418100218.0a4afd51@mschwideX1
and here
https://lore.kernel.org/linux-arch/patch.git-943f1e5dcff2.your-ad-here.call-01599856292-ext-8676@work.hours/
and will soon land via the regular upstream stable release update for kernel
5.4 in focal, too.
The process already started:
https://lore.kernel.org/stable/patch-1.thread-41918b.git-41918be365c0.your-ad-here.call-01600439945-ext-8991@work.hours/
Hence this cherry-pick from the upstream patch should be added to groovy
to avoid any potential regression in case the patch landed in focal via the
upstream release update process,
but is not in groovy and someones upgrades from focal to groovy.
__
Secure Execution with Ubuntu 20.04, secure guest crash during boot
from time to time, crashed guest went into Shufoff state instead of
Crashed state (preserve is set), so I can't get a dump.
libvirt log file:
2020-04-21T16:35:39.382999Z qemu-system-s390x: Guest says index 19608 is
available
2020-04-21 16:35:44.831+: shutting down, reason=crashed
---uname output---
Linux ubu204uclg1002 5.4.0-25-generic #29-Ubuntu SMP Fri Apr 17 15:05:32 UTC
2020 s390x s390x s390x GNU/Linux
Machine Type = z15 8561
---Debugger---
A debugger is not configured
---Steps to Reproduce---
I have a setup with 72 KVM guests which I can start in secure or non-secure
mode. Starting all of them in secure mode back to back results in a number of
guests (4..8) in Shutoff state and reason=crashed in the libvirt log. I can
manually start the guest again no problem. Different guests are failing.
Host and guests are on latest Ubuntu 20.04.
The supposed fix (kernel memory management) has landed in Andrew Mortons mm
tree
https://lore.kernel.org/mm-commits/20200916003608.ib4ln%25a...@linux-foundation.org/T/#u
Please note: while this was found with secure execution, the bug is
actually present for non-KVM workloads as well.
The complete patch is this:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=a338e69ba37286c0fc300ab7e6fa0227e6ca68b1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1896726/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837037] Re: memcg_move_charge_at_immigrate_test from controllers in ubuntu_ltp failed with D i386 / E-oracle
This will timeout on B-4.15 s390x zVM (passed on s390x LPAR): memcg_move_charge_at_immigrate_test 5 TINFO: Starting test 2 sh: echo: I/O error memcg_move_charge_at_immigrate_test 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_move_charge_at_immigrate_test 5 TINFO: Running memcg_process --mmap-anon --shm --mmap-file -s 135168 memcg_move_charge_at_immigrate_test 5 TINFO: Warming up pid: 34479 memcg_move_charge_at_immigrate_test 5 TINFO: Process is still here after warm up: 34479 memcg_move_charge_at_immigrate_test 5 TBROK: timeouted on memory.usage_in_bytes ** Tags added: sru-20200921 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837037 Title: memcg_move_charge_at_immigrate_test from controllers in ubuntu_ltp failed with D i386 / E-oracle Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Won't Fix Bug description: Similar to bug 1837035 This memcg_move_charge_at_immigrate_test test failed on an i386 node "pepe" with Disco kernel. It failed with: memcg_move_charge_at_immigrate_test 5 TINFO: Warming up pid: 2192 memcg_process: shmget() failed: Invalid argument /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 168: kill: No such process memcg_move_charge_at_immigrate_test 5 TFAIL: Process 2192 exited with 1 after warm up <<>> tag=memcg_move_charge_at_immigrate stime=1563448078 cmdline="memcg_move_charge_at_immigrate_test.sh" contacts="" analysis=exit <<>> memcg_move_charge_at_immigrate_test 1 TINFO: Starting test 1 /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 522: echo: echo: I/O error memcg_move_charge_at_immigrate_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_move_charge_at_immigrate_test 1 TINFO: Running memcg_process --mmap-anon -s 135168 memcg_move_charge_at_immigrate_test 1 TINFO: Warming up pid: 2162 memcg_move_charge_at_immigrate_test 1 TINFO: Process is still here after warm up: 2162 memcg_move_charge_at_immigrate_test 1 TPASS: rss is 0 as expected memcg_move_charge_at_immigrate_test 2 TPASS: cache is 0 as expected memcg_move_charge_at_immigrate_test 3 TPASS: rss is 135168 as expected memcg_move_charge_at_immigrate_test 4 TPASS: cache is 0 as expected memcg_move_charge_at_immigrate_test 5 TINFO: Starting test 2 /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 522: echo: echo: I/O error memcg_move_charge_at_immigrate_test 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_move_charge_at_immigrate_test 5 TINFO: Running memcg_process --mmap-anon --shm --mmap-file -s 135168 memcg_move_charge_at_immigrate_test 5 TINFO: Warming up pid: 2192 memcg_process: shmget() failed: Invalid argument /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 168: kill: No such process memcg_move_charge_at_immigrate_test 5 TFAIL: Process 2192 exited with 1 after warm up memcg_move_charge_at_immigrate_test 6 TINFO: Starting test 3 /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 522: echo: echo: I/O error memcg_move_charge_at_immigrate_test 6 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_move_charge_at_immigrate_test 6 TINFO: Running memcg_process --mmap-anon --shm --mmap-file -s 135168 memcg_move_charge_at_immigrate_test 6 TINFO: Warming up pid: 2207 memcg_process: shmget() failed: Invalid argument /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 168: kill: No such process memcg_move_charge_at_immigrate_test 6 TFAIL: Process 2207 exited with 1 after warm up memcg_move_charge_at_immigrate_test 7 TINFO: Starting test 4 /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 522: echo: echo: I/O error memcg_move_charge_at_immigrate_test 7 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_move_charge_at_immigrate_test 7 TINFO: Running memcg_process --mmap-anon --shm -s 135168 memcg_move_charge_at_immigrate_test 7 TINFO: Warming up pid: memcg_process: shmget() failed: Invalid argument /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 168: kill: No such process memcg_move_charge_at_immigrate_test 7 TFAIL: Process exited with 1 after warm up <<>> initiation_status="ok" duration=4 termination_type=exited termination_id=1 corefile=no cutime=9 cstime=2 <<>> Steps to run this test: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "memcg_move_charge_at_immigrate memcg_move_charge_at_immigrate_test.sh" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-21-generic 5.0.0-21.22 ProcVersionSignature: User Name 5.0.0-21.22-generic 5.0.15
[Kernel-packages] [Bug 1837035] Re: memcg_stat_rss from controllers in ubuntu_ltp failed
This will timeout on B-4.15 s390x zVM (passed on s390x LPAR): memcg_stat_rss 4 TINFO: Starting test 4 sh: echo: I/O error memcg_stat_rss 4 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 4 TINFO: Running memcg_process --mmap-anon --mmap-file --shm -s 135168 memcg_stat_rss 4 TINFO: Warming up pid: 33885 memcg_stat_rss 4 TINFO: Process is still here after warm up: 33885 memcg_stat_rss 4 TBROK: timeouted on memory.usage_in_bytes ** Tags added: sru-20200921 -- 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/1837035 Title: memcg_stat_rss from controllers in ubuntu_ltp failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Bug description: This issue was spotted on an i386 node "pepe" with Disco kernel, it failed with: memcg_process: shmget() failed: Invalid argument /opt/ltp/testcases/bin/memcg_stat_rss.sh: 168: kill: No such process memcg_stat_rss 4 TFAIL: Process 1845 exited with 1 after warm up <<>> tag=memcg_stat_rss stime=1563448062 cmdline="memcg_stat_rss.sh" contacts="" analysis=exit <<>> memcg_stat_rss 1 TINFO: Starting test 1 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 1 TINFO: Running memcg_process --mmap-anon -s 135168 memcg_stat_rss 1 TINFO: Warming up pid: 1784 memcg_stat_rss 1 TINFO: Process is still here after warm up: 1784 memcg_stat_rss 1 TPASS: rss is 135168 as expected memcg_stat_rss 2 TINFO: Starting test 2 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 2 TINFO: Running memcg_process --mmap-file -s 4096 memcg_stat_rss 2 TINFO: Warming up pid: 1804 memcg_stat_rss 2 TINFO: Process is still here after warm up: 1804 memcg_stat_rss 2 TPASS: rss is 0 as expected memcg_stat_rss 3 TINFO: Starting test 3 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 3 TINFO: Running memcg_process --shm -k 3 -s 4096 memcg_stat_rss 3 TINFO: Warming up pid: 1825 memcg_stat_rss 3 TINFO: Process is still here after warm up: 1825 memcg_stat_rss 3 TPASS: rss is 0 as expected memcg_stat_rss 4 TINFO: Starting test 4 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 4 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 4 TINFO: Running memcg_process --mmap-anon --mmap-file --shm -s 135168 memcg_stat_rss 4 TINFO: Warming up pid: 1845 memcg_process: shmget() failed: Invalid argument /opt/ltp/testcases/bin/memcg_stat_rss.sh: 168: kill: No such process memcg_stat_rss 4 TFAIL: Process 1845 exited with 1 after warm up memcg_stat_rss 5 TINFO: Starting test 5 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 5 TINFO: Running memcg_process --mmap-lock1 -s 135168 memcg_stat_rss 5 TINFO: Warming up pid: 1858 memcg_stat_rss 5 TINFO: Process is still here after warm up: 1858 memcg_stat_rss 5 TPASS: rss is 135168 as expected memcg_stat_rss 6 TINFO: Starting test 6 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 6 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 6 TINFO: Running memcg_process --mmap-anon -s 135168 memcg_stat_rss 6 TINFO: Warming up pid: 1878 memcg_stat_rss 6 TINFO: Process is still here after warm up: 1878 memcg_stat_rss 6 TPASS: rss is 135168 as expected memcg_stat_rss 7 TPASS: rss is 0 as expected memcg_stat_rss 8 TINFO: Starting test 7 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 8 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 8 TINFO: Running memcg_process --mmap-file -s 4096 memcg_stat_rss 8 TINFO: Warming up pid: 1901 memcg_stat_rss 8 TINFO: Process is still here after warm up: 1901 memcg_stat_rss 8 TPASS: rss is 0 as expected memcg_stat_rss 9 TPASS: rss is 0 as expected memcg_stat_rss 10 TINFO: Starting test 8 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 10 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 10 TINFO: Running memcg_process --shm -k 8 -s 4096 memcg_stat_rss 10 TINFO: Warming up pid: 1925 memcg_stat_rss 10 TINFO: Process is still here after warm up: 1925 memcg_stat_rss 10 TPASS: rss is 0 as expected memcg_stat_rss 11 TPASS: rss is 0 as expected memcg_stat_rss 12 TINFO: Starting test 9 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 12
[Kernel-packages] [Bug 1887214] Re: [18.04 LTS] Intel 8265 / 8275 [8086:24fd] Subsystem [8086:0010] Somehow wifi network latency is too high (1000~3000 ms)
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887214 Title: [18.04 LTS] Intel 8265 / 8275 [8086:24fd] Subsystem [8086:0010] Somehow wifi network latency is too high (1000~3000 ms) Status in linux package in Ubuntu: Expired Bug description: [Problem description] Somehow wifi network latency is too high. (1000~3000 ms) DUT: - Product: Lenovo X1C6 - BIOS Information: Vendor: LENOVO Version: N23ET74W (1.49 ) Release Date: 06/03/2020 - Wifi information: Intel Wireless 8265 / 8275 driverversion=5.3.0-62-generic firmware=36.9f0a2d68.0 - OS: Ubuntu 18.04.4 LTS/Linux 5.3.0-62-generic/X86-64 [Test steps] 1. Boot up Ubuntu 18.04.4 LTS. 2. Open terminal. 3. To execute ping command, and target is in the local network. (For example: local gateway) 4. After few mins, I noticed that network latency will get worse. Sample output: 64 bytes from 192.168.1.1: icmp_seq=714 ttl=64 time=2.31 ms 64 bytes from 192.168.1.1: icmp_seq=715 ttl=64 time=1.61 ms 64 bytes from 192.168.1.1: icmp_seq=716 ttl=64 time=8.93 ms 64 bytes from 192.168.1.1: icmp_seq=717 ttl=64 time=59.0 ms 64 bytes from 192.168.1.1: icmp_seq=718 ttl=64 time=101 ms 64 bytes from 192.168.1.1: icmp_seq=719 ttl=64 time=155 ms 64 bytes from 192.168.1.1: icmp_seq=720 ttl=64 time=212 ms 64 bytes from 192.168.1.1: icmp_seq=721 ttl=64 time=347 ms 64 bytes from 192.168.1.1: icmp_seq=722 ttl=64 time=485 ms 64 bytes from 192.168.1.1: icmp_seq=723 ttl=64 time=663 ms 64 bytes from 192.168.1.1: icmp_seq=724 ttl=64 time=914 ms 64 bytes from 192.168.1.1: icmp_seq=725 ttl=64 time=1149 ms 64 bytes from 192.168.1.1: icmp_seq=726 ttl=64 time=1490 ms 64 bytes from 192.168.1.1: icmp_seq=727 ttl=64 time=1828 ms 64 bytes from 192.168.1.1: icmp_seq=728 ttl=64 time=2154 ms 64 bytes from 192.168.1.1: icmp_seq=729 ttl=64 time=2609 ms 64 bytes from 192.168.1.1: icmp_seq=730 ttl=64 time=2851 ms 64 bytes from 192.168.1.1: icmp_seq=731 ttl=64 time=2825 ms 64 bytes from 192.168.1.1: icmp_seq=732 ttl=64 time=2184 ms 64 bytes from 192.168.1.1: icmp_seq=733 ttl=64 time=2582 ms 64 bytes from 192.168.1.1: icmp_seq=734 ttl=64 time=1898 ms 64 bytes from 192.168.1.1: icmp_seq=735 ttl=64 time=1377 ms 5. Same machine when I switched to W10 then I didn't encounter this symptom. [Expected result] Wifi network latency should not over 2~3 ms at least. [Actual result] Wifi network latency is too high. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lawrence 2772 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-30 (772 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20KGS0FV00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=65f0f796-b6da-4d46-98a5-325713eee95b ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-62-generic N/A linux-backports-modules-5.3.0-62-generic N/A linux-firmware1.173.18 Tags: bionic Uname: Linux 5.3.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/03/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET74W (1.49 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KGS0FV00 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:bvrN23ET74W(1.49):bd06/03/2020:svnLENOVO:pn20KGS0FV00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGS0FV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KGS0FV00 dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887214/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888385] Re: FRITZ!WLAN USB Stick v2 (Product: FRITZ!WLAN N2.4) [057c:8403] does not work with Linux version 4.4.0-186-generic (Last working version 4.4.0-185-generic and 4.4.0-
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888385 Title: FRITZ!WLAN USB Stick v2 (Product: FRITZ!WLAN N2.4) [057c:8403] does not work with Linux version 4.4.0-186-generic (Last working version 4.4.0-185-generic and 4.4.0-184-generic) Status in linux package in Ubuntu: Expired Bug description: Dear all, the USB WLAN Stick (FRITZ!WLAN USB Stick v2) worked flawlessly up to the Linux Kernel version 4.4.0-185-generic, so I assume some problem has been introduced moving from Linux version 4.4.0-185-generic to the Linux version 4.4.0-186-generic. Operating system and release can be found below. Description:Ubuntu 16.04.6 LTS Release:16.04 Attached are the files for the currently working version (4.4.0-185-generic): dmesg, version signature, lspci and uname output). I provide too the dmesg output of the failing kernel version (4.4.0-185-generic). I am happy to provide more details. Apparently the module is not loaded anymore. Kind regards, Stephan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend
The fix is not in focal (Ubuntu 20.04) yet. Please wait for that before logging any new bugs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1855757 Title: [nvidia] Background image corrupted after standby or resume from suspend Status in mutter package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in mutter source package in Focal: Triaged Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-390 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-435 source package in Focal: Won't Fix Bug description: Looks similar to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407 When the computer goes to standby, the background image becomes corrupted. I am able to fix by "killall Xorg" , change the background image (settings > background) and restart. Haven't tried login logout. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 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: Mon Dec 9 10:58:35 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c] InstallationDate: Installed on 2019-11-29 (10 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTek Computer Inc. G60JX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G60JX dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0: dmi.product.family: PEGA Family dmi.product.name: G60JX dmi.product.sku: 0 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTek Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1855757/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897501] Re: HP Zbook Studio G7 boots into corrupted screen with PSR featured panel
https://lists.ubuntu.com/archives/kernel-team/2020-September/113796.html
for F/OEM-5.6/G/U
** Changed in: linux-oem-5.6 (Ubuntu Focal)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Groovy)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Focal)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1897501
Title:
HP Zbook Studio G7 boots into corrupted screen with PSR featured panel
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
In Progress
Status in linux-oem-5.6 source package in Focal:
In Progress
Status in linux source package in Groovy:
In Progress
Status in linux-oem-5.6 source package in Groovy:
Invalid
Bug description:
Sreen divided into half after installing Focal 5.4.0-48-generic under
Power Saving/Hybrid Graphics Mode. Normal as switched to Discrete
Graphics Mode. Screenshot attached as
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897501/+attachment/5414860/+files/20200928_135412.jpg
.
With some more investigatin, https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/focal/commit/?id=d246a6cfe782
("UBUNTU: SAUCE: drm/i915: Disable PSR by default on all platforms")
for bug 1849947 is the root cause. This was landed to all Ubuntu
kernels and Ubuntu only for kernel versions 5.0 and up till v5.9
unstable currently.
It seems this panel must have PSR enabled.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-48-generic 5.4.0-48.52
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm 964 F pulseaudio
CasperMD5CheckResult: skip
Date: Mon Sep 28 01:50:54 2020
InstallationDate: Installed on 2020-09-22 (5 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200218)
MachineType: HP HP ZBook Studio G7
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic
root=UUID=ac48cfe8-5fa7-410c-ad1b-53d1e2683841 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.4.0-48-generic N/A
linux-backports-modules-5.4.0-48-generic N/A
linux-firmware1.187.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2020
dmi.bios.vendor: HP
dmi.bios.version: S91 Ver. 85.28.01
dmi.board.name: 8736
dmi.board.vendor: HP
dmi.board.version: KBC Version 14.32.03
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias:
dmi:bvnHP:bvrS91Ver.85.28.01:bd09/18/2020:svnHP:pnHPZBookStudioG7:pvr:rvnHP:rn8736:rvrKBCVersion14.32.03:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN HP ZBook
dmi.product.name: HP ZBook Studio G7
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1897501/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897664] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1897664 Title: Touchpad is not detected. Status in linux package in Ubuntu: Confirmed Bug description: After some kernel update on Ubuntu LTS 20 the touchpad was not detected. Laptop model - Lenovo Legion Y540. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shivanshu 4310 F pulseaudio /dev/snd/controlC1: shivanshu 4310 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 29 08:59:30 2020 MachineType: LENOVO 81SY ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=cde879a6-91ea-4acc-b31a-59db4b57ed42 ro acpi_osi= acpi_backlight=intel RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: BHCN38WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion Y540-15IRH-PG0 dmi.modalias: dmi:bvnLENOVO:bvrBHCN38WW:bd05/19/2020:svnLENOVO:pn81SY:pvrLenovoLegionY540-15IRH-PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrLenovoLegionY540-15IRH-PG0: dmi.product.family: Legion Y540-15IRH-PG0 dmi.product.name: 81SY dmi.product.sku: LENOVO_MT_81SY_BU_idea_FM_Legion Y540-15IRH-PG0 dmi.product.version: Lenovo Legion Y540-15IRH-PG0 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897664/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834006] Re: cpuset_hotplug from controllers in ubuntu_ltp failed
** Tags added: sru-20200921 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1834006 Title: cpuset_hotplug from controllers in ubuntu_ltp failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-aws source package in Bionic: New Status in linux-azure source package in Bionic: New Status in linux source package in Focal: New Status in linux-aws source package in Focal: New Status in linux-azure source package in Focal: New Bug description: Issue found on node amaura: <<>> tag=cpuset_hotplug stime=1561372131 cmdline="cpuset_hotplug_test.sh" contacts="" analysis=exit <<>> incrementing stop cpuset_hotplug 1 TFAIL: task's allowed list isn't expected.(Result: 0-15, Expect: 0-7) cpuset_hotplug 3 TFAIL: task's allowed list isn't expected.(Result: 0-15, Expect: 0-7) cpuset_hotplug 5 TPASS: Cpuset vs CPU hotplug test succeeded. cpuset_hotplug 7 TFAIL: task's cpu allowed list isn't expected(Result: 0-15, Expect: 0-7). cpuset_hotplug 9 TPASS: Cpuset vs CPU hotplug test succeeded. cpuset_hotplug 11 TPASS: Cpuset vs CPU hotplug test succeeded. <<>> initiation_status="ok" duration=1 termination_type=exited termination_id=1 corefile=no cutime=19 cstime=81 <<>> Test script: https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/controllers/cpuset/cpuset_hotplug_test/cpuset_hotplug_test.sh ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-22-generic 4.18.0-22.23 ProcVersionSignature: User Name 4.18.0-22.23-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 24 10:25 seq crw-rw 1 root audio 116, 33 Jun 24 10:25 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.3 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: Mon Jun 24 10:30:59 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.18.0-22-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-4.18.0-22-generic N/A linux-backports-modules-4.18.0-22-generic N/A linux-firmware 1.175.4 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.sku: To be filled by O.E.M. dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1834006/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897664] [NEW] Touchpad is not detected.
Public bug reported: After some kernel update on Ubuntu LTS 20 the touchpad was not detected. Laptop model - Lenovo Legion Y540. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shivanshu 4310 F pulseaudio /dev/snd/controlC1: shivanshu 4310 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 29 08:59:30 2020 MachineType: LENOVO 81SY ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=cde879a6-91ea-4acc-b31a-59db4b57ed42 ro acpi_osi= acpi_backlight=intel RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: BHCN38WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion Y540-15IRH-PG0 dmi.modalias: dmi:bvnLENOVO:bvrBHCN38WW:bd05/19/2020:svnLENOVO:pn81SY:pvrLenovoLegionY540-15IRH-PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrLenovoLegionY540-15IRH-PG0: dmi.product.family: Legion Y540-15IRH-PG0 dmi.product.name: 81SY dmi.product.sku: LENOVO_MT_81SY_BU_idea_FM_Legion Y540-15IRH-PG0 dmi.product.version: Lenovo Legion Y540-15IRH-PG0 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Devices which were detected." https://bugs.launchpad.net/bugs/1897664/+attachment/5415093/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1897664 Title: Touchpad is not detected. Status in linux package in Ubuntu: New Bug description: After some kernel update on Ubuntu LTS 20 the touchpad was not detected. Laptop model - Lenovo Legion Y540. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shivanshu 4310 F pulseaudio /dev/snd/controlC1: shivanshu 4310 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 29 08:59:30 2020 MachineType: LENOVO 81SY ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=cde879a6-91ea-4acc-b31a-59db4b57ed42 ro acpi_osi= acpi_backlight=intel RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: BHCN38WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion Y540-15IRH-PG0 dmi.modalias: dmi:bvnLENOVO:bvrBHCN38WW:bd05/19/2020:svnLENOVO:pn81SY:pvrLenovoLegionY540-15IRH-PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrLenovoLegionY540-15IRH-PG0: dmi.product.family: Legion Y540-15IRH-PG0 dmi.product.name: 81SY dmi.product.sku: LENOVO_MT_81SY_BU_idea_FM_Legion Y540-15IRH-PG0 dmi.product.version: Lenovo Legion Y540-15IRH-PG0 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897664/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892010] Re: [SRU] Fix acpi backlight issue on some thinkpads
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1892010 Title: [SRU] Fix acpi backlight issue on some thinkpads Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Bug description: [Impact] On some ThinkPads, the BIOS reported invalid acpi backlight implement . Then backlight can't be changed because OS use acpi backlight by default. [Fix] Check acpi backlight mode, disable it if invalid. [Test Case] Verified on 3 models of thinkpad include Intel/NV/AMD GPU with positive results. [Regression Potential] Low Most ThinkPads now use native backlight control by default. Check the false acpi mode correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1892010/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888703] Re: After the latest update on 7/21/20 the screen shows random black horizontal single pixel line stripes in columns about 10-20 pixels long on open windows and icons p
** Changed in: linux (Ubuntu) Status: Confirmed => 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/1888703 Title: After the latest update on 7/21/20 the screen shows random black horizontal single pixel line stripes in columns about 10-20 pixels long on open windows and icons presented on the desktop. Status in linux package in Ubuntu: Fix Released Bug description: Everything else works well in the system except for this issue. See attached picture for details. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 CurrentDesktop: MATE Date: Thu Jul 23 08:14:26 2020 InstallationDate: Installed on 2019-12-08 (228 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mauro 2001 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-12-08 (229 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) MachineType: IBM 2373C96 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available Socket 1: no product info available PccardctlStatus: Socket 0: no card Socket 1: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=14567323-8391-4f6b-9169-c617d286cadb ro forcepae quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-62-generic N/A linux-backports-modules-5.3.0-62-generic N/A linux-firmware1.173.19 RfKill: 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no Tags: bionic Uname: Linux 5.3.0-62-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2007 dmi.bios.vendor: IBM dmi.bios.version: 1RETDRWW (3.23 ) dmi.board.name: 2373C96 dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn2373C96:pvrThinkPadT42p:rvnIBM:rn2373C96:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 2373C96 dmi.product.version: ThinkPad T42p dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888703/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897567] Re: webcam not initialized
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1897567 Title: webcam not initialized Status in cheese package in Ubuntu: New Status in linux package in Ubuntu: Invalid Bug description: ubuntu 20.04.01 clean install. thanks in advance for your attention. polite comment, no yelling here. going thru transfer and setup machine previous install ubuntu 16.04 when usb camera was working. webcam not initialized in cheese from my generic usb anivia webcam webcam device found: Bus 001 Device 006: ID 0c45:6366 Microdia USB 2.0 Camera william@william-Studio-XPS-7100:~$ dmesg | grep -i "Camera" [43532.227381] usb 1-6: Product: USB 2.0 Camera [43532.643588] uvcvideo: Found UVC 1.00 device USB 2.0 Camera (0c45:6366) [43532.670887] uvcvideo 1-6:1.0: Entity type for entity Camera 1 was not initialized! [43532.671103] input: USB 2.0 Camera: USB Camera as /devices/pci:00/:00:12.2/usb1/1-6/1-6:1.0/input/input27 [43931.982272] usb 1-6: Product: USB 2.0 Camera [43931.985021] uvcvideo: Found UVC 1.00 device USB 2.0 Camera (0c45:6366) [43932.011454] uvcvideo 1-6:1.0: Entity type for entity Camera 1 was not initialized! [43932.011667] input: USB 2.0 Camera: USB Camera as /devices/pci:00/:00:12.2/usb1/1-6/1-6:1.0/input/input28 william@william-Studio-XPS-7100:~$ ls -ltrh /dev/video* crw-rw+ 1 root video 81, 1 Sep 27 19:39 /dev/video1 crw-rw+ 1 root video 81, 0 Sep 27 19:39 /dev/video0 william@william-Studio-XPS-7100:~$ lsusb Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 005: ID 18e3:9106 Fitipower Integrated Technology Inc Mass Storage Device Bus 002 Device 006: ID 04f9:0283 Brother Industries, Ltd MFC-J825DW Bus 002 Device 007: ID 413c:2001 Dell Computer Corp. Keyboard HID Support Bus 002 Device 004: ID 413c:1001 Dell Computer Corp. Keyboard Hub Bus 002 Device 002: ID 0424:2504 Microchip Technology, Inc. (formerly SMSC) Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 002: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 006: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: william1432 F pulseaudio /dev/snd/controlC0: william1432 F pulseaudio /dev/snd/pcmC0D1p: william1432 F...m pulseaudio /dev/snd/controlC1: william1432 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Sep 28 09:03:27 2020 GvfsMonitorError: This tool has been deprecated, use 'gio mount' instead. See 'gio help mount' for more info. GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2020-09-26 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Dell Inc. Studio XPS 7100 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=ffa0aa05-8d32-4088-b80c-8afd25831dbc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 RfKill: SourcePackage: linux Symptom: storage UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 09:03:37.505: The udisks-daemon is running (name-owner :1.10). UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0NWWY0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd09/10/2010:svnDellInc.:pnStudioXPS7100:pvr:rvnDellInc.:rn0NWWY0:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Studio XPS 7100 dmi.sys.vendor: Dell Inc. To manage
[Kernel-packages] [Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot
A very similar bug has started affecting me since I upgraded to Ubuntu 20.04. On my laptop (Dell XPS 15 9560) I am unable to decrypt my harddrive because the keyboard is unresponsive so I can't enter the password. I have found a workaround for that issue, which is to boot in recovery mode (the keyboard works in the grub menu), then drop to a root shell and run `reboot`. Upon reboot the keyboard works and lets me decrypt the drive and log in. It does not work to enter the grub menu and choose normal boot, nor does it work if I do a hard reboot after booting in recovery mode. During a Gnome session the keyboard and touchpad will occasionally become unresponsive as well. The workaround here is to press the power button - this brings up the logout dialog, which causes the touchpad and keyboard to work again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822394 Title: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot Status in libinput package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard are unresponsive at the gdm login screen. Keyboard works to unlock encrypted harddrive before that though. If I plug in a USB keyboard or activate my bluetooth mouse, I can use those to log in, and then after logging in the laptop touchpad and keyboard work again. Logging out of the desktop results in the laptop touchpad and keyboard working on the gdm screen. Did not see this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had not rebooted in a while, so not sure if bios or package upgrades triggered this behavior. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 29 17:51:00 2019 InstallationDate: Installed on 2018-09-26 (184 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867704] Re: alsa/hdmi: support nvidia mst hdmi/dp audio
@asterix52, (pci-_01_00.1) means this is a discrete Nvidia or AMD hdmi audio controller, did you install the Nvidia or AMD graphic driver under 5.4.0-48?. Please upload the log of pa-info with hdmi/dp monitor plugged. thx. -- 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/1867704 Title: alsa/hdmi: support nvidia mst hdmi/dp audio Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Bug description: This is the justification for focal: This patchset will introduce a big change on hda_jack and hda_hdmi, So I sent the patcheset to oem-b 4 months ago. After 4 months of running oem-b kernel, there is no any regression reported on this patchset, now I am backporting the patchset to our focal kernel since our oem project is waiting for the patchset to be landed to ubuntu 5.4 kernel ASAP. This patchset are already merged to mainline kernel 5.5-rc and 5.6-rc, so there is no need to send the patchset to oem-5.6 or groovy kernel. [Impact] On some LENOVO I+N machines, when setting the graphic mode to discrete, The dp/hdmi audio on the Docking Gen2 can't work with this machine + LENOVO Docking Gen2, users can't find the hdmi audio entry in the gnome-sound-setting. [Fix] Nvidia developer submit the mst audio support to 5.5-rcN and 5.6-RC1, those patches could fix this issue. [Test Case] set the machien to discrete, plug the dock gen2 to it, then boot, after booting, plug hdmi or dp to dock gen2, the hdmi or dp audio works. test other machines without Nvidia graphic or without gen2, their hdmi/dp audio still work, and check other output/input devices like headphone, microphone, they all worked as well as before. [Regression Risk] one regression possibility is the audio jacks (including analogue and hdmi) can't work anymore, that means after users plug a headphone, headset, hdmi monitor or microphone to the audio jacks or hdmi connectors, the audio driver can't detect the plugging event. But regression's possibility is very low: - this patchset was already applied to oem-b kernel for 4 months, and oem projects didn't report any regression on the patchset - I tested the testing focal kernel with this patchset on many machines, includes a dell hda audio machine, a dell dmic machine, a Lenovo I+N hda audio machine, a lenovo I+N dmic machine, a lenovo I hda audio machine, a lenovo amd hda audio machine. The audio on them all worked as well as before. This is the justification for oem-b Drop the B, so far only need to merge this patchset to OEM-B first, After the patchset is widely verified with oem-b kernel, I send the patchset to B and F then. This patchset will add support of mst audio for nvidia hdmi/dp, this patchset changes lots of common code on hda_jack and hdmi codec, so it is not easy to say it is 100% safe for other machines, but our oem project needs this patchset to be backported to ubuntu kernel, because the tight sechdule of oem project, we backport this patchset to B and OEM-B first, if the hdmi audio works well for a period of time after this patchset is merged, I will backport this patchset to focal, maybe eoan as well. [Impact] On some LENOVO I+N machines, when setting the graphic mode to discrete, The dp/hdmi audio on the Docking Gen2 can't work with this machine + LENOVO Docking Gen2 [Fix] Nvidia developer submit the mst audio support to 5.5-rcN and 5.6-RC1, those patches could fix this issue. [Test Case] set the machien to discrete, plug the dock gen2 to it, then boot, after booting, plug hdmi or dp to dock gen2, the hdmi or dp audio works. test other machines without Nvidia graphic or without gen2, their hdmi/dp audio still work. [Regression Risk] Low, those patches come from mainline kernel, I have tested those patches on the machiens with or without nvidia hdmi, and on the machines with or without docks, all worked well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1867704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871306] Re: No sound from internal card chtmax98090 - missing UCM2 files in alsa-ucm-conf 1.2.2, available in alsa-ucm-conf 1.2.3
OK, I will handle this bug. ** Changed in: alsa-ucm-conf (Ubuntu) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: alsa-ucm-conf (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1871306 Title: No sound from internal card chtmax98090 - missing UCM2 files in alsa- ucm-conf 1.2.2, available in alsa-ucm-conf 1.2.3 Status in alsa-ucm-conf package in Ubuntu: Confirmed Bug description: Asus C300 (repurposed chromembook - bios flashed by Mr.Chromebox script) - Kubuntu Focal minimal fresh installation. The sound card is detected: I see it in the Plasma Widget, in pavucontrol, in alsamixer and it's not muted. I tried and add in /usr/share/alsa/ucm/chtmax98090/ the old style use case config files: no success. I tried and unmute speakers left and right in alsamixer: no success. I rapidly tested Ubuntu Mate Focal fresh install: I had exactly the same issue. I'm running on the same rig Debian Bullseye, kernel 5.4: sound card output and input are both working perfectly - I noticed that in Kubuntu alsamixer Kubuntu when I open it I have an entry HDA IntelPCH (the HDMI card), while in Debian I find Pulseaudio. I attach the alsa-info.sh output. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.17 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Tue Apr 7 08:55:46 2020 InstallationDate: Installed on 2020-04-04 (2 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gabriel3937 F pulseaudio /dev/snd/controlC0: gabriel3937 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-04 (3 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 13d3:5657 IMC Networks USB2.0 UVC HD Webcam Bus 001 Device 002: ID 062a:4101 MosArt Semiconductor Corp. Wireless Keyboard/Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Quawks Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=225cba91-c164-4882-95d4-4f9854a80fe9 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-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: 03/17/2020 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.11.2 dmi.board.name: Quawks dmi.board.vendor: GOOGLE dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.11.2:bd03/17/2020:svnGOOGLE:pnQuawks:pvr1.0:rvnGOOGLE:rnQuawks:rvr1.0:cvnGOOGLE:ct9:cvr: dmi.product.name: Quawks dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1871306/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887674] Re: Introduce the new NVIDIA 450-server and the 450 UDA series
** Changed in: oem-priority Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1887674 Title: Introduce the new NVIDIA 450-server and the 450 UDA series Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-restricted-modules source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
** Changed in: oem-priority Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in OEM Priority Project: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in gnome-session package in Ubuntu: Invalid Status in grub2 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-430 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-435 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-440 package in Ubuntu: Invalid Status in gdm3 source package in Focal: Fix Released Status in gnome-session source package in Focal: Invalid Status in grub2 source package in Focal: Invalid Status in nvidia-graphics-drivers-390 source package in Focal: Invalid Status in nvidia-graphics-drivers-430 source package in Focal: Invalid Status in nvidia-graphics-drivers-435 source package in Focal: Invalid Status in nvidia-graphics-drivers-440 source package in Focal: Invalid Bug description: [ Impact ] In some platforms with specific Nvidia cards (with nvidia-driver-440), enable auto-login (either during installation or after installation) will fail (either stuck in gdm login screen and not able to login even typing correct password). [ Test Case ] Here are two scenario of auto login with groovy (20.10) daily build[1]: 1) Checked "Install third-party software" (e.g. nvidia-driver) with enabling "Login automatically" during installation. 2) Install groovy daily build with default options, after installation completed: 2.1) Install nvidia-driver-440 (450.66-0ubuntu1) from ubuntu-archive. 2.2) Enable "Login automatically" from system settings. Then reboot. [Expected result] System will boot into desktop environment without the login page. [Actual result] System boots to login page, and can't login to desktop environment with the correct password. [ Regression potential ] Medium, the patch comes from upstream[2] to use /dev/tty1 (instead of tty0) to prevent the auto-login user gets tty1. I did verified gdm3 from my PPA[3] and it works good. It passed the 30 times reboot stress test by using stress/reboot_30 from checkbox. [1] sha256sum: bf4359114660504ad3f6fbde5e0c3edbc67a4101e4480f576d3cbd4f59acf822 [2] https://gitlab.gnome.org/GNOME/gdm/-/commit/f843233ad4 https://gitlab.gnome.org/GNOME/gdm/-/commit/690b3c01 [3] https://launchpad.net/~os369510/+archive/ubuntu/gdm3-1845801 --- I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine:
[Kernel-packages] [Bug 1847193] Re: ath10k_pci: firmware crashed randomly (Qualcomm Atheros QCA6174 )
original bug is invalid. so mark this invalid. feel free to reopen if that's not proper. ** Changed in: oem-priority Importance: Critical => Medium ** Changed in: oem-priority Status: New => Invalid ** Changed in: linux-oem (Ubuntu) Status: New => Invalid -- 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/1847193 Title: ath10k_pci: firmware crashed randomly (Qualcomm Atheros QCA6174 ) Status in OEM Priority Project: Invalid Status in linux-oem package in Ubuntu: Invalid Bug description: the wifi failed randomly, and it seems always happens with error message: " ath10k_pci :02:00.0: firmware crashed!" 02:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32) Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter [1a56:143a] Kernel driver in use: ath10k_pci Kernel modules: ath10k_pci ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1057-oem 4.15.0-1057.66 ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18 Uname: Linux 4.15.0-1057-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 8 14:52:39 2019 InstallationDate: Installed on 2019-08-11 (57 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed-oem UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-11 (57 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: linux-firmware 1.173.9 PackageArchitecture: all ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18 Tags: bionic Uname: Linux 4.15.0-1057-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847193/+subscriptions -- Mailing list: https://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 1897567] Re: webcam not initialized
issue fixed...i think. cheese: had to select a matching resolution to enable camera. webcam resolution was higher than default. still have to resolve my no sound issue...so common, there are very many possible alsa and alsa-pulseaudio related options. On 9/28/20 12:04 PM, Kai-Heng Feng wrote: > Nothing special from dmesg. Probably a bug in Cheese. > > ** Also affects: cheese (Ubuntu) > Importance: Undecided > Status: New > -- W.C. Backus, Architect Lexington, Ky backus.will...@gmail.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/1897567 Title: webcam not initialized Status in cheese package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: ubuntu 20.04.01 clean install. thanks in advance for your attention. polite comment, no yelling here. going thru transfer and setup machine previous install ubuntu 16.04 when usb camera was working. webcam not initialized in cheese from my generic usb anivia webcam webcam device found: Bus 001 Device 006: ID 0c45:6366 Microdia USB 2.0 Camera william@william-Studio-XPS-7100:~$ dmesg | grep -i "Camera" [43532.227381] usb 1-6: Product: USB 2.0 Camera [43532.643588] uvcvideo: Found UVC 1.00 device USB 2.0 Camera (0c45:6366) [43532.670887] uvcvideo 1-6:1.0: Entity type for entity Camera 1 was not initialized! [43532.671103] input: USB 2.0 Camera: USB Camera as /devices/pci:00/:00:12.2/usb1/1-6/1-6:1.0/input/input27 [43931.982272] usb 1-6: Product: USB 2.0 Camera [43931.985021] uvcvideo: Found UVC 1.00 device USB 2.0 Camera (0c45:6366) [43932.011454] uvcvideo 1-6:1.0: Entity type for entity Camera 1 was not initialized! [43932.011667] input: USB 2.0 Camera: USB Camera as /devices/pci:00/:00:12.2/usb1/1-6/1-6:1.0/input/input28 william@william-Studio-XPS-7100:~$ ls -ltrh /dev/video* crw-rw+ 1 root video 81, 1 Sep 27 19:39 /dev/video1 crw-rw+ 1 root video 81, 0 Sep 27 19:39 /dev/video0 william@william-Studio-XPS-7100:~$ lsusb Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 005: ID 18e3:9106 Fitipower Integrated Technology Inc Mass Storage Device Bus 002 Device 006: ID 04f9:0283 Brother Industries, Ltd MFC-J825DW Bus 002 Device 007: ID 413c:2001 Dell Computer Corp. Keyboard HID Support Bus 002 Device 004: ID 413c:1001 Dell Computer Corp. Keyboard Hub Bus 002 Device 002: ID 0424:2504 Microchip Technology, Inc. (formerly SMSC) Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 002: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 006: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: william1432 F pulseaudio /dev/snd/controlC0: william1432 F pulseaudio /dev/snd/pcmC0D1p: william1432 F...m pulseaudio /dev/snd/controlC1: william1432 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Sep 28 09:03:27 2020 GvfsMonitorError: This tool has been deprecated, use 'gio mount' instead. See 'gio help mount' for more info. GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2020-09-26 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Dell Inc. Studio XPS 7100 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=ffa0aa05-8d32-4088-b80c-8afd25831dbc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 RfKill: SourcePackage: linux Symptom: storage UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 09:03:37.505: The udisks-daemon is running (name-owner :1.10). UpgradeStatus: No upgrade log present (probably fresh
[Kernel-packages] [Bug 1885730] Re: Please switch default, hwe, oem kernel flavours governor to CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y , such that advanced userspace utilities such as game-mode can be
This bug was fixed in the package linux-riscv - 5.8.0-3.3 --- linux-riscv (5.8.0-3.3) groovy; urgency=medium * groovy/linux-riscv: 5.8.0-3.3 -proposed tracker (LP: #189) * Miscellaneous Ubuntu changes - [Config] update config for CONFIG_VGACON_SOFT_SCROLLBACK [ Ubuntu: 5.8.0-20.21 ] * groovy/linux: 5.8.0-20.21 -proposed tracker (LP: #1896668) * Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices (LP: #1853277) - i2c: core: Call i2c_acpi_install_space_handler() before i2c_acpi_register_devices() * Enable LTR for endpoints behind VMD (LP: #1896598) - SAUCE: PCI/ASPM: Enable LTR for endpoints behind VMD * Remove duplicated code in ip_defrag.sh of kselftests/net (LP: #1894062) - Revert "UBUNTU: SAUCE: selftests: net: ip_defrag: modprobe missing nf_defrag_ipv6 support" * [SRU] [Focal/OEM-5.6/Groovy]Fix AMD usb host controller lost after stress S3 (LP: #1893914) - SAUCE: xhci: workaround for S3 issue on AMD SNPS 3.0 xHC * debian/rules editconfigs does not work on s390x to change s390x only configs (LP: #1863116) - [Packaging] kernelconfig -- only update/edit configurations on architectures we have compiler support * [Ubuntu 20.10] zPCI DMA tables and bitmap leak on hard unplug (PCI Event 0x0304) (LP: #1896216) - s390/pci: fix leak of DMA tables on hard unplug * md: improve IO accounting (LP: #1891151) - md: improve io stats accounting * Groovy update: v5.8.10 upstream stable release (LP: #1896078) - ARM: OMAP2+: Fix an IS_ERR() vs NULL check in _get_pwrdm() - ARM: dts: logicpd-torpedo-baseboard: Fix broken audio - ARM: dts: logicpd-som-lv-baseboard: Fix broken audio - ARM: dts: logicpd-som-lv-baseboard: Fix missing video - regulator: push allocation in regulator_ena_gpio_request() out of lock - regulator: remove superfluous lock in regulator_resolve_coupling() - ARM: dts: socfpga: fix register entry for timer3 on Arria10 - ARM: dts: omap5: Fix DSI base address and clocks - ARM: dts: ls1021a: fix QuadSPI-memory reg range - ARM: dts: imx7ulp: Correct gpio ranges - arm64: dts: imx: Add missing imx8mm-beacon-kit.dtb to build - ARM: dts: imx7d-zii-rmu2: fix rgmii phy-mode for ksz9031 phy - RDMA/rtrs-srv: Replace device_register with device_initialize and device_add - RDMA/rxe: Fix memleak in rxe_mem_init_user - RDMA/rxe: Drop pointless checks in rxe_init_ports - RDMA/rxe: Fix panic when calling kmem_cache_create() - RDMA/bnxt_re: Do not report transparent vlan from QP1 - RDMA/bnxt_re: Fix the qp table indexing - RDMA/bnxt_re: Static NQ depth allocation - RDMA/bnxt_re: Fix driver crash on unaligned PSN entry address - RDMA/bnxt_re: Remove the qp from list only if the qp destroy succeeds - drm/sun4i: add missing put_device() call in sun8i_r40_tcon_tv_set_mux() - arm64: dts: imx8mq: Fix TMU interrupt property - drm/sun4i: Fix dsi dcs long write function - scsi: qla2xxx: Fix regression on sparc64 - scsi: libsas: Set data_dir as DMA_NONE if libata marks qc as NODATA - drm/virtio: fix unblank - RDMA/core: Fix unsafe linked list traversal after failing to allocate CQ - RDMA/core: Fix reported speed and width - scsi: megaraid_sas: Don't call disable_irq from process IRQ poll - scsi: mpt3sas: Don't call disable_irq from IRQ poll handler - soundwire: fix double free of dangling pointer - Revert "kbuild: use -flive-patching when CONFIG_LIVEPATCH is enabled" - interconnect: qcom: Fix small BW votes being truncated to zero - padata: fix possible padata_works_lock deadlock - drm/sun4i: Fix DE2 YVU handling - drm/sun4i: backend: Support alpha property on lowest plane - drm/sun4i: backend: Disable alpha on the lowest plane on the A20 - KVM: arm64: Update page shift if stage 2 block mapping not supported - ARM: dts: imx6sx: fix the pad QSPI1B_SCLK mux mode for uart3 - mmc: sdhci-acpi: Clear amd_sdhci_host on reset - mmc: sdhci-msm: Add retries when all tuning phases are found valid - spi: stm32: Rate-limit the 'Communication suspended' message - btrfs: fix NULL pointer dereference after failure to create snapshot - i2c: npcm7xx: Fix timeout calculation - block: restore a specific error code in bdev_del_partition - seccomp: don't leak memory when filter install races - nvme-fabrics: allow to queue requests for live queues - spi: stm32: fix pm_runtime_get_sync() error checking - block: Set same_page to false in __bio_try_merge_page if ret is false - RDMA/rtrs-srv: Set .release function for rtrs srv device during device init - IB/isert: Fix unaligned immediate-data handling - ARM: dts: bcm: HR2: Fixed QSPI compatible string - ARM: dts: NSP: Fixed QSPI compatible string - ARM: dts: BCM5301X: Fixed QSPI compatible string - arm64: dts: ns2: Fixed QSPI compatible string - KVM:
[Kernel-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 Affecting me as well on a Lenovo X1 Gen8: $ cat /etc/issue Ubuntu 20.04.1 LTS Headset: Jabra Evolve 75 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
I have not (yet) experienced the issue you are describing, or any issues for that matter. Maybe you can remove and re-insert i2c_hid when this happens? Hopefully a fix of the GPIO driver is not too far off and will resolve the stability issues you are experiencing. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW 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 Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5
[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
Hi, My configuration : LENOVO Yoga Slim 7 15IIL05 / secure boot disabled / Linux Mint 20 I confirm that my touchpad is now working thanks to linux-image-5.9.0-rc4+_5.9.0-rc4+-1_amd64.deb A huge thank you ! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1853277 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Confirmed Status in linux-oem-5.6 source package in Focal: Confirmed Status in linux source package in Groovy: Confirmed Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: == SRU Justification == [Impact] Touchpad on sereval Lenovo ThinkBook doesn't work. [Fix] Maintain method calling ordering by calling _REG before issuing _STA, as ACPI spec suggested, for I2C ACPI devices. [Test] Positive feedback from several users. [Regression Potential] If there are some systems that rely on the wrong calling ordering then there's a regression risk. However it's rather unlikely. == Original Bug Report == This is happening on a ThinkBook 14 IML 20RV. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1848 F pulseaudio CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 11:10:52 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20RV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN21WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrCJCN21WW:bd10/10/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1891684] Re: [amdgpu] Screen flickers after resuming from suspend
This could very well be an issue with the amdgpu kernel module or the kernel itself. 20.04 uses kernel 5.4 I fixed my situation (similar) by upgrading to 20.10 (beta) which uses 5.8 packages. Now, my power management and suspend/resume actually work. My laptop (different than the nitro): Acer Aspire 5 4700U octacore APU with built-in graphics. Good luck. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891684 Title: [amdgpu] Screen flickers after resuming from suspend Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: when computer is coming out of suspension mode, i get terrible screen flickers. Only way i have worked around this is a reboot. This video card is from sapphire Nitro + SE 5700xt ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Aug 14 12:16:42 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limited Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1da2:e410] InstallationDate: Installed on 2020-06-08 (66 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=de7b87e0-cf04-4f9f-978e-3646f7e7266d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/17/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2203 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2203:bd06/17/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891684/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888703] Re: After the latest update on 7/21/20 the screen shows random black horizontal single pixel line stripes in columns about 10-20 pixels long on open windows and icons p
OK, to close this out. I manually purged 5.4.0-47, headers and modules and manually loaded up 5.4.0-48, headers and modules and everything is fine now. So I'm thinking something was broken on the previous kernels and is now working. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888703 Title: After the latest update on 7/21/20 the screen shows random black horizontal single pixel line stripes in columns about 10-20 pixels long on open windows and icons presented on the desktop. Status in linux package in Ubuntu: Confirmed Bug description: Everything else works well in the system except for this issue. See attached picture for details. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 CurrentDesktop: MATE Date: Thu Jul 23 08:14:26 2020 InstallationDate: Installed on 2019-12-08 (228 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mauro 2001 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-12-08 (229 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) MachineType: IBM 2373C96 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available Socket 1: no product info available PccardctlStatus: Socket 0: no card Socket 1: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=14567323-8391-4f6b-9169-c617d286cadb ro forcepae quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-62-generic N/A linux-backports-modules-5.3.0-62-generic N/A linux-firmware1.173.19 RfKill: 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no Tags: bionic Uname: Linux 5.3.0-62-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2007 dmi.bios.vendor: IBM dmi.bios.version: 1RETDRWW (3.23 ) dmi.board.name: 2373C96 dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn2373C96:pvrThinkPadT42p:rvnIBM:rn2373C96:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 2373C96 dmi.product.version: ThinkPad T42p dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888703/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895197] Re: amdgpu fails to load
If you can somehow do an upgrade to 20.10 beta which has kernel 5.8, I think that your issues have a good chance of being fixed. I have an Acer Aspire 5 4700U octacore APU, graphics included on-board. I was unhappy with 20.04. The upgrade to 20.10 fixed my issues: * Kernel 5.8 succeeds (where kernel 5.4 failed) detects that I need an amdgpu video driver. * Suspend followed by Resume works on 20.10; it did not on 20.04. * Power management works on 20.10; it did not on 20.04. Finally, I can close the lid, open the lid, walk away, come back - all these power mgmt functions work just as well on Linux as they did on Windoze. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895197 Title: amdgpu fails to load Status in linux package in Ubuntu: Confirmed Bug description: This happens on boot, additionally I get a black screen (the boot happens on, I have an encrypted partition which I can unlock, but there's no feedback when unlocking). nomodeset works around this problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-47-generic 5.4.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Thu Sep 10 20:06:20 2020 InstallationDate: Installed on 2020-09-09 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Google Careena ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-47-generic root=/dev/mapper/vgubuntu-root ro quiet splash text RelatedPackageVersions: linux-restricted-modules-5.4.0-47-generic N/A linux-backports-modules-5.4.0-47-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2020 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.12 dmi.board.name: Careena dmi.board.vendor: Google dmi.board.version: rev6 dmi.chassis.type: 9 dmi.chassis.vendor: Google dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.12:bd06/04/2020:svnGoogle:pnCareena:pvrrev6:rvnGoogle:rnCareena:rvrrev6:cvnGoogle:ct9:cvr: dmi.product.family: Google_Kahlee dmi.product.name: Careena dmi.product.sku: sku17 dmi.product.version: rev6 dmi.sys.vendor: Google To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867704] Re: alsa/hdmi: support nvidia mst hdmi/dp audio
Hello! We have the problem with linux-5.4.0-48 that the hdmi port (alsa_output.pci-_01_00.1.hdmi-stereo-extra1) not activ is after boot. linux-5.4.0-47 works fine. We use pulse audio. Ubuntu 20.04 linux-5.4.0-48 Active Profile: off linux-5.4.0-47 Active Profile: output:hdmi-stereo-extra1 Is it possible that this patch the reason is? -- 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/1867704 Title: alsa/hdmi: support nvidia mst hdmi/dp audio Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Bug description: This is the justification for focal: This patchset will introduce a big change on hda_jack and hda_hdmi, So I sent the patcheset to oem-b 4 months ago. After 4 months of running oem-b kernel, there is no any regression reported on this patchset, now I am backporting the patchset to our focal kernel since our oem project is waiting for the patchset to be landed to ubuntu 5.4 kernel ASAP. This patchset are already merged to mainline kernel 5.5-rc and 5.6-rc, so there is no need to send the patchset to oem-5.6 or groovy kernel. [Impact] On some LENOVO I+N machines, when setting the graphic mode to discrete, The dp/hdmi audio on the Docking Gen2 can't work with this machine + LENOVO Docking Gen2, users can't find the hdmi audio entry in the gnome-sound-setting. [Fix] Nvidia developer submit the mst audio support to 5.5-rcN and 5.6-RC1, those patches could fix this issue. [Test Case] set the machien to discrete, plug the dock gen2 to it, then boot, after booting, plug hdmi or dp to dock gen2, the hdmi or dp audio works. test other machines without Nvidia graphic or without gen2, their hdmi/dp audio still work, and check other output/input devices like headphone, microphone, they all worked as well as before. [Regression Risk] one regression possibility is the audio jacks (including analogue and hdmi) can't work anymore, that means after users plug a headphone, headset, hdmi monitor or microphone to the audio jacks or hdmi connectors, the audio driver can't detect the plugging event. But regression's possibility is very low: - this patchset was already applied to oem-b kernel for 4 months, and oem projects didn't report any regression on the patchset - I tested the testing focal kernel with this patchset on many machines, includes a dell hda audio machine, a dell dmic machine, a Lenovo I+N hda audio machine, a lenovo I+N dmic machine, a lenovo I hda audio machine, a lenovo amd hda audio machine. The audio on them all worked as well as before. This is the justification for oem-b Drop the B, so far only need to merge this patchset to OEM-B first, After the patchset is widely verified with oem-b kernel, I send the patchset to B and F then. This patchset will add support of mst audio for nvidia hdmi/dp, this patchset changes lots of common code on hda_jack and hdmi codec, so it is not easy to say it is 100% safe for other machines, but our oem project needs this patchset to be backported to ubuntu kernel, because the tight sechdule of oem project, we backport this patchset to B and OEM-B first, if the hdmi audio works well for a period of time after this patchset is merged, I will backport this patchset to focal, maybe eoan as well. [Impact] On some LENOVO I+N machines, when setting the graphic mode to discrete, The dp/hdmi audio on the Docking Gen2 can't work with this machine + LENOVO Docking Gen2 [Fix] Nvidia developer submit the mst audio support to 5.5-rcN and 5.6-RC1, those patches could fix this issue. [Test Case] set the machien to discrete, plug the dock gen2 to it, then boot, after booting, plug hdmi or dp to dock gen2, the hdmi or dp audio works. test other machines without Nvidia graphic or without gen2, their hdmi/dp audio still work. [Regression Risk] Low, those patches come from mainline kernel, I have tested those patches on the machiens with or without nvidia hdmi, and on the machines with or without docks, all worked well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1867704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
thanks @Mike Boruta (maridius)! wondered why it worked after re-install of nvidia driver, so thats the explanation now ;) what about any issues with the touchpad? not sure if something else produces my issues, but during longer usage there random stutterings, the mouse is not moved for some seconds. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW 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 Legion 5 15ARH05 dmi.modalias:
[Kernel-packages] [Bug 1882834] Re: vmxnet3: update to latest ToT
Hello Team, Can you update the status of the above patches? Is this being worked on? Can we apply below patch as well along with those mentioned above? vmxnet3: fix cksum offload issues for non-udp tunnels https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=1dac3b1bc66dc68dbb0c9f43adac71a7d0a0331a Thanks, Ronak -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882834 Title: vmxnet3: update to latest ToT Status in linux package in Ubuntu: Confirmed Bug description: This request is to port vmxnet3 patches to Ubuntu kernel. Below are the commits in order: vmxnet3: prepare for version 4 changes https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=123db31d01219a4f794f3769e7bca6649d65ecb1 vmxnet3: add support to get/set rx flow hash https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=d3a8a9e5c3b334d443e97daa59bb95c0b69f4794 vmxnet3: add geneve and vxlan tunnel offload support https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=dacce2be33124df3c71f979ac47e3d6354a41125 vmxnet3: update to version 4 https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=a31135e36eccd0d16e500d3041f23c3ece62096f vmxnet3: use correct hdr reference when packet is encapsulated https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=36432797641ff0013be9252eecf7ad1ba73171a2 vmxnet3: allow rx flow hash ops only when rss is enabled https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=11e877b2a8cfd282a1b81f9d4c594b900889a5d8 This is a request to bring Ubuntu vmxnet3 driver up to date with ToT Linux kernel. Could you apply these patches to ongoing releases? Also, could you help verify if the below commits are present in vmxnet3 of ubuntu kernel? If not, then please apply these patches before above ones. vmxnet3: set the DMA mask before the first DMA map operation https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=61aeecea40afb2b89933e27cd4adb10fc2e75cfd vmxnet3: use DMA memory barriers where required https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=f3002c1374fb2367c9d8dbb28852791ef90d2bac vmxnet3: turn off lro when rxcsum is disabled https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/drivers/net/vmxnet3?id=3dd7400b419409b1551f7f01764b1f3160feda90 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882834/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896482] Re: acpi event detection crashes
** Description changed: + = SRU Justification = + + [Impact] + + The bug causes the EC driver to fail and ACPI events are no longer + handled by Linux kernel, i.e lid close no longer triggers suspends. + + [Fix] + + Upstream commit 03e9a0e05739cf reworks ec_install_handlers to avoid + initialisation failures. + + The other three patches are prerequisite to apply 03e9a0e05739cf on + focal kernel. + + [Test] + + Tested with Lenovo ThinkPad X1 Carbon Gen 8 + + [Regression Potential] + + Low. The patches were cherry-picked from mainline kernel (two since 5.5 + and two since 5.7) + + = Original Bug Report = + Right after booting, acpi lid open/close is detected as it should be by the kernel, but some time later it crashes, so I have to manually suspend the system. The traceback is here: Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here ] Sep 20 11:35:33 laxmi kernel: [232492.303564] WARNING: CPU: 0 PID: 8302 at kernel/workqueue.c:1416 __queue_work+0x337/0x3f0 Sep 20 11:35:33 laxmi kernel: [232492.303565] Modules linked in: ccm rfcomm cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_soc_skl_hda_dsp snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_soc_dmic snd_hda_codec_generic snd_sof_pci mei_hdcp x86_pkg_temp_thermal intel_powerclamp intel_rapl_msr coretemp snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda kvm_intel snd_sof_intel_byt snd_sof_intel_ipc kvm snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine joydev crct10dif_pclmul ghash_clmulni_intel snd_hda_intel aesni_intel snd_intel_dspcfg crypto_simd iwlmvm cryptd snd_hda_codec glue_helper rapl mac80211 snd_hda_core snd_seq_midi snd_hwdep snd_seq_midi_event libarc4 intel_cstate uvcvideo snd_rawmidi i915 snd_pcm videobuf2_vmalloc input_leds thinkpad_acpi btusb videobuf2_memops serio_raw btrtl videobuf2_v4l2 snd_seq btbcm btintel nvram videobuf2_common iwlwifi processor_thermal_device bluetooth videodev Sep 20 11:35:33 laxmi kernel: [232492.303600] drm_kms_helper mc wmi_bmof i2c_algo_bit intel_rapl_common fb_sys_fops ucsi_acpi intel_wmi_thunderbolt ecdh_generic ledtrig_audio typec_ucsi mei_me syscopyarea hid_multitouch snd_seq_device sysfillrect cfg80211 ecc sysimgblt mei intel_soc_dts_iosf typec snd_timer snd soundcore int3403_thermal int340x_thermal_zone acpi_pad intel_hid int3400_thermal acpi_thermal_rel sparse_keymap mac_hid sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul nvme psmouse e1000e i2c_i801 thunderbolt intel_lpss_pci intel_lpss nvme_core idma64 virt_dma i2c_hid hid wmi video pinctrl_cannonlake pinctrl_intel Sep 20 11:35:33 laxmi kernel: [232492.303628] CPU: 0 PID: 8302 Comm: kworker/0:0 Not tainted 5.4.0-47-generic #51-Ubuntu Sep 20 11:35:33 laxmi kernel: [232492.303629] Hardware name: LENOVO 20U9001NUS/20U9001NUS, BIOS N2WET19W (1.09 ) 07/01/2020 Sep 20 11:35:33 laxmi kernel: [232492.303632] Workqueue: kec_query acpi_ec_event_processor Sep 20 11:35:33 laxmi kernel: [232492.303635] RIP: 0010:__queue_work+0x337/0x3f0 Sep 20 11:35:33 laxmi kernel: [232492.303637] Code: ff 49 8b 9d a0 00 00 00 e9 aa fd ff ff 65 8b 05 e7 59 15 6d a9 00 01 1f 00 75 0f 65 48 8b 3c 25 c0 6b 01 00 f6 47 24 20 75 25 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 0b e9 fd fd Sep 20 11:35:33 laxmi kernel: [232492.303638] RSP: 0018:b16bc0ebb8f8 EFLAGS: 00010087 Sep 20 11:35:33 laxmi kernel: [232492.303640] RAX: 9a2477432600 RBX: 0002 RCX: 0004 Sep 20 11:35:33 laxmi kernel: [232492.303641] RDX: 9a2475af4a90 RSI: 9a2475b03200 RDI: 9a2430215f00 Sep 20 11:35:33 laxmi kernel: [232492.303642] RBP: b16bc0ebb938 R08: R09: 0007 Sep 20 11:35:33 laxmi kernel: [232492.303643] R10: 9a24755ad678 R11: R12: 9a2475af4a00 Sep 20 11:35:33 laxmi kernel: [232492.303643] R13: 9a2475b03200 R14: 2000 R15: 9a2475af4a90 Sep 20 11:35:33 laxmi kernel: [232492.303645] FS: () GS:9a247740() knlGS: Sep 20 11:35:33 laxmi kernel: [232492.303646] CS: 0010 DS: ES: CR0: 80050033 Sep 20 11:35:33 laxmi kernel: [232492.303647] CR2: 00c42098b000 CR3: 00018520a003 CR4: 003606f0 Sep 20 11:35:33 laxmi kernel: [232492.303648] Call Trace: Sep 20 11:35:33 laxmi kernel: [232492.303654] ? acpi_os_release_lock+0xe/0x10 Sep 20 11:35:33 laxmi kernel: [232492.303657] queue_work_on+0x3b/0x50 Sep 20 11:35:33 laxmi kernel: [232492.303659] advance_transaction+0x2b9/0x620 Sep 20 11:35:33 laxmi kernel: [232492.303661] acpi_ec_transaction+0x16c/0x3c0 Sep 20 11:35:33 laxmi kernel: [232492.303663] acpi_ec_space_handler+0xd4/0x280 Sep 20 11:35:33 laxmi kernel: [232492.303666]
[Kernel-packages] [Bug 1896950] Re: d2020.09.22 cycle tracker
** Tags removed: block-proposed -- 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/1896950 Title: d2020.09.22 cycle tracker Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-raspi package in Ubuntu: New Status in linux-riscv package in Ubuntu: New Status in linux source package in Groovy: Confirmed Status in linux-aws source package in Groovy: New Status in linux-azure source package in Groovy: New Status in linux-gcp source package in Groovy: New Status in linux-kvm source package in Groovy: New Status in linux-oracle source package in Groovy: New Status in linux-raspi source package in Groovy: New Status in linux-riscv source package in Groovy: New Bug description: This bug is a cycle tracking bug for the d2020.09.22 development cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894378] Re: Cannot boot after updating kernel to version 5.4.0-45
@ishinberg0 I am having the same issue on an alienware aurora r6 after the upgrade to 5.4.0-48 I would like to file a new bug report for this. How do I go about generating any debug info when I have a blank screen after grub menu? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894378 Title: Cannot boot after updating kernel to version 5.4.0-45 Status in linux package in Ubuntu: Fix Released Bug description: After the kernel update from version 5.4.0-42 to version 5.4.0-45 a few days ago, the boot process is ending in a BusyBox shell. Apparently it cannot properly identify my M.2 NMVe SSD device where my root partition is. Indeed, it is not listed in /dev (precisely: nvme0 is listed in /dev, but nvme0n1 and its partitions are not). For now, I'm solving this problem by booting the previous kernel, 5.4.0-42. This works fine. Also, an earlier attempt ended in a different shell that presented the error message "Gave up on waiting for root file system device". The UUID it indicated as missing is the correct UUID of my root partition, which also appears on /etc/fstab. I tried to re-build initrd.img-5.4.0-45-generic, but to no avail. Let me also mention that in another computer with a non-M.2 SSD, kernel 5.4.0-45 boots properly. This bug seems to be the one mentioned in the following "Unix & Linux" forum question: https://unix.stackexchange.com/questions/607694/ubuntu-20-04-01-not-booting-after-kernel-update Many thanks in advance! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ami3801 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Sep 5 17:42:26 2020 HibernationDevice: RESUME=UUID=dd70dd06-717a-4acf-a85e-a9ad37cb92ea InstallationDate: Installed on 2017-10-04 (1066 days ago) InstallationMedia: Kubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: enp0s31f6 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1532:022a Razer USA, Ltd Razer Cynosa Chroma Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 480M |__ Port 8: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 8: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 8: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M MachineType: System manufacturer System Product Name ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=UUID=85262f0d-cb92-475a-8174-2d6316e199a9 ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-03 (125 days ago) dmi.bios.date: 06/20/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3807 dmi.board.asset.tag: Default string dmi.board.name: H110M-A/M.2 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3807:bd06/20/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-A/M.2:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
@alex (agolks) Just run 'sudo update-initramfs -u'; see https://unix.stackexchange.com/questions/424599/is-update-initramfs-u -needed-after-adding-or-removing-a-module-with-modprobe for more information. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW 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 Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku:
[Kernel-packages] [Bug 1002657] Re: dkms ldtarball has bad exit status
nvidia@jetson-b:~$ ls /var/lib/dkms/sxpf-dkms/2958/4.9.140-tegra/aarch64 log module nvidia@jetson-b:~$ dkms --version dkms: 2.2.1.0 nvidia@jetson-b:~$ ls /var/lib/dkms/sxpf-dkms/2958/source dkms.conf nvidia@jetson-b:~$ cat /var/lib/dkms/sxpf-dkms/2958/source/dkms.conf PACKAGE_VERSION="2958" PACKAGE_NAME="sxpf-dkms" CLEAN="make -C driver/ clean" BUILT_MODULE_NAME[0]="sxpf" BUILT_MODULE_LOCATION[0]="driver/" DEST_MODULE_LOCATION[0]="/kernel/drivers/char" MAKE[0]="unset ARCH KDIR CROSS_COMPILE; 'make' -C driver/ KSRC=$kernel_source_dir kernel_modules" AUTOINSTALL="yes" nvidia@jetson-b:~$ nvidia@jetson-b:~$ cat /var/lib/dkms/sxpf-dkms/2958/4.9.140-tegra/aarch64/log/make.log DKMS make.log for sxpf-2958 for kernel 4.9.140-tegra (aarch64) Thu Sep 24 11:37:41 EDT 2020 make[1]: Entering directory '/var/lib/dkms/sxpf/2958/build/driver' make[2]: Entering directory '/usr/src/linux-headers-4.9.140-tegra-ubuntu18.04_aarch64/kernel-4.9' CC [M] /var/lib/dkms/sxpf/2958/build/driver/sxpf_module.o CC [M] /var/lib/dkms/sxpf/2958/build/driver/sxpf_cmd_fifo.o LD [M] /var/lib/dkms/sxpf/2958/build/driver/sxpf.o Building modules, stage 2. MODPOST 1 modules CC /var/lib/dkms/sxpf/2958/build/driver/sxpf.mod.o LD [M] /var/lib/dkms/sxpf/2958/build/driver/sxpf.ko make[2]: Leaving directory '/usr/src/linux-headers-4.9.140-tegra-ubuntu18.04_aarch64/kernel-4.9' make[1]: Leaving directory '/var/lib/dkms/sxpf/2958/build/driver' nvidia@jetson-b:~$ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1002657 Title: dkms ldtarball has bad exit status Status in dkms package in Ubuntu: Confirmed Bug description: On host1 I created a tarball with the command: dkms mktarball open-vm-tools/2011.12.20 --binaries-only I then trasnfered it to host2 and ran2011.12.20 dkms ldtarball /tmp/open-vm-tools-2011.12.20-kernel3.2.0-24-generic- x86_64.dkms.tar.gz which gave the output: Loading tarball for open-vm-tools-2011.12.20 Creating /var/lib/dkms/open-vm-tools/2011.12.20/source Copying dkms.conf to /var/lib/dkms/open-vm-tools/2011.12.20/source... Loading /var/lib/dkms/open-vm-tools/2011.12.20/3.2.0-24-generic/x86_64... DKMS: ldtarball completed. But the exit status says that it failed: echo $? 1 Which creates problems when trying to script module installation. ProblemType: Bug ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Tue May 22 07:49:19 2012 Dependencies: binutils 2.22-6ubuntu1 coreutils 8.13-3ubuntu3 cpp 4:4.6.3-1ubuntu5 cpp-4.6 4.6.3-1ubuntu5 debconf 1.5.42ubuntu1 dpkg 1.16.1.2ubuntu7 gcc 4:4.6.3-1ubuntu5 gcc-4.6 4.6.3-1ubuntu5 gcc-4.6-base 4.6.3-1ubuntu5 libacl1 2.2.51-5ubuntu1 libattr1 1:2.4.46-5ubuntu1 libbz2-1.0 1.0.6-1 libc-bin 2.15-0ubuntu10 libc6 2.15-0ubuntu10 libgcc1 1:4.6.3-1ubuntu5 libgmp10 2:5.0.2+dfsg-2ubuntu1 libgomp1 4.6.3-1ubuntu5 liblzma5 5.1.1alpha+20110809-3 libmpc2 0.9-4 libmpfr4 3.1.0-3ubuntu2 libquadmath0 4.6.3-1ubuntu5 libselinux1 2.1.0-4.1ubuntu1 libstdc++6 4.6.3-1ubuntu5 make 3.81-8.1ubuntu1 module-init-tools 3.16-1ubuntu2 multiarch-support 2.15-0ubuntu10 patch 2.6.1-3 perl-base 5.14.2-6ubuntu2 tar 1.26-4ubuntu1 tzdata 2012b-1 xz-utils 5.1.1alpha+20110809-3 zlib1g 1:1.2.3.4.dfsg-3ubuntu4 DistroRelease: Ubuntu 12.04 NonfreeKernelModules: openafs Package: dkms 2.2.0.3-1ubuntu3 PackageArchitecture: all ProcEnviron: SHELL=/bin/bash TERM=screen PATH=(custom, no user) LANG=en_GB.UTF-8 LANGUAGE=en_GB: LC_CTYPE=en_GB.UTF-8 ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16 SourcePackage: dkms Tags: precise Uname: Linux 3.2.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1002657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1002657] Re: dkms ldtarball has bad exit status
strace end of output of the `dkms ldtarball ...` command :
```
...
14013 close(1) = 0
14013 close(2) = 0
14013 exit_group(0) = ?
14013 +++ exited with 0 +++
13918 <... wait4 resumed> [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) =
14013
13918 rt_sigaction(SIGINT, {sa_handler=0x555b7f3f60, sa_mask=[], sa_flags=0},
{sa_handler=0x555b7d76f8, sa_mask=[], sa_flags=0}, 8) = 0
13918 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
13918 --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=14013,
si_uid=0, si_status=0, si_utime=0, si_stime=0} ---
13918 wait4(-1, 0x7fc3f20120, WNOHANG, NULL) = -1 ECHILD (No child processes)
13918 rt_sigreturn({mask=[]}) = 0
13918 rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
13918 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
13918 exit_group(1) = ?
13918 +++ exited with 1 +++
```
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1002657
Title:
dkms ldtarball has bad exit status
Status in dkms package in Ubuntu:
Confirmed
Bug description:
On host1 I created a tarball with the command:
dkms mktarball open-vm-tools/2011.12.20 --binaries-only
I then trasnfered it to host2 and ran2011.12.20
dkms ldtarball /tmp/open-vm-tools-2011.12.20-kernel3.2.0-24-generic-
x86_64.dkms.tar.gz
which gave the output:
Loading tarball for open-vm-tools-2011.12.20
Creating /var/lib/dkms/open-vm-tools/2011.12.20/source
Copying dkms.conf to /var/lib/dkms/open-vm-tools/2011.12.20/source...
Loading /var/lib/dkms/open-vm-tools/2011.12.20/3.2.0-24-generic/x86_64...
DKMS: ldtarball completed.
But the exit status says that it failed:
echo $?
1
Which creates problems when trying to script module installation.
ProblemType: Bug
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
Date: Tue May 22 07:49:19 2012
Dependencies:
binutils 2.22-6ubuntu1
coreutils 8.13-3ubuntu3
cpp 4:4.6.3-1ubuntu5
cpp-4.6 4.6.3-1ubuntu5
debconf 1.5.42ubuntu1
dpkg 1.16.1.2ubuntu7
gcc 4:4.6.3-1ubuntu5
gcc-4.6 4.6.3-1ubuntu5
gcc-4.6-base 4.6.3-1ubuntu5
libacl1 2.2.51-5ubuntu1
libattr1 1:2.4.46-5ubuntu1
libbz2-1.0 1.0.6-1
libc-bin 2.15-0ubuntu10
libc6 2.15-0ubuntu10
libgcc1 1:4.6.3-1ubuntu5
libgmp10 2:5.0.2+dfsg-2ubuntu1
libgomp1 4.6.3-1ubuntu5
liblzma5 5.1.1alpha+20110809-3
libmpc2 0.9-4
libmpfr4 3.1.0-3ubuntu2
libquadmath0 4.6.3-1ubuntu5
libselinux1 2.1.0-4.1ubuntu1
libstdc++6 4.6.3-1ubuntu5
make 3.81-8.1ubuntu1
module-init-tools 3.16-1ubuntu2
multiarch-support 2.15-0ubuntu10
patch 2.6.1-3
perl-base 5.14.2-6ubuntu2
tar 1.26-4ubuntu1
tzdata 2012b-1
xz-utils 5.1.1alpha+20110809-3
zlib1g 1:1.2.3.4.dfsg-3ubuntu4
DistroRelease: Ubuntu 12.04
NonfreeKernelModules: openafs
Package: dkms 2.2.0.3-1ubuntu3
PackageArchitecture: all
ProcEnviron:
SHELL=/bin/bash
TERM=screen
PATH=(custom, no user)
LANG=en_GB.UTF-8
LANGUAGE=en_GB:
LC_CTYPE=en_GB.UTF-8
ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16
SourcePackage: dkms
Tags: precise
Uname: Linux 3.2.0-24-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1002657/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1002657] Re: dkms ldtarball has bad exit status
I have a case with the same issue : ``` nvidia@jetson-b:~$ sudo dkms ldtarball --archive /usr/share/sxpf-dkms/sxpf-2958.dkms.tar.gz ; echo $? Loading tarball for sxpf-dkms-2958 Creating /var/lib/dkms/sxpf-dkms/2958/source Copying dkms.conf to /var/lib/dkms/sxpf-dkms/2958/source... Loading /var/lib/dkms/sxpf-dkms/2958/4.9.140-tegra/aarch64... DKMS: ldtarball completed. 1 nvidia@jetson-b:~$ ``` and same problem than the OP. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1002657 Title: dkms ldtarball has bad exit status Status in dkms package in Ubuntu: Confirmed Bug description: On host1 I created a tarball with the command: dkms mktarball open-vm-tools/2011.12.20 --binaries-only I then trasnfered it to host2 and ran2011.12.20 dkms ldtarball /tmp/open-vm-tools-2011.12.20-kernel3.2.0-24-generic- x86_64.dkms.tar.gz which gave the output: Loading tarball for open-vm-tools-2011.12.20 Creating /var/lib/dkms/open-vm-tools/2011.12.20/source Copying dkms.conf to /var/lib/dkms/open-vm-tools/2011.12.20/source... Loading /var/lib/dkms/open-vm-tools/2011.12.20/3.2.0-24-generic/x86_64... DKMS: ldtarball completed. But the exit status says that it failed: echo $? 1 Which creates problems when trying to script module installation. ProblemType: Bug ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Tue May 22 07:49:19 2012 Dependencies: binutils 2.22-6ubuntu1 coreutils 8.13-3ubuntu3 cpp 4:4.6.3-1ubuntu5 cpp-4.6 4.6.3-1ubuntu5 debconf 1.5.42ubuntu1 dpkg 1.16.1.2ubuntu7 gcc 4:4.6.3-1ubuntu5 gcc-4.6 4.6.3-1ubuntu5 gcc-4.6-base 4.6.3-1ubuntu5 libacl1 2.2.51-5ubuntu1 libattr1 1:2.4.46-5ubuntu1 libbz2-1.0 1.0.6-1 libc-bin 2.15-0ubuntu10 libc6 2.15-0ubuntu10 libgcc1 1:4.6.3-1ubuntu5 libgmp10 2:5.0.2+dfsg-2ubuntu1 libgomp1 4.6.3-1ubuntu5 liblzma5 5.1.1alpha+20110809-3 libmpc2 0.9-4 libmpfr4 3.1.0-3ubuntu2 libquadmath0 4.6.3-1ubuntu5 libselinux1 2.1.0-4.1ubuntu1 libstdc++6 4.6.3-1ubuntu5 make 3.81-8.1ubuntu1 module-init-tools 3.16-1ubuntu2 multiarch-support 2.15-0ubuntu10 patch 2.6.1-3 perl-base 5.14.2-6ubuntu2 tar 1.26-4ubuntu1 tzdata 2012b-1 xz-utils 5.1.1alpha+20110809-3 zlib1g 1:1.2.3.4.dfsg-3ubuntu4 DistroRelease: Ubuntu 12.04 NonfreeKernelModules: openafs Package: dkms 2.2.0.3-1ubuntu3 PackageArchitecture: all ProcEnviron: SHELL=/bin/bash TERM=screen PATH=(custom, no user) LANG=en_GB.UTF-8 LANGUAGE=en_GB: LC_CTYPE=en_GB.UTF-8 ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16 SourcePackage: dkms Tags: precise Uname: Linux 3.2.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1002657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1002657] Re: dkms ldtarball has bad exit status
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dkms (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1002657 Title: dkms ldtarball has bad exit status Status in dkms package in Ubuntu: Confirmed Bug description: On host1 I created a tarball with the command: dkms mktarball open-vm-tools/2011.12.20 --binaries-only I then trasnfered it to host2 and ran2011.12.20 dkms ldtarball /tmp/open-vm-tools-2011.12.20-kernel3.2.0-24-generic- x86_64.dkms.tar.gz which gave the output: Loading tarball for open-vm-tools-2011.12.20 Creating /var/lib/dkms/open-vm-tools/2011.12.20/source Copying dkms.conf to /var/lib/dkms/open-vm-tools/2011.12.20/source... Loading /var/lib/dkms/open-vm-tools/2011.12.20/3.2.0-24-generic/x86_64... DKMS: ldtarball completed. But the exit status says that it failed: echo $? 1 Which creates problems when trying to script module installation. ProblemType: Bug ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Tue May 22 07:49:19 2012 Dependencies: binutils 2.22-6ubuntu1 coreutils 8.13-3ubuntu3 cpp 4:4.6.3-1ubuntu5 cpp-4.6 4.6.3-1ubuntu5 debconf 1.5.42ubuntu1 dpkg 1.16.1.2ubuntu7 gcc 4:4.6.3-1ubuntu5 gcc-4.6 4.6.3-1ubuntu5 gcc-4.6-base 4.6.3-1ubuntu5 libacl1 2.2.51-5ubuntu1 libattr1 1:2.4.46-5ubuntu1 libbz2-1.0 1.0.6-1 libc-bin 2.15-0ubuntu10 libc6 2.15-0ubuntu10 libgcc1 1:4.6.3-1ubuntu5 libgmp10 2:5.0.2+dfsg-2ubuntu1 libgomp1 4.6.3-1ubuntu5 liblzma5 5.1.1alpha+20110809-3 libmpc2 0.9-4 libmpfr4 3.1.0-3ubuntu2 libquadmath0 4.6.3-1ubuntu5 libselinux1 2.1.0-4.1ubuntu1 libstdc++6 4.6.3-1ubuntu5 make 3.81-8.1ubuntu1 module-init-tools 3.16-1ubuntu2 multiarch-support 2.15-0ubuntu10 patch 2.6.1-3 perl-base 5.14.2-6ubuntu2 tar 1.26-4ubuntu1 tzdata 2012b-1 xz-utils 5.1.1alpha+20110809-3 zlib1g 1:1.2.3.4.dfsg-3ubuntu4 DistroRelease: Ubuntu 12.04 NonfreeKernelModules: openafs Package: dkms 2.2.0.3-1ubuntu3 PackageArchitecture: all ProcEnviron: SHELL=/bin/bash TERM=screen PATH=(custom, no user) LANG=en_GB.UTF-8 LANGUAGE=en_GB: LC_CTYPE=en_GB.UTF-8 ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16 SourcePackage: dkms Tags: precise Uname: Linux 3.2.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1002657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Wow, thanks a lot Coiby Xu! I applied the patch and the touchpad 04F3:3186 works as expected on the 5.7.19 ubuntu mainline kernel. Please let me know if you need help developing/testing the final fix to pinctrl_amd/amd_gpio. @Azizkhan (injkgz), @Bulat (ilov3), @Paulinski (mail-izy): Please see the following guides on how to install patches and build kernel modules: https://www.thegeekstuff.com/2014/12/patch-command-examples/ https://yoursunny.com/t/2018/one-kernel-module/ https://stackoverflow.com/a/44204152 Wish you luck! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW 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
[Kernel-packages] [Bug 1548101] Re: iwlwifi kernel module failing wifi connection: Microcode SW error detected
Seems I spoke too soon, tested with Kernels 5.4.0-47 and -48, and with both firmware versions, I get the same iwlwifi errors, the card resets constantly, once or twice per minute and causes loss of connectivity and other odd delays in the system. Not sure if driver or firmware issues. 1.187 seems to be the oldest release and the firmware the card is listing is the same between both 1.187 and 1.187.3 -- 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/1548101 Title: iwlwifi kernel module failing wifi connection: Microcode SW error detected Status in linux-firmware package in Ubuntu: Confirmed Bug description: Intel Wifi 7260ac card fails WIFI connectivity with following errors in kern.log: Feb 21 19:19:04 g750 kernel: [ 2771.781401] wlan0: AP 14:cc:20:d1:76:1c changed bandwidth, new config is 2472 MHz, width 1 (2472/0 MHz) Feb 21 19:19:06 g750 kernel: [ 2773.514810] iwlwifi :03:00.0: Microcode SW error detected. Restarting 0x200. Feb 21 19:19:06 g750 kernel: [ 2773.514821] iwlwifi :03:00.0: CSR values: Feb 21 19:19:06 g750 kernel: [ 2773.514825] iwlwifi :03:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG) Feb 21 19:19:06 g750 kernel: [ 2773.514847] iwlwifi :03:00.0: CSR_HW_IF_CONFIG_REG: 0X00489204 Feb 21 19:19:06 g750 kernel: [ 2773.514869] iwlwifi :03:00.0: CSR_INT_COALESCING: 0X8000ff40 Feb 21 19:19:06 g750 kernel: [ 2773.514884] iwlwifi :03:00.0: CSR_INT: 0X Feb 21 19:19:06 g750 kernel: [ 2773.514899] iwlwifi :03:00.0: CSR_INT_MASK: 0X Feb 21 19:19:06 g750 kernel: [ 2773.514914] iwlwifi :03:00.0: CSR_FH_INT_STATUS: 0X Feb 21 19:19:06 g750 kernel: [ 2773.514929] iwlwifi :03:00.0: CSR_GPIO_IN: 0X Feb 21 19:19:06 g750 kernel: [ 2773.514944] iwlwifi :03:00.0: CSR_RESET: 0X Feb 21 19:19:06 g750 kernel: [ 2773.514960] iwlwifi :03:00.0: CSR_GP_CNTRL: 0X080403c5 Feb 21 19:19:06 g750 kernel: [ 2773.514975] iwlwifi :03:00.0: CSR_HW_REV: 0X0144 Feb 21 19:19:06 g750 kernel: [ 2773.514990] iwlwifi :03:00.0: CSR_EEPROM_REG: 0X Feb 21 19:19:06 g750 kernel: [ 2773.515006] iwlwifi :03:00.0: CSR_EEPROM_GP: 0X8000 Feb 21 19:19:06 g750 kernel: [ 2773.515021] iwlwifi :03:00.0: CSR_OTP_GP_REG: 0X803a Feb 21 19:19:06 g750 kernel: [ 2773.515036] iwlwifi :03:00.0: CSR_GIO_REG: 0X00080042 Feb 21 19:19:06 g750 kernel: [ 2773.515051] iwlwifi :03:00.0: CSR_GP_UCODE_REG: 0X Feb 21 19:19:06 g750 kernel: [ 2773.515066] iwlwifi :03:00.0: CSR_GP_DRIVER_REG: 0X Feb 21 19:19:06 g750 kernel: [ 2773.515081] iwlwifi :03:00.0: CSR_UCODE_DRV_GP1: 0X Feb 21 19:19:06 g750 kernel: [ 2773.515096] iwlwifi :03:00.0: CSR_UCODE_DRV_GP2: 0X Feb 21 19:19:06 g750 kernel: [ 2773.515111] iwlwifi :03:00.0: CSR_LED_REG: 0X0060 Feb 21 19:19:06 g750 kernel: [ 2773.515126] iwlwifi :03:00.0: CSR_DRAM_INT_TBL_REG: 0X8886e3d4 Feb 21 19:19:06 g750 kernel: [ 2773.515141] iwlwifi :03:00.0: CSR_GIO_CHICKEN_BITS: 0X27800200 Feb 21 19:19:06 g750 kernel: [ 2773.515156] iwlwifi :03:00.0: CSR_ANA_PLL_CFG: 0Xd5d5 Feb 21 19:19:06 g750 kernel: [ 2773.515171] iwlwifi :03:00.0: CSR_HW_REV_WA_REG: 0X0001001a Feb 21 19:19:06 g750 kernel: [ 2773.515186] iwlwifi :03:00.0: CSR_DBG_HPET_MEM_REG: 0X0010 Feb 21 19:19:06 g750 kernel: [ 2773.515190] iwlwifi :03:00.0: FH register values: Feb 21 19:19:06 g750 kernel: [ 2773.515217] iwlwifi :03:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X86fc6300 Feb 21 19:19:06 g750 kernel: [ 2773.515244] iwlwifi :03:00.0: FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X086fc620 Feb 21 19:19:06 g750 kernel: [ 2773.515270] iwlwifi :03:00.0: FH_RSCSR_CHNL0_WPTR: 0X0030 Feb 21 19:19:06 g750 kernel: [ 2773.515296] iwlwifi :03:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X80801114 Feb 21 19:19:06 g750 kernel: [ 2773.515323] iwlwifi :03:00.0: FH_MEM_RSSR_SHARED_CTRL_REG: 0X00fc Feb 21 19:19:06 g750 kernel: [ 2773.515350] iwlwifi :03:00.0: FH_MEM_RSSR_RX_STATUS_REG: 0X0703 Feb 21 19:19:06 g750 kernel: [ 2773.515373] iwlwifi :03:00.0: FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X Feb 21 19:19:06 g750 kernel: [ 2773.515400] iwlwifi :03:00.0: FH_TSSR_TX_STATUS_REG: 0X07ff0001 Feb 21 19:19:06 g750 kernel: [ 2773.515426] iwlwifi :03:00.0: FH_TSSR_TX_ERROR_REG: 0X Feb 21 19:19:06 g750 kernel: [
[Kernel-packages] [Bug 1845870] Re: test_verifier from ubuntu_bpf failed on B-hwe-edge 5.3 / 5.4 ARM64
Seen with Bionic linux-aws 5.4.0-1026.26~18.04.1 and 5.4.0-1025.25~18.04.1 on arm64. ** Tags added: sru-20200921 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845870 Title: test_verifier from ubuntu_bpf failed on B-hwe-edge 5.3 / 5.4 ARM64 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Issue found on a Moonshot node with B-hwe-edge 5.3 kernel, test failed with: #13/p valid read map access into a read-only array 2 FAIL retval 65507 != -29 (run 1/1) verification time 41 usec stack depth 8 processed 14 insns (limit 100) max_states_per_insn 0 total_states 1 peak_states 1 mark_read 1 This is the only test failing in this test suite: Summary: 1547 PASSED, 0 SKIPPED, 1 FAILED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1845870/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844493] Re: ubuntu_sysdig_smoke_test failed on 5.3 / 5.4 kernels
Failing with Bionic linux-aws 5.4.0-1026.26~18.04.1 and 5.4.0-1025.25~18.04.1. ** Tags added: sru-20200921 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1844493 Title: ubuntu_sysdig_smoke_test failed on 5.3 / 5.4 kernels Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Status in linux source package in Eoan: Incomplete Status in linux-aws source package in Eoan: New Status in linux-azure source package in Eoan: New Status in linux-gcp source package in Eoan: New Status in linux source package in Focal: New Status in linux-aws source package in Focal: New Status in linux-azure source package in Focal: New Status in linux-gcp source package in Focal: New Bug description: Test failed with: FAILED (trace at least 25 reads of /dev/zero by dd) FAILED (trace at least 25 writes to /dev/null by dd) Steps: sudo apt-get install git python-minimal python-yaml gdb -y git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest rm -fr autotest/client/tests ln -sf ~/autotest-client-tests autotest/client/tests AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_sysdig_smoke_test/control Test output: == sysdig smoke test to trace dd, cat, read and writes == Limiting raw capture file to 16384 blocks Try 1 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 18 Mbytes Try 2 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 22 Mbytes Try 3 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 4 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 5 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 6 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 7 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 8 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 9 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 10 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Found: 279845 sysdig events 29882 context switches 0 reads from /dev/zero by dd 0 writes to /dev/null by dd PASSED (trace at least 25 context switches) FAILED (trace at least 25 reads of /dev/zero by dd) FAILED (trace at least 25 writes to /dev/null by dd) Summary: 1 passed, 2 failed ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-10-generic 5.3.0-10.11 ProcVersionSignature: User Name 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 18 08:10 seq crw-rw 1 root audio 116, 33 Sep 18 08:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu7 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: Date: Wed Sep 18 08:18:54 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-10-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 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
Re: [Kernel-packages] [Bug 1871306] Re: No sound from internal card chtmax98090 - missing UCM2 files in alsa-ucm-conf 1.2.2, available in alsa-ucm-conf 1.2.3
Thank you for getting in touch. As I commented, I installed the alsa-ucm-conf 1.2.3 from Debian testing and it is working fine. Gabriele Il giorno lun 28 set 2020 alle ore 17:41 Sebastien Bacher < 1871...@bugs.launchpad.net> ha scritto: > Thank you for your bug report. > > Hui, is that something you would be interested to handle? Could you > perhaps do the 1.2.3 update for the Gserie as well? You cherry picked > some changes over .2 which don't seem included in .3 yet but the list of > patches would need to be reviewed in the update > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1871306 > > Title: > No sound from internal card chtmax98090 - missing UCM2 files in alsa- > ucm-conf 1.2.2, available in alsa-ucm-conf 1.2.3 > > Status in alsa-ucm-conf package in Ubuntu: > Confirmed > > Bug description: > Asus C300 (repurposed chromembook - bios flashed by Mr.Chromebox > script) - Kubuntu Focal minimal fresh installation. > The sound card is detected: I see it in the Plasma Widget, in > pavucontrol, in alsamixer and it's not muted. > I tried and add in /usr/share/alsa/ucm/chtmax98090/ the old style use > case config files: no success. > I tried and unmute speakers left and right in alsamixer: no success. > > I rapidly tested Ubuntu Mate Focal fresh install: I had exactly the > same issue. > > I'm running on the same rig Debian Bullseye, kernel 5.4: sound card > output and input are both working perfectly - I noticed that in > Kubuntu alsamixer Kubuntu when I open it I have an entry HDA IntelPCH > (the HDMI card), while in Debian I find Pulseaudio. > > > I attach the alsa-info.sh output. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: ubuntu-release-upgrader-core 1:20.04.17 > ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 > Uname: Linux 5.4.0-21-generic x86_64 > ApportVersion: 2.20.11-0ubuntu24 > Architecture: amd64 > CrashDB: ubuntu > CurrentDesktop: KDE > Date: Tue Apr 7 08:55:46 2020 > InstallationDate: Installed on 2020-04-04 (2 days ago) > InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 > (20200401) > PackageArchitecture: all > SourcePackage: ubuntu-release-upgrader > Symptom: dist-upgrade > UpgradeStatus: No upgrade log present (probably fresh install) > --- > ProblemType: Bug > ApportVersion: 2.20.11-0ubuntu24 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC1: gabriel3937 F pulseaudio >/dev/snd/controlC0: gabriel3937 F pulseaudio > CurrentDesktop: KDE > DistroRelease: Ubuntu 20.04 > InstallationDate: Installed on 2020-04-04 (3 days ago) > InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 > (20200401) > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 004: ID 8087:07dc Intel Corp. >Bus 001 Device 003: ID 13d3:5657 IMC Networks USB2.0 UVC HD Webcam >Bus 001 Device 002: ID 062a:4101 MosArt Semiconductor Corp. Wireless > Keyboard/Mouse >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: GOOGLE Quawks > Package: linux (not installed) > ProcFB: 0 i915drmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic > root=UUID=225cba91-c164-4882-95d4-4f9854a80fe9 ro quiet splash > ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 > RelatedPackageVersions: >linux-restricted-modules-5.4.0-21-generic N/A >linux-backports-modules-5.4.0-21-generic N/A >linux-firmware1.187 > Tags: focal > Uname: Linux 5.4.0-21-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: 03/17/2020 > dmi.bios.vendor: coreboot > dmi.bios.version: MrChromebox-4.11.2 > dmi.board.name: Quawks > dmi.board.vendor: GOOGLE > dmi.board.version: 1.0 > dmi.chassis.type: 9 > dmi.chassis.vendor: GOOGLE > dmi.modalias: > dmi:bvncoreboot:bvrMrChromebox-4.11.2:bd03/17/2020:svnGOOGLE:pnQuawks:pvr1.0:rvnGOOGLE:rnQuawks:rvr1.0:cvnGOOGLE:ct9:cvr: > dmi.product.name: Quawks > dmi.product.version: 1.0 > dmi.sys.vendor: GOOGLE > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1871306/+subscriptions > -- Gabriele Tettamanzi +39 3200297141 +39 3341974862 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1871306 Title: No sound from internal card chtmax98090 - missing UCM2 files in alsa- ucm-conf 1.2.2, available in alsa-ucm-conf 1.2.3 Status in alsa-ucm-conf package in Ubuntu: Confirmed Bug description: Asus C300 (repurposed chromembook - bios flashed by Mr.Chromebox script) -
[Kernel-packages] [Bug 1897602] [NEW] Xenial update: v4.4.237 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v4.4.237 upstream stable release from git://git.kernel.org/ ARM: dts: socfpga: fix register entry for timer3 on Arria10 scsi: libsas: Set data_dir as DMA_NONE if libata marks qc as NODATA drivers/net/wan/lapbether: Added needed_tailroom firestream: Fix memleak in fs_open drivers/net/wan/lapbether: Set network_header before transmitting xfs: initialize the shortform attr header padding entry drivers/net/wan/hdlc_cisco: Add hard_header_len ALSA: hda: fix a runtime pm issue in SOF when integrated GPU is disabled gcov: Disable gcov build with GCC 10 iio: adc: mcp3422: fix locking scope iio: adc: mcp3422: fix locking on error path iio:light:ltr501 Fix timestamp alignment issue. iio:accel:bmc150-accel: Fix timestamp alignment and prevent data leak. iio:accel:mma8452: Fix timestamp alignment and prevent data leak. USB: core: add helpers to retrieve endpoints staging: wlan-ng: fix out of bounds read in prism2sta_probe_usb() btrfs: fix wrong address when faulting in pages in the search ioctl scsi: target: iscsi: Fix hang in iscsit_access_np() when getting tpg->np_login_sem rbd: require global CAP_SYS_ADMIN for mapping and unmapping fbcon: remove soft scrollback code fbcon: remove now unusued 'softback_lines' cursor() argument vgacon: remove software scrollback support UBUNTU: [Config] updateconfigs for VGACON_SOFT_SCROLLBACK KVM: VMX: Don't freeze guest when event delivery causes an APIC-access exit video: fbdev: fix OOB read in vga_8planes_imageblit() USB: serial: ftdi_sio: add IDs for Xsens Mti USB converter USB: serial: option: add support for SIM7070/SIM7080/SIM7090 modules usb: Fix out of sync data toggle if a configured device is reconfigured gcov: add support for GCC 10.1 NFSv4.1 handle ERR_DELAY error reclaiming locking state on delegation recall scsi: pm8001: Fix memleak in pm8001_exec_internal_task_abort scsi: lpfc: Fix FLOGI/PLOGI receive race condition in pt2pt discovery SUNRPC: stop printk reading past end of string rapidio: Replace 'select' DMAENGINES 'with depends on' i2c: algo: pca: Reapply i2c bus settings after reset MIPS: SNI: Fix MIPS_L1_CACHE_SHIFT perf test: Free formats for perf pmu parse test fbcon: Fix user font detection test at fbcon_resize(). MIPS: SNI: Fix spurious interrupts USB: quirks: Add USB_QUIRK_IGNORE_REMOTE_WAKEUP quirk for BYD zhaoxin notebook USB: UAS: fix disconnect by unplugging a hub usblp: fix race between disconnect() and read() Input: i8042 - add Entroware Proteus EL07R4 to nomux and reset lists serial: 8250_pci: Add Realtek 816a and 816b ehci-hcd: Move include to keep CRC stable powerpc/dma: Fix dma_map_ops::get_required_mask x86/defconfig: Enable CONFIG_USB_XHCI_HCD=y Linux 4.4.237 UBUNTU: upstream stable to v4.4.237 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Xenial) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v4.4.237 upstream stable release + from git://git.kernel.org/ -v4.4.237 upstream stable release -from git://git.kernel.org/ + ARM: dts: socfpga: fix register entry for timer3 on Arria10 + scsi: libsas:
[Kernel-packages] [Bug 1897567] Re: webcam not initialized
Nothing special from dmesg. Probably a bug in Cheese. ** Also affects: cheese (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1897567 Title: webcam not initialized Status in cheese package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: ubuntu 20.04.01 clean install. thanks in advance for your attention. polite comment, no yelling here. going thru transfer and setup machine previous install ubuntu 16.04 when usb camera was working. webcam not initialized in cheese from my generic usb anivia webcam webcam device found: Bus 001 Device 006: ID 0c45:6366 Microdia USB 2.0 Camera william@william-Studio-XPS-7100:~$ dmesg | grep -i "Camera" [43532.227381] usb 1-6: Product: USB 2.0 Camera [43532.643588] uvcvideo: Found UVC 1.00 device USB 2.0 Camera (0c45:6366) [43532.670887] uvcvideo 1-6:1.0: Entity type for entity Camera 1 was not initialized! [43532.671103] input: USB 2.0 Camera: USB Camera as /devices/pci:00/:00:12.2/usb1/1-6/1-6:1.0/input/input27 [43931.982272] usb 1-6: Product: USB 2.0 Camera [43931.985021] uvcvideo: Found UVC 1.00 device USB 2.0 Camera (0c45:6366) [43932.011454] uvcvideo 1-6:1.0: Entity type for entity Camera 1 was not initialized! [43932.011667] input: USB 2.0 Camera: USB Camera as /devices/pci:00/:00:12.2/usb1/1-6/1-6:1.0/input/input28 william@william-Studio-XPS-7100:~$ ls -ltrh /dev/video* crw-rw+ 1 root video 81, 1 Sep 27 19:39 /dev/video1 crw-rw+ 1 root video 81, 0 Sep 27 19:39 /dev/video0 william@william-Studio-XPS-7100:~$ lsusb Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 005: ID 18e3:9106 Fitipower Integrated Technology Inc Mass Storage Device Bus 002 Device 006: ID 04f9:0283 Brother Industries, Ltd MFC-J825DW Bus 002 Device 007: ID 413c:2001 Dell Computer Corp. Keyboard HID Support Bus 002 Device 004: ID 413c:1001 Dell Computer Corp. Keyboard Hub Bus 002 Device 002: ID 0424:2504 Microchip Technology, Inc. (formerly SMSC) Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 002: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 006: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: william1432 F pulseaudio /dev/snd/controlC0: william1432 F pulseaudio /dev/snd/pcmC0D1p: william1432 F...m pulseaudio /dev/snd/controlC1: william1432 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Sep 28 09:03:27 2020 GvfsMonitorError: This tool has been deprecated, use 'gio mount' instead. See 'gio help mount' for more info. GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2020-09-26 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Dell Inc. Studio XPS 7100 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=ffa0aa05-8d32-4088-b80c-8afd25831dbc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 RfKill: SourcePackage: linux Symptom: storage UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 09:03:37.505: The udisks-daemon is running (name-owner :1.10). UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0NWWY0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd09/10/2010:svnDellInc.:pnStudioXPS7100:pvr:rvnDellInc.:rn0NWWY0:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name:
[Kernel-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Affecting me as well -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 Affecting me as well on Sennheiser Momentum True Wireless 2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Sennheiser Momentum True Wireless 2 -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871306] Re: No sound from internal card chtmax98090 - missing UCM2 files in alsa-ucm-conf 1.2.2, available in alsa-ucm-conf 1.2.3
Thank you for your bug report. Hui, is that something you would be interested to handle? Could you perhaps do the 1.2.3 update for the Gserie as well? You cherry picked some changes over .2 which don't seem included in .3 yet but the list of patches would need to be reviewed in the update -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1871306 Title: No sound from internal card chtmax98090 - missing UCM2 files in alsa- ucm-conf 1.2.2, available in alsa-ucm-conf 1.2.3 Status in alsa-ucm-conf package in Ubuntu: Confirmed Bug description: Asus C300 (repurposed chromembook - bios flashed by Mr.Chromebox script) - Kubuntu Focal minimal fresh installation. The sound card is detected: I see it in the Plasma Widget, in pavucontrol, in alsamixer and it's not muted. I tried and add in /usr/share/alsa/ucm/chtmax98090/ the old style use case config files: no success. I tried and unmute speakers left and right in alsamixer: no success. I rapidly tested Ubuntu Mate Focal fresh install: I had exactly the same issue. I'm running on the same rig Debian Bullseye, kernel 5.4: sound card output and input are both working perfectly - I noticed that in Kubuntu alsamixer Kubuntu when I open it I have an entry HDA IntelPCH (the HDMI card), while in Debian I find Pulseaudio. I attach the alsa-info.sh output. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.17 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Tue Apr 7 08:55:46 2020 InstallationDate: Installed on 2020-04-04 (2 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gabriel3937 F pulseaudio /dev/snd/controlC0: gabriel3937 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-04 (3 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 13d3:5657 IMC Networks USB2.0 UVC HD Webcam Bus 001 Device 002: ID 062a:4101 MosArt Semiconductor Corp. Wireless Keyboard/Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Quawks Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=225cba91-c164-4882-95d4-4f9854a80fe9 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-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: 03/17/2020 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.11.2 dmi.board.name: Quawks dmi.board.vendor: GOOGLE dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.11.2:bd03/17/2020:svnGOOGLE:pnQuawks:pvr1.0:rvnGOOGLE:rnQuawks:rvr1.0:cvnGOOGLE:ct9:cvr: dmi.product.name: Quawks dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1871306/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1548101] Re: iwlwifi kernel module failing wifi connection: Microcode SW error detected
Having the same errors here. Downgrading to linux-firmware 1.187 from 1.187.3 fixed the errors for me, appears the issue is in the updates release. ** Attachment added: "error.txt" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1548101/+attachment/5414988/+files/error.txt -- 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/1548101 Title: iwlwifi kernel module failing wifi connection: Microcode SW error detected Status in linux-firmware package in Ubuntu: Confirmed Bug description: Intel Wifi 7260ac card fails WIFI connectivity with following errors in kern.log: Feb 21 19:19:04 g750 kernel: [ 2771.781401] wlan0: AP 14:cc:20:d1:76:1c changed bandwidth, new config is 2472 MHz, width 1 (2472/0 MHz) Feb 21 19:19:06 g750 kernel: [ 2773.514810] iwlwifi :03:00.0: Microcode SW error detected. Restarting 0x200. Feb 21 19:19:06 g750 kernel: [ 2773.514821] iwlwifi :03:00.0: CSR values: Feb 21 19:19:06 g750 kernel: [ 2773.514825] iwlwifi :03:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG) Feb 21 19:19:06 g750 kernel: [ 2773.514847] iwlwifi :03:00.0: CSR_HW_IF_CONFIG_REG: 0X00489204 Feb 21 19:19:06 g750 kernel: [ 2773.514869] iwlwifi :03:00.0: CSR_INT_COALESCING: 0X8000ff40 Feb 21 19:19:06 g750 kernel: [ 2773.514884] iwlwifi :03:00.0: CSR_INT: 0X Feb 21 19:19:06 g750 kernel: [ 2773.514899] iwlwifi :03:00.0: CSR_INT_MASK: 0X Feb 21 19:19:06 g750 kernel: [ 2773.514914] iwlwifi :03:00.0: CSR_FH_INT_STATUS: 0X Feb 21 19:19:06 g750 kernel: [ 2773.514929] iwlwifi :03:00.0: CSR_GPIO_IN: 0X Feb 21 19:19:06 g750 kernel: [ 2773.514944] iwlwifi :03:00.0: CSR_RESET: 0X Feb 21 19:19:06 g750 kernel: [ 2773.514960] iwlwifi :03:00.0: CSR_GP_CNTRL: 0X080403c5 Feb 21 19:19:06 g750 kernel: [ 2773.514975] iwlwifi :03:00.0: CSR_HW_REV: 0X0144 Feb 21 19:19:06 g750 kernel: [ 2773.514990] iwlwifi :03:00.0: CSR_EEPROM_REG: 0X Feb 21 19:19:06 g750 kernel: [ 2773.515006] iwlwifi :03:00.0: CSR_EEPROM_GP: 0X8000 Feb 21 19:19:06 g750 kernel: [ 2773.515021] iwlwifi :03:00.0: CSR_OTP_GP_REG: 0X803a Feb 21 19:19:06 g750 kernel: [ 2773.515036] iwlwifi :03:00.0: CSR_GIO_REG: 0X00080042 Feb 21 19:19:06 g750 kernel: [ 2773.515051] iwlwifi :03:00.0: CSR_GP_UCODE_REG: 0X Feb 21 19:19:06 g750 kernel: [ 2773.515066] iwlwifi :03:00.0: CSR_GP_DRIVER_REG: 0X Feb 21 19:19:06 g750 kernel: [ 2773.515081] iwlwifi :03:00.0: CSR_UCODE_DRV_GP1: 0X Feb 21 19:19:06 g750 kernel: [ 2773.515096] iwlwifi :03:00.0: CSR_UCODE_DRV_GP2: 0X Feb 21 19:19:06 g750 kernel: [ 2773.515111] iwlwifi :03:00.0: CSR_LED_REG: 0X0060 Feb 21 19:19:06 g750 kernel: [ 2773.515126] iwlwifi :03:00.0: CSR_DRAM_INT_TBL_REG: 0X8886e3d4 Feb 21 19:19:06 g750 kernel: [ 2773.515141] iwlwifi :03:00.0: CSR_GIO_CHICKEN_BITS: 0X27800200 Feb 21 19:19:06 g750 kernel: [ 2773.515156] iwlwifi :03:00.0: CSR_ANA_PLL_CFG: 0Xd5d5 Feb 21 19:19:06 g750 kernel: [ 2773.515171] iwlwifi :03:00.0: CSR_HW_REV_WA_REG: 0X0001001a Feb 21 19:19:06 g750 kernel: [ 2773.515186] iwlwifi :03:00.0: CSR_DBG_HPET_MEM_REG: 0X0010 Feb 21 19:19:06 g750 kernel: [ 2773.515190] iwlwifi :03:00.0: FH register values: Feb 21 19:19:06 g750 kernel: [ 2773.515217] iwlwifi :03:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X86fc6300 Feb 21 19:19:06 g750 kernel: [ 2773.515244] iwlwifi :03:00.0: FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X086fc620 Feb 21 19:19:06 g750 kernel: [ 2773.515270] iwlwifi :03:00.0: FH_RSCSR_CHNL0_WPTR: 0X0030 Feb 21 19:19:06 g750 kernel: [ 2773.515296] iwlwifi :03:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X80801114 Feb 21 19:19:06 g750 kernel: [ 2773.515323] iwlwifi :03:00.0: FH_MEM_RSSR_SHARED_CTRL_REG: 0X00fc Feb 21 19:19:06 g750 kernel: [ 2773.515350] iwlwifi :03:00.0: FH_MEM_RSSR_RX_STATUS_REG: 0X0703 Feb 21 19:19:06 g750 kernel: [ 2773.515373] iwlwifi :03:00.0: FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X Feb 21 19:19:06 g750 kernel: [ 2773.515400] iwlwifi :03:00.0: FH_TSSR_TX_STATUS_REG: 0X07ff0001 Feb 21 19:19:06 g750 kernel: [ 2773.515426] iwlwifi :03:00.0: FH_TSSR_TX_ERROR_REG: 0X Feb 21 19:19:06 g750 kernel: [ 2773.515567] iwlwifi :03:00.0: Start IWL Error Log Dump: Feb 21 19:19:06 g750 kernel: [ 2773.515572] iwlwifi
[Kernel-packages] [Bug 1548101] Re: iwlwifi kernel module failing wifi connection: Microcode SW error detected
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-firmware (Ubuntu) Status: New => Confirmed -- 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/1548101 Title: iwlwifi kernel module failing wifi connection: Microcode SW error detected Status in linux-firmware package in Ubuntu: Confirmed Bug description: Intel Wifi 7260ac card fails WIFI connectivity with following errors in kern.log: Feb 21 19:19:04 g750 kernel: [ 2771.781401] wlan0: AP 14:cc:20:d1:76:1c changed bandwidth, new config is 2472 MHz, width 1 (2472/0 MHz) Feb 21 19:19:06 g750 kernel: [ 2773.514810] iwlwifi :03:00.0: Microcode SW error detected. Restarting 0x200. Feb 21 19:19:06 g750 kernel: [ 2773.514821] iwlwifi :03:00.0: CSR values: Feb 21 19:19:06 g750 kernel: [ 2773.514825] iwlwifi :03:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG) Feb 21 19:19:06 g750 kernel: [ 2773.514847] iwlwifi :03:00.0: CSR_HW_IF_CONFIG_REG: 0X00489204 Feb 21 19:19:06 g750 kernel: [ 2773.514869] iwlwifi :03:00.0: CSR_INT_COALESCING: 0X8000ff40 Feb 21 19:19:06 g750 kernel: [ 2773.514884] iwlwifi :03:00.0: CSR_INT: 0X Feb 21 19:19:06 g750 kernel: [ 2773.514899] iwlwifi :03:00.0: CSR_INT_MASK: 0X Feb 21 19:19:06 g750 kernel: [ 2773.514914] iwlwifi :03:00.0: CSR_FH_INT_STATUS: 0X Feb 21 19:19:06 g750 kernel: [ 2773.514929] iwlwifi :03:00.0: CSR_GPIO_IN: 0X Feb 21 19:19:06 g750 kernel: [ 2773.514944] iwlwifi :03:00.0: CSR_RESET: 0X Feb 21 19:19:06 g750 kernel: [ 2773.514960] iwlwifi :03:00.0: CSR_GP_CNTRL: 0X080403c5 Feb 21 19:19:06 g750 kernel: [ 2773.514975] iwlwifi :03:00.0: CSR_HW_REV: 0X0144 Feb 21 19:19:06 g750 kernel: [ 2773.514990] iwlwifi :03:00.0: CSR_EEPROM_REG: 0X Feb 21 19:19:06 g750 kernel: [ 2773.515006] iwlwifi :03:00.0: CSR_EEPROM_GP: 0X8000 Feb 21 19:19:06 g750 kernel: [ 2773.515021] iwlwifi :03:00.0: CSR_OTP_GP_REG: 0X803a Feb 21 19:19:06 g750 kernel: [ 2773.515036] iwlwifi :03:00.0: CSR_GIO_REG: 0X00080042 Feb 21 19:19:06 g750 kernel: [ 2773.515051] iwlwifi :03:00.0: CSR_GP_UCODE_REG: 0X Feb 21 19:19:06 g750 kernel: [ 2773.515066] iwlwifi :03:00.0: CSR_GP_DRIVER_REG: 0X Feb 21 19:19:06 g750 kernel: [ 2773.515081] iwlwifi :03:00.0: CSR_UCODE_DRV_GP1: 0X Feb 21 19:19:06 g750 kernel: [ 2773.515096] iwlwifi :03:00.0: CSR_UCODE_DRV_GP2: 0X Feb 21 19:19:06 g750 kernel: [ 2773.515111] iwlwifi :03:00.0: CSR_LED_REG: 0X0060 Feb 21 19:19:06 g750 kernel: [ 2773.515126] iwlwifi :03:00.0: CSR_DRAM_INT_TBL_REG: 0X8886e3d4 Feb 21 19:19:06 g750 kernel: [ 2773.515141] iwlwifi :03:00.0: CSR_GIO_CHICKEN_BITS: 0X27800200 Feb 21 19:19:06 g750 kernel: [ 2773.515156] iwlwifi :03:00.0: CSR_ANA_PLL_CFG: 0Xd5d5 Feb 21 19:19:06 g750 kernel: [ 2773.515171] iwlwifi :03:00.0: CSR_HW_REV_WA_REG: 0X0001001a Feb 21 19:19:06 g750 kernel: [ 2773.515186] iwlwifi :03:00.0: CSR_DBG_HPET_MEM_REG: 0X0010 Feb 21 19:19:06 g750 kernel: [ 2773.515190] iwlwifi :03:00.0: FH register values: Feb 21 19:19:06 g750 kernel: [ 2773.515217] iwlwifi :03:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X86fc6300 Feb 21 19:19:06 g750 kernel: [ 2773.515244] iwlwifi :03:00.0: FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X086fc620 Feb 21 19:19:06 g750 kernel: [ 2773.515270] iwlwifi :03:00.0: FH_RSCSR_CHNL0_WPTR: 0X0030 Feb 21 19:19:06 g750 kernel: [ 2773.515296] iwlwifi :03:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X80801114 Feb 21 19:19:06 g750 kernel: [ 2773.515323] iwlwifi :03:00.0: FH_MEM_RSSR_SHARED_CTRL_REG: 0X00fc Feb 21 19:19:06 g750 kernel: [ 2773.515350] iwlwifi :03:00.0: FH_MEM_RSSR_RX_STATUS_REG: 0X0703 Feb 21 19:19:06 g750 kernel: [ 2773.515373] iwlwifi :03:00.0: FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X Feb 21 19:19:06 g750 kernel: [ 2773.515400] iwlwifi :03:00.0: FH_TSSR_TX_STATUS_REG: 0X07ff0001 Feb 21 19:19:06 g750 kernel: [ 2773.515426] iwlwifi :03:00.0: FH_TSSR_TX_ERROR_REG: 0X Feb 21 19:19:06 g750 kernel: [ 2773.515567] iwlwifi :03:00.0: Start IWL Error Log Dump: Feb 21 19:19:06 g750 kernel: [ 2773.515572] iwlwifi :03:00.0: Status: 0x, count: 6 Feb 21 19:19:06 g750 kernel: [ 2773.515576] iwlwifi :03:00.0: Loaded firmware version: 22.24.8.0 Feb
[Kernel-packages] [Bug 1896725] Re: xenial 4.4.0-191-generic in -proposed has a regression
Or maybe that is not quite the change... I missed that the loop following, still would be using an anchor taken from the chip data... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1896725 Title: xenial 4.4.0-191-generic in -proposed has a regression Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: [Impact] The new xenial kernel in -proposed, 4.4.0-191-generic, and its derivatives, such as 4.4.0-1115-aws suffer a kernel panic on boot on AWS. I tested t2.micro and t2.medium, it happens every time. Simply install the kernel from -proposed and reboot, we get the following oops: [0.549557] BUG: unable to handle kernel paging request at ff5f3000 [0.552000] IP: [] mp_irqdomain_activate+0x5f/0xa0 [0.552000] PGD 1e0f067 PUD 1e11067 PMD 1e12067 PTE 0 [0.552000] Oops: 0002 [#1] SMP [0.552000] Modules linked in: [0.552000] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.4.0-191-generic #221-Ubuntu [0.552000] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [0.552000] task: 88010a0f ti: 88010a0f8000 task.ti: 88010a0f8000 [0.552000] RIP: 0010:[] [] mp_irqdomain_activate+0x5f/0xa0 [0.552000] RSP: :88010a0fbc48 EFLAGS: 00010086 [0.552000] RAX: 0086 RBX: 88010a1df480 RCX: [0.552000] RDX: ff5f3000 RSI: 0001 RDI: 0020c000 [0.552000] RBP: 88010a0fbc50 R08: 81ebdfd0 R09: [0.552000] R10: 0011 R11: 0009 R12: 88010ad95400 [0.552000] R13: 0001 R14: 0009 R15: 88010a1fc480 [0.552000] FS: () GS:88010b24() knlGS: [0.552000] CS: 0010 DS: ES: CR0: 80050033 [0.552000] CR2: ff5f3000 CR3: 01e0a000 CR4: 00160670 [0.552000] DR0: DR1: DR2: [0.552000] DR3: DR6: fffe0ff0 DR7: 0400 [0.552000] Stack: [0.552000] 88010ac0ba58 88010a0fbc70 810ea644 88010ac0ba00 [0.552000] 88010ac0ba58 88010a0fbca0 810e6d88 810e1009 [0.552000] 88010ac0ba00 88010ac0baa0 88010a1fc480 88010a0fbd38 [0.552000] Call Trace: [0.552000] [] irq_domain_activate_irq+0x44/0x50 [0.552000] [] irq_startup+0x38/0x90 [0.552000] [] ? vprintk_default+0x29/0x40 [0.552000] [] __setup_irq+0x5a2/0x650 [0.552000] [] ? kmem_cache_alloc_trace+0x1d4/0x1f0 [0.552000] [] ? acpi_osi_handler+0xb0/0xb0 [0.552000] [] request_threaded_irq+0xfb/0x1a0 [0.552000] [] ? acpi_osi_handler+0xb0/0xb0 [0.552000] [] ? acpi_ev_sci_dispatch+0x64/0x64 [0.552000] [] acpi_os_install_interrupt_handler+0xaa/0x100 [0.552000] [] ? acpi_sleep_proc_init+0x28/0x28 [0.552000] [] acpi_ev_install_sci_handler+0x23/0x25 [0.552000] [] acpi_ev_install_xrupt_handlers+0x1c/0x6c [0.552000] [] acpi_enable_subsystem+0x8f/0x93 [0.552000] [] acpi_init+0x8b/0x2c4 [0.552000] [] ? kasprintf+0x4e/0x70 [0.552000] [] ? acpi_sleep_proc_init+0x28/0x28 [0.552000] [] do_one_initcall+0xb5/0x200 [0.552000] [] ? parse_args+0x29a/0x4a0 [0.552000] [] kernel_init_freeable+0x177/0x218 [0.552000] [] ? rest_init+0x80/0x80 [0.552000] [] kernel_init+0xe/0xe0 [0.552000] [] ret_from_fork+0x55/0x80 [0.552000] [] ? rest_init+0x80/0x80 [0.552000] Code: 8d 1c d2 8d ba 0b 02 00 00 44 8d 51 11 42 8b 14 dd 74 ec 10 82 c1 e7 0c 48 63 ff 81 e2 ff 0f 00 00 48 81 ea 00 10 80 00 48 29 fa <44> 89 12 89 72 10 42 8b 14 dd 74 ec 10 82 83 c1 10 81 e2 ff 0f [0.552000] RIP [] mp_irqdomain_activate+0x5f/0xa0 [0.996006] RSP [0.996006] CR2: ff5f3000 [0.996006] ---[ end trace 1d0c3bd610d641a0 ]--- [1.012018] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0009 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1896725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897464] Re: Problmes with disk size with zfs
1. The specific steps or actions you took that caused you to encounter the problem. Installed 20.04 wih zfs option, allocated 64GB of drive space 2. The behavior you expected. Expected ~64GB drive space be available for use 3. The behavior you actually encountered (in as much detail as possible). In reality, see different information via Ubutnu GUI and zfs zpool GUI shows 23.6 GB drive size zpool => rpool 59G 38.7G 20.3G - - 36% 65% 1.00x ONLINE - -- 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/1897464 Title: Problmes with disk size with zfs Status in zfs-linux package in Ubuntu: Incomplete Bug description: I created a VM that has 64GB of hard drive space and I used zfs during install. Now here is what I see via desktop GUI: Disks => 69 GB Computer => 23.6 GB Two pools: zpool list NAMESIZE ALLOC FREE CKPOINT EXPANDSZ FRAGCAP DEDUPHEALTH ALTROOT bpool 1.88G 427M 1.46G- - 0%22% 1.00xONLINE - rpool59G 38.7G 20.3G- -36%65% 1.00xONLINE - As a result I run out of space. So I am confused, why is my disk size only 23.6 GB ? Definitely seems like a bug in how Computer shows the disk size. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1897464/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896725] Re: xenial 4.4.0-191-generic in -proposed has a regression
It looks like being a lucky "side-effect" of
commit 90ad9e2d91067983f3328e21b306323877e5f48a
Author: Thomas Gleixner
Date: Wed Sep 13 23:29:49 2017 +0200
x86/io_apic: Reevaluate vector configuration on activate()
This changes factors out the code that accesses the chip data, but at
the same time limits this to only do this for the ioapic chip:
static void ioapic_configure_entry(struct irq_data *irqd)
+{
+ struct mp_chip_data *mpd = irqd->chip_data;
+ struct irq_cfg *cfg = irqd_cfg(irqd);
+ struct irq_pin_list *entry;
+
+ /*
+* Only update when the parent is the vector domain, don't touch it
+* if the parent is the remapping domain. Check the installed
+* ioapic chip to verify that.
+*/
+ if (irqd->chip == _chip) {
+ mpd->entry.dest = cfg->dest_apicid;
+ mpd->entry.vector = cfg->vector;
+ }
...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1896725
Title:
xenial 4.4.0-191-generic in -proposed has a regression
Status in ubuntu-kernel-tests:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Xenial:
Confirmed
Bug description:
[Impact]
The new xenial kernel in -proposed, 4.4.0-191-generic, and its
derivatives, such as 4.4.0-1115-aws suffer a kernel panic on boot on
AWS.
I tested t2.micro and t2.medium, it happens every time. Simply install
the kernel from -proposed and reboot, we get the following oops:
[0.549557] BUG: unable to handle kernel paging request at ff5f3000
[0.552000] IP: [] mp_irqdomain_activate+0x5f/0xa0
[0.552000] PGD 1e0f067 PUD 1e11067 PMD 1e12067 PTE 0
[0.552000] Oops: 0002 [#1] SMP
[0.552000] Modules linked in:
[0.552000] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.4.0-191-generic
#221-Ubuntu
[0.552000] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
[0.552000] task: 88010a0f ti: 88010a0f8000 task.ti:
88010a0f8000
[0.552000] RIP: 0010:[] []
mp_irqdomain_activate+0x5f/0xa0
[0.552000] RSP: :88010a0fbc48 EFLAGS: 00010086
[0.552000] RAX: 0086 RBX: 88010a1df480 RCX:
[0.552000] RDX: ff5f3000 RSI: 0001 RDI:
0020c000
[0.552000] RBP: 88010a0fbc50 R08: 81ebdfd0 R09:
[0.552000] R10: 0011 R11: 0009 R12:
88010ad95400
[0.552000] R13: 0001 R14: 0009 R15:
88010a1fc480
[0.552000] FS: () GS:88010b24()
knlGS:
[0.552000] CS: 0010 DS: ES: CR0: 80050033
[0.552000] CR2: ff5f3000 CR3: 01e0a000 CR4:
00160670
[0.552000] DR0: DR1: DR2:
[0.552000] DR3: DR6: fffe0ff0 DR7:
0400
[0.552000] Stack:
[0.552000] 88010ac0ba58 88010a0fbc70 810ea644
88010ac0ba00
[0.552000] 88010ac0ba58 88010a0fbca0 810e6d88
810e1009
[0.552000] 88010ac0ba00 88010ac0baa0 88010a1fc480
88010a0fbd38
[0.552000] Call Trace:
[0.552000] [] irq_domain_activate_irq+0x44/0x50
[0.552000] [] irq_startup+0x38/0x90
[0.552000] [] ? vprintk_default+0x29/0x40
[0.552000] [] __setup_irq+0x5a2/0x650
[0.552000] [] ? kmem_cache_alloc_trace+0x1d4/0x1f0
[0.552000] [] ? acpi_osi_handler+0xb0/0xb0
[0.552000] [] request_threaded_irq+0xfb/0x1a0
[0.552000] [] ? acpi_osi_handler+0xb0/0xb0
[0.552000] [] ? acpi_ev_sci_dispatch+0x64/0x64
[0.552000] []
acpi_os_install_interrupt_handler+0xaa/0x100
[0.552000] [] ? acpi_sleep_proc_init+0x28/0x28
[0.552000] [] acpi_ev_install_sci_handler+0x23/0x25
[0.552000] [] acpi_ev_install_xrupt_handlers+0x1c/0x6c
[0.552000] [] acpi_enable_subsystem+0x8f/0x93
[0.552000] [] acpi_init+0x8b/0x2c4
[0.552000] [] ? kasprintf+0x4e/0x70
[0.552000] [] ? acpi_sleep_proc_init+0x28/0x28
[0.552000] [] do_one_initcall+0xb5/0x200
[0.552000] [] ? parse_args+0x29a/0x4a0
[0.552000] [] kernel_init_freeable+0x177/0x218
[0.552000] [] ? rest_init+0x80/0x80
[0.552000] [] kernel_init+0xe/0xe0
[0.552000] [] ret_from_fork+0x55/0x80
[0.552000] [] ? rest_init+0x80/0x80
[0.552000] Code: 8d 1c d2 8d ba 0b 02 00 00 44 8d 51 11 42 8b 14 dd 74 ec
10 82 c1 e7 0c 48 63 ff 81 e2 ff 0f 00 00 48 81 ea 00 10 80 00 48 29 fa <44> 89
12 89 72 10 42 8b 14 dd 74 ec 10 82 83 c1 10 81 e2 ff 0f
[0.552000] RIP [] mp_irqdomain_activate+0x5f/0xa0
[0.996006] RSP
[0.996006] CR2: ff5f3000
[0.996006] ---[ end trace
[Kernel-packages] [Bug 1863455] Re: USB system (mouse and keybord) are not working since kernel update to 5.3.0-26 and 5.3.0-28
Would it be possible for you to do a kernel bisection? First, find the last -rc kernel works and the first -rc kernel doesn’t work from http://kernel.ubuntu.com/~kernel-ppa/mainline/ Then, $ sudo apt build-dep linux $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git $ cd linux $ git bisect start $ git bisect good $(the working version you found) $ git bisect bad $(the non-working version found) $ make localmodconfig $ make -j`nproc` deb-pkg Install the newly built kernel, then reboot with it. If it still have the same issue, $ git bisect bad Otherwise, $ git bisect good Repeat to "make -j`nproc` deb-pkg" until you find the offending commit. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863455 Title: USB system (mouse and keybord) are not working since kernel update to 5.3.0-26 and 5.3.0-28 Status in linux package in Ubuntu: Confirmed Bug description: Since the kernel update to 5.3.0-26 it is not possible to use Ubuntu. Keyboard and mouse (both connected via USB) are not working. It looks like everything is frozen, but also ALT+PRINT REISUB is not working, so I guess the new kernel version has problems with the USB system. If I choose in GRUB an older kernel version (e.g. 5.0.0-37) everything is fine. Same problem with kernel 5.3.0-28. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Sun Feb 16 05:14:11 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.34, 5.0.0-37-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-26-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1462:7817] InstallationDate: Installed on 2019-03-19 (333 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: MSI MS-7817 ProcEnviron: LANGUAGE=de PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=bd7aadf3-2ec3-43b1-a590-407076e37c31 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V4.1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-P33 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV4.1:bd04/26/2013:svnMSI:pnMS-7817:pvr1.0:rvnMSI:rnB85M-P33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2019-03-19 (541 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: MSI MS-7817 Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user)
[Kernel-packages] [Bug 1893897] Re: [Regression] Do not initiate shutdown for EPOW_SHUTDOWN_ON_UPS event
hi Vasant, according to: - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895031 - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895328 - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893115 "powerpc/pseries: Do not initiate shutdown when system is running on UPS" has landed on proposed kernels. Please, test the kernel in -proposed (Xenial, Bionic and Focal) and update this bug with the results. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. 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/1893897 Title: [Regression] Do not initiate shutdown for EPOW_SHUTDOWN_ON_UPS event Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Released Bug description: SRU Justification: [Impact] * With commit 79872e35469b "powerpc/pseries: All events of EPOW_SYSTEM_SHUTDOWN must initiate shutdown" it was introduced that all EPOW_SYSTEM_SHUTDOWN events cause immediate shutdowns. * But on LPARs there is a user space tool (rtas_errd) that monitor for EPOW_SHUTDOWN_ON_UPS events. * Once rtas_errd gets an event it initiates a shutdown after predefined time. * Therefore immediate shutdowns must not be triggered if the system is running on UPS (means for EPOW_SHUTDOWN_ON_UPS events). [Fix] * 90a9b102eddf6a3f987d15f4454e26a2532c1c98 90a9b102eddf "powerpc/pseries: Do not initiate shutdown when system is running on UPS" [Test Case] * Setup a Power system on (D)LPAR and run it on UPS with Ubuntu 16.04 or higher (kernel 4.x is needed). * Verify that the user space tool (rtas_errd) is active and running. * Define a time for a potential shutdown in case an EPOW_SHUTDOWN_ON_UPS event occurs. * Trigger an EPOW_SHUTDOWN_ON_UPS event. * Verify if the system got shutdown immediately - or after the pre- defined time. [Regression Potential] * The regression risk is very low, because of the very limited modification in a case statement for EPOW_SHUTDOWN_ON_UPS events. * What may happen is that the system doesn't power off anymore if running on UPS due to the EPOW_SHUTDOWN_ON_UPS case changes - especially if there is a potential problem with rtas_errd that should monitor for these events and should initiate the delayed shutdown. * Other than that I cannot see much potential harm. [Other] * The patch got upstream accepted in v5.9-rc2 and already landed in groovy's kernel 'Ubuntu-5.8.0-18.19', based on the v5.8.4 upstream stable release ticket LP 1893048. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1893897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875459] Re: System hangs when loading google maps on chrome with navi AMD GPU
Hey, another ping from me: Is there any chance to get a backported fix for that issue? I would guess that this issues with current AMD hardware affects enough users to justify a backport. Currently I'm using the Ubuntu mainline kernel, but I would prefer to use the version from the standard repositories... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875459 Title: System hangs when loading google maps on chrome with navi AMD GPU Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to 20.04 from 19.10 I can reliably hang my system by loading Google Maps in Chrome and zooming in and out. After turning on DRM debugging: echo 0x1ff | sudo tee /sys/module/drm/parameters/debug I can see the following message in the kernel log: [16333.092468] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=2542114, emitted seq=2542116 [16333.092537] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process pid 0 thread pid 0 [16333.092540] [drm] GPU recovery disabled. It seems to be this upstream bug: https://gitlab.freedesktop.org/drm/amd/issues/892 I have two workarounds: * Running Chrome with AMD_DEBUG=nongg fixes the issue on 5.4.0-26 * With the latest upstream kernel, 5.6.7-050607, Chrome can load google maps with no issues. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nicholas 5696 F pulseaudio /dev/snd/controlC0: nicholas 5696 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 27 18:36:12 2020 InstallationDate: Installed on 2019-11-04 (174 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_e02uh9@/vmlinuz-5.4.0-26-generic root=ZFS=rpool/ROOT/ubuntu_e02uh9 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-26 (0 days ago) dmi.bios.date: 07/12/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.30 dmi.board.name: X570 Phantom Gaming 4 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.:bvrP1.30:bd07/12/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX570PhantomGaming4: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/1875459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897567] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1897567 Title: webcam not initialized Status in linux package in Ubuntu: Confirmed Bug description: ubuntu 20.04.01 clean install. thanks in advance for your attention. polite comment, no yelling here. going thru transfer and setup machine previous install ubuntu 16.04 when usb camera was working. webcam not initialized in cheese from my generic usb anivia webcam webcam device found: Bus 001 Device 006: ID 0c45:6366 Microdia USB 2.0 Camera william@william-Studio-XPS-7100:~$ dmesg | grep -i "Camera" [43532.227381] usb 1-6: Product: USB 2.0 Camera [43532.643588] uvcvideo: Found UVC 1.00 device USB 2.0 Camera (0c45:6366) [43532.670887] uvcvideo 1-6:1.0: Entity type for entity Camera 1 was not initialized! [43532.671103] input: USB 2.0 Camera: USB Camera as /devices/pci:00/:00:12.2/usb1/1-6/1-6:1.0/input/input27 [43931.982272] usb 1-6: Product: USB 2.0 Camera [43931.985021] uvcvideo: Found UVC 1.00 device USB 2.0 Camera (0c45:6366) [43932.011454] uvcvideo 1-6:1.0: Entity type for entity Camera 1 was not initialized! [43932.011667] input: USB 2.0 Camera: USB Camera as /devices/pci:00/:00:12.2/usb1/1-6/1-6:1.0/input/input28 william@william-Studio-XPS-7100:~$ ls -ltrh /dev/video* crw-rw+ 1 root video 81, 1 Sep 27 19:39 /dev/video1 crw-rw+ 1 root video 81, 0 Sep 27 19:39 /dev/video0 william@william-Studio-XPS-7100:~$ lsusb Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 005: ID 18e3:9106 Fitipower Integrated Technology Inc Mass Storage Device Bus 002 Device 006: ID 04f9:0283 Brother Industries, Ltd MFC-J825DW Bus 002 Device 007: ID 413c:2001 Dell Computer Corp. Keyboard HID Support Bus 002 Device 004: ID 413c:1001 Dell Computer Corp. Keyboard Hub Bus 002 Device 002: ID 0424:2504 Microchip Technology, Inc. (formerly SMSC) Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 002: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 006: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: william1432 F pulseaudio /dev/snd/controlC0: william1432 F pulseaudio /dev/snd/pcmC0D1p: william1432 F...m pulseaudio /dev/snd/controlC1: william1432 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Sep 28 09:03:27 2020 GvfsMonitorError: This tool has been deprecated, use 'gio mount' instead. See 'gio help mount' for more info. GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2020-09-26 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Dell Inc. Studio XPS 7100 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=ffa0aa05-8d32-4088-b80c-8afd25831dbc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 RfKill: SourcePackage: linux Symptom: storage UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 09:03:37.505: The udisks-daemon is running (name-owner :1.10). UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0NWWY0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd09/10/2010:svnDellInc.:pnStudioXPS7100:pvr:rvnDellInc.:rn0NWWY0:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Studio XPS 7100 dmi.sys.vendor: Dell Inc. To manage notifications about this
[Kernel-packages] [Bug 1897567] [NEW] webcam not initialized
Public bug reported: ubuntu 20.04.01 clean install. thanks in advance for your attention. polite comment, no yelling here. going thru transfer and setup machine previous install ubuntu 16.04 when usb camera was working. webcam not initialized in cheese from my generic usb anivia webcam webcam device found: Bus 001 Device 006: ID 0c45:6366 Microdia USB 2.0 Camera william@william-Studio-XPS-7100:~$ dmesg | grep -i "Camera" [43532.227381] usb 1-6: Product: USB 2.0 Camera [43532.643588] uvcvideo: Found UVC 1.00 device USB 2.0 Camera (0c45:6366) [43532.670887] uvcvideo 1-6:1.0: Entity type for entity Camera 1 was not initialized! [43532.671103] input: USB 2.0 Camera: USB Camera as /devices/pci:00/:00:12.2/usb1/1-6/1-6:1.0/input/input27 [43931.982272] usb 1-6: Product: USB 2.0 Camera [43931.985021] uvcvideo: Found UVC 1.00 device USB 2.0 Camera (0c45:6366) [43932.011454] uvcvideo 1-6:1.0: Entity type for entity Camera 1 was not initialized! [43932.011667] input: USB 2.0 Camera: USB Camera as /devices/pci:00/:00:12.2/usb1/1-6/1-6:1.0/input/input28 william@william-Studio-XPS-7100:~$ ls -ltrh /dev/video* crw-rw+ 1 root video 81, 1 Sep 27 19:39 /dev/video1 crw-rw+ 1 root video 81, 0 Sep 27 19:39 /dev/video0 william@william-Studio-XPS-7100:~$ lsusb Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 005: ID 18e3:9106 Fitipower Integrated Technology Inc Mass Storage Device Bus 002 Device 006: ID 04f9:0283 Brother Industries, Ltd MFC-J825DW Bus 002 Device 007: ID 413c:2001 Dell Computer Corp. Keyboard HID Support Bus 002 Device 004: ID 413c:1001 Dell Computer Corp. Keyboard Hub Bus 002 Device 002: ID 0424:2504 Microchip Technology, Inc. (formerly SMSC) Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 002: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 006: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: william1432 F pulseaudio /dev/snd/controlC0: william1432 F pulseaudio /dev/snd/pcmC0D1p: william1432 F...m pulseaudio /dev/snd/controlC1: william1432 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Sep 28 09:03:27 2020 GvfsMonitorError: This tool has been deprecated, use 'gio mount' instead. See 'gio help mount' for more info. GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2020-09-26 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Dell Inc. Studio XPS 7100 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=ffa0aa05-8d32-4088-b80c-8afd25831dbc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 RfKill: SourcePackage: linux Symptom: storage UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 09:03:37.505: The udisks-daemon is running (name-owner :1.10). UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0NWWY0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd09/10/2010:svnDellInc.:pnStudioXPS7100:pvr:rvnDellInc.:rn0NWWY0:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Studio XPS 7100 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1897567 Title: webcam not initialized Status in linux package in Ubuntu: New Bug description: ubuntu 20.04.01 clean install. thanks in advance for your attention. polite comment, no yelling here. going thru transfer and setup machine previous install ubuntu 16.04 when usb
[Kernel-packages] [Bug 1848883] Re: (Lenovo S130-11IGM) emmc not working in 19.04
Fixed since Linux 5.5rc3. ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1848883 Title: (Lenovo S130-11IGM) emmc not working in 19.04 Status in linux package in Ubuntu: Fix Released Bug description: Hi, I don't think this is the same issue as ; https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407 although I have read a lot of issues with emmc disks. Booting from lubuntu CD1 19.04 takes about an hour before I get to the desktop. The installer runs through to the partitioning sections and is able to see the disk, but it fails to create the partitions. The laptop has a 32gb emmc disk. There is some kind of timeout during boot on the dhpci probe. The only OS/kernel match I have got to work on this device is Lubuntu/18.04 4.15.0-20 (every single function works). After installing 18.04 there is an auto update to 4.15.0-65 but the touchpad stops working so I defaulted grub back to -20 (this failure is not caused by libinput or synaptics drivers). Neither kernels have a working wifi module but rtl8821ce install fixes this so not an issue for me. Attaching as many logs as I can grab.. please let me know and I'll happily get any other requested logging. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lubuntu1434 F pulseaudio CasperVersion: 1.405 DistroRelease: Ubuntu 19.04 IwConfig: enp0s21f0u1 no wireless extensions. lono wireless extensions. LiveMediaBuild: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81J1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 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.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 9HCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32802WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad S130-11IGM dmi.modalias: dmi:bvnLENOVO:bvr9HCN27WW:bd09/05/2019:svnLENOVO:pn81J1:pvrLenovoideapadS130-11IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0R32802WIN:cvnLENOVO:ct10:cvrLenovoideapadS130-11IGM: dmi.product.family: ideapad S130-11IGM dmi.product.name: 81J1 dmi.product.sku: LENOVO_MT_81J1_BU_idea_FM_ideapad S130-11IGM dmi.product.version: Lenovo ideapad S130-11IGM dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886277] Re: Regression on NFS: unable to handle page fault in mempool_alloc_slab
5.4.0-48-generic seems to have fixed this problem for me, 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/1886277 Title: Regression on NFS: unable to handle page fault in mempool_alloc_slab Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Bug description: On kernel 5.4.0-40-generic in focal I'm getting errors like this on several machines with different hardware in the first hour after boot: Jul 04 16:58:32 hostname kernel: BUG: unable to handle page fault for address: 9083e222e632 Jul 04 16:58:32 hostname kernel: #PF: supervisor read access in kernel mode Jul 04 16:58:32 hostname kernel: #PF: error_code(0x) - not-present page Jul 04 16:58:32 hostname kernel: PGD 3ac205067 P4D 3ac205067 PUD 0 Jul 04 16:58:32 hostname kernel: Oops: [#1] SMP NOPTI Jul 04 16:58:32 hostname kernel: CPU: 4 PID: 289 Comm: kworker/u16:4 Tainted: G OE 5.4.0-40-generic #44-Ubuntu Jul 04 16:58:32 hostname kernel: Hardware name: LENOVO 20N2CTO1WW/20N2CTO1WW, BIOS N2IET88W (1.66 ) 04/22/2020 Jul 04 16:58:32 hostname kernel: Workqueue: rpciod rpc_async_schedule [sunrpc] Jul 04 16:58:32 hostname kernel: RIP: 0010:kmem_cache_alloc+0x7e/0x230 Jul 04 16:58:32 hostname kernel: Code: 99 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 40 9d 56 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jul 04 16:58:32 hostname kernel: RSP: 0018:bc38c046fcc8 EFLAGS: 00010282 Jul 04 16:58:32 hostname kernel: RAX: 9083e222e632 RBX: RCX: 0002 Jul 04 16:58:32 hostname kernel: RDX: 0009 RSI: 00092800 RDI: 00031fb0 Jul 04 16:58:32 hostname kernel: RBP: bc38c046fcf8 R08: 90836c331fb0 R09: c1436a94 Jul 04 16:58:32 hostname kernel: R10: 908368178d2c R11: 0018 R12: 9083e222e632 Jul 04 16:58:32 hostname kernel: R13: 00092800 R14: 908367ca6140 R15: 908367ca6140 Jul 04 16:58:32 hostname kernel: FS: () GS:90836c30() knlGS: Jul 04 16:58:32 hostname kernel: CS: 0010 DS: ES: CR0: 80050033 Jul 04 16:58:32 hostname kernel: CR2: 9083e222e632 CR3: 0003ab80a003 CR4: 003606e0 Jul 04 16:58:32 hostname kernel: Call Trace: Jul 04 16:58:32 hostname kernel: ? mempool_alloc_slab+0x17/0x20 Jul 04 16:58:32 hostname kernel: mempool_alloc_slab+0x17/0x20 Jul 04 16:58:32 hostname kernel: mempool_alloc+0x64/0x180 Jul 04 16:58:32 hostname kernel: rpc_malloc+0xa1/0xb0 [sunrpc] Jul 04 16:58:32 hostname kernel: call_allocate+0xd1/0x1b0 [sunrpc] Jul 04 16:58:32 hostname kernel: ? call_refreshresult+0x100/0x100 [sunrpc] Jul 04 16:58:32 hostname kernel: __rpc_execute+0x8c/0x3a0 [sunrpc] Jul 04 16:58:32 hostname kernel: rpc_async_schedule+0x30/0x50 [sunrpc] Jul 04 16:58:32 hostname kernel: process_one_work+0x1eb/0x3b0 Jul 04 16:58:32 hostname kernel: worker_thread+0x4d/0x400 Jul 04 16:58:32 hostname kernel: kthread+0x104/0x140 Jul 04 16:58:32 hostname kernel: ? process_one_work+0x3b0/0x3b0 Jul 04 16:58:32 hostname kernel: ? kthread_park+0x90/0x90 Jul 04 16:58:32 hostname kernel: ret_from_fork+0x35/0x40 Jul 04 16:58:32 hostname kernel: Modules linked in: rfcomm rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) msr ccm cmac algif_hash algif_skcipher af_alg aufs bnep overlay nls_iso8859_1 mei_hdcp intel_rapl_msr snd_s> Jul 04 16:58:32 hostname kernel: nvram ledtrig_audio mei_me cfg80211 mei processor_thermal_device snd_seq ucsi_acpi typec_ucsi intel_rapl_common intel_soc_dts_iosf snd_seq_device typec intel_pch_thermal snd_timer snd int3403_thermal soundcore int340x_thermal_zone i> Jul 04 16:58:32 hostname kernel: pinctrl_cannonlake video pinctrl_intel Jul 04 16:58:32 hostname kernel: CR2: 9083e222e632 Jul 04 16:58:32 hostname kernel: ---[ end trace cbbaed921eb439ce ]--- Jul 04 16:58:32 hostname kernel: RIP: 0010:kmem_cache_alloc+0x7e/0x230 Jul 04 16:58:32 hostname kernel: Code: 99 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 40 9d 56 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jul 04 16:58:32 hostname kernel: RSP: 0018:bc38c046fcc8 EFLAGS: 00010282 Jul 04 16:58:32 hostname kernel: RAX: 9083e222e632 RBX: RCX: 0002 Jul 04 16:58:32 hostname kernel: RDX: 0009 RSI: 00092800 RDI: 00031fb0 Jul 04 16:58:32 hostname kernel: RBP: bc38c046fcf8 R08: 90836c331fb0 R09: c1436a94 Jul 04 16:58:32 hostname kernel: R10: 908368178d2c R11: 0018 R12:
[Kernel-packages] [Bug 1886277] Re: Regression on NFS: unable to handle page fault in mempool_alloc_slab
mainline 5.4.60-050460-generic #202008210836 did indeed fix the setup for me, I just forget to get back to you guys here. Hello Martin, It looks like the fix had not been included in the 5.4.0-47 release, but only in the following 5.4.0-48 release. Have you had the time to update to the updated kernel included with Ubuntu 20.04 and see if it has been fixed for you? On a possibly connected note, may I ask you how you are mounting the nfs share on the client? My server: Linux storage 4.19.0-9-amd64 #1 SMP Debian 4.19.118-2+deb10u1 (2020-06-07) x86_64 GNU/Linux with nfs-kernel-server 1:1.3.4-2.5+deb10u1. I switched from mounting the drives via fstab to a systemd mount after 14.04 with the following options: _netdev,sec=krb5p,vers=4.1,auto I have to use NFS4.1 with vers=4.1, because whenever I omit it, the client will still freeze when a file is being copied or cut (Ctrl+C/X). Do you run into the same issue and has this been fixed for you on 5.4.0-48 as well? Kind regards, Marc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886277 Title: Regression on NFS: unable to handle page fault in mempool_alloc_slab Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Bug description: On kernel 5.4.0-40-generic in focal I'm getting errors like this on several machines with different hardware in the first hour after boot: Jul 04 16:58:32 hostname kernel: BUG: unable to handle page fault for address: 9083e222e632 Jul 04 16:58:32 hostname kernel: #PF: supervisor read access in kernel mode Jul 04 16:58:32 hostname kernel: #PF: error_code(0x) - not-present page Jul 04 16:58:32 hostname kernel: PGD 3ac205067 P4D 3ac205067 PUD 0 Jul 04 16:58:32 hostname kernel: Oops: [#1] SMP NOPTI Jul 04 16:58:32 hostname kernel: CPU: 4 PID: 289 Comm: kworker/u16:4 Tainted: G OE 5.4.0-40-generic #44-Ubuntu Jul 04 16:58:32 hostname kernel: Hardware name: LENOVO 20N2CTO1WW/20N2CTO1WW, BIOS N2IET88W (1.66 ) 04/22/2020 Jul 04 16:58:32 hostname kernel: Workqueue: rpciod rpc_async_schedule [sunrpc] Jul 04 16:58:32 hostname kernel: RIP: 0010:kmem_cache_alloc+0x7e/0x230 Jul 04 16:58:32 hostname kernel: Code: 99 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 40 9d 56 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jul 04 16:58:32 hostname kernel: RSP: 0018:bc38c046fcc8 EFLAGS: 00010282 Jul 04 16:58:32 hostname kernel: RAX: 9083e222e632 RBX: RCX: 0002 Jul 04 16:58:32 hostname kernel: RDX: 0009 RSI: 00092800 RDI: 00031fb0 Jul 04 16:58:32 hostname kernel: RBP: bc38c046fcf8 R08: 90836c331fb0 R09: c1436a94 Jul 04 16:58:32 hostname kernel: R10: 908368178d2c R11: 0018 R12: 9083e222e632 Jul 04 16:58:32 hostname kernel: R13: 00092800 R14: 908367ca6140 R15: 908367ca6140 Jul 04 16:58:32 hostname kernel: FS: () GS:90836c30() knlGS: Jul 04 16:58:32 hostname kernel: CS: 0010 DS: ES: CR0: 80050033 Jul 04 16:58:32 hostname kernel: CR2: 9083e222e632 CR3: 0003ab80a003 CR4: 003606e0 Jul 04 16:58:32 hostname kernel: Call Trace: Jul 04 16:58:32 hostname kernel: ? mempool_alloc_slab+0x17/0x20 Jul 04 16:58:32 hostname kernel: mempool_alloc_slab+0x17/0x20 Jul 04 16:58:32 hostname kernel: mempool_alloc+0x64/0x180 Jul 04 16:58:32 hostname kernel: rpc_malloc+0xa1/0xb0 [sunrpc] Jul 04 16:58:32 hostname kernel: call_allocate+0xd1/0x1b0 [sunrpc] Jul 04 16:58:32 hostname kernel: ? call_refreshresult+0x100/0x100 [sunrpc] Jul 04 16:58:32 hostname kernel: __rpc_execute+0x8c/0x3a0 [sunrpc] Jul 04 16:58:32 hostname kernel: rpc_async_schedule+0x30/0x50 [sunrpc] Jul 04 16:58:32 hostname kernel: process_one_work+0x1eb/0x3b0 Jul 04 16:58:32 hostname kernel: worker_thread+0x4d/0x400 Jul 04 16:58:32 hostname kernel: kthread+0x104/0x140 Jul 04 16:58:32 hostname kernel: ? process_one_work+0x3b0/0x3b0 Jul 04 16:58:32 hostname kernel: ? kthread_park+0x90/0x90 Jul 04 16:58:32 hostname kernel: ret_from_fork+0x35/0x40 Jul 04 16:58:32 hostname kernel: Modules linked in: rfcomm rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) msr ccm cmac algif_hash algif_skcipher af_alg aufs bnep overlay nls_iso8859_1 mei_hdcp intel_rapl_msr snd_s> Jul 04 16:58:32 hostname kernel: nvram ledtrig_audio mei_me cfg80211 mei processor_thermal_device snd_seq ucsi_acpi typec_ucsi intel_rapl_common intel_soc_dts_iosf snd_seq_device typec intel_pch_thermal snd_timer snd int3403_thermal soundcore int340x_thermal_zone i> Jul 04 16:58:32 hostname kernel: pinctrl_cannonlake video
[Kernel-packages] [Bug 1897501] Re: HP Zbook Studio G7 boots into corrupted screen with PSR featured panel
v2 verified with focal kernel, pushing all series to ppa. Will send SRU
after verified all tomorrow.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1897501
Title:
HP Zbook Studio G7 boots into corrupted screen with PSR featured panel
Status in HWE Next:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Incomplete
Status in linux-oem-5.6 source package in Focal:
Incomplete
Status in linux source package in Groovy:
Incomplete
Status in linux-oem-5.6 source package in Groovy:
Invalid
Bug description:
Sreen divided into half after installing Focal 5.4.0-48-generic under
Power Saving/Hybrid Graphics Mode. Normal as switched to Discrete
Graphics Mode. Screenshot attached as
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897501/+attachment/5414860/+files/20200928_135412.jpg
.
With some more investigatin, https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/focal/commit/?id=d246a6cfe782
("UBUNTU: SAUCE: drm/i915: Disable PSR by default on all platforms")
for bug 1849947 is the root cause. This was landed to all Ubuntu
kernels and Ubuntu only for kernel versions 5.0 and up till v5.9
unstable currently.
It seems this panel must have PSR enabled.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-48-generic 5.4.0-48.52
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm 964 F pulseaudio
CasperMD5CheckResult: skip
Date: Mon Sep 28 01:50:54 2020
InstallationDate: Installed on 2020-09-22 (5 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200218)
MachineType: HP HP ZBook Studio G7
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic
root=UUID=ac48cfe8-5fa7-410c-ad1b-53d1e2683841 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.4.0-48-generic N/A
linux-backports-modules-5.4.0-48-generic N/A
linux-firmware1.187.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2020
dmi.bios.vendor: HP
dmi.bios.version: S91 Ver. 85.28.01
dmi.board.name: 8736
dmi.board.vendor: HP
dmi.board.version: KBC Version 14.32.03
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias:
dmi:bvnHP:bvrS91Ver.85.28.01:bd09/18/2020:svnHP:pnHPZBookStudioG7:pvr:rvnHP:rn8736:rvrKBCVersion14.32.03:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN HP ZBook
dmi.product.name: HP ZBook Studio G7
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1897501/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896419] Re: Comet Lake CPUID family:model:stepping 0x6:a5:2 (6:165:2) is not included
** Changed in: oem-priority Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1896419 Title: Comet Lake CPUID family:model:stepping 0x6:a5:2 (6:165:2) is not included Status in OEM Priority Project: Fix Committed Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: Fix Committed Status in thermald source package in Groovy: Fix Released Bug description: [Impact] * The CPUID is not included, which cause the thermald starts failed. Sep 15 17:07:00 ubuntu thermald[1089]: [WARN]Unsupported cpu model, use thermal-conf.xml file or run with --ignore-cpuid-check Sep 15 17:07:00 ubuntu thermald[1089]: [ERR]THD engine start failed Sep 15 17:07:00 ubuntu systemd[1]: thermald.service: Succeeded. * A upstream commit added missing CPUID https://github.com/intel/thermal_daemon/commit/7f2003ee911dd1c97ff74d2b84c62e10950bc9e0 [Test Case] On an affected system (Comet Lake): * $ systemctl is-active thermald active [Regression Potential] * Only new id added, no process or logic adjustment, so no regression risk. [Other Info] * The upstream bug: https://github.com/intel/thermal_daemon/issues/275 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1896419/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Can anyone provide an instruction for newbees? I made a clean install of Ubuntu 20.04 LTS, how to apply patch and make touchpad 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/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW 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 Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion
[Kernel-packages] [Bug 1897284] Re: duplicate bluetooth indicator
** Package changed: bluez (Ubuntu) => cinnamon (Ubuntu) -- 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/1897284 Title: duplicate bluetooth indicator Status in cinnamon package in Ubuntu: Confirmed Bug description: At random times I get two bluetooth indicators on the bottom of the screen instead of one. See the screenshot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Fri Sep 25 15:27:19 2020 InstallationDate: Installed on 2013-10-11 (2540 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to focal on 2020-07-12 (74 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.family: Type1Family dmi.product.name: Aspire V3-571G dmi.product.sku: Aspire V3-_0648_V2.07 dmi.product.version: V2.07 dmi.sys.vendor: Acer hciconfig: hci0:Type: Primary Bus: USB BD Address: A4:17:31:0D:4A:70 ACL MTU: 1022:8 SCO MTU: 183:5 DOWN RX bytes:1190 acl:0 sco:0 events:67 errors:0 TX bytes:1076 acl:0 sco:0 commands:67 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinnamon/+bug/1897284/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888001] Re: Focal minimal cloud image: failed to apply kernel variables
I issued the same bug. Creating the file /etc/sysctl.d/90-override.conf with the input kernel.pid_max = 32768 solved the issue for me. Thanks for the advice! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888001 Title: Focal minimal cloud image: failed to apply kernel variables Status in cloud-images: New Status in linux package in Ubuntu: Confirmed Bug description: Overview --- It appears the Focal minimal images have always shipped with a failing systemd unit: "systemd-sysctl.service" with the error "Couldn't write '4194304' to 'kernel/pid_max': Invalid argument" Expected results --- $ sudo systemctl list-units --failed --no-legend # Return no failed units Actual results --- $ sudo systemctl list-units --failed --no-legend systemd-sysctl.service loaded failed failed Apply Kernel Variables From the journal: Jul 20 12:18:53 ubuntu systemd[1]: systemd-sysctl.service: Main process exit ed, code=exited, status=1/FAILURE Jul 20 12:18:53 ubuntu systemd[1]: systemd-sysctl.service: Faile d with result 'exit-code'. Jul 20 12:18:53 ubuntu systemd[1]: Failed to start Apply Kernel Variables. Jul 20 12:18:53 ubuntu systemd-sysctl[135]: Couldn't write '4194304' to 'ker nel/pid_max': Invalid argument Steps to reproduce --- $ wget https://cloud-images.ubuntu.com/daily/server/minimal/releases/focal/release/ubuntu-20.04-minimal-cloudimg-amd64.img $ multipass launch file:///$(pwd)/ubuntu-20.04-minimal-cloudimg-amd64.img --name=focal-minimal $ multipass exec focal-minimal -- sudo systemctl list-units --failed --no-legend --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1018-kvm root=PARTUUID=4a94aad5-09c7-46a5-aa33-f2f2e03254e7 ro console=tty1 console=ttyS0 ProcVersionSignature: User Name 5.4.0-1018.18-kvm 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-1018-kvm N/A linux-backports-modules-5.4.0-1018-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1018-kvm x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True 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/cloud-images/+bug/1888001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897501] Re: HP Zbook Studio G7 boots into corrupted screen with PSR featured panel
Not shown in parse-edid, but from drm.debug=0x4 we have:
DP sink: EDID mfg 0d-ae prod-ID 19-15 quirks: 0x
DP sink: OUI 38-ec-11 dev-ID HW-rev 0.0 SW-rev 0.0 quirks 0x
So, it's possible to match by EDID manufacturer/product id.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1897501
Title:
HP Zbook Studio G7 boots into corrupted screen with PSR featured panel
Status in HWE Next:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Incomplete
Status in linux-oem-5.6 source package in Focal:
Incomplete
Status in linux source package in Groovy:
Incomplete
Status in linux-oem-5.6 source package in Groovy:
Invalid
Bug description:
Sreen divided into half after installing Focal 5.4.0-48-generic under
Power Saving/Hybrid Graphics Mode. Normal as switched to Discrete
Graphics Mode. Screenshot attached as
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897501/+attachment/5414860/+files/20200928_135412.jpg
.
With some more investigatin, https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/focal/commit/?id=d246a6cfe782
("UBUNTU: SAUCE: drm/i915: Disable PSR by default on all platforms")
for bug 1849947 is the root cause. This was landed to all Ubuntu
kernels and Ubuntu only for kernel versions 5.0 and up till v5.9
unstable currently.
It seems this panel must have PSR enabled.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-48-generic 5.4.0-48.52
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm 964 F pulseaudio
CasperMD5CheckResult: skip
Date: Mon Sep 28 01:50:54 2020
InstallationDate: Installed on 2020-09-22 (5 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200218)
MachineType: HP HP ZBook Studio G7
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic
root=UUID=ac48cfe8-5fa7-410c-ad1b-53d1e2683841 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.4.0-48-generic N/A
linux-backports-modules-5.4.0-48-generic N/A
linux-firmware1.187.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2020
dmi.bios.vendor: HP
dmi.bios.version: S91 Ver. 85.28.01
dmi.board.name: 8736
dmi.board.vendor: HP
dmi.board.version: KBC Version 14.32.03
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias:
dmi:bvnHP:bvrS91Ver.85.28.01:bd09/18/2020:svnHP:pnHPZBookStudioG7:pvr:rvnHP:rn8736:rvrKBCVersion14.32.03:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN HP ZBook
dmi.product.name: HP ZBook Studio G7
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1897501/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897464] Re: Problmes with disk size with zfs
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Thank you! ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Tags added: zfs ** Package changed: gnome-shell (Ubuntu) => zfs-linux (Ubuntu) -- 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/1897464 Title: Problmes with disk size with zfs Status in zfs-linux package in Ubuntu: Incomplete Bug description: I created a VM that has 64GB of hard drive space and I used zfs during install. Now here is what I see via desktop GUI: Disks => 69 GB Computer => 23.6 GB Two pools: zpool list NAMESIZE ALLOC FREE CKPOINT EXPANDSZ FRAGCAP DEDUPHEALTH ALTROOT bpool 1.88G 427M 1.46G- - 0%22% 1.00xONLINE - rpool59G 38.7G 20.3G- -36%65% 1.00xONLINE - As a result I run out of space. So I am confused, why is my disk size only 23.6 GB ? Definitely seems like a bug in how Computer shows the disk size. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1897464/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897550] [NEW] Groovy update: v5.8.12 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.8.12 upstream stable release from git://git.kernel.org/ Linux 5.8.12 net/mlx5e: Fix endianness when calculating pedit mask first bit net/mlx5e: Use synchronize_rcu to sync with NAPI net/mlx5e: Use RCU to protect rq->xdp_prog Revert "netns: don't disable BHs when locking "nsid_lock"" net: macb: fix for pause frame receive enable bit net: dsa: microchip: ksz8795: really set the correct number of ports net: dsa: link interfaces with the DSA master to get rid of lockdep warnings hv_netvsc: Fix hibernation for mlx5 VF driver hinic: fix rewaking txq after netif_tx_disable net/mlx5e: Fix memory leak of tunnel info when rule under multipath not ready net: ipa: fix u32_replace_bits by u32p_xxx version wireguard: peerlookup: take lock before checking hash in replace operation wireguard: noise: take lock when removing handshake entry from table net: ethernet: ti: cpsw_new: fix suspend/resume net: add __must_check to skb_put_padto() net: qrtr: check skb_put_padto() return value net: phy: Do not warn in phy_stop() on PHY_DOWN net: phy: Avoid NPD upon phy_detach() when driver is unbound net: lantiq: Disable IRQs only if NAPI gets scheduled net: lantiq: Use napi_complete_done() net: lantiq: use netif_tx_napi_add() for TX NAPI net: lantiq: Wake TX queue again bnxt_en: Protect bnxt_set_eee() and bnxt_set_pauseparam() with mutex. bnxt_en: return proper error codes in bnxt_show_temp bnxt_en: Use memcpy to copy VPD field info. net/mlx5e: TLS, Do not expose FPGA TLS counter if not supported net/mlx5e: Enable adding peer miss rules only if merged eswitch is supported tipc: use skb_unshare() instead in tipc_buf_append() tipc: fix shutdown() of connection oriented socket tipc: Fix memory leak in tipc_group_create_member() taprio: Fix allowing too small intervals nfp: use correct define to return NONE fec net: sctp: Fix IPv6 ancestor_size calc in sctp_copy_descendant net: sch_generic: aviod concurrent reset and enqueue op for lockless qdisc net: sched: initialize with 0 before setting erspan md->u net: phy: call phy_disable_interrupts() in phy_attach_direct() instead net/mlx5: Fix FTE cleanup net: ipv6: fix kconfig dependency warning for IPV6_SEG6_HMAC net: Fix bridge enslavement failure net: dsa: rtl8366: Properly clear member config net: DCB: Validate DCB_ATTR_DCB_BUFFER argument net: bridge: br_vlan_get_pvid_rcu() should dereference the VLAN group under RCU ipv6: avoid lockdep issue in fib6_del() ipv4: Update exception handling for multipath routes via same device ipv4: Initialize flowi4_multipath_hash in data path ip: fix tos reflection in ack and reset packets hinic: bump up the timeout of SET_FUNC_STATE cmd hdlc_ppp: add range checks in ppp_cp_parse_cr() geneve: add transport ports in route lookup for geneve cxgb4: Fix offset when clearing filter byte counters cxgb4: fix memory leak during module unload bnxt_en: Fix NULL ptr dereference crash in bnxt_fw_reset_task() bnxt_en: Avoid sending firmware messages when AER error is detected. act_ife: load meta modules before tcf_idr_check_alloc() ibmvnic: add missing parenthesis in do_reset() ibmvnic fix NULL tx_pools and rx_tools issue at do_reset ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Groovy) Importance: Undecided Status: Confirmed ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: 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/1897550 Title: Groovy update: v5.8.12 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Groovy: Confirmed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.8.12 upstream stable release from git://git.kernel.org/ Linux 5.8.12 net/mlx5e: Fix endianness when
[Kernel-packages] [Bug 1897464] [NEW] Problmes with disk size with zfs
You have been subscribed to a public bug: I created a VM that has 64GB of hard drive space and I used zfs during install. Now here is what I see via desktop GUI: Disks => 69 GB Computer => 23.6 GB Two pools: zpool list NAMESIZE ALLOC FREE CKPOINT EXPANDSZ FRAGCAP DEDUPHEALTH ALTROOT bpool 1.88G 427M 1.46G- - 0%22% 1.00xONLINE - rpool59G 38.7G 20.3G- -36%65% 1.00xONLINE - As a result I run out of space. So I am confused, why is my disk size only 23.6 GB ? Definitely seems like a bug in how Computer shows the disk size. ** Affects: zfs-linux (Ubuntu) Importance: Low Status: Incomplete ** Tags: zfs -- Problmes with disk size with zfs https://bugs.launchpad.net/bugs/1897464 You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863455] Re: USB system (mouse and keybord) are not working since kernel update to 5.3.0-26 and 5.3.0-28
If I connect a wired mouse the mouse is working, so USB is not the problem. The new kernels just do not accept the logitech wireless mouse and keyboard (K520 and M310) but the old kernel does. Hopefully the bug can be found and fixed soon. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863455 Title: USB system (mouse and keybord) are not working since kernel update to 5.3.0-26 and 5.3.0-28 Status in linux package in Ubuntu: Confirmed Bug description: Since the kernel update to 5.3.0-26 it is not possible to use Ubuntu. Keyboard and mouse (both connected via USB) are not working. It looks like everything is frozen, but also ALT+PRINT REISUB is not working, so I guess the new kernel version has problems with the USB system. If I choose in GRUB an older kernel version (e.g. 5.0.0-37) everything is fine. Same problem with kernel 5.3.0-28. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Sun Feb 16 05:14:11 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.34, 5.0.0-37-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-26-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1462:7817] InstallationDate: Installed on 2019-03-19 (333 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: MSI MS-7817 ProcEnviron: LANGUAGE=de PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=bd7aadf3-2ec3-43b1-a590-407076e37c31 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V4.1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-P33 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV4.1:bd04/26/2013:svnMSI:pnMS-7817:pvr1.0:rvnMSI:rnB85M-P33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2019-03-19 (541 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: MSI MS-7817 Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=bd7aadf3-2ec3-43b1-a590-407076e37c31 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-47.51~18.04.1-generic 5.4.55 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as
[Kernel-packages] [Bug 1895615] Re: Backlight adjustment doesn't work on Google Pixel Slate
That's great. Let's wait for the good news! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895615 Title: Backlight adjustment doesn't work on Google Pixel Slate Status in linux package in Ubuntu: Confirmed Bug description: The Pixel Slate/nocturne backlight does not work due to DPCD logic not identifying the DPCD backlight connection since there is no PWM on the nocturne or eve devices. ChromeOS documentation of disconnected PWM: https://chromium- review.googlesource.com/c/chromiumos/overlays/board-overlays/+/1171922 Discussion of issue & solution: https://github.com/EmbeddedAndroid /linux-eve/issues/2#issuecomment-561382927 This can be fixed with a simple patch which I have applied successfully to mainline 5.9-rc5: https://gist.github.com/satmandu/d6c2192f66cd14525049fd34d356d71d Luckily the Ubuntu kernel patches set i915.enable_psr=0 which keeps Panel Self Refresh from dimming the backlight at boot, but that isn't even needed for this device once the backlight is hooked up correctly. (As a bonus the keyboard backlight also starts working properly at boot.) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-lowlatency 5.8.0.18.22 ProcVersionSignature: Ubuntu 5.8.0-18.19-lowlatency 5.8.4 Uname: Linux 5.8.0-18-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Mon Sep 14 23:52:45 2020 InstallationDate: Installed on 2020-08-24 (21 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200728) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 18d1:5030 Google Inc. Hammer Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Google Nocturne ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-lowlatency root=UUID=90e26b2a-aaad-4576-8e90-1962b97d4e96 ro fsck.repair=yes fsck.mode=force PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-18-lowlatency N/A linux-backports-modules-5.8.0-18-lowlatency N/A linux-firmware 1.190 SourcePackage: linux StagingDrivers: ipu3_imgu UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2019 dmi.bios.release: 4.0 dmi.bios.vendor: coreboot dmi.bios.version: Google_Nocturne.10984.90.0 dmi.board.name: Nocturne dmi.board.vendor: Google dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Google dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvrGoogle_Nocturne.10984.90.0:bd06/04/2019:br4.0:efr0.0:svnGoogle:pnNocturne:pvr1.0:rvnGoogle:rnNocturne:rvr1.0:cvnGoogle:ct3:cvr: dmi.product.family: Google_Nocturne dmi.product.name: Nocturne dmi.product.version: 1.0 dmi.sys.vendor: Google To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895615/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896950] Re: d2020.09.22 cycle tracker
** Tags added: block-proposed--linux-riscv--1.2 -- 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/1896950 Title: d2020.09.22 cycle tracker Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-raspi package in Ubuntu: New Status in linux-riscv package in Ubuntu: New Status in linux source package in Groovy: Confirmed Status in linux-aws source package in Groovy: New Status in linux-azure source package in Groovy: New Status in linux-gcp source package in Groovy: New Status in linux-kvm source package in Groovy: New Status in linux-oracle source package in Groovy: New Status in linux-raspi source package in Groovy: New Status in linux-riscv source package in Groovy: New Bug description: This bug is a cycle tracking bug for the d2020.09.22 development cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897501] Re: HP Zbook Studio G7 boots into corrupted screen with PSR featured panel
Have a PoC PPA in
https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1897501 based on DMI
match on product name. But while we're still investigating the finest
way to match the problematic system, set to INCOMPLETE until ready.
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Incomplete
** Changed in: linux (Ubuntu Groovy)
Status: In Progress => Incomplete
** Changed in: linux-oem-5.6 (Ubuntu Focal)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1897501
Title:
HP Zbook Studio G7 boots into corrupted screen with PSR featured panel
Status in HWE Next:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Incomplete
Status in linux-oem-5.6 source package in Focal:
Incomplete
Status in linux source package in Groovy:
Incomplete
Status in linux-oem-5.6 source package in Groovy:
Invalid
Bug description:
Sreen divided into half after installing Focal 5.4.0-48-generic under
Power Saving/Hybrid Graphics Mode. Normal as switched to Discrete
Graphics Mode. Screenshot attached as
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897501/+attachment/5414860/+files/20200928_135412.jpg
.
With some more investigatin, https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/focal/commit/?id=d246a6cfe782
("UBUNTU: SAUCE: drm/i915: Disable PSR by default on all platforms")
for bug 1849947 is the root cause. This was landed to all Ubuntu
kernels and Ubuntu only for kernel versions 5.0 and up till v5.9
unstable currently.
It seems this panel must have PSR enabled.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-48-generic 5.4.0-48.52
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm 964 F pulseaudio
CasperMD5CheckResult: skip
Date: Mon Sep 28 01:50:54 2020
InstallationDate: Installed on 2020-09-22 (5 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200218)
MachineType: HP HP ZBook Studio G7
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic
root=UUID=ac48cfe8-5fa7-410c-ad1b-53d1e2683841 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.4.0-48-generic N/A
linux-backports-modules-5.4.0-48-generic N/A
linux-firmware1.187.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2020
dmi.bios.vendor: HP
dmi.bios.version: S91 Ver. 85.28.01
dmi.board.name: 8736
dmi.board.vendor: HP
dmi.board.version: KBC Version 14.32.03
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias:
dmi:bvnHP:bvrS91Ver.85.28.01:bd09/18/2020:svnHP:pnHPZBookStudioG7:pvr:rvnHP:rn8736:rvrKBCVersion14.32.03:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN HP ZBook
dmi.product.name: HP ZBook Studio G7
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1897501/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897501] Re: HP Zbook Studio G7 boots into corrupted screen with PSR featured panel
$ sudo get-edid | parse-edid
This is read-edid version 3.0.2. Prepare for some fun.
Attempting to use i2c interface
No EDID on bus 0
No EDID on bus 1
No EDID on bus 2
No EDID on bus 3
No EDID on bus 4
No EDID on bus 5
No EDID on bus 6
No EDID on bus 8
1 potential busses found: 7
128-byte EDID successfully retrieved from i2c bus 7
Looks like i2c was successful. Have a good day.
Checksum Correct
Section "Monitor"
Identifier ""
ModelName ""
VendorName "CMN"
# Monitor Manufactured week 38 of 2019
# EDID version 1.4
# Digital Display
DisplaySize 340 190
Gamma 2.20
Option "DPMS" "false"
Modeline"Mode 0" 152.84 1920 1968 2000 2250 1080 1083 1088 1132
+hsync -vsync
Modeline"Mode 1" 101.89 1920 1968 2000 2250 1080 1083 1088 1132
+hsync -vsync
EndSection
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1897501
Title:
HP Zbook Studio G7 boots into corrupted screen with PSR featured panel
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
In Progress
Status in linux-oem-5.6 source package in Focal:
In Progress
Status in linux source package in Groovy:
In Progress
Status in linux-oem-5.6 source package in Groovy:
Invalid
Bug description:
Sreen divided into half after installing Focal 5.4.0-48-generic under
Power Saving/Hybrid Graphics Mode. Normal as switched to Discrete
Graphics Mode. Screenshot attached as
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897501/+attachment/5414860/+files/20200928_135412.jpg
.
With some more investigatin, https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/focal/commit/?id=d246a6cfe782
("UBUNTU: SAUCE: drm/i915: Disable PSR by default on all platforms")
for bug 1849947 is the root cause. This was landed to all Ubuntu
kernels and Ubuntu only for kernel versions 5.0 and up till v5.9
unstable currently.
It seems this panel must have PSR enabled.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-48-generic 5.4.0-48.52
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm 964 F pulseaudio
CasperMD5CheckResult: skip
Date: Mon Sep 28 01:50:54 2020
InstallationDate: Installed on 2020-09-22 (5 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200218)
MachineType: HP HP ZBook Studio G7
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic
root=UUID=ac48cfe8-5fa7-410c-ad1b-53d1e2683841 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.4.0-48-generic N/A
linux-backports-modules-5.4.0-48-generic N/A
linux-firmware1.187.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2020
dmi.bios.vendor: HP
dmi.bios.version: S91 Ver. 85.28.01
dmi.board.name: 8736
dmi.board.vendor: HP
dmi.board.version: KBC Version 14.32.03
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias:
dmi:bvnHP:bvrS91Ver.85.28.01:bd09/18/2020:svnHP:pnHPZBookStudioG7:pvr:rvnHP:rn8736:rvrKBCVersion14.32.03:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN HP ZBook
dmi.product.name: HP ZBook Studio G7
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1897501/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897508] [NEW] Fix headset jack detection on Dell UFF desktops
Public bug reported: [Impact] Headset jack detection doesn't work on Dell UFF desktops. MSI interrupt doesn't work anymore if the HDA device ever gets runtime-suspended. [Fix] Disable runtime suspend on HDA device. This is a temporary workaround, we are still finding the root cause. [Test] With the patch applied, jack detection always works. [Regression Potential] This fix will not enable HDA runtime suspend by defualt, so for systems that doesn't use TLP or `powertop --auto-tune`, this will slightly increase power consumption. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-oem-5.6 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.6 (Ubuntu Focal) Importance: Medium Status: Confirmed ** Tags: oem-priority originate-from-1893610 somerville ** Package changed: linux (Ubuntu) => linux-oem-5.6 (Ubuntu) ** Also affects: linux-oem-5.6 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-oem-5.6 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-5.6 (Ubuntu Focal) Importance: Undecided => Medium ** Tags added: oem-priority originate-from-1893610 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1897508 Title: Fix headset jack detection on Dell UFF desktops Status in HWE Next: New Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux-oem-5.6 source package in Focal: Confirmed Bug description: [Impact] Headset jack detection doesn't work on Dell UFF desktops. MSI interrupt doesn't work anymore if the HDA device ever gets runtime-suspended. [Fix] Disable runtime suspend on HDA device. This is a temporary workaround, we are still finding the root cause. [Test] With the patch applied, jack detection always works. [Regression Potential] This fix will not enable HDA runtime suspend by defualt, so for systems that doesn't use TLP or `powertop --auto-tune`, this will slightly increase power consumption. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1897508/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896726] Re: [UBUNTU 20.04.1] qemu (secure guest) crash due to gup_fast / dynamic page table folding issue
I took this from "linux-next" (where it was tagged with 'next-20200923') as:
~/linux-next$ git show a02b55ea66b9
commit a02b55ea66b9257744528da609a26279152a3bc3
Author: Vasily Gorbik
Date: Wed Sep 23 09:49:28 2020 +1000
mm/gup: fix gup_fast with dynamic page table folding
Currently to make sure that every page table entry is read just once
gup_fast walks perform READ_ONCE and pass pXd value down to the next
gup_pXd_range function by value e.g.:
static int gup_pud_range(p4d_t p4d, unsigned long addr, unsigned long end,
unsigned int flags, struct page **pages, int *nr)
...
and built a patched groovy and a patched focal kernel, available here:
https://people.canonical.com/~fheimes/lp1896726/
Do you have a chance giving these a try?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1896726
Title:
[UBUNTU 20.04.1] qemu (secure guest) crash due to gup_fast / dynamic
page table folding issue
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
Incomplete
Status in linux source package in Groovy:
In Progress
Bug description:
Justification:
==
Secure KVM guest (using secure execution on Ubuntu Server 20.04 for s390x)
crashes happen from time to time during boot.
Such crashed guests ("reason=crashed" in the libvirt log) end up in hutoff
state instead of crashed state ( preserve is set).
The crash points to a kernel memory management problem, addressed by the
following patch/fix.
The modifications touch common memory management code,
but it will have no effect to architectures other than s390x.
This is ensured by the fact that only s390 provides / implements the new
helper functions.
And for s390x, this is actually a critical (and carefully tested) fix for a
(previous) regression, so it can hardly get any more regressive.
The patch landed upstream in linux-next, is in depth discussed
at LKML https://lkml.kernel.org/r/20190418100218.0a4afd51@mschwideX1
and here
https://lore.kernel.org/linux-arch/patch.git-943f1e5dcff2.your-ad-here.call-01599856292-ext-8676@work.hours/
and will soon land via the regular upstream stable release update for kernel
5.4 in focal, too.
The process already started:
https://lore.kernel.org/stable/patch-1.thread-41918b.git-41918be365c0.your-ad-here.call-01600439945-ext-8991@work.hours/
Hence this cherry-pick from the upstream patch should be added to groovy
to avoid any potential regression in case the patch landed in focal via the
upstream release update process,
but is not in groovy and someones upgrades from focal to groovy.
__
Secure Execution with Ubuntu 20.04, secure guest crash during boot
from time to time, crashed guest went into Shufoff state instead of
Crashed state (preserve is set), so I can't get a dump.
libvirt log file:
2020-04-21T16:35:39.382999Z qemu-system-s390x: Guest says index 19608 is
available
2020-04-21 16:35:44.831+: shutting down, reason=crashed
---uname output---
Linux ubu204uclg1002 5.4.0-25-generic #29-Ubuntu SMP Fri Apr 17 15:05:32 UTC
2020 s390x s390x s390x GNU/Linux
Machine Type = z15 8561
---Debugger---
A debugger is not configured
---Steps to Reproduce---
I have a setup with 72 KVM guests which I can start in secure or non-secure
mode. Starting all of them in secure mode back to back results in a number of
guests (4..8) in Shutoff state and reason=crashed in the libvirt log. I can
manually start the guest again no problem. Different guests are failing.
Host and guests are on latest Ubuntu 20.04.
The supposed fix (kernel memory management) has landed in Andrew Mortons mm
tree
https://lore.kernel.org/mm-commits/20200916003608.ib4ln%25a...@linux-foundation.org/T/#u
Please note: while this was found with secure execution, the bug is
actually present for non-KVM workloads as well.
The complete patch is this:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=a338e69ba37286c0fc300ab7e6fa0227e6ca68b1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1896726/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897501] Re: HP Zbook boot into corrupted screen with PSR featured panel
While we don't have access to the specific sku of Dell 7390 in bug
1849947, and PSR has been disabled since all 5.0 Ubuntu kernels and up,
and the platform team has planned to bring up official support to PSR in
5.10 or so, a quirk for this platform is suggested for kernels in Focal
and up until we have PSR finally.
** Description changed:
- TBD.
+ Sreen divided into half after installing Focal 5.4.0-48-generic under
+ Power Saving/Hybrid Graphics Mode. Normal as switched to Discrete
+ Graphics Mode. Screenshot attached as
+
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897501/+attachment/5414860/+files/20200928_135412.jpg
+ .
+
+ With some more investigatin, https://git.launchpad.net/~ubuntu-
+ kernel/ubuntu/+source/linux/+git/focal/commit/?id=d246a6cfe782 ("UBUNTU:
+ SAUCE: drm/i915: Disable PSR by default on all platforms") for bug
+ 1849947 is the root cause. It seems this panel must have PSR enabled.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-48-generic 5.4.0-48.52
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /dev/snd/controlC0: gdm 964 F pulseaudio
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: gdm 964 F pulseaudio
CasperMD5CheckResult: skip
Date: Mon Sep 28 01:50:54 2020
InstallationDate: Installed on 2020-09-22 (5 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200218)
MachineType: HP HP ZBook Studio G7
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic
root=UUID=ac48cfe8-5fa7-410c-ad1b-53d1e2683841 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
- linux-restricted-modules-5.4.0-48-generic N/A
- linux-backports-modules-5.4.0-48-generic N/A
- linux-firmware1.187.3
+ linux-restricted-modules-5.4.0-48-generic N/A
+ linux-backports-modules-5.4.0-48-generic N/A
+ linux-firmware1.187.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2020
dmi.bios.vendor: HP
dmi.bios.version: S91 Ver. 85.28.01
dmi.board.name: 8736
dmi.board.vendor: HP
dmi.board.version: KBC Version 14.32.03
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias:
dmi:bvnHP:bvrS91Ver.85.28.01:bd09/18/2020:svnHP:pnHPZBookStudioG7:pvr:rvnHP:rn8736:rvrKBCVersion14.32.03:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN HP ZBook
dmi.product.name: HP ZBook Studio G7
dmi.sys.vendor: HP
** Summary changed:
- HP Zbook boot into corrupted screen with PSR featured panel
+ HP Zbook Studio G7 boots into corrupted screen with PSR featured panel
** Description changed:
Sreen divided into half after installing Focal 5.4.0-48-generic under
Power Saving/Hybrid Graphics Mode. Normal as switched to Discrete
Graphics Mode. Screenshot attached as
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897501/+attachment/5414860/+files/20200928_135412.jpg
.
With some more investigatin, https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/focal/commit/?id=d246a6cfe782 ("UBUNTU:
SAUCE: drm/i915: Disable PSR by default on all platforms") for bug
- 1849947 is the root cause. It seems this panel must have PSR enabled.
+ 1849947 is the root cause. This was landed to all Ubuntu kernels and
+ Ubuntu only for kernel versions 5.0 and up till v5.9 unstable currently.
+
+ It seems this panel must have PSR enabled.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-48-generic 5.4.0-48.52
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm 964 F pulseaudio
CasperMD5CheckResult: skip
Date: Mon Sep 28 01:50:54 2020
InstallationDate: Installed on 2020-09-22 (5 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200218)
MachineType: HP HP ZBook Studio G7
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic
root=UUID=ac48cfe8-5fa7-410c-ad1b-53d1e2683841 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.4.0-48-generic N/A
linux-backports-modules-5.4.0-48-generic N/A
linux-firmware1.187.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2020
dmi.bios.vendor: HP
[Kernel-packages] [Bug 1849947] Re: Dell XPS 13 (7390) Display Flickering - 19.10
Filed bug 1897501 to address 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/1849947 Title: Dell XPS 13 (7390) Display Flickering - 19.10 Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Won't Fix Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: Hi there, I recently purchased a Dell XPS 13 7390 (Developer Edition). I decided to replace 18.4 LTS with 19.10 and so far it has been pretty smooth. However, there is one issue which occurs frequently whereby the display flickers and becomes unusable. The best way to describe the appearance is that the image becomes heavily distorted. Sometimes it only happens for a split second, other times it is permanently distorted. When this happens, simply closing the laptop lip and re-opening seems to put the display back into it's correct state. I didn't experience this issue on 18.04 LTS which is why I believe it's a Software Bug within 19.10. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 11:11:43 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2019-10-25 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 13 7390 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 0G2D0W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd08/23/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1849947/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897501] Re: HP Zbook boot into corrupted screen with PSR featured panel
** Attachment added: "screenshot at gdm"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897501/+attachment/5414860/+files/20200928_135412.jpg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1897501
Title:
HP Zbook Studio G7 boots into corrupted screen with PSR featured panel
Status in HWE Next:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
Sreen divided into half after installing Focal 5.4.0-48-generic under
Power Saving/Hybrid Graphics Mode. Normal as switched to Discrete
Graphics Mode. Screenshot attached as
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897501/+attachment/5414860/+files/20200928_135412.jpg
.
With some more investigatin, https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/focal/commit/?id=d246a6cfe782
("UBUNTU: SAUCE: drm/i915: Disable PSR by default on all platforms")
for bug 1849947 is the root cause. It seems this panel must have PSR
enabled.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-48-generic 5.4.0-48.52
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm 964 F pulseaudio
CasperMD5CheckResult: skip
Date: Mon Sep 28 01:50:54 2020
InstallationDate: Installed on 2020-09-22 (5 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200218)
MachineType: HP HP ZBook Studio G7
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic
root=UUID=ac48cfe8-5fa7-410c-ad1b-53d1e2683841 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.4.0-48-generic N/A
linux-backports-modules-5.4.0-48-generic N/A
linux-firmware1.187.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2020
dmi.bios.vendor: HP
dmi.bios.version: S91 Ver. 85.28.01
dmi.board.name: 8736
dmi.board.vendor: HP
dmi.board.version: KBC Version 14.32.03
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias:
dmi:bvnHP:bvrS91Ver.85.28.01:bd09/18/2020:svnHP:pnHPZBookStudioG7:pvr:rvnHP:rn8736:rvrKBCVersion14.32.03:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN HP ZBook
dmi.product.name: HP ZBook Studio G7
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1897501/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897392] 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 1897392 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 ** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1897392 Title: Ryzen 4800u, kernel 5.8.11 boot errors (AMD-Vi, ACPI, HDCP, Bluetooth) Status in linux package in Ubuntu: Incomplete Bug description: Lenovo IdeaPad S540, 13-ARE AMD Ryzen 4800U, 16GB dual channel RAM, 13.3" 2560x1600 screen. Note this laptop is a lot like the Lenovo Slim 7, it seems this laptop UEFI Bios does advertise S3 sleep, the Slim 7 only advertises S2idle. The errors are related to AMD Ryzen 4000 series. Clean (no dual boot) Ubuntu Budgie 20.04.1 with kernel upgraded to 5.8.11. Full dmesg: https://pastebin.com/nFbHB22d Journalclt after boot: https://pastebin.com/bcpw8Vhc erros only from dmesg: $ sudo dmesg -l err [2.686094] pci :00:00.2: AMD-Vi: Unable to read/write to IOMMU perf counter. [4.818164] I2C multi instantiate pseudo device driver INT3515:00: IRQ index 1 not found [4.836122] snd_pci_acp3x :03:00.5: Invalid ACP audio mode : 0 [4.971650] ACPI Error: No handler for Region [ECSI] (e6d23662) [EmbeddedControl] (20200528/evregion-127) [4.971933] ACPI Error: Region EmbeddedControl (ID=3) has no handler (20200528/exfldio-261) [4.972172] ACPI Error: Aborting method \_SB.UBTC.ECRD due to previous error (AE_NOT_EXIST) (20200528/psparse-529) [4.972447] ACPI Error: Aborting method \_SB.UBTC._DSM due to previous error (AE_NOT_EXIST) (20200528/psparse-529) [4.972736] ucsi_acpi USBC000:00: ucsi_acpi_dsm: failed to evaluate _DSM 2 [5.871695] acp_pdm_mach acp_pdm_mach.0: snd_soc_register_card(acp) failed: -517 [6.127547] [drm:dm_helpers_dp_write_dpcd [amdgpu]] *ERROR* Failed to find connector for link! [6.128334] [drm:dm_helpers_dp_write_dpcd [amdgpu]] *ERROR* Failed to find connector for link! [6.128558] [drm:dm_helpers_dp_write_dpcd [amdgpu]] *ERROR* Failed to find connector for link! [6.938706] [drm:mod_hdcp_add_display_to_topology [amdgpu]] *ERROR* Failed to add display topology, DTM TA is not initialized. $ lsb_release -a; uname -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.1 LTS Release: 20.04 Codename: focal Linux Idefix 5.8.11-050811-generic #202009230858 SMP Wed Sep 23 13:06:55 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897392/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897501] Status changed to Confirmed
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1897501
Title:
HP Zbook Studio G7 boots into corrupted screen with PSR featured panel
Status in HWE Next:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
Sreen divided into half after installing Focal 5.4.0-48-generic under
Power Saving/Hybrid Graphics Mode. Normal as switched to Discrete
Graphics Mode. Screenshot attached as
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897501/+attachment/5414860/+files/20200928_135412.jpg
.
With some more investigatin, https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/focal/commit/?id=d246a6cfe782
("UBUNTU: SAUCE: drm/i915: Disable PSR by default on all platforms")
for bug 1849947 is the root cause. It seems this panel must have PSR
enabled.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-48-generic 5.4.0-48.52
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm 964 F pulseaudio
CasperMD5CheckResult: skip
Date: Mon Sep 28 01:50:54 2020
InstallationDate: Installed on 2020-09-22 (5 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200218)
MachineType: HP HP ZBook Studio G7
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic
root=UUID=ac48cfe8-5fa7-410c-ad1b-53d1e2683841 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.4.0-48-generic N/A
linux-backports-modules-5.4.0-48-generic N/A
linux-firmware1.187.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2020
dmi.bios.vendor: HP
dmi.bios.version: S91 Ver. 85.28.01
dmi.board.name: 8736
dmi.board.vendor: HP
dmi.board.version: KBC Version 14.32.03
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias:
dmi:bvnHP:bvrS91Ver.85.28.01:bd09/18/2020:svnHP:pnHPZBookStudioG7:pvr:rvnHP:rn8736:rvrKBCVersion14.32.03:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN HP ZBook
dmi.product.name: HP ZBook Studio G7
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1897501/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897501] [NEW] HP Zbook Studio G7 boots into corrupted screen with PSR featured panel
Public bug reported:
Sreen divided into half after installing Focal 5.4.0-48-generic under
Power Saving/Hybrid Graphics Mode. Normal as switched to Discrete
Graphics Mode. Screenshot attached as
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897501/+attachment/5414860/+files/20200928_135412.jpg
.
With some more investigatin, https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/focal/commit/?id=d246a6cfe782 ("UBUNTU:
SAUCE: drm/i915: Disable PSR by default on all platforms") for bug
1849947 is the root cause. It seems this panel must have PSR enabled.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-48-generic 5.4.0-48.52
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm 964 F pulseaudio
CasperMD5CheckResult: skip
Date: Mon Sep 28 01:50:54 2020
InstallationDate: Installed on 2020-09-22 (5 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200218)
MachineType: HP HP ZBook Studio G7
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic
root=UUID=ac48cfe8-5fa7-410c-ad1b-53d1e2683841 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.4.0-48-generic N/A
linux-backports-modules-5.4.0-48-generic N/A
linux-firmware1.187.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2020
dmi.bios.vendor: HP
dmi.bios.version: S91 Ver. 85.28.01
dmi.board.name: 8736
dmi.board.vendor: HP
dmi.board.version: KBC Version 14.32.03
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias:
dmi:bvnHP:bvrS91Ver.85.28.01:bd09/18/2020:svnHP:pnHPZBookStudioG7:pvr:rvnHP:rn8736:rvrKBCVersion14.32.03:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN HP ZBook
dmi.product.name: HP ZBook Studio G7
dmi.sys.vendor: HP
** Affects: hwe-next
Importance: Undecided
Status: New
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed
** Tags: amd64 apport-bug focal oem-priority originate-from-1896602 stella
** Tags added: oem-priority originate-from-1896602 stella
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1897501
Title:
HP Zbook Studio G7 boots into corrupted screen with PSR featured panel
Status in HWE Next:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
Sreen divided into half after installing Focal 5.4.0-48-generic under
Power Saving/Hybrid Graphics Mode. Normal as switched to Discrete
Graphics Mode. Screenshot attached as
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897501/+attachment/5414860/+files/20200928_135412.jpg
.
With some more investigatin, https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/focal/commit/?id=d246a6cfe782
("UBUNTU: SAUCE: drm/i915: Disable PSR by default on all platforms")
for bug 1849947 is the root cause. It seems this panel must have PSR
enabled.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-48-generic 5.4.0-48.52
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm 964 F pulseaudio
CasperMD5CheckResult: skip
Date: Mon Sep 28 01:50:54 2020
InstallationDate: Installed on 2020-09-22 (5 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200218)
MachineType: HP HP ZBook Studio G7
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic
root=UUID=ac48cfe8-5fa7-410c-ad1b-53d1e2683841 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.4.0-48-generic N/A
linux-backports-modules-5.4.0-48-generic N/A
linux-firmware1.187.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2020
dmi.bios.vendor: HP
dmi.bios.version: S91 Ver. 85.28.01
dmi.board.name: 8736
dmi.board.vendor: HP
dmi.board.version: KBC Version 14.32.03
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias:
dmi:bvnHP:bvrS91Ver.85.28.01:bd09/18/2020:svnHP:pnHPZBookStudioG7:pvr:rvnHP:rn8736:rvrKBCVersion14.32.03:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN HP ZBook
dmi.product.name: HP ZBook Studio G7
dmi.sys.vendor: HP
To manage
[Kernel-packages] [Bug 1897392] Re: Ryzen 4800u, kernel 5.8.11 boot errors (AMD-Vi, ACPI, HDCP, Bluetooth)
If it is too much of an inconvenience, don't worry about it. The changelog for Lenovo's updates don't look too promising to fix the error messages. Thanks for the report. ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1897392 Title: Ryzen 4800u, kernel 5.8.11 boot errors (AMD-Vi, ACPI, HDCP, Bluetooth) Status in linux package in Ubuntu: Incomplete Bug description: Lenovo IdeaPad S540, 13-ARE AMD Ryzen 4800U, 16GB dual channel RAM, 13.3" 2560x1600 screen. Note this laptop is a lot like the Lenovo Slim 7, it seems this laptop UEFI Bios does advertise S3 sleep, the Slim 7 only advertises S2idle. The errors are related to AMD Ryzen 4000 series. Clean (no dual boot) Ubuntu Budgie 20.04.1 with kernel upgraded to 5.8.11. Full dmesg: https://pastebin.com/nFbHB22d Journalclt after boot: https://pastebin.com/bcpw8Vhc erros only from dmesg: $ sudo dmesg -l err [2.686094] pci :00:00.2: AMD-Vi: Unable to read/write to IOMMU perf counter. [4.818164] I2C multi instantiate pseudo device driver INT3515:00: IRQ index 1 not found [4.836122] snd_pci_acp3x :03:00.5: Invalid ACP audio mode : 0 [4.971650] ACPI Error: No handler for Region [ECSI] (e6d23662) [EmbeddedControl] (20200528/evregion-127) [4.971933] ACPI Error: Region EmbeddedControl (ID=3) has no handler (20200528/exfldio-261) [4.972172] ACPI Error: Aborting method \_SB.UBTC.ECRD due to previous error (AE_NOT_EXIST) (20200528/psparse-529) [4.972447] ACPI Error: Aborting method \_SB.UBTC._DSM due to previous error (AE_NOT_EXIST) (20200528/psparse-529) [4.972736] ucsi_acpi USBC000:00: ucsi_acpi_dsm: failed to evaluate _DSM 2 [5.871695] acp_pdm_mach acp_pdm_mach.0: snd_soc_register_card(acp) failed: -517 [6.127547] [drm:dm_helpers_dp_write_dpcd [amdgpu]] *ERROR* Failed to find connector for link! [6.128334] [drm:dm_helpers_dp_write_dpcd [amdgpu]] *ERROR* Failed to find connector for link! [6.128558] [drm:dm_helpers_dp_write_dpcd [amdgpu]] *ERROR* Failed to find connector for link! [6.938706] [drm:mod_hdcp_add_display_to_topology [amdgpu]] *ERROR* Failed to add display topology, DTM TA is not initialized. $ lsb_release -a; uname -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.1 LTS Release: 20.04 Codename: focal Linux Idefix 5.8.11-050811-generic #202009230858 SMP Wed Sep 23 13:06:55 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897392/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896726] Comment bridged from LTC Bugzilla
--- Comment From cborn...@de.ibm.com 2020-09-28 01:44 EDT---
Fix is upstream as
commit d3f7b1bb204099f2f7306318896223e8599bb6a2
Author: Vasily Gorbik
AuthorDate: Fri Sep 25 21:19:10 2020 -0700
Commit: Linus Torvalds
CommitDate: Sat Sep 26 10:33:57 2020 -0700
mm/gup: fix gup_fast with dynamic page table folding
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d3f7b1bb204099f2f7306318896223e8599bb6a2
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1896726
Title:
[UBUNTU 20.04.1] qemu (secure guest) crash due to gup_fast / dynamic
page table folding issue
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
Incomplete
Status in linux source package in Groovy:
In Progress
Bug description:
Justification:
==
Secure KVM guest (using secure execution on Ubuntu Server 20.04 for s390x)
crashes happen from time to time during boot.
Such crashed guests ("reason=crashed" in the libvirt log) end up in hutoff
state instead of crashed state ( preserve is set).
The crash points to a kernel memory management problem, addressed by the
following patch/fix.
The modifications touch common memory management code,
but it will have no effect to architectures other than s390x.
This is ensured by the fact that only s390 provides / implements the new
helper functions.
And for s390x, this is actually a critical (and carefully tested) fix for a
(previous) regression, so it can hardly get any more regressive.
The patch landed upstream in linux-next, is in depth discussed
at LKML https://lkml.kernel.org/r/20190418100218.0a4afd51@mschwideX1
and here
https://lore.kernel.org/linux-arch/patch.git-943f1e5dcff2.your-ad-here.call-01599856292-ext-8676@work.hours/
and will soon land via the regular upstream stable release update for kernel
5.4 in focal, too.
The process already started:
https://lore.kernel.org/stable/patch-1.thread-41918b.git-41918be365c0.your-ad-here.call-01600439945-ext-8991@work.hours/
Hence this cherry-pick from the upstream patch should be added to groovy
to avoid any potential regression in case the patch landed in focal via the
upstream release update process,
but is not in groovy and someones upgrades from focal to groovy.
__
Secure Execution with Ubuntu 20.04, secure guest crash during boot
from time to time, crashed guest went into Shufoff state instead of
Crashed state (preserve is set), so I can't get a dump.
libvirt log file:
2020-04-21T16:35:39.382999Z qemu-system-s390x: Guest says index 19608 is
available
2020-04-21 16:35:44.831+: shutting down, reason=crashed
---uname output---
Linux ubu204uclg1002 5.4.0-25-generic #29-Ubuntu SMP Fri Apr 17 15:05:32 UTC
2020 s390x s390x s390x GNU/Linux
Machine Type = z15 8561
---Debugger---
A debugger is not configured
---Steps to Reproduce---
I have a setup with 72 KVM guests which I can start in secure or non-secure
mode. Starting all of them in secure mode back to back results in a number of
guests (4..8) in Shutoff state and reason=crashed in the libvirt log. I can
manually start the guest again no problem. Different guests are failing.
Host and guests are on latest Ubuntu 20.04.
The supposed fix (kernel memory management) has landed in Andrew Mortons mm
tree
https://lore.kernel.org/mm-commits/20200916003608.ib4ln%25a...@linux-foundation.org/T/#u
Please note: while this was found with secure execution, the bug is
actually present for non-KVM workloads as well.
The complete patch is this:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=a338e69ba37286c0fc300ab7e6fa0227e6ca68b1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1896726/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
