[Kernel-packages] [Bug 1772412] Re: zfs 0.7.9 fixes a bug (https://github.com/zfsonlinux/zfs/pull/7343) that hangs the system completely

2019-04-02 Thread Richard Laager
ZFS 0.7.9 was released in Cosmic (18.10). You could update to Cosmic.
Alternatively, on 18.04, you can install the HWE kernel package: linux-
image-generic-hwe-18.04

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

Title:
  zfs 0.7.9 fixes a bug (https://github.com/zfsonlinux/zfs/pull/7343)
  that hangs the system completely

Status in zfs-linux package in Ubuntu:
  Fix Released

Bug description:
  I have experienced the problems fixed by this commit
  https://github.com/zfsonlinux/zfs/pull/7343 a few times on my NAS. The
  system hangs completely when it occurs. It looks like 0.7.9 brings
  other interesting bug fixes that potentially freeze the system.

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

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


[Kernel-packages] [Bug 1822794] Re: linux-kvm: 4.18.0-1010.10 -proposed tracker

2019-04-02 Thread Khaled El Mously
** Summary changed:

- linux-kvm:  -proposed tracker
+ linux-kvm: 4.18.0-1010.10 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

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

Title:
  linux-kvm: 4.18.0-1010.10 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Cosmic:
  New

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

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

  -- swm properties --
  kernel-stable-master-bug: 1822796
  phase: Ready for Packaging
  phase-changed: Tuesday, 02. April 2019 19:03 UTC
  reason:
prepare-package: Pending -- version not specified

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

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


[Kernel-packages] [Bug 1821663] Re: [regression][snd_hda_codec_realtek] repeating crackling noise after 19.04 upgrade

2019-04-02 Thread Hui Wang
please install this dkms on rc4 or v5.0 kernel, reboot and test.

If you add the workaround of #12, please remove it first.

thx.
 

** Attachment added: "oem-audio-hda-daily-dkms_0.1_all_blacklist_pm.deb"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821663/+attachment/5252351/+files/oem-audio-hda-daily-dkms_0.1_all_blacklist_pm.deb

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

Title:
  [regression][snd_hda_codec_realtek] repeating crackling noise after
  19.04 upgrade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm experiencing a repeating crackling noise after 19.04 upgrade that
  start just after the boot and before the login.

  I tried a bunch of fixes for pulseaudio I found googling, including this one 
https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Glitches.2C_skips_or_crackling
   and this one 
https://askubuntu.com/questions/864608/audio-crackle-through-headphones. 
Neither of which helped.

  The command "killall pulseaudio" usually stop the noise for 10
  seconds, then the noise restart.

  The system was running smoothly on 18.10

  Alessandro-

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alessandro   3310 F pulseaudio
   /dev/snd/controlC0:  alessandro   3310 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 26 03:29:00 2019
  InstallationDate: Installed on 2016-07-09 (989 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-03-25 (0 days ago)
  dmi.bios.date: 02/14/2006
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: GA-8TRC410M-NF
  dmi.board.vendor: NEC COMPUTERS INTERNATIONAL
  dmi.chassis.type: 3
  dmi.chassis.vendor: NEC COMPUTERS INTERNATIONAL
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/14/2006:svnPackardBellNEC:pnIMEDIA5204:pvrPB34310106:rvnNECCOMPUTERSINTERNATIONAL:rnGA-8TRC410M-NF:rvr:cvnNECCOMPUTERSINTERNATIONAL:ct3:cvr:
  dmi.product.name: IMEDIA 5204
  dmi.product.version: PB34310106
  dmi.sys.vendor: Packard Bell NEC

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

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


[Kernel-packages] [Bug 1821663] Re: [regression][snd_hda_codec_realtek] repeating crackling noise after 19.04 upgrade

2019-04-02 Thread Hui Wang
It is an issue of power_save setting. It is not a driver's code issue,
it is a kconfig issue. From rc4, the CONFIG_SND_HDA_POWER_SAVE_DEFAULT
is set to 1 rather 0, then the codec enables the runtime PM, that
introduce the noise.

You can workaround it by adding an module parameter (/etc/modprobe.d
/alsa-base.conf, add a new line in this file and reboot. "options snd-
hda-intel power_save=0".

And I will change the driver's code, and upload a new dkms, if that dkms
works, you don't need to add that module parameter anymore.

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

Title:
  [regression][snd_hda_codec_realtek] repeating crackling noise after
  19.04 upgrade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm experiencing a repeating crackling noise after 19.04 upgrade that
  start just after the boot and before the login.

  I tried a bunch of fixes for pulseaudio I found googling, including this one 
https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Glitches.2C_skips_or_crackling
   and this one 
https://askubuntu.com/questions/864608/audio-crackle-through-headphones. 
Neither of which helped.

  The command "killall pulseaudio" usually stop the noise for 10
  seconds, then the noise restart.

  The system was running smoothly on 18.10

  Alessandro-

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alessandro   3310 F pulseaudio
   /dev/snd/controlC0:  alessandro   3310 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 26 03:29:00 2019
  InstallationDate: Installed on 2016-07-09 (989 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-03-25 (0 days ago)
  dmi.bios.date: 02/14/2006
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: GA-8TRC410M-NF
  dmi.board.vendor: NEC COMPUTERS INTERNATIONAL
  dmi.chassis.type: 3
  dmi.chassis.vendor: NEC COMPUTERS INTERNATIONAL
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/14/2006:svnPackardBellNEC:pnIMEDIA5204:pvrPB34310106:rvnNECCOMPUTERSINTERNATIONAL:rnGA-8TRC410M-NF:rvr:cvnNECCOMPUTERSINTERNATIONAL:ct3:cvr:
  dmi.product.name: IMEDIA 5204
  dmi.product.version: PB34310106
  dmi.sys.vendor: Packard Bell NEC

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

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


[Kernel-packages] [Bug 1822870] Re: Backport support for software count cache flush Spectre v2 mitigation. (CVE) (required for POWER9 DD2.3)

2019-04-02 Thread Frank Heimes
** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-power-systems
   Importance: Undecided => Critical

** Information type changed from Public to Public Security

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Canonical Kernel Security Team 
(canonical-kernel-security-team)

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

Title:
  Backport support for software count cache flush Spectre v2 mitigation.
  (CVE) (required for POWER9 DD2.3)

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

Bug description:
  For the different kernels:

  The HWE a563fd9c62f0 UBUNTU: Ubuntu-hwe-4.18.0-17.18~18.04.1 appears
  to have all patches.

  Disco appears to be missing only this patch:
  92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 
reporting

  Cosmic (which is supported until July) is missing a number of patches:
  cf175dc315f90185128fb061dc05b6fbb211aa2f powerpc/64: Disable the speculation 
barrier from the command line
  6453b532f2c8856a80381e6b9a1f5ea2f12294df powerpc/64: Make stf barrier 
PPC_BOOK3S_64 specific.
  179ab1cbf883575c3a585bcfc0f2160f1d22a149 powerpc/64: Add 
CONFIG_PPC_BARRIER_NOSPEC
  af375eefbfb27cbb5b831984e66d724a40d26b5c powerpc/64: Call 
setup_barrier_nospec() from setup_arch()
  406d2b6ae3420f5bb2b3db6986dc6f0b6dbb637b powerpc/64: Make meltdown reporting 
Book3S 64 specific
  06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro 
& helpers for patching instructions
  dc8c6cce9a26a51fc19961accb978217a3ba8c75 powerpc/64s: Add new security 
feature flags for count cache flush
  ee13cb249fabdff8b90aaff61add347749280087 powerpc/64s: Add support for 
software count cache flush
  ba72dc171954b782a79d25e0f4b3ed91090c3b1e powerpc/pseries: Query hypervisor 
for count cache flush settings
  99d54754d3d5f896a8f616b0b6520662bc99d66b powerpc/powernv: Query firmware for 
count cache flush settings
  7d8bad99ba5a22892f0cad6881289fdc3875a930 powerpc/fsl: Fix spectre_v2 
mitigations reporting
  92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 
reporting
  This appears to already be in -next.

  For the bionic 18.04.1 (4.15) kernel only this patch is already part of 
master-next:
  a6b3964ad71a61bb7c61d80a60bea7d42187b2eb powerpc/64s: Add barrier_nospec

  The others are ported, there were only 3 that were not clean.  Those are:
  2eea7f067f495e33b8b116b35b5988ab2b8aec55 powerpc/64s: Add support for ori 
barrier_nospec patching
  This failed because commit a048a07d7f4535baa4cbad6bc024f175317ab938 is 
missing, but it does not look like that is required here.

  cb3d6759a93c6d0aea1c10deb6d00e111c29c19c powerpc/64s: Enable barrier_nospec 
based on firmware settings
  This failed because debugfs was already included, I can see that previously 
added, I didn't see where it was previously removed.

  06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro 
& helpers for patching instructions
  This failed because 8183d99f4a22c is not included - but doesn't seem 
necessary.

  All other patches applied with, at most, some fuzz.

  Has had a little testing - boots, check debugfs, etc.

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

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


[Kernel-packages] [Bug 1822797] Re: ZFS module is installed for wrong kernel on arm64-raspi3 systems (19.04 beta)

2019-04-02 Thread Lasse
I have had good experience with running ZFS on rpi3 using other distros.
Of course it would be a complete craziness to use zfs in a desktop setup
with just 1Gb of RAM. For what rpi is actually meant, 1Gb is plenty
enough to run ZFS especially if the ARC size is set to a smaller value.

This is why I hope this problem would get fixed, so I am able to use
Ubuntu on all platforms.

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

Title:
  ZFS module is installed for wrong kernel on arm64-raspi3 systems
  (19.04 beta)

Status in linux-raspi2 package in Ubuntu:
  Triaged

Bug description:
  Platform: Raspberry Pi 3 running ubuntu-19.04-beta-preinstalled-
  server-arm64+raspi3.img

  Kernel: Default (Linux ubuntu 4.18.0-1010-raspi2 #12-Ubuntu SMP
  PREEMPT Tue Feb 12 12:17:11 UTC 2019 aarch64 aarch64 aarch64
  GNU/Linux)

  Problem: The ZFS module is installed for a kernel that can not be
  used.

  apt-get install zfs-initramfs 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following additional packages will be installed:
libnvpair1linux libuutil1linux libzfs2linux libzpool2linux
linux-image-unsigned-5.0.0-8-snapdragon
linux-modules-5.0.0-8-snapdragon zfs-zed zfsutils-linux
  Suggested packages:
fdutils linux-doc-5.0.0 | linux-source-5.0.0 linux-tools
linux-headers-5.0.0-8-snapdragon nfs-kernel-server
samba-common-bin
  The following NEW packages will be installed:
libnvpair1linux libuutil1linux libzfs2linux libzpool2linux
linux-image-unsigned-5.0.0-8-snapdragon
linux-modules-5.0.0-8-snapdragon zfs-initramfs zfs-zed
zfsutils-linux
  0 upgraded, 9 newly installed, 0 to remove and 0 not upgraded.
  Need to get 55.7 MB of archives.
  After this operation, 305 MB of additional disk space will be used.
  Do you want to continue? [Y/n] Y
  Get:1 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 
linux-modules-5.0.0-8-snapdragon arm64 5.0.0-8.9 [47.5 MB]
  Get:2 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 
linux-image-unsigned-5.0.0-8-snapdragon arm64 5.0.0-8.9 [7169 kB]
  Get:3 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 libnvpair1linux 
arm64 0.7.12-1ubuntu5 [42.8 kB]
  Get:4 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 libuutil1linux 
arm64 0.7.12-1ubuntu5 [50.7 kB]
  Get:5 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 libzpool2linux 
arm64 0.7.12-1ubuntu5 [498 kB]
  Get:6 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 libzfs2linux 
arm64 0.7.12-1ubuntu5 [121 kB]
  Get:7 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 zfsutils-linux 
arm64 0.7.12-1ubuntu5 [267 kB]
  Get:8 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 zfs-initramfs 
arm64 0.7.12-1ubuntu5 [22.2 kB]
  Get:9 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 zfs-zed arm64 
0.7.12-1ubuntu5 [57.5 kB]
  Fetched 55.7 MB in 37s (1486 kB/s)   
  Selecting previously unselected package linux-modules-5.0.0-8-snapdragon.
  (Reading database ... 61671 files and directories currently installed.)
  Preparing to unpack 
.../0-linux-modules-5.0.0-8-snapdragon_5.0.0-8.9_arm64.deb ...
  Unpacking linux-modules-5.0.0-8-snapdragon (5.0.0-8.9) ...
  Selecting previously unselected package 
linux-image-unsigned-5.0.0-8-snapdragon.
  Preparing to unpack 
.../1-linux-image-unsigned-5.0.0-8-snapdragon_5.0.0-8.9_arm64.deb ...
  Unpacking linux-image-unsigned-5.0.0-8-snapdragon (5.0.0-8.9) ...
  Selecting previously unselected package libnvpair1linux.
  Preparing to unpack .../2-libnvpair1linux_0.7.12-1ubuntu5_arm64.deb ...
  Unpacking libnvpair1linux (0.7.12-1ubuntu5) ...
  Selecting previously unselected package libuutil1linux.
  Preparing to unpack .../3-libuutil1linux_0.7.12-1ubuntu5_arm64.deb ...
  Unpacking libuutil1linux (0.7.12-1ubuntu5) ...
  Selecting previously unselected package libzpool2linux.
  Preparing to unpack .../4-libzpool2linux_0.7.12-1ubuntu5_arm64.deb ...
  Unpacking libzpool2linux (0.7.12-1ubuntu5) ...
  Selecting previously unselected package libzfs2linux.
  Preparing to unpack .../5-libzfs2linux_0.7.12-1ubuntu5_arm64.deb ...
  Unpacking libzfs2linux (0.7.12-1ubuntu5) ...
  Selecting previously unselected package zfsutils-linux.
  Preparing to unpack .../6-zfsutils-linux_0.7.12-1ubuntu5_arm64.deb ...
  Unpacking zfsutils-linux (0.7.12-1ubuntu5) ...
  Selecting previously unselected package zfs-initramfs.
  Preparing to unpack .../7-zfs-initramfs_0.7.12-1ubuntu5_arm64.deb ...
  Unpacking zfs-initramfs (0.7.12-1ubuntu5) ...
  Selecting previously unselected package zfs-zed.
  Preparing to unpack .../8-zfs-zed_0.7.12-1ubuntu5_arm64.deb ...
  Unpacking zfs-zed (0.7.12-1ubuntu5) ...
  Setting up libuutil1linux (0.7.12-1ubuntu5) ...
  Setting up linux-modules-5.0.0-8-snapdragon (5.0.0-8.9) ...
  Setting up 

[Kernel-packages] [Bug 1822937] [NEW] NVIDIA settings won't write to /etc/xorg

2019-04-02 Thread Jonty Gamao
Public bug reported:

I tried running it with root (`sudo nvidia-settings`) and without.

I also generated an xorg file with `nvidia-xconfig`, and do the same
thing, but it still won't work.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: nvidia-settings 418.56-0ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
Uname: Linux 5.0.0-8-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
CurrentDesktop: KDE
Date: Wed Apr  3 00:33:48 2019
InstallationDate: Installed on 2019-04-02 (0 days ago)
InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1)
SourcePackage: nvidia-settings
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-settings (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug disco third-party-packages

** Attachment added: "Screenshot"
   
https://bugs.launchpad.net/bugs/1822937/+attachment/5252338/+files/Screenshot_20190403_002628.png

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

Title:
  NVIDIA settings won't write to /etc/xorg

Status in nvidia-settings package in Ubuntu:
  New

Bug description:
  I tried running it with root (`sudo nvidia-settings`) and without.

  I also generated an xorg file with `nvidia-xconfig`, and do the same
  thing, but it still won't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nvidia-settings 418.56-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Apr  3 00:33:48 2019
  InstallationDate: Installed on 2019-04-02 (0 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1)
  SourcePackage: nvidia-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1821663] Re: [regression][snd_hda_codec_realtek] repeating crackling noise after 19.04 upgrade

2019-04-02 Thread Daniel van Vugt
** Summary changed:

- [snd_hda_codec_realtek] repeating crackling noise after 19.04 upgrade
+ [regression][snd_hda_codec_realtek] repeating crackling noise after 19.04 
upgrade

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

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

Title:
  [regression][snd_hda_codec_realtek] repeating crackling noise after
  19.04 upgrade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm experiencing a repeating crackling noise after 19.04 upgrade that
  start just after the boot and before the login.

  I tried a bunch of fixes for pulseaudio I found googling, including this one 
https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Glitches.2C_skips_or_crackling
   and this one 
https://askubuntu.com/questions/864608/audio-crackle-through-headphones. 
Neither of which helped.

  The command "killall pulseaudio" usually stop the noise for 10
  seconds, then the noise restart.

  The system was running smoothly on 18.10

  Alessandro-

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alessandro   3310 F pulseaudio
   /dev/snd/controlC0:  alessandro   3310 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 26 03:29:00 2019
  InstallationDate: Installed on 2016-07-09 (989 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-03-25 (0 days ago)
  dmi.bios.date: 02/14/2006
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: GA-8TRC410M-NF
  dmi.board.vendor: NEC COMPUTERS INTERNATIONAL
  dmi.chassis.type: 3
  dmi.chassis.vendor: NEC COMPUTERS INTERNATIONAL
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/14/2006:svnPackardBellNEC:pnIMEDIA5204:pvrPB34310106:rvnNECCOMPUTERSINTERNATIONAL:rnGA-8TRC410M-NF:rvr:cvnNECCOMPUTERSINTERNATIONAL:ct3:cvr:
  dmi.product.name: IMEDIA 5204
  dmi.product.version: PB34310106
  dmi.sys.vendor: Packard Bell NEC

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

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


[Kernel-packages] [Bug 1731768] Re: Random desktop freeze

2019-04-02 Thread Dante Marshal
Using NVidia driver v390.116, I'm also experiencing freezes. Mouse only
moves but Mouse buttons and Keyboard don't work while freezed. Though
after the freeze all actions are performed at once. For example if I hit
Alt+Tab 3 times on freeze, nothing happens then suddenly windows switch
3 times.

I'm on KDE, and kwin keeps crashing / sometimes "Restarting because of a
Graphics reset" as stated in the notification.

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

Title:
  Random desktop freeze

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

Bug description:
  Since the last update (384.90-0ubuntu0.16.04.1 to
  384.90-0ubuntu0.16.04.2) I experience random desktop freezes. To
  recover I have to switch to tty1 and do a restart of the lightdm
  service. This has the consequence of closing all running applications.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nvidia-384 384.90-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Nov 12 16:13:56 2017
  InstallationDate: Installed on 2016-11-19 (358 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: nvidia-graphics-drivers-384
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1822786] Re: linux-raspi2: 4.18.0-1012.14 -proposed tracker

2019-04-02 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-signing-to-proposed
   Status: New => Invalid

** 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 --
  kernel-stable-master-bug: 1822796
- phase: Ready for Packaging
- phase-changed: Tuesday, 02. April 2019 19:05 UTC
+ phase: Packaging
+ phase-changed: Wednesday, 03. April 2019 03:30 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded

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

Title:
  linux-raspi2: 4.18.0-1012.14 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Cosmic:
  New

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

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

  -- swm properties --
  kernel-stable-master-bug: 1822796
  phase: Packaging
  phase-changed: Wednesday, 03. April 2019 03:30 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded

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

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


[Kernel-packages] [Bug 1822834] Re: linux: 4.4.0-146.172 -proposed tracker

2019-04-02 Thread 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
  
  backports: bug 1822832 (trusty/linux-aws), bug 1822833 
(trusty/linux-lts-xenial)
  derivatives: bug 1822824 (linux-aws), bug 1822825 (linux-euclid), bug 1822826 
(linux-kvm), bug 1822828 (linux-raspi2), bug 1822829 (linux-snapdragon), bug 
1822830 (linux-fips)
  
  -- swm properties --
- phase: Ready for Packaging
- phase-changed: Tuesday, 02. April 2019 15:16 UTC
+ phase: Packaging
+ phase-changed: Wednesday, 03. April 2019 03:33 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
+   prepare-package-signed: Pending -- package not yet uploaded

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

Title:
  linux: 4.4.0-146.172 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

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

  backports: bug 1822832 (trusty/linux-aws), bug 1822833 
(trusty/linux-lts-xenial)
  derivatives: bug 1822824 (linux-aws), bug 1822825 (linux-euclid), bug 1822826 
(linux-kvm), bug 1822828 (linux-raspi2), bug 1822829 (linux-snapdragon), bug 
1822830 (linux-fips)

  -- swm properties --
  phase: Packaging
  phase-changed: Wednesday, 03. April 2019 03:33 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded

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

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


[Kernel-packages] [Bug 1822854] Re: External monitor turns off for short period of times / until moving mouse

2019-04-02 Thread Daniel van Vugt
I don't think this is going to be a gnome-shell or mutter bug. But in
case it is, please test some other desktop environments to verify.

** Changed in: gnome-shell (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/1822854

Title:
  External monitor turns off for short period of times / until moving
  mouse

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In disco; I have this issue where my external monitor (a ThinkVision
  P24h-10) connected to my ThinkPad T480s turns off for short times
  while actively working on the system. I noticed that if I don't move
  my mouse at all while it's off, it stays off.

  The T480s is connected to the monitor via USB-C; the monitor provides
  DP, USB, and Power over that connection. When the display turns off,
  USB devices continue working.

  I have attached /sys/debug/dri/0 output from when the monitor was off
  (a) vs on (b).

  Other related bits:
  * This also happens on HDMI, but much less often
  * There are no log messages when the display turns on/off in the journal.

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

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


[Kernel-packages] [Bug 1822786] Re: linux-raspi2: 4.18.0-1012.14 -proposed tracker

2019-04-02 Thread Khaled El Mously
** Summary changed:

- linux-raspi2:  -proposed tracker
+ linux-raspi2: 4.18.0-1012.14 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

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

Title:
  linux-raspi2: 4.18.0-1012.14 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Cosmic:
  New

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

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

  -- swm properties --
  kernel-stable-master-bug: 1822796
  phase: Packaging
  phase-changed: Wednesday, 03. April 2019 03:30 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded

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

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


[Kernel-packages] [Bug 1658219] Re: flock not mediated by 'k'

2019-04-02 Thread thighland
I encountered this issue on xenial after updating to Azure's 4.15 kernel
for testing. We started encountering an apparmor deny which doesn't
happen on the latest 4.4 kernel. I had missed setting the k flag for a
policy, and everything worked on the new kerenl once we fixed the
policy.

Given that this bug leads to incorrect enforcement of policy does it
make sense to release a fix for xenial?

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

Title:
  flock not mediated by 'k'

Status in AppArmor:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Yakkety:
  Won't Fix

Bug description:
  $ cat ./apparmor.profile 
  #include 

  profile test {
#include 

/bin/bash ixr,
/dev/pts/* rw,
/usr/bin/flock ixr,
# Not blocked:
# aa-exec -p test -- flock -w 1 /tmp/test.lock -c true
/tmp/test.lock rw,

  }

  $ sudo apparmor_parser -r ./apparmor.profile

  $ aa-exec -p test -- flock -w 1 /tmp/test.lock -c true && echo yes
  yes

  $ ls -l /tmp/test.lock 
  -rw-rw-r-- 1 jamie jamie 0 Jan 20 15:57 /tmp/test.lock

  The flock command uses flock(LOCK_EX) and I expected it to be blocked
  due to the lack of 'k'.

  apparmor userspace 2.10.95-0ubuntu2.5 (xenial) and 4.9.0-12.13-generic
  kernel on amd64.

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

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


[Kernel-packages] [Bug 1822834] Re: linux: 4.4.0-146.172 -proposed tracker

2019-04-02 Thread Khaled El Mously
** Summary changed:

- linux:  -proposed tracker
+ linux: 4.4.0-146.172 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

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

Title:
  linux: 4.4.0-146.172 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

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

  backports: bug 1822832 (trusty/linux-aws), bug 1822833 
(trusty/linux-lts-xenial)
  derivatives: bug 1822824 (linux-aws), bug 1822825 (linux-euclid), bug 1822826 
(linux-kvm), bug 1822828 (linux-raspi2), bug 1822829 (linux-snapdragon), bug 
1822830 (linux-fips)

  -- swm properties --
  phase: Ready for Packaging
  phase-changed: Tuesday, 02. April 2019 15:16 UTC
  reason:
prepare-package: Pending -- version not specified

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

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


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

2019-04-02 Thread 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 1821641

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

Title:
  [HP Elitebook 840 G1] Screen is upside down on 19.04 daily

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On the 19.04 daily image (2019-03-24), the screen on my laptop is
  completely upside down, from the moment the GUI loads. This does not
  happen on 18.04 and 18.10.

  It appears to be an accelerometer issue since holding the laptop
  upside down flips the image to its correct orientation - basically the
  functionality of the accelerometer is suddenly inverted.

  Please contact me if you want me to help testing the issue on my
  hardware. Thanks!

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

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


[Kernel-packages] [Bug 1821882] Re: Screen is very dark and brightness cannot be adjusted

2019-04-02 Thread Pierre Equoy
Sorry Timo, I had missed your last comment.

It's not a regression. The same thing happens on a 18.04.2 live session.

Please find attached a snapshot of the BIOS screen.

As you can see, there are two options:

- Enable Switchable Graphics (1)
- Discrete Graphics Controller Direct Output Mode (2)

I tried to start the 19.04 beta live USB in the four possible cases,
here are the results:

 (1) | (2) | Comments
-+-+---
 [ ] | [ ] | Issue described in original description
-+-+---
 [ ] | [X] | Issue described in original description
-+-+---
 [X] | [ ] | OK (/sys/class/backlight/ has only one element: "intel_backlight"
 | | Backlight can be adjusted with backlight keys
 | | `lspci` freezes, probably because of a nouveau bug
 | | Enough to install Ubuntu and switch to nvidia closed drivers
-+-+---
 [X] | [X] | OK (/sys/class/backlight/ has only one element: "intel_backlight"
 | | Backlight can be adjusted with backlight keys
 | | `lspci` freezes, probably because of a nouveau bug
 | | Enough to install Ubuntu and switch to nvidia closed drivers
-+-+---

** Attachment added: "20190403_100225.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821882/+attachment/5252334/+files/20190403_100225.jpg

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

Title:
  Screen is very dark and brightness cannot be adjusted

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Device: Dell Precision 7530
  In the BIOS, the Switchable Graphics option is deactived, which means only 
the nVidia GPU is used.

  When booting 19.04 beta live USB, the screen becomes very dark and
  brightness cannot be adjusted. (The same issue happens with 18.04.2)

  There is only a "nv_backlight" in /sys/class/backlight/ (i.e. no
  intel_backlight):

  $ ll /sys/class/backlight/
  total 0
  drwxr-xr-x  2 root root 0 Mar 27 09:36 ./
  drwxr-xr-x 74 root root 0 Mar 27 09:28 ../
  lrwxrwxrwx  1 root root 0 Mar 27 09:28 nv_backlight -> 
../../devices/pci:00/:00:01.0/:01:00.0/drm/card0/card0-eDP-1/nv_backlight/

  Trying to manually change brightness doesn't do anything:

  $ sudo su
  root@ubuntu:/home/ubuntu# cd /sys/class/backlight/nv_backlight
  root@ubuntu:/sys/class/backlight/nv_backlight# ll
  total 0
  drwxr-xr-x 3 root root0 Mar 27 09:28 ./
  drwxr-xr-x 4 root root0 Mar 27 09:28 ../
  -r--r--r-- 1 root root 4096 Mar 27 09:37 actual_brightness
  -rw-r--r-- 1 root root 4096 Mar 27 09:37 bl_power
  -rw-r--r-- 1 root root 4096 Mar 27 09:28 brightness
  lrwxrwxrwx 1 root root0 Mar 27 09:37 device -> ../../card0-eDP-1/
  -r--r--r-- 1 root root 4096 Mar 27 09:28 max_brightness
  drwxr-xr-x 2 root root0 Mar 27 09:28 power/
  lrwxrwxrwx 1 root root0 Mar 27 09:28 subsystem -> 
../../../../../../../../class/backlight/
  -r--r--r-- 1 root root 4096 Mar 27 09:28 type
  -rw-r--r-- 1 root root 4096 Mar 27 09:28 uevent
  root@ubuntu:/sys/class/backlight/nv_backlight# cat actual_brightness
  100
  root@ubuntu:/sys/class/backlight/nv_backlight# cat brightness
  100
  root@ubuntu:/sys/class/backlight/nv_backlight# cat max_brightness
  100
  root@ubuntu:/sys/class/backlight/nv_backlight# echo 50 > brightness
  root@ubuntu:/sys/class/backlight/nv_backlight# cat brightness
  50

  Although the value is changed, the screen brightness doesn't change.

  in dmesg, I can see the following:

  [0.241878] ACPI: Added _OSI(Module Device)
  [0.241878] ACPI: Added _OSI(Processor Device)
  [0.241878] ACPI: Added _OSI(3.0 _SCP Extensions)
  [0.241878] ACPI: Added _OSI(Processor Aggregator Device)
  [0.241878] ACPI: Added _OSI(Linux-Dell-Video)
  [0.241878] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
  [0.241878] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
  [0.286326] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.286332] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.286334] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.286336] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS01._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.286339] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.286340] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.287096] ACPI BIOS Error (bug): Failure creating 

[Kernel-packages] [Bug 1821641] Re: [HP Elitebook 840 G1] Screen is upside down on 19.04 daily

2019-04-02 Thread Daniel van Vugt
It sounds like this bug is correctly assigned to the kernel. No need to
move it in my opinion.

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

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

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

Title:
  [HP Elitebook 840 G1] Screen is upside down on 19.04 daily

Status in linux package in Ubuntu:
  New

Bug description:
  On the 19.04 daily image (2019-03-24), the screen on my laptop is
  completely upside down, from the moment the GUI loads. This does not
  happen on 18.04 and 18.10.

  It appears to be an accelerometer issue since holding the laptop
  upside down flips the image to its correct orientation - basically the
  functionality of the accelerometer is suddenly inverted.

  Please contact me if you want me to help testing the issue on my
  hardware. Thanks!

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

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


[Kernel-packages] [Bug 1819023] Re: [nouveau] Scrolling screen flicker, especially on default Ubuntu lock screen

2019-04-02 Thread Daniel van Vugt
Thanks for the animation.

I think that flicker is occurring in the LCD itself. The reason is that
the old gradient (which was only used in Ubuntu 18.10) covers more
colours than 24-bit RGB can support. On top of that, if your monitor is
only 18-bit RGB in hardware then you will see even fewer colours and the
display/kernel will flicker on purpose to create the illusion of all the
shades it can't really display. This is called temporal dithering, or
Frame Rate Control:

  https://en.wikipedia.org/wiki/Frame_rate_control

Essentially that gradient is just a pathological case which will make
the shimmering/flickering more visible than it usually is. For this and
other reasons, I reported a bug 1789355 too.

In the end this is a hardware limitation. But it is a common one which
the kernel driver should have some control over. You should be able to
configure the nouveau kernel driver directly using something like:

  xrandr --output DVI-I-1 --set "dithering mode" "off"

or

  xrandr --output DVI-I-1 --set "dithering mode" "static 2x2"

based on your Xrandr.txt which says:

dithering depth: auto 
supported: auto, 6 bpc, 8 bpc
dithering mode: auto 
supported: auto, off, static 2x2, dynamic 2x2

I am going to reassign this bug to the kernel because it sounds like the
only software solution possible here would be for the kernel to
automatically choose a less annoying dithering mode for this model of
monitor.

P.S. The gradient is completely gone in Ubuntu 19.04 so you won't have
any trouble there.


** Package changed: xorg-server (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/1819023

Title:
  [nouveau] Scrolling screen flicker, especially on default Ubuntu lock
  screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My screen is experiencing a weird "scrolling" flicker, especially
  while displaying blue, indigo, and violet hues/colors, such as on the
  default Ubuntu 18.10 (x64 Desktop) lock screen. The screen flicker
  scrolls up and down, with the brightest part of the flicker being
  towards the top, with a gradient that fades back to the original color
  near the bottom.

  Problem occurs on any one monitor on any one video output protocol
  (DVI-D, HDMI, and VGA).

  
  I will upload an illustration or render as soon as possible for better 
explanation.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  7 10:39:50 2019
  DistUpgraded: 2018-10-19 10:50:54,557 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 440] [10de:0de0] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation GF108 [GeForce GT 440] [10de:0828]
  InstallationDate: Installed on 2018-08-17 (202 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: BIOSTAR Group A880G+
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=a967adb1-1600-455b-8704-e2bf5de5081d ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to cosmic on 2018-10-19 (139 days ago)
  dmi.bios.date: 09/21/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080016
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: A880G+
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/21/2011:svnBIOSTARGroup:pnA880G+:pvr:rvnBIOSTARGroup:rnA880G+:rvr:cvnBIOSTARGroup:ct3:cvr:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: A880G+
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.sys.vendor: BIOSTAR Group
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  

[Kernel-packages] [Bug 1819915] Re: s2disk freezes at saving image to disk (hibernation)

2019-04-02 Thread Kai-Heng Feng
> Could you please test or tell what happens with nvidia selected?
Hang at freeze or thaw stage. Can't really tell.
Nothing much as I do as it's proprietary.

> Are you on the latest release? 18.04.2? Up to date?
Both kernel 4.15 and 4.18.

I did increase the size of swapfile to match the RAM size though.

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

Title:
  s2disk freezes at saving image to disk (hibernation)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This started happening after I upgrade to ubuntu 18.04.2. In 18.04.1
  hibernation was working flawlessly on my machine. (with kernel
  4.15-46! not a kernel issue then?)

  Another thing that got updated recently was nvidia drivers which were
  known to cause hibernation issues, but those were on restoring the
  snapshot.

  http://imgur.com/gallery/jOyHEcL  --> I get stuck on this screen after
  running hibernate or pm-hibernate. (sys-req REISUB combination works
  there and is the only good way to restart I found)

  
  SPECS

  Laptop Dell Inspiron 7567 A30P
  Intel Core i7-7700HQ
  1x 16 GB DDR4 
  1 TB HDD + 256 GB SSD 
  Nvidia GeForce GTX 1050 
  Ti FHD display 
  Intel Dual Band Wireless AC 3165 
  1x1 Motherboard: 
  Intel HM175 Graphics adapter: 
  NVIDIA GeForce GTX 1050 Ti (Laptop) - 4096 MB, 
  Core: 1620 MHz, 
  Memory: 1752 MHz, 
  GDDR5, 21.21.13.7320 (ForceWare 373.20), 
  Nvidia Optimus

  nvidia driver: 415.27

  INFO

  # uname -a
  Linux matheus-Inspiron-15-7000-Gaming 4.15.0-46-generic #49-Ubuntu SMP Wed 
Feb 6 09:33:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  # free -m
totalusedfree  shared  buff/cache   
available
  Mem:  1590629258742 1614238   
12485
  Swap: 16333   0   16333

  # cat /etc/fstab | grep swap
  # swap was on /dev/sda8 during installation
  UUID=70d967e6-ad52-4c21-baf0-01a813ccc6ac noneswapsw  
0   0
  n

  root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | 
grep hibernate 
  root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | 
grep hiber 
  root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | 
grep s2disk
  root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | 
grep hibernation

  
  I could find nothing scrolling up on syslog about the hibernation process or 
with grep 

  
  An interesting Note is that if I run hibernate just after I boot, it works 
and resumes perfectly! But after some system usage it randomly has that problem 
if I try. The percentage it freezes at is also random, sometimes 0, 1 even 30 
once.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   matheus   25949 F...m pulseaudio
   /dev/snd/pcmC0D0p:   matheus   25949 F...m pulseaudio
   /dev/snd/controlC0:  matheus   25949 F pulseaudio
   /dev/snd/seq:matheus4986 f qsynth
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bfc6f294-b737-4999-a444-01e1f410de06
  InstallationDate: Installed on 2018-05-10 (308 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Dell Inc. Inspiron 15 7000 Gaming
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=659db14c-2a6c-4f9c-93bf-d31c4a84abb6 ro nouveau.blacklist=1 debug 
no_console_suspend systemd.log_level=info nvidia-drm.modeset=0
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-46-generic N/A
   linux-backports-modules-4.15.0-46-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip kvm lpadmin netdev plugdev sambashare sudo 
vboxusers
  _MarkForUpload: True
  dmi.bios.date: 08/15/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.1
  dmi.board.name: 0P84C9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.1:bd08/15/2018:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn0P84C9:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15 7000 Gaming
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing 

[Kernel-packages] [Bug 1819023] [NEW] [nouveau] Scrolling screen flicker, especially on default Ubuntu lock screen

2019-04-02 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

My screen is experiencing a weird "scrolling" flicker, especially while
displaying blue, indigo, and violet hues/colors, such as on the default
Ubuntu 18.10 (x64 Desktop) lock screen. The screen flicker scrolls up
and down, with the brightest part of the flicker being towards the top,
with a gradient that fades back to the original color near the bottom.

Problem occurs on any one monitor on any one video output protocol
(DVI-D, HDMI, and VGA).


I will upload an illustration or render as soon as possible for better 
explanation.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
Uname: Linux 4.18.0-16-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar  7 10:39:50 2019
DistUpgraded: 2018-10-19 10:50:54,557 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: cosmic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GF108 [GeForce GT 440] [10de:0de0] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: NVIDIA Corporation GF108 [GeForce GT 440] [10de:0828]
InstallationDate: Installed on 2018-08-17 (202 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: BIOSTAR Group A880G+
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=a967adb1-1600-455b-8704-e2bf5de5081d ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to cosmic on 2018-10-19 (139 days ago)
dmi.bios.date: 09/21/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080016
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: A880G+
dmi.board.vendor: BIOSTAR Group
dmi.chassis.asset.tag: None
dmi.chassis.type: 3
dmi.chassis.vendor: BIOSTAR Group
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/21/2011:svnBIOSTARGroup:pnA880G+:pvr:rvnBIOSTARGroup:rnA880G+:rvr:cvnBIOSTARGroup:ct3:cvr:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: A880G+
dmi.product.sku: To Be Filled By O.E.M.
dmi.sys.vendor: BIOSTAR Group
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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


** Tags: amd64 apport-bug cosmic driver flicker gpu gradient graphic manager 
nouveau ubuntu window
-- 
[nouveau] Scrolling screen flicker, especially on default Ubuntu lock screen
https://bugs.launchpad.net/bugs/1819023
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 1772412] Re: zfs 0.7.9 fixes a bug (https://github.com/zfsonlinux/zfs/pull/7343) that hangs the system completely

2019-04-02 Thread Saurabh Nanda
I noticed that the status of this bug has been changed to `fix
released`. Where/how has the fix been released and how does one patch a
live Ubuntu 18.04.2 system to get this bugfix?

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

Title:
  zfs 0.7.9 fixes a bug (https://github.com/zfsonlinux/zfs/pull/7343)
  that hangs the system completely

Status in zfs-linux package in Ubuntu:
  Fix Released

Bug description:
  I have experienced the problems fixed by this commit
  https://github.com/zfsonlinux/zfs/pull/7343 a few times on my NAS. The
  system hangs completely when it occurs. It looks like 0.7.9 brings
  other interesting bug fixes that potentially freeze the system.

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

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


[Kernel-packages] [Bug 1791405] Re: bluetooth always in discoverable mode (security issue)

2019-04-02 Thread Daniel van Vugt
And the gnome-bluetooth fix was released in 3.28.2.

** Package changed: bluez (Ubuntu) => gnome-bluetooth (Ubuntu)

** Changed in: gnome-bluetooth (Ubuntu)
   Status: Fix Committed => Fix Released

** Also affects: gnome-bluetooth (Ubuntu Disco)
   Importance: Medium
   Status: Fix Released

** Also affects: gnome-bluetooth (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: gnome-bluetooth (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: gnome-bluetooth (Ubuntu Cosmic)
   Status: New => Fix Released

** Changed in: gnome-bluetooth (Ubuntu Cosmic)
   Importance: Undecided => Medium

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-10910

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

Title:
  bluetooth always in discoverable mode (security issue)

Status in bluez package in Ubuntu:
  New
Status in gnome-bluetooth package in Ubuntu:
  Fix Released
Status in bluez source package in Bionic:
  New
Status in gnome-bluetooth source package in Bionic:
  Fix Released
Status in bluez source package in Cosmic:
  New
Status in gnome-bluetooth source package in Cosmic:
  Fix Released
Status in bluez source package in Disco:
  New
Status in gnome-bluetooth source package in Disco:
  Fix Released
Status in bluez source package in EE-Series:
  Fix Committed
Status in gnome-bluetooth package in Fedora:
  Confirmed

Bug description:
  Excerpt from a similar report
  (https://bugzilla.redhat.com/show_bug.cgi?id=1602985) :

  Opening the Bluetooth settings will make the device discoverable
  again, but does not make the device undiscoverable after the settings
  are closed (this is not intended behavior; devices should only be
  discoverable when the bluetooth settings UI is open).

  There seem to be a merge request :

  https://gitlab.gnome.org/GNOME/gnome-bluetooth/merge_requests/1

  Could you please merge it asap, it should be treated as a security
  issue IMHO.

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

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


[Kernel-packages] [Bug 1791405] Re: bluetooth always in discoverable mode (security issue)

2019-04-02 Thread Daniel van Vugt
Although the gnome-bluetooth "fix" sounds like a workaround. So re-
adding a bluez task.

** Also affects: bluez (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gnome-bluetooth (Ubuntu Ee-series)
   Importance: Undecided
   Status: New

** Also affects: bluez (Ubuntu Ee-series)
   Importance: Undecided
   Status: New

** Changed in: bluez (Ubuntu Ee-series)
   Status: New => Fix Committed

** No longer affects: gnome-bluetooth (Ubuntu Ee-series)

** Changed in: gnome-bluetooth (Ubuntu Bionic)
   Importance: Undecided => Medium

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

Title:
  bluetooth always in discoverable mode (security issue)

Status in bluez package in Ubuntu:
  New
Status in gnome-bluetooth package in Ubuntu:
  Fix Released
Status in bluez source package in Bionic:
  New
Status in gnome-bluetooth source package in Bionic:
  Fix Released
Status in bluez source package in Cosmic:
  New
Status in gnome-bluetooth source package in Cosmic:
  Fix Released
Status in bluez source package in Disco:
  New
Status in gnome-bluetooth source package in Disco:
  Fix Released
Status in bluez source package in EE-Series:
  Fix Committed
Status in gnome-bluetooth package in Fedora:
  Confirmed

Bug description:
  Excerpt from a similar report
  (https://bugzilla.redhat.com/show_bug.cgi?id=1602985) :

  Opening the Bluetooth settings will make the device discoverable
  again, but does not make the device undiscoverable after the settings
  are closed (this is not intended behavior; devices should only be
  discoverable when the bluetooth settings UI is open).

  There seem to be a merge request :

  https://gitlab.gnome.org/GNOME/gnome-bluetooth/merge_requests/1

  Could you please merge it asap, it should be treated as a security
  issue IMHO.

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

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


[Kernel-packages] [Bug 1791405] Re: bluetooth always in discoverable mode (security issue)

2019-04-02 Thread Daniel van Vugt
Looks like the upstream fix is gnome-bluetooth, not bluez?

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

Title:
  bluetooth always in discoverable mode (security issue)

Status in bluez package in Ubuntu:
  New
Status in gnome-bluetooth package in Ubuntu:
  Fix Released
Status in bluez source package in Bionic:
  New
Status in gnome-bluetooth source package in Bionic:
  Fix Released
Status in bluez source package in Cosmic:
  New
Status in gnome-bluetooth source package in Cosmic:
  Fix Released
Status in bluez source package in Disco:
  New
Status in gnome-bluetooth source package in Disco:
  Fix Released
Status in bluez source package in EE-Series:
  Fix Committed
Status in gnome-bluetooth package in Fedora:
  Confirmed

Bug description:
  Excerpt from a similar report
  (https://bugzilla.redhat.com/show_bug.cgi?id=1602985) :

  Opening the Bluetooth settings will make the device discoverable
  again, but does not make the device undiscoverable after the settings
  are closed (this is not intended behavior; devices should only be
  discoverable when the bluetooth settings UI is open).

  There seem to be a merge request :

  https://gitlab.gnome.org/GNOME/gnome-bluetooth/merge_requests/1

  Could you please merge it asap, it should be treated as a security
  issue IMHO.

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

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


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

2019-04-02 Thread 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 1822913

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

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

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

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

** Tags added: disco

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

Title:
  Kernel 5.0.0-8 unable to handle kernel NULL pointer dereference at
  

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With Kernel 5.0.0-8 I have strange behaivour. I have no wifi and no sound, 
typing sudo doesn't work.
  kern.log attached, include a boot with kernel 5 and one with 4.19 (which 
works ok)

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

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


[Kernel-packages] [Bug 1822913] Re: Kernel 5.0.0-8 unable to handle kernel NULL pointer dereference at 0000000000000000

2019-04-02 Thread Hans P Möller
forgot to add info about the audio and wifi:
*-multimedia
 description: Audio device
 product: NM10/ICH7 Family High Definition Audio Controller
 vendor: Intel Corporation
 physical id: 1b
 bus info: pci@:00:1b.0
 version: 01
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list
 configuration: driver=snd_hda_intel latency=0
 resources: irq:25 memory:efebc000-efeb
*-network
description: Wireless interface
product: PRO/Wireless 3945ABG [Golan] Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@:0c:00.0
logical name: wlp12s0
version: 02
serial: 00:18:de:8a:64:ec
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet 
physical wireless
configuration: broadcast=yes driver=iwl3945 
driverversion=4.19.0-13-generic firmware=15.32.2.9 ip=192.168.0.18 latency=0 
link=yes multicast=yes wireless=IEEE 802.11
resources: irq:24 memory:efdff000-efdf

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

Title:
  Kernel 5.0.0-8 unable to handle kernel NULL pointer dereference at
  

Status in linux package in Ubuntu:
  New

Bug description:
  With Kernel 5.0.0-8 I have strange behaivour. I have no wifi and no sound, 
typing sudo doesn't work.
  kern.log attached, include a boot with kernel 5 and one with 4.19 (which 
works ok)

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

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


[Kernel-packages] [Bug 1822913] [NEW] Kernel 5.0.0-8 unable to handle kernel NULL pointer dereference at 0000000000000000

2019-04-02 Thread Hans P Möller
Public bug reported:

With Kernel 5.0.0-8 I have strange behaivour. I have no wifi and no sound, 
typing sudo doesn't work.
kern.log attached, include a boot with kernel 5 and one with 4.19 (which works 
ok)

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


** Tags: kernel kernel-bug

** Attachment added: "kern.log"
   https://bugs.launchpad.net/bugs/1822913/+attachment/5252319/+files/kern.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/1822913

Title:
  Kernel 5.0.0-8 unable to handle kernel NULL pointer dereference at
  

Status in linux package in Ubuntu:
  New

Bug description:
  With Kernel 5.0.0-8 I have strange behaivour. I have no wifi and no sound, 
typing sudo doesn't work.
  kern.log attached, include a boot with kernel 5 and one with 4.19 (which 
works ok)

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

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


[Kernel-packages] [Bug 1822797] Re: ZFS module is installed for wrong kernel on arm64-raspi3 systems (19.04 beta)

2019-04-02 Thread Steve Langasek
This is because the raspi2 kernel package does not Provides:  zfs-dkms,
zfs-modules, as expected for Ubuntu kernel packages which include ZFS
support.  So if you try to install the zfs-initramfs package, apt will
try to pull in something which satisfies the dependencies if nothing
else is already installed which does, and it doesn't know that the
kernel image it's pulling is not an appropriate provider of zfs for the
running system.

If there is a bug here, it's that the Ubuntu zfs sauce patches are not
enabled on the raspi2 arm64 kernel build.

However, given the memory limitations of the raspi3 family of devices,
I'm not sure it's at all advisable to try to run zfs on such a system.

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

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

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

Title:
  ZFS module is installed for wrong kernel on arm64-raspi3 systems
  (19.04 beta)

Status in linux-raspi2 package in Ubuntu:
  Triaged

Bug description:
  Platform: Raspberry Pi 3 running ubuntu-19.04-beta-preinstalled-
  server-arm64+raspi3.img

  Kernel: Default (Linux ubuntu 4.18.0-1010-raspi2 #12-Ubuntu SMP
  PREEMPT Tue Feb 12 12:17:11 UTC 2019 aarch64 aarch64 aarch64
  GNU/Linux)

  Problem: The ZFS module is installed for a kernel that can not be
  used.

  apt-get install zfs-initramfs 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following additional packages will be installed:
libnvpair1linux libuutil1linux libzfs2linux libzpool2linux
linux-image-unsigned-5.0.0-8-snapdragon
linux-modules-5.0.0-8-snapdragon zfs-zed zfsutils-linux
  Suggested packages:
fdutils linux-doc-5.0.0 | linux-source-5.0.0 linux-tools
linux-headers-5.0.0-8-snapdragon nfs-kernel-server
samba-common-bin
  The following NEW packages will be installed:
libnvpair1linux libuutil1linux libzfs2linux libzpool2linux
linux-image-unsigned-5.0.0-8-snapdragon
linux-modules-5.0.0-8-snapdragon zfs-initramfs zfs-zed
zfsutils-linux
  0 upgraded, 9 newly installed, 0 to remove and 0 not upgraded.
  Need to get 55.7 MB of archives.
  After this operation, 305 MB of additional disk space will be used.
  Do you want to continue? [Y/n] Y
  Get:1 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 
linux-modules-5.0.0-8-snapdragon arm64 5.0.0-8.9 [47.5 MB]
  Get:2 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 
linux-image-unsigned-5.0.0-8-snapdragon arm64 5.0.0-8.9 [7169 kB]
  Get:3 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 libnvpair1linux 
arm64 0.7.12-1ubuntu5 [42.8 kB]
  Get:4 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 libuutil1linux 
arm64 0.7.12-1ubuntu5 [50.7 kB]
  Get:5 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 libzpool2linux 
arm64 0.7.12-1ubuntu5 [498 kB]
  Get:6 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 libzfs2linux 
arm64 0.7.12-1ubuntu5 [121 kB]
  Get:7 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 zfsutils-linux 
arm64 0.7.12-1ubuntu5 [267 kB]
  Get:8 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 zfs-initramfs 
arm64 0.7.12-1ubuntu5 [22.2 kB]
  Get:9 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 zfs-zed arm64 
0.7.12-1ubuntu5 [57.5 kB]
  Fetched 55.7 MB in 37s (1486 kB/s)   
  Selecting previously unselected package linux-modules-5.0.0-8-snapdragon.
  (Reading database ... 61671 files and directories currently installed.)
  Preparing to unpack 
.../0-linux-modules-5.0.0-8-snapdragon_5.0.0-8.9_arm64.deb ...
  Unpacking linux-modules-5.0.0-8-snapdragon (5.0.0-8.9) ...
  Selecting previously unselected package 
linux-image-unsigned-5.0.0-8-snapdragon.
  Preparing to unpack 
.../1-linux-image-unsigned-5.0.0-8-snapdragon_5.0.0-8.9_arm64.deb ...
  Unpacking linux-image-unsigned-5.0.0-8-snapdragon (5.0.0-8.9) ...
  Selecting previously unselected package libnvpair1linux.
  Preparing to unpack .../2-libnvpair1linux_0.7.12-1ubuntu5_arm64.deb ...
  Unpacking libnvpair1linux (0.7.12-1ubuntu5) ...
  Selecting previously unselected package libuutil1linux.
  Preparing to unpack .../3-libuutil1linux_0.7.12-1ubuntu5_arm64.deb ...
  Unpacking libuutil1linux (0.7.12-1ubuntu5) ...
  Selecting previously unselected package libzpool2linux.
  Preparing to unpack .../4-libzpool2linux_0.7.12-1ubuntu5_arm64.deb ...
  Unpacking libzpool2linux (0.7.12-1ubuntu5) ...
  Selecting previously unselected package libzfs2linux.
  Preparing to unpack .../5-libzfs2linux_0.7.12-1ubuntu5_arm64.deb ...
  Unpacking libzfs2linux (0.7.12-1ubuntu5) ...
  Selecting previously unselected package zfsutils-linux.
  Preparing to unpack .../6-zfsutils-linux_0.7.12-1ubuntu5_arm64.deb ...
  Unpacking zfsutils-linux (0.7.12-1ubuntu5) ...
  Selecting previously unselected package zfs-initramfs.
  

[Kernel-packages] [Bug 1822363] Re: Booting hangs when USB 3.0 Etron EJ168 PCI card is detected

2019-04-02 Thread Mike
I was temporary installed Ubuntu 15.10 amd64 as base to test kernels,
becouse it was working with card. After long retries I have discovered
that v4.9 (https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9/) is
working, but 4.10 (https://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.10/) stops at this 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/1822363

Title:
  Booting hangs when USB 3.0 Etron EJ168 PCI card is detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have installed Etron EJ168 PCI USB 3.0 [1B6F:7023] which briliantly works 
in any Windows OS (I use multiboot PC) on my Conroe865PE AGP/PCI Intel 
Kentsfield QX6800 system with classic BIOS (non UEFI).
  There are no devices connected to PCI USB card during boot.

  The desktop Ubuntu 18.04 kernel 4.15.0-46-generic freezes with this
  card during boot (see attached "photo log" with boot and grub
  options). I can't access/login Ubuntu or console. It was checked and
  confirmed on ubuntu-18.04.1-desktop-amd64.iso LIVE CD desktop (with
  acpi=off option too).

  Previously I was used and removed USB 3.0 NEC Renesas upd720200 PCI card 
[1033:0194], which was partially workable under my installation of Ubuntu 18.04 
and Windows. It had problems from time to time with FW load from card on start 
and not detecting USB devices connected even if FW present.
  I tried and also removed USB 3.0 NEC Renesas upd720202 PCI card [1912:0015] 
which also was partially workable in the same way (other card bios and newer 
NEC chip). System was fully bootable with NEC cards.

  The Etron EJ168 works superb on Windows OS's with directly or with hub 
connections with USB devices.
  I can assist in any way to solve this bug as IT Professional.

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

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


[Kernel-packages] [Bug 1822797] [NEW] ZFS module is installed for wrong kernel on arm64-raspi3 systems (19.04 beta)

2019-04-02 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Platform: Raspberry Pi 3 running ubuntu-19.04-beta-preinstalled-server-
arm64+raspi3.img

Kernel: Default (Linux ubuntu 4.18.0-1010-raspi2 #12-Ubuntu SMP PREEMPT
Tue Feb 12 12:17:11 UTC 2019 aarch64 aarch64 aarch64 GNU/Linux)

Problem: The ZFS module is installed for a kernel that can not be used.

apt-get install zfs-initramfs 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  libnvpair1linux libuutil1linux libzfs2linux libzpool2linux
  linux-image-unsigned-5.0.0-8-snapdragon
  linux-modules-5.0.0-8-snapdragon zfs-zed zfsutils-linux
Suggested packages:
  fdutils linux-doc-5.0.0 | linux-source-5.0.0 linux-tools
  linux-headers-5.0.0-8-snapdragon nfs-kernel-server
  samba-common-bin
The following NEW packages will be installed:
  libnvpair1linux libuutil1linux libzfs2linux libzpool2linux
  linux-image-unsigned-5.0.0-8-snapdragon
  linux-modules-5.0.0-8-snapdragon zfs-initramfs zfs-zed
  zfsutils-linux
0 upgraded, 9 newly installed, 0 to remove and 0 not upgraded.
Need to get 55.7 MB of archives.
After this operation, 305 MB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 
linux-modules-5.0.0-8-snapdragon arm64 5.0.0-8.9 [47.5 MB]
Get:2 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 
linux-image-unsigned-5.0.0-8-snapdragon arm64 5.0.0-8.9 [7169 kB]
Get:3 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 libnvpair1linux 
arm64 0.7.12-1ubuntu5 [42.8 kB]
Get:4 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 libuutil1linux 
arm64 0.7.12-1ubuntu5 [50.7 kB]
Get:5 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 libzpool2linux 
arm64 0.7.12-1ubuntu5 [498 kB]
Get:6 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 libzfs2linux arm64 
0.7.12-1ubuntu5 [121 kB]
Get:7 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 zfsutils-linux 
arm64 0.7.12-1ubuntu5 [267 kB]
Get:8 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 zfs-initramfs arm64 
0.7.12-1ubuntu5 [22.2 kB]
Get:9 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 zfs-zed arm64 
0.7.12-1ubuntu5 [57.5 kB]
Fetched 55.7 MB in 37s (1486 kB/s)   
Selecting previously unselected package linux-modules-5.0.0-8-snapdragon.
(Reading database ... 61671 files and directories currently installed.)
Preparing to unpack .../0-linux-modules-5.0.0-8-snapdragon_5.0.0-8.9_arm64.deb 
...
Unpacking linux-modules-5.0.0-8-snapdragon (5.0.0-8.9) ...
Selecting previously unselected package linux-image-unsigned-5.0.0-8-snapdragon.
Preparing to unpack 
.../1-linux-image-unsigned-5.0.0-8-snapdragon_5.0.0-8.9_arm64.deb ...
Unpacking linux-image-unsigned-5.0.0-8-snapdragon (5.0.0-8.9) ...
Selecting previously unselected package libnvpair1linux.
Preparing to unpack .../2-libnvpair1linux_0.7.12-1ubuntu5_arm64.deb ...
Unpacking libnvpair1linux (0.7.12-1ubuntu5) ...
Selecting previously unselected package libuutil1linux.
Preparing to unpack .../3-libuutil1linux_0.7.12-1ubuntu5_arm64.deb ...
Unpacking libuutil1linux (0.7.12-1ubuntu5) ...
Selecting previously unselected package libzpool2linux.
Preparing to unpack .../4-libzpool2linux_0.7.12-1ubuntu5_arm64.deb ...
Unpacking libzpool2linux (0.7.12-1ubuntu5) ...
Selecting previously unselected package libzfs2linux.
Preparing to unpack .../5-libzfs2linux_0.7.12-1ubuntu5_arm64.deb ...
Unpacking libzfs2linux (0.7.12-1ubuntu5) ...
Selecting previously unselected package zfsutils-linux.
Preparing to unpack .../6-zfsutils-linux_0.7.12-1ubuntu5_arm64.deb ...
Unpacking zfsutils-linux (0.7.12-1ubuntu5) ...
Selecting previously unselected package zfs-initramfs.
Preparing to unpack .../7-zfs-initramfs_0.7.12-1ubuntu5_arm64.deb ...
Unpacking zfs-initramfs (0.7.12-1ubuntu5) ...
Selecting previously unselected package zfs-zed.
Preparing to unpack .../8-zfs-zed_0.7.12-1ubuntu5_arm64.deb ...
Unpacking zfs-zed (0.7.12-1ubuntu5) ...
Setting up libuutil1linux (0.7.12-1ubuntu5) ...
Setting up linux-modules-5.0.0-8-snapdragon (5.0.0-8.9) ...
Setting up linux-image-unsigned-5.0.0-8-snapdragon (5.0.0-8.9) ...
I: /boot/vmlinuz is now a symlink to vmlinuz-5.0.0-8-snapdragon
I: /boot/initrd.img is now a symlink to initrd.img-5.0.0-8-snapdragon
Setting up libnvpair1linux (0.7.12-1ubuntu5) ...
Setting up libzpool2linux (0.7.12-1ubuntu5) ...
Setting up libzfs2linux (0.7.12-1ubuntu5) ...
Setting up zfsutils-linux (0.7.12-1ubuntu5) ...
Created symlink 
/etc/systemd/system/zfs-import.target.wants/zfs-import-cache.service → 
/lib/systemd/system/zfs-import-cache.service.
Created symlink /etc/systemd/system/zfs-mount.service.wants/zfs-import.target → 
/lib/systemd/system/zfs-import.target.
Created symlink /etc/systemd/system/zfs.target.wants/zfs-import.target → 
/lib/systemd/system/zfs-import.target.
Created symlink 
/etc/systemd/system/zfs-mount.service.wants/zfs-load-module.service → 

[Kernel-packages] [Bug 1796130] Re: Patches for Additional NVME Support

2019-04-02 Thread Michael Reed
** Changed in: dell-poweredge
   Status: New => Triaged

** Changed in: dell-poweredge
   Importance: Undecided => 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/1796130

Title:
  Patches for  Additional NVME Support

Status in The Dell-poweredge project:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged
Status in linux source package in Cosmic:
  Triaged

Bug description:
  Dell is requesting these patches for inclusion into 18.04.2 for
  additional NVME support

  PCI: Check for PCIe Link downtraining
  
https://github.com/torvalds/linux/commit/2d1ce5ec2117d16047334a1aa4b62e0cfb5a0605

  
  PCI/AER: Add sysfs attributes to provide AER stats and breakdown
  https://github.com/torvalds/linux/commit/81aa5206f9a7

  
  PCI/AER: Honor "pcie_ports=native" even if HEST sets FIRMWARE_FIRST
  https://github.com/torvalds/linux/commit/7af02fcd84c1

  
  PCI/AER: Don't clear AER bits if error handling is Firmware-First
  https://github.com/torvalds/linux/commit/45687f96c112

  
  PCI: pciehp: Differentiate between surprise and safe removal
  
https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git/commit/?h=pci/hotplug=e76ac5875f5d5848558edc79a0869bf20765fec3

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-poweredge/+bug/1796130/+subscriptions

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


[Kernel-packages] [Bug 1328727] Re: [Asus 1000HE] s2disk/hibernate hangs during saving of image data

2019-04-02 Thread Matheus
Exact same problem:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819915 even on
kernel 5!

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

Title:
  [Asus 1000HE] s2disk/hibernate hangs during saving of image data

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hibernation with the pm-hibernate command works fine on a freshly
  booted system, but when a significant portion of the RAM is in use,
  for instance by starting gimp, google-chrome and firefox at the same
  time, it stalls at the start of the saving of the image data:

  s2disk: Snapshotting system
  s2disk: System snapshot ready. Preparing to write
  s2disk: Image size: 441652 kilobytes
  s2disk: Free swap: 1798624 kilobytes
  s2disk: Saving 110413 image data pages (press backspace to abort) ...   0%

  The system is not usable at this point, although alt-sysrq still
  works. It looks like some sort of deadlock.

  The system is an Asus eeePC 1000HE with 2GB RAM and a 2GB swap
  partition and a Samsung SSD 840 EVO. The Ubuntu release is 14.04
  LTS. The kernel package is linux-image-3.13.0-27-generic version
  3.13.0-27.50 (32 bit).

  I found a kernel bug report that looks exactly the same:

  https://bugzilla.kernel.org/show_bug.cgi?id=75101

  In that bug report, the problem was bisected to commit a1c3bfb2.
  This commit is part of the 3.14 kernel, but was apparently backported
  to the 3.13 Ubuntu kernel. I've rebuild the kernel package with this
  commit reverted, and it seems to fix this issue for me.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dick   1719 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=c6b78f80-b4a1-4b1a-91b4-8ae5c41b36f4
  InstallationDate: Installed on 2013-04-28 (408 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  MachineType: ASUSTeK Computer INC. 1000HE
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic 
root=UUID=54684f57-2a33-403f-ae4d-ad6b3d0168ea ro acpi_osi=Linux 
acpi_backlight=vendor quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-27.50hib-generic 3.13.11
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-27-generic N/A
   linux-backports-modules-3.13.0-27-generic  N/A
   linux-firmware 1.127.2
  Tags:  trusty
  Uname: Linux 3.13.0-27-generic i686
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (45 days ago)
  UserGroups: adm cdrom dialout dip fuse lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/24/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0902
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1000HE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTek Computer INC.
  dmi.chassis.version: x.x
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0902:bd06/24/2009:svnASUSTeKComputerINC.:pn1000HE:pvrx.x:rvnASUSTeKComputerINC.:rn1000HE:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1000HE
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK Computer INC.

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

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


[Kernel-packages] [Bug 1821823] Re: No wireless networks displayed for broadcom BCM43142

2019-04-02 Thread Brian Murray
Could you add the ubiquity log file to the bug report or try and the
beta iso image and then include the ubiquity log file?

** Changed in: ubiquity (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/1821823

Title:
  No wireless networks displayed for broadcom BCM43142

Status in linux package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Incomplete

Bug description:
  For 19.04 UB did a minimal install.  I selected the ubiquity
  proprietary option and expected the broadcom driver to be found and
  installed.

  On reboot I could not see any wireless networks.  I went to the
  Additional Drivers window and it stated that the computer was indeed
  using Broadcom 802.11 Linux STA wireless driver and was in use.

  This is a regression - in both 18.04 and 18.10, the same steps also
  installed the driver, and wireless networks were found and could be
  connected to.

  ProblemType: BugDistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-7-generic 5.0.0-7.8
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dad1060 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Wed Mar 27 00:25:09 2019
  InstallationDate: Installed on 2019-03-27 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 
(20190326.1)
  IwConfig:
   lono wireless extensions.

   enp3s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd 
(Foxlink)
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=25581458-0e76-468f-8318-628c1a279716 ro nomodeset quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-7-generic N/A
   linux-backports-modules-5.0.0-7-generic  N/A
   linux-firmware   1.178
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: noSourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:

  dmi.bios.date: 02/15/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80BF
  dmi.board.vendor: HP
  dmi.board.version: 95.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: N9S73EA#ABU
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1822897] [NEW] RDMA/hns updates for disco

2019-04-02 Thread dann frazier
Public bug reported:

[Impact]
A number of changes for the RDMA/hns driver landed upstream post-5.0, including 
a number of bug fixes, corrections for consistency w/ the hip08 SoC spec, as 
well as a couple new features and cleanup. I recommend we sync up the changes 
for disco so that we have an established base for future changes.

[Test Case]
Regression tested w/ perftest:

= server =
sudo ib_send_bw -d hns_2 -i 1 -a -F --report_gbits
= client =
sudo ib_send_bw -d hns_2 -i 1 -a -F --report_gbits 

[Fixes]
9c6ccc035c209dda07685e8dba829a203ba17499 RDMA/hns: Fix the bug with updating rq 
head pointer when flush cqe
4d103905eb1e4f14cb62fcf962c9d35da7005dea RDMA/hns: Bugfix for the scene without 
receiver queue
44754b95dd35ee07c462b5425ae9c4cde8c7e7c8 RDMA/hns: Add constraint on the 
setting of local ACK timeout
91fb4d83b88a7b544ce564c44167aad29d4154f0 RDMA/hns: Modify the pbl ba page size 
for hip08
de77503a59403e7045c18c6bb0a10c245a99b648 RDMA/hns: RDMA/hns: Assign rq head 
pointer when enable rq record db
2b9acb9a97fe9b4101ca020643760c4a090b4cb4 RDMA/hns: Add the process of AEQ 
overflow for hip08
6a157f7d1b14eb88d89fbd396cfea15ac4bded2d RDMA/hns: Add SCC context allocation 
support for hip08
aa84fa18741b83daf0f8f160c46ae92f4d6f1343 RDMA/hns: Add SCC context clr support 
for hip08
0e40dc2f70cda099e13392a26bd37aed24bcd25d RDMA/hns: Add timer allocation support 
for hip08
da91ddfdc7212e6e716be55a5cf2305ce84a422f RDMA/hns: Remove set but not used 
variable 'rst'
c3c668e742397dfc107e44c09606cc68b37df30d RDMA/hns: Make some function static
d061effc36f7bd38a12912977a37a50ac9140d11 RDMA/hns: Fix the Oops during rmmod or 
insmod ko when reset occurs
6a04aed6afaefd5fd396f23da184298135f31e37 RDMA/hns: Fix the chip hanging caused 
by sending mailbox during reset
d3743fa94ccd177917783726faf54632439ddb54 RDMA/hns: Fix the chip hanging caused 
by sending doorbell during reset
3856ec55270099494afa0cabba020365a38430a2 RDMA/hns: Use for_each_sg_dma_page 
iterator on umem SGL
704e0e613a6d584fde1c80ead0329e918b4f8671 RDMA/hns: Limit minimum ROCE CQ depth 
to 64
ab22bf05216a6bb4812448f3a8609489047cf311 RDMA/hns: Fix the state of rereg mr
f7f27a5f03cc9f47cc14f75a5be25f0f26b1b5ff RDMA/hns: Set allocated memory to zero 
for wrid
e95c716c7faa0d0eede5eabb6fea2504709e25b6 RDMA/hns: Delete useful prints for aeq 
subtype event
dad1f9802ecee3a21143293b2505e1b57b1ae525 RDMA/hns: Configure capacity of hns 
device
3e394f9413ecba2779b6a1d77095f4d8611a52d2 RDMA/hns: Modify qp 
specification according to UM
6ac16e403900a98f9b330daa5f0d89f76a24c6eb RDMA/hns: Bugfix for set hem of SCC
4e69cf1fe2c52d189acdd06c1fd99cc258aba61f RDMA/hns: Use GFP_ATOMIC in 
hns_roce_v2_modify_qp

[Regression Risk]
Driver is only for HNS nics on HiSilicon SoCs

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: In Progress

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => dann frazier (dannf)

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

Title:
  RDMA/hns updates for disco

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  A number of changes for the RDMA/hns driver landed upstream post-5.0, 
including a number of bug fixes, corrections for consistency w/ the hip08 SoC 
spec, as well as a couple new features and cleanup. I recommend we sync up the 
changes for disco so that we have an established base for future changes.

  [Test Case]
  Regression tested w/ perftest:

  = server =
  sudo ib_send_bw -d hns_2 -i 1 -a -F --report_gbits
  = client =
  sudo ib_send_bw -d hns_2 -i 1 -a -F --report_gbits 

  [Fixes]
  9c6ccc035c209dda07685e8dba829a203ba17499 RDMA/hns: Fix the bug with updating 
rq head pointer when flush cqe
  4d103905eb1e4f14cb62fcf962c9d35da7005dea RDMA/hns: Bugfix for the scene 
without receiver queue
  44754b95dd35ee07c462b5425ae9c4cde8c7e7c8 RDMA/hns: Add constraint on the 
setting of local ACK timeout
  91fb4d83b88a7b544ce564c44167aad29d4154f0 RDMA/hns: Modify the pbl ba page 
size for hip08
  de77503a59403e7045c18c6bb0a10c245a99b648 RDMA/hns: RDMA/hns: Assign rq head 
pointer when enable rq record db
  2b9acb9a97fe9b4101ca020643760c4a090b4cb4 RDMA/hns: Add the process of AEQ 
overflow for hip08
  6a157f7d1b14eb88d89fbd396cfea15ac4bded2d RDMA/hns: Add SCC context allocation 
support for hip08
  aa84fa18741b83daf0f8f160c46ae92f4d6f1343 RDMA/hns: Add SCC context clr 
support for hip08
  0e40dc2f70cda099e13392a26bd37aed24bcd25d RDMA/hns: Add timer allocation 
support for hip08
  da91ddfdc7212e6e716be55a5cf2305ce84a422f RDMA/hns: Remove set but not used 
variable 'rst'
  c3c668e742397dfc107e44c09606cc68b37df30d RDMA/hns: Make some function static
  d061effc36f7bd38a12912977a37a50ac9140d11 RDMA/hns: Fix the Oops during rmmod 
or insmod ko when reset occurs
  

[Kernel-packages] [Bug 1822682] Re: nvidia driver issues

2019-04-02 Thread Frank
Sometimes after reboot system freezing and i can do nothing excepting 
hard-reboot.
Same issue on Manjaro Linux after nvidia drivers installing:
Kernel 4.20.17-1
from logs:
[TTM] Buffer eviction failed
nouveau :01:00.0: DRM: failed to idle channel 0 [DRM]

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

Title:
  nvidia driver issues

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-signed-hwe package in Ubuntu:
  New
Status in linux-firmware source package in Bionic:
  New
Status in linux-signed-hwe source package in Bionic:
  New
Status in linux-firmware source package in Cosmic:
  New
Status in linux-signed-hwe source package in Cosmic:
  New

Bug description:
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Kernel: Linux 4.18.0-15-generic
  Intel Core i7-7700HQ + GeForce 1050Ti
  after: sudo update-initramfs -u (i'm using this command after installing 
fresh Ubuntu because it can't reboot correctly)
  I get :
  update-initramfs: Generating /boot/initrd.img-4.18.0-16-generic
  W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/sig.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/image.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/desc.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/nvdec/scrubber.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_method_init.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_bundle_init.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_nonctx.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_ctx.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_sig.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_data.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_inst.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_bl.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_sig.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_data.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_inst.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_bl.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_unload.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_load.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/unload_bl.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/bl.bin for module 
nouveau

  Had no such trouble on Ubuntu 18.04.01 with older kernel

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.18.0-15-generic 4.18.0-15.16~18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  2 00:18:33 2019
  InstallationDate: Installed on 2019-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1821936] Re: No sound output on Zen AIO 27 Z272SD_Z272SD

2019-04-02 Thread Derek Gordon
Command ran to add it again and run dmesg so it shows.  That does not
help.  See attached dmesg.

** Attachment added: "dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821936/+attachment/5252245/+files/dmesg

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

Title:
  No sound output on Zen AIO 27 Z272SD_Z272SD

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I find this to be an issue with current LTS 18.04's latest 4.19
  kernel.  I tested this on mainline 4.20 and 5.0 kernels as well.

  No audio because ALC274 not properly loaded for use, so no audio
  output.  A related card had a similar bug, which was fixed, and may be
  of use in resolving this one:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485

  
  # cat /proc/asound/card0/codec* | grep Codec
  Codec: Realtek ALC274
  Codec: Intel Kabylake HDMI

  # cat /proc/asound/card0/pcm0c/info
  card: 0
  device: 0
  subdevice: 0
  stream: CAPTURE
  id: ALC274 Analog
  name: ALC274 Analog
  subname: subdevice #0
  class: 0
  subclass: 0
  subdevices_count: 1
  subdevices_avail: 0

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 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

  d# hwinfo --sound
  21: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.WnojYJLVCm0
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0xa348 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x31d0 
Revision: 0x10
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable)
Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable)
IRQ: 145 (663 events)
Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1903 F pulseaudio
derek  2464 F pulseaudio
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-23 (5 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  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-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.18.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/26/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Z272SD.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: Z272SD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 13
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0:
  dmi.product.family: Zen AIO
  dmi.product.name: Zen AIO 27 Z272SD_Z272SD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  --- 
  ProblemType: Bug
  ApportVersion: 

[Kernel-packages] [Bug 1820868] Re: bionic: fork out linux-snapdragon into its own topic kernel

2019-04-02 Thread Seth Forshee
** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

** Changed in: linux-snapdragon (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/1820868

Title:
  bionic: fork out linux-snapdragon into its own topic kernel

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-meta package in Ubuntu:
  Fix Committed
Status in linux-snapdragon package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  New
Status in linux-meta source package in Bionic:
  New
Status in linux-snapdragon source package in Bionic:
  In Progress

Bug description:
  Impact:

  During the Bionic cycle, a decision was made to incorporate the 
linux-snapdragon
  kernel into the master branch, thus reducing the number of topic kernels and 
the
  stable maintenance burden.

  But as time passed and new patches were produced by Qualcomm, incorporating 
them
  into master while avoiding to destabilize generic became more and more
  problematic, down to the point where it was not a viable approach
  anymore.

  At that point, the decision was made to fork out linux-snapdragon into its own
  topic kernel (e.g. linux-raspi2), giving more room to incorporate new code
  coming from the Qualcomm tree and avoiding to destabilize any other target in
  generic.

  Fix:

  This is a three step process:

  1) disable building linux-snapdragon from master by applying the attached 
patch
  to bionic/master

  2) create a new bionic/linux-snapdragon branch and reset hard to my
  lp:snapdragon-topic-kernel branch  (see below)

  3) update bionic-meta to point to the new bionic/linux-snapdragon
  kernel

  Regression potential

  From the point of view of bionic/master, this pull request doesn't introduce 
any
  substantial change, and in the future will let us purge generic from several
  external patches.

  While from the point of view of linux-snapdragon, with ~600 code commits and 
~4k
  config changes, this represent a brand new kernel and while great care was 
used
  while putting together this branch, there's clearly a regression potential 
here
  but we can't leave linux-snapdragon stagnate behind the curve, so the sooner 
we
  bite the bullet, the better we can the deal with the eventual fallout.

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

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


[Kernel-packages] [Bug 1787775] Re: touchpad not working on lenovo yoga 530

2019-04-02 Thread Seth Forshee
** Changed in: linux (Ubuntu Disco)
   Status: Confirmed => Fix Committed

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

Title:
  touchpad not working on lenovo yoga 530

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  New
Status in linux source package in Disco:
  Fix Committed

Bug description:
  === SRU Justification ===

  [Impact]
  AMD MP2 I2C driver doesn't support more than one bus.
  This makes touchpad on Lenovo Yoga 530 doensn't work as expected.

  [Fix]
  Sync the MP2 driver with upstream version.

  [Test]
  The new upstream driver doesn't break on Latitude 5495.
  Users haven't given any feedback yet, but since Disco is freezing I
  am sending this out.

  [Regression Potential]
  Low. It's from upstream, and only a subset of Raven Ridge has this
  device.

  === Original Bug Report ===

  The touchpad is not working and does not show up in cat
  /proc/bus/input/devices on multiple kernels. I've tried the newest
  kernel to date (19.08.18) and a few others.

  The touchpad works on windows.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-08-18 (0 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  Package: linux (not installed)
  Tags:  bionic
  Uname: Linux 4.18.3-041803-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to bionic on 2018-08-18 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Kernel-packages] [Bug 1822692] Re: Please ship the ib_uverbs driver module in the main modules package

2019-04-02 Thread Seth Forshee
** Changed in: linux-aws (Ubuntu Disco)
   Status: In Progress => Fix Committed

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

Title:
  Please ship the ib_uverbs driver module in the main modules package

Status in linux-aws package in Ubuntu:
  Fix Committed
Status in linux-aws source package in Xenial:
  In Progress
Status in linux-aws source package in Bionic:
  In Progress
Status in linux-aws source package in Cosmic:
  In Progress
Status in linux-aws source package in Disco:
  Fix Committed

Bug description:
  Please include the module drivers/infiniband/core/ib_uverbs.ko and its
  companion ib_umad.ko in the main linux-modules-*-aws package, in order
  to support upcoming Amazon features.

  +++ b/debian.aws/control.d/aws.inclusion-list

  +drivers/infiniband/core/ib_umad.ko
  +drivers/infiniband/core/ib_uverbs.ko

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

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


[Kernel-packages] [Bug 1822882] Re: linux-lts-trusty: -proposed tracker

2019-04-02 Thread 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 --
  kernel-stable-master-bug: 1822883
+ phase: Holding before Packaging
+ phase-changed: Tuesday, 02. April 2019 21:05 UTC
+ reason:
+   prepare-package: Stalled -- waiting for master bug

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

Title:
  linux-lts-trusty:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
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:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New

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

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

  -- swm properties --
  kernel-stable-master-bug: 1822883
  phase: Holding before Packaging
  phase-changed: Tuesday, 02. April 2019 21:05 UTC
  reason:
prepare-package: Stalled -- waiting for master bug

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

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


[Kernel-packages] [Bug 1822883] Re: linux: -proposed tracker

2019-04-02 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Confirmed

** 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
  
  backports: bug 1822882 (precise/linux-lts-trusty)
  
  -- swm properties --
+ phase: Ready for Packaging
+ phase-changed: Tuesday, 02. April 2019 21:05 UTC
+ reason:
+   prepare-package: Pending -- version not specified

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  New

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

  backports: bug 1822882 (precise/linux-lts-trusty)

  -- swm properties --
  phase: Ready for Packaging
  phase-changed: Tuesday, 02. April 2019 21:05 UTC
  reason:
prepare-package: Pending -- version not specified

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

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


[Kernel-packages] [Bug 1822633] Re: Pairing failure with BLE 4.0

2019-04-02 Thread Jason Gerecke
I've recently found that while pairing with this pen does not work,
"merely" connecting to the pen does work. That is:

# This command fails
$ echo -e "scan on\npair \nscan off" | bluetoothctl

# But this command works
$ echo -e "scan on\nconnect \nscan off" | bluetoothctl

Looking through the hcidump logs, it appears that "connect" has lower
(really, "no") security requirements, which could explain why it
succeeds where pairing fails (the AuthReq = 00 sent from the device
implies it doesn't want/support security).

I see that GNOME ships /usr/share/gnome-bluetooth/pin-code-database.xml
which defines default PINs. Inside the file, it says "the special NULL
pin means that the devices will not be paired, but connected to and
marked as trusted. This is for devices such as mice and joypads where
there is no encryption." If I add the pen to the database by adding the
following lines at the top of the "device" section, GNOME pairing starts
working (although it seems to be a little hit-or-miss):







With the connection fix in place, a new issue has been identified.
Specifically, the kernel input device is removed after processing just a
single Bluetooth HID event. Looking at the output of "journalctl -b0", I
see the following error message logged, followed by normal device
disconnect messages:

bluetoothd[6318]: Error Reading PNP_ID value: Request attribute has
encountered an unlikely error

Looking at the hcidump logs, it seems that when the pen's Bluetooth
button is pressed, it briefly wakes up only long enough to send a HID
report to the system. After doing so, it disconnects to save power. The
logs show that the system begins requesting information from the device
when it connects, and that it gets a response to some of those requests,
but at some point (e.g. when asking for PNP_ID) the device goes to sleep
and a response is never returned.

It would seem that there either the system needs to not re-ask the
device for information like PNP-ID (which it already received in the
initial "connect" process and should have associated with its MAC) or to
not be so stringent when these requests fail.

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

Title:
  Pairing failure with BLE 4.0

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

Bug description:
  When attempting to pair a BLE 4.0 pen using Bluez, we receive
  authentication errors.

  Here is the FW from Jason.

  Details:

  ===

  I added a few debug statements (patch attached) to the kernel's
  net/bluetooth/smp.c:smp_sig_channel() function
  (https://github.com/torvalds/linux/blob/v5.0/net/bluetooth/smp.c#L2883).
  When I try to pair the PN579X, I get the following logs:

  [ 5653.563048] DBG: Received code 2 (allowed = 0024) with 6 bytes
  [ 5653.563053] DBG: Processing code...
  [ 5653.709572] DBG: Received code 3 (allowed = 0028) with 16 bytes
  [ 5653.709577] DBG: Processing code...
  [ 5653.807085] DBG: Received code 4 (allowed = 0030) with 16 bytes
  [ 5653.807089] DBG: Processing code...
  [ 5654.148553] DBG: Received code 6 (allowed = 0060) with 16 bytes
  [ 5654.148557] DBG: Processing code...
  [ 5654.197024] DBG: Received code 7 (allowed = 00a0) with 10 bytes
  [ 5654.197027] DBG: Processing code...
  [ 5654.245824] DBG: Received code 8 (allowed = 0120) with 16 bytes
  [ 5654.245828] DBG: Processing code...
  [ 5654.246178] DBG: Received code 9 (allowed = 0220) with 7 bytes
  [ 5654.246182] DBG: Processing code...
  [ 5657.610656] input: Dell Active Pen PN579X Keyboard as 
/devices/virtual/misc/uhid/0005:413C:81D5.0004/input/input23
  [ 5657.610997] hid-generic 0005:413C:81D5.0004: input,hidraw0: BLUETOOTH HID 
vf.08 Keyboard [Dell Active Pen PN579X] on 18:56:80:18:6A:E5

  When I try to pair the PN557W, however, I only get the following:

  [   64.924901] DBG: Received code 11 (allowed = 0024) with 1 bytes
  [   64.924906] DBG: AuthReq = 00
  [   64.924907] ERR: Code not allowed on existing connection
  [   64.924943] Bluetooth: hci0: unexpected SMP command 0x0b from 
bc:82:5d:fa:5e:b7
  [   64.940314] NET: Registered protocol family 38
  [   65.022326] DBG: Received code 5 (allowed = 0024) with 1 bytes
  [   65.022331] DBG: Processing code...

  The "allowed" value is a bitmap, so 0024 means that only event
  code 2 and 5 are allowed. The "smp_sig_channel()" function does allow
  code 11 ("SMP_CMD_SECURITY_REQ") to be sent from the device at the
  beginning of the connection but *only* if the "smp" variable hasn't
  been set yet. It looks like the host starts the pairing process and
  initializes the "smp" variable, which then prevents code 11 from being
  allowed.

  I did try to force the code to allow code 11 at any time, but this
  didn't seem to help the situation any. The device still sent code 5
  

[Kernel-packages] [Bug 1822882] [NEW] linux-lts-trusty: -proposed tracker

2019-04-02 Thread Stefan Bader
Public bug reported:

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

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

-- swm properties --
kernel-stable-master-bug: 1822883

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Invalid

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: Invalid

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-signing-to-proposed
 Importance: Medium
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-lts-trusty (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux-lts-trusty (Ubuntu Precise)
 Importance: Medium
 Status: New


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-backport-of-1822883 kernel-sru-cycle-2019.04.01-1 precise

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-signing-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Invalid

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Invalid

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: 

[Kernel-packages] [Bug 1822883] [NEW] linux: -proposed tracker

2019-04-02 Thread Stefan Bader
Public bug reported:

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

backports: bug 1822882 (precise/linux-lts-trusty)

-- swm properties --

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: linux (Ubuntu Trusty)
 Importance: Medium
 Status: New


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2019.04.01-1 trusty

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

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

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru)

** 

[Kernel-packages] [Bug 1822796] Re: linux: 4.18.0-18.19 -proposed tracker

2019-04-02 Thread 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
  
  backports: bug 1822795 (bionic/linux-hwe)
  derivatives: bug 1822786 (linux-raspi2), bug 1822788 (linux-aws), bug 1822791 
(linux-azure), bug 1822793 (linux-gcp), bug 1822794 (linux-kvm)
  
  -- swm properties --
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 02. April 2019 19:02 UTC
+ reason:
+   promote-to-proposed: Holding -- builds not complete

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

Title:
  linux: 4.18.0-18.19 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  New

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

  backports: bug 1822795 (bionic/linux-hwe)
  derivatives: bug 1822786 (linux-raspi2), bug 1822788 (linux-aws), bug 1822791 
(linux-azure), bug 1822793 (linux-gcp), bug 1822794 (linux-kvm)

  -- swm properties --
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 02. April 2019 19:02 UTC
  reason:
promote-to-proposed: Holding -- builds not complete

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

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


[Kernel-packages] [Bug 1822680] Re: Detect SMP PHY control command errors

2019-04-02 Thread Seth Forshee
** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Detect SMP PHY control command errors

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  [Impact]
  Errors from SMP PHY control commands (e.g. enabling, disabling, resetting phy 
links) are currently ignored. This is likely to escalate into problems later in 
driver initialization - mostly around reset paths. By logging a message and 
returning an error, it should be easier to root cause failures, as well as 
avoiding continued use of a phy that has failed to reset.

  [Test Case]
  Regression testing only on a system that uses a libsas-based driver (hisi_sas)

  [Fix]
  01929a65dfa13 scsi: libsas: Check SMP PHY control function result

  [Regression Risk]
  Restricted to systems w/ libsas-based drivers (mvsas, hisi_sas, aic94xx). A 
possible risk is that a system was previously functioning normally even though 
SMP PHY control commands were failing, and now we'd be logging an error an 
aborting the operation.

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

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


[Kernel-packages] [Bug 1820409] Re: Audio stutter after update

2019-04-02 Thread Johnny Izzo
Hm, that was a bit early. Now it has "happened" ONCE with the 
5.1.0-050100rc2-generic kernel.
I think the battery of the laptop was pretty low at the time. 
Youtube audio went totally out of sync with video.

Restarted to 4.15.0-43 to see what that does with youtube. It had pauses
in getting the video (the circle going round) but when picture came back
it was still in sync with audio.

Restarted back to 5.1.0-050100rc2-generic again. Now everything was ok
there.


Also computer shows i have powersave governor on.
Another notebook with (Celeron N3350 and) powersave has no problems at all 
though.
I should probably also try a clean install.

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

Title:
  Audio stutter after update

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After some update:
  Audio stutters in VLC
  Video and audio stutters in Youtube

  I think cpu usage might be bigger in VLC too, over 20% vs. below 20%
  earlier (one thread gets full 100%?)

  Stuttering kernel at the moment is 4.15.0-46-generic.

  Kernel version 4.15.0-43-generic definitely worked good.
  Cant remember if i could get slight stutter from previous version version -45.

  
  Tried also lowlatency and 4.18 kernel, bad stuttering in those.

  (Distro is Lubuntu)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-46-generic 4.15.0-46.49
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-46-generic.
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 1: PCH [HDA Intel PCH], device 0: CX20751/2 Analog [CX20751/2 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  meie855 F pulseaudio
   /dev/snd/controlC1:  meie855 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'HDMI'/'HDA Intel HDMI at 0xf711c000 irq 50'
 Mixer name : 'Intel Broadwell HDMI'
 Components : 'HDA:80862808,80860101,0010'
 Controls  : 35
 Simple ctrls  : 5
  Card1.Amixer.info:
   Card hw:1 'PCH'/'HDA Intel PCH at 0xf7118000 irq 47'
 Mixer name : 'Conexant CX20751/2'
 Components : 'HDA:14f1510f,1043181d,00100100'
 Controls  : 20
 Simple ctrls  : 9
  CurrentDesktop: LXDE
  Date: Sat Mar 16 18:02:18 2019
  InstallationDate: Installed on 2018-07-04 (255 days ago)
  InstallationMedia: Lubuntu 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 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305FA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=a032fe2a-8284-47a9-a0d1-cfa1f01a5812 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-46-generic N/A
   linux-backports-modules-4.15.0-46-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/19/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305FA.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305FA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX305FA.210:bd05/19/2015:svnASUSTeKCOMPUTERINC.:pnUX305FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX305FA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1821641] Re: [HP Elitebook 840 G1] Screen is upside down on 19.04 daily

2019-04-02 Thread Woodcarver
I followed the suggestions in the related bug report. Removing iio-
sensor-proxy indeed solved the problem completely, with no need for
rotation lock. Should I move the bug report somewhere else at this
stage?

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

Title:
  [HP Elitebook 840 G1] Screen is upside down on 19.04 daily

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On the 19.04 daily image (2019-03-24), the screen on my laptop is
  completely upside down, from the moment the GUI loads. This does not
  happen on 18.04 and 18.10.

  It appears to be an accelerometer issue since holding the laptop
  upside down flips the image to its correct orientation - basically the
  functionality of the accelerometer is suddenly inverted.

  Please contact me if you want me to help testing the issue on my
  hardware. Thanks!

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

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


[Kernel-packages] [Bug 1822871] Re: enabling ftrace on Hi1620 CS causes an Oops

2019-04-02 Thread dann frazier
** 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/1822871

Title:
  enabling ftrace on Hi1620 CS causes an Oops

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]
  Attempting to enable the function tracer causes an Oops. This impacts the 
current disco kernel, as well as latest upstream 
(@5e7a8ca319268a70a6c7c3c1fde5bea38e1e5539).

  This is 100% reproducible on D06 CS systems, but not reproducible on
  D06 ES systems (the previous silicon rev).

  [Test Case]
  $ echo function | sudo tee /sys/kernel/debug/tracing/current_tracer

  [ 3125.651453] kernel BUG at arch/arm64/kernel/insn.c:1325!
  [ 3125.656766] Internal error: Oops - BUG: 0 [#1] SMP
  [ 3125.661551] Modules linked in: nls_iso8859_1 ipmi_ssif joydev input_leds 
tpm_tis_spi hns_roce_hw_v2 hns_roce ib_uverbs spi_dw_mmio ipmi_si spi_dw 
ipmi_devintf ipmi_msghandler cppc_cpufreq sch_fq_codel ib_iser rdma_cm iw_cm 
ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables 
x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 
raid0 multipath linear ses enclosure marvell aes_ce_blk aes_ce_cipher hibmc_drm 
hid_generic ttm crct10dif_ce drm_kms_helper ghash_ce sha2_ce syscopyarea 
sha256_arm64 sysfillrect ixgbe igb sha1_ce hns3 sysimgblt usbhid fb_sys_fops 
hisi_sas_v3_hw hclge i2c_algo_bit xfrm_algo hisi_sas_main mdio hid drm hnae3 
libsas ahci scsi_transport_sas hinic gpio_dwapb aes_neon_bs aes_neon_blk 
crypto_simd cryptd aes_arm64
  [ 3125.736544] CPU: 124 PID: 3306 Comm: tee Not tainted 5.0.0-rc4+ #12
  [ 3125.742802] Hardware name: Huawei TaiShan 2280 V2/BC82AMDA, BIOS TA BIOS 
2280-A CS V2.16.01 03/16/2019
  [ 3125.752099] pstate: 0049 (nzcv daif +PAN -UAO)
  [ 3125.756893] pc : aarch64_insn_adrp_get_offset+0x34/0x38
  [ 3125.762111] lr : plt_entries_equal.part.3+0x40/0x80
  [ 3125.766979] sp : 2837b9f0
  [ 3125.770286] x29: 2837b9f0 x28: bef4fd20d880
  [ 3125.775591] x27:  x26: 
  [ 3125.780896] x25: dea2a7e8 x24: 3dceb8413000
  [ 3125.786200] x23: 0002 x22: 3dce9d2289a4
  [ 3125.791504] x21: 2837ba8c x20: 2837b000
  [ 3125.796808] x19: 3dce9d228000 x18: 
  [ 3125.802112] x17:  x16: 3dceb7742780
  [ 3125.807416] x15: 3dceb7ce7c38 x14: 0001
  [ 3125.812720] x13: bef50bb9e188 x12: 
  [ 3125.818023] x11: 7efba3e79608 x10: 0a70
  [ 3125.823327] x9 : 3dceb6deeacc x8 : 
  [ 3125.828631] x7 : 0005 x6 : 3dceb8413f10
  [ 3125.833935] x5 : 002b3000 x4 : 3dceb6f4f4b8
  [ 3125.839239] x3 :  x2 : 9000
  [ 3125.844543] x1 :  x0 : 
  [ 3125.849850] Process tee (pid: 3306, stack limit = 0x262bb476)
  [ 3125.856281] Call trace:
  [ 3125.858723] aarch64_insn_adrp_get_offset+0x34/0x38
  [ 3125.863593] plt_entries_equal.part.3+0x40/0x80
  [ 3125.868115] plt_entries_equal+0x5c/0x70
  [ 3125.872031] ftrace_make_call+0xf0/0x150
  [ 3125.875950] __ftrace_replace_code+0xe8/0xf8
  [ 3125.880212] ftrace_replace_code+0x64/0xc0
  [ 3125.884301] ftrace_modify_all_code+0xb0/0x148
  [ 3125.888738] arch_ftrace_update_code+0x10/0x18
  [ 3125.893174] ftrace_run_update_code+0x20/0x70
  [ 3125.897524] ftrace_startup_enable+0x4c/0x58
  [ 3125.901788] ftrace_startup+0xa4/0x140
  [ 3125.905531] register_ftrace_function+0x64/0x80
  [ 3125.910059] function_trace_init+0x50/0x98
  [ 3125.914149] tracing_set_tracer+0xf4/0x1c0
  [ 3125.918238] tracing_set_trace_write+0x10c/0x168
  [ 3125.922852] __vfs_write+0x60/0x1a8
  [ 3125.926333] vfs_write+0xac/0x1b8
  [ 3125.929641] ksys_write+0x6c/0xd8
  [ 3125.932949] __arm64_sys_write+0x24/0x30
  [ 3125.936866] el0_svc_common+0x78/0x120
  [ 3125.940608] el0_svc_handler+0x38/0x78
  [ 3125.944349] el0_svc+0x8/0xc
  [ 3125.947224] Code: 97fffb33 53144c00 a8c17bfd d65f03c0 (d421)
  [ 3125.953312] ---[ end trace 0872d3e5933385e2 ]---

  [Fix]
  TBD

  [Regression Risk]
  TBD

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

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


[Kernel-packages] [Bug 1822871] Re: enabling ftrace on Hi1620 CS causes an Oops

2019-04-02 Thread dann frazier
** Summary changed:

- enabling ftrace on Hi1620 causes an Oops
+ enabling ftrace on Hi1620 CS causes an Oops

** Description changed:

  [Impact]
  Attempting to enable the function tracer causes an Oops. This impacts the 
current disco kernel, as well as latest upstream 
(@5e7a8ca319268a70a6c7c3c1fde5bea38e1e5539).
+ 
+ This is 100% reproducible on D06 CS systems, but not reproducible on D06
+ ES systems (the previous silicon rev).
  
  [Test Case]
  $ echo function | sudo tee /sys/kernel/debug/tracing/current_tracer
  
  [ 3125.651453] kernel BUG at arch/arm64/kernel/insn.c:1325!
  [ 3125.656766] Internal error: Oops - BUG: 0 [#1] SMP
  [ 3125.661551] Modules linked in: nls_iso8859_1 ipmi_ssif joydev input_leds 
tpm_tis_spi hns_roce_hw_v2 hns_roce ib_uverbs spi_dw_mmio ipmi_si spi_dw 
ipmi_devintf ipmi_msghandler cppc_cpufreq sch_fq_codel ib_iser rdma_cm iw_cm 
ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables 
x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 
raid0 multipath linear ses enclosure marvell aes_ce_blk aes_ce_cipher hibmc_drm 
hid_generic ttm crct10dif_ce drm_kms_helper ghash_ce sha2_ce syscopyarea 
sha256_arm64 sysfillrect ixgbe igb sha1_ce hns3 sysimgblt usbhid fb_sys_fops 
hisi_sas_v3_hw hclge i2c_algo_bit xfrm_algo hisi_sas_main mdio hid drm hnae3 
libsas ahci scsi_transport_sas hinic gpio_dwapb aes_neon_bs aes_neon_blk 
crypto_simd cryptd aes_arm64
  [ 3125.736544] CPU: 124 PID: 3306 Comm: tee Not tainted 5.0.0-rc4+ #12
  [ 3125.742802] Hardware name: Huawei TaiShan 2280 V2/BC82AMDA, BIOS TA BIOS 
2280-A CS V2.16.01 03/16/2019
  [ 3125.752099] pstate: 0049 (nzcv daif +PAN -UAO)
  [ 3125.756893] pc : aarch64_insn_adrp_get_offset+0x34/0x38
  [ 3125.762111] lr : plt_entries_equal.part.3+0x40/0x80
  [ 3125.766979] sp : 2837b9f0
  [ 3125.770286] x29: 2837b9f0 x28: bef4fd20d880
  [ 3125.775591] x27:  x26: 
  [ 3125.780896] x25: dea2a7e8 x24: 3dceb8413000
  [ 3125.786200] x23: 0002 x22: 3dce9d2289a4
  [ 3125.791504] x21: 2837ba8c x20: 2837b000
  [ 3125.796808] x19: 3dce9d228000 x18: 
  [ 3125.802112] x17:  x16: 3dceb7742780
  [ 3125.807416] x15: 3dceb7ce7c38 x14: 0001
  [ 3125.812720] x13: bef50bb9e188 x12: 
  [ 3125.818023] x11: 7efba3e79608 x10: 0a70
  [ 3125.823327] x9 : 3dceb6deeacc x8 : 
  [ 3125.828631] x7 : 0005 x6 : 3dceb8413f10
  [ 3125.833935] x5 : 002b3000 x4 : 3dceb6f4f4b8
  [ 3125.839239] x3 :  x2 : 9000
  [ 3125.844543] x1 :  x0 : 
  [ 3125.849850] Process tee (pid: 3306, stack limit = 0x262bb476)
  [ 3125.856281] Call trace:
  [ 3125.858723] aarch64_insn_adrp_get_offset+0x34/0x38
  [ 3125.863593] plt_entries_equal.part.3+0x40/0x80
  [ 3125.868115] plt_entries_equal+0x5c/0x70
  [ 3125.872031] ftrace_make_call+0xf0/0x150
  [ 3125.875950] __ftrace_replace_code+0xe8/0xf8
  [ 3125.880212] ftrace_replace_code+0x64/0xc0
  [ 3125.884301] ftrace_modify_all_code+0xb0/0x148
  [ 3125.888738] arch_ftrace_update_code+0x10/0x18
  [ 3125.893174] ftrace_run_update_code+0x20/0x70
  [ 3125.897524] ftrace_startup_enable+0x4c/0x58
  [ 3125.901788] ftrace_startup+0xa4/0x140
  [ 3125.905531] register_ftrace_function+0x64/0x80
  [ 3125.910059] function_trace_init+0x50/0x98
  [ 3125.914149] tracing_set_tracer+0xf4/0x1c0
  [ 3125.918238] tracing_set_trace_write+0x10c/0x168
  [ 3125.922852] __vfs_write+0x60/0x1a8
  [ 3125.926333] vfs_write+0xac/0x1b8
  [ 3125.929641] ksys_write+0x6c/0xd8
  [ 3125.932949] __arm64_sys_write+0x24/0x30
  [ 3125.936866] el0_svc_common+0x78/0x120
  [ 3125.940608] el0_svc_handler+0x38/0x78
  [ 3125.944349] el0_svc+0x8/0xc
  [ 3125.947224] Code: 97fffb33 53144c00 a8c17bfd d65f03c0 (d421)
  [ 3125.953312] ---[ end trace 0872d3e5933385e2 ]---
  
  [Fix]
  TBD
  
  [Regression Risk]
  TBD

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

Title:
  enabling ftrace on Hi1620 CS causes an Oops

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  Attempting to enable the function tracer causes an Oops. This impacts the 
current disco kernel, as well as latest upstream 
(@5e7a8ca319268a70a6c7c3c1fde5bea38e1e5539).

  This is 100% reproducible on D06 CS systems, but not reproducible on
  D06 ES systems (the previous silicon rev).

  [Test Case]
  $ echo function | sudo tee /sys/kernel/debug/tracing/current_tracer

  [ 3125.651453] kernel BUG at arch/arm64/kernel/insn.c:1325!
  [ 3125.656766] Internal error: Oops - BUG: 0 [#1] SMP
  [ 3125.661551] Modules linked in: nls_iso8859_1 ipmi_ssif joydev input_leds 

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

2019-04-02 Thread bugproxy
--- Comment From mranw...@us.ibm.com 2019-04-02 15:26 EDT---
Disco appears to be missing only this patch on master, but it's included on 
master-next:
92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 
reporting

The HWE and Cosmic are missing these patches:
cf175dc315f90185128fb061dc05b6fbb211aa2f powerpc/64: Disable the speculation 
barrier from the command line
6453b532f2c8856a80381e6b9a1f5ea2f12294df powerpc/64: Make stf barrier 
PPC_BOOK3S_64 specific.
179ab1cbf883575c3a585bcfc0f2160f1d22a149 powerpc/64: Add 
CONFIG_PPC_BARRIER_NOSPEC
af375eefbfb27cbb5b831984e66d724a40d26b5c powerpc/64: Call 
setup_barrier_nospec() from setup_arch()
406d2b6ae3420f5bb2b3db6986dc6f0b6dbb637b powerpc/64: Make meltdown reporting 
Book3S 64 specific
06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro & 
helpers for patching instructions
dc8c6cce9a26a51fc19961accb978217a3ba8c75 powerpc/64s: Add new security feature 
flags for count cache flush
ee13cb249fabdff8b90aaff61add347749280087 powerpc/64s: Add support for software 
count cache flush
ba72dc171954b782a79d25e0f4b3ed91090c3b1e powerpc/pseries: Query hypervisor for 
count cache flush settings
99d54754d3d5f896a8f616b0b6520662bc99d66b powerpc/powernv: Query firmware for 
count cache flush settings
7d8bad99ba5a22892f0cad6881289fdc3875a930 powerpc/fsl: Fix spectre_v2 
mitigations reporting
92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 
reporting

HWE-edge is missing the last patch still at this moment.

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

Title:
  Backport support for software count cache flush Spectre v2 mitigation.
  (CVE) (required for POWER9 DD2.3)

Status in linux package in Ubuntu:
  New

Bug description:
  For the different kernels:

  The HWE a563fd9c62f0 UBUNTU: Ubuntu-hwe-4.18.0-17.18~18.04.1 appears
  to have all patches.

  Disco appears to be missing only this patch:
  92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 
reporting

  Cosmic (which is supported until July) is missing a number of patches:
  cf175dc315f90185128fb061dc05b6fbb211aa2f powerpc/64: Disable the speculation 
barrier from the command line
  6453b532f2c8856a80381e6b9a1f5ea2f12294df powerpc/64: Make stf barrier 
PPC_BOOK3S_64 specific.
  179ab1cbf883575c3a585bcfc0f2160f1d22a149 powerpc/64: Add 
CONFIG_PPC_BARRIER_NOSPEC
  af375eefbfb27cbb5b831984e66d724a40d26b5c powerpc/64: Call 
setup_barrier_nospec() from setup_arch()
  406d2b6ae3420f5bb2b3db6986dc6f0b6dbb637b powerpc/64: Make meltdown reporting 
Book3S 64 specific
  06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro 
& helpers for patching instructions
  dc8c6cce9a26a51fc19961accb978217a3ba8c75 powerpc/64s: Add new security 
feature flags for count cache flush
  ee13cb249fabdff8b90aaff61add347749280087 powerpc/64s: Add support for 
software count cache flush
  ba72dc171954b782a79d25e0f4b3ed91090c3b1e powerpc/pseries: Query hypervisor 
for count cache flush settings
  99d54754d3d5f896a8f616b0b6520662bc99d66b powerpc/powernv: Query firmware for 
count cache flush settings
  7d8bad99ba5a22892f0cad6881289fdc3875a930 powerpc/fsl: Fix spectre_v2 
mitigations reporting
  92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 
reporting
  This appears to already be in -next.

  For the bionic 18.04.1 (4.15) kernel only this patch is already part of 
master-next:
  a6b3964ad71a61bb7c61d80a60bea7d42187b2eb powerpc/64s: Add barrier_nospec

  The others are ported, there were only 3 that were not clean.  Those are:
  2eea7f067f495e33b8b116b35b5988ab2b8aec55 powerpc/64s: Add support for ori 
barrier_nospec patching
  This failed because commit a048a07d7f4535baa4cbad6bc024f175317ab938 is 
missing, but it does not look like that is required here.

  cb3d6759a93c6d0aea1c10deb6d00e111c29c19c powerpc/64s: Enable barrier_nospec 
based on firmware settings
  This failed because debugfs was already included, I can see that previously 
added, I didn't see where it was previously removed.

  06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro 
& helpers for patching instructions
  This failed because 8183d99f4a22c is not included - but doesn't seem 
necessary.

  All other patches applied with, at most, some fuzz.

  Has had a little testing - boots, check debugfs, etc.

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

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


[Kernel-packages] [Bug 1822796] Re: linux: 4.18.0-18.19 -proposed tracker

2019-04-02 Thread 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
  
  backports: bug 1822795 (bionic/linux-hwe)
  derivatives: bug 1822786 (linux-raspi2), bug 1822788 (linux-aws), bug 1822791 
(linux-azure), bug 1822793 (linux-gcp), bug 1822794 (linux-kvm)
  
  -- swm properties --
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 02. April 2019 19:02 UTC
- reason:
-   promote-to-proposed: Holding -- builds not complete

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

Title:
  linux: 4.18.0-18.19 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  New

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

  backports: bug 1822795 (bionic/linux-hwe)
  derivatives: bug 1822786 (linux-raspi2), bug 1822788 (linux-aws), bug 1822791 
(linux-azure), bug 1822793 (linux-gcp), bug 1822794 (linux-kvm)

  -- swm properties --
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 02. April 2019 19:02 UTC

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

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


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

2019-04-02 Thread 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 1822871

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

Title:
  enabling ftrace on Hi1620 CS causes an Oops

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  Attempting to enable the function tracer causes an Oops. This impacts the 
current disco kernel, as well as latest upstream 
(@5e7a8ca319268a70a6c7c3c1fde5bea38e1e5539).

  This is 100% reproducible on D06 CS systems, but not reproducible on
  D06 ES systems (the previous silicon rev).

  [Test Case]
  $ echo function | sudo tee /sys/kernel/debug/tracing/current_tracer

  [ 3125.651453] kernel BUG at arch/arm64/kernel/insn.c:1325!
  [ 3125.656766] Internal error: Oops - BUG: 0 [#1] SMP
  [ 3125.661551] Modules linked in: nls_iso8859_1 ipmi_ssif joydev input_leds 
tpm_tis_spi hns_roce_hw_v2 hns_roce ib_uverbs spi_dw_mmio ipmi_si spi_dw 
ipmi_devintf ipmi_msghandler cppc_cpufreq sch_fq_codel ib_iser rdma_cm iw_cm 
ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables 
x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 
raid0 multipath linear ses enclosure marvell aes_ce_blk aes_ce_cipher hibmc_drm 
hid_generic ttm crct10dif_ce drm_kms_helper ghash_ce sha2_ce syscopyarea 
sha256_arm64 sysfillrect ixgbe igb sha1_ce hns3 sysimgblt usbhid fb_sys_fops 
hisi_sas_v3_hw hclge i2c_algo_bit xfrm_algo hisi_sas_main mdio hid drm hnae3 
libsas ahci scsi_transport_sas hinic gpio_dwapb aes_neon_bs aes_neon_blk 
crypto_simd cryptd aes_arm64
  [ 3125.736544] CPU: 124 PID: 3306 Comm: tee Not tainted 5.0.0-rc4+ #12
  [ 3125.742802] Hardware name: Huawei TaiShan 2280 V2/BC82AMDA, BIOS TA BIOS 
2280-A CS V2.16.01 03/16/2019
  [ 3125.752099] pstate: 0049 (nzcv daif +PAN -UAO)
  [ 3125.756893] pc : aarch64_insn_adrp_get_offset+0x34/0x38
  [ 3125.762111] lr : plt_entries_equal.part.3+0x40/0x80
  [ 3125.766979] sp : 2837b9f0
  [ 3125.770286] x29: 2837b9f0 x28: bef4fd20d880
  [ 3125.775591] x27:  x26: 
  [ 3125.780896] x25: dea2a7e8 x24: 3dceb8413000
  [ 3125.786200] x23: 0002 x22: 3dce9d2289a4
  [ 3125.791504] x21: 2837ba8c x20: 2837b000
  [ 3125.796808] x19: 3dce9d228000 x18: 
  [ 3125.802112] x17:  x16: 3dceb7742780
  [ 3125.807416] x15: 3dceb7ce7c38 x14: 0001
  [ 3125.812720] x13: bef50bb9e188 x12: 
  [ 3125.818023] x11: 7efba3e79608 x10: 0a70
  [ 3125.823327] x9 : 3dceb6deeacc x8 : 
  [ 3125.828631] x7 : 0005 x6 : 3dceb8413f10
  [ 3125.833935] x5 : 002b3000 x4 : 3dceb6f4f4b8
  [ 3125.839239] x3 :  x2 : 9000
  [ 3125.844543] x1 :  x0 : 
  [ 3125.849850] Process tee (pid: 3306, stack limit = 0x262bb476)
  [ 3125.856281] Call trace:
  [ 3125.858723] aarch64_insn_adrp_get_offset+0x34/0x38
  [ 3125.863593] plt_entries_equal.part.3+0x40/0x80
  [ 3125.868115] plt_entries_equal+0x5c/0x70
  [ 3125.872031] ftrace_make_call+0xf0/0x150
  [ 3125.875950] __ftrace_replace_code+0xe8/0xf8
  [ 3125.880212] ftrace_replace_code+0x64/0xc0
  [ 3125.884301] ftrace_modify_all_code+0xb0/0x148
  [ 3125.888738] arch_ftrace_update_code+0x10/0x18
  [ 3125.893174] ftrace_run_update_code+0x20/0x70
  [ 3125.897524] ftrace_startup_enable+0x4c/0x58
  [ 3125.901788] ftrace_startup+0xa4/0x140
  [ 3125.905531] register_ftrace_function+0x64/0x80
  [ 3125.910059] function_trace_init+0x50/0x98
  [ 3125.914149] tracing_set_tracer+0xf4/0x1c0
  [ 3125.918238] tracing_set_trace_write+0x10c/0x168
  [ 3125.922852] __vfs_write+0x60/0x1a8
  [ 3125.926333] vfs_write+0xac/0x1b8
  [ 3125.929641] ksys_write+0x6c/0xd8
  [ 3125.932949] __arm64_sys_write+0x24/0x30
  [ 3125.936866] el0_svc_common+0x78/0x120
  [ 3125.940608] el0_svc_handler+0x38/0x78
  [ 3125.944349] el0_svc+0x8/0xc
  [ 3125.947224] Code: 97fffb33 53144c00 a8c17bfd d65f03c0 (d421)
  [ 3125.953312] ---[ end trace 0872d3e5933385e2 ]---

  [Fix]
  TBD

  [Regression Risk]
  TBD

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

-- 

[Kernel-packages] [Bug 1787775] Re: touchpad not working on lenovo yoga 530

2019-04-02 Thread Julian Schrögel
I can also confirm the fix is working great for touchpad and touchscreen
on my YOGA-530-14ARR (AMD® Ryzen 3 2200u with radeon vega mobile gfx × 4
).

-- Fixing the wifi issue for three days until it finally worked,
stumbled upon this bug ticket today, downloaded the fix - and it works.
I am amazed and grateful for the great work. Thanks --

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

Title:
  touchpad not working on lenovo yoga 530

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  New
Status in linux source package in Disco:
  Confirmed

Bug description:
  === SRU Justification ===

  [Impact]
  AMD MP2 I2C driver doesn't support more than one bus.
  This makes touchpad on Lenovo Yoga 530 doensn't work as expected.

  [Fix]
  Sync the MP2 driver with upstream version.

  [Test]
  The new upstream driver doesn't break on Latitude 5495.
  Users haven't given any feedback yet, but since Disco is freezing I
  am sending this out.

  [Regression Potential]
  Low. It's from upstream, and only a subset of Raven Ridge has this
  device.

  === Original Bug Report ===

  The touchpad is not working and does not show up in cat
  /proc/bus/input/devices on multiple kernels. I've tried the newest
  kernel to date (19.08.18) and a few others.

  The touchpad works on windows.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-08-18 (0 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  Package: linux (not installed)
  Tags:  bionic
  Uname: Linux 4.18.3-041803-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to bionic on 2018-08-18 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Kernel-packages] [Bug 1822871] Re: enabling ftrace on Hi1620 causes an Oops

2019-04-02 Thread dann frazier
Bisection led to the following commit:

# first bad commit: [bdb85cd1d20669dfae813555dddb745ad09323ba]
arm64/module: switch to ADRP/ADD sequences for PLT entries

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

Title:
  enabling ftrace on Hi1620 causes an Oops

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  Attempting to enable the function tracer causes an Oops. This impacts the 
current disco kernel, as well as latest upstream 
(@5e7a8ca319268a70a6c7c3c1fde5bea38e1e5539).

  [Test Case]
  $ echo function | sudo tee /sys/kernel/debug/tracing/current_tracer

  [ 3125.651453] kernel BUG at arch/arm64/kernel/insn.c:1325!
  [ 3125.656766] Internal error: Oops - BUG: 0 [#1] SMP
  [ 3125.661551] Modules linked in: nls_iso8859_1 ipmi_ssif joydev input_leds 
tpm_tis_spi hns_roce_hw_v2 hns_roce ib_uverbs spi_dw_mmio ipmi_si spi_dw 
ipmi_devintf ipmi_msghandler cppc_cpufreq sch_fq_codel ib_iser rdma_cm iw_cm 
ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables 
x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 
raid0 multipath linear ses enclosure marvell aes_ce_blk aes_ce_cipher hibmc_drm 
hid_generic ttm crct10dif_ce drm_kms_helper ghash_ce sha2_ce syscopyarea 
sha256_arm64 sysfillrect ixgbe igb sha1_ce hns3 sysimgblt usbhid fb_sys_fops 
hisi_sas_v3_hw hclge i2c_algo_bit xfrm_algo hisi_sas_main mdio hid drm hnae3 
libsas ahci scsi_transport_sas hinic gpio_dwapb aes_neon_bs aes_neon_blk 
crypto_simd cryptd aes_arm64
  [ 3125.736544] CPU: 124 PID: 3306 Comm: tee Not tainted 5.0.0-rc4+ #12
  [ 3125.742802] Hardware name: Huawei TaiShan 2280 V2/BC82AMDA, BIOS TA BIOS 
2280-A CS V2.16.01 03/16/2019
  [ 3125.752099] pstate: 0049 (nzcv daif +PAN -UAO)
  [ 3125.756893] pc : aarch64_insn_adrp_get_offset+0x34/0x38
  [ 3125.762111] lr : plt_entries_equal.part.3+0x40/0x80
  [ 3125.766979] sp : 2837b9f0
  [ 3125.770286] x29: 2837b9f0 x28: bef4fd20d880
  [ 3125.775591] x27:  x26: 
  [ 3125.780896] x25: dea2a7e8 x24: 3dceb8413000
  [ 3125.786200] x23: 0002 x22: 3dce9d2289a4
  [ 3125.791504] x21: 2837ba8c x20: 2837b000
  [ 3125.796808] x19: 3dce9d228000 x18: 
  [ 3125.802112] x17:  x16: 3dceb7742780
  [ 3125.807416] x15: 3dceb7ce7c38 x14: 0001
  [ 3125.812720] x13: bef50bb9e188 x12: 
  [ 3125.818023] x11: 7efba3e79608 x10: 0a70
  [ 3125.823327] x9 : 3dceb6deeacc x8 : 
  [ 3125.828631] x7 : 0005 x6 : 3dceb8413f10
  [ 3125.833935] x5 : 002b3000 x4 : 3dceb6f4f4b8
  [ 3125.839239] x3 :  x2 : 9000
  [ 3125.844543] x1 :  x0 : 
  [ 3125.849850] Process tee (pid: 3306, stack limit = 0x262bb476)
  [ 3125.856281] Call trace:
  [ 3125.858723] aarch64_insn_adrp_get_offset+0x34/0x38
  [ 3125.863593] plt_entries_equal.part.3+0x40/0x80
  [ 3125.868115] plt_entries_equal+0x5c/0x70
  [ 3125.872031] ftrace_make_call+0xf0/0x150
  [ 3125.875950] __ftrace_replace_code+0xe8/0xf8
  [ 3125.880212] ftrace_replace_code+0x64/0xc0
  [ 3125.884301] ftrace_modify_all_code+0xb0/0x148
  [ 3125.888738] arch_ftrace_update_code+0x10/0x18
  [ 3125.893174] ftrace_run_update_code+0x20/0x70
  [ 3125.897524] ftrace_startup_enable+0x4c/0x58
  [ 3125.901788] ftrace_startup+0xa4/0x140
  [ 3125.905531] register_ftrace_function+0x64/0x80
  [ 3125.910059] function_trace_init+0x50/0x98
  [ 3125.914149] tracing_set_tracer+0xf4/0x1c0
  [ 3125.918238] tracing_set_trace_write+0x10c/0x168
  [ 3125.922852] __vfs_write+0x60/0x1a8
  [ 3125.926333] vfs_write+0xac/0x1b8
  [ 3125.929641] ksys_write+0x6c/0xd8
  [ 3125.932949] __arm64_sys_write+0x24/0x30
  [ 3125.936866] el0_svc_common+0x78/0x120
  [ 3125.940608] el0_svc_handler+0x38/0x78
  [ 3125.944349] el0_svc+0x8/0xc
  [ 3125.947224] Code: 97fffb33 53144c00 a8c17bfd d65f03c0 (d421)
  [ 3125.953312] ---[ end trace 0872d3e5933385e2 ]---

  [Fix]
  TBD

  [Regression Risk]
  TBD

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

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


[Kernel-packages] [Bug 1822870] tarball of patches for bionic

2019-04-02 Thread bugproxy
Default Comment by Bridge

** Attachment added: "tarball of patches for bionic"
   
https://bugs.launchpad.net/bugs/1822870/+attachment/5252187/+files/patches-bionic-dd2.3-spectre.tgz

** Changed in: ubuntu
 Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage 
(ubuntu-power-triage)

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

Title:
  Backport support for software count cache flush Spectre v2 mitigation.
  (CVE) (required for POWER9 DD2.3)

Status in linux package in Ubuntu:
  New

Bug description:
  For the different kernels:

  The HWE a563fd9c62f0 UBUNTU: Ubuntu-hwe-4.18.0-17.18~18.04.1 appears
  to have all patches.

  Disco appears to be missing only this patch:
  92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 
reporting

  Cosmic (which is supported until July) is missing a number of patches:
  cf175dc315f90185128fb061dc05b6fbb211aa2f powerpc/64: Disable the speculation 
barrier from the command line
  6453b532f2c8856a80381e6b9a1f5ea2f12294df powerpc/64: Make stf barrier 
PPC_BOOK3S_64 specific.
  179ab1cbf883575c3a585bcfc0f2160f1d22a149 powerpc/64: Add 
CONFIG_PPC_BARRIER_NOSPEC
  af375eefbfb27cbb5b831984e66d724a40d26b5c powerpc/64: Call 
setup_barrier_nospec() from setup_arch()
  406d2b6ae3420f5bb2b3db6986dc6f0b6dbb637b powerpc/64: Make meltdown reporting 
Book3S 64 specific
  06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro 
& helpers for patching instructions
  dc8c6cce9a26a51fc19961accb978217a3ba8c75 powerpc/64s: Add new security 
feature flags for count cache flush
  ee13cb249fabdff8b90aaff61add347749280087 powerpc/64s: Add support for 
software count cache flush
  ba72dc171954b782a79d25e0f4b3ed91090c3b1e powerpc/pseries: Query hypervisor 
for count cache flush settings
  99d54754d3d5f896a8f616b0b6520662bc99d66b powerpc/powernv: Query firmware for 
count cache flush settings
  7d8bad99ba5a22892f0cad6881289fdc3875a930 powerpc/fsl: Fix spectre_v2 
mitigations reporting
  92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 
reporting
  This appears to already be in -next.

  For the bionic 18.04.1 (4.15) kernel only this patch is already part of 
master-next:
  a6b3964ad71a61bb7c61d80a60bea7d42187b2eb powerpc/64s: Add barrier_nospec

  The others are ported, there were only 3 that were not clean.  Those are:
  2eea7f067f495e33b8b116b35b5988ab2b8aec55 powerpc/64s: Add support for ori 
barrier_nospec patching
  This failed because commit a048a07d7f4535baa4cbad6bc024f175317ab938 is 
missing, but it does not look like that is required here.

  cb3d6759a93c6d0aea1c10deb6d00e111c29c19c powerpc/64s: Enable barrier_nospec 
based on firmware settings
  This failed because debugfs was already included, I can see that previously 
added, I didn't see where it was previously removed.

  06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro 
& helpers for patching instructions
  This failed because 8183d99f4a22c is not included - but doesn't seem 
necessary.

  All other patches applied with, at most, some fuzz.

  Has had a little testing - boots, check debugfs, etc.

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

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


[Kernel-packages] [Bug 1822871] [NEW] enabling ftrace on Hi1620 causes an Oops

2019-04-02 Thread dann frazier
Public bug reported:

[Impact]
Attempting to enable the function tracer causes an Oops. This impacts the 
current disco kernel, as well as latest upstream 
(@5e7a8ca319268a70a6c7c3c1fde5bea38e1e5539).

[Test Case]
$ echo function | sudo tee /sys/kernel/debug/tracing/current_tracer

[ 3125.651453] kernel BUG at arch/arm64/kernel/insn.c:1325!
[ 3125.656766] Internal error: Oops - BUG: 0 [#1] SMP
[ 3125.661551] Modules linked in: nls_iso8859_1 ipmi_ssif joydev input_leds 
tpm_tis_spi hns_roce_hw_v2 hns_roce ib_uverbs spi_dw_mmio ipmi_si spi_dw 
ipmi_devintf ipmi_msghandler cppc_cpufreq sch_fq_codel ib_iser rdma_cm iw_cm 
ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables 
x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 
raid0 multipath linear ses enclosure marvell aes_ce_blk aes_ce_cipher hibmc_drm 
hid_generic ttm crct10dif_ce drm_kms_helper ghash_ce sha2_ce syscopyarea 
sha256_arm64 sysfillrect ixgbe igb sha1_ce hns3 sysimgblt usbhid fb_sys_fops 
hisi_sas_v3_hw hclge i2c_algo_bit xfrm_algo hisi_sas_main mdio hid drm hnae3 
libsas ahci scsi_transport_sas hinic gpio_dwapb aes_neon_bs aes_neon_blk 
crypto_simd cryptd aes_arm64
[ 3125.736544] CPU: 124 PID: 3306 Comm: tee Not tainted 5.0.0-rc4+ #12
[ 3125.742802] Hardware name: Huawei TaiShan 2280 V2/BC82AMDA, BIOS TA BIOS 
2280-A CS V2.16.01 03/16/2019
[ 3125.752099] pstate: 0049 (nzcv daif +PAN -UAO)
[ 3125.756893] pc : aarch64_insn_adrp_get_offset+0x34/0x38
[ 3125.762111] lr : plt_entries_equal.part.3+0x40/0x80
[ 3125.766979] sp : 2837b9f0
[ 3125.770286] x29: 2837b9f0 x28: bef4fd20d880
[ 3125.775591] x27:  x26: 
[ 3125.780896] x25: dea2a7e8 x24: 3dceb8413000
[ 3125.786200] x23: 0002 x22: 3dce9d2289a4
[ 3125.791504] x21: 2837ba8c x20: 2837b000
[ 3125.796808] x19: 3dce9d228000 x18: 
[ 3125.802112] x17:  x16: 3dceb7742780
[ 3125.807416] x15: 3dceb7ce7c38 x14: 0001
[ 3125.812720] x13: bef50bb9e188 x12: 
[ 3125.818023] x11: 7efba3e79608 x10: 0a70
[ 3125.823327] x9 : 3dceb6deeacc x8 : 
[ 3125.828631] x7 : 0005 x6 : 3dceb8413f10
[ 3125.833935] x5 : 002b3000 x4 : 3dceb6f4f4b8
[ 3125.839239] x3 :  x2 : 9000
[ 3125.844543] x1 :  x0 : 
[ 3125.849850] Process tee (pid: 3306, stack limit = 0x262bb476)
[ 3125.856281] Call trace:
[ 3125.858723] aarch64_insn_adrp_get_offset+0x34/0x38
[ 3125.863593] plt_entries_equal.part.3+0x40/0x80
[ 3125.868115] plt_entries_equal+0x5c/0x70
[ 3125.872031] ftrace_make_call+0xf0/0x150
[ 3125.875950] __ftrace_replace_code+0xe8/0xf8
[ 3125.880212] ftrace_replace_code+0x64/0xc0
[ 3125.884301] ftrace_modify_all_code+0xb0/0x148
[ 3125.888738] arch_ftrace_update_code+0x10/0x18
[ 3125.893174] ftrace_run_update_code+0x20/0x70
[ 3125.897524] ftrace_startup_enable+0x4c/0x58
[ 3125.901788] ftrace_startup+0xa4/0x140
[ 3125.905531] register_ftrace_function+0x64/0x80
[ 3125.910059] function_trace_init+0x50/0x98
[ 3125.914149] tracing_set_tracer+0xf4/0x1c0
[ 3125.918238] tracing_set_trace_write+0x10c/0x168
[ 3125.922852] __vfs_write+0x60/0x1a8
[ 3125.926333] vfs_write+0xac/0x1b8
[ 3125.929641] ksys_write+0x6c/0xd8
[ 3125.932949] __arm64_sys_write+0x24/0x30
[ 3125.936866] el0_svc_common+0x78/0x120
[ 3125.940608] el0_svc_handler+0x38/0x78
[ 3125.944349] el0_svc+0x8/0xc
[ 3125.947224] Code: 97fffb33 53144c00 a8c17bfd d65f03c0 (d421)
[ 3125.953312] ---[ end trace 0872d3e5933385e2 ]---

[Fix]
TBD

[Regression Risk]
TBD

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: 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/1822871

Title:
  enabling ftrace on Hi1620 causes an Oops

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  Attempting to enable the function tracer causes an Oops. This impacts the 
current disco kernel, as well as latest upstream 
(@5e7a8ca319268a70a6c7c3c1fde5bea38e1e5539).

  [Test Case]
  $ echo function | sudo tee /sys/kernel/debug/tracing/current_tracer

  [ 3125.651453] kernel BUG at arch/arm64/kernel/insn.c:1325!
  [ 3125.656766] Internal error: Oops - BUG: 0 [#1] SMP
  [ 3125.661551] Modules linked in: nls_iso8859_1 ipmi_ssif joydev input_leds 
tpm_tis_spi hns_roce_hw_v2 hns_roce ib_uverbs spi_dw_mmio ipmi_si spi_dw 
ipmi_devintf ipmi_msghandler cppc_cpufreq sch_fq_codel ib_iser rdma_cm iw_cm 
ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables 
x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 
raid0 multipath 

[Kernel-packages] [Bug 1822791] Re: linux-azure: -proposed tracker

2019-04-02 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Confirmed

** 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
  
  backports: bug 1822790 (bionic/linux-azure)
  
  -- swm properties --
  kernel-stable-master-bug: 1822796
- phase: Holding before Packaging
- phase-changed: Tuesday, 02. April 2019 14:02 UTC
+ phase: Ready for Packaging
+ phase-changed: Tuesday, 02. April 2019 19:06 UTC
  reason:
-   prepare-package: Stalled -- waiting for master bug
+   prepare-package: Pending -- version not specified

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

Title:
  linux-azure:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Cosmic:
  New

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

  backports: bug 1822790 (bionic/linux-azure)

  -- swm properties --
  kernel-stable-master-bug: 1822796
  phase: Ready for Packaging
  phase-changed: Tuesday, 02. April 2019 19:06 UTC
  reason:
prepare-package: Pending -- version not specified

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

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


[Kernel-packages] [Bug 1822870] [NEW] Backport support for software count cache flush Spectre v2 mitigation. (CVE) (required for POWER9 DD2.3)

2019-04-02 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

For the different kernels:

The HWE a563fd9c62f0 UBUNTU: Ubuntu-hwe-4.18.0-17.18~18.04.1 appears to
have all patches.

Disco appears to be missing only this patch:
92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 
reporting

Cosmic (which is supported until July) is missing a number of patches:
cf175dc315f90185128fb061dc05b6fbb211aa2f powerpc/64: Disable the speculation 
barrier from the command line
6453b532f2c8856a80381e6b9a1f5ea2f12294df powerpc/64: Make stf barrier 
PPC_BOOK3S_64 specific.
179ab1cbf883575c3a585bcfc0f2160f1d22a149 powerpc/64: Add 
CONFIG_PPC_BARRIER_NOSPEC
af375eefbfb27cbb5b831984e66d724a40d26b5c powerpc/64: Call 
setup_barrier_nospec() from setup_arch()
406d2b6ae3420f5bb2b3db6986dc6f0b6dbb637b powerpc/64: Make meltdown reporting 
Book3S 64 specific
06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro & 
helpers for patching instructions
dc8c6cce9a26a51fc19961accb978217a3ba8c75 powerpc/64s: Add new security feature 
flags for count cache flush
ee13cb249fabdff8b90aaff61add347749280087 powerpc/64s: Add support for software 
count cache flush
ba72dc171954b782a79d25e0f4b3ed91090c3b1e powerpc/pseries: Query hypervisor for 
count cache flush settings
99d54754d3d5f896a8f616b0b6520662bc99d66b powerpc/powernv: Query firmware for 
count cache flush settings
7d8bad99ba5a22892f0cad6881289fdc3875a930 powerpc/fsl: Fix spectre_v2 
mitigations reporting
92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 
reporting
This appears to already be in -next.

For the bionic 18.04.1 (4.15) kernel only this patch is already part of 
master-next:
a6b3964ad71a61bb7c61d80a60bea7d42187b2eb powerpc/64s: Add barrier_nospec

The others are ported, there were only 3 that were not clean.  Those are:
2eea7f067f495e33b8b116b35b5988ab2b8aec55 powerpc/64s: Add support for ori 
barrier_nospec patching
This failed because commit a048a07d7f4535baa4cbad6bc024f175317ab938 is missing, 
but it does not look like that is required here.

cb3d6759a93c6d0aea1c10deb6d00e111c29c19c powerpc/64s: Enable barrier_nospec 
based on firmware settings
This failed because debugfs was already included, I can see that previously 
added, I didn't see where it was previously removed.

06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro & 
helpers for patching instructions
This failed because 8183d99f4a22c is not included - but doesn't seem necessary.

All other patches applied with, at most, some fuzz.

Has had a little testing - boots, check debugfs, etc.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-ppc64le bugnameltc-176424 severity-critical 
targetmilestone-inin18042
-- 
Backport support for software count cache flush Spectre v2 mitigation. (CVE) 
(required for POWER9 DD2.3)
https://bugs.launchpad.net/bugs/1822870
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 1822788] Re: linux-aws: -proposed tracker

2019-04-02 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Confirmed

** 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
  
  backports: bug 1822787 (bionic/linux-aws-edge)
  
  -- swm properties --
  kernel-stable-master-bug: 1822796
- phase: Holding before Packaging
- phase-changed: Tuesday, 02. April 2019 14:01 UTC
+ phase: Ready for Packaging
+ phase-changed: Tuesday, 02. April 2019 19:02 UTC
  reason:
-   prepare-package: Stalled -- waiting for master bug
+   prepare-package: Pending -- version not specified

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

Title:
  linux-aws:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Cosmic:
  New

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

  backports: bug 1822787 (bionic/linux-aws-edge)

  -- swm properties --
  kernel-stable-master-bug: 1822796
  phase: Ready for Packaging
  phase-changed: Tuesday, 02. April 2019 19:02 UTC
  reason:
prepare-package: Pending -- version not specified

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

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


[Kernel-packages] [Bug 1822786] Re: linux-raspi2: -proposed tracker

2019-04-02 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Confirmed

** 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 --
  kernel-stable-master-bug: 1822796
- phase: Holding before Packaging
- phase-changed: Tuesday, 02. April 2019 14:01 UTC
+ phase: Ready for Packaging
+ phase-changed: Tuesday, 02. April 2019 19:05 UTC
  reason:
-   prepare-package: Stalled -- waiting for master bug
+   prepare-package: Pending -- version not specified

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

Title:
  linux-raspi2:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Cosmic:
  New

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

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

  -- swm properties --
  kernel-stable-master-bug: 1822796
  phase: Ready for Packaging
  phase-changed: Tuesday, 02. April 2019 19:05 UTC
  reason:
prepare-package: Pending -- version not specified

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

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


[Kernel-packages] [Bug 1822682] Re: nvidia driver issues

2019-04-02 Thread Frank
lspci -vvnn
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [8086:5910] (rev 05)
Subsystem: Dell Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM 
Registers [1028:07fa]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen 
Core Processor PCIe Controller (x16) [8086:1901] (rev 05) (prog-if 00 [Normal 
decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:591b] 
(rev 04) (prog-if 00 [VGA controller])
Subsystem: Dell Device [1028:07fa]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 05)
Subsystem: Dell Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor 
Thermal Subsystem [1028:07fa]
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device

00:14.0 USB controller [0c03]: Intel Corporation 100 Series/C230 Series Chipset 
Family USB 3.0 xHCI Controller [8086:a12f] (rev 31) (prog-if 30 [XHCI])
Subsystem: Dell Sunrise Point-H USB 3.0 xHCI Controller [1028:07fa]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: xhci_hcd

00:14.2 Signal processing controller [1180]: Intel Corporation 100 Series/C230 
Series Chipset Family Thermal Subsystem [8086:a131] (rev 31)
Subsystem: Dell Sunrise Point-H Thermal subsystem [1028:07fa]
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: intel_pch_thermal
Kernel modules: intel_pch_thermal

00:15.0 Signal processing controller [1180]: Intel Corporation 100 Series/C230 
Series Chipset Family Serial IO I2C Controller #0 [8086:a160] (rev 31)
Subsystem: Dell Sunrise Point-H Serial IO I2C Controller [1028:07fa]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

00:15.1 Signal processing controller [1180]: Intel Corporation 100 Series/C230 
Series Chipset Family Serial IO I2C Controller #1 [8086:a161] (rev 31)
Subsystem: Dell Sunrise Point-H Serial IO I2C Controller [1028:07fa]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

00:16.0 Communication controller [0780]: Intel Corporation 100 Series/C230 
Series Chipset Family MEI Controller #1 [8086:a13a] (rev 31)
Subsystem: Dell Sunrise Point-H CSME HECI [1028:07fa]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: mei_me
Kernel modules: mei_me

00:17.0 SATA controller [0106]: Intel Corporation HM170/QM170 Chipset SATA 
Controller [AHCI Mode] [8086:a103] (rev 31) (prog-if 01 [AHCI 1.0])
Subsystem: Dell Sunrise Point-H SATA Controller [AHCI mode] [1028:07fa]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: ahci
Kernel modules: ahci

00:1c.0 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset 
Family PCI Express Root Port #1 [8086:a110] (rev f1) (prog-if 00 [Normal 
decode])
Control: I/O+ Mem+ BusMaster+ 

[Kernel-packages] [Bug 1822794] Re: linux-kvm: -proposed tracker

2019-04-02 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Confirmed

** 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 --
  kernel-stable-master-bug: 1822796
- phase: Holding before Packaging
- phase-changed: Tuesday, 02. April 2019 14:00 UTC
+ phase: Ready for Packaging
+ phase-changed: Tuesday, 02. April 2019 19:03 UTC
  reason:
-   prepare-package: Stalled -- waiting for master bug
+   prepare-package: Pending -- version not specified

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

Title:
  linux-kvm:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Cosmic:
  New

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

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

  -- swm properties --
  kernel-stable-master-bug: 1822796
  phase: Ready for Packaging
  phase-changed: Tuesday, 02. April 2019 19:03 UTC
  reason:
prepare-package: Pending -- version not specified

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

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


[Kernel-packages] [Bug 1822793] Re: linux-gcp: -proposed tracker

2019-04-02 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Confirmed

** 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
  
  backports: bug 1822792 (bionic/linux-gcp-edge)
  
  -- swm properties --
  kernel-stable-master-bug: 1822796
- phase: Holding before Packaging
- phase-changed: Tuesday, 02. April 2019 14:02 UTC
+ phase: Ready for Packaging
+ phase-changed: Tuesday, 02. April 2019 19:05 UTC
  reason:
-   prepare-package: Stalled -- waiting for master bug
+   prepare-package: Pending -- version not specified

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

Title:
  linux-gcp:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Cosmic:
  New

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

  backports: bug 1822792 (bionic/linux-gcp-edge)

  -- swm properties --
  kernel-stable-master-bug: 1822796
  phase: Ready for Packaging
  phase-changed: Tuesday, 02. April 2019 19:05 UTC
  reason:
prepare-package: Pending -- version not specified

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

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


[Kernel-packages] [Bug 1822796] Re: linux: 4.18.0-18.19 -proposed tracker

2019-04-02 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: In Progress => Fix Released

** 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
  
  backports: bug 1822795 (bionic/linux-hwe)
  derivatives: bug 1822786 (linux-raspi2), bug 1822788 (linux-aws), bug 1822791 
(linux-azure), bug 1822793 (linux-gcp), bug 1822794 (linux-kvm)
  
  -- swm properties --
- phase: Packaging
- phase-changed: Tuesday, 02. April 2019 16:12 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Tuesday, 02. April 2019 19:02 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
-   prepare-package-signed: Pending -- package not yet uploaded
+   promote-to-proposed: Holding -- builds not complete

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

Title:
  linux: 4.18.0-18.19 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  New

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

  backports: bug 1822795 (bionic/linux-hwe)
  derivatives: bug 1822786 (linux-raspi2), bug 1822788 (linux-aws), bug 1822791 
(linux-azure), bug 1822793 (linux-gcp), bug 1822794 (linux-kvm)

  -- swm properties --
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 02. April 2019 19:02 UTC
  reason:
promote-to-proposed: Holding -- builds not complete

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

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


[Kernel-packages] [Bug 1822682] Re: nvidia driver issues

2019-04-02 Thread Frank
After updating kernel to 4.18.5 it's no more warnings and rcu_sched errors, but 
when i launch csgo from steam i get the same error:
Failed to create GL context; Could not make GL context current: GLXBadContext

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

Title:
  nvidia driver issues

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-signed-hwe package in Ubuntu:
  New
Status in linux-firmware source package in Bionic:
  New
Status in linux-signed-hwe source package in Bionic:
  New
Status in linux-firmware source package in Cosmic:
  New
Status in linux-signed-hwe source package in Cosmic:
  New

Bug description:
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Kernel: Linux 4.18.0-15-generic
  Intel Core i7-7700HQ + GeForce 1050Ti
  after: sudo update-initramfs -u (i'm using this command after installing 
fresh Ubuntu because it can't reboot correctly)
  I get :
  update-initramfs: Generating /boot/initrd.img-4.18.0-16-generic
  W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/sig.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/image.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/desc.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/nvdec/scrubber.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_method_init.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_bundle_init.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_nonctx.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_ctx.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_sig.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_data.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_inst.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_bl.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_sig.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_data.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_inst.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_bl.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_unload.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_load.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/unload_bl.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/bl.bin for module 
nouveau

  Had no such trouble on Ubuntu 18.04.01 with older kernel

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.18.0-15-generic 4.18.0-15.16~18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  2 00:18:33 2019
  InstallationDate: Installed on 2019-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1804149] Re: Kernel panic, Oops: 0004 ilc:3 [#1] SMP, iscsi_q_20 iscsi_xmitworker [libiscsi]

2019-04-02 Thread Frank Heimes
** Changed in: ubuntu-z-systems
   Status: Triaged => 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/1804149

Title:
  Kernel panic,Oops: 0004 ilc:3 [#1] SMP,  iscsi_q_20 iscsi_xmitworker
  [libiscsi]

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - Michael Finnegan  - 2018-11-19 14:14:40 
==
  ---Problem Description---
  Kernel panic,Oops: 0004 ilc:3 [#1] SMP,  iscsi_q_20 iscsi_xmitworker 
[libiscsi]
   
  ---uname output---
  Linux ilabg3 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:13:24 UTC 2018 
s390x s390x s390x GNU/Linux
   
  Machine Type = IBM 3906 M05 7G4 (z/VM 7.1.0) 
   
  ---Debugger---
  A debugger is not configured
   
  Contact Information = Michael Finnegan/finne...@us.ibm.com 
   
  Stack trace output:
   dmesg.201811161956
  [1363037.322472] Unable to handle kernel pointer dereference in virtual 
kernel address space
  [1363037.322481] Failing address:  TEID: 0483
  [1363037.322483] Fault in home space mode while using kernel ASCE.
  [1363037.322486] AS:00ea0007 R3:f37d0007 S:f37ff000 
P:013d
  [1363037.322524] Oops: 0004 ilc:3 [#1] SMP
  [1363037.322529] Modules linked in: iptable_filter binfmt_misc 
rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache qeth_l3 qeth_l2 
s390_trng ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 
sha1_s390 sha_common qeth vmur ccwgroup vfio_ccw vfio_mdev mdev 
vfio_iommu_type1 vfio sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core sunrpc 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables 
dm_round_robin dm_service_time crc32_vx_s390 dasd_eckd_mod zfcp qdio 
scsi_transport_fc dasd_fba_mod dasd_mod scsi_dh_emc scsi_dh_rdac scsi_dh_alua 
dm_multipath
  [1363037.322567] CPU: 3 PID: 37970 Comm: kworker/u128:19 Not tainted 
4.15.0-36-generic #39-Ubuntu
  [1363037.322573] Hardware name: IBM 3906 M05 7G4 (z/VM 7.1.0)
  [1363037.322581] Workqueue: iscsi_q_20 iscsi_xmitworker [libiscsi]
  [1363037.322583] Krnl PSW : c8051cf6 e49a28f4 
(__iscsi_get_task+0x6/0x18 [libiscsi])
  [1363037.322587]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 
PM:0 RI:0 EA:3
  [1363037.322589] Krnl GPRS:  02923ce0 
 0400
  [1363037.322591]03ff80277640 0008 
788efc00 03ff802777cc
  [1363037.322592]03ff8027769c  
 78ce8310
  [1363037.322594]f3689800 78ce83a2 
03ff80272e8e 02923c90
  [1363037.322601] Krnl Code: 03ff80272624: c0f4fcf6  brcl
15,3ff80272010
  03ff8027262a: c0f4377b  brcl
15,3ff80279520
 #03ff80272630: c004  brcl
0,3ff80272630
 >03ff80272636: eb012078006a  asi 
120(%r2),1
  03ff8027263c: c0f43772  brcl
15,3ff80279520
  03ff80272642: 0707  bcr 0,%r7
  03ff80272644: 0707  bcr 0,%r7
  03ff80272646: 0707  bcr 0,%r7
  [1363037.322618] Call Trace:
  [1363037.322621] ([<03ff80272ec6>] iscsi_xmit_task+0x86/0x138 [libiscsi])
  [1363037.322625]  [<03ff8027769c>] iscsi_data_xmit+0x44c/0x548 [libiscsi]
  [1363037.322636]  [<03ff802777cc>] iscsi_xmitworker+0x34/0x58 [libiscsi]
  [1363037.322642]  [<001918f2>] process_one_work+0x262/0x4d8
  [1363037.322644]  [<00191bc0>] worker_thread+0x58/0x4e8
  [1363037.322648]  [<00198d24>] kthread+0x14c/0x168
  [1363037.322652]  [<008e3eb2>] kernel_thread_starter+0xa/0x10
  [1363037.322654]  [<008e3ea8>] kernel_thread_starter+0x0/0x10
  [1363037.322655] Last Breaking-Event-Address:
  [1363037.322657]  [<03ff80272e88>] iscsi_xmit_task+0x48/0x138 [libiscsi]
  [1363037.322658]
  [1363037.322660] Kernel panic - not syncing: Fatal exception in interrupt

  
   
  Oops output:
Oops: 0004 ilc:3 [#1] SMP


  *Additional Instructions for Michael Finnegan/finne...@us.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on. 
  -Attach sysctl -a output output to the bug.

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

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


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

2019-04-02 Thread bugproxy
--- Comment From finne...@us.ibm.com 2019-04-02 14:10 EDT---
(In reply to comment #29)
> Can you please test the test kernel at:
> https://kernel.ubuntu.com/~juergh/lp1804149/

I am waiting for the configuration to complete current testing.
I hope to be able to test the test kernel within the next 2-3 weeks

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

Title:
  Kernel panic,Oops: 0004 ilc:3 [#1] SMP,  iscsi_q_20 iscsi_xmitworker
  [libiscsi]

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - Michael Finnegan  - 2018-11-19 14:14:40 
==
  ---Problem Description---
  Kernel panic,Oops: 0004 ilc:3 [#1] SMP,  iscsi_q_20 iscsi_xmitworker 
[libiscsi]
   
  ---uname output---
  Linux ilabg3 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:13:24 UTC 2018 
s390x s390x s390x GNU/Linux
   
  Machine Type = IBM 3906 M05 7G4 (z/VM 7.1.0) 
   
  ---Debugger---
  A debugger is not configured
   
  Contact Information = Michael Finnegan/finne...@us.ibm.com 
   
  Stack trace output:
   dmesg.201811161956
  [1363037.322472] Unable to handle kernel pointer dereference in virtual 
kernel address space
  [1363037.322481] Failing address:  TEID: 0483
  [1363037.322483] Fault in home space mode while using kernel ASCE.
  [1363037.322486] AS:00ea0007 R3:f37d0007 S:f37ff000 
P:013d
  [1363037.322524] Oops: 0004 ilc:3 [#1] SMP
  [1363037.322529] Modules linked in: iptable_filter binfmt_misc 
rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache qeth_l3 qeth_l2 
s390_trng ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 
sha1_s390 sha_common qeth vmur ccwgroup vfio_ccw vfio_mdev mdev 
vfio_iommu_type1 vfio sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core sunrpc 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables 
dm_round_robin dm_service_time crc32_vx_s390 dasd_eckd_mod zfcp qdio 
scsi_transport_fc dasd_fba_mod dasd_mod scsi_dh_emc scsi_dh_rdac scsi_dh_alua 
dm_multipath
  [1363037.322567] CPU: 3 PID: 37970 Comm: kworker/u128:19 Not tainted 
4.15.0-36-generic #39-Ubuntu
  [1363037.322573] Hardware name: IBM 3906 M05 7G4 (z/VM 7.1.0)
  [1363037.322581] Workqueue: iscsi_q_20 iscsi_xmitworker [libiscsi]
  [1363037.322583] Krnl PSW : c8051cf6 e49a28f4 
(__iscsi_get_task+0x6/0x18 [libiscsi])
  [1363037.322587]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 
PM:0 RI:0 EA:3
  [1363037.322589] Krnl GPRS:  02923ce0 
 0400
  [1363037.322591]03ff80277640 0008 
788efc00 03ff802777cc
  [1363037.322592]03ff8027769c  
 78ce8310
  [1363037.322594]f3689800 78ce83a2 
03ff80272e8e 02923c90
  [1363037.322601] Krnl Code: 03ff80272624: c0f4fcf6  brcl
15,3ff80272010
  03ff8027262a: c0f4377b  brcl
15,3ff80279520
 #03ff80272630: c004  brcl
0,3ff80272630
 >03ff80272636: eb012078006a  asi 
120(%r2),1
  03ff8027263c: c0f43772  brcl
15,3ff80279520
  03ff80272642: 0707  bcr 0,%r7
  03ff80272644: 0707  bcr 0,%r7
  03ff80272646: 0707  bcr 0,%r7
  [1363037.322618] Call Trace:
  [1363037.322621] ([<03ff80272ec6>] iscsi_xmit_task+0x86/0x138 [libiscsi])
  [1363037.322625]  [<03ff8027769c>] iscsi_data_xmit+0x44c/0x548 [libiscsi]
  [1363037.322636]  [<03ff802777cc>] iscsi_xmitworker+0x34/0x58 [libiscsi]
  [1363037.322642]  [<001918f2>] process_one_work+0x262/0x4d8
  [1363037.322644]  [<00191bc0>] worker_thread+0x58/0x4e8
  [1363037.322648]  [<00198d24>] kthread+0x14c/0x168
  [1363037.322652]  [<008e3eb2>] kernel_thread_starter+0xa/0x10
  [1363037.322654]  [<008e3ea8>] kernel_thread_starter+0x0/0x10
  [1363037.322655] Last Breaking-Event-Address:
  [1363037.322657]  [<03ff80272e88>] iscsi_xmit_task+0x48/0x138 [libiscsi]
  [1363037.322658]
  [1363037.322660] Kernel panic - not syncing: Fatal exception in interrupt

  
   
  Oops output:
Oops: 0004 ilc:3 [#1] SMP


  *Additional Instructions for Michael Finnegan/finne...@us.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on. 
  -Attach sysctl -a output output to the bug.

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

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

[Kernel-packages] [Bug 1822633] Re: Pairing failure with BLE 4.0

2019-04-02 Thread Jason Gerecke
I've just built and installed the master branch of gnome-bluetooth
(commit b4edf6a8) and didn't see any behavioral change. Since it isn't
even possible to pair through bluetoothctl, I wasn't particularly
hopeful that an update to gnome-bluetooth would fix things.

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

Title:
  Pairing failure with BLE 4.0

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

Bug description:
  When attempting to pair a BLE 4.0 pen using Bluez, we receive
  authentication errors.

  Here is the FW from Jason.

  Details:

  ===

  I added a few debug statements (patch attached) to the kernel's
  net/bluetooth/smp.c:smp_sig_channel() function
  (https://github.com/torvalds/linux/blob/v5.0/net/bluetooth/smp.c#L2883).
  When I try to pair the PN579X, I get the following logs:

  [ 5653.563048] DBG: Received code 2 (allowed = 0024) with 6 bytes
  [ 5653.563053] DBG: Processing code...
  [ 5653.709572] DBG: Received code 3 (allowed = 0028) with 16 bytes
  [ 5653.709577] DBG: Processing code...
  [ 5653.807085] DBG: Received code 4 (allowed = 0030) with 16 bytes
  [ 5653.807089] DBG: Processing code...
  [ 5654.148553] DBG: Received code 6 (allowed = 0060) with 16 bytes
  [ 5654.148557] DBG: Processing code...
  [ 5654.197024] DBG: Received code 7 (allowed = 00a0) with 10 bytes
  [ 5654.197027] DBG: Processing code...
  [ 5654.245824] DBG: Received code 8 (allowed = 0120) with 16 bytes
  [ 5654.245828] DBG: Processing code...
  [ 5654.246178] DBG: Received code 9 (allowed = 0220) with 7 bytes
  [ 5654.246182] DBG: Processing code...
  [ 5657.610656] input: Dell Active Pen PN579X Keyboard as 
/devices/virtual/misc/uhid/0005:413C:81D5.0004/input/input23
  [ 5657.610997] hid-generic 0005:413C:81D5.0004: input,hidraw0: BLUETOOTH HID 
vf.08 Keyboard [Dell Active Pen PN579X] on 18:56:80:18:6A:E5

  When I try to pair the PN557W, however, I only get the following:

  [   64.924901] DBG: Received code 11 (allowed = 0024) with 1 bytes
  [   64.924906] DBG: AuthReq = 00
  [   64.924907] ERR: Code not allowed on existing connection
  [   64.924943] Bluetooth: hci0: unexpected SMP command 0x0b from 
bc:82:5d:fa:5e:b7
  [   64.940314] NET: Registered protocol family 38
  [   65.022326] DBG: Received code 5 (allowed = 0024) with 1 bytes
  [   65.022331] DBG: Processing code...

  The "allowed" value is a bitmap, so 0024 means that only event
  code 2 and 5 are allowed. The "smp_sig_channel()" function does allow
  code 11 ("SMP_CMD_SECURITY_REQ") to be sent from the device at the
  beginning of the connection but *only* if the "smp" variable hasn't
  been set yet. It looks like the host starts the pairing process and
  initializes the "smp" variable, which then prevents code 11 from being
  allowed.

  I did try to force the code to allow code 11 at any time, but this
  didn't seem to help the situation any. The device still sent code 5
  ("SMP_CMD_PAIRING_FAIL") immediately afterwards, just like it does in
  the trace above. Worse, the kernel logs a general protection fault
  several seconds afterwards, so it clearly doesn't like the workaround.

  I also find it odd that the "AuthReq = 00". I found a copy of the core
  Bluetooth spec at https://www.bluetooth.com/specifications/bluetooth-
  core-specification and Vol. 3 Part H Chapter 3.6.7 describes the
  AuthReq flags. All zero would seem to indicate that no security is
  requested, and I'm not sure if the kernel enforces a minimum security
  level or something.

  Finally, I also tried the suggestion at 
https://www.raymondjdouglas.com/blog/2019/airpods-on-arch/  on the assumption 
that maybe this is an issue caused by LE communication rather than classic 
BR/EDR communication. Alas, my computer wasn't even able to start the pairing 
process after making the change.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-01-21 (70 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 9360
  Package: linux
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=c045330d-1b98-41ff-99cb-26bf69b59fd3 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-46-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh 

[Kernel-packages] [Bug 1822821] Re: TSC clocksource not available in nested guests

2019-04-02 Thread Heitor R. Alves de Siqueira
Patches submitted to kernel-team list:

Xenial - https://lists.ubuntu.com/archives/kernel-team/2019-April/099810.html
Bionic - https://lists.ubuntu.com/archives/kernel-team/2019-April/099813.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/1822821

Title:
  TSC clocksource not available in nested guests

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

Bug description:
  [Impact]
   * TSC clocksource not available in nested guests

  [Test Case]
   * Spin up a nested Xenial/Bionic guest and check for 'tsc' at
     /sys/devices/system/clocksource/clocksource0/available_clocksource

  [Regression Potential]
   * The regression potential is low. Upstream code still maintains this
     behaviour of skipping calibration on guests, and tsc code verifies if
     the frequency is known before registering the clocksource

   * Patches were verified against the above test case, and also tested
     with stress-ng in both nested and non-nested guest scenarios

  [Fix]
   * By applying the upstream commits [0] [1], we skip refined calibration and
     register TSC as a clocksource directly if its frequency is known (via
     MSR or CPUID)

   * Cosmic onwards (kernel 4.18+) are already fixed

  [0] For Xenial only - https://git.kernel.org/linus/47c95a46d0f
  [1] https://git.kernel.org/linus/e10f78050323

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

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


[Kernel-packages] [Bug 1822821] Re: TSC clocksource not available in nested guests

2019-04-02 Thread Heitor R. Alves de Siqueira
** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Heitor R. Alves de Siqueira (halves)

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Heitor R. 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/1822821

Title:
  TSC clocksource not available in nested guests

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

Bug description:
  [Impact]
   * TSC clocksource not available in nested guests

  [Test Case]
   * Spin up a nested Xenial/Bionic guest and check for 'tsc' at
     /sys/devices/system/clocksource/clocksource0/available_clocksource

  [Regression Potential]
   * The regression potential is low. Upstream code still maintains this
     behaviour of skipping calibration on guests, and tsc code verifies if
     the frequency is known before registering the clocksource

   * Patches were verified against the above test case, and also tested
     with stress-ng in both nested and non-nested guest scenarios

  [Fix]
   * By applying the upstream commits [0] [1], we skip refined calibration and
     register TSC as a clocksource directly if its frequency is known (via
     MSR or CPUID)

   * Cosmic onwards (kernel 4.18+) are already fixed

  [0] For Xenial only - https://git.kernel.org/linus/47c95a46d0f
  [1] https://git.kernel.org/linus/e10f78050323

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

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


[Kernel-packages] [Bug 1818881] Re: ath10k_pci crashing

2019-04-02 Thread Stephan Fabel
I've reset the machine with the latest OEM image to retest. I am now
experiencing system freezes at random times. I've generated a new
sosreport and am attaching it to this case.

** Attachment added: "SOS Report from OEM installed XPS 13 9380"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818881/+attachment/5252154/+files/sosreport-perseus-20190402103031.tar.xz

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

Title:
  ath10k_pci crashing

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  The below happens on a regular basis on my DELL XPS 13 9380:

  [77451.338493] RIP: 0010:ath10k_htt_rx_pop_paddr.isra.29+0xd9/0xf0 
[ath10k_core]
  [77451.338494] Code: 74 32 48 8b 87 10 02 00 00 48 85 c0 74 26 48 8b 40 28 48 
85 c0 74 17 45 31 c0 b9 02 00 00 00 e8 dd c1 d7 db 48 89 d8 5b 5d c3 <0f> 0b 31 
db 48 89 d8 5b 5d c3 48 8b 05 de 67 5a dc eb d1 0f 1f 40 
  [77451.338531] RSP: 0018:9d996e503d78 EFLAGS: 00010246
  [77451.338533] RAX:  RBX: 9d97b7c12290 RCX: 
9d96cbfd5528
  [77451.338534] RDX: 37af2804 RSI: 9d9944c51ed4 RDI: 
9d9944c51de0
  [77451.338535] RBP: 9d996e503d80 R08: 0020 R09: 

  [77451.338537] R10: 9d94f045ecd8 R11: 01ff R12: 
9d9944c51520
  [77451.338538] R13: 9d996e503e40 R14: 0040 R15: 
9d996e503e28
  [77451.338540] FS:  () GS:9d996e50() 
knlGS:
  [77451.338541] CS:  0010 DS:  ES:  CR0: 80050033
  [77451.338542] CR2: 1f1104c31000 CR3: 00017aa0a005 CR4: 
003606e0
  [77451.338543] Call Trace:
  [77451.338545]  
  [77451.338557]  ath10k_htt_txrx_compl_task+0x3d6/0xe40 [ath10k_core]
  [77451.338561]  ? ath10k_pci_irq_msi_fw_unmask+0x70/0x70 [ath10k_pci]
  [77451.338563]  ? ath10k_pci_wake.part.24+0xa0/0xa0 [ath10k_pci]
  [77451.338567]  ath10k_pci_napi_poll+0x54/0x110 [ath10k_pci]
  [77451.338571]  net_rx_action+0x140/0x3a0
  [77451.338575]  __do_softirq+0xe4/0x2d4
  [77451.338580]  irq_exit+0xc5/0xd0
  [77451.338582]  do_IRQ+0x8a/0xe0
  [77451.338585]  common_interrupt+0xf/0xf
  [77451.338586]  
  [77451.338589] RIP: 0010:cpuidle_enter_state+0xa5/0x2c0
  [77451.338590] Code: 8b 3d df bf 9d 63 e8 6a 09 89 ff 48 89 c3 0f 1f 44 00 00 
31 ff e8 cb 14 89 ff 45 84 ff 0f 85 c8 01 00 00 fb 66 0f 1f 44 00 00 <48> 2b 5d 
d0 48 ba cf f7 53 e3 a5 9b c4 20 48 89 d8 48 c1 fb 3f 48 
  [77451.338621] RSP: 0018:af4601993e50 EFLAGS: 0246 ORIG_RAX: 
ffde
  [77451.338623] RAX: 9d996e522c40 RBX: 46710b80e2b6 RCX: 
001f
  [77451.338624] RDX: 46710b80e2b6 RSI: 4041cc98 RDI: 

  [77451.338625] RBP: af4601993e90 R08: 0002 R09: 
000224c0
  [77451.338626] R10: af4601993e20 R11: 00d9 R12: 
0004
  [77451.338626] R13: 9d996e52ce00 R14: 9d3849f8 R15: 

  [77451.338630]  cpuidle_enter+0x17/0x20
  [77451.338632]  call_cpuidle+0x23/0x40
  [77451.338634]  do_idle+0x204/0x280
  [77451.338636]  cpu_startup_entry+0x73/0x80
  [77451.338639]  start_secondary+0x1ab/0x200
  [77451.338642]  secondary_startup_64+0xa5/0xb0
  [77451.338643] ---[ end trace 22914e3b3a848f81 ]---
  [77451.338655] ath10k_pci :02:00.0: failed to pop paddr list: -2

  $ uname -a
  Linux perseus 4.18.0-15-generic #16~18.04.1-Ubuntu SMP Thu Feb 7 14:06:04 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  $ modinfo ath10k_pci
  filename:   
/lib/modules/4.18.0-15-generic/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko
  firmware:   ath10k/QCA9377/hw1.0/board.bin
  firmware:   ath10k/QCA9377/hw1.0/firmware-5.bin
  firmware:   ath10k/QCA9377/hw1.0/firmware-6.bin
  firmware:   ath10k/QCA6174/hw3.0/board-2.bin
  firmware:   ath10k/QCA6174/hw3.0/board.bin
  firmware:   ath10k/QCA6174/hw3.0/firmware-6.bin
  firmware:   ath10k/QCA6174/hw3.0/firmware-5.bin
  firmware:   ath10k/QCA6174/hw3.0/firmware-4.bin
  firmware:   ath10k/QCA6174/hw2.1/board-2.bin
  firmware:   ath10k/QCA6174/hw2.1/board.bin
  firmware:   ath10k/QCA6174/hw2.1/firmware-5.bin
  firmware:   ath10k/QCA6174/hw2.1/firmware-4.bin
  firmware:   ath10k/QCA9887/hw1.0/board-2.bin
  firmware:   ath10k/QCA9887/hw1.0/board.bin
  firmware:   ath10k/QCA9887/hw1.0/firmware-5.bin
  firmware:   ath10k/QCA988X/hw2.0/board-2.bin
  firmware:   ath10k/QCA988X/hw2.0/board.bin
  firmware:   ath10k/QCA988X/hw2.0/firmware-5.bin
  firmware:   ath10k/QCA988X/hw2.0/firmware-4.bin
  firmware:   ath10k/QCA988X/hw2.0/firmware-3.bin
  firmware:   ath10k/QCA988X/hw2.0/firmware-2.bin
  license:Dual BSD/GPL
  description:Driver support for Qualcomm Atheros 802.11ac WLAN PCIe/AHB 
devices
  author: Qualcomm 

[Kernel-packages] [Bug 1787775] Re: touchpad not working on lenovo yoga 530

2019-04-02 Thread Lukas Wiest
tested on cosmic without mp2 dmks module and tochpad and screen are
working fine :)

Now only the wifi is with additional module and the screen flicker I
have is left for me.

Should I file a bug for this screen issue?
https://askubuntu.com/questions/1124286/cosmic-vega-8-screen-flicker-glitches

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

Title:
  touchpad not working on lenovo yoga 530

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  New
Status in linux source package in Disco:
  Confirmed

Bug description:
  === SRU Justification ===

  [Impact]
  AMD MP2 I2C driver doesn't support more than one bus.
  This makes touchpad on Lenovo Yoga 530 doensn't work as expected.

  [Fix]
  Sync the MP2 driver with upstream version.

  [Test]
  The new upstream driver doesn't break on Latitude 5495.
  Users haven't given any feedback yet, but since Disco is freezing I
  am sending this out.

  [Regression Potential]
  Low. It's from upstream, and only a subset of Raven Ridge has this
  device.

  === Original Bug Report ===

  The touchpad is not working and does not show up in cat
  /proc/bus/input/devices on multiple kernels. I've tried the newest
  kernel to date (19.08.18) and a few others.

  The touchpad works on windows.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-08-18 (0 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  Package: linux (not installed)
  Tags:  bionic
  Uname: Linux 4.18.3-041803-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to bionic on 2018-08-18 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Kernel-packages] [Bug 1818881] Re: ath10k_pci crashing

2019-04-02 Thread Alex Tu
shared more information from Stephan,
"
so just to be clear, I often times am able to stay on 5 hours on a Meet with no 
problem
then it just starts happening and I can't seem to get out of it
"

and the machine is also plugged AC power while meeting.

I also followed the way to test google hangout video call + youtube
playing over 6 hours on the same environment of #24 which the XPS 13 I
have, but no luck to reproduce that here so far.

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

Title:
  ath10k_pci crashing

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  The below happens on a regular basis on my DELL XPS 13 9380:

  [77451.338493] RIP: 0010:ath10k_htt_rx_pop_paddr.isra.29+0xd9/0xf0 
[ath10k_core]
  [77451.338494] Code: 74 32 48 8b 87 10 02 00 00 48 85 c0 74 26 48 8b 40 28 48 
85 c0 74 17 45 31 c0 b9 02 00 00 00 e8 dd c1 d7 db 48 89 d8 5b 5d c3 <0f> 0b 31 
db 48 89 d8 5b 5d c3 48 8b 05 de 67 5a dc eb d1 0f 1f 40 
  [77451.338531] RSP: 0018:9d996e503d78 EFLAGS: 00010246
  [77451.338533] RAX:  RBX: 9d97b7c12290 RCX: 
9d96cbfd5528
  [77451.338534] RDX: 37af2804 RSI: 9d9944c51ed4 RDI: 
9d9944c51de0
  [77451.338535] RBP: 9d996e503d80 R08: 0020 R09: 

  [77451.338537] R10: 9d94f045ecd8 R11: 01ff R12: 
9d9944c51520
  [77451.338538] R13: 9d996e503e40 R14: 0040 R15: 
9d996e503e28
  [77451.338540] FS:  () GS:9d996e50() 
knlGS:
  [77451.338541] CS:  0010 DS:  ES:  CR0: 80050033
  [77451.338542] CR2: 1f1104c31000 CR3: 00017aa0a005 CR4: 
003606e0
  [77451.338543] Call Trace:
  [77451.338545]  
  [77451.338557]  ath10k_htt_txrx_compl_task+0x3d6/0xe40 [ath10k_core]
  [77451.338561]  ? ath10k_pci_irq_msi_fw_unmask+0x70/0x70 [ath10k_pci]
  [77451.338563]  ? ath10k_pci_wake.part.24+0xa0/0xa0 [ath10k_pci]
  [77451.338567]  ath10k_pci_napi_poll+0x54/0x110 [ath10k_pci]
  [77451.338571]  net_rx_action+0x140/0x3a0
  [77451.338575]  __do_softirq+0xe4/0x2d4
  [77451.338580]  irq_exit+0xc5/0xd0
  [77451.338582]  do_IRQ+0x8a/0xe0
  [77451.338585]  common_interrupt+0xf/0xf
  [77451.338586]  
  [77451.338589] RIP: 0010:cpuidle_enter_state+0xa5/0x2c0
  [77451.338590] Code: 8b 3d df bf 9d 63 e8 6a 09 89 ff 48 89 c3 0f 1f 44 00 00 
31 ff e8 cb 14 89 ff 45 84 ff 0f 85 c8 01 00 00 fb 66 0f 1f 44 00 00 <48> 2b 5d 
d0 48 ba cf f7 53 e3 a5 9b c4 20 48 89 d8 48 c1 fb 3f 48 
  [77451.338621] RSP: 0018:af4601993e50 EFLAGS: 0246 ORIG_RAX: 
ffde
  [77451.338623] RAX: 9d996e522c40 RBX: 46710b80e2b6 RCX: 
001f
  [77451.338624] RDX: 46710b80e2b6 RSI: 4041cc98 RDI: 

  [77451.338625] RBP: af4601993e90 R08: 0002 R09: 
000224c0
  [77451.338626] R10: af4601993e20 R11: 00d9 R12: 
0004
  [77451.338626] R13: 9d996e52ce00 R14: 9d3849f8 R15: 

  [77451.338630]  cpuidle_enter+0x17/0x20
  [77451.338632]  call_cpuidle+0x23/0x40
  [77451.338634]  do_idle+0x204/0x280
  [77451.338636]  cpu_startup_entry+0x73/0x80
  [77451.338639]  start_secondary+0x1ab/0x200
  [77451.338642]  secondary_startup_64+0xa5/0xb0
  [77451.338643] ---[ end trace 22914e3b3a848f81 ]---
  [77451.338655] ath10k_pci :02:00.0: failed to pop paddr list: -2

  $ uname -a
  Linux perseus 4.18.0-15-generic #16~18.04.1-Ubuntu SMP Thu Feb 7 14:06:04 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  $ modinfo ath10k_pci
  filename:   
/lib/modules/4.18.0-15-generic/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko
  firmware:   ath10k/QCA9377/hw1.0/board.bin
  firmware:   ath10k/QCA9377/hw1.0/firmware-5.bin
  firmware:   ath10k/QCA9377/hw1.0/firmware-6.bin
  firmware:   ath10k/QCA6174/hw3.0/board-2.bin
  firmware:   ath10k/QCA6174/hw3.0/board.bin
  firmware:   ath10k/QCA6174/hw3.0/firmware-6.bin
  firmware:   ath10k/QCA6174/hw3.0/firmware-5.bin
  firmware:   ath10k/QCA6174/hw3.0/firmware-4.bin
  firmware:   ath10k/QCA6174/hw2.1/board-2.bin
  firmware:   ath10k/QCA6174/hw2.1/board.bin
  firmware:   ath10k/QCA6174/hw2.1/firmware-5.bin
  firmware:   ath10k/QCA6174/hw2.1/firmware-4.bin
  firmware:   ath10k/QCA9887/hw1.0/board-2.bin
  firmware:   ath10k/QCA9887/hw1.0/board.bin
  firmware:   ath10k/QCA9887/hw1.0/firmware-5.bin
  firmware:   ath10k/QCA988X/hw2.0/board-2.bin
  firmware:   ath10k/QCA988X/hw2.0/board.bin
  firmware:   ath10k/QCA988X/hw2.0/firmware-5.bin
  firmware:   ath10k/QCA988X/hw2.0/firmware-4.bin
  firmware:   ath10k/QCA988X/hw2.0/firmware-3.bin
  firmware:   ath10k/QCA988X/hw2.0/firmware-2.bin
  license:Dual BSD/GPL
  description:Driver support for Qualcomm Atheros 

[Kernel-packages] [Bug 1819707] Re: linux-fips: 4.15.0-1002.3 -proposed tracker

2019-04-02 Thread 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
  kernel-stable-master-bug: 1819716
  phase: Ready for Testing
  phase-changed: Tuesday, 02. April 2019 16:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
-   verification-testing: Pending -- Ready

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

Title:
  linux-fips: 4.15.0-1002.3 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
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-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Ready for Testing
  phase-changed: Tuesday, 02. April 2019 16:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress

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

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


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

2019-04-02 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  External monitor turns off for short period of times / until moving
  mouse

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In disco; I have this issue where my external monitor (a ThinkVision
  P24h-10) connected to my ThinkPad T480s turns off for short times
  while actively working on the system. I noticed that if I don't move
  my mouse at all while it's off, it stays off.

  The T480s is connected to the monitor via USB-C; the monitor provides
  DP, USB, and Power over that connection. When the display turns off,
  USB devices continue working.

  I have attached /sys/debug/dri/0 output from when the monitor was off
  (a) vs on (b).

  Other related bits:
  * This also happens on HDMI, but much less often
  * There are no log messages when the display turns on/off in the journal.

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

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


[Kernel-packages] [Bug 1822821] Re: TSC clocksource not available in nested guests

2019-04-02 Thread Heitor R. Alves de Siqueira
** Changed in: linux (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  TSC clocksource not available in nested guests

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

Bug description:
  [Impact]
   * TSC clocksource not available in nested guests

  [Test Case]
   * Spin up a nested Xenial/Bionic guest and check for 'tsc' at
     /sys/devices/system/clocksource/clocksource0/available_clocksource

  [Regression Potential]
   * The regression potential is low. Upstream code still maintains this
     behaviour of skipping calibration on guests, and tsc code verifies if
     the frequency is known before registering the clocksource

   * Patches were verified against the above test case, and also tested
     with stress-ng in both nested and non-nested guest scenarios

  [Fix]
   * By applying the upstream commits [0] [1], we skip refined calibration and
     register TSC as a clocksource directly if its frequency is known (via
     MSR or CPUID)

   * Cosmic onwards (kernel 4.18+) are already fixed

  [0] For Xenial only - https://git.kernel.org/linus/47c95a46d0f
  [1] https://git.kernel.org/linus/e10f78050323

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

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


[Kernel-packages] [Bug 1822854] Re: External monitor turns off for short period of times / until moving mouse

2019-04-02 Thread Julian Andres Klode
** Attachment added: "Display-off debug state"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822854/+attachment/5252138/+files/a

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

Title:
  External monitor turns off for short period of times / until moving
  mouse

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  In disco; I have this issue where my external monitor (a ThinkVision
  P24h-10) connected to my ThinkPad T480s turns off for short times
  while actively working on the system. I noticed that if I don't move
  my mouse at all while it's off, it stays off.

  The T480s is connected to the monitor via USB-C; the monitor provides
  DP, USB, and Power over that connection. When the display turns off,
  USB devices continue working.

  I have attached /sys/debug/dri/0 output from when the monitor was off
  (a) vs on (b).

  Other related bits:
  * This also happens on HDMI, but much less often
  * There are no log messages when the display turns on/off in the journal.

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

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


[Kernel-packages] [Bug 1822854] Re: External monitor turns off for short period of times / until moving mouse

2019-04-02 Thread Julian Andres Klode
Also, FYI: There are no log messages when the display turns on/off in
the journal.

** Description changed:

  In disco; I have this issue where my external monitor (a ThinkVision
  P24h-10) connected to my ThinkPad T480s turns off for short times while
  actively working on the system. I noticed that if I don't move my mouse
  at all while it's off, it stays off.
  
  The T480s is connected to the monitor via USB-C; the monitor provides
  DP, USB, and Power over that connection. When the display turns off, USB
  devices continue working.
  
  I have attached /sys/debug/dri/0 output from when the monitor was off
  (a) vs on (b).
+ 
+ Other related bits:
+ * This also happens on HDMI, but much less often
+ * There are no log messages when the display turns on/off in the journal.

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

Title:
  External monitor turns off for short period of times / until moving
  mouse

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  In disco; I have this issue where my external monitor (a ThinkVision
  P24h-10) connected to my ThinkPad T480s turns off for short times
  while actively working on the system. I noticed that if I don't move
  my mouse at all while it's off, it stays off.

  The T480s is connected to the monitor via USB-C; the monitor provides
  DP, USB, and Power over that connection. When the display turns off,
  USB devices continue working.

  I have attached /sys/debug/dri/0 output from when the monitor was off
  (a) vs on (b).

  Other related bits:
  * This also happens on HDMI, but much less often
  * There are no log messages when the display turns on/off in the journal.

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

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


[Kernel-packages] [Bug 1822854] Re: External monitor turns off for short period of times / until moving mouse

2019-04-02 Thread Julian Andres Klode
** Attachment added: "Display-on debug state (b)"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822854/+attachment/5252139/+files/b

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

Title:
  External monitor turns off for short period of times / until moving
  mouse

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  In disco; I have this issue where my external monitor (a ThinkVision
  P24h-10) connected to my ThinkPad T480s turns off for short times
  while actively working on the system. I noticed that if I don't move
  my mouse at all while it's off, it stays off.

  The T480s is connected to the monitor via USB-C; the monitor provides
  DP, USB, and Power over that connection. When the display turns off,
  USB devices continue working.

  I have attached /sys/debug/dri/0 output from when the monitor was off
  (a) vs on (b).

  Other related bits:
  * This also happens on HDMI, but much less often
  * There are no log messages when the display turns on/off in the journal.

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

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


[Kernel-packages] [Bug 1822854] Re: External monitor turns off for short period of times / until moving mouse

2019-04-02 Thread Julian Andres Klode
Interesting (?) difference between the i915 debug files:

--- display off
+++ display on
-  Active context: [0] user_handle 0 hw_id 0, prio 0, ban score 0 (unbannable) 
guilty 0 active 0 
+  ELSP[0]:  pid 12429, ban score 0, seqno5:010cd84c, prio 0, emitted 
0ms, start 00e21000, head 3c50, tail 3cd8  
+  Active context: Xorg[12429] user_handle 1 hw_id 5, prio 0, ban score 0 
guilty 0 active 0

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

Title:
  External monitor turns off for short period of times / until moving
  mouse

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  In disco; I have this issue where my external monitor (a ThinkVision
  P24h-10) connected to my ThinkPad T480s turns off for short times
  while actively working on the system. I noticed that if I don't move
  my mouse at all while it's off, it stays off.

  The T480s is connected to the monitor via USB-C; the monitor provides
  DP, USB, and Power over that connection. When the display turns off,
  USB devices continue working.

  I have attached /sys/debug/dri/0 output from when the monitor was off
  (a) vs on (b).

  Other related bits:
  * This also happens on HDMI, but much less often
  * There are no log messages when the display turns on/off in the journal.

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

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


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

2019-04-02 Thread Julian Andres Klode
apport information

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

Title:
  External monitor turns off for short period of times / until moving
  mouse

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  In disco; I have this issue where my external monitor (a ThinkVision
  P24h-10) connected to my ThinkPad T480s turns off for short times
  while actively working on the system. I noticed that if I don't move
  my mouse at all while it's off, it stays off.

  The T480s is connected to the monitor via USB-C; the monitor provides
  DP, USB, and Power over that connection. When the display turns off,
  USB devices continue working.

  I have attached /sys/debug/dri/0 output from when the monitor was off
  (a) vs on (b).

  Other related bits:
  * This also happens on HDMI, but much less often
  * There are no log messages when the display turns on/off in the journal.

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

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


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

2019-04-02 Thread Julian Andres Klode
apport information

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

** Description changed:

- I have this issue where my external monitor (a ThinkVision P24h-10)
- connected to my ThinkPad T480s turns off for short times while actively
- working on the system. I noticed that if I don't move my mouse at all
- while it's off, it stays off.
+ In disco; I have this issue where my external monitor (a ThinkVision
+ P24h-10) connected to my ThinkPad T480s turns off for short times while
+ actively working on the system. I noticed that if I don't move my mouse
+ at all while it's off, it stays off.
  
  The T480s is connected to the monitor via USB-C; the monitor provides
  DP, USB, and Power over that connection. When the display turns off, USB
  devices continue working.
  
- I have attached /sys/debug/dri/0 output from when the monitor was off (a) vs 
on (b).
- --- 
- ProblemType: Bug
- ApportVersion: 2.20.10-0ubuntu23
- Architecture: amd64
- AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC2:  jak   17606 F pulseaudio
-  /dev/snd/controlC1:  jak   17606 F pulseaudio
-  /dev/snd/controlC0:  jak   17606 F pulseaudio
- CurrentDesktop: GNOME
- DistroRelease: Ubuntu 19.04
- InstallationDate: Installed on 2018-03-14 (383 days ago)
- InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
- MachineType: LENOVO 20L8S02D00
- Package: linux (not installed)
- ProcFB: 0 inteldrmfb
- ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic 
root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ quiet splash 
i915.enable_gvt=1 intel_iommu=on vt.handoff=1
- ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
- RelatedPackageVersions:
-  linux-restricted-modules-5.0.0-7-generic N/A
-  linux-backports-modules-5.0.0-7-generic  N/A
-  linux-firmware   1.178
- Tags:  disco
- Uname: Linux 5.0.0-7-generic x86_64
- UpgradeStatus: Upgraded to disco on 2018-11-20 (133 days ago)
- UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sbuild 
sudo
- _MarkForUpload: True
- dmi.bios.date: 02/19/2019
- dmi.bios.vendor: LENOVO
- dmi.bios.version: N22ET53W (1.30 )
- dmi.board.asset.tag: Not Available
- dmi.board.name: 20L8S02D00
- dmi.board.vendor: LENOVO
- dmi.board.version: Not Defined
- dmi.chassis.asset.tag: No Asset Information
- dmi.chassis.type: 10
- dmi.chassis.vendor: LENOVO
- dmi.chassis.version: None
- dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET53W(1.30):bd02/19/2019:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
- dmi.product.family: ThinkPad T480s
- dmi.product.name: 20L8S02D00
- dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s
- dmi.product.version: ThinkPad T480s
- dmi.sys.vendor: LENOVO
+ I have attached /sys/debug/dri/0 output from when the monitor was off
+ (a) vs on (b).

** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  External monitor turns off for short period of times / until moving
  mouse

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  In disco; I have this issue where my external monitor (a ThinkVision
  P24h-10) connected to my ThinkPad T480s turns off for short times
  while actively working on the system. I noticed that if I don't move
  my mouse at all while it's off, it stays off.

  The T480s is connected to the monitor via USB-C; the monitor provides
  DP, USB, and Power over that connection. When the display turns off,
  USB devices continue working.

  I have attached /sys/debug/dri/0 output from when the monitor was off
  (a) vs on (b).

  Other related bits:
  * This also happens on HDMI, but much less often
  * There are no log messages when the display turns on/off in the journal.

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

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


[Kernel-packages] [Bug 1822854] Re: External monitor turns off for short period of times / until moving mouse

2019-04-02 Thread Julian Andres Klode
** Attachment added: "head of dmesg (journalctl -k) for that boot"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822854/+attachment/5252140/+files/dmesg-boot.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/1822854

Title:
  External monitor turns off for short period of times / until moving
  mouse

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  In disco; I have this issue where my external monitor (a ThinkVision
  P24h-10) connected to my ThinkPad T480s turns off for short times
  while actively working on the system. I noticed that if I don't move
  my mouse at all while it's off, it stays off.

  The T480s is connected to the monitor via USB-C; the monitor provides
  DP, USB, and Power over that connection. When the display turns off,
  USB devices continue working.

  I have attached /sys/debug/dri/0 output from when the monitor was off
  (a) vs on (b).

  Other related bits:
  * This also happens on HDMI, but much less often
  * There are no log messages when the display turns on/off in the journal.

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

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


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

2019-04-02 Thread Julian Andres Klode
apport information

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

Title:
  External monitor turns off for short period of times / until moving
  mouse

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  In disco; I have this issue where my external monitor (a ThinkVision
  P24h-10) connected to my ThinkPad T480s turns off for short times
  while actively working on the system. I noticed that if I don't move
  my mouse at all while it's off, it stays off.

  The T480s is connected to the monitor via USB-C; the monitor provides
  DP, USB, and Power over that connection. When the display turns off,
  USB devices continue working.

  I have attached /sys/debug/dri/0 output from when the monitor was off
  (a) vs on (b).

  Other related bits:
  * This also happens on HDMI, but much less often
  * There are no log messages when the display turns on/off in the journal.

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

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


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

2019-04-02 Thread Julian Andres Klode
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1822854/+attachment/5252128/+files/Lsusb.txt

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

Title:
  External monitor turns off for short period of times / until moving
  mouse

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  In disco; I have this issue where my external monitor (a ThinkVision
  P24h-10) connected to my ThinkPad T480s turns off for short times
  while actively working on the system. I noticed that if I don't move
  my mouse at all while it's off, it stays off.

  The T480s is connected to the monitor via USB-C; the monitor provides
  DP, USB, and Power over that connection. When the display turns off,
  USB devices continue working.

  I have attached /sys/debug/dri/0 output from when the monitor was off
  (a) vs on (b).

  Other related bits:
  * This also happens on HDMI, but much less often
  * There are no log messages when the display turns on/off in the journal.

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

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


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

2019-04-02 Thread Julian Andres Klode
apport information

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

Title:
  External monitor turns off for short period of times / until moving
  mouse

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  In disco; I have this issue where my external monitor (a ThinkVision
  P24h-10) connected to my ThinkPad T480s turns off for short times
  while actively working on the system. I noticed that if I don't move
  my mouse at all while it's off, it stays off.

  The T480s is connected to the monitor via USB-C; the monitor provides
  DP, USB, and Power over that connection. When the display turns off,
  USB devices continue working.

  I have attached /sys/debug/dri/0 output from when the monitor was off
  (a) vs on (b).

  Other related bits:
  * This also happens on HDMI, but much less often
  * There are no log messages when the display turns on/off in the journal.

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

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


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

2019-04-02 Thread Julian Andres Klode
apport information

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

Title:
  External monitor turns off for short period of times / until moving
  mouse

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  In disco; I have this issue where my external monitor (a ThinkVision
  P24h-10) connected to my ThinkPad T480s turns off for short times
  while actively working on the system. I noticed that if I don't move
  my mouse at all while it's off, it stays off.

  The T480s is connected to the monitor via USB-C; the monitor provides
  DP, USB, and Power over that connection. When the display turns off,
  USB devices continue working.

  I have attached /sys/debug/dri/0 output from when the monitor was off
  (a) vs on (b).

  Other related bits:
  * This also happens on HDMI, but much less often
  * There are no log messages when the display turns on/off in the journal.

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

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


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

2019-04-02 Thread Julian Andres Klode
apport information

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

Title:
  External monitor turns off for short period of times / until moving
  mouse

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  In disco; I have this issue where my external monitor (a ThinkVision
  P24h-10) connected to my ThinkPad T480s turns off for short times
  while actively working on the system. I noticed that if I don't move
  my mouse at all while it's off, it stays off.

  The T480s is connected to the monitor via USB-C; the monitor provides
  DP, USB, and Power over that connection. When the display turns off,
  USB devices continue working.

  I have attached /sys/debug/dri/0 output from when the monitor was off
  (a) vs on (b).

  Other related bits:
  * This also happens on HDMI, but much less often
  * There are no log messages when the display turns on/off in the journal.

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

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


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

2019-04-02 Thread Julian Andres Klode
apport information

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

Title:
  External monitor turns off for short period of times / until moving
  mouse

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  In disco; I have this issue where my external monitor (a ThinkVision
  P24h-10) connected to my ThinkPad T480s turns off for short times
  while actively working on the system. I noticed that if I don't move
  my mouse at all while it's off, it stays off.

  The T480s is connected to the monitor via USB-C; the monitor provides
  DP, USB, and Power over that connection. When the display turns off,
  USB devices continue working.

  I have attached /sys/debug/dri/0 output from when the monitor was off
  (a) vs on (b).

  Other related bits:
  * This also happens on HDMI, but much less often
  * There are no log messages when the display turns on/off in the journal.

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

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


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

2019-04-02 Thread Julian Andres Klode
apport information

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

Title:
  External monitor turns off for short period of times / until moving
  mouse

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  In disco; I have this issue where my external monitor (a ThinkVision
  P24h-10) connected to my ThinkPad T480s turns off for short times
  while actively working on the system. I noticed that if I don't move
  my mouse at all while it's off, it stays off.

  The T480s is connected to the monitor via USB-C; the monitor provides
  DP, USB, and Power over that connection. When the display turns off,
  USB devices continue working.

  I have attached /sys/debug/dri/0 output from when the monitor was off
  (a) vs on (b).

  Other related bits:
  * This also happens on HDMI, but much less often
  * There are no log messages when the display turns on/off in the journal.

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

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


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

2019-04-02 Thread Julian Andres Klode
apport information

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

Title:
  External monitor turns off for short period of times / until moving
  mouse

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  In disco; I have this issue where my external monitor (a ThinkVision
  P24h-10) connected to my ThinkPad T480s turns off for short times
  while actively working on the system. I noticed that if I don't move
  my mouse at all while it's off, it stays off.

  The T480s is connected to the monitor via USB-C; the monitor provides
  DP, USB, and Power over that connection. When the display turns off,
  USB devices continue working.

  I have attached /sys/debug/dri/0 output from when the monitor was off
  (a) vs on (b).

  Other related bits:
  * This also happens on HDMI, but much less often
  * There are no log messages when the display turns on/off in the journal.

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

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


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

2019-04-02 Thread Julian Andres Klode
apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1822854/+attachment/5252135/+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/1822854

Title:
  External monitor turns off for short period of times / until moving
  mouse

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  In disco; I have this issue where my external monitor (a ThinkVision
  P24h-10) connected to my ThinkPad T480s turns off for short times
  while actively working on the system. I noticed that if I don't move
  my mouse at all while it's off, it stays off.

  The T480s is connected to the monitor via USB-C; the monitor provides
  DP, USB, and Power over that connection. When the display turns off,
  USB devices continue working.

  I have attached /sys/debug/dri/0 output from when the monitor was off
  (a) vs on (b).

  Other related bits:
  * This also happens on HDMI, but much less often
  * There are no log messages when the display turns on/off in the journal.

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

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


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

2019-04-02 Thread Julian Andres Klode
apport information

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

Title:
  External monitor turns off for short period of times / until moving
  mouse

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  In disco; I have this issue where my external monitor (a ThinkVision
  P24h-10) connected to my ThinkPad T480s turns off for short times
  while actively working on the system. I noticed that if I don't move
  my mouse at all while it's off, it stays off.

  The T480s is connected to the monitor via USB-C; the monitor provides
  DP, USB, and Power over that connection. When the display turns off,
  USB devices continue working.

  I have attached /sys/debug/dri/0 output from when the monitor was off
  (a) vs on (b).

  Other related bits:
  * This also happens on HDMI, but much less often
  * There are no log messages when the display turns on/off in the journal.

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

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


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

2019-04-02 Thread Julian Andres Klode
apport information

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

Title:
  External monitor turns off for short period of times / until moving
  mouse

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  In disco; I have this issue where my external monitor (a ThinkVision
  P24h-10) connected to my ThinkPad T480s turns off for short times
  while actively working on the system. I noticed that if I don't move
  my mouse at all while it's off, it stays off.

  The T480s is connected to the monitor via USB-C; the monitor provides
  DP, USB, and Power over that connection. When the display turns off,
  USB devices continue working.

  I have attached /sys/debug/dri/0 output from when the monitor was off
  (a) vs on (b).

  Other related bits:
  * This also happens on HDMI, but much less often
  * There are no log messages when the display turns on/off in the journal.

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

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


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

2019-04-02 Thread Julian Andres Klode
apport information

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

Title:
  External monitor turns off for short period of times / until moving
  mouse

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  In disco; I have this issue where my external monitor (a ThinkVision
  P24h-10) connected to my ThinkPad T480s turns off for short times
  while actively working on the system. I noticed that if I don't move
  my mouse at all while it's off, it stays off.

  The T480s is connected to the monitor via USB-C; the monitor provides
  DP, USB, and Power over that connection. When the display turns off,
  USB devices continue working.

  I have attached /sys/debug/dri/0 output from when the monitor was off
  (a) vs on (b).

  Other related bits:
  * This also happens on HDMI, but much less often
  * There are no log messages when the display turns on/off in the journal.

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

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


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

2019-04-02 Thread Julian Andres Klode
apport information

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

Title:
  External monitor turns off for short period of times / until moving
  mouse

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  In disco; I have this issue where my external monitor (a ThinkVision
  P24h-10) connected to my ThinkPad T480s turns off for short times
  while actively working on the system. I noticed that if I don't move
  my mouse at all while it's off, it stays off.

  The T480s is connected to the monitor via USB-C; the monitor provides
  DP, USB, and Power over that connection. When the display turns off,
  USB devices continue working.

  I have attached /sys/debug/dri/0 output from when the monitor was off
  (a) vs on (b).

  Other related bits:
  * This also happens on HDMI, but much less often
  * There are no log messages when the display turns on/off in the journal.

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

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


[Kernel-packages] [Bug 1822854] [NEW] External monitor turns off for short period of times / until moving mouse

2019-04-02 Thread Julian Andres Klode
Public bug reported:

In disco; I have this issue where my external monitor (a ThinkVision
P24h-10) connected to my ThinkPad T480s turns off for short times while
actively working on the system. I noticed that if I don't move my mouse
at all while it's off, it stays off.

The T480s is connected to the monitor via USB-C; the monitor provides
DP, USB, and Power over that connection. When the display turns off, USB
devices continue working.

I have attached /sys/debug/dri/0 output from when the monitor was off
(a) vs on (b).

Other related bits:
* This also happens on HDMI, but much less often
* There are no log messages when the display turns on/off in the journal.

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New

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


** Tags: apport-collected disco

** Tags added: apport-collected disco

** Description changed:

  I have this issue where my external monitor (a ThinkVision P24h-10)
  connected to my ThinkPad T480s turns off for short times while actively
  working on the system. I noticed that if I don't move my mouse at all
  while it's off, it stays off.
  
  The T480s is connected to the monitor via USB-C; the monitor provides
  DP, USB, and Power over that connection. When the display turns off, USB
  devices continue working.
  
- I have attached /sys/debug/dri/0 output from when the monitor was off
- (a) vs on (b).
+ I have attached /sys/debug/dri/0 output from when the monitor was off (a) vs 
on (b).
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu23
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC2:  jak   17606 F pulseaudio
+  /dev/snd/controlC1:  jak   17606 F pulseaudio
+  /dev/snd/controlC0:  jak   17606 F pulseaudio
+ CurrentDesktop: GNOME
+ DistroRelease: Ubuntu 19.04
+ InstallationDate: Installed on 2018-03-14 (383 days ago)
+ InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
+ MachineType: LENOVO 20L8S02D00
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic 
root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ quiet splash 
i915.enable_gvt=1 intel_iommu=on vt.handoff=1
+ ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
+ RelatedPackageVersions:
+  linux-restricted-modules-5.0.0-7-generic N/A
+  linux-backports-modules-5.0.0-7-generic  N/A
+  linux-firmware   1.178
+ Tags:  disco
+ Uname: Linux 5.0.0-7-generic x86_64
+ UpgradeStatus: Upgraded to disco on 2018-11-20 (133 days ago)
+ UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sbuild 
sudo
+ _MarkForUpload: True
+ dmi.bios.date: 02/19/2019
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: N22ET53W (1.30 )
+ dmi.board.asset.tag: Not Available
+ dmi.board.name: 20L8S02D00
+ dmi.board.vendor: LENOVO
+ dmi.board.version: Not Defined
+ dmi.chassis.asset.tag: No Asset Information
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: None
+ dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET53W(1.30):bd02/19/2019:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
+ dmi.product.family: ThinkPad T480s
+ dmi.product.name: 20L8S02D00
+ dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s
+ dmi.product.version: ThinkPad T480s
+ dmi.sys.vendor: LENOVO

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

Title:
  External monitor turns off for short period of times / until moving
  mouse

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  In disco; I have this issue where my external monitor (a ThinkVision
  P24h-10) connected to my ThinkPad T480s turns off for short times
  while actively working on the system. I noticed that if I don't move
  my mouse at all while it's off, it stays off.

  The T480s is connected to the monitor via USB-C; the monitor provides
  DP, USB, and Power over that connection. When the display turns off,
  USB devices continue working.

  I have attached /sys/debug/dri/0 output from when the monitor was off
  (a) vs on (b).

  Other related bits:
  * This also happens on HDMI, but much less often
  * There are no log messages when the display turns on/off in the journal.

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

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


[Kernel-packages] [Bug 1819707] Re: linux-fips: 4.15.0-1002.3 -proposed tracker

2019-04-02 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-signing-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Fix Released

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

** 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
  kernel-stable-master-bug: 1819716
- phase: Promote to Proposed
- phase-changed: Tuesday, 02. April 2019 15:13 UTC
+ phase: Ready for Testing
+ phase-changed: Tuesday, 02. April 2019 16:35 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-signing-to-proposed: Ongoing -- packages waiting in -proposed for 
mirror
- sync
+   regression-testing: Ongoing -- testing in progress
+   verification-testing: Pending -- Ready

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

Title:
  linux-fips: 4.15.0-1002.3 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
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-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Ready for Testing
  phase-changed: Tuesday, 02. April 2019 16:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
verification-testing: Pending -- Ready

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

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


  1   2   3   4   5   6   >