[Kernel-packages] [Bug 1853446] Re: linux-raspi2: set two flavours to armhf kernel and change the flavour name to raspi4 for arm64 kernel

[Hui Wang]

** Changed in: linux-raspi2 (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  linux-raspi2: set two flavours to armhf kernel and change the flavour
  name to raspi4 for arm64 kernel

Status in linux-raspi2 package in Ubuntu:
  Won't Fix
Status in linux-raspi2 source package in Eoan:
  Won't Fix
Status in linux-raspi2 source package in Focal:
  Won't Fix

Bug description:
  [Impact]
  It is risky to use single armhf kernel to support rpi2/3/4, since
  upstream has a specific config for rpi2/3 and another config for rpi4,
  the major difference are LPAE, HIGHMEM and VMSPLIT_3G, we already
  met a bug that is intrduced by HIGHMEM and VMSPLIT_3G on rpi2/3,
  so add two falvours for rpi2/3 and rpi4.
  flavour 1: raspi2 (for rpi2/3, disable LPAE, HIGHMEM and VMSPLIT_3G)
  flavour 2: raspi4 (for rpi4, enable LPAE, HIGHMEM and VMSPLIT_3G)

  For arm64 kernel, we change the flavour name to raspi4, it supports
  rpi2/3/4.

  [Fix]
  Change the related configuration files in the debian.raspi2.

  
  [Test Case]
  After apply the patches, and I built two flavours of armhf and
  arm64 kernels, Then check the .config, they all meet the expectation.
  And boot those kernels on the rpi2/3/4 boards. worked well.

  [Regression Risk]
  Low, just change the flavour name for arm64, and for armhf, the
  flavour raspi4 is basically same as bofre (raspi2), the new flavour
  raspi2 just disable LPAE/HIGHMEM/VMSPLIT_3G, it is same as the config
  for rpi2/3 in the upstream.

  
  For armhf kernel:
   flavour 1: raspi2  # support rpi2/3 boards
   flavour 2: raspi4  # support rpi4 boards (in theory support all rpi2/3/4 
boards)

  Form arm64 kernel:
   flavour 1: raspi4  # support rpi2/3/4 boards

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

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

[Kernel-packages] [Bug 1862736] Re: sof driver fails and print lots of errors in the dmesg (focal)

[Hui Wang]

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

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

Title:
  sof driver fails and print lots of errors in  the dmesg (focal)

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  In the focal kernel, we backported a commit from the stable patches,
  that commit make the sof driver fail to work, and even make the system
  hang randomly.

  The commit we introduced is:
  Author: Ranjani Sridharan 
  Date: Mon Nov 4 14:48:12 2019 -0800

  ASoC: SOF: topology: set trigger order for FE DAI link

  BugLink: https://bugs.launchpad.net/bugs/1858428

  [ Upstream commit 5eee2b3f60065a2530d13f28e771be48b989eb4c ]

  Set trigger order for FE DAI links to SND_SOC_DPCM_TRIGGER_POST
  to trigger the BE DAI's before the FE DAI's. This prevents the
  xruns seen on playback pipelines using the link DMA.

  Signed-off-by: Ranjani Sridharan 
  Signed-off-by: Pierre-Louis Bossart 
  Link: 
https://lore.kernel.org/r/20191104224812.3393-3-ranjani.sridha...@linux.intel.com
  Signed-off-by: Mark Brown 
  Signed-off-by: Sasha Levin 
  Signed-off-by: Seth Forshee 

  
  [Impact]
  Booting the focal kernel on the LENOVO X1 corbon 7th and a Dell
  machine which has dmic on it, the sof driver print lots of errors
  even it loaded the firmware and topology conf file correctly, and
  the sof driver fails to initializaton, after booting up, we run:
  aplay -l, it print out that there is no soundcard. And the system
  randomly hang.

  [Fix]
  We backported a patch from stable kernel, that is not enough, the
  submitter of that patch sent 2 patches out, the stable kernel only
  integrated the 2nd one, to fix this problem, let's integrate the
  1st one as well.

  
  [Test Case]
  After applied all patches, the sof driver worked well, all audio
  functions worked well, and the system didn't hang randomly anymore.

  [Regression Risk]
  Low, these two patches fix FB/BE order issue, we should backport them
  together. And I have tested the patches on a LENOVO and a Dell machine,
  all worked well.

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

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

[Kernel-packages] [Bug 1125595] Re: /usr/sbin/dkms: line echo: write error: Broken pipe

[ALinuxUser]

It would be nice to see some movement on this.

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

Title:
  /usr/sbin/dkms: line   echo: write error: Broken pipe

Status in dkms package in Ubuntu:
  Confirmed

Bug description:
  There are appearing errors within uninstall of kernel/s deb packages.

  
   Uninstall Beginning 
  Module:  fglrx
  Version: 9.012
  Kernel:  3.5.0-23-lowlatency (x86_64)
  -

  Status: Before uninstall, this module version was ACTIVE on this
  kernel.

  fglrx.ko:
   - Uninstallation
 - Deleting from: /lib/modules/3.5.0-23-lowlatency/updates/dkms/
   - Original module
 - No original module was found for this module on this kernel.
 - Use the dkms install command to reinstall any previous module version.
  /usr/sbin/dkms: line 1905: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1907: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1905: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1907: echo: write error: Broken pipe

  depmod

  DKMS: uninstall completed.
  dkms: removing: vboxhost 4.2.6 (3.5.0-23-lowlatency) (x86_64)

   Uninstall Beginning 
  Module:  vboxhost
  Version: 4.2.6
  Kernel:  3.5.0-23-lowlatency (x86_64)
  -

  Status: Before uninstall, this module version was ACTIVE on this
  kernel.

  vboxdrv.ko:
   - Uninstallation
 - Deleting from: /lib/modules/3.5.0-23-lowlatency/updates/dkms/
   - Original module
 - No original module was found for this module on this kernel.
 - Use the dkms install command to reinstall any previous module version.
  /usr/sbin/dkms: line 1905: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1907: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1905: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1907: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1905: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1907: echo: write error: Broken pipe

  
  vboxnetflt.ko:
   - Uninstallation
 - Deleting from: /lib/modules/3.5.0-23-lowlatency/updates/dkms/
   - Original module
 - No original module was found for this module on this kernel.
 - Use the dkms install command to reinstall any previous module version.
  /usr/sbin/dkms: line 1905: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1907: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1905: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1907: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1905: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1907: echo: write error: Broken pipe

  
  vboxnetadp.ko:
   - Uninstallation
 - Deleting from: /lib/modules/3.5.0-23-lowlatency/updates/dkms/
   - Original module
 - No original module was found for this module on this kernel.
 - Use the dkms install command to reinstall any previous module version.
  /usr/sbin/dkms: line 1905: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1907: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1905: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1907: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1905: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1907: echo: write error: Broken pipe

  
  vboxpci.ko:
   - Uninstallation
 - Deleting from: /lib/modules/3.5.0-23-lowlatency/updates/dkms/
   - Original module
 - No original module was found for this module on this kernel.
 - Use the dkms install command to reinstall any previous module version.
  /usr/sbin/dkms: line 1905: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1907: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1905: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1907: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1905: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1907: echo: write error: Broken pipe

  depmod

  DKMS: uninstall completed.
  dkms: removing: vhba 20130121 (3.5.0-23-lowlatency) (x86_64)

   Uninstall Beginning 
  Module:  vhba
  Version: 20130121
  Kernel:  3.5.0-23-lowlatency (x86_64)
  -

  Status: Before uninstall, this module version was ACTIVE on this
  kernel.

  vhba.ko:
   - Uninstallation
 - Deleting from: /lib/modules/3.5.0-23-lowlatency/updates/dkms/
   - Original module
 - No original module was found for this module on this kernel.
 - Use the dkms install command to reinstall any previous module version.
  /usr/sbin/dkms: line 1905: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1907: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1905: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1907: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1905: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1907: echo: write error: 

[Kernel-packages] [Bug 1860986] Re: openvswitch: same tcp session encapsulated with different udp src port for ovs vxlan tunnel

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  openvswitch: same tcp session encapsulated with different udp src port
  for ovs vxlan tunnel

Status in linux package in Ubuntu:
  Expired

Bug description:
  [SRU Justification]

  [Impact]

  Packets encapsulated into a vxlan tunnel with openvswitch don't have
  the same udp source port for the first packet and the following ones
  of the same  TCP flow in a DOCKER scenario usecase.

  In fact, when using the kernel datapath, the upcall don't include skb
  hash info relatived. As VXLAN module uses the skb hash to select UDP
  src port, the source port is different for the first packet.

  More information can be found here:
  https://mail.openvswitch.org/pipermail/ovs-dev/2019-October/364062.html

  This has been fixed in v5.5 by the following upstream commit:
  bd1903b7c4596 ("net: openvswitch: add hash info to upcall")

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/net/openvswitch?id=bd1903b7c4596ba6f7677d0dfefd05ba5876707d

  The bug exists since the beginning of vxlan support in openvswitch.

  == Fix ==

  Backport the requested patches to Focal (5.4), Eoan (5.3), Bionic (4.15) and
  Xenial (4.4).

  == Risk of Regression ==

  This patch only add hash information when we do upcall, thus the risk
  should be low.

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

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

[Kernel-packages] [Bug 1869453] Re: Move gvnic driver from -modules-extras to -modules

[Khaled El Mously]

** Description changed:

- There's a salesforce ticket that I will link to here.
+ There's a salesforce ticket:
+ 
+ https://canonical.my.salesforce.com/5003z25pQss

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

Title:
  Move gvnic driver from -modules-extras to -modules

Status in linux-gcp package in Ubuntu:
  New
Status in linux-gcp source package in Xenial:
  Fix Committed
Status in linux-gcp source package in Bionic:
  Fix Committed
Status in linux-gcp source package in Eoan:
  Fix Committed
Status in linux-gcp source package in Focal:
  New

Bug description:
  There's a salesforce ticket:

  https://canonical.my.salesforce.com/5003z25pQss

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

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

[Kernel-packages] [Bug 1869453] Re: Move gvnic driver from -modules-extras to -modules

[Khaled El Mously]

** Changed in: linux-gcp (Ubuntu Xenial)
   Status: New => Fix Committed

** No longer affects: linux-gcp (Ubuntu Disco)

** Changed in: linux-gcp (Ubuntu Eoan)
   Status: New => Fix Committed

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

Title:
  Move gvnic driver from -modules-extras to -modules

Status in linux-gcp package in Ubuntu:
  New
Status in linux-gcp source package in Xenial:
  Fix Committed
Status in linux-gcp source package in Bionic:
  Fix Committed
Status in linux-gcp source package in Eoan:
  Fix Committed
Status in linux-gcp source package in Focal:
  New

Bug description:
  There's a salesforce ticket that I will link to here.

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

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

[Kernel-packages] [Bug 1869453] [NEW] Move gvnic driver from -modules-extras to -modules

[Khaled El Mously]

Public bug reported:

There's a salesforce ticket that I will link to here.

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

** Affects: linux-gcp (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: linux-gcp (Ubuntu Bionic)
 Importance: Undecided
 Status: Fix Committed

** Affects: linux-gcp (Ubuntu Disco)
 Importance: Undecided
 Status: New

** Affects: linux-gcp (Ubuntu Eoan)
 Importance: Undecided
 Status: New

** Affects: linux-gcp (Ubuntu Focal)
 Importance: Undecided
 Status: New

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

** No longer affects: linux (Ubuntu)

** Also affects: linux-gcp (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux-gcp (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: linux-gcp (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

** Also affects: linux-gcp (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Changed in: linux-gcp (Ubuntu Bionic)
   Status: New => Fix Committed

** No longer affects: linux-gcp (Ubuntu Disco)

** Also affects: linux-gcp (Ubuntu Disco)
   Importance: Undecided
   Status: New

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

Title:
  Move gvnic driver from -modules-extras to -modules

Status in linux-gcp package in Ubuntu:
  New
Status in linux-gcp source package in Xenial:
  New
Status in linux-gcp source package in Bionic:
  Fix Committed
Status in linux-gcp source package in Disco:
  New
Status in linux-gcp source package in Eoan:
  New
Status in linux-gcp source package in Focal:
  New

Bug description:
  There's a salesforce ticket that I will link to here.

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

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

[Kernel-packages] [Bug 1868442] Re: Missing wireless network interface after kernel 5.3.0-43 upgrade with eoan

[Rustin Schenk]

** Description changed:

  I updated to latest kernel: initrd.img-5.3.0-43-generic and find that 
bluetooth is enabled and no wireless connection. When I stop bluetooth I go 
into airplane mode.  I cannot find any wireless connection in network or 
wireless connection setup in settings.  ifconfig shows there is no wireless 
interface setup. When I go back to kernel 5.3.0-42 everything is working 
correctly. I am using an HP laptop.
  I can see the wireless network controller with lshw:
  
  lshw -C network
-   *-network
-description: Ethernet interface
-product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
-vendor: Realtek Semiconductor Co., Ltd.
-physical id: 0
-bus info: pci@:02:00.0
-logical name: eno1
-version: 15
-serial: b4:b6:86:e7:67:29
-size: 100Mbit/s
-capacity: 1Gbit/s
-width: 64 bits
-clock: 33MHz
-capabilities: pm msi pciexpress msix bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
-configuration: autonegotiation=on broadcast=yes driver=r8169 
duplex=full firmware=rtl8168h-2_0.0.2 02/26/15 ip=192.168.1.108 latency=0 
link=yes multicast=yes port=MII speed=100Mbit/s
-resources: irq:38 ioport:e000(size=256) memory:fe904000-fe904fff 
memory:fe90-fe903fff
-   *-network
-description: Network controller
-product: Dual Band Wireless-AC 3168NGW [Stone Peak]
-vendor: Intel Corporation
-physical id: 0
-bus info: pci@:03:00.0
-version: 10
-width: 64 bits
-clock: 33MHz
-capabilities: pm msi pciexpress bus_master cap_list
-configuration: driver=iwlwifi latency=0
-resources: irq:43 memory:fe80-fe801fff
+   *-network
+    description: Ethernet interface
+    product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
+    vendor: Realtek Semiconductor Co., Ltd.
+    physical id: 0
+    bus info: pci@:02:00.0
+    logical name: eno1
+    version: 15
+    serial: b4:b6:86:e7:67:29
+    size: 100Mbit/s
+    capacity: 1Gbit/s
+    width: 64 bits
+    clock: 33MHz
+    capabilities: pm msi pciexpress msix bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
+    configuration: autonegotiation=on broadcast=yes driver=r8169 
duplex=full firmware=rtl8168h-2_0.0.2 02/26/15 ip=192.168.1.108 latency=0 
link=yes multicast=yes port=MII speed=100Mbit/s
+    resources: irq:38 ioport:e000(size=256) memory:fe904000-fe904fff 
memory:fe90-fe903fff
+   *-network
+    description: Network controller
+    product: Dual Band Wireless-AC 3168NGW [Stone Peak]
+    vendor: Intel Corporation
+    physical id: 0
+    bus info: pci@:03:00.0
+    version: 10
+    width: 64 bits
+    clock: 33MHz
+    capabilities: pm msi pciexpress bus_master cap_list
+    configuration: driver=iwlwifi latency=0
+    resources: irq:43 memory:fe80-fe801fff
  
  lspci |grep Network
  03:00.0 Network controller: Intel Corporation Dual Band Wireless-AC 3168NGW 
[Stone Peak] (rev 10)
  
  iwconfig
  lo no wireless extensions.
  
  eno1 no wireless extensions.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-43-generic 5.3.0-43.36
  ProcVersionSignature: Ubuntu 5.3.0-43.36-generic 5.3.18
  Uname: Linux 5.3.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.7
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  rustin 1684 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  rustin 1684 F pulseaudio
  Date: Sun Mar 22 05:43:04 2020
  InstallationDate: Installed on 2018-11-30 (478 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
-  lono wireless extensions.
-  
-  eno1  no wireless extensions.
+  lono wireless extensions.
+ 
+  eno1  no wireless extensions.
  MachineType: HP HP Pavilion Laptop 17-ar0xx
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-43-generic 
root=UUID=29898130-1fa9-464b-88cf-ed44cfd58f76 ro pcie_aspm=force 
acpi_backlight=vendor
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
-  linux-restricted-modules-5.3.0-43-generic N/A
-  linux-backports-modules-5.3.0-43-generic  N/A
-  linux-firmware1.183.5
+  linux-restricted-modules-5.3.0-43-generic N/A
+  linux-backports-modules-5.3.0-43-generic  N/A
+  linux-firmware

Re: [Kernel-packages] [Bug 1865359] Re: sysfs: incorrect network device permissions on network namespace change

[Christian Brauner]

On March 27, 2020 10:57:17 PM GMT+01:00, Seth Forshee 
 wrote:
>Applied the patches from linux-next, plus one additional fix I saw,
>"sysfs: fix static inline declaration of sysfs_groups_change_owner()".
>@Christian, please let me know if there are any other fixes we need to
>grab.
>
>** Changed in: linux (Ubuntu Focal)
>   Status: In Progress => Fix Committed

Nope, no additional fixes. This is great, thank you for doing this!

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

Title:
  sysfs: incorrect network device permissions on network namespace
  change

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

Bug description:
  SRU Justification

  Impact:
   patchsets.)
  We have been struggling with a bug surrounding the ownership of network
  device sysfs files when moving network devices between network
  namespaces owned by different user namespaces reported by multiple
  users.

  Currently, when moving network devices between network namespaces the
  ownership of the corresponding sysfs entries is not changed. This leads
  to problems when tools try to operate on the corresponding sysfs files.

  I also causes a bug when creating a network device in a network
  namespaces owned by a user namespace and moving that network device back
  to the host network namespaces. Because when a network device is created
  in a network namespaces it will be owned by the root user of the user
  namespace and all its associated sysfs files will also be owned by the
  root user of the corresponding user namespace.
  If such a network device has to be moved back to the host network
  namespace the permissions will still be set to the root user of the
  owning user namespaces of the originating network namespace. This means
  unprivileged users can e.g. re-trigger uevents for such incorrectly
  owned devices on the host or in other network namespaces. They can also
  modify the settings of the device itself through sysfs when they
  wouldn't be able to do the same through netlink. Both of these things
  are unwanted.

  For example, quite a few workloads will create network devices in the
  host network namespace. Other tools will then proceed to move such
  devices between network namespaces owner by other user namespaces. While
  the ownership of the device itself is updated in
  net/core/net-sysfs.c:dev_change_net_namespace() the corresponding sysfs
  entry for the device is not. Below you'll find that moving a network
  device (here a veth device) from a network namespace into another
  network namespaces owned by a different user namespace with a different
  id mapping. As you can see the permissions are wrong even though it is
  owned by the userns root user after it has been moved and can be
  interacted with through netlink:

  drwxr-xr-x 5 nobody nobody0 Jan 25 18:08 .
  drwxr-xr-x 9 nobody nobody0 Jan 25 18:08 ..
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 addr_assign_type
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 addr_len
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 address
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 broadcast
  -rw-r--r-- 1 nobody nobody 4096 Jan 25 18:09 carrier
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 carrier_changes
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 carrier_down_count
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 carrier_up_count
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 dev_id
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 dev_port
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 dormant
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 duplex
  -rw-r--r-- 1 nobody nobody 4096 Jan 25 18:09 flags
  -rw-r--r-- 1 nobody nobody 4096 Jan 25 18:09 gro_flush_timeout
  -rw-r--r-- 1 nobody nobody 4096 Jan 25 18:09 ifalias
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 ifindex
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 iflink
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 link_mode
  -rw-r--r-- 1 nobody nobody 4096 Jan 25 18:09 mtu
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 name_assign_type
  -rw-r--r-- 1 nobody nobody 4096 Jan 25 18:09 netdev_group
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 operstate
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 phys_port_id
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 phys_port_name
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 phys_switch_id
  drwxr-xr-x 2 nobody nobody0 Jan 25 18:09 power
  -rw-r--r-- 1 nobody nobody 4096 Jan 25 18:09 proto_down
  drwxr-xr-x 4 nobody nobody0 Jan 25 18:09 queues
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 speed
  drwxr-xr-x 2 nobody nobody0 Jan 25 18:09 statistics
  lrwxrwxrwx 1 nobody nobody0 Jan 25 18:08 subsystem -> 
../../../../class/net
  -rw-r--r-- 1 nobody nobody 4096 Jan 25 18:09 tx_queue_len
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 type
  -rw-r--r-- 1 nobody 

[Kernel-packages] [Bug 1865359] Re: sysfs: incorrect network device permissions on network namespace change

[Seth Forshee]

Applied the patches from linux-next, plus one additional fix I saw,
"sysfs: fix static inline declaration of sysfs_groups_change_owner()".
@Christian, please let me know if there are any other fixes we need to
grab.

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

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

Title:
  sysfs: incorrect network device permissions on network namespace
  change

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

Bug description:
  SRU Justification

  Impact:
   patchsets.)
  We have been struggling with a bug surrounding the ownership of network
  device sysfs files when moving network devices between network
  namespaces owned by different user namespaces reported by multiple
  users.

  Currently, when moving network devices between network namespaces the
  ownership of the corresponding sysfs entries is not changed. This leads
  to problems when tools try to operate on the corresponding sysfs files.

  I also causes a bug when creating a network device in a network
  namespaces owned by a user namespace and moving that network device back
  to the host network namespaces. Because when a network device is created
  in a network namespaces it will be owned by the root user of the user
  namespace and all its associated sysfs files will also be owned by the
  root user of the corresponding user namespace.
  If such a network device has to be moved back to the host network
  namespace the permissions will still be set to the root user of the
  owning user namespaces of the originating network namespace. This means
  unprivileged users can e.g. re-trigger uevents for such incorrectly
  owned devices on the host or in other network namespaces. They can also
  modify the settings of the device itself through sysfs when they
  wouldn't be able to do the same through netlink. Both of these things
  are unwanted.

  For example, quite a few workloads will create network devices in the
  host network namespace. Other tools will then proceed to move such
  devices between network namespaces owner by other user namespaces. While
  the ownership of the device itself is updated in
  net/core/net-sysfs.c:dev_change_net_namespace() the corresponding sysfs
  entry for the device is not. Below you'll find that moving a network
  device (here a veth device) from a network namespace into another
  network namespaces owned by a different user namespace with a different
  id mapping. As you can see the permissions are wrong even though it is
  owned by the userns root user after it has been moved and can be
  interacted with through netlink:

  drwxr-xr-x 5 nobody nobody0 Jan 25 18:08 .
  drwxr-xr-x 9 nobody nobody0 Jan 25 18:08 ..
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 addr_assign_type
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 addr_len
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 address
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 broadcast
  -rw-r--r-- 1 nobody nobody 4096 Jan 25 18:09 carrier
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 carrier_changes
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 carrier_down_count
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 carrier_up_count
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 dev_id
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 dev_port
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 dormant
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 duplex
  -rw-r--r-- 1 nobody nobody 4096 Jan 25 18:09 flags
  -rw-r--r-- 1 nobody nobody 4096 Jan 25 18:09 gro_flush_timeout
  -rw-r--r-- 1 nobody nobody 4096 Jan 25 18:09 ifalias
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 ifindex
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 iflink
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 link_mode
  -rw-r--r-- 1 nobody nobody 4096 Jan 25 18:09 mtu
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 name_assign_type
  -rw-r--r-- 1 nobody nobody 4096 Jan 25 18:09 netdev_group
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 operstate
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 phys_port_id
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 phys_port_name
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 phys_switch_id
  drwxr-xr-x 2 nobody nobody0 Jan 25 18:09 power
  -rw-r--r-- 1 nobody nobody 4096 Jan 25 18:09 proto_down
  drwxr-xr-x 4 nobody nobody0 Jan 25 18:09 queues
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 speed
  drwxr-xr-x 2 nobody nobody0 Jan 25 18:09 statistics
  lrwxrwxrwx 1 nobody nobody0 Jan 25 18:08 subsystem -> 
../../../../class/net
  -rw-r--r-- 1 nobody nobody 4096 Jan 25 18:09 tx_queue_len
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 type
  -rw-r--r-- 1 nobody nobody 4096 Jan 25 18:08 uevent

  Constrast this with creating a device of the same type in the network
  namespace directly. In this case 

[Kernel-packages] [Bug 1845319] Re: writing 'add' to /sys/devices/vio/uevent fails with ENODEV

[Dan Streetman]

removing myself as bug owner, as I tried to send a simple patch upstream
to fix this, but was told to instead make more complex changes.  As the
bug isn't really that important, and systemd has been patched to ignore
the kernel bug, I'm just letting it go.

** Changed in: linux (Ubuntu)
 Assignee: Dan Streetman (ddstreet) => (unassigned)

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

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

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

Title:
  writing 'add' to /sys/devices/vio/uevent fails with ENODEV

Status in systemd:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Eoan:
  Won't Fix
Status in systemd source package in Eoan:
  Invalid

Bug description:
  [impact]

  The systemd-udev-trigger service calls 'udevadm trigger --type=devices
  --action=add', which writes 'add' to all /sys/devices/ uevent nodes,
  to re-generate their uevents sent to udev.  Until systemd commit
  97afc0351a96e0daa83964df33937967c75c644f, any errors during this
  process were simply logged to debug and ignored, but now udevadm will
  log errors and return failure.

  On ppc64el, the /sys/devices/vio device returns ENODEV when writing
  'add' to its uevent, which causes the udevadm command to return
  failure, which causes the systemd-udev-trigger system service to fail.

  The kernel vio driver should be fixed to not return ENODEV.

  [test case]

  On a ppc64el system, with any systemd containing commit
  97afc0351a96e0daa83964df33937967c75c644f, check the status of the
  systemd-udev-trigger service, to see that it's failed.

  Alternately, again on a ppc64el system, run as root:

  # echo add > /sys/devices/vio/uevent
  -bash: echo: write error: No such device

  [regression potential]

  the potential should be low, as this appears to have always behaved
  this way, at least for a while now.

  [other info]

  the systemd commit that changes udevadm to start failing for this
  error isn't included in any Ubuntu release yet, this is found from
  systemd upstream testing.

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

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

[Kernel-packages] [Bug 1869235] Re: Ryzen 3rd gen (3900X) ECC support missing from kernel

[araemo]

Yes, that version worked:
$ dmesg | grep EDAC
[0.801863] EDAC MC: Ver: 3.0.0
[   21.536674] EDAC amd64: Node 0: DRAM ECC enabled.
[   21.536674] EDAC amd64: F17h_M70h detected (node 0).
[   21.536704] EDAC MC: UMC0 chip selects:
[   21.536704] EDAC amd64: MC: 0: 0MB 1: 0MB
[   21.536705] EDAC amd64: MC: 2: 16384MB 3: 16384MB
[   21.536707] EDAC MC: UMC1 chip selects:
[   21.536708] EDAC amd64: MC: 0: 0MB 1: 0MB
[   21.536708] EDAC amd64: MC: 2: 16384MB 3: 16384MB
[   21.536708] EDAC amd64: using x16 syndromes.
[   21.536709] EDAC amd64: MCT channel count: 2
[   21.536759] EDAC MC0: Giving out device to module amd64_edac controller 
F17h_M70h: DEV :00:18.3 (INTERRUPT)
[   21.536766] EDAC PCI0: Giving out device to module amd64_edac controller 
EDAC PCI controller: DEV :00:18.0 (POLLED)
[   21.536767] AMD64 EDAC driver v3.5.0

$ sudo edac-util
edac-util: No errors to report.

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

Title:
  Ryzen 3rd gen (3900X) ECC support missing from kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu server:
  Description:Ubuntu 19.10
  Release:19.10
  Installed kernel:
  linux-generic:
Installed: 5.3.0.42.36
  (I could not figure out what package to select in the 'in what package did 
you find this bug' chooser)

  Expected behavior: ECC RAM is detected and utilized
  Result instead:
  Error in dmesg at boot:
  EDAC amd64: Error: F0 not found, device 0x1460 (broken BIOS?) (more in the 
attached KernelErrors.log)

  Kernel 5.3 is missing ECC support for some families of AMD Ryzen 3rd
  gen CPUs.

  Support is added via these two commits in the mainline tree:
  
https://github.com/torvalds/linux/commit/e53a3b267fb0a79db9ca1f1e08b97889b22013e6
  
https://github.com/torvalds/linux/commit/3e443eb353eda6f4b4796e07f2599683fa752f1d

  The second commit actually adds the missing support, but it relies on
  the first commit: a partial refactor of the AMD ECC code.

  I tested myself, followed the instructions at 
https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel to build my own kernel, 
cherry-picked the two above commits, and have working ECC support on my 
self-built kernel:
  Linux smaug 5.3.0-43-generic #36 SMP Sat Mar 21 02:33:30 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux:

  EDAC MC: Ver: 3.0.0
  EDAC amd64: Node 0: DRAM ECC enabled.
  EDAC amd64: F17h_M70h detected (node 0).
  EDAC MC: UMC0 chip selects:
  EDAC amd64: MC: 0: 0MB 1: 0MB
  EDAC amd64: MC: 2: 16384MB 3: 16384MB
  EDAC MC: UMC1 chip selects:
  EDAC amd64: MC: 0: 0MB 1: 0MB
  EDAC amd64: MC: 2: 16384MB 3: 16384MB
  EDAC amd64: using x16 syndromes.
  EDAC amd64: MCT channel count: 2
  EDAC MC0: Giving out device to module amd64_edac controller F17h_M70h: DEV 
:00:18.3 (INTERRUPT)
  EDAC PCI0: Giving out device to module amd64_edac controller EDAC PCI 
controller: DEV :00:18.0 (POLLED)
  AMD64 EDAC driver v3.5.0

  
  If this could be included in a future hardware support kernel release, that 
would be very helpful.  I am unsure what the policy is for including this kind 
of backport in non-LTS kernels, though I know the LTS releases have hardware 
support updates that include this type of fix.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-03-20 (6 days ago)
  InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=89cfcc61-dbca-43d3-9a2e-5961df9ae5b4 ro
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  RfKill:
   
  Tags:  eoan uec-images
  Uname: Linux 5.3.0-42-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lxd plugdev sudo
  _MarkForUpload: False
  dmi.bios.date: 10/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.30
  dmi.board.name: X470D4U2-2T
  dmi.board.vendor: ASRockRack
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.

[Kernel-packages] [Bug 1869433] [NEW] Eoan update: upstream stable patchset 2020-03-27

[Kamal Mostafa]

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   upstream stable patchset 2020-03-27

Ported from the following upstream stable releases:
v4.19.109, v5.4.25,
v4.19.110,
v4.19.111, v5.4.26

   from git://git.kernel.org/

net: dsa: bcm_sf2: Forcibly configure IMP port for 1Gb/sec
RDMA/core: Fix pkey and port assignment in get_new_pps
RDMA/core: Fix use of logical OR in get_new_pps
kprobes: Fix optimize_kprobe()/unoptimize_kprobe() cancellation logic
ALSA: hda: do not override bus codec_mask in link_get()
serial: ar933x_uart: set UART_CS_{RX,TX}_READY_ORIDE
selftests: fix too long argument
usb: gadget: composite: Support more than 500mA MaxPower
usb: gadget: ffs: ffs_aio_cancel(): Save/restore IRQ flags
usb: gadget: serial: fix Tx stall after buffer overflow
drm/msm/mdp5: rate limit pp done timeout warnings
drm: msm: Fix return type of dsi_mgr_connector_mode_valid for kCFI
scsi: megaraid_sas: silence a warning
drm/msm/dsi: save pll state before dsi host is powered off
drm/msm/dsi/pll: call vco set rate explicitly
selftests: forwarding: use proto icmp for {gretap, ip6gretap}_mac testing
net: ks8851-ml: Remove 8-bit bus accessors
net: ks8851-ml: Fix 16-bit data access
net: ks8851-ml: Fix 16-bit IO operation
watchdog: da9062: do not ping the hw during stop()
s390/cio: cio_ignore_proc_seq_next should increase position index
s390: make 'install' not depend on vmlinux
x86/boot/compressed: Don't declare __force_order in kaslr_64.c
s390/qdio: fill SL with absolute addresses
nvme: Fix uninitialized-variable warning
ice: Don't tell the OS that link is going down
x86/xen: Distribute switch variables for initialization
net: thunderx: workaround BGX TX Underflow issue
ALSA: hda/realtek - Fix silent output on Gigabyte X570 Aorus Master
cifs: don't leak -EAGAIN for stat() during reconnect
usb: storage: Add quirk for Samsung Fit flash
usb: quirks: add NO_LPM quirk for Logitech Screen Share
usb: dwc3: gadget: Update chain bit correctly when using sg list
usb: core: hub: fix unhandled return by employing a void function
usb: core: hub: do error out if usb_autopm_get_interface() fails
usb: core: port: do error out if usb_autopm_get_interface() fails
vgacon: Fix a UAF in vgacon_invert_region
mm, numa: fix bad pmd by atomically check for pmd_trans_huge when marking page 
tables prot_numa
mm: fix possible PMD dirty bit lost in set_pmd_migration_entry()
fat: fix uninit-memory access for partial initialized inode
arm: dts: dra76x: Fix mmc3 max-frequency
tty:serial:mvebu-uart:fix a wrong return
serial: 8250_exar: add support for ACCES cards
vt: selection, close sel_buffer race
vt: selection, push console lock down
vt: selection, push sel_lock up
media: v4l2-mem2mem.c: fix broken links
x86/pkeys: Manually set X86_FEATURE_OSPKE to preserve existing changes
dmaengine: tegra-apb: Fix use-after-free
dmaengine: tegra-apb: Prevent race conditions of tasklet vs free list
dm cache: fix a crash due to incorrect work item cancelling
dm: report suspended device during destroy
dm writecache: verify watermark during resume
ARM: dts: ls1021a: Restore MDIO compatible to gianfar
spi: bcm63xx-hsspi: Really keep pll clk enabled
ASoC: topology: Fix memleak in soc_tplg_link_elems_load()
ASoC: topology: Fix memleak in soc_tplg_manifest_load()
ASoC: intel: skl: Fix pin debug prints
ASoC: intel: skl: Fix possible buffer overflow in debug outputs
ASoC: pcm: Fix possible buffer overflow in dpcm state sysfs output
ASoC: pcm512x: Fix unbalanced regulator enable call in probe error path
ASoC: dapm: Correct DAPM handling of active widgets during shutdown
drm/sun4i: Fix DE2 VI layer format support
drm/sun4i: de2/de3: Remove unsupported VI layer formats
phy: mapphone-mdm6600: Fix timeouts by adding wake-up handling
phy: mapphone-mdm6600: Fix write timeouts with shorter GPIO toggle interval
ARM: dts: imx6: phycore-som: fix emmc supply
RDMA/iwcm: Fix iwcm work deallocation
RMDA/cm: Fix missing ib_cm_destroy_id() in ib_cm_insert_listen()
IB/hfi1, qib: Ensure RCU is locked when accessing list
ARM: imx: build v7_cpu_resume() unconditionally
ARM: dts: am437x-idk-evm: Fix incorrect OPP node names
ARM: dts: imx7-colibri: Fix frequency for sd/mmc
hwmon: (adt7462) Fix an error return in ADT7462_REG_VOLT()
dmaengine: coh901318: Fix a double lock bug in dma_tc_handle()
powerpc: fix hardware PMU exception bug on PowerVM compatibility mode systems
efi/x86: Align GUIDs to their size in the mixed mode runtime wrapper
efi/x86: Handle by-ref arguments covering multiple 

[Kernel-packages] [Bug 1861359] Re: swap storms kills interactive use

[Sultan Alsawaf]

FYI, this bug has nothing to do with the use of swap. It just happens
that the slow writeback incurred by using a swap device backed by non-
volatile memory makes kswapd's bouts of page thrashing last longer,
enough to the point where there's a visual freeze.

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

Title:
  swap storms kills interactive use

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  High watermark boosting can cause large swap activity under certain
  memory intensive workloads, making the system very unresponsive
  (screen does not refresh, keyboard not responding, etc.).

  This large swap activity seems to be prevented disabling high
  watermark boosting.

  [Test case]

  Opening this web page in chrome seems to be a good reproducer of the
  problem:

  
https://platform.leolabs.space/visualizations/conjunction?type=conjunction=2004981040

  When this page is opened we can clearly see from 'top' (for example)
  that the used swap is going up very quickly.

  With the fix applied swap is not used at all and the system is always
  responsive.

  [Fix]

  Set vm.watermark_boost_factor to 0, disabling watermark boosting by
  default.

  [Regression potential]

  Regression potential is minimal, setting vm.watermark_boost_factor to
  0 by default restores the old kernel behavior before watermark
  boosting was introduced. In case of unexpected regressions we can
  always fix this in user-space via sysctl.

  [Original report]

  Hello, several times since upgrading to focal from 19.04 I've found my
  computer entirely unresponsive for periods of twenty or thirty
  seconds. No mouse movement, no keyboard input, the screen output does
  not change.

  My computer was using swap space and despite very slow writeout speeds
  well below what the NVME drive can handle, the computer was unusable.

  I've captured some vmstat 1 output and top output that I started
  collecting during the event. (Normally one very long painful period is
  followed by several shorter periods of uselessness.)

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Wed Jan 29 23:44:05 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  ---
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
     Mixer name : 'Realtek ALC285'
     Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
     Controls  : 53
     Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
     Mixer name : 'USB Mixer'
     Components : 'USB17ef:306f'
     Controls  : 9
     Simple ctrls  : 4
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=none
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: LENOVO 20KHCTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic 
root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash 
acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  UserGroups: adm cdrom libvirt lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET69W (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 

[Kernel-packages] [Bug 1860196] WifiSyslog.txt

[Seiichi Nakashima]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1860196/+attachment/5342330/+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/1860196

Title:
  kernel-5.3.0-26 could not use appliicatins on geforce 8600GTI

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

Bug description:
  dear everyone.

  I update ubuntu-18.04.3 to use software-updater,
  then kernel update to 5.3.0-26.

  Desktop PC environment(Core2 Duo E8400, so old PC) are updated and boot up 
fine.
  but could not use applicaion, may be hung up.
  could not click icon, but mouse are moved.
  I use to restore backup and retry 3 times, but same result.

  I reboot another patition ubuntu-18.04, and get /var/log/syslog.
  I attached this report.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1711 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-30 (140 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190808)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5K/EPU
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=7bb03d3f-117f-4243-ab29-c91ee32f2b44 ro recovery nomodeset 
ipv6.disable=1
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.173.14
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0304
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5K/EPU
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: P5K/EPU
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1456 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-30 (146 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190808)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5K/EPU
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=a84f138c-6bc7-4958-94c6-661217949cbb ro ipv6.disable=1 quiet
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.173.14
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0304
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5K/EPU
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: 

[Kernel-packages] [Bug 1860196] UdevDb.txt

[Seiichi Nakashima]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1860196/+attachment/5342329/+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/1860196

Title:
  kernel-5.3.0-26 could not use appliicatins on geforce 8600GTI

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

Bug description:
  dear everyone.

  I update ubuntu-18.04.3 to use software-updater,
  then kernel update to 5.3.0-26.

  Desktop PC environment(Core2 Duo E8400, so old PC) are updated and boot up 
fine.
  but could not use applicaion, may be hung up.
  could not click icon, but mouse are moved.
  I use to restore backup and retry 3 times, but same result.

  I reboot another patition ubuntu-18.04, and get /var/log/syslog.
  I attached this report.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1711 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-30 (140 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190808)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5K/EPU
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=7bb03d3f-117f-4243-ab29-c91ee32f2b44 ro recovery nomodeset 
ipv6.disable=1
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.173.14
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0304
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5K/EPU
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: P5K/EPU
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1456 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-30 (146 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190808)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5K/EPU
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=a84f138c-6bc7-4958-94c6-661217949cbb ro ipv6.disable=1 quiet
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.173.14
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0304
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5K/EPU
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: P5K/EPU
  

[Kernel-packages] [Bug 1860196] CurrentDmesg.txt

[Seiichi Nakashima]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1860196/+attachment/5342320/+files/CurrentDmesg.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/1860196

Title:
  kernel-5.3.0-26 could not use appliicatins on geforce 8600GTI

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

Bug description:
  dear everyone.

  I update ubuntu-18.04.3 to use software-updater,
  then kernel update to 5.3.0-26.

  Desktop PC environment(Core2 Duo E8400, so old PC) are updated and boot up 
fine.
  but could not use applicaion, may be hung up.
  could not click icon, but mouse are moved.
  I use to restore backup and retry 3 times, but same result.

  I reboot another patition ubuntu-18.04, and get /var/log/syslog.
  I attached this report.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1711 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-30 (140 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190808)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5K/EPU
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=7bb03d3f-117f-4243-ab29-c91ee32f2b44 ro recovery nomodeset 
ipv6.disable=1
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.173.14
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0304
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5K/EPU
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: P5K/EPU
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1456 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-30 (146 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190808)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5K/EPU
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=a84f138c-6bc7-4958-94c6-661217949cbb ro ipv6.disable=1 quiet
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.173.14
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0304
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5K/EPU
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: 

[Kernel-packages] [Bug 1860196] Lspci.txt

[Seiichi Nakashima]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1860196/+attachment/5342321/+files/Lspci.txt

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

Title:
  kernel-5.3.0-26 could not use appliicatins on geforce 8600GTI

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

Bug description:
  dear everyone.

  I update ubuntu-18.04.3 to use software-updater,
  then kernel update to 5.3.0-26.

  Desktop PC environment(Core2 Duo E8400, so old PC) are updated and boot up 
fine.
  but could not use applicaion, may be hung up.
  could not click icon, but mouse are moved.
  I use to restore backup and retry 3 times, but same result.

  I reboot another patition ubuntu-18.04, and get /var/log/syslog.
  I attached this report.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1711 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-30 (140 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190808)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5K/EPU
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=7bb03d3f-117f-4243-ab29-c91ee32f2b44 ro recovery nomodeset 
ipv6.disable=1
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.173.14
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0304
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5K/EPU
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: P5K/EPU
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1456 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-30 (146 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190808)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5K/EPU
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=a84f138c-6bc7-4958-94c6-661217949cbb ro ipv6.disable=1 quiet
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.173.14
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0304
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5K/EPU
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: P5K/EPU
  

[Kernel-packages] [Bug 1860196] CRDA.txt

[Seiichi Nakashima]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1860196/+attachment/5342319/+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/1860196

Title:
  kernel-5.3.0-26 could not use appliicatins on geforce 8600GTI

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

Bug description:
  dear everyone.

  I update ubuntu-18.04.3 to use software-updater,
  then kernel update to 5.3.0-26.

  Desktop PC environment(Core2 Duo E8400, so old PC) are updated and boot up 
fine.
  but could not use applicaion, may be hung up.
  could not click icon, but mouse are moved.
  I use to restore backup and retry 3 times, but same result.

  I reboot another patition ubuntu-18.04, and get /var/log/syslog.
  I attached this report.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1711 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-30 (140 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190808)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5K/EPU
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=7bb03d3f-117f-4243-ab29-c91ee32f2b44 ro recovery nomodeset 
ipv6.disable=1
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.173.14
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0304
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5K/EPU
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: P5K/EPU
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1456 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-30 (146 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190808)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5K/EPU
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=a84f138c-6bc7-4958-94c6-661217949cbb ro ipv6.disable=1 quiet
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.173.14
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0304
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5K/EPU
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: P5K/EPU
  

[Kernel-packages] [Bug 1860196] AlsaInfo.txt

[Seiichi Nakashima]

apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1860196/+attachment/5342318/+files/AlsaInfo.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/1860196

Title:
  kernel-5.3.0-26 could not use appliicatins on geforce 8600GTI

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

Bug description:
  dear everyone.

  I update ubuntu-18.04.3 to use software-updater,
  then kernel update to 5.3.0-26.

  Desktop PC environment(Core2 Duo E8400, so old PC) are updated and boot up 
fine.
  but could not use applicaion, may be hung up.
  could not click icon, but mouse are moved.
  I use to restore backup and retry 3 times, but same result.

  I reboot another patition ubuntu-18.04, and get /var/log/syslog.
  I attached this report.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1711 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-30 (140 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190808)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5K/EPU
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=7bb03d3f-117f-4243-ab29-c91ee32f2b44 ro recovery nomodeset 
ipv6.disable=1
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.173.14
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0304
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5K/EPU
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: P5K/EPU
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1456 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-30 (146 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190808)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5K/EPU
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=a84f138c-6bc7-4958-94c6-661217949cbb ro ipv6.disable=1 quiet
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.173.14
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0304
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5K/EPU
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: P5K/EPU
  

[Kernel-packages] [Bug 1860196] PulseList.txt

[Seiichi Nakashima]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1860196/+attachment/5342328/+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/1860196

Title:
  kernel-5.3.0-26 could not use appliicatins on geforce 8600GTI

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

Bug description:
  dear everyone.

  I update ubuntu-18.04.3 to use software-updater,
  then kernel update to 5.3.0-26.

  Desktop PC environment(Core2 Duo E8400, so old PC) are updated and boot up 
fine.
  but could not use applicaion, may be hung up.
  could not click icon, but mouse are moved.
  I use to restore backup and retry 3 times, but same result.

  I reboot another patition ubuntu-18.04, and get /var/log/syslog.
  I attached this report.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1711 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-30 (140 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190808)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5K/EPU
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=7bb03d3f-117f-4243-ab29-c91ee32f2b44 ro recovery nomodeset 
ipv6.disable=1
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.173.14
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0304
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5K/EPU
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: P5K/EPU
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1456 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-30 (146 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190808)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5K/EPU
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=a84f138c-6bc7-4958-94c6-661217949cbb ro ipv6.disable=1 quiet
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.173.14
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0304
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5K/EPU
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: P5K/EPU
 

[Kernel-packages] [Bug 1860196] ProcInterrupts.txt

[Seiichi Nakashima]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1860196/+attachment/5342326/+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/1860196

Title:
  kernel-5.3.0-26 could not use appliicatins on geforce 8600GTI

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

Bug description:
  dear everyone.

  I update ubuntu-18.04.3 to use software-updater,
  then kernel update to 5.3.0-26.

  Desktop PC environment(Core2 Duo E8400, so old PC) are updated and boot up 
fine.
  but could not use applicaion, may be hung up.
  could not click icon, but mouse are moved.
  I use to restore backup and retry 3 times, but same result.

  I reboot another patition ubuntu-18.04, and get /var/log/syslog.
  I attached this report.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1711 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-30 (140 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190808)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5K/EPU
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=7bb03d3f-117f-4243-ab29-c91ee32f2b44 ro recovery nomodeset 
ipv6.disable=1
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.173.14
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0304
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5K/EPU
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: P5K/EPU
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1456 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-30 (146 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190808)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5K/EPU
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=a84f138c-6bc7-4958-94c6-661217949cbb ro ipv6.disable=1 quiet
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.173.14
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0304
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5K/EPU
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  

[Kernel-packages] [Bug 1860196] ProcModules.txt

[Seiichi Nakashima]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1860196/+attachment/5342327/+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/1860196

Title:
  kernel-5.3.0-26 could not use appliicatins on geforce 8600GTI

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

Bug description:
  dear everyone.

  I update ubuntu-18.04.3 to use software-updater,
  then kernel update to 5.3.0-26.

  Desktop PC environment(Core2 Duo E8400, so old PC) are updated and boot up 
fine.
  but could not use applicaion, may be hung up.
  could not click icon, but mouse are moved.
  I use to restore backup and retry 3 times, but same result.

  I reboot another patition ubuntu-18.04, and get /var/log/syslog.
  I attached this report.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1711 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-30 (140 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190808)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5K/EPU
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=7bb03d3f-117f-4243-ab29-c91ee32f2b44 ro recovery nomodeset 
ipv6.disable=1
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.173.14
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0304
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5K/EPU
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: P5K/EPU
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1456 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-30 (146 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190808)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5K/EPU
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=a84f138c-6bc7-4958-94c6-661217949cbb ro ipv6.disable=1 quiet
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.173.14
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0304
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5K/EPU
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: 

[Kernel-packages] [Bug 1860196] Lsusb.txt

[Seiichi Nakashima]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1860196/+attachment/5342322/+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/1860196

Title:
  kernel-5.3.0-26 could not use appliicatins on geforce 8600GTI

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

Bug description:
  dear everyone.

  I update ubuntu-18.04.3 to use software-updater,
  then kernel update to 5.3.0-26.

  Desktop PC environment(Core2 Duo E8400, so old PC) are updated and boot up 
fine.
  but could not use applicaion, may be hung up.
  could not click icon, but mouse are moved.
  I use to restore backup and retry 3 times, but same result.

  I reboot another patition ubuntu-18.04, and get /var/log/syslog.
  I attached this report.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1711 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-30 (140 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190808)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5K/EPU
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=7bb03d3f-117f-4243-ab29-c91ee32f2b44 ro recovery nomodeset 
ipv6.disable=1
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.173.14
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0304
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5K/EPU
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: P5K/EPU
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1456 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-30 (146 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190808)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5K/EPU
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=a84f138c-6bc7-4958-94c6-661217949cbb ro ipv6.disable=1 quiet
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.173.14
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0304
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5K/EPU
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: P5K/EPU
  

[Kernel-packages] [Bug 1860196] ProcCpuinfoMinimal.txt

[Seiichi Nakashima]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1860196/+attachment/5342324/+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/1860196

Title:
  kernel-5.3.0-26 could not use appliicatins on geforce 8600GTI

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

Bug description:
  dear everyone.

  I update ubuntu-18.04.3 to use software-updater,
  then kernel update to 5.3.0-26.

  Desktop PC environment(Core2 Duo E8400, so old PC) are updated and boot up 
fine.
  but could not use applicaion, may be hung up.
  could not click icon, but mouse are moved.
  I use to restore backup and retry 3 times, but same result.

  I reboot another patition ubuntu-18.04, and get /var/log/syslog.
  I attached this report.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1711 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-30 (140 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190808)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5K/EPU
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=7bb03d3f-117f-4243-ab29-c91ee32f2b44 ro recovery nomodeset 
ipv6.disable=1
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.173.14
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0304
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5K/EPU
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: P5K/EPU
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1456 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-30 (146 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190808)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5K/EPU
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=a84f138c-6bc7-4958-94c6-661217949cbb ro ipv6.disable=1 quiet
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.173.14
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0304
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5K/EPU
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  

[Kernel-packages] [Bug 1860196] ProcEnviron.txt

[Seiichi Nakashima]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1860196/+attachment/5342325/+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/1860196

Title:
  kernel-5.3.0-26 could not use appliicatins on geforce 8600GTI

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

Bug description:
  dear everyone.

  I update ubuntu-18.04.3 to use software-updater,
  then kernel update to 5.3.0-26.

  Desktop PC environment(Core2 Duo E8400, so old PC) are updated and boot up 
fine.
  but could not use applicaion, may be hung up.
  could not click icon, but mouse are moved.
  I use to restore backup and retry 3 times, but same result.

  I reboot another patition ubuntu-18.04, and get /var/log/syslog.
  I attached this report.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1711 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-30 (140 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190808)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5K/EPU
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=7bb03d3f-117f-4243-ab29-c91ee32f2b44 ro recovery nomodeset 
ipv6.disable=1
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.173.14
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0304
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5K/EPU
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: P5K/EPU
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1456 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-30 (146 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190808)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5K/EPU
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=a84f138c-6bc7-4958-94c6-661217949cbb ro ipv6.disable=1 quiet
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.173.14
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0304
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5K/EPU
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: 

[Kernel-packages] [Bug 1860196] ProcCpuinfo.txt

[Seiichi Nakashima]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1860196/+attachment/5342323/+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/1860196

Title:
  kernel-5.3.0-26 could not use appliicatins on geforce 8600GTI

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

Bug description:
  dear everyone.

  I update ubuntu-18.04.3 to use software-updater,
  then kernel update to 5.3.0-26.

  Desktop PC environment(Core2 Duo E8400, so old PC) are updated and boot up 
fine.
  but could not use applicaion, may be hung up.
  could not click icon, but mouse are moved.
  I use to restore backup and retry 3 times, but same result.

  I reboot another patition ubuntu-18.04, and get /var/log/syslog.
  I attached this report.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1711 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-30 (140 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190808)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5K/EPU
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=7bb03d3f-117f-4243-ab29-c91ee32f2b44 ro recovery nomodeset 
ipv6.disable=1
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.173.14
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0304
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5K/EPU
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: P5K/EPU
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1456 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-30 (146 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190808)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5K/EPU
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=a84f138c-6bc7-4958-94c6-661217949cbb ro ipv6.disable=1 quiet
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.173.14
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0304
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5K/EPU
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: 

[Kernel-packages] [Bug 1860196] Re: kernel-5.3.0-26 could not use appliicatins on geforce 8600GTI

[Seiichi Nakashima]

today I update kernel-5.3.0-43 to use software-updater.
I use firefox and I browsing COVID-19 site, 
then gui hung up, only mouse can move.
I power Off/On PC, send log to use apport-collect 1860196.



** Description changed:

  dear everyone.
  
  I update ubuntu-18.04.3 to use software-updater,
  then kernel update to 5.3.0-26.
  
  Desktop PC environment(Core2 Duo E8400, so old PC) are updated and boot up 
fine.
  but could not use applicaion, may be hung up.
  could not click icon, but mouse are moved.
  I use to restore backup and retry 3 times, but same result.
  
  I reboot another patition ubuntu-18.04, and get /var/log/syslog.
  I attached this report.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1711 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-30 (140 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190808)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5K/EPU
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=7bb03d3f-117f-4243-ab29-c91ee32f2b44 ro recovery nomodeset 
ipv6.disable=1
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.173.14
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0304
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5K/EPU
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: P5K/EPU
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1456 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-30 (146 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190808)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5K/EPU
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=a84f138c-6bc7-4958-94c6-661217949cbb ro ipv6.disable=1 quiet
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.173.14
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0304
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5K/EPU
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: P5K/EPU
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 

[Kernel-packages] [Bug 1865359] Re: sysfs: incorrect network device permissions on network namespace change

[Seth Forshee]

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

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

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

Title:
  sysfs: incorrect network device permissions on network namespace
  change

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

Bug description:
  SRU Justification

  Impact:
   patchsets.)
  We have been struggling with a bug surrounding the ownership of network
  device sysfs files when moving network devices between network
  namespaces owned by different user namespaces reported by multiple
  users.

  Currently, when moving network devices between network namespaces the
  ownership of the corresponding sysfs entries is not changed. This leads
  to problems when tools try to operate on the corresponding sysfs files.

  I also causes a bug when creating a network device in a network
  namespaces owned by a user namespace and moving that network device back
  to the host network namespaces. Because when a network device is created
  in a network namespaces it will be owned by the root user of the user
  namespace and all its associated sysfs files will also be owned by the
  root user of the corresponding user namespace.
  If such a network device has to be moved back to the host network
  namespace the permissions will still be set to the root user of the
  owning user namespaces of the originating network namespace. This means
  unprivileged users can e.g. re-trigger uevents for such incorrectly
  owned devices on the host or in other network namespaces. They can also
  modify the settings of the device itself through sysfs when they
  wouldn't be able to do the same through netlink. Both of these things
  are unwanted.

  For example, quite a few workloads will create network devices in the
  host network namespace. Other tools will then proceed to move such
  devices between network namespaces owner by other user namespaces. While
  the ownership of the device itself is updated in
  net/core/net-sysfs.c:dev_change_net_namespace() the corresponding sysfs
  entry for the device is not. Below you'll find that moving a network
  device (here a veth device) from a network namespace into another
  network namespaces owned by a different user namespace with a different
  id mapping. As you can see the permissions are wrong even though it is
  owned by the userns root user after it has been moved and can be
  interacted with through netlink:

  drwxr-xr-x 5 nobody nobody0 Jan 25 18:08 .
  drwxr-xr-x 9 nobody nobody0 Jan 25 18:08 ..
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 addr_assign_type
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 addr_len
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 address
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 broadcast
  -rw-r--r-- 1 nobody nobody 4096 Jan 25 18:09 carrier
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 carrier_changes
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 carrier_down_count
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 carrier_up_count
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 dev_id
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 dev_port
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 dormant
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 duplex
  -rw-r--r-- 1 nobody nobody 4096 Jan 25 18:09 flags
  -rw-r--r-- 1 nobody nobody 4096 Jan 25 18:09 gro_flush_timeout
  -rw-r--r-- 1 nobody nobody 4096 Jan 25 18:09 ifalias
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 ifindex
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 iflink
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 link_mode
  -rw-r--r-- 1 nobody nobody 4096 Jan 25 18:09 mtu
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 name_assign_type
  -rw-r--r-- 1 nobody nobody 4096 Jan 25 18:09 netdev_group
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 operstate
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 phys_port_id
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 phys_port_name
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 phys_switch_id
  drwxr-xr-x 2 nobody nobody0 Jan 25 18:09 power
  -rw-r--r-- 1 nobody nobody 4096 Jan 25 18:09 proto_down
  drwxr-xr-x 4 nobody nobody0 Jan 25 18:09 queues
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 speed
  drwxr-xr-x 2 nobody nobody0 Jan 25 18:09 statistics
  lrwxrwxrwx 1 nobody nobody0 Jan 25 18:08 subsystem -> 
../../../../class/net
  -rw-r--r-- 1 nobody nobody 4096 Jan 25 18:09 tx_queue_len
  -r--r--r-- 1 nobody nobody 4096 Jan 25 18:09 type
  -rw-r--r-- 1 nobody nobody 4096 Jan 25 18:08 uevent

  Constrast this with creating a device of the same type in the network
  namespace directly. In this case the device's sysfs permissions will be
  correctly updated.
  

[Kernel-packages] [Bug 1869423] Re: Restore kernel control of PCIe DPC via option

[Thadeu Lima de Souza Cascardo]

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

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

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

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

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

Title:
  Restore kernel control of PCIe DPC via option

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

Bug description:
  
  SRU Justification:

  Impact:

Since upstream commit eed85ff4c0da7 (4.16), control of PCIe DPC
  (Downstream Port Containment) is coupled with control of AER (Advanced
  Error Reporting), eliminating the option for the kernel to separately
  manage DPC (which was previously the default behavior).

  Fix:

  The upstream commit log explains the change:

  commit 35a0b2378c199d4f26e458b2ca38ea56aaf2d9b8
  Author: Olof Johansson 
  Date:   Wed Oct 23 12:22:05 2019 -0700

  PCI/DPC: Add "pcie_ports=dpc-native" to allow DPC without AER control
  
  Prior to eed85ff4c0da7 ("PCI/DPC: Enable DPC only if AER is available"),
  Linux handled DPC events regardless of whether firmware had granted it
  ownership of AER or DPC, e.g., via _OSC.
  
  PCIe r5.0, sec 6.2.10, recommends that the OS link control of DPC to
  control of AER, so after eed85ff4c0da7, Linux handles DPC events only if 
it
  has control of AER.
  
  On platforms that do not grant OS control of AER via _OSC, Linux DPC
  handling worked before eed85ff4c0da7 but not after.
  
  To make Linux DPC handling work on those platforms the same way they did
  before, add a "pcie_ports=dpc-native" kernel parameter that makes Linux
  handle DPC events regardless of whether it has control of AER.
  
  [bhelgaas: commit log, move pcie_ports_dpc_native to drivers/pci/]
  Link: https://lore.kernel.org/r/20191023192205.97024-1-o...@lixom.net
  Signed-off-by: Olof Johansson 
  Signed-off-by: Bjorn Helgaas 

  Testcase:

Control of DPC can be determined from kernel boot messages when
  pciehp probes a capable slot; when the kernel controls DPC, messages
  of the format:

  pcieport :2d:00.0: pciehp: Slot #0
  pcieport :2d:00.0: DPC: error containment capabilities:

will appear; if the kernel does not control DPC, the DPC line will
  not be present (only the "pciehp: Slot" message).

Additionally, devices bound to the kernel DPC PCIe port service
  driver will be found in the /sys/bus/pci_express/drivers/dpc/ sysfs
  directory; this will be empty of devices if the kernel does not control
  DPC.

  Regression Potential:

The risk of regression is low as (a) by default, the patch has no
  effect (the default setting is to not enable the option), and (b) when
  enabled, the patch restores functionality that previously worked, and was,
  in fact, the default behavior.

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

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

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

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1869423

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  Restore kernel control of PCIe DPC via option

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

Bug description:
  
  SRU Justification:

  Impact:

Since upstream commit eed85ff4c0da7 (4.16), control of PCIe DPC
  (Downstream Port Containment) is coupled with control of AER (Advanced
  Error Reporting), eliminating the option for the kernel to separately
  manage DPC (which was previously the default behavior).

  Fix:

  The upstream commit log explains the change:

  commit 35a0b2378c199d4f26e458b2ca38ea56aaf2d9b8
  Author: Olof Johansson 
  Date:   Wed Oct 23 12:22:05 2019 -0700

  PCI/DPC: Add "pcie_ports=dpc-native" to allow DPC without AER control
  
  Prior to eed85ff4c0da7 ("PCI/DPC: Enable DPC only if AER is available"),
  Linux handled DPC events regardless of whether firmware had granted it
  ownership of AER or DPC, e.g., via _OSC.
  
  PCIe r5.0, sec 6.2.10, recommends that the OS link control of DPC to
  control of AER, so after eed85ff4c0da7, Linux handles DPC events only if 
it
  has control of AER.
  
  On platforms that do not grant OS control of AER via _OSC, Linux DPC
  handling worked before eed85ff4c0da7 but not after.
  
  To make Linux DPC handling work on those platforms the same way they did
  before, add a "pcie_ports=dpc-native" kernel parameter that makes Linux
  handle DPC events regardless of whether it has control of AER.
  
  [bhelgaas: commit log, move pcie_ports_dpc_native to drivers/pci/]
  Link: https://lore.kernel.org/r/20191023192205.97024-1-o...@lixom.net
  Signed-off-by: Olof Johansson 
  Signed-off-by: Bjorn Helgaas 

  Testcase:

Control of DPC can be determined from kernel boot messages when
  pciehp probes a capable slot; when the kernel controls DPC, messages
  of the format:

  pcieport :2d:00.0: pciehp: Slot #0
  pcieport :2d:00.0: DPC: error containment capabilities:

will appear; if the kernel does not control DPC, the DPC line will
  not be present (only the "pciehp: Slot" message).

Additionally, devices bound to the kernel DPC PCIe port service
  driver will be found in the /sys/bus/pci_express/drivers/dpc/ sysfs
  directory; this will be empty of devices if the kernel does not control
  DPC.

  Regression Potential:

The risk of regression is low as (a) by default, the patch has no
  effect (the default setting is to not enable the option), and (b) when
  enabled, the patch restores functionality that previously worked, and was,
  in fact, the default behavior.

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

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

[Kernel-packages] [Bug 1866909] Re: Ubuntu Kernel Support for OpenPOWER NV Secure & Trusted Boot

[Dimitri John Ledkov]

"May I ask the kernel version that Ubuntu will be using for 20.04 ?"

I see this getting asked a lot on both Power and Z tickets, I thought
Ubuntu communicated way back in November 2019 to everyone that we will
ship linux-generic in 20.04 based on v5.4 kernel.

Is this not been clear? or are there any teams working on Power or Z
that need this reiterated? Where should this be communicated, such that
it no longer is a question?

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

Title:
  Ubuntu Kernel Support for OpenPOWER NV Secure & Trusted Boot

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  == Comment: #0 - George C. Wilson  - 2020-02-25 18:40:44 
==
  - sysfs enablement: TBD
  - ima: arch specific policy support 6191706246de
  - platform keyring changes for powerpc: TBD
  - Appended signatures support for IMA appraisal 
39b07096364a42c516415d5f841069e885234e61
  - integrity: Define a trusted platform keyring: 9dc92c45177a
  - ima: Support platform keyring for kernel appraisal: d7cecb676dd3
  - TPM 2.0 Multibank extend support: c1f92b4b04ad
  - TPM 2.0 Eventlog support: 4d23cc323cdb
  - ima: carry the measurement list across kexec: d68a6fe9fccf
  - kexec_file_load system call support: 500c7ab1a9db

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

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

[Kernel-packages] [Bug 1869423] [NEW] Restore kernel control of PCIe DPC via option

[Jay Vosburgh]

Public bug reported:


SRU Justification:

Impact:

Since upstream commit eed85ff4c0da7 (4.16), control of PCIe DPC
(Downstream Port Containment) is coupled with control of AER (Advanced
Error Reporting), eliminating the option for the kernel to separately
manage DPC (which was previously the default behavior).

Fix:

The upstream commit log explains the change:

commit 35a0b2378c199d4f26e458b2ca38ea56aaf2d9b8
Author: Olof Johansson 
Date:   Wed Oct 23 12:22:05 2019 -0700

PCI/DPC: Add "pcie_ports=dpc-native" to allow DPC without AER control

Prior to eed85ff4c0da7 ("PCI/DPC: Enable DPC only if AER is available"),
Linux handled DPC events regardless of whether firmware had granted it
ownership of AER or DPC, e.g., via _OSC.

PCIe r5.0, sec 6.2.10, recommends that the OS link control of DPC to
control of AER, so after eed85ff4c0da7, Linux handles DPC events only if it
has control of AER.

On platforms that do not grant OS control of AER via _OSC, Linux DPC
handling worked before eed85ff4c0da7 but not after.

To make Linux DPC handling work on those platforms the same way they did
before, add a "pcie_ports=dpc-native" kernel parameter that makes Linux
handle DPC events regardless of whether it has control of AER.

[bhelgaas: commit log, move pcie_ports_dpc_native to drivers/pci/]
Link: https://lore.kernel.org/r/20191023192205.97024-1-o...@lixom.net
Signed-off-by: Olof Johansson 
Signed-off-by: Bjorn Helgaas 

Testcase:

Control of DPC can be determined from kernel boot messages when
pciehp probes a capable slot; when the kernel controls DPC, messages
of the format:

pcieport :2d:00.0: pciehp: Slot #0
pcieport :2d:00.0: DPC: error containment capabilities:

will appear; if the kernel does not control DPC, the DPC line will
not be present (only the "pciehp: Slot" message).

Additionally, devices bound to the kernel DPC PCIe port service
driver will be found in the /sys/bus/pci_express/drivers/dpc/ sysfs
directory; this will be empty of devices if the kernel does not control
DPC.

Regression Potential:

The risk of regression is low as (a) by default, the patch has no
effect (the default setting is to not enable the option), and (b) when
enabled, the patch restores functionality that previously worked, and was,
in fact, the default behavior.

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

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

Title:
  Restore kernel control of PCIe DPC via option

Status in linux package in Ubuntu:
  New

Bug description:
  
  SRU Justification:

  Impact:

Since upstream commit eed85ff4c0da7 (4.16), control of PCIe DPC
  (Downstream Port Containment) is coupled with control of AER (Advanced
  Error Reporting), eliminating the option for the kernel to separately
  manage DPC (which was previously the default behavior).

  Fix:

  The upstream commit log explains the change:

  commit 35a0b2378c199d4f26e458b2ca38ea56aaf2d9b8
  Author: Olof Johansson 
  Date:   Wed Oct 23 12:22:05 2019 -0700

  PCI/DPC: Add "pcie_ports=dpc-native" to allow DPC without AER control
  
  Prior to eed85ff4c0da7 ("PCI/DPC: Enable DPC only if AER is available"),
  Linux handled DPC events regardless of whether firmware had granted it
  ownership of AER or DPC, e.g., via _OSC.
  
  PCIe r5.0, sec 6.2.10, recommends that the OS link control of DPC to
  control of AER, so after eed85ff4c0da7, Linux handles DPC events only if 
it
  has control of AER.
  
  On platforms that do not grant OS control of AER via _OSC, Linux DPC
  handling worked before eed85ff4c0da7 but not after.
  
  To make Linux DPC handling work on those platforms the same way they did
  before, add a "pcie_ports=dpc-native" kernel parameter that makes Linux
  handle DPC events regardless of whether it has control of AER.
  
  [bhelgaas: commit log, move pcie_ports_dpc_native to drivers/pci/]
  Link: https://lore.kernel.org/r/20191023192205.97024-1-o...@lixom.net
  Signed-off-by: Olof Johansson 
  Signed-off-by: Bjorn Helgaas 

  Testcase:

Control of DPC can be determined from kernel boot messages when
  pciehp probes a capable slot; when the kernel controls DPC, messages
  of the format:

  pcieport :2d:00.0: pciehp: Slot #0
  pcieport :2d:00.0: DPC: error containment capabilities:

will appear; if the kernel does not control DPC, the DPC line will
  not be present (only the "pciehp: Slot" message).

Additionally, devices bound to the kernel DPC PCIe port service
  driver will be found in the /sys/bus/pci_express/drivers/dpc/ sysfs
  directory; this will be empty of devices if the kernel does not control
  DPC.

  Regression 

[Kernel-packages] [Bug 1869235] Re: Ryzen 3rd gen (3900X) ECC support missing from kernel

[Alex Hung]

@araemo,

Thanks for reporting.

I will prepare a SRU for eoan kernel (5.3). Can you try the below kernel
(Ubuntu-5.3.0-42.34 + cherry-picked e53a3b267fb0 & 3e443eb353ed). If
your problem goes away I will send the patches for SRU reviews.

https://people.canonical.com/~alexhung/LP1869235/

We may need your help test proposed kernel before next kernel updates
later as I do not have the hardware to verify it.

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

Title:
  Ryzen 3rd gen (3900X) ECC support missing from kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu server:
  Description:Ubuntu 19.10
  Release:19.10
  Installed kernel:
  linux-generic:
Installed: 5.3.0.42.36
  (I could not figure out what package to select in the 'in what package did 
you find this bug' chooser)

  Expected behavior: ECC RAM is detected and utilized
  Result instead:
  Error in dmesg at boot:
  EDAC amd64: Error: F0 not found, device 0x1460 (broken BIOS?) (more in the 
attached KernelErrors.log)

  Kernel 5.3 is missing ECC support for some families of AMD Ryzen 3rd
  gen CPUs.

  Support is added via these two commits in the mainline tree:
  
https://github.com/torvalds/linux/commit/e53a3b267fb0a79db9ca1f1e08b97889b22013e6
  
https://github.com/torvalds/linux/commit/3e443eb353eda6f4b4796e07f2599683fa752f1d

  The second commit actually adds the missing support, but it relies on
  the first commit: a partial refactor of the AMD ECC code.

  I tested myself, followed the instructions at 
https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel to build my own kernel, 
cherry-picked the two above commits, and have working ECC support on my 
self-built kernel:
  Linux smaug 5.3.0-43-generic #36 SMP Sat Mar 21 02:33:30 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux:

  EDAC MC: Ver: 3.0.0
  EDAC amd64: Node 0: DRAM ECC enabled.
  EDAC amd64: F17h_M70h detected (node 0).
  EDAC MC: UMC0 chip selects:
  EDAC amd64: MC: 0: 0MB 1: 0MB
  EDAC amd64: MC: 2: 16384MB 3: 16384MB
  EDAC MC: UMC1 chip selects:
  EDAC amd64: MC: 0: 0MB 1: 0MB
  EDAC amd64: MC: 2: 16384MB 3: 16384MB
  EDAC amd64: using x16 syndromes.
  EDAC amd64: MCT channel count: 2
  EDAC MC0: Giving out device to module amd64_edac controller F17h_M70h: DEV 
:00:18.3 (INTERRUPT)
  EDAC PCI0: Giving out device to module amd64_edac controller EDAC PCI 
controller: DEV :00:18.0 (POLLED)
  AMD64 EDAC driver v3.5.0

  
  If this could be included in a future hardware support kernel release, that 
would be very helpful.  I am unsure what the policy is for including this kind 
of backport in non-LTS kernels, though I know the LTS releases have hardware 
support updates that include this type of fix.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-03-20 (6 days ago)
  InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=89cfcc61-dbca-43d3-9a2e-5961df9ae5b4 ro
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  RfKill:
   
  Tags:  eoan uec-images
  Uname: Linux 5.3.0-42-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lxd plugdev sudo
  _MarkForUpload: False
  dmi.bios.date: 10/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.30
  dmi.board.name: X470D4U2-2T
  dmi.board.vendor: ASRockRack
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.30:bd10/03/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRockRack:rnX470D4U2-2T:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1869413] [NEW] Disco update: upstream stable patchset 2020-03-27

[Kamal Mostafa]

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   upstream stable patchset 2020-03-27

Ported from the following upstream stable releases:
v4.19.109, v5.4.25,
v4.19.110, 
v4.19.111, v5.4.26

   from git://git.kernel.org/

ALSA: hda/realtek - Fix a regression for mute led on Lenovo Carbon X1
net: dsa: bcm_sf2: Forcibly configure IMP port for 1Gb/sec
RDMA/core: Fix pkey and port assignment in get_new_pps
RDMA/core: Fix use of logical OR in get_new_pps
kprobes: Fix optimize_kprobe()/unoptimize_kprobe() cancellation logic
ALSA: hda: do not override bus codec_mask in link_get()
serial: ar933x_uart: set UART_CS_{RX,TX}_READY_ORIDE
selftests: fix too long argument
usb: gadget: composite: Support more than 500mA MaxPower
usb: gadget: ffs: ffs_aio_cancel(): Save/restore IRQ flags
usb: gadget: serial: fix Tx stall after buffer overflow
drm/msm/mdp5: rate limit pp done timeout warnings
drm: msm: Fix return type of dsi_mgr_connector_mode_valid for kCFI
scsi: megaraid_sas: silence a warning
drm/msm/dsi: save pll state before dsi host is powered off
drm/msm/dsi/pll: call vco set rate explicitly
selftests: forwarding: use proto icmp for {gretap, ip6gretap}_mac testing
net: ks8851-ml: Remove 8-bit bus accessors
net: ks8851-ml: Fix 16-bit data access
net: ks8851-ml: Fix 16-bit IO operation
watchdog: da9062: do not ping the hw during stop()
s390/cio: cio_ignore_proc_seq_next should increase position index
s390: make 'install' not depend on vmlinux
x86/boot/compressed: Don't declare __force_order in kaslr_64.c
s390/qdio: fill SL with absolute addresses
nvme: Fix uninitialized-variable warning
ice: Don't tell the OS that link is going down
x86/xen: Distribute switch variables for initialization
net: thunderx: workaround BGX TX Underflow issue
ALSA: hda/realtek - Add Headset Mic supported
ALSA: hda/realtek - Fix silent output on Gigabyte X570 Aorus Master
cifs: don't leak -EAGAIN for stat() during reconnect
usb: storage: Add quirk for Samsung Fit flash
usb: quirks: add NO_LPM quirk for Logitech Screen Share
usb: dwc3: gadget: Update chain bit correctly when using sg list
usb: core: hub: fix unhandled return by employing a void function
usb: core: hub: do error out if usb_autopm_get_interface() fails
usb: core: port: do error out if usb_autopm_get_interface() fails
vgacon: Fix a UAF in vgacon_invert_region
mm, numa: fix bad pmd by atomically check for pmd_trans_huge when marking page 
tables prot_numa
mm: fix possible PMD dirty bit lost in set_pmd_migration_entry()
fat: fix uninit-memory access for partial initialized inode
arm: dts: dra76x: Fix mmc3 max-frequency
tty:serial:mvebu-uart:fix a wrong return
serial: 8250_exar: add support for ACCES cards
vt: selection, close sel_buffer race
vt: selection, push console lock down
vt: selection, push sel_lock up
media: v4l2-mem2mem.c: fix broken links
x86/pkeys: Manually set X86_FEATURE_OSPKE to preserve existing changes
dmaengine: tegra-apb: Fix use-after-free
dmaengine: tegra-apb: Prevent race conditions of tasklet vs free list
dm cache: fix a crash due to incorrect work item cancelling
dm: report suspended device during destroy
dm writecache: verify watermark during resume
ARM: dts: ls1021a: Restore MDIO compatible to gianfar
spi: bcm63xx-hsspi: Really keep pll clk enabled
ASoC: topology: Fix memleak in soc_tplg_link_elems_load()
ASoC: topology: Fix memleak in soc_tplg_manifest_load()
ASoC: intel: skl: Fix pin debug prints
ASoC: intel: skl: Fix possible buffer overflow in debug outputs
ASoC: pcm: Fix possible buffer overflow in dpcm state sysfs output
ASoC: pcm512x: Fix unbalanced regulator enable call in probe error path
ASoC: dapm: Correct DAPM handling of active widgets during shutdown
drm/sun4i: Fix DE2 VI layer format support
drm/sun4i: de2/de3: Remove unsupported VI layer formats
phy: mapphone-mdm6600: Fix timeouts by adding wake-up handling
phy: mapphone-mdm6600: Fix write timeouts with shorter GPIO toggle interval
ARM: dts: imx6: phycore-som: fix emmc supply
RDMA/iwcm: Fix iwcm work deallocation
RMDA/cm: Fix missing ib_cm_destroy_id() in ib_cm_insert_listen()
IB/hfi1, qib: Ensure RCU is locked when accessing list
ARM: imx: build v7_cpu_resume() unconditionally
ARM: dts: am437x-idk-evm: Fix incorrect OPP node names
ARM: dts: imx7-colibri: Fix frequency for sd/mmc
hwmon: (adt7462) Fix an error return in ADT7462_REG_VOLT()
dmaengine: coh901318: Fix a double lock bug in dma_tc_handle()
powerpc: fix hardware PMU exception bug on PowerVM compatibility mode systems

[Kernel-packages] [Bug 1861359] Re: swap storms kills interactive use

[Andrea Righi]

** Description changed:

+ [Impact]
+ 
+ High watermark boosting can cause large swap activity under certain
+ memory intensive workloads, making the system very unresponsive (screen
+ does not refresh, keyboard not responding, etc.).
+ 
+ This large swap activity seems to be prevented disabling high watermark
+ boosting.
+ 
+ [Test case]
+ 
+ Opening this web page in chrome seems to be a good reproducer of the
+ problem:
+ 
+ 
https://platform.leolabs.space/visualizations/conjunction?type=conjunction=2004981040
+ 
+ When this page is opened we can clearly see from 'top' (for example)
+ that the used swap is going up very quickly.
+ 
+ With the fix applied swap is not used at all and the system is always
+ responsive.
+ 
+ [Fix]
+ 
+ Set vm.watermark_boost_factor to 0, disabling watermark boosting by
+ default.
+ 
+ [Regression potential]
+ 
+ Regression potential is minimal, setting vm.watermark_boost_factor to 0
+ by default restores the old kernel behavior before watermark boosting
+ was introduced. In case of unexpected regressions we can always fix this
+ in user-space via sysctl.
+ 
+ [Original report]
+ 
  Hello, several times since upgrading to focal from 19.04 I've found my
  computer entirely unresponsive for periods of twenty or thirty seconds.
  No mouse movement, no keyboard input, the screen output does not change.
  
  My computer was using swap space and despite very slow writeout speeds
  well below what the NVME drive can handle, the computer was unusable.
  
  I've captured some vmstat 1 output and top output that I started
  collecting during the event. (Normally one very long painful period is
  followed by several shorter periods of uselessness.)
  
  Thanks
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Wed Jan 29 23:44:05 2020
  ProcEnviron:
-  TERM=rxvt-unicode-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=rxvt-unicode-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
- --- 
+ ---
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  sarnold2734 F pulseaudio
-  /dev/snd/controlC1:  sarnold2734 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  sarnold2734 F pulseaudio
+  /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
-  Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
-Mixer name : 'Realtek ALC285'
-Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
-Controls  : 53
-Simple ctrls  : 15
+  Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
+    Mixer name : 'Realtek ALC285'
+    Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
+    Controls  : 53
+    Simple ctrls  : 15
  Card1.Amixer.info:
-  Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
-Mixer name : 'USB Mixer'
-Components : 'USB17ef:306f'
-Controls  : 9
-Simple ctrls  : 4
+  Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
+    Mixer name : 'USB Mixer'
+    Components : 'USB17ef:306f'
+    Controls  : 9
+    Simple ctrls  : 4
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=none
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: LENOVO 20KHCTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
-  TERM=rxvt-unicode-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=rxvt-unicode-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic 
root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash 
acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
-  linux-restricted-modules-5.4.0-12-generic N/A
-  linux-backports-modules-5.4.0-12-generic  N/A
-  linux-firmware1.185
+  linux-restricted-modules-5.4.0-12-generic N/A
+  linux-backports-modules-5.4.0-12-generic  N/A
+  linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 

[Kernel-packages] [Bug 1847816] Re: storage autopkgtest always fails with linux-{kvm, azure, etc} kernels that don't include scsi_debug module

[Dan Streetman]

** Changed in: autopkgtest-cloud
   Status: New => Fix Released

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

Title:
  storage autopkgtest always fails with linux-{kvm,azure,etc} kernels
  that don't include scsi_debug module

Status in autopkgtest-cloud:
  Fix Released
Status in linux-kvm package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in linux-kvm source package in Xenial:
  New
Status in systemd source package in Xenial:
  In Progress
Status in linux-kvm source package in Bionic:
  New
Status in systemd source package in Bionic:
  Fix Released
Status in linux-kvm source package in Disco:
  New
Status in systemd source package in Disco:
  Won't Fix
Status in linux-kvm source package in Eoan:
  New
Status in systemd source package in Eoan:
  Fix Released
Status in linux-kvm source package in Focal:
  New
Status in systemd source package in Focal:
  Fix Released

Bug description:
  Note: this bug touches on multiple packages:
  - autopkgtest-cloud: merge request open to install 'modules-extra' package
  - systemd: update autopkgtest to skip test if scsi_debug module isn't 
available (SRU template below is for this change)
  - linux-kvm: has CONFIG_SCSI_DEBUG unset, but would be good to have 
scsi_debug module built for this kernel

  [SRU template for systemd]

  [impact]

  the 'storage' autopkgtest requires the 'scsi_debug' module, and if it
  can't load it (and it's not built-in), the test fails.  On some custom
  kernels, this module is included in the new 'linux-modules-extra-*'
  deb which isn't installed by default, so the test always fails when
  doing a reverse-dep autopkgtest using such a kernel's meta pkg.

  Additionally, some custom kernels, like linux-kvm, have SCSI_DEBUG
  disabled entirely; for those kernels, it will never be possible to
  load the scsi_debug module and the test should be skipped.

  [test case]

  run the 'storage' autopkgtest with a custom kernel that doesn't
  provide the scsi_debug module in the standard linux-modules deb, or
  check the autopkgtest.u.c history, for example:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal/focal/amd64/s/systemd/20191209_150835_237a5@/log.gz

  [regression potential]

  as this modifies one of the autopkgtest --setup-commands, a regression
  would most likely cause immediate test failure due to failing to
  install the proper linux-* debs.

  For the systemd 'storage' test change, this only skips the test if the
  scsi_debug module can't be loaded (and isn't already present, i.e.
  loaded or built-in).  Any regression potential from that is low, but
  likely would involve incorrect test skips and/or missing valid
  problems due to skipping the test.

  [scope]

  systemd in all releases needs to have its 'storage' test updated

To manage notifications about this bug go to:
https://bugs.launchpad.net/autopkgtest-cloud/+bug/1847816/+subscriptions

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

[Kernel-packages] [Bug 1778087] Re: ELAN1200 touchpad jumps around and disconnects

[Gaston Castro]

Hi, as an update, on my ASUS-GL503VD the erratic behaviour disappeared
around 5.2.x but still disconnected from time to time. I'm on 5.3.7 now
and disconnecting remains.

I just use: 'modprobe -r i2c_hid' and 'modprobe i2c_hid' to restore it
and keep on going.

Thanks for the effort!

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

Title:
  ELAN1200 touchpad jumps around and disconnects

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is on an ASUS GL503VD laptop and would probably affect other ASUS
  laptops equipped with the ELAN1200 touchpad.

  I am on Kernel 4.17.2 because older kernels did not enable the
  touchpad at all(It was just unrecognized or i2c-hid stopped the
  computer from booting)

  The touchpad works but it has erratic behaviour and disconnects
  randomly. After it disconnects the only way to bring it back is to
  `modprobe -r hid-multitouch && modprobe hid-multitouch`

  Libinput and synaptics can handle the touchpad though I found
  synaptics to be more stable.

  dmesg gets spammed with this whenever I move the touchpad:
  [timestamp] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report 
(16/65535)

  I tried to compile: https://github.com/mishurov/linux_elan1200_touchpad
  Because from what I understand the "jumpy/disconnect" problem is associated 
to the incomplete reports and Mishurov managed to mitigate those. Unfortunately 
some symbols were deprecated in kernel 4.17.2 and it did not compile for my 
system.

  While I can use my touchpad as is right now, and "restart" it with
  modprobe when needed, it would be nice to have it function bug-free.
  (Right after I typed this my touchpad disconnected and I needed to
  modprobe again, I am considering making a cronjob for that)

  Let me know if anything else is needed. Will wait for an apport collection to 
add log files.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-10 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  Tags:  bionic
  Uname: Linux 4.17.2 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1861359] Re: swap storms kills interactive use

[Sultan Alsawaf]

This problem is caused by an upstream memory management feature called
watermark boosting. Normally, when a memory allocation fails and falls
back to the page allocator, the page allocator will wake up kswapd to
free up pages in order to make the memory allocation succeed. kswapd
tries to free memory until it reaches a minimum amount of memory for
each memory zone called the high watermark.

What watermark boosting does is try to preemptively fire up kswapd to
free memory when there hasn't been an allocation failure. It does this
by increasing kswapd's high watermark goal and then firing up kswapd.
The reason why this causes freezes is because, with the increased high
watermark goal, kswapd will steal memory from processes that need it in
order to make forward progress. These processes will, in turn, try to
allocate memory again, which will cause kswapd to steal necessary pages
from those processes again, in a positive feedback loop known as page
thrashing. When page thrashing occurs, your system is essentially
livelocked until the necessary forward progress can be made to stop
processes from trying to continuously allocate memory and trigger kswapd
to steal it back.

This problem already occurs with kswapd *without* watermark boosting,
but it's usually only encountered on machines with a small amount of
memory and/or a slow CPU. Watermark boosting just makes the existing
problem worse enough to notice on higher spec'd machines.

To fix the issue in this bug, watermark boosting can be disabled with the 
following:
# echo 0 > /proc/sys/vm/watermark_boost_factor

There's really no harm in doing so, because watermark boosting is an
inherently broken feature...

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

Title:
  swap storms kills interactive use

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello, several times since upgrading to focal from 19.04 I've found my
  computer entirely unresponsive for periods of twenty or thirty
  seconds. No mouse movement, no keyboard input, the screen output does
  not change.

  My computer was using swap space and despite very slow writeout speeds
  well below what the NVME drive can handle, the computer was unusable.

  I've captured some vmstat 1 output and top output that I started
  collecting during the event. (Normally one very long painful period is
  followed by several shorter periods of uselessness.)

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Wed Jan 29 23:44:05 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
 Mixer name : 'Realtek ALC285'
 Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
 Controls  : 53
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB17ef:306f'
 Controls  : 9
 Simple ctrls  : 4
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=none
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: LENOVO 20KHCTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic 
root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash 
acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  UserGroups: adm cdrom libvirt lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 

[Kernel-packages] [Bug 1855668] Re: lockdown on power

[Seth Forshee]

Also I'll add, you can use this ppa to test the -proposed kernels
without enabling all of -proposed.

https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/proposed/

These are kernels copied from the -proposed pocked, after we've built
signed packages in -proposed.

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

Title:
  lockdown on power

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  == Comment: #0 - Michael Ranweiler  - 2019-11-11 
08:50:51 ==
  For 20.04 testing/inclusion.  The ubuntu kernel team has a ppa here for 
testing:
  https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable

  Test results will follow...

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

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

[Kernel-packages] [Bug 1855668] Re: lockdown on power

[Seth Forshee]

Lockdown is enabled in focal, and the default mode when booted without
any secure boot scheme is NONE.

When booted under a secure boot scheme, we had previously forced the
CONFIDENTIALITY mode for lockdown. But we have now scaled that back, and
the kernel in focal-proposed sets the mode to INTEGRITY under secure
boot. This kernel should be released early next week.

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

Title:
  lockdown on power

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  == Comment: #0 - Michael Ranweiler  - 2019-11-11 
08:50:51 ==
  For 20.04 testing/inclusion.  The ubuntu kernel team has a ppa here for 
testing:
  https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable

  Test results will follow...

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

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

[Kernel-packages] [Bug 1869395] [NEW] build failure when building with clang

[Colin Ian King]

Public bug reported:

Building this package against the unstable kernel with clang I hit the
following build failure:

>/build/nvidia/390.132/build/common/inc/nv-linux.h: In function 
‘nv_ioremap_nocache’:
<>/build/nvidia/390.132/build/common/inc/nv-linux.h:556:17: error: 
implicit declaration of function ‘ioremap_nocache’; did you mean 
‘ioremap_cache’? [-Werror=implicit-function-declaration]
  556 | void *ptr = ioremap_nocache(phys, size);
  | ^~~
  | ioremap_cache

Building the same dkms package with gcc this works fine. I think clang
is being more pedantic about the missing declaration for
ioremap_nocache()

** Affects: nvidia-graphics-drivers-390 (Ubuntu)
 Importance: Medium
 Status: New

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  build failure when building with clang

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

Bug description:
  Building this package against the unstable kernel with clang I hit the
  following build failure:

  >/build/nvidia/390.132/build/common/inc/nv-linux.h: In function 
‘nv_ioremap_nocache’:
  <>/build/nvidia/390.132/build/common/inc/nv-linux.h:556:17: error: 
implicit declaration of function ‘ioremap_nocache’; did you mean 
‘ioremap_cache’? [-Werror=implicit-function-declaration]
556 | void *ptr = ioremap_nocache(phys, size);
| ^~~
| ioremap_cache

  Building the same dkms package with gcc this works fine. I think clang
  is being more pedantic about the missing declaration for
  ioremap_nocache()

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

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

[Kernel-packages] [Bug 1855668] Re: lockdown on power

[Frank Heimes]

Looking up the options I see that on ppc64el there is (on focal/20.04):
CONFIG_LOCK_DOWN_KERNEL_FORCE_INTEGRITY=n
CONFIG_LOCK_DOWN_KERNEL_FORCE_CONFIDENTIALITY=n
CONFIG_LOCK_DOWN_KERNEL_FORCE_NONE=y
but
CONFIG_LSM="lockdown,yama,integrity,apparmor"

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

Title:
  lockdown on power

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  == Comment: #0 - Michael Ranweiler  - 2019-11-11 
08:50:51 ==
  For 20.04 testing/inclusion.  The ubuntu kernel team has a ppa here for 
testing:
  https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable

  Test results will follow...

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

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

[Kernel-packages] [Bug 1869032] Re: Kernel oopsed and null pointer dereference while running ubuntu_kernel_selftests on Eoan Power8

[Po-Hsu Lin]

The jenkins job for sru-misc has successfully completed on node modoc
with 5.3.0-43 without any hang issue. (I don't have a chance to check
for syslog, but since it's not hanging I guess it's fine).

I've also tested the net/tls test in the selftest for 100 times on modoc with 
5.3.0-43, passed with oops:
  for i in $(seq 1 100); do sudo ./tls; done

Furthermore, I had it tested with the net test suite for 100 time, passed 
without oops:
  for i in $(seq 1 100); do echo "== cycle $i ==" | sudo tee /dev/kmsg; 
sudo make run_tests TARGETS=net; done

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

Title:
  Kernel oopsed and null pointer dereference while running
  ubuntu_kernel_selftests on Eoan Power8

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

Bug description:
  Issue found on P8 node modoc with Eoan (5.3.0-43.36)
  (Note that this test has passed with P9 node baltar without any traces in 
syslog)

  The ubuntu_kernel_selftests hangs:
  15:16:53 DEBUG| [stdout] ok 4 selftests: net: reuseport_dualstack
  15:16:53 DEBUG| [stdout] # selftests: net: reuseaddr_conflict
  15:16:53 DEBUG| [stdout] # Opening 127.0.0.1:
  15:16:53 DEBUG| [stdout] # Opening INADDR_ANY:
  15:16:53 DEBUG| [stdout] # bind: Address already in use
  15:16:53 DEBUG| [stdout] # Opening in6addr_any:
  15:16:53 DEBUG| [stdout] # Opening INADDR_ANY:
  15:16:53 DEBUG| [stdout] # bind: Address already in use
  15:16:53 DEBUG| [stdout] # Opening INADDR_ANY: after closing ipv6 socket
  15:16:53 DEBUG| [stdout] # bind: Address already in use
  15:16:53 DEBUG| [stdout] # Successok 5 selftests: net: reuseaddr_conflict
  15:16:53 DEBUG| [stdout] # selftests: net: tls
  15:16:56 DEBUG| [stdout] # tls.c:967:tls.mutliproc_sendpage_even:Expected 
status (4) == 0 (0)
  15:17:26 DEBUG| [stdout] # Alarm clock
  15:45:20 INFO | Timer expired (1800 sec.), nuking pid 33351
  (And test continues)

  It looks like it's the selftests: net: tls that's causing this issue.

  If you ssh to the node, the following trace could be found in dmesg:
   Injecting error (-12) to MEM_GOING_OFFLINE
   Injecting error (-12) to MEM_GOING_OFFLINE
   Injecting error (-12) to MEM_GOING_OFFLINE
   Oops: Exception in kernel mode, sig: 4 [#1]
   LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA PowerNV
   Modules linked in: tls binfmt_misc dm_multipath scsi_dh_rdac scsi_dh_emc 
scsi_dh_alua ipmi_powernv uio_pdrv_genirq ipmi_devintf ipmi_msghandler uio 
powernv_rng ibmpowernv vmx_crypto leds_powernv powernv_op_panel sch_fq_codel 
ip_tables x_tables autofs4 ses enclosure scsi_transport_sas btrfs zstd_compress 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_vpmsum crc32c_vpmsum 
tg3 ipr [last unloaded: notifier_error_inject]
   CPU: 18 PID: 36045 Comm: tls Not tainted 5.3.0-43-generic #36-Ubuntu
   NIP:  c0080a4d6a40 LR: c0080a4d6a40 CTR: c0179270
   REGS: c00fc97837a0 TRAP: 0e40   Not tainted  (5.3.0-43-generic)
   MSR:  9288b033   CR: 28002862  
XER: 2000
   CFAR: c000dfc4 IRQMASK: 0
   GPR00: c0080a4d6a40 c00fc9783a30 c19d9000 
   GPR04: c00f5afc  c00fc97839b8 
   GPR08: c00f5afc   c00ff9a13780
   GPR12: 88002462 c00eb380  
   GPR16:  0ac875961368 0ac875960d38 0ac875960d90
   GPR20: 7c6b4ef0 c00e3996dc48  
   GPR24: c04a9d70  ea60 
   GPR28: c00c0398c740 cab32e70  c00f7ecebd00
   NIP [c0080a4d6a40] tls_sw_sendpage+0x68/0x100 [tls]
   LR [c0080a4d6a40] tls_sw_sendpage+0x68/0x100 [tls]
   Call Trace:
   [c00fc9783a30] [c0080a4d6a40] tls_sw_sendpage+0x68/0x100 [tls] 
(unreliable)
   [c00fc9783a80] [c0d7698c] inet_sendpage+0x8c/0x140
   [c00fc9783ad0] [c0c33fd8] kernel_sendpage+0x38/0x70
   [c00fc9783af0] [c0c34044] sock_sendpage+0x34/0x50
   [c00fc9783b10] [c04a9e8c] pipe_to_sendpage+0x7c/0xf0
   [c00fc9783b40] [c04ab3d4] __splice_from_pipe+0x164/0x280
   [c00fc9783ba0] [c04ad994] splice_from_pipe+0x74/0xc0
   [c00fc9783c20] [c04a9dbc] direct_splice_actor+0x4c/0xa0
   [c00fc9783c40] [c04aad14] splice_direct_to_actor+0x2a4/0x3c0
   [c00fc9783cc0] [c04aaee4] do_splice_direct+0xb4/0x130
   [c00fc9783d30] [c04565c4] do_sendfile+0x234/0x4a0
   [c00fc9783dd0] [c0456b70] sys_sendfile64+0x160/0x170
   [c00fc9783e20] [c000b388] system_call+0x5c/0x70
   Instruction dump:
       

[Kernel-packages] [Bug 1850130] Re: zpools fail to import after reboot on fresh install of eoan

[Launchpad Bug Tracker]

This bug was fixed in the package zfs-linux - 0.8.3-1ubuntu9

---
zfs-linux (0.8.3-1ubuntu9) focal; urgency=medium

  * debian/patches/4000-zsys-support.patch:
- Fix import of external pools by preserving original cache file on zpool
  detection imports (LP: #1850130)

 -- Didier Roche   Fri, 27 Mar 2020 14:56:47 +0100

** Changed in: zfs-linux (Ubuntu Focal)
   Status: Confirmed => Fix Released

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

Title:
  zpools fail to import after reboot on fresh install of eoan

Status in grub2 package in Ubuntu:
  New
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in grub2 source package in Focal:
  New
Status in zfs-linux source package in Focal:
  Fix Released

Bug description:
  Fresh installation of stock Ubuntu 19.10 Eoan with experimental root on ZFS.
  System has existing zpools with data.

  Installation is uneventful. First boot with no problems. Updates
  applied. No other changes from fresh installation. Reboot.

  External pool 'tank' imports with no errors. Reboot.

  External pool has failed to import on boot. In contrast bpool and
  rpool are ok. Manually re-import 'tank' with no issues. I can see both
  'tank' and its path in /dev/disk/by-id/ in /etc/zfs/zpool.cache.
  Reboot.

  'tank' has failed to import on boot. It is also missing from
  /etc/zfs/zpool.cache. Is it possible that the cache is being re-
  generated on reboot, and the newly imported pools are getting erased
  from it? I can re-import the pools again manually with no issues, but
  they don't persist between re-boots.

  Installing normally on ext4 this is not an issue and data pools import
  automatically on boot with no further effort.

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

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

[Kernel-packages] [Bug 1863234] Re: Disabling bpf() syscall on kernel lockdown break apps when secure boot is on

[Stefan Bader]

This was reverted due to bug #1868626

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

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

Title:
  Disabling bpf() syscall on kernel lockdown break apps when secure boot
  is on

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Triaged

Bug description:
  [Impact]

  The bpf(2) system call is completely blocked in Disco and Eoan when
  Secure Boot is enabled due to overly restrictive Lockdown policies.
  This makes it so that all bpf related tools are not usable on those
  releases.

  [Test Case]

  Set up test BPF programs:

  $ cat hello.bt
  BEGIN { printf("hello\n"); exit(); }
  $ cat kprobe.bt
  kprobe:do_nanosleep { printf("task sleeping...\n"); exit(); }
  $ cat open.bt
  tracepoint:syscalls:sys_enter_openat {
    printf("filename: [%s]; flags: [%d]\n",
   str(args->filename), args->flags);
  }

  Disable Secure Boot:

  $ sudo mokutil --disable-validation
  ...
  $ sudo reboot

  Ensure that hello.bt can run:

  $ sudo bpftrace hello.bt
  Attaching 1 probe...
  hello

  Ensure that a BPF program triggered by a kprobe works (run `sleep 1` in 
another terminal):
  $ sudo bpftrace kprobe.bt
  Attaching 1 probe...
  task sleeping...

  Ensure that a BPF program triggered by a tracepoint can access the filename 
and flags of openat(2):
  $ sudo bpftrace open.bt
  Attaching 1 probe...
  filename: [/proc/2317/cmdline]; flags: [0]
  filename: [/dev/iio:device1]; flags: [2048]
  ...

  Enable Secure Boot

  $ sudo mokutil --enable-validation
  ...
  $ sudo reboot

  Ensure that a basic BPF program can run:

  $ sudo bpftrace hello.bt
  Attaching 1 probe...
  hello

  Ensure that a BPF program triggered by a kprobe is blocked (kprobes aren't 
allowed under Secure Boot):
  $ sudo bpftrace kprobe.bt
  Attaching 1 probe...
  cannot attach kprobe, Operation not permitted
  Error attaching probe: 'kprobe:do_nanosleep'

  You should see the following kernel message logged:

  Lockdown: bpftrace: Use of kprobes is restricted; see man
  kernel_lockdown.7

  Ensure that a BPF program triggered by a tracepoint can NOT access the 
filename and flags of openat(2) (all filenames should be empty and all flags 
should be 0):
  $ sudo bpftrace open.bt
  Attaching 1 probe...
  filename: []; flags: [0]
  filename: []; flags: [0]
  ...

  You should see the following kernel message logged:

  Lockdown: iio-sensor-prox: BPF is restricted; see man
  kernel_lockdown.7

  [Regression Potential]

  Low. This is opening up the use of bpf(2) while under Lockdown. There
  should be no new restrictions put in place.

  [Original Report]

  In disco and eoan, lockdown is automatically enforced when secure boot
  is on [0]. Because lockdown was not in the mailine kernel at the time,
  some disrto-specific patches were added to the kernel, including one
  that drastically restricts BPF usage by completely disabling the use
  of the `bpf()` system call when lockdown is on [1].

  A consequence of that decision is that no application relying on eBPF
  can run on 19.04/19.10, unless secure boot / lockdown is disabled. For
  example, Cilium (cilium.io) strongly relies on BPF programs to
  implement its datapath and securing network connectivity between
  containers. Other applications like Suricata or Sysdig also rely on
  BPF to some extent. None of which will work by default on a EFI
  machine with secure boot activated.

  If I understand correctly, kernel 5.4 (to be used in focal) will have
  a different, lighter restricton (comming from mainline Linux kernel)
  [2], so `bpf()` for networking use cases should mostly work on 20.04.
  Is my understanding correct? If so, could this patch be backported to
  19.10 (and 19.04, if still supported) instead of completely disabling
  the syscall on lockdown?

  Links:
  [0] 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/disco/commit/?id=d0db99473fc3bb8a5d03f99ed454ac7ca5e7d517
  [1] 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/disco/commit/?id=2a68c65abae66d28e2acb3245cb156ae2ea6eb1d
  [2] 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/commit/?id=9d1f8be5cf42b497a3bddf1d523f2bb142e9318c

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

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

[Kernel-packages] [Bug 1225922] Re: Support static network configuration even on already configured devices

[Roufique Hossain]

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

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

** Changed in: linux-gcp (Ubuntu)
 Assignee: (unassigned) => Roufique Hossain (roufique)

** Changed in: cloud-init
 Assignee: (unassigned) => Roufique Hossain (roufique)

** Changed in: cloud-init
   Status: Confirmed => Fix Committed

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

Title:
  Support static network configuration even on already configured
  devices

Status in cloud-init:
  Fix Committed
Status in linux-gcp package in Ubuntu:
  Confirmed

Bug description:
  Some datasources (e.g. OpenNebula) support full static network
  configuration. It's done in local execution phase by pushing new
  interfaces configuration to *distro.apply_network*. This new
  configuration is written on disk and activated by calling ifup on
  particular devices. Unfortunatelly  it can't be guaranteed that full
  local phase is executed before any network configuration is done by
  system. Mentioned steps are OK only for devices not present in former
  network configuration or not configurated to start on boot (e.g. eth0
  configured on boot to take address from DHCP, the new static
  configuration is not applied on this device, it's already up and ifup
  just passes).

  It would be good to first put interfaces down before writing new
  configuration.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1225922/+subscriptions

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

[Kernel-packages] [Bug 1247712] Re: Unable to install Broadcom STA wireless driver on Precise 3.8 / 3.11 / 3.13 kernel via jockey-gtk

[Taihsiang Ho]

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

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

Title:
  Unable to install Broadcom STA wireless driver on Precise 3.8 / 3.11 /
  3.13 kernel via jockey-gtk

Status in Jockey:
  Invalid
Status in bcmwl package in Ubuntu:
  Invalid
Status in jockey package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  In Progress
Status in bcmwl source package in Precise:
  Invalid
Status in jockey source package in Precise:
  Won't Fix
Status in linux-lts-trusty source package in Precise:
  In Progress
Status in bcmwl source package in Trusty:
  Invalid
Status in jockey source package in Trusty:
  In Progress
Status in linux-lts-trusty source package in Trusty:
  In Progress
Status in bcmwl package in Baltix:
  Invalid

Bug description:
  SRU request:

  Please accept jockey_0.9.7-0ubuntu7.15 into precise-proposed.

  [Impact]

  Kernel versions higher than 3.8 fail to rebind the Broadcom device to
  the driver thus compromising system stability. While rebinding is a
  nice feature it can't come at the cost of system stability. For this
  reason we'll disable this feature when dealing with Linux >= 3.8 and
  preserve it in the other cases.

  [Test Case]

  Install and reboot into Linux 3.8 or higher (linux-lts-saucy or linux-
  lts-trusty), then use Jockey to install the broadcom wireless driver.
  Jockey will hang and the system will probably hang on shutdown.

  [Regression Potential]

  It should be minimal i.e. there won't be device rebinding on the
  livecd. This, however, shouldn't be an issue since the open broadcom
  driver should already work out of the box.

  Furthermore the test suite now covers this test case.


  == Description ==

  CID: 201303-13027 Dell Inspiron 5535
  CID: 201012-6925 Dell Latitude E6320
  CID: 201208-11536 Dell Latitude 6430u

  Affected chipsets:
  Broadcom 4365
  Broadcom 4313 [14e4:4727] (rev 01)
  Broadcom 43132

  The bcmwl (6.20.155.1+bdcom-0ubuntu0.0.2) cannot be installed on
  12.04.4 (3.11.0-15), 12.04.3 (3.8.0-29)

  Steps:
  1. Install Ubuntu 12.04.3 (or 12.04.4) + update
  2. Boot to desktop
  3. Install the Broadcom STA wireless driver via jockey-gtk

  Driver cannot be installed, jockey-gtk will stuck at "Downloading and 
installing driver"
  The last message from jockey.jog is:
  unbind/rebind on driver /sys/module/wl/drivers/pci:wl: device :02:00.0

  Error message could be found in dmesg:
  Nov  3 21:34:14 201012-6925 kernel: [  528.104653] 
wlc_lcnphy_rx_gain_tbl_free_entry = 5
  Nov  3 21:34:14 201012-6925 kernel: [  528.104863] BUG: unable to handle 
kernel paging request at a045d020
  Nov  3 21:34:14 201012-6925 kernel: [  528.104906] IP: [] 
0xa045d01f
  Nov  3 21:34:14 201012-6925 kernel: [  528.104936] PGD 1c0f067 PUD 1c13063 
PMD 2ea40067 PTE 0
  Nov  3 21:34:14 201012-6925 kernel: [  528.104967] Oops: 0010 [#1] SMP
  Nov  3 21:34:14 201012-6925 kernel: [  528.104988] Modules linked in: 
lib80211_crypt_tkip(F) wl(POF) lib80211(F) rfcomm(F) bnep(F) bluetooth(F) 
snd_hda_codec_hdmi(F) snd_hda_codec_idt(F) coretemp(F) kvm_intel(F) arc4(F) 
kvm(F) joydev(F) ghash_clmulni_intel(F) aesni_intel(F) ablk_helper(F) cryptd(F) 
lrw(F) mac80211(F) snd_hda_intel(F) brcmutil(F) snd_hda_codec(F) snd_hwdep(F) 
snd_pcm(F) i915(F) snd_seq_midi(F) snd_rawmidi(F) snd_seq_midi_event(F) 
snd_seq(F) aes_x86_64(F) snd_timer(F) snd_seq_device(F) cfg80211(F) snd(F) 
cordic(F) drm_kms_helper(F) drm(F) mei(F) psmouse(F) soundcore(F) xts(F) 
ppdev(F) gf128mul(F) parport_pc(F) i2c_algo_bit(F) dell_laptop(F) dcdbas(F) 
dell_wmi(F) video(F) lpc_ich(F) serio_raw(F) mac_hid(F) sparse_keymap(F) 
snd_page_alloc(F) wmi(F) microcode(F) lp(F) parport(F) ahci(F) libahci(F) 
sdhci_pci(F) sdhci(F) e1000e(F) [last unloaded: bcma]
  Nov  3 21:34:14 201012-6925 kernel: [  528.105424] CPU 0
  Nov  3 21:34:14 201012-6925 kernel: [  528.105438] Pid: 2695, comm: 
jockey-backend Tainted: PF  O 3.8.0-33-generic #48~precise1-Ubuntu Dell 
Inc. Latitude E6320/
  Nov  3 21:34:14 201012-6925 kernel: [  528.105493] RIP: 
0010:[]  [] 0xa045d01f
  Nov  3 21:34:14 201012-6925 kernel: [  528.105533] RSP: 0018:88001b405d50 
 EFLAGS: 00010282
  Nov  3 21:34:14 201012-6925 kernel: [  528.105558] RAX: 0001 RBX: 
880031788000 RCX: 
  Nov  3 21:34:14 201012-6925 kernel: [  528.105590] RDX:  RSI: 
a0861ec0 RDI: 880031788000
  Nov  3 21:34:14 201012-6925 kernel: [  528.105623] RBP: 88001b405d78 R08: 
 R09: 
  Nov  3 21:34:14 201012-6925 kernel: [  528.105657] R10: 3684 R11: 
0293 R12: 88001b405da0
  Nov  3 21:34:14 201012-6925 kernel: [  528.105690] R13: a08643e0 R14: 
880031788098 R15: 8800317880f8
  Nov  3 21:34:14 201012-6925 kernel: 

[Kernel-packages] [Bug 1849493] Re: CONFIG_ANDROID_BINDER_IPC=m is missing in the custom rolling kernels

[Roufique Hossain]

rtat.net

** Changed in: linux-gcp (Ubuntu Bionic)
 Assignee: (unassigned) => Roufique Hossain (roufique)

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

Title:
  CONFIG_ANDROID_BINDER_IPC=m is missing in the custom rolling kernels

Status in linux package in Ubuntu:
  Incomplete
Status in linux-azure package in Ubuntu:
  Incomplete
Status in linux-gcp package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Incomplete
Status in linux-azure source package in Bionic:
  New
Status in linux-gcp source package in Bionic:
  Fix Released
Status in linux source package in Disco:
  Incomplete
Status in linux-azure source package in Disco:
  New
Status in linux-gcp source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Incomplete
Status in linux-azure source package in Eoan:
  New
Status in linux-gcp source package in Eoan:
  New

Bug description:
  The rolling GCP kernel for bionic is missing
  CONFIG_ANDROID_BINDER_IPC=m which is enabled in the standard Ubuntu
  kernel since 19.04 and available through the HWE kernels in Bionic.

  As we require CONFIG_ANDROID_BINDER_IPC=m for a not released product
  in our kernels it would be great if we can import the relevant config
  changes to the GCP kernel (haven't yet checked our other cloud
  kernels).

  All relevant changes from Christian Brauner to enable binder in the
  Ubuntu kernel are present in the GCP kernel (see
  https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-
  gcp/+git/bionic/log/?h=gcp-edge=grep=brauner).

  See https://kernel.ubuntu.com/git/ubuntu/ubuntu-
  
bionic.git/commit/debian.master/config/config.common.ubuntu?h=hwe=a758aeb0bb0f52ccbee99f850709c57711753b33
  and https://kernel.ubuntu.com/git/ubuntu/ubuntu-
  
bionic.git/commit/debian.master/config/config.common.ubuntu?h=hwe=4b44b695fb5ee2f405d0ad4eda2fc2cad856414c
  for the relevant config changes in the Ubuntu kernel from Seth.

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

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

[Kernel-packages] [Bug 1866909] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From naynj...@ibm.com 2020-03-27 11:57 EDT---
Ok. Thanks for sharing the info.

These ones should be very straightforward to backport.

Thanks & Regards,
- Nayna

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

Title:
  Ubuntu Kernel Support for OpenPOWER NV Secure & Trusted Boot

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  == Comment: #0 - George C. Wilson  - 2020-02-25 18:40:44 
==
  - sysfs enablement: TBD
  - ima: arch specific policy support 6191706246de
  - platform keyring changes for powerpc: TBD
  - Appended signatures support for IMA appraisal 
39b07096364a42c516415d5f841069e885234e61
  - integrity: Define a trusted platform keyring: 9dc92c45177a
  - ima: Support platform keyring for kernel appraisal: d7cecb676dd3
  - TPM 2.0 Multibank extend support: c1f92b4b04ad
  - TPM 2.0 Eventlog support: 4d23cc323cdb
  - ima: carry the measurement list across kexec: d68a6fe9fccf
  - kexec_file_load system call support: 500c7ab1a9db

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

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

[Kernel-packages] [Bug 1869235] Lspci.txt

[araemo]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1869235/+attachment/5342186/+files/Lspci.txt

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

Title:
  Ryzen 3rd gen (3900X) ECC support missing from kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu server:
  Description:Ubuntu 19.10
  Release:19.10
  Installed kernel:
  linux-generic:
Installed: 5.3.0.42.36
  (I could not figure out what package to select in the 'in what package did 
you find this bug' chooser)

  Expected behavior: ECC RAM is detected and utilized
  Result instead:
  Error in dmesg at boot:
  EDAC amd64: Error: F0 not found, device 0x1460 (broken BIOS?) (more in the 
attached KernelErrors.log)

  Kernel 5.3 is missing ECC support for some families of AMD Ryzen 3rd
  gen CPUs.

  Support is added via these two commits in the mainline tree:
  
https://github.com/torvalds/linux/commit/e53a3b267fb0a79db9ca1f1e08b97889b22013e6
  
https://github.com/torvalds/linux/commit/3e443eb353eda6f4b4796e07f2599683fa752f1d

  The second commit actually adds the missing support, but it relies on
  the first commit: a partial refactor of the AMD ECC code.

  I tested myself, followed the instructions at 
https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel to build my own kernel, 
cherry-picked the two above commits, and have working ECC support on my 
self-built kernel:
  Linux smaug 5.3.0-43-generic #36 SMP Sat Mar 21 02:33:30 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux:

  EDAC MC: Ver: 3.0.0
  EDAC amd64: Node 0: DRAM ECC enabled.
  EDAC amd64: F17h_M70h detected (node 0).
  EDAC MC: UMC0 chip selects:
  EDAC amd64: MC: 0: 0MB 1: 0MB
  EDAC amd64: MC: 2: 16384MB 3: 16384MB
  EDAC MC: UMC1 chip selects:
  EDAC amd64: MC: 0: 0MB 1: 0MB
  EDAC amd64: MC: 2: 16384MB 3: 16384MB
  EDAC amd64: using x16 syndromes.
  EDAC amd64: MCT channel count: 2
  EDAC MC0: Giving out device to module amd64_edac controller F17h_M70h: DEV 
:00:18.3 (INTERRUPT)
  EDAC PCI0: Giving out device to module amd64_edac controller EDAC PCI 
controller: DEV :00:18.0 (POLLED)
  AMD64 EDAC driver v3.5.0

  
  If this could be included in a future hardware support kernel release, that 
would be very helpful.  I am unsure what the policy is for including this kind 
of backport in non-LTS kernels, though I know the LTS releases have hardware 
support updates that include this type of fix.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-03-20 (6 days ago)
  InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=89cfcc61-dbca-43d3-9a2e-5961df9ae5b4 ro
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  RfKill:
   
  Tags:  eoan uec-images
  Uname: Linux 5.3.0-42-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lxd plugdev sudo
  _MarkForUpload: False
  dmi.bios.date: 10/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.30
  dmi.board.name: X470D4U2-2T
  dmi.board.vendor: ASRockRack
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.30:bd10/03/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRockRack:rnX470D4U2-2T:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1869235] UdevDb.txt

[araemo]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1869235/+attachment/5342192/+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/1869235

Title:
  Ryzen 3rd gen (3900X) ECC support missing from kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu server:
  Description:Ubuntu 19.10
  Release:19.10
  Installed kernel:
  linux-generic:
Installed: 5.3.0.42.36
  (I could not figure out what package to select in the 'in what package did 
you find this bug' chooser)

  Expected behavior: ECC RAM is detected and utilized
  Result instead:
  Error in dmesg at boot:
  EDAC amd64: Error: F0 not found, device 0x1460 (broken BIOS?) (more in the 
attached KernelErrors.log)

  Kernel 5.3 is missing ECC support for some families of AMD Ryzen 3rd
  gen CPUs.

  Support is added via these two commits in the mainline tree:
  
https://github.com/torvalds/linux/commit/e53a3b267fb0a79db9ca1f1e08b97889b22013e6
  
https://github.com/torvalds/linux/commit/3e443eb353eda6f4b4796e07f2599683fa752f1d

  The second commit actually adds the missing support, but it relies on
  the first commit: a partial refactor of the AMD ECC code.

  I tested myself, followed the instructions at 
https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel to build my own kernel, 
cherry-picked the two above commits, and have working ECC support on my 
self-built kernel:
  Linux smaug 5.3.0-43-generic #36 SMP Sat Mar 21 02:33:30 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux:

  EDAC MC: Ver: 3.0.0
  EDAC amd64: Node 0: DRAM ECC enabled.
  EDAC amd64: F17h_M70h detected (node 0).
  EDAC MC: UMC0 chip selects:
  EDAC amd64: MC: 0: 0MB 1: 0MB
  EDAC amd64: MC: 2: 16384MB 3: 16384MB
  EDAC MC: UMC1 chip selects:
  EDAC amd64: MC: 0: 0MB 1: 0MB
  EDAC amd64: MC: 2: 16384MB 3: 16384MB
  EDAC amd64: using x16 syndromes.
  EDAC amd64: MCT channel count: 2
  EDAC MC0: Giving out device to module amd64_edac controller F17h_M70h: DEV 
:00:18.3 (INTERRUPT)
  EDAC PCI0: Giving out device to module amd64_edac controller EDAC PCI 
controller: DEV :00:18.0 (POLLED)
  AMD64 EDAC driver v3.5.0

  
  If this could be included in a future hardware support kernel release, that 
would be very helpful.  I am unsure what the policy is for including this kind 
of backport in non-LTS kernels, though I know the LTS releases have hardware 
support updates that include this type of fix.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-03-20 (6 days ago)
  InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=89cfcc61-dbca-43d3-9a2e-5961df9ae5b4 ro
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  RfKill:
   
  Tags:  eoan uec-images
  Uname: Linux 5.3.0-42-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lxd plugdev sudo
  _MarkForUpload: False
  dmi.bios.date: 10/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.30
  dmi.board.name: X470D4U2-2T
  dmi.board.vendor: ASRockRack
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.30:bd10/03/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRockRack:rnX470D4U2-2T:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1869235] PulseList.txt

[araemo]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1869235/+attachment/5342191/+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/1869235

Title:
  Ryzen 3rd gen (3900X) ECC support missing from kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu server:
  Description:Ubuntu 19.10
  Release:19.10
  Installed kernel:
  linux-generic:
Installed: 5.3.0.42.36
  (I could not figure out what package to select in the 'in what package did 
you find this bug' chooser)

  Expected behavior: ECC RAM is detected and utilized
  Result instead:
  Error in dmesg at boot:
  EDAC amd64: Error: F0 not found, device 0x1460 (broken BIOS?) (more in the 
attached KernelErrors.log)

  Kernel 5.3 is missing ECC support for some families of AMD Ryzen 3rd
  gen CPUs.

  Support is added via these two commits in the mainline tree:
  
https://github.com/torvalds/linux/commit/e53a3b267fb0a79db9ca1f1e08b97889b22013e6
  
https://github.com/torvalds/linux/commit/3e443eb353eda6f4b4796e07f2599683fa752f1d

  The second commit actually adds the missing support, but it relies on
  the first commit: a partial refactor of the AMD ECC code.

  I tested myself, followed the instructions at 
https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel to build my own kernel, 
cherry-picked the two above commits, and have working ECC support on my 
self-built kernel:
  Linux smaug 5.3.0-43-generic #36 SMP Sat Mar 21 02:33:30 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux:

  EDAC MC: Ver: 3.0.0
  EDAC amd64: Node 0: DRAM ECC enabled.
  EDAC amd64: F17h_M70h detected (node 0).
  EDAC MC: UMC0 chip selects:
  EDAC amd64: MC: 0: 0MB 1: 0MB
  EDAC amd64: MC: 2: 16384MB 3: 16384MB
  EDAC MC: UMC1 chip selects:
  EDAC amd64: MC: 0: 0MB 1: 0MB
  EDAC amd64: MC: 2: 16384MB 3: 16384MB
  EDAC amd64: using x16 syndromes.
  EDAC amd64: MCT channel count: 2
  EDAC MC0: Giving out device to module amd64_edac controller F17h_M70h: DEV 
:00:18.3 (INTERRUPT)
  EDAC PCI0: Giving out device to module amd64_edac controller EDAC PCI 
controller: DEV :00:18.0 (POLLED)
  AMD64 EDAC driver v3.5.0

  
  If this could be included in a future hardware support kernel release, that 
would be very helpful.  I am unsure what the policy is for including this kind 
of backport in non-LTS kernels, though I know the LTS releases have hardware 
support updates that include this type of fix.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-03-20 (6 days ago)
  InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=89cfcc61-dbca-43d3-9a2e-5961df9ae5b4 ro
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  RfKill:
   
  Tags:  eoan uec-images
  Uname: Linux 5.3.0-42-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lxd plugdev sudo
  _MarkForUpload: False
  dmi.bios.date: 10/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.30
  dmi.board.name: X470D4U2-2T
  dmi.board.vendor: ASRockRack
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.30:bd10/03/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRockRack:rnX470D4U2-2T:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1869235] ProcCpuinfoMinimal.txt

[araemo]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1869235/+attachment/5342188/+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/1869235

Title:
  Ryzen 3rd gen (3900X) ECC support missing from kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu server:
  Description:Ubuntu 19.10
  Release:19.10
  Installed kernel:
  linux-generic:
Installed: 5.3.0.42.36
  (I could not figure out what package to select in the 'in what package did 
you find this bug' chooser)

  Expected behavior: ECC RAM is detected and utilized
  Result instead:
  Error in dmesg at boot:
  EDAC amd64: Error: F0 not found, device 0x1460 (broken BIOS?) (more in the 
attached KernelErrors.log)

  Kernel 5.3 is missing ECC support for some families of AMD Ryzen 3rd
  gen CPUs.

  Support is added via these two commits in the mainline tree:
  
https://github.com/torvalds/linux/commit/e53a3b267fb0a79db9ca1f1e08b97889b22013e6
  
https://github.com/torvalds/linux/commit/3e443eb353eda6f4b4796e07f2599683fa752f1d

  The second commit actually adds the missing support, but it relies on
  the first commit: a partial refactor of the AMD ECC code.

  I tested myself, followed the instructions at 
https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel to build my own kernel, 
cherry-picked the two above commits, and have working ECC support on my 
self-built kernel:
  Linux smaug 5.3.0-43-generic #36 SMP Sat Mar 21 02:33:30 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux:

  EDAC MC: Ver: 3.0.0
  EDAC amd64: Node 0: DRAM ECC enabled.
  EDAC amd64: F17h_M70h detected (node 0).
  EDAC MC: UMC0 chip selects:
  EDAC amd64: MC: 0: 0MB 1: 0MB
  EDAC amd64: MC: 2: 16384MB 3: 16384MB
  EDAC MC: UMC1 chip selects:
  EDAC amd64: MC: 0: 0MB 1: 0MB
  EDAC amd64: MC: 2: 16384MB 3: 16384MB
  EDAC amd64: using x16 syndromes.
  EDAC amd64: MCT channel count: 2
  EDAC MC0: Giving out device to module amd64_edac controller F17h_M70h: DEV 
:00:18.3 (INTERRUPT)
  EDAC PCI0: Giving out device to module amd64_edac controller EDAC PCI 
controller: DEV :00:18.0 (POLLED)
  AMD64 EDAC driver v3.5.0

  
  If this could be included in a future hardware support kernel release, that 
would be very helpful.  I am unsure what the policy is for including this kind 
of backport in non-LTS kernels, though I know the LTS releases have hardware 
support updates that include this type of fix.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-03-20 (6 days ago)
  InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=89cfcc61-dbca-43d3-9a2e-5961df9ae5b4 ro
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  RfKill:
   
  Tags:  eoan uec-images
  Uname: Linux 5.3.0-42-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lxd plugdev sudo
  _MarkForUpload: False
  dmi.bios.date: 10/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.30
  dmi.board.name: X470D4U2-2T
  dmi.board.vendor: ASRockRack
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.30:bd10/03/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRockRack:rnX470D4U2-2T:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1869235] CurrentDmesg.txt

[araemo]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1869235/+attachment/5342184/+files/CurrentDmesg.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/1869235

Title:
  Ryzen 3rd gen (3900X) ECC support missing from kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu server:
  Description:Ubuntu 19.10
  Release:19.10
  Installed kernel:
  linux-generic:
Installed: 5.3.0.42.36
  (I could not figure out what package to select in the 'in what package did 
you find this bug' chooser)

  Expected behavior: ECC RAM is detected and utilized
  Result instead:
  Error in dmesg at boot:
  EDAC amd64: Error: F0 not found, device 0x1460 (broken BIOS?) (more in the 
attached KernelErrors.log)

  Kernel 5.3 is missing ECC support for some families of AMD Ryzen 3rd
  gen CPUs.

  Support is added via these two commits in the mainline tree:
  
https://github.com/torvalds/linux/commit/e53a3b267fb0a79db9ca1f1e08b97889b22013e6
  
https://github.com/torvalds/linux/commit/3e443eb353eda6f4b4796e07f2599683fa752f1d

  The second commit actually adds the missing support, but it relies on
  the first commit: a partial refactor of the AMD ECC code.

  I tested myself, followed the instructions at 
https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel to build my own kernel, 
cherry-picked the two above commits, and have working ECC support on my 
self-built kernel:
  Linux smaug 5.3.0-43-generic #36 SMP Sat Mar 21 02:33:30 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux:

  EDAC MC: Ver: 3.0.0
  EDAC amd64: Node 0: DRAM ECC enabled.
  EDAC amd64: F17h_M70h detected (node 0).
  EDAC MC: UMC0 chip selects:
  EDAC amd64: MC: 0: 0MB 1: 0MB
  EDAC amd64: MC: 2: 16384MB 3: 16384MB
  EDAC MC: UMC1 chip selects:
  EDAC amd64: MC: 0: 0MB 1: 0MB
  EDAC amd64: MC: 2: 16384MB 3: 16384MB
  EDAC amd64: using x16 syndromes.
  EDAC amd64: MCT channel count: 2
  EDAC MC0: Giving out device to module amd64_edac controller F17h_M70h: DEV 
:00:18.3 (INTERRUPT)
  EDAC PCI0: Giving out device to module amd64_edac controller EDAC PCI 
controller: DEV :00:18.0 (POLLED)
  AMD64 EDAC driver v3.5.0

  
  If this could be included in a future hardware support kernel release, that 
would be very helpful.  I am unsure what the policy is for including this kind 
of backport in non-LTS kernels, though I know the LTS releases have hardware 
support updates that include this type of fix.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-03-20 (6 days ago)
  InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=89cfcc61-dbca-43d3-9a2e-5961df9ae5b4 ro
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  RfKill:
   
  Tags:  eoan uec-images
  Uname: Linux 5.3.0-42-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lxd plugdev sudo
  _MarkForUpload: False
  dmi.bios.date: 10/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.30
  dmi.board.name: X470D4U2-2T
  dmi.board.vendor: ASRockRack
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.30:bd10/03/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRockRack:rnX470D4U2-2T:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1869235] WifiSyslog.txt

[araemo]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1869235/+attachment/5342193/+files/WifiSyslog.txt

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

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

Title:
  Ryzen 3rd gen (3900X) ECC support missing from kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu server:
  Description:Ubuntu 19.10
  Release:19.10
  Installed kernel:
  linux-generic:
Installed: 5.3.0.42.36
  (I could not figure out what package to select in the 'in what package did 
you find this bug' chooser)

  Expected behavior: ECC RAM is detected and utilized
  Result instead:
  Error in dmesg at boot:
  EDAC amd64: Error: F0 not found, device 0x1460 (broken BIOS?) (more in the 
attached KernelErrors.log)

  Kernel 5.3 is missing ECC support for some families of AMD Ryzen 3rd
  gen CPUs.

  Support is added via these two commits in the mainline tree:
  
https://github.com/torvalds/linux/commit/e53a3b267fb0a79db9ca1f1e08b97889b22013e6
  
https://github.com/torvalds/linux/commit/3e443eb353eda6f4b4796e07f2599683fa752f1d

  The second commit actually adds the missing support, but it relies on
  the first commit: a partial refactor of the AMD ECC code.

  I tested myself, followed the instructions at 
https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel to build my own kernel, 
cherry-picked the two above commits, and have working ECC support on my 
self-built kernel:
  Linux smaug 5.3.0-43-generic #36 SMP Sat Mar 21 02:33:30 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux:

  EDAC MC: Ver: 3.0.0
  EDAC amd64: Node 0: DRAM ECC enabled.
  EDAC amd64: F17h_M70h detected (node 0).
  EDAC MC: UMC0 chip selects:
  EDAC amd64: MC: 0: 0MB 1: 0MB
  EDAC amd64: MC: 2: 16384MB 3: 16384MB
  EDAC MC: UMC1 chip selects:
  EDAC amd64: MC: 0: 0MB 1: 0MB
  EDAC amd64: MC: 2: 16384MB 3: 16384MB
  EDAC amd64: using x16 syndromes.
  EDAC amd64: MCT channel count: 2
  EDAC MC0: Giving out device to module amd64_edac controller F17h_M70h: DEV 
:00:18.3 (INTERRUPT)
  EDAC PCI0: Giving out device to module amd64_edac controller EDAC PCI 
controller: DEV :00:18.0 (POLLED)
  AMD64 EDAC driver v3.5.0

  
  If this could be included in a future hardware support kernel release, that 
would be very helpful.  I am unsure what the policy is for including this kind 
of backport in non-LTS kernels, though I know the LTS releases have hardware 
support updates that include this type of fix.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-03-20 (6 days ago)
  InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=89cfcc61-dbca-43d3-9a2e-5961df9ae5b4 ro
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  RfKill:
   
  Tags:  eoan uec-images
  Uname: Linux 5.3.0-42-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lxd plugdev sudo
  _MarkForUpload: False
  dmi.bios.date: 10/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.30
  dmi.board.name: X470D4U2-2T
  dmi.board.vendor: ASRockRack
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.30:bd10/03/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRockRack:rnX470D4U2-2T:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1869235] ProcInterrupts.txt

[araemo]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1869235/+attachment/5342189/+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/1869235

Title:
  Ryzen 3rd gen (3900X) ECC support missing from kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu server:
  Description:Ubuntu 19.10
  Release:19.10
  Installed kernel:
  linux-generic:
Installed: 5.3.0.42.36
  (I could not figure out what package to select in the 'in what package did 
you find this bug' chooser)

  Expected behavior: ECC RAM is detected and utilized
  Result instead:
  Error in dmesg at boot:
  EDAC amd64: Error: F0 not found, device 0x1460 (broken BIOS?) (more in the 
attached KernelErrors.log)

  Kernel 5.3 is missing ECC support for some families of AMD Ryzen 3rd
  gen CPUs.

  Support is added via these two commits in the mainline tree:
  
https://github.com/torvalds/linux/commit/e53a3b267fb0a79db9ca1f1e08b97889b22013e6
  
https://github.com/torvalds/linux/commit/3e443eb353eda6f4b4796e07f2599683fa752f1d

  The second commit actually adds the missing support, but it relies on
  the first commit: a partial refactor of the AMD ECC code.

  I tested myself, followed the instructions at 
https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel to build my own kernel, 
cherry-picked the two above commits, and have working ECC support on my 
self-built kernel:
  Linux smaug 5.3.0-43-generic #36 SMP Sat Mar 21 02:33:30 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux:

  EDAC MC: Ver: 3.0.0
  EDAC amd64: Node 0: DRAM ECC enabled.
  EDAC amd64: F17h_M70h detected (node 0).
  EDAC MC: UMC0 chip selects:
  EDAC amd64: MC: 0: 0MB 1: 0MB
  EDAC amd64: MC: 2: 16384MB 3: 16384MB
  EDAC MC: UMC1 chip selects:
  EDAC amd64: MC: 0: 0MB 1: 0MB
  EDAC amd64: MC: 2: 16384MB 3: 16384MB
  EDAC amd64: using x16 syndromes.
  EDAC amd64: MCT channel count: 2
  EDAC MC0: Giving out device to module amd64_edac controller F17h_M70h: DEV 
:00:18.3 (INTERRUPT)
  EDAC PCI0: Giving out device to module amd64_edac controller EDAC PCI 
controller: DEV :00:18.0 (POLLED)
  AMD64 EDAC driver v3.5.0

  
  If this could be included in a future hardware support kernel release, that 
would be very helpful.  I am unsure what the policy is for including this kind 
of backport in non-LTS kernels, though I know the LTS releases have hardware 
support updates that include this type of fix.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-03-20 (6 days ago)
  InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=89cfcc61-dbca-43d3-9a2e-5961df9ae5b4 ro
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  RfKill:
   
  Tags:  eoan uec-images
  Uname: Linux 5.3.0-42-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lxd plugdev sudo
  _MarkForUpload: False
  dmi.bios.date: 10/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.30
  dmi.board.name: X470D4U2-2T
  dmi.board.vendor: ASRockRack
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.30:bd10/03/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRockRack:rnX470D4U2-2T:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1869235] CRDA.txt

[araemo]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1869235/+attachment/5342183/+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/1869235

Title:
  Ryzen 3rd gen (3900X) ECC support missing from kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu server:
  Description:Ubuntu 19.10
  Release:19.10
  Installed kernel:
  linux-generic:
Installed: 5.3.0.42.36
  (I could not figure out what package to select in the 'in what package did 
you find this bug' chooser)

  Expected behavior: ECC RAM is detected and utilized
  Result instead:
  Error in dmesg at boot:
  EDAC amd64: Error: F0 not found, device 0x1460 (broken BIOS?) (more in the 
attached KernelErrors.log)

  Kernel 5.3 is missing ECC support for some families of AMD Ryzen 3rd
  gen CPUs.

  Support is added via these two commits in the mainline tree:
  
https://github.com/torvalds/linux/commit/e53a3b267fb0a79db9ca1f1e08b97889b22013e6
  
https://github.com/torvalds/linux/commit/3e443eb353eda6f4b4796e07f2599683fa752f1d

  The second commit actually adds the missing support, but it relies on
  the first commit: a partial refactor of the AMD ECC code.

  I tested myself, followed the instructions at 
https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel to build my own kernel, 
cherry-picked the two above commits, and have working ECC support on my 
self-built kernel:
  Linux smaug 5.3.0-43-generic #36 SMP Sat Mar 21 02:33:30 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux:

  EDAC MC: Ver: 3.0.0
  EDAC amd64: Node 0: DRAM ECC enabled.
  EDAC amd64: F17h_M70h detected (node 0).
  EDAC MC: UMC0 chip selects:
  EDAC amd64: MC: 0: 0MB 1: 0MB
  EDAC amd64: MC: 2: 16384MB 3: 16384MB
  EDAC MC: UMC1 chip selects:
  EDAC amd64: MC: 0: 0MB 1: 0MB
  EDAC amd64: MC: 2: 16384MB 3: 16384MB
  EDAC amd64: using x16 syndromes.
  EDAC amd64: MCT channel count: 2
  EDAC MC0: Giving out device to module amd64_edac controller F17h_M70h: DEV 
:00:18.3 (INTERRUPT)
  EDAC PCI0: Giving out device to module amd64_edac controller EDAC PCI 
controller: DEV :00:18.0 (POLLED)
  AMD64 EDAC driver v3.5.0

  
  If this could be included in a future hardware support kernel release, that 
would be very helpful.  I am unsure what the policy is for including this kind 
of backport in non-LTS kernels, though I know the LTS releases have hardware 
support updates that include this type of fix.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-03-20 (6 days ago)
  InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=89cfcc61-dbca-43d3-9a2e-5961df9ae5b4 ro
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  RfKill:
   
  Tags:  eoan uec-images
  Uname: Linux 5.3.0-42-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lxd plugdev sudo
  _MarkForUpload: False
  dmi.bios.date: 10/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.30
  dmi.board.name: X470D4U2-2T
  dmi.board.vendor: ASRockRack
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.30:bd10/03/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRockRack:rnX470D4U2-2T:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1869235] Lsusb.txt

[araemo]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1869235/+attachment/5342187/+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/1869235

Title:
  Ryzen 3rd gen (3900X) ECC support missing from kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu server:
  Description:Ubuntu 19.10
  Release:19.10
  Installed kernel:
  linux-generic:
Installed: 5.3.0.42.36
  (I could not figure out what package to select in the 'in what package did 
you find this bug' chooser)

  Expected behavior: ECC RAM is detected and utilized
  Result instead:
  Error in dmesg at boot:
  EDAC amd64: Error: F0 not found, device 0x1460 (broken BIOS?) (more in the 
attached KernelErrors.log)

  Kernel 5.3 is missing ECC support for some families of AMD Ryzen 3rd
  gen CPUs.

  Support is added via these two commits in the mainline tree:
  
https://github.com/torvalds/linux/commit/e53a3b267fb0a79db9ca1f1e08b97889b22013e6
  
https://github.com/torvalds/linux/commit/3e443eb353eda6f4b4796e07f2599683fa752f1d

  The second commit actually adds the missing support, but it relies on
  the first commit: a partial refactor of the AMD ECC code.

  I tested myself, followed the instructions at 
https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel to build my own kernel, 
cherry-picked the two above commits, and have working ECC support on my 
self-built kernel:
  Linux smaug 5.3.0-43-generic #36 SMP Sat Mar 21 02:33:30 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux:

  EDAC MC: Ver: 3.0.0
  EDAC amd64: Node 0: DRAM ECC enabled.
  EDAC amd64: F17h_M70h detected (node 0).
  EDAC MC: UMC0 chip selects:
  EDAC amd64: MC: 0: 0MB 1: 0MB
  EDAC amd64: MC: 2: 16384MB 3: 16384MB
  EDAC MC: UMC1 chip selects:
  EDAC amd64: MC: 0: 0MB 1: 0MB
  EDAC amd64: MC: 2: 16384MB 3: 16384MB
  EDAC amd64: using x16 syndromes.
  EDAC amd64: MCT channel count: 2
  EDAC MC0: Giving out device to module amd64_edac controller F17h_M70h: DEV 
:00:18.3 (INTERRUPT)
  EDAC PCI0: Giving out device to module amd64_edac controller EDAC PCI 
controller: DEV :00:18.0 (POLLED)
  AMD64 EDAC driver v3.5.0

  
  If this could be included in a future hardware support kernel release, that 
would be very helpful.  I am unsure what the policy is for including this kind 
of backport in non-LTS kernels, though I know the LTS releases have hardware 
support updates that include this type of fix.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-03-20 (6 days ago)
  InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=89cfcc61-dbca-43d3-9a2e-5961df9ae5b4 ro
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  RfKill:
   
  Tags:  eoan uec-images
  Uname: Linux 5.3.0-42-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lxd plugdev sudo
  _MarkForUpload: False
  dmi.bios.date: 10/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.30
  dmi.board.name: X470D4U2-2T
  dmi.board.vendor: ASRockRack
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.30:bd10/03/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRockRack:rnX470D4U2-2T:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1869180] Re: focal/linux-raspi2: Upstream raspberrypi patchset 2020-03-27

[Juerg Haefliger]

** Changed in: linux-raspi2 (Ubuntu Focal)
   Status: New => Fix Committed

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

Title:
  focal/linux-raspi2: Upstream raspberrypi patchset 2020-03-27

Status in linux-raspi2 package in Ubuntu:
  Fix Committed
Status in linux-raspi2 source package in Focal:
  Fix Committed

Bug description:
  Upstream raspberrypi patchset 2020-03-27

    Ported from the following raspberrypi branch:
  rpi-5.4.y
    from https://github.com/raspberrypi/linux.git

  drm/modes: parse_cmdline: Explicitly memset the passed in drm_cmdline_mode 
struct
  drm/modes: parse_cmdline: Remove some unnecessary code (v2)
  drm/modes: parse_cmdline: Add support for specifying panel_orientation (v2)
  drm/modes: parse_cmdline: Allow specifying stand-alone options
  drm/modes: parse_cmdline: Set bpp/refresh_specified after successful parsing
  drm/modes: parse_cmdline: Add freestanding argument to 
drm_mode_parse_cmdline_options()
  drm/modes: parse_cmdline: Rework drm_mode_parse_cmdline_options()
  drm/modes: parse_cmdline: Accept extras directly after mode combined with 
options
  drm/modes: parse_cmdline: Stop parsing extras after bpp / refresh at ', '
  drm/modes: parse_cmdline: Make various char pointers const
  drm/modes: parse_cmdline: Fix possible reference past end of string
  net: bcmgenet: Clear ID_MODE_DIS in EXT_RGMII_OOB_CTRL when not needed
  ARM: dts: bcm271x: Use a53 pmu, drop RPI364
  ARM: dts: bcm2711: Add 32-bit PMU compatibility
  Add support for merus-amp soundcard and ma120x0p codec
  gpio-ir-overlay: add parameter to configure signal polarity (#3490)
  drm/vc4: Add DRM_FORMAT_P030 support to firmware-kms
  drm/fourcc: Add packed 10bit YUV 4:2:0 format
  drm/vc4: fkms: Change crtc_state structure name to avoid conflict
  media: ov5647: change defaults to better match raw camera applications.
  media: ov5647: Add extra 10-bit sensor modes.
  media: ov5647: Add V4L2 controls for analogue gain, exposure and AWB
  media: ov5647: Add basic support for multiple sensor modes.
  media: ov5647: Fix return codes from ov5647_write/ov5647_read functions.
  Kbuild: Allow .dtbo overlays to be built, adjust.
  overlays: imx219: Correct link frequency to match the upstream driver
  media: i2c: Add driver for Sony IMX219 sensor
  media: dt-bindings: media: i2c: Add IMX219 CMOS sensor binding
  Revert "media: dt-bindings: Add binding for the Sony IMX219 sensor"
  Revert "media: i2c: Add driver for Sony IMX219 sensor"
  bcm2711-rpi.dtsi: Use upstream pcie node
  PCI: brcmstb: Fix build on 32bit ARM platforms with older compilers
  PCI: brcmstb: Add MSI support
  PCI: brcmstb: Add Broadcom STB PCIe host controller driver
  ARM: dts: bcm2711: Enable PCIe controller
  dma-mapping: treat dev->bus_dma_mask as a DMA limit
  dma-direct: exclude dma_direct_map_resource from the min_low_pfn check
  dma-direct: avoid a forward declaration for phys_to_dma
  dma-direct: unify the dma_capable definitions
  PCI: of: Add inbound resource parsing to helpers
  x86/PCI: sta2x11: use default DMA address translation
  dma-direct: check for overflows on 32 bit DMA addresses
  dma/direct: turn ARCH_ZONE_DMA_BITS into a variable
  resource: Add a resource_list_first_type helper
  mm: refresh ZONE_DMA and ZONE_DMA32 comments in 'enum zone_type'
  arm64: use both ZONE_DMA and ZONE_DMA32
  arm64: rename variables used to calculate ZONE_DMA32's size
  arm64: mm: use arm64_dma_phys_limit instead of calling max_zone_dma_phys()
  of: Make of_dma_get_range() work on bus nodes
  of/address: Translate 'dma-ranges' for parent nodes missing 'dma-ranges'
  of: Factor out #{addr,size}-cells parsing
  of: address: Follow DMA parent for "dma-coherent"
  of/address: Introduce of_get_next_dma_parent() helper
  Revert "dma-direct: check for overflows on 32 bit DMA addresses"
  Revert "arm64/mm: Limit the DMA zone for arm64"
  Revert "PCI: brcmstb: Add Broadcom STB PCIe host controller driver"
  Revert "PCI: brcmstb: Add dma-range mapping for inbound traffic"
  Revert "PCI: brcmstb: Add MSI capability"
  Revert "pcie-brcmstb: Changes for BCM2711"
  Revert "bcm2835-dma: Add proper 40-bit DMA support"
  Revert "bcm2835-dma: Correct SoC name"
  Revert "pcie-brcmstb: Don't set DMA ops for root complex"
  Revert "Ported pcie-brcmstb bounce buffer implementation to ARM64. (#3144)"
  Revert "pcie-brcmstb-bounce64.c: dev_err() -> dev_info() for info messages"
  Revert "pcie-brcmstb: Eliminate arch_dma_ops error message"
  Revert "pcie-brcmstb: Bounce buffer support is for BCM2711B0"
  Revert "pcie-brcmstb: Correct SoC name"
  Revert "ARM: dts: bcm283x: Restore simple-bus to /clocks"
  ARM: dts: bcm283x: Restore simple-bus to /clocks

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1869235] ProcModules.txt

[araemo]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1869235/+attachment/5342190/+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/1869235

Title:
  Ryzen 3rd gen (3900X) ECC support missing from kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu server:
  Description:Ubuntu 19.10
  Release:19.10
  Installed kernel:
  linux-generic:
Installed: 5.3.0.42.36
  (I could not figure out what package to select in the 'in what package did 
you find this bug' chooser)

  Expected behavior: ECC RAM is detected and utilized
  Result instead:
  Error in dmesg at boot:
  EDAC amd64: Error: F0 not found, device 0x1460 (broken BIOS?) (more in the 
attached KernelErrors.log)

  Kernel 5.3 is missing ECC support for some families of AMD Ryzen 3rd
  gen CPUs.

  Support is added via these two commits in the mainline tree:
  
https://github.com/torvalds/linux/commit/e53a3b267fb0a79db9ca1f1e08b97889b22013e6
  
https://github.com/torvalds/linux/commit/3e443eb353eda6f4b4796e07f2599683fa752f1d

  The second commit actually adds the missing support, but it relies on
  the first commit: a partial refactor of the AMD ECC code.

  I tested myself, followed the instructions at 
https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel to build my own kernel, 
cherry-picked the two above commits, and have working ECC support on my 
self-built kernel:
  Linux smaug 5.3.0-43-generic #36 SMP Sat Mar 21 02:33:30 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux:

  EDAC MC: Ver: 3.0.0
  EDAC amd64: Node 0: DRAM ECC enabled.
  EDAC amd64: F17h_M70h detected (node 0).
  EDAC MC: UMC0 chip selects:
  EDAC amd64: MC: 0: 0MB 1: 0MB
  EDAC amd64: MC: 2: 16384MB 3: 16384MB
  EDAC MC: UMC1 chip selects:
  EDAC amd64: MC: 0: 0MB 1: 0MB
  EDAC amd64: MC: 2: 16384MB 3: 16384MB
  EDAC amd64: using x16 syndromes.
  EDAC amd64: MCT channel count: 2
  EDAC MC0: Giving out device to module amd64_edac controller F17h_M70h: DEV 
:00:18.3 (INTERRUPT)
  EDAC PCI0: Giving out device to module amd64_edac controller EDAC PCI 
controller: DEV :00:18.0 (POLLED)
  AMD64 EDAC driver v3.5.0

  
  If this could be included in a future hardware support kernel release, that 
would be very helpful.  I am unsure what the policy is for including this kind 
of backport in non-LTS kernels, though I know the LTS releases have hardware 
support updates that include this type of fix.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-03-20 (6 days ago)
  InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=89cfcc61-dbca-43d3-9a2e-5961df9ae5b4 ro
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  RfKill:
   
  Tags:  eoan uec-images
  Uname: Linux 5.3.0-42-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lxd plugdev sudo
  _MarkForUpload: False
  dmi.bios.date: 10/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.30
  dmi.board.name: X470D4U2-2T
  dmi.board.vendor: ASRockRack
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.30:bd10/03/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRockRack:rnX470D4U2-2T:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1869235] IwConfig.txt

[araemo]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1869235/+attachment/5342185/+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/1869235

Title:
  Ryzen 3rd gen (3900X) ECC support missing from kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu server:
  Description:Ubuntu 19.10
  Release:19.10
  Installed kernel:
  linux-generic:
Installed: 5.3.0.42.36
  (I could not figure out what package to select in the 'in what package did 
you find this bug' chooser)

  Expected behavior: ECC RAM is detected and utilized
  Result instead:
  Error in dmesg at boot:
  EDAC amd64: Error: F0 not found, device 0x1460 (broken BIOS?) (more in the 
attached KernelErrors.log)

  Kernel 5.3 is missing ECC support for some families of AMD Ryzen 3rd
  gen CPUs.

  Support is added via these two commits in the mainline tree:
  
https://github.com/torvalds/linux/commit/e53a3b267fb0a79db9ca1f1e08b97889b22013e6
  
https://github.com/torvalds/linux/commit/3e443eb353eda6f4b4796e07f2599683fa752f1d

  The second commit actually adds the missing support, but it relies on
  the first commit: a partial refactor of the AMD ECC code.

  I tested myself, followed the instructions at 
https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel to build my own kernel, 
cherry-picked the two above commits, and have working ECC support on my 
self-built kernel:
  Linux smaug 5.3.0-43-generic #36 SMP Sat Mar 21 02:33:30 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux:

  EDAC MC: Ver: 3.0.0
  EDAC amd64: Node 0: DRAM ECC enabled.
  EDAC amd64: F17h_M70h detected (node 0).
  EDAC MC: UMC0 chip selects:
  EDAC amd64: MC: 0: 0MB 1: 0MB
  EDAC amd64: MC: 2: 16384MB 3: 16384MB
  EDAC MC: UMC1 chip selects:
  EDAC amd64: MC: 0: 0MB 1: 0MB
  EDAC amd64: MC: 2: 16384MB 3: 16384MB
  EDAC amd64: using x16 syndromes.
  EDAC amd64: MCT channel count: 2
  EDAC MC0: Giving out device to module amd64_edac controller F17h_M70h: DEV 
:00:18.3 (INTERRUPT)
  EDAC PCI0: Giving out device to module amd64_edac controller EDAC PCI 
controller: DEV :00:18.0 (POLLED)
  AMD64 EDAC driver v3.5.0

  
  If this could be included in a future hardware support kernel release, that 
would be very helpful.  I am unsure what the policy is for including this kind 
of backport in non-LTS kernels, though I know the LTS releases have hardware 
support updates that include this type of fix.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-03-20 (6 days ago)
  InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=89cfcc61-dbca-43d3-9a2e-5961df9ae5b4 ro
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  RfKill:
   
  Tags:  eoan uec-images
  Uname: Linux 5.3.0-42-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lxd plugdev sudo
  _MarkForUpload: False
  dmi.bios.date: 10/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.30
  dmi.board.name: X470D4U2-2T
  dmi.board.vendor: ASRockRack
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.30:bd10/03/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRockRack:rnX470D4U2-2T:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1869235] Re: Ryzen 3rd gen (3900X) ECC support missing from kernel

[araemo]

apport information

** Tags added: apport-collected uec-images

** Description changed:

  Ubuntu server:
  Description:Ubuntu 19.10
  Release:19.10
  Installed kernel:
  linux-generic:
Installed: 5.3.0.42.36
  (I could not figure out what package to select in the 'in what package did 
you find this bug' chooser)
  
  Expected behavior: ECC RAM is detected and utilized
  Result instead:
  Error in dmesg at boot:
  EDAC amd64: Error: F0 not found, device 0x1460 (broken BIOS?) (more in the 
attached KernelErrors.log)
  
  Kernel 5.3 is missing ECC support for some families of AMD Ryzen 3rd gen
  CPUs.
  
  Support is added via these two commits in the mainline tree:
  
https://github.com/torvalds/linux/commit/e53a3b267fb0a79db9ca1f1e08b97889b22013e6
  
https://github.com/torvalds/linux/commit/3e443eb353eda6f4b4796e07f2599683fa752f1d
  
  The second commit actually adds the missing support, but it relies on
  the first commit: a partial refactor of the AMD ECC code.
  
  I tested myself, followed the instructions at 
https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel to build my own kernel, 
cherry-picked the two above commits, and have working ECC support on my 
self-built kernel:
  Linux smaug 5.3.0-43-generic #36 SMP Sat Mar 21 02:33:30 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux:
  
  EDAC MC: Ver: 3.0.0
  EDAC amd64: Node 0: DRAM ECC enabled.
  EDAC amd64: F17h_M70h detected (node 0).
  EDAC MC: UMC0 chip selects:
  EDAC amd64: MC: 0: 0MB 1: 0MB
  EDAC amd64: MC: 2: 16384MB 3: 16384MB
  EDAC MC: UMC1 chip selects:
  EDAC amd64: MC: 0: 0MB 1: 0MB
  EDAC amd64: MC: 2: 16384MB 3: 16384MB
  EDAC amd64: using x16 syndromes.
  EDAC amd64: MCT channel count: 2
  EDAC MC0: Giving out device to module amd64_edac controller F17h_M70h: DEV 
:00:18.3 (INTERRUPT)
  EDAC PCI0: Giving out device to module amd64_edac controller EDAC PCI 
controller: DEV :00:18.0 (POLLED)
  AMD64 EDAC driver v3.5.0
  
  
  If this could be included in a future hardware support kernel release, that 
would be very helpful.  I am unsure what the policy is for including this kind 
of backport in non-LTS kernels, though I know the LTS releases have hardware 
support updates that include this type of fix.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu8.6
+ Architecture: amd64
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
+ CurrentDesktop: XFCE
+ DistroRelease: Ubuntu 19.10
+ InstallationDate: Installed on 2020-03-20 (6 days ago)
+ InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 
(20191017)
+ MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
+ NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=C.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 astdrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=89cfcc61-dbca-43d3-9a2e-5961df9ae5b4 ro
+ ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
+ RelatedPackageVersions:
+  linux-restricted-modules-5.3.0-42-generic N/A
+  linux-backports-modules-5.3.0-42-generic  N/A
+  linux-firmware1.183.4
+ RfKill:
+  
+ Tags:  eoan uec-images
+ Uname: Linux 5.3.0-42-generic x86_64
+ UnreportableReason: This report is about a package that is not installed.
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip libvirt lxd plugdev sudo
+ _MarkForUpload: False
+ dmi.bios.date: 10/03/2019
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: P3.30
+ dmi.board.name: X470D4U2-2T
+ dmi.board.vendor: ASRockRack
+ dmi.chassis.asset.tag: To Be Filled By O.E.M.
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: To Be Filled By O.E.M.
+ dmi.chassis.version: To Be Filled By O.E.M.
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.30:bd10/03/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRockRack:rnX470D4U2-2T:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
+ dmi.product.family: To Be Filled By O.E.M.
+ dmi.product.name: To Be Filled By O.E.M.
+ dmi.product.sku: To Be Filled By O.E.M.
+ dmi.product.version: To Be Filled By O.E.M.
+ dmi.sys.vendor: To Be Filled By O.E.M.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1869235/+attachment/5342182/+files/AlsaInfo.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/1869235

Title:
  Ryzen 3rd gen (3900X) ECC support missing from kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu server:
  Description:Ubuntu 19.10
  Release:19.10
  Installed kernel:
  linux-generic:
Installed: 5.3.0.42.36
  (I could not figure out what package to select in the 'in what package did 
you find this bug' chooser)

  Expected 

[Kernel-packages] [Bug 1778087] Re: ELAN1200 touchpad jumps around and disconnects

[Alistair Sutter]

This bug is back and I'm getting a bunch of emails related to it. Re-
opening because the bug is back in upstream. It was fixed in kernel
5.2.5 for me but I'm getting reports of it being back in 5.3.0 and
5.5.13.

** Changed in: linux (Ubuntu)
   Status: Fix Released => 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/1778087

Title:
  ELAN1200 touchpad jumps around and disconnects

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is on an ASUS GL503VD laptop and would probably affect other ASUS
  laptops equipped with the ELAN1200 touchpad.

  I am on Kernel 4.17.2 because older kernels did not enable the
  touchpad at all(It was just unrecognized or i2c-hid stopped the
  computer from booting)

  The touchpad works but it has erratic behaviour and disconnects
  randomly. After it disconnects the only way to bring it back is to
  `modprobe -r hid-multitouch && modprobe hid-multitouch`

  Libinput and synaptics can handle the touchpad though I found
  synaptics to be more stable.

  dmesg gets spammed with this whenever I move the touchpad:
  [timestamp] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report 
(16/65535)

  I tried to compile: https://github.com/mishurov/linux_elan1200_touchpad
  Because from what I understand the "jumpy/disconnect" problem is associated 
to the incomplete reports and Mishurov managed to mitigate those. Unfortunately 
some symbols were deprecated in kernel 4.17.2 and it did not compile for my 
system.

  While I can use my touchpad as is right now, and "restart" it with
  modprobe when needed, it would be nice to have it function bug-free.
  (Right after I typed this my touchpad disconnected and I needed to
  modprobe again, I am considering making a cronjob for that)

  Let me know if anything else is needed. Will wait for an apport collection to 
add log files.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-10 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  Tags:  bionic
  Uname: Linux 4.17.2 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1852608] Re: ZFS Severe Performance issue due to poorly supported feature

[Colin Ian King]

Refer to the following comment:

https://github.com/openzfs/zfs/issues/9584#issuecomment-554725253

Probably won't disable this feature.

** Bug watch added: github.com/openzfs/zfs/issues #9584
   https://github.com/openzfs/zfs/issues/9584

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

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

Title:
  ZFS Severe Performance issue due to poorly supported feature

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

Bug description:
  I installed ZFS using the 19.10 installer and ran into some severe
  load caused by /etc/zfs/zed.d/history_event-zfs-list-cacher.sh

  Microk8s, due to the way containerd manages container filesystems,
  causes numerous zevents and can easily overwhelm the above script.

  I filed a ticket and partial fix to ZOL team, however in response
  Richard Elling recommended not using that feature.

  * "it is not core to zfs operation, it is an attempt at optimization that few 
people know about, and even fewer use"
  * "zed is allowed to drop events under load, so it might not be called and 
therefore the cache cannot be authoritative"

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

  
  I'm providing this feedback to you so you can make changes to the Ubuntu 
installer to not enable this zfs feature.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: zfs-zed 0.8.1-1ubuntu14 [modified: 
usr/lib/zfs-linux/zed.d/history_event-zfs-list-cacher.sh]
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Nov 14 10:51:49 2019
  InstallationDate: Installed on 2019-10-31 (13 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1865130] Re: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!

[knossos456]

And please post before AND after revert to linux-firmware_1.173.12_all.deb
dmesg | grep UVD

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

Title:
  [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to
  reset the VCPU!!!

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux-firmware source package in Eoan:
  Fix Committed

Bug description:
  === SRU Justification ===
  [Impact] 
  Firmware update of radeon/oland_rlc.bin breaks some radeon cards.

  [Fix]
  Revert the new firmware.

  [Regression Potential]
  Low. The old firmware has been used for a long time.

  === Original Bug Report ===

  when trying > DRI_PRIME=1 glxgears , the result in dmesg is as
  following

  [  +0.91] radeon :01:00.0: WB enabled
  [  +0.02] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x8c00 and cpu addr 0x8ac2d26f
  [  +0.01] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x8c04 and cpu addr 0xa848de20
  [  +0.01] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x8c08 and cpu addr 0x1e4494a9
  [  +0.01] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x8c0c and cpu addr 0x98a9748e
  [  +0.01] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x8c10 and cpu addr 0xb6ff734d
  [  +0.000212] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0x6b4da526
  [  +0.100566] radeon :01:00.0: failed VCE resume (-110).
  [  +0.179115] [drm] ring test on 0 succeeded in 1 usecs
  [  +0.04] [drm] ring test on 1 succeeded in 1 usecs
  [  +0.04] [drm] ring test on 2 succeeded in 1 usecs
  [  +0.06] [drm] ring test on 3 succeeded in 3 usecs
  [  +0.04] [drm] ring test on 4 succeeded in 3 usecs
  [  +1.171892] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015643] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015509] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015572] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015514] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015405] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015442] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015416] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015388] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015379] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +0.019924] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
giving up!!!
  [  +0.40] radeon :01:00.0: failed initializing UVD (-1).
  [  +0.60] [drm] ib test on ring 0 succeeded in 0 usecs
  [  +0.51] [drm] ib test on ring 1 succeeded in 0 usecs
  [  +0.32] [drm] ib test on ring 2 succeeded in 0 usecs
  [  +0.52] [drm] ib test on ring 3 succeeded in 0 usecs
  [  +0.29] [drm] ib test on ring 4 succeeded in 0 usecs

  Also it affects the boot time.

  the used OpenGL renderer is:
  "OpenGL renderer string: AMD OLAND (DRM 2.50.0, 5.3.0-40-generic, LLVM 9.0.0)"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Fri Feb 28 11:50:50 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.3.0-28-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.3.0-40-generic, x86_64: installed
   virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed
   virtualbox, 5.2.34, 5.3.0-40-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:3801]
     Subsystem: Lenovo Mars [Radeon HD 8670A/8670M/8750M] [17aa:3801]
  InstallationDate: Installed on 2019-09-17 (163 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: LENOVO 20238
  

[Kernel-packages] [Bug 1865017] Re: focal/linux-raspi2: 5.4.0-1004.4 -proposed tracker

[Juerg Haefliger]

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

** This bug is no longer a duplicate of bug 1868339
   focal/linux-raspi2:  -proposed tracker
** This bug has been marked a duplicate of bug 1869383
   focal/linux-raspi:  -proposed tracker

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

Title:
  focal/linux-raspi2: 5.4.0-1004.4 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Fix Released
Status in linux-raspi2 source package in Focal:
  Fix Released

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1865025
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Holding before Promote to Release
  phase-changed: Thursday, 05. March 2020 17:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-release: Holding -- master bug not ready for release
  trackers:
focal/linux-raspi2/pi-kernel: bug 1865031
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865017/+subscriptions

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

[Kernel-packages] [Bug 1857398] Re: ubiquity should support encryption by default with zfsroot, with users able to opt in to running change-key after install

[Colin Ian King]

Backporting that commit is rather non-trivial as it has some other
change dependencies and it's quite a large change for the normal SRU
process.

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

Title:
  ubiquity should support encryption by default with zfsroot, with users
  able to opt in to running change-key after install

Status in ubiquity package in Ubuntu:
  New
Status in zfs-linux package in Ubuntu:
  New

Bug description:
  zfs supports built-in encryption support, but the decision of whether
  a pool is encrypted or not must be made at pool creation time; it is
  possible to add encrypted datasets on top of an unencrypted pool but
  it is not possible to do an online change of a dataset (or a whole
  pool) to toggle encryption.

  We should therefore always install with encryption enabled on zfs
  systems, with a non-secret key by default, and allow the user to use
  'zfs change-key -o keylocation=prompt' after install to take ownership
  of the encryption and upgrade the security.

  This is also the simplest way to allow users to avoid having to choose
  between the security of full-disk encryption, and the advanced
  filesystem features of zfs since it requires no additional UX work in
  ubiquity.

  We should make sure that
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857040 is fixed
  first in the kernel so that enabling zfs encryption does not impose an
  unreasonable performance penalty.

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

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

[Kernel-packages] [Bug 1861350] Re: focal/linux-raspi2-5.4: -proposed tracker

[Juerg Haefliger]

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

** This bug is no longer a duplicate of bug 1868339
   focal/linux-raspi2:  -proposed tracker
** This bug has been marked a duplicate of bug 1869383
   focal/linux-raspi:  -proposed tracker

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

Title:
  focal/linux-raspi2-5.4:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  kernel-stable-master-bug: 1861352
  packages:
main: linux-raspi2-5.4
meta: linux-meta-raspi2-5.4
  phase: Ready for Packaging
  phase-changed: Friday, 31. January 2020 04:42 UTC
  reason:
prepare-package: Pending -- version not specified
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861350/+subscriptions

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

[Kernel-packages] [Bug 1864078] Re: focal/linux-raspi2: 5.4.0-1003.3 -proposed tracker

[Juerg Haefliger]

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

** This bug is no longer a duplicate of bug 1868339
   focal/linux-raspi2:  -proposed tracker
** This bug has been marked a duplicate of bug 1869383
   focal/linux-raspi:  -proposed tracker

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

Title:
  focal/linux-raspi2: 5.4.0-1003.3 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Fix Released
Status in linux-raspi2 source package in Focal:
  Fix Released

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1864085
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Ready for Promote to Proposed
  phase-changed: Monday, 24. February 2020 12:52 UTC
  reason:
promote-to-proposed: Stalled -- ready for review
  trackers:
focal/linux-raspi2/pi-kernel: bug 1864502
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1864078/+subscriptions

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

[Kernel-packages] [Bug 1867007] Re: zfs-initramfs fails with multiple rpool on separate disks

[Kevin Menard]

** Description changed:

  == Test Case ==
  1. On a multi disks setup, install Ubuntu with ZFS on disk 1
  2. Reboot and make sure everything works as expected
  3. Do a second installation and install Ubuntu with ZFS on disk 2
  4. Reboot
  
- * Expected Result * 
+ * Expected Result *
  GRUB should display all the machines available and let the user select which 
installation to boot
  
- * Actual result * 
+ * Actual result *
  - Only one machine is listed
  - initramfs crashes because there are several pool with the same name but 
different IDs and import the pools by name
  - Same problem in the systemd generator which will try to import all the 
rpools.
- 
  
  == Original Description ==
  
  I had an Ubuntu old installation that used a ZFS root, using the layout
  described in the ZFS on Linux docs. Consequently, the pool name for my
  Ubuntu installation was "rpool". I'm currently encountering an issue
  with that pool that only allows me to mount it read-only. So, I'd like
  to replicate the datasets from there to a new device.
  
  On the new device, I've set up a ZFS system using the Ubuntu 20.04 daily
  installer (March 9, 2020). This setup creates a new pool named "rpool".
  So, with both devices inserted, I have two distinct pools each named
  "rpool", one of which will kernel panic if I try to mount it read-write.
  
  ZFS is fine with having multiple pools with the same name. In these
  cases, you use `zfs import` with the pool's GUID and give it a distinct
  pool name on import. However, the grub config for booting from ZFS
  doesn't appear to handle multiple pools with the same rpool name very
  well. Rather than using the pool's GUID, it uses the name, and as such,
  it's unable to boot properly when another pool with the name "rpool" is
  attached to the system.
  
  I think it'd be better if the config were written in such a way that
  `update-grub` generated boot config bound to whatever pool it found at
  the time of its invocation, and not start searching through all pools
  dynamically upon boot. Just to be clear, I have an Ubuntu 20.04 system
  with a ZFS root that boots just fine. But, the moment I attach the old
  pool, also named "rpool", I'm no longer able to boot up my system even
  though I haven't removed the good pool and I haven't re-run `update-
- grub`. Instead of botoing, I'm thrown into the grub command line.
+ grub`. Instead of booting, I'm thrown into the grub command line.

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

Title:
  zfs-initramfs fails with multiple rpool on separate disks

Status in grub2 package in Ubuntu:
  Triaged
Status in zfs-linux package in Ubuntu:
  Triaged

Bug description:
  == Test Case ==
  1. On a multi disks setup, install Ubuntu with ZFS on disk 1
  2. Reboot and make sure everything works as expected
  3. Do a second installation and install Ubuntu with ZFS on disk 2
  4. Reboot

  * Expected Result *
  GRUB should display all the machines available and let the user select which 
installation to boot

  * Actual result *
  - Only one machine is listed
  - initramfs crashes because there are several pool with the same name but 
different IDs and import the pools by name
  - Same problem in the systemd generator which will try to import all the 
rpools.

  == Original Description ==

  I had an Ubuntu old installation that used a ZFS root, using the
  layout described in the ZFS on Linux docs. Consequently, the pool name
  for my Ubuntu installation was "rpool". I'm currently encountering an
  issue with that pool that only allows me to mount it read-only. So,
  I'd like to replicate the datasets from there to a new device.

  On the new device, I've set up a ZFS system using the Ubuntu 20.04
  daily installer (March 9, 2020). This setup creates a new pool named
  "rpool". So, with both devices inserted, I have two distinct pools
  each named "rpool", one of which will kernel panic if I try to mount
  it read-write.

  ZFS is fine with having multiple pools with the same name. In these
  cases, you use `zfs import` with the pool's GUID and give it a
  distinct pool name on import. However, the grub config for booting
  from ZFS doesn't appear to handle multiple pools with the same rpool
  name very well. Rather than using the pool's GUID, it uses the name,
  and as such, it's unable to boot properly when another pool with the
  name "rpool" is attached to the system.

  I think it'd be better if the config were written in such a way that
  `update-grub` generated boot config bound to whatever pool it found at
  the time of its invocation, and not start searching through all pools
  dynamically upon boot. Just to be clear, I have an Ubuntu 20.04 system
  with a ZFS root that boots just fine. But, the moment I attach the old
  pool, also named "rpool", I'm no longer able to boot up my system even
  though I haven't 

[Kernel-packages] [Bug 1866480] Re: focal/linux-raspi2: 5.4.0-1005.5 -proposed tracker

[Juerg Haefliger]

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

** This bug is no longer a duplicate of bug 1868339
   focal/linux-raspi2:  -proposed tracker
** This bug has been marked a duplicate of bug 1869383
   focal/linux-raspi:  -proposed tracker

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

Title:
  focal/linux-raspi2: 5.4.0-1005.5 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Incomplete
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Fix Released
Status in linux-raspi2 source package in Focal:
  Fix Released

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1866488
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Promote to Proposed
  phase-changed: Thursday, 12. March 2020 10:35 UTC
  reason:
promote-to-proposed: Stalled -- review FAILED
  trackers:
focal/linux-raspi2/pi-kernel: bug 1866906
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1866480/+subscriptions

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

[Kernel-packages] [Bug 1861410] Re: focal/linux-raspi2-5.4: 5.4.0-1001.1 -proposed tracker

[Juerg Haefliger]

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

** This bug is no longer a duplicate of bug 1868339
   focal/linux-raspi2:  -proposed tracker
** This bug has been marked a duplicate of bug 1869383
   focal/linux-raspi:  -proposed tracker

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

Title:
  focal/linux-raspi2-5.4: 5.4.0-1001.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1862255
  packages:
main: linux-raspi2-5.4
meta: linux-meta-raspi2-5.4
  phase: Holding before Promote to Release
  phase-changed: Thursday, 30. January 2020 23:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861410/+subscriptions

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

[Kernel-packages] [Bug 1864880] Re: focal/linux-raspi2: -proposed tracker

[Juerg Haefliger]

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

** This bug is no longer a duplicate of bug 1868339
   focal/linux-raspi2:  -proposed tracker
** This bug has been marked a duplicate of bug 1869383
   focal/linux-raspi:  -proposed tracker

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

Title:
  focal/linux-raspi2:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Confirmed
Status in linux-raspi2 source package in Focal:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  kernel-stable-master-bug: 1864889
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Ready for Packaging
  phase-changed: Thursday, 27. February 2020 02:32 UTC
  reason:
prepare-package: Pending -- version not specified
  trackers:
focal/linux-raspi2/pi-kernel: bug 1865009
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1864880/+subscriptions

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

[Kernel-packages] [Bug 1866909] Re: Ubuntu Kernel Support for OpenPOWER NV Secure & Trusted Boot

[Frank Heimes]

That is a significant list for patches - are they all > 5.4? (I'll look them up 
...)
Ubuntu Server 20.04 will be shipped with a kernel 5.4 - and beta is planned to 
be released on April 2nd (so next Thursday) - things are largely freezed 
already.

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

Title:
  Ubuntu Kernel Support for OpenPOWER NV Secure & Trusted Boot

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  == Comment: #0 - George C. Wilson  - 2020-02-25 18:40:44 
==
  - sysfs enablement: TBD
  - ima: arch specific policy support 6191706246de
  - platform keyring changes for powerpc: TBD
  - Appended signatures support for IMA appraisal 
39b07096364a42c516415d5f841069e885234e61
  - integrity: Define a trusted platform keyring: 9dc92c45177a
  - ima: Support platform keyring for kernel appraisal: d7cecb676dd3
  - TPM 2.0 Multibank extend support: c1f92b4b04ad
  - TPM 2.0 Eventlog support: 4d23cc323cdb
  - ima: carry the measurement list across kexec: d68a6fe9fccf
  - kexec_file_load system call support: 500c7ab1a9db

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

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

[Kernel-packages] [Bug 1855668] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From naynj...@ibm.com 2020-03-27 11:17 EDT---
Hi, Thanks for the quick response. I have one question based on your statement 
- "prior to 20.04 the secure-boot lockdown in Ubuntu was largely based on 
Matthew Garrett patch set."

Q. Is the lockdown enabled during build ? And if yes, in which mode
INTEGRITY/CONFIDENTIALITY ?

Thanks & Regards,
- Nayna

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

Title:
  lockdown on power

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  == Comment: #0 - Michael Ranweiler  - 2019-11-11 
08:50:51 ==
  For 20.04 testing/inclusion.  The ubuntu kernel team has a ppa here for 
testing:
  https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable

  Test results will follow...

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

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

[Kernel-packages] [Bug 1865130] Re: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!

[Здравко]

Hi @dersuuzalachillout,
That's really strange! Did you check if reverting back to previous version 
solves the issue?
Repeat the commands in my previous post, while replace in all 3 lines 
"linux-firmware_1.173.17_all.deb" to "linux-firmware_1.173.12_all.deb". Don't 
forget reboot at the end. Let's see the result.
After reboot, post output of:

dmesg | grep UVD

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

Title:
  [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to
  reset the VCPU!!!

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux-firmware source package in Eoan:
  Fix Committed

Bug description:
  === SRU Justification ===
  [Impact] 
  Firmware update of radeon/oland_rlc.bin breaks some radeon cards.

  [Fix]
  Revert the new firmware.

  [Regression Potential]
  Low. The old firmware has been used for a long time.

  === Original Bug Report ===

  when trying > DRI_PRIME=1 glxgears , the result in dmesg is as
  following

  [  +0.91] radeon :01:00.0: WB enabled
  [  +0.02] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x8c00 and cpu addr 0x8ac2d26f
  [  +0.01] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x8c04 and cpu addr 0xa848de20
  [  +0.01] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x8c08 and cpu addr 0x1e4494a9
  [  +0.01] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x8c0c and cpu addr 0x98a9748e
  [  +0.01] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x8c10 and cpu addr 0xb6ff734d
  [  +0.000212] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0x6b4da526
  [  +0.100566] radeon :01:00.0: failed VCE resume (-110).
  [  +0.179115] [drm] ring test on 0 succeeded in 1 usecs
  [  +0.04] [drm] ring test on 1 succeeded in 1 usecs
  [  +0.04] [drm] ring test on 2 succeeded in 1 usecs
  [  +0.06] [drm] ring test on 3 succeeded in 3 usecs
  [  +0.04] [drm] ring test on 4 succeeded in 3 usecs
  [  +1.171892] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015643] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015509] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015572] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015514] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015405] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015442] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015416] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015388] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015379] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +0.019924] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
giving up!!!
  [  +0.40] radeon :01:00.0: failed initializing UVD (-1).
  [  +0.60] [drm] ib test on ring 0 succeeded in 0 usecs
  [  +0.51] [drm] ib test on ring 1 succeeded in 0 usecs
  [  +0.32] [drm] ib test on ring 2 succeeded in 0 usecs
  [  +0.52] [drm] ib test on ring 3 succeeded in 0 usecs
  [  +0.29] [drm] ib test on ring 4 succeeded in 0 usecs

  Also it affects the boot time.

  the used OpenGL renderer is:
  "OpenGL renderer string: AMD OLAND (DRM 2.50.0, 5.3.0-40-generic, LLVM 9.0.0)"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Fri Feb 28 11:50:50 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.3.0-28-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.3.0-40-generic, x86_64: installed
   virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed
   virtualbox, 5.2.34, 5.3.0-40-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics 

[Kernel-packages] [Bug 1864005] Re: Fix AMD Stoney Ridge screen flickering under 4K resolution

[Kamal Mostafa]

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

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

** Changed in: linux (Ubuntu Disco)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

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

Title:
  Fix AMD Stoney Ridge screen flickering under 4K resolution

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Disco:
  In Progress
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Released

Bug description:
  [Impact]
  Screen flickering/tearing when AMD Stoney Ridge outputs to 4K display.

  [Fix]
  Disable IOMMU on Stoney Ridge.

  [Test]
  Connect to 4K screen through DP or HDMI. Heavy flickering/tearing can be
  observed.
  The flickering/tearing is gone once the patch is applied.

  [Regression Potential]
  Low. This fix limits to one specific SoC.
  According to AMD, IOMMU isn't enabled for this SoC under Windows.
  So it's expected behavior.

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

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

[Kernel-packages] [Bug 1855668] Re: lockdown on power

[Frank Heimes]

Well, prior to 20.04 the secure-boot lockdown in Ubuntu was largely based on 
Matthew Garrett patch set. With the upstream acceptance of secure boot in 5.4 
we moved over to the upstream code, and 20.04 contains kernel 5.4 anyway.
In a different LP bug IBM got generally asked for checking lock-down on two 
architectures, and this is the spin-off ticket of this ticket for Power.
With Daniel Axtens comments on this tickets and the request to pick up some 
commits we thought that now all lock-down patches are in - secureboot is in 
from upstream - incl. any linkages.
I suggest to have a chat with Daniel on that, too.

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

Title:
  lockdown on power

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  == Comment: #0 - Michael Ranweiler  - 2019-11-11 
08:50:51 ==
  For 20.04 testing/inclusion.  The ubuntu kernel team has a ppa here for 
testing:
  https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable

  Test results will follow...

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

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

[Kernel-packages] [Bug 1867007] Re: zfs-initramfs fails with multiple rpool on separate disks

[Jean-Baptiste Lallement]

Thanks for your report. I reproduced the issue.

There are actually 3 different points to fix in grub and initramfs to
display individual entries per machine in grub and import the pools by
ID to prevent the name clash.

** Description changed:

+ == Test Case ==
+ 1. On a multi disks setup, install Ubuntu with ZFS on disk 1
+ 2. Reboot and make sure everything works as expected
+ 3. Do a second installation and install Ubuntu with ZFS on disk 2
+ 4. Reboot
+ 
+ * Expected Result * 
+ GRUB should display all the machines available and let the user select which 
installation to boot
+ 
+ * Actual result * 
+ - Only one machine is listed
+ - initramfs crashes because there are several pool with the same name but 
different IDs and import the pools by name
+ - Same problem in the systemd generator which will try to import all the 
rpools.
+ 
+ 
+ == Original Description ==
+ 
  I had an Ubuntu old installation that used a ZFS root, using the layout
  described in the ZFS on Linux docs. Consequently, the pool name for my
  Ubuntu installation was "rpool". I'm currently encountering an issue
  with that pool that only allows me to mount it read-only. So, I'd like
  to replicate the datasets from there to a new device.
  
  On the new device, I've set up a ZFS system using the Ubuntu 20.04 daily
  installer (March 9, 2020). This setup creates a new pool named "rpool".
  So, with both devices inserted, I have two distinct pools each named
  "rpool", one of which will kernel panic if I try to mount it read-write.
  
  ZFS is fine with having multiple pools with the same name. In these
  cases, you use `zfs import` with the pool's GUID and give it a distinct
  pool name on import. However, the grub config for booting from ZFS
  doesn't appear to handle multiple pools with the same rpool name very
  well. Rather than using the pool's GUID, it uses the name, and as such,
  it's unable to boot properly when another pool with the name "rpool" is
  attached to the system.
  
  I think it'd be better if the config were written in such a way that
  `update-grub` generated boot config bound to whatever pool it found at
  the time of its invocation, and not start searching through all pools
  dynamically upon boot. Just to be clear, I have an Ubuntu 20.04 system
  with a ZFS root that boots just fine. But, the moment I attach the old
  pool, also named "rpool", I'm no longer able to boot up my system even
  though I haven't removed the good pool and I haven't re-run `update-
  grub`. Instead of botoing, I'm thrown into the grub command line.

** Also affects: grub2 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: grub2 (Ubuntu)
   Status: New => Triaged

** Changed in: grub2 (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  zfs-initramfs fails with multiple rpool on separate disks

Status in grub2 package in Ubuntu:
  Triaged
Status in zfs-linux package in Ubuntu:
  Triaged

Bug description:
  == Test Case ==
  1. On a multi disks setup, install Ubuntu with ZFS on disk 1
  2. Reboot and make sure everything works as expected
  3. Do a second installation and install Ubuntu with ZFS on disk 2
  4. Reboot

  * Expected Result * 
  GRUB should display all the machines available and let the user select which 
installation to boot

  * Actual result * 
  - Only one machine is listed
  - initramfs crashes because there are several pool with the same name but 
different IDs and import the pools by name
  - Same problem in the systemd generator which will try to import all the 
rpools.

  
  == Original Description ==

  I had an Ubuntu old installation that used a ZFS root, using the
  layout described in the ZFS on Linux docs. Consequently, the pool name
  for my Ubuntu installation was "rpool". I'm currently encountering an
  issue with that pool that only allows me to mount it read-only. So,
  I'd like to replicate the datasets from there to a new device.

  On the new device, I've set up a ZFS system using the Ubuntu 20.04
  daily installer (March 9, 2020). This setup creates a new pool named
  "rpool". So, with both devices inserted, I have two distinct pools
  each named "rpool", one of which will kernel panic if I try to mount
  it read-write.

  ZFS is fine with having multiple pools with the same name. In these
  cases, you use `zfs import` with the pool's GUID and give it a
  distinct pool name on import. However, the grub config for booting
  from ZFS doesn't appear to handle multiple pools with the same rpool
  name very well. Rather than using the pool's GUID, it uses the name,
  and as such, it's unable to boot properly when another pool with the
  name "rpool" is attached to the system.

  I think it'd be better if the config were written in such a way that
  `update-grub` generated boot config bound to whatever pool it 

[Kernel-packages] [Bug 1867007] Re: ZFS won't boot if multiple rpools found

[Jean-Baptiste Lallement]

** Package changed: grub2 (Ubuntu) => zfs-linux (Ubuntu)

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

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

** Summary changed:

- ZFS won't boot if multiple rpools found
+ zfs-initramfs fails with multiple rpool on separate disks

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

Title:
  zfs-initramfs fails with multiple rpool on separate disks

Status in zfs-linux package in Ubuntu:
  Triaged

Bug description:
  I had an Ubuntu old installation that used a ZFS root, using the
  layout described in the ZFS on Linux docs. Consequently, the pool name
  for my Ubuntu installation was "rpool". I'm currently encountering an
  issue with that pool that only allows me to mount it read-only. So,
  I'd like to replicate the datasets from there to a new device.

  On the new device, I've set up a ZFS system using the Ubuntu 20.04
  daily installer (March 9, 2020). This setup creates a new pool named
  "rpool". So, with both devices inserted, I have two distinct pools
  each named "rpool", one of which will kernel panic if I try to mount
  it read-write.

  ZFS is fine with having multiple pools with the same name. In these
  cases, you use `zfs import` with the pool's GUID and give it a
  distinct pool name on import. However, the grub config for booting
  from ZFS doesn't appear to handle multiple pools with the same rpool
  name very well. Rather than using the pool's GUID, it uses the name,
  and as such, it's unable to boot properly when another pool with the
  name "rpool" is attached to the system.

  I think it'd be better if the config were written in such a way that
  `update-grub` generated boot config bound to whatever pool it found at
  the time of its invocation, and not start searching through all pools
  dynamically upon boot. Just to be clear, I have an Ubuntu 20.04 system
  with a ZFS root that boots just fine. But, the moment I attach the old
  pool, also named "rpool", I'm no longer able to boot up my system even
  though I haven't removed the good pool and I haven't re-run `update-
  grub`. Instead of botoing, I'm thrown into the grub command line.

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

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

[Kernel-packages] [Bug 1843298] Re: Upgrade of datapool to ZFS 0.8 creates a problem if dual booting

[Colin Ian King]

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

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

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

Title:
  Upgrade of datapool to ZFS 0.8 creates a problem if dual booting

Status in zfs-linux package in Ubuntu:
  Triaged

Bug description:
  I have upgraded my dual boot laptop (Xubuntu 19.04 on ZFS) to 19.10, I
  only had a minor problems:

  The system started scrubbing the exisisting datapools.
  In the scrub I have been notified, that my datapool did not support all new 
features and that I had to upgrade the datapool. Of course I followed that 
advice enthusiastically and now the second 18.04.3 OS does not recognize the 
upgraded datapool anymore. I found out I can’t disable the culprit features.

  I think there should be a more specific warning in the "zpool upgrade"
  for stupids like me. Only upgrade the datapool, if all OSes on the PC
  have been upgraded to zfs 0.8.

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

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

[Kernel-packages] [Bug 1865236] Re: zsysctl inconsistency in handling snapshots/states

[Colin Ian King]

** Also affects: zsys (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: zfs-linux (Ubuntu)

** Changed in: zsys (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  zsysctl inconsistency in handling snapshots/states

Status in zsys package in Ubuntu:
  New

Bug description:
  Before the zsys of 27 Feb update I had created a snapshot for the
  system BOOT, ROOT and USERDATA datasets. These snapshots are reported
  by "zsysctl show" for the USERDATA datasets, but they are ignored for
  the BOOT and ROOT datasets.

  see annex with:
  zfs list -t snapshot
  zsysctl show
  zsysctl show --full

  Remark: Please stick as close as possible to the established zfs terminology, 
like:
  state vs snapshot
  list vs show

  Where can we find info about, what to expect in 20.04 and a
  description of the commands. I have no clue what e.g. the command
  "completion" does!

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

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

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

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1869372

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  Popping/crackling noise when sound card wakes from powersaving

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I could not find an existing report on this.
  When Ubuntu 20.04 does powersaving, the audio card powers down.
  When the card powers up again, it emits a short annoying popping/crackling 
noise, then audio plays just fine.

  The workaround is to disable power-saving for the audio card, by
  adding

  options snd_hda_intel power_save=0 power_save_controller=N

  to a file in /etc/modprobe.d/alsa-intel-no-powersave.conf

  and then reboot.

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

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

[Kernel-packages] [Bug 1867007] [NEW] ZFS won't boot if multiple rpools found

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I had an Ubuntu old installation that used a ZFS root, using the layout
described in the ZFS on Linux docs. Consequently, the pool name for my
Ubuntu installation was "rpool". I'm currently encountering an issue
with that pool that only allows me to mount it read-only. So, I'd like
to replicate the datasets from there to a new device.

On the new device, I've set up a ZFS system using the Ubuntu 20.04 daily
installer (March 9, 2020). This setup creates a new pool named "rpool".
So, with both devices inserted, I have two distinct pools each named
"rpool", one of which will kernel panic if I try to mount it read-write.

ZFS is fine with having multiple pools with the same name. In these
cases, you use `zfs import` with the pool's GUID and give it a distinct
pool name on import. However, the grub config for booting from ZFS
doesn't appear to handle multiple pools with the same rpool name very
well. Rather than using the pool's GUID, it uses the name, and as such,
it's unable to boot properly when another pool with the name "rpool" is
attached to the system.

I think it'd be better if the config were written in such a way that
`update-grub` generated boot config bound to whatever pool it found at
the time of its invocation, and not start searching through all pools
dynamically upon boot. Just to be clear, I have an Ubuntu 20.04 system
with a ZFS root that boots just fine. But, the moment I attach the old
pool, also named "rpool", I'm no longer able to boot up my system even
though I haven't removed the good pool and I haven't re-run `update-
grub`. Instead of botoing, I'm thrown into the grub command line.

** Affects: zfs-linux (Ubuntu)
 Importance: Medium
 Status: Triaged


** Tags: zfs
-- 
ZFS won't boot if multiple rpools found
https://bugs.launchpad.net/bugs/1867007
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to zfs-linux in Ubuntu.

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

[Kernel-packages] [Bug 1866681] Re: [HP Pavilion dv9000] Mute toggles on/off while plugged into the headphone/speaker jack (19.04+)

[Kuroš Taheri-Golværzi]

So, I've upgraded my main OS (Xubuntu 18.04) to 5.3.0-42-generic, and
now, it's partially suffering from the mute-toggle issue. The computer
mutes or unmutes whenever something happens that produces sound (e.g.,
when a messenger app gives a notification, when I pause/play a video,
etc), and it gives that sound through the speakers when it does (as I've
recorded in the video, linked in the first post). Is there anything else
I can test and/or try for you guys to gather more information?

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

Title:
  [HP Pavilion dv9000] Mute toggles on/off while plugged into the
  headphone/speaker jack (19.04+)

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I'm on an HP Pavilion dv9000 (https://www.cnet.com/products/hp-
  pavilion-dv9000/specs/) built many years ago.

  
  Whenever I'm using any distro that's based on Ubuntu which was published from 
Version 19.04 onwards, I've been having a major issue with the mute button 
toggling on and off whenever I have something plugged into the audio out jack. 
I know that it's not the fault of XFCE, because I also use the latest version 
of Manjaro with XFCE on this same computer, and it works fine. I also know it's 
not any Red Hat-based distro, because I use Stella (which is a remix of CentOS 
6) also on this exact same computer, and it also works fine. Qubes, Mageia, and 
Fedora 31 also work perfectly fine and don't have this issue.

  My "lsb-release" is:
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=19.10
  DISTRIB_CODENAME=eoan
  DISTRIB_DESCRIPTION="Ubuntu 19.10"

  and "apt-cache policy pulseaudio" outputs:
  pulseaudio:
Installed: 1:13.0-1ubuntu1.1
Candidate: 1:13.0-1ubuntu1.1
Version table:
   *** 1:13.0-1ubuntu1.1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:13.0-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages

  I've uploaded a short video of the problem that I recorded with my phone here:
  https://www.youtube.com/watch?v=GXaHXQA-5uQ

  
  The problem appears with Kali 2019 and 2020, Peppermint 19.04, Lubuntu 19.04, 
Xubuntu 19.04, and Sparky 5.10 and 2020.02.

  
  I've checked pretty much everything I can think of. There's a log for my ALSA 
help diagnostics results on my current computer (which works properly with 
18.04) at:
  http://alsa-project.org/db/?f=4859b85cd7fc32e7f01f8df63591b5a43dbf6829

  
  the result output of lspci is:
  [code]00:00.0 RAM memory: NVIDIA Corporation C51 Host Bridge (rev a2)
  00:00.1 RAM memory: NVIDIA Corporation C51 Memory Controller 0 (rev a2)
  00:00.2 RAM memory: NVIDIA Corporation C51 Memory Controller 1 (rev a2)
  00:00.3 RAM memory: NVIDIA Corporation C51 Memory Controller 5 (rev a2)
  00:00.4 RAM memory: NVIDIA Corporation C51 Memory Controller 4 (rev a2)
  00:00.5 RAM memory: NVIDIA Corporation C51 Host Bridge (rev a2)
  00:00.6 RAM memory: NVIDIA Corporation C51 Memory Controller 3 (rev a2)
  00:00.7 RAM memory: NVIDIA Corporation C51 Memory Controller 2 (rev a2)
  00:02.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1)
  00:03.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1)
  00:04.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1)
  00:09.0 RAM memory: NVIDIA Corporation MCP51 Host Bridge (rev a2)
  00:0a.0 ISA bridge: NVIDIA Corporation MCP51 LPC Bridge (rev a3)
  00:0a.1 SMBus: NVIDIA Corporation MCP51 SMBus (rev a3)
  00:0a.3 Co-processor: NVIDIA Corporation MCP51 PMU (rev a3)
  00:0b.0 USB controller: NVIDIA Corporation MCP51 USB Controller (rev a3)
  00:0b.1 USB controller: NVIDIA Corporation MCP51 USB Controller (rev a3)
  00:0d.0 IDE interface: NVIDIA Corporation MCP51 IDE (rev f1)
  00:0e.0 IDE interface: NVIDIA Corporation MCP51 Serial ATA Controller (rev f1)
  00:0f.0 IDE interface: NVIDIA Corporation MCP51 Serial ATA Controller (rev f1)
  00:10.0 PCI bridge: NVIDIA Corporation MCP51 PCI Bridge (rev a2)
  00:10.1 Audio device: NVIDIA Corporation MCP51 High Definition Audio (rev a2)
  00:14.0 Bridge: NVIDIA Corporation MCP51 Ethernet Controller (rev a3)
  00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] 
HyperTransport Technology Configuration
  00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] 
Address Map
  00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] 
DRAM Controller
  00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] 
Miscellaneous Control
  03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4311 802.11b/g 
WLAN (rev 01)
  05:00.0 VGA compatible controller: NVIDIA Corporation G73M [GeForce Go 7600] 
(rev a1)
  07:05.0 FireWire (IEEE 

[Kernel-packages] [Bug 1855668] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From naynj...@ibm.com 2020-03-27 10:03 EDT---
I would like to understand that with new lockdown patches upstreamed now,

* Is Ubuntu still going to carry a patch linking secureboot with lockdown ? If 
yes, would you be doing same for powerpc ?
* Is Ubuntu going to enable lockdown during build time ? If yes, then in which 
mode -  INTEGRITY or CONFIDENTIALITY. ?

Thanks & Regards,
- Nayna

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

Title:
  lockdown on power

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  == Comment: #0 - Michael Ranweiler  - 2019-11-11 
08:50:51 ==
  For 20.04 testing/inclusion.  The ubuntu kernel team has a ppa here for 
testing:
  https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable

  Test results will follow...

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

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

[Kernel-packages] [Bug 1866909] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From naynj...@ibm.com 2020-03-27 10:00 EDT---
Below is the list of commits for specified TBDs (sysfs enablement/platform 
keyring changes for powerpc):. These were upstreamed in kernel v5.5 version.

Platform Keyring changes for powerpc:
8220e22 - powerpc: Load firmware trusted keys/hashes into kernel keyring
ad72367 - x86/efi: move common keyring handler functions to new file
bd5d9c7 - powerpc: expose secure variables to userspace via sysfs
9155e23 - powerpc/powernv: Add OPAL API interface to access secure variable
39a963b - sysfs: Fixes __BIN_ATTR_WO() macro

sysfs enablement:
d72ea49 - powerpc/ima: Indicate kernel modules appended signatures are enforced
dc87f18 - powerpc/ima: Update ima arch policy to check for blacklist
273df86 - ima: Check against blacklisted hashes for files with modsig
2434f7d - certs: Add wrapper function to check blacklisted binary hash
e14555e - ima: Make process_buffer_measurement() generic
1917855 - powerpc/ima: Define trusted boot policy
2702809 - powerpc: Detect the trusted boot state of the system
4238fad - powerpc/ima: Add support to initialize ima policy rules
1a8916e - powerpc: Detect the secure boot mode of the system
82af5b6 - sysfs: Fixes __BIN_ATTR_WO() macro

May I ask the kernel version that Ubuntu will be using for 20.04 ?

Thanks & Regards,
- Nayna

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

Title:
  Ubuntu Kernel Support for OpenPOWER NV Secure & Trusted Boot

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  == Comment: #0 - George C. Wilson  - 2020-02-25 18:40:44 
==
  - sysfs enablement: TBD
  - ima: arch specific policy support 6191706246de
  - platform keyring changes for powerpc: TBD
  - Appended signatures support for IMA appraisal 
39b07096364a42c516415d5f841069e885234e61
  - integrity: Define a trusted platform keyring: 9dc92c45177a
  - ima: Support platform keyring for kernel appraisal: d7cecb676dd3
  - TPM 2.0 Multibank extend support: c1f92b4b04ad
  - TPM 2.0 Eventlog support: 4d23cc323cdb
  - ima: carry the measurement list across kexec: d68a6fe9fccf
  - kexec_file_load system call support: 500c7ab1a9db

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

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

[Kernel-packages] [Bug 1869372] [NEW] Popping/crackling noise when sound card wakes from powersaving

[Simos Xenitellis ]

Public bug reported:

I could not find an existing report on this.
When Ubuntu 20.04 does powersaving, the audio card powers down.
When the card powers up again, it emits a short annoying popping/crackling 
noise, then audio plays just fine.

The workaround is to disable power-saving for the audio card, by adding

options snd_hda_intel power_save=0 power_save_controller=N

to a file in /etc/modprobe.d/alsa-intel-no-powersave.conf

and then reboot.

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

** Description changed:

  I could not find an existing report on this.
- When Ubuntu does powersaving, the audio card powers down.
+ When Ubuntu 20.04 does powersaving, the audio card powers down.
  When the card powers up again, it emits a short annoying popping/crackling 
noise, then audio plays just fine.
  
  The workaround is to disable power-saving for the audio card, by adding
  
  options snd_hda_intel power_save=0 power_save_controller=N
  
  to a file in /etc/modprobe.d/alsa-intel-no-powersave.conf
  
  and then reboot.

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

Title:
  Popping/crackling noise when sound card wakes from powersaving

Status in linux package in Ubuntu:
  New

Bug description:
  I could not find an existing report on this.
  When Ubuntu 20.04 does powersaving, the audio card powers down.
  When the card powers up again, it emits a short annoying popping/crackling 
noise, then audio plays just fine.

  The workaround is to disable power-saving for the audio card, by
  adding

  options snd_hda_intel power_save=0 power_save_controller=N

  to a file in /etc/modprobe.d/alsa-intel-no-powersave.conf

  and then reboot.

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

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

[Kernel-packages] [Bug 1850130] Re: zpools fail to import after reboot on fresh install of eoan

[Didier Roche]

** Also affects: grub2 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  zpools fail to import after reboot on fresh install of eoan

Status in grub2 package in Ubuntu:
  New
Status in zfs-linux package in Ubuntu:
  Confirmed
Status in grub2 source package in Focal:
  New
Status in zfs-linux source package in Focal:
  Confirmed

Bug description:
  Fresh installation of stock Ubuntu 19.10 Eoan with experimental root on ZFS.
  System has existing zpools with data.

  Installation is uneventful. First boot with no problems. Updates
  applied. No other changes from fresh installation. Reboot.

  External pool 'tank' imports with no errors. Reboot.

  External pool has failed to import on boot. In contrast bpool and
  rpool are ok. Manually re-import 'tank' with no issues. I can see both
  'tank' and its path in /dev/disk/by-id/ in /etc/zfs/zpool.cache.
  Reboot.

  'tank' has failed to import on boot. It is also missing from
  /etc/zfs/zpool.cache. Is it possible that the cache is being re-
  generated on reboot, and the newly imported pools are getting erased
  from it? I can re-import the pools again manually with no issues, but
  they don't persist between re-boots.

  Installing normally on ext4 this is not an issue and data pools import
  automatically on boot with no further effort.

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

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

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

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1869235

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  Ryzen 3rd gen (3900X) ECC support missing from kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu server:
  Description:Ubuntu 19.10
  Release:19.10
  Installed kernel:
  linux-generic:
Installed: 5.3.0.42.36
  (I could not figure out what package to select in the 'in what package did 
you find this bug' chooser)

  Expected behavior: ECC RAM is detected and utilized
  Result instead:
  Error in dmesg at boot:
  EDAC amd64: Error: F0 not found, device 0x1460 (broken BIOS?) (more in the 
attached KernelErrors.log)

  Kernel 5.3 is missing ECC support for some families of AMD Ryzen 3rd
  gen CPUs.

  Support is added via these two commits in the mainline tree:
  
https://github.com/torvalds/linux/commit/e53a3b267fb0a79db9ca1f1e08b97889b22013e6
  
https://github.com/torvalds/linux/commit/3e443eb353eda6f4b4796e07f2599683fa752f1d

  The second commit actually adds the missing support, but it relies on
  the first commit: a partial refactor of the AMD ECC code.

  I tested myself, followed the instructions at 
https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel to build my own kernel, 
cherry-picked the two above commits, and have working ECC support on my 
self-built kernel:
  Linux smaug 5.3.0-43-generic #36 SMP Sat Mar 21 02:33:30 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux:

  EDAC MC: Ver: 3.0.0
  EDAC amd64: Node 0: DRAM ECC enabled.
  EDAC amd64: F17h_M70h detected (node 0).
  EDAC MC: UMC0 chip selects:
  EDAC amd64: MC: 0: 0MB 1: 0MB
  EDAC amd64: MC: 2: 16384MB 3: 16384MB
  EDAC MC: UMC1 chip selects:
  EDAC amd64: MC: 0: 0MB 1: 0MB
  EDAC amd64: MC: 2: 16384MB 3: 16384MB
  EDAC amd64: using x16 syndromes.
  EDAC amd64: MCT channel count: 2
  EDAC MC0: Giving out device to module amd64_edac controller F17h_M70h: DEV 
:00:18.3 (INTERRUPT)
  EDAC PCI0: Giving out device to module amd64_edac controller EDAC PCI 
controller: DEV :00:18.0 (POLLED)
  AMD64 EDAC driver v3.5.0

  
  If this could be included in a future hardware support kernel release, that 
would be very helpful.  I am unsure what the policy is for including this kind 
of backport in non-LTS kernels, though I know the LTS releases have hardware 
support updates that include this type of fix.

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

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

[Kernel-packages] [Bug 1869368] Re: ubuntu_qrt_apparmor fails on ADT bionic/linux i386

[Kleber Sacilotto de Souza]

** Also affects: apparmor (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: qa-regression-testing
   Importance: Undecided
   Status: New

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

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

Title:
  ubuntu_qrt_apparmor fails on ADT bionic/linux i386

Status in QA Regression Testing:
  New
Status in ubuntu-kernel-tests:
  New
Status in apparmor package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid
Status in apparmor source package in Bionic:
  New
Status in linux source package in Bionic:
  Confirmed

Bug description:
  Testing failed on:
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/i386/l/linux/20200326_224620_0dd01@/log.gz

  Kernel version: bionic/linux 4.15.0-94.95

  The ubuntu_qrt_apparmor.test-apparmor.py fails intermittently on
  bionic/linux i386 ADT tests. It has failed some releases in the past
  and I'm seeing the failure in the current release as well. I have not
  seen this failure on other architectures.

  These are the last messages on the test log:
  20:12:39 ERROR| [stderr] Test mediation of file based SOCK_STREAM connect ... 
ok
  20:12:39 ERROR| [stderr] test_libapparmor_testsuite 
(__main__.ApparmorTestsuites)
  20:14:18 DEBUG| [stdout]   unconfined_user can access confined_user's file
  20:14:18 DEBUG| [stdout]   unconfined_user can access default_user's file
  20:14:18 DEBUG| [stdout]   unconfined_user can access unconfined_group's file
  20:14:18 DEBUG| [stdout] 
  20:15:42 ERROR| [stderr] Run libapparmor testsuite ... (Applying patch 
0001-mount-regression-test-convert-mount-test-to-use-MS_N.patch) (Applying 
patch 0001-usr-merge-fixups.patch) ok
  20:15:42 ERROR| [stderr] test_libapparmor_testsuite3 
(__main__.ApparmorTestsuites)
  20:15:52 DEBUG| [stdout]   preparing apparmor_2.12-4ubuntu5.1.dsc...  done
  20:15:52 DEBUG| [stdout] 
  20:17:10 ERROR| [stderr] Run libapparmor testsuite (with python3) ... 
(Applying patch 
0001-mount-regression-test-convert-mount-test-to-use-MS_N.patch) (Applying 
patch 0001-usr-merge-fixups.patch) ok
  20:17:10 ERROR| [stderr] test_old_trusty_parser_testsuite 
(__main__.ApparmorTestsuites)
  20:17:10 DEBUG| [stdout]   preparing apparmor_2.12-4ubuntu5.1.dsc...  done
  20:17:10 ERROR| [stderr] Run parser regression tests from 14.04's 
apparmor_2.8.95~2430-0ubuntu5.3 ... (skipped: This test is only for 14.04 
systems with the apparmor 2.10.95 SRU or newer installed) ok
  20:17:10 ERROR| [stderr] test_old_trusty_regression_testsuite 
(__main__.ApparmorTestsuites)
  20:17:10 ERROR| [stderr] Run kernel regression tests from 14.04's 
apparmor_2.8.95~2430-0ubuntu5.3 ... (skipped: This test is only for 14.04 
systems with the apparmor 2.10.95 SRU or newer installed) ok
  20:17:10 ERROR| [stderr] test_parser_testsuite (__main__.ApparmorTestsuites)
  20:17:19 DEBUG| [stdout] 
  20:52:35 ERROR| [stderr] Run parser regression tests ... (Applying patch 
0001-mount-regression-test-convert-mount-test-to-use-MS_N.patch) (Applying 
patch 0001-usr-merge-fixups.patch) ok
  20:52:35 ERROR| [stderr] test_regression_testsuite 
(__main__.ApparmorTestsuites)
  20:52:42 DEBUG| [stdout]   preparing apparmor_2.12-4ubuntu5.1.dsc...  done
  20:52:42 DEBUG| [stdout] 
  21:01:56 INFO | ERROR   ubuntu_qrt_apparmor.test-apparmor.py  
  ubuntu_qrt_apparmor.test-apparmor.pytimestamp=1585256516localtime=Mar 
26 21:01:56   Test subprocess failed rc=9

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1869368/+subscriptions

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

[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

[Laguna Thanga]

How to find out who submitted this code that broke the system?

I wonder weather this is intentional by competitors

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

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in gdm3 source package in Eoan:
  Confirmed
Status in gnome-session source package in Eoan:
  Confirmed
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed

Bug description:
  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  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.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1865130] Re: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!

[Françesc]

Deseado=desconocido(U)/Instalar/eliminaR/Purgar/retener(H)
| 
Estado=No/Inst/ficheros-Conf/desempaqUetado/medio-conF/medio-inst(H)/espera-disparo(W)/pendienTe-disparo
|/ Err?=(ninguno)/requiere-Reinst (Estado,Err: mayúsc.=malo)
||/ Nombre Versión  Arquitectura Descripción
+++-==---=
ii  linux-firmware 1.173.17 all  Firmware for Linux kernel drivers


Graphics:  Card-1: Advanced Micro Devices [AMD/ATI] Kaveri [Radeon R6 Graphics]
   Card-2: Advanced Micro Devices [AMD/ATI] Opal XT [Radeon R7 
M265/M365X/M465]
   Display Server: X.Org 1.19.6
   drivers: ati,radeon (unloaded: modesetting,fbdev,vesa)
   Resolution: 1366x768@60.02hz
   OpenGL: renderer: AMD KAVERI (DRM 2.50.0, 4.15.0-91-generic, LLVM 
9.0.0)
   version: 4.5 Mesa 19.2.8

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

Title:
  [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to
  reset the VCPU!!!

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux-firmware source package in Eoan:
  Fix Committed

Bug description:
  === SRU Justification ===
  [Impact] 
  Firmware update of radeon/oland_rlc.bin breaks some radeon cards.

  [Fix]
  Revert the new firmware.

  [Regression Potential]
  Low. The old firmware has been used for a long time.

  === Original Bug Report ===

  when trying > DRI_PRIME=1 glxgears , the result in dmesg is as
  following

  [  +0.91] radeon :01:00.0: WB enabled
  [  +0.02] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x8c00 and cpu addr 0x8ac2d26f
  [  +0.01] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x8c04 and cpu addr 0xa848de20
  [  +0.01] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x8c08 and cpu addr 0x1e4494a9
  [  +0.01] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x8c0c and cpu addr 0x98a9748e
  [  +0.01] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x8c10 and cpu addr 0xb6ff734d
  [  +0.000212] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0x6b4da526
  [  +0.100566] radeon :01:00.0: failed VCE resume (-110).
  [  +0.179115] [drm] ring test on 0 succeeded in 1 usecs
  [  +0.04] [drm] ring test on 1 succeeded in 1 usecs
  [  +0.04] [drm] ring test on 2 succeeded in 1 usecs
  [  +0.06] [drm] ring test on 3 succeeded in 3 usecs
  [  +0.04] [drm] ring test on 4 succeeded in 3 usecs
  [  +1.171892] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015643] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015509] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015572] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015514] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015405] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015442] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015416] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015388] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015379] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +0.019924] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
giving up!!!
  [  +0.40] radeon :01:00.0: failed initializing UVD (-1).
  [  +0.60] [drm] ib test on ring 0 succeeded in 0 usecs
  [  +0.51] [drm] ib test on ring 1 succeeded in 0 usecs
  [  +0.32] [drm] ib test on ring 2 succeeded in 0 usecs
  [  +0.52] [drm] ib test on ring 3 succeeded in 0 usecs
  [  +0.29] [drm] ib test on ring 4 succeeded in 0 usecs

  Also it affects the boot time.

  the used OpenGL renderer is:
  "OpenGL renderer string: AMD OLAND (DRM 2.50.0, 5.3.0-40-generic, LLVM 9.0.0)"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Fri Feb 28 11:50:50 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  

[Kernel-packages] [Bug 1869235] Re: Ryzen 3rd gen (3900X) ECC support missing from kernel

[Paul White]

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

** Tags added: eoan

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

Title:
  Ryzen 3rd gen (3900X) ECC support missing from kernel

Status in linux package in Ubuntu:
  New

Bug description:
  Ubuntu server:
  Description:Ubuntu 19.10
  Release:19.10
  Installed kernel:
  linux-generic:
Installed: 5.3.0.42.36
  (I could not figure out what package to select in the 'in what package did 
you find this bug' chooser)

  Expected behavior: ECC RAM is detected and utilized
  Result instead:
  Error in dmesg at boot:
  EDAC amd64: Error: F0 not found, device 0x1460 (broken BIOS?) (more in the 
attached KernelErrors.log)

  Kernel 5.3 is missing ECC support for some families of AMD Ryzen 3rd
  gen CPUs.

  Support is added via these two commits in the mainline tree:
  
https://github.com/torvalds/linux/commit/e53a3b267fb0a79db9ca1f1e08b97889b22013e6
  
https://github.com/torvalds/linux/commit/3e443eb353eda6f4b4796e07f2599683fa752f1d

  The second commit actually adds the missing support, but it relies on
  the first commit: a partial refactor of the AMD ECC code.

  I tested myself, followed the instructions at 
https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel to build my own kernel, 
cherry-picked the two above commits, and have working ECC support on my 
self-built kernel:
  Linux smaug 5.3.0-43-generic #36 SMP Sat Mar 21 02:33:30 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux:

  EDAC MC: Ver: 3.0.0
  EDAC amd64: Node 0: DRAM ECC enabled.
  EDAC amd64: F17h_M70h detected (node 0).
  EDAC MC: UMC0 chip selects:
  EDAC amd64: MC: 0: 0MB 1: 0MB
  EDAC amd64: MC: 2: 16384MB 3: 16384MB
  EDAC MC: UMC1 chip selects:
  EDAC amd64: MC: 0: 0MB 1: 0MB
  EDAC amd64: MC: 2: 16384MB 3: 16384MB
  EDAC amd64: using x16 syndromes.
  EDAC amd64: MCT channel count: 2
  EDAC MC0: Giving out device to module amd64_edac controller F17h_M70h: DEV 
:00:18.3 (INTERRUPT)
  EDAC PCI0: Giving out device to module amd64_edac controller EDAC PCI 
controller: DEV :00:18.0 (POLLED)
  AMD64 EDAC driver v3.5.0

  
  If this could be included in a future hardware support kernel release, that 
would be very helpful.  I am unsure what the policy is for including this kind 
of backport in non-LTS kernels, though I know the LTS releases have hardware 
support updates that include this type of fix.

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

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

[Kernel-packages] [Bug 1869368] Re: ubuntu_qrt_apparmor fails on ADT bionic/linux i386

[Kleber Sacilotto de Souza]

** Description changed:

  Testing failed on:
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/i386/l/linux/20200326_224620_0dd01@/log.gz
+ 
+ Kernel version: bionic/linux 4.15.0-94.95
+ 
+ The ubuntu_qrt_apparmor.test-apparmor.py fails intermittently on
+ bionic/linux i386 ADT tests. It has failed some releases in the past and
+ I'm seeing the failure in the current release as well. I have not seen
+ this failure on other architectures.
+ 
+ These are the last messages on the test log:
+ 20:12:39 ERROR| [stderr] Test mediation of file based SOCK_STREAM connect ... 
ok
+ 20:12:39 ERROR| [stderr] test_libapparmor_testsuite 
(__main__.ApparmorTestsuites)
+ 20:14:18 DEBUG| [stdout]   unconfined_user can access confined_user's file
+ 20:14:18 DEBUG| [stdout]   unconfined_user can access default_user's file
+ 20:14:18 DEBUG| [stdout]   unconfined_user can access unconfined_group's file
+ 20:14:18 DEBUG| [stdout] 
+ 20:15:42 ERROR| [stderr] Run libapparmor testsuite ... (Applying patch 
0001-mount-regression-test-convert-mount-test-to-use-MS_N.patch) (Applying 
patch 0001-usr-merge-fixups.patch) ok
+ 20:15:42 ERROR| [stderr] test_libapparmor_testsuite3 
(__main__.ApparmorTestsuites)
+ 20:15:52 DEBUG| [stdout]   preparing apparmor_2.12-4ubuntu5.1.dsc...  done
+ 20:15:52 DEBUG| [stdout] 
+ 20:17:10 ERROR| [stderr] Run libapparmor testsuite (with python3) ... 
(Applying patch 
0001-mount-regression-test-convert-mount-test-to-use-MS_N.patch) (Applying 
patch 0001-usr-merge-fixups.patch) ok
+ 20:17:10 ERROR| [stderr] test_old_trusty_parser_testsuite 
(__main__.ApparmorTestsuites)
+ 20:17:10 DEBUG| [stdout]   preparing apparmor_2.12-4ubuntu5.1.dsc...  done
+ 20:17:10 ERROR| [stderr] Run parser regression tests from 14.04's 
apparmor_2.8.95~2430-0ubuntu5.3 ... (skipped: This test is only for 14.04 
systems with the apparmor 2.10.95 SRU or newer installed) ok
+ 20:17:10 ERROR| [stderr] test_old_trusty_regression_testsuite 
(__main__.ApparmorTestsuites)
+ 20:17:10 ERROR| [stderr] Run kernel regression tests from 14.04's 
apparmor_2.8.95~2430-0ubuntu5.3 ... (skipped: This test is only for 14.04 
systems with the apparmor 2.10.95 SRU or newer installed) ok
+ 20:17:10 ERROR| [stderr] test_parser_testsuite (__main__.ApparmorTestsuites)
+ 20:17:19 DEBUG| [stdout] 
+ 20:52:35 ERROR| [stderr] Run parser regression tests ... (Applying patch 
0001-mount-regression-test-convert-mount-test-to-use-MS_N.patch) (Applying 
patch 0001-usr-merge-fixups.patch) ok
+ 20:52:35 ERROR| [stderr] test_regression_testsuite 
(__main__.ApparmorTestsuites)
+ 20:52:42 DEBUG| [stdout]   preparing apparmor_2.12-4ubuntu5.1.dsc...  done
+ 20:52:42 DEBUG| [stdout] 
+ 21:01:56 INFO | ERROR   ubuntu_qrt_apparmor.test-apparmor.py  
  ubuntu_qrt_apparmor.test-apparmor.pytimestamp=1585256516localtime=Mar 
26 21:01:56   Test subprocess failed rc=9

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

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

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

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

Title:
  ubuntu_qrt_apparmor fails on ADT bionic/linux i386

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

Bug description:
  Testing failed on:
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/i386/l/linux/20200326_224620_0dd01@/log.gz

  Kernel version: bionic/linux 4.15.0-94.95

  The ubuntu_qrt_apparmor.test-apparmor.py fails intermittently on
  bionic/linux i386 ADT tests. It has failed some releases in the past
  and I'm seeing the failure in the current release as well. I have not
  seen this failure on other architectures.

  These are the last messages on the test log:
  20:12:39 ERROR| [stderr] Test mediation of file based SOCK_STREAM connect ... 
ok
  20:12:39 ERROR| [stderr] test_libapparmor_testsuite 
(__main__.ApparmorTestsuites)
  20:14:18 DEBUG| [stdout]   unconfined_user can access confined_user's file
  20:14:18 DEBUG| [stdout]   unconfined_user can access default_user's file
  20:14:18 DEBUG| [stdout]   unconfined_user can access unconfined_group's file
  20:14:18 DEBUG| [stdout] 
  20:15:42 ERROR| [stderr] Run libapparmor testsuite ... (Applying patch 
0001-mount-regression-test-convert-mount-test-to-use-MS_N.patch) (Applying 
patch 0001-usr-merge-fixups.patch) ok
  20:15:42 ERROR| [stderr] test_libapparmor_testsuite3 
(__main__.ApparmorTestsuites)
  20:15:52 DEBUG| [stdout]   preparing apparmor_2.12-4ubuntu5.1.dsc...  done
  20:15:52 DEBUG| [stdout] 
  20:17:10 ERROR| [stderr] Run libapparmor testsuite (with python3) ... 

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

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1869368

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

** Tags added: bionic

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

Title:
  ubuntu_qrt_apparmor fails on ADT bionic/linux i386

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

Bug description:
  Testing failed on:
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/i386/l/linux/20200326_224620_0dd01@/log.gz

  Kernel version: bionic/linux 4.15.0-94.95

  The ubuntu_qrt_apparmor.test-apparmor.py fails intermittently on
  bionic/linux i386 ADT tests. It has failed some releases in the past
  and I'm seeing the failure in the current release as well. I have not
  seen this failure on other architectures.

  These are the last messages on the test log:
  20:12:39 ERROR| [stderr] Test mediation of file based SOCK_STREAM connect ... 
ok
  20:12:39 ERROR| [stderr] test_libapparmor_testsuite 
(__main__.ApparmorTestsuites)
  20:14:18 DEBUG| [stdout]   unconfined_user can access confined_user's file
  20:14:18 DEBUG| [stdout]   unconfined_user can access default_user's file
  20:14:18 DEBUG| [stdout]   unconfined_user can access unconfined_group's file
  20:14:18 DEBUG| [stdout] 
  20:15:42 ERROR| [stderr] Run libapparmor testsuite ... (Applying patch 
0001-mount-regression-test-convert-mount-test-to-use-MS_N.patch) (Applying 
patch 0001-usr-merge-fixups.patch) ok
  20:15:42 ERROR| [stderr] test_libapparmor_testsuite3 
(__main__.ApparmorTestsuites)
  20:15:52 DEBUG| [stdout]   preparing apparmor_2.12-4ubuntu5.1.dsc...  done
  20:15:52 DEBUG| [stdout] 
  20:17:10 ERROR| [stderr] Run libapparmor testsuite (with python3) ... 
(Applying patch 
0001-mount-regression-test-convert-mount-test-to-use-MS_N.patch) (Applying 
patch 0001-usr-merge-fixups.patch) ok
  20:17:10 ERROR| [stderr] test_old_trusty_parser_testsuite 
(__main__.ApparmorTestsuites)
  20:17:10 DEBUG| [stdout]   preparing apparmor_2.12-4ubuntu5.1.dsc...  done
  20:17:10 ERROR| [stderr] Run parser regression tests from 14.04's 
apparmor_2.8.95~2430-0ubuntu5.3 ... (skipped: This test is only for 14.04 
systems with the apparmor 2.10.95 SRU or newer installed) ok
  20:17:10 ERROR| [stderr] test_old_trusty_regression_testsuite 
(__main__.ApparmorTestsuites)
  20:17:10 ERROR| [stderr] Run kernel regression tests from 14.04's 
apparmor_2.8.95~2430-0ubuntu5.3 ... (skipped: This test is only for 14.04 
systems with the apparmor 2.10.95 SRU or newer installed) ok
  20:17:10 ERROR| [stderr] test_parser_testsuite (__main__.ApparmorTestsuites)
  20:17:19 DEBUG| [stdout] 
  20:52:35 ERROR| [stderr] Run parser regression tests ... (Applying patch 
0001-mount-regression-test-convert-mount-test-to-use-MS_N.patch) (Applying 
patch 0001-usr-merge-fixups.patch) ok
  20:52:35 ERROR| [stderr] test_regression_testsuite 
(__main__.ApparmorTestsuites)
  20:52:42 DEBUG| [stdout]   preparing apparmor_2.12-4ubuntu5.1.dsc...  done
  20:52:42 DEBUG| [stdout] 
  21:01:56 INFO | ERROR   ubuntu_qrt_apparmor.test-apparmor.py  
  ubuntu_qrt_apparmor.test-apparmor.pytimestamp=1585256516localtime=Mar 
26 21:01:56   Test subprocess failed rc=9

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

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

[Kernel-packages] [Bug 1869368] [NEW] ubuntu_qrt_apparmor fails on ADT bionic/linux i386

[Kleber Sacilotto de Souza]

Public bug reported:

Testing failed on:
i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/i386/l/linux/20200326_224620_0dd01@/log.gz

Kernel version: bionic/linux 4.15.0-94.95

The ubuntu_qrt_apparmor.test-apparmor.py fails intermittently on
bionic/linux i386 ADT tests. It has failed some releases in the past and
I'm seeing the failure in the current release as well. I have not seen
this failure on other architectures.

These are the last messages on the test log:
20:12:39 ERROR| [stderr] Test mediation of file based SOCK_STREAM connect ... ok
20:12:39 ERROR| [stderr] test_libapparmor_testsuite 
(__main__.ApparmorTestsuites)
20:14:18 DEBUG| [stdout]   unconfined_user can access confined_user's file
20:14:18 DEBUG| [stdout]   unconfined_user can access default_user's file
20:14:18 DEBUG| [stdout]   unconfined_user can access unconfined_group's file
20:14:18 DEBUG| [stdout] 
20:15:42 ERROR| [stderr] Run libapparmor testsuite ... (Applying patch 
0001-mount-regression-test-convert-mount-test-to-use-MS_N.patch) (Applying 
patch 0001-usr-merge-fixups.patch) ok
20:15:42 ERROR| [stderr] test_libapparmor_testsuite3 
(__main__.ApparmorTestsuites)
20:15:52 DEBUG| [stdout]   preparing apparmor_2.12-4ubuntu5.1.dsc...  done
20:15:52 DEBUG| [stdout] 
20:17:10 ERROR| [stderr] Run libapparmor testsuite (with python3) ... (Applying 
patch 0001-mount-regression-test-convert-mount-test-to-use-MS_N.patch) 
(Applying patch 0001-usr-merge-fixups.patch) ok
20:17:10 ERROR| [stderr] test_old_trusty_parser_testsuite 
(__main__.ApparmorTestsuites)
20:17:10 DEBUG| [stdout]   preparing apparmor_2.12-4ubuntu5.1.dsc...  done
20:17:10 ERROR| [stderr] Run parser regression tests from 14.04's 
apparmor_2.8.95~2430-0ubuntu5.3 ... (skipped: This test is only for 14.04 
systems with the apparmor 2.10.95 SRU or newer installed) ok
20:17:10 ERROR| [stderr] test_old_trusty_regression_testsuite 
(__main__.ApparmorTestsuites)
20:17:10 ERROR| [stderr] Run kernel regression tests from 14.04's 
apparmor_2.8.95~2430-0ubuntu5.3 ... (skipped: This test is only for 14.04 
systems with the apparmor 2.10.95 SRU or newer installed) ok
20:17:10 ERROR| [stderr] test_parser_testsuite (__main__.ApparmorTestsuites)
20:17:19 DEBUG| [stdout] 
20:52:35 ERROR| [stderr] Run parser regression tests ... (Applying patch 
0001-mount-regression-test-convert-mount-test-to-use-MS_N.patch) (Applying 
patch 0001-usr-merge-fixups.patch) ok
20:52:35 ERROR| [stderr] test_regression_testsuite (__main__.ApparmorTestsuites)
20:52:42 DEBUG| [stdout]   preparing apparmor_2.12-4ubuntu5.1.dsc...  done
20:52:42 DEBUG| [stdout] 
21:01:56 INFO | ERROR   ubuntu_qrt_apparmor.test-apparmor.py
ubuntu_qrt_apparmor.test-apparmor.pytimestamp=1585256516localtime=Mar 
26 21:01:56   Test subprocess failed rc=9

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

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

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Status: Confirmed


** Tags: bionic kernel-adt-failure

** Tags added: kernel-adt-failure

** Description changed:

  Testing failed on:
- i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/i386/l/linux/20200326_224620_0dd01@/log.gz
- ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/l/linux/20200326_171753_5e0d2@/log.gz
- s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/l/linux/20200326_165651_dc1a0@/log.gz
+ i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/i386/l/linux/20200326_224620_0dd01@/log.gz

** Summary changed:

- linux 4.15.0-94.95 ADT test failure with linux 4.15.0-94.95
+ ubuntu_qrt_apparmor fails on bionic/linux i386

** Summary changed:

- ubuntu_qrt_apparmor fails on bionic/linux i386
+ ubuntu_qrt_apparmor fails on ADT bionic/linux i386

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

Title:
  ubuntu_qrt_apparmor fails on ADT bionic/linux i386

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

Bug description:
  Testing failed on:
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/i386/l/linux/20200326_224620_0dd01@/log.gz

  Kernel version: bionic/linux 4.15.0-94.95

  The ubuntu_qrt_apparmor.test-apparmor.py fails intermittently on
  bionic/linux i386 ADT tests. It has failed some releases in the past
  and I'm seeing the failure in 

[Kernel-packages] [Bug 1869235] [NEW] Ryzen 3rd gen (3900X) ECC support missing from kernel

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Ubuntu server:
Description:Ubuntu 19.10
Release:19.10
Installed kernel:
linux-generic:
  Installed: 5.3.0.42.36
(I could not figure out what package to select in the 'in what package did you 
find this bug' chooser)

Expected behavior: ECC RAM is detected and utilized
Result instead:
Error in dmesg at boot:
EDAC amd64: Error: F0 not found, device 0x1460 (broken BIOS?) (more in the 
attached KernelErrors.log)

Kernel 5.3 is missing ECC support for some families of AMD Ryzen 3rd gen
CPUs.

Support is added via these two commits in the mainline tree:
https://github.com/torvalds/linux/commit/e53a3b267fb0a79db9ca1f1e08b97889b22013e6
https://github.com/torvalds/linux/commit/3e443eb353eda6f4b4796e07f2599683fa752f1d

The second commit actually adds the missing support, but it relies on
the first commit: a partial refactor of the AMD ECC code.

I tested myself, followed the instructions at 
https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel to build my own kernel, 
cherry-picked the two above commits, and have working ECC support on my 
self-built kernel:
Linux smaug 5.3.0-43-generic #36 SMP Sat Mar 21 02:33:30 UTC 2020 x86_64 x86_64 
x86_64 GNU/Linux:

EDAC MC: Ver: 3.0.0
EDAC amd64: Node 0: DRAM ECC enabled.
EDAC amd64: F17h_M70h detected (node 0).
EDAC MC: UMC0 chip selects:
EDAC amd64: MC: 0: 0MB 1: 0MB
EDAC amd64: MC: 2: 16384MB 3: 16384MB
EDAC MC: UMC1 chip selects:
EDAC amd64: MC: 0: 0MB 1: 0MB
EDAC amd64: MC: 2: 16384MB 3: 16384MB
EDAC amd64: using x16 syndromes.
EDAC amd64: MCT channel count: 2
EDAC MC0: Giving out device to module amd64_edac controller F17h_M70h: DEV 
:00:18.3 (INTERRUPT)
EDAC PCI0: Giving out device to module amd64_edac controller EDAC PCI 
controller: DEV :00:18.0 (POLLED)
AMD64 EDAC driver v3.5.0


If this could be included in a future hardware support kernel release, that 
would be very helpful.  I am unsure what the policy is for including this kind 
of backport in non-LTS kernels, though I know the LTS releases have hardware 
support updates that include this type of fix.

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


** Tags: bot-comment
-- 
Ryzen 3rd gen (3900X) ECC support missing from kernel
https://bugs.launchpad.net/bugs/1869235
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 1863222] Re: Sync hwdata 0.333-1 (main) from Debian unstable (main)

[Sebastien Bacher]

This bug was fixed in the package hwdata - 0.333-1
Sponsored for Amr Ibrahim (amribrahim1987)

---
hwdata (0.333-1) unstable; urgency=medium

  * New upstream release: (Closes: #947191)
- pnp.ids: update Goldstar to LG Electronics (Closes: #95)

 -- Pino Toscano   Thu, 12 Mar 2020 06:45:31 +0100

** Changed in: hwdata (Ubuntu)
   Status: New => Fix Released

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

Title:
  Sync hwdata 0.333-1 (main) from Debian unstable (main)

Status in hwdata package in Ubuntu:
  Fix Released
Status in hwdata package in Debian:
  New

Bug description:
  Please sync hwdata 0.333-1 (main) from Debian unstable (main)

  It has updated packaging and newer IDs useful for the new LTS.

  Explanation of the Ubuntu delta and why it can be dropped:
* debian/rules:
  - don't install deprecated changelog

  The Ubuntu delta can be dropped because it's already in the Debian
  package.

  Changelog entries since current focal version 0.317-0ubuntu2:

  hwdata (0.333-1) unstable; urgency=medium

* New upstream release: (Closes: #947191)
  - pnp.ids: update Goldstar to LG Electronics (Closes: #95)

   -- Pino Toscano   Thu, 12 Mar 2020 06:45:31 +0100

  hwdata (0.290-2) unstable; urgency=medium

* Take over the maintainership from Noël Köthe, with his permission.
  Thanks for maintaining hwdata so far!
* Add the configuration for the CI on salsa.
* Stop shipping, and installing, a ChangeLog file generated from the 
upstream Git repository, as it is not useful.
* Move the installation of pnp.ids to a hwdata.install file, instead of
  copying it manually.
* Move the symlinks creation to a hwdata.links file, instead of passing 
them as arguments of dh_link.
* Stop patching usb.ids, as we do not ship it anyway.
* Switch source format to "3.0 (quilt)".
* Bump the debhelper compatibility to 12:
  - switch the debhelper build dependency to debhelper-compat 12
  - remove debian/compat
* Rewrite rules to the dh sequencer, with no specific buildsystem.
* Remove dirs file, as the right directories are automatically created.
* Stop using the ${shlibs:Depends} substvar, as it does not exist in 
arch:all binaries.
* Upstream moved to GitHub, so:
  - switch Homepage to https://github.com/vcrhonek/hwdata
  - switch watch file to GitHub tags
* Add Vcs-* fields.
* Remove README.build, as we do not ship usb.ids.
* Remove trailing whitespaces in changelog.
* Bump Standards-Version to 4.5.0, no changes required.
* Mark hwdata as Multi-Arch: foreign.
* Set Rules-Requires-Root: no.

   -- Pino Toscano   Fri, 06 Mar 2020 20:47:41 +0100

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

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