[Kernel-packages] [Bug 1854480] Re: zfs_arc_max not working anymore in zfs 0.8.1

[Colin Ian King]

I've experimented with this on eoan and focal (ZFS 0.8.1 and ZFS 0.8.3)
on a 4GB VM image.  I set the /etc/modprobe.d/zfs.conf as follows:

options zfs zfs_arc_max=134217728
# 128 MB

And rebooted.  I then exercised the zfs with various greps and git logs
on the linux git repository while running:

while true; do cat /proc/spl/kstat/zfs/arcstats | grep -m 1 size | awk
'{ print $3 / (1024 * 1024) }'; sleep 1; done

The output shows that one does get arc sizes greater than the 128MB
while doing a lot of I/O but it settles down to sub 128MB once the I/O
activity is finished:

2.93295
2.93295
2.93295
63.8354
131.395
127.909
148.942
128.498
138.224
145.271
133.244
134.122
138.132
144.814
129.4
134.788
135.666
140.428
143.811
146.734
132.323
136.709
143.225
143.225
143.225
143.225
143.225
143.225
143.225
143.225
143.225
143.225
143.225
143.225
143.225
143.225
143.225
143.225
143.225
143.225
143.225
130.353
130.34
130.34
130.34
138.63
140.16
139.826
139.826
139.826
139.921
139.921
133.32
122.35
115.929
111.941
110.478
111.219
111.219

Two observations:

1. The driver does some sanity checks; if zfs_arc_max is too small (<
64MB) or too large (> physical memory size) then the setting is ignored
and the default is used.  One can double check if the setting has been
updated by checking with c_max, e.g.:

grep c_max /proc/spl/kstat/zfs/arcstats
c_max   4134217728

If c_max is not the same as zfs_arc_max then the zfs_arc_max has worked.
Can you sanity check that?

2. With a high amount of throughput the arcstats show that the "size"
stat can overshot the zfs_arc_max setting but once I/O has completed it
will setting down to the threshold set.  This setting is not updated
directly and is only sync'd during an arc_kstat update. So maybe it's a
snapshot that maybe transient and possibly not completely up to date.
Keeping the stats exactly up to date would cause a performance
bottleneck, so the stats are aggregated - I believe these values are not
exactly 100% correct as there is a performance impact in gathering and
summing the stats.

Perhaps you could experiment with a low zfs_arc_max setting (e.g. 128MB
134217728) and see if this works OK and then bumping up the value to see
if it stops working; then we can work out why it's going wrong at that
point.

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

Title:
  zfs_arc_max not working anymore in zfs 0.8.1

Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  In the past I could limit the size of L1ARC by specifying "options zfs
  zfs_arc_max=3221225472" in /etc/modprobe.d/zfs.conf. I tried even to
  fill /sys/module/zfs/parameters/zfs_arc_max directly, but none of
  those methods limits the size of L1ARC. It worked nicely in zfs 0.7.x.

  Nowadays I use a nvme drive with 3400 MB/s read throughput and I see
  not much difference between e.g booting the system from nvme and
  rebooting the system from L1ARC. Having a 96-99% hit rate for the
  L1ARC, I like to free up some memory, thus avoiding some delay of
  freeing memory from L1ARC while loading a VM.

  -
  UPDATE:

  The system only limits the L1ARC, if we directly after the login write
  the zfs_arc_max value to the file
  /sys/module/zfs/parameters/zfs_arc_max.

  

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: zfsutils-linux 0.8.1-1ubuntu14.1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 29 06:19:15 2019
  InstallationDate: Installed on 2019-11-25 (3 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission 
denied: '/etc/sudoers.d/zfs']

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

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

[Kernel-packages] [Bug 1869080] [NEW] White noise during sound playing and after sound stopped for 5 seconds in headphones

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I have an Ubuntu 18.04 installed on my DELL 7490 laptop.
Kernel version is: 5.3.0-40-generic

When I plug in one of my headphones and start to play sound I
immediately start to hear white noise in the earphone. After I stop the
music the white noise still remains for 5 more seconds, after 5 seconds
it stops.

I tried with different headphones, the only difference between them is
the volume of the white noise.

I tried several ways to fix the problem but without any luck.

lspci -nnk | grep -iA2 audio output:
00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio 
[8086:9d71] (rev 21)
Subsystem: Dell Sunrise Point-LP HD Audio [1028:081c]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl
sudo aplay -l output:
 List of PLAYBACK Hardware Devices 
card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Thanks for your help in advance!

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


** Tags: alc3246 bot-comment dell headphones hiss noise white
-- 
White noise during sound playing and after sound stopped for 5 seconds in 
headphones
https://bugs.launchpad.net/bugs/1869080
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 1869080] Re: White noise during sound playing and after sound stopped for 5 seconds in headphones

[Brian Murray]

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

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

Title:
  White noise during sound playing and after sound stopped for 5 seconds
  in headphones

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have an Ubuntu 18.04 installed on my DELL 7490 laptop.
  Kernel version is: 5.3.0-40-generic

  When I plug in one of my headphones and start to play sound I
  immediately start to hear white noise in the earphone. After I stop
  the music the white noise still remains for 5 more seconds, after 5
  seconds it stops.

  I tried with different headphones, the only difference between them is
  the volume of the white noise.

  I tried several ways to fix the problem but without any luck.

  lspci -nnk | grep -iA2 audio output:
  00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio 
[8086:9d71] (rev 21)
  Subsystem: Dell Sunrise Point-LP HD Audio [1028:081c]
  Kernel driver in use: snd_hda_intel
  Kernel modules: snd_hda_intel, snd_soc_skl
  sudo aplay -l output:
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  Thanks for your help in advance!

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

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

[Kernel-packages] [Bug 1849981] Re: package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10

[Colin Ian King]

If you are using the latest ZFS the drivers are built into the kernel so
the zfs-dkms package should be removed.

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

Title:
  package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed
  zfs-dkms package post-installation script subprocess returned error
  exit status 10

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  Was upgrading to 19.10 and encountered this

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: zfs-dkms 0.8.1-1ubuntu14
  ProcVersionSignature: Ubuntu 5.0.0-30.32-generic 5.0.21
  Uname: Linux 5.0.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  Date: Sat Oct 26 10:28:20 2019
  ErrorMessage: installed zfs-dkms package post-installation script subprocess 
returned error exit status 10
  InstallationDate: Installed on 2013-06-08 (2331 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  SourcePackage: zfs-linux
  Title: package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed 
zfs-dkms package post-installation script subprocess returned error exit status 
10
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (0 days ago)

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

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

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

[zsambek]

apport information

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

Title:
  White noise during sound playing and after sound stopped for 5 seconds
  in headphones

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an Ubuntu 18.04 installed on my DELL 7490 laptop.
  Kernel version is: 5.3.0-40-generic

  When I plug in one of my headphones and start to play sound I
  immediately start to hear white noise in the earphone. After I stop
  the music the white noise still remains for 5 more seconds, after 5
  seconds it stops.

  I tried with different headphones, the only difference between them is
  the volume of the white noise.

  I tried several ways to fix the problem but without any luck.

  lspci -nnk | grep -iA2 audio output:
  00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio 
[8086:9d71] (rev 21)
  Subsystem: Dell Sunrise Point-LP HD Audio [1028:081c]
  Kernel driver in use: snd_hda_intel
  Kernel modules: snd_hda_intel, snd_soc_skl
  sudo aplay -l output:
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  Thanks for your help in advance!


  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zsambek2196 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-20 (34 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 7490
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-42-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-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.173.16
  Tags:  bionic
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/08/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.1
  dmi.board.name: 0PP44F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.1:bd11/08/2019:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0PP44F:rvrA02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7490
  dmi.product.sku: 081C
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1869080] RfKill.txt

[zsambek]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1869080/+attachment/5341863/+files/RfKill.txt

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

Title:
  White noise during sound playing and after sound stopped for 5 seconds
  in headphones

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an Ubuntu 18.04 installed on my DELL 7490 laptop.
  Kernel version is: 5.3.0-40-generic

  When I plug in one of my headphones and start to play sound I
  immediately start to hear white noise in the earphone. After I stop
  the music the white noise still remains for 5 more seconds, after 5
  seconds it stops.

  I tried with different headphones, the only difference between them is
  the volume of the white noise.

  I tried several ways to fix the problem but without any luck.

  lspci -nnk | grep -iA2 audio output:
  00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio 
[8086:9d71] (rev 21)
  Subsystem: Dell Sunrise Point-LP HD Audio [1028:081c]
  Kernel driver in use: snd_hda_intel
  Kernel modules: snd_hda_intel, snd_soc_skl
  sudo aplay -l output:
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  Thanks for your help in advance!


  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zsambek2196 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-20 (34 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 7490
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-42-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-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.173.16
  Tags:  bionic
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/08/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.1
  dmi.board.name: 0PP44F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.1:bd11/08/2019:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0PP44F:rvrA02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7490
  dmi.product.sku: 081C
  dmi.sys.vendor: Dell Inc.

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

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

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

[zsambek]

apport information

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

Title:
  White noise during sound playing and after sound stopped for 5 seconds
  in headphones

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an Ubuntu 18.04 installed on my DELL 7490 laptop.
  Kernel version is: 5.3.0-40-generic

  When I plug in one of my headphones and start to play sound I
  immediately start to hear white noise in the earphone. After I stop
  the music the white noise still remains for 5 more seconds, after 5
  seconds it stops.

  I tried with different headphones, the only difference between them is
  the volume of the white noise.

  I tried several ways to fix the problem but without any luck.

  lspci -nnk | grep -iA2 audio output:
  00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio 
[8086:9d71] (rev 21)
  Subsystem: Dell Sunrise Point-LP HD Audio [1028:081c]
  Kernel driver in use: snd_hda_intel
  Kernel modules: snd_hda_intel, snd_soc_skl
  sudo aplay -l output:
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  Thanks for your help in advance!


  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zsambek2196 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-20 (34 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 7490
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-42-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-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.173.16
  Tags:  bionic
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/08/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.1
  dmi.board.name: 0PP44F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.1:bd11/08/2019:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0PP44F:rvrA02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7490
  dmi.product.sku: 081C
  dmi.sys.vendor: Dell Inc.

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

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

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

[zsambek]

apport information

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

Title:
  White noise during sound playing and after sound stopped for 5 seconds
  in headphones

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an Ubuntu 18.04 installed on my DELL 7490 laptop.
  Kernel version is: 5.3.0-40-generic

  When I plug in one of my headphones and start to play sound I
  immediately start to hear white noise in the earphone. After I stop
  the music the white noise still remains for 5 more seconds, after 5
  seconds it stops.

  I tried with different headphones, the only difference between them is
  the volume of the white noise.

  I tried several ways to fix the problem but without any luck.

  lspci -nnk | grep -iA2 audio output:
  00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio 
[8086:9d71] (rev 21)
  Subsystem: Dell Sunrise Point-LP HD Audio [1028:081c]
  Kernel driver in use: snd_hda_intel
  Kernel modules: snd_hda_intel, snd_soc_skl
  sudo aplay -l output:
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  Thanks for your help in advance!


  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zsambek2196 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-20 (34 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 7490
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-42-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-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.173.16
  Tags:  bionic
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/08/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.1
  dmi.board.name: 0PP44F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.1:bd11/08/2019:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0PP44F:rvrA02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7490
  dmi.product.sku: 081C
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1869229] Re: Mounting LVM snapshots with xfs can hit kernel BUG in nvme driver

[Heitor Alves de Siqueira]

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Heitor Alves de Siqueira (halves)

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

Title:
  Mounting LVM snapshots with xfs can hit kernel BUG in nvme driver

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Confirmed

Bug description:
  [Impact]
  When mounting LVM snapshots using xfs, it's possible to hit a BUG_ON() in 
nvme driver.

  Upstream commit 729204ef49ec ("block: relax check on sg gap")
  introduced a way to merge bios if they are physically contiguous. This
  can lead to issues if one rq starts with a non-aligned buffer, as it
  can cause the merged segment to end in an unaligned virtual boundary.
  In some AWS instances, it's possible to craft such a request when
  attempting to mount LVM snapshots using xfs. This will then cause a
  kernel spew due to a BUG_ON in nvme_setup_prps(), which checks if
  dma_len is aligned to the page size.

  [Fix]
  Upstream commit 5a8d75a1b8c9 ("block: fix bio_will_gap() for first bvec with 
offset") disallows requests that begin with an unaligned buffer from being 
merged.

  [Test Case]
  This has been verified on AWS with c5d.large instances:

  1) Prepare the LVM device + snapshot
  $ sudo vgcreate vg0 /dev/nvme1n1
  $ sudo lvcreate -L5G -n data0 vg0
  $ sudo mkfs.xfs /dev/vg0/data0
  $ sudo mount /dev/vg0/data0 /mnt
  $ sudo touch /mnt/test
  $ sudo touch /mnt/test2
  $ sudo ls /mnt
  $ sudo umount /mnt
  $ sudo lvcreate -l100%FREE -s /dev/vg0/data0 -n data0_snap

  2) Attempting to mount the previously created snapshot results in the Oops:
  $ sudo mount /dev/vg0/data0_snap /mnt 
  Segmentation fault (core dumped)

  [Regression Potential]
  The fix prevents some bios from being merged, so it can have a performance 
impact in certain scenarios. The patch only targets misaligned segments, so the 
impact should be less noticeable in the general case.
  The commit is also present in mainline kernels since 4.13, and hasn't been 
changed significantly, so potential for other regressions should be low.

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

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

[Kernel-packages] [Bug 1868551] Re: Screen freezes : NULL pointer dereference i915_active_acquire since Linux 5.4

[Guy Baconniere]

I did not manage to compile the kernel the Ubuntu way
https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel
Is this doc still relevant for Linux 5.4 and 20.04 / Focal?

I included the patch I ported to the latest version of ubuntu-focal
git clone git://kernel.ubuntu.com/ubuntu/ubuntu-focal.git

** Patch added: "ubuntu-focal-1868551-i915_active_acquire.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868551/+attachment/5341878/+files/ubuntu-focal-1868551-i915_active_acquire.patch

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

Title:
  Screen freezes : NULL pointer dereference i915_active_acquire since
  Linux 5.4

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  uname -a
  Linux xps 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux

  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  Codename: focal

  [ 2556.956079] BUG: kernel NULL pointer dereference, address: 0040
  [ 2556.956084] #PF: supervisor read access in kernel mode
  [ 2556.956084] #PF: error_code(0x) - not-present page
  [ 2556.956085] PGD 0 P4D 0 
  [ 2556.956088] Oops:  [#1] SMP NOPTI
  [ 2556.956090] CPU: 2 PID: 1685 Comm: xfwm4 Not tainted 5.4.0-14-generic 
#17-Ubuntu
  [ 2556.956092] Hardware name: Dell Inc. XPS 13 7390/0G2D0W, BIOS 1.2.0 
10/03/2019
  [ 2556.956161] RIP: 0010:i915_active_acquire+0xe/0x80 [i915]
  [ 2556.956163] Code: 00 48 c7 c6 11 4d 6b c0 e8 af a1 d6 c7 5d c3 66 66 2e 0f 
1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 <8b> 47 38 
48 89 fb 85 c0 74 17 8d 50 01 f0 0f b1 53 38 75 f2 45 31
  [ 2556.956164] RSP: 0018:ac17c13279c8 EFLAGS: 00010286
  [ 2556.956165] RAX:  RBX: 983831d3e480 RCX: 

  [ 2556.956166] RDX: 983783475200 RSI: 983831d3e480 RDI: 
0008
  [ 2556.956167] RBP: ac17c13279e0 R08:  R09: 
98382d6b6520
  [ 2556.956168] R10: 6cc0 R11: 983838b4db00 R12: 
983783475200
  [ 2556.956169] R13: 0008 R14: 983783475200 R15: 
98382d6b6400
  [ 2556.956170] FS:  7f9031c28f00() GS:98383e50() 
knlGS:
  [ 2556.956171] CS:  0010 DS:  ES:  CR0: 80050033
  [ 2556.956172] CR2: 0040 CR3: 00046eac6001 CR4: 
003606e0
  [ 2556.956173] Call Trace:
  [ 2556.956199]  i915_active_ref+0x24/0x200 [i915]
  [ 2556.956223]  i915_vma_move_to_active+0x74/0xf0 [i915]
  [ 2556.956245]  eb_submit+0xff/0x440 [i915]
  [ 2556.956267]  i915_gem_do_execbuffer+0x88e/0xc20 [i915]
  [ 2556.956271]  ? sock_def_readable+0x40/0x70
  [ 2556.956274]  ? __kmalloc_node+0x205/0x320
  [ 2556.956294]  i915_gem_execbuffer2_ioctl+0x2c3/0x3d0 [i915]
  [ 2556.956314]  ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915]
  [ 2556.956330]  drm_ioctl_kernel+0xae/0xf0 [drm]
  [ 2556.956338]  drm_ioctl+0x234/0x3d0 [drm]
  [ 2556.956358]  ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915]
  [ 2556.956361]  ? vfs_writev+0xc3/0xf0
  [ 2556.956363]  do_vfs_ioctl+0x407/0x670
  [ 2556.956365]  ? fput+0x13/0x15
  [ 2556.956367]  ? __sys_recvmsg+0x88/0xa0
  [ 2556.956369]  ksys_ioctl+0x67/0x90
  [ 2556.956371]  __x64_sys_ioctl+0x1a/0x20
  [ 2556.956373]  do_syscall_64+0x57/0x190
  [ 2556.956376]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [ 2556.956377] RIP: 0033:0x7f9032b3f68b
  [ 2556.956379] Code: 0f 1e fa 48 8b 05 05 28 0d 00 64 c7 00 26 00 00 00 48 c7 
c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d d5 27 0d 00 f7 d8 64 89 01 48
  [ 2556.956380] RSP: 002b:7ffee39a0078 EFLAGS: 0246 ORIG_RAX: 
0010
  [ 2556.956381] RAX: ffda RBX: 55a8abeb6e48 RCX: 
7f9032b3f68b
  [ 2556.956382] RDX: 7ffee39a0090 RSI: 40406469 RDI: 
000d
  [ 2556.956382] RBP: 7ffee39a0120 R08: 0001 R09: 

  [ 2556.956383] R10: 7ffee39a0140 R11: 0246 R12: 
7f9022a4f460
  [ 2556.956384] R13:  R14: 7ffee39a0090 R15: 
000d
  [ 2556.956385] Modules linked in: ccm rfcomm xt_CHECKSUM xt_MASQUERADE 
xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat 
typec_displayport iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 nf_tables cmac nfnetlink algif_hash ip6table_filter ip6_tables 
iptable_filter algif_skcipher af_alg bpfilter bridge stp llc snd_sof_pci 
snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt 
snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi snd_hda_codec_hdmi snd_soc_core 
snd_compress ac97_bus snd_pcm_dmaengine bnep snd_hda_codec_realtek 

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

[Solomon Nadar]

Missed the UVD part. Seems that is fixed.

@Aspire-E1-572G:~$ dmesg |grep UVD
[2.273739] [drm] UVD initialized successfully.
[   27.022685] [drm] UVD initialized successfully.
[   37.101343] [drm] UVD initialized successfully.
[  582.474512] [drm] UVD initialized successfully.

-- 
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] 

[Kernel-packages] [Bug 1869229] [NEW] Mounting LVM snapshots with xfs can hit kernel BUG in nvme driver

[Heitor Alves de Siqueira]

Public bug reported:

[Impact]
When mounting LVM snapshots using xfs, it's possible to hit a BUG_ON() in nvme 
driver.

Upstream commit 729204ef49ec ("block: relax check on sg gap") introduced
a way to merge bios if they are physically contiguous. This can lead to
issues if one rq starts with a non-aligned buffer, as it can cause the
merged segment to end in an unaligned virtual boundary. In some AWS
instances, it's possible to craft such a request when attempting to
mount LVM snapshots using xfs. This will then cause a kernel spew due to
a BUG_ON in nvme_setup_prps(), which checks if dma_len is aligned to the
page size.

[Fix]
Upstream commit 5a8d75a1b8c9 ("block: fix bio_will_gap() for first bvec with 
offset") disallows requests that begin with an unaligned buffer from being 
merged.

[Test Case]
This has been verified on AWS with c5d.large instances:

1) Prepare the LVM device + snapshot
$ sudo vgcreate vg0 /dev/nvme1n1
$ sudo lvcreate -L5G -n data0 vg0
$ sudo mkfs.xfs /dev/vg0/data0
$ sudo mount /dev/vg0/data0 /mnt
$ sudo touch /mnt/test
$ sudo touch /mnt/test2
$ sudo ls /mnt
$ sudo umount /mnt
$ sudo lvcreate -l100%FREE -s /dev/vg0/data0 -n data0_snap

2) Attempting to mount the previously created snapshot results in the Oops:
$ sudo mount /dev/vg0/data0_snap /mnt 
Segmentation fault (core dumped)

[Regression Potential]
The fix prevents some bios from being merged, so it can have a performance 
impact in certain scenarios. The patch only targets misaligned segments, so the 
impact should be less noticeable in the general case.
The commit is also present in mainline kernels since 4.13, and hasn't been 
changed significantly, so potential for other regressions should be low.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Fix Released

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


** Tags: sts

** Changed in: linux (Ubuntu)
 Assignee: Heitor Alves de Siqueira (halves) => (unassigned)

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

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

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

Title:
  Mounting LVM snapshots with xfs can hit kernel BUG in nvme driver

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  New

Bug description:
  [Impact]
  When mounting LVM snapshots using xfs, it's possible to hit a BUG_ON() in 
nvme driver.

  Upstream commit 729204ef49ec ("block: relax check on sg gap")
  introduced a way to merge bios if they are physically contiguous. This
  can lead to issues if one rq starts with a non-aligned buffer, as it
  can cause the merged segment to end in an unaligned virtual boundary.
  In some AWS instances, it's possible to craft such a request when
  attempting to mount LVM snapshots using xfs. This will then cause a
  kernel spew due to a BUG_ON in nvme_setup_prps(), which checks if
  dma_len is aligned to the page size.

  [Fix]
  Upstream commit 5a8d75a1b8c9 ("block: fix bio_will_gap() for first bvec with 
offset") disallows requests that begin with an unaligned buffer from being 
merged.

  [Test Case]
  This has been verified on AWS with c5d.large instances:

  1) Prepare the LVM device + snapshot
  $ sudo vgcreate vg0 /dev/nvme1n1
  $ sudo lvcreate -L5G -n data0 vg0
  $ sudo mkfs.xfs /dev/vg0/data0
  $ sudo mount /dev/vg0/data0 /mnt
  $ sudo touch /mnt/test
  $ sudo touch /mnt/test2
  $ sudo ls /mnt
  $ sudo umount /mnt
  $ sudo lvcreate -l100%FREE -s /dev/vg0/data0 -n data0_snap

  2) Attempting to mount the previously created snapshot results in the Oops:
  $ sudo mount /dev/vg0/data0_snap /mnt 
  Segmentation fault (core dumped)

  [Regression Potential]
  The fix prevents some bios from being merged, so it can have a performance 
impact in certain scenarios. The patch only targets misaligned segments, so the 
impact should be less noticeable in the general case.
  The commit is also present in mainline kernels since 4.13, and hasn't been 
changed significantly, so potential for other regressions should be low.

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

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

[Kernel-packages] [Bug 1832088] Re: zpool import -f throws kernel Ooops

[Colin Ian King]

There has been no update, so I'm closing this bug. If this is still is
an issue, please re-open this bug.

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

Title:
  zpool import -f throws kernel Ooops

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

Bug description:
  I believe this started with the upgrade from 5.0.0-15-generic to
  5.0.0-16-generic.

  I'm running a ZFS RAID2 pool and one of the drives is faulted.  I
  rebooted under 5.0.0-16-generic and the pool won't import, even with
  '-f'.  zpool emits a kernel oops spa_load and any zfs tools run after
  that just hangs (the system itself seems fine otherwise).

  Trace included just incase the bug tool didn't pick it up.

  [ 1365.610907] BUG: unable to handle kernel NULL pointer dereference at 

  [ 1365.610980] #PF error: [normal kernel read fault]
  [ 1365.611017] PGD 0 P4D 0
  [ 1365.611042] Oops:  [#1] SMP PTI
  [ 1365.611073] CPU: 2 PID: 5945 Comm: zpool Tainted: P   O  
5.0.0-16-generic #17-Ubuntu
  [ 1365.611139] Hardware name: Supermicro A1SRM-2758F/A1SRM-2758F, BIOS 2.1 
01/19/2018
  [ 1365.611270] RIP: 0010:spa_config_valid_zaps+0x43/0x70 [zfs]
  [ 1365.611315] Code: 00 00 48 8b 86 e0 26 00 00 48 89 87 e0 26 00 00 74 42 55 
48 89 e5 41 55 49 89 f5 41 54 49 89 fc 53 31 db 49 8b 85 88 00 00 00 <48> 8b 34 
d8 49 8b 84 24 88 00 00 00 48 8b 3c d8 48 83 c3 01 e8 a4
  [ 1365.611450] RSP: 0018:b59d43bc7c48 EFLAGS: 00010246
  [ 1365.611492] RAX:  RBX:  RCX: 
1485
  [ 1365.611546] RDX: 9fa181649780 RSI: 9fa1986d4000 RDI: 
9fa17bdcc000
  [ 1365.611600] RBP: b59d43bc7c60 R08: 00027060 R09: 
c0bd5f53
  [ 1365.611653] R10: dda120059240 R11: 9fa1986a8000 R12: 
9fa17bdcc000
  [ 1365.611707] R13: 9fa1986d4000 R14: 9fa17bd94000 R15: 
9fa1986d4000
  [ 1365.611761] FS:  7f8c91465780() GS:9fa1dfa8() 
knlGS:
  [ 1365.611822] CS:  0010 DS:  ES:  CR0: 80050033
  [ 1365.611866] CR2:  CR3: 0007fccd2000 CR4: 
001006e0
  [ 1365.611920] Call Trace:
  [ 1365.612021]  spa_load+0x14b4/0x21e0 [zfs]
  [ 1365.612121]  spa_tryimport+0xaa/0x450 [zfs]
  [ 1365.612217]  zfs_ioc_pool_tryimport+0x64/0xc0 [zfs]
  [ 1365.612317]  zfsdev_ioctl+0x54e/0x630 [zfs]
  [ 1365.612357]  do_vfs_ioctl+0xa9/0x640
  [ 1365.612391]  ? handle_mm_fault+0xe1/0x210
  [ 1365.612426]  ksys_ioctl+0x67/0x90
  [ 1365.612456]  __x64_sys_ioctl+0x1a/0x20
  [ 1365.612489]  do_syscall_64+0x5a/0x110
  [ 1365.612522]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [ 1365.612563] RIP: 0033:0x7f8c915b3417
  [ 1365.612595] Code: 00 00 90 48 8b 05 79 0a 0d 00 64 c7 00 26 00 00 00 48 c7 
c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d 49 0a 0d 00 f7 d8 64 89 01 48
  [ 1365.612731] RSP: 002b:7fff14f9fd78 EFLAGS: 0246 ORIG_RAX: 
0010
  [ 1365.612790] RAX: ffda RBX: 7fff14f9fd90 RCX: 
7f8c915b3417
  [ 1365.612844] RDX: 7fff14f9fd90 RSI: 5a06 RDI: 
0003
  [ 1365.612897] RBP: 559b69acc160 R08: 559b69ae4af0 R09: 
0800
  [ 1365.612952] R10: f000 R11: 0246 R12: 
559b69ace1e0
  [ 1365.613005] R13: 559b69ada6f0 R14: 7fff14fa3410 R15: 
7fff14fa3458
  [ 1365.613062] Modules linked in: zfs(PO) zunicode(PO) zavl(PO) icp(PO) 
zcommon(PO) znvpair(PO) spl(O) xt_nat xt_tcpudp veth ipt_MASQUERADE 
nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat_ipv4 
xt_addrtype iptable_filter bpfilter xt_conntrack nf_nat nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter bridge stp llc aufs overlay 
nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif 
joydev input_leds intel_powerclamp kvm_intel kvm irqbypass crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel intel_cstate ipmi_si ipmi_devintf mac_hid 
ipmi_msghandler sch_fq_codel nfsd auth_rpcgss nfs_acl lockd grace sunrpc 
ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi coretemp ip_tables x_tables autofs4 xfs btrfs 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid 
hid ast ttm aesni_intel uas aes_x86_64 drm_kms_helper
  [ 1365.613113]  syscopyarea usb_storage crypto_simd sysfillrect gpio_ich 
sysimgblt cryptd fb_sys_fops glue_helper ahci lpc_ich igb mpt3sas libahci 
i2c_i801 dca drm raid_class i2c_algo_bit scsi_transport_sas i2c_ismt
  [ 1365.624209] CR2: 
  [ 1365.626489] ---[ end trace b55794841dc1b04f ]---
  [ 1365.720954] RIP: 0010:spa_config_valid_zaps+0x43/0x70 [zfs]
  [ 1365.720957] 

[Kernel-packages] [Bug 1869080] 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 1869080

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

Title:
  White noise during sound playing and after sound stopped for 5 seconds
  in headphones

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have an Ubuntu 18.04 installed on my DELL 7490 laptop.
  Kernel version is: 5.3.0-40-generic

  When I plug in one of my headphones and start to play sound I
  immediately start to hear white noise in the earphone. After I stop
  the music the white noise still remains for 5 more seconds, after 5
  seconds it stops.

  I tried with different headphones, the only difference between them is
  the volume of the white noise.

  I tried several ways to fix the problem but without any luck.

  lspci -nnk | grep -iA2 audio output:
  00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio 
[8086:9d71] (rev 21)
  Subsystem: Dell Sunrise Point-LP HD Audio [1028:081c]
  Kernel driver in use: snd_hda_intel
  Kernel modules: snd_hda_intel, snd_soc_skl
  sudo aplay -l output:
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  Thanks for your help in advance!

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

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

[Kernel-packages] [Bug 1806973] Re: zfs-dkms 0.7.9-3ubuntu6: zfs kernel module failed to build

[Colin Ian King]

The ZFS drivers are now provided by the kernel package and so zfs-dkms
can be safely removed and will avoid this issue.

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

** Changed in: zfs-linux (Ubuntu)
   Status: Confirmed => 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/1806973

Title:
  zfs-dkms 0.7.9-3ubuntu6: zfs kernel module failed to build

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

Bug description:
  Happened during an upgrade from Xubuntu 18.04 to Xubuntu 18.10. But
  ZFS did work OK after upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: zfs-dkms 0.7.9-3ubuntu6
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  DKMSBuildLog:
   DKMS make.log for zfs-0.7.9 for kernel 4.18.0-12-generic (x86_64)
   Wed Dec  5 13:43:02 AST 2018
   make: *** No targets specified and no makefile found.  Stop.
  DKMSKernelVersion: 4.18.0-12-generic
  Date: Wed Dec  5 13:43:04 2018
  InstallationDate: Installed on 2018-01-11 (328 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  PackageVersion: 0.7.9-3ubuntu6
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.0
  SourcePackage: zfs-linux
  Title: zfs-dkms 0.7.9-3ubuntu6: zfs kernel module failed to build
  UpgradeStatus: Upgraded to cosmic on 2018-12-05 (0 days ago)

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

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

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

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

Title:
  ZFS Severe Performance issue due to poorly supported feature

Status in zfs-linux package in Ubuntu:
  New

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 1869229] Re: Mounting LVM snapshots with xfs can hit kernel BUG in nvme driver

[Heitor Alves de Siqueira]

** Description changed:

  [Impact]
  When mounting LVM snapshots using xfs, it's possible to hit a BUG_ON() in 
nvme driver.
  
  Upstream commit 729204ef49ec ("block: relax check on sg gap") introduced
  a way to merge bios if they are physically contiguous. This can lead to
  issues if one rq starts with a non-aligned buffer, as it can cause the
  merged segment to end in an unaligned virtual boundary. In some AWS
  instances, it's possible to craft such a request when attempting to
  mount LVM snapshots using xfs. This will then cause a kernel spew due to
  a BUG_ON in nvme_setup_prps(), which checks if dma_len is aligned to the
  page size.
  
  [Fix]
- Upstream commit 5a8d75a1b8c9 ("block: fix bio_will_gap() for first bvec with 
offset") disallows requests that begin with an unaligned buffer from being 
merged.
+ Upstream commit 5a8d75a1b8c9 ("block: fix bio_will_gap() for first bvec with 
offset") prevents requests that begin with an unaligned buffer from being 
merged.
  
  [Test Case]
  This has been verified on AWS with c5d.large instances:
  
  1) Prepare the LVM device + snapshot
  $ sudo vgcreate vg0 /dev/nvme1n1
  $ sudo lvcreate -L5G -n data0 vg0
  $ sudo mkfs.xfs /dev/vg0/data0
  $ sudo mount /dev/vg0/data0 /mnt
  $ sudo touch /mnt/test
  $ sudo touch /mnt/test2
  $ sudo ls /mnt
  $ sudo umount /mnt
  $ sudo lvcreate -l100%FREE -s /dev/vg0/data0 -n data0_snap
  
  2) Attempting to mount the previously created snapshot results in the Oops:
- $ sudo mount /dev/vg0/data0_snap /mnt 
+ $ sudo mount /dev/vg0/data0_snap /mnt
  Segmentation fault (core dumped)
  
  [Regression Potential]
  The fix prevents some bios from being merged, so it can have a performance 
impact in certain scenarios. The patch only targets misaligned segments, so the 
impact should be less noticeable in the general case.
  The commit is also present in mainline kernels since 4.13, and hasn't been 
changed significantly, so potential for other regressions should be low.

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

Title:
  Mounting LVM snapshots with xfs can hit kernel BUG in nvme driver

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Confirmed

Bug description:
  [Impact]
  When mounting LVM snapshots using xfs, it's possible to hit a BUG_ON() in 
nvme driver.

  Upstream commit 729204ef49ec ("block: relax check on sg gap")
  introduced a way to merge bios if they are physically contiguous. This
  can lead to issues if one rq starts with a non-aligned buffer, as it
  can cause the merged segment to end in an unaligned virtual boundary.
  In some AWS instances, it's possible to craft such a request when
  attempting to mount LVM snapshots using xfs. This will then cause a
  kernel spew due to a BUG_ON in nvme_setup_prps(), which checks if
  dma_len is aligned to the page size.

  [Fix]
  Upstream commit 5a8d75a1b8c9 ("block: fix bio_will_gap() for first bvec with 
offset") prevents requests that begin with an unaligned buffer from being 
merged.

  [Test Case]
  This has been verified on AWS with c5d.large instances:

  1) Prepare the LVM device + snapshot
  $ sudo vgcreate vg0 /dev/nvme1n1
  $ sudo lvcreate -L5G -n data0 vg0
  $ sudo mkfs.xfs /dev/vg0/data0
  $ sudo mount /dev/vg0/data0 /mnt
  $ sudo touch /mnt/test
  $ sudo touch /mnt/test2
  $ sudo ls /mnt
  $ sudo umount /mnt
  $ sudo lvcreate -l100%FREE -s /dev/vg0/data0 -n data0_snap

  2) Attempting to mount the previously created snapshot results in the Oops:
  $ sudo mount /dev/vg0/data0_snap /mnt
  Segmentation fault (core dumped)

  [Regression Potential]
  The fix prevents some bios from being merged, so it can have a performance 
impact in certain scenarios. The patch only targets misaligned segments, so the 
impact should be less noticeable in the general case.
  The commit is also present in mainline kernels since 4.13, and hasn't been 
changed significantly, so potential for other regressions should be low.

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

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

[Solomon Nadar]

Now it is back to "radeon :03:00.0: failed VCE resume (-110)."


@Aspire-E1-572G:~$ dmesg | grep radeon
[1.704846] [drm] radeon kernel modesetting enabled.
[1.705248] radeon :03:00.0: remove_conflicting_pci_framebuffers: bar 0: 
0xa000 -> 0xafff
[1.705250] radeon :03:00.0: remove_conflicting_pci_framebuffers: bar 2: 
0xc050 -> 0xc053
[1.705263] radeon :03:00.0: enabling device ( -> 0003)
[1.736776] radeon :03:00.0: VRAM: 2048M 0x - 
0x7FFF (2048M used)
[1.736778] radeon :03:00.0: GTT: 2048M 0x8000 - 
0x
[1.736895] [drm] radeon: 2048M of VRAM memory ready
[1.736896] [drm] radeon: 2048M of GTT memory ready.
[1.745652] [drm] radeon: dpm initialized
[1.758577] radeon :03:00.0: WB enabled
[1.758580] radeon :03:00.0: fence driver on ring 0 use gpu addr 
0x8c00 and cpu addr 0x0b922bb2
[1.758581] radeon :03:00.0: fence driver on ring 1 use gpu addr 
0x8c04 and cpu addr 0x6468c07f
[1.758582] radeon :03:00.0: fence driver on ring 2 use gpu addr 
0x8c08 and cpu addr 0x824579d7
[1.758583] radeon :03:00.0: fence driver on ring 3 use gpu addr 
0x8c0c and cpu addr 0x815d08f8
[1.758584] radeon :03:00.0: fence driver on ring 4 use gpu addr 
0x8c10 and cpu addr 0x8fb35308
[1.759379] radeon :03:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xae56c323
[1.860176] radeon :03:00.0: failed VCE resume (-110).
[1.860181] radeon :03:00.0: radeon: MSI limited to 32-bit
[1.860224] radeon :03:00.0: radeon: using MSI.
[1.860258] [drm] radeon: irq initialized.
[2.939589] [drm] Initialized radeon 2.50.0 20080528 for :03:00.0 on 
minor 1
[   26.508807] radeon :03:00.0: WB enabled
[   26.508809] radeon :03:00.0: fence driver on ring 0 use gpu addr 
0x8c00 and cpu addr 0x0b922bb2
[   26.508811] radeon :03:00.0: fence driver on ring 1 use gpu addr 
0x8c04 and cpu addr 0x6468c07f
[   26.508812] radeon :03:00.0: fence driver on ring 2 use gpu addr 
0x8c08 and cpu addr 0x824579d7
[   26.508813] radeon :03:00.0: fence driver on ring 3 use gpu addr 
0x8c0c and cpu addr 0x815d08f8
[   26.508814] radeon :03:00.0: fence driver on ring 4 use gpu addr 
0x8c10 and cpu addr 0x8fb35308
[   26.509622] radeon :03:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xae56c323
[   26.610391] radeon :03:00.0: failed VCE resume (-110).
[   36.587124] radeon :03:00.0: WB enabled
[   36.587126] radeon :03:00.0: fence driver on ring 0 use gpu addr 
0x8c00 and cpu addr 0x0b922bb2
[   36.587127] radeon :03:00.0: fence driver on ring 1 use gpu addr 
0x8c04 and cpu addr 0x6468c07f
[   36.587128] radeon :03:00.0: fence driver on ring 2 use gpu addr 
0x8c08 and cpu addr 0x824579d7
[   36.587129] radeon :03:00.0: fence driver on ring 3 use gpu addr 
0x8c0c and cpu addr 0x815d08f8
[   36.587130] radeon :03:00.0: fence driver on ring 4 use gpu addr 
0x8c10 and cpu addr 0x8fb35308
[   36.587925] radeon :03:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xae56c323
[   36.688793] radeon :03:00.0: failed VCE resume (-110).
[  581.960318] radeon :03:00.0: WB enabled
[  581.960321] radeon :03:00.0: fence driver on ring 0 use gpu addr 
0x8c00 and cpu addr 0x0b922bb2
[  581.960322] radeon :03:00.0: fence driver on ring 1 use gpu addr 
0x8c04 and cpu addr 0x6468c07f
[  581.960323] radeon :03:00.0: fence driver on ring 2 use gpu addr 
0x8c08 and cpu addr 0x824579d7
[  581.960324] radeon :03:00.0: fence driver on ring 3 use gpu addr 
0x8c0c and cpu addr 0x815d08f8
[  581.960325] radeon :03:00.0: fence driver on ring 4 use gpu addr 
0x8c10 and cpu addr 0x8fb35308
[  581.961119] radeon :03:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xae56c323
[  582.061931] radeon :03:00.0: failed VCE resume (-110).

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

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

[Po-Hsu Lin]

I can finish running this test manually with autotest framework locally on this 
affected node modoc with 5.3.0-43:
AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/ubuntu_kernel_selftests/control

And the test suite can finish without tripping this issue.

But during the test I noticed that there will be another "missing remote IOA" 
error in dmesg:
[  353.854103] test_bpf: Summary: 378 PASSED, 0 FAILED, [366/366 JIT'ed]
[  353.854127] test_bpf: test_skb_segment: success in skb_segment!
[  359.982427] u32 classifier
[  359.982431] input device check on
[  359.982432] Actions configured
[  360.023690] gre: GRE over IPv4 demultiplexor driver
[  360.027718] ip_gre: GRE over IPv4 tunneling driver
[  360.231910] ip6_gre: GRE over IPv6 tunneling driver
[  361.139317] bridge: filtering via arp/ip/ip6tables is no longer available by 
default. Update your scripts to load br_netfilter if you need this.
[  361.141793] test-br0: port 1(test-dummy0) entered blocking state
[  361.141796] test-br0: port 1(test-dummy0) entered disabled state
[  361.141929] device test-dummy0 entered promiscuous mode
[  361.143982] test-br0: port 1(test-dummy0) entered blocking state
[  361.143984] test-br0: port 1(test-dummy0) entered forwarding state
[  361.166931] 8021q: 802.1Q VLAN Support v1.8
[  361.276750] device test-dummy0 left promiscuous mode
[  361.276826] test-br0: port 1(test-dummy0) entered disabled state
[  363.318680] MACsec IEEE 802.1AE
[  363.401018] Initializing XFRM netlink socket
[  365.457161] IPv6: ADDRCONF(NETDEV_CHANGE): veth0: link becomes ready
[  365.462267] IPv6: ADDRCONF(NETDEV_CHANGE): veth0: link becomes ready
[  365.464936] IPv6: ADDRCONF(NETDEV_CHANGE): veth0: link becomes ready
[  365.550548] bpfilter: Loaded bpfilter_umh pid 20653
[  366.415447] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[  397.070039] ipr 0001:08:00.0: 9076: Configuration error, missing remote IOA
[  397.070068] ipr 0001:08:00.0: Attached Adapter not discovered within 
allotted time [PRC: 17101541]
[  397.070077] ipr 0001:08:00.0: Remote IOA VPID/SN:   
[  397.070084] ipr 0001:08:00.0: Remote IOA WWN: 

Maybe it's some combination issue with the sru-misc test suite, which contains 
the following tests and will be executed in the following order:
'hwclock',
'libhugetlbfs',
'ubuntu_bpf_jit',
'ubuntu_kernel_selftests',
'ubuntu_lxc',
'ubuntu_seccomp',
'ubuntu_unionmount_ovlfs',
'ubuntu_cts_kernel',
'ubuntu_kvm_unit_tests',

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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: 

Re: [Kernel-packages] [Bug 1863581] Re: Ubuntu 20.04: megaraid_sas driver update to version 07.713.01.00-rc1

[Sumit Saxena]

Hi Michael,

I have asked our internal test to validate megaraid_sas driver. I will
check with them and get back to you

Thanks,
Sumit

On Fri, Mar 27, 2020, 12:05 AM Michael Reed 
wrote:

> Hi Sumit,
>
> Have you had a chance to test this yet?
>
> Regards,
> Michael
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1863581
>
> Title:
>   Ubuntu 20.04: megaraid_sas driver update to version 07.713.01.00-rc1
>
> Status in linux package in Ubuntu:
>   In Progress
> Status in linux source package in Focal:
>   In Progress
>
> Bug description:
>   [IMPACT]
>   This is a feature request to update megaraid_sas driver in Ubuntu 20.04
> release to latest Linux upstream tip.
>   The current latest upstream megaraid_sas driver version is-
> 07.713.01.00-rc1.
>   The current latest Ubuntu 20.04 Pre GA kernel has megaraid_sas driver
> version- 07.710.50.00-rc1. This will allow users to utilize features of
>   the PERC 11 device. For this reason, Broadcom and Dell have requested
> that we pull these patches to update the megaraid_sas driver to the current
> upstream version.
>
>   [FIXES]
>   Below set of upstream commit ids will lift driver version to
> 07.713.01.00-rc1 from 07.710.50.00-rc1:
>
>   92b4f9d15059 scsi: megaraid_sas: fixup MSIx interrupt setup during resume
>   824b72db5086 scsi: megaraid_sas: Update driver version to
> 07.713.01.00-rc1
>   4d1634b8d12e scsi: megaraid_sas: Use Block layer API to check SCSI
> device in-flight IO requests
>   56ee0c585602 scsi: megaraid_sas: Limit the number of retries for the
> IOCTLs causing firmware fault
>   6d7537270e32 scsi: megaraid_sas: Do not initiate OCR if controller is
> not in ready state
>   201a810cc188 scsi: megaraid_sas: Re-Define enum DCMD_RETURN_STATUS
>   eeb63c23ffe1 scsi: megaraid_sas: Do not set HBA Operational if FW is not
> in operational state
>   9330a0fd827a scsi: megaraid_sas: Do not kill HBA if JBOD Seqence map or
> RAID map is disabled
>   eb974f34bb9d scsi: megaraid_sas: Do not kill host bus adapter, if
> adapter is already dead
>   6e73550670ed scsi: megaraid_sas: Update optimal queue depth for SAS and
> NVMe devices
>   a7faf81d7858 scsi: megaraid_sas: Set no_write_same only for Virtual Disk
>   499e7246d6da scsi: megaraid_sas: Reset adapter if FW is not in READY
> state after device resume
>   73374b39b01e scsi: megaraid_sas: Make poll_aen_lock static
>   01b8bca81e18 compat_ioctl: use correct compat_ptr() translation in
> drivers
>   8cfb8e40d686 scsi: megaraid_sas: remove unused variables
> 'debugBlk','fusion'
>   ff7ca7fd03ce scsi: megaraid_sas: Unique names for MSI-X vectors
>   9ab089d30bcf scsi: megaraid_sas: Introduce module parameter for default
> queue depth
>   e5460f084b84 scsi: megaraid_sas: Fix a compilation warning
>   88d5c343949e scsi: megaraid_sas: Make a bunch of functions static
>   e45ab43b1d40 scsi: megaraid_sas: Make some functions static
>   3b5f307ef3cb scsi: megaraid_sas: fix panic on loading firmware crashdump
>   359603a3847e scsi: megaraid_sas: fix spelling mistake "megarid_sas" ->
> "megaraid_sas"
>   07d9aa143464 scsi: megaraid_sas: set an unlimited max_segment_size
>
>   Here is the link to latest Linux upstream megaraid_sas driver source:
>
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/scsi/megaraid
>
>   Please let me know if any further information is required.
>
>   Thanks,
>   Sumit
>
>   All are clean cherry picks into the 5.4 branch and can be pulled from the
>   following branch:
>
>
> https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/focal/+ref/lp1863581_megaraid_sas
>
>   [TESTING]
>   Modinfo should show that the megaraid_sas driver has been updated to
> 07.713.01.00
>
>   [REGRESSION RISK]
>   Low - Focal is not yet released, this is not being backported to current
> releases.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863581/+subscriptions
>

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

Title:
  Ubuntu 20.04: megaraid_sas driver update to version 07.713.01.00-rc1

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

Bug description:
  [IMPACT]
  This is a feature request to update megaraid_sas driver in Ubuntu 20.04 
release to latest Linux upstream tip.
  The current latest upstream megaraid_sas driver version is- 07.713.01.00-rc1.
  The current latest Ubuntu 20.04 Pre GA kernel has megaraid_sas driver 
version- 07.710.50.00-rc1. This will allow users to utilize features of
  the PERC 11 device. For this reason, Broadcom and Dell have requested that we 
pull these patches to update the megaraid_sas driver to the current upstream 
version.

  [FIXES]
  Below set of upstream commit ids will lift driver version to 07.713.01.00-rc1 
from 

[Kernel-packages] [Bug 1866866] Re: [FFe] Please accept patches for secure guest feature

[Łukasz Zemczak]

Ok, even though Steve was the one initially handling this FFe, seeing
that he's not available right now I sat down and took a look at the qemu
part - browsing through the diff took a while. I see work and testing is
happening all the time via LP: #1835546, so I think this is actually in
good hands. Though the changeset is really big and makes me feel a bit
weary, having a +1 from the qemu maintainer is a plus.

FFe for qemu granted.

** Changed in: qemu (Ubuntu)
   Status: New => 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/1866866

Title:
  [FFe] Please accept patches for secure guest feature

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in qemu package in Ubuntu:
  Triaged
Status in s390-tools package in Ubuntu:
  Fix Released

Bug description:
  The secure guest feature (aka protvirt) affects multiple components (kernel, 
qemu and s390-tools - see below).
  While dedicated tickets for the different components exist since quite a 
while, the code arrived late and/or discussion to get it upstream accepted took 
longer than expected.
  (Even if we as of today didn't reached the kernel freeze, I'm already adding 
kernel to this FFe.)

  Since this is a very important feature the current IBM Z and LinuxONE
  family, it's requested to be included into focal, the next LTS
  release, to become exploitable by long running systems.

  The code is largely architecture specific.
  No brand new packages or new upstream version are requested, only the 
cherry-pick of commits (or PR) - so far everything is 'cherry-pick'-able.

  kernel:
  The patch set for the kernel is huge (30+ commits), but has only one common 
code patch (two files).
  The arch specific patches landed in between in linux-next, the arch specific 
one is expected to land there very soon (hours/days from now). The common-code 
patch ran through several hands and landed in between in Andrew Morton's mmots 
tree.
  A pre-screening of the code was done by the kernel team and it looked 
acceptable.
  (dedicated kernel ticket: https://bugs.launchpad.net/bugs/1835531)

  qemu:
  The entire code seems to be arch specific.
  Again a pre-screening of the maintainer lead to the fact that it should be 
acceptable, too.
  (dedicated qemu ticket: https://bugs.launchpad.net/bugs/1835546)

  s390-tools:
  The entire tool only exists for the s390x architecture.
  Hence obviously everything is arch specific on that.
  (dedicated s390-tools ticket: https://bugs.launchpad.net/bugs/1834534)

  Currently work is going on to test this function end to end based on Ubuntu 
components (means based on our s390-tools, qemu and kernel [focal master-next] 
trees).
  On top I applied the patches to the packages as well and did manual test 
buids.

  With that a potential regression can be considered as low - and even
  in case of a regression, it will affect s390x only.

  The patches are being staged for this feature in:
  https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3970

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

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

[Kernel-packages] [Bug 1865293] Re: ryzen 5 3600x soft lockups

[Martin Gerdzhev]

And another crash

** Attachment added: "journal_log3.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1865293/+attachment/5341851/+files/journal_log3.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/1865293

Title:
  ryzen 5 3600x soft lockups

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using ubuntu 19.10 with a ryzen 5 3600x cpu and am getting soft lockups 
with the machine unresponsive almost on a daily basis. The only fix is a hard 
reset.
  I have the latest amd64-microcode installed - 
3.20191021.1+really3.20181128.1ubuntu2, but still continues to happen.

  
  Description:  Ubuntu 19.10
  Release:  19.10

  using kernel: 
  5.3.0-40-generic #32-Ubuntu SMP Fri Jan 31 20:24:34 UTC 2020 x86_64 x86_64 
x86_64 GNU/Linux
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  martin 2483 F pulseaudio
   /dev/snd/controlC0:  martin 2483 F pulseaudio
   /dev/snd/controlC2:  martin 2483 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-12-08 (87 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=05d2cb45-6b9c-47b3-8102-e6c6a13de26b ro acpi_enforce_resources=lax 
quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.183.4
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  eoan
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F11
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ELITE
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X570 AORUS ELITE
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1868665] Re: quotactl04 from ubuntu_ltp_syscalls failed with B

[Ubuntu Kernel Bot]

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

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

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


** Tags added: verification-needed-bionic

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

Title:
  quotactl04 from ubuntu_ltp_syscalls failed with B

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification ==
  Commit d65d87a07476 ("ext4: improve explanation of a mount failure
  caused by a misconfigured kernel") applied to our Bionic tree via the
  stable-update process does not consider the situation when quota support
  was configured as a module.

  This will cause failure to quotactl04 test from ubuntu_ltp_syscalls:
<<>>
tag=quotactl04 stime=1585032076
cmdline="quotactl04"
contacts=""
analysis=exit
<<>>
incrementing stop
tst_kconfig.c:62: INFO: Parsing kernel config 
'/boot/config-4.15.0-92-generic'
tst_device.c:244: INFO: Using test device LTP_DEV='/dev/loop0'
tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s
tst_mkfs.c:90: INFO: Formatting /dev/loop0 with ext4 opts='' extra opts='-O 
quota,project'
mke2fs 1.44.1 (24-Mar-2018)
safe_macros.c:769: BROK: quotactl04.c:109: mount(/dev/loop0, mntpoint, 
ext4, 0, 0x55edd2c1ab1d) failed: EINVAL (22)

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

  And from the syslog you will see:
LTP: starting quotactl04
EXT4-fs (loop0): The kernel was not built with CONFIG_QUOTA and 
CONFIG_QFMT_V2

  == Fix ==
  * 9db176bceb5c ("ext4: fix mount failure with quota configured as module")

  This patch can be cherry-picked into Bionic and it's already in Focal.

  I didn't see commit d65d87a07476 in Eoan / Disco, so I think they don't
  need this patch.

  == Test ==
  Test kernel could be found here:
  https://people.canonical.com/~phlin/kernel/lp-1868665-quota-module/

  Tested with the quotactl04 test from ubuntu_ltp_syscalls and it has
  passed as expected.

  == Regression Potential ==
  Low, this patch is specific to ext4 quota support. And it's just using
  a more general way to do the check.

  
  == Original Bug Report ==
  Issue found on Bionic 4.15.0-92-generic
  Manually verified with 4.15.0-91, this issue does not exist.

  Result for 4.15.0-92:
  <<>>
  tag=quotactl04 stime=1585032076
  cmdline="quotactl04"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_kconfig.c:62: INFO: Parsing kernel config '/boot/config-4.15.0-92-generic'
  tst_device.c:244: INFO: Using test device LTP_DEV='/dev/loop0'
  tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s
  tst_mkfs.c:90: INFO: Formatting /dev/loop0 with ext4 opts='' extra opts='-O 
quota,project'
  mke2fs 1.44.1 (24-Mar-2018)
  safe_macros.c:769: BROK: quotactl04.c:109: mount(/dev/loop0, mntpoint, ext4, 
0, 0x55edd2c1ab1d) failed: EINVAL (22)

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

  Syslog for 4.15.0-92:
  Mar 24 06:40:31 larry kernel: [  135.916625] LTP: starting quotactl04
  Mar 24 06:40:32 larry kernel: [  136.163837] EXT4-fs (loop0): The kernel was 
not built with CONFIG_QUOTA and CONFIG_QFMT_V2

  Result for 4.15.0-91:
  <<>>
  tag=quotactl04 stime=1585031743
  cmdline="quotactl04"
  contacts=""
  analysis=exit
  <<>>
  tst_kconfig.c:62: INFO: Parsing kernel config '/boot/config-4.15.0-91-generic'
  tst_device.c:244: INFO: Using test device LTP_DEV='/dev/loop1'
  tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s
  tst_mkfs.c:90: INFO: Formatting /dev/loop1 with ext4 opts='' extra opts='-O 
quota,project'
  mke2fs 1.44.1 (24-Mar-2018)
  quotactl04.c:127: INFO: Test #0: QCMD(Q_QUOTAON, PRJQUOTA)
  quotactl04.c:142: PASS: quotactl succeeded to turn on quota for project
  quotactl04.c:127: INFO: Test #1: QCMD(Q_SETQUOTA, PRJQUOTA)
  quotactl04.c:142: PASS: quotactl succeeded to set disk quota limit for project
  quotactl04.c:127: INFO: Test #2: QCMD(Q_GETQUOTA, PRJQUOTA)
  quotactl04.c:142: PASS: quotactl succeeded to get disk quota limit for project
  quotactl04.c:127: INFO: Test #3: 

[Kernel-packages] [Bug 1869080] Re: White noise during sound playing and after sound stopped for 5 seconds in headphones

[zsambek]

apport information

** Tags added: apport-collected bionic

** Description changed:

  I have an Ubuntu 18.04 installed on my DELL 7490 laptop.
  Kernel version is: 5.3.0-40-generic
  
  When I plug in one of my headphones and start to play sound I
  immediately start to hear white noise in the earphone. After I stop the
  music the white noise still remains for 5 more seconds, after 5 seconds
  it stops.
  
  I tried with different headphones, the only difference between them is
  the volume of the white noise.
  
  I tried several ways to fix the problem but without any luck.
  
  lspci -nnk | grep -iA2 audio output:
  00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio 
[8086:9d71] (rev 21)
  Subsystem: Dell Sunrise Point-LP HD Audio [1028:081c]
  Kernel driver in use: snd_hda_intel
  Kernel modules: snd_hda_intel, snd_soc_skl
  sudo aplay -l output:
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0
  
  Thanks for your help in advance!
+ 
+ 
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.12
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  zsambek2196 F pulseaudio
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2020-02-20 (34 days ago)
+ InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
+  Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp. 
+  Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: Dell Inc. Latitude 7490
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-42-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-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.173.16
+ Tags:  bionic
+ Uname: Linux 5.3.0-42-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 11/08/2019
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: 1.13.1
+ dmi.board.name: 0PP44F
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A02
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.1:bd11/08/2019:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0PP44F:rvrA02:cvnDellInc.:ct10:cvr:
+ dmi.product.family: Latitude
+ dmi.product.name: Latitude 7490
+ dmi.product.sku: 081C
+ dmi.sys.vendor: Dell Inc.

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

Title:
  White noise during sound playing and after sound stopped for 5 seconds
  in headphones

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an Ubuntu 18.04 installed on my DELL 7490 laptop.
  Kernel version is: 5.3.0-40-generic

  When I plug in one of my headphones and start to play sound I
  immediately start to hear white noise in the earphone. After I stop
  the music the white noise still remains for 5 more seconds, after 5
  seconds it stops.

  I tried with different headphones, the only difference between them is
  the volume of the white noise.

  I tried several ways to fix the problem but without any luck.

  lspci -nnk | grep -iA2 audio output:
  00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio 
[8086:9d71] (rev 21)
  Subsystem: Dell Sunrise Point-LP HD Audio [1028:081c]
  Kernel driver in use: snd_hda_intel
  Kernel modules: snd_hda_intel, snd_soc_skl
  sudo aplay -l output:
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 

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

[zsambek]

apport information

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

Title:
  White noise during sound playing and after sound stopped for 5 seconds
  in headphones

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an Ubuntu 18.04 installed on my DELL 7490 laptop.
  Kernel version is: 5.3.0-40-generic

  When I plug in one of my headphones and start to play sound I
  immediately start to hear white noise in the earphone. After I stop
  the music the white noise still remains for 5 more seconds, after 5
  seconds it stops.

  I tried with different headphones, the only difference between them is
  the volume of the white noise.

  I tried several ways to fix the problem but without any luck.

  lspci -nnk | grep -iA2 audio output:
  00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio 
[8086:9d71] (rev 21)
  Subsystem: Dell Sunrise Point-LP HD Audio [1028:081c]
  Kernel driver in use: snd_hda_intel
  Kernel modules: snd_hda_intel, snd_soc_skl
  sudo aplay -l output:
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  Thanks for your help in advance!


  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zsambek2196 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-20 (34 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 7490
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-42-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-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.173.16
  Tags:  bionic
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/08/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.1
  dmi.board.name: 0PP44F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.1:bd11/08/2019:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0PP44F:rvrA02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7490
  dmi.product.sku: 081C
  dmi.sys.vendor: Dell Inc.

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

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

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

[zsambek]

apport information

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

Title:
  White noise during sound playing and after sound stopped for 5 seconds
  in headphones

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an Ubuntu 18.04 installed on my DELL 7490 laptop.
  Kernel version is: 5.3.0-40-generic

  When I plug in one of my headphones and start to play sound I
  immediately start to hear white noise in the earphone. After I stop
  the music the white noise still remains for 5 more seconds, after 5
  seconds it stops.

  I tried with different headphones, the only difference between them is
  the volume of the white noise.

  I tried several ways to fix the problem but without any luck.

  lspci -nnk | grep -iA2 audio output:
  00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio 
[8086:9d71] (rev 21)
  Subsystem: Dell Sunrise Point-LP HD Audio [1028:081c]
  Kernel driver in use: snd_hda_intel
  Kernel modules: snd_hda_intel, snd_soc_skl
  sudo aplay -l output:
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  Thanks for your help in advance!


  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zsambek2196 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-20 (34 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 7490
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-42-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-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.173.16
  Tags:  bionic
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/08/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.1
  dmi.board.name: 0PP44F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.1:bd11/08/2019:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0PP44F:rvrA02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7490
  dmi.product.sku: 081C
  dmi.sys.vendor: Dell Inc.

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

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

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

[zsambek]

apport information

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

Title:
  White noise during sound playing and after sound stopped for 5 seconds
  in headphones

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an Ubuntu 18.04 installed on my DELL 7490 laptop.
  Kernel version is: 5.3.0-40-generic

  When I plug in one of my headphones and start to play sound I
  immediately start to hear white noise in the earphone. After I stop
  the music the white noise still remains for 5 more seconds, after 5
  seconds it stops.

  I tried with different headphones, the only difference between them is
  the volume of the white noise.

  I tried several ways to fix the problem but without any luck.

  lspci -nnk | grep -iA2 audio output:
  00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio 
[8086:9d71] (rev 21)
  Subsystem: Dell Sunrise Point-LP HD Audio [1028:081c]
  Kernel driver in use: snd_hda_intel
  Kernel modules: snd_hda_intel, snd_soc_skl
  sudo aplay -l output:
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  Thanks for your help in advance!


  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zsambek2196 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-20 (34 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 7490
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-42-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-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.173.16
  Tags:  bionic
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/08/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.1
  dmi.board.name: 0PP44F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.1:bd11/08/2019:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0PP44F:rvrA02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7490
  dmi.product.sku: 081C
  dmi.sys.vendor: Dell Inc.

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

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

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

[zsambek]

apport information

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

Title:
  White noise during sound playing and after sound stopped for 5 seconds
  in headphones

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an Ubuntu 18.04 installed on my DELL 7490 laptop.
  Kernel version is: 5.3.0-40-generic

  When I plug in one of my headphones and start to play sound I
  immediately start to hear white noise in the earphone. After I stop
  the music the white noise still remains for 5 more seconds, after 5
  seconds it stops.

  I tried with different headphones, the only difference between them is
  the volume of the white noise.

  I tried several ways to fix the problem but without any luck.

  lspci -nnk | grep -iA2 audio output:
  00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio 
[8086:9d71] (rev 21)
  Subsystem: Dell Sunrise Point-LP HD Audio [1028:081c]
  Kernel driver in use: snd_hda_intel
  Kernel modules: snd_hda_intel, snd_soc_skl
  sudo aplay -l output:
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  Thanks for your help in advance!


  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zsambek2196 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-20 (34 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 7490
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-42-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-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.173.16
  Tags:  bionic
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/08/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.1
  dmi.board.name: 0PP44F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.1:bd11/08/2019:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0PP44F:rvrA02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7490
  dmi.product.sku: 081C
  dmi.sys.vendor: Dell Inc.

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

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

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

[zsambek]

apport information

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

Title:
  White noise during sound playing and after sound stopped for 5 seconds
  in headphones

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an Ubuntu 18.04 installed on my DELL 7490 laptop.
  Kernel version is: 5.3.0-40-generic

  When I plug in one of my headphones and start to play sound I
  immediately start to hear white noise in the earphone. After I stop
  the music the white noise still remains for 5 more seconds, after 5
  seconds it stops.

  I tried with different headphones, the only difference between them is
  the volume of the white noise.

  I tried several ways to fix the problem but without any luck.

  lspci -nnk | grep -iA2 audio output:
  00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio 
[8086:9d71] (rev 21)
  Subsystem: Dell Sunrise Point-LP HD Audio [1028:081c]
  Kernel driver in use: snd_hda_intel
  Kernel modules: snd_hda_intel, snd_soc_skl
  sudo aplay -l output:
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  Thanks for your help in advance!


  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zsambek2196 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-20 (34 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 7490
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-42-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-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.173.16
  Tags:  bionic
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/08/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.1
  dmi.board.name: 0PP44F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.1:bd11/08/2019:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0PP44F:rvrA02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7490
  dmi.product.sku: 081C
  dmi.sys.vendor: Dell Inc.

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

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

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

[zsambek]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1869080/+attachment/5341856/+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/1869080

Title:
  White noise during sound playing and after sound stopped for 5 seconds
  in headphones

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an Ubuntu 18.04 installed on my DELL 7490 laptop.
  Kernel version is: 5.3.0-40-generic

  When I plug in one of my headphones and start to play sound I
  immediately start to hear white noise in the earphone. After I stop
  the music the white noise still remains for 5 more seconds, after 5
  seconds it stops.

  I tried with different headphones, the only difference between them is
  the volume of the white noise.

  I tried several ways to fix the problem but without any luck.

  lspci -nnk | grep -iA2 audio output:
  00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio 
[8086:9d71] (rev 21)
  Subsystem: Dell Sunrise Point-LP HD Audio [1028:081c]
  Kernel driver in use: snd_hda_intel
  Kernel modules: snd_hda_intel, snd_soc_skl
  sudo aplay -l output:
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  Thanks for your help in advance!


  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zsambek2196 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-20 (34 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 7490
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-42-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-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.173.16
  Tags:  bionic
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/08/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.1
  dmi.board.name: 0PP44F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.1:bd11/08/2019:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0PP44F:rvrA02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7490
  dmi.product.sku: 081C
  dmi.sys.vendor: Dell Inc.

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

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

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

[zsambek]

apport information

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

Title:
  White noise during sound playing and after sound stopped for 5 seconds
  in headphones

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an Ubuntu 18.04 installed on my DELL 7490 laptop.
  Kernel version is: 5.3.0-40-generic

  When I plug in one of my headphones and start to play sound I
  immediately start to hear white noise in the earphone. After I stop
  the music the white noise still remains for 5 more seconds, after 5
  seconds it stops.

  I tried with different headphones, the only difference between them is
  the volume of the white noise.

  I tried several ways to fix the problem but without any luck.

  lspci -nnk | grep -iA2 audio output:
  00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio 
[8086:9d71] (rev 21)
  Subsystem: Dell Sunrise Point-LP HD Audio [1028:081c]
  Kernel driver in use: snd_hda_intel
  Kernel modules: snd_hda_intel, snd_soc_skl
  sudo aplay -l output:
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  Thanks for your help in advance!


  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zsambek2196 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-20 (34 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 7490
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-42-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-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.173.16
  Tags:  bionic
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/08/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.1
  dmi.board.name: 0PP44F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.1:bd11/08/2019:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0PP44F:rvrA02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7490
  dmi.product.sku: 081C
  dmi.sys.vendor: Dell Inc.

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

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

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

[zsambek]

apport information

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

Title:
  White noise during sound playing and after sound stopped for 5 seconds
  in headphones

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an Ubuntu 18.04 installed on my DELL 7490 laptop.
  Kernel version is: 5.3.0-40-generic

  When I plug in one of my headphones and start to play sound I
  immediately start to hear white noise in the earphone. After I stop
  the music the white noise still remains for 5 more seconds, after 5
  seconds it stops.

  I tried with different headphones, the only difference between them is
  the volume of the white noise.

  I tried several ways to fix the problem but without any luck.

  lspci -nnk | grep -iA2 audio output:
  00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio 
[8086:9d71] (rev 21)
  Subsystem: Dell Sunrise Point-LP HD Audio [1028:081c]
  Kernel driver in use: snd_hda_intel
  Kernel modules: snd_hda_intel, snd_soc_skl
  sudo aplay -l output:
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  Thanks for your help in advance!


  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zsambek2196 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-20 (34 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 7490
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-42-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-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.173.16
  Tags:  bionic
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/08/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.1
  dmi.board.name: 0PP44F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.1:bd11/08/2019:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0PP44F:rvrA02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7490
  dmi.product.sku: 081C
  dmi.sys.vendor: Dell Inc.

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

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

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

[zsambek]

apport information

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

Title:
  White noise during sound playing and after sound stopped for 5 seconds
  in headphones

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an Ubuntu 18.04 installed on my DELL 7490 laptop.
  Kernel version is: 5.3.0-40-generic

  When I plug in one of my headphones and start to play sound I
  immediately start to hear white noise in the earphone. After I stop
  the music the white noise still remains for 5 more seconds, after 5
  seconds it stops.

  I tried with different headphones, the only difference between them is
  the volume of the white noise.

  I tried several ways to fix the problem but without any luck.

  lspci -nnk | grep -iA2 audio output:
  00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio 
[8086:9d71] (rev 21)
  Subsystem: Dell Sunrise Point-LP HD Audio [1028:081c]
  Kernel driver in use: snd_hda_intel
  Kernel modules: snd_hda_intel, snd_soc_skl
  sudo aplay -l output:
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  Thanks for your help in advance!


  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zsambek2196 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-20 (34 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 7490
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-42-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-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.173.16
  Tags:  bionic
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/08/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.1
  dmi.board.name: 0PP44F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.1:bd11/08/2019:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0PP44F:rvrA02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7490
  dmi.product.sku: 081C
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1869229] Re: Mounting LVM snapshots with xfs can hit kernel BUG in nvme driver

[Heitor Alves de Siqueira]

Patches sent out to kernel-team list:

https://lists.ubuntu.com/archives/kernel-team/2020-March/108551.html
https://lists.ubuntu.com/archives/kernel-team/2020-March/108552.html

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

Title:
  Mounting LVM snapshots with xfs can hit kernel BUG in nvme driver

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Confirmed

Bug description:
  [Impact]
  When mounting LVM snapshots using xfs, it's possible to hit a BUG_ON() in 
nvme driver.

  Upstream commit 729204ef49ec ("block: relax check on sg gap")
  introduced a way to merge bios if they are physically contiguous. This
  can lead to issues if one rq starts with a non-aligned buffer, as it
  can cause the merged segment to end in an unaligned virtual boundary.
  In some AWS instances, it's possible to craft such a request when
  attempting to mount LVM snapshots using xfs. This will then cause a
  kernel spew due to a BUG_ON in nvme_setup_prps(), which checks if
  dma_len is aligned to the page size.

  [Fix]
  Upstream commit 5a8d75a1b8c9 ("block: fix bio_will_gap() for first bvec with 
offset") prevents requests that begin with an unaligned buffer from being 
merged.

  [Test Case]
  This has been verified on AWS with c5d.large instances:

  1) Prepare the LVM device + snapshot
  $ sudo vgcreate vg0 /dev/nvme1n1
  $ sudo lvcreate -L5G -n data0 vg0
  $ sudo mkfs.xfs /dev/vg0/data0
  $ sudo mount /dev/vg0/data0 /mnt
  $ sudo touch /mnt/test
  $ sudo touch /mnt/test2
  $ sudo ls /mnt
  $ sudo umount /mnt
  $ sudo lvcreate -l100%FREE -s /dev/vg0/data0 -n data0_snap

  2) Attempting to mount the previously created snapshot results in the Oops:
  $ sudo mount /dev/vg0/data0_snap /mnt
  Segmentation fault (core dumped)

  [Regression Potential]
  The fix prevents some bios from being merged, so it can have a performance 
impact in certain scenarios. The patch only targets misaligned segments, so the 
impact should be less noticeable in the general case.
  The commit is also present in mainline kernels since 4.13, and hasn't been 
changed significantly, so potential for other regressions should be low.

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

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

[Kernel-packages] [Bug 1863581] Re: Ubuntu 20.04: megaraid_sas driver update to version 07.713.01.00-rc1

[Michael Reed]

Hi Sumit,

Have you had a chance to test this yet?

Regards,
Michael

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

Title:
  Ubuntu 20.04: megaraid_sas driver update to version 07.713.01.00-rc1

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

Bug description:
  [IMPACT]
  This is a feature request to update megaraid_sas driver in Ubuntu 20.04 
release to latest Linux upstream tip.
  The current latest upstream megaraid_sas driver version is- 07.713.01.00-rc1.
  The current latest Ubuntu 20.04 Pre GA kernel has megaraid_sas driver 
version- 07.710.50.00-rc1. This will allow users to utilize features of
  the PERC 11 device. For this reason, Broadcom and Dell have requested that we 
pull these patches to update the megaraid_sas driver to the current upstream 
version.

  [FIXES]
  Below set of upstream commit ids will lift driver version to 07.713.01.00-rc1 
from 07.710.50.00-rc1:

  92b4f9d15059 scsi: megaraid_sas: fixup MSIx interrupt setup during resume
  824b72db5086 scsi: megaraid_sas: Update driver version to 07.713.01.00-rc1
  4d1634b8d12e scsi: megaraid_sas: Use Block layer API to check SCSI device 
in-flight IO requests
  56ee0c585602 scsi: megaraid_sas: Limit the number of retries for the IOCTLs 
causing firmware fault
  6d7537270e32 scsi: megaraid_sas: Do not initiate OCR if controller is not in 
ready state
  201a810cc188 scsi: megaraid_sas: Re-Define enum DCMD_RETURN_STATUS
  eeb63c23ffe1 scsi: megaraid_sas: Do not set HBA Operational if FW is not in 
operational state
  9330a0fd827a scsi: megaraid_sas: Do not kill HBA if JBOD Seqence map or RAID 
map is disabled
  eb974f34bb9d scsi: megaraid_sas: Do not kill host bus adapter, if adapter is 
already dead
  6e73550670ed scsi: megaraid_sas: Update optimal queue depth for SAS and NVMe 
devices
  a7faf81d7858 scsi: megaraid_sas: Set no_write_same only for Virtual Disk
  499e7246d6da scsi: megaraid_sas: Reset adapter if FW is not in READY state 
after device resume
  73374b39b01e scsi: megaraid_sas: Make poll_aen_lock static
  01b8bca81e18 compat_ioctl: use correct compat_ptr() translation in drivers
  8cfb8e40d686 scsi: megaraid_sas: remove unused variables 'debugBlk','fusion'
  ff7ca7fd03ce scsi: megaraid_sas: Unique names for MSI-X vectors
  9ab089d30bcf scsi: megaraid_sas: Introduce module parameter for default queue 
depth
  e5460f084b84 scsi: megaraid_sas: Fix a compilation warning
  88d5c343949e scsi: megaraid_sas: Make a bunch of functions static
  e45ab43b1d40 scsi: megaraid_sas: Make some functions static
  3b5f307ef3cb scsi: megaraid_sas: fix panic on loading firmware crashdump
  359603a3847e scsi: megaraid_sas: fix spelling mistake "megarid_sas" -> 
"megaraid_sas"
  07d9aa143464 scsi: megaraid_sas: set an unlimited max_segment_size

  Here is the link to latest Linux upstream megaraid_sas driver source:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/scsi/megaraid

  Please let me know if any further information is required.

  Thanks,
  Sumit

  All are clean cherry picks into the 5.4 branch and can be pulled from the
  following branch:

  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/focal/+ref/lp1863581_megaraid_sas

  [TESTING]
  Modinfo should show that the megaraid_sas driver has been updated to 
07.713.01.00

  [REGRESSION RISK]
  Low - Focal is not yet released, this is not being backported to current 
releases.

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

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

[Kernel-packages] [Bug 1869229] Re: Mounting LVM snapshots with xfs can hit kernel BUG in nvme driver

[Heitor Alves de Siqueira]

For reference, the kernel spew of the BUG_ON:

[   78.354129] kernel BUG at 
/home/ubuntu/xenial-aws/drivers/nvme/host/pci.c:619!
[   78.357297] invalid opcode:  [#1] SMP
[   78.359613] Modules linked in: dm_snapshot dm_bufio xfs ppdev serio_raw 
parport_pc 8250_fintek parport i2c_piix4 ib_iser rdma_cm iw_cm ib_cm ib_sa 
ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 
autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul 
glue_helper ablk_helper cryptd ena
[   78.387878] CPU: 0 PID: 1687 Comm: mount Not tainted 4.4.0-1105-aws #116
[   78.390837] Hardware name: Amazon EC2 c5d.large/, BIOS 1.0 10/16/2017
[   78.393692] task: 8800bb155400 ti: 8800b93bc000 task.ti: 
8800b93bc000
[   78.396973] RIP: 0010:[]  [] 
nvme_queue_rq+0x8c6/0xa60
[   78.400787] RSP: 0018:8800b93bf7c8  EFLAGS: 00010286
[   78.403151] RAX: 0078 RBX: 1000 RCX: 1000
[   78.406276] RDX:  RSI: 0246 RDI: 
[   78.409390] RBP: 8800b93bf8a8 R08: 8800b916c700 R09: 1000
[   78.412518] R10: 0001ec00 R11: 8800b8e3 R12: fc00
[   78.417056] R13: 0010 R14: fc00 R15: 35fd5000
[   78.421581] FS:  7f30fe043840() GS:880130a0() 
knlGS:
[   78.427884] CS:  0010 DS:  ES:  CR0: 80050033
[   78.431827] CR2: 7f57d4057889 CR3: 35974000 CR4: 00360670
[   78.436322] DR0:  DR1:  DR2: 
[   78.440821] DR3:  DR6: fffe0ff0 DR7: 0400
[   78.445316] Stack:
[   78.447706]  880036009480 880036009700 8800b7782800 
0ff8
[   78.454583]  8800b8e30420 8800360a9400 8801fc00 
8800b7697b00
[   78.461462]  88011000 8800b8e3 88003604c000 
0001ffc00400
[   78.468332] Call Trace:
[   78.470921]  [] blk_mq_make_request+0x407/0x550
[   78.475001]  [] generic_make_request+0x114/0x2d0
[   78.479110]  [] ? bvec_alloc+0x91/0x100
[   78.482936]  [] submit_bio+0x76/0x160
[   78.486680]  [] _xfs_buf_ioapply+0x2e4/0x4a0 [xfs]
[   78.490866]  [] ? wake_up_q+0x70/0x70
[   78.494601]  [] ? xfs_bwrite+0x24/0x60 [xfs]
[   78.498583]  [] xfs_buf_submit_wait+0x5d/0x230 [xfs]
[   78.502861]  [] xfs_bwrite+0x24/0x60 [xfs]
[   78.506785]  [] xlog_bwrite+0x7f/0x100 [xfs]
[   78.510787]  [] xlog_write_log_records+0x1a4/0x230 [xfs]
[   78.515192]  [] xlog_clear_stale_blocks+0xb7/0x1b0 [xfs]
[   78.519596]  [] ? xlog_bread+0x3f/0x50 [xfs]
[   78.523588]  [] xlog_find_tail+0x2db/0x3b0 [xfs]
[   78.527705]  [] xlog_recover+0x2d/0x160 [xfs]
[   78.531720]  [] xfs_log_mount+0xdb/0x2a0 [xfs]
[   78.535767]  [] xfs_mountfs+0x4f3/0x870 [xfs]
[   78.539788]  [] ? xfs_mru_cache_create+0x12b/0x180 [xfs]
[   78.544197]  [] xfs_fs_fill_super+0x3bb/0x4e0 [xfs]
[   78.548400]  [] mount_bdev+0x270/0x2c0
[   78.552169]  [] ? xfs_parseargs+0xab0/0xab0 [xfs]
[   78.556338]  [] xfs_fs_mount+0x15/0x20 [xfs]
[   78.560337]  [] mount_fs+0x3d/0x170
[   78.564091]  [] ? __alloc_percpu+0x15/0x20
[   78.568060]  [] vfs_kern_mount+0x67/0x110
[   78.571971]  [] do_mount+0x25f/0xda0
[   78.575692]  [] ? mntput+0x24/0x40
[   78.579334]  [] ? __kmalloc_track_caller+0x1b6/0x250
[   78.583595]  [] ? __fput+0x193/0x230
[   78.587296]  [] ? memdup_user+0x42/0x70
[   78.59]  [] SyS_mount+0x9f/0x100
[   78.594804]  [] entry_SYSCALL_64_fastpath+0x22/0xcb
[   78.599029] Code: 11 e3 e3 ff 44 8b 95 50 ff ff ff 48 89 85 68 ff ff ff 4c 
8b 48 10 44 8b 58 18 8b 95 58 ff ff ff 8b 8d 60 ff ff ff e9 0a fd ff ff <0f> 0b 
48 8b 73 68 48 8b bd 70 ff ff ff e8 58 c5 e2 ff 83 f8 01
[   78.625198] RIP  [] nvme_queue_rq+0x8c6/0xa60
[   78.629410]  RSP 
[   78.632442] ---[ end trace de20412ccd13806e ]---

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

Title:
  Mounting LVM snapshots with xfs can hit kernel BUG in nvme driver

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Confirmed

Bug description:
  [Impact]
  When mounting LVM snapshots using xfs, it's possible to hit a BUG_ON() in 
nvme driver.

  Upstream commit 729204ef49ec ("block: relax check on sg gap")
  introduced a way to merge bios if they are physically contiguous. This
  can lead to issues if one rq starts with a non-aligned buffer, as it
  can cause the merged segment to end in an unaligned virtual boundary.
  In some AWS instances, it's possible to craft such a request when
  attempting to mount LVM snapshots using xfs. This will then cause a
  kernel spew due to a BUG_ON in nvme_setup_prps(), which checks if
  dma_len is aligned to the 

[Kernel-packages] [Bug 1768962] Re: zfs-dkms 0.6.5.6-0ubuntu21: zfs kernel module failed to build

[Colin Ian King]

Apologies for taking so long to get around to triage this issue. If this
is still an issue please attach the DKMS make.log file generated on the
failed build.


** Changed in: zfs-linux (Ubuntu)
   Status: Confirmed => Triaged

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

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

Title:
  zfs-dkms 0.6.5.6-0ubuntu21: zfs kernel module failed to build

Status in zfs-linux package in Ubuntu:
  Triaged

Bug description:
  nothing more to say -> failed to build in apt dist-upgrade...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: zfs-dkms 0.6.5.6-0ubuntu21
  ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117
  Uname: Linux 4.4.0-121-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  DKMSBuildLog:
   DKMS make.log for zfs-0.6.5.6 for kernel 4.4.0-122-generic (x86_64)
   Do 3. Mai 21:43:07 CEST 2018
   make: *** Es wurden keine Ziele angegeben und keine „make“-Steuerdatei 
gefunden.  Schluss.
  DKMSKernelVersion: 4.4.0-122-generic
  Date: Thu May  3 21:43:11 2018
  InstallationDate: Installed on 2012-04-30 (2194 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  PackageVersion: 0.6.5.6-0ubuntu21
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: zfs-linux
  Title: zfs-dkms 0.6.5.6-0ubuntu21: zfs kernel module failed to build
  UpgradeStatus: Upgraded to xenial on 2016-06-03 (699 days ago)

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

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

[Kernel-packages] [Bug 1849982] Re: package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10

[Colin Ian King]

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

If you are using the latest ZFS the drivers are built into the kernel so
the zfs-dkms package should be removed.

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

** This bug has been marked a duplicate of bug 1849981
   package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed 
zfs-dkms package post-installation script subprocess returned error exit status 
10

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

Title:
  package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed
  zfs-dkms package post-installation script subprocess returned error
  exit status 10

Status in zfs-linux package in Ubuntu:
  Triaged

Bug description:
  Package is really zfs-dkms but bug tool no have

  upgrading 19.04 - 19.10 mac Mini

     Processing triggers for initramfs-tools (0.133ubuntu10) ...
     This system doesn't support Secure Boot
     Secure Boot not enabled on this system.
     Errors were encountered while processing:
  zfs-dkms

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: zfs-dkms 0.8.1-1ubuntu14
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zlua zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  Date: Sat Oct 26 12:22:09 2019
  ErrorMessage: installed zfs-dkms package post-installation script subprocess 
returned error exit status 10
  InstallationDate: Installed on 2019-06-20 (128 days ago)
  InstallationMedia: Ubuntu-Server 19.04 "Disco Dingo" - Release amd64 
(20190416.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  SourcePackage: zfs-linux
  Title: package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed 
zfs-dkms package post-installation script subprocess returned error exit status 
10
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (0 days ago)

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

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

[Kernel-packages] [Bug 1838276] Re: zfs-module depedency selects random kernel package to install

[Colin Ian King]

** Changed in: zfs-linux (Ubuntu)
   Status: Triaged => 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/1838276

Title:
  zfs-module depedency selects random kernel package to install

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

Bug description:
  In MAAS (ephemeral environment) or LXD where no kernel package is
  currently installed; installing the zfsutils-linux package will pull
  in a kernel package from the zfs-modules dependency.

  
  1) # lsb_release -rd
  Description:  Ubuntu Eoan Ermine (development branch)
  Release:  19.10

  2) n/a

  3) zfsutils-linux installed without pulling in a random kernel

  4) # apt install --dry-run zfsutils-linux
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following additional packages will be installed:
grub-common grub-gfxpayload-lists grub-pc grub-pc-bin grub2-common 
libzfs2linux libzpool2linux
linux-image-unsigned-5.0.0-1010-oem-osp1 linux-modules-5.0.0-1010-oem-osp1 
os-prober zfs-zed
  Suggested packages:
multiboot-doc grub-emu xorriso desktop-base fdutils linux-oem-osp1-tools 
linux-headers-5.0.0-1010-oem-osp1
nfs-kernel-server samba-common-bin zfs-initramfs | zfs-dracut
  The following NEW packages will be installed:
grub-common grub-gfxpayload-lists grub-pc grub-pc-bin grub2-common 
libzfs2linux libzpool2linux
linux-image-unsigned-5.0.0-1010-oem-osp1 linux-modules-5.0.0-1010-oem-osp1 
os-prober zfs-zed zfsutils-linux
  0 upgraded, 12 newly installed, 0 to remove and 1 not upgraded.
  Inst grub-common (2.04-1ubuntu2 Ubuntu:19.10/eoan [amd64])
  Inst grub2-common (2.04-1ubuntu2 Ubuntu:19.10/eoan [amd64])
  Inst grub-pc-bin (2.04-1ubuntu2 Ubuntu:19.10/eoan [amd64])
  Inst grub-pc (2.04-1ubuntu2 Ubuntu:19.10/eoan [amd64]) []
  Inst grub-gfxpayload-lists (0.7 Ubuntu:19.10/eoan [amd64])
  Inst linux-modules-5.0.0-1010-oem-osp1 (5.0.0-1010.11 Ubuntu:19.10/eoan 
[amd64])
  Inst linux-image-unsigned-5.0.0-1010-oem-osp1 (5.0.0-1010.11 
Ubuntu:19.10/eoan [amd64])
  Inst os-prober (1.74ubuntu2 Ubuntu:19.10/eoan [amd64])
  Inst libzfs2linux (0.8.1-1ubuntu7 Ubuntu:19.10/eoan [amd64])
  Inst libzpool2linux (0.8.1-1ubuntu7 Ubuntu:19.10/eoan [amd64])
  Inst zfsutils-linux (0.8.1-1ubuntu7 Ubuntu:19.10/eoan [amd64])
  Inst zfs-zed (0.8.1-1ubuntu7 Ubuntu:19.10/eoan [amd64])
  Conf grub-common (2.04-1ubuntu2 Ubuntu:19.10/eoan [amd64])
  Conf grub2-common (2.04-1ubuntu2 Ubuntu:19.10/eoan [amd64])
  Conf grub-pc-bin (2.04-1ubuntu2 Ubuntu:19.10/eoan [amd64])
  Conf grub-pc (2.04-1ubuntu2 Ubuntu:19.10/eoan [amd64])
  Conf grub-gfxpayload-lists (0.7 Ubuntu:19.10/eoan [amd64])
  Conf linux-modules-5.0.0-1010-oem-osp1 (5.0.0-1010.11 Ubuntu:19.10/eoan 
[amd64])
  Conf linux-image-unsigned-5.0.0-1010-oem-osp1 (5.0.0-1010.11 
Ubuntu:19.10/eoan [amd64])
  Conf os-prober (1.74ubuntu2 Ubuntu:19.10/eoan [amd64])
  Conf libzfs2linux (0.8.1-1ubuntu7 Ubuntu:19.10/eoan [amd64])
  Conf libzpool2linux (0.8.1-1ubuntu7 Ubuntu:19.10/eoan [amd64])
  Conf zfsutils-linux (0.8.1-1ubuntu7 Ubuntu:19.10/eoan [amd64])
  Conf zfs-zed (0.8.1-1ubuntu7 Ubuntu:19.10/eoan [amd64])

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

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

[Kernel-packages] [Bug 1849981] Re: package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10

[Launchpad Bug Tracker]

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

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

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

Title:
  package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed
  zfs-dkms package post-installation script subprocess returned error
  exit status 10

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  Was upgrading to 19.10 and encountered this

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: zfs-dkms 0.8.1-1ubuntu14
  ProcVersionSignature: Ubuntu 5.0.0-30.32-generic 5.0.21
  Uname: Linux 5.0.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  Date: Sat Oct 26 10:28:20 2019
  ErrorMessage: installed zfs-dkms package post-installation script subprocess 
returned error exit status 10
  InstallationDate: Installed on 2013-06-08 (2331 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  SourcePackage: zfs-linux
  Title: package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed 
zfs-dkms package post-installation script subprocess returned error exit status 
10
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (0 days ago)

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

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

[Kernel-packages] [Bug 1814983] Re: zfs poor sustained read performance from ssd pool

[Colin Ian King]

It may be worth reading the following article as it has some tuning
tweaks that may help resolve your issue:

https://www.bountysource.com/issues/46175251-arc_prune-high-load-and-
soft-lockups

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

** Also affects: zfs via
   https://github.com/openzfs/zfs/issues/7559
   Importance: Unknown
   Status: Unknown

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

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

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

Title:
  zfs poor sustained read performance from ssd pool

Status in Native ZFS for Linux:
  Unknown
Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I'm seeing substantially slower read performance from an ssd pool than
  I expected.

  I have two pools on this computer; one ('fst') is four sata ssds, the
  other ('srv') is nine spinning metal drives.

  With a long-running ripgrep process on the fst pool, performance
  started out really good and grew to astonishingly good (iirc ~30kiops,
  as measured by zpool iostat -v 1). However after a few hours the
  performance has dropped to 30-40 iops. top reports an arc_reclaim and
  many arc_prune processes to be consuming most of the CPU time.

  I've included a screenshot of top, some output from zpool iostat -v 1,
  and arc_summary, with "===" to indicate the start of the next
  command's output:

  ===
  top (memory in gigabytes):

  top - 16:27:53 up 70 days, 16:03,  3 users,  load average: 35.67, 35.81, 35.58
  Tasks: 809 total,  19 running, 612 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  0.0 us, 58.1 sy,  0.0 ni, 39.2 id,  2.6 wa,  0.0 hi,  0.0 si,  0.0 
st
  GiB Mem :  125.805 total,0.620 free,   96.942 used,   28.243 buff/cache
  GiB Swap:5.694 total,5.688 free,0.006 used.   27.840 avail Mem 

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   
  
   1523 root  20   00.0m   0.0m   0.0m R 100.0  0.0 290:52.26 
arc_reclaim 
   4484 root  20   00.0m   0.0m   0.0m R  56.2  0.0   1:18.79 arc_prune 
  
   6225 root  20   00.0m   0.0m   0.0m R  56.2  0.0   1:11.92 arc_prune 
  
   7601 root  20   00.0m   0.0m   0.0m S  56.2  0.0   2:50.25 arc_prune 
  
  30891 root  20   00.0m   0.0m   0.0m S  56.2  0.0   1:33.08 arc_prune 
  
   3057 root  20   00.0m   0.0m   0.0m S  55.9  0.0   9:00.95 arc_prune 
  
   3259 root  20   00.0m   0.0m   0.0m R  55.9  0.0   3:16.84 arc_prune 
  
  24008 root  20   00.0m   0.0m   0.0m S  55.9  0.0   1:55.71 arc_prune 
  
   1285 root  20   00.0m   0.0m   0.0m R  55.6  0.0   3:20.52 arc_prune 
  
   5345 root  20   00.0m   0.0m   0.0m R  55.6  0.0   1:15.99 arc_prune 
  
  30121 root  20   00.0m   0.0m   0.0m S  55.6  0.0   1:35.50 arc_prune 
  
  31192 root  20   00.0m   0.0m   0.0m S  55.6  0.0   6:17.16 arc_prune 
  
  32287 root  20   00.0m   0.0m   0.0m S  55.6  0.0   1:28.02 arc_prune 
  
  32625 root  20   00.0m   0.0m   0.0m R  55.6  0.0   1:27.34 arc_prune 
  
  22572 root  20   00.0m   0.0m   0.0m S  55.3  0.0  10:02.92 arc_prune 
  
  31989 root  20   00.0m   0.0m   0.0m R  55.3  0.0   1:28.03 arc_prune 
  
   3353 root  20   00.0m   0.0m   0.0m R  54.9  0.0   8:58.81 arc_prune 
  
  10252 root  20   00.0m   0.0m   0.0m R  54.9  0.0   2:36.37 arc_prune 
  
   1522 root  20   00.0m   0.0m   0.0m S  53.9  0.0 158:42.45 arc_prune 
  
   3694 root  20   00.0m   0.0m   0.0m R  53.9  0.0   1:20.79 arc_prune 
  
  13394 root  20   00.0m   0.0m   0.0m R  53.9  0.0  10:35.78 arc_prune 
  
  24592 root  20   00.0m   0.0m   0.0m R  53.9  0.0   1:54.19 arc_prune 
  
  25859 root  20   00.0m   0.0m   0.0m S  53.9  0.0   1:51.71 arc_prune 
  
   8194 root  20   00.0m   0.0m   0.0m S  53.6  0.0   

[Kernel-packages] [Bug 1866866] Re: [FFe] Please accept patches for secure guest feature

[Frank Heimes]

Hello Łukasz, oh, I wasn't aware that he is not available, so many thanks for 
taking over and having a look at it and of course for the granting.
The qemu maintainer (cpaelzer) already had a look at this of course and was the 
one who prepared the PPA package and verbally gave his okay after code 
screening.
But I'm sure he's happy to leave another quick comment on that here, too.
Thx again!

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

Title:
  [FFe] Please accept patches for secure guest feature

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in qemu package in Ubuntu:
  Triaged
Status in s390-tools package in Ubuntu:
  Fix Released

Bug description:
  The secure guest feature (aka protvirt) affects multiple components (kernel, 
qemu and s390-tools - see below).
  While dedicated tickets for the different components exist since quite a 
while, the code arrived late and/or discussion to get it upstream accepted took 
longer than expected.
  (Even if we as of today didn't reached the kernel freeze, I'm already adding 
kernel to this FFe.)

  Since this is a very important feature the current IBM Z and LinuxONE
  family, it's requested to be included into focal, the next LTS
  release, to become exploitable by long running systems.

  The code is largely architecture specific.
  No brand new packages or new upstream version are requested, only the 
cherry-pick of commits (or PR) - so far everything is 'cherry-pick'-able.

  kernel:
  The patch set for the kernel is huge (30+ commits), but has only one common 
code patch (two files).
  The arch specific patches landed in between in linux-next, the arch specific 
one is expected to land there very soon (hours/days from now). The common-code 
patch ran through several hands and landed in between in Andrew Morton's mmots 
tree.
  A pre-screening of the code was done by the kernel team and it looked 
acceptable.
  (dedicated kernel ticket: https://bugs.launchpad.net/bugs/1835531)

  qemu:
  The entire code seems to be arch specific.
  Again a pre-screening of the maintainer lead to the fact that it should be 
acceptable, too.
  (dedicated qemu ticket: https://bugs.launchpad.net/bugs/1835546)

  s390-tools:
  The entire tool only exists for the s390x architecture.
  Hence obviously everything is arch specific on that.
  (dedicated s390-tools ticket: https://bugs.launchpad.net/bugs/1834534)

  Currently work is going on to test this function end to end based on Ubuntu 
components (means based on our s390-tools, qemu and kernel [focal master-next] 
trees).
  On top I applied the patches to the packages as well and did manual test 
buids.

  With that a potential regression can be considered as low - and even
  in case of a regression, it will affect s390x only.

  The patches are being staged for this feature in:
  https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3970

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

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

[Kernel-packages] [Bug 1869254] Re: Disco update: upstream stable patchset 2020-03-26

[Kamal Mostafa]

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    upstream stable patchset 2020-03-26
  
-upstream stable patchset 2020-03-26
-from git://git.kernel.org/
+ Ported from the following upstream stable releases:
+ v4.19.108, v5.4.24
+ 
+    from git://git.kernel.org/
+ 
+ irqchip/gic-v3-its: Fix misuse of GENMASK macro
+ iwlwifi: pcie: fix rb_allocator workqueue allocation
+ ipmi:ssif: Handle a possible NULL pointer reference
+ drm/msm: Set dma maximum segment size for mdss
+ dax: pass NOWAIT flag to iomap_apply
+ mac80211: consider more elements in parsing CRC
+ cfg80211: check wiphy driver existence for drvinfo report
+ s390/zcrypt: fix card and queue total counter wrap
+ qmi_wwan: re-add DW5821e pre-production variant
+ qmi_wwan: unconditionally reject 2 ep interfaces
+ ARM: dts: sti: fixup sound frame-inversion for stihxxx-b2120.dtsi
+ soc/tegra: fuse: Fix build with Tegra194 configuration
+ net: ena: fix potential crash when rxfh key is NULL
+ net: ena: fix uses of round_jiffies()
+ net: ena: add missing ethtool TX timestamping indication
+ net: ena: fix incorrect default RSS key
+ net: ena: rss: fix failure to get indirection table
+ net: ena: rss: store hash function as values and not bits
+ net: ena: fix incorrectly saving queue numbers when setting RSS indirection 
table
+ net: ena: ethtool: use correct value for crc32 hash
+ net: ena: ena-com.c: prevent NULL pointer dereference
+ cifs: Fix mode output in debugging statements
+ cfg80211: add missing policy for NL80211_ATTR_STATUS_CODE
+ sysrq: Restore original console_loglevel when sysrq disabled
+ sysrq: Remove duplicated sysrq message
+ net: fib_rules: Correctly set table field when table number exceeds 8 bits
+ net: mscc: fix in frame extraction
+ net: phy: restore mdio regs in the iproc mdio driver
+ net: sched: correct flower port blocking
+ nfc: pn544: Fix occasional HW initialization failure
+ sctp: move the format error check out of __sctp_sf_do_9_1_abort
+ ipv6: Fix route replacement with dev-only route
+ ipv6: Fix nlmsg_flags when splitting a multipath route
+ qede: Fix race between rdma destroy workqueue and link change event
+ net/tls: Fix to avoid gettig invalid tls record
+ ext4: potential crash on allocation error in ext4_alloc_flex_bg_array()
+ audit: fix error handling in audit_data_to_entry()
+ ACPICA: Introduce ACPI_ACCESS_BYTE_WIDTH() macro
+ ACPI: watchdog: Fix gas->access_width usage
+ KVM: VMX: check descriptor table exits on instruction emulation
+ HID: ite: Only bind to keyboard USB interface on Acer SW5-012 keyboard dock
+ HID: core: fix off-by-one memset in hid_report_raw_event()
+ HID: core: increase HID report buffer size to 8KiB
+ macintosh: therm_windtunnel: fix regression when instantiating devices
+ tracing: Disable trace_printk() on post poned tests
+ Revert "PM / devfreq: Modify the device name as devfreq(X) for sysfs"
+ amdgpu/gmc_v9: save/restore sdpif regs during S3
+ vhost: Check docket sk_family instead of call getname
+ HID: alps: Fix an error handling path in 'alps_input_configured()'
+ HID: hiddev: Fix race in in hiddev_disconnect()
+ MIPS: VPE: Fix a double free and a memory leak in 'release_vpe()'
+ i2c: altera: Fix potential integer overflow
+ i2c: jz4780: silence log flood on txabrt
+ drm/i915/gvt: Fix orphan vgpu dmabuf_objs' lifetime
+ drm/i915/gvt: Separate display reset from ALL_ENGINES reset
+ hv_netvsc: Fix unwanted wakeup in netvsc_attach()
+ usb: charger: assign specific number for enum value
+ s390/qeth: vnicc Fix EOPNOTSUPP precedence
+ net: netlink: cap max groups which will be considered in netlink_bind()
+ net: atlantic: fix use after free kasan warn
+ net: atlantic: fix potential error handling
+ net/smc: no peer ID in CLC decline for SMCD
+ net: ena: make ena rxfh support ETH_RSS_HASH_NO_CHANGE
+ namei: only return -ECHILD from follow_dotdot_rcu()
+ mwifiex: drop most magic 

[Kernel-packages] [Bug 1861610] Re: 'Elan touchpad' not detected in 'Ubuntu 19.04' on 'Lenovo ThinkBook 15 IIL'

[Bas Mevissen]

The problem here is that the ID of the Elan touchpad is not in the white
list of the driver. For a patch, see https://lore.kernel.org/linux-
input/20191202010253.GO248138@dtor-
ws/t/#m008d36e30f2711c0e3e33d396a444dd2ee98f8b1

So far, I could not find a tree carrying this change. So you need to
patch some kernel source to make it work. With the patch applied, no
need to modify the DSDT table nor do any other change.

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

Title:
  'Elan touchpad' not detected in 'Ubuntu 19.04' on 'Lenovo ThinkBook 15
  IIL'

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Elan touchpad on my Lenovo Thinkbook isn't being detected, and
  hence isn't working.

  `sudo acpidump | grep -C3 ELAN` gives me the device's ACPI id:

  ```bash
  ghosthawkzero@EchelonV:~$ sudo acpidump | grep -C3 ELAN
 2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46  INT1p. IDAD..SBF
 2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F  SSBFI.[.B.TPD2._
 2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00  ADR..IDAD..HID2.
 2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08  ._HID.ELAN0634..
 2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55  _CID.PNP0C50.._U
 2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11  ID..K._DSM..<.h.
 2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D  ..https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+subscriptions

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

[Kernel-packages] [Bug 1866866] Re: [FFe] Please accept patches for secure guest feature

[Christian Ehrhardt ]

There is no power box free this week, but indeed I'm +1 as well.

Test results look good as well (I've re-run them just to be extra sure) btw:
prep (x86_64): Pass   20  F/S/N  0/0/0 - RC 0 (15 min 55036 lin)
migrate (x86_64) : Pass  288  F/S/N  0/0/0 - RC 0 (60 min 214809 lin)
cross (x86_64)   : Pass   24  F/S/N  0/1/3 - RC 0 (51 min 47738 lin)
misc (x86_64): Pass  103  F/S/N  0/0/0 - RC 0 (39 min 72305 lin)

prep (s390x) : Pass   20  F/S/N  0/0/0 - RC 0 (14 min 43627 lin)
migrate (s390x)  : Pass  268  F/S/N  0/5/0 - RC 0 (66 min 161708 lin)
cross (s390x): Pass   19  F/S/N  1/1/2 - RC 1 (47 min 45401 lin)
misc (s390x) : Pass   67  F/S/N  0/0/0 - RC 0 (24 min 32119 lin)

@Frank - I guess he meant Cornelia being the s390x maintainer who already acked 
it upstream.
Furthermore in bug 1835546 we have the ack from the IBM test Team.
I think we are as ready as we can be.

Thanky everyone involved!

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

Title:
  [FFe] Please accept patches for secure guest feature

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in qemu package in Ubuntu:
  Triaged
Status in s390-tools package in Ubuntu:
  Fix Released

Bug description:
  The secure guest feature (aka protvirt) affects multiple components (kernel, 
qemu and s390-tools - see below).
  While dedicated tickets for the different components exist since quite a 
while, the code arrived late and/or discussion to get it upstream accepted took 
longer than expected.
  (Even if we as of today didn't reached the kernel freeze, I'm already adding 
kernel to this FFe.)

  Since this is a very important feature the current IBM Z and LinuxONE
  family, it's requested to be included into focal, the next LTS
  release, to become exploitable by long running systems.

  The code is largely architecture specific.
  No brand new packages or new upstream version are requested, only the 
cherry-pick of commits (or PR) - so far everything is 'cherry-pick'-able.

  kernel:
  The patch set for the kernel is huge (30+ commits), but has only one common 
code patch (two files).
  The arch specific patches landed in between in linux-next, the arch specific 
one is expected to land there very soon (hours/days from now). The common-code 
patch ran through several hands and landed in between in Andrew Morton's mmots 
tree.
  A pre-screening of the code was done by the kernel team and it looked 
acceptable.
  (dedicated kernel ticket: https://bugs.launchpad.net/bugs/1835531)

  qemu:
  The entire code seems to be arch specific.
  Again a pre-screening of the maintainer lead to the fact that it should be 
acceptable, too.
  (dedicated qemu ticket: https://bugs.launchpad.net/bugs/1835546)

  s390-tools:
  The entire tool only exists for the s390x architecture.
  Hence obviously everything is arch specific on that.
  (dedicated s390-tools ticket: https://bugs.launchpad.net/bugs/1834534)

  Currently work is going on to test this function end to end based on Ubuntu 
components (means based on our s390-tools, qemu and kernel [focal master-next] 
trees).
  On top I applied the patches to the packages as well and did manual test 
buids.

  With that a potential regression can be considered as low - and even
  in case of a regression, it will affect s390x only.

  The patches are being staged for this feature in:
  https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3970

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

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

[Kernel-packages] [Bug 1869253] [NEW] Disco update: upstream stable patchset 2020-03-26

[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-26
   from git://git.kernel.org/

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


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

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

Title:
  Disco update: upstream stable patchset 2020-03-26

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  SRU Justification

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

 upstream stable patchset 2020-03-26
 from git://git.kernel.org/

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

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

[Kernel-packages] [Bug 1869254] [NEW] Disco update: upstream stable patchset 2020-03-26

[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-26
   from git://git.kernel.org/

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


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

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

Title:
  Disco update: upstream stable patchset 2020-03-26

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  SRU Justification

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

 upstream stable patchset 2020-03-26
 from git://git.kernel.org/

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

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

[Kernel-packages] [Bug 1850238] Re: ucsi_ccg 50 second hang while resuming from s2ram with nvidia, recent kernels

[Timo Aaltonen]

** Changed in: linux-oem-osp1 (Ubuntu Bionic)
   Status: New => 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/1850238

Title:
  ucsi_ccg 50 second hang while resuming from s2ram with nvidia, recent
  kernels

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Won't Fix
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  New
Status in linux-oem-osp1 source package in Eoan:
  Won't Fix
Status in linux source package in Focal:
  Confirmed
Status in linux-oem-osp1 source package in Focal:
  Won't Fix
Status in linux package in Arch Linux:
  New

Bug description:
  === SRU Justification ===
  [Impact]
  Some systems have a "phantom" Nvidia UCSI, which prevent systems from
  suspending. 

  [Fix]
  ucsi_ccg is stuck in its probe routine because of the i2c bus never
  timeouts. Let it timeouts and probe can fail since it's just a phantom
  device.

  [Test]
  After applying this patch system can suspend/resume succesfully.

  [Regression Potential]
  Low. It's a trivial change to correctly handle timeout.

  === Original Bug Report ===

  Short version
  =
  I'm experiencing a 50-second hang each time I resume from a "deep" 
(suspend-to-RAM) sleep.

  It happens with the newer kernel (5.3 series; I'm currently running
  the version from eoan-proposed), but not with the version from the
  Ubuntu 18.04.3 LTS (uname says "5.0.0-31-generic #33~18.04.1-Ubuntu
  SMP").

  [I haven't yet tried to test the mainline builds, nor to find/confirm
  the regression range, as this seems like something that will take me
  another week, and I'm not sure if it would be helpful.]

  I narrowed the problem down to what I believe is a broken USB Type-C
  controller on the NVIDIA GPU: the ucsi_ccg driver for
  /sys/devices/pci:00/:00:01.0/:01:00.3/i2c-0/0-0008 reports
  a timeout for both the initial PPM_RESET command (on system startup)
  and for the SET_NOTIFICATION_ENABLE command the driver runs on resume.

  I guess the hang is the driver waiting for a response to
  SET_NOTIFICATION_ENABLE; it appears to have been added recently in
  
https://github.com/torvalds/linux/commit/a94ecde41f7e51e2742e53b5f151aee662c54d39,
  which could explain why I don't see the hang with 5.0.x.

  Creating /etc/modprobe.d/dell.conf with a `blacklist ucsi_ccg` line
  (and rebooting) makes the hang go away.

  Steps to reproduce
  ==
  (these are not the actual steps one can take to reproduce, starting from a 
new install; let me know if those will be useful)

  1. Boot Ubuntu 19.10 with NVIDIA GPU drivers uninstalled and the following 
kernel parameters 
:
   nouveau.modeset=0 nouveau.runpm=0   # force using integrated graphics
  # (the problem can be reproduced 
using NVIDIA's proprietary driver too, but I
  # guessed it's better to avoid 
it, and nouveau prints lots of errors with this GPU)
   mem_sleep_default=deep  # suspend to RAM; suspend-to-idle has 
its own problems on this system

  2. Run `dmesg -w` and wait a minute or two until a message like the
  following is printed:

   [  175.611346] ucsi_ccg 0-0008: failed to reset PPM!
   [  175.611355] ucsi_ccg 0-0008: PPM init failed (-110)

  (attempting to suspend before the PPM init timeout will fail to enter sleep 
at all.)
  (if your system doesn't report PPM init timeout, you probably won't see the 
hang on resume either)

  3. Run `sudo pm-suspend` (using the power button to suspend causes
  other problems)

  ...wait for the laptop to go to sleep and the fans to turn off.

  4. Press Enter on the built-in keyboard to resume. (Although the way
  we wake up the system doesn't seem to matter.)

  5. Observe a hang lasting for almost a minute before the system is
  operational, with dmesg reporting:

   [  299.331393] ata1.00: configured for UDMA/100
   

   [  346.133024] ucsi_ccg 0-0008: PPM NOT RESPONDING
   [  346.133039] PM: dpm_run_callback(): ucsi_ccg_resume+0x0/0x20 [ucsi_ccg] 
returns -110
   [  346.133042] PM: Device 0-0008 failed to resume: error -110
   ...
   [  346.141504] Restarting tasks ... done.
   [  346.340221] PM: suspend exit

  System info
  ===

  My Dell G3 3590 laptop has an NVIDIA "GeForce GTX 1660 Ti with Max-Q Design" 
GPU.
  NVIDIA's "Turing" chips include USB Type-C controller on the GPU (I read 
future VR headsets are supposed to use it 
),
 and indeed I'm seeing:

  # lspci -tv
  -[:00]-+-00.0  Intel Corporation 8th Gen Core 

[Kernel-packages] [Bug 1854480] Re: zfs_arc_max not working anymore in zfs 0.8.1

[BertN45]

I moved to Ubuntu 20.04 and I do not have that problem anymore.

I stopped with writing directly after the login the value to the file
/sys/module/zfs/parameters/zfs_arc_max.

I now only rely on "options zfs zfs_arc_max=3221225472" in
/etc/modprobe.d/zfs.conf.

Problem solved in 20.04 and I tried it by loading various VMs including
Windows 10 and run the updates for those VMs. The L1ARC size never
exceeded 3.01 GB of the 3.00 GB I allowed. I knew it would exceed for a
short period the max value, but in 19.10 at the time of the bug report,
it did exceed it sometimes with 1 GB or more.

I use and used conky to display L1ARC values constantly; L1ARC size
uncompressed; L1ARC size compressed; max allowed vale and L1ARC hit rate
and I have a tweaked bar display that would allow up to 102% :)

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

Title:
  zfs_arc_max not working anymore in zfs 0.8.1

Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  In the past I could limit the size of L1ARC by specifying "options zfs
  zfs_arc_max=3221225472" in /etc/modprobe.d/zfs.conf. I tried even to
  fill /sys/module/zfs/parameters/zfs_arc_max directly, but none of
  those methods limits the size of L1ARC. It worked nicely in zfs 0.7.x.

  Nowadays I use a nvme drive with 3400 MB/s read throughput and I see
  not much difference between e.g booting the system from nvme and
  rebooting the system from L1ARC. Having a 96-99% hit rate for the
  L1ARC, I like to free up some memory, thus avoiding some delay of
  freeing memory from L1ARC while loading a VM.

  -
  UPDATE:

  The system only limits the L1ARC, if we directly after the login write
  the zfs_arc_max value to the file
  /sys/module/zfs/parameters/zfs_arc_max.

  

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: zfsutils-linux 0.8.1-1ubuntu14.1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 29 06:19:15 2019
  InstallationDate: Installed on 2019-11-25 (3 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission 
denied: '/etc/sudoers.d/zfs']

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

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

[Kernel-packages] [Bug 1869254] Re: Disco update: upstream stable patchset 2020-03-26

[Kamal Mostafa]

** 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/1869254

Title:
  Disco update: upstream stable patchset 2020-03-26

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

Bug description:
  SRU Justification

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

     upstream stable patchset 2020-03-26

  Ported from the following upstream stable releases:
  v4.19.108, v5.4.24

     from git://git.kernel.org/

  irqchip/gic-v3-its: Fix misuse of GENMASK macro
  iwlwifi: pcie: fix rb_allocator workqueue allocation
  ipmi:ssif: Handle a possible NULL pointer reference
  drm/msm: Set dma maximum segment size for mdss
  dax: pass NOWAIT flag to iomap_apply
  mac80211: consider more elements in parsing CRC
  cfg80211: check wiphy driver existence for drvinfo report
  s390/zcrypt: fix card and queue total counter wrap
  qmi_wwan: re-add DW5821e pre-production variant
  qmi_wwan: unconditionally reject 2 ep interfaces
  ARM: dts: sti: fixup sound frame-inversion for stihxxx-b2120.dtsi
  soc/tegra: fuse: Fix build with Tegra194 configuration
  net: ena: fix potential crash when rxfh key is NULL
  net: ena: fix uses of round_jiffies()
  net: ena: add missing ethtool TX timestamping indication
  net: ena: fix incorrect default RSS key
  net: ena: rss: fix failure to get indirection table
  net: ena: rss: store hash function as values and not bits
  net: ena: fix incorrectly saving queue numbers when setting RSS indirection 
table
  net: ena: ethtool: use correct value for crc32 hash
  net: ena: ena-com.c: prevent NULL pointer dereference
  cifs: Fix mode output in debugging statements
  cfg80211: add missing policy for NL80211_ATTR_STATUS_CODE
  sysrq: Restore original console_loglevel when sysrq disabled
  sysrq: Remove duplicated sysrq message
  net: fib_rules: Correctly set table field when table number exceeds 8 bits
  net: mscc: fix in frame extraction
  net: phy: restore mdio regs in the iproc mdio driver
  net: sched: correct flower port blocking
  nfc: pn544: Fix occasional HW initialization failure
  sctp: move the format error check out of __sctp_sf_do_9_1_abort
  ipv6: Fix route replacement with dev-only route
  ipv6: Fix nlmsg_flags when splitting a multipath route
  qede: Fix race between rdma destroy workqueue and link change event
  net/tls: Fix to avoid gettig invalid tls record
  ext4: potential crash on allocation error in ext4_alloc_flex_bg_array()
  audit: fix error handling in audit_data_to_entry()
  ACPICA: Introduce ACPI_ACCESS_BYTE_WIDTH() macro
  ACPI: watchdog: Fix gas->access_width usage
  KVM: VMX: check descriptor table exits on instruction emulation
  HID: ite: Only bind to keyboard USB interface on Acer SW5-012 keyboard dock
  HID: core: fix off-by-one memset in hid_report_raw_event()
  HID: core: increase HID report buffer size to 8KiB
  macintosh: therm_windtunnel: fix regression when instantiating devices
  tracing: Disable trace_printk() on post poned tests
  Revert "PM / devfreq: Modify the device name as devfreq(X) for sysfs"
  amdgpu/gmc_v9: save/restore sdpif regs during S3
  vhost: Check docket sk_family instead of call getname
  HID: alps: Fix an error handling path in 'alps_input_configured()'
  HID: hiddev: Fix race in in hiddev_disconnect()
  MIPS: VPE: Fix a double free and a memory leak in 'release_vpe()'
  i2c: altera: Fix potential integer overflow
  i2c: jz4780: silence log flood on txabrt
  drm/i915/gvt: Fix orphan vgpu dmabuf_objs' lifetime
  drm/i915/gvt: Separate display reset from ALL_ENGINES reset
  hv_netvsc: Fix unwanted wakeup in netvsc_attach()
  usb: charger: assign specific number for enum value
  s390/qeth: vnicc Fix EOPNOTSUPP precedence
  net: netlink: cap max groups which will be considered in netlink_bind()
  net: atlantic: fix use after free kasan warn
  net: atlantic: fix potential error handling
  net/smc: no peer ID in CLC decline for SMCD
  net: ena: make ena rxfh support ETH_RSS_HASH_NO_CHANGE
  namei: only return -ECHILD from follow_dotdot_rcu()
  mwifiex: drop most magic numbers from mwifiex_process_tdls_action_frame()
  mwifiex: delete unused mwifiex_get_intf_num()
  KVM: SVM: Override default MMIO mask if memory encryption is enabled
  KVM: Check for a bad hva before dropping into the ghc 

[Kernel-packages] [Bug 1861395] Re: system hang: i915 Resetting rcs0 for hang on rcs0

[Warren]

Unfortunately I can't upgrade from 5.4.0 so I added the following to
/etc/modprobe.d/modesetting.conf

options i915 modeset=1 reset=1

See other options with modinfo i915

This seems to have made the problem occur less frequently.

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

Title:
  system hang: i915 Resetting rcs0 for hang on rcs0

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Eoan:
  Invalid
Status in linux source package in Focal:
  Fix Released

Bug description:
  System hangs, unknown cause, When this happens, the mouse pointer
  still moves, but I can't do anything else with the keys or clicking in
  the UI.  Only recover I have found is a hard power-off

  Last bit of kern.log below:

  Jan 30 12:43:51 aries kernel: [ 6649.263031] i915 :00:02.0: GPU HANG: 
ecode 9:1:0x, hang on rcs0
  Jan 30 12:43:51 aries kernel: [ 6649.263032] GPU hangs can indicate a bug 
anywhere in the entire gfx stack, including userspace.
  Jan 30 12:43:51 aries kernel: [ 6649.263033] Please file a _new_ bug report 
on bugs.freedesktop.org against DRI -> DRM/Intel
  Jan 30 12:43:51 aries kernel: [ 6649.263033] drm/i915 developers can then 
reassign to the right component if it's not a kernel issue.
  Jan 30 12:43:51 aries kernel: [ 6649.263034] The GPU crash dump is required 
to analyze GPU hangs, so please always attach it.
  Jan 30 12:43:51 aries kernel: [ 6649.263034] GPU crash dump saved to 
/sys/class/drm/card0/error
  Jan 30 12:43:51 aries kernel: [ 6649.264039] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:43:51 aries kernel: [ 6649.264778] [drm:gen8_reset_engines [i915]] 
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
  Jan 30 12:43:51 aries kernel: [ 6649.265046] i915 :00:02.0: Resetting 
chip for hang on rcs0
  Jan 30 12:43:51 aries kernel: [ 6649.267018] [drm:gen8_reset_engines [i915]] 
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
  Jan 30 12:43:51 aries kernel: [ 6649.267764] [drm:gen8_reset_engines [i915]] 
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
  Jan 30 12:43:59 aries kernel: [ 6657.262680] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:01 aries kernel: [ 6659.246609] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:09 aries kernel: [ 6667.246324] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:09 aries kernel: [ 6667.494008] show_signal_msg: 20 callbacks 
suppressed
  Jan 30 12:44:09 aries kernel: [ 6667.494011] GpuWatchdog[6827]: segfault at 0 
ip 55fd01917ded sp 7f63043cc480 error 6 in chrome[55fcfd9dc000+7171000]
  Jan 30 12:44:09 aries kernel: [ 6667.494017] Code: 48 c1 c9 03 48 81 f9 af 00 
00 00 0f 87 c9 00 00 00 48 8d 15 a9 5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be 
01 00 00 00 ff 50 30  04 25 00 00 00 00 37 13 00 00 c6 05 c1 6d a4 03 01 80 
7d 8f 00
  Jan 30 12:44:23 aries kernel: [ 6681.265885] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:25 aries kernel: [ 6683.245838] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:27 aries kernel: [ 6685.261749] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:29 aries kernel: [ 6687.245641] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:31 aries kernel: [ 6689.261618] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:51 aries kernel: [ 6709.260901] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0

  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
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 30 12:51:24 2020
  InstallationDate: Installed on 2018-06-18 (591 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-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-22 (8 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dpb   115653 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2018-06-18 (604 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0097 Validity Sensors, Inc. 
   Bus 001 Device 003: ID 

[Kernel-packages] [Bug 1869252] [NEW] Disco update: upstream stable patchset 2020-03-26

[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-26
   from git://git.kernel.org/

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


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

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

Title:
  Disco update: upstream stable patchset 2020-03-26

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  SRU Justification

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

 upstream stable patchset 2020-03-26
 from git://git.kernel.org/

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

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

[Kernel-packages] [Bug 1863581] Re: Ubuntu 20.04: megaraid_sas driver update to version 07.713.01.00-rc1

[Michael Reed]

** Tags added: hwcert-server

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

Title:
  Ubuntu 20.04: megaraid_sas driver update to version 07.713.01.00-rc1

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

Bug description:
  [IMPACT]
  This is a feature request to update megaraid_sas driver in Ubuntu 20.04 
release to latest Linux upstream tip.
  The current latest upstream megaraid_sas driver version is- 07.713.01.00-rc1.
  The current latest Ubuntu 20.04 Pre GA kernel has megaraid_sas driver 
version- 07.710.50.00-rc1. This will allow users to utilize features of
  the PERC 11 device. For this reason, Broadcom and Dell have requested that we 
pull these patches to update the megaraid_sas driver to the current upstream 
version.

  [FIXES]
  Below set of upstream commit ids will lift driver version to 07.713.01.00-rc1 
from 07.710.50.00-rc1:

  92b4f9d15059 scsi: megaraid_sas: fixup MSIx interrupt setup during resume
  824b72db5086 scsi: megaraid_sas: Update driver version to 07.713.01.00-rc1
  4d1634b8d12e scsi: megaraid_sas: Use Block layer API to check SCSI device 
in-flight IO requests
  56ee0c585602 scsi: megaraid_sas: Limit the number of retries for the IOCTLs 
causing firmware fault
  6d7537270e32 scsi: megaraid_sas: Do not initiate OCR if controller is not in 
ready state
  201a810cc188 scsi: megaraid_sas: Re-Define enum DCMD_RETURN_STATUS
  eeb63c23ffe1 scsi: megaraid_sas: Do not set HBA Operational if FW is not in 
operational state
  9330a0fd827a scsi: megaraid_sas: Do not kill HBA if JBOD Seqence map or RAID 
map is disabled
  eb974f34bb9d scsi: megaraid_sas: Do not kill host bus adapter, if adapter is 
already dead
  6e73550670ed scsi: megaraid_sas: Update optimal queue depth for SAS and NVMe 
devices
  a7faf81d7858 scsi: megaraid_sas: Set no_write_same only for Virtual Disk
  499e7246d6da scsi: megaraid_sas: Reset adapter if FW is not in READY state 
after device resume
  73374b39b01e scsi: megaraid_sas: Make poll_aen_lock static
  01b8bca81e18 compat_ioctl: use correct compat_ptr() translation in drivers
  8cfb8e40d686 scsi: megaraid_sas: remove unused variables 'debugBlk','fusion'
  ff7ca7fd03ce scsi: megaraid_sas: Unique names for MSI-X vectors
  9ab089d30bcf scsi: megaraid_sas: Introduce module parameter for default queue 
depth
  e5460f084b84 scsi: megaraid_sas: Fix a compilation warning
  88d5c343949e scsi: megaraid_sas: Make a bunch of functions static
  e45ab43b1d40 scsi: megaraid_sas: Make some functions static
  3b5f307ef3cb scsi: megaraid_sas: fix panic on loading firmware crashdump
  359603a3847e scsi: megaraid_sas: fix spelling mistake "megarid_sas" -> 
"megaraid_sas"
  07d9aa143464 scsi: megaraid_sas: set an unlimited max_segment_size

  Here is the link to latest Linux upstream megaraid_sas driver source:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/scsi/megaraid

  Please let me know if any further information is required.

  Thanks,
  Sumit

  All are clean cherry picks into the 5.4 branch and can be pulled from the
  following branch:

  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/focal/+ref/lp1863581_megaraid_sas

  [TESTING]
  Modinfo should show that the megaraid_sas driver has been updated to 
07.713.01.00

  [REGRESSION RISK]
  Low - Focal is not yet released, this is not being backported to current 
releases.

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

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

[Kernel-packages] [Bug 1863574] Re: Update mpt3sas Driver to 33.100.00.00 for Ubuntu 20.04

[Michael Reed]

** Tags added: focal hwcert-server

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

Title:
  Update mpt3sas Driver to 33.100.00.00 for Ubuntu 20.04

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

Bug description:
  [IMPACT]
  This is a feature request to update the mpt3sas driver in focal to latest 
version 33.100.00.00 in Ubuntu 20.04.  This will allow users to use
  fixes and enhancements that landed upstream in 5.6.  For this reason,
  Broadcom and Dell have requested that we pull these patches to update the 
  mpt3sas driver to the current upstream version.  

  [FIXES]
  The following commit ID's from Broadcom that whould be cherry-picked form 
mainline

  commit c53cf10ef6d9faeee9baa1fab824139c6f10a134
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=c53cf10ef6d9faeee9baa1fab824139c6f10a134
  commit c50ed99cd56ee725d9e14dffec8e8f1641b8ca30
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=c50ed99cd56ee725d9e14dffec8e8f1641b8ca30
  commit c6bdb6a10892d1130638a5e28d1523a813e45d5e
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=c6bdb6a10892d1130638a5e28d1523a813e45d5e
  commit 5b061980e362820894d7d884370b37005bed23ec
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=5b061980e362820894d7d884370b37005bed23ec
  commit c59777189433621392f6f5c82ecfc62f00a1232d
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=c59777189433621392f6f5c82ecfc62f00a1232d
  commit fce0aa08792b3ae725395fa25d44507dee0b603b
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=fce0aa08792b3ae725395fa25d44507dee0b603b
  commit e8c2307e6a690db9aaff84153b2857c5c4dfd969
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=e8c2307e6a690db9aaff84153b2857c5c4dfd969
  commit 36c6c7f75b0998f5a4b5c79cbb94ee1ab4ee35c0
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=36c6c7f75b0998f5a4b5c79cbb94ee1ab4ee35c0
  commit d3f623ae8e0323ca434ee9029100312a8be37773
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=d3f623ae8e0323ca434ee9029100312a8be37773
  commit 1ade26b616cc2da0b7277a97e3799c99bae0655b
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=1ade26b616cc2da0b7277a97e3799c99bae0655b
  commit ee560e7bbab0c10cf3f0e71997fbc354ab2ee5cb
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=ee560e7bbab0c10cf3f0e71997fbc354ab2ee5cb
  commit 5bb2f743cdaa6da618e77a6aab5c38b46072365b
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=5bb2f743cdaa6da618e77a6aab5c38b46072365b
  commit 3524a38e594dd5f090cbc3226e5f47cb4067fac7
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=3524a38e594dd5f090cbc3226e5f47cb4067fac7
  commit d8b2625f4699a36b1753d87e96b0c50a4531c065
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=d8b2625f4699a36b1753d87e96b0c50a4531c065
  commit 9e64fd1e65f72d229f96fcf390576e772770a01c
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=9e64fd1e65f72d229f96fcf390576e772770a01c
  commit 77fd4f2c88bf83205a21f9ca49fdcc0c7868dba9
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=77fd4f2c88bf83205a21f9ca49fdcc0c7868dba9
  commit b06ff10249036eec74fa8565503ac40d0ee92213
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=b06ff10249036eec74fa8565503ac40d0ee92213
  commit 29f571f8b4cc652cae9244630f714a610549d301
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=29f571f8b4cc652cae9244630f714a610549d301
  commit a8a6cbcd038de4ee3722c17edd7a4d84ce423f7d
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=a8a6cbcd038de4ee3722c17edd7a4d84ce423f7d
  commit a066f4c31359d07b1a2c5144b4b9a29901365fd0
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=a066f4c31359d07b1a2c5144b4b9a29901365fd0
  commit dd180e4eedfd85b80020a6fd566601f4765a9d69
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=dd180e4eedfd85b80020a6fd566601f4765a9d69
  commit 08e7378ee331a803cfdd91c512a3dea040f1da79
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=08e7378ee331a803cfdd91c512a3dea040f1da79
  commit 764f472ba4a7a0c18107ebfbe1a9f1f5f5a1e411
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=764f472ba4a7a0c18107ebfbe1a9f1f5f5a1e411
  commit 

[Kernel-packages] [Bug 1854480] Re: zfs_arc_max not working anymore in zfs 0.8.1

[Colin Ian King]

I'll close this bug report if that's OK.

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

Title:
  zfs_arc_max not working anymore in zfs 0.8.1

Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  In the past I could limit the size of L1ARC by specifying "options zfs
  zfs_arc_max=3221225472" in /etc/modprobe.d/zfs.conf. I tried even to
  fill /sys/module/zfs/parameters/zfs_arc_max directly, but none of
  those methods limits the size of L1ARC. It worked nicely in zfs 0.7.x.

  Nowadays I use a nvme drive with 3400 MB/s read throughput and I see
  not much difference between e.g booting the system from nvme and
  rebooting the system from L1ARC. Having a 96-99% hit rate for the
  L1ARC, I like to free up some memory, thus avoiding some delay of
  freeing memory from L1ARC while loading a VM.

  -
  UPDATE:

  The system only limits the L1ARC, if we directly after the login write
  the zfs_arc_max value to the file
  /sys/module/zfs/parameters/zfs_arc_max.

  

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: zfsutils-linux 0.8.1-1ubuntu14.1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 29 06:19:15 2019
  InstallationDate: Installed on 2019-11-25 (3 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission 
denied: '/etc/sudoers.d/zfs']

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

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

[Kernel-packages] [Bug 1850238] Re: ucsi_ccg 50 second hang while resuming from s2ram with nvidia, recent kernels

[Kai-Heng Feng]

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

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

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

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

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

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

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

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

Title:
  ucsi_ccg 50 second hang while resuming from s2ram with nvidia, recent
  kernels

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

Bug description:
  === SRU Justification ===
  [Impact]
  Some systems have a "phantom" Nvidia UCSI, which prevent systems from
  suspending. 

  [Fix]
  ucsi_ccg is stuck in its probe routine because of the i2c bus never
  timeouts. Let it timeouts and probe can fail since it's just a phantom
  device.

  [Test]
  After applying this patch system can suspend/resume succesfully.

  [Regression Potential]
  Low. It's a trivial change to correctly handle timeout.

  === Original Bug Report ===

  Short version
  =
  I'm experiencing a 50-second hang each time I resume from a "deep" 
(suspend-to-RAM) sleep.

  It happens with the newer kernel (5.3 series; I'm currently running
  the version from eoan-proposed), but not with the version from the
  Ubuntu 18.04.3 LTS (uname says "5.0.0-31-generic #33~18.04.1-Ubuntu
  SMP").

  [I haven't yet tried to test the mainline builds, nor to find/confirm
  the regression range, as this seems like something that will take me
  another week, and I'm not sure if it would be helpful.]

  I narrowed the problem down to what I believe is a broken USB Type-C
  controller on the NVIDIA GPU: the ucsi_ccg driver for
  /sys/devices/pci:00/:00:01.0/:01:00.3/i2c-0/0-0008 reports
  a timeout for both the initial PPM_RESET command (on system startup)
  and for the SET_NOTIFICATION_ENABLE command the driver runs on resume.

  I guess the hang is the driver waiting for a response to
  SET_NOTIFICATION_ENABLE; it appears to have been added recently in
  
https://github.com/torvalds/linux/commit/a94ecde41f7e51e2742e53b5f151aee662c54d39,
  which could explain why I don't see the hang with 5.0.x.

  Creating /etc/modprobe.d/dell.conf with a `blacklist ucsi_ccg` line
  (and rebooting) makes the hang go away.

  Steps to reproduce
  ==
  (these are not the actual steps one can take to reproduce, starting from a 
new install; let me know if those will be useful)

  1. Boot Ubuntu 19.10 with NVIDIA GPU drivers uninstalled and the following 
kernel parameters 
:
   nouveau.modeset=0 nouveau.runpm=0   # force using integrated graphics
  # (the problem can be reproduced 
using NVIDIA's proprietary driver too, but I
  # guessed it's better to avoid 
it, and nouveau prints lots of errors with this GPU)
   mem_sleep_default=deep  # suspend to RAM; suspend-to-idle has 
its own problems on this system

  2. Run `dmesg -w` and wait a minute or two until a message like the
  following is printed:

   [  175.611346] ucsi_ccg 0-0008: failed to reset PPM!
   [  175.611355] ucsi_ccg 0-0008: PPM init failed (-110)

  (attempting to suspend before the PPM init timeout will fail to enter sleep 
at all.)
  (if your system doesn't report PPM init timeout, you probably won't see the 
hang on resume either)

  3. Run `sudo pm-suspend` (using the power button to suspend causes
  other problems)

  ...wait for the laptop to go to sleep and the fans to turn off.

  4. Press Enter on the built-in keyboard to resume. (Although the way
  we wake up the system doesn't seem to matter.)

  5. Observe a hang lasting for almost a minute before the system is
  operational, with dmesg reporting:

   [  299.331393] ata1.00: configured for UDMA/100
   

   [  346.133024] ucsi_ccg 0-0008: PPM NOT RESPONDING
   [  346.133039] PM: dpm_run_callback(): ucsi_ccg_resume+0x0/0x20 [ucsi_ccg] 
returns -110
   [  346.133042] PM: Device 0-0008 failed to resume: error -110
   ...
   [  346.141504] Restarting tasks ... done.
   [  346.340221] PM: suspend exit

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

[Ubuntu Kernel Bot]

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

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

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


** Tags added: verification-needed-bionic

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

Title:
  Missing wireless network interface after kernel 5.3.0-43 upgrade with
  eoan

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  I updated to latest kernel: initrd.img-5.3.0-43-generic and find that 
bluetooth is enabled and no wireless connection. When I stop bluetooth I go 
into airplane mode.  I cannot find any wireless connection in network or 
wireless connection setup in settings.  ifconfig shows there is no wireless 
interface setup. When I go back to kernel 5.3.0-42 everything is working 
correctly. I am using an HP laptop.
  I can see the wireless network controller with lshw:

  lshw -C network
*-network
 description: Ethernet interface
 product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0
 bus info: pci@:02:00.0
 logical name: eno1
 version: 15
 serial: b4:b6:86:e7:67:29
 size: 100Mbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress msix bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=r8169 
duplex=full firmware=rtl8168h-2_0.0.2 02/26/15 ip=192.168.1.108 latency=0 
link=yes multicast=yes port=MII speed=100Mbit/s
 resources: irq:38 ioport:e000(size=256) memory:fe904000-fe904fff 
memory:fe90-fe903fff
*-network
 description: Network controller
 product: Dual Band Wireless-AC 3168NGW [Stone Peak]
 vendor: Intel Corporation
 physical id: 0
 bus info: pci@:03:00.0
 version: 10
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list
 configuration: driver=iwlwifi latency=0
 resources: irq:43 memory:fe80-fe801fff

  lspci |grep Network
  03:00.0 Network controller: Intel Corporation Dual Band Wireless-AC 3168NGW 
[Stone Peak] (rev 10)

  iwconfig
  lo no wireless extensions.

  eno1 no wireless extensions.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-43-generic 5.3.0-43.36
  ProcVersionSignature: Ubuntu 5.3.0-43.36-generic 5.3.18
  Uname: Linux 5.3.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rustin 1684 F pulseaudio
  Date: Sun Mar 22 05:43:04 2020
  InstallationDate: Installed on 2018-11-30 (478 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: HP HP Pavilion Laptop 17-ar0xx
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-43-generic 
root=UUID=29898130-1fa9-464b-88cf-ed44cfd58f76 ro pcie_aspm=force 
acpi_backlight=vendor
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-43-generic N/A
   linux-backports-modules-5.3.0-43-generic  N/A
   linux-firmware1.183.5
  RfKill:
   0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/12/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8357
  dmi.board.vendor: HP
  dmi.board.version: 37.34
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

[Kernel-packages] [Bug 1866866] Re: [FFe] Please accept patches for secure guest feature

[Frank Heimes]

Oh, hehe, since I saw (from LP 1835546) that Cornelia already ACKed it, I 
thought that Lukasz probably meant you, Christian - apologize.
And yes, two teams at IBM tested it successfully.
I will see if I can get a Power9 box freed up on short notice ...

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

Title:
  [FFe] Please accept patches for secure guest feature

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in qemu package in Ubuntu:
  Triaged
Status in s390-tools package in Ubuntu:
  Fix Released

Bug description:
  The secure guest feature (aka protvirt) affects multiple components (kernel, 
qemu and s390-tools - see below).
  While dedicated tickets for the different components exist since quite a 
while, the code arrived late and/or discussion to get it upstream accepted took 
longer than expected.
  (Even if we as of today didn't reached the kernel freeze, I'm already adding 
kernel to this FFe.)

  Since this is a very important feature the current IBM Z and LinuxONE
  family, it's requested to be included into focal, the next LTS
  release, to become exploitable by long running systems.

  The code is largely architecture specific.
  No brand new packages or new upstream version are requested, only the 
cherry-pick of commits (or PR) - so far everything is 'cherry-pick'-able.

  kernel:
  The patch set for the kernel is huge (30+ commits), but has only one common 
code patch (two files).
  The arch specific patches landed in between in linux-next, the arch specific 
one is expected to land there very soon (hours/days from now). The common-code 
patch ran through several hands and landed in between in Andrew Morton's mmots 
tree.
  A pre-screening of the code was done by the kernel team and it looked 
acceptable.
  (dedicated kernel ticket: https://bugs.launchpad.net/bugs/1835531)

  qemu:
  The entire code seems to be arch specific.
  Again a pre-screening of the maintainer lead to the fact that it should be 
acceptable, too.
  (dedicated qemu ticket: https://bugs.launchpad.net/bugs/1835546)

  s390-tools:
  The entire tool only exists for the s390x architecture.
  Hence obviously everything is arch specific on that.
  (dedicated s390-tools ticket: https://bugs.launchpad.net/bugs/1834534)

  Currently work is going on to test this function end to end based on Ubuntu 
components (means based on our s390-tools, qemu and kernel [focal master-next] 
trees).
  On top I applied the patches to the packages as well and did manual test 
buids.

  With that a potential regression can be considered as low - and even
  in case of a regression, it will affect s390x only.

  The patches are being staged for this feature in:
  https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3970

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

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

[Françesc]

If more information needed...

product: Aspire E5-551G (Aspire E5-551G_086A_V1.08)

 descripción: CPU
  producto: AMD A10-7300 Radeon R6, 10 Compute Cores 4C+6G
  fabricante: Advanced Micro Devices [AMD]
  id físico: 4
  información del bus: cpu@0
  versión: AMD A10-7300 Radeon R6, 10 Compute Cores 4C+6G
  serie: NotSupport
  ranura: Socket FP3
  tamaño: 1250MHz
  capacidad: 1900MHz
  anchura: 64 bits
  reloj: 100MHz

 descripción: VGA compatible controller
 producto: Kaveri [Radeon R6 Graphics]

  *-disk
 descripción: ATA Disk
 producto: SanDisk SSD PLUS
 id físico: 0.0.0
 información del bus: scsi@0:0.0.0
 nombre lógico: /dev/sda
 versión: 00RL
 serie: 184594802576
 tamaño: 447GiB (480GB)
 capacidades: partitioned partitioned:dos
 configuración: ansiversion=5 logicalsectorsize=512 sectorsize=512 
signature=c22322fd
   *-volume:0
descripción: Windows NTFS volumen
id físico: 1
información del bus: scsi@0:0.0.0,1
nombre lógico: /dev/sda1
versión: 3.1
serie: d80b-5c10
tamaño: 498MiB
capacidad: 500MiB
capacidades: primary bootable ntfs initialized
configuración: clustersize=4096 created=2017-09-11 18:10:39 
filesystem=ntfs label=Reservado para el sistema modified_by_chkdsk=true 
mounted_on_nt4=true resize_log_file=true state=dirty upgrade_on_mount=true
   *-volume:1
descripción: Windows NTFS volumen
id físico: 2
información del bus: scsi@0:0.0.0,2
nombre lógico: /dev/sda2
versión: 3.1
serie: a8b72e55-2ee1-2a4e-91d9-182560e67966
tamaño: 95GiB
capacidad: 95GiB
capacidades: primary ntfs initialized
configuración: clustersize=4096 created=2017-11-30 15:23:41 
filesystem=ntfs state=clean
   *-volume:2
descripción: Extended partition
id físico: 3
información del bus: scsi@0:0.0.0,3
nombre lógico: /dev/sda3
tamaño: 351GiB
capacidad: 351GiB
capacidades: primary extended partitioned partitioned:extended
  *-logicalvolume
   descripción: partición EXT4
   fabricante: Linux
   id físico: 5
   nombre lógico: /dev/sda5
   nombre lógico: /
   versión: 1.0
   serie: 3aac0dd9-fe52-4e9e-9abf-4fa7f443fc08
   tamaño: 351GiB
   capacidad: 351GiB
   capacidades: journaled extended_attributes large_files 
huge_files dir_nlink recover 64bit extents ext4 ext2 initialized
   configuración: created=2019-01-23 13:51:25 filesystem=ext4 
lastmountpoint=/ modified=2020-03-17 14:38:03 mount.fstype=ext4 
mount.options=rw,relatime,errors=remount-ro,data=ordered mounted=2020-03-17 
14:38:09 state=mounted

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

[Kernel-packages] [Bug 1814938] Re: drm.edid_firmware fails to load firmware where crypsetup-initramfs is installed

[Kai-Heng Feng]

** Package changed: linux (Ubuntu) => initramfs-tools (Ubuntu)

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

Title:
  drm.edid_firmware fails to load firmware where crypsetup-initramfs is
  installed

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  My HP LP2475W monitor reports incorrect EDID info resulting in bad
  image quality.

  It can be fixed with a customized edid file, and adding
  drm.edid_firmware kernel boot parameter.

  But in Ubuntu 18.04.1 and Ubuntu 18.10, if crypsetup-initramfs package
  is installed, it fails to load the firmware file.

  Detailed bug report:

  Following this istructions (https://blog.tingping.se/2018/12/01
  /amdgpu-fullrgb.html), I created a modified edid.bin file in
  /lib/firmware/edid/edid.bin and passed drm.edid_firmware=edid/edid.bin
  to the kernel at boot.

  In my daily Ubuntu 18.04.1 dmesg report this error and I could not solve it.
  [1.173897] platform HDMI-A-1: Direct firmware load for edid/edid.bin 
failed with error -2

  So I tried in a fresh Ubuntu 18.10 and it worked nicely, no error and nice 
crisp display image.
  But when I began to install the software I need for daily use it ceased to 
work and began to show the same message as in my work Ubuntu 18.04.1.

  After some test it seems that the problem occurs after I install cryptsetup:
  --
  dmesg | grep edid
  [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.18.0-14-generic 
root=UUID=dfb5fdf3-b93b-4abf-99fd-d5a7ec4e66df ro 
drm.edid_firmware=edid/edid.bin quiet splash vt.handoff=1
  [0.00] Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-4.18.0-14-generic 
root=UUID=dfb5fdf3-b93b-4abf-99fd-d5a7ec4e66df ro 
drm.edid_firmware=edid/edid.bin quiet splash vt.handoff=1
  [3.792846] [drm] Got external EDID base block and 1 extension from 
"edid/edid.bin" for connector "HDMI-A-1"
  --

  I purged cryptsetup but the problem persisted, so I removed too 
cryptsetup-initramfs and the the problem disapeared and the edid file is loaded 
again, improving the display quality:
  --
  dmesg | grep edid
  [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.18.0-14-generic 
root=UUID=dfb5fdf3-b93b-4abf-99fd-d5a7ec4e66df ro 
drm.edid_firmware=edid/edid.bin quiet splash vt.handoff=1
  [0.00] Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-4.18.0-14-generic 
root=UUID=dfb5fdf3-b93b-4abf-99fd-d5a7ec4e66df ro 
drm.edid_firmware=edid/edid.bin quiet splash vt.handoff=1
  [3.717878] [drm] Got external EDID base block and 1 extension from 
"edid/edid.bin" for connector "HDMI-A-1"
  ---

  This question in AskUbuntu suggest that there are more people with
  this probem (https://askubuntu.com/questions/1113195/how-to-output-
  full-range-rgb-in-ubuntu-18-04-1)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-14-generic 4.18.0-14.15
  ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20
  Uname: Linux 4.18.0-14-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  david  2007 F pulseaudio
   /dev/snd/pcmC0D1p:   david  2007 F...m pulseaudio
   /dev/snd/controlC1:  david  2007 F pulseaudio
  Date: Wed Feb  6 18:37:39 2019
  InstallationDate: Installed on 2019-02-06 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   lono wireless extensions.
   
   enp7s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-14-generic 
root=UUID=dfb5fdf3-b93b-4abf-99fd-d5a7ec4e66df ro 
drm.edid_firmware=edid/edid.bin quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-14-generic N/A
   linux-backports-modules-4.18.0-14-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/11/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: U1n
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z68X-UD3H-B3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 

[Kernel-packages] [Bug 1837525] Re: [20.04 FEAT] Set Architecture Level (ALS) to z13

[Launchpad Bug Tracker]

This bug was fixed in the package atlas - 3.10.3-8ubuntu7

---
atlas (3.10.3-8ubuntu7) focal; urgency=medium

  * s390x: Drop zEC12 build, bump default build to z13, with
"cross-compiled" z14 build. LP: #1837525

 -- Dimitri John Ledkov   Thu, 26 Mar 2020 11:13:42
+

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

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

Title:
  [20.04 FEAT] Set Architecture Level (ALS) to z13

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in atlas package in Ubuntu:
  Fix Released
Status in gcc-9 package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  IBM requests to update the Architecture Level Set (ALS) as follow..
  march=z13
  mtune=z15

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

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

[Kernel-packages] [Bug 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'

[You-Sheng Yang]

** Summary changed:

- 'Elan touchpad' not detected in 'Ubuntu 19.04' on 'Lenovo ThinkBook 15 IIL'
+ 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'

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

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

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

Title:
  'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  New
Status in linux source package in Eoan:
  New
Status in linux source package in Focal:
  Confirmed

Bug description:
  The Elan touchpad on my Lenovo Thinkbook isn't being detected, and
  hence isn't working.

  `sudo acpidump | grep -C3 ELAN` gives me the device's ACPI id:

  ```bash
  ghosthawkzero@EchelonV:~$ sudo acpidump | grep -C3 ELAN
 2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46  INT1p. IDAD..SBF
 2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F  SSBFI.[.B.TPD2._
 2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00  ADR..IDAD..HID2.
 2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08  ._HID.ELAN0634..
 2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55  _CID.PNP0C50.._U
 2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11  ID..K._DSM..<.h.
 2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D  ..https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+subscriptions

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

[Kernel-packages] [Bug 1865110] Re: disco/linux: 5.0.0-43.47 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Complete
  phase-changed: Monday, 16. March 2020 13:26 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason: {}
  trackers:
bionic/linux-aws-5.0: bug 1865434
bionic/linux-azure: bug 1867856
bionic/linux-bluefield: bug 1863295
bionic/linux-gcp: bug 1865431
bionic/linux-gke-5.0: bug 1865429
bionic/linux-hwe-5.0: bug 1865140
-   bionic/linux-oem-osp1: bug 1867127
+   bionic/linux-oem-osp1: bug 1869295
bionic/linux-oracle-5.0: bug 1865422
  variant: debs

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

Title:
  disco/linux: 5.0.0-43.47 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Disco:
  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 --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Complete
  phase-changed: Monday, 16. March 2020 13:26 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason: {}
  trackers:
bionic/linux-aws-5.0: bug 1865434
bionic/linux-azure: bug 1867856
bionic/linux-bluefield: bug 1863295
bionic/linux-gcp: bug 1865431
bionic/linux-gke-5.0: bug 1865429
bionic/linux-hwe-5.0: bug 1865140
bionic/linux-oem-osp1: bug 1869295
bionic/linux-oracle-5.0: bug 1865422
  variant: debs

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

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

[Françesc]

Hey again mr. knossos456 (knossos456) and Здравко (zdravko-garmev), and
thanks for your helps, but i reboot, yes, and no changes...

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

[Kernel-packages] [Bug 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'

[You-Sheng Yang]

@basmevissen, @ralvarezt could you try
https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1861610 ? If that
works for you, I'll send the merge proposal to Ubuntu kernels.

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

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

Title:
  'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  New
Status in linux source package in Eoan:
  New
Status in linux source package in Focal:
  Confirmed

Bug description:
  The Elan touchpad on my Lenovo Thinkbook isn't being detected, and
  hence isn't working.

  `sudo acpidump | grep -C3 ELAN` gives me the device's ACPI id:

  ```bash
  ghosthawkzero@EchelonV:~$ sudo acpidump | grep -C3 ELAN
 2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46  INT1p. IDAD..SBF
 2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F  SSBFI.[.B.TPD2._
 2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00  ADR..IDAD..HID2.
 2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08  ._HID.ELAN0634..
 2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55  _CID.PNP0C50.._U
 2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11  ID..K._DSM..<.h.
 2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D  ..https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+subscriptions

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

[Kernel-packages] [Bug 1868551] Re: Screen freezes : NULL pointer dereference i915_active_acquire since Linux 5.4

[Guy Baconniere]

** Attachment removed: "WifiSyslog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868551/+attachment/5340470/+files/WifiSyslog.txt

** Attachment removed: "RfKill.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868551/+attachment/5340468/+files/RfKill.txt

** Attachment removed: "AlsaInfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868551/+attachment/5340454/+files/AlsaInfo.txt

** Attachment removed: "CRDA.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868551/+attachment/5340455/+files/CRDA.txt

** Attachment removed: "IwConfig.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868551/+attachment/5340457/+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/1868551

Title:
  Screen freezes : NULL pointer dereference i915_active_acquire since
  Linux 5.4

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  uname -a
  Linux xps 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux

  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  Codename: focal

  [ 2556.956079] BUG: kernel NULL pointer dereference, address: 0040
  [ 2556.956084] #PF: supervisor read access in kernel mode
  [ 2556.956084] #PF: error_code(0x) - not-present page
  [ 2556.956085] PGD 0 P4D 0 
  [ 2556.956088] Oops:  [#1] SMP NOPTI
  [ 2556.956090] CPU: 2 PID: 1685 Comm: xfwm4 Not tainted 5.4.0-14-generic 
#17-Ubuntu
  [ 2556.956092] Hardware name: Dell Inc. XPS 13 7390/0G2D0W, BIOS 1.2.0 
10/03/2019
  [ 2556.956161] RIP: 0010:i915_active_acquire+0xe/0x80 [i915]
  [ 2556.956163] Code: 00 48 c7 c6 11 4d 6b c0 e8 af a1 d6 c7 5d c3 66 66 2e 0f 
1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 <8b> 47 38 
48 89 fb 85 c0 74 17 8d 50 01 f0 0f b1 53 38 75 f2 45 31
  [ 2556.956164] RSP: 0018:ac17c13279c8 EFLAGS: 00010286
  [ 2556.956165] RAX:  RBX: 983831d3e480 RCX: 

  [ 2556.956166] RDX: 983783475200 RSI: 983831d3e480 RDI: 
0008
  [ 2556.956167] RBP: ac17c13279e0 R08:  R09: 
98382d6b6520
  [ 2556.956168] R10: 6cc0 R11: 983838b4db00 R12: 
983783475200
  [ 2556.956169] R13: 0008 R14: 983783475200 R15: 
98382d6b6400
  [ 2556.956170] FS:  7f9031c28f00() GS:98383e50() 
knlGS:
  [ 2556.956171] CS:  0010 DS:  ES:  CR0: 80050033
  [ 2556.956172] CR2: 0040 CR3: 00046eac6001 CR4: 
003606e0
  [ 2556.956173] Call Trace:
  [ 2556.956199]  i915_active_ref+0x24/0x200 [i915]
  [ 2556.956223]  i915_vma_move_to_active+0x74/0xf0 [i915]
  [ 2556.956245]  eb_submit+0xff/0x440 [i915]
  [ 2556.956267]  i915_gem_do_execbuffer+0x88e/0xc20 [i915]
  [ 2556.956271]  ? sock_def_readable+0x40/0x70
  [ 2556.956274]  ? __kmalloc_node+0x205/0x320
  [ 2556.956294]  i915_gem_execbuffer2_ioctl+0x2c3/0x3d0 [i915]
  [ 2556.956314]  ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915]
  [ 2556.956330]  drm_ioctl_kernel+0xae/0xf0 [drm]
  [ 2556.956338]  drm_ioctl+0x234/0x3d0 [drm]
  [ 2556.956358]  ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915]
  [ 2556.956361]  ? vfs_writev+0xc3/0xf0
  [ 2556.956363]  do_vfs_ioctl+0x407/0x670
  [ 2556.956365]  ? fput+0x13/0x15
  [ 2556.956367]  ? __sys_recvmsg+0x88/0xa0
  [ 2556.956369]  ksys_ioctl+0x67/0x90
  [ 2556.956371]  __x64_sys_ioctl+0x1a/0x20
  [ 2556.956373]  do_syscall_64+0x57/0x190
  [ 2556.956376]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [ 2556.956377] RIP: 0033:0x7f9032b3f68b
  [ 2556.956379] Code: 0f 1e fa 48 8b 05 05 28 0d 00 64 c7 00 26 00 00 00 48 c7 
c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d d5 27 0d 00 f7 d8 64 89 01 48
  [ 2556.956380] RSP: 002b:7ffee39a0078 EFLAGS: 0246 ORIG_RAX: 
0010
  [ 2556.956381] RAX: ffda RBX: 55a8abeb6e48 RCX: 
7f9032b3f68b
  [ 2556.956382] RDX: 7ffee39a0090 RSI: 40406469 RDI: 
000d
  [ 2556.956382] RBP: 7ffee39a0120 R08: 0001 R09: 

  [ 2556.956383] R10: 7ffee39a0140 R11: 0246 R12: 
7f9022a4f460
  [ 2556.956384] R13:  R14: 7ffee39a0090 R15: 
000d
  [ 2556.956385] Modules linked in: ccm rfcomm xt_CHECKSUM xt_MASQUERADE 
xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat 
typec_displayport iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 nf_tables cmac nfnetlink algif_hash ip6table_filter ip6_tables 
iptable_filter algif_skcipher af_alg bpfilter bridge stp llc snd_sof_pci 
snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda 

[Kernel-packages] [Bug 1868551] Re: Screen freezes : NULL pointer dereference i915_active_acquire since Linux 5.4

[Kai-Heng Feng]

Is there an upstream commit?

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

Title:
  Screen freezes : NULL pointer dereference i915_active_acquire since
  Linux 5.4

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  uname -a
  Linux xps 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux

  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  Codename: focal

  [ 2556.956079] BUG: kernel NULL pointer dereference, address: 0040
  [ 2556.956084] #PF: supervisor read access in kernel mode
  [ 2556.956084] #PF: error_code(0x) - not-present page
  [ 2556.956085] PGD 0 P4D 0 
  [ 2556.956088] Oops:  [#1] SMP NOPTI
  [ 2556.956090] CPU: 2 PID: 1685 Comm: xfwm4 Not tainted 5.4.0-14-generic 
#17-Ubuntu
  [ 2556.956092] Hardware name: Dell Inc. XPS 13 7390/0G2D0W, BIOS 1.2.0 
10/03/2019
  [ 2556.956161] RIP: 0010:i915_active_acquire+0xe/0x80 [i915]
  [ 2556.956163] Code: 00 48 c7 c6 11 4d 6b c0 e8 af a1 d6 c7 5d c3 66 66 2e 0f 
1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 <8b> 47 38 
48 89 fb 85 c0 74 17 8d 50 01 f0 0f b1 53 38 75 f2 45 31
  [ 2556.956164] RSP: 0018:ac17c13279c8 EFLAGS: 00010286
  [ 2556.956165] RAX:  RBX: 983831d3e480 RCX: 

  [ 2556.956166] RDX: 983783475200 RSI: 983831d3e480 RDI: 
0008
  [ 2556.956167] RBP: ac17c13279e0 R08:  R09: 
98382d6b6520
  [ 2556.956168] R10: 6cc0 R11: 983838b4db00 R12: 
983783475200
  [ 2556.956169] R13: 0008 R14: 983783475200 R15: 
98382d6b6400
  [ 2556.956170] FS:  7f9031c28f00() GS:98383e50() 
knlGS:
  [ 2556.956171] CS:  0010 DS:  ES:  CR0: 80050033
  [ 2556.956172] CR2: 0040 CR3: 00046eac6001 CR4: 
003606e0
  [ 2556.956173] Call Trace:
  [ 2556.956199]  i915_active_ref+0x24/0x200 [i915]
  [ 2556.956223]  i915_vma_move_to_active+0x74/0xf0 [i915]
  [ 2556.956245]  eb_submit+0xff/0x440 [i915]
  [ 2556.956267]  i915_gem_do_execbuffer+0x88e/0xc20 [i915]
  [ 2556.956271]  ? sock_def_readable+0x40/0x70
  [ 2556.956274]  ? __kmalloc_node+0x205/0x320
  [ 2556.956294]  i915_gem_execbuffer2_ioctl+0x2c3/0x3d0 [i915]
  [ 2556.956314]  ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915]
  [ 2556.956330]  drm_ioctl_kernel+0xae/0xf0 [drm]
  [ 2556.956338]  drm_ioctl+0x234/0x3d0 [drm]
  [ 2556.956358]  ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915]
  [ 2556.956361]  ? vfs_writev+0xc3/0xf0
  [ 2556.956363]  do_vfs_ioctl+0x407/0x670
  [ 2556.956365]  ? fput+0x13/0x15
  [ 2556.956367]  ? __sys_recvmsg+0x88/0xa0
  [ 2556.956369]  ksys_ioctl+0x67/0x90
  [ 2556.956371]  __x64_sys_ioctl+0x1a/0x20
  [ 2556.956373]  do_syscall_64+0x57/0x190
  [ 2556.956376]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [ 2556.956377] RIP: 0033:0x7f9032b3f68b
  [ 2556.956379] Code: 0f 1e fa 48 8b 05 05 28 0d 00 64 c7 00 26 00 00 00 48 c7 
c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d d5 27 0d 00 f7 d8 64 89 01 48
  [ 2556.956380] RSP: 002b:7ffee39a0078 EFLAGS: 0246 ORIG_RAX: 
0010
  [ 2556.956381] RAX: ffda RBX: 55a8abeb6e48 RCX: 
7f9032b3f68b
  [ 2556.956382] RDX: 7ffee39a0090 RSI: 40406469 RDI: 
000d
  [ 2556.956382] RBP: 7ffee39a0120 R08: 0001 R09: 

  [ 2556.956383] R10: 7ffee39a0140 R11: 0246 R12: 
7f9022a4f460
  [ 2556.956384] R13:  R14: 7ffee39a0090 R15: 
000d
  [ 2556.956385] Modules linked in: ccm rfcomm xt_CHECKSUM xt_MASQUERADE 
xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat 
typec_displayport iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 nf_tables cmac nfnetlink algif_hash ip6table_filter ip6_tables 
iptable_filter algif_skcipher af_alg bpfilter bridge stp llc snd_sof_pci 
snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt 
snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi snd_hda_codec_hdmi snd_soc_core 
snd_compress ac97_bus snd_pcm_dmaengine bnep snd_hda_codec_realtek 
snd_hda_codec_generic snd_hda_intel snd_intel_nhlt snd_hda_codec snd_hda_core 
snd_hwdep snd_pcm nls_iso8859_1 mei_hdcp intel_rapl_msr snd_seq_midi 
snd_seq_midi_event dell_laptop ledtrig_audio snd_rawmidi x86_pkg_temp_thermal 
intel_powerclamp coretemp joydev kvm_intel kvm cdc_ether intel_cstate 
intel_rapl_perf snd_seq usbnet serio_raw iwlmvm r8152
  [ 2556.956409]  wmi_bmof mii mac80211 dell_wmi dell_smbios dcdbas 
snd_seq_device uvcvideo intel_wmi_thunderbolt 

[Kernel-packages] [Bug 1868494] Re: The system hangs after a while of usage

[Kai-Heng Feng]

MCE is from CPU, so it's possible that memtest can pass.

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6-rc7/

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

Title:
  The system hangs after a while of usage

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since it is a hard hang, I suspect wireguard. I use wireguard as the
  vpn solution to connect to the office at work.

  ProblemType: KernelCrash
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-18-generic 5.4.0-18.22
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1316 F pulseaudio
lawrence   2050 F pulseaudio
   /dev/snd/controlC0:  gdm1316 F pulseaudio
lawrence   2050 F pulseaudio
  Date: Sun Mar 22 13:20:14 2020
  InstallationDate: Installed on 2020-02-06 (45 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Gigabyte Technology Co., Ltd. X299 AORUS Ultra Gaming
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=f3a48b61-47e3-43d3-9d03-b5ad88bf966d ro quiet splash 
crashkernel=512M-:192M vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-18-generic N/A
   linux-backports-modules-5.4.0-18-generic  N/A
   linux-firmware1.187
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  StagingDrivers: exfat
  UpgradeStatus: Upgraded to focal on 2020-03-22 (0 days ago)
  dmi.bios.date: 09/14/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: Default string
  dmi.board.name: X299 AORUS Ultra Gaming-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd09/14/2017:svnGigabyteTechnologyCo.,Ltd.:pnX299AORUSUltraGaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX299AORUSUltraGaming-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X299 AORUS Ultra Gaming
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

Re: [Kernel-packages] [Bug 1854480] Re: zfs_arc_max not working anymore in zfs 0.8.1

[BertN45]

OK, close the bug-report.

On Thu, 2020-03-26 at 22:47 +, Colin Ian King wrote:
> I'll close this bug report if that's OK.
>

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

Title:
  zfs_arc_max not working anymore in zfs 0.8.1

Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  In the past I could limit the size of L1ARC by specifying "options zfs
  zfs_arc_max=3221225472" in /etc/modprobe.d/zfs.conf. I tried even to
  fill /sys/module/zfs/parameters/zfs_arc_max directly, but none of
  those methods limits the size of L1ARC. It worked nicely in zfs 0.7.x.

  Nowadays I use a nvme drive with 3400 MB/s read throughput and I see
  not much difference between e.g booting the system from nvme and
  rebooting the system from L1ARC. Having a 96-99% hit rate for the
  L1ARC, I like to free up some memory, thus avoiding some delay of
  freeing memory from L1ARC while loading a VM.

  -
  UPDATE:

  The system only limits the L1ARC, if we directly after the login write
  the zfs_arc_max value to the file
  /sys/module/zfs/parameters/zfs_arc_max.

  

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: zfsutils-linux 0.8.1-1ubuntu14.1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 29 06:19:15 2019
  InstallationDate: Installed on 2019-11-25 (3 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission 
denied: '/etc/sudoers.d/zfs']

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

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

[Kernel-packages] [Bug 1868551] Re: Screen freezes : NULL pointer dereference i915_active_acquire since Linux 5.4

[Guy Baconniere]

I managed to build, install and boot the Linux Kernel 5.4 patched with
the above patch.

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

Title:
  Screen freezes : NULL pointer dereference i915_active_acquire since
  Linux 5.4

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  uname -a
  Linux xps 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux

  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  Codename: focal

  [ 2556.956079] BUG: kernel NULL pointer dereference, address: 0040
  [ 2556.956084] #PF: supervisor read access in kernel mode
  [ 2556.956084] #PF: error_code(0x) - not-present page
  [ 2556.956085] PGD 0 P4D 0 
  [ 2556.956088] Oops:  [#1] SMP NOPTI
  [ 2556.956090] CPU: 2 PID: 1685 Comm: xfwm4 Not tainted 5.4.0-14-generic 
#17-Ubuntu
  [ 2556.956092] Hardware name: Dell Inc. XPS 13 7390/0G2D0W, BIOS 1.2.0 
10/03/2019
  [ 2556.956161] RIP: 0010:i915_active_acquire+0xe/0x80 [i915]
  [ 2556.956163] Code: 00 48 c7 c6 11 4d 6b c0 e8 af a1 d6 c7 5d c3 66 66 2e 0f 
1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 <8b> 47 38 
48 89 fb 85 c0 74 17 8d 50 01 f0 0f b1 53 38 75 f2 45 31
  [ 2556.956164] RSP: 0018:ac17c13279c8 EFLAGS: 00010286
  [ 2556.956165] RAX:  RBX: 983831d3e480 RCX: 

  [ 2556.956166] RDX: 983783475200 RSI: 983831d3e480 RDI: 
0008
  [ 2556.956167] RBP: ac17c13279e0 R08:  R09: 
98382d6b6520
  [ 2556.956168] R10: 6cc0 R11: 983838b4db00 R12: 
983783475200
  [ 2556.956169] R13: 0008 R14: 983783475200 R15: 
98382d6b6400
  [ 2556.956170] FS:  7f9031c28f00() GS:98383e50() 
knlGS:
  [ 2556.956171] CS:  0010 DS:  ES:  CR0: 80050033
  [ 2556.956172] CR2: 0040 CR3: 00046eac6001 CR4: 
003606e0
  [ 2556.956173] Call Trace:
  [ 2556.956199]  i915_active_ref+0x24/0x200 [i915]
  [ 2556.956223]  i915_vma_move_to_active+0x74/0xf0 [i915]
  [ 2556.956245]  eb_submit+0xff/0x440 [i915]
  [ 2556.956267]  i915_gem_do_execbuffer+0x88e/0xc20 [i915]
  [ 2556.956271]  ? sock_def_readable+0x40/0x70
  [ 2556.956274]  ? __kmalloc_node+0x205/0x320
  [ 2556.956294]  i915_gem_execbuffer2_ioctl+0x2c3/0x3d0 [i915]
  [ 2556.956314]  ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915]
  [ 2556.956330]  drm_ioctl_kernel+0xae/0xf0 [drm]
  [ 2556.956338]  drm_ioctl+0x234/0x3d0 [drm]
  [ 2556.956358]  ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915]
  [ 2556.956361]  ? vfs_writev+0xc3/0xf0
  [ 2556.956363]  do_vfs_ioctl+0x407/0x670
  [ 2556.956365]  ? fput+0x13/0x15
  [ 2556.956367]  ? __sys_recvmsg+0x88/0xa0
  [ 2556.956369]  ksys_ioctl+0x67/0x90
  [ 2556.956371]  __x64_sys_ioctl+0x1a/0x20
  [ 2556.956373]  do_syscall_64+0x57/0x190
  [ 2556.956376]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [ 2556.956377] RIP: 0033:0x7f9032b3f68b
  [ 2556.956379] Code: 0f 1e fa 48 8b 05 05 28 0d 00 64 c7 00 26 00 00 00 48 c7 
c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d d5 27 0d 00 f7 d8 64 89 01 48
  [ 2556.956380] RSP: 002b:7ffee39a0078 EFLAGS: 0246 ORIG_RAX: 
0010
  [ 2556.956381] RAX: ffda RBX: 55a8abeb6e48 RCX: 
7f9032b3f68b
  [ 2556.956382] RDX: 7ffee39a0090 RSI: 40406469 RDI: 
000d
  [ 2556.956382] RBP: 7ffee39a0120 R08: 0001 R09: 

  [ 2556.956383] R10: 7ffee39a0140 R11: 0246 R12: 
7f9022a4f460
  [ 2556.956384] R13:  R14: 7ffee39a0090 R15: 
000d
  [ 2556.956385] Modules linked in: ccm rfcomm xt_CHECKSUM xt_MASQUERADE 
xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat 
typec_displayport iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 nf_tables cmac nfnetlink algif_hash ip6table_filter ip6_tables 
iptable_filter algif_skcipher af_alg bpfilter bridge stp llc snd_sof_pci 
snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt 
snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi snd_hda_codec_hdmi snd_soc_core 
snd_compress ac97_bus snd_pcm_dmaengine bnep snd_hda_codec_realtek 
snd_hda_codec_generic snd_hda_intel snd_intel_nhlt snd_hda_codec snd_hda_core 
snd_hwdep snd_pcm nls_iso8859_1 mei_hdcp intel_rapl_msr snd_seq_midi 
snd_seq_midi_event dell_laptop ledtrig_audio snd_rawmidi x86_pkg_temp_thermal 
intel_powerclamp coretemp joydev kvm_intel kvm cdc_ether intel_cstate 
intel_rapl_perf snd_seq usbnet serio_raw iwlmvm r8152
  [ 2556.956409]  wmi_bmof mii mac80211 dell_wmi dell_smbios 

[Kernel-packages] [Bug 1821269] Re: [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch (4-pole combo jack mic doesn't detect)

[Murilo]

Does it have a workaround for manjaro linux, since I cant install .deb
packages in manjaro?

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

Title:
  [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch (4-pole
  combo jack mic doesn't detect)

Status in linux package in Ubuntu:
  Expired

Bug description:
  I use realtek alc255 analog audio jack. External jack is 4 pole combo(apple 
type. not europe type.).
  When I plug 4 pole mic into jack, It doesn't detect.
  So I can't my voice through external mic.

  My laptop has internal mic. It belongs to Intel sound(HDA Intel PCH. Audio 
device: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Series High Definition Audio Controller (rev 21)).
  Internal mic works well.

  Please check 4pole external mic detection.

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jimnong1441 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jimnong1441 F...m pulseaudio
   /dev/snd/controlC0:  jimnong1441 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 22 11:30:39 2019
  InstallationDate: Installed on 2017-07-27 (603 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: 내장 오디오 - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_Type: No auto-switch between inputs
  Title: [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch
  UpgradeStatus: Upgraded to bionic on 2018-09-23 (179 days ago)
  dmi.bios.date: 09/06/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.24
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Garp_BA
  dmi.board.vendor: Acer
  dmi.board.version: V1.24
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.24:bd09/06/2016:svnAcer:pnAspireES1-131:pvrV1.24:rvnAcer:rnGarp_BA:rvrV1.24:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: BSW
  dmi.product.name: Aspire ES1-131
  dmi.product.version: V1.24
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1868210] Re: [SRU] Load ucm on Lenovo notebooks based on bios version

[Hui Wang]

This is the debdiff for bionic (18.04), please help put it into the
queue.

thx.

** Patch added: "alsa-lib_1.1.3-5ubuntu0.5.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1868210/+attachment/5341982/+files/alsa-lib_1.1.3-5ubuntu0.5.debdiff

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

Title:
  [SRU] Load ucm on Lenovo notebooks based on bios version

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Invalid
Status in alsa-lib source package in Bionic:
  Confirmed
Status in alsa-lib source package in Eoan:
  Confirmed
Status in alsa-lib source package in Focal:
  Invalid

Bug description:
  This SRU is not backported from upstream of alsa-lib and this SRU is
  not going to be submitted to upstream. That is because the latest
  alsa-lib already supports ucm2, and with ucm2 all machines could share
  one ucm, so latest alsa-lib does not have this problem. This problem
  is only specific to the alsa-lib in Bionic and Eoan.

  [Impact]
  On some Lenovo notebooks, UCM files are not loaded and mic can't be used.

  [Fix]
  UCM was loaded based on cardlongname, but that can't cover all configs of the 
same model. Lenovo suggested to load  ucm by the first 3 letters of 
/sys/devices/virtual/dmi/id/bios_version, so that all configs could use just 
one ucm.

  [Test Case]
  After applying this patch, install the testing alsa-lib on Lenovo X1C7 and 
Dell vostro 5390, which are all machines with the DMIC connected to PCH. After 
system bootup, check the /usr/share/alsa/ucm/ for the presence of 
LENOVO-BIOSID-xxx directories.

  Lenovo X1C7 should load the N2H/*.conf and verify the audio
  functionalities. The Dell machine should still load the ucm by
  cardname, and it should work as good as before.

  [Regression Potential]
  low, just add some new UCMs and let Lenovo machine find the UCM by 
bios_version if it fails by cardlongname. I've already tested the change on 
Lenovo and Dell machines.

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

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

[Kernel-packages] [Bug 1868210] Re: [SRU] Load ucm on Lenovo notebooks based on bios version

[Hui Wang]

This is the debdiff for eoan (19.10), please help put it into the queue.

thx.


** Patch added: "alsa-lib_1.1.9-0ubuntu1.3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1868210/+attachment/5341981/+files/alsa-lib_1.1.9-0ubuntu1.3.debdiff

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

Title:
  [SRU] Load ucm on Lenovo notebooks based on bios version

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Invalid
Status in alsa-lib source package in Bionic:
  Confirmed
Status in alsa-lib source package in Eoan:
  Confirmed
Status in alsa-lib source package in Focal:
  Invalid

Bug description:
  This SRU is not backported from upstream of alsa-lib and this SRU is
  not going to be submitted to upstream. That is because the latest
  alsa-lib already supports ucm2, and with ucm2 all machines could share
  one ucm, so latest alsa-lib does not have this problem. This problem
  is only specific to the alsa-lib in Bionic and Eoan.

  [Impact]
  On some Lenovo notebooks, UCM files are not loaded and mic can't be used.

  [Fix]
  UCM was loaded based on cardlongname, but that can't cover all configs of the 
same model. Lenovo suggested to load  ucm by the first 3 letters of 
/sys/devices/virtual/dmi/id/bios_version, so that all configs could use just 
one ucm.

  [Test Case]
  After applying this patch, install the testing alsa-lib on Lenovo X1C7 and 
Dell vostro 5390, which are all machines with the DMIC connected to PCH. After 
system bootup, check the /usr/share/alsa/ucm/ for the presence of 
LENOVO-BIOSID-xxx directories.

  Lenovo X1C7 should load the N2H/*.conf and verify the audio
  functionalities. The Dell machine should still load the ucm by
  cardname, and it should work as good as before.

  [Regression Potential]
  low, just add some new UCMs and let Lenovo machine find the UCM by 
bios_version if it fails by cardlongname. I've already tested the change on 
Lenovo and Dell machines.

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

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

[Kernel-packages] [Bug 1865170] Re: lid close simply turns off laptop screen

[Alex Hung]

Thanks for opening a bug and testing. Let's mark it fix released. Please
re-open if you have found it fails again.

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

** Changed in: gnome-session (Ubuntu)
   Status: New => Fix Released

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

Title:
  lid close simply turns off laptop screen

Status in gnome-session package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  OS: Ubuntu 18.04 LTS (beaver-three-eyed-raven X92.1)
  ubuntu-session version: 3.28.1-0ubuntu3
  Expected behavior: On laptop screen close, system should suspend
  Actual behavior: On laptop screen close, laptop screen disabled

  Previously, I triggered 'suspend when laptop lid is closed' in gnome-
  tweaks. This worked fine until about 2-3 days ago, when I came back to
  work with a dead laptop (I don't charge overnight, usually, but I do
  use a dock at work). Now, whenever I close my laptop screen, it
  doesn't trigger sleep - instead, it simply disables the laptop screen,
  resulting in my external monitor being used as the only output screen.
  Once I re-open my laptop, the laptop screen is re-enabled as the
  primary monitor.

  This happens regardless of connection to my dock. I tested this by
  unplugging my laptop, closing it, letting it sit for 3 minutes, then
  re-opening it. While the laptop was closed, fans still ran. When I re-
  opened my laptop, the lock screen didn't appear.

  Links to attempted fixes that didn't work:

  - 
https://askubuntu.com/questions/1115572/ubuntu-18-04-dell-xps15-9570-impossible-to-reliably-suspend-hibernate
  - 
https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close
  - 
https://www.dell.com/community/Laptops-General-Read-Only/Sleep-Issues-and-Wake-Up-Issues-xps-13/td-p/5018369
  - 
https://askubuntu.com/questions/15520/how-can-i-tell-ubuntu-to-do-nothing-when-i-close-my-laptop-lid

  Results of attempted fixes:
  - mem_sleep: no behavior change (files correctly modified)
  - pm-hibernate: first run, hangs until I kill the process. future runs result 
in exit code 1.
  - update bios: already on latest bios
  - logind.conf: no behavior change
  - gnome tweaks: no behavior change

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-session 3.28.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18
  Uname: Linux 4.15.0-1073-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 28 10:23:52 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1
  InstallationDate: Installed on 2020-01-08 (51 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  colton 4205 F pulseaudio
   /dev/snd/controlC0:  colton 4205 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-08 (53 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. XPS 13 7390
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1073-oem 
root=UUID=ef2a7f80-1cfd-48d6-a2be-0875e4832f2f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1073-oem N/A
   linux-backports-modules-4.15.0-1073-oem  N/A
   linux-firmware   1.173.15
  Tags:  bionic
  Uname: Linux 4.15.0-1073-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0377MH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  

[Kernel-packages] [Bug 1869252] Re: Disco update: upstream stable patchset 2020-03-26

[Kamal Mostafa]

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

** Tags removed: kernel-stable-tracking-bug

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

Title:
  Disco update: upstream stable patchset 2020-03-26

Status in linux package in Ubuntu:
  Invalid

Bug description:
  
  SRU Justification

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

 upstream stable patchset 2020-03-26
 from git://git.kernel.org/

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

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

[Kernel-packages] [Bug 1869253] Re: Disco update: upstream stable patchset 2020-03-26

[Kamal Mostafa]

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

** Tags removed: kernel-stable-tracking-bug

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

Title:
  Disco update: upstream stable patchset 2020-03-26

Status in linux package in Ubuntu:
  Invalid

Bug description:
  
  SRU Justification

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

 upstream stable patchset 2020-03-26
 from git://git.kernel.org/

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

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

[Kernel-packages] [Bug 1869254] Re: Disco update: upstream stable patchset 2020-03-26

[Kamal Mostafa]

** Also affects: linux (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/1869254

Title:
  Disco update: upstream stable patchset 2020-03-26

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

Bug description:
  SRU Justification

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

     upstream stable patchset 2020-03-26

  Ported from the following upstream stable releases:
  v4.19.108, v5.4.24

     from git://git.kernel.org/

  irqchip/gic-v3-its: Fix misuse of GENMASK macro
  iwlwifi: pcie: fix rb_allocator workqueue allocation
  ipmi:ssif: Handle a possible NULL pointer reference
  drm/msm: Set dma maximum segment size for mdss
  dax: pass NOWAIT flag to iomap_apply
  mac80211: consider more elements in parsing CRC
  cfg80211: check wiphy driver existence for drvinfo report
  s390/zcrypt: fix card and queue total counter wrap
  qmi_wwan: re-add DW5821e pre-production variant
  qmi_wwan: unconditionally reject 2 ep interfaces
  ARM: dts: sti: fixup sound frame-inversion for stihxxx-b2120.dtsi
  soc/tegra: fuse: Fix build with Tegra194 configuration
  net: ena: fix potential crash when rxfh key is NULL
  net: ena: fix uses of round_jiffies()
  net: ena: add missing ethtool TX timestamping indication
  net: ena: fix incorrect default RSS key
  net: ena: rss: fix failure to get indirection table
  net: ena: rss: store hash function as values and not bits
  net: ena: fix incorrectly saving queue numbers when setting RSS indirection 
table
  net: ena: ethtool: use correct value for crc32 hash
  net: ena: ena-com.c: prevent NULL pointer dereference
  cifs: Fix mode output in debugging statements
  cfg80211: add missing policy for NL80211_ATTR_STATUS_CODE
  sysrq: Restore original console_loglevel when sysrq disabled
  sysrq: Remove duplicated sysrq message
  net: fib_rules: Correctly set table field when table number exceeds 8 bits
  net: mscc: fix in frame extraction
  net: phy: restore mdio regs in the iproc mdio driver
  net: sched: correct flower port blocking
  nfc: pn544: Fix occasional HW initialization failure
  sctp: move the format error check out of __sctp_sf_do_9_1_abort
  ipv6: Fix route replacement with dev-only route
  ipv6: Fix nlmsg_flags when splitting a multipath route
  qede: Fix race between rdma destroy workqueue and link change event
  net/tls: Fix to avoid gettig invalid tls record
  ext4: potential crash on allocation error in ext4_alloc_flex_bg_array()
  audit: fix error handling in audit_data_to_entry()
  ACPICA: Introduce ACPI_ACCESS_BYTE_WIDTH() macro
  ACPI: watchdog: Fix gas->access_width usage
  KVM: VMX: check descriptor table exits on instruction emulation
  HID: ite: Only bind to keyboard USB interface on Acer SW5-012 keyboard dock
  HID: core: fix off-by-one memset in hid_report_raw_event()
  HID: core: increase HID report buffer size to 8KiB
  macintosh: therm_windtunnel: fix regression when instantiating devices
  tracing: Disable trace_printk() on post poned tests
  Revert "PM / devfreq: Modify the device name as devfreq(X) for sysfs"
  amdgpu/gmc_v9: save/restore sdpif regs during S3
  vhost: Check docket sk_family instead of call getname
  HID: alps: Fix an error handling path in 'alps_input_configured()'
  HID: hiddev: Fix race in in hiddev_disconnect()
  MIPS: VPE: Fix a double free and a memory leak in 'release_vpe()'
  i2c: altera: Fix potential integer overflow
  i2c: jz4780: silence log flood on txabrt
  drm/i915/gvt: Fix orphan vgpu dmabuf_objs' lifetime
  drm/i915/gvt: Separate display reset from ALL_ENGINES reset
  hv_netvsc: Fix unwanted wakeup in netvsc_attach()
  usb: charger: assign specific number for enum value
  s390/qeth: vnicc Fix EOPNOTSUPP precedence
  net: netlink: cap max groups which will be considered in netlink_bind()
  net: atlantic: fix use after free kasan warn
  net: atlantic: fix potential error handling
  net/smc: no peer ID in CLC decline for SMCD
  net: ena: make ena rxfh support ETH_RSS_HASH_NO_CHANGE
  namei: only return -ECHILD from follow_dotdot_rcu()
  mwifiex: drop most magic numbers from mwifiex_process_tdls_action_frame()
  mwifiex: delete unused mwifiex_get_intf_num()
  KVM: SVM: Override default MMIO mask if memory encryption is enabled
  KVM: Check for a bad hva before dropping into the ghc slow path
  sched/fair: Optimize update_blocked_averages()
  sched/fair: Fix 

[Kernel-packages] [Bug 1869268] [NEW] Eoan update: upstream stable patchset 2020-03-26

[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-26

Ported from the following upstream stable releases:
v4.19.108, v5.4.24

   from git://git.kernel.org/

iwlwifi: pcie: fix rb_allocator workqueue allocation
ipmi:ssif: Handle a possible NULL pointer reference
drm/msm: Set dma maximum segment size for mdss
dax: pass NOWAIT flag to iomap_apply
mac80211: consider more elements in parsing CRC
cfg80211: check wiphy driver existence for drvinfo report
s390/zcrypt: fix card and queue total counter wrap
qmi_wwan: re-add DW5821e pre-production variant
qmi_wwan: unconditionally reject 2 ep interfaces
ARM: dts: sti: fixup sound frame-inversion for stihxxx-b2120.dtsi
soc/tegra: fuse: Fix build with Tegra194 configuration
net: ena: fix potential crash when rxfh key is NULL
net: ena: fix uses of round_jiffies()
net: ena: add missing ethtool TX timestamping indication
net: ena: fix incorrect default RSS key
net: ena: rss: fix failure to get indirection table
net: ena: rss: store hash function as values and not bits
net: ena: fix incorrectly saving queue numbers when setting RSS indirection 
table
net: ena: ethtool: use correct value for crc32 hash
net: ena: ena-com.c: prevent NULL pointer dereference
cifs: Fix mode output in debugging statements
cfg80211: add missing policy for NL80211_ATTR_STATUS_CODE
net: fib_rules: Correctly set table field when table number exceeds 8 bits
net: mscc: fix in frame extraction
net: phy: restore mdio regs in the iproc mdio driver
net: sched: correct flower port blocking
nfc: pn544: Fix occasional HW initialization failure
sctp: move the format error check out of __sctp_sf_do_9_1_abort
ipv6: Fix route replacement with dev-only route
ipv6: Fix nlmsg_flags when splitting a multipath route
qede: Fix race between rdma destroy workqueue and link change event
net/tls: Fix to avoid gettig invalid tls record
ext4: potential crash on allocation error in ext4_alloc_flex_bg_array()
audit: fix error handling in audit_data_to_entry()
ACPICA: Introduce ACPI_ACCESS_BYTE_WIDTH() macro
ACPI: watchdog: Fix gas->access_width usage
KVM: VMX: check descriptor table exits on instruction emulation
HID: ite: Only bind to keyboard USB interface on Acer SW5-012 keyboard dock
HID: core: fix off-by-one memset in hid_report_raw_event()
HID: core: increase HID report buffer size to 8KiB
macintosh: therm_windtunnel: fix regression when instantiating devices
tracing: Disable trace_printk() on post poned tests
Revert "PM / devfreq: Modify the device name as devfreq(X) for sysfs"
amdgpu/gmc_v9: save/restore sdpif regs during S3
vhost: Check docket sk_family instead of call getname
HID: alps: Fix an error handling path in 'alps_input_configured()'
HID: hiddev: Fix race in in hiddev_disconnect()
MIPS: VPE: Fix a double free and a memory leak in 'release_vpe()'
i2c: altera: Fix potential integer overflow
i2c: jz4780: silence log flood on txabrt
drm/i915/gvt: Fix orphan vgpu dmabuf_objs' lifetime
drm/i915/gvt: Separate display reset from ALL_ENGINES reset
hv_netvsc: Fix unwanted wakeup in netvsc_attach()
usb: charger: assign specific number for enum value
s390/qeth: vnicc Fix EOPNOTSUPP precedence
net: netlink: cap max groups which will be considered in netlink_bind()
net: atlantic: fix use after free kasan warn
net: atlantic: fix potential error handling
net/smc: no peer ID in CLC decline for SMCD
net: ena: make ena rxfh support ETH_RSS_HASH_NO_CHANGE
namei: only return -ECHILD from follow_dotdot_rcu()
mwifiex: drop most magic numbers from mwifiex_process_tdls_action_frame()
mwifiex: delete unused mwifiex_get_intf_num()
KVM: SVM: Override default MMIO mask if memory encryption is enabled
KVM: Check for a bad hva before dropping into the ghc slow path
drivers: net: xgene: Fix the order of the arguments of 'alloc_etherdev_mqs()'
kprobes: Set unoptimized flag after unoptimizing code
pwm: omap-dmtimer: put_device() after of_find_device_by_node()
perf hists browser: Restore ESC as "Zoom out" of DSO/thread/etc
KVM: x86: Remove spurious kvm_mmu_unload() from vcpu destruction path
KVM: x86: Remove spurious clearing of async #PF MSR
thermal: brcmstb_thermal: Do not use DT coefficients
netfilter: nft_tunnel: no need to call htons() when dumping ports
netfilter: nf_flowtable: fix documentation
mm/huge_memory.c: use head to check huge zero page
mm, thp: fix defrag setting if newline is not used
audit: always check the netlink payload length in audit_receive_msg()
io_uring: grab ->fs as part of async offload
EDAC: skx_common: downgrade 

[Kernel-packages] [Bug 1869123] Re: [LTCTest][OPAL][OP930] IMC PMU (null) Register failed

[Frank Heimes]

Since there is the tag "targetmilestone-inin2004" set, I assume this bug
was opened against focal / 20.04.

Doing a look-up of b59bd3527fe3 "powerpc/powernv: Return for invalid IMC
domain" in the focal master tree (that correlates to the kernel that is
currently in focal's release pocket and is with that the current default
kernel) shows that this specific patch/commit is already in:

$ git clone 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal
...
$ git log --oneline --grep "powerpc/powernv: Return for invalid IMC domain"
b59bd3527fe3 powerpc/powernv: Return for invalid IMC domain
$ git tag --contains b59bd3527fe3
Ubuntu-5.4-5.4.0-10.13
Ubuntu-5.4-5.4.0-11.14
Ubuntu-5.4-5.4.0-12.15
Ubuntu-5.4-5.4.0-13.16
Ubuntu-5.4-5.4.0-14.17
Ubuntu-5.4.0-15.18
Ubuntu-5.4.0-16.19
Ubuntu-5.4.0-17.20
Ubuntu-5.4.0-17.21
Ubuntu-5.4.0-18.22
Ubuntu-5.4.0-19.23
Ubuntu-5.4.0-20.24
Ubuntu-5.4.0-8.11
Ubuntu-5.4.0-9.12
v5.4

So I'm wondering which kernel version was used in your case?
Please can you share the output of 'uname -a'?

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

** Changed in: ubuntu-power-systems
   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/1869123

Title:
  [LTCTest][OPAL][OP930] IMC PMU (null) Register failed

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

Bug description:
  == Comment: #0 - PAVAMAN SUBRAMANIYAM  - 2019-04-10 
00:15:32 ==
  Install a P9 Open Power Hardware with the latest OP930 Firmware images 
provided in the following link:
  
http://pfd.austin.ibm.com/releasenotes/openpower9/OP930/OP930_1913A/OP930_1913B_RelNote_Main.html

  root@witherspoon:~# cat /etc/os-release
  ID="openbmc-phosphor"
  NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)"
  VERSION="ibm-v2.3"
  VERSION_ID="ibm-v2.3-476-g2d622cb-r32-0-g9973ab0"
  PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) 
ibm-v2.3"
  BUILD_ID="ibm-v2.3-476-g2d622cb-r32"
  root@witherspoon:~# cat /var/lib/phosphor-software-manager/pnor/ro/VERSION
IBM-witherspoon-OP9-v2.2-9.71
  op-build-v2.2-58-gf60d718
  buildroot-2019.02-3-g28a7eab
  skiboot-v6.3-rc1
  hostboot-30a512e-pf453f1d
  occ-58e422d
  linux-4.19.30-openpower1-pa764076
  petitboot-v1.10.2
  machine-xml-e3e9aef
  hostboot-binaries-hw021419a.930
  capp-ucode-p9-dd2-v4
  sbe-1410677
  hcode-hw032719a.940

  Then seeing the following messages in dmesg of Linux HOST OS and also
  when we reboot the machine in the SOL console.

  [1.731663] nest_phb0_imc performance monitor hardware support registered
  [1.731704] nest_phb1_imc performance monitor hardware support registered
  [1.731746] nest_phb2_imc performance monitor hardware support registered
  [1.731788] nest_phb3_imc performance monitor hardware support registered
  [1.731829] nest_phb4_imc performance monitor hardware support registered
  [1.731870] nest_phb5_imc performance monitor hardware support registered
  [1.731944] nest_powerbus0_imc performance monitor hardware support 
registered
  [1.734458] thread_imc performance monitor hardware support registered
  [1.734460] IMC Unknown Device type
  [1.734462] IMC PMU (null) Register failed
  [1.734558] nest_xlink0_imc performance monitor hardware support registered
  [1.734614] nest_xlink1_imc performance monitor hardware support registered
  [1.734670] nest_xlink2_imc performance monitor hardware support registered
  [1.747043] Initialise system trusted keyrings
  [1.747054] Key type blacklist registered
  [1.747170] workingset: timestamp_bits=38 max_order=23 bucket_order=0

  == Comment: #2 - PAVAMAN SUBRAMANIYAM  - 2019-04-10 
00:30:47 ==
  So should this bug be moved to kernel to get the fixes be made available to 
Ubuntu 18.04 release or should we keep this bug opened for skiboot under OPAL 
itself, since we are already in the upstream level of skiboot installed on the 
system.

  == Comment: #5 - Application Cdeadmin  - 2019-04-11 
15:15:13 ==
   State: Open by: jayeshp on 11 April 2019 15:05:22 

  #=#=# 2019-04-11 15:05:21 (CDT) #=#=#
  New Fix_Potential = [P910.40W]
  #=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#

  == Comment: #7 - Application Cdeadmin  - 2019-04-16 
06:12:44 ==
  cde00 (cdead...@us.ibm.com) added native attachment 
/tmp/AIXOS11139536/0001-Return-for-invalid-domain.patch on 2019-04-16 06:12:39

  == Comment: #8 - Deborah L. McLemore  - 2019-04-20
  09:58:13 ==

  
  == Comment: #9 - Application Cdeadmin  - 2019-04-26 
08:25:05 ==
   State: Open by: csburns on 26 April 2019 08:15:35 

  The patch in comment #7 was included in a test pnor driver -
  op999.1999.20190423t - that was provided to ISST to look at 

[Kernel-packages] [Bug 1867099] Re: please help enable CONFIG_EROFS_FS_ZIP

[You-Sheng Yang]

Verified linux 5.4.0-20-generic from focal-proposed.

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

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

Title:
  please help enable CONFIG_EROFS_FS_ZIP

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Greeting,

  It seems that the Ubuntu configuration for EROFS file system
  disables compression support, which is not the current default
  option..

  Therefore, I'd recommand the following default options,
  please help apply them from linux kernel 5.4+.

  CONFIG_EROFS_FS=m 


  # CONFIG_EROFS_FS_DEBUG is not set
  CONFIG_EROFS_FS_XATTR=y
  CONFIG_EROFS_FS_POSIX_ACL=y
  CONFIG_EROFS_FS_SECURITY=y
  CONFIG_EROFS_FS_ZIP=y
  CONFIG_EROFS_FS_CLUSTER_PAGE_LIMIT=1

  Thanks in advance!

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

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

[Kernel-packages] [Bug 1869123] [NEW] [LTCTest][OPAL][OP930] IMC PMU (null) Register failed

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

== Comment: #0 - PAVAMAN SUBRAMANIYAM  - 2019-04-10 
00:15:32 ==
Install a P9 Open Power Hardware with the latest OP930 Firmware images provided 
in the following link:
http://pfd.austin.ibm.com/releasenotes/openpower9/OP930/OP930_1913A/OP930_1913B_RelNote_Main.html

root@witherspoon:~# cat /etc/os-release
ID="openbmc-phosphor"
NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)"
VERSION="ibm-v2.3"
VERSION_ID="ibm-v2.3-476-g2d622cb-r32-0-g9973ab0"
PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) 
ibm-v2.3"
BUILD_ID="ibm-v2.3-476-g2d622cb-r32"
root@witherspoon:~# cat /var/lib/phosphor-software-manager/pnor/ro/VERSION
IBM-witherspoon-OP9-v2.2-9.71
op-build-v2.2-58-gf60d718
buildroot-2019.02-3-g28a7eab
skiboot-v6.3-rc1
hostboot-30a512e-pf453f1d
occ-58e422d
linux-4.19.30-openpower1-pa764076
petitboot-v1.10.2
machine-xml-e3e9aef
hostboot-binaries-hw021419a.930
capp-ucode-p9-dd2-v4
sbe-1410677
hcode-hw032719a.940

Then seeing the following messages in dmesg of Linux HOST OS and also
when we reboot the machine in the SOL console.

[1.731663] nest_phb0_imc performance monitor hardware support registered
[1.731704] nest_phb1_imc performance monitor hardware support registered
[1.731746] nest_phb2_imc performance monitor hardware support registered
[1.731788] nest_phb3_imc performance monitor hardware support registered
[1.731829] nest_phb4_imc performance monitor hardware support registered
[1.731870] nest_phb5_imc performance monitor hardware support registered
[1.731944] nest_powerbus0_imc performance monitor hardware support 
registered
[1.734458] thread_imc performance monitor hardware support registered
[1.734460] IMC Unknown Device type
[1.734462] IMC PMU (null) Register failed
[1.734558] nest_xlink0_imc performance monitor hardware support registered
[1.734614] nest_xlink1_imc performance monitor hardware support registered
[1.734670] nest_xlink2_imc performance monitor hardware support registered
[1.747043] Initialise system trusted keyrings
[1.747054] Key type blacklist registered
[1.747170] workingset: timestamp_bits=38 max_order=23 bucket_order=0

== Comment: #2 - PAVAMAN SUBRAMANIYAM  - 2019-04-10 
00:30:47 ==
So should this bug be moved to kernel to get the fixes be made available to 
Ubuntu 18.04 release or should we keep this bug opened for skiboot under OPAL 
itself, since we are already in the upstream level of skiboot installed on the 
system.

== Comment: #5 - Application Cdeadmin  - 2019-04-11 
15:15:13 ==
 State: Open by: jayeshp on 11 April 2019 15:05:22 

#=#=# 2019-04-11 15:05:21 (CDT) #=#=#
New Fix_Potential = [P910.40W]
#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#

== Comment: #7 - Application Cdeadmin  - 2019-04-16 
06:12:44 ==
cde00 (cdead...@us.ibm.com) added native attachment 
/tmp/AIXOS11139536/0001-Return-for-invalid-domain.patch on 2019-04-16 06:12:39

== Comment: #8 - Deborah L. McLemore  - 2019-04-20
09:58:13 ==


== Comment: #9 - Application Cdeadmin  - 2019-04-26 
08:25:05 ==
 State: Open by: csburns on 26 April 2019 08:15:35 

The patch in comment #7 was included in a test pnor driver -
op999.1999.20190423t - that was provided to ISST to look at several
skiboot pending changes. This defect was also seen in System Mfg Test -
so this patch should be merged for OP930 GA.

== Comment: #10 - VASANT HEGDE  - 2019-05-14 23:02:35 ==
Anju,

Where are we with this patch? Did you push changes to upstream?

Also is this really a ship issue?

-Vasant

== Comment: #15 - Klaus Heinrich Kiwi  - 2020-03-25 06:27:01 
==
(In reply to comment #13)
> Patch is now upstream.
> https://git.kernel.org/powerpc/c/b59bd3527fe3c1939340df558d7f9d56
> 
> Thanks,
> Anju

== Comment: #16 - Klaus Heinrich Kiwi  - 2020-03-25 06:33:24 
==
(In reply to comment #14)
> (In reply to comment #13)
> > Patch is now upstream.
> > https://git.kernel.org/powerpc/c/b59bd3527fe3c1939340df558d7f9d56
> > 
> > Thanks,
> > Anju
> 
> What next?  will you be sending fix to distros?
> 
> -Vasant

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-ppc64le bugnameltc-176827 severity-critical 
targetmilestone-inin2004
-- 
[LTCTest][OPAL][OP930] IMC PMU (null) Register failed
https://bugs.launchpad.net/bugs/1869123
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 1869123] Re: [LTCTest][OPAL][OP930] IMC PMU (null) Register failed

[Frank Heimes]

** Package changed: kernel-package (Ubuntu) => linux (Ubuntu)

** Also affects: ubuntu-power-systems
   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/1869123

Title:
  [LTCTest][OPAL][OP930] IMC PMU (null) Register failed

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

Bug description:
  == Comment: #0 - PAVAMAN SUBRAMANIYAM  - 2019-04-10 
00:15:32 ==
  Install a P9 Open Power Hardware with the latest OP930 Firmware images 
provided in the following link:
  
http://pfd.austin.ibm.com/releasenotes/openpower9/OP930/OP930_1913A/OP930_1913B_RelNote_Main.html

  root@witherspoon:~# cat /etc/os-release
  ID="openbmc-phosphor"
  NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)"
  VERSION="ibm-v2.3"
  VERSION_ID="ibm-v2.3-476-g2d622cb-r32-0-g9973ab0"
  PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) 
ibm-v2.3"
  BUILD_ID="ibm-v2.3-476-g2d622cb-r32"
  root@witherspoon:~# cat /var/lib/phosphor-software-manager/pnor/ro/VERSION
IBM-witherspoon-OP9-v2.2-9.71
  op-build-v2.2-58-gf60d718
  buildroot-2019.02-3-g28a7eab
  skiboot-v6.3-rc1
  hostboot-30a512e-pf453f1d
  occ-58e422d
  linux-4.19.30-openpower1-pa764076
  petitboot-v1.10.2
  machine-xml-e3e9aef
  hostboot-binaries-hw021419a.930
  capp-ucode-p9-dd2-v4
  sbe-1410677
  hcode-hw032719a.940

  Then seeing the following messages in dmesg of Linux HOST OS and also
  when we reboot the machine in the SOL console.

  [1.731663] nest_phb0_imc performance monitor hardware support registered
  [1.731704] nest_phb1_imc performance monitor hardware support registered
  [1.731746] nest_phb2_imc performance monitor hardware support registered
  [1.731788] nest_phb3_imc performance monitor hardware support registered
  [1.731829] nest_phb4_imc performance monitor hardware support registered
  [1.731870] nest_phb5_imc performance monitor hardware support registered
  [1.731944] nest_powerbus0_imc performance monitor hardware support 
registered
  [1.734458] thread_imc performance monitor hardware support registered
  [1.734460] IMC Unknown Device type
  [1.734462] IMC PMU (null) Register failed
  [1.734558] nest_xlink0_imc performance monitor hardware support registered
  [1.734614] nest_xlink1_imc performance monitor hardware support registered
  [1.734670] nest_xlink2_imc performance monitor hardware support registered
  [1.747043] Initialise system trusted keyrings
  [1.747054] Key type blacklist registered
  [1.747170] workingset: timestamp_bits=38 max_order=23 bucket_order=0

  == Comment: #2 - PAVAMAN SUBRAMANIYAM  - 2019-04-10 
00:30:47 ==
  So should this bug be moved to kernel to get the fixes be made available to 
Ubuntu 18.04 release or should we keep this bug opened for skiboot under OPAL 
itself, since we are already in the upstream level of skiboot installed on the 
system.

  == Comment: #5 - Application Cdeadmin  - 2019-04-11 
15:15:13 ==
   State: Open by: jayeshp on 11 April 2019 15:05:22 

  #=#=# 2019-04-11 15:05:21 (CDT) #=#=#
  New Fix_Potential = [P910.40W]
  #=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#

  == Comment: #7 - Application Cdeadmin  - 2019-04-16 
06:12:44 ==
  cde00 (cdead...@us.ibm.com) added native attachment 
/tmp/AIXOS11139536/0001-Return-for-invalid-domain.patch on 2019-04-16 06:12:39

  == Comment: #8 - Deborah L. McLemore  - 2019-04-20
  09:58:13 ==

  
  == Comment: #9 - Application Cdeadmin  - 2019-04-26 
08:25:05 ==
   State: Open by: csburns on 26 April 2019 08:15:35 

  The patch in comment #7 was included in a test pnor driver -
  op999.1999.20190423t - that was provided to ISST to look at several
  skiboot pending changes. This defect was also seen in System Mfg Test
  - so this patch should be merged for OP930 GA.

  == Comment: #10 - VASANT HEGDE  - 2019-05-14 23:02:35 
==
  Anju,

  Where are we with this patch? Did you push changes to upstream?

  Also is this really a ship issue?

  -Vasant

  == Comment: #15 - Klaus Heinrich Kiwi  - 2020-03-25 
06:27:01 ==
  (In reply to comment #13)
  > Patch is now upstream.
  > https://git.kernel.org/powerpc/c/b59bd3527fe3c1939340df558d7f9d56
  > 
  > Thanks,
  > Anju

  == Comment: #16 - Klaus Heinrich Kiwi  - 2020-03-25 
06:33:24 ==
  (In reply to comment #14)
  > (In reply to comment #13)
  > > Patch is now upstream.
  > > https://git.kernel.org/powerpc/c/b59bd3527fe3c1939340df558d7f9d56
  > > 
  > > Thanks,
  > > Anju
  > 
  > What next?  will you be sending fix to distros?
  > 
  > -Vasant

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post 

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

[knossos456]

If sudo dpkg -i linux-firmware_1.173.17_all.deb has success , yes you can 
delete the file.
And to take effect, you have to reboot the machine as written by zdravko. Only 
after reboot you can test again

-- 
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)
  

[Kernel-packages] [Bug 1868113] Re: [Ubuntu 20.04] Striding RQ as Default for ConnectX-4

[Frank Heimes]

Reverting the patch is not a good idea and would not help in all the
cases mentioned - since it would impact all architectures, not only
s390x, would also impact z13 and zEC12 where this should not be changed
and would move us away from the upstream code base.

Instead please think about introducing a kernel config option that allows to 
toggle Striding RQ.
A kernel config option allows to set different defaults for different 
architectures, hence it could be at least changed for s390x in general.

** Changed in: ubuntu-z-systems
   Importance: Undecided => Medium

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

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

Title:
  [Ubuntu 20.04]  Striding RQ as Default for ConnectX-4

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ello,
  Within our Network Performance runs in the RoCE Express 2(.1) area, we 
noticed a performance regression with streaming workloads which could be 
mitigated by using an ethtool setting.
   
  The Commit which switched the default value from "Striding RQ" to "Legacy RQ" 
for ConnectX-4 devices (RoCE Express 2(.1)) is attached here:
  commit 5ffd81943d7a57423f204cd5844bf430b5634472 (refs/bisect/bad)
  Author: Tariq Toukan 
  Date:   Tue Feb 20 15:17:54 2018 +0200
  net/mlx5e: RX, Always prefer Linear SKB configuration
  Prefer the linear SKB configuration of Legacy RQ over the
  non-linear one of Striding RQ.
  This implies that ConnectX-4 LX now uses legacy RQ by default,
  as it does not support the linear configuration of Striding RQ.
  Signed-off-by: Tariq Toukan 
  Signed-off-by: Saeed Mahameed 
   
  diff --git a/drivers/net/ethernet/mellanox/mlx5/core/en_main.c 
b/drivers/net/ethernet/mellanox/mlx5/core/en_main.c
  index 2c634e50d051..333d4ed52b94 100644
  --- a/drivers/net/ethernet/mellanox/mlx5/core/en_main.c
  +++ b/drivers/net/ethernet/mellanox/mlx5/core/en_main.c
  @@ -4405,9 +4405,16 @@ void mlx5e_build_nic_params(struct mlx5_core_dev *mdev,
  MLX5E_SET_PFLAG(params, MLX5E_PFLAG_RX_CQE_COMPRESS, 
params->rx_cqe_compress_def);
  /* RQ */
  -   if (mlx5e_striding_rq_possible(mdev, params))
  -   MLX5E_SET_PFLAG(params, MLX5E_PFLAG_RX_STRIDING_RQ,
  -   !slow_pci_heuristic(mdev));
  +   /* Prefer Striding RQ, unless any of the following holds:
  +* - Striding RQ configuration is not possible/supported.
  +* - Slow PCI heuristic.
  +* - Legacy RQ would use linear SKB while Striding RQ would use 
non-linear.
  +*/
  +   if (!slow_pci_heuristic(mdev) &&
  +   mlx5e_striding_rq_possible(mdev, params) &&
  +   (mlx5e_rx_mpwqe_is_linear_skb(mdev, params) ||
  +!mlx5e_rx_is_linear_skb(mdev, params)))
  +   MLX5E_SET_PFLAG(params, MLX5E_PFLAG_RX_STRIDING_RQ, true);
  mlx5e_set_rq_type(mdev, params);
  mlx5e_init_rq_type_params(mdev, params);
   
  We have modified the upstream-kernel to allow us running of measurements and 
compare differences between Legacy RQ vs Striding RQ. Here is an example below: 
   
  Kernel used: 5.4.0-rc7
  The measurements run on a dedicated machine (z14) using uperf with streaming 
profiles (MTU size 1500).
   
  Example throughput drop:
  (traffic via a shared card, i.e. client and server using VFs from the same 
ConnectX-4)
  --
  | |Legacy RQ|  Striding RQ   |
  --
  |str-writex30k (1 connection) |24.62Gb/s|   33.47Gb/s|
  --
  Additionaly, two tests with transactional workload using the ethtool proposed 
switch: 
  --
  | |Legacy RQ|  Striding RQ   |
  --
  |  rr1c-200x30k---1   | 4.12Gb/s|5.66Gb/s|
  --
  |  rr1c-200x30k--10   |15.10Gb/s|   20.77Gb/s|
  --

  As concluded in the communication with Mellanox, there is a possibility to 
use a simple ethtool command to switch between the queuing methods, allowing us 
to avoid kernel code changes:
  ethtool --set-priv-flags DEVNAME rx_striding_rq on
  (To list the available settings you may use: ethtool --show-priv-flags 
DEVNAME)

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1780590] Re: Add support for Realtek 8723DE wireless adapter

[AceLan Kao]

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

** Tags removed: verification-done-focal
** Tags added: verification-need-focal

** Tags removed: verification-need-focal
** Tags added: verification-done-focal

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

Title:
  Add support for Realtek 8723DE wireless adapter

Status in OEM Priority Project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Won't Fix
Status in linux-firmware source package in Bionic:
  Fix Released
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Disco:
  Won't Fix
Status in linux-firmware source package in Disco:
  Fix Released
Status in linux-oem-osp1 source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Won't Fix
Status in linux-firmware source package in Eoan:
  Fix Released
Status in linux-oem-osp1 source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Committed
Status in linux-firmware source package in Focal:
  Fix Released
Status in linux-oem-osp1 source package in Focal:
  Won't Fix

Bug description:
  === SRU Justification ===
  [Impact]
  There's no in-kernel support for Realtek 8723DE, so users need to use
  out-of-tree DKMS which is not from Ubuntu archive. This has security
  implication and should be avoided. Also this provides pretty bad user
  experience.

  [Fix]
  Add support to Realtek 8723DE.
  All commits are cherry-picked from Realtek maintained repo:
  https://github.com/rtlwifi-linux/rtw88_8723de

  [Test]
  With the patch series applied, 8723DE can scan and connect to APs
  succesfully. Also did some S3 smoke test, it continues to work.

  [Regression Potential]
  Low. The device in question was never supported, and if there's any
  regression, we can count on Realtek Wireless team, thy are now pretty
  responsive on upstream mailing list.

  === Original Bug Report ===
  recently I just installed ubuntu 18.04 lts in dual bot next to windows 10. 
Everything in the installation was fine until the moment to start session. The 
problem is that the wireless network card does not detect me and when entering 
the configuration I simply get an error message saying that no wireless adapter 
was found. I have already followed all the tutorials I found on the web. and 
update the driver of a github repository, and install how much program they 
told me to install and I still can not connect via wifi.

  I just do not know what to do. I have a laptop hp 14-bs004 came with
  windows 10 installed. The information on the network card is as
  follows:

   Network controller [0280]: Realtek Semiconductor Co., Ltd. Device [10ec: 
d723]
  Subsystem: Hewlett-Packard Company Device [103c: 8319]
  Control: I / O + Mem + BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
  Status: Cap + 66MHz- UDF- FastB2B- ParErr- DEVSEL = fast> TAbort-  SERR- 
  Kernel modules: wl

  already install the most recent kernel, already intale driver driver
  realtek rtl8723be according to the instructions of the git repository.
  and nothing has worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul  7 22:57:40 2018
  InstallationDate: Installed on 2018-07-08 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_MX.UTF-8
   SHELL=/bin/bash
  SourcePackage: bcmwl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1856387] Re: Freezing on boot since kernel 4.15.0-72-generic release

[You-Sheng Yang]

Hi, for those who still suffers from this issue, it was a regression
issue caused by commit f723dd269d07 "x86/timer: Skip PIT initialization
on modern chipsets"), which was backported to 4.15.0-71 in bug 1851216
as a fix for some other platforms. So, please try latest mainline
kernel[1] as possible as there might be yet another fix to this
regression, then we may finally cherry-pick it back to 4.15 and fix
hardware platforms of either group. As far as we know, this issue was
still reproducible on v5.5-rc5, so you may want to try something newer
than that directly.

[1]: https://kernel.ubuntu.com/~kernel-ppa/mainline/

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

Title:
  Freezing on boot since kernel 4.15.0-72-generic release

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After the update to install kernel 4.15.0-72-generic (a bit over a week ago) 
my computer will not boot. On boot, all I see is the purple screen with:
  Loading Linux 4.15.0-72-generic ...
  Loading initial ramdisk ...
  and nothing happens. Just sits there. I've waited about 5-10 minutes on 
occasion but to no avail.
  I've checked a number of logs in /var/log but not found anything.

  If I go into the advanced options and select kernel
  4.15.0-70-generic, the computer boots normally.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-72-generic 4.15.0-72.81
  ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18
  Uname: Linux 4.15.0-70-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tony   1977 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 14 21:53:14 2019
  HibernationDevice: RESUME=UUID=5475ce25-e091-45e2-9811-9b5cddc08dd1
  InstallationDate: Installed on 2018-09-16 (454 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 046d:c063 Logitech, Inc. DELL Laser Mouse
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GIGABYTE Sabre 17WV8
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic 
root=UUID=9455257c-d3b7-4d61-853d-ab0b0ee40013 ro acpi=off
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-70-generic N/A
   linux-backports-modules-4.15.0-70-generic  N/A
   linux-firmware 1.173.13
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/22/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Sabre 17WV8
  dmi.board.vendor: GIGABYTE
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: GIGABYTE
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF05:bd05/22/2018:svnGIGABYTE:pnSabre17WV8:pvrNotApplicable:rvnGIGABYTE:rnSabre17WV8:rvrNotApplicable:cvnGIGABYTE:ct10:cvrN/A:
  dmi.product.family: Sabre
  dmi.product.name: Sabre 17WV8
  dmi.product.version: Not Applicable
  dmi.sys.vendor: GIGABYTE

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

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

[Kernel-packages] [Bug 1867428] Re: /dev/vcsm-cma missing on Ubuntu 18.04.4 aarch64

[Juerg Haefliger]

Can you try a Focal image from 
http://cdimage.ubuntu.com/ubuntu-server/daily-preinstalled/current/
while I'm debugging this on Bionic?

I do see /dev/vcsm-cma on Focal with the 5.4.0-1006.6 kernel.

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

Title:
  /dev/vcsm-cma missing on Ubuntu 18.04.4 aarch64

Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-raspi2 source package in Bionic:
  New

Bug description:
  On fully upgraded Ubuntu 18.04 aarch64 the vc_sm_cma kernel module
  does not expose /dev/vcsm-cma, thus application working with the
  Raspberry Pi Camera, e.g. raspivid, do not work properly.

  $ lsb_release -a
  No LSB modules are available. 

  
  Distributor ID: Ubuntu

  
  Description:Ubuntu 18.04.4 LTS

  
  Release:18.04 

  
  Codename:   bionic

  Test with both linux-image-5.3.0-1017-raspi2 and linux-
  image-5.3.0-1018-raspi2 in combination with with
  https://github.com/raspberrypi/userland at
  6e6a2c859a17a195fbb6a97c9da584dd2b9b0178 compiled using ./buildme
  --aarch64 on Raspberry Pi 4 and 3+.

  Everything works, if I use a recent Raspbian kernel on the Ubuntu image:
  Copy RASPBIAN/boot/kernel8.img to UBUNTU/boot/firmware/vmlinuz, 
RASPBIAN/boot/bcm2711-rpi-4-b.dtb to UBUNTU/boot/firmware/ and 
RASPBIAN/lib/modules/4.19.97-v8+ to UBUNTU/lib/modules.

  I cannot tell whether the problem is specific to the 5.3.0 kernel
  compiled for Ubuntu or a general issue with the 5.3.0 kernel as the
  Raspbian kernel is still based on 4.19.

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

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

[Kernel-packages] [Bug 1842236] Re: [TGL] Trace Hub 2.x Enhancements/NPK

[Rex Tsai]

** Tags added: tigerlake

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

Title:
  [TGL] Trace Hub 2.x Enhancements/NPK

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description
  Enable Trace Hub 2.x Enhancements/NPK
  Should be same solution as ICL except for new PCI IDs

  Target Release: 20.04
  Target Kernel: 5.5

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

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

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

[bugproxy]

--- Comment From danijel.so...@de.ibm.com 2020-03-26 06:29 EDT---
Hi,
our intention was *never* to revert a patch. What we propose is to trigger the 
mentioned ethtool command (ethtool --set-priv-flags DEVNAME rx_striding_rq on) 
as soon as the distro is running on a z14/z15 machine and the ConnectX-4 driver 
is started.
Do you think something like that would be possible?

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

Title:
  [Ubuntu 20.04]  Striding RQ as Default for ConnectX-4

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ello,
  Within our Network Performance runs in the RoCE Express 2(.1) area, we 
noticed a performance regression with streaming workloads which could be 
mitigated by using an ethtool setting.
   
  The Commit which switched the default value from "Striding RQ" to "Legacy RQ" 
for ConnectX-4 devices (RoCE Express 2(.1)) is attached here:
  commit 5ffd81943d7a57423f204cd5844bf430b5634472 (refs/bisect/bad)
  Author: Tariq Toukan 
  Date:   Tue Feb 20 15:17:54 2018 +0200
  net/mlx5e: RX, Always prefer Linear SKB configuration
  Prefer the linear SKB configuration of Legacy RQ over the
  non-linear one of Striding RQ.
  This implies that ConnectX-4 LX now uses legacy RQ by default,
  as it does not support the linear configuration of Striding RQ.
  Signed-off-by: Tariq Toukan 
  Signed-off-by: Saeed Mahameed 
   
  diff --git a/drivers/net/ethernet/mellanox/mlx5/core/en_main.c 
b/drivers/net/ethernet/mellanox/mlx5/core/en_main.c
  index 2c634e50d051..333d4ed52b94 100644
  --- a/drivers/net/ethernet/mellanox/mlx5/core/en_main.c
  +++ b/drivers/net/ethernet/mellanox/mlx5/core/en_main.c
  @@ -4405,9 +4405,16 @@ void mlx5e_build_nic_params(struct mlx5_core_dev *mdev,
  MLX5E_SET_PFLAG(params, MLX5E_PFLAG_RX_CQE_COMPRESS, 
params->rx_cqe_compress_def);
  /* RQ */
  -   if (mlx5e_striding_rq_possible(mdev, params))
  -   MLX5E_SET_PFLAG(params, MLX5E_PFLAG_RX_STRIDING_RQ,
  -   !slow_pci_heuristic(mdev));
  +   /* Prefer Striding RQ, unless any of the following holds:
  +* - Striding RQ configuration is not possible/supported.
  +* - Slow PCI heuristic.
  +* - Legacy RQ would use linear SKB while Striding RQ would use 
non-linear.
  +*/
  +   if (!slow_pci_heuristic(mdev) &&
  +   mlx5e_striding_rq_possible(mdev, params) &&
  +   (mlx5e_rx_mpwqe_is_linear_skb(mdev, params) ||
  +!mlx5e_rx_is_linear_skb(mdev, params)))
  +   MLX5E_SET_PFLAG(params, MLX5E_PFLAG_RX_STRIDING_RQ, true);
  mlx5e_set_rq_type(mdev, params);
  mlx5e_init_rq_type_params(mdev, params);
   
  We have modified the upstream-kernel to allow us running of measurements and 
compare differences between Legacy RQ vs Striding RQ. Here is an example below: 
   
  Kernel used: 5.4.0-rc7
  The measurements run on a dedicated machine (z14) using uperf with streaming 
profiles (MTU size 1500).
   
  Example throughput drop:
  (traffic via a shared card, i.e. client and server using VFs from the same 
ConnectX-4)
  --
  | |Legacy RQ|  Striding RQ   |
  --
  |str-writex30k (1 connection) |24.62Gb/s|   33.47Gb/s|
  --
  Additionaly, two tests with transactional workload using the ethtool proposed 
switch: 
  --
  | |Legacy RQ|  Striding RQ   |
  --
  |  rr1c-200x30k---1   | 4.12Gb/s|5.66Gb/s|
  --
  |  rr1c-200x30k--10   |15.10Gb/s|   20.77Gb/s|
  --

  As concluded in the communication with Mellanox, there is a possibility to 
use a simple ethtool command to switch between the queuing methods, allowing us 
to avoid kernel code changes:
  ethtool --set-priv-flags DEVNAME rx_striding_rq on
  (To list the available settings you may use: ethtool --show-priv-flags 
DEVNAME)

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

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

[Kernel-packages] [Bug 1866581] Re: The voice recording function cannot work while connecting a headset on a Dell machine

[Hui Wang]

** Tags removed: verification-needed-bionic verification-needed-eoan
** Tags added: verification-done-bionic verification-done-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/1866581

Title:
  The voice recording function cannot work while connecting a headset on
  a Dell machine

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux-oem-osp1 source package in Eoan:
  Invalid
Status in linux source package in Focal:
  Incomplete
Status in linux-oem-osp1 source package in Focal:
  Invalid

Bug description:
  [Impact]
  The headset mic can't record any sound on this machine.

  [Fix]
  The headset-mic is set to ctia mode by hardware. we need to apply
  an existing quirk.

  [Test Case]
  boot the system, plug the headset, it could record the sound via
  headset mic.

  
  [Regression Risk]
  Low, this patch is specific to 2 dell machines.

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

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

[Kernel-packages] [Bug 1771254] Re: [TGL] SPI support

[Rex Tsai]

** Tags added: tigerlake

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

Title:
  [TGL] SPI support

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:
  Adding CSE DMA access capability to SPI and UART controller.

  Target Release: 20.04
  Target Kernel: v5.4

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

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

[Kernel-packages] [Bug 1806396] Re: lis3lv02d: unknown sensor type 0x0

[tony cook]

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

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

Title:
  lis3lv02d: unknown sensor type 0x0

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  dmesg:
  [   15.684425] lis3lv02d: unknown sensor type 0x0

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2647 F pulseaudio
   /dev/snd/pcmC0D0p:   caravena   2647 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  3 10:22:33 2018
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.176
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (0 days ago)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1833281] Re: System freeze when memory is put on SWAP in Linux >4.10.x

[Corben]

It seems that zram mitigates the problem for me during a work day. As long as 
the system doesn't have to write swap to the disk, it seems fine. The longer I 
use the system, the sooner it is running out of (z)ram and swapping also to 
disk. As soon as this happens, I get these freezes again. I have the feeling, 
that the amount of swapped out data that is swapped at once is causing this. 
Seems like I/O is blocking to me.
I have the impression with a previous kernel, the blocks have been smaller so 
the system didn't block too long so it didn't really interrupt work.

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

Title:
  System freeze when memory is put on SWAP in Linux >4.10.x

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

Bug description:
  I'm reporting this since it's reproduceable the 70% of the time.
  Summary:

  In different circumstances, when the systems starts to swap out RAM
  memory, even small amounts, the system becomes completely unusuable
  and the screen freezes up, no mouse movement, no TTY access or SSH
  access can be made, only SYSRQ keys seem to do something (only reboot,
  so REISUB worked so far though, OOM is useless since the memory/swap
  is not even full)

  The I/O Disk led is stuck to 100% in ALL the following cases when this
  happens.

  So far:
  - This happens even when only ZRAM is enabled, and no swap partition is used.
  - Happens when ZSWAP is used with a swap partition
  - Happens also when a partition without zram or zswap is used
  - Maybe it's AMD specific? 

  However, I'm not experiencing this on my laptop using the same tests.

  My laptop is an Intel one, while my desktop is an AMD Ryzen platform.

  Here are the specs:
  CPU: AMD Ryzen 5 1600 no OC
  GPU: AMD RX 580 8GB
  SSD: Crucial MX500 500GB
  MOBO: MSI B350M Grenade
  RAM: 8GB HyperX Kingston 2667Mhz

  Ubuntu version: 18.04 LTS, backports repo enabled
  Kernel version: 4.18.0-18, official ubuntu repo
  Bios settings: Default

  Additional info: Maybe I'm not 100% sure, but I noticed when using the
  5.0.0-17 generic kernel, the lockups seem to still happen, but they
  recover eventually. Happened only a few times though...

  But will always be frozen for at least 30 seconds, differently from my
  intel laptop where those do occur.

  The SSD make is the same. I bought two of these, they got also the
  same amount of RAM.

  In my laptop those do not occur at all. Swapping memory even huge
  quantities like 1GB or more, do not produce any issues.

  Tests made:
  For testing this behaviour I tried:

  - Compiling the chromium-browser source code (takes up a lot of system
  RAM)

  - Used the "stress" command, using a specific amount of memory to
  decide how many it will be swapped, and here I noticed that even small
  quantities like a couple of megabytes will cause the system to freeze
  the 70% of the times

  Example: "stress --vm 1 --vm-bytes=7G"

  What should happen:
  I expect system slowdowns when swapping out memory since I do not have enough 
RAM, but unlikely when using Windows or my laptop with the same Linux version, 
not a completely unusuable environment. The swap partition is in both cases on 
an SSD.

  Reproduceability: 70% of the times

  Additional info again:
  I'm not sure this is due to any hardware failure, my SSD health is fine, as 
my CPU and RAM. As I said swapping in Windows works fine...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  haru   2076 F pulseaudio
   /dev/snd/controlC2:  haru   2076 F pulseaudio
   /dev/snd/controlC0:  haru   2076 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IwConfig:
   enp24s0   no wireless extensions.
   
   lono wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7A37
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-17-generic 
root=UUID=75d45574-7169-4653-aea3-9f95087f0806 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-17.18~18.04.1-generic 5.0.8
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-17-generic N/A
   linux-backports-modules-5.0.0-17-generic  N/A
   linux-firmware1.173.6
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 5.0.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo video
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 01/22/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.K0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B350M MORTAR (MS-7A37)
  dmi.board.vendor: 

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

[Juerg Haefliger]

Public bug reported:

Upstream raspberrypi patchset 2020-03-26

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

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

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

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

-- 
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-26

Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-raspi2 source package in Focal:
  New

Bug description:
  Upstream raspberrypi patchset 2020-03-26

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

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

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

[Kernel-packages] [Bug 1837525] Re: [20.04 FEAT] Set Architecture Level (ALS) to z13

[Dimitri John Ledkov]

** Changed in: atlas (Ubuntu)
   Status: New => 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/1837525

Title:
  [20.04 FEAT] Set Architecture Level (ALS) to z13

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in atlas package in Ubuntu:
  Fix Committed
Status in gcc-9 package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  IBM requests to update the Architecture Level Set (ALS) as follow..
  march=z13
  mtune=z15

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

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

[Kernel-packages] [Bug 1868494] Re: The system hangs after a while of usage

[Kai-Heng Feng]

[ 1736.165122] mce: [Hardware Error]: CPU 4: Machine Check Exception: 5 Bank 0: 
f2070005
[ 1736.165125] mce: [Hardware Error]: RIP !INEXACT! 33:<7fffd19a92e1> 
[ 1736.165126] mce: [Hardware Error]: TSC e32f5eeda4d6 
[ 1736.165127] mce: [Hardware Error]: PROCESSOR 0:50654 TIME 1584908346 SOCKET 
0 APIC 8 microcode 264
[ 1736.165128] mce: [Hardware Error]: Run the above through 'mcelog --ascii'
[ 1736.165129] mce: [Hardware Error]: Machine check: Processor context corrupt
[ 1736.165130] Kernel panic - not syncing: Fatal machine check

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

Title:
  The system hangs after a while of usage

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since it is a hard hang, I suspect wireguard. I use wireguard as the
  vpn solution to connect to the office at work.

  ProblemType: KernelCrash
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-18-generic 5.4.0-18.22
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1316 F pulseaudio
lawrence   2050 F pulseaudio
   /dev/snd/controlC0:  gdm1316 F pulseaudio
lawrence   2050 F pulseaudio
  Date: Sun Mar 22 13:20:14 2020
  InstallationDate: Installed on 2020-02-06 (45 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Gigabyte Technology Co., Ltd. X299 AORUS Ultra Gaming
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=f3a48b61-47e3-43d3-9d03-b5ad88bf966d ro quiet splash 
crashkernel=512M-:192M vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-18-generic N/A
   linux-backports-modules-5.4.0-18-generic  N/A
   linux-firmware1.187
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  StagingDrivers: exfat
  UpgradeStatus: Upgraded to focal on 2020-03-22 (0 days ago)
  dmi.bios.date: 09/14/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: Default string
  dmi.board.name: X299 AORUS Ultra Gaming-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd09/14/2017:svnGigabyteTechnologyCo.,Ltd.:pnX299AORUSUltraGaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX299AORUSUltraGaming-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X299 AORUS Ultra Gaming
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1850238] Re: ucsi_ccg 50 second hang while resuming from s2ram with nvidia, recent kernels

[Kai-Heng Feng]

** Description changed:

+ === SRU Justification ===
+ [Impact]
+ Some systems have a "phantom" Nvidia UCSI, which prevent systems from
+ suspending. 
+ 
+ [Fix]
+ ucsi_ccg is stuck in its probe routine because of the i2c bus never
+ timeouts. Let it timeouts and probe can fail since it's just a phantom
+ device.
+ 
+ [Test]
+ After applying this patch system can suspend/resume succesfully.
+ 
+ [Regression Potential]
+ Low. It's a trivial change to correctly handle timeout.
+ 
+ === Original Bug Report ===
+ 
  Short version
  =
  I'm experiencing a 50-second hang each time I resume from a "deep" 
(suspend-to-RAM) sleep.
  
  It happens with the newer kernel (5.3 series; I'm currently running the
  version from eoan-proposed), but not with the version from the Ubuntu
  18.04.3 LTS (uname says "5.0.0-31-generic #33~18.04.1-Ubuntu SMP").
  
  [I haven't yet tried to test the mainline builds, nor to find/confirm
  the regression range, as this seems like something that will take me
  another week, and I'm not sure if it would be helpful.]
  
  I narrowed the problem down to what I believe is a broken USB Type-C
  controller on the NVIDIA GPU: the ucsi_ccg driver for
  /sys/devices/pci:00/:00:01.0/:01:00.3/i2c-0/0-0008 reports a
  timeout for both the initial PPM_RESET command (on system startup) and
  for the SET_NOTIFICATION_ENABLE command the driver runs on resume.
  
  I guess the hang is the driver waiting for a response to
  SET_NOTIFICATION_ENABLE; it appears to have been added recently in
  
https://github.com/torvalds/linux/commit/a94ecde41f7e51e2742e53b5f151aee662c54d39,
  which could explain why I don't see the hang with 5.0.x.
  
  Creating /etc/modprobe.d/dell.conf with a `blacklist ucsi_ccg` line (and
  rebooting) makes the hang go away.
  
- 
  Steps to reproduce
  ==
  (these are not the actual steps one can take to reproduce, starting from a 
new install; let me know if those will be useful)
  
  1. Boot Ubuntu 19.10 with NVIDIA GPU drivers uninstalled and the following 
kernel parameters 
:
-   nouveau.modeset=0 nouveau.runpm=0   # force using integrated graphics
- # (the problem can be reproduced 
using NVIDIA's proprietary driver too, but I
- # guessed it's better to avoid 
it, and nouveau prints lots of errors with this GPU)
-   mem_sleep_default=deep  # suspend to RAM; suspend-to-idle 
has its own problems on this system
+  nouveau.modeset=0 nouveau.runpm=0   # force using integrated graphics
+ # (the problem can be reproduced 
using NVIDIA's proprietary driver too, but I
+ # guessed it's better to avoid 
it, and nouveau prints lots of errors with this GPU)
+  mem_sleep_default=deep  # suspend to RAM; suspend-to-idle has 
its own problems on this system
  
  2. Run `dmesg -w` and wait a minute or two until a message like the
  following is printed:
  
-   [  175.611346] ucsi_ccg 0-0008: failed to reset PPM!
-   [  175.611355] ucsi_ccg 0-0008: PPM init failed (-110)
+  [  175.611346] ucsi_ccg 0-0008: failed to reset PPM!
+  [  175.611355] ucsi_ccg 0-0008: PPM init failed (-110)
  
  (attempting to suspend before the PPM init timeout will fail to enter sleep 
at all.)
  (if your system doesn't report PPM init timeout, you probably won't see the 
hang on resume either)
  
  3. Run `sudo pm-suspend` (using the power button to suspend causes other
  problems)
  
  ...wait for the laptop to go to sleep and the fans to turn off.
  
  4. Press Enter on the built-in keyboard to resume. (Although the way we
  wake up the system doesn't seem to matter.)
  
  5. Observe a hang lasting for almost a minute before the system is
  operational, with dmesg reporting:
  
-   [  299.331393] ata1.00: configured for UDMA/100
-   
+  [  299.331393] ata1.00: configured for UDMA/100
+  
  
-   [  346.133024] ucsi_ccg 0-0008: PPM NOT RESPONDING
-   [  346.133039] PM: dpm_run_callback(): ucsi_ccg_resume+0x0/0x20 
[ucsi_ccg] returns -110
-   [  346.133042] PM: Device 0-0008 failed to resume: error -110
-   ...
-   [  346.141504] Restarting tasks ... done.
-   [  346.340221] PM: suspend exit
- 
+  [  346.133024] ucsi_ccg 0-0008: PPM NOT RESPONDING
+  [  346.133039] PM: dpm_run_callback(): ucsi_ccg_resume+0x0/0x20 [ucsi_ccg] 
returns -110
+  [  346.133042] PM: Device 0-0008 failed to resume: error -110
+  ...
+  [  346.141504] Restarting tasks ... done.
+  [  346.340221] PM: suspend exit
  
  System info
  ===
  
  My Dell G3 3590 laptop has an NVIDIA "GeForce GTX 1660 Ti with Max-Q Design" 
GPU.
  NVIDIA's "Turing" chips include USB Type-C controller on the GPU (I read 
future VR headsets are supposed to use it 

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

[Po-Hsu Lin]

I can manually run the net suite in kselftest on 5.3.0-43-generic with modoc, 
by running the following command in Eoan tree: 
sudo make run_tests TARGETS=net

The test can finish without tripping this issue.

Also, I can see a "[   28.249600] ipr 0001:08:00.0: 8150: Permanent IOA
failure" message in boot dmesg, not sure if this means HW issue?

https://www.ibm.com/support/knowledgecenter/TI0003N/p8ebk/urc_tables.htm

** Attachment added: "modoc.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869032/+attachment/5341833/+files/modoc.log

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 1869123] Re: [LTCTest][OPAL][OP930] IMC PMU (null) Register failed

[Andrew Cloke]

Thanks. As this issue is seen with the 4.15 Bionic (18.04) kernel, I'll
update the tags and title accordingly. From Frank's comment above, I
think we can assume that this is fixed in Focal (20.04).

** Summary changed:

- [LTCTest][OPAL][OP930] IMC PMU (null) Register failed
+ [18.04][LTCTest][OPAL][OP930] IMC PMU (null) Register failed

** Tags removed: targetmilestone-inin2004
** Tags added: targetmilestone-1804

** Changed in: ubuntu-power-systems
   Status: Incomplete => Triaged

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

** Changed in: ubuntu-power-systems
   Status: Triaged => 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/1869123

Title:
  [18.04][LTCTest][OPAL][OP930] IMC PMU (null) Register failed

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

Bug description:
  == Comment: #0 - PAVAMAN SUBRAMANIYAM  - 2019-04-10 
00:15:32 ==
  Install a P9 Open Power Hardware with the latest OP930 Firmware images 
provided in the following link:
  
http://pfd.austin.ibm.com/releasenotes/openpower9/OP930/OP930_1913A/OP930_1913B_RelNote_Main.html

  root@witherspoon:~# cat /etc/os-release
  ID="openbmc-phosphor"
  NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)"
  VERSION="ibm-v2.3"
  VERSION_ID="ibm-v2.3-476-g2d622cb-r32-0-g9973ab0"
  PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) 
ibm-v2.3"
  BUILD_ID="ibm-v2.3-476-g2d622cb-r32"
  root@witherspoon:~# cat /var/lib/phosphor-software-manager/pnor/ro/VERSION
IBM-witherspoon-OP9-v2.2-9.71
  op-build-v2.2-58-gf60d718
  buildroot-2019.02-3-g28a7eab
  skiboot-v6.3-rc1
  hostboot-30a512e-pf453f1d
  occ-58e422d
  linux-4.19.30-openpower1-pa764076
  petitboot-v1.10.2
  machine-xml-e3e9aef
  hostboot-binaries-hw021419a.930
  capp-ucode-p9-dd2-v4
  sbe-1410677
  hcode-hw032719a.940

  Then seeing the following messages in dmesg of Linux HOST OS and also
  when we reboot the machine in the SOL console.

  [1.731663] nest_phb0_imc performance monitor hardware support registered
  [1.731704] nest_phb1_imc performance monitor hardware support registered
  [1.731746] nest_phb2_imc performance monitor hardware support registered
  [1.731788] nest_phb3_imc performance monitor hardware support registered
  [1.731829] nest_phb4_imc performance monitor hardware support registered
  [1.731870] nest_phb5_imc performance monitor hardware support registered
  [1.731944] nest_powerbus0_imc performance monitor hardware support 
registered
  [1.734458] thread_imc performance monitor hardware support registered
  [1.734460] IMC Unknown Device type
  [1.734462] IMC PMU (null) Register failed
  [1.734558] nest_xlink0_imc performance monitor hardware support registered
  [1.734614] nest_xlink1_imc performance monitor hardware support registered
  [1.734670] nest_xlink2_imc performance monitor hardware support registered
  [1.747043] Initialise system trusted keyrings
  [1.747054] Key type blacklist registered
  [1.747170] workingset: timestamp_bits=38 max_order=23 bucket_order=0

  == Comment: #2 - PAVAMAN SUBRAMANIYAM  - 2019-04-10 
00:30:47 ==
  So should this bug be moved to kernel to get the fixes be made available to 
Ubuntu 18.04 release or should we keep this bug opened for skiboot under OPAL 
itself, since we are already in the upstream level of skiboot installed on the 
system.

  == Comment: #5 - Application Cdeadmin  - 2019-04-11 
15:15:13 ==
   State: Open by: jayeshp on 11 April 2019 15:05:22 

  #=#=# 2019-04-11 15:05:21 (CDT) #=#=#
  New Fix_Potential = [P910.40W]
  #=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#

  == Comment: #7 - Application Cdeadmin  - 2019-04-16 
06:12:44 ==
  cde00 (cdead...@us.ibm.com) added native attachment 
/tmp/AIXOS11139536/0001-Return-for-invalid-domain.patch on 2019-04-16 06:12:39

  == Comment: #8 - Deborah L. McLemore  - 2019-04-20
  09:58:13 ==

  
  == Comment: #9 - Application Cdeadmin  - 2019-04-26 
08:25:05 ==
   State: Open by: csburns on 26 April 2019 08:15:35 

  The patch in comment #7 was included in a test pnor driver -
  op999.1999.20190423t - that was provided to ISST to look at several
  skiboot pending changes. This defect was also seen in System Mfg Test
  - so this patch should be merged for OP930 GA.

  == Comment: #10 - VASANT HEGDE  - 2019-05-14 23:02:35 
==
  Anju,

  Where are we with this patch? Did you push changes to upstream?

  Also is this really a ship issue?

  -Vasant

  == Comment: #15 - Klaus Heinrich Kiwi  - 2020-03-25 
06:27:01 ==
  (In reply to comment #13)
  > Patch is now upstream.
  > https://git.kernel.org/powerpc/c/b59bd3527fe3c1939340df558d7f9d56
  > 
  > Thanks,
  > Anju

  == Comment: #16 - Klaus 

[Kernel-packages] [Bug 1869123] Re: [18.04][LTCTest][OPAL][OP930] IMC PMU (null) Register failed

[bugproxy]

** Tags removed: targetmilestone-1804
** Tags added: targetmilestone-inin2004

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

Title:
  [18.04][LTCTest][OPAL][OP930] IMC PMU (null) Register failed

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

Bug description:
  == Comment: #0 - PAVAMAN SUBRAMANIYAM  - 2019-04-10 
00:15:32 ==
  Install a P9 Open Power Hardware with the latest OP930 Firmware images 
provided in the following link:
  
http://pfd.austin.ibm.com/releasenotes/openpower9/OP930/OP930_1913A/OP930_1913B_RelNote_Main.html

  root@witherspoon:~# cat /etc/os-release
  ID="openbmc-phosphor"
  NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)"
  VERSION="ibm-v2.3"
  VERSION_ID="ibm-v2.3-476-g2d622cb-r32-0-g9973ab0"
  PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) 
ibm-v2.3"
  BUILD_ID="ibm-v2.3-476-g2d622cb-r32"
  root@witherspoon:~# cat /var/lib/phosphor-software-manager/pnor/ro/VERSION
IBM-witherspoon-OP9-v2.2-9.71
  op-build-v2.2-58-gf60d718
  buildroot-2019.02-3-g28a7eab
  skiboot-v6.3-rc1
  hostboot-30a512e-pf453f1d
  occ-58e422d
  linux-4.19.30-openpower1-pa764076
  petitboot-v1.10.2
  machine-xml-e3e9aef
  hostboot-binaries-hw021419a.930
  capp-ucode-p9-dd2-v4
  sbe-1410677
  hcode-hw032719a.940

  Then seeing the following messages in dmesg of Linux HOST OS and also
  when we reboot the machine in the SOL console.

  [1.731663] nest_phb0_imc performance monitor hardware support registered
  [1.731704] nest_phb1_imc performance monitor hardware support registered
  [1.731746] nest_phb2_imc performance monitor hardware support registered
  [1.731788] nest_phb3_imc performance monitor hardware support registered
  [1.731829] nest_phb4_imc performance monitor hardware support registered
  [1.731870] nest_phb5_imc performance monitor hardware support registered
  [1.731944] nest_powerbus0_imc performance monitor hardware support 
registered
  [1.734458] thread_imc performance monitor hardware support registered
  [1.734460] IMC Unknown Device type
  [1.734462] IMC PMU (null) Register failed
  [1.734558] nest_xlink0_imc performance monitor hardware support registered
  [1.734614] nest_xlink1_imc performance monitor hardware support registered
  [1.734670] nest_xlink2_imc performance monitor hardware support registered
  [1.747043] Initialise system trusted keyrings
  [1.747054] Key type blacklist registered
  [1.747170] workingset: timestamp_bits=38 max_order=23 bucket_order=0

  == Comment: #2 - PAVAMAN SUBRAMANIYAM  - 2019-04-10 
00:30:47 ==
  So should this bug be moved to kernel to get the fixes be made available to 
Ubuntu 18.04 release or should we keep this bug opened for skiboot under OPAL 
itself, since we are already in the upstream level of skiboot installed on the 
system.

  == Comment: #5 - Application Cdeadmin  - 2019-04-11 
15:15:13 ==
   State: Open by: jayeshp on 11 April 2019 15:05:22 

  #=#=# 2019-04-11 15:05:21 (CDT) #=#=#
  New Fix_Potential = [P910.40W]
  #=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#

  == Comment: #7 - Application Cdeadmin  - 2019-04-16 
06:12:44 ==
  cde00 (cdead...@us.ibm.com) added native attachment 
/tmp/AIXOS11139536/0001-Return-for-invalid-domain.patch on 2019-04-16 06:12:39

  == Comment: #8 - Deborah L. McLemore  - 2019-04-20
  09:58:13 ==

  
  == Comment: #9 - Application Cdeadmin  - 2019-04-26 
08:25:05 ==
   State: Open by: csburns on 26 April 2019 08:15:35 

  The patch in comment #7 was included in a test pnor driver -
  op999.1999.20190423t - that was provided to ISST to look at several
  skiboot pending changes. This defect was also seen in System Mfg Test
  - so this patch should be merged for OP930 GA.

  == Comment: #10 - VASANT HEGDE  - 2019-05-14 23:02:35 
==
  Anju,

  Where are we with this patch? Did you push changes to upstream?

  Also is this really a ship issue?

  -Vasant

  == Comment: #15 - Klaus Heinrich Kiwi  - 2020-03-25 
06:27:01 ==
  (In reply to comment #13)
  > Patch is now upstream.
  > https://git.kernel.org/powerpc/c/b59bd3527fe3c1939340df558d7f9d56
  > 
  > Thanks,
  > Anju

  == Comment: #16 - Klaus Heinrich Kiwi  - 2020-03-25 
06:33:24 ==
  (In reply to comment #14)
  > (In reply to comment #13)
  > > Patch is now upstream.
  > > https://git.kernel.org/powerpc/c/b59bd3527fe3c1939340df558d7f9d56
  > > 
  > > Thanks,
  > > Anju
  > 
  > What next?  will you be sending fix to distros?
  > 
  > -Vasant

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

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