[Kernel-packages] [Bug 1840161] Re: Very severe regression in ZFS 0.7.12 in 18.04.3

[Colin Ian King]

This appears to be a relevant fix
https://github.com/openzfs/zfs/commit/45f0437912f4688bb15b353c8773b0e37e0b1a89


** Changed in: zfs-linux (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: zfs-linux (Ubuntu)
   Status: New => Incomplete

** Changed in: zfs-linux (Ubuntu)
   Status: Incomplete => In Progress

-- 
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/1840161

Title:
  Very severe regression in ZFS 0.7.12 in 18.04.3

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  ZFS version 0.7.12 has a documented very severe regression on sending
  and receiving datasets with dnodesize=auto set on the dataset (not
  present in 0.7.9 or 0.8.1). This manifests itself primarily when
  sending and receiving datasets with lots of files, such as happens if
  root is on ZFS. This issue has been documented on the ZFSonlinux git
  repositories in issues:

  https://github.com/zfsonlinux/zfs/issues/9147

  and

  https://github.com/zfsonlinux/zfs/issues/8458

  Since 0.7.12 was just brought into 18.04.3, this regression is now
  affecting LTS. I'm opening this issue in the hopes that the fix is
  backported to the LTS release

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1840161/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1840161] Re: Very severe regression in ZFS 0.7.12 in 18.04.3

[Colin Ian King]

Reproducer: Create an fs with dnodesize=auto (also confirmed stall with
4k). Create (touch) a million files in the same directory. send/receive
it and it stalls. 'zfs list' shows that the fs uses is 130M. The receive
stalls/slowdown at 94M.

-- 
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/1840161

Title:
  Very severe regression in ZFS 0.7.12 in 18.04.3

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  ZFS version 0.7.12 has a documented very severe regression on sending
  and receiving datasets with dnodesize=auto set on the dataset (not
  present in 0.7.9 or 0.8.1). This manifests itself primarily when
  sending and receiving datasets with lots of files, such as happens if
  root is on ZFS. This issue has been documented on the ZFSonlinux git
  repositories in issues:

  https://github.com/zfsonlinux/zfs/issues/9147

  and

  https://github.com/zfsonlinux/zfs/issues/8458

  Since 0.7.12 was just brought into 18.04.3, this regression is now
  affecting LTS. I'm opening this issue in the hopes that the fix is
  backported to the LTS release

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1840161/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-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

[mjay]

*** This bug is a duplicate of bug 1871794 ***
https://bugs.launchpad.net/bugs/1871794

Same problem here, Sone WH-1000MX2, ubuntu 20.04.1 LTS, Linux
5.4.0-45-generic. Tried proposed solutions with no luck.

-- 
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 1893914] Re: [SRU] [Focal/OEM-5.6/Groovy]Fix AMD usb host controller lost after stress S3

[Timo Aaltonen]

** Changed in: linux-oem-5.6 (Ubuntu Focal)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1893914

Title:
  [SRU] [Focal/OEM-5.6/Groovy]Fix AMD usb host controller lost after
  stress S3

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.6 package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux-oem-5.6 source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  In Progress

Bug description:
  [Impact]
  When stress S3 on AMD 0x15e5 usb host controller, it failed to resume.
  The controller indicates "internal Host Controller Error"

  [Fix]
  To fix this, sparse controller enable bit has to be disabled.

  [Test Case]
  Verified on the target platform, OK for  100 times of S3.

  [Regression Potential]
  Low,
  Add specific ID quirk for hw, no other hw related, tested with positive 
results.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1893914/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1847105] Re: very slow disk creation, snapshotting

[Christian Ehrhardt ]

FYI:
Related potential improvements in libvirt got identified, but a fix of the 
"slowness" might indeed eventually land via ZFS (Details in the ML discussion 
linked above).

And thanks Richard btw!

-- 
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/1847105

Title:
  very slow disk creation, snapshotting

Status in virt-manager:
  Confirmed
Status in Native ZFS for Linux:
  New
Status in libvirt package in Ubuntu:
  Triaged
Status in virt-manager package in Ubuntu:
  Triaged
Status in zfs-linux package in Ubuntu:
  New
Status in libvirt source package in Bionic:
  Invalid
Status in virt-manager source package in Bionic:
  Invalid
Status in zfs-linux source package in Bionic:
  Won't Fix
Status in libvirt source package in Disco:
  Won't Fix
Status in virt-manager source package in Disco:
  Won't Fix
Status in zfs-linux source package in Disco:
  Won't Fix
Status in libvirt source package in Focal:
  Triaged
Status in libvirt source package in Groovy:
  Triaged

Bug description:
  This is a regression in eoan for me. I use virt-manager to create vms,
  and I noticed that creating one now takes more than a minute.

  Looking at the process listing while the backing disk is being created, I see 
this qemu-img command line:
  15658 ?Ssl0:00 /usr/sbin/libvirtd
  23726 ?Sl 0:04  \_ /usr/bin/qemu-img create -f qcow2 -o 
preallocation=falloc,compat=1.1,lazy_refcounts 
/var/lib/libvirt/images/live-server.qcow2 41943040K

  If I run qemu-img with that preallocation parameter set, even on
  bionic, then it also takes a very long time.

  On eoan, for comparison:
  andreas@nsn7:~$ time qemu-img create -f qcow2 no-prealloc-image.qcow2 40G
  Formatting 'no-prealloc-image.qcow2', fmt=qcow2 size=42949672960 
cluster_size=65536 lazy_refcounts=off refcount_bits=16

  real  0m0,016s
  user  0m0,010s
  sys   0m0,006s
  andreas@nsn7:~$ qemu-img info no-prealloc-image.qcow2 
  image: no-prealloc-image.qcow2
  file format: qcow2
  virtual size: 40G (42949672960 bytes)
  disk size: 17K
  cluster_size: 65536
  Format specific information:
  compat: 1.1
  lazy refcounts: false
  refcount bits: 16
  corrupt: false
  andreas@nsn7:~$ du -hs no-prealloc-image.qcow2 
  17K   no-prealloc-image.qcow2
  andreas@nsn7:~$ 

  
  and now with preallocation=falloc:
  andreas@nsn7:~$ time qemu-img create -f qcow2 -o preallocation=falloc 
with-prealloc-image.qcow2 40G
  Formatting 'with-prealloc-image.qcow2', fmt=qcow2 size=42949672960 
cluster_size=65536 preallocation=falloc lazy_refcounts=off refcount_bits=16

  real  1m43,196s
  user  0m3,564s
  sys   1m26,720s
  andreas@nsn7:~$ qemu-img info with-prealloc-image.qcow2 
  image: with-prealloc-image.qcow2
  file format: qcow2
  virtual size: 40G (42949672960 bytes)
  disk size: 2.7M
  cluster_size: 65536
  Format specific information:
  compat: 1.1
  lazy refcounts: false
  refcount bits: 16
  corrupt: false
  andreas@nsn7:~$ du -hs with-prealloc-image.qcow2 
  2,8M  with-prealloc-image.qcow2
  andreas@nsn7:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: libvirt-daemon 5.4.0-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Mon Oct  7 11:36:03 2019
  InstallationDate: Installed on 2019-10-07 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191006)
  SourcePackage: libvirt
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.libvirt.nwfilter.allow-arp.xml: [inaccessible: [Errno 
13] Permission denied: '/etc/libvirt/nwfilter/allow-arp.xml']
  modified.conffile..etc.libvirt.nwfilter.allow-dhcp-server.xml: [inaccessible: 
[Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp-server.xml']
  modified.conffile..etc.libvirt.nwfilter.allow-dhcp.xml: [inaccessible: [Errno 
13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp.xml']
  modified.conffile..etc.libvirt.nwfilter.allow-incoming-ipv4.xml: 
[inaccessible: [Errno 13] Permission denied: 
'/etc/libvirt/nwfilter/allow-incoming-ipv4.xml']
  modified.conffile..etc.libvirt.nwfilter.allow-ipv4.xml: [inaccessible: [Errno 
13] Permission denied: '/etc/libvirt/nwfilter/allow-ipv4.xml']
  modified.conffile..etc.libvirt.nwfilter.clean-traffic-gateway.xml: 
[inaccessible: [Errno 13] Permission denied: 
'/etc/libvirt/nwfilter/clean-traffic-gateway.xml']
  modified.conffile..etc.libvirt.nwfilter.clean-traffic.xml: [inaccessible: 
[Errno 13] Permission denied: '/etc/libvirt/nwfilter/clean-traffic.xml']
  modified.conffile..etc.libvirt.nwfilter.no-arp-ip-spoofing.xml: 
[inaccessible: [Errno 13] Permission denied: 
'/etc/libvirt/nwfilter/no-arp-ip-spoofing.xml']
  modified.conffile..etc.libvirt.nwfilter.no-arp-mac-spoofing.xml: 

[Kernel-packages] [Bug 1891336] Re: gkrellm2-cpufreq depends on libcpupower-dev produced by Debian kernel

[Brian Murray]

See also bug 1215411 for some discussion regarding providing
libcpupower.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1891336

Title:
  gkrellm2-cpufreq depends on libcpupower-dev produced by Debian kernel

Status in cpufreqd package in Ubuntu:
  New
Status in gkrellm2-cpufreq package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I don't know how important that is as gkrellm2-cpufreq itself is scheduled 
for removal.
  But I wanted to make sure that it is known that the Debian kernel produces 
"libcpupower-dev" which isn't available in Ubuntu and thereby blocking various 
things in proposed.

  
  root@d10-sid:~# apt-cache show libcpupower-dev
  Package: libcpupower-dev
  Source: linux
  Version: 5.7.10-1
  Installed-Size: 169
  Maintainer: Debian Kernel Team 
  Architecture: amd64
  Replaces: libcpufreq-dev
  Provides: libcpufreq-dev
  Depends: libcpupower1 (= 5.7.10-1)
  Conflicts: libcpufreq-dev
  Description-en: CPU frequency and voltage scaling tools for Linux 
(development files)
   libcpupower is a library for inspecting and controlling cpufreq and
   cpuidle tunables.
   .
   This package is needed to compile programs against libcpupower.


  gkrellm2-cpufreq will most likely be removed from goovy as it makes no sense 
without that build-dep.
  Never the less the kernel Team could evaluate if providing "libcpupower-dev" 
makes sense for Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cpufreqd/+bug/1891336/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1890136] Re: Fix false-negative return value for rtnetlink.sh in kselftests/net

[Kleber Sacilotto de Souza]

Confirmed the tests to be reporting FAIL on bionic/linux with
4.15.0-116.117.

amd64 fou test:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/l/linux/20200901_180043_d4ea1@/log.gz

** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1890136

Title:
  Fix false-negative return value for rtnetlink.sh in kselftests/net

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-hwe source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  In Progress

Bug description:
  == Justification ==
  All the sub test cases in rtnetlink.sh from kselftests/net were using
  the same variable "ret" to store the return value of their test result,
  and it will be reset to 0 in the beginning of each test.

  This will cause false-negative result if the last case has passed.

  Also, the kci_test_encap() test in rtnetlink.sh is actually composed by
  two different sub-tests, kci_test_encap_vxlan() and kci_test_encap_fou()

  Therefore we should check the test result of these two to avoid
  false-negative result for this test case.

  == Fixes ==
  * c2a4d2747996 ("selftests: rtnetlink: correct the final return value for the 
test")
  * 72f70c159b53 ("selftests: rtnetlink: make kci_test_encap() return sub-test 
result")

  This issue is affecting our kernels from B to G, there is no such test
  in X thus it can be skipped.

  The first patch can be cherry-picked for E/F/G, but needs to be
  backported for B/D as they're missing some tests.
  The second patch can be cherry-picked for all affected kernels.

  == Test ==
  Manually tested. The test will fail as expected:
  $ sudo ./rtnetlink.sh
  PASS: policy routing
  PASS: route get
  echo $?
  PASS: preferred_lft addresses have expired
  PASS: promote_secondaries complete
  PASS: tc htb hierarchy
  PASS: gre tunnel endpoint
  PASS: gretap
  PASS: ip6gretap
  PASS: erspan
  PASS: ip6erspan
  PASS: bridge setup
  PASS: ipv6 addrlabel
  PASS: set ifalias a28e0b75-bcc7-4b62-8f5a-381215796229 for test-dummy0
  PASS: vrf
  PASS: vxlan
  FAIL: can't add fou port , skipping test
  PASS: macsec
  PASS: ipsec
  PASS: ipsec_offload
  PASS: bridge fdb get
  PASS: neigh get
  $ echo $?
  1

  == Regression Potential ==
  Low, changes limited to testing tools. It's expected to see this test
  failing after applying these patches, since it is reflecting the actual
  test result.


  == Original Bug Report ==
  In this test, it uses ret to store the return value of each test.

  However, this value will be reset to 0 in the beginning of each test.

  In the end of this test, it will judge PASS/FAIL base on this value.

  Thus this will cause false-negative in some cases.
  Below is an example for the test on Bionic OEM-OSP1, test "ip6erspan", 
"erspan", "ip6gretap" failed with return value 255, but the return value will 
soon be overridden with 0 if following test passed without any issue (I made 
the test to print === RET $ret === line for debugging purpose):

  PASS: policy routing
  === RET 0 ===
  PASS: route get
  === RET 0 ===
  PASS: preferred_lft addresses have expired
  === RET 0 ===
  PASS: tc htb hierarchy
  === RET 0 ===
  PASS: gre tunnel endpoint
  === RET 0 ===
  PASS: gretap
  === RET 0 ===
  Usage: ... { ip6gre | ip6gretap | ip6erspan} [ remote ADDR ]
    [ local ADDR ]
    [ [i|o]seq ]
    [ [i|o]key KEY ]
    [ [i|o]csum ]
    [ hoplimit TTL ]
    [ encaplimit ELIM ]
    [ tclass TCLASS ]
    [ flowlabel FLOWLABEL ]
    [ dscp inherit ]
    [ fwmark MARK ]
    [ dev PHYS_DEV ]
    [ noencap ]
    [ encap { fou | gue | none } ]
    [ encap-sport PORT ]
    [ encap-dport PORT ]
    [ [no]encap-csum ]
    [ [no]encap-csum6 ]
    [ [no]encap-remcsum ]
    [ erspan IDX ]

  Where: ADDR  := IPV6_ADDRESS
     TTL   := { 0..255 } (default=64)
     KEY   := { DOTTED_QUAD | NUMBER }
     ELIM  := { none | 0..255 

[Kernel-packages] [Bug 825130] Re: nvidia-detector crashed with ValueError in __get_value_from_name(): invalid literal for int() with base 10: '173-updates'

[Launchpad Bug Tracker]

*** This bug is a duplicate of bug 1070795 ***
https://bugs.launchpad.net/bugs/1070795

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: nvidia-common (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-common in Ubuntu.
https://bugs.launchpad.net/bugs/825130

Title:
  nvidia-detector crashed with ValueError in __get_value_from_name():
  invalid literal for int() with base 10: '173-updates'

Status in nvidia-common package in Ubuntu:
  Confirmed

Bug description:
  Just dist-upgraded to latest Onieric (as of 12/8/2011). Dist upgrade
  failed with kernel errors for exact same reason.

  Am running inside a VirtualBox.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: nvidia-common 1:0.2.31
  ProcVersionSignature: Ubuntu 3.0.0-7.9-generic 3.0.0
  Uname: Linux 3.0.0-7-generic i686
  Architecture: i386
  Date: Fri Aug 12 12:50:04 2011
  ExecutablePath: /usr/bin/nvidia-detector
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110803.1)
  InterpreterPath: /usr/bin/python2.7
  ProcCmdline: /usr/bin/python /usr/bin/nvidia-detector
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  PythonArgs: ['/usr/bin/nvidia-detector']
  SourcePackage: nvidia-common
  Title: nvidia-detector crashed with ValueError in __get_value_from_name(): 
invalid literal for int() with base 10: '173-updates'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-common/+bug/825130/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver

[khitschler]

Since beginning of September the bug disappeared for me. I'm not sure
what update caused it but the usual suspects are: linux-
image-5.4.0-45-generic:amd64 (5.4.0-45.49~18.04.2, automatic) with its
kernel module amdgpu.ko or some xorg-...-hwe parts or a combination of
them.

But I tried with a boot of a kernel 5.3.0-40 and the bug emerged again.
So it is more likely that it was a kernel related problem.

I have to note that I removed the line with "EnablePageFlip" within the
configuration file "/usr/share/X11/xorg.conf.d/10-amdgpu.conf" of my
suggested workaround #54 like this:

Section "OutputClass"
Identifier "AMDgpu"
MatchDriver "amdgpu"
Driver "amdgpu"
EndSection

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849084

Title:
  Freeze on system-resume caused by kwin and amdgpu driver

Status in kwin package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  This is a well investigated bug by me.

  Problem: a black screen freeze occurs by suspend-resume process
  Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17
  Kernel version: default 5.3.10 or the mainline 5.4.0rc3
  xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works 
well

  This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is
  enabled in Plasma settings. Xrender is OK however I don't like screen
  tearing.

  On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the
  Gnome's compositor is enabled. (I don't know what is the default one
  there but I haven't disabled it)

  I think this is a Kwin / amdgpu driver related bug because of the
  differentiation. These can be fixed even in Kwin/opengl compositor not
  just in the amdgpu driver or in kernel.

  One possible solution: disable opengl compositor by suspend and re-
  enable it after login. Use fe.: Xrender before login / before the
  system restored from suspend.

  For Ubuntu's maintainers: Couldn't be this problem solved by a
  downstream solution? Maybe a proper script could be enough by resume
  and by suspend. There are a lot of bugs like this reported in
  freedesktop bugreport and the developers haven't got enough time for
  fix them fast enough.


  Syslog:

  Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 
8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 
08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 
00 00
  Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 
00010002
  Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 
0202 RCX: 046a
  Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 
0202 RDI: 0002
  Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: 
 R09: 94da76b2d170
  Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: 
b7b54274b70c R12: 94da76b2d000
  Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 
94da758d25d0 R15: 94da270d1400
  Oct 21 10:57:26 pc kernel: [ 9475.308861] FS:  7f2a1b9bea80() 
GS:94da87c4() knlGS:
  Oct 21 10:57:26 pc kernel: [ 9475.308863] CS:  0010 DS:  ES:  CR0: 
80050033
  Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 
00012c11 CR4: 003406e0
  Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace:
  Oct 21 10:57:26 pc kernel: [ 9475.308977]  
amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.308991]  commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309000]  ? commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309009]  
drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309115]  amdgpu_dm_atomic_commit+0x95/0xa0 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309135]  drm_atomic_commit+0x4a/0x50 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309144]  
drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309159]  drm_mode_setcrtc+0x1cd/0x7a0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309234]  ? amdgpu_cs_wait_ioctl+0xd6/0x150 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309249]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309262]  drm_ioctl_kernel+0xae/0xf0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309276]  drm_ioctl+0x234/0x3d0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309290]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309370]  amdgpu_drm_ioctl+0x4e/0x80 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 

[Kernel-packages] [Bug 1496942] Re: Infiniband (mellanox) SR-IOV and libvirt + libnl problems

[Rafael David Tinoco]

Let's keep this bug as Invalid please. There is no issue specific issue
to be solved here.

Thank you

-rafaeldtinoco

** Changed in: linux (Ubuntu)
   Status: In Progress => 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/1496942

Title:
  Infiniband (mellanox) SR-IOV and libvirt + libnl problems

Status in linux package in Ubuntu:
  Invalid
Status in linux package in Debian:
  New

Bug description:
  When trying to start an IB SR-IOV guest by using the following XML:

  


  


  

  following the Mellanox SR-IOV guide, we are able to start guests using
  kernel 3.16 (Utopic).

  We are NOT able to start guests using 3.13 OR 3.19. The following
  error occurs:

  2015-09-17 02:25:07.208+: 52157: info : libvirt version: 1.2.12, package: 
1.2.12-0ubuntu14.1~cloud0
  2015-09-17 02:25:07.208+: 52157: error : virSecurityDriverLookup:80 : 
unsupported configuration: Security driver apparmor not enabled
  2015-09-17 02:25:42.308+: 52281: info : libvirt version: 1.2.12, package: 
1.2.12-0ubuntu14.1~cloud0
  2015-09-17 02:25:42.308+: 52281: error : virSecurityDriverLookup:80 : 
unsupported configuration: Security driver apparmor not enabled
  2015-09-17 02:25:48.996+: 52274: error : virNetDevParseVfConfig:1905 : 
internal error: missing IFLA_VF_INFO in netlink response
  2015-09-17 02:25:49.006+: 52274: error : virFileReadAll:1347 : Failed to 
open file '/var/run/libvirt/hostdevmgr/ib0_vf0': No such file or directory
  2015-09-17 02:25:49.006+: 52274: error : virFileReadAll:1347 : Failed to 
open file '/var/run/libvirt/qemu/ib0_vf0': No such file or directory

  So probably there is some regression in between 3.16 and 3.19 for the
  IFLA_VF_INFO feature from netlink AND this has to be backported to
  kernel 3.13 for Trusty to have IB SR-IOV working.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1496942/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1894104] [NEW] Patriot PXD USB SSD cannot be mount with type-C connector

[LittleBigBrain]

Public bug reported:

It works fine a few weeks ago. But after recent kernel/driver updates.
It stops working. It still works if I connect it to USB 3.1 5000M port.
if I connect it to 1M port, it stops working.

I can still use `smartctl -a -d sntjmicron /dev/sdx` to obtain the smart
data. But any block operation will fail with remote I/O error: mount,
format, dd, etc

The port is find, I connected other device to it, it is still working without 
issue. The USB controller and storage device are:
```
USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller 
(rev 10)
ID 13fe:2570 Kingston Technology Company Inc. Patriot Memory
```

kernel
```
5.4.0-45-generic #49-Ubuntu SMP Wed Aug 26 13:38:52 UTC 2020 x86_64 x86_64 
x86_64 GNU/Linux
```

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  It works fine a few weeks ago. But after recent kernel/driver updates.
  It stop working. It still work if I connect it to USB 3.1 5000M port. if
  I connect it to 1M port, it stop working.
  
  I can still use `smartctl -a -d sntjmicron /dev/sdx` to obtain the smart
  data. But any block operation will fail with remote I/O error: mount,
  format, dd, etc
  
  The port is find, I connected other device to it, it is still working without 
issue. The USB controller and storage device are:
  ```
  USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host 
Controller (rev 10)
  ID 13fe:2570 Kingston Technology Company Inc. Patriot Memory
  ```
+ 
+ kernel
+ ```
+ 5.4.0-45-generic #49-Ubuntu SMP Wed Aug 26 13:38:52 UTC 2020 x86_64 x86_64 
x86_64 GNU/Linux
+ ```

** Description changed:

  It works fine a few weeks ago. But after recent kernel/driver updates.
- It stop working. It still work if I connect it to USB 3.1 5000M port. if
- I connect it to 1M port, it stop working.
+ It stops working. It still works if I connect it to USB 3.1 5000M port.
+ if I connect it to 1M port, it stops working.
  
  I can still use `smartctl -a -d sntjmicron /dev/sdx` to obtain the smart
  data. But any block operation will fail with remote I/O error: mount,
  format, dd, etc
  
  The port is find, I connected other device to it, it is still working without 
issue. The USB controller and storage device are:
  ```
  USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host 
Controller (rev 10)
  ID 13fe:2570 Kingston Technology Company Inc. Patriot Memory
  ```
  
  kernel
  ```
  5.4.0-45-generic #49-Ubuntu SMP Wed Aug 26 13:38:52 UTC 2020 x86_64 x86_64 
x86_64 GNU/Linux
  ```

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894104

Title:
  Patriot PXD USB SSD cannot be mount with type-C connector

Status in linux package in Ubuntu:
  New

Bug description:
  It works fine a few weeks ago. But after recent kernel/driver updates.
  It stops working. It still works if I connect it to USB 3.1 5000M
  port. if I connect it to 1M port, it stops working.

  I can still use `smartctl -a -d sntjmicron /dev/sdx` to obtain the
  smart data. But any block operation will fail with remote I/O error:
  mount, format, dd, etc

  The port is find, I connected other device to it, it is still working without 
issue. The USB controller and storage device are:
  ```
  USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host 
Controller (rev 10)
  ID 13fe:2570 Kingston Technology Company Inc. Patriot Memory
  ```

  kernel
  ```
  5.4.0-45-generic #49-Ubuntu SMP Wed Aug 26 13:38:52 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/1894104/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1894104] Missing required logs.

[Ubuntu Kernel Bot]

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 1894104

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/1894104

Title:
  Patriot PXD USB SSD cannot be mount with type-C connector

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It works fine a few weeks ago. But after recent kernel/driver updates.
  It stops working. It still works if I connect it to USB 3.1 5000M
  port. if I connect it to 1M port, it stops working.

  I can still use `smartctl -a -d sntjmicron /dev/sdx` to obtain the
  smart data. But any block operation will fail with remote I/O error:
  mount, format, dd, etc

  The port is find, I connected other device to it, it is still working without 
issue. The USB controller and storage device are:
  ```
  USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host 
Controller (rev 10)
  ID 13fe:2570 Kingston Technology Company Inc. Patriot Memory
  ```

  kernel
  ```
  5.4.0-45-generic #49-Ubuntu SMP Wed Aug 26 13:38:52 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/1894104/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1893985] Re: Latest Azure optimised fips-updates kernel 4.15.0-2007-azure-fips leaves instance in unbootable state

[Marcelo Cerri]

** Changed in: linux (Ubuntu)
   Status: Confirmed => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1893985

Title:
  Latest Azure optimised fips-updates kernel 4.15.0-2007-azure-fips
  leaves instance in unbootable state

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  In Azure, updating an instance to the latest Azure optimised fips-
  updates kernel (4.15.0-2007-azure-fips) leaves the system in an
  unbootable state.

  The serial console shows the following and reboots:

  Checking kernel image: /boot/vmlinuz-4.15.0-2007-azure-fips
  Kernel integrity check failed
  Rebooting automatically due to panic= boot argument

  This is with the instance type Standard D2s v3

  Steps to reproduce (with the UA client in Ubuntu Pro):

  -Launch an Ubuntu Pro 18.04 instance on AWS on a Standard D2s v3
  instance

  sudo add-apt-repository ppa:canonical-server/ua-client-daily --yes
  sudo apt install ubuntu-advantage-tools ubuntu-advantage-pro --yes
  sudo ua disable livepatch
  sudo ua enable fips-updates --beta
  sudo apt install linux-azure-fips

  KERNEL=$(awk -F"'" '/menuentry.*azure-fips/ { print $(NF-1); exit }'
  /boot/grub/grub.cfg)

  sudo tee /etc/default/grub.d/99-fips.cfg << __EOF__
  GRUB_DEFAULT="Advanced options for Ubuntu>$KERNEL"
  GRUB_CMDLINE_LINUX_DEFAULT="\$GRUB_CMDLINE_LINUX_DEFAULT fips=1" 
  __EOF__

  sudo update-grub
  sudo reboot

  -Look at serial console in Azure Portal

  Attaching screenshot of error before kernel panic and auto reboot.

  Here is the list of packages installed with the action:

  base-files amd64 10.1ubuntu2.9
  libpam0g amd64 1.1.8-3.6ubuntu2.18.04.2
  libpam-modules-bin amd64 1.1.8-3.6ubuntu2.18.04.2
  libpam-modules amd64 1.1.8-3.6ubuntu2.18.04.2
  libnss-systemd amd64 237-3ubuntu10.42
  libsystemd0 amd64 237-3ubuntu10.42
  libpam-systemd amd64 237-3ubuntu10.42
  systemd amd64 237-3ubuntu10.42
  udev amd64 237-3ubuntu10.42
  libudev1 amd64 237-3ubuntu10.42
  kmod amd64 24-1ubuntu3.5
  libkmod2 amd64 24-1ubuntu3.5
  libpam-runtime all 1.1.8-3.6ubuntu2.18.04.2
  systemd-sysv amd64 237-3ubuntu10.42
  python-samba amd64 2:4.7.6+dfsg~ubuntu-0ubuntu2.18
  samba-common-bin amd64 2:4.7.6+dfsg~ubuntu-0ubuntu2.18
  samba-common all 2:4.7.6+dfsg~ubuntu-0ubuntu2.18
  samba-libs amd64 2:4.7.6+dfsg~ubuntu-0ubuntu2.18
  libwbclient0 amd64 2:4.7.6+dfsg~ubuntu-0ubuntu2.18
  iproute2 amd64 4.15.0-2ubuntu1.2
  libisc-export169 amd64 1:9.11.3+dfsg-1ubuntu1.13
  libdns-export1100 amd64 1:9.11.3+dfsg-1ubuntu1.13
  libirs160 amd64 1:9.11.3+dfsg-1ubuntu1.13
  bind9-host amd64 1:9.11.3+dfsg-1ubuntu1.13
  dnsutils amd64 1:9.11.3+dfsg-1ubuntu1.13
  libbind9-160 amd64 1:9.11.3+dfsg-1ubuntu1.13
  libisccfg160 amd64 1:9.11.3+dfsg-1ubuntu1.13
  libisccc160 amd64 1:9.11.3+dfsg-1ubuntu1.13
  libdns1100 amd64 1:9.11.3+dfsg-1ubuntu1.13
  libisc169 amd64 1:9.11.3+dfsg-1ubuntu1.13
  liblwres160 amd64 1:9.11.3+dfsg-1ubuntu1.13
  libpcap0.8 amd64 1.8.1-6ubuntu1.18.04.2
  libx11-data all 2:1.6.4-3ubuntu0.3
  libx11-6 amd64 2:1.6.4-3ubuntu0.3
  grub-efi-amd64 amd64 2.02-2ubuntu8.18
  grub2-common amd64 2.02-2ubuntu8.18
  shim-signed amd64 1.37~18.04.6+15+1533136590.3beb971-0ubuntu1
  grub-efi-amd64-signed amd64 1.93.20+2.02-2ubuntu8.18
  grub-efi-amd64-bin amd64 2.02-2ubuntu8.18
  grub-pc-bin amd64 2.02-2ubuntu8.18
  grub-common amd64 2.02-2ubuntu8.18
  libgssapi-krb5-2 amd64 1.16-2ubuntu0.1+esm1
  python3-problem-report all 2.20.9-0ubuntu7.17
  python3-apport all 2.20.9-0ubuntu7.17
  apport all 2.20.9-0ubuntu7.17
  bcache-tools amd64 1.0.8-2ubuntu0.18.04.1
  curl amd64 7.58.0-2ubuntu3.10
  libcurl4 amd64 7.58.0-2ubuntu3.10
  libcurl3-gnutls amd64 7.58.0-2ubuntu3.10
  linux-modules-5.4.0-1023-azure amd64 5.4.0-1023.23~18.04.1
  linux-image-5.4.0-1023-azure amd64 5.4.0-1023.23~18.04.1
  libkrb5-3 amd64 1.16-2ubuntu0.1+esm1
  libkrb5support0 amd64 1.16-2ubuntu0.1+esm1
  libk5crypto3 amd64 1.16-2ubuntu0.1+esm1
  krb5-locales all 1.16-2ubuntu0.1+esm1
  linux-modules-4.15.0-2007-azure-fips amd64 4.15.0-2007.8
  linux-modules-extra-5.4.0-1023-azure amd64 5.4.0-1023.23~18.04.1
  linux-azure amd64 5.4.0.1023.7
  linux-image-azure amd64 5.4.0.1023.7
  linux-azure-5.4-headers-5.4.0-1023 all 5.4.0-1023.23~18.04.1
  linux-image-4.15.0-2007-azure-fips amd64 4.15.0-2007.8
  linux-headers-5.4.0-1023-azure amd64 5.4.0-1023.23~18.04.1
  linux-headers-azure amd64 5.4.0.1023.7
  linux-tools-common all 4.15.0-115.116
  linux-azure-5.4-tools-5.4.0-1023 amd64 5.4.0-1023.23~18.04.1
  linux-azure-fips amd64 4.15.0.2007.7
  linux-image-azure-fips amd64 4.15.0.2007.7
  linux-azure-fips-headers-4.15.0-2007 all 4.15.0-2007.8
  linux-tools-5.4.0-1023-azure amd64 5.4.0-1023.23~18.04.1
  linux-tools-azure amd64 5.4.0.1023.7
  linux-cloud-tools-common all 4.15.0-115.116
  linux-azure-5.4-cloud-tools-5.4.0-1023 amd64 5.4.0-1023.23~18.04.1
  linux-cloud-tools-5.4.0-1023-azure amd64 

[Kernel-packages] [Bug 1888507] Re: [UBUNTU 18.04] BPF programs fail on Ubuntu s390x

[Frank Heimes]

Based on the last recent conversation (and comment #9) I am closing this ticket 
for now as Invalid.
If the upstream work succeeded and BPF got stabilized and tested again and 
further issues occur, a new LP bug can be opened any time.

** Changed in: linux (Ubuntu Focal)
   Status: In Progress => Invalid

** Changed in: linux (Ubuntu Bionic)
   Status: Triaged => Invalid

** Changed in: linux (Ubuntu)
   Status: New => Invalid

** Changed in: ubuntu-z-systems
   Status: In Progress => 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/1888507

Title:
  [UBUNTU 18.04] BPF programs fail on Ubuntu s390x

Status in Ubuntu on IBM z Systems:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in linux source package in Focal:
  Invalid

Bug description:
  [Impact]
  Some bpf programs will fail to execute on s390x, returning EFAULT when they 
should be able to read user memory.

  [Test case]
  apt-get source linux
  mkdir -p /usr/lib/perf/
  cp -a linux-5.4.0/tools/perf/include /usr/lib/perf/
  probe_read=$(grep -w probe_read /usr/lib/perf/include/bpf/bpf.h)
  probe_read_user=${probe_read//read/read_user}
  sed -i "/probe_read)/i$probe_read_user" /usr/lib/perf/include/bpf/bpf.h
  probe_read_user_str=${probe_read//read/read_user_str}
  sed -i "/probe_read)/i$probe_read_user_str" /usr/lib/perf/include/bpf/bpf.h

  ed - linux-5.4.0/tools/perf/examples/bpf/augmented_raw_syscalls.c << EOF
  100c
  int string_len = probe_read_user_str(_arg->value, arg_len, arg);
  .
  w
  EOF
  perf trace -eopenat,augmented_raw_syscalls.c cat /etc/passwd > /dev/null

  You should see:
   0.332 ( 0.002 ms): cat/3223 openat(dfd: CWD, filename: "/etc/passwd")
 = 3
  instead of
   0.334 ( 0.003 ms): cat/3739 openat(dfd: CWD, filename: "")   
 = 3

  [Potential regressions]
  One potential regression is that unprivileged code can be able to exploit the 
changes to read or write kernel memory.


  --

  
  We need to run BPF filters to analyse and monitor network traffic. The BPF 
filters are created by skydive (http://skydive.network). Currently skydive 
fails to install BPF filters on s390x (using Ubuntu 18.04 currently, soon 
moving to Ubuntu 20.04).

  Because of these failures, we decided to try the BPF samples that come
  with the kernel first. These samples also fail on s390x while they
  work fine on Intel.

  shense@boe-build:~/bionic/samples/bpf$ uname -a
  Linux boe-build 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:40:36 UTC 
2020 s390x s390x s390x GNU/Linux

  Example instructions:

  sudo apt install -y dpkg-dev clang llvm libelf-dev
  sudo apt-get source linux-image-unsigned-$(uname -r)
  cd linux-4.15.0/
  make headers_install
  make samples/bpf/

  Errors:

  shense@boe-build:~/bionic/samples/bpf$ sudo ./test_map_in_map
  [sudo] password for shense:
  invalid relo for insn[4].code 0x85
  bpf_load_program() err=22
  0: (bf) r7 = r1
  1: (b7) r1 = 0
  2: (63) *(u32 *)(r10 -32) = r1
  3: (bf) r1 = r7
  4: (85) call unknown#-1
  BPF_CALL uses reserved fields
  0: (bf) r7 = r1
  1: (b7) r1 = 0
  2: (63) *(u32 *)(r10 -32) = r1
  3: (bf) r1 = r7
  4: (85) call unknown#-1
  BPF_CALL uses reserved fields

  shense@boe-build:~/bionic/samples/bpf$ sudo ./map_perf_test
  invalid relo for insn[22].code 0x85
  bpf_load_program() err=22
  0: (bf) r7 = r1
  1: (18) r1 = 0x207265743a25646e
  3: (7b) *(u64 *)(r10 -16) = r1
  4: (18) r1 = 0x705f616c6c6f632e
  6: (7b) *(u64 *)(r10 -24) = r1
  7: (18) r1 = 0x5f6c72755f686d61
  9: (7b) *(u64 *)(r10 -32) = r1
  10: (18) r1 = 0x7420737472657373
  12: (7b) *(u64 *)(r10 -40) = r1
  13: (18) r1 = 0x4661696c65642061
  15: (7b) *(u64 *)(r10 -48) = r1
  16: (b7) r1 = 0
  17: (73) *(u8 *)(r10 -8) = r1
  18: (b7) r2 = 1
  19: (7b) *(u64 *)(r10 -72) = r2
  20: (63) *(u32 *)(r10 -76) = r1
  21: (bf) r1 = r7
  22: (85) call unknown#-1
  BPF_CALL uses reserved fields
  0: (bf) r7 = r1
  1: (18) r1 = 0x207265743a25646e
  3: (7b) *(u64 *)(r10 -16) = r1
  4: (18) r1 = 0x705f616c6c6f632e
  6: (7b) *(u64 *)(r10 -24) = r1
  7: (18) r1 = 0x5f6c72755f686d61
  9: (7b) *(u64 *)(r10 -32) = r1
  10: (18) r1 = 0x7420737472657373
  12: (7b) *(u64 *)(r10 -40) = r1
  13: (18) r1 = 0x4661696c65642061
  15: (7b) *(u64 *)(r10 -48) = r1
  16: (b7) r1 = 0
  17: (73) *(u8 *)(r10 -8) = r1
  18: (b7) r2 = 1
  19: (7b) *(u64 *)(r10 -72) = r2
  20: (63) *(u32 *)(r10 -76) = r1
  21: (bf) r1 = r7
  22: (85) call unknown#-1
  BPF_CALL uses reserved fields

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1888507/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : 

[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices

[Kai-Heng Feng]

Please also attach `udevadm info -e` and `cat
/sys/class/dmi/id/product_version`.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux 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

Bug description:
  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 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices

[Kai-Heng Feng]

Can you please attach dmesg?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux 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

Bug description:
  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 1840161] Re: Very severe regression in ZFS 0.7.12 in 18.04.3

[Colin Ian King]

Ubuntu Bionic 18.04.x was released with ZFS 0.7.5 and not 0.7.12.
Ubuntu Disco 19.04 contained ZFS 0.7.11 and then 0.7.12 but this is now
EOL.

Supported versions of ZFS are as follows:

Xenial: 0.6.5.6
Bionic: 0.7.5
Focal:  0.8.3
Groovy: 0.8.4

0.7.12 is EOL. The bug you are referring to has the fixes in the Focal
and Groovy releases. Marking this as Won't Fix.

** Changed in: zfs-linux (Ubuntu)
   Status: In Progress => Won't Fix

-- 
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/1840161

Title:
  Very severe regression in ZFS 0.7.12 in 18.04.3

Status in zfs-linux package in Ubuntu:
  Won't Fix

Bug description:
  ZFS version 0.7.12 has a documented very severe regression on sending
  and receiving datasets with dnodesize=auto set on the dataset (not
  present in 0.7.9 or 0.8.1). This manifests itself primarily when
  sending and receiving datasets with lots of files, such as happens if
  root is on ZFS. This issue has been documented on the ZFSonlinux git
  repositories in issues:

  https://github.com/zfsonlinux/zfs/issues/9147

  and

  https://github.com/zfsonlinux/zfs/issues/8458

  Since 0.7.12 was just brought into 18.04.3, this regression is now
  affecting LTS. I'm opening this issue in the hopes that the fix is
  backported to the LTS release

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1840161/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1771310] Re: zfs doesn't automount after a new disk is plugged in

[Colin Ian King]

When using pluggable devices it is advisable to use the UUID of the
device as this is guaranteed to find the correct device. USB block
devices may not be enumerated in order.  I suggest re-trying using the
UUID of devices and see if this helps.

To find the UUID, use ls /dev/disk/by-uuid/

-- 
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/1771310

Title:
  zfs doesn't automount after a new disk is plugged in

Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  I've a zfs that automount itself fine. If I plug a USB disk, the
  enumerated list of disk change and on reboot the zfs doesn't automount
  anymore and complains on missing device when trying to manually mount
  it.

  The pool was created with:

  zpool create -f srv raidz3 /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1
  /dev/sdf1 /dev/sdg1 /dev/sdh1 /dev/sdi1 /dev/sdj1

  On boot the removable hdd is enumerated as sdd.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: zfs-zed 0.7.5-1ubuntu16
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Tue May 15 11:12:55 2018
  InstallationDate: Installed on 2018-05-08 (7 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1771310/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1771310] Re: zfs doesn't automount after a new disk is plugged in

[Colin Ian King]

Is this still an issue or can we close the bug?

** Changed in: zfs-linux (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1771310

Title:
  zfs doesn't automount after a new disk is plugged in

Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  I've a zfs that automount itself fine. If I plug a USB disk, the
  enumerated list of disk change and on reboot the zfs doesn't automount
  anymore and complains on missing device when trying to manually mount
  it.

  The pool was created with:

  zpool create -f srv raidz3 /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1
  /dev/sdf1 /dev/sdg1 /dev/sdh1 /dev/sdi1 /dev/sdj1

  On boot the removable hdd is enumerated as sdd.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: zfs-zed 0.7.5-1ubuntu16
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Tue May 15 11:12:55 2018
  InstallationDate: Installed on 2018-05-08 (7 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1771310/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1889110] Re: zfs pool locks and see "INFO: task txg_sync:4307 blocked for more than 120 seconds. "

[Rob Babb]

Hi Colin,

It seems to happen on 2 different controllers (both LSI). I'm using the
9201-16e at the moment and it performs much faster overall, but doing
something like a zfs scrub on a pool still causes the resets and thus
zfs locks as part of those. Basically seems to be under heavy IO load.
Although, this controller can handle much heavier IO that just a single
scrub. For example, it seems much more likely to happen on my 3.5" 2TB
and 3TB HDD drives, as opposed to my 2.5" 1TB SSD's. The SSD's scream
through a scrub in about an hour, whereas the HDD's take a day or more.

The only thing I can think of is maybe to increase direct cooling on the
controller in case it's overheating. But this is a Dell R710 server
chassis with lots of high volume airflow.

It's really hard to pinpoint the problem between controller, driver, and
filesystem.

-- 
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/1889110

Title:
  zfs pool locks and see "INFO: task txg_sync:4307 blocked for more than
  120 seconds. "

Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  ZFS filesystem becomes unresponsive and subsequent NFS shares
  unresponsive. ESXi sees all paths down.

  See this error 3 times in a row.

  
  [184383.479511] INFO: task txg_sync:4307 blocked for more than 120 seconds.   

  
  [184383.479565]   Tainted: P  IO  5.4.0-42-generic #46-Ubuntu 

  
  [184383.479607] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.   

  [184383.479655] txg_syncD0  4307  2 0x80004000

  
  [184383.479658] Call Trace:   

  
  [184383.479670]  __schedule+0x2e3/0x740   

  
  [184383.479673]  schedule+0x42/0xb0   

  
  [184383.479676]  schedule_timeout+0x152/0x2f0 

  
  [184383.479683]  ? __next_timer_interrupt+0xe0/0xe0   

  
  [184383.479685]  io_schedule_timeout+0x1e/0x50

  
  [184383.479697]  __cv_timedwait_common+0x15e/0x1c0 [spl]  

  
  [184383.479702]  ? wait_woken+0x80/0x80   

  
  [184383.479710]  __cv_timedwait_io+0x19/0x20 [spl]

  
  [184383.479816]  zio_wait+0x11b/0x230 [zfs]   

  
  [184383.479905]  ? __raw_spin_unlock+0x9/0x10 [zfs]   

  
  [184383.479983]  dsl_pool_sync+0xbc/0x410 [zfs]   

  
  [184383.480069]  spa_sync_iterate_to_convergence+0xe0/0x1c0 [zfs] 

  
  [184383.480156]  spa_sync+0x312/0x5b0 

[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices

[Cristian Waimann]

Hello Kai,

I compiled your test kernel and there was a warning while installing it
that could be referred to the problem we are living. I am copying the
output lines of:

>> sudo dpkg -i linux-image-5.9.0-rc3+_5.9.0-rc3+-1_amd64.deb

This is the output:
-
update-initramfs: Generating /boot/initrd.img-5.9.0-rc3+
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125b-2.fw for module 
r8169
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.9.0-rc3+
Found initrd image: /boot/initrd.img-5.9.0-rc3+
Found linux image: /boot/vmlinuz-5.4.0-45-generic
Found initrd image: /boot/initrd.img-5.4.0-45-generic
Found linux image: /boot/vmlinuz-5.4.0-42-generic
Found initrd image: /boot/initrd.img-5.4.0-42-generic
Adding boot menu entry for UEFI Firmware Settings
done
-

Unfortunately touchpad is still unrecognized

Thanks for our efforts.

I tried to contact Lenovo Support team and their answer is really
disappointing. They said Lenovo IML 15 is not certified for linux
systems, so, I should use Windows instead. Thing is that I don't like
their solution

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux 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

Bug description:
  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 1872108] Re: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal

[ash]

That's great. Thank you for the update Hui Wang

-- 
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/1872108

Title:
  Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal

Status in alsa-ucm-conf package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Related to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845677/comments/14

  Audio works and the volume seems reasonable however the audio is
  noticeably missing bass giving everything a high treble sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-ucm-conf 1.2.2-1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 10 09:17:33 2020
  Dependencies:

  InstallationDate: Installed on 2020-04-08 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-ucm-conf
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Dependencies:
   
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-08 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  Package: linux
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1891288] Re: arm64 gcov in 5.8 breaks when trying to enable it

[Colin Ian King]

This is due to using gcc-10.2. Building with gcc-9 is fine. This
compiler support for GCOV will be disabled, see
https://lkml.org/lkml/2020/9/2/934

So, marking this as Won't Fix because there is a workaround and 10.2 is
not looking favourably for GCOV support at the moment.

** Changed in: linux (Ubuntu)
   Status: In Progress => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1891288

Title:
  arm64 gcov in 5.8 breaks when trying to enable it

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  Running:

  sudo lcov --zerocounters on a gcov enabled kernel causes a read-only
  splat:

  
  [  139.798968] Unable to handle kernel write to read-only memory at virtual 
address b4511ee6bb10
  [  139.803325] Mem abort info:
  [  139.804882]   ESR = 0x964e
  [  139.806265]   EC = 0x25: DABT (current EL), IL = 32 bits
  [  139.811261]   SET = 0, FnV = 0
  [  139.814163]   EA = 0, S1PTW = 0
  [  139.816545] Data abort info:
  [  139.817852]   ISV = 0, ISS = 0x004e
  [  139.820023]   CM = 0, WnR = 1
  [  139.821350] swapper pgtable: 4k pages, 48-bit VAs, pgdp=5086f000
  [  139.825005] [b4511ee6bb10] pgd=0001b6fff003, p4d=0001b6fff003, 
pud=0001b6ffe003, pmd=00404e200f91
  [  139.832061] Internal error: Oops: 964e [#1] SMP
  [  139.835002] Modules linked in: nls_iso8859_1 dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua efi_pstore qemu_fw_cfg sch_fq_codel drm virtio_rng ip_t
  ables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c rai
  d1 raid0 multipath linear crct10dif_ce ghash_ce sha2_ce sha256_arm64 sha1_ce 
virtio_net net_failover xhci_pci virtio_blk virtio_scsi failover xhci_pci_ren
  esas aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher
  [  139.865929] CPU: 5 PID: 1235 Comm: lcov Tainted: GW 
5.8.0-8-generic #9
  [  139.871293] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015
  [  139.876248] pstate: 2045 (nzCv daif +PAN -UAO BTYPE=--)
  [  139.879993] pc : __memset+0x148/0x188
  [  139.882387] lr : gcov_info_reset+0xa0/0x110
  [  139.885404] sp : 8000122f3bf0
  [  139.887730] x29: 8000122f3bf0 x28: 000167480f40
  [  139.891129] x27:  x26: b450e46bc060
  [  139.894688] x25: 0001 x24: b450e46bc040
  [  139.897391] x23:  x22: b450e46bc0a8
  [  139.900064] x21: b45122ba5db8 x20: b450e46bc068
  [  139.902681] x19: b450e46bc068 x18: 
  [  139.905345] x17:  x16: 
  [  139.908016] x15:  x14: 
  [  139.910625] x13:  x12: 
  [  139.913260] x11:  x10: 
  [  139.915922] x9 :  x8 : b4511ee6bb10
  [  139.918531] x7 :  x6 : 003f
  [  139.921196] x5 : 0040 x4 : 0030
  [  139.923852] x3 : 0007235d7fd0 x2 : 0007235d7fd0
  [  139.926460] x1 :  x0 : b4511ee6bb10
  [  139.929126] Call trace:
  [  139.930349]  __memset+0x148/0x188
  [  139.932025]  reset_node+0x70/0xc0
  [  139.933662]  reset_write+0xc0/0x130
  [  139.935389]  full_proxy_write+0x98/0x110
  [  139.937349]  vfs_write+0x18c/0x3e0
  [  139.939031]  ksys_write+0xc4/0x1f0
  [  139.940766]  __arm64_sys_write+0x44/0x60
  [  139.942705]  invoke_syscall+0x74/0x150
  [  139.944601]  el0_svc_common.constprop.0+0x94/0x264
  [  139.946961]  do_el0_svc+0x5c/0x7c
  [  139.948651]  el0_svc+0x70/0x114
  [  139.950206]  el0_sync_handler+0x140/0x39c
  [  139.952239]  el0_sync+0x17c/0x180
  [  139.953894] Code: f101007f fa45a068 54fffc0b aa0303e2 (a9001d07)
  [  139.956946] ---[ end trace 71e2f9cc3eaddf4e ]---

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1891288/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices

[Kai-Heng Feng]

Can you please blacklist elan_i2c and use i2c-hid instead? I guess it
will start 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/1853277

Title:
  Lenovo ThinkBook 14-IML Touchpad not showing up in
  /proc/bus/input/devices

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  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 1893489] Re: 20.10 gets black screen after login on 5.8.0-16 kernel

[Rob Peters]

** Description changed:

  Using Ubuntu Budgie base of 20.04 and Virtualbox.  Have 20.10 running in
  VB.  With last last kernel update 8.8.0-16 after login in get a black
  screen.   Booting the 5.4 kernel works ok
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  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-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  rob1015 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  rob1015 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Fri Aug 28 15:12:32 2020
  InstallationDate: Installed on 2020-04-30 (120 days ago)
  InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Alpha amd64 
(20200429)
  IwConfig:
-  lono wireless extensions.
-  
-  enp0s3no wireless extensions.
+  lono wireless extensions.
+ 
+  enp0s3no wireless extensions.
  Lsusb:
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
-  Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
-  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
+  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
-  /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
-  |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
-  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M
+  /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
+  |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
+  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=8ca86e24-ebcc-44dd-a552-a66c1612724f 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.190
+  linux-restricted-modules-5.4.0-42-generic N/A
+  linux-backports-modules-5.4.0-42-generic  N/A
+  linux-firmware1.190
  RfKill:
-  
+ 
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

** Description changed:

  Using Ubuntu Budgie base of 20.04 and Virtualbox.  Have 20.10 running in
- VB.  With last last kernel update 8.8.0-16 after login in get a black
+ VB.  With last last kernel update 5.8.0.16 after login in get a black
  screen.   Booting the 5.4 kernel works ok
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  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-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob1015 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Fri Aug 28 15:12:32 2020
  InstallationDate: Installed on 2020-04-30 (120 days ago)
  InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Alpha amd64 
(20200429)
  IwConfig:
   lono wireless extensions.
  
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=8ca86e24-ebcc-44dd-a552-a66c1612724f 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.190
  RfKill:
  
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  

[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices

[Cristian Waimann]

Hi Kai,

attached on this message are the log files for dmesg, udevadm and the
prpduct version.

I have to point out two things:

1) I don't know how, but on ONE occasion TOUCHPAD WORKED with your
kernel. It worked with its basic functions. However never happened again
after several reboots.

2) Shut down or reboot is not working on your kernel. I have to press
power button to power off the laptop since it is waiting for some action
that never occurred.

Thanks again Kai


** Attachment added: "logs.tar"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+attachment/5407431/+files/logs.tar

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux 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

Bug description:
  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 1893956] Re: Intel NIC LOMs do not work on Focal

[Jeff Lane]

** Tags added: blocks-hwcert-server

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1893956

Title:
  Intel NIC LOMs do not work on Focal

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  In Progress

Bug description:
  The latest Intel NIC based LOMs do not work fully on Focal.

  These devices have 4 ports, but only two seem to work and this has
  been seen on at least two different systems using LOMs based on this.

  We've discovered via testing that while the i40e driver in 5.4 fails,
  the version in 5.8 works, so that's the point to start patching.

  First batch of patches to try:
  d5226fa6dbae (tag: v5.5) Linux 5.5
  | * 959b1825d9ab i40e: fix spelling mistake "to" -> "too"
  | * def9d2780727 (tag: v5.5-rc7) Linux 5.5-rc7
  | * bb37362f34d6 i40e: Set PHY Access flag on X722
  | * d9d6a9aed3f6 i40e: Fix virtchnl_queue_select bitmap validation
  | | * b3a987b0264d (tag: v5.5-rc6) Linux 5.5-rc6
  | | * c79f46a28239 (tag: v5.5-rc5) Linux 5.5-rc5
  | |/··
  | * fd6988496e79 (tag: v5.5-rc4) Linux 5.5-rc4
  | * 46cf053efec6 (tag: v5.5-rc3) Linux 5.5-rc3
  | * b3873a5be757 net/i40e: Fix concurrency issues between config flow and XSK
  |/··
  | * d1eef1c61974 (tag: v5.5-rc2) Linux 5.5-rc2
  | * c593642c8be0 treewide: Use sizeof_field() macro
  |/··
  * e42617b825f8 (tag: v5.5-rc1) Linux 5.5-rc1
  * 12299132b3d3 net: ethernet: intel: Demote MTU change prints to debug
  * dc645daef9af i40e: implement VF stats NDO

  Already in kernel
  * e42b7e9cefca i40e: Wrong 'Advertised FEC modes' after set FEC to AUTO
  * 998e5166e604 i40e: initialize ITRN registers with correct values
  * 27d461333459 i40e: prevent memory leak in i40e_setup_macvlans

  
  Picked

  * 3df5b9a6a9ec i40e: enable X710 support
  * 3fd8ed563958 i40e: Add UDP segmentation offload support
  * 621650cabee5 i40e: Refactoring VF MAC filters counting to make more reliable
  * d80a476f4a12 i40e: Fix LED blinking flow for X710T*L devices
  * cdb89f15bd46 i40e: allow ethtool to report SW and FW versions in recovery 
mode
  * ff9246571a2e i40e: Fix for persistent lldp support
  * a3e09ded6a6d i40e: Extract detection of HW flags into a function
  * 0514db37dd78 i40e: Extend PHY access with page change flag

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893956/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14

[Francisco Soares]

+1 same problem with me, asus UX425JA

5.4.0-45-generic #49-Ubuntu SMP Wed Aug 26 13:38:52 UTC 2020 x86_64
x86_64 x86_64 GNU/Linux

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1810183

Title:
  numpad on touchpad doesn't work in ASUS Zenbook 14

Status in Linux:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside 
windows 10. 
  The numeric keypads are within the touchpad and are supposed to be turned on 
by a button on the touchpad. This works well in Windows but doesn't work in 
Ubuntu. 
  I have tried to search for any related problems/solutions online but I 
haven't been able to.
  I will appreciate any suggestion or help.
  Thanks,
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-30 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: linux (not installed)
  Tags:  cosmic
  Uname: Linux 4.19.11-041911-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-30 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: linux (not installed)
  Tags:  cosmic
  Uname: Linux 4.18.10-041810-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1852116] Re: zfs send / recv properties failing

[Colin Ian King]

Apologies for taking so long to reply. Ubuntu 19.10 is now end-of-life.
Is this still an issue on 20.04?

** Changed in: zfs-linux (Ubuntu)
   Status: New => Incomplete

** Changed in: zfs-linux (Ubuntu)
   Importance: Undecided => Medium

-- 
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/1852116

Title:
  zfs send / recv properties failing

Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  Running Ubuntu 19.10 on both the send and recv systems.

  I can't send properties. If I don't include the -p switch, all is
  good.

  If I include the -p switch it looks like it is going to work, but it
  hangs like this:

  sudo /usr/sbin/zfs send -vp -I tank/vm@2019-11-02_22-41-35__daily__batch1 
tank/vm@2019-11-05_18-26-01__daily__batch1 | /bin/ssh back1 sudo /usr/sbin/zfs 
recv -vu backup/vm
  send from @2019-11-02_22-41-35__daily__batch1 to 
tank/vm@2019-11-05_18-24-41__daily__batch1 estimated size is 4.12G
  send from @2019-11-05_18-24-41__daily__batch1 to 
tank/vm@2019-11-05_18-26-01__daily__batch1 estimated size is 2.50M
  total estimated size is 4.13G
  TIME SENT SNAPSHOT tank/vm@2019-11-05_18-24-41__daily__batch1
  receiving incremental stream of tank/vm@2019-11-05_18-24-41__daily__batch1 
into backup/vm@2019-11-05_18-24-41__daily__batch1
  20:03:24 2.06M tank/vm@2019-11-05_18-24-41__daily__batch1
  20:03:25 2.06M tank/vm@2019-11-05_18-24-41__daily__batch1
  20:03:26 2.06M tank/vm@2019-11-05_18-24-41__daily__batch1
  20:03:27 2.06M tank/vm@2019-11-05_18-24-41__daily__batch1
  20:03:28 2.06M tank/vm@2019-11-05_18-24-41__daily__batch1
  20:03:29 2.06M tank/vm@2019-11-05_18-24-41__daily__batch1
  20:03:30 2.06M tank/vm@2019-11-05_18-24-41__daily__batch1

  Then I have to kill it.

  Any thoughts?
  thanks,
  Geoff

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1852116/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices

[Cristian Waimann]

I edited /etc/modprobe.d/blacklist.conf file. I added the following line
at the end of the file:

blacklist elan_i2c

After that I rebooted the laptop but touchpad is still not recognized

Do I have to do any extra action to be sure it is using i2c-hid ?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux 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

Bug description:
  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 1892422] Re: Pci passthrough interface not showing up in Ubuntu 20.04 but does show in 18.04

[Tim Epkes]

I relayed to Neil, he'll follow the guidance above and let you know
results.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1892422

Title:
  Pci passthrough interface not showing up in Ubuntu 20.04 but does show
  in 18.04

Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  
  After setting up pci pass through for a virtual function it did not show up 
as an interface in Ubuntu 20.04, it did however show up as a PCI device. 
  After reverting back to 18.04 with exactly the same configuration the 
interface showed up as expected.
  Bellow is the configuration and output for both 18.04 and 20.04.

  virt-install 
  --import 
  --connect qemu:///system --name emsk8sm1 --ram 8192 
  --disk pool/emsk8sm1/emsk8sm1.img,format=img,bus=virtio   
  --disk  cidata.img,device=cdrom,format=img  
  --vcpus 4 --cpu host --os-type linux --os-variant ubuntu18.04
  --network 
bridge=br0,model=virtio,virtualport_type=openvswitch,mac=52:54:00:8a:9c:ea
  --hostdev 3b:02.5
  --console pty,target_type=serial
  --graphics type=vnc,listen=0.0.0.0 
  --noautoconsole
  --autostart -v


  Configuration of 18.04 where the passthrough works

  Version
  Linux emsk8sm1 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

  virsh dumpxml emsk8sm1
  






  


  lspci | grep Ethernet
  00:03.0 Ethernet controller: Red Hat, Inc. Virtio network device
  00:06.0 Ethernet controller: Intel Corporation Ethernet Virtual Function 700 
Series (rev 02)  <--- Pass through interface

  
  ip link show [interface shows inside of vm ens6]
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc fq_codel state UP 
mode DEFAULT group default qlen 1000
  link/ether 52:54:00:8a:9c:ea brd ff:ff:ff:ff:ff:ff
  3: ens6:  mtu 1500 qdisc mq state UP mode 
DEFAULT group default qlen 1000
  link/ether ea:99:ea:36:3e:63 brd ff:ff:ff:ff:ff:ff


  Configuration of 20.04 where the VF shows as a PCI device but does not show 
as an interface

  Version
  Linux emsk8sm1 5.4.0-1020-kvm #20-Ubuntu SMP Fri Jul 10 05:03:04 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

  virsh dumpxml emsk8sm1
  






  


  lspci | grep Ethernet
  00:03.0 Ethernet controller: Red Hat, Inc. Virtio network device
  00:06.0 Ethernet controller: Intel Corporation Ethernet Virtual Function 700 
Series (rev 02)   <--- Pass through interface

  
  ip link show [ens 6 does not show as an interface} 
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc pfifo_fast state UP 
mode DEFAULT group default qlen 1000
  link/ether 52:54:00:8a:9c:ea brd ff:ff:ff:ff:ff:ff
  3: tunl0@NONE:  mtu 1480 qdisc noop state DOWN mode DEFAULT group 
default qlen 1000
  link/ipip 0.0.0.0 brd 0.0.0.0
  4: sit0@NONE:  mtu 1480 qdisc noop state DOWN mode DEFAULT group 
default qlen 1000
  link/sit 0.0.0.0 brd 0.0.0.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892422/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1892397] Re: Fix statistics on Broadcom Ethernet driver

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oracle - 5.8.0-1001.1

---
linux-oracle (5.8.0-1001.1) groovy; urgency=medium

  * groovy/linux-oracle: 5.8.0-1001.1 -proposed tracker (LP: #1892957)

  * Packaging resync (LP: #1786013)
- [Packaging] update update.conf

  * Miscellaneous Ubuntu changes
- [packaging] debhelper-compat (= 10)
- [Config] updateconfigs following 5.8.0-18.19 rebase
- annotations: retire SND_SOC_SOF_HDA_COMMON_HDMI_CODEC
- [packaging] add required dwarves build dependency
- [Config] Remove variables for vbox/wireguard dkms builds
- [Config] Enable nvidia server dkms build
- [Config] linux-oracle: move wireguard to the main modules package

  [ Ubuntu: 5.8.0-18.19 ]

  * groovy/linux: 5.8.0-18.19 -proposed tracker (LP: #1893047)
  * Packaging resync (LP: #1786013)
- update dkms package versions
  * Groovy update: v5.8.4 upstream stable release (LP: #1893048)
- drm/vgem: Replace opencoded version of drm_gem_dumb_map_offset()
- drm/panel-simple: Fix inverted V/H SYNC for Frida FRD350H54004 panel
- drm/ast: Remove unused code paths for AST 1180
- drm/ast: Initialize DRAM type before posting GPU
- khugepaged: adjust VM_BUG_ON_MM() in __khugepaged_enter()
- ALSA: hda: avoid reset of sdo_limit
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Flex Book
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Book Ion
- can: j1939: transport: j1939_session_tx_dat(): fix use-after-free read in
  j1939_tp_txtimer()
- can: j1939: socket: j1939_sk_bind(): make sure ml_priv is allocated
- spi: Prevent adding devices below an unregistering controller
- io_uring: find and cancel head link async work on files exit
- mm/vunmap: add cond_resched() in vunmap_pmd_range
- romfs: fix uninitialized memory leak in romfs_dev_read()
- kernel/relay.c: fix memleak on destroy relay channel
- uprobes: __replace_page() avoid BUG in munlock_vma_page()
- squashfs: avoid bio_alloc() failure with 1Mbyte blocks
- mm: include CMA pages in lowmem_reserve at boot
- mm, page_alloc: fix core hung in free_pcppages_bulk()
- ASoC: amd: renoir: restore two more registers during resume
- RDMA/hfi1: Correct an interlock issue for TID RDMA WRITE request
- opp: Enable resources again if they were disabled earlier
- opp: Put opp table in dev_pm_opp_set_rate() for empty tables
- opp: Put opp table in dev_pm_opp_set_rate() if _set_opp_bw() fails
- ext4: do not block RWF_NOWAIT dio write on unallocated space
- ext4: fix checking of directory entry validity for inline directories
- jbd2: add the missing unlock_buffer() in the error path of
  jbd2_write_superblock()
- scsi: zfcp: Fix use-after-free in request timeout handlers
- selftests: kvm: Use a shorter encoding to clear RAX
- s390/pci: fix zpci_bus_link_virtfn()
- s390/pci: re-introduce zpci_remove_device()
- s390/pci: fix PF/VF linking on hot plug
- s390/pci: ignore stale configuration request event
- mm/memory.c: skip spurious TLB flush for retried page fault
- drm: amdgpu: Use the correct size when allocating memory
- drm/amdgpu/display: use GFP_ATOMIC in dcn20_validate_bandwidth_internal
- drm/amd/display: Fix incorrect backlight register offset for DCN
- drm/amd/display: Fix EDID parsing after resume from suspend
- drm/amd/display: Blank stream before destroying HDCP session
- drm/amd/display: Fix DFPstate hang due to view port changed
- drm/amd/display: fix pow() crashing when given base 0
- drm/i915/pmu: Prefer drm_WARN_ON over WARN_ON
- drm/i915: Provide the perf pmu.module
- scsi: ufs: Add DELAY_BEFORE_LPM quirk for Micron devices
- scsi: target: tcmu: Fix crash in tcmu_flush_dcache_range on ARM
- media: budget-core: Improve exception handling in budget_register()
- media: coda: jpeg: add NULL check after kmalloc
- f2fs: fix to check page dirty status before writeback
- rtc: goldfish: Enable interrupt in set_alarm() when necessary
- media: vpss: clean up resources in init
- f2fs: should avoid inode eviction in synchronous path
- Input: psmouse - add a newline when printing 'proto' by sysfs
- MIPS: Fix unable to reserve memory for Crash kernel
- m68knommu: fix overwriting of bits in ColdFire V3 cache control
- svcrdma: Fix another Receive buffer leak
- xfs: fix inode quota reservation checks
- drm/ttm: fix offset in VMAs with a pg_offs in ttm_bo_vm_access
- riscv: Fixup static_obj() fail
- jffs2: fix UAF problem
- ceph: fix use-after-free for fsc->mdsc
- swiotlb-xen: use vmalloc_to_page on vmalloc virt addresses
- cpufreq: intel_pstate: Fix cpuinfo_max_freq when MSR_TURBO_RATIO_LIMIT is 0
- scsi: libfc: Free skb in fc_disc_gpn_id_resp() for valid cases
- virtio_ring: Avoid loop when vq is broken in virtqueue_poll
- media: camss: fix memory leaks on error handling paths in 

[Kernel-packages] [Bug 1894104] Re: Patriot PXD USB SSD cannot be mount with type-C connector

[Matthew Ruffell]

@braingateway

Can you please try booting into the 5.4.0-42-generic kernel and see if
that works?

When you turn your computer on, press and hold the shift key to access the GRUB 
boot menu.
Select "Advanced Options" and then "Ubuntu, with Linux 5.4.0-42-generic"

If 5.4.0-42-generic works and 5.4.0-45-generic doesn't, then we broke
something, and we will likely need to bisect to find the fix.

** Also affects: linux (Ubuntu Focal)
   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/1894104

Title:
  Patriot PXD USB SSD cannot be mount with type-C connector

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  New

Bug description:
  It works fine a few weeks ago. But after recent kernel/driver updates.
  It stops working. It still works if I connect it to USB 3.1 5000M
  port. if I connect it to 1M port, it stops working.

  I can still use `smartctl -a -d sntjmicron /dev/sdx` to obtain the
  smart data. But any block operation will fail with remote I/O error:
  mount, format, dd, etc

  The port is find, I connected other device to it, it is still working without 
issue. The USB controller and storage device are:
  ```
  USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host 
Controller (rev 10)
  ID 13fe:2570 Kingston Technology Company Inc. Patriot Memory
  ```

  kernel
  ```
  5.4.0-45-generic #49-Ubuntu SMP Wed Aug 26 13:38:52 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/1894104/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1889384] Re: ASPM not enabled on child devices behind VMD controller

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.8.0-18.19

---
linux (5.8.0-18.19) groovy; urgency=medium

  * groovy/linux: 5.8.0-18.19 -proposed tracker (LP: #1893047)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Groovy update: v5.8.4 upstream stable release (LP: #1893048)
- drm/vgem: Replace opencoded version of drm_gem_dumb_map_offset()
- drm/panel-simple: Fix inverted V/H SYNC for Frida FRD350H54004 panel
- drm/ast: Remove unused code paths for AST 1180
- drm/ast: Initialize DRAM type before posting GPU
- khugepaged: adjust VM_BUG_ON_MM() in __khugepaged_enter()
- ALSA: hda: avoid reset of sdo_limit
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Flex Book
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Book Ion
- can: j1939: transport: j1939_session_tx_dat(): fix use-after-free read in
  j1939_tp_txtimer()
- can: j1939: socket: j1939_sk_bind(): make sure ml_priv is allocated
- spi: Prevent adding devices below an unregistering controller
- io_uring: find and cancel head link async work on files exit
- mm/vunmap: add cond_resched() in vunmap_pmd_range
- romfs: fix uninitialized memory leak in romfs_dev_read()
- kernel/relay.c: fix memleak on destroy relay channel
- uprobes: __replace_page() avoid BUG in munlock_vma_page()
- squashfs: avoid bio_alloc() failure with 1Mbyte blocks
- mm: include CMA pages in lowmem_reserve at boot
- mm, page_alloc: fix core hung in free_pcppages_bulk()
- ASoC: amd: renoir: restore two more registers during resume
- RDMA/hfi1: Correct an interlock issue for TID RDMA WRITE request
- opp: Enable resources again if they were disabled earlier
- opp: Put opp table in dev_pm_opp_set_rate() for empty tables
- opp: Put opp table in dev_pm_opp_set_rate() if _set_opp_bw() fails
- ext4: do not block RWF_NOWAIT dio write on unallocated space
- ext4: fix checking of directory entry validity for inline directories
- jbd2: add the missing unlock_buffer() in the error path of
  jbd2_write_superblock()
- scsi: zfcp: Fix use-after-free in request timeout handlers
- selftests: kvm: Use a shorter encoding to clear RAX
- s390/pci: fix zpci_bus_link_virtfn()
- s390/pci: re-introduce zpci_remove_device()
- s390/pci: fix PF/VF linking on hot plug
- s390/pci: ignore stale configuration request event
- mm/memory.c: skip spurious TLB flush for retried page fault
- drm: amdgpu: Use the correct size when allocating memory
- drm/amdgpu/display: use GFP_ATOMIC in dcn20_validate_bandwidth_internal
- drm/amd/display: Fix incorrect backlight register offset for DCN
- drm/amd/display: Fix EDID parsing after resume from suspend
- drm/amd/display: Blank stream before destroying HDCP session
- drm/amd/display: Fix DFPstate hang due to view port changed
- drm/amd/display: fix pow() crashing when given base 0
- drm/i915/pmu: Prefer drm_WARN_ON over WARN_ON
- drm/i915: Provide the perf pmu.module
- scsi: ufs: Add DELAY_BEFORE_LPM quirk for Micron devices
- scsi: target: tcmu: Fix crash in tcmu_flush_dcache_range on ARM
- media: budget-core: Improve exception handling in budget_register()
- media: coda: jpeg: add NULL check after kmalloc
- f2fs: fix to check page dirty status before writeback
- rtc: goldfish: Enable interrupt in set_alarm() when necessary
- media: vpss: clean up resources in init
- f2fs: should avoid inode eviction in synchronous path
- Input: psmouse - add a newline when printing 'proto' by sysfs
- MIPS: Fix unable to reserve memory for Crash kernel
- m68knommu: fix overwriting of bits in ColdFire V3 cache control
- svcrdma: Fix another Receive buffer leak
- xfs: fix inode quota reservation checks
- drm/ttm: fix offset in VMAs with a pg_offs in ttm_bo_vm_access
- riscv: Fixup static_obj() fail
- jffs2: fix UAF problem
- ceph: fix use-after-free for fsc->mdsc
- swiotlb-xen: use vmalloc_to_page on vmalloc virt addresses
- cpufreq: intel_pstate: Fix cpuinfo_max_freq when MSR_TURBO_RATIO_LIMIT is 0
- scsi: libfc: Free skb in fc_disc_gpn_id_resp() for valid cases
- virtio_ring: Avoid loop when vq is broken in virtqueue_poll
- media: camss: fix memory leaks on error handling paths in probe
- tools/testing/selftests/cgroup/cgroup_util.c: cg_read_strcmp: fix null
  pointer dereference
- xfs: Fix UBSAN null-ptr-deref in xfs_sysfs_init
- alpha: fix annotation of io{read,write}{16,32}be()
- fat: fix fat_ra_init() for data clusters == 0
- fs/signalfd.c: fix inconsistent return codes for signalfd4
- ext4: fix potential negative array index in do_split()
- drm/virtio: fix missing dma_fence_put() in virtio_gpu_execbuffer_ioctl()
- ext4: don't allow overlapping system zones
- ext4: check journal inode extents more carefully
- netfilter: nf_tables: nft_exthdr: 

[Kernel-packages] [Bug 1890845] Re: update ENA driver for LLQ acceleration mode, new hw support

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.8.0-18.19

---
linux (5.8.0-18.19) groovy; urgency=medium

  * groovy/linux: 5.8.0-18.19 -proposed tracker (LP: #1893047)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Groovy update: v5.8.4 upstream stable release (LP: #1893048)
- drm/vgem: Replace opencoded version of drm_gem_dumb_map_offset()
- drm/panel-simple: Fix inverted V/H SYNC for Frida FRD350H54004 panel
- drm/ast: Remove unused code paths for AST 1180
- drm/ast: Initialize DRAM type before posting GPU
- khugepaged: adjust VM_BUG_ON_MM() in __khugepaged_enter()
- ALSA: hda: avoid reset of sdo_limit
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Flex Book
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Book Ion
- can: j1939: transport: j1939_session_tx_dat(): fix use-after-free read in
  j1939_tp_txtimer()
- can: j1939: socket: j1939_sk_bind(): make sure ml_priv is allocated
- spi: Prevent adding devices below an unregistering controller
- io_uring: find and cancel head link async work on files exit
- mm/vunmap: add cond_resched() in vunmap_pmd_range
- romfs: fix uninitialized memory leak in romfs_dev_read()
- kernel/relay.c: fix memleak on destroy relay channel
- uprobes: __replace_page() avoid BUG in munlock_vma_page()
- squashfs: avoid bio_alloc() failure with 1Mbyte blocks
- mm: include CMA pages in lowmem_reserve at boot
- mm, page_alloc: fix core hung in free_pcppages_bulk()
- ASoC: amd: renoir: restore two more registers during resume
- RDMA/hfi1: Correct an interlock issue for TID RDMA WRITE request
- opp: Enable resources again if they were disabled earlier
- opp: Put opp table in dev_pm_opp_set_rate() for empty tables
- opp: Put opp table in dev_pm_opp_set_rate() if _set_opp_bw() fails
- ext4: do not block RWF_NOWAIT dio write on unallocated space
- ext4: fix checking of directory entry validity for inline directories
- jbd2: add the missing unlock_buffer() in the error path of
  jbd2_write_superblock()
- scsi: zfcp: Fix use-after-free in request timeout handlers
- selftests: kvm: Use a shorter encoding to clear RAX
- s390/pci: fix zpci_bus_link_virtfn()
- s390/pci: re-introduce zpci_remove_device()
- s390/pci: fix PF/VF linking on hot plug
- s390/pci: ignore stale configuration request event
- mm/memory.c: skip spurious TLB flush for retried page fault
- drm: amdgpu: Use the correct size when allocating memory
- drm/amdgpu/display: use GFP_ATOMIC in dcn20_validate_bandwidth_internal
- drm/amd/display: Fix incorrect backlight register offset for DCN
- drm/amd/display: Fix EDID parsing after resume from suspend
- drm/amd/display: Blank stream before destroying HDCP session
- drm/amd/display: Fix DFPstate hang due to view port changed
- drm/amd/display: fix pow() crashing when given base 0
- drm/i915/pmu: Prefer drm_WARN_ON over WARN_ON
- drm/i915: Provide the perf pmu.module
- scsi: ufs: Add DELAY_BEFORE_LPM quirk for Micron devices
- scsi: target: tcmu: Fix crash in tcmu_flush_dcache_range on ARM
- media: budget-core: Improve exception handling in budget_register()
- media: coda: jpeg: add NULL check after kmalloc
- f2fs: fix to check page dirty status before writeback
- rtc: goldfish: Enable interrupt in set_alarm() when necessary
- media: vpss: clean up resources in init
- f2fs: should avoid inode eviction in synchronous path
- Input: psmouse - add a newline when printing 'proto' by sysfs
- MIPS: Fix unable to reserve memory for Crash kernel
- m68knommu: fix overwriting of bits in ColdFire V3 cache control
- svcrdma: Fix another Receive buffer leak
- xfs: fix inode quota reservation checks
- drm/ttm: fix offset in VMAs with a pg_offs in ttm_bo_vm_access
- riscv: Fixup static_obj() fail
- jffs2: fix UAF problem
- ceph: fix use-after-free for fsc->mdsc
- swiotlb-xen: use vmalloc_to_page on vmalloc virt addresses
- cpufreq: intel_pstate: Fix cpuinfo_max_freq when MSR_TURBO_RATIO_LIMIT is 0
- scsi: libfc: Free skb in fc_disc_gpn_id_resp() for valid cases
- virtio_ring: Avoid loop when vq is broken in virtqueue_poll
- media: camss: fix memory leaks on error handling paths in probe
- tools/testing/selftests/cgroup/cgroup_util.c: cg_read_strcmp: fix null
  pointer dereference
- xfs: Fix UBSAN null-ptr-deref in xfs_sysfs_init
- alpha: fix annotation of io{read,write}{16,32}be()
- fat: fix fat_ra_init() for data clusters == 0
- fs/signalfd.c: fix inconsistent return codes for signalfd4
- ext4: fix potential negative array index in do_split()
- drm/virtio: fix missing dma_fence_put() in virtio_gpu_execbuffer_ioctl()
- ext4: don't allow overlapping system zones
- ext4: check journal inode extents more carefully
- netfilter: nf_tables: nft_exthdr: 

[Kernel-packages] [Bug 1890136] Re: Fix false-negative return value for rtnetlink.sh in kselftests/net

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.8.0-18.19

---
linux (5.8.0-18.19) groovy; urgency=medium

  * groovy/linux: 5.8.0-18.19 -proposed tracker (LP: #1893047)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Groovy update: v5.8.4 upstream stable release (LP: #1893048)
- drm/vgem: Replace opencoded version of drm_gem_dumb_map_offset()
- drm/panel-simple: Fix inverted V/H SYNC for Frida FRD350H54004 panel
- drm/ast: Remove unused code paths for AST 1180
- drm/ast: Initialize DRAM type before posting GPU
- khugepaged: adjust VM_BUG_ON_MM() in __khugepaged_enter()
- ALSA: hda: avoid reset of sdo_limit
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Flex Book
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Book Ion
- can: j1939: transport: j1939_session_tx_dat(): fix use-after-free read in
  j1939_tp_txtimer()
- can: j1939: socket: j1939_sk_bind(): make sure ml_priv is allocated
- spi: Prevent adding devices below an unregistering controller
- io_uring: find and cancel head link async work on files exit
- mm/vunmap: add cond_resched() in vunmap_pmd_range
- romfs: fix uninitialized memory leak in romfs_dev_read()
- kernel/relay.c: fix memleak on destroy relay channel
- uprobes: __replace_page() avoid BUG in munlock_vma_page()
- squashfs: avoid bio_alloc() failure with 1Mbyte blocks
- mm: include CMA pages in lowmem_reserve at boot
- mm, page_alloc: fix core hung in free_pcppages_bulk()
- ASoC: amd: renoir: restore two more registers during resume
- RDMA/hfi1: Correct an interlock issue for TID RDMA WRITE request
- opp: Enable resources again if they were disabled earlier
- opp: Put opp table in dev_pm_opp_set_rate() for empty tables
- opp: Put opp table in dev_pm_opp_set_rate() if _set_opp_bw() fails
- ext4: do not block RWF_NOWAIT dio write on unallocated space
- ext4: fix checking of directory entry validity for inline directories
- jbd2: add the missing unlock_buffer() in the error path of
  jbd2_write_superblock()
- scsi: zfcp: Fix use-after-free in request timeout handlers
- selftests: kvm: Use a shorter encoding to clear RAX
- s390/pci: fix zpci_bus_link_virtfn()
- s390/pci: re-introduce zpci_remove_device()
- s390/pci: fix PF/VF linking on hot plug
- s390/pci: ignore stale configuration request event
- mm/memory.c: skip spurious TLB flush for retried page fault
- drm: amdgpu: Use the correct size when allocating memory
- drm/amdgpu/display: use GFP_ATOMIC in dcn20_validate_bandwidth_internal
- drm/amd/display: Fix incorrect backlight register offset for DCN
- drm/amd/display: Fix EDID parsing after resume from suspend
- drm/amd/display: Blank stream before destroying HDCP session
- drm/amd/display: Fix DFPstate hang due to view port changed
- drm/amd/display: fix pow() crashing when given base 0
- drm/i915/pmu: Prefer drm_WARN_ON over WARN_ON
- drm/i915: Provide the perf pmu.module
- scsi: ufs: Add DELAY_BEFORE_LPM quirk for Micron devices
- scsi: target: tcmu: Fix crash in tcmu_flush_dcache_range on ARM
- media: budget-core: Improve exception handling in budget_register()
- media: coda: jpeg: add NULL check after kmalloc
- f2fs: fix to check page dirty status before writeback
- rtc: goldfish: Enable interrupt in set_alarm() when necessary
- media: vpss: clean up resources in init
- f2fs: should avoid inode eviction in synchronous path
- Input: psmouse - add a newline when printing 'proto' by sysfs
- MIPS: Fix unable to reserve memory for Crash kernel
- m68knommu: fix overwriting of bits in ColdFire V3 cache control
- svcrdma: Fix another Receive buffer leak
- xfs: fix inode quota reservation checks
- drm/ttm: fix offset in VMAs with a pg_offs in ttm_bo_vm_access
- riscv: Fixup static_obj() fail
- jffs2: fix UAF problem
- ceph: fix use-after-free for fsc->mdsc
- swiotlb-xen: use vmalloc_to_page on vmalloc virt addresses
- cpufreq: intel_pstate: Fix cpuinfo_max_freq when MSR_TURBO_RATIO_LIMIT is 0
- scsi: libfc: Free skb in fc_disc_gpn_id_resp() for valid cases
- virtio_ring: Avoid loop when vq is broken in virtqueue_poll
- media: camss: fix memory leaks on error handling paths in probe
- tools/testing/selftests/cgroup/cgroup_util.c: cg_read_strcmp: fix null
  pointer dereference
- xfs: Fix UBSAN null-ptr-deref in xfs_sysfs_init
- alpha: fix annotation of io{read,write}{16,32}be()
- fat: fix fat_ra_init() for data clusters == 0
- fs/signalfd.c: fix inconsistent return codes for signalfd4
- ext4: fix potential negative array index in do_split()
- drm/virtio: fix missing dma_fence_put() in virtio_gpu_execbuffer_ioctl()
- ext4: don't allow overlapping system zones
- ext4: check journal inode extents more carefully
- netfilter: nf_tables: nft_exthdr: 

[Kernel-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.8.0-18.19

---
linux (5.8.0-18.19) groovy; urgency=medium

  * groovy/linux: 5.8.0-18.19 -proposed tracker (LP: #1893047)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Groovy update: v5.8.4 upstream stable release (LP: #1893048)
- drm/vgem: Replace opencoded version of drm_gem_dumb_map_offset()
- drm/panel-simple: Fix inverted V/H SYNC for Frida FRD350H54004 panel
- drm/ast: Remove unused code paths for AST 1180
- drm/ast: Initialize DRAM type before posting GPU
- khugepaged: adjust VM_BUG_ON_MM() in __khugepaged_enter()
- ALSA: hda: avoid reset of sdo_limit
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Flex Book
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Book Ion
- can: j1939: transport: j1939_session_tx_dat(): fix use-after-free read in
  j1939_tp_txtimer()
- can: j1939: socket: j1939_sk_bind(): make sure ml_priv is allocated
- spi: Prevent adding devices below an unregistering controller
- io_uring: find and cancel head link async work on files exit
- mm/vunmap: add cond_resched() in vunmap_pmd_range
- romfs: fix uninitialized memory leak in romfs_dev_read()
- kernel/relay.c: fix memleak on destroy relay channel
- uprobes: __replace_page() avoid BUG in munlock_vma_page()
- squashfs: avoid bio_alloc() failure with 1Mbyte blocks
- mm: include CMA pages in lowmem_reserve at boot
- mm, page_alloc: fix core hung in free_pcppages_bulk()
- ASoC: amd: renoir: restore two more registers during resume
- RDMA/hfi1: Correct an interlock issue for TID RDMA WRITE request
- opp: Enable resources again if they were disabled earlier
- opp: Put opp table in dev_pm_opp_set_rate() for empty tables
- opp: Put opp table in dev_pm_opp_set_rate() if _set_opp_bw() fails
- ext4: do not block RWF_NOWAIT dio write on unallocated space
- ext4: fix checking of directory entry validity for inline directories
- jbd2: add the missing unlock_buffer() in the error path of
  jbd2_write_superblock()
- scsi: zfcp: Fix use-after-free in request timeout handlers
- selftests: kvm: Use a shorter encoding to clear RAX
- s390/pci: fix zpci_bus_link_virtfn()
- s390/pci: re-introduce zpci_remove_device()
- s390/pci: fix PF/VF linking on hot plug
- s390/pci: ignore stale configuration request event
- mm/memory.c: skip spurious TLB flush for retried page fault
- drm: amdgpu: Use the correct size when allocating memory
- drm/amdgpu/display: use GFP_ATOMIC in dcn20_validate_bandwidth_internal
- drm/amd/display: Fix incorrect backlight register offset for DCN
- drm/amd/display: Fix EDID parsing after resume from suspend
- drm/amd/display: Blank stream before destroying HDCP session
- drm/amd/display: Fix DFPstate hang due to view port changed
- drm/amd/display: fix pow() crashing when given base 0
- drm/i915/pmu: Prefer drm_WARN_ON over WARN_ON
- drm/i915: Provide the perf pmu.module
- scsi: ufs: Add DELAY_BEFORE_LPM quirk for Micron devices
- scsi: target: tcmu: Fix crash in tcmu_flush_dcache_range on ARM
- media: budget-core: Improve exception handling in budget_register()
- media: coda: jpeg: add NULL check after kmalloc
- f2fs: fix to check page dirty status before writeback
- rtc: goldfish: Enable interrupt in set_alarm() when necessary
- media: vpss: clean up resources in init
- f2fs: should avoid inode eviction in synchronous path
- Input: psmouse - add a newline when printing 'proto' by sysfs
- MIPS: Fix unable to reserve memory for Crash kernel
- m68knommu: fix overwriting of bits in ColdFire V3 cache control
- svcrdma: Fix another Receive buffer leak
- xfs: fix inode quota reservation checks
- drm/ttm: fix offset in VMAs with a pg_offs in ttm_bo_vm_access
- riscv: Fixup static_obj() fail
- jffs2: fix UAF problem
- ceph: fix use-after-free for fsc->mdsc
- swiotlb-xen: use vmalloc_to_page on vmalloc virt addresses
- cpufreq: intel_pstate: Fix cpuinfo_max_freq when MSR_TURBO_RATIO_LIMIT is 0
- scsi: libfc: Free skb in fc_disc_gpn_id_resp() for valid cases
- virtio_ring: Avoid loop when vq is broken in virtqueue_poll
- media: camss: fix memory leaks on error handling paths in probe
- tools/testing/selftests/cgroup/cgroup_util.c: cg_read_strcmp: fix null
  pointer dereference
- xfs: Fix UBSAN null-ptr-deref in xfs_sysfs_init
- alpha: fix annotation of io{read,write}{16,32}be()
- fat: fix fat_ra_init() for data clusters == 0
- fs/signalfd.c: fix inconsistent return codes for signalfd4
- ext4: fix potential negative array index in do_split()
- drm/virtio: fix missing dma_fence_put() in virtio_gpu_execbuffer_ioctl()
- ext4: don't allow overlapping system zones
- ext4: check journal inode extents more carefully
- netfilter: nf_tables: nft_exthdr: 

[Kernel-packages] [Bug 1886188] Re: linux-libc-dev broken for crossbuilding, Multi-Arch:same violation

[Launchpad Bug Tracker]

This bug was fixed in the package linux-riscv - 5.8.0-1.1

---
linux-riscv (5.8.0-1.1) groovy; urgency=medium

  * groovy/linux-riscv: 5.8.0-1.1 -proposed tracker (LP: #1892958)

  * Packaging resync (LP: #1786013)
- [Packaging] update variants
- [Packaging] update update.conf
- [Packaging] update variants
- [Packaging] update update.conf

  * linux-libc-dev broken for crossbuilding, Multi-Arch:same violation
(LP: #1886188)
- [Config] Move build of linux-libc-dev to primary kernel

  * Miscellaneous Ubuntu changes
- [Packaging] Update debhelper build-depends for compat 10
- [Packaging] Updates for using upstream wireguard driver
- [Config] Update configs for 5.8
- [Config] Update annotations for 5.8
- [Config] Update configs after rebase to 5.8.0-18.19
- [Config] Enable CONFIG_DEBUG_INFO_BTF
- [Config] Update toolchain versions in configs
- [Config] CONFIG_SECURITY_DMESG_RESTRICT=y
- [Config] Update toolchain versions in configs
- [Config] Remove stale enforcements from annotations

 -- Seth Forshee   Thu, 27 Aug 2020 13:42:40
-0500

** Changed in: linux-riscv (Ubuntu Groovy)
   Status: Invalid => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/1886188

Title:
  linux-libc-dev broken for crossbuilding, Multi-Arch:same violation

Status in linux package in Ubuntu:
  Fix Released
Status in linux-riscv package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux-riscv source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Released
Status in linux-riscv source package in Groovy:
  Fix Released

Bug description:
  SRU Justificatoin

  Impact: Building linux-libc-dev for riscv64 from the linux-riscv
  package means that it can have a different version from the package on
  other architectures. This makes it uninstallable for cross building.

  Fix: Move the riscv64 linux-libc-dev build back to the main kernel
  package so that the version will match.

  Test Case: See below.

  Regression Potential: This could cause trouble if the main kernel
  package version is behind the linux-riscv package version, and may
  require artificially inflating the version of the linux package.
  Currently this is not necessary, but it needs to be kept in mind when
  preparing packages for upload with the fixes applied.

  ---

  # apt install linux-libc-dev:amd64 linux-libc-dev:riscv64
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  linux-libc-dev is already the newest version (5.4.0-26.30).
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   linux-libc-dev : Breaks: linux-libc-dev:riscv64 (!= 5.4.0-26.30) but 
5.4.0-27.31 is to be installed
   linux-libc-dev:riscv64 : Breaks: linux-libc-dev (!= 5.4.0-27.31) but 
5.4.0-26.30 is to be installed
  E: Unable to correct problems, you have held broken packages.

  $ rmadison -S linux-libc-dev | grep -e riscv64 -e amd64 | grep -e focal -e 
groovy
   linux-libc-dev | 5.4.0-24.28| focal| riscv64
   linux-libc-dev | 5.4.0-26.30| focal| amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-26.30| groovy   | amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-27.31| groovy   | riscv64
   linux-libc-dev | 5.4.0-28.32| focal-security   | riscv64
   linux-libc-dev | 5.4.0-28.32| focal-updates| riscv64
   linux-libc-dev | 5.4.0-40.44| focal-security   | amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-40.44| focal-updates| amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-40.44| groovy-proposed  | amd64, arm64, armhf, 
i386, ppc64el, s390x

  This is broken.

  linux-libc-dev must have identical content for common files, across
  all architectures, and must have identical version number.

  A few ways to fix this:

  * Either enforce that src:linux & src:linux-riscv are at the same
  version number. But then reasons for splitting riscv into a separate
  build dissappear

  * Make src:linux build _just_ the headers linux-libc-dev for risv64,
  and nothing else. And stop bulding linux-libc-dev form the src:linux-
  riscv package. Just like it does for i386.

  * Or create new src:linux-headers that only builds linux-libc-dev for
  all architectures, without building any kernels. This way for example,
  we could rev userspace headers to v5.8/v5.9 ahead of said kernel
  landing, to shake out build-failures / userspace 

[Kernel-packages] [Bug 1886277] Re: Regression on NFS: unable to handle page fault in mempool_alloc_slab

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.8.0-18.19

---
linux (5.8.0-18.19) groovy; urgency=medium

  * groovy/linux: 5.8.0-18.19 -proposed tracker (LP: #1893047)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Groovy update: v5.8.4 upstream stable release (LP: #1893048)
- drm/vgem: Replace opencoded version of drm_gem_dumb_map_offset()
- drm/panel-simple: Fix inverted V/H SYNC for Frida FRD350H54004 panel
- drm/ast: Remove unused code paths for AST 1180
- drm/ast: Initialize DRAM type before posting GPU
- khugepaged: adjust VM_BUG_ON_MM() in __khugepaged_enter()
- ALSA: hda: avoid reset of sdo_limit
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Flex Book
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Book Ion
- can: j1939: transport: j1939_session_tx_dat(): fix use-after-free read in
  j1939_tp_txtimer()
- can: j1939: socket: j1939_sk_bind(): make sure ml_priv is allocated
- spi: Prevent adding devices below an unregistering controller
- io_uring: find and cancel head link async work on files exit
- mm/vunmap: add cond_resched() in vunmap_pmd_range
- romfs: fix uninitialized memory leak in romfs_dev_read()
- kernel/relay.c: fix memleak on destroy relay channel
- uprobes: __replace_page() avoid BUG in munlock_vma_page()
- squashfs: avoid bio_alloc() failure with 1Mbyte blocks
- mm: include CMA pages in lowmem_reserve at boot
- mm, page_alloc: fix core hung in free_pcppages_bulk()
- ASoC: amd: renoir: restore two more registers during resume
- RDMA/hfi1: Correct an interlock issue for TID RDMA WRITE request
- opp: Enable resources again if they were disabled earlier
- opp: Put opp table in dev_pm_opp_set_rate() for empty tables
- opp: Put opp table in dev_pm_opp_set_rate() if _set_opp_bw() fails
- ext4: do not block RWF_NOWAIT dio write on unallocated space
- ext4: fix checking of directory entry validity for inline directories
- jbd2: add the missing unlock_buffer() in the error path of
  jbd2_write_superblock()
- scsi: zfcp: Fix use-after-free in request timeout handlers
- selftests: kvm: Use a shorter encoding to clear RAX
- s390/pci: fix zpci_bus_link_virtfn()
- s390/pci: re-introduce zpci_remove_device()
- s390/pci: fix PF/VF linking on hot plug
- s390/pci: ignore stale configuration request event
- mm/memory.c: skip spurious TLB flush for retried page fault
- drm: amdgpu: Use the correct size when allocating memory
- drm/amdgpu/display: use GFP_ATOMIC in dcn20_validate_bandwidth_internal
- drm/amd/display: Fix incorrect backlight register offset for DCN
- drm/amd/display: Fix EDID parsing after resume from suspend
- drm/amd/display: Blank stream before destroying HDCP session
- drm/amd/display: Fix DFPstate hang due to view port changed
- drm/amd/display: fix pow() crashing when given base 0
- drm/i915/pmu: Prefer drm_WARN_ON over WARN_ON
- drm/i915: Provide the perf pmu.module
- scsi: ufs: Add DELAY_BEFORE_LPM quirk for Micron devices
- scsi: target: tcmu: Fix crash in tcmu_flush_dcache_range on ARM
- media: budget-core: Improve exception handling in budget_register()
- media: coda: jpeg: add NULL check after kmalloc
- f2fs: fix to check page dirty status before writeback
- rtc: goldfish: Enable interrupt in set_alarm() when necessary
- media: vpss: clean up resources in init
- f2fs: should avoid inode eviction in synchronous path
- Input: psmouse - add a newline when printing 'proto' by sysfs
- MIPS: Fix unable to reserve memory for Crash kernel
- m68knommu: fix overwriting of bits in ColdFire V3 cache control
- svcrdma: Fix another Receive buffer leak
- xfs: fix inode quota reservation checks
- drm/ttm: fix offset in VMAs with a pg_offs in ttm_bo_vm_access
- riscv: Fixup static_obj() fail
- jffs2: fix UAF problem
- ceph: fix use-after-free for fsc->mdsc
- swiotlb-xen: use vmalloc_to_page on vmalloc virt addresses
- cpufreq: intel_pstate: Fix cpuinfo_max_freq when MSR_TURBO_RATIO_LIMIT is 0
- scsi: libfc: Free skb in fc_disc_gpn_id_resp() for valid cases
- virtio_ring: Avoid loop when vq is broken in virtqueue_poll
- media: camss: fix memory leaks on error handling paths in probe
- tools/testing/selftests/cgroup/cgroup_util.c: cg_read_strcmp: fix null
  pointer dereference
- xfs: Fix UBSAN null-ptr-deref in xfs_sysfs_init
- alpha: fix annotation of io{read,write}{16,32}be()
- fat: fix fat_ra_init() for data clusters == 0
- fs/signalfd.c: fix inconsistent return codes for signalfd4
- ext4: fix potential negative array index in do_split()
- drm/virtio: fix missing dma_fence_put() in virtio_gpu_execbuffer_ioctl()
- ext4: don't allow overlapping system zones
- ext4: check journal inode extents more carefully
- netfilter: nf_tables: nft_exthdr: 

[Kernel-packages] [Bug 1869134] Re: tcp_fastopen_backup_key.sh from net in ubuntu_kernel_selftests failed on Eoan LPAR

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.8.0-18.19

---
linux (5.8.0-18.19) groovy; urgency=medium

  * groovy/linux: 5.8.0-18.19 -proposed tracker (LP: #1893047)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Groovy update: v5.8.4 upstream stable release (LP: #1893048)
- drm/vgem: Replace opencoded version of drm_gem_dumb_map_offset()
- drm/panel-simple: Fix inverted V/H SYNC for Frida FRD350H54004 panel
- drm/ast: Remove unused code paths for AST 1180
- drm/ast: Initialize DRAM type before posting GPU
- khugepaged: adjust VM_BUG_ON_MM() in __khugepaged_enter()
- ALSA: hda: avoid reset of sdo_limit
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Flex Book
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Book Ion
- can: j1939: transport: j1939_session_tx_dat(): fix use-after-free read in
  j1939_tp_txtimer()
- can: j1939: socket: j1939_sk_bind(): make sure ml_priv is allocated
- spi: Prevent adding devices below an unregistering controller
- io_uring: find and cancel head link async work on files exit
- mm/vunmap: add cond_resched() in vunmap_pmd_range
- romfs: fix uninitialized memory leak in romfs_dev_read()
- kernel/relay.c: fix memleak on destroy relay channel
- uprobes: __replace_page() avoid BUG in munlock_vma_page()
- squashfs: avoid bio_alloc() failure with 1Mbyte blocks
- mm: include CMA pages in lowmem_reserve at boot
- mm, page_alloc: fix core hung in free_pcppages_bulk()
- ASoC: amd: renoir: restore two more registers during resume
- RDMA/hfi1: Correct an interlock issue for TID RDMA WRITE request
- opp: Enable resources again if they were disabled earlier
- opp: Put opp table in dev_pm_opp_set_rate() for empty tables
- opp: Put opp table in dev_pm_opp_set_rate() if _set_opp_bw() fails
- ext4: do not block RWF_NOWAIT dio write on unallocated space
- ext4: fix checking of directory entry validity for inline directories
- jbd2: add the missing unlock_buffer() in the error path of
  jbd2_write_superblock()
- scsi: zfcp: Fix use-after-free in request timeout handlers
- selftests: kvm: Use a shorter encoding to clear RAX
- s390/pci: fix zpci_bus_link_virtfn()
- s390/pci: re-introduce zpci_remove_device()
- s390/pci: fix PF/VF linking on hot plug
- s390/pci: ignore stale configuration request event
- mm/memory.c: skip spurious TLB flush for retried page fault
- drm: amdgpu: Use the correct size when allocating memory
- drm/amdgpu/display: use GFP_ATOMIC in dcn20_validate_bandwidth_internal
- drm/amd/display: Fix incorrect backlight register offset for DCN
- drm/amd/display: Fix EDID parsing after resume from suspend
- drm/amd/display: Blank stream before destroying HDCP session
- drm/amd/display: Fix DFPstate hang due to view port changed
- drm/amd/display: fix pow() crashing when given base 0
- drm/i915/pmu: Prefer drm_WARN_ON over WARN_ON
- drm/i915: Provide the perf pmu.module
- scsi: ufs: Add DELAY_BEFORE_LPM quirk for Micron devices
- scsi: target: tcmu: Fix crash in tcmu_flush_dcache_range on ARM
- media: budget-core: Improve exception handling in budget_register()
- media: coda: jpeg: add NULL check after kmalloc
- f2fs: fix to check page dirty status before writeback
- rtc: goldfish: Enable interrupt in set_alarm() when necessary
- media: vpss: clean up resources in init
- f2fs: should avoid inode eviction in synchronous path
- Input: psmouse - add a newline when printing 'proto' by sysfs
- MIPS: Fix unable to reserve memory for Crash kernel
- m68knommu: fix overwriting of bits in ColdFire V3 cache control
- svcrdma: Fix another Receive buffer leak
- xfs: fix inode quota reservation checks
- drm/ttm: fix offset in VMAs with a pg_offs in ttm_bo_vm_access
- riscv: Fixup static_obj() fail
- jffs2: fix UAF problem
- ceph: fix use-after-free for fsc->mdsc
- swiotlb-xen: use vmalloc_to_page on vmalloc virt addresses
- cpufreq: intel_pstate: Fix cpuinfo_max_freq when MSR_TURBO_RATIO_LIMIT is 0
- scsi: libfc: Free skb in fc_disc_gpn_id_resp() for valid cases
- virtio_ring: Avoid loop when vq is broken in virtqueue_poll
- media: camss: fix memory leaks on error handling paths in probe
- tools/testing/selftests/cgroup/cgroup_util.c: cg_read_strcmp: fix null
  pointer dereference
- xfs: Fix UBSAN null-ptr-deref in xfs_sysfs_init
- alpha: fix annotation of io{read,write}{16,32}be()
- fat: fix fat_ra_init() for data clusters == 0
- fs/signalfd.c: fix inconsistent return codes for signalfd4
- ext4: fix potential negative array index in do_split()
- drm/virtio: fix missing dma_fence_put() in virtio_gpu_execbuffer_ioctl()
- ext4: don't allow overlapping system zones
- ext4: check journal inode extents more carefully
- netfilter: nf_tables: nft_exthdr: 

[Kernel-packages] [Bug 1891224] Re: [Hyper-V] VSS and File Copy daemons intermittently fails to start

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.8.0-18.19

---
linux (5.8.0-18.19) groovy; urgency=medium

  * groovy/linux: 5.8.0-18.19 -proposed tracker (LP: #1893047)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Groovy update: v5.8.4 upstream stable release (LP: #1893048)
- drm/vgem: Replace opencoded version of drm_gem_dumb_map_offset()
- drm/panel-simple: Fix inverted V/H SYNC for Frida FRD350H54004 panel
- drm/ast: Remove unused code paths for AST 1180
- drm/ast: Initialize DRAM type before posting GPU
- khugepaged: adjust VM_BUG_ON_MM() in __khugepaged_enter()
- ALSA: hda: avoid reset of sdo_limit
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Flex Book
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Book Ion
- can: j1939: transport: j1939_session_tx_dat(): fix use-after-free read in
  j1939_tp_txtimer()
- can: j1939: socket: j1939_sk_bind(): make sure ml_priv is allocated
- spi: Prevent adding devices below an unregistering controller
- io_uring: find and cancel head link async work on files exit
- mm/vunmap: add cond_resched() in vunmap_pmd_range
- romfs: fix uninitialized memory leak in romfs_dev_read()
- kernel/relay.c: fix memleak on destroy relay channel
- uprobes: __replace_page() avoid BUG in munlock_vma_page()
- squashfs: avoid bio_alloc() failure with 1Mbyte blocks
- mm: include CMA pages in lowmem_reserve at boot
- mm, page_alloc: fix core hung in free_pcppages_bulk()
- ASoC: amd: renoir: restore two more registers during resume
- RDMA/hfi1: Correct an interlock issue for TID RDMA WRITE request
- opp: Enable resources again if they were disabled earlier
- opp: Put opp table in dev_pm_opp_set_rate() for empty tables
- opp: Put opp table in dev_pm_opp_set_rate() if _set_opp_bw() fails
- ext4: do not block RWF_NOWAIT dio write on unallocated space
- ext4: fix checking of directory entry validity for inline directories
- jbd2: add the missing unlock_buffer() in the error path of
  jbd2_write_superblock()
- scsi: zfcp: Fix use-after-free in request timeout handlers
- selftests: kvm: Use a shorter encoding to clear RAX
- s390/pci: fix zpci_bus_link_virtfn()
- s390/pci: re-introduce zpci_remove_device()
- s390/pci: fix PF/VF linking on hot plug
- s390/pci: ignore stale configuration request event
- mm/memory.c: skip spurious TLB flush for retried page fault
- drm: amdgpu: Use the correct size when allocating memory
- drm/amdgpu/display: use GFP_ATOMIC in dcn20_validate_bandwidth_internal
- drm/amd/display: Fix incorrect backlight register offset for DCN
- drm/amd/display: Fix EDID parsing after resume from suspend
- drm/amd/display: Blank stream before destroying HDCP session
- drm/amd/display: Fix DFPstate hang due to view port changed
- drm/amd/display: fix pow() crashing when given base 0
- drm/i915/pmu: Prefer drm_WARN_ON over WARN_ON
- drm/i915: Provide the perf pmu.module
- scsi: ufs: Add DELAY_BEFORE_LPM quirk for Micron devices
- scsi: target: tcmu: Fix crash in tcmu_flush_dcache_range on ARM
- media: budget-core: Improve exception handling in budget_register()
- media: coda: jpeg: add NULL check after kmalloc
- f2fs: fix to check page dirty status before writeback
- rtc: goldfish: Enable interrupt in set_alarm() when necessary
- media: vpss: clean up resources in init
- f2fs: should avoid inode eviction in synchronous path
- Input: psmouse - add a newline when printing 'proto' by sysfs
- MIPS: Fix unable to reserve memory for Crash kernel
- m68knommu: fix overwriting of bits in ColdFire V3 cache control
- svcrdma: Fix another Receive buffer leak
- xfs: fix inode quota reservation checks
- drm/ttm: fix offset in VMAs with a pg_offs in ttm_bo_vm_access
- riscv: Fixup static_obj() fail
- jffs2: fix UAF problem
- ceph: fix use-after-free for fsc->mdsc
- swiotlb-xen: use vmalloc_to_page on vmalloc virt addresses
- cpufreq: intel_pstate: Fix cpuinfo_max_freq when MSR_TURBO_RATIO_LIMIT is 0
- scsi: libfc: Free skb in fc_disc_gpn_id_resp() for valid cases
- virtio_ring: Avoid loop when vq is broken in virtqueue_poll
- media: camss: fix memory leaks on error handling paths in probe
- tools/testing/selftests/cgroup/cgroup_util.c: cg_read_strcmp: fix null
  pointer dereference
- xfs: Fix UBSAN null-ptr-deref in xfs_sysfs_init
- alpha: fix annotation of io{read,write}{16,32}be()
- fat: fix fat_ra_init() for data clusters == 0
- fs/signalfd.c: fix inconsistent return codes for signalfd4
- ext4: fix potential negative array index in do_split()
- drm/virtio: fix missing dma_fence_put() in virtio_gpu_execbuffer_ioctl()
- ext4: don't allow overlapping system zones
- ext4: check journal inode extents more carefully
- netfilter: nf_tables: nft_exthdr: 

[Kernel-packages] [Bug 1891585] Re: alsa/sof: support 1 and 3 dmics

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.8.0-18.19

---
linux (5.8.0-18.19) groovy; urgency=medium

  * groovy/linux: 5.8.0-18.19 -proposed tracker (LP: #1893047)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Groovy update: v5.8.4 upstream stable release (LP: #1893048)
- drm/vgem: Replace opencoded version of drm_gem_dumb_map_offset()
- drm/panel-simple: Fix inverted V/H SYNC for Frida FRD350H54004 panel
- drm/ast: Remove unused code paths for AST 1180
- drm/ast: Initialize DRAM type before posting GPU
- khugepaged: adjust VM_BUG_ON_MM() in __khugepaged_enter()
- ALSA: hda: avoid reset of sdo_limit
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Flex Book
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Book Ion
- can: j1939: transport: j1939_session_tx_dat(): fix use-after-free read in
  j1939_tp_txtimer()
- can: j1939: socket: j1939_sk_bind(): make sure ml_priv is allocated
- spi: Prevent adding devices below an unregistering controller
- io_uring: find and cancel head link async work on files exit
- mm/vunmap: add cond_resched() in vunmap_pmd_range
- romfs: fix uninitialized memory leak in romfs_dev_read()
- kernel/relay.c: fix memleak on destroy relay channel
- uprobes: __replace_page() avoid BUG in munlock_vma_page()
- squashfs: avoid bio_alloc() failure with 1Mbyte blocks
- mm: include CMA pages in lowmem_reserve at boot
- mm, page_alloc: fix core hung in free_pcppages_bulk()
- ASoC: amd: renoir: restore two more registers during resume
- RDMA/hfi1: Correct an interlock issue for TID RDMA WRITE request
- opp: Enable resources again if they were disabled earlier
- opp: Put opp table in dev_pm_opp_set_rate() for empty tables
- opp: Put opp table in dev_pm_opp_set_rate() if _set_opp_bw() fails
- ext4: do not block RWF_NOWAIT dio write on unallocated space
- ext4: fix checking of directory entry validity for inline directories
- jbd2: add the missing unlock_buffer() in the error path of
  jbd2_write_superblock()
- scsi: zfcp: Fix use-after-free in request timeout handlers
- selftests: kvm: Use a shorter encoding to clear RAX
- s390/pci: fix zpci_bus_link_virtfn()
- s390/pci: re-introduce zpci_remove_device()
- s390/pci: fix PF/VF linking on hot plug
- s390/pci: ignore stale configuration request event
- mm/memory.c: skip spurious TLB flush for retried page fault
- drm: amdgpu: Use the correct size when allocating memory
- drm/amdgpu/display: use GFP_ATOMIC in dcn20_validate_bandwidth_internal
- drm/amd/display: Fix incorrect backlight register offset for DCN
- drm/amd/display: Fix EDID parsing after resume from suspend
- drm/amd/display: Blank stream before destroying HDCP session
- drm/amd/display: Fix DFPstate hang due to view port changed
- drm/amd/display: fix pow() crashing when given base 0
- drm/i915/pmu: Prefer drm_WARN_ON over WARN_ON
- drm/i915: Provide the perf pmu.module
- scsi: ufs: Add DELAY_BEFORE_LPM quirk for Micron devices
- scsi: target: tcmu: Fix crash in tcmu_flush_dcache_range on ARM
- media: budget-core: Improve exception handling in budget_register()
- media: coda: jpeg: add NULL check after kmalloc
- f2fs: fix to check page dirty status before writeback
- rtc: goldfish: Enable interrupt in set_alarm() when necessary
- media: vpss: clean up resources in init
- f2fs: should avoid inode eviction in synchronous path
- Input: psmouse - add a newline when printing 'proto' by sysfs
- MIPS: Fix unable to reserve memory for Crash kernel
- m68knommu: fix overwriting of bits in ColdFire V3 cache control
- svcrdma: Fix another Receive buffer leak
- xfs: fix inode quota reservation checks
- drm/ttm: fix offset in VMAs with a pg_offs in ttm_bo_vm_access
- riscv: Fixup static_obj() fail
- jffs2: fix UAF problem
- ceph: fix use-after-free for fsc->mdsc
- swiotlb-xen: use vmalloc_to_page on vmalloc virt addresses
- cpufreq: intel_pstate: Fix cpuinfo_max_freq when MSR_TURBO_RATIO_LIMIT is 0
- scsi: libfc: Free skb in fc_disc_gpn_id_resp() for valid cases
- virtio_ring: Avoid loop when vq is broken in virtqueue_poll
- media: camss: fix memory leaks on error handling paths in probe
- tools/testing/selftests/cgroup/cgroup_util.c: cg_read_strcmp: fix null
  pointer dereference
- xfs: Fix UBSAN null-ptr-deref in xfs_sysfs_init
- alpha: fix annotation of io{read,write}{16,32}be()
- fat: fix fat_ra_init() for data clusters == 0
- fs/signalfd.c: fix inconsistent return codes for signalfd4
- ext4: fix potential negative array index in do_split()
- drm/virtio: fix missing dma_fence_put() in virtio_gpu_execbuffer_ioctl()
- ext4: don't allow overlapping system zones
- ext4: check journal inode extents more carefully
- netfilter: nf_tables: nft_exthdr: 

[Kernel-packages] [Bug 1891528] Re: fix ftrace pid filtering on linux 5.8

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.8.0-18.19

---
linux (5.8.0-18.19) groovy; urgency=medium

  * groovy/linux: 5.8.0-18.19 -proposed tracker (LP: #1893047)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Groovy update: v5.8.4 upstream stable release (LP: #1893048)
- drm/vgem: Replace opencoded version of drm_gem_dumb_map_offset()
- drm/panel-simple: Fix inverted V/H SYNC for Frida FRD350H54004 panel
- drm/ast: Remove unused code paths for AST 1180
- drm/ast: Initialize DRAM type before posting GPU
- khugepaged: adjust VM_BUG_ON_MM() in __khugepaged_enter()
- ALSA: hda: avoid reset of sdo_limit
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Flex Book
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Book Ion
- can: j1939: transport: j1939_session_tx_dat(): fix use-after-free read in
  j1939_tp_txtimer()
- can: j1939: socket: j1939_sk_bind(): make sure ml_priv is allocated
- spi: Prevent adding devices below an unregistering controller
- io_uring: find and cancel head link async work on files exit
- mm/vunmap: add cond_resched() in vunmap_pmd_range
- romfs: fix uninitialized memory leak in romfs_dev_read()
- kernel/relay.c: fix memleak on destroy relay channel
- uprobes: __replace_page() avoid BUG in munlock_vma_page()
- squashfs: avoid bio_alloc() failure with 1Mbyte blocks
- mm: include CMA pages in lowmem_reserve at boot
- mm, page_alloc: fix core hung in free_pcppages_bulk()
- ASoC: amd: renoir: restore two more registers during resume
- RDMA/hfi1: Correct an interlock issue for TID RDMA WRITE request
- opp: Enable resources again if they were disabled earlier
- opp: Put opp table in dev_pm_opp_set_rate() for empty tables
- opp: Put opp table in dev_pm_opp_set_rate() if _set_opp_bw() fails
- ext4: do not block RWF_NOWAIT dio write on unallocated space
- ext4: fix checking of directory entry validity for inline directories
- jbd2: add the missing unlock_buffer() in the error path of
  jbd2_write_superblock()
- scsi: zfcp: Fix use-after-free in request timeout handlers
- selftests: kvm: Use a shorter encoding to clear RAX
- s390/pci: fix zpci_bus_link_virtfn()
- s390/pci: re-introduce zpci_remove_device()
- s390/pci: fix PF/VF linking on hot plug
- s390/pci: ignore stale configuration request event
- mm/memory.c: skip spurious TLB flush for retried page fault
- drm: amdgpu: Use the correct size when allocating memory
- drm/amdgpu/display: use GFP_ATOMIC in dcn20_validate_bandwidth_internal
- drm/amd/display: Fix incorrect backlight register offset for DCN
- drm/amd/display: Fix EDID parsing after resume from suspend
- drm/amd/display: Blank stream before destroying HDCP session
- drm/amd/display: Fix DFPstate hang due to view port changed
- drm/amd/display: fix pow() crashing when given base 0
- drm/i915/pmu: Prefer drm_WARN_ON over WARN_ON
- drm/i915: Provide the perf pmu.module
- scsi: ufs: Add DELAY_BEFORE_LPM quirk for Micron devices
- scsi: target: tcmu: Fix crash in tcmu_flush_dcache_range on ARM
- media: budget-core: Improve exception handling in budget_register()
- media: coda: jpeg: add NULL check after kmalloc
- f2fs: fix to check page dirty status before writeback
- rtc: goldfish: Enable interrupt in set_alarm() when necessary
- media: vpss: clean up resources in init
- f2fs: should avoid inode eviction in synchronous path
- Input: psmouse - add a newline when printing 'proto' by sysfs
- MIPS: Fix unable to reserve memory for Crash kernel
- m68knommu: fix overwriting of bits in ColdFire V3 cache control
- svcrdma: Fix another Receive buffer leak
- xfs: fix inode quota reservation checks
- drm/ttm: fix offset in VMAs with a pg_offs in ttm_bo_vm_access
- riscv: Fixup static_obj() fail
- jffs2: fix UAF problem
- ceph: fix use-after-free for fsc->mdsc
- swiotlb-xen: use vmalloc_to_page on vmalloc virt addresses
- cpufreq: intel_pstate: Fix cpuinfo_max_freq when MSR_TURBO_RATIO_LIMIT is 0
- scsi: libfc: Free skb in fc_disc_gpn_id_resp() for valid cases
- virtio_ring: Avoid loop when vq is broken in virtqueue_poll
- media: camss: fix memory leaks on error handling paths in probe
- tools/testing/selftests/cgroup/cgroup_util.c: cg_read_strcmp: fix null
  pointer dereference
- xfs: Fix UBSAN null-ptr-deref in xfs_sysfs_init
- alpha: fix annotation of io{read,write}{16,32}be()
- fat: fix fat_ra_init() for data clusters == 0
- fs/signalfd.c: fix inconsistent return codes for signalfd4
- ext4: fix potential negative array index in do_split()
- drm/virtio: fix missing dma_fence_put() in virtio_gpu_execbuffer_ioctl()
- ext4: don't allow overlapping system zones
- ext4: check journal inode extents more carefully
- netfilter: nf_tables: nft_exthdr: 

[Kernel-packages] [Bug 1891998] Re: Fix non-working Goodix touchpad after system sleep

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.8.0-18.19

---
linux (5.8.0-18.19) groovy; urgency=medium

  * groovy/linux: 5.8.0-18.19 -proposed tracker (LP: #1893047)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Groovy update: v5.8.4 upstream stable release (LP: #1893048)
- drm/vgem: Replace opencoded version of drm_gem_dumb_map_offset()
- drm/panel-simple: Fix inverted V/H SYNC for Frida FRD350H54004 panel
- drm/ast: Remove unused code paths for AST 1180
- drm/ast: Initialize DRAM type before posting GPU
- khugepaged: adjust VM_BUG_ON_MM() in __khugepaged_enter()
- ALSA: hda: avoid reset of sdo_limit
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Flex Book
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Book Ion
- can: j1939: transport: j1939_session_tx_dat(): fix use-after-free read in
  j1939_tp_txtimer()
- can: j1939: socket: j1939_sk_bind(): make sure ml_priv is allocated
- spi: Prevent adding devices below an unregistering controller
- io_uring: find and cancel head link async work on files exit
- mm/vunmap: add cond_resched() in vunmap_pmd_range
- romfs: fix uninitialized memory leak in romfs_dev_read()
- kernel/relay.c: fix memleak on destroy relay channel
- uprobes: __replace_page() avoid BUG in munlock_vma_page()
- squashfs: avoid bio_alloc() failure with 1Mbyte blocks
- mm: include CMA pages in lowmem_reserve at boot
- mm, page_alloc: fix core hung in free_pcppages_bulk()
- ASoC: amd: renoir: restore two more registers during resume
- RDMA/hfi1: Correct an interlock issue for TID RDMA WRITE request
- opp: Enable resources again if they were disabled earlier
- opp: Put opp table in dev_pm_opp_set_rate() for empty tables
- opp: Put opp table in dev_pm_opp_set_rate() if _set_opp_bw() fails
- ext4: do not block RWF_NOWAIT dio write on unallocated space
- ext4: fix checking of directory entry validity for inline directories
- jbd2: add the missing unlock_buffer() in the error path of
  jbd2_write_superblock()
- scsi: zfcp: Fix use-after-free in request timeout handlers
- selftests: kvm: Use a shorter encoding to clear RAX
- s390/pci: fix zpci_bus_link_virtfn()
- s390/pci: re-introduce zpci_remove_device()
- s390/pci: fix PF/VF linking on hot plug
- s390/pci: ignore stale configuration request event
- mm/memory.c: skip spurious TLB flush for retried page fault
- drm: amdgpu: Use the correct size when allocating memory
- drm/amdgpu/display: use GFP_ATOMIC in dcn20_validate_bandwidth_internal
- drm/amd/display: Fix incorrect backlight register offset for DCN
- drm/amd/display: Fix EDID parsing after resume from suspend
- drm/amd/display: Blank stream before destroying HDCP session
- drm/amd/display: Fix DFPstate hang due to view port changed
- drm/amd/display: fix pow() crashing when given base 0
- drm/i915/pmu: Prefer drm_WARN_ON over WARN_ON
- drm/i915: Provide the perf pmu.module
- scsi: ufs: Add DELAY_BEFORE_LPM quirk for Micron devices
- scsi: target: tcmu: Fix crash in tcmu_flush_dcache_range on ARM
- media: budget-core: Improve exception handling in budget_register()
- media: coda: jpeg: add NULL check after kmalloc
- f2fs: fix to check page dirty status before writeback
- rtc: goldfish: Enable interrupt in set_alarm() when necessary
- media: vpss: clean up resources in init
- f2fs: should avoid inode eviction in synchronous path
- Input: psmouse - add a newline when printing 'proto' by sysfs
- MIPS: Fix unable to reserve memory for Crash kernel
- m68knommu: fix overwriting of bits in ColdFire V3 cache control
- svcrdma: Fix another Receive buffer leak
- xfs: fix inode quota reservation checks
- drm/ttm: fix offset in VMAs with a pg_offs in ttm_bo_vm_access
- riscv: Fixup static_obj() fail
- jffs2: fix UAF problem
- ceph: fix use-after-free for fsc->mdsc
- swiotlb-xen: use vmalloc_to_page on vmalloc virt addresses
- cpufreq: intel_pstate: Fix cpuinfo_max_freq when MSR_TURBO_RATIO_LIMIT is 0
- scsi: libfc: Free skb in fc_disc_gpn_id_resp() for valid cases
- virtio_ring: Avoid loop when vq is broken in virtqueue_poll
- media: camss: fix memory leaks on error handling paths in probe
- tools/testing/selftests/cgroup/cgroup_util.c: cg_read_strcmp: fix null
  pointer dereference
- xfs: Fix UBSAN null-ptr-deref in xfs_sysfs_init
- alpha: fix annotation of io{read,write}{16,32}be()
- fat: fix fat_ra_init() for data clusters == 0
- fs/signalfd.c: fix inconsistent return codes for signalfd4
- ext4: fix potential negative array index in do_split()
- drm/virtio: fix missing dma_fence_put() in virtio_gpu_execbuffer_ioctl()
- ext4: don't allow overlapping system zones
- ext4: check journal inode extents more carefully
- netfilter: nf_tables: nft_exthdr: 

[Kernel-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones

[John Hoff]

@gannon1 @PowerKiKi

Mike, I never heard back from Jaroslav (I suspect he is pretty busy),
and my consulting work is very slow with the pandemic so I just
continued to work on it.  Your concept is spot on.  Thank you for all
the wisdom and thoughtful guidance.  I am happy to report, after much
more effort than I care to admit, that step 1 has been successfully
achieved and I have stereo sound through my laptop speakers... finally!
Once you get through all the numerous setup pitfalls, it seems (a bit of
an assumption on my part) like the big gotcha is that the windows driver
appears to instantaneously turn off the speakers when not in use (i.e.
if you record a large time period like booting or disabling and enabling
devices then the speakers start and end in off mode and you never catch
it).  It took numerous attempts to catch the right segments.

Anyway, I have begun working on step 2 now.   I stared with >2000 verbs
and am down to what seems to be a consistent 788.  I am confident there
are more to eliminate because it turns on the left speaker (alone) then
turns on the right speaker (alone), then (most importantly) ends with
stereo.  For at least the galaxy book ion (likely will work for others
too), I should be able to provide an optimized result soonish.

PowerKiKi, even with the Xbuntu difference, I feel confident what I have
now will at least work for you since you have the same Ion hardware.
The sound is actually pretty good on these laptops (I never heard it
before today because I wiped windows on day 1 :)  If you would like
to give it a shot, just run the attached script.  I use it on top of
running a custom kernel that includes Mike's headphone patch and I have
full sound on speakers and headphones during the entire session.  Once I
minimize the verbs I will try creating a custom kernel with the final
verbs (I have skipped that for now because the hda verbs work fine and
each attempt at a custom kernel is about an hour journey..)



** Attachment added: "ION Sound Script"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851518/+attachment/5407530/+files/TO93.sh

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1851518

Title:
  [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on
  internal speakers, very very quiet on headphones

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've been googling this issue for 10's of hours and tried many things.

  Relase of Ubuntu: 19.10

  Expected outcome: Music plays on the internal speakers and headphones.

  Actual outcome: I can barely hear audio using headphones with volume
  turned up to 150%.  Absolutely nothing comes out of the speakers. (The
  speakers sound great under Windows 10.)

  Complete alsa-info output is attached, but here are some snippets:

  !!DMI Information
  !!---

  Manufacturer:  SAMSUNG ELECTRONICS CO., LTD.
  Product Name:  950SBE/951SBE
  Product Version:   P06RES
  Firmware Version:  P06RES.075.190529.SP
  Board Vendor:  SAMSUNG ELECTRONICS CO., LTD.
  Board Name:NP950SBE-K01US

  
  !!Kernel Information
  !!--

  Kernel release:5.3.0-19-generic
  Operating System:  GNU/Linux
  Architecture:  x86_64
  Processor: x86_64
  SMP Enabled:   Yes


  !!ALSA Version
  !!

  Driver version: k5.3.0-19-generic
  Library version:1.1.9
  Utilities version:  1.1.9

  
  !!Loaded ALSA modules
  !!---

  snd_hda_intel

  
  !!Sound Servers on this system
  !!

  Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - Yes

  
  !!Soundcards recognised by ALSA
  !!-

   0 [PCH]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0x604b118000 irq 177

  
  !!PCI Soundcards installed in the system
  !!--

  00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP
  High Definition Audio Controller (rev 11)

  
  !!Advanced information - PCI Vendor/Device/Subsystem ID's
  !!---

  00:1f.3 0401: 8086:9dc8 (rev 11)
  DeviceName: Onboard - Sound

  
  !!HDA-Intel Codec information
  !!---
  --startcollapse--

  Codec: Realtek ALC298
  Address: 0
  AFG Function Id: 0x1 (unsol 1)
  Vendor Id: 0x10ec0298
  Subsystem Id: 0x144dc812
  Revision Id: 0x100103
  No Modem Function Group found
  Default PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
  Default Amp-In caps: N/A
  Default Amp-Out caps: N/A
  State of AFG node 0x01:
Power states:  D0 D1 D2 D3 D3cold CLKSTOP EPSS
Power: setting=D0, actual=D0
  GPIO: io=8, o=0, i=0, unsolicited=1, wake=0
IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[1]: enable=0, 

[Kernel-packages] [Bug 1894157] [NEW] No recupera tras suspensión en MacBook Pro

[Darío García Martos]

Public bug reported:

Se fuerza el apagado con el botón de encendido, no funciona "resume".

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-45-generic 5.4.0-45.49
ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
Uname: Linux 5.4.0-45-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  usuario1193 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: Budgie:GNOME
Date: Thu Sep  3 23:57:55 2020
InstallationDate: Installed on 2020-08-31 (3 days ago)
InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
MachineType: Apple Inc. MacBookPro4,1
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=3a38607a-f3e9-4f46-840c-edf92ddc3ad9 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-45-generic N/A
 linux-backports-modules-5.4.0-45-generic  N/A
 linux-firmware1.187.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/09/08
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP41.88Z.00C1.B00.0802091544
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Mac-F42C89C8
dmi.board.vendor: Apple Inc.
dmi.board.version: PVT
dmi.chassis.asset.tag: Asset Tag#
dmi.chassis.type: 2
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F42C89C8
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP41.88Z.00C1.B00.0802091544:bd02/09/08:svnAppleInc.:pnMacBookPro4,1:pvr1.0:rvnAppleInc.:rnMac-F42C89C8:rvrPVT:cvnAppleInc.:ct2:cvrMac-F42C89C8:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro4,1
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple 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/1894157

Title:
  No recupera tras suspensión en MacBook Pro

Status in linux package in Ubuntu:
  New

Bug description:
  Se fuerza el apagado con el botón de encendido, no funciona "resume".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-45-generic 5.4.0-45.49
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Uname: Linux 5.4.0-45-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1193 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Thu Sep  3 23:57:55 2020
  InstallationDate: Installed on 2020-08-31 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  MachineType: Apple Inc. MacBookPro4,1
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=3a38607a-f3e9-4f46-840c-edf92ddc3ad9 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-45-generic N/A
   linux-backports-modules-5.4.0-45-generic  N/A
   linux-firmware1.187.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/09/08
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP41.88Z.00C1.B00.0802091544
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F42C89C8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 2
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F42C89C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP41.88Z.00C1.B00.0802091544:bd02/09/08:svnAppleInc.:pnMacBookPro4,1:pvr1.0:rvnAppleInc.:rnMac-F42C89C8:rvrPVT:cvnAppleInc.:ct2:cvrMac-F42C89C8:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro4,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894157/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1894157] Status changed to Confirmed

[Ubuntu Kernel Bot]

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/1894157

Title:
  No recupera tras suspensión en MacBook Pro

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Se fuerza el apagado con el botón de encendido, no funciona "resume".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-45-generic 5.4.0-45.49
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Uname: Linux 5.4.0-45-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1193 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Thu Sep  3 23:57:55 2020
  InstallationDate: Installed on 2020-08-31 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  MachineType: Apple Inc. MacBookPro4,1
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=3a38607a-f3e9-4f46-840c-edf92ddc3ad9 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-45-generic N/A
   linux-backports-modules-5.4.0-45-generic  N/A
   linux-firmware1.187.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/09/08
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP41.88Z.00C1.B00.0802091544
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F42C89C8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 2
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F42C89C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP41.88Z.00C1.B00.0802091544:bd02/09/08:svnAppleInc.:pnMacBookPro4,1:pvr1.0:rvnAppleInc.:rnMac-F42C89C8:rvrPVT:cvnAppleInc.:ct2:cvrMac-F42C89C8:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro4,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894157/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1894012] Re: touchpad and keyboard

[Woody]

This happened to me as well.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894012

Title:
  touchpad and keyboard

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I reinstalled Ubuntu on 20.04 version in my laptop on an SSD and the
  keyboard and touch-pad stopped working

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-45-generic 5.4.0-45.49
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Uname: Linux 5.4.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jorge  1551 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  3 00:47:37 2020
  InstallationDate: Installed on 2020-09-02 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: CHUWI INNOVATION LIMITED AeroBook
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=4259a678-3627-47b0-81a7-b8449ea7222c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-45-generic N/A
   linux-backports-modules-5.4.0-45-generic  N/A
   linux-firmware1.187.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/20/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: YZ-BI-133-X133KR110-KJ66B-106-N
  dmi.board.asset.tag: Default string
  dmi.board.name: AeroBook
  dmi.board.vendor: CHUWI INNOVATION LIMITED
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: CHUWI INNOVATION LIMITED
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrYZ-BI-133-X133KR110-KJ66B-106-N:bd09/20/2019:svnCHUWIINNOVATIONLIMITED:pnAeroBook:pvrDefaultstring:rvnCHUWIINNOVATIONLIMITED:rnAeroBook:rvrDefaultstring:cvnCHUWIINNOVATIONLIMITED:ct10:cvrDefaultstring:
  dmi.product.family: YZ106
  dmi.product.name: AeroBook
  dmi.product.sku: YZ106
  dmi.product.version: Default string
  dmi.sys.vendor: CHUWI INNOVATION LIMITED

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894012/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1892138] Re: DMA config issues on Synquacer ARM64 platform cause SATA configuration failures on boot

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.8.0-18.19

---
linux (5.8.0-18.19) groovy; urgency=medium

  * groovy/linux: 5.8.0-18.19 -proposed tracker (LP: #1893047)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Groovy update: v5.8.4 upstream stable release (LP: #1893048)
- drm/vgem: Replace opencoded version of drm_gem_dumb_map_offset()
- drm/panel-simple: Fix inverted V/H SYNC for Frida FRD350H54004 panel
- drm/ast: Remove unused code paths for AST 1180
- drm/ast: Initialize DRAM type before posting GPU
- khugepaged: adjust VM_BUG_ON_MM() in __khugepaged_enter()
- ALSA: hda: avoid reset of sdo_limit
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Flex Book
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Book Ion
- can: j1939: transport: j1939_session_tx_dat(): fix use-after-free read in
  j1939_tp_txtimer()
- can: j1939: socket: j1939_sk_bind(): make sure ml_priv is allocated
- spi: Prevent adding devices below an unregistering controller
- io_uring: find and cancel head link async work on files exit
- mm/vunmap: add cond_resched() in vunmap_pmd_range
- romfs: fix uninitialized memory leak in romfs_dev_read()
- kernel/relay.c: fix memleak on destroy relay channel
- uprobes: __replace_page() avoid BUG in munlock_vma_page()
- squashfs: avoid bio_alloc() failure with 1Mbyte blocks
- mm: include CMA pages in lowmem_reserve at boot
- mm, page_alloc: fix core hung in free_pcppages_bulk()
- ASoC: amd: renoir: restore two more registers during resume
- RDMA/hfi1: Correct an interlock issue for TID RDMA WRITE request
- opp: Enable resources again if they were disabled earlier
- opp: Put opp table in dev_pm_opp_set_rate() for empty tables
- opp: Put opp table in dev_pm_opp_set_rate() if _set_opp_bw() fails
- ext4: do not block RWF_NOWAIT dio write on unallocated space
- ext4: fix checking of directory entry validity for inline directories
- jbd2: add the missing unlock_buffer() in the error path of
  jbd2_write_superblock()
- scsi: zfcp: Fix use-after-free in request timeout handlers
- selftests: kvm: Use a shorter encoding to clear RAX
- s390/pci: fix zpci_bus_link_virtfn()
- s390/pci: re-introduce zpci_remove_device()
- s390/pci: fix PF/VF linking on hot plug
- s390/pci: ignore stale configuration request event
- mm/memory.c: skip spurious TLB flush for retried page fault
- drm: amdgpu: Use the correct size when allocating memory
- drm/amdgpu/display: use GFP_ATOMIC in dcn20_validate_bandwidth_internal
- drm/amd/display: Fix incorrect backlight register offset for DCN
- drm/amd/display: Fix EDID parsing after resume from suspend
- drm/amd/display: Blank stream before destroying HDCP session
- drm/amd/display: Fix DFPstate hang due to view port changed
- drm/amd/display: fix pow() crashing when given base 0
- drm/i915/pmu: Prefer drm_WARN_ON over WARN_ON
- drm/i915: Provide the perf pmu.module
- scsi: ufs: Add DELAY_BEFORE_LPM quirk for Micron devices
- scsi: target: tcmu: Fix crash in tcmu_flush_dcache_range on ARM
- media: budget-core: Improve exception handling in budget_register()
- media: coda: jpeg: add NULL check after kmalloc
- f2fs: fix to check page dirty status before writeback
- rtc: goldfish: Enable interrupt in set_alarm() when necessary
- media: vpss: clean up resources in init
- f2fs: should avoid inode eviction in synchronous path
- Input: psmouse - add a newline when printing 'proto' by sysfs
- MIPS: Fix unable to reserve memory for Crash kernel
- m68knommu: fix overwriting of bits in ColdFire V3 cache control
- svcrdma: Fix another Receive buffer leak
- xfs: fix inode quota reservation checks
- drm/ttm: fix offset in VMAs with a pg_offs in ttm_bo_vm_access
- riscv: Fixup static_obj() fail
- jffs2: fix UAF problem
- ceph: fix use-after-free for fsc->mdsc
- swiotlb-xen: use vmalloc_to_page on vmalloc virt addresses
- cpufreq: intel_pstate: Fix cpuinfo_max_freq when MSR_TURBO_RATIO_LIMIT is 0
- scsi: libfc: Free skb in fc_disc_gpn_id_resp() for valid cases
- virtio_ring: Avoid loop when vq is broken in virtqueue_poll
- media: camss: fix memory leaks on error handling paths in probe
- tools/testing/selftests/cgroup/cgroup_util.c: cg_read_strcmp: fix null
  pointer dereference
- xfs: Fix UBSAN null-ptr-deref in xfs_sysfs_init
- alpha: fix annotation of io{read,write}{16,32}be()
- fat: fix fat_ra_init() for data clusters == 0
- fs/signalfd.c: fix inconsistent return codes for signalfd4
- ext4: fix potential negative array index in do_split()
- drm/virtio: fix missing dma_fence_put() in virtio_gpu_execbuffer_ioctl()
- ext4: don't allow overlapping system zones
- ext4: check journal inode extents more carefully
- netfilter: nf_tables: nft_exthdr: 

[Kernel-packages] [Bug 1892774] Re: Groovy update: v5.8.3 upstream stable release

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.8.0-18.19

---
linux (5.8.0-18.19) groovy; urgency=medium

  * groovy/linux: 5.8.0-18.19 -proposed tracker (LP: #1893047)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Groovy update: v5.8.4 upstream stable release (LP: #1893048)
- drm/vgem: Replace opencoded version of drm_gem_dumb_map_offset()
- drm/panel-simple: Fix inverted V/H SYNC for Frida FRD350H54004 panel
- drm/ast: Remove unused code paths for AST 1180
- drm/ast: Initialize DRAM type before posting GPU
- khugepaged: adjust VM_BUG_ON_MM() in __khugepaged_enter()
- ALSA: hda: avoid reset of sdo_limit
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Flex Book
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Book Ion
- can: j1939: transport: j1939_session_tx_dat(): fix use-after-free read in
  j1939_tp_txtimer()
- can: j1939: socket: j1939_sk_bind(): make sure ml_priv is allocated
- spi: Prevent adding devices below an unregistering controller
- io_uring: find and cancel head link async work on files exit
- mm/vunmap: add cond_resched() in vunmap_pmd_range
- romfs: fix uninitialized memory leak in romfs_dev_read()
- kernel/relay.c: fix memleak on destroy relay channel
- uprobes: __replace_page() avoid BUG in munlock_vma_page()
- squashfs: avoid bio_alloc() failure with 1Mbyte blocks
- mm: include CMA pages in lowmem_reserve at boot
- mm, page_alloc: fix core hung in free_pcppages_bulk()
- ASoC: amd: renoir: restore two more registers during resume
- RDMA/hfi1: Correct an interlock issue for TID RDMA WRITE request
- opp: Enable resources again if they were disabled earlier
- opp: Put opp table in dev_pm_opp_set_rate() for empty tables
- opp: Put opp table in dev_pm_opp_set_rate() if _set_opp_bw() fails
- ext4: do not block RWF_NOWAIT dio write on unallocated space
- ext4: fix checking of directory entry validity for inline directories
- jbd2: add the missing unlock_buffer() in the error path of
  jbd2_write_superblock()
- scsi: zfcp: Fix use-after-free in request timeout handlers
- selftests: kvm: Use a shorter encoding to clear RAX
- s390/pci: fix zpci_bus_link_virtfn()
- s390/pci: re-introduce zpci_remove_device()
- s390/pci: fix PF/VF linking on hot plug
- s390/pci: ignore stale configuration request event
- mm/memory.c: skip spurious TLB flush for retried page fault
- drm: amdgpu: Use the correct size when allocating memory
- drm/amdgpu/display: use GFP_ATOMIC in dcn20_validate_bandwidth_internal
- drm/amd/display: Fix incorrect backlight register offset for DCN
- drm/amd/display: Fix EDID parsing after resume from suspend
- drm/amd/display: Blank stream before destroying HDCP session
- drm/amd/display: Fix DFPstate hang due to view port changed
- drm/amd/display: fix pow() crashing when given base 0
- drm/i915/pmu: Prefer drm_WARN_ON over WARN_ON
- drm/i915: Provide the perf pmu.module
- scsi: ufs: Add DELAY_BEFORE_LPM quirk for Micron devices
- scsi: target: tcmu: Fix crash in tcmu_flush_dcache_range on ARM
- media: budget-core: Improve exception handling in budget_register()
- media: coda: jpeg: add NULL check after kmalloc
- f2fs: fix to check page dirty status before writeback
- rtc: goldfish: Enable interrupt in set_alarm() when necessary
- media: vpss: clean up resources in init
- f2fs: should avoid inode eviction in synchronous path
- Input: psmouse - add a newline when printing 'proto' by sysfs
- MIPS: Fix unable to reserve memory for Crash kernel
- m68knommu: fix overwriting of bits in ColdFire V3 cache control
- svcrdma: Fix another Receive buffer leak
- xfs: fix inode quota reservation checks
- drm/ttm: fix offset in VMAs with a pg_offs in ttm_bo_vm_access
- riscv: Fixup static_obj() fail
- jffs2: fix UAF problem
- ceph: fix use-after-free for fsc->mdsc
- swiotlb-xen: use vmalloc_to_page on vmalloc virt addresses
- cpufreq: intel_pstate: Fix cpuinfo_max_freq when MSR_TURBO_RATIO_LIMIT is 0
- scsi: libfc: Free skb in fc_disc_gpn_id_resp() for valid cases
- virtio_ring: Avoid loop when vq is broken in virtqueue_poll
- media: camss: fix memory leaks on error handling paths in probe
- tools/testing/selftests/cgroup/cgroup_util.c: cg_read_strcmp: fix null
  pointer dereference
- xfs: Fix UBSAN null-ptr-deref in xfs_sysfs_init
- alpha: fix annotation of io{read,write}{16,32}be()
- fat: fix fat_ra_init() for data clusters == 0
- fs/signalfd.c: fix inconsistent return codes for signalfd4
- ext4: fix potential negative array index in do_split()
- drm/virtio: fix missing dma_fence_put() in virtio_gpu_execbuffer_ioctl()
- ext4: don't allow overlapping system zones
- ext4: check journal inode extents more carefully
- netfilter: nf_tables: nft_exthdr: 

[Kernel-packages] [Bug 1893048] Re: Groovy update: v5.8.4 upstream stable release

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.8.0-18.19

---
linux (5.8.0-18.19) groovy; urgency=medium

  * groovy/linux: 5.8.0-18.19 -proposed tracker (LP: #1893047)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Groovy update: v5.8.4 upstream stable release (LP: #1893048)
- drm/vgem: Replace opencoded version of drm_gem_dumb_map_offset()
- drm/panel-simple: Fix inverted V/H SYNC for Frida FRD350H54004 panel
- drm/ast: Remove unused code paths for AST 1180
- drm/ast: Initialize DRAM type before posting GPU
- khugepaged: adjust VM_BUG_ON_MM() in __khugepaged_enter()
- ALSA: hda: avoid reset of sdo_limit
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Flex Book
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Book Ion
- can: j1939: transport: j1939_session_tx_dat(): fix use-after-free read in
  j1939_tp_txtimer()
- can: j1939: socket: j1939_sk_bind(): make sure ml_priv is allocated
- spi: Prevent adding devices below an unregistering controller
- io_uring: find and cancel head link async work on files exit
- mm/vunmap: add cond_resched() in vunmap_pmd_range
- romfs: fix uninitialized memory leak in romfs_dev_read()
- kernel/relay.c: fix memleak on destroy relay channel
- uprobes: __replace_page() avoid BUG in munlock_vma_page()
- squashfs: avoid bio_alloc() failure with 1Mbyte blocks
- mm: include CMA pages in lowmem_reserve at boot
- mm, page_alloc: fix core hung in free_pcppages_bulk()
- ASoC: amd: renoir: restore two more registers during resume
- RDMA/hfi1: Correct an interlock issue for TID RDMA WRITE request
- opp: Enable resources again if they were disabled earlier
- opp: Put opp table in dev_pm_opp_set_rate() for empty tables
- opp: Put opp table in dev_pm_opp_set_rate() if _set_opp_bw() fails
- ext4: do not block RWF_NOWAIT dio write on unallocated space
- ext4: fix checking of directory entry validity for inline directories
- jbd2: add the missing unlock_buffer() in the error path of
  jbd2_write_superblock()
- scsi: zfcp: Fix use-after-free in request timeout handlers
- selftests: kvm: Use a shorter encoding to clear RAX
- s390/pci: fix zpci_bus_link_virtfn()
- s390/pci: re-introduce zpci_remove_device()
- s390/pci: fix PF/VF linking on hot plug
- s390/pci: ignore stale configuration request event
- mm/memory.c: skip spurious TLB flush for retried page fault
- drm: amdgpu: Use the correct size when allocating memory
- drm/amdgpu/display: use GFP_ATOMIC in dcn20_validate_bandwidth_internal
- drm/amd/display: Fix incorrect backlight register offset for DCN
- drm/amd/display: Fix EDID parsing after resume from suspend
- drm/amd/display: Blank stream before destroying HDCP session
- drm/amd/display: Fix DFPstate hang due to view port changed
- drm/amd/display: fix pow() crashing when given base 0
- drm/i915/pmu: Prefer drm_WARN_ON over WARN_ON
- drm/i915: Provide the perf pmu.module
- scsi: ufs: Add DELAY_BEFORE_LPM quirk for Micron devices
- scsi: target: tcmu: Fix crash in tcmu_flush_dcache_range on ARM
- media: budget-core: Improve exception handling in budget_register()
- media: coda: jpeg: add NULL check after kmalloc
- f2fs: fix to check page dirty status before writeback
- rtc: goldfish: Enable interrupt in set_alarm() when necessary
- media: vpss: clean up resources in init
- f2fs: should avoid inode eviction in synchronous path
- Input: psmouse - add a newline when printing 'proto' by sysfs
- MIPS: Fix unable to reserve memory for Crash kernel
- m68knommu: fix overwriting of bits in ColdFire V3 cache control
- svcrdma: Fix another Receive buffer leak
- xfs: fix inode quota reservation checks
- drm/ttm: fix offset in VMAs with a pg_offs in ttm_bo_vm_access
- riscv: Fixup static_obj() fail
- jffs2: fix UAF problem
- ceph: fix use-after-free for fsc->mdsc
- swiotlb-xen: use vmalloc_to_page on vmalloc virt addresses
- cpufreq: intel_pstate: Fix cpuinfo_max_freq when MSR_TURBO_RATIO_LIMIT is 0
- scsi: libfc: Free skb in fc_disc_gpn_id_resp() for valid cases
- virtio_ring: Avoid loop when vq is broken in virtqueue_poll
- media: camss: fix memory leaks on error handling paths in probe
- tools/testing/selftests/cgroup/cgroup_util.c: cg_read_strcmp: fix null
  pointer dereference
- xfs: Fix UBSAN null-ptr-deref in xfs_sysfs_init
- alpha: fix annotation of io{read,write}{16,32}be()
- fat: fix fat_ra_init() for data clusters == 0
- fs/signalfd.c: fix inconsistent return codes for signalfd4
- ext4: fix potential negative array index in do_split()
- drm/virtio: fix missing dma_fence_put() in virtio_gpu_execbuffer_ioctl()
- ext4: don't allow overlapping system zones
- ext4: check journal inode extents more carefully
- netfilter: nf_tables: nft_exthdr: 

[Kernel-packages] [Bug 1892678] Re: Fix non-working USB devices plugged during system sleep

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.8.0-18.19

---
linux (5.8.0-18.19) groovy; urgency=medium

  * groovy/linux: 5.8.0-18.19 -proposed tracker (LP: #1893047)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Groovy update: v5.8.4 upstream stable release (LP: #1893048)
- drm/vgem: Replace opencoded version of drm_gem_dumb_map_offset()
- drm/panel-simple: Fix inverted V/H SYNC for Frida FRD350H54004 panel
- drm/ast: Remove unused code paths for AST 1180
- drm/ast: Initialize DRAM type before posting GPU
- khugepaged: adjust VM_BUG_ON_MM() in __khugepaged_enter()
- ALSA: hda: avoid reset of sdo_limit
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Flex Book
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Book Ion
- can: j1939: transport: j1939_session_tx_dat(): fix use-after-free read in
  j1939_tp_txtimer()
- can: j1939: socket: j1939_sk_bind(): make sure ml_priv is allocated
- spi: Prevent adding devices below an unregistering controller
- io_uring: find and cancel head link async work on files exit
- mm/vunmap: add cond_resched() in vunmap_pmd_range
- romfs: fix uninitialized memory leak in romfs_dev_read()
- kernel/relay.c: fix memleak on destroy relay channel
- uprobes: __replace_page() avoid BUG in munlock_vma_page()
- squashfs: avoid bio_alloc() failure with 1Mbyte blocks
- mm: include CMA pages in lowmem_reserve at boot
- mm, page_alloc: fix core hung in free_pcppages_bulk()
- ASoC: amd: renoir: restore two more registers during resume
- RDMA/hfi1: Correct an interlock issue for TID RDMA WRITE request
- opp: Enable resources again if they were disabled earlier
- opp: Put opp table in dev_pm_opp_set_rate() for empty tables
- opp: Put opp table in dev_pm_opp_set_rate() if _set_opp_bw() fails
- ext4: do not block RWF_NOWAIT dio write on unallocated space
- ext4: fix checking of directory entry validity for inline directories
- jbd2: add the missing unlock_buffer() in the error path of
  jbd2_write_superblock()
- scsi: zfcp: Fix use-after-free in request timeout handlers
- selftests: kvm: Use a shorter encoding to clear RAX
- s390/pci: fix zpci_bus_link_virtfn()
- s390/pci: re-introduce zpci_remove_device()
- s390/pci: fix PF/VF linking on hot plug
- s390/pci: ignore stale configuration request event
- mm/memory.c: skip spurious TLB flush for retried page fault
- drm: amdgpu: Use the correct size when allocating memory
- drm/amdgpu/display: use GFP_ATOMIC in dcn20_validate_bandwidth_internal
- drm/amd/display: Fix incorrect backlight register offset for DCN
- drm/amd/display: Fix EDID parsing after resume from suspend
- drm/amd/display: Blank stream before destroying HDCP session
- drm/amd/display: Fix DFPstate hang due to view port changed
- drm/amd/display: fix pow() crashing when given base 0
- drm/i915/pmu: Prefer drm_WARN_ON over WARN_ON
- drm/i915: Provide the perf pmu.module
- scsi: ufs: Add DELAY_BEFORE_LPM quirk for Micron devices
- scsi: target: tcmu: Fix crash in tcmu_flush_dcache_range on ARM
- media: budget-core: Improve exception handling in budget_register()
- media: coda: jpeg: add NULL check after kmalloc
- f2fs: fix to check page dirty status before writeback
- rtc: goldfish: Enable interrupt in set_alarm() when necessary
- media: vpss: clean up resources in init
- f2fs: should avoid inode eviction in synchronous path
- Input: psmouse - add a newline when printing 'proto' by sysfs
- MIPS: Fix unable to reserve memory for Crash kernel
- m68knommu: fix overwriting of bits in ColdFire V3 cache control
- svcrdma: Fix another Receive buffer leak
- xfs: fix inode quota reservation checks
- drm/ttm: fix offset in VMAs with a pg_offs in ttm_bo_vm_access
- riscv: Fixup static_obj() fail
- jffs2: fix UAF problem
- ceph: fix use-after-free for fsc->mdsc
- swiotlb-xen: use vmalloc_to_page on vmalloc virt addresses
- cpufreq: intel_pstate: Fix cpuinfo_max_freq when MSR_TURBO_RATIO_LIMIT is 0
- scsi: libfc: Free skb in fc_disc_gpn_id_resp() for valid cases
- virtio_ring: Avoid loop when vq is broken in virtqueue_poll
- media: camss: fix memory leaks on error handling paths in probe
- tools/testing/selftests/cgroup/cgroup_util.c: cg_read_strcmp: fix null
  pointer dereference
- xfs: Fix UBSAN null-ptr-deref in xfs_sysfs_init
- alpha: fix annotation of io{read,write}{16,32}be()
- fat: fix fat_ra_init() for data clusters == 0
- fs/signalfd.c: fix inconsistent return codes for signalfd4
- ext4: fix potential negative array index in do_split()
- drm/virtio: fix missing dma_fence_put() in virtio_gpu_execbuffer_ioctl()
- ext4: don't allow overlapping system zones
- ext4: check journal inode extents more carefully
- netfilter: nf_tables: nft_exthdr: 

[Kernel-packages] [Bug 1892010] Re: [SRU] Fix acpi backlight issue on some thinkpads

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.8.0-18.19

---
linux (5.8.0-18.19) groovy; urgency=medium

  * groovy/linux: 5.8.0-18.19 -proposed tracker (LP: #1893047)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Groovy update: v5.8.4 upstream stable release (LP: #1893048)
- drm/vgem: Replace opencoded version of drm_gem_dumb_map_offset()
- drm/panel-simple: Fix inverted V/H SYNC for Frida FRD350H54004 panel
- drm/ast: Remove unused code paths for AST 1180
- drm/ast: Initialize DRAM type before posting GPU
- khugepaged: adjust VM_BUG_ON_MM() in __khugepaged_enter()
- ALSA: hda: avoid reset of sdo_limit
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Flex Book
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Book Ion
- can: j1939: transport: j1939_session_tx_dat(): fix use-after-free read in
  j1939_tp_txtimer()
- can: j1939: socket: j1939_sk_bind(): make sure ml_priv is allocated
- spi: Prevent adding devices below an unregistering controller
- io_uring: find and cancel head link async work on files exit
- mm/vunmap: add cond_resched() in vunmap_pmd_range
- romfs: fix uninitialized memory leak in romfs_dev_read()
- kernel/relay.c: fix memleak on destroy relay channel
- uprobes: __replace_page() avoid BUG in munlock_vma_page()
- squashfs: avoid bio_alloc() failure with 1Mbyte blocks
- mm: include CMA pages in lowmem_reserve at boot
- mm, page_alloc: fix core hung in free_pcppages_bulk()
- ASoC: amd: renoir: restore two more registers during resume
- RDMA/hfi1: Correct an interlock issue for TID RDMA WRITE request
- opp: Enable resources again if they were disabled earlier
- opp: Put opp table in dev_pm_opp_set_rate() for empty tables
- opp: Put opp table in dev_pm_opp_set_rate() if _set_opp_bw() fails
- ext4: do not block RWF_NOWAIT dio write on unallocated space
- ext4: fix checking of directory entry validity for inline directories
- jbd2: add the missing unlock_buffer() in the error path of
  jbd2_write_superblock()
- scsi: zfcp: Fix use-after-free in request timeout handlers
- selftests: kvm: Use a shorter encoding to clear RAX
- s390/pci: fix zpci_bus_link_virtfn()
- s390/pci: re-introduce zpci_remove_device()
- s390/pci: fix PF/VF linking on hot plug
- s390/pci: ignore stale configuration request event
- mm/memory.c: skip spurious TLB flush for retried page fault
- drm: amdgpu: Use the correct size when allocating memory
- drm/amdgpu/display: use GFP_ATOMIC in dcn20_validate_bandwidth_internal
- drm/amd/display: Fix incorrect backlight register offset for DCN
- drm/amd/display: Fix EDID parsing after resume from suspend
- drm/amd/display: Blank stream before destroying HDCP session
- drm/amd/display: Fix DFPstate hang due to view port changed
- drm/amd/display: fix pow() crashing when given base 0
- drm/i915/pmu: Prefer drm_WARN_ON over WARN_ON
- drm/i915: Provide the perf pmu.module
- scsi: ufs: Add DELAY_BEFORE_LPM quirk for Micron devices
- scsi: target: tcmu: Fix crash in tcmu_flush_dcache_range on ARM
- media: budget-core: Improve exception handling in budget_register()
- media: coda: jpeg: add NULL check after kmalloc
- f2fs: fix to check page dirty status before writeback
- rtc: goldfish: Enable interrupt in set_alarm() when necessary
- media: vpss: clean up resources in init
- f2fs: should avoid inode eviction in synchronous path
- Input: psmouse - add a newline when printing 'proto' by sysfs
- MIPS: Fix unable to reserve memory for Crash kernel
- m68knommu: fix overwriting of bits in ColdFire V3 cache control
- svcrdma: Fix another Receive buffer leak
- xfs: fix inode quota reservation checks
- drm/ttm: fix offset in VMAs with a pg_offs in ttm_bo_vm_access
- riscv: Fixup static_obj() fail
- jffs2: fix UAF problem
- ceph: fix use-after-free for fsc->mdsc
- swiotlb-xen: use vmalloc_to_page on vmalloc virt addresses
- cpufreq: intel_pstate: Fix cpuinfo_max_freq when MSR_TURBO_RATIO_LIMIT is 0
- scsi: libfc: Free skb in fc_disc_gpn_id_resp() for valid cases
- virtio_ring: Avoid loop when vq is broken in virtqueue_poll
- media: camss: fix memory leaks on error handling paths in probe
- tools/testing/selftests/cgroup/cgroup_util.c: cg_read_strcmp: fix null
  pointer dereference
- xfs: Fix UBSAN null-ptr-deref in xfs_sysfs_init
- alpha: fix annotation of io{read,write}{16,32}be()
- fat: fix fat_ra_init() for data clusters == 0
- fs/signalfd.c: fix inconsistent return codes for signalfd4
- ext4: fix potential negative array index in do_split()
- drm/virtio: fix missing dma_fence_put() in virtio_gpu_execbuffer_ioctl()
- ext4: don't allow overlapping system zones
- ext4: check journal inode extents more carefully
- netfilter: nf_tables: nft_exthdr: 

[Kernel-packages] [Bug 1891281] Re: Disable Lenovo P620 Rear line-in volume control

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.8.0-18.19

---
linux (5.8.0-18.19) groovy; urgency=medium

  * groovy/linux: 5.8.0-18.19 -proposed tracker (LP: #1893047)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Groovy update: v5.8.4 upstream stable release (LP: #1893048)
- drm/vgem: Replace opencoded version of drm_gem_dumb_map_offset()
- drm/panel-simple: Fix inverted V/H SYNC for Frida FRD350H54004 panel
- drm/ast: Remove unused code paths for AST 1180
- drm/ast: Initialize DRAM type before posting GPU
- khugepaged: adjust VM_BUG_ON_MM() in __khugepaged_enter()
- ALSA: hda: avoid reset of sdo_limit
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Flex Book
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Book Ion
- can: j1939: transport: j1939_session_tx_dat(): fix use-after-free read in
  j1939_tp_txtimer()
- can: j1939: socket: j1939_sk_bind(): make sure ml_priv is allocated
- spi: Prevent adding devices below an unregistering controller
- io_uring: find and cancel head link async work on files exit
- mm/vunmap: add cond_resched() in vunmap_pmd_range
- romfs: fix uninitialized memory leak in romfs_dev_read()
- kernel/relay.c: fix memleak on destroy relay channel
- uprobes: __replace_page() avoid BUG in munlock_vma_page()
- squashfs: avoid bio_alloc() failure with 1Mbyte blocks
- mm: include CMA pages in lowmem_reserve at boot
- mm, page_alloc: fix core hung in free_pcppages_bulk()
- ASoC: amd: renoir: restore two more registers during resume
- RDMA/hfi1: Correct an interlock issue for TID RDMA WRITE request
- opp: Enable resources again if they were disabled earlier
- opp: Put opp table in dev_pm_opp_set_rate() for empty tables
- opp: Put opp table in dev_pm_opp_set_rate() if _set_opp_bw() fails
- ext4: do not block RWF_NOWAIT dio write on unallocated space
- ext4: fix checking of directory entry validity for inline directories
- jbd2: add the missing unlock_buffer() in the error path of
  jbd2_write_superblock()
- scsi: zfcp: Fix use-after-free in request timeout handlers
- selftests: kvm: Use a shorter encoding to clear RAX
- s390/pci: fix zpci_bus_link_virtfn()
- s390/pci: re-introduce zpci_remove_device()
- s390/pci: fix PF/VF linking on hot plug
- s390/pci: ignore stale configuration request event
- mm/memory.c: skip spurious TLB flush for retried page fault
- drm: amdgpu: Use the correct size when allocating memory
- drm/amdgpu/display: use GFP_ATOMIC in dcn20_validate_bandwidth_internal
- drm/amd/display: Fix incorrect backlight register offset for DCN
- drm/amd/display: Fix EDID parsing after resume from suspend
- drm/amd/display: Blank stream before destroying HDCP session
- drm/amd/display: Fix DFPstate hang due to view port changed
- drm/amd/display: fix pow() crashing when given base 0
- drm/i915/pmu: Prefer drm_WARN_ON over WARN_ON
- drm/i915: Provide the perf pmu.module
- scsi: ufs: Add DELAY_BEFORE_LPM quirk for Micron devices
- scsi: target: tcmu: Fix crash in tcmu_flush_dcache_range on ARM
- media: budget-core: Improve exception handling in budget_register()
- media: coda: jpeg: add NULL check after kmalloc
- f2fs: fix to check page dirty status before writeback
- rtc: goldfish: Enable interrupt in set_alarm() when necessary
- media: vpss: clean up resources in init
- f2fs: should avoid inode eviction in synchronous path
- Input: psmouse - add a newline when printing 'proto' by sysfs
- MIPS: Fix unable to reserve memory for Crash kernel
- m68knommu: fix overwriting of bits in ColdFire V3 cache control
- svcrdma: Fix another Receive buffer leak
- xfs: fix inode quota reservation checks
- drm/ttm: fix offset in VMAs with a pg_offs in ttm_bo_vm_access
- riscv: Fixup static_obj() fail
- jffs2: fix UAF problem
- ceph: fix use-after-free for fsc->mdsc
- swiotlb-xen: use vmalloc_to_page on vmalloc virt addresses
- cpufreq: intel_pstate: Fix cpuinfo_max_freq when MSR_TURBO_RATIO_LIMIT is 0
- scsi: libfc: Free skb in fc_disc_gpn_id_resp() for valid cases
- virtio_ring: Avoid loop when vq is broken in virtqueue_poll
- media: camss: fix memory leaks on error handling paths in probe
- tools/testing/selftests/cgroup/cgroup_util.c: cg_read_strcmp: fix null
  pointer dereference
- xfs: Fix UBSAN null-ptr-deref in xfs_sysfs_init
- alpha: fix annotation of io{read,write}{16,32}be()
- fat: fix fat_ra_init() for data clusters == 0
- fs/signalfd.c: fix inconsistent return codes for signalfd4
- ext4: fix potential negative array index in do_split()
- drm/virtio: fix missing dma_fence_put() in virtio_gpu_execbuffer_ioctl()
- ext4: don't allow overlapping system zones
- ext4: check journal inode extents more carefully
- netfilter: nf_tables: nft_exthdr: 

[Kernel-packages] [Bug 1891617] Re: Fix missing HDMI Audio on another HP Desktop

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.8.0-18.19

---
linux (5.8.0-18.19) groovy; urgency=medium

  * groovy/linux: 5.8.0-18.19 -proposed tracker (LP: #1893047)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Groovy update: v5.8.4 upstream stable release (LP: #1893048)
- drm/vgem: Replace opencoded version of drm_gem_dumb_map_offset()
- drm/panel-simple: Fix inverted V/H SYNC for Frida FRD350H54004 panel
- drm/ast: Remove unused code paths for AST 1180
- drm/ast: Initialize DRAM type before posting GPU
- khugepaged: adjust VM_BUG_ON_MM() in __khugepaged_enter()
- ALSA: hda: avoid reset of sdo_limit
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Flex Book
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Book Ion
- can: j1939: transport: j1939_session_tx_dat(): fix use-after-free read in
  j1939_tp_txtimer()
- can: j1939: socket: j1939_sk_bind(): make sure ml_priv is allocated
- spi: Prevent adding devices below an unregistering controller
- io_uring: find and cancel head link async work on files exit
- mm/vunmap: add cond_resched() in vunmap_pmd_range
- romfs: fix uninitialized memory leak in romfs_dev_read()
- kernel/relay.c: fix memleak on destroy relay channel
- uprobes: __replace_page() avoid BUG in munlock_vma_page()
- squashfs: avoid bio_alloc() failure with 1Mbyte blocks
- mm: include CMA pages in lowmem_reserve at boot
- mm, page_alloc: fix core hung in free_pcppages_bulk()
- ASoC: amd: renoir: restore two more registers during resume
- RDMA/hfi1: Correct an interlock issue for TID RDMA WRITE request
- opp: Enable resources again if they were disabled earlier
- opp: Put opp table in dev_pm_opp_set_rate() for empty tables
- opp: Put opp table in dev_pm_opp_set_rate() if _set_opp_bw() fails
- ext4: do not block RWF_NOWAIT dio write on unallocated space
- ext4: fix checking of directory entry validity for inline directories
- jbd2: add the missing unlock_buffer() in the error path of
  jbd2_write_superblock()
- scsi: zfcp: Fix use-after-free in request timeout handlers
- selftests: kvm: Use a shorter encoding to clear RAX
- s390/pci: fix zpci_bus_link_virtfn()
- s390/pci: re-introduce zpci_remove_device()
- s390/pci: fix PF/VF linking on hot plug
- s390/pci: ignore stale configuration request event
- mm/memory.c: skip spurious TLB flush for retried page fault
- drm: amdgpu: Use the correct size when allocating memory
- drm/amdgpu/display: use GFP_ATOMIC in dcn20_validate_bandwidth_internal
- drm/amd/display: Fix incorrect backlight register offset for DCN
- drm/amd/display: Fix EDID parsing after resume from suspend
- drm/amd/display: Blank stream before destroying HDCP session
- drm/amd/display: Fix DFPstate hang due to view port changed
- drm/amd/display: fix pow() crashing when given base 0
- drm/i915/pmu: Prefer drm_WARN_ON over WARN_ON
- drm/i915: Provide the perf pmu.module
- scsi: ufs: Add DELAY_BEFORE_LPM quirk for Micron devices
- scsi: target: tcmu: Fix crash in tcmu_flush_dcache_range on ARM
- media: budget-core: Improve exception handling in budget_register()
- media: coda: jpeg: add NULL check after kmalloc
- f2fs: fix to check page dirty status before writeback
- rtc: goldfish: Enable interrupt in set_alarm() when necessary
- media: vpss: clean up resources in init
- f2fs: should avoid inode eviction in synchronous path
- Input: psmouse - add a newline when printing 'proto' by sysfs
- MIPS: Fix unable to reserve memory for Crash kernel
- m68knommu: fix overwriting of bits in ColdFire V3 cache control
- svcrdma: Fix another Receive buffer leak
- xfs: fix inode quota reservation checks
- drm/ttm: fix offset in VMAs with a pg_offs in ttm_bo_vm_access
- riscv: Fixup static_obj() fail
- jffs2: fix UAF problem
- ceph: fix use-after-free for fsc->mdsc
- swiotlb-xen: use vmalloc_to_page on vmalloc virt addresses
- cpufreq: intel_pstate: Fix cpuinfo_max_freq when MSR_TURBO_RATIO_LIMIT is 0
- scsi: libfc: Free skb in fc_disc_gpn_id_resp() for valid cases
- virtio_ring: Avoid loop when vq is broken in virtqueue_poll
- media: camss: fix memory leaks on error handling paths in probe
- tools/testing/selftests/cgroup/cgroup_util.c: cg_read_strcmp: fix null
  pointer dereference
- xfs: Fix UBSAN null-ptr-deref in xfs_sysfs_init
- alpha: fix annotation of io{read,write}{16,32}be()
- fat: fix fat_ra_init() for data clusters == 0
- fs/signalfd.c: fix inconsistent return codes for signalfd4
- ext4: fix potential negative array index in do_split()
- drm/virtio: fix missing dma_fence_put() in virtio_gpu_execbuffer_ioctl()
- ext4: don't allow overlapping system zones
- ext4: check journal inode extents more carefully
- netfilter: nf_tables: nft_exthdr: 

[Kernel-packages] [Bug 1892215] Re: Groovy update: v5.8.2 upstream stable release

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.8.0-18.19

---
linux (5.8.0-18.19) groovy; urgency=medium

  * groovy/linux: 5.8.0-18.19 -proposed tracker (LP: #1893047)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Groovy update: v5.8.4 upstream stable release (LP: #1893048)
- drm/vgem: Replace opencoded version of drm_gem_dumb_map_offset()
- drm/panel-simple: Fix inverted V/H SYNC for Frida FRD350H54004 panel
- drm/ast: Remove unused code paths for AST 1180
- drm/ast: Initialize DRAM type before posting GPU
- khugepaged: adjust VM_BUG_ON_MM() in __khugepaged_enter()
- ALSA: hda: avoid reset of sdo_limit
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Flex Book
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Book Ion
- can: j1939: transport: j1939_session_tx_dat(): fix use-after-free read in
  j1939_tp_txtimer()
- can: j1939: socket: j1939_sk_bind(): make sure ml_priv is allocated
- spi: Prevent adding devices below an unregistering controller
- io_uring: find and cancel head link async work on files exit
- mm/vunmap: add cond_resched() in vunmap_pmd_range
- romfs: fix uninitialized memory leak in romfs_dev_read()
- kernel/relay.c: fix memleak on destroy relay channel
- uprobes: __replace_page() avoid BUG in munlock_vma_page()
- squashfs: avoid bio_alloc() failure with 1Mbyte blocks
- mm: include CMA pages in lowmem_reserve at boot
- mm, page_alloc: fix core hung in free_pcppages_bulk()
- ASoC: amd: renoir: restore two more registers during resume
- RDMA/hfi1: Correct an interlock issue for TID RDMA WRITE request
- opp: Enable resources again if they were disabled earlier
- opp: Put opp table in dev_pm_opp_set_rate() for empty tables
- opp: Put opp table in dev_pm_opp_set_rate() if _set_opp_bw() fails
- ext4: do not block RWF_NOWAIT dio write on unallocated space
- ext4: fix checking of directory entry validity for inline directories
- jbd2: add the missing unlock_buffer() in the error path of
  jbd2_write_superblock()
- scsi: zfcp: Fix use-after-free in request timeout handlers
- selftests: kvm: Use a shorter encoding to clear RAX
- s390/pci: fix zpci_bus_link_virtfn()
- s390/pci: re-introduce zpci_remove_device()
- s390/pci: fix PF/VF linking on hot plug
- s390/pci: ignore stale configuration request event
- mm/memory.c: skip spurious TLB flush for retried page fault
- drm: amdgpu: Use the correct size when allocating memory
- drm/amdgpu/display: use GFP_ATOMIC in dcn20_validate_bandwidth_internal
- drm/amd/display: Fix incorrect backlight register offset for DCN
- drm/amd/display: Fix EDID parsing after resume from suspend
- drm/amd/display: Blank stream before destroying HDCP session
- drm/amd/display: Fix DFPstate hang due to view port changed
- drm/amd/display: fix pow() crashing when given base 0
- drm/i915/pmu: Prefer drm_WARN_ON over WARN_ON
- drm/i915: Provide the perf pmu.module
- scsi: ufs: Add DELAY_BEFORE_LPM quirk for Micron devices
- scsi: target: tcmu: Fix crash in tcmu_flush_dcache_range on ARM
- media: budget-core: Improve exception handling in budget_register()
- media: coda: jpeg: add NULL check after kmalloc
- f2fs: fix to check page dirty status before writeback
- rtc: goldfish: Enable interrupt in set_alarm() when necessary
- media: vpss: clean up resources in init
- f2fs: should avoid inode eviction in synchronous path
- Input: psmouse - add a newline when printing 'proto' by sysfs
- MIPS: Fix unable to reserve memory for Crash kernel
- m68knommu: fix overwriting of bits in ColdFire V3 cache control
- svcrdma: Fix another Receive buffer leak
- xfs: fix inode quota reservation checks
- drm/ttm: fix offset in VMAs with a pg_offs in ttm_bo_vm_access
- riscv: Fixup static_obj() fail
- jffs2: fix UAF problem
- ceph: fix use-after-free for fsc->mdsc
- swiotlb-xen: use vmalloc_to_page on vmalloc virt addresses
- cpufreq: intel_pstate: Fix cpuinfo_max_freq when MSR_TURBO_RATIO_LIMIT is 0
- scsi: libfc: Free skb in fc_disc_gpn_id_resp() for valid cases
- virtio_ring: Avoid loop when vq is broken in virtqueue_poll
- media: camss: fix memory leaks on error handling paths in probe
- tools/testing/selftests/cgroup/cgroup_util.c: cg_read_strcmp: fix null
  pointer dereference
- xfs: Fix UBSAN null-ptr-deref in xfs_sysfs_init
- alpha: fix annotation of io{read,write}{16,32}be()
- fat: fix fat_ra_init() for data clusters == 0
- fs/signalfd.c: fix inconsistent return codes for signalfd4
- ext4: fix potential negative array index in do_split()
- drm/virtio: fix missing dma_fence_put() in virtio_gpu_execbuffer_ioctl()
- ext4: don't allow overlapping system zones
- ext4: check journal inode extents more carefully
- netfilter: nf_tables: nft_exthdr: 

[Kernel-packages] [Bug 1891647] Re: Groovy update: v5.8.1 upstream stable release

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.8.0-18.19

---
linux (5.8.0-18.19) groovy; urgency=medium

  * groovy/linux: 5.8.0-18.19 -proposed tracker (LP: #1893047)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Groovy update: v5.8.4 upstream stable release (LP: #1893048)
- drm/vgem: Replace opencoded version of drm_gem_dumb_map_offset()
- drm/panel-simple: Fix inverted V/H SYNC for Frida FRD350H54004 panel
- drm/ast: Remove unused code paths for AST 1180
- drm/ast: Initialize DRAM type before posting GPU
- khugepaged: adjust VM_BUG_ON_MM() in __khugepaged_enter()
- ALSA: hda: avoid reset of sdo_limit
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Flex Book
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Book Ion
- can: j1939: transport: j1939_session_tx_dat(): fix use-after-free read in
  j1939_tp_txtimer()
- can: j1939: socket: j1939_sk_bind(): make sure ml_priv is allocated
- spi: Prevent adding devices below an unregistering controller
- io_uring: find and cancel head link async work on files exit
- mm/vunmap: add cond_resched() in vunmap_pmd_range
- romfs: fix uninitialized memory leak in romfs_dev_read()
- kernel/relay.c: fix memleak on destroy relay channel
- uprobes: __replace_page() avoid BUG in munlock_vma_page()
- squashfs: avoid bio_alloc() failure with 1Mbyte blocks
- mm: include CMA pages in lowmem_reserve at boot
- mm, page_alloc: fix core hung in free_pcppages_bulk()
- ASoC: amd: renoir: restore two more registers during resume
- RDMA/hfi1: Correct an interlock issue for TID RDMA WRITE request
- opp: Enable resources again if they were disabled earlier
- opp: Put opp table in dev_pm_opp_set_rate() for empty tables
- opp: Put opp table in dev_pm_opp_set_rate() if _set_opp_bw() fails
- ext4: do not block RWF_NOWAIT dio write on unallocated space
- ext4: fix checking of directory entry validity for inline directories
- jbd2: add the missing unlock_buffer() in the error path of
  jbd2_write_superblock()
- scsi: zfcp: Fix use-after-free in request timeout handlers
- selftests: kvm: Use a shorter encoding to clear RAX
- s390/pci: fix zpci_bus_link_virtfn()
- s390/pci: re-introduce zpci_remove_device()
- s390/pci: fix PF/VF linking on hot plug
- s390/pci: ignore stale configuration request event
- mm/memory.c: skip spurious TLB flush for retried page fault
- drm: amdgpu: Use the correct size when allocating memory
- drm/amdgpu/display: use GFP_ATOMIC in dcn20_validate_bandwidth_internal
- drm/amd/display: Fix incorrect backlight register offset for DCN
- drm/amd/display: Fix EDID parsing after resume from suspend
- drm/amd/display: Blank stream before destroying HDCP session
- drm/amd/display: Fix DFPstate hang due to view port changed
- drm/amd/display: fix pow() crashing when given base 0
- drm/i915/pmu: Prefer drm_WARN_ON over WARN_ON
- drm/i915: Provide the perf pmu.module
- scsi: ufs: Add DELAY_BEFORE_LPM quirk for Micron devices
- scsi: target: tcmu: Fix crash in tcmu_flush_dcache_range on ARM
- media: budget-core: Improve exception handling in budget_register()
- media: coda: jpeg: add NULL check after kmalloc
- f2fs: fix to check page dirty status before writeback
- rtc: goldfish: Enable interrupt in set_alarm() when necessary
- media: vpss: clean up resources in init
- f2fs: should avoid inode eviction in synchronous path
- Input: psmouse - add a newline when printing 'proto' by sysfs
- MIPS: Fix unable to reserve memory for Crash kernel
- m68knommu: fix overwriting of bits in ColdFire V3 cache control
- svcrdma: Fix another Receive buffer leak
- xfs: fix inode quota reservation checks
- drm/ttm: fix offset in VMAs with a pg_offs in ttm_bo_vm_access
- riscv: Fixup static_obj() fail
- jffs2: fix UAF problem
- ceph: fix use-after-free for fsc->mdsc
- swiotlb-xen: use vmalloc_to_page on vmalloc virt addresses
- cpufreq: intel_pstate: Fix cpuinfo_max_freq when MSR_TURBO_RATIO_LIMIT is 0
- scsi: libfc: Free skb in fc_disc_gpn_id_resp() for valid cases
- virtio_ring: Avoid loop when vq is broken in virtqueue_poll
- media: camss: fix memory leaks on error handling paths in probe
- tools/testing/selftests/cgroup/cgroup_util.c: cg_read_strcmp: fix null
  pointer dereference
- xfs: Fix UBSAN null-ptr-deref in xfs_sysfs_init
- alpha: fix annotation of io{read,write}{16,32}be()
- fat: fix fat_ra_init() for data clusters == 0
- fs/signalfd.c: fix inconsistent return codes for signalfd4
- ext4: fix potential negative array index in do_split()
- drm/virtio: fix missing dma_fence_put() in virtio_gpu_execbuffer_ioctl()
- ext4: don't allow overlapping system zones
- ext4: check journal inode extents more carefully
- netfilter: nf_tables: nft_exthdr: 

[Kernel-packages] [Bug 1892714] Re: Microphone not working on HP Omen 17

[Vedran Rafaelic]

After doing a minor update (through Software Updater) couple of days
ago, which included several dozen of packages (I remember alsa something
was in it) with a new kernel in it 5.4.0-45-generic (from
5.4.0-42-generic) the freezing started again to happen after login
(almost always).

Now I managed to make a dmesg after a number of restarts. Do you think
it has something to do with this issue, or should I open a new bug?
Audio is working on 5.4.0-45, it is just the freeze.

(I'm booting 5.4.0-42 last couple of days as a workaround)

** Attachment added: "dmesg_5_4_0_45.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1892714/+attachment/5407528/+files/dmesg_5_4_0_45.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/1892714

Title:
  Microphone not working on HP Omen 17

Status in linux-firmware package in Ubuntu:
  Triaged

Bug description:
  I have the following laptop https://support.hp.com/us-en/product/omen-
  by-hp-17-cb-laptop-pc/26122176/document/c06411586

  I cannot make the internal microphone to work. Sound->Input device
  gives no device list. Jack plug (pink) mic works.

  (The link says: HP Wide Vision HD Camera with integrated dual array
  digital microphone. So I guess this is the one and only internal
  microphone.)

  cat /proc/asound/card0/codec* | grep Codec   Codec: Realtek ALC285
  cat /proc/asound/card1/codec* | grep Codec   Codec: Nvidia GPU 92 HDMI/DP

  I guess the internal microphone is related to this "Realtek ALC285"
  codec.

  
  In alsa-base.conf I had to add "options snd-hda-intel dmic_detect=0" or 
otherwise my screen freezes soon after boot.

  I tried "options snd-hda-intel model=laptop-amic" and "model=laptop-
  dmic" and "model=auto". The "model=laptop-dmic" shows the device in
  "Sound->Input device" but it loops laptop's sound output into the
  input.

  
  OS: Ubuntu 20.04
  uname -a: 5.4.0-42-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  croraf 1940 F pulseaudio
   /dev/snd/controlC0:  croraf 1940 F pulseaudio
   /dev/snd/pcmC0D0p:   croraf 1940 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-16 (281 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: HP OMEN by HP Laptop 17-cb0xxx
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-07-13 (42 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8603
  dmi.board.vendor: HP
  dmi.board.version: 45.38
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 17-cb0xxx
  dmi.product.sku: 7NG00EA#BED
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1892714/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1893820] Re: DPLL2 override remains enabled after warm boot of Linux

[Timo Aaltonen]

18.04.1 is using kernel version 4.4, please test with 20.04.1 which has
5.4.

** Package changed: ubuntu => linux (Ubuntu)

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1893820

Title:
  DPLL2 override remains enabled after warm boot of Linux

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu Version Target: 18.04.1 LTS (bootable Ubuntu USB stick)

  Package Version Target: Unknown

  Expected: Windows S3 Sleep actions with two DisplayPort monitors using
  Intel integrated graphics should be able to work without issue after
  entering a Windows OS from a previously loaded Ubuntu session

  Actual: Windows S3 Sleep actions with two DisplayPort monitors using
  Intel integrated graphics will result in a BSOD event if a Windows OS
  is loaded after an Ubuntu OS session that was ended by a warm reboot
  action

  Description:
  Using a dual-boot Ubuntu/Windows 10 desktop computer environment with two 
native DisplayPort MB connections to the Intel integrated graphics solution and 
two DisplayPort monitors it was observed that performing a Windows S3 Sleep 
action will cause a "WHEA uncorrectable error" BSOD event if the first OS 
loaded is Linux and the second OS Windows is loaded using a warm boot action.

  Investigating this BSOD event further it was determined that this issue is 
specific to the "Linux->warm boot->Windows->S3 Sleep" sequence as long as two 
DisplayPort monitors are connected to the desktop computer's DisplayPort MB 
connections. 
   
  A deeper investigation of the cause of the BSOD identified that upon 
unloading Linux the DPLL2 override bit remains enabled and will cause a 
subsequent Windows desktop environment to be vulnerable to failure if it makes 
use of two DisplayPort-connected monitors.

  This issue can be reproduced using OEM hardware from either of Lenovo, HP, or 
Dell.
  This issue was first observed on the Q270/Q370 Intel chipset and the Intel 
530/630 Graphics hardware.
  Calvin Hartwell of Canonical has been made aware of this issue and been 
provided issue details and video evidence.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893820/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1893820] Re: DPLL2 override remains enabled after warm boot of Linux

[Timo Aaltonen]

Or use 18.04.5 which has kernel 5.4 backported from 20.04.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1893820

Title:
  DPLL2 override remains enabled after warm boot of Linux

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu Version Target: 18.04.1 LTS (bootable Ubuntu USB stick)

  Package Version Target: Unknown

  Expected: Windows S3 Sleep actions with two DisplayPort monitors using
  Intel integrated graphics should be able to work without issue after
  entering a Windows OS from a previously loaded Ubuntu session

  Actual: Windows S3 Sleep actions with two DisplayPort monitors using
  Intel integrated graphics will result in a BSOD event if a Windows OS
  is loaded after an Ubuntu OS session that was ended by a warm reboot
  action

  Description:
  Using a dual-boot Ubuntu/Windows 10 desktop computer environment with two 
native DisplayPort MB connections to the Intel integrated graphics solution and 
two DisplayPort monitors it was observed that performing a Windows S3 Sleep 
action will cause a "WHEA uncorrectable error" BSOD event if the first OS 
loaded is Linux and the second OS Windows is loaded using a warm boot action.

  Investigating this BSOD event further it was determined that this issue is 
specific to the "Linux->warm boot->Windows->S3 Sleep" sequence as long as two 
DisplayPort monitors are connected to the desktop computer's DisplayPort MB 
connections. 
   
  A deeper investigation of the cause of the BSOD identified that upon 
unloading Linux the DPLL2 override bit remains enabled and will cause a 
subsequent Windows desktop environment to be vulnerable to failure if it makes 
use of two DisplayPort-connected monitors.

  This issue can be reproduced using OEM hardware from either of Lenovo, HP, or 
Dell.
  This issue was first observed on the Q270/Q370 Intel chipset and the Intel 
530/630 Graphics hardware.
  Calvin Hartwell of Canonical has been made aware of this issue and been 
provided issue details and video evidence.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893820/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1878484] Re: kernel panic on i915

[Launchpad Bug Tracker]

[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/1878484

Title:
  kernel panic on i915

Status in linux package in Ubuntu:
  Expired

Bug description:
  I'm using 20.04 fully up to date on an Asrock N3700.

  I'm getting random crashes every now and then. Total crash, no ssh or
  anything (later I found out it's a kernel panic). Not tied to any app,
  but it happened more often during gaming. Logs didn't show anything,
  they just stop. I set up netconsole, with debug and ignore_loglevel in
  the command line and I got this:

  [77196.866485] BUG: unable to handle page fault for address: 00a72860
  [77196.866527] #PF: supervisor read access in kernel mode
  [77196.866535] #PF: error_code(0x) - not-present page
  [77196.866542] PGD 0 P4D 0 
  [77196.866552] Oops:  [#1] SMP PTI
  [77196.866567] CPU: 2 PID: 1408 Comm: Xorg Tainted: P   O  
5.4.0-29-generic #33-Ubuntu
  [77196.866575] Hardware name: To Be Filled By O.E.M. To Be Filled By 
O.E.M./N3700-ITX, BIOS P2.00 04/16/2018
  [77196.866743] RIP: 0010:__i915_schedule+0x261/0x350 [i915]
  [77196.866748] Code: ff a8 08 0f 84 a0 00 00 00 45 3b b4 24 18 04 00 00 7e 50 
49 8b 84 24 d8 03 00 00 48 8b 00 48 85 c0 74 40 48 8b b3 30 ff ff ff <48> 39 70 
60 74 33 45 89 b4 24 18 04 00 00 8b 80 60 01 00 00 be 00
  [77196.866753] RSP: 0018:a48380c2b9e0 EFLAGS: 00010006
  [77196.866759] RAX: 00a72800 RBX: 961bed909a30 RCX: 
9619a559edb0
  [77196.866764] RDX: 961bed909a50 RSI: 961beaa21180 RDI: 
9619a559edc0
  [77196.866769] RBP: a48380c2ba78 R08: 961bf73f4420 R09: 
9619a559ed80
  [77196.866773] R10:  R11: 0208 R12: 
961bf73f4000
  [77196.866783] R13: a48380c2b9f0 R14: 1000 R15: 
a48380c2b9c0
  [77196.866788] FS:  7f6ee2aa9a80() GS:961bf830() 
knlGS:
  [77196.866794] CS:  0010 DS:  ES:  CR0: 80050033
  [77196.866798] CR2: 00a72860 CR3: 00026a0a2000 CR4: 
001006e0
  [77196.866802] Call Trace:
  [77196.866887]  i915_schedule+0x2d/0x50 [i915]
  [77196.866979]  __fence_set_priority+0x6b/0x90 [i915]
  [77196.867067]  fence_set_priority+0x23/0x60 [i915]
  [77196.867117]  i915_gem_object_wait_priority+0x13e/0x170 [i915]
  [77196.867194]  intel_prepare_plane_fb+0x1ab/0x2d0 [i915]
  [77196.867232]  drm_atomic_helper_prepare_planes+0x94/0x120 [drm_kms_helper]
  [77196.867305]  intel_atomic_commit+0xc2/0x2b0 [i915]
  [77196.867370]  drm_atomic_nonblocking_commit+0x4d/0x60 [drm]
  [77196.867401]  drm_atomic_helper_page_flip+0x63/0xa0 [drm_kms_helper]
  [77196.867443]  drm_mode_page_flip_ioctl+0x59d/0x630 [drm]
  [77196.867469]  ? drm_mode_cursor2_ioctl+0x10/0x10 [drm]
  [77196.867490]  drm_ioctl_kernel+0xae/0xf0 [drm]
  [77196.867512]  drm_ioctl+0x234/0x3d0 [drm]
  [77196.867536]  ? drm_mode_cursor2_ioctl+0x10/0x10 [drm]
  [77196.867550]  do_vfs_ioctl+0x407/0x670
  [77196.867560]  ? fput+0x13/0x15
  [77196.867568]  ? __sys_recvmsg+0x88/0xa0
  [77196.867575]  ksys_ioctl+0x67/0x90
  [77196.867582]  __x64_sys_ioctl+0x1a/0x20
  [77196.867592]  do_syscall_64+0x57/0x190
  [77196.867603]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [77196.867611] RIP: 0033:0x7f6ee2e0737b
  [77196.867618] Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 
c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48
  [77196.867624] RSP: 002b:7ffe6ff493d8 EFLAGS: 0246 ORIG_RAX: 
0010
  [77196.867631] RAX: ffda RBX: 7ffe6ff49410 RCX: 
7f6ee2e0737b
  [77196.867635] RDX: 7ffe6ff49410 RSI: c01864b0 RDI: 
000e
  [77196.867640] RBP: c01864b0 R08: 002bf8f2 R09: 
006a
  [77196.867645] R10: 000e R11: 0246 R12: 
56454c520040
  [77196.867649] R13: 000e R14: 002bf8f2 R15: 
0002
  [77196.867655] Modules linked in: bnep wireguard(O) ip6_udp_tunnel udp_tunnel 
binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) 
spl(O) zlua(PO) joydev input_leds nls_iso8859_1 snd_hda_codec_hdmi 
snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio intel_rapl_msr 
mei_hdcp snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep 
snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi intel_rapl_common 
intel_powerclamp coretemp kvm_intel kvm punit_atom_debug intel_cstate snd_seq 
snd_seq_device snd_timer snd mei_txe soundcore mei hci_uart 
intel_xhci_usb_role_switch btqca roles btrtl btbcm btintel bluetooth 
ecdh_generic ecc rfkill_gpio acpi_pad intel_int0002_vgpio mac_hid sch_fq_codel 
parport_pc ppdev lp parport ip_tables 

[Kernel-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones

[PowerKiKi]

This is great news !

I just tried your script, while a song was already playing, and I
instantly got sound on my speakers (both left and right).

While the script is running I can hear each side coming on. First left,
then right.

I also noticed that if switching to my bluetooth headphones, the
headphones will start, and the speakers will stop (as expected). However
when switching off my bluetooth headphones, the speaker will not work
again. But of course running the script again will restore speaker
sound. This sounds similar to the "non-sticky" behavior we experienced
for cabled headphones.

Anyway thanks a lot for the huge effort you put into this !

PS: I also run a custom Kernel with a slight variation of Mike's patch.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1851518

Title:
  [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on
  internal speakers, very very quiet on headphones

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've been googling this issue for 10's of hours and tried many things.

  Relase of Ubuntu: 19.10

  Expected outcome: Music plays on the internal speakers and headphones.

  Actual outcome: I can barely hear audio using headphones with volume
  turned up to 150%.  Absolutely nothing comes out of the speakers. (The
  speakers sound great under Windows 10.)

  Complete alsa-info output is attached, but here are some snippets:

  !!DMI Information
  !!---

  Manufacturer:  SAMSUNG ELECTRONICS CO., LTD.
  Product Name:  950SBE/951SBE
  Product Version:   P06RES
  Firmware Version:  P06RES.075.190529.SP
  Board Vendor:  SAMSUNG ELECTRONICS CO., LTD.
  Board Name:NP950SBE-K01US

  
  !!Kernel Information
  !!--

  Kernel release:5.3.0-19-generic
  Operating System:  GNU/Linux
  Architecture:  x86_64
  Processor: x86_64
  SMP Enabled:   Yes


  !!ALSA Version
  !!

  Driver version: k5.3.0-19-generic
  Library version:1.1.9
  Utilities version:  1.1.9

  
  !!Loaded ALSA modules
  !!---

  snd_hda_intel

  
  !!Sound Servers on this system
  !!

  Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - Yes

  
  !!Soundcards recognised by ALSA
  !!-

   0 [PCH]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0x604b118000 irq 177

  
  !!PCI Soundcards installed in the system
  !!--

  00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP
  High Definition Audio Controller (rev 11)

  
  !!Advanced information - PCI Vendor/Device/Subsystem ID's
  !!---

  00:1f.3 0401: 8086:9dc8 (rev 11)
  DeviceName: Onboard - Sound

  
  !!HDA-Intel Codec information
  !!---
  --startcollapse--

  Codec: Realtek ALC298
  Address: 0
  AFG Function Id: 0x1 (unsol 1)
  Vendor Id: 0x10ec0298
  Subsystem Id: 0x144dc812
  Revision Id: 0x100103
  No Modem Function Group found
  Default PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
  Default Amp-In caps: N/A
  Default Amp-Out caps: N/A
  State of AFG node 0x01:
Power states:  D0 D1 D2 D3 D3cold CLKSTOP EPSS
Power: setting=D0, actual=D0
  GPIO: io=8, o=0, i=0, unsolicited=1, wake=0
IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
  Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Headphone Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Device: name="ALC298 Analog", type="Audio", device=0
Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
Amp-Out vals:  [0x00 0x00]
Converter: stream=1, channel=0
PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
Power states:  D0 D1 D2 D3 EPSS
Power: setting=D0, actual=D0
  Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Speaker Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
Amp-Out vals:  [0x7f 0x7f]
Converter: stream=1, channel=0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 

[Kernel-packages] [Bug 1893820] [NEW] DPLL2 override remains enabled after warm boot of Linux

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Ubuntu Version Target: 18.04.1 LTS (bootable Ubuntu USB stick)

Package Version Target: Unknown

Expected: Windows S3 Sleep actions with two DisplayPort monitors using
Intel integrated graphics should be able to work without issue after
entering a Windows OS from a previously loaded Ubuntu session

Actual: Windows S3 Sleep actions with two DisplayPort monitors using
Intel integrated graphics will result in a BSOD event if a Windows OS is
loaded after an Ubuntu OS session that was ended by a warm reboot action

Description:
Using a dual-boot Ubuntu/Windows 10 desktop computer environment with two 
native DisplayPort MB connections to the Intel integrated graphics solution and 
two DisplayPort monitors it was observed that performing a Windows S3 Sleep 
action will cause a "WHEA uncorrectable error" BSOD event if the first OS 
loaded is Linux and the second OS Windows is loaded using a warm boot action.

Investigating this BSOD event further it was determined that this issue is 
specific to the "Linux->warm boot->Windows->S3 Sleep" sequence as long as two 
DisplayPort monitors are connected to the desktop computer's DisplayPort MB 
connections. 
 
A deeper investigation of the cause of the BSOD identified that upon unloading 
Linux the DPLL2 override bit remains enabled and will cause a subsequent 
Windows desktop environment to be vulnerable to failure if it makes use of two 
DisplayPort-connected monitors.

This issue can be reproduced using OEM hardware from either of Lenovo, HP, or 
Dell.
This issue was first observed on the Q270/Q370 Intel chipset and the Intel 
530/630 Graphics hardware.
Calvin Hartwell of Canonical has been made aware of this issue and been 
provided issue details and video evidence.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: bot-comment hw-specific suspend-resume
-- 
DPLL2 override remains enabled after warm boot of Linux
https://bugs.launchpad.net/bugs/1893820
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1892714] Re: Microphone not working on HP Omen 17

[Hui Wang]

I think you upgraded the linux-firmware, then the sof-cfl.ri is back to
v1.4.2. Please backup this file and use the file in the #46.

-- 
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/1892714

Title:
  Microphone not working on HP Omen 17

Status in linux-firmware package in Ubuntu:
  Triaged

Bug description:
  I have the following laptop https://support.hp.com/us-en/product/omen-
  by-hp-17-cb-laptop-pc/26122176/document/c06411586

  I cannot make the internal microphone to work. Sound->Input device
  gives no device list. Jack plug (pink) mic works.

  (The link says: HP Wide Vision HD Camera with integrated dual array
  digital microphone. So I guess this is the one and only internal
  microphone.)

  cat /proc/asound/card0/codec* | grep Codec   Codec: Realtek ALC285
  cat /proc/asound/card1/codec* | grep Codec   Codec: Nvidia GPU 92 HDMI/DP

  I guess the internal microphone is related to this "Realtek ALC285"
  codec.

  
  In alsa-base.conf I had to add "options snd-hda-intel dmic_detect=0" or 
otherwise my screen freezes soon after boot.

  I tried "options snd-hda-intel model=laptop-amic" and "model=laptop-
  dmic" and "model=auto". The "model=laptop-dmic" shows the device in
  "Sound->Input device" but it loops laptop's sound output into the
  input.

  
  OS: Ubuntu 20.04
  uname -a: 5.4.0-42-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  croraf 1940 F pulseaudio
   /dev/snd/controlC0:  croraf 1940 F pulseaudio
   /dev/snd/pcmC0D0p:   croraf 1940 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-16 (281 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: HP OMEN by HP Laptop 17-cb0xxx
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-07-13 (42 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8603
  dmi.board.vendor: HP
  dmi.board.version: 45.38
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 17-cb0xxx
  dmi.product.sku: 7NG00EA#BED
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1892714/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1834771] Re: No HDMI-audio after kernel 4.15.-0.50

[Gerry]

Yes, I should have updated this.
I tried about 6-7 kernels all between 4.15 and 4.18.19 (i think, or some high 
number like that), all of them worked across Ubuntu, Linux Mint, Fedora, and 
Debian, and I think it was Manjaro. 100% no audio issues.

But once i tried the 4.19 kernel (or higher, I tried about 8 kernels
such as 4.19.0, 5.10, 5.2, 5.5, 5.5, 5.7, 5.8 etc), no luck across any
distribution!

So something definitely changed in the audio settings in the move from
the last kernel build in the 4.18 build and the 4.19 series and higher.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1834771

Title:
  No HDMI-audio after kernel 4.15.-0.50

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've got no HDMI-audio. Latest kernel with working HDMI-audio is 4.15.-0.50. 
In pavucontrol HDMI-audio shows unplugged. And also internal audio shows 
unplugged, but it still works. I'm on linux mint 18.3.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jouni  1859 F pulseaudio
   /dev/snd/controlC1:  jouni  1859 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=9e8d7bf3-dc5f-4c72-b875-6dbe81a36c36
  InstallationDate: Installed on 2017-01-28 (883 days ago)
  InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic 
root=UUID=f167a2b0-3b30-4a5a-907f-6b97c95b7a91 ro quiet iommu=soft splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-54.58~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-54-generic N/A
   linux-backports-modules-4.15.0-54-generic  N/A
   linux-firmware 1.157.21
  RfKill:
   
  Tags:  sylvia
  Uname: Linux 4.15.0-54-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 02/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FC
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970A-UD3P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFC:bd02/26/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834771/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1881096] Re: [UBUNTU 20.04] Deflate counters reported by lscpumf are not valid or available with perf

[Frank Heimes]

The fix landed in focal master with 'Ubuntu-5.4.0-43.47' and we are as
of today at '5.4.0.45.49' in focal-updates, hence updating the focal
entry of this ticket to Fix Released.

** Changed in: linux (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: ubuntu-z-systems
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1881096

Title:
  [UBUNTU 20.04] Deflate counters reported by lscpumf are not valid or
  available with perf

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

  * With perf from Ubuntu 20.04 on IBM z15 hardware, some counters
  reported with lscpumf are not usable with 'perf stat -e'.

  * 'lscpumf -c' provides a list of available counters, but the
  following are not usable: DFLT_ACCESS, DFLT_CYCLES, DFLT_CC,
  DFLT_CCERROR

  * 'perf list' is also not offering these counters.

  * On the kernel side this is fixed with the following upstream
  accepted commit:

  [Fix]

  * d68d5d51dc898895b4e15bea52e5668ca9e76180 d68d5d51dc898895b
  "s390/cpum_cf: Add new extended counters for IBM z15"

  [Test Case]

  * Requires the fix/patch of the perf tool, as mentioned in the bug,
  too.

  * An IBM z15 (or LinuxONE III) system with Ubuntu 20.04 installed in
  LPAR is needed where the counters are enabled in the activation
  profile.

  * Use 'perf list' to determine if the counters DFLT_ACCESS,
  DFLT_CYCLES, DFLT_CC, DFLT_CCERROR are listed

  * Use 'perf stat -e' to enable amd make use of these counters.

  [Regression Potential]

  * The regression can be considered as low, since:

  * it's architecture specific (s390x)

  * limited to IBM z15 hardware

  * and only additional (s390x) hardware counters are defined and added.

  [Other]

  * This requires a patch to be included into the perf itself, too -
  please see bug description for more details.

  * Since this patch is upstream in kernel 5.7 it will automatically
  land in groovy.

  __

  ---Problem Description---
  ubuntu 20.04: perf on z15: some counters reported with lscpumf are not usable 
with perf stat -e

  ---uname output---
  Linux ubu204 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:57:22 UTC 2020 
s390x s390x s390x GNU/Linux

  Machine Type = z15 8561

  ---Steps to Reproduce---
   lscpumf -c gives a list of available counters, but a few of them are not 
usable: DFLT_ACCESS,DFLT_CYCLES,DFLT_CC,DFLT_CCERROR
  perf list is also not offering these counters.

  A solution will be a backport to 20.04, and tried to made available
  for next SRU , code needed before 06-12.

  Addl Info from Dev:
  I have downloaded the following repository
  https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal
  and checked out branch master-next.

  Both patches appended apply without warning and the compilation showed
  no error.

  For the perf tool:
  e7950166e40271c02 perf vendor events s390: Add new deflate counters for IBM 
z15

  For the s390 kernel
  d68d5d51dc898895b s390/cpum_cf: Add new extended counters for IBM z15

  All accepted for kernel 5.7 rc1

  Please include both patches into Ubuntu 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1881096/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1892070] Re: ip_defrag.sh in net from ubuntu_kernel_selftests ADT failure with focal/linux

[Po-Hsu Lin]

Need to check if this is still failing on B-hwe-5.3, looks like this is
affected.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1892070

Title:
  ip_defrag.sh in net from ubuntu_kernel_selftests ADT failure with
  focal/linux

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Fix Released

Bug description:
  Testing failed on focal/linux 5.4.0-44.48:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux/20200812_171444_31971@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/l/linux/20200812_210509_145fd@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/l/linux/20200812_165855_1dabd@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/l/linux/20200812_153600_9c7cb@/log.gz

  ip_defrag.sh fails with return code 255 without any output. Commenting
  the "set +x" line from the script and running it we get:

  $ sudo bash -x ./ip_defrag.sh
  + set -e
  ++ mktemp -u XX
  + readonly NETNS=ns-2Wn99i
  + NETNS=ns-2Wn99i
  + trap cleanup EXIT
  + setup
  + ip netns add ns-2Wn99i
  + ip -netns ns-2Wn99i link set lo up
  + ip netns exec ns-2Wn99i sysctl -w net.ipv4.ipfrag_high_thresh=900
  + ip netns exec ns-2Wn99i sysctl -w net.ipv4.ipfrag_low_thresh=700
  + ip netns exec ns-2Wn99i sysctl -w net.ipv4.ipfrag_time=1
  + ip netns exec ns-2Wn99i sysctl -w net.ipv6.ip6frag_high_thresh=900
  + ip netns exec ns-2Wn99i sysctl -w net.ipv6.ip6frag_low_thresh=700
  + ip netns exec ns-2Wn99i sysctl -w net.ipv6.ip6frag_time=1
  + ip netns exec ns-2Wn99i sysctl -w 
net.netfilter.nf_conntrack_frag6_high_thresh=900
  + cleanup
  + ip netns del ns-2Wn99i

  Running these manually we get the following error:

  $ sudo ip netns exec ns-2Wn99i sysctl -w 
net.netfilter.nf_conntrack_frag6_high_thresh=900
  sysctl: cannot stat /proc/sys/net/netfilter/nf_conntrack_frag6_high_thresh: 
No such file or directory

  This happens because this step needs the 'nf_defrag_ipv6' module to be
  loaded.

  This has always failed like this with the ADT tests but not always
  with our Regression Tests. I suspect that on Regression Tests there
  might be another testcase that's run before it that loads this module.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1892070/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1881601] Re: Fan excessively runs, even when idle

[Kai-Heng Feng]

Sorry it was off my radar.

Can you please attach `sudo lspci -vvnn`? The lspci attached by apport
doesn't have config space 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/1881601

Title:
  Fan excessively runs, even when idle

Status in linux package in Ubuntu:
  In Progress

Bug description:
  I have a skull canyon NUC as my daily driver and the fan is running
  much higher than it should, even when the machine is completely idle.

  This happened with the 5.3 kernel and also with the 5.4 kernel during
  focal development cycle. It was fixed somewhere along the way prior to
  release but it's back with a vengeance now.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-33-generic 5.4.0-33.37
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dean   4523 F pulseaudio
   /dev/snd/controlC0:  dean   4523 F pulseaudio
   /dev/snd/controlC1:  dean   4523 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun  1 08:37:23 2020
  HibernationDevice: RESUME=UUID=55a42c82-50bf-4e75-a133-dbd3aa93611b
  InstallationDate: Installed on 2018-07-24 (677 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-33-generic N/A
   linux-backports-modules-5.4.0-33-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-01-07 (145 days ago)
  dmi.bios.date: 05/16/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629
  dmi.board.name: NUC6i7KYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H90766-406
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881601/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1890223] Re: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-42-generic

[Kai-Heng Feng]

$ sudo apt install bcmwl-kernel-source

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1890223

Title:
  No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to
  version 5.4.0-42-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I use Ubuntu 20.04 in HP laptop and updated Linux kernel to version 
5.4.0-42-generic after that Wifi Menu can't find on Settings and Wifi Adapter 
cannot detect so I use bluetooth tethering to connect to the internet. I think 
the problem in driver package. I try to install driver with find information 
from many site such as documentation or stackoverflow but still failed. Can you 
help me to resolve this. Thankyou very much and I appreciated for it.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ekoadin   32543 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  IwConfig:
   lono wireless extensions.
   
   bnep0 no wireless extensions.
   
   eno1  no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 002: ID 25a7:fa23 Compx 2.4G Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Notebook
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=aba06a00-074b-4a90-8880-854f890802cf ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 08/18/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.82
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80A3
  dmi.board.vendor: HP
  dmi.board.version: 91.1E
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.82:bd08/18/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A3:rvr91.1E:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion Notebook
  dmi.product.sku: P3V63PA#AR6
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm3067 F pulseaudio
ekoadin6063 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  IwConfig:
   usb0  no wireless extensions.
   
   lono wireless extensions.
   
   eno1  no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 003: ID 04e8:6864 Samsung Electronics Co., Ltd GT-I9070 
(network tethering, USB debugging enabled)
   Bus 001 Device 002: ID 25a7:fa23 Compx 2.4G Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Notebook
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=aba06a00-074b-4a90-8880-854f890802cf ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.3
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  WifiSyslog:
   Sep 01 20:09:09 ekoadin-ubuntu kernel: Lockdown: systemd-logind: hibernation 
is restricted; see man kernel_lockdown.7
   Sep 01 20:09:12 ekoadin-ubuntu kernel: Lockdown: systemd-logind: hibernation 
is restricted; see man kernel_lockdown.7
  _MarkForUpload: True
  dmi.bios.date: 08/18/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.82
  dmi.board.asset.tag: Type2 - 

[Kernel-packages] [Bug 1881367] Re: Ubuntu 20.04 boot hangs when laptop unplugged

[koyakun]

No, it's no longer an issue on 5.4.0-42-generic.
The system boots normally.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1881367

Title:
  Ubuntu 20.04 boot hangs when laptop unplugged

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Dell Latitude 5500 laptop, dual-boot Ubuntu/Windows, Ubuntu 20.04
  64-bit, 5.4.0-33-generic, Ubuntu boot stops with blank screen when the
  laptop is unplugged, even in recovery mode.

  After plugging in power after a failed boot, the following message is shown 
before the splash screen:
  [ 0.468311] Initramfs unpacking failed: Decoding failed
  /dev/nvme-n1p6: clean, 470502/4800512 files, 6138995/1920 blocks

  As long as the laptop is plugged in before selecting Ubuntu in GRUB,
  it will boot, but it never finishes booting if it is unplugged, even
  in recovery mode. It also occurred in Ubuntu 19.10.

  When the boot freezes even in recovery mode, the bug should be
  reported against the kernel according to this page:
  https://wiki.ubuntu.com/Bugs/FindRightPackage#During_boot

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-33-generic 5.4.0-33.37
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tyler  1777 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 30 10:05:26 2020
  InstallationDate: Installed on 2020-02-05 (114 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. Latitude 5500
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=fa5c4fdb-0e37-4ef5-b109-3c129736f66c ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-33-generic N/A
   linux-backports-modules-5.4.0-33-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-05-12 (17 days ago)
  dmi.bios.date: 12/26/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.5
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.5:bd12/26/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881367/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1892070] Re: ip_defrag.sh in net from ubuntu_kernel_selftests ADT failure with focal/linux

[Po-Hsu Lin]

Patch applied in Focal kernel
625247c91d94 ("selftests: net: ip_defrag: modprobe missing nf_defrag_ipv6 
support")
$ git tag --contain 625247c91d9453d24ff035ee5bfcf34375208782
Ubuntu-5.4.0-46.50


** Changed in: linux (Ubuntu Focal)
   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/1892070

Title:
  ip_defrag.sh in net from ubuntu_kernel_selftests ADT failure with
  focal/linux

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Fix Released

Bug description:
  Testing failed on focal/linux 5.4.0-44.48:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux/20200812_171444_31971@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/l/linux/20200812_210509_145fd@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/l/linux/20200812_165855_1dabd@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/l/linux/20200812_153600_9c7cb@/log.gz

  ip_defrag.sh fails with return code 255 without any output. Commenting
  the "set +x" line from the script and running it we get:

  $ sudo bash -x ./ip_defrag.sh
  + set -e
  ++ mktemp -u XX
  + readonly NETNS=ns-2Wn99i
  + NETNS=ns-2Wn99i
  + trap cleanup EXIT
  + setup
  + ip netns add ns-2Wn99i
  + ip -netns ns-2Wn99i link set lo up
  + ip netns exec ns-2Wn99i sysctl -w net.ipv4.ipfrag_high_thresh=900
  + ip netns exec ns-2Wn99i sysctl -w net.ipv4.ipfrag_low_thresh=700
  + ip netns exec ns-2Wn99i sysctl -w net.ipv4.ipfrag_time=1
  + ip netns exec ns-2Wn99i sysctl -w net.ipv6.ip6frag_high_thresh=900
  + ip netns exec ns-2Wn99i sysctl -w net.ipv6.ip6frag_low_thresh=700
  + ip netns exec ns-2Wn99i sysctl -w net.ipv6.ip6frag_time=1
  + ip netns exec ns-2Wn99i sysctl -w 
net.netfilter.nf_conntrack_frag6_high_thresh=900
  + cleanup
  + ip netns del ns-2Wn99i

  Running these manually we get the following error:

  $ sudo ip netns exec ns-2Wn99i sysctl -w 
net.netfilter.nf_conntrack_frag6_high_thresh=900
  sysctl: cannot stat /proc/sys/net/netfilter/nf_conntrack_frag6_high_thresh: 
No such file or directory

  This happens because this step needs the 'nf_defrag_ipv6' module to be
  loaded.

  This has always failed like this with the ADT tests but not always
  with our Regression Tests. I suspect that on Regression Tests there
  might be another testcase that's run before it that loads this module.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1892070/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1893795] Re: [Ubuntu 20.04.1 LTS] Backlight brightness can't be changed, even in /sys/

[Kai-Heng Feng]

** Package changed: linux (Ubuntu) => nvidia-graphics-drivers (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1893795

Title:
  [Ubuntu 20.04.1 LTS] Backlight brightness can't be changed, even in
  /sys/

Status in nvidia-graphics-drivers package in Ubuntu:
  Confirmed

Bug description:
  None of the boot parameters worked, but with acpi_backlight=vendor the
  backlight was dimmer (systemd-backlight didn't fail). The only way it
  starts working is to do "setpci -v -H1 -s 00:01.00 BRIDGE_CONTROL=0"

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-45-generic 5.4.0-45.49
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Uname: Linux 5.4.0-45-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  xma1345 F pulseaudio
   /dev/snd/controlC0:  xma1345 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  1 14:36:14 2020
  InstallationDate: Installed on 2020-08-30 (1 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Apple Inc. MacBookPro11,3
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=01482a85-82e8-44ce-a63d-a429cd6d5381 ro acpi_osi=
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-45-generic N/A
   linux-backports-modules-5.4.0-45-generic  N/A
   linux-firmware1.187.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/10/2020
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 162.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-2BD1B31983FE1663
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,3
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-2BD1B31983FE1663
  dmi.modalias: 
dmi:bvnAppleInc.:bvr162.0.0.0.0:bd06/10/2020:svnAppleInc.:pnMacBookPro11,3:pvr1.0:rvnAppleInc.:rnMac-2BD1B31983FE1663:rvrMacBookPro11,3:cvnAppleInc.:ct10:cvrMac-2BD1B31983FE1663:
  dmi.product.family: Mac
  dmi.product.name: MacBookPro11,3
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1893795/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1893984] Re: Wayland is still unstable with ubuntu 20.04

[Kai-Heng Feng]

** Package changed: linux (Ubuntu) => gnome-shell (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1893984

Title:
  Wayland is still unstable with ubuntu 20.04

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Wayland is running almost smoothly on Ubuntu 20.04,however there are some 
small issues that should be addressed.
  .the run command (ALT+F2) is not working correctly ...For example "r" for 
restarting the gnome-shell doesn't work.

  .my computer froze on a wayland session

  .geometry specified in the .config for apps like Mpv are ignored in
  wayland sessions

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-45-generic 5.4.0-45.49
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Uname: Linux 5.4.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  regern 1436 F pulseaudio
   /dev/snd/pcmC0D0p:   regern 1436 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  2 21:06:01 2020
  InstallationDate: Installed on 2020-05-16 (109 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. Inspiron 15-3552
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=55652357-023b-4633-8d3a-46ce1a22d378 ro transparent_hugepage=never 
quiet splash DEEPIN_GFXMODE= vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-45-generic N/A
   linux-backports-modules-5.4.0-45-generic  N/A
   linux-firmware1.187.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/06/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 4.4.0
  dmi.board.name: 079W3P
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr4.4.0:bd03/06/2018:svnDellInc.:pnInspiron15-3552:pvr4.4.0:rvnDellInc.:rn079W3P:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3552
  dmi.product.sku: 06AC
  dmi.product.version: 4.4.0
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893984/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1885118] Re: Lenovo Thinkbook 15-IIL and 14-IIL touchpad not found

[Kai-Heng Feng]

*** This bug is a duplicate of bug 1853277 ***
https://bugs.launchpad.net/bugs/1853277

** This bug has been marked a duplicate of bug 1853277
   Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/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/1885118

Title:
  Lenovo Thinkbook 15-IIL and 14-IIL touchpad not found

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Greetings,
  tried 3 different distros nothing seemd to work, also tried at lest 5 boot 
parameters and some other hacks that worked on 14-IML for example but nothing 
worked.

  Only driver that's missing is touchpad and it's not even showing in
  the list.

  Current distro: Ubuntu, tried on manjaro and kali

  Kernel version: 5.7.1-050701-generic

  Xinput log:
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ USB Gaming Mouseid=9[slave  pointer 
 (2)]
  ⎜   ↳ USB Gaming Mouse Consumer Control   id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ USB Gaming Mouseid=10   [slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=12   [slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=13   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=14   [slave  
keyboard (3)]
  ↳ USB Gaming Mouse Consumer Control   id=15   [slave  
keyboard (3)]

  Also cat /proc/bus/input/devices shows everything except touchpad.

  If you need any more info please let me know, I bought this laptop for linux 
only and it's really annoying when you cant use touchpad.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  almir   879 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-06-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20SM
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=b236fe34-8dda-44ae-ad12-6af861ad21d7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/15/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN17WW
  dmi.board.name: LVAC/LVAD
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 15-IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN17WW:bd04/15/2020:svnLENOVO:pn20SM:pvrLenovoThinkBook15-IIL:rvnLENOVO:rnLVAC/LVAD:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook15-IIL:
  dmi.product.family: Thinkbook 15-IIL
  dmi.product.name: 20SM
  dmi.product.sku: LENOVO_MT_20SM_BU_idea_FM_Thinkbook 15-IIL
  dmi.product.version: Lenovo ThinkBook 15-IIL
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885118/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1881367] Re: Ubuntu 20.04 boot hangs when laptop unplugged

[Kai-Heng Feng]

** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/1881367

Title:
  Ubuntu 20.04 boot hangs when laptop unplugged

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  On Dell Latitude 5500 laptop, dual-boot Ubuntu/Windows, Ubuntu 20.04
  64-bit, 5.4.0-33-generic, Ubuntu boot stops with blank screen when the
  laptop is unplugged, even in recovery mode.

  After plugging in power after a failed boot, the following message is shown 
before the splash screen:
  [ 0.468311] Initramfs unpacking failed: Decoding failed
  /dev/nvme-n1p6: clean, 470502/4800512 files, 6138995/1920 blocks

  As long as the laptop is plugged in before selecting Ubuntu in GRUB,
  it will boot, but it never finishes booting if it is unplugged, even
  in recovery mode. It also occurred in Ubuntu 19.10.

  When the boot freezes even in recovery mode, the bug should be
  reported against the kernel according to this page:
  https://wiki.ubuntu.com/Bugs/FindRightPackage#During_boot

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-33-generic 5.4.0-33.37
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tyler  1777 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 30 10:05:26 2020
  InstallationDate: Installed on 2020-02-05 (114 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. Latitude 5500
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=fa5c4fdb-0e37-4ef5-b109-3c129736f66c ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-33-generic N/A
   linux-backports-modules-5.4.0-33-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-05-12 (17 days ago)
  dmi.bios.date: 12/26/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.5
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.5:bd12/26/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881367/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1893914] Re: [SRU] [Focal/OEM-5.6/Groovy]Fix AMD usb host controller lost after stress S3

[AaronMa]

** Tags added: oem-priority originate-from-1886754 sutton

** Also affects: linux (Ubuntu Groovy)
   Importance: Undecided
   Status: Incomplete

** Also affects: linux-oem-5.6 (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-5.6 (Ubuntu Focal)
   Importance: Undecided
   Status: New

** No longer affects: linux-oem-5.6 (Ubuntu Groovy)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1893914

Title:
  [SRU] [Focal/OEM-5.6/Groovy]Fix AMD usb host controller lost after
  stress S3

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.6 package in Ubuntu:
  New
Status in linux source package in Focal:
  New
Status in linux-oem-5.6 source package in Focal:
  New
Status in linux source package in Groovy:
  Incomplete

Bug description:
  [Impact]
  When stress S3 on AMD 0x15e5 usb host controller, it failed to resume.
  The controller indicates "internal Host Controller Error"

  [Fix]
  To fix this, sparse controller enable bit has to be disabled.

  [Test Case]
  Verified on the target platform, OK for  100 times of S3.

  [Regression Potential]
  Low,
  Add specific ID quirk for hw, no other hw related, tested with positive 
results.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1893914/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 329466] Re: No support for triple head configurations in Kubuntu

[Daniel Letzeisen]

** Changed in: nvidia-common (Ubuntu)
 Assignee: Badum (nvidia) => (unassigned)

** Changed in: nvidia-common (Ubuntu)
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-common in Ubuntu.
https://bugs.launchpad.net/bugs/329466

Title:
  No support for triple head configurations in Kubuntu

Status in nvidia-common package in Ubuntu:
  Invalid

Bug description:
  I have an extremely nice setup, 2x22" and 1x26" screens and an Nvidia
  card with 3 outpus. However I can use only 2 them at a time because
  kwin/plasma do not seem to support more than 2 heads.

  jussi@galaxy:~$ lsb_release -rd
  Description:Ubuntu jaunty (development branch)
  Release:9.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-common/+bug/329466/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

[neoglez]

This happens to me every week on Ubuntu 16.04. LTS with kernel
4.15.0-112-generic. It seems to be  a random complete system freeze. The
mouse does not respond, caps lock and numlock do not change light on
keyboard, ctrl alt f2/f3/etc does not work, and even Alt + SysRq REISUB
does not respond. Only a hard reset works by pressing the power button
will reboot the system.

I noticed I could reproduce the bug easily by watching videos and/or
reading news on "heavy" newspaper websites in Firefox. In contrast, in
Chrome I rarely experience the issue.

>From what I have read, and since I have a GeForce GTX graphic card with
original NVIDIA drivers installed, I suspect that the problem is
strongly related to these three components: video encoder/decoder,
browser and graphic card/drivers.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1798961

Title:
  Random unrecoverable freezes on Ubuntu 18.10

Status in Linux:
  New
Status in linux package in Ubuntu:
  Won't Fix
Status in xserver-xorg-video-intel package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Won't Fix
Status in xserver-xorg-video-intel source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  Won't Fix
Status in xserver-xorg-video-intel source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  Won't Fix
Status in xserver-xorg-video-intel source package in Disco:
  Invalid

Bug description:
  First thing I notice is that the mouse cursor freezes as I'm using it,
  then I hit the CAPS LOCK key and the LED indicator doesn't respond.
  Then I try the "REISUB" command, but it doesn't do anything either.
  Only a hard reset works, pressing down the power button for a few
  seconds.

  How to reproduce?
  I couldn't figure out a consistent method. It is still random to me.

  Version: Ubuntu 4.18.0-10.11-generic 4.18.12
  System information attached.

  Also happens under Arch Linux and Fedora.
  I've talked to another user on IRC who seems to be having the same freezes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsilva 1213 F pulseaudio
   /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.sku: Inspiron 5458
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1798961/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1893774] Re: [amdgpu] Screen freeze when loging in after a log out

[snow]

also not working. even with root I get some errors like not sufficient
rights. I attach the file here. I you are afraid you can delete it.

** Attachment added: "_usr_bin_kglobalaccel5.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1893774/+attachment/5407349/+files/_usr_bin_kglobalaccel5.1000.crash

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1893774

Title:
  [amdgpu] Screen freeze when loging in after a log out

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Incomplete

Bug description:
  I use Kubuntu 20.04.1 on Thinpad T495 with encrypted disk (LVMS) and
  finger print reader.

  PROBLEM:
  1. I boot the laptop and can work
  2. I log my user out and try to log in again with te password
  3. I enter the password and press enter
  4. The screen freezes and shows the login screen. It can only be killed and 
rebooted. 

  Also, the finger print reader works everywhere, but not in the
  situation above. These are the seetings of my common-auth file:

  # here are the per-package modules (the "Primary" block)
  auth  [success=2 default=ignore]  pam_fprintd.so max_tries=1 timeout=10 # 
debug
  auth  [success=1 default=ignore]  pam_unix.so nullok_secure try_first_pass

  But I do NOT think that the problem is related to the fingerprint
  reader.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Uname: Linux 5.4.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Tue Sep  1 13:38:09 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev d2) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Picasso [17aa:5125]
  InstallationDate: Installed on 2020-08-31 (0 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  MachineType: LENOVO 20NKS01Y00
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-45-generic 
root=/dev/mapper/vgkubuntu-root ro quiet splash iommu=soft vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R12ET50W(1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NKS01Y00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR12ET50W(1.20):bd02/19/2020:svnLENOVO:pn20NKS01Y00:pvrThinkPadT495:rvnLENOVO:rn20NKS01Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T495
  dmi.product.name: 20NKS01Y00
  dmi.product.sku: LENOVO_MT_20NK_BU_Think_FM_ThinkPad T495
  dmi.product.version: ThinkPad T495
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 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/1893774/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1894062] [NEW] Remove duplicated code in ip_defrag.sh of kselftests/net

[Po-Hsu Lin]

Public bug reported:

== SRU Justification ==
In Groovy, patch 6c6ab1256 "UBUNTU: SAUCE: selftests: net: ip_defrag: modprobe 
missing nf_defrag_ipv6 support" has been applied again with commit aba69d49

Therefore there are two lines with:
modprobe -q nf_defrag_ipv6

== Fix ==
Revert the SAUCE patch can correct this, and it matches the code in upstream.

== Regression Potential ==
Low, change limited to testing tools and it's only remove the duplicated code.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Po-Hsu Lin (cypressyew)
 Status: In Progress

** Affects: linux (Ubuntu Groovy)
 Importance: Undecided
 Assignee: Po-Hsu Lin (cypressyew)
 Status: In Progress

** Also affects: linux (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Groovy)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: linux (Ubuntu Groovy)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894062

Title:
  Remove duplicated code in ip_defrag.sh of kselftests/net

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Groovy:
  In Progress

Bug description:
  == SRU Justification ==
  In Groovy, patch 6c6ab1256 "UBUNTU: SAUCE: selftests: net: ip_defrag: 
modprobe missing nf_defrag_ipv6 support" has been applied again with commit 
aba69d49

  Therefore there are two lines with:
  modprobe -q nf_defrag_ipv6

  == Fix ==
  Revert the SAUCE patch can correct this, and it matches the code in upstream.

  == Regression Potential ==
  Low, change limited to testing tools and it's only remove the duplicated code.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894062/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1894062] Re: Remove duplicated code in ip_defrag.sh of kselftests/net

[Po-Hsu Lin]

** Tags added: groovy

** Description changed:

  == SRU Justification ==
- In Groovy, patch 6c6ab1256 "UBUNTU: SAUCE: selftests: net: ip_defrag: 
modprobe missing nf_defrag_ipv6 support" has been applied again with commit 
aba69d49
+ In Groovy, patch 6c6ab1256 "UBUNTU: SAUCE: selftests: net: ip_defrag:
+ modprobe missing nf_defrag_ipv6 support" has been applied again with
+ commit aba69d49
  
  Therefore there are two lines with:
  modprobe -q nf_defrag_ipv6
  
  == Fix ==
- Revert the SAUCE patch can correct this, and it matches the code in upstream.
+ Revert the SAUCE patch can correct this, and it can make our code
+ matches with the one upstream.
  
  == Regression Potential ==
- Low, change limited to testing tools and it's only remove the duplicated code.
+ Low, change limited to testing tools and it's only removing the
+ duplicated code.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894062

Title:
  Remove duplicated code in ip_defrag.sh of kselftests/net

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Groovy:
  In Progress

Bug description:
  == SRU Justification ==
  In Groovy, patch 6c6ab1256 "UBUNTU: SAUCE: selftests: net: ip_defrag:
  modprobe missing nf_defrag_ipv6 support" has been applied again with
  commit aba69d49

  Therefore there are two lines with:
  modprobe -q nf_defrag_ipv6

  == Fix ==
  Revert the SAUCE patch can correct this, and it can make our code
  matches with the one upstream.

  == Regression Potential ==
  Low, change limited to testing tools and it's only removing the
  duplicated code.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894062/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1893778] Re: [UBUNTU 20.04] zPCI device hot-plug during boot may result in unusable device

[Frank Heimes]

While working on this SRU a set of patched kernel packages was created that 
were now made available here for further testing:
https://people.canonical.com/~fheimes/lp1893778/

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1893778

Title:
  [UBUNTU 20.04] zPCI device hot-plug during boot may result in unusable
  device

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  New
Status in linux source package in Groovy:
  Fix Released

Bug description:
  When a PCI device (including virtio-pci for which this is easiest to test)
  is hot-plugged while Linux is still booting, it can be detected as
  an entry in CLP List PCI Functions (basically equivalent to boot time probing
  on other architectures) and with the hot-plug event.
  In this case the hot-plug event will be stale but Linux still
  tried to add and enable the device leading

  a) to a duplicate entry in zPCI internal device list 
  b) an attempt to enable the device witha stale function handle

  Part b) would lead to the device being place in the error state
  and make it unusable.

  This can most easily be reproduced using KVM and doing

  # sudo virsh start myguest && sudo virsh attach-device myguest
  hotplug_pci_block.xml

  Where hotplug_pci_block.xml looks like the following:

  
  
  
  
  
  
  
  

  
  The problem is fixed with the 3-line upstream commit

  b76fee1bc56c31a9d2a49592810eba30cc06d61a s390/pci: ignore stale
  configuration request event

  I also confirmed that as of the focal tag Ubuntu-5.4.0-46.50 this
  cherry-picks cleanly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1893778/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1893774] Re: [amdgpu] Screen freeze when loging in after a log out

[Daniel van Vugt]

Try using 'apport-cli' in place of 'ubuntu-bug'.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1893774

Title:
  [amdgpu] Screen freeze when loging in after a log out

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Incomplete

Bug description:
  I use Kubuntu 20.04.1 on Thinpad T495 with encrypted disk (LVMS) and
  finger print reader.

  PROBLEM:
  1. I boot the laptop and can work
  2. I log my user out and try to log in again with te password
  3. I enter the password and press enter
  4. The screen freezes and shows the login screen. It can only be killed and 
rebooted. 

  Also, the finger print reader works everywhere, but not in the
  situation above. These are the seetings of my common-auth file:

  # here are the per-package modules (the "Primary" block)
  auth  [success=2 default=ignore]  pam_fprintd.so max_tries=1 timeout=10 # 
debug
  auth  [success=1 default=ignore]  pam_unix.so nullok_secure try_first_pass

  But I do NOT think that the problem is related to the fingerprint
  reader.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Uname: Linux 5.4.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Tue Sep  1 13:38:09 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev d2) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Picasso [17aa:5125]
  InstallationDate: Installed on 2020-08-31 (0 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  MachineType: LENOVO 20NKS01Y00
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-45-generic 
root=/dev/mapper/vgkubuntu-root ro quiet splash iommu=soft vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R12ET50W(1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NKS01Y00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR12ET50W(1.20):bd02/19/2020:svnLENOVO:pn20NKS01Y00:pvrThinkPadT495:rvnLENOVO:rn20NKS01Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T495
  dmi.product.name: 20NKS01Y00
  dmi.product.sku: LENOVO_MT_20NK_BU_Think_FM_ThinkPad T495
  dmi.product.version: ThinkPad T495
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 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/1893774/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1893914] Re: [SRU] [Focal/OEM-5.6/Groovy]Fix AMD usb host controller lost after stress S3

[AaronMa]

** Changed in: linux (Ubuntu Groovy)
   Status: Incomplete => In Progress

** Changed in: linux (Ubuntu Focal)
   Status: New => In Progress

** Changed in: hwe-next
   Status: New => In Progress

** Changed in: linux-oem-5.6 (Ubuntu)
   Status: New => In Progress

** Changed in: linux-oem-5.6 (Ubuntu Focal)
   Status: New => In Progress

** Changed in: linux (Ubuntu Focal)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Groovy)
   Importance: Undecided => Medium

** Changed in: linux-oem-5.6 (Ubuntu)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Groovy)
   Importance: Medium => High

** Changed in: linux (Ubuntu Focal)
   Importance: Medium => High

** Changed in: linux-oem-5.6 (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: hwe-next
   Importance: Undecided => High

-- 
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/1893914

Title:
  [SRU] [Focal/OEM-5.6/Groovy]Fix AMD usb host controller lost after
  stress S3

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.6 package in Ubuntu:
  In Progress
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

Bug description:
  [Impact]
  When stress S3 on AMD 0x15e5 usb host controller, it failed to resume.
  The controller indicates "internal Host Controller Error"

  [Fix]
  To fix this, sparse controller enable bit has to be disabled.

  [Test Case]
  Verified on the target platform, OK for  100 times of S3.

  [Regression Potential]
  Low,
  Add specific ID quirk for hw, no other hw related, tested with positive 
results.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1893914/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1847105] Re: very slow disk creation, snapshotting

[Christian Ehrhardt ]

Got one Reviewed-by, lets 6.7.0 is released so it is not Frozen atm.
Giving it another day before pushing it.

-- 
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/1847105

Title:
  very slow disk creation, snapshotting

Status in virt-manager:
  Fix Released
Status in Native ZFS for Linux:
  New
Status in libvirt package in Ubuntu:
  Triaged
Status in virt-manager package in Ubuntu:
  Triaged
Status in zfs-linux package in Ubuntu:
  New
Status in libvirt source package in Bionic:
  Invalid
Status in virt-manager source package in Bionic:
  Invalid
Status in zfs-linux source package in Bionic:
  Won't Fix
Status in libvirt source package in Disco:
  Won't Fix
Status in virt-manager source package in Disco:
  Won't Fix
Status in zfs-linux source package in Disco:
  Won't Fix
Status in libvirt source package in Focal:
  Triaged
Status in libvirt source package in Groovy:
  Triaged

Bug description:
  This is a regression in eoan for me. I use virt-manager to create vms,
  and I noticed that creating one now takes more than a minute.

  Looking at the process listing while the backing disk is being created, I see 
this qemu-img command line:
  15658 ?Ssl0:00 /usr/sbin/libvirtd
  23726 ?Sl 0:04  \_ /usr/bin/qemu-img create -f qcow2 -o 
preallocation=falloc,compat=1.1,lazy_refcounts 
/var/lib/libvirt/images/live-server.qcow2 41943040K

  If I run qemu-img with that preallocation parameter set, even on
  bionic, then it also takes a very long time.

  On eoan, for comparison:
  andreas@nsn7:~$ time qemu-img create -f qcow2 no-prealloc-image.qcow2 40G
  Formatting 'no-prealloc-image.qcow2', fmt=qcow2 size=42949672960 
cluster_size=65536 lazy_refcounts=off refcount_bits=16

  real  0m0,016s
  user  0m0,010s
  sys   0m0,006s
  andreas@nsn7:~$ qemu-img info no-prealloc-image.qcow2 
  image: no-prealloc-image.qcow2
  file format: qcow2
  virtual size: 40G (42949672960 bytes)
  disk size: 17K
  cluster_size: 65536
  Format specific information:
  compat: 1.1
  lazy refcounts: false
  refcount bits: 16
  corrupt: false
  andreas@nsn7:~$ du -hs no-prealloc-image.qcow2 
  17K   no-prealloc-image.qcow2
  andreas@nsn7:~$ 

  
  and now with preallocation=falloc:
  andreas@nsn7:~$ time qemu-img create -f qcow2 -o preallocation=falloc 
with-prealloc-image.qcow2 40G
  Formatting 'with-prealloc-image.qcow2', fmt=qcow2 size=42949672960 
cluster_size=65536 preallocation=falloc lazy_refcounts=off refcount_bits=16

  real  1m43,196s
  user  0m3,564s
  sys   1m26,720s
  andreas@nsn7:~$ qemu-img info with-prealloc-image.qcow2 
  image: with-prealloc-image.qcow2
  file format: qcow2
  virtual size: 40G (42949672960 bytes)
  disk size: 2.7M
  cluster_size: 65536
  Format specific information:
  compat: 1.1
  lazy refcounts: false
  refcount bits: 16
  corrupt: false
  andreas@nsn7:~$ du -hs with-prealloc-image.qcow2 
  2,8M  with-prealloc-image.qcow2
  andreas@nsn7:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: libvirt-daemon 5.4.0-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Mon Oct  7 11:36:03 2019
  InstallationDate: Installed on 2019-10-07 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191006)
  SourcePackage: libvirt
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.libvirt.nwfilter.allow-arp.xml: [inaccessible: [Errno 
13] Permission denied: '/etc/libvirt/nwfilter/allow-arp.xml']
  modified.conffile..etc.libvirt.nwfilter.allow-dhcp-server.xml: [inaccessible: 
[Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp-server.xml']
  modified.conffile..etc.libvirt.nwfilter.allow-dhcp.xml: [inaccessible: [Errno 
13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp.xml']
  modified.conffile..etc.libvirt.nwfilter.allow-incoming-ipv4.xml: 
[inaccessible: [Errno 13] Permission denied: 
'/etc/libvirt/nwfilter/allow-incoming-ipv4.xml']
  modified.conffile..etc.libvirt.nwfilter.allow-ipv4.xml: [inaccessible: [Errno 
13] Permission denied: '/etc/libvirt/nwfilter/allow-ipv4.xml']
  modified.conffile..etc.libvirt.nwfilter.clean-traffic-gateway.xml: 
[inaccessible: [Errno 13] Permission denied: 
'/etc/libvirt/nwfilter/clean-traffic-gateway.xml']
  modified.conffile..etc.libvirt.nwfilter.clean-traffic.xml: [inaccessible: 
[Errno 13] Permission denied: '/etc/libvirt/nwfilter/clean-traffic.xml']
  modified.conffile..etc.libvirt.nwfilter.no-arp-ip-spoofing.xml: 
[inaccessible: [Errno 13] Permission denied: 
'/etc/libvirt/nwfilter/no-arp-ip-spoofing.xml']
  modified.conffile..etc.libvirt.nwfilter.no-arp-mac-spoofing.xml: 
[inaccessible: [Errno 13] Permission denied: 

[Kernel-packages] [Bug 1847105] Re: very slow disk creation, snapshotting

[Christian Ehrhardt ]

grmls/, lets/and/

-- 
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/1847105

Title:
  very slow disk creation, snapshotting

Status in virt-manager:
  Fix Released
Status in Native ZFS for Linux:
  New
Status in libvirt package in Ubuntu:
  Triaged
Status in virt-manager package in Ubuntu:
  Triaged
Status in zfs-linux package in Ubuntu:
  New
Status in libvirt source package in Bionic:
  Invalid
Status in virt-manager source package in Bionic:
  Invalid
Status in zfs-linux source package in Bionic:
  Won't Fix
Status in libvirt source package in Disco:
  Won't Fix
Status in virt-manager source package in Disco:
  Won't Fix
Status in zfs-linux source package in Disco:
  Won't Fix
Status in libvirt source package in Focal:
  Triaged
Status in libvirt source package in Groovy:
  Triaged

Bug description:
  This is a regression in eoan for me. I use virt-manager to create vms,
  and I noticed that creating one now takes more than a minute.

  Looking at the process listing while the backing disk is being created, I see 
this qemu-img command line:
  15658 ?Ssl0:00 /usr/sbin/libvirtd
  23726 ?Sl 0:04  \_ /usr/bin/qemu-img create -f qcow2 -o 
preallocation=falloc,compat=1.1,lazy_refcounts 
/var/lib/libvirt/images/live-server.qcow2 41943040K

  If I run qemu-img with that preallocation parameter set, even on
  bionic, then it also takes a very long time.

  On eoan, for comparison:
  andreas@nsn7:~$ time qemu-img create -f qcow2 no-prealloc-image.qcow2 40G
  Formatting 'no-prealloc-image.qcow2', fmt=qcow2 size=42949672960 
cluster_size=65536 lazy_refcounts=off refcount_bits=16

  real  0m0,016s
  user  0m0,010s
  sys   0m0,006s
  andreas@nsn7:~$ qemu-img info no-prealloc-image.qcow2 
  image: no-prealloc-image.qcow2
  file format: qcow2
  virtual size: 40G (42949672960 bytes)
  disk size: 17K
  cluster_size: 65536
  Format specific information:
  compat: 1.1
  lazy refcounts: false
  refcount bits: 16
  corrupt: false
  andreas@nsn7:~$ du -hs no-prealloc-image.qcow2 
  17K   no-prealloc-image.qcow2
  andreas@nsn7:~$ 

  
  and now with preallocation=falloc:
  andreas@nsn7:~$ time qemu-img create -f qcow2 -o preallocation=falloc 
with-prealloc-image.qcow2 40G
  Formatting 'with-prealloc-image.qcow2', fmt=qcow2 size=42949672960 
cluster_size=65536 preallocation=falloc lazy_refcounts=off refcount_bits=16

  real  1m43,196s
  user  0m3,564s
  sys   1m26,720s
  andreas@nsn7:~$ qemu-img info with-prealloc-image.qcow2 
  image: with-prealloc-image.qcow2
  file format: qcow2
  virtual size: 40G (42949672960 bytes)
  disk size: 2.7M
  cluster_size: 65536
  Format specific information:
  compat: 1.1
  lazy refcounts: false
  refcount bits: 16
  corrupt: false
  andreas@nsn7:~$ du -hs with-prealloc-image.qcow2 
  2,8M  with-prealloc-image.qcow2
  andreas@nsn7:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: libvirt-daemon 5.4.0-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Mon Oct  7 11:36:03 2019
  InstallationDate: Installed on 2019-10-07 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191006)
  SourcePackage: libvirt
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.libvirt.nwfilter.allow-arp.xml: [inaccessible: [Errno 
13] Permission denied: '/etc/libvirt/nwfilter/allow-arp.xml']
  modified.conffile..etc.libvirt.nwfilter.allow-dhcp-server.xml: [inaccessible: 
[Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp-server.xml']
  modified.conffile..etc.libvirt.nwfilter.allow-dhcp.xml: [inaccessible: [Errno 
13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp.xml']
  modified.conffile..etc.libvirt.nwfilter.allow-incoming-ipv4.xml: 
[inaccessible: [Errno 13] Permission denied: 
'/etc/libvirt/nwfilter/allow-incoming-ipv4.xml']
  modified.conffile..etc.libvirt.nwfilter.allow-ipv4.xml: [inaccessible: [Errno 
13] Permission denied: '/etc/libvirt/nwfilter/allow-ipv4.xml']
  modified.conffile..etc.libvirt.nwfilter.clean-traffic-gateway.xml: 
[inaccessible: [Errno 13] Permission denied: 
'/etc/libvirt/nwfilter/clean-traffic-gateway.xml']
  modified.conffile..etc.libvirt.nwfilter.clean-traffic.xml: [inaccessible: 
[Errno 13] Permission denied: '/etc/libvirt/nwfilter/clean-traffic.xml']
  modified.conffile..etc.libvirt.nwfilter.no-arp-ip-spoofing.xml: 
[inaccessible: [Errno 13] Permission denied: 
'/etc/libvirt/nwfilter/no-arp-ip-spoofing.xml']
  modified.conffile..etc.libvirt.nwfilter.no-arp-mac-spoofing.xml: 
[inaccessible: [Errno 13] Permission denied: 
'/etc/libvirt/nwfilter/no-arp-mac-spoofing.xml']
  modified.conffile..etc.libvirt.nwfilter.no-arp-spoofing.xml: [inaccessible: 

[Kernel-packages] [Bug 1847105] Re: very slow disk creation, snapshotting

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~paelzer/ubuntu/+source/libvirt/+git/libvirt/+merge/390220

-- 
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/1847105

Title:
  very slow disk creation, snapshotting

Status in virt-manager:
  Fix Released
Status in Native ZFS for Linux:
  New
Status in libvirt package in Ubuntu:
  Triaged
Status in virt-manager package in Ubuntu:
  Triaged
Status in zfs-linux package in Ubuntu:
  New
Status in libvirt source package in Bionic:
  Invalid
Status in virt-manager source package in Bionic:
  Invalid
Status in zfs-linux source package in Bionic:
  Won't Fix
Status in libvirt source package in Disco:
  Won't Fix
Status in virt-manager source package in Disco:
  Won't Fix
Status in zfs-linux source package in Disco:
  Won't Fix
Status in libvirt source package in Focal:
  Triaged
Status in libvirt source package in Groovy:
  Triaged

Bug description:
  This is a regression in eoan for me. I use virt-manager to create vms,
  and I noticed that creating one now takes more than a minute.

  Looking at the process listing while the backing disk is being created, I see 
this qemu-img command line:
  15658 ?Ssl0:00 /usr/sbin/libvirtd
  23726 ?Sl 0:04  \_ /usr/bin/qemu-img create -f qcow2 -o 
preallocation=falloc,compat=1.1,lazy_refcounts 
/var/lib/libvirt/images/live-server.qcow2 41943040K

  If I run qemu-img with that preallocation parameter set, even on
  bionic, then it also takes a very long time.

  On eoan, for comparison:
  andreas@nsn7:~$ time qemu-img create -f qcow2 no-prealloc-image.qcow2 40G
  Formatting 'no-prealloc-image.qcow2', fmt=qcow2 size=42949672960 
cluster_size=65536 lazy_refcounts=off refcount_bits=16

  real  0m0,016s
  user  0m0,010s
  sys   0m0,006s
  andreas@nsn7:~$ qemu-img info no-prealloc-image.qcow2 
  image: no-prealloc-image.qcow2
  file format: qcow2
  virtual size: 40G (42949672960 bytes)
  disk size: 17K
  cluster_size: 65536
  Format specific information:
  compat: 1.1
  lazy refcounts: false
  refcount bits: 16
  corrupt: false
  andreas@nsn7:~$ du -hs no-prealloc-image.qcow2 
  17K   no-prealloc-image.qcow2
  andreas@nsn7:~$ 

  
  and now with preallocation=falloc:
  andreas@nsn7:~$ time qemu-img create -f qcow2 -o preallocation=falloc 
with-prealloc-image.qcow2 40G
  Formatting 'with-prealloc-image.qcow2', fmt=qcow2 size=42949672960 
cluster_size=65536 preallocation=falloc lazy_refcounts=off refcount_bits=16

  real  1m43,196s
  user  0m3,564s
  sys   1m26,720s
  andreas@nsn7:~$ qemu-img info with-prealloc-image.qcow2 
  image: with-prealloc-image.qcow2
  file format: qcow2
  virtual size: 40G (42949672960 bytes)
  disk size: 2.7M
  cluster_size: 65536
  Format specific information:
  compat: 1.1
  lazy refcounts: false
  refcount bits: 16
  corrupt: false
  andreas@nsn7:~$ du -hs with-prealloc-image.qcow2 
  2,8M  with-prealloc-image.qcow2
  andreas@nsn7:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: libvirt-daemon 5.4.0-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Mon Oct  7 11:36:03 2019
  InstallationDate: Installed on 2019-10-07 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191006)
  SourcePackage: libvirt
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.libvirt.nwfilter.allow-arp.xml: [inaccessible: [Errno 
13] Permission denied: '/etc/libvirt/nwfilter/allow-arp.xml']
  modified.conffile..etc.libvirt.nwfilter.allow-dhcp-server.xml: [inaccessible: 
[Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp-server.xml']
  modified.conffile..etc.libvirt.nwfilter.allow-dhcp.xml: [inaccessible: [Errno 
13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp.xml']
  modified.conffile..etc.libvirt.nwfilter.allow-incoming-ipv4.xml: 
[inaccessible: [Errno 13] Permission denied: 
'/etc/libvirt/nwfilter/allow-incoming-ipv4.xml']
  modified.conffile..etc.libvirt.nwfilter.allow-ipv4.xml: [inaccessible: [Errno 
13] Permission denied: '/etc/libvirt/nwfilter/allow-ipv4.xml']
  modified.conffile..etc.libvirt.nwfilter.clean-traffic-gateway.xml: 
[inaccessible: [Errno 13] Permission denied: 
'/etc/libvirt/nwfilter/clean-traffic-gateway.xml']
  modified.conffile..etc.libvirt.nwfilter.clean-traffic.xml: [inaccessible: 
[Errno 13] Permission denied: '/etc/libvirt/nwfilter/clean-traffic.xml']
  modified.conffile..etc.libvirt.nwfilter.no-arp-ip-spoofing.xml: 
[inaccessible: [Errno 13] Permission denied: 
'/etc/libvirt/nwfilter/no-arp-ip-spoofing.xml']
  modified.conffile..etc.libvirt.nwfilter.no-arp-mac-spoofing.xml: 
[inaccessible: [Errno 13] Permission denied: 

[Kernel-packages] [Bug 1890863] Re: [amdgpu] Display does not come on after suspend (amdgpu crashes)

[Nick]

After installing today's updates the issue is no longer occurring.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1890863

Title:
  [amdgpu] Display does not come on after suspend (amdgpu crashes)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After coming out of suspend the display is not receiving any data and
  stays in power saving mode.  Only power cycling the system brings it
  back.  Unsure whether this is related to amdgpu or something else.

  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: Sat Aug  8 12:51:28 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 
5700/5700 XT] [1002:731f] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Navi 10 [Radeon RX 5600 OEM/5600 
XT / 5700/5700 XT] [1458:2314]
  InstallationDate: Installed on 2020-01-08 (212 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200106)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=d1ce6274-5a98-4eab-93b4-393469cec0d9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2603
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF GAMING X570-PLUS (WI-FI)
  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.:bvr2603:bd08/05/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):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/1890863/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1893774] Re: [amdgpu] Screen freeze when loging in after a log out

[snow]

I have a crash file, but creating a bug with "ubuntu-bug" did not open a
webbrowser even if there is no error message on the console. So if you
do like to have it attached here how can I provide you the crash file?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1893774

Title:
  [amdgpu] Screen freeze when loging in after a log out

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Incomplete

Bug description:
  I use Kubuntu 20.04.1 on Thinpad T495 with encrypted disk (LVMS) and
  finger print reader.

  PROBLEM:
  1. I boot the laptop and can work
  2. I log my user out and try to log in again with te password
  3. I enter the password and press enter
  4. The screen freezes and shows the login screen. It can only be killed and 
rebooted. 

  Also, the finger print reader works everywhere, but not in the
  situation above. These are the seetings of my common-auth file:

  # here are the per-package modules (the "Primary" block)
  auth  [success=2 default=ignore]  pam_fprintd.so max_tries=1 timeout=10 # 
debug
  auth  [success=1 default=ignore]  pam_unix.so nullok_secure try_first_pass

  But I do NOT think that the problem is related to the fingerprint
  reader.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Uname: Linux 5.4.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Tue Sep  1 13:38:09 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev d2) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Picasso [17aa:5125]
  InstallationDate: Installed on 2020-08-31 (0 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  MachineType: LENOVO 20NKS01Y00
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-45-generic 
root=/dev/mapper/vgkubuntu-root ro quiet splash iommu=soft vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R12ET50W(1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NKS01Y00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR12ET50W(1.20):bd02/19/2020:svnLENOVO:pn20NKS01Y00:pvrThinkPadT495:rvnLENOVO:rn20NKS01Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T495
  dmi.product.name: 20NKS01Y00
  dmi.product.sku: LENOVO_MT_20NK_BU_Think_FM_ThinkPad T495
  dmi.product.version: ThinkPad T495
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 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/1893774/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1894064] [NEW] lubuntu groovy QA-test live session locked up

[Chris Guiver]

Public bug reported:

Lubuntu groovy 'live' QA-test on 
hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)

Test went for some time, then on waking xscreensaver (testing for a
bug), the session froze (news being streamed was still audible)

I attempted to fix (see below), but was unable. On switching to text
term (ctrl+alt+F4) audio ended (I was streaming news in firefox) &
nothing responded (numlock & capslock had already stopped responding on
GUI lock up).

This report will be of little value I suspect, as the logs are of a new
session given I was unable to recover the first session (which had the
useful logs).

Refer to iso.qa.ubuntu.com for test details.. 
Key paste from the link will be as follows

---
...
this session went for some time, I had screensaver kick in, plus stated it 
looking for http://launchpad.net/bugs/1855220 (choppy issues) and didn't notice 
anything choppy (maybe these screens but a different box)... However after 
waking screensaver for a "preview" the session was not recoverable... news kept 
streaming so session was running.. but session appeared unrecoverable..

using ctrl+alt+F4 shut news up.. but screen did not change. black upper
display still (it went black when I stopped xscreensaver preview,
pointer visible on top display but won't move.. and bottom display shows
a stuck flurry screen still).

I was unable to recover session, could not use a text terminal either
and strangely he numlock/capslock keys weren't even changing the LEDs on
the keyboard..

No mouse movement after I tried to end xscreensaver preview.
- the upper display had returned to black (flurry xscreensaver image gone where 
I was expecting the streaming firefox/news to return but no
- mouse pointer was drawn on upper display
- lower display stayed locked on a frozen flurry (xscreensaver) screen

I've machine (with SysRq REISUB) and will file bug from there, alas as
session is lost the bug report will be near meaningless, but filed for
this QA anyway.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: linux-image-5.8.0-16-generic 5.8.0-16.17
ProcVersionSignature: Ubuntu 5.8.0-16.17-generic 5.8.0
Uname: Linux 5.8.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  lubuntu1552 F pulseaudio
 /dev/snd/controlC1:  lubuntu1552 F pulseaudio
CasperMD5CheckResult: pass
CasperVersion: 1.452
CurrentDesktop: LXQt
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
Date: Thu Sep  3 08:32:43 2020
IwConfig:
 lono wireless extensions.
 
 eno1  no wireless extensions.
LiveMediaBuild: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200902)
MachineType: Hewlett-Packard HP Compaq 8200 Elite SFF PC
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed 
quiet splash ---
RelatedPackageVersions:
 linux-restricted-modules-5.8.0-16-generic N/A
 linux-backports-modules-5.8.0-16-generic  N/A
 linux-firmware1.190
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/09/2011
dmi.bios.release: 2.6
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: J01 v02.06
dmi.board.asset.tag: AUD14001GG
dmi.board.name: 1495
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: AUD14001GG
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ01v02.06:bd06/09/2011:br2.6:svnHewlett-Packard:pnHPCompaq8200EliteSFFPC:pvr:rvnHewlett-Packard:rn1495:rvr:cvnHewlett-Packard:ct6:cvr:
dmi.product.family: 103C_53307F G=D
dmi.product.name: HP Compaq 8200 Elite SFF PC
dmi.product.sku: XL510AV
dmi.sys.vendor: Hewlett-Packard

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug groovy

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894064

Title:
  lubuntu groovy QA-test live session locked up

Status in linux package in Ubuntu:
  New

Bug description:
  Lubuntu groovy 'live' QA-test on 
  hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)

  Test went for some time, then on waking xscreensaver (testing for a
  bug), the session froze (news being streamed was still audible)

  I attempted to fix (see below), but was unable. On switching to text
  term (ctrl+alt+F4) audio ended (I was streaming news in firefox) &
  nothing responded (numlock & capslock had already stopped responding
  on GUI lock up).

  This report will be of little value I suspect, as the logs are of a
  new session given I was unable to recover the first session (which had
  the useful logs).

  Refer to iso.qa.ubuntu.com for test details.. 
  Key paste from the link will be as follows

  ---
  ...
  this session went for some time, I had screensaver kick in, plus 

[Kernel-packages] [Bug 1890863] Re: [amdgpu] Display does not come on after suspend (amdgpu crashes)

[Kai-Heng Feng]

** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/1890863

Title:
  [amdgpu] Display does not come on after suspend (amdgpu crashes)

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  After coming out of suspend the display is not receiving any data and
  stays in power saving mode.  Only power cycling the system brings it
  back.  Unsure whether this is related to amdgpu or something else.

  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: Sat Aug  8 12:51:28 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 
5700/5700 XT] [1002:731f] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Navi 10 [Radeon RX 5600 OEM/5600 
XT / 5700/5700 XT] [1458:2314]
  InstallationDate: Installed on 2020-01-08 (212 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200106)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=d1ce6274-5a98-4eab-93b4-393469cec0d9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2603
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF GAMING X570-PLUS (WI-FI)
  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.:bvr2603:bd08/05/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):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/1890863/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1893817] Re: aws: enable PCI write-combine for arm64

[Stefan Bader]

** Changed in: linux-aws (Ubuntu Bionic)
   Importance: Undecided => Low

** Changed in: linux-aws (Ubuntu Focal)
   Importance: Undecided => Low

** Changed in: linux-aws (Ubuntu Groovy)
   Importance: Undecided => Low

** Changed in: linux-aws (Ubuntu Bionic)
   Importance: Low => Medium

** Changed in: linux-aws (Ubuntu Focal)
   Importance: Low => Medium

** Changed in: linux-aws (Ubuntu Groovy)
   Importance: Low => Medium

-- 
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/1893817

Title:
  aws: enable PCI write-combine for arm64

Status in linux-aws package in Ubuntu:
  In Progress
Status in linux-aws source package in Bionic:
  In Progress
Status in linux-aws source package in Focal:
  In Progress
Status in linux-aws source package in Groovy:
  In Progress

Bug description:
  To improve PCI performance on arm64 AWS instances, enable
  arch_can_pci_mmap_wc() via the patch:

  From: Clint Sbisa 
  Subject: [PATCH] arm64: Enable PCI write-combine resources under sysfs

  https://lore.kernel.org/linux-
  pci/20200831151827.pumm2p54fyj7f...@amazon.com/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1893817/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1894064] Re: lubuntu groovy QA-test live session locked up

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1894064

** Tags added: iso-testing

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894064

Title:
  lubuntu groovy QA-test live session locked up

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Lubuntu groovy 'live' QA-test on 
  hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)

  Test went for some time, then on waking xscreensaver (testing for a
  bug), the session froze (news being streamed was still audible)

  I attempted to fix (see below), but was unable. On switching to text
  term (ctrl+alt+F4) audio ended (I was streaming news in firefox) &
  nothing responded (numlock & capslock had already stopped responding
  on GUI lock up).

  This report will be of little value I suspect, as the logs are of a
  new session given I was unable to recover the first session (which had
  the useful logs).

  Refer to iso.qa.ubuntu.com for test details.. 
  Key paste from the link will be as follows

  ---
  ...
  this session went for some time, I had screensaver kick in, plus stated it 
looking for http://launchpad.net/bugs/1855220 (choppy issues) and didn't notice 
anything choppy (maybe these screens but a different box)... However after 
waking screensaver for a "preview" the session was not recoverable... news kept 
streaming so session was running.. but session appeared unrecoverable..

  using ctrl+alt+F4 shut news up.. but screen did not change. black
  upper display still (it went black when I stopped xscreensaver
  preview, pointer visible on top display but won't move.. and bottom
  display shows a stuck flurry screen still).

  I was unable to recover session, could not use a text terminal either
  and strangely he numlock/capslock keys weren't even changing the LEDs
  on the keyboard..

  No mouse movement after I tried to end xscreensaver preview.
  - the upper display had returned to black (flurry xscreensaver image gone 
where I was expecting the streaming firefox/news to return but no
  - mouse pointer was drawn on upper display
  - lower display stayed locked on a frozen flurry (xscreensaver) screen

  I've machine (with SysRq REISUB) and will file bug from there, alas as
  session is lost the bug report will be near meaningless, but filed for
  this QA anyway.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-16-generic 5.8.0-16.17
  ProcVersionSignature: Ubuntu 5.8.0-16.17-generic 5.8.0
  Uname: Linux 5.8.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lubuntu1552 F pulseaudio
   /dev/snd/controlC1:  lubuntu1552 F pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.452
  CurrentDesktop: LXQt
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Thu Sep  3 08:32:43 2020
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  LiveMediaBuild: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200902)
  MachineType: Hewlett-Packard HP Compaq 8200 Elite SFF PC
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed quiet splash ---
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-16-generic N/A
   linux-backports-modules-5.8.0-16-generic  N/A
   linux-firmware1.190
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/09/2011
  dmi.bios.release: 2.6
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J01 v02.06
  dmi.board.asset.tag: AUD14001GG
  dmi.board.name: 1495
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: AUD14001GG
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ01v02.06:bd06/09/2011:br2.6:svnHewlett-Packard:pnHPCompaq8200EliteSFFPC:pvr:rvnHewlett-Packard:rn1495:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP Compaq 8200 Elite SFF PC
  dmi.product.sku: XL510AV
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894064/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1894064] Missing required logs.

[Ubuntu Kernel Bot]

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 1894064

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894064

Title:
  lubuntu groovy QA-test live session locked up

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Lubuntu groovy 'live' QA-test on 
  hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)

  Test went for some time, then on waking xscreensaver (testing for a
  bug), the session froze (news being streamed was still audible)

  I attempted to fix (see below), but was unable. On switching to text
  term (ctrl+alt+F4) audio ended (I was streaming news in firefox) &
  nothing responded (numlock & capslock had already stopped responding
  on GUI lock up).

  This report will be of little value I suspect, as the logs are of a
  new session given I was unable to recover the first session (which had
  the useful logs).

  Refer to iso.qa.ubuntu.com for test details.. 
  Key paste from the link will be as follows

  ---
  ...
  this session went for some time, I had screensaver kick in, plus stated it 
looking for http://launchpad.net/bugs/1855220 (choppy issues) and didn't notice 
anything choppy (maybe these screens but a different box)... However after 
waking screensaver for a "preview" the session was not recoverable... news kept 
streaming so session was running.. but session appeared unrecoverable..

  using ctrl+alt+F4 shut news up.. but screen did not change. black
  upper display still (it went black when I stopped xscreensaver
  preview, pointer visible on top display but won't move.. and bottom
  display shows a stuck flurry screen still).

  I was unable to recover session, could not use a text terminal either
  and strangely he numlock/capslock keys weren't even changing the LEDs
  on the keyboard..

  No mouse movement after I tried to end xscreensaver preview.
  - the upper display had returned to black (flurry xscreensaver image gone 
where I was expecting the streaming firefox/news to return but no
  - mouse pointer was drawn on upper display
  - lower display stayed locked on a frozen flurry (xscreensaver) screen

  I've machine (with SysRq REISUB) and will file bug from there, alas as
  session is lost the bug report will be near meaningless, but filed for
  this QA anyway.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-16-generic 5.8.0-16.17
  ProcVersionSignature: Ubuntu 5.8.0-16.17-generic 5.8.0
  Uname: Linux 5.8.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lubuntu1552 F pulseaudio
   /dev/snd/controlC1:  lubuntu1552 F pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.452
  CurrentDesktop: LXQt
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Thu Sep  3 08:32:43 2020
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  LiveMediaBuild: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200902)
  MachineType: Hewlett-Packard HP Compaq 8200 Elite SFF PC
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed quiet splash ---
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-16-generic N/A
   linux-backports-modules-5.8.0-16-generic  N/A
   linux-firmware1.190
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/09/2011
  dmi.bios.release: 2.6
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J01 v02.06
  dmi.board.asset.tag: AUD14001GG
  dmi.board.name: 1495
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: AUD14001GG
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ01v02.06:bd06/09/2011:br2.6:svnHewlett-Packard:pnHPCompaq8200EliteSFFPC:pvr:rvnHewlett-Packard:rn1495:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP Compaq 8200 Elite SFF PC
  dmi.product.sku: XL510AV
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894064/+subscriptions

-- 
Mailing list: 

[Kernel-packages] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

[Daniel van Vugt]

This bug is closed. Please use the 'ubuntu-bug' command to open a new
one.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1798961

Title:
  Random unrecoverable freezes on Ubuntu 18.10

Status in Linux:
  New
Status in linux package in Ubuntu:
  Won't Fix
Status in xserver-xorg-video-intel package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Won't Fix
Status in xserver-xorg-video-intel source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  Won't Fix
Status in xserver-xorg-video-intel source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  Won't Fix
Status in xserver-xorg-video-intel source package in Disco:
  Invalid

Bug description:
  First thing I notice is that the mouse cursor freezes as I'm using it,
  then I hit the CAPS LOCK key and the LED indicator doesn't respond.
  Then I try the "REISUB" command, but it doesn't do anything either.
  Only a hard reset works, pressing down the power button for a few
  seconds.

  How to reproduce?
  I couldn't figure out a consistent method. It is still random to me.

  Version: Ubuntu 4.18.0-10.11-generic 4.18.12
  System information attached.

  Also happens under Arch Linux and Fedora.
  I've talked to another user on IRC who seems to be having the same freezes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsilva 1213 F pulseaudio
   /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.sku: Inspiron 5458
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1798961/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1893774] Re: [amdgpu] Screen freeze when loging in after a log out

[Daniel van Vugt]

That's a crash in the kglobalaccel package, which is probably not
relevant here. Do you have any other crash files? If not then look at
https://errors.ubuntu.com/user/ID where ID is the content of file
/var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to
recent problems on that page? If so then please send the links to us.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1893774

Title:
  [amdgpu] Screen freeze when loging in after a log out

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Incomplete

Bug description:
  I use Kubuntu 20.04.1 on Thinpad T495 with encrypted disk (LVMS) and
  finger print reader.

  PROBLEM:
  1. I boot the laptop and can work
  2. I log my user out and try to log in again with te password
  3. I enter the password and press enter
  4. The screen freezes and shows the login screen. It can only be killed and 
rebooted. 

  Also, the finger print reader works everywhere, but not in the
  situation above. These are the seetings of my common-auth file:

  # here are the per-package modules (the "Primary" block)
  auth  [success=2 default=ignore]  pam_fprintd.so max_tries=1 timeout=10 # 
debug
  auth  [success=1 default=ignore]  pam_unix.so nullok_secure try_first_pass

  But I do NOT think that the problem is related to the fingerprint
  reader.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Uname: Linux 5.4.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Tue Sep  1 13:38:09 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev d2) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Picasso [17aa:5125]
  InstallationDate: Installed on 2020-08-31 (0 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  MachineType: LENOVO 20NKS01Y00
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-45-generic 
root=/dev/mapper/vgkubuntu-root ro quiet splash iommu=soft vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R12ET50W(1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NKS01Y00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR12ET50W(1.20):bd02/19/2020:svnLENOVO:pn20NKS01Y00:pvrThinkPadT495:rvnLENOVO:rn20NKS01Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T495
  dmi.product.name: 20NKS01Y00
  dmi.product.sku: LENOVO_MT_20NK_BU_Think_FM_ThinkPad T495
  dmi.product.version: ThinkPad T495
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 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/1893774/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1894064] ProcCpuinfo.txt

[Chris Guiver]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1894064/+attachment/5407357/+files/ProcCpuinfo.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894064

Title:
  lubuntu groovy QA-test live session locked up

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Lubuntu groovy 'live' QA-test on 
  hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)

  Test went for some time, then on waking xscreensaver (testing for a
  bug), the session froze (news being streamed was still audible)

  I attempted to fix (see below), but was unable. On switching to text
  term (ctrl+alt+F4) audio ended (I was streaming news in firefox) &
  nothing responded (numlock & capslock had already stopped responding
  on GUI lock up).

  This report will be of little value I suspect, as the logs are of a
  new session given I was unable to recover the first session (which had
  the useful logs).

  Refer to iso.qa.ubuntu.com for test details.. 
  Key paste from the link will be as follows

  ---
  ...
  this session went for some time, I had screensaver kick in, plus stated it 
looking for http://launchpad.net/bugs/1855220 (choppy issues) and didn't notice 
anything choppy (maybe these screens but a different box)... However after 
waking screensaver for a "preview" the session was not recoverable... news kept 
streaming so session was running.. but session appeared unrecoverable..

  using ctrl+alt+F4 shut news up.. but screen did not change. black
  upper display still (it went black when I stopped xscreensaver
  preview, pointer visible on top display but won't move.. and bottom
  display shows a stuck flurry screen still).

  I was unable to recover session, could not use a text terminal either
  and strangely he numlock/capslock keys weren't even changing the LEDs
  on the keyboard..

  No mouse movement after I tried to end xscreensaver preview.
  - the upper display had returned to black (flurry xscreensaver image gone 
where I was expecting the streaming firefox/news to return but no
  - mouse pointer was drawn on upper display
  - lower display stayed locked on a frozen flurry (xscreensaver) screen

  I've machine (with SysRq REISUB) and will file bug from there, alas as
  session is lost the bug report will be near meaningless, but filed for
  this QA anyway.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-16-generic 5.8.0-16.17
  ProcVersionSignature: Ubuntu 5.8.0-16.17-generic 5.8.0
  Uname: Linux 5.8.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lubuntu1552 F pulseaudio
   /dev/snd/controlC1:  lubuntu1552 F pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.452
  CurrentDesktop: LXQt
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Thu Sep  3 08:32:43 2020
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  LiveMediaBuild: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200902)
  MachineType: Hewlett-Packard HP Compaq 8200 Elite SFF PC
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed quiet splash ---
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-16-generic N/A
   linux-backports-modules-5.8.0-16-generic  N/A
   linux-firmware1.190
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/09/2011
  dmi.bios.release: 2.6
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J01 v02.06
  dmi.board.asset.tag: AUD14001GG
  dmi.board.name: 1495
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: AUD14001GG
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ01v02.06:bd06/09/2011:br2.6:svnHewlett-Packard:pnHPCompaq8200EliteSFFPC:pvr:rvnHewlett-Packard:rn1495:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP Compaq 8200 Elite SFF PC
  dmi.product.sku: XL510AV
  dmi.sys.vendor: Hewlett-Packard
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lubuntu1527 F pulseaudio
   /dev/snd/controlC1:  lubuntu1527 F pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.452
  CurrentDesktop: LXQt
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  DistroRelease: Ubuntu 20.10
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  LiveMediaBuild: Lubuntu 20.10 "Groovy Gorilla" - 

[Kernel-packages] [Bug 1894064] Lsusb-t.txt

[Chris Guiver]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1894064/+attachment/5407355/+files/Lsusb-t.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894064

Title:
  lubuntu groovy QA-test live session locked up

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Lubuntu groovy 'live' QA-test on 
  hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)

  Test went for some time, then on waking xscreensaver (testing for a
  bug), the session froze (news being streamed was still audible)

  I attempted to fix (see below), but was unable. On switching to text
  term (ctrl+alt+F4) audio ended (I was streaming news in firefox) &
  nothing responded (numlock & capslock had already stopped responding
  on GUI lock up).

  This report will be of little value I suspect, as the logs are of a
  new session given I was unable to recover the first session (which had
  the useful logs).

  Refer to iso.qa.ubuntu.com for test details.. 
  Key paste from the link will be as follows

  ---
  ...
  this session went for some time, I had screensaver kick in, plus stated it 
looking for http://launchpad.net/bugs/1855220 (choppy issues) and didn't notice 
anything choppy (maybe these screens but a different box)... However after 
waking screensaver for a "preview" the session was not recoverable... news kept 
streaming so session was running.. but session appeared unrecoverable..

  using ctrl+alt+F4 shut news up.. but screen did not change. black
  upper display still (it went black when I stopped xscreensaver
  preview, pointer visible on top display but won't move.. and bottom
  display shows a stuck flurry screen still).

  I was unable to recover session, could not use a text terminal either
  and strangely he numlock/capslock keys weren't even changing the LEDs
  on the keyboard..

  No mouse movement after I tried to end xscreensaver preview.
  - the upper display had returned to black (flurry xscreensaver image gone 
where I was expecting the streaming firefox/news to return but no
  - mouse pointer was drawn on upper display
  - lower display stayed locked on a frozen flurry (xscreensaver) screen

  I've machine (with SysRq REISUB) and will file bug from there, alas as
  session is lost the bug report will be near meaningless, but filed for
  this QA anyway.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-16-generic 5.8.0-16.17
  ProcVersionSignature: Ubuntu 5.8.0-16.17-generic 5.8.0
  Uname: Linux 5.8.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lubuntu1552 F pulseaudio
   /dev/snd/controlC1:  lubuntu1552 F pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.452
  CurrentDesktop: LXQt
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Thu Sep  3 08:32:43 2020
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  LiveMediaBuild: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200902)
  MachineType: Hewlett-Packard HP Compaq 8200 Elite SFF PC
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed quiet splash ---
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-16-generic N/A
   linux-backports-modules-5.8.0-16-generic  N/A
   linux-firmware1.190
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/09/2011
  dmi.bios.release: 2.6
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J01 v02.06
  dmi.board.asset.tag: AUD14001GG
  dmi.board.name: 1495
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: AUD14001GG
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ01v02.06:bd06/09/2011:br2.6:svnHewlett-Packard:pnHPCompaq8200EliteSFFPC:pvr:rvnHewlett-Packard:rn1495:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP Compaq 8200 Elite SFF PC
  dmi.product.sku: XL510AV
  dmi.sys.vendor: Hewlett-Packard
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lubuntu1527 F pulseaudio
   /dev/snd/controlC1:  lubuntu1527 F pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.452
  CurrentDesktop: LXQt
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  DistroRelease: Ubuntu 20.10
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  LiveMediaBuild: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 

[Kernel-packages] [Bug 1894064] Lsusb.txt

[Chris Guiver]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1894064/+attachment/5407354/+files/Lsusb.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894064

Title:
  lubuntu groovy QA-test live session locked up

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Lubuntu groovy 'live' QA-test on 
  hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)

  Test went for some time, then on waking xscreensaver (testing for a
  bug), the session froze (news being streamed was still audible)

  I attempted to fix (see below), but was unable. On switching to text
  term (ctrl+alt+F4) audio ended (I was streaming news in firefox) &
  nothing responded (numlock & capslock had already stopped responding
  on GUI lock up).

  This report will be of little value I suspect, as the logs are of a
  new session given I was unable to recover the first session (which had
  the useful logs).

  Refer to iso.qa.ubuntu.com for test details.. 
  Key paste from the link will be as follows

  ---
  ...
  this session went for some time, I had screensaver kick in, plus stated it 
looking for http://launchpad.net/bugs/1855220 (choppy issues) and didn't notice 
anything choppy (maybe these screens but a different box)... However after 
waking screensaver for a "preview" the session was not recoverable... news kept 
streaming so session was running.. but session appeared unrecoverable..

  using ctrl+alt+F4 shut news up.. but screen did not change. black
  upper display still (it went black when I stopped xscreensaver
  preview, pointer visible on top display but won't move.. and bottom
  display shows a stuck flurry screen still).

  I was unable to recover session, could not use a text terminal either
  and strangely he numlock/capslock keys weren't even changing the LEDs
  on the keyboard..

  No mouse movement after I tried to end xscreensaver preview.
  - the upper display had returned to black (flurry xscreensaver image gone 
where I was expecting the streaming firefox/news to return but no
  - mouse pointer was drawn on upper display
  - lower display stayed locked on a frozen flurry (xscreensaver) screen

  I've machine (with SysRq REISUB) and will file bug from there, alas as
  session is lost the bug report will be near meaningless, but filed for
  this QA anyway.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-16-generic 5.8.0-16.17
  ProcVersionSignature: Ubuntu 5.8.0-16.17-generic 5.8.0
  Uname: Linux 5.8.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lubuntu1552 F pulseaudio
   /dev/snd/controlC1:  lubuntu1552 F pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.452
  CurrentDesktop: LXQt
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Thu Sep  3 08:32:43 2020
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  LiveMediaBuild: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200902)
  MachineType: Hewlett-Packard HP Compaq 8200 Elite SFF PC
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed quiet splash ---
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-16-generic N/A
   linux-backports-modules-5.8.0-16-generic  N/A
   linux-firmware1.190
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/09/2011
  dmi.bios.release: 2.6
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J01 v02.06
  dmi.board.asset.tag: AUD14001GG
  dmi.board.name: 1495
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: AUD14001GG
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ01v02.06:bd06/09/2011:br2.6:svnHewlett-Packard:pnHPCompaq8200EliteSFFPC:pvr:rvnHewlett-Packard:rn1495:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP Compaq 8200 Elite SFF PC
  dmi.product.sku: XL510AV
  dmi.sys.vendor: Hewlett-Packard
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lubuntu1527 F pulseaudio
   /dev/snd/controlC1:  lubuntu1527 F pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.452
  CurrentDesktop: LXQt
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  DistroRelease: Ubuntu 20.10
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  LiveMediaBuild: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 

[Kernel-packages] [Bug 1894064] CRDA.txt

[Chris Guiver]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1894064/+attachment/5407351/+files/CRDA.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894064

Title:
  lubuntu groovy QA-test live session locked up

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Lubuntu groovy 'live' QA-test on 
  hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)

  Test went for some time, then on waking xscreensaver (testing for a
  bug), the session froze (news being streamed was still audible)

  I attempted to fix (see below), but was unable. On switching to text
  term (ctrl+alt+F4) audio ended (I was streaming news in firefox) &
  nothing responded (numlock & capslock had already stopped responding
  on GUI lock up).

  This report will be of little value I suspect, as the logs are of a
  new session given I was unable to recover the first session (which had
  the useful logs).

  Refer to iso.qa.ubuntu.com for test details.. 
  Key paste from the link will be as follows

  ---
  ...
  this session went for some time, I had screensaver kick in, plus stated it 
looking for http://launchpad.net/bugs/1855220 (choppy issues) and didn't notice 
anything choppy (maybe these screens but a different box)... However after 
waking screensaver for a "preview" the session was not recoverable... news kept 
streaming so session was running.. but session appeared unrecoverable..

  using ctrl+alt+F4 shut news up.. but screen did not change. black
  upper display still (it went black when I stopped xscreensaver
  preview, pointer visible on top display but won't move.. and bottom
  display shows a stuck flurry screen still).

  I was unable to recover session, could not use a text terminal either
  and strangely he numlock/capslock keys weren't even changing the LEDs
  on the keyboard..

  No mouse movement after I tried to end xscreensaver preview.
  - the upper display had returned to black (flurry xscreensaver image gone 
where I was expecting the streaming firefox/news to return but no
  - mouse pointer was drawn on upper display
  - lower display stayed locked on a frozen flurry (xscreensaver) screen

  I've machine (with SysRq REISUB) and will file bug from there, alas as
  session is lost the bug report will be near meaningless, but filed for
  this QA anyway.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-16-generic 5.8.0-16.17
  ProcVersionSignature: Ubuntu 5.8.0-16.17-generic 5.8.0
  Uname: Linux 5.8.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lubuntu1552 F pulseaudio
   /dev/snd/controlC1:  lubuntu1552 F pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.452
  CurrentDesktop: LXQt
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Thu Sep  3 08:32:43 2020
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  LiveMediaBuild: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200902)
  MachineType: Hewlett-Packard HP Compaq 8200 Elite SFF PC
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed quiet splash ---
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-16-generic N/A
   linux-backports-modules-5.8.0-16-generic  N/A
   linux-firmware1.190
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/09/2011
  dmi.bios.release: 2.6
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J01 v02.06
  dmi.board.asset.tag: AUD14001GG
  dmi.board.name: 1495
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: AUD14001GG
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ01v02.06:bd06/09/2011:br2.6:svnHewlett-Packard:pnHPCompaq8200EliteSFFPC:pvr:rvnHewlett-Packard:rn1495:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP Compaq 8200 Elite SFF PC
  dmi.product.sku: XL510AV
  dmi.sys.vendor: Hewlett-Packard
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lubuntu1527 F pulseaudio
   /dev/snd/controlC1:  lubuntu1527 F pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.452
  CurrentDesktop: LXQt
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  DistroRelease: Ubuntu 20.10
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  LiveMediaBuild: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64