date:20210128

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1882503

Title:
  eeh-basic.sh in powerpc from ubuntu_kernel_selftests timeout with 5.4
  P8 / P9

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Committed
Status in linux source package in Hirsute:
  In Progress

Bug description:
  [Impact]
  The breakable devices test is hardware-dependent. In our test pool
  it will take about:
  * 30 seconds to run on a Power8 system that with 5 breakable devices,
  * 60 seconds to run on a Power9 system that with 4 breakable devices.

  The default 45 seconds kselftest framework timeout is not enough to
  allow this test to finish on some nodes. Thus causing this test to
  fail with TIMEOUT error.

  [Fix]
  * f5eca0b279117f ("selftests/powerpc/eeh: disable kselftest timeout
  setting for eeh-basic")

  We have this testcase since Focal, and this patch can be cherry-picked
  into all affected releases.

  [Test case]
  Run this test on P9 node baltar, on which this timeout issue can be
  100% reproduced. With this patch applied, the test can finish without
  being terminated by the default timeout.

  [Where problems could occur]
  This will make test takes longer to finish, but it's still being
  controlled by the timeout mechanism both in the test case and
  kselftest framework. It's unlikely to make the test hang forever.

  == Original Bug Report ==
  Issue found on 5.4.0-34.38, Focal P9 "baltar"

   # selftests: powerpc/eeh: eeh-basic.sh
   # :00:00.0, Skipped: bridge
   # 0001:00:00.0, Skipped: bridge
   # 0002:00:00.0, Skipped: bridge
   # 0002:01:00.0, Added
   # 0003:00:00.0, Skipped: bridge
   # 0003:01:00.0, Added
   # 0004:00:00.0, Skipped: bridge
   # 0004:01:00.0, Skipped: bridge
   # 0004:02:00.0, Added
   # 0005:00:00.0, Skipped: bridge
   # 0005:01:00.0, Added
   # 0030:00:00.0, Skipped: bridge
   # 0031:00:00.0, Skipped: bridge
   # 0032:00:00.0, Skipped: bridge
   # 0033:00:00.0, Skipped: bridge
   # Found 4 breakable devices...
   # Breaking 0002:01:00.0...
   # 0002:01:00.0, waited 0/60
   # 0002:01:00.0, waited 1/60
   # 0002:01:00.0, waited 2/60
   # 0002:01:00.0, waited 3/60
   # 0002:01:00.0, waited 4/60
   # 0002:01:00.0, waited 5/60
   # 0002:01:00.0, waited 6/60
   # 0002:01:00.0, Recovered after 7 seconds
   # Breaking 0003:01:00.0...
   # 0003:01:00.0, waited 0/60
   # 0003:01:00.0, waited 1/60
   # 0003:01:00.0, waited 2/60
   # 0003:01:00.0, waited 3/60
   # 0003:01:00.0, waited 4/60
   # 0003:01:00.0, waited 5/60
   # 0003:01:00.0, waited 6/60
   # 0003:01:00.0, waited 7/60
   # 0003:01:00.0, waited 8/60
   # 0003:01:00.0, waited 9/60
   # 0003:01:00.0, waited 10/60
   # 0003:01:00.0, waited 11/60
   # 0003:01:00.0, waited 12/60
   # 0003:01:00.0, waited 13/60
   # 0003:01:00.0, waited 14/60
   # 0003:01:00.0, waited 15/60
   # 0003:01:00.0, waited 16/60
   # 0003:01:00.0, waited 17/60
   # 0003:01:00.0, waited 18/60
   # 0003:01:00.0, waited 19/60
   # 0003:01:00.0, waited 20/60
   # 0003:01:00.0, waited 21/60
   # 0003:01:00.0, waited 22/60
   # 0003:01:00.0, waited 23/60
   # 0003:01:00.0, waited 24/60
   # 0003:01:00.0, waited 25/60
   # 0003:01:00.0, waited 26/60
   # 0003:01:00.0, waited 27/60
   # 0003:01:00.0, waited 28/60
   # 0003:01:00.0, waited 29/60
   # 0003:01:00.0, waited 30/60
   # 0003:01:00.0, waited 31/60
   # 0003:01:00.0, waited 32/60
   # 0003:01:00.0, waited 33/60
   # 0003:01:00.0, waited 34/60
   # 0003:01:00.0, waited 35/60
   # 0003:01:00.0, Recovered after 36 seconds
   # Breaking 0004:02:00.0...
   # 0004:02:00.0, Recovered after 0 seconds
   # Breaking 0005:01:00.0...
   # 0005:01:00.0, waited 0/60
   # 0005:01:00.0, waited 1/60
   #
   not ok 1 selftests: powerpc/eeh: eeh-basic.sh # TIMEOUT

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

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

[Kernel-packages] [Bug 1865570] Re: suspend only works once on ThinkPad X1 Carbon gen 7

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1865570

Title:
  suspend only works once on ThinkPad X1 Carbon gen 7

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Won't Fix
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux-oem-osp1 source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-osp1 source package in Focal:
  Won't Fix

Bug description:
  === SRU Justification Fix===

  [Impact]
  Some ThinkPads failed to suspend to s2idle when ethernet disconnected.

  [Fix]
  I219 chip of some platforms is controlled by ME, which needs more time
  when setting ULP mode. Wait for ME to finish setting ULP mode.

  [Test]
  Verified on hw, and user reported s2idle works.

  [Regression Potential]
  Low, Increase timeout and breaks with condition,
  no impacts for who don't need this long wait.

  Bionic doesn't introduce the commit f15bb6dde738cc8fa0, no need for
  this.

  === SRU Justification ===

  [Impact]
  Lenovo X1 Carbon 7th can only susped (s2idle) once, subsquent suspends
  are blocked by failed e1000e resume routine.

  [Fix]
  It's not root caused yet by Intel, so disable the s0ix flow on X1 Carbon
  7th as a temporary workaround.

  [Test]
  After applying the DMI quirk patch, e1000e keeps working, so it doesn't
  block s2idle anymore.
  User also confimred the workaround works.

  [Regression Potential]
  Low. It limits to a specific model, and I can confirm s0ix can still be
  reached withouth this feature.

  === Original Bug Report ===

  5.4.0-16 and 5.4.0-17 go to suspend when the lid is closed, but *only
  once* after boot. On subsequent attempts, when the lid it closed,
  backlight and wifi are turned off, but system does not suspend.

  First successful suspend:
  [ 147.413295] PM: suspend entry (s2idle)
  [ 147.416601] Filesystems sync: 0.003 seconds
  [ 147.419371] Freezing user space processes ... (elapsed 0.001 seconds) done.
  [ 147.421210] OOM killer disabled.
  [ 147.421210] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
  [ 147.422375] printk: Suspending console(s) (use no_console_suspend to debug)
  [ 147.422630] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local 
choice (Reason: 3=DEAUTH_LEAVING)
  [ 147.527810] e1000e: EEE TX LPI TIMER: 0011
  [ 150.246317] ACPI: EC: interrupt blocked
  [ 881.134544] ACPI: EC: interrupt unblocked
  [ 883.933255] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
  [ 884.047802] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
  [ 884.112730] iwlwifi :00:14.3: FW already configured (0) - re-configuring
  [ 886.815475] e1000e :00:1f.6 enp0s31f6: PHY Wakeup cause - Unicast Packet
  [ 887.485832] e1000e :00:1f.6 enp0s31f6: Hardware Error
  [ 888.016931] OOM killer enabled.
  [ 888.016932] Restarting tasks ... done.
  [ 888.060613] PM: suspend exit

  Second unsuccessful suspend:
  [ 907.584802] PM: suspend entry (s2idle)
  [ 907.589779] Filesystems sync: 0.004 seconds
  [ 907.591416] Freezing user space processes ... (elapsed 0.002 seconds) done.
  [ 907.593518] OOM killer disabled.
  [ 907.593518] Freezing remaining freezable tasks ... (elapsed 0.328 seconds) 
done.
  [ 907.921560] printk: Suspending console(s) (use no_console_suspend to debug)
  [ 907.922127] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local 
choice (Reason: 3=DEAUTH_LEAVING)
  [ 908.024438] e1000e: EEE TX LPI TIMER: 0011
  [ 909.916364] PM: pci_pm_suspend(): e1000e_pm_suspend+0x0/0x80 [e1000e] 
returns -2
  [ 909.916367] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -2
  [ 909.916369] PM: Device :00:1f.6 failed to suspend async: error -2
  [ 911.183052] PM: Some devices failed to suspend, or early wake event detected
  [ 911.197091] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
  [ 911.314903] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
  [ 911.382438] iwlwifi :00:14.3: FW already configured (0) - re-configuring
  [ 911.413624] OOM killer enabled.
  [

[Kernel-packages] [Bug 1903596] Re: stack trace in kernel

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1903596

Title:
  stack trace in kernel

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Committed
Status in linux source package in Hirsute:
  In Progress

Bug description:
  == SRU Justification ==
  Whenever a buggy NAPI driver returns more than its budget, it will
  trigger a stack trace warning with:
  WARN_ON_ONCE(work > weight);

  The warning message looks like this :
  WARNING: CPU: 2 PID: 0 at 
/build/linux-hwe-ymdo11/linux-hwe-4.15.0/net/core/dev.c:5672 
net_rx_action+0x276/0x3b0

  This is not very useful for debugging purpose, since it does not tell
  you what's going on there.

  == Fix ==
  * 427d5838e996 ("net: napi: remove useless stack trace")

  This patch will emit a message giving the function name, and a
  descriptive message like:
  NAPI poll function ath10k_pci_napi_poll+0x0/0x120 [ath10k_pci] returned 
0, exceeding its budget of 64.

  This patch is a clean-cherry for all the releases except Xenial.
  For Xenial it will need to be applied with -C1

  == Test ==
  Test kernels can be found here:
  https://people.canonical.com/~phlin/kernel/lp-1903596-napi-warnon/

  Please note that even though I tried to reproduce this on a XPS 13
  9360 mentioned in this bug report that shipped with Atheros QCA6174
  [168c:003e] wireless card, but I can't trigger this warning message.
  The bug opener is also unable to test this due to some other reasons.

  Howeve I did tried to trigger this warning forcibly by putting it
  outside the if statement with the test kernels in the following link
  to make sure it won't cause some other problem.

  https://people.canonical.com/~phlin/kernel/lp-1903596-napi-warnon
  /force-to-warn/

  == Where problems could occur ==
  For this bug itself, this patch does not really solve the problem
  but it will provide more debug information for developers in the
  future (and since this is just a warning message, it should be fine).
  We can expect to see more a detailed report against ath10k driver
  in the future on launchpad.


  == Original Bug Report ==
  This appears to be a problem in the ath10k module. I am not sure what it is 
exactly.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.15.0-122-generic 4.15.0-122.124~16.04.1
  ProcVersionSignature: Ubuntu 4.15.0-122.124~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-122-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.26
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Nov  9 13:35:54 2020
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2020-11-09 (0 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1908144] Re: disable building bpf selftests

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1908144

Title:
  disable building bpf selftests

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Groovy:
  Fix Committed
Status in linux source package in Hirsute:
  In Progress

Bug description:
  Building tools/testing/selftests/bpf/ requires dependencies which
  cannot be easily satisfied by our build process.  The problem is well-
  described by the pending upstream patch:

  https://lore.kernel.org/bpf/20201210185233.28091-1-broo...@kernel.org/
  From: Mark Brown 
  Subject: [PATCH] selftests: Skip BPF seftests by default

  To effect the same for {groovy, hirsute} we must instead make a
  debian/rules change via "UBUNTU: disable building bpf selftests (no
  VMLINUX_BTF)".

  But lets also pick up the upstream change above, as well as my related
  "clarify" change, also pending upstream.

  These three patches should be applied to {groovy, hirsute}:

    UBUNTU: SAUCE: selftests/bpf: clarify build error if no vmlinux
    UBUNTU: SAUCE: selftests: Skip BPF seftests by default
    UBUNTU: disable building bpf selftests (no VMLINUX_BTF)

  [Impact]

   * No end-user effect; selftests are not packaged.
   * Allows us to build-test upstream changes to selftests/.

  [Test Case]

   * fdr compileselftests

  [Regression Potential]

   * Low: disables building a subtree that has always to build in {g,h}.

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

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

[Kernel-packages] [Bug 1908529] Re: dep-8 ubuntu-regression-suite tests are not run for all linux-hwe-* kernels

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1908529

Title:
  dep-8 ubuntu-regression-suite tests are not run for all linux-hwe-*
  kernels

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-5.8 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-hwe-5.8 source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Committed
Status in linux-hwe-5.8 source package in Groovy:
  Invalid
Status in linux source package in Hirsute:
  In Progress
Status in linux-hwe-5.8 source package in Hirsute:
  Invalid

Bug description:
  [ Impact ]
  On autopkgtest, ubuntu-regression-suite is not run for all kernels because 
for most of them it doesn't make sense to run the tests on the environment 
provided. If a given package is going to be tested is decided on 
'debian/tests/ubuntu-regression-suite' on an opt-in basis. The current criteria 
lists all source packages, however, new hwe kernels are named as linux-hwe-x.y 
and are not included on the list.

  Logs from a skipped test run:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux-hwe-5.8/20201216_001007_32069@/log.gz

  [ Test case ]
  ADT tests are triggered when packages are promoted to -proposed. Looking at 
the logs one can check whether the tests were skipped or run.

  [ Fix ]
  The fix is to use a wild card to include all linux-hwe* kernels. A fix was 
already applied locally for bionic/linux-hwe-5.4, the same patch can be applied 
to F/G/H/U to carry it forward.

  https://git.launchpad.net/~ubuntu-
  
kernel/ubuntu/+source/linux/+git/bionic/commit/?h=hwe-5.4=a077e2f94c3a948e293fd31bce09b08c3fef7c1f

  [ Where problems could occur ]
  The code changed controls which kernel get tested on ADT 
ubuntu-regression-suite, a failure on the selection could result in testing 
kernels which shouldn't be tested or the other way around. However, the change 
is simple and has already been applied to focal/linux-hwe-5.4, so I don't 
expect it to cause issues.

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

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

[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Update (based on #296)
  =

  The latest kernel tree
  (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
  has the complete solution to fix this bug. So we can expect kernel
  v5.11 to fix this issue without any additional work.

  Before the release of v5.11, you are suggested to use #189 to save your 
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd 
driver is built into the initramfs. So you have to rebuild the initramfs after 
replacing the old module with new one.
  On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs 
-u`.

  The complete solution is three patches,
   - 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce 
filter setting in IRQ type setting")
   - 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way 
to disable debounce filter")
   - 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into 
account debounce settings")

  The first two patches has reached the stable tree. If the last one is
  also backported to LTS kernel, you won't need to install kernel 5.11.
  But I don't know when this will happen.

  Original bug report
  ===

  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:

[Kernel-packages] [Bug 1908499] Re: udpgro.sh in net from ubuntu_kernel_selftests seems not reflecting sub-test result

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1908499

Title:
  udpgro.sh in net from ubuntu_kernel_selftests seems not reflecting
  sub-test result

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.10 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:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]
  In udpgro.sh, the exit value is 0 even if there are some failed sub
  test cases:

  $ sudo ./udpgro.sh
  ipv4
   no GRO
  BTF debug data section '.BTF' rejected: Invalid argument (22)!
   - Length: 568
  Verifier analysis:

  magic: 0xeb9f
  version: 1
  flags: 0x0
  hdr_len: 24
  type_off: 0
  type_len: 256
  str_off: 256
  str_len: 288
  btf_total_size: 568
  [1] PTR (anon) type_id=2
  [2] STRUCT xdp_md size=20 vlen=5
   data type_id=3 bits_offset=0
   data_end type_id=3 bits_offset=32
   data_meta type_id=3 bits_offset=64
   ingress_ifindex type_id=3 bits_offset=96
   rx_queue_index type_id=3 bits_offset=128
  [3] TYPEDEF __u32 type_id=4
  [4] INT unsigned int size=4 bits_offset=0 nr_bits=32 encoding=(none)
  [5] FUNC_PROTO (anon) return=6 args=(1 ctx)
  [6] INT int size=4 bits_offset=0 nr_bits=32 encoding=SIGNED
  [7] FUNC xdp_dummy_prog type_id=5
  [8] INT char size=1 bits_offset=0 nr_bits=8 encoding=SIGNED
  [9] ARRAY (anon) type_id=8 index_type_id=10 nr_elems=4
  [10] INT __ARRAY_SIZE_TYPE__ size=4 bits_offset=0 nr_bits=32 encoding=(none)
  [11] VAR _license type_id=9 linkage=1
  [12] DATASEC license size=0 vlen=1 size == 0

  ./udpgso_bench_rx: poll: 0x0 expected 0x1

  failed
  ./udpgso_bench_tx: write: Connection refused

  ...

   multiple GRO socks
  BTF debug data section '.BTF' rejected: Invalid argument (22)!
   - Length: 568
  Verifier analysis:

  magic: 0xeb9f
  version: 1
  flags: 0x0
  hdr_len: 24
  type_off: 0
  type_len: 256
  str_off: 256
  str_len: 288
  btf_total_size: 568
  [1] PTR (anon) type_id=2
  [2] STRUCT xdp_md size=20 vlen=5
   data type_id=3 bits_offset=0
   data_end type_id=3 bits_offset=32
   data_meta type_id=3 bits_offset=64
   ingress_ifindex type_id=3 bits_offset=96
   rx_queue_index type_id=3 bits_offset=128
  [3] TYPEDEF __u32 type_id=4
  [4] INT unsigned int size=4 bits_offset=0 nr_bits=32 encoding=(none)
  [5] FUNC_PROTO (anon) return=6 args=(1 ctx)
  [6] INT int size=4 bits_offset=0 nr_bits=32 encoding=SIGNED
  [7] FUNC xdp_dummy_prog type_id=5
  [8] INT char size=1 bits_offset=0 nr_bits=8 encoding=SIGNED
  [9] ARRAY (anon) type_id=8 index_type_id=10 nr_elems=4
  [10] INT __ARRAY_SIZE_TYPE__ size=4 bits_offset=0 nr_bits=32 encoding=(none)
  [11] VAR _license type_id=9 linkage=1
  [12] DATASEC license size=0 vlen=1 size == 0

  ./udpgso_bench_rx: poll: 0x0 expected 0x1

  ./udpgso_bench_rx: poll: 0x0 expected 0x1

  failed
  $ echo $?
  0

  [Fix]
  * 3503ee6c0bec5f ("selftests: fix the return value for UDP GRO test")

  We have this test since Focal.
  This patch can be cherry-picked into all the affected kernels.

  [Test]
  Run this test with:
sudo ./udpgro.sh

  And check its final return value with:
echo $?

  If there is any failure, the return value should not be 0.

  [Where problems could occur]
  If this fix is incorrect it might affect the test execution, but it
  should be fine as this is just affecting the test tool. Also, with
  this patch, we are expecting to see this test case to fail until
  bug 1908501 got fixed.

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

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

[Kernel-packages] [Bug 1892860] Re: af_alg07 in crypto / cve-2019-8912 in cve from ubuntu_ltp failed on B-arm64

** Tags added: sru-20210104

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

Title:
  af_alg07 in crypto / cve-2019-8912 in cve from ubuntu_ltp failed on
  B-arm64

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Issue found on 4.15.0-114.115-generic with ARM64 node appleton-kernel
  and wright-kernel.

  Looks like this is a new test case added 13 days ago:
  
https://github.com/linux-test-project/ltp/commit/fdff6139e43aa9b19f27907f6d7f2cb4765632a1#diff-8a83d6b2c6c7d74e750e3af47e3f4a79

  The test will fail with:
   startup='Fri Aug 14 10:13:27 2020'
   tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s
   tst_taint.c:88: CONF: Ignoring already set kernel warning taint
   ../../../include/tst_fuzzy_sync.h:507: INFO: Minimum sampling period ended
   ../../../include/tst_fuzzy_sync.h:331: INFO: loop = 1024, delay_bias = 0
   ../../../include/tst_fuzzy_sync.h:320: INFO: start_a - start_b: { avg = 
-2259470ns, avg_dev = 13695382ns, dev_ratio = 6.06 }
   ../../../include/tst_fuzzy_sync.h:320: INFO: end_a - start_a : { avg = 
13968ns, avg_dev = 4310ns, dev_ratio = 0.31 } 
   ../../../include/tst_fuzzy_sync.h:320: INFO: end_b - start_b : { avg = 
15975ns, avg_dev = 50ns, dev_ratio = 0.00 } 
   ../../../include/tst_fuzzy_sync.h:320: INFO: end_a - end_b : { avg = 
-2261477ns, avg_dev = 13699742ns, dev_ratio = 6.06 }
   ../../../include/tst_fuzzy_sync.h:320: INFO: spins : { avg = 3575095 , 
avg_dev = 4553 , dev_ratio = 0.00 } 
   ../../../include/tst_fuzzy_sync.h:637: INFO: Exceeded execution time, 
requesting exit
   af_alg07.c:97: FAIL: fchownat() failed to fail, kernel may be vulnerable

   HINT: You _MAY_ be missing kernel fixes, see:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9060cb719e61

   HINT: You _MAY_ be vulnerable to CVE(s), see:

   https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-8912

   Summary:
   passed 0
   failed 1
   skipped 1
   warnings 0
   tag=af_alg07 stime=159747 dur=150 exit=exited stat=33 core=no cu=15051 
cs=0

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

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

[Kernel-packages] [Bug 1894667] Re: [HP 635] Radeon 6310 brightness control does not work

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1894667

Title:
  [HP 635] Radeon 6310 brightness control does not work

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released

Bug description:
  Brightness setting does not work on versions 16.04.7 and 20.04.1

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-112.113~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-112-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.24
  Architecture: amd64
  CasperVersion: 1.376.2
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Sep  7 12:10:27 2020
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Wrestler [Radeon HD 6310] [103c:3577]
  LiveMediaBuild: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 (20200806)
  MachineType: Hewlett-Packard HP 635 Notebook PC
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=tr_TR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd quiet splash --- debian-installer/language=tr 
keyboard-configuration/layoutcode?=tr
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.48
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3577
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 24.4A
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.48:bd12/18/2011:svnHewlett-Packard:pnHP635NotebookPC:pvr058A10004C1000260:rvnHewlett-Packard:rn3577:rvr24.4A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=635
  dmi.product.name: HP 635 Notebook PC
  dmi.product.version: 058A10004C1000260
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Mon Sep  7 14:57:25 2020
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2
  xserver.video_driver: radeon
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  xubuntu1827 F pulseaudio
   /dev/snd/controlC0:  xubuntu1827 F pulseaudio
  CasperMD5CheckMismatches: 
./pool/main/g/glibc/libc-dev-bin_2.31-0ubuntu9_amd64.deb
  CasperMD5CheckResult: skip
  CasperVersion: 1.445.1
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 20.04
  LiveMediaBuild: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Hewlett-Packard HP 635 Notebook PC
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=tr_TR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine:

[Kernel-packages] [Bug 1908335] Re: [SRU][F/G/H/U/OEM-5.6] Fix i2c report error on elan trackpoint

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1908335

Title:
  [SRU][F/G/H/U/OEM-5.6] Fix i2c report error on elan trackpoint

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.10 package in Ubuntu:
  Fix Released
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux-oem-5.6 source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Committed
Status in linux-oem-5.10 source package in Groovy:
  Fix Released
Status in linux-oem-5.6 source package in Groovy:
  Invalid
Status in linux source package in Hirsute:
  Fix Released
Status in linux-oem-5.10 source package in Hirsute:
  Fix Released
Status in linux-oem-5.6 source package in Hirsute:
  Invalid

Bug description:
  [Impact]
  New elan trackpoint on elan_i2c reports the following error:
  "failed to read report data: -71"
  it failed to work.

  [Fix]
  Add new report type support and fix protocol errors for some trackpoints in 
SMBus mode.

  [Test Case]
  Touchpad and trackpoint work well.
  Verified on 3 other models of ThinkPads with elan touchpad loaded.
  All good.

  [Where problems could occur]
  elan touchpad and trackpoint may not work.

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

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

[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

** Tags added: verification-needed-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/1887190

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Update (based on #296)
  =

  The latest kernel tree
  (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
  has the complete solution to fix this bug. So we can expect kernel
  v5.11 to fix this issue without any additional work.

  Before the release of v5.11, you are suggested to use #189 to save your 
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd 
driver is built into the initramfs. So you have to rebuild the initramfs after 
replacing the old module with new one.
  On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs 
-u`.

  The complete solution is three patches,
   - 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce 
filter setting in IRQ type setting")
   - 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way 
to disable debounce filter")
   - 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into 
account debounce settings")

  The first two patches has reached the stable tree. If the last one is
  also backported to LTS kernel, you won't need to install kernel 5.11.
  But I don't know when this will happen.

  Original bug report
  ===

  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset

[Kernel-packages] [Bug 1908992] Re: SYNA30B4:00 06CB:CE09 Mouse on HP EliteBook 850 G7 not working at all

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1908992

Title:
  SYNA30B4:00 06CB:CE09 Mouse  on HP EliteBook 850 G7 not working at all

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Committed
Status in linux-oem-5.10 source package in Groovy:
  Invalid

Bug description:
  == SRU Justification ==
  [Impact]
  Pointstick and its left right buttons don't work on EliteBook 859 G7.

  [Fix]
  Use the MT_CLS_WIN_8_FORCE_MULTI_INPUT so the usage collection for
  pointsitck and touchpad won't merge together.

  [Test]
  With the patch applied, pointstick and its left and right buttons start
  to work.

  [Where problems could occur]
  The quirk limits to one specific touchpad/pointstick combo, so
  regression would be highly unlikely.

  == Original Bug Report ==

  $ xinput
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SYNA30B4:00 06CB:CE09 Mouse id=11   [slave  pointer 
 (2)]
  ⎜   ↳ SYNA30B4:00 06CB:CE09 Touchpad  id=12   [slave  pointer 
 (2)]

  The touchpad is working fine, but the pointing stick/trackpoint does not work 
at all.
  No input is registered with xinput and libinput device tests.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-input-libinput 0.29.0-1
  ProcVersionSignature: Ubuntu 5.8.0-33.36~20.04.1-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Dec 22 10:13:13 2020
  DistUpgraded: 2020-12-22 07:48:08,643 DEBUG /openCache(), new cache size 70584
  DistroCodename: focal
  DistroVariant: ubuntu
  InstallationDate: Installed on 2020-12-11 (10 days ago)
  InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  MachineType: HP HP EliteBook 850 G7 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic 
root=/dev/mapper/vgxubuntu-root ro quiet splash psmouse.proto=bare
  SourcePackage: xserver-xorg-input-libinput
  UpgradeStatus: Upgraded to focal on 2020-12-22 (0 days ago)
  dmi.bios.date: 08/24/2020
  dmi.bios.release: 1.7
  dmi.bios.vendor: HP
  dmi.bios.version: S73 Ver. 01.01.07
  dmi.board.name: 8724
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 06.34.00
  dmi.chassis.asset.tag: 5CG0471SRC
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 6.52
  dmi.modalias: 
dmi:bvnHP:bvrS73Ver.01.01.07:bd08/24/2020:br1.7:efr6.52:svnHP:pnHPEliteBook850G7NotebookPC:pvr:rvnHP:rn8724:rvrKBCVersion06.34.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 850 G7 Notebook PC
  dmi.product.sku: 1J6F3EA#ABD
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.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.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Kernel-packages] [Bug 1901842] Re: Ubuntu 20.04 - multicast counter is not increased in ip -s

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1901842

Title:
  Ubuntu 20.04 - multicast counter is not increased in ip -s

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Committed
Status in linux source package in Hirsute:
  Invalid

Bug description:
  [Impact]
  on a mlx5 device rx-mcast counter is not increased in ip -s after receiving 
mcast packets.
  Rx-packets counter is increased normally.

  [test case]
  send multicast packets to a mlx5 device using mcast address (like 224.0.0.1)
  # iperf --client 224.0.0.1 -u  --bind 15.194.5.1

  see that before and after sending the mcast counter remains the same

  before:
  # ip -s l show ens5f0
  10: ens5f0:  mtu 1500 qdisc mq state UP mode 
DEFAULT group default qlen 1000
  link/ether ec:0d:9a:d4:2d:fc brd ff:ff:ff:ff:ff:ff
  RX: bytes  packets  errors  dropped overrun mcast   
  1350216893  0   0   0   0   
  TX: bytes  packets  errors  dropped carrier collsns 
  16221  94   0   0   0   0   

  after
  # ip -s l show ens5f0
  10: ens5f0:  mtu 1500 qdisc mq state UP mode 
DEFAULT group default qlen 1000
  link/ether ec:0d:9a:d4:2d:fc brd ff:ff:ff:ff:ff:ff
  RX: bytes  packets  errors  dropped overrun mcast   
  27004321786 0   0   0   0   
  TX: bytes  packets  errors  dropped carrier collsns 
  16221  94   0   0   0   0 

  [Fix]
  The issue is solved with upstream commit:

  commit 47c97e6b10a1e3680cad539929da092bfa535446
  Author: Ron Diskin 
  Date:   Sun May 10 14:39:51 2020 +0300

  net/mlx5e: Fix multicast counter not up-to-date in "ip -s"
  
  Currently the FW does not generate events for counters other than error
  counters. Unlike ".get_ethtool_stats", ".ndo_get_stats64" (which ip -s
  uses) might run in atomic context, while the FW interface is non atomic.
  Thus, 'ip' is not allowed to issue FW commands, so it will only display
  cached counters in the driver.
  
  Add a SW counter (mcast_packets) in the driver to count rx multicast
  packets. The counter also counts broadcast packets, as we consider it a
  special case of multicast.
  Use the counter value when calling "ip -s"/"ifconfig".
  
  Fixes: f62b8bb8f2d3 ("net/mlx5: Extend mlx5_core to support ConnectX-4 
Ethernet functionality")
  Signed-off-by: Ron Diskin 
  Reviewed-by: Tariq Toukan 
  Reviewed-by: Moshe Shemesh 
  Signed-off-by: Saeed Mahameed 

  after applying this patch the mcast counter is increased.
  before sending mcast packets

  # ip -s l show ens5f0
  10: ens5f0:  mtu 1500 qdisc mq state UP mode 
DEFAULT group default qlen 1000
  link/ether ec:0d:9a:d4:2d:fc brd ff:ff:ff:ff:ff:ff
  RX: bytes  packets  errors  dropped overrun mcast   
  0  00   0   0   0   
  TX: bytes  packets  errors  dropped carrier collsns 
  7182   41   0   0   0   0  

  after sending mcast packets
  # ip -s l show ens5f0
  10: ens5f0:  mtu 1500 qdisc mq state UP mode 
DEFAULT group default qlen 1000
  link/ether ec:0d:9a:d4:2d:fc brd ff:ff:ff:ff:ff:ff
  RX: bytes  packets  errors  dropped overrun mcast   
  1350216893  0   0   0   893 
  TX: bytes  packets  errors  dropped carrier collsns 
  9860   58   0   0   0   0   

  The patch is applied with 2 rejected hunks that need to be inserted
  manually with no changes.

  [Regression Potential]
  Regression risk is low since this patch is small and inserts only minor 
changes to the statistics mechanism.

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

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

[Kernel-packages] [Bug 1906229] Re: Refresh ACPI wakeup power to make Thunderbolt hotplug detection work

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1906229

Title:
  Refresh ACPI wakeup power to make Thunderbolt hotplug detection work

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

Bug description:
  [Impact]
  Dell Precision 5550 cannot detect Thunderbolt device hotplug.

  [Fix]
  Refresh ACPI wakeup power if it's already enabled to make GPE work.

  [Test]
  Make sure the root port of TBT hierachy is in D3cold.
  Plug a Thunderbolt Dock or Thunderbolt Disk, the system cannot detect
  anything.

  With the patch applied, OS can always detect hotplugged Thunderbolt
  devices.

  [Where problems could occur]
  Though we refresh the wakeup device power, we didn't disable/enable ACPI
  GPEs, so we won't miss any GPE event from this fix.

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

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

[Kernel-packages] [Bug 1908342] Re: selftests: test_vxlan_under_vrf: mute unnecessary error message

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1908342

Title:
  selftests: test_vxlan_under_vrf: mute unnecessary error message

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Committed
Status in linux source package in Hirsute:
  In Progress

Bug description:
  [Impact]
  The cleanup function in the selftests/net/test_vxlan_under_vrf.sh
  script that tries to delete hv-1 / hv-2 and vm-1 / vm-2 netns will
  generate some unnecessary error messages:

  Cannot remove namespace file "/run/netns/hv-2": No such file or directory
  Cannot remove namespace file "/run/netns/vm-1": No such file or directory
  Cannot remove namespace file "/run/netns/vm-2": No such file or directory

  Redirect it to /dev/null like other commands in the cleanup function
  to reduce confusion.

  [Fix]
  * 0e12c0271887f1 ("selftests: test_vxlan_under_vrf: mute unnecessary error 
message")

  This script exists in selftests/net since Focal, and this patch can be
  cherry-picked into all affected series.

  [Test]
  Run this script directly, these unnecessary error message won't be
  printed anymore.

  [Where problems could occur]
  As this change is quite straightforward, I don't think anything bad
  would happen. And even it did happen, this change is limited to testing
  tool so it should be fine.

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

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

[Kernel-packages] [Bug 1906255] Re: [UBUNTU 20.10] Applications runing in QEMU/KVM get translation faults

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1906255

Title:
  [UBUNTU 20.10] Applications runing in QEMU/KVM get translation faults

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Groovy:
  Fix Committed
Status in linux source package in Hirsute:
  In Progress

Bug description:
  SRU Justification:
  ==

  [Impact]

  * The commit 0b0ed657fe "s390: remove critical section cleanup from
  entry.S" was introduced in kernel 5.8, but instigated a problem where
  FPU registers were not properly restored when entering the SIE (start
  interpretive execution) instruction.

  * This leads to crashes of applications runnning inside KVM, as most
  of the programs in use nowdays are using FPU registers for backing of
  general register content.

  * To fix this interrupts in load_fpu_regs() need to be disabled -
  otherwise an interrupt might come in after the registers are loaded,
  but before CIF_FPU is cleared in load_fpu_regs().

  * When the interrupt returns, CIF_FPU will be cleared and the
  registers will never be restored.

  [Fix]

  * 1179f170b6f0af7bb0b3b7628136eaac450ddf31 1179f170b6f0 "s390: fix fpu
  restore in entry.S"

  [Test Case]

  * IBM Z or LinuxONE hardware with Ubuntu Server 20.10 installed.

  * A KVM host needs to be setup as well as an KVM guest (use again
  20.10).

  * Run (ideally context switching) workload that makes use of FP
  instructions inside of the KVM guest.

  * Monitor the health of the guest for crashes (logs).

  [Regression Potential]

  * Even if the code changes are quite overseeable, there is still a
  certain risk for regression, because:

  * the modifications affect a critical part of the kernel
  (arch/s390/kernel/entry.S)

  * affect the handling of the FPU registers

  * and are always in use if KVM guests run

  * So in worst case the changes may have an even bigger impact on FPU
  workloads in KVM guests

  * and may not only crash in case of FPU usage, but also KVM in
  general.

  * But the code is peurly s390x specific, hence affects IBM Z only,

  * and it got already upstream accepted with v5.10-rc6

  * and a test kernel (based on groovy master-next) was build for
  further testing.

  [Other]

  * The patch got upstream accepted with kernel v5.10-rc6, hence it will
  land sooner or later in Hirsute.

  * It was initially planned to address groovy via 5.8 upstream stable
  update, and in fact the patch was already marked for this, but it
  didn't made it because 5.8 already reached it's EOL.

  * Hence this SRU is submitted for groovy only.

  __

  commit 0b0ed657fe ("s390: remove critical section cleanup from
  entry.S") introduced a problem where FPU registers were not properly
  restored when entering SIE. This leads to crashes of applications
  runnning inside kvm, as most of the programs in use nowdays are using
  FPU registers for backing of general register content.

  Fix is upstream:
  authorSven Schnelle  2020-11-20 14:17:52 
+0100
  committer Heiko Carstens  2020-11-23 11:52:13 
+0100
  commit1179f170b6f0af7bb0b3b7628136eaac450ddf31 (patch)
  tree  19e8acb64e0968b41de4899cc1315c41b002839e /arch/s390/kernel/entry.S
  parent78d732e1f326f74f240d416af9484928303d9951 (diff)
  download  linux-1179f170b6f0af7bb0b3b7628136eaac450ddf31.tar.gz
  s390: fix fpu restore in entry.S
  We need to disable interrupts in load_fpu_regs(). Otherwise an
  interrupt might come in after the registers are loaded, but before
  CIF_FPU is cleared in load_fpu_regs(). When the interrupt returns,
  CIF_FPU will be cleared and the registers will never be restored.

  The entry.S code usually saves the interrupt state in __SF_EMPTY on the
  stack when disabling/restoring interrupts. sie64a however saves the pointer
  to the sie control block in __SF_SIE_CONTROL, which references the same
  location.  This is non-obvious to the reader. To avoid thrashing the sie
  control block pointer in load_fpu_regs(), move the __SIE_* offsets eight
  bytes after __SF_EMPTY on the stack.

  Cc:  # 5.8
  Fixes: 0b0ed657fe00 ("s390: remove critical section cleanup from entry.S")
  Reported-by:

[Kernel-packages] [Bug 1907200] Re: rtwpci driver blocks the system to enter PC10, stuck at PC3

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1907200

Title:
  rtwpci driver blocks the system to enter PC10, stuck at PC3

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

Bug description:
  [Impact]
  The deepest CPU package C-state is PC3 after rtwpci module is loaded.

  [Fix]
  The fix is from Realtek.
  They will upstream this fix with some other fixes later.

  [Test]
  Verified on RTL8723DE [10ec:d723] wifi card, and it enters PC10 during long 
idle.

  [Where problems could occur]
  The fix is pretty simple and small, and just increases the idle/active 
latency value. Nothing could went wrong in this case.

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

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

[Kernel-packages] [Bug 1906851] Re: Fix reading speed and duplex sysfs on igc device

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1906851

Title:
  Fix reading speed and duplex sysfs on igc device

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux-oem-5.6 source package in Focal:
  Confirmed
Status in linux source package in Groovy:
  Fix Committed
Status in linux-oem-5.10 source package in Groovy:
  Won't Fix
Status in linux-oem-5.6 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]
  Reading speed and duplex sysfs on igc device when it's runtime suspended
  will make it stops working. Even kernel panic sometimes.

  [Fix]
  If igc device is runtime suspended, it means link isn't up, so we can
  just report speed as -1 and duplex as unknown.

  [Test]
  $ cat /sys/class/net/*/speed
  Then we'll see:
  [  123.449883] igc :03:00.0 enp3s0: PCIe link lost, device now detached
  [  123.450052] BUG: kernel NULL pointer dereference, address: 0008

  With the fix applied,
  $ cat /sys/class/net/*/speed
  -1

  [Where problems could occur]
  Not at all. Reading register when device is runtime suspended is just
  wrong. The fix prevents it from happening.

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

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

[Kernel-packages] [Bug 1904991] Re: [SRU][OEM-5.6] UBUNTU: SAUCE: Fix brightness control on BOE 2270 panel

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1904991

Title:
  [SRU][OEM-5.6] UBUNTU: SAUCE: Fix brightness control on BOE 2270 panel

Status in HWE Next:
  New
Status in HWE Next groovy series:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.10 package in Ubuntu:
  New
Status in linux-oem-5.6 package in Ubuntu:
  New
Status in linux source package in Focal:
  Incomplete
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux-oem-5.6 source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Committed
Status in linux source package in Hirsute:
  Incomplete

Bug description:
  [Impact]
  BOE 2270 panel is used by several models of ThinkPads.
  This brightness can not be controlled by default PWM.

  [Fix]
  The panel claims both PWM and AUX supports.
  But actually PWM works on SDR mode, AUX works on HDR mode.
  Intel i915 driver got a new SDR support to use PWM by maintainer, still in 
upstream review.
  To fix this on certain project, use a quirk first to fix this.
  The maintainer's fix can be backported in future.

  [Test Case]
  Backlight brightness can be changed.

  [Regression Potential]
  Low,
  Fix for specific panel ID, no effects for others.
  Since this is temporary quirk, it will go to oem-5.6 only.

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

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

[Kernel-packages] [Bug 1894778] Re: Cannot probe sata disk on sata controller behind VMD: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1894778

Title:
  Cannot probe sata disk on sata controller behind VMD: ata1.00: failed
  to IDENTIFY (I/O error, err_mask=0x4)

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux-oem-5.6 source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Committed
Status in linux-oem-5.10 source package in Groovy:
  Invalid
Status in linux-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  When booting with a certain platforms with boot disk attached to SATA
  bus behind Intel VMD controller, disk probing may fail with following
  error messages left in dmesg:

[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)

  [Fix]

  Upstream commit f6b7bb847ca8 ("PCI: vmd: Offset Client VMD MSI-X
  vectors") currently in vanilla kernel tree for v5.11.

  [Test Case]

  Check dmesg/lsblk for disk probe.

  For pci MSI address, check lspci output:

$ lspci -vvnn

Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee0  Data: 

  When it fails, the address is fee0. And with a patched kernel:

$ lspci -vvnn

Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee01000  Data: 

  [Where problems could occur]

  An unpatched kernel will not be able to probe SATA controllers moved
  behind VMD when VMD/RAID mode is enabled in BIOS, leaving disks
  attached on it completely unusable. With this change, kernel would
  then be able to probe them but may also suffer from issues that only
  occur under such configuration. However, the worst case is to move away
  sata disks from VMD bus as they are currently without this fix, so the
  risk here should be justified.

  == Previous SRU ==

  [SRU Justification]

  [Impact]

  When booting with a certain platforms with boot disk attached to SATA
  bus behind Intel VMD controller, disk probing may fail with following
  error messages left in dmesg:

    [ 6.163286] ata1.00: qc timeout (cmd 0xec)
    [ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)

  [Fix]

  Proposed kernel patch https://patchwork.kernel.org/patch/11758345/

  [Test Case]

  Check dmesg/lsblk for disk probe.

  For pci MSI address, check lspci output:

    $ lspci -vvnn
    
    Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
    Address: fee0  Data: 

  When it fails, the address is fee0. And with a patched kernel:

    $ lspci -vvnn
    
    Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
    Address: fee01000  Data: 

  [Regression Potential]
  Low.  For previous NVMe based platforms, this patch brings no effective
  change for NVMe devices because they will still stay in fast-interrupt
  list.

  == Original Bug Description ==

  When booting with root filesystem on sata disks under Intel VMD mode,
  following errors printed in dmesg and no disk is found, nor booting
  into it:

    [ 6.163286] ata1.00: qc timeout (cmd 0xec)
    [ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    [ 6.483649] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    [ 16.659284] ata1.00: qc timeout (cmd 0xec)
    [ 16.661717] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    [ 16.663161] ata1: limiting SATA link speed to 1.5 Gbps
    [ 16.983890] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    [ 48.147294] ata1.00: qc timeout (cmd 0xec)
    [ 48.149737] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    [ 48.467889] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

    $ lspci
    ...
    1:e0:17.0 SATA controller: Intel Corporation Device a0d3 (rev 20)

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1909062] Re: qede: Kubernetes Internal DNS Failure due to QL41xxx NIC not supporting IPIP tx csum offload

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1909062

Title:
  qede: Kubernetes Internal DNS Failure due to QL41xxx NIC not
  supporting IPIP tx csum offload

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1909062

  [Impact]

  For users with QLogic QL41xxx series NICs, such as the FastLinQ
  QL41000 Series 10/25/40/50GbE Controller, when they upgrade from the
  4.15 kernel to the 5.4 kernel, Kubernetes Internal DNS requests will
  fail, due to these packets getting corrupted.

  Kubernetes uses IPIP tunnelled packets for internal DNS resolution,
  and this particular packet type is not supported for hardware tx
  checksum offload, and the packets end up corrupted when the qede
  driver attempts to checksum them.

  This only affects internal Kubernetes DNS, as regular DNS lookups to
  regular external domains will succeed, due to them not using IPIP
  packet types.

  [Fix]

  Marvell has developed a fix for the qede driver, which checks the
  packet type, and if it is IPPROTO_IPIP, then csum offloads are
  disabled for socket buffers of type IPIP.

  commit 5d5647dad259bb416fd5d3d87012760386d97530
  Author: Manish Chopra 
  Date: Mon Dec 21 06:55:30 2020 -0800
  Subject: qede: fix offload for IPIP tunnel packets
  Link: 
https://github.com/torvalds/linux/commit/5d5647dad259bb416fd5d3d87012760386d97530

  This commit landed in mainline in 5.11-rc3. The commit was accepted
  into upstream stable 4.14.215, 4.19.167, 5.4.89 and 5.10.7.

  Note, this SRU isn't targeted for Bionic due to tx csum offload
  support only landing in 5.0 and onward, meaning the 4.15 kernel still
  works even without this patch. Because of this, Bionic can pick the
  patch up naturally from upstream stable.

  [Testcase]

  The system must have a QLogic QL41xxx series NIC fitted, and needs to
  be a part of a Kubernetes cluster.

  Firstly, get a list of all devices in the system:

  $ sudo ifconfig

  Next, set all devices down with:

  $ sudo ifconfig  down

  Next, bring up the QLogic QL41xxx device:

  $ sudo ifconfig  up

  Then, attempt to lookup an internal Kubernetes domain:

  $ nslookup 

  Without the patch, the connection will time out:

  ;; connection timed out; no servers could be reached

  If we look at packet traces with tcpdump, we see it leaves the source,
  but never arrives at the destination.

  There is a test kernel available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf297772-test

  If you install it, then Kubernetes internal DNS lookups will succeed.

  [Where problems could occur]

  If a regression were to occur, then users of the qede driver would be
  affected. This is limited to those with QLogic QL41xxx series NICs.
  The patch explicitly checks for IPIP type packets, so only those
  particular packets would be affected.

  Since IPIP type packets are uncommon, it would not cause a total
  outage on regression, since most packets are not IPIP tunnelled. It
  could potentially cause problems for users who frequently handle VPN
  or Kubernetes internal DNS traffic.

  A workaround would be to use ethtool to disable tx csum offload for
  all packet types, or to revert to an older kernel.

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

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

[Kernel-packages] [Bug 1905663] Re: Add dpcd backlight control for 0x4c83 0x4f41

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1905663

Title:
  Add dpcd backlight control for 0x4c83 0x4f41

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  New
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux-oem-5.6 source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Committed
Status in linux source package in Hirsute:
  In Progress

Bug description:
  [Impact]
  There is a new OLED panel that is required to be listed in the EDID quirk to 
make its backlight work.

  [Fix]
  The commit adds its EDID to the quirk.
  https://lkml.org/lkml/2020/11/19/1564

  [Test]
  Verified on Dell's platform with this panel.

  [Where problems could occur]
  Only if this panel switches to use PWM mode only, and doesn't support DPCD 
backlight.

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

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

[Kernel-packages] [Bug 1907421] Re: [UBUNTU 21.04] vfio: pass DMA availability information to userspace

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1907421

Title:
  [UBUNTU 21.04] vfio: pass DMA availability information to userspace

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Confirmed
Status in linux source package in Groovy:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed

Bug description:
  Description:   vfio: pass DMA availability information to userspace
  Symptom:   vfio-pci device on s390 enters error state
  Problem:   Commit 492855939bdb added a limit to the number of concurrent
     DMA requests for a vfio container.  However, lazy unmapping in
     s390 can in fact cause quite a large number of outstanding DMA
     requests to build up prior to being purged, potentially the
     entire guest DMA space.  This results in unexpected errors seen
     in qemu such as 'VFIO_MAP_DMA failed: No space left on device'
  Solution:  The solution requires a change to both kernel and qemu - For
     the kernel, add the ability to provide the number of allowable
     DMA requests via the VFIO_IOMMU_GET_INFO ioctl.
  Reproduction:  Put a vfio-pci device on s390 under I/O load
  Upstream-ID:   a717072007e8aedd3f951726d8cf55454860b30d
     7d6e1329652ed971d1b6e0e7bea66fba5044e271

  Need also to be integrated into 20.10 and 20.04.

  OK, just to clarify we don't need to fix bionic for this one, but rather 
focal (20.04) and groovy (20.10).  Furthermore, for 20.04, 20.10 and 21.04 ONLY 
commit 7d6e1329652ed971d1b6e0e7bea66fba5044e271 is needed, the other was a 
pre-req that is already present.
  __

  SRU Justification:

  [Impact]

  * In case a vfio-pci device on s390x is under I/O load, vfio-pci
  device may end up in error state.

  * The commit 492855939bdb added a limit to the number of concurrent
  DMA requests for a vfio container.

  * However, lazy unmapping in s390x can in fact cause quite a large number of 
outstanding DMA requests
to build up prior to being purged - potentially the entire guest DMA space.

  * This results in unexpected errors seen in qemu such as 'VFIO_MAP_DMA
  failed: No space left on device'.

  * The solution requires a change to both kernel and qemu.

  * The kernel side of things is addressed by this SRU.

  * The fix adds the ability to provide the number of allowable DMA
  requests via VFIO_IOMMU_GET_INFO ioctl.

  * The actual fix comes with commit 7d6e1329652e, but another fix
  ccd59dce1a21 is needed to get it cleanly applied.

  [Fix]

  * ccd59dce1a21f473518bf273bdf5b182bab955b3 ccd59dce1a21 "vfio/type1:
  Refactor vfio_iommu_type1_ioctl()"

  * 7d6e1329652ed971d1b6e0e7bea66fba5044e271 7d6e1329652e "vfio iommu:
  Add dma available capability"

  [Test Case]

  * IBM Z or LinuxONE hardware with Ubuntu Server 20.10 installed.

  * PCIe adapters in place that provide vfio, like RoCE Express 2.

  * A KVM host needs to be setup and a KVM guest (use again 20.10) that
  uses vfio.

  * Generate I/O that flows through the vf and watch out for error like
  'VFIO_MAP_DMA failed: No space left on device' in the log.

  [Regression Potential]

  * The first patch ccd59dce1a21 modifies the common code file
  drivers/vfio/vfio_iommu_type1.c quity significantly.

  * But the reason is not that it introduces a lot of new things, it's a
  refactoring patch.

  * Nevertheless if done in a bad way it can significantly harm the IO
  memory management of virtual function adapters.

  * In worst case it may break them entirely, instead of 'just' exeeding
  the entire DMA space.

  * Things could also go wrong while doing the mapping and unmapping of
  DMA, that may even have an impact beyond vf adapters - harming other
  DMA devices.

  * The handling of dirty pages is also touched and the ioctl itself -
  which is important to keep the control of the devices.

  * But as said before, it re-factoring work, it's upstream accepted
  since 5.9 and the provenance shows that many engineers had an eye on
  these changes.

  * The second patch 7d6e1329652e - that inclides the needed fix - comes
  with far less

[Kernel-packages] [Bug 1906128] Re: Touchpad not detected on ByteSpeed C15B laptop

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1906128

Title:
  Touchpad not detected on ByteSpeed C15B laptop

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Committed
Status in linux source package in Hirsute:
  In Progress

Bug description:
  [Impact]
  Touchpad on a ByteSpeed C15B laptop is not working.
  User will need to add i8042.noloop=1 to boot options to make it work.

  [Fix]
  * a48491c65b513e ("Input: i8042 - add ByteSpeed touchpad to noloop table")

  This fix can be cherry-picked into all affected releases.

  [Test Case]
  Test kernel for Bionic / Focal can be found here:
  https://people.canonical.com/~phlin/kernel/lp-1906128-C15B/

  And they have been tested with positive test results.

  [Where problems could occur]
  The fix is just a small and simple hardware quirk. I can't think of any 
potential problem for now.

  == Original Bug Report ==
  Touchpad hardware is OK and works for Win10.  Not working for live disc, not 
for 18.04 and not for 20.04 after upgrading.  I've attached a Logitech wireless 
mouse with its USB adapter and that works.   Bluetooth is also missing, but I 
have not started trying to skull that out.  I'm happy to help try debugging 
things, and to help resolve the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-54-generic 5.4.0-54.60
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tom1395 F pulseaudio
   /dev/snd/controlC0:  tom1395 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 28 19:09:05 2020
  InstallationDate: Installed on 2020-01-26 (307 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: ByteSpeed LLC ByteSpeed Laptop C15B
  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-54-generic 
root=UUID=07b919ee-c6ad-41a5-9c64-df3c8e477b6f ro quiet splash i8042.reset 
i8042.nomux i8042.nopnp i8042noloop noapic vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-54-generic N/A
   linux-backports-modules-5.4.0-54-generic  N/A
   linux-firmware1.187.4
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-11-25 (3 days ago)
  dmi.bios.date: 03/18/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C15B.616
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: C15B
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: ByteSpeed LLC
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC15B.616:bd03/18/2014:svnByteSpeedLLC:pnByteSpeedLaptopC15B:pvr1.0:rvnPEGATRONCORPORATION:rnC15B:rvr1.0:cvnByteSpeedLLC:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: PEGA Family
  dmi.product.name: ByteSpeed Laptop C15B
  dmi.product.sku: 0
  dmi.product.version: 1.0
  dmi.sys.vendor: ByteSpeed LLC

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

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

[Kernel-packages] [Bug 1910102] Re: Enable mute and micmute LED on HP EliteBook 850 G7

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1910102

Title:
  Enable mute and micmute LED on HP EliteBook 850 G7

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Committed
Status in linux-oem-5.10 source package in Groovy:
  Invalid

Bug description:
  [Impact]
  Mute and micmute LED on HP EliteBook 850 G7 don't reflect the mute
  status.

  [Fix]
  Apply an HDA quirk to let HP EliteBook 850 G7 use codec GPIO to control
  LED.

  [Test]
  With the patch applied, both mute and micmute LED can be lit when audio
  output or input is muted, respectively.
   
  [Where problems could occur]
  This quirk is specific to one model. It's not likely to regress other
  systems.

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

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

[Kernel-packages] [Bug 1903682] Re: NULL pointer dereference when configuring multi-function with devfn != 0 before devfn == 0

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1903682

Title:
  NULL pointer dereference when configuring multi-function with devfn !=
  0 before devfn == 0

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Committed
Status in linux source package in Hirsute:
  Triaged

Bug description:
  SRU Justification:
  ==

  [Impact]

  * While handling multifunction devices in zPCI the UID of the PCI
  function with function number 0 (that always exists according to the
  PCI spec) is taken as domain number.

  * Therefore if hot plugging functions with a function number larger
  than 0 are used before function 0, these need to be held in standby
  before creating the domain and bus.

  * This has been tested during development of this feature using a
  patched QEMU and in DPM, but unfortunately never in
  classic/traditional HMC mode.

  * On a classic/traditional mode machine with a multi-function device,
  and hot plug ("Reassign I/O Path") of the FID of the second port of
  the LPAR, any additional hotplug (and even just deconfiguring a PCI
  device) will hang - and hotplug now makes the entire Linux instance
  unresponsive.

  * The reason for this is a NULL pointer dereference - inc case
  configuring multi-function with devfn != 0 before devfn == 0.

  * This issue was introduced with the topology-aware PCI enumeration
  code.

  [Fix]

  * 0b2ca2c7d0c9e2731d01b6c862375d44a7e13923 0b2ca2c7d0c9 "s390/pci: fix
  hot-plug of PCI function missing bus"

  [Test Case]

  * IBM Z or LinuxONE hardware, equipped with hot-pluggable, multi-
  functional PCIe cards (like for example RoCE Express 2 adapters) in
  classic/traditional mode.

  * An Ubuntu OS running in LPAR, that comes with a kernel that includes
  the topology-aware PCI enumeration code (like for example 20.04.1 w/o
  further updates or 20.10 GA kernel).

  * Now on a system that is in classic/traditional mode, hot plug
  ("Reassign I/O Path") a multi-function device, but using the FID of
  the second port.

  [Regression Potential]

  * There is at least some regression risk, but I consider it as low,
  because:

  * Even is the modification is a single if statement (that spans two
  lines) in 'zpci_event_availability' it could harm the zPCI event
  management even more, in worst case it could break hot plug not only
  for systems in classic/traditional mode, but also in DPM mode (and
  making the system hang) or for all ports.

  * In such a case no enabling / disabling of devices would be possible.

  * But the fix is very simple and straight-forward, it checks
  zdev->zbus->bus for being NULL and in such a case break the function -
  means breaking instead of calling the PCI common code
  pci_scan_single_device() with the NULL pointer.

  * PCIe devices are usually more optional devices on s390x (compared to
  CCW and OSA devices for network) and this affects the zPCI subsystem
  only, which is unique to s390x.

  [Other]

  * The patch got upstream accepted with kernel v5.10-rc3, hence it will
  land sooner or later in Hirsute.

  * It was initially planned to address groovy via 5.8 upstream stable
  update, and in fact the patch was already marked for this, but it
  didn't made it because 5.8 reached it's EOL already.

  * Hence in addition to the already submitted SRU for focal, this is now a 
separate SRU for groovy.
  __

  Background:

  When handling multifunction devices in zPCI we take the
  UID of the PCI function with function number 0
  (that always exists according to the PCI spec)
  as domain number.
  Therefore when hot plugging functions with function
  number larger than 0 before function 0, we need
  to hold these in standby before creating the
  domain and bus.

  This has been tested during feature development
  using a patched QEMU and with DPM but never in Classic
  Mode.

  Reproduction:

  This issue was introduced with the Topology aware PCI
  Enumeration code so test with a Linux supporting
  that feature. E.g. Upstream, Devel Driver etc.

  On a Classic Mode machine with a multi-function device,
  hot plug

[Kernel-packages] [Bug 1912676] Re: Fix regression introduced by codec PM change

2021-01-28 Thread Timo Aaltonen

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

Title:
   Fix regression introduced by codec PM change

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Confirmed
Status in linux-oem-5.10 source package in Groovy:
  Invalid

Bug description:
  [Impact]
  After the codec PM optimization, laptops with SOF may take very long to
  suspend. In addition to that, HDA may not be able to be runtim suspended
  again after resume from hibernation.

  [Fix]
  Prevent the SOF driver touches codec during system suspend, and properly
  refcount the PM usage counter.

  [Test]
  On an affected SOF system, it takes 5 mins to suspend.
  On another affected HDA system, S4 resume causes high power consumption
  becuase HDA controller can't be runtime suspended.

  Both issues are gone by applying these patches.

  [Where problems could occur]
  If somehow any laptop depends on the old behavior to work properly, this
  can break them. It's highly unlikely though.

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

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

[Kernel-packages] [Bug 1910291] Re: update ENA driver, incl. new ethtool stats

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

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

Title:
  update ENA driver, incl. new ethtool stats

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Committed

Bug description:
  Update Amazon ENA driver in {bionic,focal,groovy}-generic with latest
  upstream commits from mainline applicable to each series, including
  "net: ena: ethtool: Add new device statistics".

  [Impact]

   * Supplies ENA device stats requested by AWS.

   * Supplies general bug fixes for the ENA driver.

  [Test Case]

  Use of any ENA-enabled instance is a basic regression test.  The "new
  ethtool stats" can be verified by observing additional entries listed
  by ;ethtool -S'.

  [Regression Potential]

  Low: These commits are all mainline cherry-picks or trivial (file
  rename) backports.  Only the Amazon ENA driver is affected.

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

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

[Kernel-packages] [Bug 1910291] Re: update ENA driver, incl. new ethtool stats

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

** Tags added: verification-needed-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/1910291

Title:
  update ENA driver, incl. new ethtool stats

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Committed

Bug description:
  Update Amazon ENA driver in {bionic,focal,groovy}-generic with latest
  upstream commits from mainline applicable to each series, including
  "net: ena: ethtool: Add new device statistics".

  [Impact]

   * Supplies ENA device stats requested by AWS.

   * Supplies general bug fixes for the ENA driver.

  [Test Case]

  Use of any ENA-enabled instance is a basic regression test.  The "new
  ethtool stats" can be verified by observing additional entries listed
  by ;ethtool -S'.

  [Regression Potential]

  Low: These commits are all mainline cherry-picks or trivial (file
  rename) backports.  Only the Amazon ENA driver is affected.

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

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

[Kernel-packages] [Bug 1910639] Re: DMI entry syntax fix for Pegatron / ByteSpeed C15B

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

** Tags added: verification-needed-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/1910639

Title:
  DMI entry syntax fix for Pegatron / ByteSpeed C15B

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Committed
Status in linux source package in Hirsute:
  Incomplete

Bug description:
  [Impact]
  Upstream reports that when compiling the kernel with a48491c65b51 ("Input: 
i8042 - add ByteSpeed touchpad to noloop table"), g++ will complain about:
  drivers/input/serio/i8042-x86ia64io.h:225:3: error: ‘.matches’ designator 
used multiple times in the same initializer list

  C99 semantics is that last duplicated initialiser wins,
  so DMI entry gets overwritten.

  [Fix]
  * a3a9060ecad030 ("Input: i8042 - unbreak Pegatron C15B") in linux-next

  This can be cherry-picked into all the affected series.
  Note that patch for bug 1906128 should be applied first.

  [Test]
  I didn't get this error while building the test kernels for bug 1906128 on 
builder kathleen, with fakeroot commands.

  So the only thing that I can test is to build them again and make sure
  there is no other issues.

  [Where problems could occur]
  If this fix is incorrect it might affect the touchpad support on Pegatron / 
ByteSpeed C15B laptop.

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

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

[Kernel-packages] [Bug 1910561] Re: Fix right sounds and mute/micmute LEDs for HP ZBook Fury 15/17 G7 Mobile Workstation

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1910561

Title:
  Fix right sounds and mute/micmute LEDs for HP ZBook Fury 15/17 G7
  Mobile Workstation

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Committed
Status in linux-oem-5.10 source package in Groovy:
  Invalid
Status in linux source package in Hirsute:
  In Progress
Status in linux-oem-5.10 source package in Hirsute:
  Invalid

Bug description:
  [Impact]
  * Mute and micmute LED are not work accurately on HP ZBook Fury 15/17 G7 
Mobile Workstation when muting corresponding audio devices.
  * The right channel of internal speaker has not sound.

  [Fix]
  Apply ALC285_FIXUP_HP_GPIO_AMP_INIT quirk to expose GPIOs for controlling 
LEDs and initialing AMP.

  [Test]
  Built a test kernel with applying this patch, the mute/micmute LEDs are work 
as expected.
  The internal speaker could play the sounds from left and right channels.

  [Where problems could occur]
  This quirk is specific for these two platforms. It should not cause the 
regression to other systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1910561/+subscriptions

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

[Kernel-packages] [Bug 1910541] Re: [SRU][G/H/U/OEM-5.10] re-enable s0ix of e1000e

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1910541

Title:
  [SRU][G/H/U/OEM-5.10] re-enable s0ix of e1000e

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Committed
Status in linux source package in Hirsute:
  In Progress

Bug description:
  [Impact]
  Due to s2idle failure on e1000e driver in ME enabled system, it disabled s0ix.
  Finally latest kernel accepted the bump up timeout value to fixed the issue.
  s0ix can be supported again.

  [Fix]
  Rebase the sauce patch to upstream patch, then support s0ix of e1000e.

  [Test Case]
  s2idle can work normally on ME enabled platform.

  [Where problems could occur]
  s2idle may fail to suspend on 2nd times.

  These patches are trying to revert the disabled s0ix patch in 5.8+,
  no need for 5.7- kernels.

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

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

[Kernel-packages] [Bug 1912803] Re: switch to an autogenerated nvidia series based core via dkms-versions

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

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

Title:
  switch to an autogenerated nvidia series based core via dkms-versions

Status in linux package in Ubuntu:
  In Progress
Status in linux-restricted-modules package in Ubuntu:
  In Progress

Bug description:
  Switch the linux-restricted-modules payload to an autogenerated core
  based on the contents of the debian/dkms-versions.

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

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

[Kernel-packages] [Bug 1910639] Re: DMI entry syntax fix for Pegatron / ByteSpeed C15B

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

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

Title:
  DMI entry syntax fix for Pegatron / ByteSpeed C15B

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Committed
Status in linux source package in Hirsute:
  Incomplete

Bug description:
  [Impact]
  Upstream reports that when compiling the kernel with a48491c65b51 ("Input: 
i8042 - add ByteSpeed touchpad to noloop table"), g++ will complain about:
  drivers/input/serio/i8042-x86ia64io.h:225:3: error: ‘.matches’ designator 
used multiple times in the same initializer list

  C99 semantics is that last duplicated initialiser wins,
  so DMI entry gets overwritten.

  [Fix]
  * a3a9060ecad030 ("Input: i8042 - unbreak Pegatron C15B") in linux-next

  This can be cherry-picked into all the affected series.
  Note that patch for bug 1906128 should be applied first.

  [Test]
  I didn't get this error while building the test kernels for bug 1906128 on 
builder kathleen, with fakeroot commands.

  So the only thing that I can test is to build them again and make sure
  there is no other issues.

  [Where problems could occur]
  If this fix is incorrect it might affect the touchpad support on Pegatron / 
ByteSpeed C15B laptop.

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

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

[Kernel-packages] [Bug 1912427] Re: HD Audio Device PCI ID for the Intel Cometlake-R platform

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1912427

Title:
  HD Audio Device PCI ID for the Intel Cometlake-R platform

Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Committed
Status in linux source package in Hirsute:
  In Progress

Bug description:
  [Impact]
  Intel Cometlake-R platform has a new ID, have to include it in hda driver

  [Fix]
  https://lkml.org/lkml/2021/1/14/1418

  [Test]
  Verified on CML-R platforms.

  [Where problems could occur]
  It should be pretty safe to include a new ID

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

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

[Kernel-packages] [Bug 1911001] Re: Use DCPD to control HP DreamColor panel

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1911001

Title:
  Use DCPD to control HP DreamColor panel

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Committed
Status in linux-oem-5.10 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]
  Cannot change brightness on HP ZBook Fury with certain panel.

  [Fix]
  Add the panel to DPCD quirk table to use DPCD to control the panel
  backlight.

  [Test]
  Changing backlight sysfs doesn't change the display brightness.
  With the patch applied, changing sysfs backlight can really change the
  display brightness.

  [Where problems could occur]
  This fix is specific to a single panel, so it's not likely to cause any
  regression to other devices.

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

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

[Kernel-packages] [Bug 1912803] Re: switch to an autogenerated nvidia series based core via dkms-versions

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

** Tags added: verification-needed-groovy

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

Title:
  switch to an autogenerated nvidia series based core via dkms-versions

Status in linux package in Ubuntu:
  In Progress
Status in linux-restricted-modules package in Ubuntu:
  In Progress

Bug description:
  Switch the linux-restricted-modules payload to an autogenerated core
  based on the contents of the debian/dkms-versions.

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

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

[Kernel-packages] [Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)

2021-01-28 Thread Juerg Haefliger

** Description changed:

+ [Impact]
+ 
+ A mix of incoming TCP traffic, forwarding packets and saturating the
+ link results in lan78xx TX queue timeouts which brings the network
+ interface down.
+ 
+ [Test Case]
+ 
+ Se comment #99 below.
+ 
+ [Where Problems Could Occur]
+ 
+ Probably lost or corrupted TCP packets. Most likely not worse than what
+ we're currently seeing.
+ 
+ [Original Description]
+ 
  Desciption changed:
  Raspberry Pi 3 network partially dies (transmission doesn't work, reception 
still does) shortly after a burst of network load over IPv6, when IPv6 
connectivity is provided by a tunnel from tunnelbroker.net. The triggering load 
is typically an HTTP(S) download, and replication can be done without actually 
saving the file (wget -O /dev/null ...). Problem happens within downloading ~10 
GB, usually withinthe first 1 GB of traffic)
- Replication is 100% as long as _all_ of the following conditions are met 
+ Replication is 100% as long as _all_ of the following conditions are met
  - 6in4 tunnel to HE.net set up with netplan
  - ipv6 rules applied (netfilter-persistent)
  - ipv6 forwarding enabled (edit /etc/sysctl.conf)
- 
  
  kern.log message that appears after a while:
  
  Feb  4 23:42:59 rpi3 kernel: [  571.878359] [ cut here 
]
  Feb  4 23:42:59 rpi3 kernel: [  571.878420] NETDEV WATCHDOG: eth0 (lan78xx): 
transmit queue 0 timed out
  Feb  4 23:42:59 rpi3 kernel: [  571.878550] WARNING: CPU: 3 PID: 0 at 
net/sched/sch_generic.c:447 dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878557] Modules linked in: sit tunnel4 
ip_tunnel bridge stp llc ip6table_filter ip6_tables xt_tcpudp xt_conntrack 
nf_conntrack iptable_filter bpfilter nls_ascii dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic ecc brcmfmac brcmutil 
cfg80211 bcm2835_v4l2(CE) bcm2835_mmal_vchiq(CE) input_leds vc_sm_cma(CE) 
v4l2_common videobuf2_vmalloc spidev videobuf2_memops videobuf2_v4l2 
raspberrypi_hwmon videobuf2_common videodev mc uio_pdrv_genirq uio sch_fq_codel 
jool(OE) jool_common(OE) nf_defrag_ipv6 nf_defrag_ipv4 ip_tables x_tables 
autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 
multipath linear hid_generic usbhid crct10dif_ce sdhci_iproc phy_generic fixed 
aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64
  Feb  4 23:42:59 rpi3 kernel: [  571.878774] CPU: 3 PID: 0 Comm: swapper/3 
Tainted: G C OE 5.3.0-1017-raspi2 #19-Ubuntu
  Feb  4 23:42:59 rpi3 kernel: [  571.878781] Hardware name: Raspberry Pi 3 
Model B Plus Rev 1.3 (DT)
  Feb  4 23:42:59 rpi3 kernel: [  571.878789] pstate: 6045 (nZCv daif +PAN 
-UAO)
  Feb  4 23:42:59 rpi3 kernel: [  571.878800] pc : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878807] lr : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878812] sp : 1001bd60
  Feb  4 23:42:59 rpi3 kernel: [  571.878817] x29: 1001bd60 x28: 
0140
  Feb  4 23:42:59 rpi3 kernel: [  571.878827] x27:  x26: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878836] x25: 8ecbefa4e000 x24: 
305e0f529018
  Feb  4 23:42:59 rpi3 kernel: [  571.878845] x23:  x22: 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878853] x21: 8ecbefa4e480 x20: 
305e0f807000
  Feb  4 23:42:59 rpi3 kernel: [  571.878862] x19:  x18: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878871] x17: 10fd8218 x16: 
305e0e30efb8
  Feb  4 23:42:59 rpi3 kernel: [  571.878879] x15: 8ecbf922a290 x14: 

  Feb  4 23:42:59 rpi3 kernel: [  571.87] x13:  x12: 
305e0f944000
  Feb  4 23:42:59 rpi3 kernel: [  571.878897] x11: 305e0f82d000 x10: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878905] x9 : 0004 x8 : 
017f
  Feb  4 23:42:59 rpi3 kernel: [  571.878913] x7 :  x6 : 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878921] x5 :  x4 : 
0008
  Feb  4 23:42:59 rpi3 kernel: [  571.878929] x3 : 305e0ee15750 x2 : 
0004
  Feb  4 23:42:59 rpi3 kernel: [  571.878937] x1 : 6abb42c67c954600 x0 : 

  Feb  4 23:42:59 rpi3 kernel: [  571.878946] Call trace:
  Feb  4 23:42:59 rpi3 kernel: [  571.878955]  dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878967]  call_timer_fn+0x3c/0x178
  Feb  4 23:42:59 rpi3 kernel: [  571.878977]  __run_timers.part.0+0x200/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878985]  run_timer_softirq+0x40/0x78
  Feb  4 23:42:59 rpi3 kernel: [  571.878995]  __do_softirq+0x168/0x384
  Feb  4 23:42:59 rpi3 kernel: [  571.879007]  irq_exit+0xb0/0xe8
  Feb  4 23:42:59 rpi3 kernel: [  571.879020]  __handle_domain_irq+0x70/0xc0
  Feb  4 23:42:59 rpi3 kernel: [  571.879028]  
bcm2836_arm_irqchip_handle_irq+0x74/0xe0

[Kernel-packages] [Bug 1830360] Re: cpuset_load_balance from controller test suite in LTP failed

** Tags added: sru-20210104

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

Title:
  cpuset_load_balance from controller test suite in LTP failed

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  New
Status in linux source package in Disco:
  Won't Fix

Bug description:
  Issue found on Disco with node glameow:
   startup='Fri May 24 10:24:55 2019'
   cpuset_load_balance 1 TINFO: general group load balance test
   cpuset_load_balance 1 TINFO: root group info:
   cpuset_load_balance 1 TINFO:  sched load balance: 0
   cpuset_load_balance 1 TINFO: general group info:
   cpuset_load_balance 1 TINFO:  cpus: -
   cpuset_load_balance 1 TINFO:  sched load balance: 1
   cpuset_load_balance 1 TFAIL: load balance test failed.
   cpuset_load_balance 3 TINFO: general group load balance test
   cpuset_load_balance 3 TINFO: root group info:
   cpuset_load_balance 3 TINFO:  sched load balance: 0
   cpuset_load_balance 3 TINFO: general group info:
   cpuset_load_balance 3 TINFO:  cpus: 1
   cpuset_load_balance 3 TINFO:  sched load balance: 0
   cpuset_load_balance 3 TFAIL: load balance test failed.
   cpuset_load_balance 5 TINFO: general group load balance test
   cpuset_load_balance 5 TINFO: root group info:
   cpuset_load_balance 5 TINFO:  sched load balance: 1
   cpuset_load_balance 5 TINFO: general group info:
   cpuset_load_balance 5 TINFO:  cpus: -
   cpuset_load_balance 5 TINFO:  sched load balance: 1
   cpuset_load_balance 5 TFAIL: load balance test failed.
   cpuset_load_balance 7 TINFO: general group load balance test
   cpuset_load_balance 7 TINFO: root group info:
   cpuset_load_balance 7 TINFO:  sched load balance: 1
   cpuset_load_balance 7 TINFO: general group info:
   cpuset_load_balance 7 TINFO:  cpus: 1
   cpuset_load_balance 7 TINFO:  sched load balance: 1
   cpuset_load_balance 7 TFAIL: load balance test failed.
   cpuset_load_balance 9 TINFO: general group load balance test
   cpuset_load_balance 9 TINFO: root group info:
   cpuset_load_balance 9 TINFO:  sched load balance: 0
   cpuset_load_balance 9 TINFO: general group info:
   cpuset_load_balance 9 TINFO:  cpus: 1,2
   cpuset_load_balance 9 TINFO:  sched load balance: 0
   cpuset_load_balance 9 TFAIL: load balance test failed.
   cpuset_load_balance 11 TINFO: general group load balance test
   cpuset_load_balance 11 TINFO: root group info:
   cpuset_load_balance 11 TINFO:  sched load balance: 0
   cpuset_load_balance 11 TINFO: general group info:
   cpuset_load_balance 11 TINFO:  cpus: 1,2
   cpuset_load_balance 11 TINFO:  sched load balance: 1
   cpuset_load_balance 11 TFAIL: load balance test failed.
   cpuset_load_balance 13 TINFO: general group load balance test
   cpuset_load_balance 13 TINFO: root group info:
   cpuset_load_balance 13 TINFO:  sched load balance: 0
   cpuset_load_balance 13 TINFO: general group info:
   cpuset_load_balance 13 TINFO:  cpus: 
0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39
   cpuset_load_balance 13 TINFO:  sched load balance: 1
   cpuset_load_balance 13 TFAIL: load balance test failed.
   cpuset_load_balance 15 TINFO: general group load balance test
   cpuset_load_balance 15 TINFO: root group info:
   cpuset_load_balance 15 TINFO:  sched load balance: 0
   cpuset_load_balance 15 TINFO: general group1 info:
   cpuset_load_balance 15 TINFO:  cpus: 1
   cpuset_load_balance 15 TINFO:  sched load balance: 1
   cpuset_load_balance 15 TINFO: general group2 info:
   cpuset_load_balance 15 TINFO:  cpus: 0
   cpuset_load_balance 15 TINFO:  sched load balance: 1
   cpuset_load_balance 15 TINFO: CPU hotplug: none
   cpuset_load_balance 15 TFAIL: load balance test failed.
   cpuset_load_balance 17 TINFO: general group load balance test
   cpuset_load_balance 17 TINFO: root group info:
   cpuset_load_balance 17 TINFO:  sched load balance: 0
   cpuset_load_balance 17 TINFO: general group1 info:
   cpuset_load_balance 17 TINFO:  cpus: 1,2
   cpuset_load_balance 17 TINFO:  sched load balance: 1
   cpuset_load_balance 17 TINFO: general group2 info:
   cpuset_load_balance 17 TINFO:  cpus: 0-3
   cpuset_load_balance 17 TINFO:  sched load balance: 0
   cpuset_load_balance 17 TINFO: CPU hotplug: none
   cpuset_load_balance 17 TFAIL: load balance test failed.
   cpuset_load_balance 19 TINFO: general group load balance test
   cpuset_load_balance 19 TINFO: root group info:
   cpuset_load_balance 19 TINFO:  sched load balance: 0
   cpuset_load_balance 19 TINFO: general group1 info:
   cpuset_load_balance 19 TINFO:  cpus: 1,2
   cpuset_load_balance 19 TINFO:  sched load balance: 1
   cpuset_load_balance 19 TINFO: general group2 info:

[Kernel-packages] [Bug 1910736] Re: package libnvidia-compute-390 (not installed) failed to install/upgrade: paylaşılan '/etc/OpenCL/vendors/nvidia.icd' dosyasının üzerine yazılmaya çalışılıyor, dosya

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package libnvidia-compute-390 (not installed) failed to
  install/upgrade: paylaşılan '/etc/OpenCL/vendors/nvidia.icd'
  dosyasının üzerine yazılmaya çalışılıyor, dosya libnvidia-
  compute-390:amd64 paketinin diğer örneklerinden farklı

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  nvidia problem

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libnvidia-compute-390 (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Jan  8 13:48:05 2021
  ErrorMessage: paylaşılan '/etc/OpenCL/vendors/nvidia.icd' dosyasının üzerine 
yazılmaya çalışılıyor, dosya libnvidia-compute-390:amd64 paketinin diğer 
örneklerinden farklı
  InstallationDate: Installed on 2021-01-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.2
  SourcePackage: nvidia-graphics-drivers-390
  Title: package libnvidia-compute-390 (not installed) failed to 
install/upgrade: paylaşılan '/etc/OpenCL/vendors/nvidia.icd' dosyasının üzerine 
yazılmaya çalışılıyor, dosya libnvidia-compute-390:amd64 paketinin diğer 
örneklerinden farklı
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1910665] Re: package nvidia-dkms-390 390.138-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exi

2021-01-28 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package nvidia-dkms-390 390.138-0ubuntu0.20.04.1 failed to
  install/upgrade: installed nvidia-dkms-390 package post-installation
  script subprocess returned error exit status 10

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  Wifi is not beeen working the update is not getting completed. Now
  what to do about it?

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-dkms-390 390.138-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18
  Uname: Linux 5.8.0-34-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Jan  8 12:03:49 2021
  ErrorMessage: installed nvidia-dkms-390 package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2020-11-09 (59 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.2
  SourcePackage: nvidia-graphics-drivers-390
  Title: package nvidia-dkms-390 390.138-0ubuntu0.20.04.1 failed to 
install/upgrade: installed nvidia-dkms-390 package post-installation script 
subprocess returned error exit status 10
  UpgradeStatus: Upgraded to focal on 2020-12-30 (9 days ago)

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

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

[Kernel-packages] [Bug 1910665] Re: package nvidia-dkms-390 390.138-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exi

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package nvidia-dkms-390 390.138-0ubuntu0.20.04.1 failed to
  install/upgrade: installed nvidia-dkms-390 package post-installation
  script subprocess returned error exit status 10

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  Wifi is not beeen working the update is not getting completed. Now
  what to do about it?

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-dkms-390 390.138-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18
  Uname: Linux 5.8.0-34-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Jan  8 12:03:49 2021
  ErrorMessage: installed nvidia-dkms-390 package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2020-11-09 (59 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.2
  SourcePackage: nvidia-graphics-drivers-390
  Title: package nvidia-dkms-390 390.138-0ubuntu0.20.04.1 failed to 
install/upgrade: installed nvidia-dkms-390 package post-installation script 
subprocess returned error exit status 10
  UpgradeStatus: Upgraded to focal on 2020-12-30 (9 days ago)

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

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

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

This change was made by a bot.

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

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

Title:
  ouchpad doesn't work properly after Ubuntu Installation

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Touchpad' incorrectly detected in 'Lenovo s740' after the ubuntu
  installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-60-generic 5.4.0-60.67
  ProcVersionSignature: Ubuntu 5.4.0-60.67-generic 5.4.78
  Uname: Linux 5.4.0-60-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  felipe 1451 F pulseaudio
   /dev/snd/pcmC0D0p:   felipe 1451 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 13 21:52:13 2021
  InstallationDate: Installed on 2021-01-07 (6 days ago)
  InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
  MachineType: LENOVO 81RM
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-60-generic 
root=UUID=32be46bd-d75e-4c0e-a754-56d7e63881ba ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-60-generic N/A
   linux-backports-modules-5.4.0-60-generic  N/A
   linux-firmware1.187.7
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2021-01-08 (5 days ago)
  dmi.bios.date: 07/15/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BYCN36WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40688 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga S740-14IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrBYCN36WW:bd07/15/2020:svnLENOVO:pn81RM:pvrLenovoYogaS740-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrLenovoYogaS740-14IIL:
  dmi.product.family: Yoga S740-14IIL
  dmi.product.name: 81RM
  dmi.product.sku: LENOVO_MT_81RM_BU_idea_FM_Yoga S740-14IIL
  dmi.product.version: Lenovo Yoga S740-14IIL
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1829995] Re: getaddrinfo_01 from ipv6_lib test suite in LTP failed

** Tags added: sru-20210104

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

Title:
  getaddrinfo_01 from ipv6_lib test suite in LTP failed

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Bionic:
  Incomplete
Status in linux-aws source package in Bionic:
  New
Status in linux source package in Eoan:
  New
Status in linux-aws source package in Eoan:
  New

Bug description:
  startup='Wed May 22 08:02:52 2019'
  getaddrinfo_011  TPASS  :  getaddrinfo IPv4 basic lookup
  getaddrinfo_012  TFAIL  :  getaddrinfo_01.c:140: getaddrinfo IPv4 
canonical name ("curly.maas") doesn't match hostname ("curly")
  getaddrinfo_013  TFAIL  :  getaddrinfo_01.c:578: getaddrinfo IPv6 basic 
lookup ("curly") returns -5 ("No address associated with hostname")
  tag=getaddrinfo_01 stime=1558512172 dur=1 exit=exited stat=1 core=no cu=0 cs=0

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-50-generic 4.15.0-50.54
  ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 22 02:57 seq
   crw-rw 1 root audio 116, 33 May 22 02:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   
  Date: Wed May 22 08:04:30 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-50-generic N/A
   linux-backports-modules-4.15.0-50-generic  N/A
   linux-firmware 1.173.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1836166] Re: cpuhotplug02 in cpuhotplug from ubuntu_ltp failed on C Moonshot ARM64

** Tags added: sru-20210104

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

Title:
  cpuhotplug02 in cpuhotplug from ubuntu_ltp failed on C Moonshot ARM64

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  Steps to run this test:
    git clone --depth=1 https://github.com/linux-test-project/ltp.git
    cd ltp; make autotools; ./configure; make; sudo make install
    echo "cpuhotplug02 cpuhotplug02.sh -c 1 -l 1" > /tmp/jobs
    sudo /opt/ltp/runltp -f /tmp/jobs

  <<>>
  incrementing stop
  Name:   cpuhotplug02
  Date:   Thu Jul 11 08:21:54 UTC 2019
  Desc:   What happens to a process when its CPU is offlined?

  CPU is 1
  sh: echo: I/O error
  cpuhotplug02 1 TFAIL: process did not change from CPU   1
  <<>>

  Test passed on ThunderX ARM64, probably a test case issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-25-generic 4.18.0-25.26
  ProcVersionSignature: User Name 4.18.0-25.26-generic 4.18.20
  Uname: Linux 4.18.0-25-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 11 06:57 seq
   crw-rw 1 root audio 116, 33 Jul 11 06:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13.4
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jul 11 08:22:09 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:

  ProcFB:

  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-25-generic N/A
   linux-backports-modules-4.18.0-25-generic  N/A
   linux-firmware 1.175.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1836167] Re: cpuhotplug03 in cpuhotplug from ubuntu_ltp failed on some testing nodes

** Tags added: sru-20210104

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

Title:
  cpuhotplug03 in cpuhotplug from ubuntu_ltp failed on some testing
  nodes

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  <<>>
  incrementing stop
  Name:   cpuhotplug03
  Date:   Thu Jul 11 08:31:48 UTC 2019
  Desc:   Do tasks get scheduled to a newly on-lined CPU?

  CPU is 1
  sh: echo: I/O error
  cpuhotplug03 1 TBROK: CPU1 cannot be offlined
  USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
  root  4642  0.0  0.0   2020   488 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4643  0.0  0.0   2020   480 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4644  0.0  0.0   2020   468 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4645  0.0  0.0   2020   488 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4646  0.0  0.0   2020   472 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4647  0.0  0.0   2020   480 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4648  0.0  0.0   2020   456 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4649  0.0  0.0   2020   508 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4650  0.0  0.0   2020   488 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4651  0.0  0.0   2020   472 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4652  0.0  0.0   2020   484 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4653  0.0  0.0   2020   496 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4654  0.0  0.0   2020   464 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4655  0.0  0.0   2020   492 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4656  0.0  0.0   2020   448 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4657  0.0  0.0   2020   472 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4661  0.0  0.0   7540   648 pts/0S08:31   0:00 grep 
cpuhotplug_do_spin_loop
  cpuhotplug03 1 TINFO: Onlining CPU 1
7 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
1 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
4 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
0 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
3 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
6 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
1 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
5 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
3 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
7 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
6 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
2 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
4 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
2 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
0 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
5 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  cpuhotplug03 1 TPASS: 2 cpuhotplug_do_spin_loop processes found onCPU1
  <<>>
  initiation_status="ok"
  duration=1 termination_type=exited termination_id=2 corefile=no
  cutime=1060 cstime=9
  <<>>

  
  Test passed on ThunderX ARM64, probably a test case issue.

  
  Steps to run this test:
git clone --depth=1 https://github.com/linux-test-project/ltp.git
cd ltp; make autotools; ./configure; make; sudo make install
echo "cpuhotplug03 cpuhotplug03.sh -c 1 -l 1" > /tmp/jobs
sudo /opt/ltp/runltp -f /tmp/jobs

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-25-generic 4.18.0-25.26
  ProcVersionSignature: User Name 4.18.0-25.26-generic 4.18.20
  Uname: Linux 4.18.0-25-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 11 06:57 seq
   crw-rw 1 root audio 116, 33 Jul 11 06:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13.4
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jul 11 08:22:51

[Kernel-packages] [Bug 1836169] Re: cpuhotplug04 in cpuhotplug from ubuntu_ltp failed on ARM64

** Tags added: sru-20210104

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

Title:
  cpuhotplug04 in cpuhotplug from ubuntu_ltp failed on ARM64

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Won't Fix

Bug description:
  This issue can be found on both ThunderX and Moonshot ARM64

  <<>>
  incrementing stop
  Name:   cpuhotplug04
  Date:   Thu Jul 11 08:34:50 UTC 2019
  Desc:   Does it prevent us from offlining the last CPU?

  sh: echo: I/O error
  cpuhotplug04 1 TFAIL: Could not offline cpu0
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=1 corefile=no
  cutime=9 cstime=4
  <<>>

  Steps to run this test:
git clone --depth=1 https://github.com/linux-test-project/ltp.git
cd ltp; make autotools; ./configure; make; sudo make install
echo "cpuhotplug04 cpuhotplug04.sh -l 1" > /tmp/jobs
sudo /opt/ltp/runltp -f /tmp/jobs

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-25-generic 4.18.0-25.26
  ProcVersionSignature: User Name 4.18.0-25.26-generic 4.18.20
  Uname: Linux 4.18.0-25-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 11 06:57 seq
   crw-rw 1 root audio 116, 33 Jul 11 06:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13.4
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jul 11 08:28:42 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-25-generic N/A
   linux-backports-modules-4.18.0-25-generic  N/A
   linux-firmware 1.175.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1836170] Re: cpuhotplug06 in cpuhotplug from ubuntu_ltp failed on C ARM64

** Tags added: sru-20210104

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

Title:
  cpuhotplug06 in cpuhotplug from ubuntu_ltp failed on C ARM64

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  This issue was only spotted on Moonshot ARM64, probably a test case
  issue:

  <<>>
  incrementing stop
  Name:   cpuhotplug06
  Date:   Thu Jul 11 08:38:03 UTC 2019
  Desc:   Does top work properly when CPU hotplug events occur?

  CPU is 1
  sh: echo: I/O error
  cpuhotplug06 1 TBROK: CPU1 cannot be offlined
   5221 pts/000:00:00 top
  <<>>
  initiation_status="ok"
  duration=1 termination_type=exited termination_id=2 corefile=no
  cutime=2 cstime=1
  <<>>

  Steps to run this test:
git clone --depth=1 https://github.com/linux-test-project/ltp.git
cd ltp; make autotools; ./configure; make; sudo make install
echo "cpuhotplug06 cpuhotplug06.sh -c 1 -l 1" > /tmp/jobs
sudo /opt/ltp/runltp -f /tmp/jobs

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-25-generic 4.18.0-25.26
  ProcVersionSignature: User Name 4.18.0-25.26-generic 4.18.20
  Uname: Linux 4.18.0-25-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 11 06:57 seq
   crw-rw 1 root audio 116, 33 Jul 11 06:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13.4
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jul 11 08:30:02 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-25-generic N/A
   linux-backports-modules-4.18.0-25-generic  N/A
   linux-firmware 1.175.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1837543] Re: crypto_user02 in crypto from ubuntu_ltp failed

** Tags added: sru-20210104

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

Title:
  crypto_user02 in crypto from ubuntu_ltp failed

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-aws source package in Bionic:
  Confirmed

Bug description:
  This is a new test, test will fail with:

  <<>>
  tag=crypto_user02 stime=1563881396
  cmdline="crypto_user02"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s
  crypto_user02.c:59: INFO: Starting crypto_user larval deletion test.  May 
crash buggy kernels.
  crypto_user02.c:91: BROK: unexpected error from tst_crypto_del_alg(): EBUSY

  Summary:
  passed   0
  failed   0
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=2 corefile=no
  cutime=0 cstime=0
  <<>>

  
  Nothing interesting in syslog:
  Jul 23 11:29:20 amaura systemd[1]: Started Session 1 of user ubuntu.
  Jul 23 11:29:56 amaura kernel: [  619.646330] LTP: starting crypto_user02
  Jul 23 11:30:23 amaura kernel: [  646.554403] cfg80211: Loading compiled-in 
X.509 certificates for regulatory database

  
  Steps to run this test:
git clone --depth=1 https://github.com/linux-test-project/ltp.git
cd ltp; make autotools; ./configure; make; sudo make install
echo "crypto_user02 crypto_user02" > /tmp/jobs
sudo /opt/ltp/runltp -f /tmp/jobs

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-21-generic 5.0.0-21.22
  ProcVersionSignature: User Name 5.0.0-21.22-generic 5.0.15
  Uname: Linux 5.0.0-21-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 23 11:19 seq
   crw-rw 1 root audio 116, 33 Jul 23 11:19 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Jul 23 11:30:15 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Intel Corporation S1200RP
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic 
root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-21-generic N/A
   linux-backports-modules-5.0.0-21-generic  N/A
   linux-firmware1.178.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: S1200RP.86B.03.02.0003.070120151022
  dmi.board.asset.tag: 
  dmi.board.name: S1200RP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: G62254-407
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 17
  dmi.chassis.vendor: ..
  dmi.chassis.version: ..
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: S1200RP
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 
  dmi.sys.vendor: Intel Corporation

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

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

[Kernel-packages] [Bug 1911585] Re: ouchpad doesn't work properly after Ubuntu Installation

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  ouchpad doesn't work properly after Ubuntu Installation

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Touchpad' incorrectly detected in 'Lenovo s740' after the ubuntu
  installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-60-generic 5.4.0-60.67
  ProcVersionSignature: Ubuntu 5.4.0-60.67-generic 5.4.78
  Uname: Linux 5.4.0-60-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  felipe 1451 F pulseaudio
   /dev/snd/pcmC0D0p:   felipe 1451 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 13 21:52:13 2021
  InstallationDate: Installed on 2021-01-07 (6 days ago)
  InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
  MachineType: LENOVO 81RM
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-60-generic 
root=UUID=32be46bd-d75e-4c0e-a754-56d7e63881ba ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-60-generic N/A
   linux-backports-modules-5.4.0-60-generic  N/A
   linux-firmware1.187.7
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2021-01-08 (5 days ago)
  dmi.bios.date: 07/15/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BYCN36WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40688 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga S740-14IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrBYCN36WW:bd07/15/2020:svnLENOVO:pn81RM:pvrLenovoYogaS740-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrLenovoYogaS740-14IIL:
  dmi.product.family: Yoga S740-14IIL
  dmi.product.name: 81RM
  dmi.product.sku: LENOVO_MT_81RM_BU_idea_FM_Yoga S740-14IIL
  dmi.product.version: Lenovo Yoga S740-14IIL
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1911835] Re: package linux-firmware 1.187.7 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package linux-firmware 1.187.7 failed to install/upgrade: installed
  linux-firmware package post-installation script subprocess returned
  error exit status 1

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Upgraded from 18.04 to 20.04 without doing a clean install. Just
  started encountering issues with updates. I'm not sure if it's related
  to my encrypted swap which seems to have been broken/unreadable at
  some point in upgrading.

  Happy to provide more info.

  $ lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187.7
  ProcVersionSignature: Ubuntu 5.4.0-60.67-generic 5.4.78
  Uname: Linux 5.4.0-60-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Jan 10 22:02:00 2021
  Dependencies:
   
  ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
  HibernationDevice: RESUME=UUID=b9d6e51c-6ef1-4b05-916a-17aa1a75141c
  InstallationDate: Installed on 2016-07-02 (1657 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 80K9
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-60-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26.7
  SourcePackage: initramfs-tools
  Title: package linux-firmware 1.187.7 failed to install/upgrade: installed 
linux-firmware package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to focal on 2020-12-06 (39 days ago)
  dmi.bios.date: 07/21/2015
  dmi.bios.vendor: Lenovo
  dmi.bios.version: A9CN61WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Edge 15
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Edge 15
  dmi.modalias: 
dmi:bvnLenovo:bvrA9CN61WW:bd07/21/2015:svnLENOVO:pn80K9:pvrLenovoEdge15:rvnLENOVO:rnLenovoEdge15:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoEdge15:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80K9
  dmi.product.sku: LENOVO_MT_80K9_BU_idea_FM_Lenovo Edge 15
  dmi.product.version: Lenovo Edge 15
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1829983] Re: memcg_stat from controllers test suite in LTP failed

** Tags added: sru-20210104

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

Title:
  memcg_stat from controllers test suite in LTP failed

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Xenial:
  New
Status in linux-aws source package in Xenial:
  New
Status in linux source package in Bionic:
  Confirmed
Status in linux-aws source package in Bionic:
  New
Status in linux source package in Cosmic:
  Confirmed
Status in linux-aws source package in Cosmic:
  New

Bug description:
   memcg_stat_test 1 TINFO: Starting test 1
   sh: echo: I/O error
   memcg_stat_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 1 TINFO: Running memcg_process --shm -k 3 -s 135168
   memcg_stat_test 1 TINFO: Warming up pid: 31352
   memcg_stat_test 1 TINFO: Process is still here after warm up: 31352
   memcg_stat_test 1 TPASS: cache is 135168 as expected
   memcg_stat_test 2 TINFO: Starting test 2
   sh: echo: I/O error
   memcg_stat_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 2 TINFO: Running memcg_process --mmap-file -s 135168
   memcg_stat_test 2 TINFO: Warming up pid: 31380
   memcg_stat_test 2 TINFO: Process is still here after warm up: 31380
   memcg_stat_test 2 TPASS: mapped_file is 135168 as expected
   memcg_stat_test 3 TINFO: Starting test 3
   sh: echo: I/O error
   memcg_stat_test 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 3 TINFO: Running memcg_process --mmap-lock1 -s 4096
   memcg_stat_test 3 TINFO: Warming up pid: 31409
   memcg_stat_test 3 TINFO: Process is still here after warm up: 31409
   memcg_stat_test 3 TPASS: unevictable is 4096 as expected
   memcg_stat_test 4 TINFO: Starting test 4
   sh: echo: I/O error
   memcg_stat_test 4 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 4 TINFO: Running memcg_process --mmap-lock2 -s 4096
   memcg_stat_test 4 TINFO: Warming up pid: 31434
   memcg_stat_test 4 TINFO: Process is still here after warm up: 31434
   memcg_stat_test 4 TPASS: unevictable is 4096 as expected
   memcg_stat_test 5 TINFO: Starting test 5
   sh: echo: I/O error
   memcg_stat_test 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 5 TPASS: hierarchical_memory_limit is 4096 as expected
   memcg_stat_test 6 TINFO: Starting test 6
   sh: echo: I/O error
   memcg_stat_test 6 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   sh: echo: I/O error
   memcg_stat_test 6 TFAIL: hierarchical_memory_limit is 4096, 8192 expected
   memcg_stat_test 7 TINFO: Starting test 7
   sh: echo: I/O error
   memcg_stat_test 7 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 7 TCONF: mem+swap is not enabled
   memcg_stat_test 7 TINFO: Starting test 8
   sh: echo: I/O error
   memcg_stat_test 7 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 7 TCONF: mem+swap is not enabled
   tag=memcg_stat stime=1558504742 dur=4 exit=exited stat=33 core=no cu=16 cs=10

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-50-generic 4.15.0-50.54
  ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 22 02:57 seq
   crw-rw 1 root audio 116, 33 May 22 02:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   [14538.862950] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
   [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
  Date: Wed May 22 07:17:43 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-50-generic N/A
   linux-backports-modules-4.15.0-50-generic  N/A
   linux-firmware 1.173.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version:

[Kernel-packages] [Bug 1829989] Re: memcg_use_hierarchy from controllers test suite in LTP failed

** Tags added: sru-20210104

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

Title:
  memcg_use_hierarchy from controllers test suite in LTP failed

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Confirmed
Status in linux-aws source package in Bionic:
  New
Status in linux source package in Cosmic:
  Confirmed
Status in linux-aws source package in Cosmic:
  New

Bug description:
  startup='Wed May 22 05:59:07 2019'
  memcg_use_hierarchy_test 1 TINFO: Starting test 1
  sh: echo: I/O error
  memcg_use_hierarchy_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
  memcg_use_hierarchy_test 1 TPASS: process 31577 is killed
  memcg_use_hierarchy_test 2 TINFO: Starting test 2
  sh: echo: I/O error
  memcg_use_hierarchy_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
  memcg_use_hierarchy_test 2 TFAIL: echo 1 > memory.use_hierarchy passed 
unexpectedly
  memcg_use_hierarchy_test 3 TINFO: Starting test 3
  sh: echo: I/O error
  memcg_use_hierarchy_test 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
  memcg_use_hierarchy_test 3 TPASS: echo 0 > subgroup/memory.use_hierarchy 
failed as expected
  tag=memcg_use_hierarchy stime=1558504747 dur=1 exit=exited stat=1 core=no 
cu=5 cs=5

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-50-generic 4.15.0-50.54
  ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 22 02:57 seq
   crw-rw 1 root audio 116, 33 May 22 02:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   [14538.862950] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
   [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
  Date: Wed May 22 07:33:33 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-50-generic N/A
   linux-backports-modules-4.15.0-50-generic  N/A
   linux-firmware 1.173.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1829984] Re: memcg_usage_in_bytes from controllers test suite in LTP failed

** Tags added: sru-20210104

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

Title:
  memcg_usage_in_bytes from controllers test suite in LTP failed

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Xenial:
  New
Status in linux-aws source package in Xenial:
  New
Status in linux source package in Bionic:
  Confirmed
Status in linux-aws source package in Bionic:
  New
Status in linux source package in Cosmic:
  Confirmed
Status in linux-aws source package in Cosmic:
  New

Bug description:
   startup='Wed May 22 05:59:09 2019'
   memcg_usage_in_bytes_test 1 TINFO: Starting test 1
   sh: echo: I/O error
   memcg_usage_in_bytes_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
   memcg_usage_in_bytes_test 1 TINFO: Running memcg_process --mmap-anon -s 
4194304
   memcg_usage_in_bytes_test 1 TINFO: Warming up pid: 31689
   memcg_usage_in_bytes_test 1 TINFO: Process is still here after warm up: 31689
   memcg_usage_in_bytes_test 1 TFAIL: memory.usage_in_bytes is 4202496, 4194304 
expected
   memcg_usage_in_bytes_test 2 TINFO: Starting test 2
   sh: echo: I/O error
   memcg_usage_in_bytes_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
   memcg_usage_in_bytes_test 2 TCONF: mem+swap is not enabled
   tag=memcg_usage_in_bytes stime=1558504749 dur=1 exit=exited stat=33 core=no 
cu=5 cs=3

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-50-generic 4.15.0-50.54
  ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 22 02:57 seq
   crw-rw 1 root audio 116, 33 May 22 02:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   [14538.862950] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
   [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
  Date: Wed May 22 07:17:43 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-50-generic N/A
   linux-backports-modules-4.15.0-50-generic  N/A
   linux-firmware 1.173.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1912676] Re: Fix regression introduced by codec PM change

2021-01-28 Thread jeremyszu

** Tags added: originate-from-1913684 stella

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

Title:
   Fix regression introduced by codec PM change

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  Confirmed
Status in linux source package in Groovy:
  Confirmed
Status in linux-oem-5.10 source package in Groovy:
  Invalid

Bug description:
  [Impact]
  After the codec PM optimization, laptops with SOF may take very long to
  suspend. In addition to that, HDA may not be able to be runtim suspended
  again after resume from hibernation.

  [Fix]
  Prevent the SOF driver touches codec during system suspend, and properly
  refcount the PM usage counter.

  [Test]
  On an affected SOF system, it takes 5 mins to suspend.
  On another affected HDA system, S4 resume causes high power consumption
  becuase HDA controller can't be runtime suspended.

  Both issues are gone by applying these patches.

  [Where problems could occur]
  If somehow any laptop depends on the old behavior to work properly, this
  can break them. It's highly unlikely though.

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

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

[Kernel-packages] [Bug 1913682] [NEW] Fix no screen show on display after S3 on CML-R

2021-01-28 Thread koba

Public bug reported:

[Impact]
On CML-R, after S3, No screen show on all three connector(3*DP).

[Fix]
The patch is got from https://patchwork.freedesktop.org/patch/416162/.
For Legacy S3 suspend/resume GEN9 BC needs to enable and setup TGP PCH.

[Test Case]
1. Connected the monitor on one of 3*DP on CML-R.
2. Suspend the machine.
3. Check the monitor can output something.

[Where problems could occur]
Just Enable the hpd detection in IRQ installer and during suspend

** Affects: hwe-next
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: koba (kobako)
 Status: In Progress

** Affects: linux-oem-5.10 (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Focal)
 Importance: Undecided
 Assignee: koba (kobako)
 Status: In Progress

** Affects: linux-oem-5.10 (Ubuntu Focal)
 Importance: Undecided
 Assignee: koba (kobako)
 Status: In Progress

** Affects: linux (Ubuntu Groovy)
 Importance: Undecided
 Assignee: koba (kobako)
 Status: In Progress

** Affects: linux-oem-5.10 (Ubuntu Groovy)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Hirsute)
 Importance: Undecided
 Assignee: koba (kobako)
 Status: In Progress

** Affects: linux-oem-5.10 (Ubuntu Hirsute)
 Importance: Undecided
 Status: New


** Tags: oem-priority originate-from-1912745 somerville

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

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

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

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

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

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

** Also affects: linux-oem-5.10 (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => koba (kobako)

** Changed in: linux (Ubuntu Groovy)
 Assignee: (unassigned) => koba (kobako)

** Changed in: linux-oem-5.10 (Ubuntu Focal)
 Assignee: (unassigned) => koba (kobako)

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

** Changed in: linux (Ubuntu Hirsute)
 Assignee: (unassigned) => koba (kobako)

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

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

** Changed in: linux-oem-5.10 (Ubuntu Focal)
   Status: New => In Progress

** Tags added: oem-priority originate-from-1912745 somerville

** Description changed:

  [Impact]
  On CML-R, after S3, No screen show on all three connector(3*DP).
  
  [Fix]
  The patch is got from https://patchwork.freedesktop.org/patch/416162/.
  For Legacy S3 suspend/resume GEN9 BC needs to enable and setup TGP PCH.
  
  [Test Case]
  1. Connected the monitor on one of 3*DP on CML-R.
  2. Suspend the machine.
  3. Check the monitor can output something.
  
  [Where problems could occur]
- Just Enable the hpd detection in IRQ installer.
+ Just Enable the hpd detection in IRQ installer and during suspend

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

Title:
  Fix  no screen show on display after S3 on CML-R

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  New
Status in linux source package in Focal:
  In Progress
Status in linux-oem-5.10 source package in Focal:
  In Progress
Status in linux source package in Groovy:
  In Progress
Status in linux-oem-5.10 source package in Groovy:
  New
Status in linux source package in Hirsute:
  In Progress
Status in linux-oem-5.10 source package in Hirsute:
  New

Bug description:
  [Impact]
  On CML-R, after S3, No screen show on all three connector(3*DP).

  [Fix]
  The patch is got from https://patchwork.freedesktop.org/patch/416162/.
  For Legacy S3 suspend/resume GEN9 BC needs to enable and setup TGP PCH.

  [Test Case]
  1. Connected the monitor on one of 3*DP on CML-R.
  2. Suspend the machine.
  3. Check the monitor can output something.

  [Where problems could occur]
  Just Enable the hpd detection in IRQ installer and during suspend

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

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

[Kernel-packages] [Bug 1829978] Re: cpuacct_100_100 from controllers test suite in LTP failed

** Tags added: sru-20210104

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

Title:
  cpuacct_100_100 from controllers test suite in LTP failed

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Bionic:
  Incomplete
Status in linux-aws source package in Bionic:
  New

Bug description:
   startup='Wed May 22 06:50:45 2019'
   cpuacct 1 TINFO: timeout per run is 0h 5m 0s
   cpuacct 1 TINFO: cpuacct: /sys/fs/cgroup/cpu,cpuacct
   cpuacct 1 TINFO: Creating 100 subgroups each with 100 processes
   /opt/ltp/testcases/bin/cpuacct.sh: -2110094999: 
/opt/ltp/testcases/bin/cpuacct.sh: Cannot fork
   tag=cpuacct_100_100 stime=1558507845 dur=9 exit=exited stat=2 core=no cu=30 
cs=53

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-50-generic 4.15.0-50.54
  ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 22 02:57 seq
   crw-rw 1 root audio 116, 33 May 22 02:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   
  Date: Wed May 22 06:59:27 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-50-generic N/A
   linux-backports-modules-4.15.0-50-generic  N/A
   linux-firmware 1.173.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1834006] Re: cpuset_hotplug from controllers in ubuntu_ltp failed

** Tags added: sru-20210104

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

Title:
  cpuset_hotplug from controllers in ubuntu_ltp failed

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-aws source package in Bionic:
  New
Status in linux-azure source package in Bionic:
  New
Status in linux source package in Focal:
  New
Status in linux-aws source package in Focal:
  New
Status in linux-azure source package in Focal:
  New

Bug description:
  Issue found on node amaura:
  <<>>
  tag=cpuset_hotplug stime=1561372131
  cmdline="cpuset_hotplug_test.sh"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  cpuset_hotplug 1 TFAIL: task's allowed list isn't expected.(Result: 0-15, 
Expect: 0-7)
  cpuset_hotplug 3 TFAIL: task's allowed list isn't expected.(Result: 0-15, 
Expect: 0-7)
  cpuset_hotplug 5 TPASS: Cpuset vs CPU hotplug test succeeded.
  cpuset_hotplug 7 TFAIL: task's cpu allowed list isn't expected(Result: 0-15, 
Expect: 0-7).
  cpuset_hotplug 9 TPASS: Cpuset vs CPU hotplug test succeeded.
  cpuset_hotplug 11 TPASS: Cpuset vs CPU hotplug test succeeded.
  <<>>
  initiation_status="ok"
  duration=1 termination_type=exited termination_id=1 corefile=no
  cutime=19 cstime=81
  <<>>

  Test script:
  
https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/controllers/cpuset/cpuset_hotplug_test/cpuset_hotplug_test.sh

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-22-generic 4.18.0-22.23
  ProcVersionSignature: User Name 4.18.0-22.23-generic 4.18.20
  Uname: Linux 4.18.0-22-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 24 10:25 seq
   crw-rw 1 root audio 116, 33 Jun 24 10:25 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Mon Jun 24 10:30:59 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Intel Corporation S1200RP
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic 
root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-22-generic N/A
   linux-backports-modules-4.18.0-22-generic  N/A
   linux-firmware 1.175.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: S1200RP.86B.03.02.0003.070120151022
  dmi.board.asset.tag: 
  dmi.board.name: S1200RP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: G62254-407
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 17
  dmi.chassis.vendor: ..
  dmi.chassis.version: ..
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: S1200RP
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 
  dmi.sys.vendor: Intel Corporation

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

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

[Kernel-packages] [Bug 1912057] Re: Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA

2021-01-28 Thread Kai-Heng Feng

The test kernel (accidentally) disabled pcieport driver, and made the issue 
went away.
Two things happened:
1) The rootport stays at D0
2) PME service isn't enabled

Let's try 1) first. Will upload a kernel soon.

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

Title:
  Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After boot the idle power consumption is around 2.3 W but after suspend it is 
4.7 W.
  The measurement is 5-10 min after boot/resume - looking at "top" to see 
system was idle.
  This is consistent - I have tried more that 10 times. 
  BIOS is updated to latest version.
  I have checked power consumption with external meter - and confirmed that it 
is higher.

  I have attached output of:
  sudo powertop -t 60 -r --html=before.html  (and after)

  I have noticed that Package C-state 6 is reached before suspend but
  not after.

  I expect that idle power consumption after suspend should be the same
  as before.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-38-generic 5.8.0-38.43
  ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hjh1448 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 16 15:49:32 2021
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2021-01-03 (13 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX425JA_UX425JA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic 
root=UUID=6296ce1c-eec8-4302-beb1-b4a228780075 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-38-generic N/A
   linux-backports-modules-5.8.0-38-generic  N/A
   linux-firmware1.190.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/28/2020
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX425JA.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX425JA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.4
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX425JA.304:bd10/28/2020:br5.14:efr3.4:svnASUSTeKCOMPUTERINC.:pnZenBookUX425JA_UX425JA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425JA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX425JA_UX425JA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1913215] Re: Random kernel bugs on nouveau driver and NVidia 1070 Ti

2021-01-28 Thread Kai-Heng Feng

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.11-rc5/amd64/


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

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

Title:
  Random kernel bugs on nouveau driver and NVidia 1070 Ti

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The issue exists for quite some time already. The affected UI freezes and 
luckily while using the new KDE beta only the desktop freezes. Before I had to 
do a hard reset since nothing was responding to key presses.
  Hope there are enough debug info attached by apport_cli to the bug report.

  If there is any way I can help, please ask! :)

  Thanks
  - Thomas

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.8.0-36-generic 5.8.0-36.40+21.04.1
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  NonfreeKernelModules: rcraid
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Jan 25 21:32:22 2021
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=7252ebf2-954b-4560-87a0-ace5e9c25fbe ro nouveau.runpm=0 quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-36-generic N/A
   linux-backports-modules-5.8.0-36-generic  N/A
   linux-firmware1.194
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X470-PRO
  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.:bvr5809:bd12/03/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO: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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  DistroRelease: Ubuntu 21.04
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: rcraid
  Package: linux (not installed)
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=7252ebf2-954b-4560-87a0-ace5e9c25fbe ro nouveau.runpm=0 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  RebootRequiredPkgs: evolution-data-server
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-36-generic N/A
   linux-backports-modules-5.8.0-36-generic  N/A
   linux-firmware1.194
  Tags:  hirsute
  Uname: Linux 5.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm apt-mirror audio avahi avahi-autoipd bin bluetooth cdrom 
chrome-remote-desktop colord crontab daemon davfs2 debian-tor dialout disk 
docker fax floppy fuse games i2c icecc kmem kvm libvirt libvirt-dnsmasq lightdm 
lp lpadmin mail man mythtv netdev news nm-openconnect ntp nvidia-persistenced 
operator plugdev proxy pulse root rtkit sambashare saned scanner science shadow 
ssh sudo sys syslog systemd-bus-proxy systemd-journal systemd-journal-remote 
systemd-network systemd-resolve systemd-timesync tape tty users uucp video 
voice weston-launch whoopsie www-data
  _MarkForUpload: True
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 12/03/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X470-PRO
  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:

[Kernel-packages] [Bug 1829849] Re: proc01 in fs from ubuntu_ltp failed

** Tags added: sru-20210104

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

Title:
  proc01 in fs from ubuntu_ltp failed

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  Triaged
Status in linux-azure package in Ubuntu:
  Triaged
Status in linux-oracle-5.0 package in Ubuntu:
  Confirmed

Bug description:
   proc01  0  TINFO  :  /proc/sys/fs/binfmt_misc/register: is write-only.
   proc01  0  TINFO  :  /proc/sys/net/ipv6/conf/all/stable_secret: known 
issue: errno=EIO(5): Input/output error
   proc01  0  TINFO  :  /proc/sys/net/ipv6/conf/default/stable_secret: 
known issue: errno=EIO(5): Input/output error
   proc01  0  TINFO  :  /proc/sys/net/ipv6/conf/ens6/stable_secret: known 
issue: errno=EIO(5): Input/output error
   proc01  0  TINFO  :  /proc/sys/net/ipv6/conf/lo/stable_secret: known 
issue: errno=EIO(5): Input/output error
   proc01  0  TINFO  :  /proc/kmsg: known issue: 
errno=EAGAIN/EWOULDBLOCK(11): Resource temporarily unavailable
   proc01  0  TINFO  :  /proc/sysrq-trigger: is write-only.
   proc01  0  TINFO  :  /proc/self/task/8782/mem: known issue: 
errno=EIO(5): Input/output error
   proc01  0  TINFO  :  /proc/self/task/8782/clear_refs: is write-only.
   proc01  0  TINFO  :  /proc/self/task/8782/pagemap: reached maxmbytes (-m)
   proc01  0  TINFO  :  /proc/self/task/8782/attr/prev: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/task/8782/attr/exec: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/task/8782/attr/fscreate: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/task/8782/attr/keycreate: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/task/8782/attr/sockcreate: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  1  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/selinux/current: errno=EINVAL(22): Invalid argument
   proc01  2  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/selinux/prev: errno=EINVAL(22): Invalid argument
   proc01  3  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/selinux/exec: errno=EINVAL(22): Invalid argument
   proc01  4  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/selinux/fscreate: errno=EINVAL(22): Invalid argument
   proc01  5  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/selinux/keycreate: errno=EINVAL(22): Invalid argument
   proc01  6  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/selinux/sockcreate: errno=EINVAL(22): Invalid argument
   proc01  7  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/smack/current: errno=EINVAL(22): Invalid argument
   proc01  8  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/apparmor/prev: errno=EINVAL(22): Invalid argument
   proc01  9  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/apparmor/exec: errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/mem: known issue: errno=EIO(5): 
Input/output error
   proc01  0  TINFO  :  /proc/self/clear_refs: is write-only.
   proc01  0  TINFO  :  /proc/self/pagemap: reached maxmbytes (-m)
   proc01  0  TINFO  :  /proc/self/attr/prev: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/attr/exec: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/attr/fscreate: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/attr/keycreate: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/attr/sockcreate: known issue: 
errno=EINVAL(22): Invalid argument
   proc01 10  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/selinux/current: errno=EINVAL(22): Invalid argument
   proc01 11  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/selinux/prev: errno=EINVAL(22): Invalid argument
   proc01 12  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/selinux/exec: errno=EINVAL(22): Invalid argument
   proc01 13  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/selinux/fscreate: errno=EINVAL(22): Invalid argument
   proc01 14  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/selinux/keycreate: errno=EINVAL(22): Invalid argument
   proc01 15  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/selinux/sockcreate: errno=EINVAL(22): Invalid argument
   proc01 16  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/smack/current: errno=EINVAL(22): Invalid argument
   proc01 17  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/apparmor/prev: errno=EINVAL(22): Invalid argument

[Kernel-packages] [Bug 1874693] Re: vmx_host_state_area test from ubuntu_kvm_unit_tests crashed with Eoan Azure

** Tags added: sru-20210104

** Tags added: amd64 azure bionic

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

Title:
  vmx_host_state_area test from ubuntu_kvm_unit_tests crashed with Eoan
  Azure

Status in ubuntu-kernel-tests:
  New
Status in linux-azure package in Ubuntu:
  New

Bug description:
  Only Standard_F32s_v2 and Standard_D48_v3 can be tested with KVM unit
  test.

  And it looks like the kvm_unit_test will crash with
  vmx_host_state_area:

  01:49:05 DEBUG| Running 
'/home/azure/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/vmx_host_state_area'
   BUILD_HEAD=4671e4ba
   timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults 
-device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none 
-serial stdio -device pci-testdev -machine accel=kvm -kernel 
/tmp/tmp.p1fskNt1wF -smp 1 -cpu host,+vmx -append vmx_host_state_area_test # 
-initrd /tmp/tmp.YTVFJ025gz
   enabling apic
   paging enabled
   cr0 = 80010011
   cr3 = 477000
   cr4 = 20

   Test suite: vmx_host_state_area_test
   PASS: HOST_CR0 8021: vmlaunch succeeds
   PASS: HOST_CR0 80010030: vmlaunch fails
   PASS: HOST_CR0 80010030: VMX inst error is 8 (actual 8)
   PASS: HOST_CR0 80010011: vmlaunch fails
   PASS: HOST_CR0 80010011: VMX inst error is 8 (actual 8)
   PASS: HOST_CR0 10031: vmlaunch fails
   PASS: HOST_CR0 10031: VMX inst error is 8 (actual 8)
   PASS: HOST_CR0 180010031: vmlaunch fails
   PASS: HOST_CR0 180010031: VMX inst error is 8 (actual 8)
   PASS: HOST_CR0 280010031: vmlaunch fails
   PASS: HOST_CR0 280010031: VMX inst error is 8 (actual 8)
   PASS: HOST_CR0 480010031: vmlaunch fails
   PASS: HOST_CR0 480010031: VMX inst error is 8 (actual 8)
   PASS: HOST_CR0 880010031: vmlaunch fails
   PASS: HOST_CR0 880010031: VMX inst error is 8 (actual 8)
   PASS: HOST_CR0 1080010031: vmlaunch fails
   PASS: HOST_CR0 1080010031: VMX inst error is 8 (actual 8)
   PASS: HOST_CR0 2080010031: vmlaunch fails
   PASS: HOST_CR0 2080010031: VMX inst error is 8 (actual 8)
   PASS: HOST_CR0 4080010031: vmlaunch fails
   PASS: HOST_CR0 4080010031: VMX inst error is 8 (actual 8)
   PASS: HOST_CR0 8080010031: vmlaunch fails
   PASS: HOST_CR0 8080010031: VMX inst error is 8 (actual 8)
   PASS: HOST_CR0 10080010031: vmlaunch fails
   PASS: HOST_CR0 10080010031: VMX inst error is 8 (actual 8)
   PASS: HOST_CR0 20080010031: vmlaunch fails
   PASS: HOST_CR0 20080010031: VMX inst error is 8 (actual 8)
   PASS: HOST_CR0 40080010031: vmlaunch fails
   PASS: HOST_CR0 40080010031: VMX inst error is 8 (actual 8)
   PASS: HOST_CR0 80080010031: vmlaunch fails
   PASS: HOST_CR0 80080010031: VMX inst error is 8 (actual 8)
   PASS: HOST_CR0 100080010031: vmlaunch fails
   PASS: HOST_CR0 100080010031: VMX inst error is 8 (actual 8)
   PASS: HOST_CR0 200080010031: vmlaunch fails
   PASS: HOST_CR0 200080010031: VMX inst error is 8 (actual 8)
   PASS: HOST_CR0 400080010031: vmlaunch fails
   PASS: HOST_CR0 400080010031: VMX inst error is 8 (actual 8)
   PASS: HOST_CR0 800080010031: vmlaunch fails
   PASS: HOST_CR0 800080010031: VMX inst error is 8 (actual 8)
   PASS: HOST_CR0 180010031: vmlaunch fails
   PASS: HOST_CR0 180010031: VMX inst error is 8 (actual 8)
   PASS: HOST_CR0 280010031: vmlaunch fails
   PASS: HOST_CR0 280010031: VMX inst error is 8 (actual 8)
   PASS: HOST_CR0 480010031: vmlaunch fails
   PASS: HOST_CR0 480010031: VMX inst error is 8 (actual 8)
   PASS: HOST_CR0 880010031: vmlaunch fails
   PASS: HOST_CR0 880010031: VMX inst error is 8 (actual 8)
   PASS: HOST_CR0 1080010031: vmlaunch fails
   PASS: HOST_CR0 1080010031: VMX inst error is 8 (actual 8)
   PASS: HOST_CR0 2080010031: vmlaunch fails
   PASS: HOST_CR0 2080010031: VMX inst error is 8 (actual 8)
   PASS: HOST_CR0 4080010031: vmlaunch fails
   PASS: HOST_CR0 4080010031: VMX inst error is 8 (actual 8)
   PASS: HOST_CR0 8080010031: vmlaunch fails
   PASS: HOST_CR0 8080010031: VMX inst error is 8 (actual 8)
   PASS: HOST_CR0 10080010031: vmlaunch fails
   PASS: HOST_CR0 10080010031: VMX inst error is 8 (actual 8)
   PASS: HOST_CR0 20080010031: vmlaunch fails
   PASS: HOST_CR0 20080010031: VMX inst error is 8 (actual 8)
   PASS: HOST_CR0 40080010031: vmlaunch fails
   PASS: HOST_CR0 40080010031: VMX inst error is 8 (actual 8)
   PASS: HOST_CR0 80080010031: vmlaunch fails
   PASS: HOST_CR0 80080010031: VMX inst error is 8 (actual 8)
   PASS: HOST_CR0 100080010031: vmlaunch fails
   PASS: HOST_CR0 100080010031: VMX inst error is 8 (actual 8)
   PASS: HOST_CR0 200080010031: vmlaunch fails
   PASS: HOST_CR0 200080010031: VMX inst error is 8 (actual 8)
   PASS: HOST_CR0 400080010031: vmlaunch fails
   PASS: HOST_CR0 400080010031: VMX inst error is 8 (actual 8)
   PASS: HOST_CR0 800080010031:

[Kernel-packages] [Bug 1824228] Re: ept test fails in kvm_unit_tests

** Tags added: sru-20210104

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

Title:
  ept test fails in kvm_unit_tests

Status in ubuntu-kernel-tests:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New
Status in linux-oracle package in Ubuntu:
  New
Status in linux-azure source package in Disco:
  Won't Fix
Status in linux-kvm source package in Disco:
  Won't Fix
Status in linux-oracle source package in Disco:
  Won't Fix
Status in linux-azure source package in Eoan:
  New
Status in linux-kvm source package in Eoan:
  New
Status in linux-oracle source package in Eoan:
  New

Bug description:
  Reproducible: Yes,
  Series: cosmic
  Kernel: "linux-azure 4.18.0-1015.15"
  Steps:

  1.) apt-get install -y build-essential cpu-checker qemu-kvm git gcc-multilib
  2.) git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  3.) cd kvm-unit-tests; ./configure; make
  4.) sudo TESTNAME=ept TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu 
host,host-phys-bits,+vmx -m 2560 -append "ept_access*"
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults 
-device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none 
-serial stdio -device pci-testdev -machine accel=kvm -kernel x86/vmx.flat -smp 
1 -cpu host,host-phys-bits,+vmx -m 2560 -append ept_access* # -initrd 
/tmp/tmp.RcwfbGP5Ou
  enabling apic
  paging enabled
  cr0 = 80010011
  cr3 = 477000
  cr4 = 20

  Test suite: ept_access_test_not_present

  Test suite: ept_access_test_read_only

  Test suite: ept_access_test_write_only

  Test suite: ept_access_test_read_write

  Test suite: ept_access_test_execute_only

  Test suite: ept_access_test_read_execute

  Test suite: ept_access_test_write_execute

  Test suite: ept_access_test_read_write_execute

  Test suite: ept_access_test_reserved_bits

  Test suite: ept_access_test_ignored_bits

  Test suite: ept_access_test_paddr_not_present_ad_disabled

  Test suite: ept_access_test_paddr_not_present_ad_enabled
  Host skipping test: EPT AD bits not supported.

  Test suite: ept_access_test_paddr_read_only_ad_disabled
  EPT_VLT_RD expected
  FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x008b - 
''''''''''''''1000'1011 
- 139
RHS: 0x008a - 
''''''''''''''1000'1010 
- 138
STACK: 40f328 40f8fb 40fb0b 40ff49 401577 4039d0 400312
  EPT_VLT_RD expected
  FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x008b - 
''''''''''''''1000'1011 
- 139
RHS: 0x008a - 
''''''''''''''1000'1010 
- 138
STACK: 40f328 40f8fb 40fb0b 40ff62 401577 4039d0 400312
  EPT_VLT_RD expected
  FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x008b - 
''''''''''''''1000'1011 
- 139
RHS: 0x008a - 
''''''''''''''1000'1010 
- 138
STACK: 40f328 40f8fb 40fb0b 40ff7b 401577 4039d0 400312
  EPT_VLT_RD expected
  FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x008b - 
''''''''''''''1000'1011 
- 139
RHS: 0x008a - 
''''''''''''''1000'1010 
- 138
STACK: 40f328 40f8fb 40fb0b 40ffa8 401577 4039d0 400312

  Test suite: ept_access_test_paddr_read_only_ad_enabled
  Host skipping test: EPT AD bits not supported.

  Test suite: ept_access_test_paddr_read_write

  Test suite: ept_access_test_paddr_read_write_execute

  Test suite: ept_access_test_paddr_read_execute_ad_disabled
  EPT_VLT_RD expected
  FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x00ab - 
''''''''''''''1010'1011 
- 171
RHS: 0x00aa - 
''''''''''''''1010'1010 
- 170
STACK: 40f328 40f8fb 40fb0b 40fde3 401577 4039d0 400312
  EPT_VLT_RD expected
  FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x00ab - 
''''''''''''''1010'1011 
- 171
RHS: 0x00aa - 
''''''''''''''1010'1010 
- 170
STACK: 40f328 40f8fb 40fb0b 40fdfc 401577 4039d0 400312
  EPT_VLT_RD expected

[Kernel-packages] [Bug 1831449] Re: memory in ubuntu_kvm_unit_tests fails

** Tags added: sru-20210104

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

Title:
  memory in ubuntu_kvm_unit_tests fails

Status in ubuntu-kernel-tests:
  Triaged
Status in linux-kvm package in Ubuntu:
  New
Status in linux-oracle package in Ubuntu:
  New

Bug description:
  Need to run this on oracle manually to get the full output:
   TESTNAME=memory TIMEOUT=90s ACCEL= ./x86/run x86/memory.flat -smp 1 -cpu host
   FAIL memory (8 tests, 2 unexpected failures)

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

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

[Kernel-packages] [Bug 1896784] Re: Use Azure host for time keeping in all images

This bug was fixed in the package linux-azure - 4.15.0-1106.118~16.04.1

---
linux-azure (4.15.0-1106.118~16.04.1) xenial; urgency=medium

  * xenial/linux-azure: 4.15.0-1106.118~16.04.1 -proposed tracker (LP:
#1911278)

  [ Ubuntu: 4.15.0-1106.118 ]

  * bionic/linux-azure-4.15: 4.15.0-1106.118 -proposed tracker (LP: #1911280)
  * bionic/linux: 4.15.0-133.137 -proposed tracker (LP: #1911295)
  * [drm:qxl_enc_commit [qxl]] *ERROR* head number too large or missing monitors
config: (LP: #1908219)
- qxl: remove qxl_io_log()
- qxl: move qxl_send_monitors_config()
- qxl: hook monitors_config updates into crtc, not encoder.
  * Touchpad not detected on ByteSpeed C15B laptop (LP: #1906128)
- Input: i8042 - add ByteSpeed touchpad to noloop table
  * vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 /
B-oracle-4.15 / X-KVM / B-KVM (LP: #1872401)
- KVM: nVMX: Always reflect #NM VM-exits to L1
  * stack trace in kernel (LP: #1903596)
- net: napi: remove useless stack trace
  * CVE-2020-2
- [Config]: Set CONFIG_PPC_RTAS_FILTER
  * Bionic update: upstream stable patchset 2020-12-04 (LP: #1906875)
- regulator: defer probe when trying to get voltage from unresolved supply
- ring-buffer: Fix recursion protection transitions between interrupt 
context
- time: Prevent undefined behaviour in timespec64_to_ns()
- nbd: don't update block size after device is started
- btrfs: sysfs: init devices outside of the chunk_mutex
- btrfs: reschedule when cloning lots of extents
- genirq: Let GENERIC_IRQ_IPI select IRQ_DOMAIN_HIERARCHY
- hv_balloon: disable warning when floor reached
- net: xfrm: fix a race condition during allocing spi
- perf tools: Add missing swap for ino_generation
- ALSA: hda: prevent undefined shift in snd_hdac_ext_bus_get_link()
- can: rx-offload: don't call kfree_skb() from IRQ context
- can: dev: can_get_echo_skb(): prevent call to kfree_skb() in hard IRQ
  context
- can: dev: __can_get_echo_skb(): fix real payload length return value for 
RTR
  frames
- can: can_create_echo_skb(): fix echo skb generation: always use 
skb_clone()
- can: peak_usb: add range checking in decode operations
- can: peak_usb: peak_usb_get_ts_time(): fix timestamp wrapping
- can: peak_canfd: pucan_handle_can_rx(): fix echo management when loopback 
is
  on
- xfs: flush new eof page on truncate to avoid post-eof corruption
- Btrfs: fix missing error return if writeback for extent buffer never 
started
- ath9k_htc: Use appropriate rs_datalen type
- usb: gadget: goku_udc: fix potential crashes in probe
- gfs2: Free rd_bits later in gfs2_clear_rgrpd to fix use-after-free
- gfs2: Add missing truncate_inode_pages_final for sd_aspace
- gfs2: check for live vs. read-only file system in gfs2_fitrim
- scsi: hpsa: Fix memory leak in hpsa_init_one()
- drm/amdgpu: perform srbm soft reset always on SDMA resume
- mac80211: fix use of skb payload instead of header
- cfg80211: regulatory: Fix inconsistent format argument
- scsi: scsi_dh_alua: Avoid crash during alua_bus_detach()
- iommu/amd: Increase interrupt remapping table limit to 512 entries
- pinctrl: intel: Set default bias in case no particular value given
- ARM: 9019/1: kprobes: Avoid fortify_panic() when copying optprobe template
- pinctrl: aspeed: Fix GPI only function problem.
- nbd: fix a block_device refcount leak in nbd_release
- xfs: fix flags argument to rmap lookup when converting shared file rmaps
- xfs: fix rmap key and record comparison functions
- xfs: fix a missing unlock on error in xfs_fs_map_blocks
- of/address: Fix of_node memory leak in of_dma_is_coherent
- cosa: Add missing kfree in error path of cosa_write
- perf: Fix get_recursion_context()
- ext4: correctly report "not supported" for {usr,grp}jquota when
  !CONFIG_QUOTA
- ext4: unlock xattr_sem properly in ext4_inline_data_truncate()
- thunderbolt: Add the missed ida_simple_remove() in ring_request_msix()
- uio: Fix use-after-free in uio_unregister_device()
- usb: cdc-acm: Add DISABLE_ECHO for Renesas USB Download mode
- mei: protect mei_cl_mtu from null dereference
- futex: Don't enable IRQs unconditionally in put_pi_state()
- ocfs2: initialize ip_next_orphan
- selinux: Fix error return code in sel_ib_pkey_sid_slow()
- don't dump the threads that had been already exiting when zapped.
- drm/gma500: Fix out-of-bounds access to struct drm_device.vblank[]
- pinctrl: amd: use higher precision for 512 RtcClk
- pinctrl: amd: fix incorrect way to disable debounce filter
- swiotlb: fix "x86: Don't panic if can not alloc buffer for swiotlb"
- IPv6: Set SIT tunnel hard_header_len to zero
- net/af_iucv: fix null pointer dereference on shutdown
- net/x25: Fix null-ptr-deref in x25_connect
- vrf: Fix fast path output

[Kernel-packages] [Bug 1896784] Re: Use Azure host for time keeping in all images

This bug was fixed in the package linux-azure-4.15 - 4.15.0-1106.118

---
linux-azure-4.15 (4.15.0-1106.118) bionic; urgency=medium

  * bionic/linux-azure-4.15: 4.15.0-1106.118 -proposed tracker (LP:
#1911280)

  [ Ubuntu: 4.15.0-133.137 ]

  * bionic/linux: 4.15.0-133.137 -proposed tracker (LP: #1911295)
  * [drm:qxl_enc_commit [qxl]] *ERROR* head number too large or missing monitors
config: (LP: #1908219)
- qxl: remove qxl_io_log()
- qxl: move qxl_send_monitors_config()
- qxl: hook monitors_config updates into crtc, not encoder.
  * Touchpad not detected on ByteSpeed C15B laptop (LP: #1906128)
- Input: i8042 - add ByteSpeed touchpad to noloop table
  * vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 /
B-oracle-4.15 / X-KVM / B-KVM (LP: #1872401)
- KVM: nVMX: Always reflect #NM VM-exits to L1
  * stack trace in kernel (LP: #1903596)
- net: napi: remove useless stack trace
  * CVE-2020-2
- [Config]: Set CONFIG_PPC_RTAS_FILTER
  * Bionic update: upstream stable patchset 2020-12-04 (LP: #1906875)
- regulator: defer probe when trying to get voltage from unresolved supply
- ring-buffer: Fix recursion protection transitions between interrupt 
context
- time: Prevent undefined behaviour in timespec64_to_ns()
- nbd: don't update block size after device is started
- btrfs: sysfs: init devices outside of the chunk_mutex
- btrfs: reschedule when cloning lots of extents
- genirq: Let GENERIC_IRQ_IPI select IRQ_DOMAIN_HIERARCHY
- hv_balloon: disable warning when floor reached
- net: xfrm: fix a race condition during allocing spi
- perf tools: Add missing swap for ino_generation
- ALSA: hda: prevent undefined shift in snd_hdac_ext_bus_get_link()
- can: rx-offload: don't call kfree_skb() from IRQ context
- can: dev: can_get_echo_skb(): prevent call to kfree_skb() in hard IRQ
  context
- can: dev: __can_get_echo_skb(): fix real payload length return value for 
RTR
  frames
- can: can_create_echo_skb(): fix echo skb generation: always use 
skb_clone()
- can: peak_usb: add range checking in decode operations
- can: peak_usb: peak_usb_get_ts_time(): fix timestamp wrapping
- can: peak_canfd: pucan_handle_can_rx(): fix echo management when loopback 
is
  on
- xfs: flush new eof page on truncate to avoid post-eof corruption
- Btrfs: fix missing error return if writeback for extent buffer never 
started
- ath9k_htc: Use appropriate rs_datalen type
- usb: gadget: goku_udc: fix potential crashes in probe
- gfs2: Free rd_bits later in gfs2_clear_rgrpd to fix use-after-free
- gfs2: Add missing truncate_inode_pages_final for sd_aspace
- gfs2: check for live vs. read-only file system in gfs2_fitrim
- scsi: hpsa: Fix memory leak in hpsa_init_one()
- drm/amdgpu: perform srbm soft reset always on SDMA resume
- mac80211: fix use of skb payload instead of header
- cfg80211: regulatory: Fix inconsistent format argument
- scsi: scsi_dh_alua: Avoid crash during alua_bus_detach()
- iommu/amd: Increase interrupt remapping table limit to 512 entries
- pinctrl: intel: Set default bias in case no particular value given
- ARM: 9019/1: kprobes: Avoid fortify_panic() when copying optprobe template
- pinctrl: aspeed: Fix GPI only function problem.
- nbd: fix a block_device refcount leak in nbd_release
- xfs: fix flags argument to rmap lookup when converting shared file rmaps
- xfs: fix rmap key and record comparison functions
- xfs: fix a missing unlock on error in xfs_fs_map_blocks
- of/address: Fix of_node memory leak in of_dma_is_coherent
- cosa: Add missing kfree in error path of cosa_write
- perf: Fix get_recursion_context()
- ext4: correctly report "not supported" for {usr,grp}jquota when
  !CONFIG_QUOTA
- ext4: unlock xattr_sem properly in ext4_inline_data_truncate()
- thunderbolt: Add the missed ida_simple_remove() in ring_request_msix()
- uio: Fix use-after-free in uio_unregister_device()
- usb: cdc-acm: Add DISABLE_ECHO for Renesas USB Download mode
- mei: protect mei_cl_mtu from null dereference
- futex: Don't enable IRQs unconditionally in put_pi_state()
- ocfs2: initialize ip_next_orphan
- selinux: Fix error return code in sel_ib_pkey_sid_slow()
- don't dump the threads that had been already exiting when zapped.
- drm/gma500: Fix out-of-bounds access to struct drm_device.vblank[]
- pinctrl: amd: use higher precision for 512 RtcClk
- pinctrl: amd: fix incorrect way to disable debounce filter
- swiotlb: fix "x86: Don't panic if can not alloc buffer for swiotlb"
- IPv6: Set SIT tunnel hard_header_len to zero
- net/af_iucv: fix null pointer dereference on shutdown
- net/x25: Fix null-ptr-deref in x25_connect
- vrf: Fix fast path output packet handling with async Netfilter rules
- r8169: fix potential skb double free in

[Kernel-packages] [Bug 1912676] Re: Fix regression introduced by codec PM change

2021-01-28 Thread jeremyszu

** Tags added: originate-from-1913680

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

Title:
   Fix regression introduced by codec PM change

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  Confirmed
Status in linux source package in Groovy:
  Confirmed
Status in linux-oem-5.10 source package in Groovy:
  Invalid

Bug description:
  [Impact]
  After the codec PM optimization, laptops with SOF may take very long to
  suspend. In addition to that, HDA may not be able to be runtim suspended
  again after resume from hibernation.

  [Fix]
  Prevent the SOF driver touches codec during system suspend, and properly
  refcount the PM usage counter.

  [Test]
  On an affected SOF system, it takes 5 mins to suspend.
  On another affected HDA system, S4 resume causes high power consumption
  becuase HDA controller can't be runtime suspended.

  Both issues are gone by applying these patches.

  [Where problems could occur]
  If somehow any laptop depends on the old behavior to work properly, this
  can break them. It's highly unlikely though.

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

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

[Kernel-packages] [Bug 1821394] Re: vmx tests fail in kvm_unit_tests

** Tags added: sru-20210104

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

Title:
  vmx tests fail in kvm_unit_tests

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux-aws package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-kvm package in Ubuntu:
  Confirmed
Status in linux-oracle package in Ubuntu:
  Confirmed

Bug description:
  Reproducible: Yes, every time.
  Series: cosmic
  Kernel: "linux-aws 4.18.0-1012.14"
  Steps:

  1.) apt-get install --yes --allow build-essential cpu-checker qemu-kvm git 
gcc-multilib
  2.) git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  3.) cd kvm-unit-tests; ./configure; make
  4.) TESTNAME=vmx TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu 
host,+vmx -append "-exit_monitor_from_l2_test -ept_access* -vmx_smp* 
-vmx_vmcs_shadow_test"

  PASS: Enable-EPT enabled; EPT memory type 6: vmlaunch succeeds
  FAIL: Enable-EPT enabled; EPT memory type 7: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 0: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 8: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 16: vmlaunch fails
  PASS: Enable-EPT enabled; EPT page walk length 24: vmlaunch succeeds
  FAIL: Enable-EPT enabled; EPT page walk length 32: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 40: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 48: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 56: vmlaunch fails
  INFO: Processor supports accessed and dirty flag
  PASS: Enable-EPT enabled; EPT accessed and dirty flag 0: vmlaunch succeeds
  PASS: Enable-EPT enabled; EPT accessed and dirty flag 1: vmlaunch succeeds
  PASS: Enable-EPT enabled; reserved bits [11:7] 0: vmlaunch succeeds
  FAIL: Enable-EPT enabled; reserved bits [11:7] 1: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 2: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 3: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 4: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 5: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 6: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 7: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 8: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 9: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 10: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 11: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 12: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 13: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 14: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 15: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 16: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 17: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 18: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 19: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 20: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 21: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 22: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 23: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 24: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 25: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 26: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 27: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 28: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 29: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 30: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 31: vmlaunch fails
  PASS: Enable-EPT enabled; reserved bits [63:N] 0: vmlaunch succeeds
  FAIL: Enable-EPT enabled; reserved bits [63:N] 1: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 2: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 4: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 8: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 16: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 32: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 64: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 128: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 256: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 512: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 1024: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 2048: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 4096: vmlaunch

[Kernel-packages] [Bug 1748103] Re: apic test in kvm-unit-test failed with timeout

** Tags added: sru-20210104

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

Title:
  apic test in kvm-unit-test failed with timeout

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in linux-azure package in Ubuntu:
  New
Status in linux-azure-edge package in Ubuntu:
  New
Status in linux source package in Xenial:
  New
Status in linux-azure source package in Xenial:
  New
Status in linux-azure-edge source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in linux-azure source package in Bionic:
  New
Status in linux-azure-edge source package in Bionic:
  New

Bug description:
  With Joshua's comment in bug 1719524: "Nested KVM can only be tried on
  instance sizes with nested Hypervisor support: Ev3 and Dv3.", although
  the instance name is E4v3 here but I can start a KVM on it.

  Test apic will timeout on it.

  Steps:
  1. git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  2. cd kvm-unit-tests; ./configure; make
  3. Run the apic test as root:
   
  # TESTNAME=apic TIMEOUT=30 ACCEL= ./x86/run x86/apic.flat -smp 2 -cpu 
qemu64,+x2apic,+tsc-deadline
  timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device 
pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial 
stdio -device pci-testdev -machine accel=kvm -kernel x86/apic.flat -smp 2 -cpu 
qemu64,+x2apic,+tsc-deadline # -initrd /tmp/tmp.onXtr5JVp7
  enabling apic
  enabling apic
  paging enabled
  cr0 = 80010011
  cr3 = 459000
  cr4 = 20
  apic version: 1050014
  PASS: apic existence
  PASS: xapic id matches cpuid
  PASS: writeable xapic id
  PASS: non-writeable x2apic id
  PASS: sane x2apic id
  FAIL: x2apic id matches cpuid
  PASS: correct xapic id after reset
  PASS: apic_disable: Local apic enabled
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set
  PASS: apic_disable: Local apic disabled
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is clear
  PASS: apic_disable: Local apic enabled
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set
  x2apic enabled
  PASS: x2apic enabled to invalid state
  PASS: x2apic enabled to apic enabled
  PASS: disabled to invalid state
  PASS: disabled to x2apic enabled
  PASS: apic enabled to invalid state
  PASS: apicbase: relocate apic
  PASS: apicbase: reserved physaddr bits
  PASS: apicbase: reserved low bits
  PASS: self ipi
  starting broadcast (x2apic)
  PASS: APIC physical broadcast address
  PASS: APIC physical broadcast shorthand
  PASS: nmi-after-sti
  qemu-system-x86_64: terminating on signal 15 from pid 7246

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.14.0-1004-azure-edge 4.14.0-1004.4
  ProcVersionSignature: User Name 4.14.0-1004.4-username-edge 4.14.14
  Uname: Linux 4.14.0-1004-azure-edge x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Feb  8 06:00:55 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-azure-edge
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  Package: linux-azure-edge
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: User Name 4.13.0-1009.12-username 4.13.13
  Tags:  xenial uec-images
  Uname: Linux 4.13.0-1009-azure x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy libvirtd lxd netdev plugdev 
sudo video
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1910541] Re: [SRU][G/H/U/OEM-5.10] re-enable s0ix of e1000e

2021-01-28 Thread You-Sheng Yang

** Tags added: oem-priority originate-from-1912754 somerville

** Tags added: originate-from-1912758

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

Title:
  [SRU][G/H/U/OEM-5.10] re-enable s0ix of e1000e

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Committed
Status in linux source package in Hirsute:
  In Progress

Bug description:
  [Impact]
  Due to s2idle failure on e1000e driver in ME enabled system, it disabled s0ix.
  Finally latest kernel accepted the bump up timeout value to fixed the issue.
  s0ix can be supported again.

  [Fix]
  Rebase the sauce patch to upstream patch, then support s0ix of e1000e.

  [Test Case]
  s2idle can work normally on ME enabled platform.

  [Where problems could occur]
  s2idle may fail to suspend on 2nd times.

  These patches are trying to revert the disabled s0ix patch in 5.8+,
  no need for 5.7- kernels.

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

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

[Kernel-packages] [Bug 1906102] Re: Drains lots of power under s2idle, can't wake up when using Deep

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

Title:
  Drains lots of power under s2idle, can't wake up when using Deep

Status in linux package in Ubuntu:
  Expired

Bug description:
  I have a laptop with i7-1165G7 and it suspend defaults to s2idle. It
  will drain 10% every hour.

  When switching to Deep using mem_sleep_default=deep (grub), the
  battery does not drain anymore but everytime I wake up from suspend
  the laptop shuts down.

  This is what my grub looks like

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i8042.reset i8042.nomux=1 
intel_idle.max_cstate=1 mem_sleep_default=deep acpi_sleep=nonvs
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jupiter 944 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-26 (1 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Notebook NV4XMB,ME,MZ
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-31-generic 
root=UUID=b1ae43f0-f126-4956-a280-078fe1f5e65f ro quiet splash i8042.reset 
i8042.nomux=1 intel_idle.max_cstate=1 mem_sleep_default=deep acpi_sleep=nonvs 
acpi_osi=Linux vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-31.33~20.04.1-generic 5.8.17
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-31-generic N/A
   linux-backports-modules-5.8.0-31-generic  N/A
   linux-firmware1.187.6
  Tags:  focal
  Uname: Linux 5.8.0-31-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: 09/07/2020
  dmi.bios.release: 7.1
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.01
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NV4XMB,ME,MZ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.1
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.01:bd09/07/2020:br7.1:efr7.1:svnNotebook:pnNV4XMB,ME,MZ:pvrNotApplicable:rvnNotebook:rnNV4XMB,ME,MZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NV4XMB,ME,MZ
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-11-26T23:26:30.152145

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

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

[Kernel-packages] [Bug 1911830] Re: alsa/sdw: support soundwire audio for TGL-H machines

2021-01-28 Thread Anthony Wong

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

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

Title:
  alsa/sdw: support soundwire audio for TGL-H machines

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  New
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-firmware source package in Focal:
  New
Status in linux-oem-5.10 source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  In the OEM project, we have a new TGL-H soundwire machine, with
  the current oem-5.10 kernel, the audio can't work.

  [Fix]
  Backport 6 patches from Intel thesofproject kernel.

  [Test]
  Put the testing sof-tgl-h.ri in the /lib/firmware/intel/sof,
  boot the patched kernel, we could see speakers and microphone
  from gnome-setting, and they all work well.

  
  [Where problems could occur]
  The patches changed soundwire machine driver, it is possible
  to make the audio on old soundwire machines not work anymore.
  But we tested the patches on TGL-U and cml soundwire machines,
  all worked well.

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

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

[Kernel-packages] [Bug 1907489] Re: restore reverted commit "crypto: arm64/sha - avoid non-standard inline asm tricks"

2021-01-28 Thread dann frazier

Verification:

ubuntu@anuchin:~$ cat /proc/version
Linux version 4.4.0-202-generic (buildd@bos02-arm64-077) (gcc version 5.4.0 
20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.12) ) #234-Ubuntu SMP Thu Jan 28 
02:06:34 UTC 2021
ubuntu@anuchin:~$ lsmod | grep sha
sha2_ce16384  0
sha1_ce16384  0


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

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

Title:
  restore reverted commit "crypto: arm64/sha - avoid non-standard inline
  asm tricks"

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  To address bug 1905336, we reverted an upstream commit. Upstream have now 
pulled in a commit to properly fix the underlying issue. Once we merge that 
fix, we should be able to reapply the reverted commit.

  [Test Case]
  If the kernel boots and we can still load the sha{1,2}_ce modules, we should 
be good.

  [Fix]
  After this is applied:
https://www.spinics.net/lists/stable/msg431217.html
  We should reapply the commit we reverted here:

https://kernel.ubuntu.com/git/ubuntu/ubuntu-xenial.git/commit/?id=4baa2fdd354700e2304e10cdbc64402621c3fa29

  
  [Where Problems May Occur]
  Although we shipped the reverted patch for many releases - the whole time we 
did so, the impacted modules were not loadable. Once we reapply it, xenial 
users will be running that code for the first time. If there are issues with 
the code, users of the sha{1,2}_ce modules may now hit them. Issues could 
include kernel oopses, corruption, etc.

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

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

[Kernel-packages] [Bug 1877533] Re: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted

2021-01-28 Thread Thadeu Lima de Souza Cascardo

** Patch added: "debdiff for hirsute"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877533/+attachment/5457887/+files/zipl_hirsute.patch

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

Title:
  [20.10 FEAT] Increase the crashkernel setting if the root volume is
  luks2-encrypted

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Invalid
Status in makedumpfile source package in Focal:
  In Progress
Status in linux source package in Groovy:
  Invalid
Status in makedumpfile source package in Groovy:
  In Progress

Bug description:
  Description:
  In case the volume containing the root filesystem is encrypted using LUKS2 
the memory used while unlocking the volume may exceed the size allocated to the 
kdump kernel. This will lead to a failure while processing kdump and the dump 
file will not be stored. Unfortunately, this condition may not be detected by a 
client before a problem occurs.
  The request is to have the kdump package installation script check for LUKS2 
encryption (more precisely for Argon2i PBKDF, which is the root cause of the 
high memory usage). If the condition is met, the installation procedure should 
increase the crashkernel parameter to a higher value (>=512M)or issue a 
warning, if the system memory is insufficient to reserve enough crashkernel 
memory.

  Business Case:
  Pervasive Encryption and Secure Execution require encryption of the 
filesystems in order to keep customer data secure at all times. With the 
increasing usage of these technologies, the number of kdump will rise too, 
typically at inconvenient times, when the kdump is triggered due to a real 
customer issue.
  With the suggested change, the number of customer complaints and effort to 
handle them will be reduced.

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

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

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

This change was made by a bot.

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

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

Title:
  linux-crashdump is not capable of mounting zfs root pools

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I could not get any crash logs after using this package.

  I tried using it and triggering a crash from a terminal. The alternate
  kernel boots successfully, but the initrd for linux-crashdump is not
  capable of loading my rpool.

  running: linux-crashdump:amd64 5.4.0.64.67

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-crashdump:amd64 (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Thu Jan 28 20:15:19 2021
  InstallationDate: Installed on 2019-08-15 (532 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  IwConfig:
   eno1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7885
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_fnpezh@/vmlinuz-5.4.0-65-generic 
root=ZFS=rpool/ROOT/ubuntu_fnpezh ro usbcore.autosuspend=-1 quiet splash 
intel_iommu=on iommu=pt vfio-pci.ids=10de:1b81,10de:10f0,1b21:1242 
video=efifb:off,vesafb=off,simplefb=off nouveau.modeset=0 
rd.driver.blacklist=nouveau,nvidia,nvidia_uvm,nvidia_drm,nvidia_modeset 
crashkernel=2096M-:2096M vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-65-generic N/A
   linux-backports-modules-5.4.0-65-generic  N/A
   linux-firmware1.187.8
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-22 (281 days ago)
  dmi.bios.date: 06/15/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.E0
  dmi.board.asset.tag: Default string
  dmi.board.name: X99A SLI PLUS(MS-7885)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.E0:bd06/15/2018:svnMSI:pnMS-7885:pvr1.0:rvnMSI:rnX99ASLIPLUS(MS-7885):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7885
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-03-23T10:46:45.197962

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

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

[Kernel-packages] [Bug 1913639] Re: linux-crashdump is not capable of mounting zfs root pools

2021-01-28 Thread Ubuntu Foundations Team Bug Bot

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

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

Title:
  linux-crashdump is not capable of mounting zfs root pools

Status in linux package in Ubuntu:
  New

Bug description:
  I could not get any crash logs after using this package.

  I tried using it and triggering a crash from a terminal. The alternate
  kernel boots successfully, but the initrd for linux-crashdump is not
  capable of loading my rpool.

  running: linux-crashdump:amd64 5.4.0.64.67

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-crashdump:amd64 (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Thu Jan 28 20:15:19 2021
  InstallationDate: Installed on 2019-08-15 (532 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  IwConfig:
   eno1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7885
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_fnpezh@/vmlinuz-5.4.0-65-generic 
root=ZFS=rpool/ROOT/ubuntu_fnpezh ro usbcore.autosuspend=-1 quiet splash 
intel_iommu=on iommu=pt vfio-pci.ids=10de:1b81,10de:10f0,1b21:1242 
video=efifb:off,vesafb=off,simplefb=off nouveau.modeset=0 
rd.driver.blacklist=nouveau,nvidia,nvidia_uvm,nvidia_drm,nvidia_modeset 
crashkernel=2096M-:2096M vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-65-generic N/A
   linux-backports-modules-5.4.0-65-generic  N/A
   linux-firmware1.187.8
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-22 (281 days ago)
  dmi.bios.date: 06/15/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.E0
  dmi.board.asset.tag: Default string
  dmi.board.name: X99A SLI PLUS(MS-7885)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.E0:bd06/15/2018:svnMSI:pnMS-7885:pvr1.0:rvnMSI:rnX99ASLIPLUS(MS-7885):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7885
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-03-23T10:46:45.197962

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

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

[Kernel-packages] [Bug 1913639] [NEW] linux-crashdump is not capable of mounting zfs root pools

You have been subscribed to a public bug:

I could not get any crash logs after using this package.

I tried using it and triggering a crash from a terminal. The alternate
kernel boots successfully, but the initrd for linux-crashdump is not
capable of loading my rpool.

running: linux-crashdump:amd64 5.4.0.64.67

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-crashdump:amd64 (not installed)
ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
Uname: Linux 5.4.0-65-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Thu Jan 28 20:15:19 2021
InstallationDate: Installed on 2019-08-15 (532 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
IwConfig:
 eno1  no wireless extensions.
 
 lono wireless extensions.
MachineType: MSI MS-7885
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_fnpezh@/vmlinuz-5.4.0-65-generic 
root=ZFS=rpool/ROOT/ubuntu_fnpezh ro usbcore.autosuspend=-1 quiet splash 
intel_iommu=on iommu=pt vfio-pci.ids=10de:1b81,10de:10f0,1b21:1242 
video=efifb:off,vesafb=off,simplefb=off nouveau.modeset=0 
rd.driver.blacklist=nouveau,nvidia,nvidia_uvm,nvidia_drm,nvidia_modeset 
crashkernel=2096M-:2096M vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-65-generic N/A
 linux-backports-modules-5.4.0-65-generic  N/A
 linux-firmware1.187.8
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2020-04-22 (281 days ago)
dmi.bios.date: 06/15/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.E0
dmi.board.asset.tag: Default string
dmi.board.name: X99A SLI PLUS(MS-7885)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.E0:bd06/15/2018:svnMSI:pnMS-7885:pvr1.0:rvnMSI:rnX99ASLIPLUS(MS-7885):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.family: Default string
dmi.product.name: MS-7885
dmi.product.sku: Default string
dmi.product.version: 1.0
dmi.sys.vendor: MSI
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2020-03-23T10:46:45.197962

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


** Tags: amd64 apport-bug focal
-- 
linux-crashdump is not capable of mounting zfs root pools
https://bugs.launchpad.net/bugs/1913639
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 1913442] Re: [Ubuntu 20.04] Problem leading IUCV service down (on s390x)

2021-01-28 Thread Frank Heimes

** Patch added: "backport of upstream commit 49f2d2419d60 to focal 5.4"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913442/+attachment/5457885/+files/commit_49f2d2419d60_backport.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/1913442

Title:
  [Ubuntu 20.04] Problem leading IUCV service down (on s390x)

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

Bug description:
  When I deployed a Ubuntu20.04 instance with kernel version of
  5.4.0-58-generic under z/VM, I saw below messages from kernel and the
  iucvserv program malfunctioned. Hence it caused some devices like
  network device configuration failure and deployment failure.

  
  Dec 14 22:02:26 ub2004img iucvserv: Receive OPNCLD4 0.0.0.1 pwd sent from 
IUCV client.
  Dec 14 22:02:26 ub2004img iucvserv: /etc/iucv_authorized_userid exists, check 
authorization.
  Dec 14 22:02:26 ub2004img iucvserv: senduserid=OPNCLD4, authuserid=OPNCLD4, 
len=7
  Dec 14 22:02:26 ub2004img iucvserv: Current version is 0.0.0.1, upgraded 
version is 0.0.0.1
  Dec 14 22:02:26 ub2004img iucvserv: Will execute the linux command pwd  2>&1; 
echo iucvcmdrc=$? sent from IUCV client.
  Dec 14 22:02:26 ub2004img iucvserv: result length=14, send message 
length=14,#012 /#012iucvcmdrc=0
  Dec 14 22:02:26 ub2004img kernel: [63084.184649] [ cut here 
]
  Dec 14 22:02:26 ub2004img kernel: [63084.184654] Bad or missing usercopy 
whitelist? Kernel memory exposure attempt detected from SLUB object 
'dma-kmalloc-1k' (offset 0, size 20)!
  Dec 14 22:02:26 ub2004img kernel: [63084.184680] WARNING: CPU: 1 PID: 697 at 
mm/usercopy.c:75 usercopy_warn+0xa0/0xd0
  Dec 14 22:02:26 ub2004img kernel: [63084.184681] Modules linked in: tcp_diag 
udp_diag raw_diag inet_diag unix_diag xt_CT iptable_raw ipt_REJECT 
nf_reject_ipv4 xt_tcpudp xt_conntrack nf_conntrack nf_defr
  ag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter af_iucv nls_utf8 isofs 
dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua vmur vfio_ccw vfio_mdev mdev 
s390_trng vfio_iommu_type1 vfio sch_fq_codel drm drm
  _panel_orientation_quirks i2c_core ip_tables x_tables btrfs zstd_compress 
zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 linear
   pkey zcrypt crc32_vx_s390 ghash_s390 prng aes_s390 des_s390 libdes 
sha3_512_s390 sha3_256_s390 sha512_s390 sha256_s390 sha1_s390 sha_common 
dasd_fba_mod dasd_mod qeth_l2 qeth qdio ccwgroup
  Dec 14 22:02:26 ub2004img kernel: [63084.184718] CPU: 1 PID: 697 Comm: 
iucvserv Not tainted 5.4.0-58-generic #64-Ubuntu
  Dec 14 22:02:26 ub2004img kernel: [63084.184718] Hardware name: IBM 8561 LT1 
400 (z/VM 7.1.0)
  Dec 14 22:02:26 ub2004img kernel: [63084.184719] Krnl PSW : 0704c0018000 
b3c37a60 (usercopy_warn+0xa0/0xd0)
  Dec 14 22:02:26 ub2004img kernel: [63084.184721]R:0 T:1 IO:1 EX:1 
Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3
  Dec 14 22:02:26 ub2004img kernel: [63084.184722] Krnl GPRS: 0004 
0006 0081 0007
  Dec 14 22:02:26 ub2004img kernel: [63084.184722]0007 
f2ecb400 b43fdc6a 03e00014
  Dec 14 22:02:26 ub2004img kernel: [63084.184723] 
0014  b43f01f0
  Dec 14 22:02:26 ub2004img kernel: [63084.184723]aae13300 
e9332a00 b3c37a5c 03e000987a10
  Dec 14 22:02:26 ub2004img kernel: [63084.184728] Krnl Code: b3c37a50: 
c020003e310f  larl%r2,b43fdc6e
  Dec 14 22:02:26 ub2004img kernel: [63084.184728]b3c37a56: 
c0e5ffedbe85  brasl   %r14,b39ef760
  Dec 14 22:02:26 ub2004img kernel: [63084.184728]   #b3c37a5c: 
a7f40001  brc 15,b3c37a5e
  Dec 14 22:02:26 ub2004img kernel: [63084.184728]   >b3c37a60: 
eb6ff0c4  lmg %r6,%r15,192(%r15)
  Dec 14 22:02:26 ub2004img kernel: [63084.184728]b3c37a66: 
07fe  bcr 15,%r14
  Dec 14 22:02:26 ub2004img kernel: [63084.184728]b3c37a68: 
47000700  bc  0,1792
  Dec 14 22:02:26 ub2004img kernel: [63084.184728]b3c37a6c: 
c020003e30fa  larl%r2,b43fdc60
  Dec 14 22:02:26 ub2004img kernel: [63084.184728]b3c37a72: 
a7f4ffd4  brc 15,b3c37a1a
  Dec 14 22:02:26 ub2004img kernel: [63084.184735] Call Trace:
  Dec 14 22:02:26 ub2004img kernel: [63084.184736] ([] 
usercopy_warn+0x9c/0xd0)
  Dec 14 22:02:26 ub2004img kernel: [63084.184740]  [] 
__check_heap_object+0xd8/0x150
  Dec 14 22:02:26 ub2004img kernel: [63084.184741]  []

[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Update (based on #296)
  =

  The latest kernel tree
  (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
  has the complete solution to fix this bug. So we can expect kernel
  v5.11 to fix this issue without any additional work.

  Before the release of v5.11, you are suggested to use #189 to save your 
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd 
driver is built into the initramfs. So you have to rebuild the initramfs after 
replacing the old module with new one.
  On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs 
-u`.

  The complete solution is three patches,
   - 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce 
filter setting in IRQ type setting")
   - 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way 
to disable debounce filter")
   - 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into 
account debounce settings")

  The first two patches has reached the stable tree. If the last one is
  also backported to LTS kernel, you won't need to install kernel 5.11.
  But I don't know when this will happen.

  Original bug report
  ===

  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3

[Kernel-packages] [Bug 1908428] Re: 4.4 kernel panics in kvm wake_up() handler

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

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

Title:
  4.4 kernel panics in kvm wake_up() handler

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  [Description]

  User reported that 4.4 kernels are affected by the bug in [1].

  The bug presents itself with the following trace :

  [219901.424329] CPU: 19 PID: 0 Comm: swapper/19 Tainted: G   OE   
4.4.0-133-generic #159~14.04.1-Ubuntu
  [219901.441800] task: 885f62e63fc0 ti: 885f62e7c000 task.ti: 
885f62e7c000
  [219901.449408] RIP: 0010:[]  [] 
wakeup_handler+0x6d/0xa0 [kvm_intel]
  [219901.458791] RSP: 0018:885f7c043f70  EFLAGS: 00010083
  [219901.464217] RAX: 885f7c04 RBX: dead00b8 RCX: 
885f7c0586c0
  [219901.471480] RDX: dead0100 RSI:  RDI: 
885f7c0586b0
  [219901.478741] RBP: 885f7c043f90 R08:  R09: 
c7ffc2ec9069
  [219901.486003] R10: 0494 R11: 885f7c057370 R12: 
000186b0
  [219901.493267] R13: 0013 R14: 000186c0 R15: 
885f62e7c000
  [219901.500528] FS:  () GS:885f7c04() 
knlGS:
  [219901.511738] CS:  0010 DS:  ES:  CR0: 80050033
  [219901.517597] CR2: 7f6d57098000 CR3: 003183dfe000 CR4: 
00362670
  [219901.524860] DR0:  DR1:  DR2: 

  [219901.532121] DR3:  DR6: fffe0ff0 DR7: 
0400
  [219901.539384] Stack:
  [219901.541509]   0013  

  [219901.549120]  885f7c043fa8 8102fa99 81f40200 
885f62e7fe98
  [219901.556747]  8182131f 885f62e7fde8   885f62e7c000 

  [219901.565006] Call Trace:
  [219901.567567]  
  [219901.569592]  [] smp_kvm_posted_intr_wakeup_ipi+0x59/0x70
  [219901.576795]  [] kvm_posted_intr_wakeup_ipi+0xbf/0xd0
  [219901.583431]  
  [219901.585456]  [] ? hard_disable_TSC+0x30/0x30
  [219901.591621]  [] ? native_safe_halt+0x6/0x10
  [219901.597479]  [] default_idle+0x1e/0xe0
  [219901.602900]  [] arch_cpu_idle+0x15/0x20
  [219901.608416]  [] default_idle_call+0x2a/0x40
  [219901.614270]  [] cpu_startup_entry+0x2e0/0x350
  [219901.620305]  [] start_secondary+0x16c/0x190

  The root cause is blocked_vcpu_on_cpu list is corrupted.
  This bug is fixed  with the patchset found in [2].
  Only the first 3 (out of 4) of them have made their way in upstream kernel and
  are the ones needed to fix the bug.

  [Test case]
  It was not possible to reproduce this bug locally.
  A test kernel with the fixing patches has been provided to the user and they 
confirmed that it resolves the issue.

  [Regression Potential]

  The patches have been accepted upstream in 4.14 and so far there are no known 
regressions.
  Backporting the patches was necessary; original patches modify 
pi_pre/post_block functions which are not present in 4.4.
  These functions are introduced by upstream commit bc22512bb24c(kvm: vmx: 
rename vmx_pre/post_block to pi_pre/post_block).
  Appropriate changes where made for the patches to modify vmx_pre/post_block 
function without changing the functionality of the patches.
  Testing has not revealed any regressions.

  
  [Other]

  Only 4.4 kernels are affected.

  
  [1] https://marc.info/?l=kvm=149559827906211=2
  [2] https://lore.kernel.org/lkml/20170606105707.23207-1-pbonz...@redhat.com/

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

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

[Kernel-packages] [Bug 1907489] Re: restore reverted commit "crypto: arm64/sha - avoid non-standard inline asm tricks"

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

** Tags added: verification-needed-xenial

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

Title:
restore reverted commit "crypto: arm64/sha - avoid non-standard inline
asm tricks"

Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
Fix Committed

Bug description:
[Impact]
To address bug 1905336, we reverted an upstream commit. Upstream have now
pulled in a commit to properly fix the underlying issue. Once we merge that
fix, we should be able to reapply the reverted commit.

[Test Case]
If the kernel boots and we can still load the sha{1,2}_ce modules, we should
be good.

[Fix]
After this is applied:
https://www.spinics.net/lists/stable/msg431217.html
We should reapply the commit we reverted here:

https://kernel.ubuntu.com/git/ubuntu/ubuntu-xenial.git/commit/?id=4baa2fdd354700e2304e10cdbc64402621c3fa29

[Where Problems May Occur]
Although we shipped the reverted patch for many releases - the whole time we
did so, the impacted modules were not loadable. Once we reapply it, xenial
users will be running that code for the first time. If there are issues with
the code, users of the sha{1,2}_ce modules may now hit them. Issues could
include kernel oopses, corruption, etc.

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

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

[Kernel-packages] [Bug 1908710] Re: errinjct open fails on IBM POWER LPAR

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

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

Title:
  errinjct open fails on IBM POWER LPAR

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  errinjct open fails on IBM POWER LPAR. That prevents error injection tests to 
be performed.

  [Test case]
  Run errinjct open on an LPAR.
  Success case:
  $ sudo errinjct open
  RTAS error injection facility open, token = 1
  Failure case:
  $ sudo errinjct open
  errinjct: Could not open RTAS error injection facility

  errinjct: librtas: open: Unexpected I/O error

  
  [Fix]
  Typo in RTAS filters.

  [Regression potential]
  errinjct could still be broken, or other RTAS operations could break, which 
could even prevent booting on any IBM POWER systems.

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

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

[Kernel-packages] [Bug 1910639] Re: DMI entry syntax fix for Pegatron / ByteSpeed C15B

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

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

Title:
  DMI entry syntax fix for Pegatron / ByteSpeed C15B

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Committed
Status in linux source package in Hirsute:
  Incomplete

Bug description:
  [Impact]
  Upstream reports that when compiling the kernel with a48491c65b51 ("Input: 
i8042 - add ByteSpeed touchpad to noloop table"), g++ will complain about:
  drivers/input/serio/i8042-x86ia64io.h:225:3: error: ‘.matches’ designator 
used multiple times in the same initializer list

  C99 semantics is that last duplicated initialiser wins,
  so DMI entry gets overwritten.

  [Fix]
  * a3a9060ecad030 ("Input: i8042 - unbreak Pegatron C15B") in linux-next

  This can be cherry-picked into all the affected series.
  Note that patch for bug 1906128 should be applied first.

  [Test]
  I didn't get this error while building the test kernels for bug 1906128 on 
builder kathleen, with fakeroot commands.

  So the only thing that I can test is to build them again and make sure
  there is no other issues.

  [Where problems could occur]
  If this fix is incorrect it might affect the touchpad support on Pegatron / 
ByteSpeed C15B laptop.

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

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

[Kernel-packages] [Bug 1913215] WifiSyslog.txt

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1913215/+attachment/5457857/+files/WifiSyslog.txt

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

Title:
  Random kernel bugs on nouveau driver and NVidia 1070 Ti

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The issue exists for quite some time already. The affected UI freezes and 
luckily while using the new KDE beta only the desktop freezes. Before I had to 
do a hard reset since nothing was responding to key presses.
  Hope there are enough debug info attached by apport_cli to the bug report.

  If there is any way I can help, please ask! :)

  Thanks
  - Thomas

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.8.0-36-generic 5.8.0-36.40+21.04.1
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  NonfreeKernelModules: rcraid
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Jan 25 21:32:22 2021
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=7252ebf2-954b-4560-87a0-ace5e9c25fbe ro nouveau.runpm=0 quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-36-generic N/A
   linux-backports-modules-5.8.0-36-generic  N/A
   linux-firmware1.194
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X470-PRO
  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.:bvr5809:bd12/03/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO: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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  DistroRelease: Ubuntu 21.04
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: rcraid
  Package: linux (not installed)
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=7252ebf2-954b-4560-87a0-ace5e9c25fbe ro nouveau.runpm=0 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  RebootRequiredPkgs: evolution-data-server
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-36-generic N/A
   linux-backports-modules-5.8.0-36-generic  N/A
   linux-firmware1.194
  Tags:  hirsute
  Uname: Linux 5.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm apt-mirror audio avahi avahi-autoipd bin bluetooth cdrom 
chrome-remote-desktop colord crontab daemon davfs2 debian-tor dialout disk 
docker fax floppy fuse games i2c icecc kmem kvm libvirt libvirt-dnsmasq lightdm 
lp lpadmin mail man mythtv netdev news nm-openconnect ntp nvidia-persistenced 
operator plugdev proxy pulse root rtkit sambashare saned scanner science shadow 
ssh sudo sys syslog systemd-bus-proxy systemd-journal systemd-journal-remote 
systemd-network systemd-resolve systemd-timesync tape tty users uucp video 
voice weston-launch whoopsie www-data
  _MarkForUpload: True
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 12/03/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X470-PRO
  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

[Kernel-packages] [Bug 1913215] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1913215/+attachment/5457851/+files/ProcEnviron.txt

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

Title:
  Random kernel bugs on nouveau driver and NVidia 1070 Ti

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The issue exists for quite some time already. The affected UI freezes and 
luckily while using the new KDE beta only the desktop freezes. Before I had to 
do a hard reset since nothing was responding to key presses.
  Hope there are enough debug info attached by apport_cli to the bug report.

  If there is any way I can help, please ask! :)

  Thanks
  - Thomas

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.8.0-36-generic 5.8.0-36.40+21.04.1
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  NonfreeKernelModules: rcraid
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Jan 25 21:32:22 2021
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=7252ebf2-954b-4560-87a0-ace5e9c25fbe ro nouveau.runpm=0 quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-36-generic N/A
   linux-backports-modules-5.8.0-36-generic  N/A
   linux-firmware1.194
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X470-PRO
  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.:bvr5809:bd12/03/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO: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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  DistroRelease: Ubuntu 21.04
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: rcraid
  Package: linux (not installed)
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=7252ebf2-954b-4560-87a0-ace5e9c25fbe ro nouveau.runpm=0 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  RebootRequiredPkgs: evolution-data-server
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-36-generic N/A
   linux-backports-modules-5.8.0-36-generic  N/A
   linux-firmware1.194
  Tags:  hirsute
  Uname: Linux 5.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm apt-mirror audio avahi avahi-autoipd bin bluetooth cdrom 
chrome-remote-desktop colord crontab daemon davfs2 debian-tor dialout disk 
docker fax floppy fuse games i2c icecc kmem kvm libvirt libvirt-dnsmasq lightdm 
lp lpadmin mail man mythtv netdev news nm-openconnect ntp nvidia-persistenced 
operator plugdev proxy pulse root rtkit sambashare saned scanner science shadow 
ssh sudo sys syslog systemd-bus-proxy systemd-journal systemd-journal-remote 
systemd-network systemd-resolve systemd-timesync tape tty users uucp video 
voice weston-launch whoopsie www-data
  _MarkForUpload: True
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 12/03/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X470-PRO
  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

[Kernel-packages] [Bug 1913215] Re: Random kernel bugs on nouveau driver and NVidia 1070 Ti

[ 3571.565465] BUG: kernel NULL pointer dereference, address: 0008
[ 3571.565468] #PF: supervisor read access in kernel mode
[ 3571.565469] #PF: error_code(0x) - not-present page
[ 3571.565470] PGD 0 P4D 0 
[ 3571.565472] Oops:  [#1] SMP NOPTI
[ 3571.565474] CPU: 0 PID: 1870 Comm: Xorg Tainted: P   O  
5.8.0-36-generic #40+21.04.1-Ubuntu
[ 3571.565475] Hardware name: System manufacturer System Product Name/PRIME 
X470-PRO, BIOS 5809 12/03/2020
[ 3571.565507] RIP: 0010:gp100_vmm_pgt_mem+0xca/0x180 [nouveau]
[ 3571.565508] Code: ff 49 89 7e 50 8b 45 c8 41 89 c5 8d 44 02 01 89 45 d4 41 
0f b7 57 12 49 8b 7f 08 46 8d 24 ea 48 8b 57 08 41 83 c5 01 4c 89 e6 <48> 8b 4a 
08 89 da e8 5b 39 21 d4 49 8b 7f 08 48 89 da 49 8d 74 24
[ 3571.565509] RSP: 0018:a46342343698 EFLAGS: 00010202
[ 3571.565510] RAX: 0008 RBX: fe970001 RCX: 0010
[ 3571.565511] RDX:  RSI: 0b00 RDI: 97a7c84e2c80
[ 3571.565511] RBP: a463423436d0 R08: a463423438a8 R09: 0008
[ 3571.565512] R10:  R11:  R12: 0b00
[ 3571.565513] R13: 0001 R14: a463423438a8 R15: 97a75dc360c0
[ 3571.565514] FS:  7f83e5e98a40() GS:97a8ee80() 
knlGS:
[ 3571.565514] CS:  0010 DS:  ES:  CR0: 80050033
[ 3571.565515] CR2: 0008 CR3: 000f98c26000 CR4: 003406f0
[ 3571.565516] Call Trace:
[ 3571.565541]  nvkm_vmm_iter.constprop.0+0x275/0x480 [nouveau]
[ 3571.565566]  ? gp100_vmm_pgt_sgl+0x180/0x180 [nouveau]
[ 3571.565589]  ? gp100_vmm_pgt_sgl+0x180/0x180 [nouveau]
[ 3571.565612]  ? nvkm_vmm_ref_sptes.isra.0+0x1b0/0x1b0 [nouveau]
[ 3571.565636]  nvkm_vmm_ptes_get_map+0x31/0xa0 [nouveau]
[ 3571.565658]  ? nvkm_vmm_ref_sptes.isra.0+0x1b0/0x1b0 [nouveau]
[ 3571.565681]  ? gp100_vmm_pgt_sgl+0x180/0x180 [nouveau]
[ 3571.565704]  nvkm_vmm_map_locked+0x1b9/0x330 [nouveau]
[ 3571.565727]  nvkm_vmm_map+0x49/0x70 [nouveau]
[ 3571.565747]  nvkm_vram_map+0x58/0x80 [nouveau]
[ 3571.565770]  nvkm_uvmm_mthd_map.isra.0+0x1d6/0x270 [nouveau]
[ 3571.565793]  nvkm_uvmm_mthd+0x4e/0x390 [nouveau]
[ 3571.565816]  ? nvkm_vmm_node_insert+0x69/0x80 [nouveau]
[ 3571.565838]  ? nvkm_vmm_get_locked+0x378/0x520 [nouveau]
[ 3571.565855]  nvkm_object_mthd+0x1a/0x30 [nouveau]
[ 3571.565871]  nvkm_ioctl_mthd+0x65/0x70 [nouveau]
[ 3571.565888]  nvkm_ioctl+0xf0/0x190 [nouveau]
[ 3571.565912]  nvkm_client_ioctl+0x12/0x20 [nouveau]
[ 3571.565928]  nvif_object_ioctl+0x4e/0x60 [nouveau]
[ 3571.565944]  nvif_object_mthd+0x124/0x150 [nouveau]
[ 3571.565969]  ? nvkm_client_ioctl+0x12/0x20 [nouveau]
[ 3571.565985]  ? nvif_object_ioctl+0x4e/0x60 [nouveau]
[ 3571.566001]  ? nvif_object_mthd+0x139/0x150 [nouveau]
[ 3571.566017]  nvif_vmm_map+0x112/0x130 [nouveau]
[ 3571.566041]  nouveau_mem_map+0x8b/0xf0 [nouveau]
[ 3571.566065]  nouveau_vma_new+0x1b7/0x1e0 [nouveau]
[ 3571.566089]  nouveau_gem_object_open+0xdd/0x150 [nouveau]
[ 3571.566105]  drm_gem_handle_create_tail+0xe7/0x1b0 [drm]
[ 3571.566114]  drm_gem_prime_fd_to_handle+0xfe/0x1a0 [drm]
[ 3571.566123]  ? drm_prime_destroy_file_private+0x20/0x20 [drm]
[ 3571.566132]  drm_prime_fd_to_handle_ioctl+0x27/0x30 [drm]
[ 3571.566140]  drm_ioctl_kernel+0xae/0xf0 [drm]
[ 3571.566147]  drm_ioctl+0x238/0x3d0 [drm]
[ 3571.566156]  ? drm_prime_destroy_file_private+0x20/0x20 [drm]
[ 3571.566159]  ? hrtimer_start_range_ns+0x84/0xd0
[ 3571.566183]  nouveau_drm_ioctl+0x66/0xc0 [nouveau]
[ 3571.566185]  ksys_ioctl+0x8e/0xc0
[ 3571.566186]  __x64_sys_ioctl+0x1a/0x20
[ 3571.566188]  do_syscall_64+0x49/0xc0
[ 3571.566190]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 3571.566191] RIP: 0033:0x7f83e631913b
[ 3571.566193] Code: 89 d8 49 8d 3c 1c 48 f7 d8 49 39 c4 72 b5 e8 1c ff ff ff 
85 c0 78 ba 4c 89 e0 5b 5d 41 5c c3 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d fd 2c 0d 00 f7 d8 64 89 01 48
[ 3571.566193] RSP: 002b:7ffedc52f0d8 EFLAGS: 0246 ORIG_RAX: 
0010
[ 3571.566194] RAX: ffda RBX: 7ffedc52f11c RCX: 7f83e631913b
[ 3571.566195] RDX: 7ffedc52f11c RSI: c00c642e RDI: 0014
[ 3571.566195] RBP: c00c642e R08: 561859800c20 R09: 561859800c20
[ 3571.566196] R10: 0007 R11: 0246 R12: 007b
[ 3571.566197] R13: 0014 R14: 561858819f38 R15: 
[ 3571.566198] Modules linked in: veth nf_conntrack_netlink xfrm_user xfrm_algo 
xt_addrtype br_netfilter md4 vboxnetadp(O) vboxnetflt(O) vboxdrv(O) nls_utf8 
cifs fscache libdes xt_CHECKSUM xt_MASQUERADE snd_seq_dummy snd_hrtimer snd_seq 
bridge stp llc aufs evdi(O) ip6t_REJECT nf_reject_ipv6 ip6t_rpfilter ipt_REJECT 
nf_reject_ipv4 xt_conntrack nf_conntrack_netbios_ns nf_conntrack_broadcast 
xt_CT xt_tcpudp nft_counter overlay nft_chain_nat nf_nat nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 ip6_tables nft_compat ip_set nf_tables nfnetlink

[Kernel-packages] [Bug 1913215] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1913215/+attachment/5457852/+files/ProcInterrupts.txt

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

Title:
  Random kernel bugs on nouveau driver and NVidia 1070 Ti

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The issue exists for quite some time already. The affected UI freezes and 
luckily while using the new KDE beta only the desktop freezes. Before I had to 
do a hard reset since nothing was responding to key presses.
  Hope there are enough debug info attached by apport_cli to the bug report.

  If there is any way I can help, please ask! :)

  Thanks
  - Thomas

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.8.0-36-generic 5.8.0-36.40+21.04.1
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  NonfreeKernelModules: rcraid
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Jan 25 21:32:22 2021
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=7252ebf2-954b-4560-87a0-ace5e9c25fbe ro nouveau.runpm=0 quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-36-generic N/A
   linux-backports-modules-5.8.0-36-generic  N/A
   linux-firmware1.194
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X470-PRO
  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.:bvr5809:bd12/03/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO: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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  DistroRelease: Ubuntu 21.04
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: rcraid
  Package: linux (not installed)
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=7252ebf2-954b-4560-87a0-ace5e9c25fbe ro nouveau.runpm=0 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  RebootRequiredPkgs: evolution-data-server
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-36-generic N/A
   linux-backports-modules-5.8.0-36-generic  N/A
   linux-firmware1.194
  Tags:  hirsute
  Uname: Linux 5.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm apt-mirror audio avahi avahi-autoipd bin bluetooth cdrom 
chrome-remote-desktop colord crontab daemon davfs2 debian-tor dialout disk 
docker fax floppy fuse games i2c icecc kmem kvm libvirt libvirt-dnsmasq lightdm 
lp lpadmin mail man mythtv netdev news nm-openconnect ntp nvidia-persistenced 
operator plugdev proxy pulse root rtkit sambashare saned scanner science shadow 
ssh sudo sys syslog systemd-bus-proxy systemd-journal systemd-journal-remote 
systemd-network systemd-resolve systemd-timesync tape tty users uucp video 
voice weston-launch whoopsie www-data
  _MarkForUpload: True
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 12/03/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X470-PRO
  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

[Kernel-packages] [Bug 1913215] PulseList.txt

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1913215/+attachment/5457854/+files/PulseList.txt

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

Title:
  Random kernel bugs on nouveau driver and NVidia 1070 Ti

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The issue exists for quite some time already. The affected UI freezes and 
luckily while using the new KDE beta only the desktop freezes. Before I had to 
do a hard reset since nothing was responding to key presses.
  Hope there are enough debug info attached by apport_cli to the bug report.

  If there is any way I can help, please ask! :)

  Thanks
  - Thomas

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.8.0-36-generic 5.8.0-36.40+21.04.1
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  NonfreeKernelModules: rcraid
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Jan 25 21:32:22 2021
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=7252ebf2-954b-4560-87a0-ace5e9c25fbe ro nouveau.runpm=0 quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-36-generic N/A
   linux-backports-modules-5.8.0-36-generic  N/A
   linux-firmware1.194
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X470-PRO
  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.:bvr5809:bd12/03/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO: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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  DistroRelease: Ubuntu 21.04
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: rcraid
  Package: linux (not installed)
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=7252ebf2-954b-4560-87a0-ace5e9c25fbe ro nouveau.runpm=0 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  RebootRequiredPkgs: evolution-data-server
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-36-generic N/A
   linux-backports-modules-5.8.0-36-generic  N/A
   linux-firmware1.194
  Tags:  hirsute
  Uname: Linux 5.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm apt-mirror audio avahi avahi-autoipd bin bluetooth cdrom 
chrome-remote-desktop colord crontab daemon davfs2 debian-tor dialout disk 
docker fax floppy fuse games i2c icecc kmem kvm libvirt libvirt-dnsmasq lightdm 
lp lpadmin mail man mythtv netdev news nm-openconnect ntp nvidia-persistenced 
operator plugdev proxy pulse root rtkit sambashare saned scanner science shadow 
ssh sudo sys syslog systemd-bus-proxy systemd-journal systemd-journal-remote 
systemd-network systemd-resolve systemd-timesync tape tty users uucp video 
voice weston-launch whoopsie www-data
  _MarkForUpload: True
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 12/03/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X470-PRO
  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

[Kernel-packages] [Bug 1913215] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1913215/+attachment/5457856/+files/UdevDb.txt

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

Title:
  Random kernel bugs on nouveau driver and NVidia 1070 Ti

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The issue exists for quite some time already. The affected UI freezes and 
luckily while using the new KDE beta only the desktop freezes. Before I had to 
do a hard reset since nothing was responding to key presses.
  Hope there are enough debug info attached by apport_cli to the bug report.

  If there is any way I can help, please ask! :)

  Thanks
  - Thomas

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.8.0-36-generic 5.8.0-36.40+21.04.1
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  NonfreeKernelModules: rcraid
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Jan 25 21:32:22 2021
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=7252ebf2-954b-4560-87a0-ace5e9c25fbe ro nouveau.runpm=0 quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-36-generic N/A
   linux-backports-modules-5.8.0-36-generic  N/A
   linux-firmware1.194
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X470-PRO
  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.:bvr5809:bd12/03/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO: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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  DistroRelease: Ubuntu 21.04
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: rcraid
  Package: linux (not installed)
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=7252ebf2-954b-4560-87a0-ace5e9c25fbe ro nouveau.runpm=0 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  RebootRequiredPkgs: evolution-data-server
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-36-generic N/A
   linux-backports-modules-5.8.0-36-generic  N/A
   linux-firmware1.194
  Tags:  hirsute
  Uname: Linux 5.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm apt-mirror audio avahi avahi-autoipd bin bluetooth cdrom 
chrome-remote-desktop colord crontab daemon davfs2 debian-tor dialout disk 
docker fax floppy fuse games i2c icecc kmem kvm libvirt libvirt-dnsmasq lightdm 
lp lpadmin mail man mythtv netdev news nm-openconnect ntp nvidia-persistenced 
operator plugdev proxy pulse root rtkit sambashare saned scanner science shadow 
ssh sudo sys syslog systemd-bus-proxy systemd-journal systemd-journal-remote 
systemd-network systemd-resolve systemd-timesync tape tty users uucp video 
voice weston-launch whoopsie www-data
  _MarkForUpload: True
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 12/03/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X470-PRO
  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:

[Kernel-packages] [Bug 1913215] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1913215/+attachment/5457853/+files/ProcModules.txt

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

Title:
  Random kernel bugs on nouveau driver and NVidia 1070 Ti

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The issue exists for quite some time already. The affected UI freezes and 
luckily while using the new KDE beta only the desktop freezes. Before I had to 
do a hard reset since nothing was responding to key presses.
  Hope there are enough debug info attached by apport_cli to the bug report.

  If there is any way I can help, please ask! :)

  Thanks
  - Thomas

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.8.0-36-generic 5.8.0-36.40+21.04.1
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  NonfreeKernelModules: rcraid
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Jan 25 21:32:22 2021
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=7252ebf2-954b-4560-87a0-ace5e9c25fbe ro nouveau.runpm=0 quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-36-generic N/A
   linux-backports-modules-5.8.0-36-generic  N/A
   linux-firmware1.194
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X470-PRO
  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.:bvr5809:bd12/03/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO: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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  DistroRelease: Ubuntu 21.04
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: rcraid
  Package: linux (not installed)
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=7252ebf2-954b-4560-87a0-ace5e9c25fbe ro nouveau.runpm=0 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  RebootRequiredPkgs: evolution-data-server
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-36-generic N/A
   linux-backports-modules-5.8.0-36-generic  N/A
   linux-firmware1.194
  Tags:  hirsute
  Uname: Linux 5.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm apt-mirror audio avahi avahi-autoipd bin bluetooth cdrom 
chrome-remote-desktop colord crontab daemon davfs2 debian-tor dialout disk 
docker fax floppy fuse games i2c icecc kmem kvm libvirt libvirt-dnsmasq lightdm 
lp lpadmin mail man mythtv netdev news nm-openconnect ntp nvidia-persistenced 
operator plugdev proxy pulse root rtkit sambashare saned scanner science shadow 
ssh sudo sys syslog systemd-bus-proxy systemd-journal systemd-journal-remote 
systemd-network systemd-resolve systemd-timesync tape tty users uucp video 
voice weston-launch whoopsie www-data
  _MarkForUpload: True
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 12/03/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X470-PRO
  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

[Kernel-packages] [Bug 1913215] RfKill.txt

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1913215/+attachment/5457855/+files/RfKill.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/1913215

Title:
  Random kernel bugs on nouveau driver and NVidia 1070 Ti

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The issue exists for quite some time already. The affected UI freezes and 
luckily while using the new KDE beta only the desktop freezes. Before I had to 
do a hard reset since nothing was responding to key presses.
  Hope there are enough debug info attached by apport_cli to the bug report.

  If there is any way I can help, please ask! :)

  Thanks
  - Thomas

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.8.0-36-generic 5.8.0-36.40+21.04.1
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  NonfreeKernelModules: rcraid
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Jan 25 21:32:22 2021
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=7252ebf2-954b-4560-87a0-ace5e9c25fbe ro nouveau.runpm=0 quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-36-generic N/A
   linux-backports-modules-5.8.0-36-generic  N/A
   linux-firmware1.194
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X470-PRO
  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.:bvr5809:bd12/03/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO: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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  DistroRelease: Ubuntu 21.04
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: rcraid
  Package: linux (not installed)
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=7252ebf2-954b-4560-87a0-ace5e9c25fbe ro nouveau.runpm=0 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  RebootRequiredPkgs: evolution-data-server
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-36-generic N/A
   linux-backports-modules-5.8.0-36-generic  N/A
   linux-firmware1.194
  Tags:  hirsute
  Uname: Linux 5.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm apt-mirror audio avahi avahi-autoipd bin bluetooth cdrom 
chrome-remote-desktop colord crontab daemon davfs2 debian-tor dialout disk 
docker fax floppy fuse games i2c icecc kmem kvm libvirt libvirt-dnsmasq lightdm 
lp lpadmin mail man mythtv netdev news nm-openconnect ntp nvidia-persistenced 
operator plugdev proxy pulse root rtkit sambashare saned scanner science shadow 
ssh sudo sys syslog systemd-bus-proxy systemd-journal systemd-journal-remote 
systemd-network systemd-resolve systemd-timesync tape tty users uucp video 
voice weston-launch whoopsie www-data
  _MarkForUpload: True
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 12/03/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X470-PRO
  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:

[Kernel-packages] [Bug 1913215] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1913215/+attachment/5457850/+files/ProcCpuinfoMinimal.txt

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

Title:
  Random kernel bugs on nouveau driver and NVidia 1070 Ti

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The issue exists for quite some time already. The affected UI freezes and 
luckily while using the new KDE beta only the desktop freezes. Before I had to 
do a hard reset since nothing was responding to key presses.
  Hope there are enough debug info attached by apport_cli to the bug report.

  If there is any way I can help, please ask! :)

  Thanks
  - Thomas

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.8.0-36-generic 5.8.0-36.40+21.04.1
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  NonfreeKernelModules: rcraid
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Jan 25 21:32:22 2021
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=7252ebf2-954b-4560-87a0-ace5e9c25fbe ro nouveau.runpm=0 quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-36-generic N/A
   linux-backports-modules-5.8.0-36-generic  N/A
   linux-firmware1.194
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X470-PRO
  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.:bvr5809:bd12/03/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO: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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  DistroRelease: Ubuntu 21.04
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: rcraid
  Package: linux (not installed)
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=7252ebf2-954b-4560-87a0-ace5e9c25fbe ro nouveau.runpm=0 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  RebootRequiredPkgs: evolution-data-server
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-36-generic N/A
   linux-backports-modules-5.8.0-36-generic  N/A
   linux-firmware1.194
  Tags:  hirsute
  Uname: Linux 5.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm apt-mirror audio avahi avahi-autoipd bin bluetooth cdrom 
chrome-remote-desktop colord crontab daemon davfs2 debian-tor dialout disk 
docker fax floppy fuse games i2c icecc kmem kvm libvirt libvirt-dnsmasq lightdm 
lp lpadmin mail man mythtv netdev news nm-openconnect ntp nvidia-persistenced 
operator plugdev proxy pulse root rtkit sambashare saned scanner science shadow 
ssh sudo sys syslog systemd-bus-proxy systemd-journal systemd-journal-remote 
systemd-network systemd-resolve systemd-timesync tape tty users uucp video 
voice weston-launch whoopsie www-data
  _MarkForUpload: True
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 12/03/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X470-PRO
  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

[Kernel-packages] [Bug 1913215] ProcCpuinfo.txt

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1913215/+attachment/5457849/+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/1913215

Title:
  Random kernel bugs on nouveau driver and NVidia 1070 Ti

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The issue exists for quite some time already. The affected UI freezes and 
luckily while using the new KDE beta only the desktop freezes. Before I had to 
do a hard reset since nothing was responding to key presses.
  Hope there are enough debug info attached by apport_cli to the bug report.

  If there is any way I can help, please ask! :)

  Thanks
  - Thomas

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.8.0-36-generic 5.8.0-36.40+21.04.1
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  NonfreeKernelModules: rcraid
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Jan 25 21:32:22 2021
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=7252ebf2-954b-4560-87a0-ace5e9c25fbe ro nouveau.runpm=0 quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-36-generic N/A
   linux-backports-modules-5.8.0-36-generic  N/A
   linux-firmware1.194
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X470-PRO
  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.:bvr5809:bd12/03/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO: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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  DistroRelease: Ubuntu 21.04
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: rcraid
  Package: linux (not installed)
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=7252ebf2-954b-4560-87a0-ace5e9c25fbe ro nouveau.runpm=0 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  RebootRequiredPkgs: evolution-data-server
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-36-generic N/A
   linux-backports-modules-5.8.0-36-generic  N/A
   linux-firmware1.194
  Tags:  hirsute
  Uname: Linux 5.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm apt-mirror audio avahi avahi-autoipd bin bluetooth cdrom 
chrome-remote-desktop colord crontab daemon davfs2 debian-tor dialout disk 
docker fax floppy fuse games i2c icecc kmem kvm libvirt libvirt-dnsmasq lightdm 
lp lpadmin mail man mythtv netdev news nm-openconnect ntp nvidia-persistenced 
operator plugdev proxy pulse root rtkit sambashare saned scanner science shadow 
ssh sudo sys syslog systemd-bus-proxy systemd-journal systemd-journal-remote 
systemd-network systemd-resolve systemd-timesync tape tty users uucp video 
voice weston-launch whoopsie www-data
  _MarkForUpload: True
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 12/03/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X470-PRO
  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

[Kernel-packages] [Bug 1913215] Lspci-vt.txt

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1913215/+attachment/5457844/+files/Lspci-vt.txt

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

Title:
  Random kernel bugs on nouveau driver and NVidia 1070 Ti

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The issue exists for quite some time already. The affected UI freezes and 
luckily while using the new KDE beta only the desktop freezes. Before I had to 
do a hard reset since nothing was responding to key presses.
  Hope there are enough debug info attached by apport_cli to the bug report.

  If there is any way I can help, please ask! :)

  Thanks
  - Thomas

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.8.0-36-generic 5.8.0-36.40+21.04.1
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  NonfreeKernelModules: rcraid
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Jan 25 21:32:22 2021
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=7252ebf2-954b-4560-87a0-ace5e9c25fbe ro nouveau.runpm=0 quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-36-generic N/A
   linux-backports-modules-5.8.0-36-generic  N/A
   linux-firmware1.194
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X470-PRO
  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.:bvr5809:bd12/03/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO: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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  DistroRelease: Ubuntu 21.04
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: rcraid
  Package: linux (not installed)
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=7252ebf2-954b-4560-87a0-ace5e9c25fbe ro nouveau.runpm=0 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  RebootRequiredPkgs: evolution-data-server
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-36-generic N/A
   linux-backports-modules-5.8.0-36-generic  N/A
   linux-firmware1.194
  Tags:  hirsute
  Uname: Linux 5.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm apt-mirror audio avahi avahi-autoipd bin bluetooth cdrom 
chrome-remote-desktop colord crontab daemon davfs2 debian-tor dialout disk 
docker fax floppy fuse games i2c icecc kmem kvm libvirt libvirt-dnsmasq lightdm 
lp lpadmin mail man mythtv netdev news nm-openconnect ntp nvidia-persistenced 
operator plugdev proxy pulse root rtkit sambashare saned scanner science shadow 
ssh sudo sys syslog systemd-bus-proxy systemd-journal systemd-journal-remote 
systemd-network systemd-resolve systemd-timesync tape tty users uucp video 
voice weston-launch whoopsie www-data
  _MarkForUpload: True
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 12/03/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X470-PRO
  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

[Kernel-packages] [Bug 1913215] CRDA.txt

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1913215/+attachment/5457841/+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/1913215

Title:
  Random kernel bugs on nouveau driver and NVidia 1070 Ti

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The issue exists for quite some time already. The affected UI freezes and 
luckily while using the new KDE beta only the desktop freezes. Before I had to 
do a hard reset since nothing was responding to key presses.
  Hope there are enough debug info attached by apport_cli to the bug report.

  If there is any way I can help, please ask! :)

  Thanks
  - Thomas

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.8.0-36-generic 5.8.0-36.40+21.04.1
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  NonfreeKernelModules: rcraid
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Jan 25 21:32:22 2021
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=7252ebf2-954b-4560-87a0-ace5e9c25fbe ro nouveau.runpm=0 quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-36-generic N/A
   linux-backports-modules-5.8.0-36-generic  N/A
   linux-firmware1.194
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X470-PRO
  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.:bvr5809:bd12/03/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO: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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  DistroRelease: Ubuntu 21.04
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: rcraid
  Package: linux (not installed)
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=7252ebf2-954b-4560-87a0-ace5e9c25fbe ro nouveau.runpm=0 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  RebootRequiredPkgs: evolution-data-server
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-36-generic N/A
   linux-backports-modules-5.8.0-36-generic  N/A
   linux-firmware1.194
  Tags:  hirsute
  Uname: Linux 5.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm apt-mirror audio avahi avahi-autoipd bin bluetooth cdrom 
chrome-remote-desktop colord crontab daemon davfs2 debian-tor dialout disk 
docker fax floppy fuse games i2c icecc kmem kvm libvirt libvirt-dnsmasq lightdm 
lp lpadmin mail man mythtv netdev news nm-openconnect ntp nvidia-persistenced 
operator plugdev proxy pulse root rtkit sambashare saned scanner science shadow 
ssh sudo sys syslog systemd-bus-proxy systemd-journal systemd-journal-remote 
systemd-network systemd-resolve systemd-timesync tape tty users uucp video 
voice weston-launch whoopsie www-data
  _MarkForUpload: True
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 12/03/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X470-PRO
  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:

[Kernel-packages] [Bug 1913215] Lsusb-v.txt

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1913215/+attachment/5457847/+files/Lsusb-v.txt

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

Title:
  Random kernel bugs on nouveau driver and NVidia 1070 Ti

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The issue exists for quite some time already. The affected UI freezes and 
luckily while using the new KDE beta only the desktop freezes. Before I had to 
do a hard reset since nothing was responding to key presses.
  Hope there are enough debug info attached by apport_cli to the bug report.

  If there is any way I can help, please ask! :)

  Thanks
  - Thomas

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.8.0-36-generic 5.8.0-36.40+21.04.1
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  NonfreeKernelModules: rcraid
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Jan 25 21:32:22 2021
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=7252ebf2-954b-4560-87a0-ace5e9c25fbe ro nouveau.runpm=0 quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-36-generic N/A
   linux-backports-modules-5.8.0-36-generic  N/A
   linux-firmware1.194
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X470-PRO
  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.:bvr5809:bd12/03/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO: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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  DistroRelease: Ubuntu 21.04
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: rcraid
  Package: linux (not installed)
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=7252ebf2-954b-4560-87a0-ace5e9c25fbe ro nouveau.runpm=0 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  RebootRequiredPkgs: evolution-data-server
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-36-generic N/A
   linux-backports-modules-5.8.0-36-generic  N/A
   linux-firmware1.194
  Tags:  hirsute
  Uname: Linux 5.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm apt-mirror audio avahi avahi-autoipd bin bluetooth cdrom 
chrome-remote-desktop colord crontab daemon davfs2 debian-tor dialout disk 
docker fax floppy fuse games i2c icecc kmem kvm libvirt libvirt-dnsmasq lightdm 
lp lpadmin mail man mythtv netdev news nm-openconnect ntp nvidia-persistenced 
operator plugdev proxy pulse root rtkit sambashare saned scanner science shadow 
ssh sudo sys syslog systemd-bus-proxy systemd-journal systemd-journal-remote 
systemd-network systemd-resolve systemd-timesync tape tty users uucp video 
voice weston-launch whoopsie www-data
  _MarkForUpload: True
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 12/03/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X470-PRO
  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

[Kernel-packages] [Bug 1913215] Lsusb.txt

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1913215/+attachment/5457845/+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/1913215

Title:
  Random kernel bugs on nouveau driver and NVidia 1070 Ti

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The issue exists for quite some time already. The affected UI freezes and 
luckily while using the new KDE beta only the desktop freezes. Before I had to 
do a hard reset since nothing was responding to key presses.
  Hope there are enough debug info attached by apport_cli to the bug report.

  If there is any way I can help, please ask! :)

  Thanks
  - Thomas

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.8.0-36-generic 5.8.0-36.40+21.04.1
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  NonfreeKernelModules: rcraid
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Jan 25 21:32:22 2021
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=7252ebf2-954b-4560-87a0-ace5e9c25fbe ro nouveau.runpm=0 quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-36-generic N/A
   linux-backports-modules-5.8.0-36-generic  N/A
   linux-firmware1.194
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X470-PRO
  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.:bvr5809:bd12/03/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO: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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  DistroRelease: Ubuntu 21.04
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: rcraid
  Package: linux (not installed)
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=7252ebf2-954b-4560-87a0-ace5e9c25fbe ro nouveau.runpm=0 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  RebootRequiredPkgs: evolution-data-server
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-36-generic N/A
   linux-backports-modules-5.8.0-36-generic  N/A
   linux-firmware1.194
  Tags:  hirsute
  Uname: Linux 5.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm apt-mirror audio avahi avahi-autoipd bin bluetooth cdrom 
chrome-remote-desktop colord crontab daemon davfs2 debian-tor dialout disk 
docker fax floppy fuse games i2c icecc kmem kvm libvirt libvirt-dnsmasq lightdm 
lp lpadmin mail man mythtv netdev news nm-openconnect ntp nvidia-persistenced 
operator plugdev proxy pulse root rtkit sambashare saned scanner science shadow 
ssh sudo sys syslog systemd-bus-proxy systemd-journal systemd-journal-remote 
systemd-network systemd-resolve systemd-timesync tape tty users uucp video 
voice weston-launch whoopsie www-data
  _MarkForUpload: True
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 12/03/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X470-PRO
  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:

[Kernel-packages] [Bug 1913215] Lsusb-t.txt

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1913215/+attachment/5457846/+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/1913215

Title:
  Random kernel bugs on nouveau driver and NVidia 1070 Ti

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The issue exists for quite some time already. The affected UI freezes and 
luckily while using the new KDE beta only the desktop freezes. Before I had to 
do a hard reset since nothing was responding to key presses.
  Hope there are enough debug info attached by apport_cli to the bug report.

  If there is any way I can help, please ask! :)

  Thanks
  - Thomas

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.8.0-36-generic 5.8.0-36.40+21.04.1
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  NonfreeKernelModules: rcraid
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Jan 25 21:32:22 2021
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=7252ebf2-954b-4560-87a0-ace5e9c25fbe ro nouveau.runpm=0 quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-36-generic N/A
   linux-backports-modules-5.8.0-36-generic  N/A
   linux-firmware1.194
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X470-PRO
  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.:bvr5809:bd12/03/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO: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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  DistroRelease: Ubuntu 21.04
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: rcraid
  Package: linux (not installed)
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=7252ebf2-954b-4560-87a0-ace5e9c25fbe ro nouveau.runpm=0 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  RebootRequiredPkgs: evolution-data-server
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-36-generic N/A
   linux-backports-modules-5.8.0-36-generic  N/A
   linux-firmware1.194
  Tags:  hirsute
  Uname: Linux 5.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm apt-mirror audio avahi avahi-autoipd bin bluetooth cdrom 
chrome-remote-desktop colord crontab daemon davfs2 debian-tor dialout disk 
docker fax floppy fuse games i2c icecc kmem kvm libvirt libvirt-dnsmasq lightdm 
lp lpadmin mail man mythtv netdev news nm-openconnect ntp nvidia-persistenced 
operator plugdev proxy pulse root rtkit sambashare saned scanner science shadow 
ssh sudo sys syslog systemd-bus-proxy systemd-journal systemd-journal-remote 
systemd-network systemd-resolve systemd-timesync tape tty users uucp video 
voice weston-launch whoopsie www-data
  _MarkForUpload: True
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 12/03/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X470-PRO
  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

[Kernel-packages] [Bug 1913215] IwConfig.txt

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1913215/+attachment/5457842/+files/IwConfig.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/1913215

Title:
  Random kernel bugs on nouveau driver and NVidia 1070 Ti

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The issue exists for quite some time already. The affected UI freezes and 
luckily while using the new KDE beta only the desktop freezes. Before I had to 
do a hard reset since nothing was responding to key presses.
  Hope there are enough debug info attached by apport_cli to the bug report.

  If there is any way I can help, please ask! :)

  Thanks
  - Thomas

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.8.0-36-generic 5.8.0-36.40+21.04.1
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  NonfreeKernelModules: rcraid
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Jan 25 21:32:22 2021
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=7252ebf2-954b-4560-87a0-ace5e9c25fbe ro nouveau.runpm=0 quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-36-generic N/A
   linux-backports-modules-5.8.0-36-generic  N/A
   linux-firmware1.194
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X470-PRO
  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.:bvr5809:bd12/03/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO: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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  DistroRelease: Ubuntu 21.04
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: rcraid
  Package: linux (not installed)
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=7252ebf2-954b-4560-87a0-ace5e9c25fbe ro nouveau.runpm=0 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  RebootRequiredPkgs: evolution-data-server
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-36-generic N/A
   linux-backports-modules-5.8.0-36-generic  N/A
   linux-firmware1.194
  Tags:  hirsute
  Uname: Linux 5.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm apt-mirror audio avahi avahi-autoipd bin bluetooth cdrom 
chrome-remote-desktop colord crontab daemon davfs2 debian-tor dialout disk 
docker fax floppy fuse games i2c icecc kmem kvm libvirt libvirt-dnsmasq lightdm 
lp lpadmin mail man mythtv netdev news nm-openconnect ntp nvidia-persistenced 
operator plugdev proxy pulse root rtkit sambashare saned scanner science shadow 
ssh sudo sys syslog systemd-bus-proxy systemd-journal systemd-journal-remote 
systemd-network systemd-resolve systemd-timesync tape tty users uucp video 
voice weston-launch whoopsie www-data
  _MarkForUpload: True
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 12/03/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X470-PRO
  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

[Kernel-packages] [Bug 1913215] AudioDevicesInUse.txt