[Kernel-packages] [Bug 1804160] [NEW] package linux-image-4.15.0-38-generic 4.15.0-38.41 failed to install/upgrade: Unterprozess installed linux-image-4.15.0-38-generic package pre-removal script gab

[Martin Schaaf]

Public bug reported:

On upgrading the system it failed to remove the old kernel image.
There is no reason displayed for the error.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-38-generic 4.15.0-38.41
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
NonfreeKernelModules: qnx4 hfsplus hfs minix ntfs jfs rfcomm pci_stub 
thunderbolt bnep snd_hda_codec_hdmi wl intel_rapl x86_pkg_temp_thermal 
ath10k_pci intel_powerclamp ath10k_core coretemp ath btusb hid_multitouch 
mac80211 btrtl btbcm dell_laptop dell_wmi dell_smbios_smm dell_smbios_wmi 
uvcvideo dell_smbios videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core wmi_bmof btintel bluetooth videodev dcdbas dell_wmi_descriptor 
intel_wmi_thunderbolt rtsx_pci_ms memstick cfg80211 dell_smm_hwmon media 
mxm_wmi snd_hda_codec_realtek snd_hda_codec_generic intel_cstate snd_hda_intel 
snd_hda_codec snd_hda_core idma64 virt_dma intel_rapl_perf 
processor_thermal_device shpchp intel_soc_dts_iosf intel_lpss_pci mei_me 
intel_pch_thermal mei intel_lpss int3400_thermal acpi_thermal_rel 
int3403_thermal mac_hid intel_hid int340x_thermal_zone sparse_keymap wmi 
reiserfs nvidia_modeset i915 nvidia rtsx_pci_sdmmc rtsx_pci i2c_hid
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm2086 F pulseaudio
  ms 4158 F pulseaudio
Date: Tue Nov 20 08:31:46 2018
ErrorMessage: Unterprozess installed linux-image-4.15.0-38-generic package 
pre-removal script gab den Fehler-Ausgangsstatus 1 zurück
HibernationDevice: RESUME=UUID=4f44d3fa-bd29-4146-b0fa-e432c25736da
InstallationDate: Installed on 2010-11-01 (2940 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
Lsusb:
 Bus 002 Device 002: ID 152d:0578 JMicron Technology Corp. / JMicron USA 
Technology Corp. 
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. 
 Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 15 9560
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-38-generic 
root=UUID=ed779b00-1c51-4110-8f04-0c0dbec6bad1 ro quiet splash vt.handoff=7 
initrd=boot\initrd.img-4.15.0-38-generic
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions: grub-pc 2.02-2ubuntu8.7
SourcePackage: linux
Title: package linux-image-4.15.0-38-generic 4.15.0-38.41 failed to 
install/upgrade: Unterprozess installed linux-image-4.15.0-38-generic package 
pre-removal script gab den Fehler-Ausgangsstatus 1 zurück
UpgradeStatus: Upgraded to bionic on 2018-10-25 (26 days ago)
dmi.bios.date: 08/30/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.5.0
dmi.board.name: 05FFDN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9560
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-package bionic

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

Title:
  package linux-image-4.15.0-38-generic 4.15.0-38.41 failed to
  install/upgrade: Unterprozess installed linux-image-4.15.0-38-generic
  package pre-removal script gab den Fehler-Ausgangsstatus 1 zurück

Status in linux package in Ubuntu:
  New

Bug description:
  On upgrading the system it failed to remove the old kernel image.
  There is no reason displayed for the error.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-38-generic 4.15.0-38.41
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  NonfreeKernelModules: qnx4 hfsplus hfs minix ntfs jfs rfcomm pci_stub 
thunderbolt bnep snd_hda_codec_hdmi wl intel_rapl x86_pkg_temp_thermal 
ath10k_pci intel_powerclamp ath10k_core coretemp ath btusb hid_multitouch 
mac80211 btrtl btbcm dell_laptop dell_wmi dell_smbios_smm dell_smbios_wmi 
uvcvideo dell_smbios videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core wmi_bmof btintel bluetooth videodev dcdbas dell_wmi_descriptor 
intel_wmi_thunderbolt rtsx_pci_ms memstick cfg80211 dell_smm_hwmon media 
mxm_wmi snd_hda_codec_realtek snd_hda_codec_generic intel_cstate snd_hda_intel 
snd_hda_codec snd_hda_core idma64 

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

[bugproxy]

--- Comment From boris_fiuczyn...@de.ibm.com 2018-11-20 02:26 EDT---
I forgot to mention that with the patches provided in the tar.gz I was able to 
successfully run a guest with guest-dedicated crypto adapters.

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

Title:
  [FEAT] Guest-dedicated Crypto Adapters

Status in Ubuntu on IBM z Systems:
  In Progress
Status in libvirt package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in qemu package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  == SRU Justification ==

  (Kernel SRU)

  Allow kvm to dedicate crypto adapters (and domains) as passthrough devices to 
a KVM guest such that the hypervisor cannot observe the communication of the 
guest with the device.
  (Since all kernel patches/commits are from kernel 4.19, they will 
automagically land in 'Disco'.)

  == Fix ==

  9ea5972 ("KVM: s390: vsie: simulate VCPU SIE entry/exit")
  3194cdb ("KVM: s390: introduce and use KVM_REQ_VSIE_RESTART")
  e585b24 ("KVM: s390: refactor crypto initialization")
  1fde573 ("s390: vfio-ap: base implementation of VFIO AP device driver")
  65f0671 ("s390: vfio-ap: register matrix device with VFIO mdev framework")
  96d152b ("s390: vfio-ap: sysfs interfaces to configure adapters")
  3211da0 ("s390: vfio-ap: sysfs interfaces to configure domains")
  3b1eab7 ("s390: vfio-ap: sysfs interfaces to configure control domains")
  81b2b4b ("s390: vfio-ap: sysfs interface to view matrix mdev matrix")
  4210459 ("KVM: s390: interface to clear CRYCB masks")
  258287c ("s390: vfio-ap: implement mediated device open callback")
  e06670c ("s390: vfio-ap: implement VFIO_DEVICE_GET_INFO ioctl")
  46a7263 ("s390: vfio-ap: zeroize the AP queues")
  cd8a377 ("s390: vfio-ap: implement VFIO_DEVICE_RESET ioctl")
  6cc571b ("KVM: s390: Clear Crypto Control Block when using vSIE")
  d6f6959 ("KVM: s390: vsie: Do the CRYCB validation first")
  3af84de ("KVM: s390: vsie: Make use of CRYCB FORMAT2 clear")
  56019f9 ("KVM: s390: vsie: Allow CRYCB FORMAT-2")
  19fd83a ("KVM: s390: vsie: allow CRYCB FORMAT-1")
  6ee7409 ("KVM: s390: vsie: allow CRYCB FORMAT-0")
  c9ba8c2 ("KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-1")
  6b79de4 ("KVM: s390: vsie: allow guest FORMAT-1 CRYCB on host FORMAT-2")
  9ee71f2 ("KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-2")
  37940fb ("KVM: s390: device attrs to enable/disable AP interpretation")
  112c24d ("KVM: s390: CPU model support for AP virtualization")
  492a6be ("s390: doc: detailed specifications for AP virtualization")

  <-- till here in 'kvm/next'
  (https://git.kernel.org/pub/scm/virt/kvm/kvm.git/) -->

  8e41bd5 ("KVM: s390: fix locking for crypto setting error path")
  0e237e4 ("KVM: s390: Tracing APCB changes")
  76c7829 ("s390: vfio-ap: setup APCB mask using KVM dedicated function")

  <-- till here in 'kvms390/next'
  (https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git/)
  -->

  <-- In addition to that some prereqs for the 'ap/crypto' driver are
  necessary -->

  ea3c418 ("s390/zcrypt: Add ZAPQ inline function.")
  df80c03 ("s390/zcrypt: Review inline assembler constraints.")
  f1b0a43 ("s390/zcrypt: Integrate ap_asm.h into include/asm/ap.h.")
  2395103 ("s390/zcrypt: fix ap_instructions_available() returncodes")
  7e0bdbe ("s390/zcrypt: AP bus support for alternate driver(s)")
  3d8f60d3 ("s390/zcrypt: hex string mask improvements for apmask and aqmask.")
  fa108f9 ("s390/zcrypt: remove VLA usage from the AP bus")

  <--
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787405/comments/12
  -->

  == PATCH ==

  Above git commits are all from 4.19.
  The git commands for 4.18 would be:

  $ git cherry-pick 

  (112c24d "KVM: s390: CPU model support for AP virtualization" may have
  a trivial merge conflict with the etoken patch)

  $ git cherry-pick 

  $ git cherry-pick 

  == Regression Potential ==

  Low to mid:

  - mid because in summary there are a lot of changes, but low
  - they are all limited to the s390x architecture
  - and again limited to KVM/s390x, vfio-ap and the zcrypt (aka ap) driver
  - Test kernel was built for testting.

  == Test Case ==

  Setup a system for KVM use on an s390x LPAR that has CryptoExpress (aka 
crypto-) adapters installed.
  Verify that the AP bus created a sysfs device for each APQN, like:
  /sys/devices/ap/card04/04.0006
  /sys/devices/ap/card04/04.0047
  /sys/devices/ap/card0a/0a.0006
  /sys/devices/ap/card0a/0a.0047
  Verify the APQN range via the following two sysfs files:
  /sys/bus/ap/apmask
  /sys/bus/ap/aqmask
  Configure and start a guest.
  More details see: 492a6be ("s390: doc: detailed specifications for AP 
virtualization")
 

[Kernel-packages] [Bug 1787405] libvirt patches for vfio-ap support

[bugproxy]

--- Comment on attachment From boris_fiuczyn...@de.ibm.com 2018-11-20 02:21 
EDT---


This file contains the changes required for the vfio-ap support in libvirt 
based on the code level Christian Erhard provided in comment 62.
The list of required backported code needed to be extended and the second patch 
Christian provided required some changes.

It also turned out that appamor prevents access to the vfio-ap devices
located in /dev/vfio/*. I changed (hacked) the patch for LP1775777 to
bypass the problem temporally. This certainly needs to be adjusted in
the correct way which I am not certain of.

** Attachment added: "libvirt patches for vfio-ap support"
   
https://bugs.launchpad.net/bugs/1787405/+attachment/5214397/+files/libvirt-4.0.0-bionic_vfio-ap.tar.gz

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

Title:
  [FEAT] Guest-dedicated Crypto Adapters

Status in Ubuntu on IBM z Systems:
  In Progress
Status in libvirt package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in qemu package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  == SRU Justification ==

  (Kernel SRU)

  Allow kvm to dedicate crypto adapters (and domains) as passthrough devices to 
a KVM guest such that the hypervisor cannot observe the communication of the 
guest with the device.
  (Since all kernel patches/commits are from kernel 4.19, they will 
automagically land in 'Disco'.)

  == Fix ==

  9ea5972 ("KVM: s390: vsie: simulate VCPU SIE entry/exit")
  3194cdb ("KVM: s390: introduce and use KVM_REQ_VSIE_RESTART")
  e585b24 ("KVM: s390: refactor crypto initialization")
  1fde573 ("s390: vfio-ap: base implementation of VFIO AP device driver")
  65f0671 ("s390: vfio-ap: register matrix device with VFIO mdev framework")
  96d152b ("s390: vfio-ap: sysfs interfaces to configure adapters")
  3211da0 ("s390: vfio-ap: sysfs interfaces to configure domains")
  3b1eab7 ("s390: vfio-ap: sysfs interfaces to configure control domains")
  81b2b4b ("s390: vfio-ap: sysfs interface to view matrix mdev matrix")
  4210459 ("KVM: s390: interface to clear CRYCB masks")
  258287c ("s390: vfio-ap: implement mediated device open callback")
  e06670c ("s390: vfio-ap: implement VFIO_DEVICE_GET_INFO ioctl")
  46a7263 ("s390: vfio-ap: zeroize the AP queues")
  cd8a377 ("s390: vfio-ap: implement VFIO_DEVICE_RESET ioctl")
  6cc571b ("KVM: s390: Clear Crypto Control Block when using vSIE")
  d6f6959 ("KVM: s390: vsie: Do the CRYCB validation first")
  3af84de ("KVM: s390: vsie: Make use of CRYCB FORMAT2 clear")
  56019f9 ("KVM: s390: vsie: Allow CRYCB FORMAT-2")
  19fd83a ("KVM: s390: vsie: allow CRYCB FORMAT-1")
  6ee7409 ("KVM: s390: vsie: allow CRYCB FORMAT-0")
  c9ba8c2 ("KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-1")
  6b79de4 ("KVM: s390: vsie: allow guest FORMAT-1 CRYCB on host FORMAT-2")
  9ee71f2 ("KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-2")
  37940fb ("KVM: s390: device attrs to enable/disable AP interpretation")
  112c24d ("KVM: s390: CPU model support for AP virtualization")
  492a6be ("s390: doc: detailed specifications for AP virtualization")

  <-- till here in 'kvm/next'
  (https://git.kernel.org/pub/scm/virt/kvm/kvm.git/) -->

  8e41bd5 ("KVM: s390: fix locking for crypto setting error path")
  0e237e4 ("KVM: s390: Tracing APCB changes")
  76c7829 ("s390: vfio-ap: setup APCB mask using KVM dedicated function")

  <-- till here in 'kvms390/next'
  (https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git/)
  -->

  <-- In addition to that some prereqs for the 'ap/crypto' driver are
  necessary -->

  ea3c418 ("s390/zcrypt: Add ZAPQ inline function.")
  df80c03 ("s390/zcrypt: Review inline assembler constraints.")
  f1b0a43 ("s390/zcrypt: Integrate ap_asm.h into include/asm/ap.h.")
  2395103 ("s390/zcrypt: fix ap_instructions_available() returncodes")
  7e0bdbe ("s390/zcrypt: AP bus support for alternate driver(s)")
  3d8f60d3 ("s390/zcrypt: hex string mask improvements for apmask and aqmask.")
  fa108f9 ("s390/zcrypt: remove VLA usage from the AP bus")

  <--
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787405/comments/12
  -->

  == PATCH ==

  Above git commits are all from 4.19.
  The git commands for 4.18 would be:

  $ git cherry-pick 

  (112c24d "KVM: s390: CPU model support for AP virtualization" may have
  a trivial merge conflict with the etoken patch)

  $ git cherry-pick 

  $ git cherry-pick 

  == Regression Potential ==

  Low to mid:

  - mid because in summary there are a lot of changes, but low
  - they are all limited to the s390x architecture
  - and again limited to KVM/s390x, vfio-ap and the zcrypt (aka ap) driver
  - Test kernel was built 

[Kernel-packages] [Bug 1793458] Re: Overlayfs in user namespace leaks directory content of inaccessible directories

[Philipp Wendler]

Tyler, thanks for the clarification.

I have tested it with 4.15.0-42-generic from bionic-proposed and can
confirm it is fixed.

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

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

Title:
  Overlayfs in user namespace leaks directory content of inaccessible
  directories

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

Bug description:
  Summary: With a combination of overlayfs and user namespaces, regular
  users can see the content of directories that would otherwise be
  inaccessible to them because of directory permissions (e.g., all users
  can see content of "/root").

  Details: For the exploit it is necessary to create user and mount
  namespaces and mount an overlayfs inside it. Ubuntu allows this for
  regular users. The lower dir of the overlay would be "/", and the
  upper dir an attacker-controlled temporary directory. If the attacker
  wants to see the content of "/root", they would create a directory
  "root" in the upper dir of the overlay. Overlays seems to get confused
  about the permissions, and instead of applying the restrictive
  permissions of "root" from the lower dir, it applies more relaxed
  restrictions of "root" from the upper dir, granting the attacker the
  possibility to list the directory contents of "/root".

  To reproduce, simply run the attached script as regular user. It will show 
the content of "/root", on my system the output is this:
  ```
  /bin/ls: cannot access '/root/.cache': Permission denied
  /bin/ls: cannot access '/root/.bashrc': Permission denied
  /bin/ls: cannot access '/root/snap': Permission denied
  /bin/ls: cannot access '/root/.gnupg': Permission denied
  /bin/ls: cannot access '/root/.aptitude': Permission denied
  /bin/ls: cannot access '/root/.bash_history': Permission denied
  /bin/ls: cannot access '/root/.profile': Permission denied
  /bin/ls: cannot access '/root/.hplip': Permission denied
  total 8
  drwxr-xr-x 1 nobody nogroup 4096 Sep 20 09:02 .
  drwxr-xr-x 1 nobody nogroup 4096 Sep 20 09:02 ..
  d? ? ?  ?  ?? .aptitude
  -? ? ?  ?  ?? .bash_history
  -? ? ?  ?  ?? .bashrc
  d? ? ?  ?  ?? .cache
  d? ? ?  ?  ?? .gnupg
  d? ? ?  ?  ?? .hplip
  -? ? ?  ?  ?? .profile
  d? ? ?  ?  ?? snap
  ```

  The script also has some comments that explain the necessary steps in
  more details.

  I tested on Ubuntu 18.04 with Linux 4.15.0-34-generic, but the bug
  probably affects all Ubuntu versions of the last years. Other
  distributions and the vanilla kernel should not be affected because
  AFAIK only Ubuntu allows mounting of overlayfs inside user namespaces.
  But of course it would be good to apply a potential fix upstream.

  So far I did not succeed in doing more than leaking the directory
  content, but of course that is no guarantee that it is not possible to
  do worse things.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-34-generic 4.15.0-34.37
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  wendler3414 F pulseaudio
   /dev/snd/controlC0:  wendler3414 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Sep 20 08:56:01 2018
  HibernationDevice: RESUME=UUID=f9d1a1f9-50d2-4b7c-b7e4-66dc78d38062
  InstallationDate: Installed on 2016-12-12 (646 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20FXS1B700
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=/dev/mapper/ubuntu--vg-swap_1 swapaccount=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-34-generic N/A
   linux-backports-modules-4.15.0-34-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-09-04 (15 days ago)
  dmi.bios.date: 09/26/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET71W (2.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FXS1B700
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 

[Kernel-packages] [Bug 1804028] Re: Surface Go - Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not correctly recognized

[Waynexyz]

There is also a .zip files available
https://www.killernetworking.com/killersupport/item/killer-drivers-inf
which includes some .bin files for the QCA6174 (e.g.
"qca61x4_1_1_2.bin" )

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

Title:
  Surface Go - Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not
  correctly recognized

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Output of dmesg on Surface Go fresh installed Ubuntu 18.10.

  "[ 4.242132] ath10k_pci :01:00.0: qca6174 hw3.2 target 0x0503 chip_id 
0x00340aff sub 168c:3370
  [ 4.242138] ath10k_pci :01:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 
0 testmode 0
  [ 4.243006] ath10k_pci :01:00.0: firmware ver 
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
  [ 4.308059] ath10k_pci :01:00.0: failed to fetch board data for 
bus=pci,vendor=168c,device=003e,subsystem-vendor=168c,subsystem-device=3370 
from ath10k/QCA6174/hw3.0/board-2.bin
  [ 4.309354] ath10k_pci :01:00.0: board_file api 1 bmi_id N/A crc32 
ed5f849a"

  There is a board.bin available directly from the vendor
  http://www.killernetworking.com/support/K1535_Debian/board.bin

  The only thing which is missing is getting this added to
  https://wireless.wiki.kernel.org/en/users/drivers/ath10k/boardfiles so
  the official board-2.bin. My problem is that I dont know how to read
  the board files and modify them because I do not know the encoding
  they use.

  Also there have been some updates in the upstream linux-firmware repo.
  https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
  firmware.git/commit/?id=a87eb5f7bac0f70ade57da57d9126d14eee12336 and
  https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0 but
  they also do not help to get the wifi card working/recognized.

  Any ideas how to get this solved?

  Also there is a guide how to port it to Linux
  https://developer.qualcomm.com/download/qca9377/wlan-bluetooth-linux-
  porting-guide.pdf

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

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

[Kernel-packages] [Bug 1803929] Re: Summary: Kernel bug (unhandled paging request) on "udisksctl power-off"

[Matt C]

Yes, it only started occurring within the last few weeks/month.

I can confirm that booting the previous (but still installed) kernel,
fixes the problem.

$ uname -a
Linux metabox 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

That kernel works for me, so the issue must be in the "139" version.

I did not try the latest upstream kernel because I have NVIDIA drivers
and Virtualbox installed and I'd rather not go through the hassle of
uninstalling all custom modules, if I can avoid it.

Do you still need me to try the latest upstream?

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

Title:
  Summary: Kernel bug (unhandled paging request) on "udisksctl power-
  off"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  uname -a
  Linux metabox 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Steps (1) to reproduce:
  1) Plug in a USB3 hard drive.
  2) Right click on launcher icon.
  3) Select "Safely Remove".

  After finding this: https://askubuntu.com/a/532691
  ...the following steps also reproduce the problem.

  Steps (2) to reproduce:
  1) Plugin in a USB3 hard drive.
  2) udisksctl unmount -b /dev/sdXY
  3) udisksctl power-off -b /dev/sdX

  System completely locks and becomes unresponsive, such that even the Magic 
SysRq key combination does nothing.
  Most of the time the fans on my laptop go crazy (so the CPU must get stuck in 
some loop), but once they did not and the system was just locked (without the 
fans going nuts).

  I can't get a textual copy of the kernel bug log (because I have to do a hard 
reset to regain control of the system and the output doesn't get flushed to 
disk), but I did manage to get a photo of some of it (please refer to 
attachment).
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   matt   2754 F...m pulseaudio
   /dev/snd/controlC1:  matt   2754 F pulseaudio
   /dev/snd/controlC0:  matt   2754 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=f00235c0-ba8a-4403-91b1-64e9d87b76e0
  InstallationDate: Installed on 2016-04-23 (940 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Notebook N150SD/N155SD
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-139-generic 
root=UUID=beb9b9ce-39a7-464a-978c-ac4fb82a5a81 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-139-generic N/A
   linux-backports-modules-4.4.0-139-generic  N/A
   linux-firmware 1.157.20
  Tags:  xenial
  Uname: Linux 4.4.0-139-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/31/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N150SD/N155SD
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.05:bd03/31/2015:svnNotebook:pnN150SD/N155SD:pvrNotApplicable:rvnNotebook:rnN150SD/N155SD:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: N150SD/N155SD
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

[Kernel-packages] [Bug 1752437]

[jwrdegoede]

(In reply to Lukas Kahnert from comment #76)
> This error happens because your patch only fixes the mis-detection of the
> IRQ. There ist still https://bugzilla.kernel.org/show_bug.cgi?id=199529
> which needs also bei fixed to get the touchscreen work.

Right, I figured that out now, actually I believe that with your hack to
drivers/acpi/resource.c the changes you made to drivers/base/platform.c
should no longer be necessary.

We've been looking at the wrong part of the DSDT the culprit is not:

Interrupt (ResourceConsumer, Level, ActiveLow, Shared, ,, )
{
0x0007,
}

This uses an extended interrupt syntax, so acpi_dev_get_irqresource() gets 
called with legacy == false and the troublesome acpi_get_override_irq()
never happens.

I believe the real culprit is:

Scope (_SB.PCI0)
{
Device (SMBD)
{
Name (_HID, "SMB0001")  // _HID: Hardware ID
Name (_CRS, ResourceTemplate ()  // _CRS: Current Resource Settings
{
IO (Decode16,
0x0B20, // Range Minimum
0x0B20, // Range Maximum
0x20,   // Alignment
0x20,   // Length
)
IRQ (Level, ActiveLow, Shared, )
{7}
})
}
}

Which does use a legacy style IRQ resource, this causes
acpi_dev_get_irqresource() to be called with legacy == true and then the
troublesome acpi_get_override_irq() happens.

I believe that this troublesome node gets parsed before the AMDI0030
node and then by the time the AMDI0030 node happens, inside
acpi_dev_get_irqresource() we hit the else of:

irq = acpi_register_gsi(NULL, gsi, triggering, polarity);
if (irq >= 0) {
res->start = irq;
res->end = irq;
} else {
acpi_dev_irqresource_disabled(res, gsi);
}

Which sets the DISABLED flag, which is causing the issue in
drivers/base/platform.c . The reason we hit the else path is because of
the earlier enumeration of the same interrupt with conflicting trigger /
polarity settings so the second one fails with -EBUSY (it would work if
the flags would match).

My new attempt deals with this by adding the "SMB0001" HID to the
blacklist for creating platform devices, so that
acpi_dev_get_resources() does not get called on it at all, avoiding the
call of acpi_dev_get_irqresource() with legacy == false.

The not creating of a platform_device for the "SMB0001" HID is not an
issue since the driver for it is an acpi bus driver not a platform bus
driver.

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

Title:
  [HP ENVY x360 - 15-bq102ng] Touchscreen does not work

Status in linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch screen on my HP ENVY x360 15-bq102ng does not work with
  stock kernel or with mainline kernel 4.16-rc3.

  marc@snapbug:~$ xinput
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ HP Wireless hotkeys id=14   [slave  
keyboard (3)]
  ↳ HP WMI hotkeys  id=15   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP I id=11   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP W id=10   [slave  
keyboard (3)]

  WORKAROUND: Use the following patch with 4.17-rc3:
  https://bugzilla.kernel.org/attachment.cgi?id=275381

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  Uname: Linux 4.16.0-041600rc2-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  BootLog:
   No key available with this passphrase.
   /dev/mapper/nvme0n1p2_crypt: clean, 621596/15597568 files, 54013381/62389248 
blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 22:34:50 2018
  

[Kernel-packages] [Bug 1752437]

[openproggerfreak]

(In reply to Hans de Goede from comment #78)
> (In reply to Lukas Kahnert from comment #76)
> > This error happens because your patch only fixes the mis-detection of the
> > IRQ. There ist still https://bugzilla.kernel.org/show_bug.cgi?id=199529
> > which needs also bei fixed to get the touchscreen work.
> 
> Right, I figured that out now, actually I believe that with your hack to
> drivers/acpi/resource.c the changes you made to drivers/base/platform.c
> should no longer be necessary.
> 
> We've been looking at the wrong part of the DSDT the culprit is not:
> 
> Interrupt (ResourceConsumer, Level, ActiveLow, Shared, ,, )
> {
> 0x0007,
> }
> 
> This uses an extended interrupt syntax, so acpi_dev_get_irqresource() gets
> called with legacy == false and the troublesome acpi_get_override_irq()
> never happens.
> 
> I believe the real culprit is:
> 
> Scope (_SB.PCI0)
> {
> Device (SMBD)
> {
> Name (_HID, "SMB0001")  // _HID: Hardware ID
> Name (_CRS, ResourceTemplate ()  // _CRS: Current Resource
> Settings
> {
> IO (Decode16,
> 0x0B20, // Range Minimum
> 0x0B20, // Range Maximum
> 0x20,   // Alignment
> 0x20,   // Length
> )
> IRQ (Level, ActiveLow, Shared, )
> {7}
> })
> }
> }
> 
> Which does use a legacy style IRQ resource, this causes
> acpi_dev_get_irqresource() to be called with legacy == true and then the
> troublesome acpi_get_override_irq() happens.
> 
> I believe that this troublesome node gets parsed before the AMDI0030 node
> and then by the time the AMDI0030 node happens, inside
> acpi_dev_get_irqresource() we hit the else of:
> 
> irq = acpi_register_gsi(NULL, gsi, triggering, polarity);
> if (irq >= 0) {
> res->start = irq;
> res->end = irq;
> } else {
> acpi_dev_irqresource_disabled(res, gsi);
> }
> 
> Which sets the DISABLED flag, which is causing the issue in
> drivers/base/platform.c . The reason we hit the else path is because of the
> earlier enumeration of the same interrupt with conflicting trigger /
> polarity settings so the second one fails with -EBUSY (it would work if the
> flags would match).
> 
> My new attempt deals with this by adding the "SMB0001" HID to the blacklist
> for creating platform devices, so that acpi_dev_get_resources() does not get
> called on it at all, avoiding the call of acpi_dev_get_irqresource() with
> legacy == false.
> 
> The not creating of a platform_device for the "SMB0001" HID is not an issue
> since the driver for it is an acpi bus driver not a platform bus driver.

Thanks for this good explanation :)

I can also confirm that your patch works on my laptop

(In reply to Hans de Goede from comment #81)
> p.s.
> 
> I plan to add the following to the commit msg, please let me know if you've
> objections against this:
> 
> Reported-by: Lukas Kahnert 
> Tested-by: Marc 

I'm glad that I could help :)

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

Title:
  [HP ENVY x360 - 15-bq102ng] Touchscreen does not work

Status in linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch screen on my HP ENVY x360 15-bq102ng does not work with
  stock kernel or with mainline kernel 4.16-rc3.

  marc@snapbug:~$ xinput
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ HP Wireless hotkeys id=14   [slave  
keyboard (3)]
  ↳ HP WMI hotkeys  id=15   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP I id=11   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP W id=10   [slave  
keyboard (3)]

  WORKAROUND: Use the following patch with 4.17-rc3:
  

[Kernel-packages] [Bug 1752437]

[jwrdegoede]

p.s.

I plan to add the following to the commit msg, please let me know if
you've objections against this:

Reported-by: Lukas Kahnert 
Tested-by: Marc 

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

Title:
  [HP ENVY x360 - 15-bq102ng] Touchscreen does not work

Status in linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch screen on my HP ENVY x360 15-bq102ng does not work with
  stock kernel or with mainline kernel 4.16-rc3.

  marc@snapbug:~$ xinput
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ HP Wireless hotkeys id=14   [slave  
keyboard (3)]
  ↳ HP WMI hotkeys  id=15   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP I id=11   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP W id=10   [slave  
keyboard (3)]

  WORKAROUND: Use the following patch with 4.17-rc3:
  https://bugzilla.kernel.org/attachment.cgi?id=275381

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  Uname: Linux 4.16.0-041600rc2-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  BootLog:
   No key available with this passphrase.
   /dev/mapper/nvme0n1p2_crypt: clean, 621596/15597568 files, 54013381/62389248 
blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 22:34:50 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:83c6]
  InstallationDate: Installed on 2018-01-16 (42 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: HP HP ENVY x360 Convertible 15-bq1xx
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.16.0-041600rc2-generic 
root=UUID=415eb027-1fd5-4b75-9860-5cac88a630db ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/26/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83C6
  dmi.board.vendor: HP
  dmi.board.version: 63.18
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd01/26/2018:svnHP:pnHPENVYx360Convertible15-bq1xx:pvr:rvnHP:rn83C6:rvr63.18:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 15-bq1xx
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-4~a~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1752437]

[suaefar]

Created attachment 279541
Output of dmesg after booting kernel 4.19.2 with new patch v2 (touchscreen 
works)

Congratulations, this work!

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

Title:
  [HP ENVY x360 - 15-bq102ng] Touchscreen does not work

Status in linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch screen on my HP ENVY x360 15-bq102ng does not work with
  stock kernel or with mainline kernel 4.16-rc3.

  marc@snapbug:~$ xinput
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ HP Wireless hotkeys id=14   [slave  
keyboard (3)]
  ↳ HP WMI hotkeys  id=15   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP I id=11   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP W id=10   [slave  
keyboard (3)]

  WORKAROUND: Use the following patch with 4.17-rc3:
  https://bugzilla.kernel.org/attachment.cgi?id=275381

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  Uname: Linux 4.16.0-041600rc2-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  BootLog:
   No key available with this passphrase.
   /dev/mapper/nvme0n1p2_crypt: clean, 621596/15597568 files, 54013381/62389248 
blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 22:34:50 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:83c6]
  InstallationDate: Installed on 2018-01-16 (42 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: HP HP ENVY x360 Convertible 15-bq1xx
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.16.0-041600rc2-generic 
root=UUID=415eb027-1fd5-4b75-9860-5cac88a630db ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/26/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83C6
  dmi.board.vendor: HP
  dmi.board.version: 63.18
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd01/26/2018:svnHP:pnHPENVYx360Convertible15-bq1xx:pvr:rvnHP:rn83C6:rvr63.18:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 15-bq1xx
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-4~a~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1752437]

[tardivo.fabio]

(In reply to Hans de Goede from comment #77)
> Created attachment 279539 [details]
> [PATCH] ACPI / platform: Add SMB0001 HID to forbidden_id_list
> 
> Ok second attempt, a completely different patch which I think actually is
> better (if it works).
> 
> Please give this one a try (without any other patches for this same issue).
> 
> Again please attach dmesg output.
> 
> If this patch does not fix things, then also please attach the output of:
> 
> ls /sys/bus/platform/devices
> 
> I would like the output of that command for both a kernel without the patch
> as well as for one with the patch.

It worked also on mine HP 13M-AG0002DX.

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

Title:
  [HP ENVY x360 - 15-bq102ng] Touchscreen does not work

Status in linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch screen on my HP ENVY x360 15-bq102ng does not work with
  stock kernel or with mainline kernel 4.16-rc3.

  marc@snapbug:~$ xinput
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ HP Wireless hotkeys id=14   [slave  
keyboard (3)]
  ↳ HP WMI hotkeys  id=15   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP I id=11   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP W id=10   [slave  
keyboard (3)]

  WORKAROUND: Use the following patch with 4.17-rc3:
  https://bugzilla.kernel.org/attachment.cgi?id=275381

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  Uname: Linux 4.16.0-041600rc2-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  BootLog:
   No key available with this passphrase.
   /dev/mapper/nvme0n1p2_crypt: clean, 621596/15597568 files, 54013381/62389248 
blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 22:34:50 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:83c6]
  InstallationDate: Installed on 2018-01-16 (42 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: HP HP ENVY x360 Convertible 15-bq1xx
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.16.0-041600rc2-generic 
root=UUID=415eb027-1fd5-4b75-9860-5cac88a630db ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/26/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83C6
  dmi.board.vendor: HP
  dmi.board.version: 63.18
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd01/26/2018:svnHP:pnHPENVYx360Convertible15-bq1xx:pvr:rvnHP:rn83C6:rvr63.18:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 15-bq1xx
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-4~a~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 

[Kernel-packages] [Bug 1752437]

[jwrdegoede]

(In reply to Marc from comment #79)
> Created attachment 279541 [details]
> Output of dmesg after booting kernel 4.19.2 with new patch v2 (touchscreen
> works)
> 
> Congratulations, this work!

Great and the "ACPI: IRQ 7 override to edge, high" message is gone. So
you've proven my theory.

Now I need to improve the commit message and then this patch can be
submitted upstream.

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

Title:
  [HP ENVY x360 - 15-bq102ng] Touchscreen does not work

Status in linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch screen on my HP ENVY x360 15-bq102ng does not work with
  stock kernel or with mainline kernel 4.16-rc3.

  marc@snapbug:~$ xinput
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ HP Wireless hotkeys id=14   [slave  
keyboard (3)]
  ↳ HP WMI hotkeys  id=15   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP I id=11   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP W id=10   [slave  
keyboard (3)]

  WORKAROUND: Use the following patch with 4.17-rc3:
  https://bugzilla.kernel.org/attachment.cgi?id=275381

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  Uname: Linux 4.16.0-041600rc2-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  BootLog:
   No key available with this passphrase.
   /dev/mapper/nvme0n1p2_crypt: clean, 621596/15597568 files, 54013381/62389248 
blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 22:34:50 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:83c6]
  InstallationDate: Installed on 2018-01-16 (42 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: HP HP ENVY x360 Convertible 15-bq1xx
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.16.0-041600rc2-generic 
root=UUID=415eb027-1fd5-4b75-9860-5cac88a630db ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/26/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83C6
  dmi.board.vendor: HP
  dmi.board.version: 63.18
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd01/26/2018:svnHP:pnHPENVYx360Convertible15-bq1xx:pvr:rvnHP:rn83C6:rvr63.18:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 15-bq1xx
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-4~a~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1752437]

[jwrdegoede]

Created attachment 279539
[PATCH] ACPI / platform: Add SMB0001 HID to forbidden_id_list

Ok second attempt, a completely different patch which I think actually
is better (if it works).

Please give this one a try (without any other patches for this same
issue).

Again please attach dmesg output.

If this patch does not fix things, then also please attach the output
of:

ls /sys/bus/platform/devices

I would like the output of that command for both a kernel without the
patch as well as for one with the patch.

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

Title:
  [HP ENVY x360 - 15-bq102ng] Touchscreen does not work

Status in linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch screen on my HP ENVY x360 15-bq102ng does not work with
  stock kernel or with mainline kernel 4.16-rc3.

  marc@snapbug:~$ xinput
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ HP Wireless hotkeys id=14   [slave  
keyboard (3)]
  ↳ HP WMI hotkeys  id=15   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP I id=11   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP W id=10   [slave  
keyboard (3)]

  WORKAROUND: Use the following patch with 4.17-rc3:
  https://bugzilla.kernel.org/attachment.cgi?id=275381

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  Uname: Linux 4.16.0-041600rc2-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  BootLog:
   No key available with this passphrase.
   /dev/mapper/nvme0n1p2_crypt: clean, 621596/15597568 files, 54013381/62389248 
blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 22:34:50 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:83c6]
  InstallationDate: Installed on 2018-01-16 (42 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: HP HP ENVY x360 Convertible 15-bq1xx
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.16.0-041600rc2-generic 
root=UUID=415eb027-1fd5-4b75-9860-5cac88a630db ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/26/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83C6
  dmi.board.vendor: HP
  dmi.board.version: 63.18
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd01/26/2018:svnHP:pnHPENVYx360Convertible15-bq1xx:pvr:rvnHP:rn83C6:rvr63.18:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 15-bq1xx
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-4~a~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1752437]

[suaefar]

Created attachment 279529
Output of dmesg after booting kernel 4.19.2 with new patch

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

Title:
  [HP ENVY x360 - 15-bq102ng] Touchscreen does not work

Status in linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch screen on my HP ENVY x360 15-bq102ng does not work with
  stock kernel or with mainline kernel 4.16-rc3.

  marc@snapbug:~$ xinput
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ HP Wireless hotkeys id=14   [slave  
keyboard (3)]
  ↳ HP WMI hotkeys  id=15   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP I id=11   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP W id=10   [slave  
keyboard (3)]

  WORKAROUND: Use the following patch with 4.17-rc3:
  https://bugzilla.kernel.org/attachment.cgi?id=275381

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  Uname: Linux 4.16.0-041600rc2-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  BootLog:
   No key available with this passphrase.
   /dev/mapper/nvme0n1p2_crypt: clean, 621596/15597568 files, 54013381/62389248 
blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 22:34:50 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:83c6]
  InstallationDate: Installed on 2018-01-16 (42 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: HP HP ENVY x360 Convertible 15-bq1xx
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.16.0-041600rc2-generic 
root=UUID=415eb027-1fd5-4b75-9860-5cac88a630db ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/26/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83C6
  dmi.board.vendor: HP
  dmi.board.version: 63.18
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd01/26/2018:svnHP:pnHPENVYx360Convertible15-bq1xx:pvr:rvnHP:rn83C6:rvr63.18:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 15-bq1xx
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-4~a~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1752437]

[jwrdegoede]

(In reply to Marc from comment #70)
> I would test the patch but can't find it.

My bad, I was updating the 3 different bugs about this all at the same
time and I actually forgot to attach the patch, it is attached to bug
199523 now.

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

Title:
  [HP ENVY x360 - 15-bq102ng] Touchscreen does not work

Status in linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch screen on my HP ENVY x360 15-bq102ng does not work with
  stock kernel or with mainline kernel 4.16-rc3.

  marc@snapbug:~$ xinput
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ HP Wireless hotkeys id=14   [slave  
keyboard (3)]
  ↳ HP WMI hotkeys  id=15   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP I id=11   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP W id=10   [slave  
keyboard (3)]

  WORKAROUND: Use the following patch with 4.17-rc3:
  https://bugzilla.kernel.org/attachment.cgi?id=275381

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  Uname: Linux 4.16.0-041600rc2-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  BootLog:
   No key available with this passphrase.
   /dev/mapper/nvme0n1p2_crypt: clean, 621596/15597568 files, 54013381/62389248 
blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 22:34:50 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:83c6]
  InstallationDate: Installed on 2018-01-16 (42 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: HP HP ENVY x360 Convertible 15-bq1xx
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.16.0-041600rc2-generic 
root=UUID=415eb027-1fd5-4b75-9860-5cac88a630db ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/26/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83C6
  dmi.board.vendor: HP
  dmi.board.version: 63.18
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd01/26/2018:svnHP:pnHPENVYx360Convertible15-bq1xx:pvr:rvnHP:rn83C6:rvr63.18:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 15-bq1xx
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-4~a~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1752437] Re: [HP ENVY x360 - 15-bq102ng] Touchscreen does not work

[Bug Watch Updater]

** Bug watch added: Linux Kernel Bug Tracker #199529
   https://bugzilla.kernel.org/show_bug.cgi?id=199529

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

Title:
  [HP ENVY x360 - 15-bq102ng] Touchscreen does not work

Status in linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch screen on my HP ENVY x360 15-bq102ng does not work with
  stock kernel or with mainline kernel 4.16-rc3.

  marc@snapbug:~$ xinput
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ HP Wireless hotkeys id=14   [slave  
keyboard (3)]
  ↳ HP WMI hotkeys  id=15   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP I id=11   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP W id=10   [slave  
keyboard (3)]

  WORKAROUND: Use the following patch with 4.17-rc3:
  https://bugzilla.kernel.org/attachment.cgi?id=275381

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  Uname: Linux 4.16.0-041600rc2-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  BootLog:
   No key available with this passphrase.
   /dev/mapper/nvme0n1p2_crypt: clean, 621596/15597568 files, 54013381/62389248 
blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 22:34:50 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:83c6]
  InstallationDate: Installed on 2018-01-16 (42 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: HP HP ENVY x360 Convertible 15-bq1xx
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.16.0-041600rc2-generic 
root=UUID=415eb027-1fd5-4b75-9860-5cac88a630db ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/26/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83C6
  dmi.board.vendor: HP
  dmi.board.version: 63.18
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd01/26/2018:svnHP:pnHPENVYx360Convertible15-bq1xx:pvr:rvnHP:rn83C6:rvr63.18:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 15-bq1xx
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-4~a~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1752437]

[jwrdegoede]

First if all thank you Lukas, for pinpointing the problem. I don't see
any really obvious nice answer here.

So I believe it is best to override the IRQ type manually in the AMD
gpio driver to correct the acpi_get_override_irq() results from the ACPI
core.

I've attached a patch doing this to bug 199523.

If someone who is seeing this issue can build and test a kernel with
that patch (replacing Lukas patch) that would be great. To be clear
please drop Lukas' patch  when testing mine!

If you test my patch, please provide the output of "dmesg" directly
after boot and let me know if the patch fixes things (makes/keeps the
touchscreen working).

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

Title:
  [HP ENVY x360 - 15-bq102ng] Touchscreen does not work

Status in linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch screen on my HP ENVY x360 15-bq102ng does not work with
  stock kernel or with mainline kernel 4.16-rc3.

  marc@snapbug:~$ xinput
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ HP Wireless hotkeys id=14   [slave  
keyboard (3)]
  ↳ HP WMI hotkeys  id=15   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP I id=11   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP W id=10   [slave  
keyboard (3)]

  WORKAROUND: Use the following patch with 4.17-rc3:
  https://bugzilla.kernel.org/attachment.cgi?id=275381

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  Uname: Linux 4.16.0-041600rc2-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  BootLog:
   No key available with this passphrase.
   /dev/mapper/nvme0n1p2_crypt: clean, 621596/15597568 files, 54013381/62389248 
blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 22:34:50 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:83c6]
  InstallationDate: Installed on 2018-01-16 (42 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: HP HP ENVY x360 Convertible 15-bq1xx
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.16.0-041600rc2-generic 
root=UUID=415eb027-1fd5-4b75-9860-5cac88a630db ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/26/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83C6
  dmi.board.vendor: HP
  dmi.board.version: 63.18
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd01/26/2018:svnHP:pnHPENVYx360Convertible15-bq1xx:pvr:rvnHP:rn83C6:rvr63.18:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 15-bq1xx
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-4~a~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1752437]

[suaefar]

I am happy to test further patches.

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

Title:
  [HP ENVY x360 - 15-bq102ng] Touchscreen does not work

Status in linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch screen on my HP ENVY x360 15-bq102ng does not work with
  stock kernel or with mainline kernel 4.16-rc3.

  marc@snapbug:~$ xinput
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ HP Wireless hotkeys id=14   [slave  
keyboard (3)]
  ↳ HP WMI hotkeys  id=15   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP I id=11   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP W id=10   [slave  
keyboard (3)]

  WORKAROUND: Use the following patch with 4.17-rc3:
  https://bugzilla.kernel.org/attachment.cgi?id=275381

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  Uname: Linux 4.16.0-041600rc2-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  BootLog:
   No key available with this passphrase.
   /dev/mapper/nvme0n1p2_crypt: clean, 621596/15597568 files, 54013381/62389248 
blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 22:34:50 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:83c6]
  InstallationDate: Installed on 2018-01-16 (42 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: HP HP ENVY x360 Convertible 15-bq1xx
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.16.0-041600rc2-generic 
root=UUID=415eb027-1fd5-4b75-9860-5cac88a630db ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/26/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83C6
  dmi.board.vendor: HP
  dmi.board.version: 63.18
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd01/26/2018:svnHP:pnHPENVYx360Convertible15-bq1xx:pvr:rvnHP:rn83C6:rvr63.18:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 15-bq1xx
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-4~a~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1752437]

[openproggerfreak]

When I come home I will test your Patch and report asap.


(In reply to Hans de Goede from comment #74)
> (In reply to Marc from comment #73)
> > Unfortunately the new patch does not work on my ENVY 15-bq102ng.
> > 
> > I used linux kernel 4.19.2 from kernel.org, patched it with the ubuntu
> > mainline patches and on top your patch (instead of Lukas patch).
> 
> Thank you for testing. These 2 lines in the log seem to be the problem,
> these happen before my patch even comes into play:
> 
> [1.445982] amd_gpio AMDI0030:00: Failed to get gpio IRQ: -22
> [1.446019] amd_gpio: probe of AMDI0030:00 failed with error -22
> 
> With -22 being -EINVAL.
> 
> Taking a closer look at things here I think I know what is going on here.
> 
> To be continued.

This error happens because your patch only fixes the mis-detection of the IRQ. 
There ist still https://bugzilla.kernel.org/show_bug.cgi?id=199529 which needs 
also bei fixed to get the touchscreen work.
One half of my Patch hides the affected code, so the gpio driver can probe 
successfully.

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

Title:
  [HP ENVY x360 - 15-bq102ng] Touchscreen does not work

Status in linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch screen on my HP ENVY x360 15-bq102ng does not work with
  stock kernel or with mainline kernel 4.16-rc3.

  marc@snapbug:~$ xinput
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ HP Wireless hotkeys id=14   [slave  
keyboard (3)]
  ↳ HP WMI hotkeys  id=15   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP I id=11   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP W id=10   [slave  
keyboard (3)]

  WORKAROUND: Use the following patch with 4.17-rc3:
  https://bugzilla.kernel.org/attachment.cgi?id=275381

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  Uname: Linux 4.16.0-041600rc2-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  BootLog:
   No key available with this passphrase.
   /dev/mapper/nvme0n1p2_crypt: clean, 621596/15597568 files, 54013381/62389248 
blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 22:34:50 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:83c6]
  InstallationDate: Installed on 2018-01-16 (42 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: HP HP ENVY x360 Convertible 15-bq1xx
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.16.0-041600rc2-generic 
root=UUID=415eb027-1fd5-4b75-9860-5cac88a630db ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/26/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83C6
  dmi.board.vendor: HP
  dmi.board.version: 63.18
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd01/26/2018:svnHP:pnHPENVYx360Convertible15-bq1xx:pvr:rvnHP:rn83C6:rvr63.18:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 15-bq1xx
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-4~a~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  

[Kernel-packages] [Bug 1752437]

[suaefar]

I would test the patch but can't find it.

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

Title:
  [HP ENVY x360 - 15-bq102ng] Touchscreen does not work

Status in linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch screen on my HP ENVY x360 15-bq102ng does not work with
  stock kernel or with mainline kernel 4.16-rc3.

  marc@snapbug:~$ xinput
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ HP Wireless hotkeys id=14   [slave  
keyboard (3)]
  ↳ HP WMI hotkeys  id=15   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP I id=11   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP W id=10   [slave  
keyboard (3)]

  WORKAROUND: Use the following patch with 4.17-rc3:
  https://bugzilla.kernel.org/attachment.cgi?id=275381

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  Uname: Linux 4.16.0-041600rc2-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  BootLog:
   No key available with this passphrase.
   /dev/mapper/nvme0n1p2_crypt: clean, 621596/15597568 files, 54013381/62389248 
blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 22:34:50 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:83c6]
  InstallationDate: Installed on 2018-01-16 (42 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: HP HP ENVY x360 Convertible 15-bq1xx
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.16.0-041600rc2-generic 
root=UUID=415eb027-1fd5-4b75-9860-5cac88a630db ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/26/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83C6
  dmi.board.vendor: HP
  dmi.board.version: 63.18
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd01/26/2018:svnHP:pnHPENVYx360Convertible15-bq1xx:pvr:rvnHP:rn83C6:rvr63.18:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 15-bq1xx
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-4~a~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1752437]

[jwrdegoede]

(In reply to Marc from comment #73)
> Unfortunately the new patch does not work on my ENVY 15-bq102ng.
> 
> I used linux kernel 4.19.2 from kernel.org, patched it with the ubuntu
> mainline patches and on top your patch (instead of Lukas patch).

Thank you for testing. These 2 lines in the log seem to be the problem,
these happen before my patch even comes into play:

[1.445982] amd_gpio AMDI0030:00: Failed to get gpio IRQ: -22
[1.446019] amd_gpio: probe of AMDI0030:00 failed with error -22

With -22 being -EINVAL.

Taking a closer look at things here I think I know what is going on
here.

To be continued.

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

Title:
  [HP ENVY x360 - 15-bq102ng] Touchscreen does not work

Status in linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch screen on my HP ENVY x360 15-bq102ng does not work with
  stock kernel or with mainline kernel 4.16-rc3.

  marc@snapbug:~$ xinput
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ HP Wireless hotkeys id=14   [slave  
keyboard (3)]
  ↳ HP WMI hotkeys  id=15   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP I id=11   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP W id=10   [slave  
keyboard (3)]

  WORKAROUND: Use the following patch with 4.17-rc3:
  https://bugzilla.kernel.org/attachment.cgi?id=275381

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  Uname: Linux 4.16.0-041600rc2-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  BootLog:
   No key available with this passphrase.
   /dev/mapper/nvme0n1p2_crypt: clean, 621596/15597568 files, 54013381/62389248 
blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 22:34:50 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:83c6]
  InstallationDate: Installed on 2018-01-16 (42 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: HP HP ENVY x360 Convertible 15-bq1xx
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.16.0-041600rc2-generic 
root=UUID=415eb027-1fd5-4b75-9860-5cac88a630db ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/26/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83C6
  dmi.board.vendor: HP
  dmi.board.version: 63.18
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd01/26/2018:svnHP:pnHPENVYx360Convertible15-bq1xx:pvr:rvnHP:rn83C6:rvr63.18:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 15-bq1xx
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-4~a~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1752437]

[suaefar]

Unfortunately the new patch does not work on my ENVY 15-bq102ng.

I used linux kernel 4.19.2 from kernel.org, patched it with the ubuntu
mainline patches and on top your patch (instead of Lukas patch).

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

Title:
  [HP ENVY x360 - 15-bq102ng] Touchscreen does not work

Status in linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch screen on my HP ENVY x360 15-bq102ng does not work with
  stock kernel or with mainline kernel 4.16-rc3.

  marc@snapbug:~$ xinput
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ HP Wireless hotkeys id=14   [slave  
keyboard (3)]
  ↳ HP WMI hotkeys  id=15   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP I id=11   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP W id=10   [slave  
keyboard (3)]

  WORKAROUND: Use the following patch with 4.17-rc3:
  https://bugzilla.kernel.org/attachment.cgi?id=275381

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  Uname: Linux 4.16.0-041600rc2-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  BootLog:
   No key available with this passphrase.
   /dev/mapper/nvme0n1p2_crypt: clean, 621596/15597568 files, 54013381/62389248 
blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 22:34:50 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:83c6]
  InstallationDate: Installed on 2018-01-16 (42 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: HP HP ENVY x360 Convertible 15-bq1xx
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.16.0-041600rc2-generic 
root=UUID=415eb027-1fd5-4b75-9860-5cac88a630db ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/26/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83C6
  dmi.board.vendor: HP
  dmi.board.version: 63.18
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd01/26/2018:svnHP:pnHPENVYx360Convertible15-bq1xx:pvr:rvnHP:rn83C6:rvr63.18:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 15-bq1xx
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-4~a~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1792144] Re: missing patch for i915 in 4.15.0-33-generic => black screen on boot

[redger]

I have the same bug on a similar motherboard - Asrock j4105-itx (j4105 CPU, 
asmedia asm1061, realtek rtl8111h)
After the boot sequence 
KUbuntu 18.04 fully updated to Nov-19-2018
Bios 4.0.0.1245Intel GOP  13.0.1011

I doubt this is the same as the freedesktop 105549 bug since the
hardware is quite different (no lspcon chip on this motherboard)

Also note that the problem only arises when a disk is connected to one
of the asmedia sata ports on this motherboard. If no disk on asmedia all
is good. No HDMI or DVI screen if disk on asmedia port

Windows (8.1) does not experience this issue  BUT does not have
drivers for this chip at all (Vesa only)> I don't currently have access
to Windows 10

When the VGA port is connected to a screen then BOTH the vga and hdmi /
dvi screens are active ie. the hdmi / dvi output is live if vga
simultaneously connected ... though vga is primary

May be spurious, but fwiw, under these conditions ... The system will
not power down correctly (even if both VGA and hdmi / dvi connected).
Powerdown  seems to stop after a message about "ata3 SError" "failed
command STANDBY IMMEDIATE" and then a manual power off is required

Any debug data I can provide ?

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

Title:
  missing patch for i915 in 4.15.0-33-generic => black screen on boot

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged

Bug description:
  we must use i915 with modesetting, because else the hdmi-audio isn't
  available.

  enabling modesetting, the monitor went black immediately after dmesg:

  fb: switching to inteldrmfb from EFI VGA
  Console: switching to colour dummy device 80x25
  [drm] Replacing VGA console driver

  for this bug at https://bugs.freedesktop.org/show_bug.cgi?id=105549
  there seems to be a patch available which doesn't seem to be
  integrated in last available xenial-kernel 4.15.0-33-generic.

  please integrate it in next kernel-update.

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

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

[Kernel-packages] [Bug 1797546] Re: dev test in ubuntu_stress_smoke_test cause kernel oops on T-3.13

[Po-Hsu Lin]

Stress smoke test passed with the proposed Trusty kernel without any issue.
Thanks

** Changed in: ubuntu-kernel-tests
   Status: In Progress => Fix Released

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

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

Title:
  dev test in ubuntu_stress_smoke_test cause kernel oops on T-3.13

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Committed

Bug description:
  SRU Request [Trusty]

  == Justification ==

  It is possible to cause an oops in drm with an unimplemented ioctl call
  with the following reproducer run as root:

  #include 
  #include 
  #include 
  #include 

  int main(void)
  {
  int ptnum, fd;

  fd = open("/dev/dri/card0", O_RDWR);
  return ioctl(fd, TIOCGPTN, );
  }

  == Fix ==

  A backport (minor wiggle) of upstream commit 1539fb9bd405
  ("drm: fix NULL pointer access by wrong ioctl").

  == Testing ==

  Run the reproducer above as root, it will trip the oops. With the fix
  this oops won't occur.

  == Regression Potential ==

  Minimal, this is an upstream fix to this exact issue and has been in
  the kernel since 3.16

  


  This is a bare-metal node running with 3.13.0-160 amd64 kernel.

  The dev test will cause kernel oops:
    dev STARTING
    dev RETURNED 0
    dev FAILED (kernel oopsed)
    [  222.555784] BUG: unable to handle kernel NULL pointer dereference at 
  (null)
    [  222.564547] IP: [] memset+0x9/0xb0
    [  222.570101] PGD 8004586b1067 PUD 45784a067 PMD 0
    [  222.575767] Oops: 0002 [#1] SMP
    [  222.579385] Modules linked in: macvlan(+) dccp_ipv4 dccp ghash_generic 
salsa20_generic salsa20_x86_64 camellia_generic camellia_aesni_avx2 
camellia_aesni_avx_x86_64 camellia_x86_64 cast6_avx_x86_64 cast6_generic 
cast_common serpent_avx2 serpent_avx_x86_64 serpent_sse2_x86_64 serpent_generic 
twofish_generic twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64 
twofish_common xts algif_skcipher tgr192 wp512 rmd320 rmd256 rmd160 rmd128 md4 
algif_hash af_alg ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi dm_crypt 
x86_pkg_temp_thermal coretemp kvm_intel kvm joydev lpc_ich shpchp mac_hid 
hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel igb 
aesni_intel aes_x86_64 i915_bdw dca lrw gf128mul ahci intel_ips glue_helper ptp 
ablk_helper drm_kms_helper cryptd pps_core libahci i2c_algo_bit drm video
    [  222.647301] CPU: 0 PID: 23159 Comm: stress-ng-dev Not tainted 
3.13.0-160-generic #210-Ubuntu
    [  222.647301] Hardware name: Intel Corporation S1200RP/S1200RP, BIOS 
S1200RP.86B.03.02.0003.070120151022 07/01/2015
    [  222.647302] task: 880035bf1800 ti: 880453b6 task.ti: 
880453b6
    [  222.647303] RIP: 0010:[]  [] 
memset+0x9/0xb0
    [  222.647306] RSP: 0018:880453b61db8  EFLAGS: 00010246
    [  222.647306] RAX: 88045af55d00 RBX: 880455538000 RCX: 
0004
    [  222.647307] RDX: 0004 RSI:  RDI: 

    [  222.647307] RBP: 880453b61ec0 R08: 81c43740 R09: 

    [  222.647308] R10: a002f260 R11: 880453b61e10 R12: 
880455f07a00
    [  222.647309] R13: 0004 R14:  R15: 
0030
    [  222.647310] FS:  7f64909ef700() GS:88047040() 
knlGS:
    [  222.647310] CS:  0010 DS:  ES:  CR0: 80050033
    [  222.647311] CR2:  CR3: 000458904000 CR4: 
00360770
    [  222.647312] DR0:  DR1:  DR2: 

    [  222.647312] DR3:  DR6: fffe0ff0 DR7: 
0400
    [  222.647313] Stack:
    [  222.647314]  a0010c05 88040001 a003ace4 
00410086
    [  222.647316]  880453b61e10 880453b61e10 a00185d0 
643054506240
    [  222.647317]  7f64909ebce0 88040004 a002f260 

    [  222.647317] Call Trace:
    [  222.647329]  [] ? drm_ioctl+0x4d5/0x630 [drm]
    [  222.647337]  [] ? drm_agp_info_ioctl+0x10/0x10 [drm]
    [  222.647341]  [] do_vfs_ioctl+0x2e3/0x4d0
    [  222.647343]  [] ? SYSC_newfstat+0x25/0x30
    [  222.647344]  [] SyS_ioctl+0x81/0xa0
    [  222.647347]  [] system_call_fastpath+0x26/0x2b
    [  222.647359] Code: 16 fe 66 44 89 1f 66 44 89 54 17 fe eb 0c 48 83 fa 01 
72 06 44 8a 1e 44 88 1f c3 90 90 90 90 90 90 90 49 89 f9 40 88 f0 48 89 d1  
aa 4c 89 c8 c3 0f 1f 84 00 00 00 00 00 0f 1f 84 00 00 00 00
    [  222.647360] RIP  [] memset+0x9/0xb0
    [  222.647361]  RSP 
    [  222.647361] CR2: 
    [  222.647363] ---[ end trace 

[Kernel-packages] [Bug 1802454] Re: fanotify10 in ubuntu_ltp_syscalls failed

[Po-Hsu Lin]

For cosmic, it's been fixed in stable update, bug 1801931

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

Title:
  fanotify10 in ubuntu_ltp_syscalls failed

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  In Progress

Bug description:
  This is a new test case that landed 7 days ago.

  <<>>
  tag=fanotify10 stime=1541744937
  cmdline="fanotify10"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop1'
  tst_mkfs.c:90: INFO: Formatting /dev/loop1 with ext2 opts='' extra opts=''
  mke2fs 1.44.1 (24-Mar-2018)
  tst_test.c:1085: INFO: Timeout per run is 0h 05m 00s
  fanotify10.c:199: INFO: Test #0: ignore mount events created on a specific 
file
  fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
  fanotify10.c:264: PASS: group 0 (prio 1) with FAN_MARK_MOUNT and 
FAN_MARK_INODE ignore mask got no event
  fanotify10.c:264: PASS: group 1 (prio 1) with FAN_MARK_MOUNT and 
FAN_MARK_INODE ignore mask got no event
  fanotify10.c:264: PASS: group 2 (prio 1) with FAN_MARK_MOUNT and 
FAN_MARK_INODE ignore mask got no event
  fanotify10.c:264: PASS: group 0 (prio 2) with FAN_MARK_MOUNT and 
FAN_MARK_INODE ignore mask got no event
  fanotify10.c:264: PASS: group 1 (prio 2) with FAN_MARK_MOUNT and 
FAN_MARK_INODE ignore mask got no event
  fanotify10.c:264: PASS: group 2 (prio 2) with FAN_MARK_MOUNT and 
FAN_MARK_INODE ignore mask got no event
  fanotify10.c:199: INFO: Test #1: don't ignore mount events created on another 
file
  fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
  fanotify10.c:199: INFO: Test #2: ignore inode events created on a specific 
mount point
  fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
  fanotify10.c:258: FAIL: group 0 (prio 1) with FAN_MARK_INODE and 
FAN_MARK_MOUNT ignore mask got event
  fanotify10.c:258: FAIL: group 1 (prio 1) with FAN_MARK_INODE and 
FAN_MARK_MOUNT ignore mask got event
  fanotify10.c:258: FAIL: group 2 (prio 1) with FAN_MARK_INODE and 
FAN_MARK_MOUNT ignore mask got event
  fanotify10.c:258: FAIL: group 0 (prio 2) with FAN_MARK_INODE and 
FAN_MARK_MOUNT ignore mask got event
  fanotify10.c:258: FAIL: group 1 (prio 2) with FAN_MARK_INODE and 
FAN_MARK_MOUNT ignore mask got event
  fanotify10.c:258: FAIL: group 2 (prio 2) with FAN_MARK_INODE and 
FAN_MARK_MOUNT ignore mask got event
  fanotify10.c:199: INFO: Test #3: don't ignore inode events created on another 
mount point
  fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15

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

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12~18.04.1
  ProcVersionSignature: User Name 4.18.0-11.12~18.04.1-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Fri Nov  9 06:24:06 2018
  SourcePackage: linux-signed-hwe-edge
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1793451] Re: mlock203 test in ubuntu_ltp_syscalls failed with Xenial kernel

[Po-Hsu Lin]

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

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

** Changed in: ubuntu-kernel-tests
   Status: In Progress => 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/1793451

Title:
  mlock203 test in ubuntu_ltp_syscalls failed with Xenial kernel

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

Bug description:
  == Justification ==
  When one vma was with flag VM_LOCKED|VM_LOCKONFAULT (by invoking
  mlock2(,MLOCK_ONFAULT)), it can again be populated with mlock() with
  VM_LOCKED flag only.

  There is a hole in mlock_fixup() which increase mm->locked_vm twice even
  the two operations are on the same vma and both with VM_LOCKED flags.

  The issue can be reproduced by following code:

    mlock2(p, 1024 * 64, MLOCK_ONFAULT); //VM_LOCKED|VM_LOCKONFAULT
    mlock(p, 1024 * 64);  //VM_LOCKED

  Then check the increase VmLck field in /proc/pid/status(to 128k).

  When vma is set with different vm_flags, and the new vm_flags is with
  VM_LOCKED, it is not necessarily be a "new locked" vma.

  There is a dedicated reproducer, the "mlock203" test in
  ubuntu_ltp_syscalls, you can see the failure for all the Ubuntu 4.4
  kernel:

   <<>>
   tag=mlock203 stime=1537369891
   cmdline="mlock203"
   contacts=""
   analysis=exit
   <<>>
   tst_test.c:1063: INFO: Timeout per run is 0h 05m 00s
   mlock203.c:63: FAIL: Locking one memory again increased VmLck

   Summary:
   passed   0
   failed   1
   skipped  0
   warnings 0

  == Fix ==
  b155b4fd (mm: mlock: avoid increase mm->locked_vm on mlock() when already 
mlock2(,MLOCK_ONFAULT))

  A test kernel for Xenial / Xenial-KVM could be found here:
  http://people.canonical.com/~phlin/kernel/lp-1793451-mlock203/

  == Regression Potential ==
  Low, this patch prevents mm->locked_vm from increment just by adding an extra 
check to see if the old vm_flags is already VM_LOCKED.

  == Test Case ==
  Run the mlock203 test in ubuntu_ltp_syscalls test suite. And it will pass 
with the patched kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1068-aws 4.4.0-1068.78
  ProcVersionSignature: User Name 4.4.0-1068.78-aws 4.4.144
  Uname: Linux 4.4.0-1068-aws x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Thu Sep 20 06:44:13 2018
  Ec2AMI: ami-0e32ec5bc225539f5
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2b
  Ec2InstanceType: c3.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  SourcePackage: linux-aws
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1804071] Re: linux-aws-edge: 4.15.0-1028.29~16.04.1 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-xenial

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the 4.15.0-1028.29~16.04.1 upload package. This
  bug will contain status and testing results related to that upload.
  
  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
  phase: Uploaded
  reason:
-   promote-to-proposed: Builds not complete
+   promote-to-proposed: Ready for review

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

Title:
  linux-aws-edge: 4.15.0-1028.29~16.04.1 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-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 upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  This bug is for tracking the 4.15.0-1028.29~16.04.1 upload package.
  This bug will contain status and testing results related to that
  upload.

  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
  phase: Uploaded
  reason:
promote-to-proposed: Ready for review

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

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

[Kernel-packages] [Bug 1793464] Re: Kernel panic after the ubuntu_nbd_smoke_test on Xenial kernel

[Po-Hsu Lin]

** Changed in: ubuntu-kernel-tests
   Status: New => Fix Released

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

Title:
  Kernel panic after the ubuntu_nbd_smoke_test on Xenial kernel

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  == SRU Justification ==

  When running the Ubuntu nbd autotest regression test we trip a hang
  and then a little later a panic message.  There are two upstream
  fixes required as this is actually two issues in one. One fix is to 
  not to shutdown the sock when IRQs are disable and a second to fix is
  to race in the nbd ioctl.

  == Fix ==

  Upstream commits:

  23272a6754b81ff6503e09c743bb4ceeeab39997
nbd: Remove signal usage

  1f7b5cf1be4351e60cf8ae7aab976503dd73c5f8
nbd: Timeouts are not user requested disconnects

  0e4f0f6f63d3416a9e529d99febfe98545427b81
nbd: Cleanup reset of nbd and bdev after a disconnect

  c261189862c6f65117eb3b1748622a08ef49c262
nbd: don't shutdown sock with irq's disabled

  97240963eb308d8d21a89c0459822f7ea98463b4
nbd: fix race in ioctl

  The first 3 patches are prerequisites required for the latter two fixes to 
apply and work correctly.  Most of these backports are minor patch wiggles
  required because later patches have been applied to the driver in earlier 
fixes to this driver.
 

  == Regression Potential ==

  These fixes just touch nbd, so the regression potential is just
  limited to this. Secondly, we are pulling in upstream fixes that exist
  in Bionic and Cosmic kernels, so these are tried and tested fixes.

  == Test Case ==

1. Deploy a node with 4.4 Xenial
2. Run the ubuntu_nbd_smoke_test

  Without the fix, we get hang/crashes.  With the fix one can run this test
  multiple times without any issues at all.

  
  

  This issue can be reproduced on AMD64 KVM //bare-metal node, s390x
  zKVM node

  The test itself will pass, but the system will hang after a few
  second.

  Steps:
    1. Deploy a node with 4.4 Xenial
    2. Run the ubuntu_nbd_smoke_test

  If you have access to the console, you will see that this system
  actually bumped into a kernel panic:

   Unable to handle kernel pointer dereference in virtual kernel address space
   failing address: 03ff802c1000 TEID: 03ff802c1803
   Fault in home space mode while using kernel ASCE.
   Log here (s390x KVM): https://pastebin.ubuntu.com/p/dNmtvbGjmz/

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-136-generic 4.4.0-136.162
  ProcVersionSignature: Ubuntu 4.4.0-136.162-generic 4.4.144
  Uname: Linux 4.4.0-136-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Thu Sep 20 03:46:00 2018
  HibernationDevice: RESUME=UUID=ca468a9c-9563-442c-85c6-6055e800a66e
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:

  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:

  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=b65b756a-ba4e-4c53-aa32-0db2bdb50bb3 
crashkernel=196M
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-136-generic N/A
   linux-backports-modules-4.4.0-136-generic  N/A
   linux-firmware 1.157.20
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1786894] Re: test_265_config_retpoline in kernel_security_test failed on 3.13 Precise

[Po-Hsu Lin]

Hi Juerg,
Thanks for the feedback, so I think this should be fixed in the 
qa-regression-testing test suite now.

** Also affects: qa-regression-testing
   Importance: Undecided
   Status: New

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

** Changed in: ubuntu-kernel-tests
 Assignee: Po-Hsu Lin (cypressyew) => (unassigned)

** Changed in: qa-regression-testing
   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/1786894

Title:
  test_265_config_retpoline in kernel_security_test failed on 3.13
  Precise

Status in QA Regression Testing:
  Confirmed
Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Justification ==
  In the Precise 3.13 kernel, the CONFIG_RETPOLINE was set to y in commit 
eae992be4, which should be disabled to meet the security team's requirement.

  ==
   FAIL: test_265_config_retpoline (__main__.KernelSecurityConfigTest)
   Ensure retpoline configuration option is set
   --
   Traceback (most recent call last):
   File "./test-kernel-security.py", line 2445, in test_265_config_retpoline
   self.assertKernelConfig('RETPOLINE', expected)
   File "./test-kernel-security.py", line 209, in assertKernelConfig
   self.assertKernelConfigUnset(name)
   File "./test-kernel-security.py", line 200, in assertKernelConfigUnset
   '%s option was expected to be unset in the kernel config' % name)
   AssertionError: RETPOLINE option was expected to be unset in the kernel 
config

  In this test case, this config was expected to be NOT set:
  elif self.lsb_release['Release'] == 12.04:
  self._skipped("RETPOLINE compiler not in precise")
  expected = False
  self.assertKernelConfig('RETPOLINE', expected)

  == Fix ==
  [Precise/lts-backport-trusty][SRU][PATCHv2] Revert "UBUNTU: [Config] 
CONFIG_RETPOLINE=y"

  == Test ==
  The test_265_config_retpoline will pass after disabling CONFIG_RETPOLINE

  == Regression Potential ==
  Minimal.
  No code changes, just a config changes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1786894/+subscriptions

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

[Kernel-packages] [Bug 1786729] Re: execveat03 in ubuntu_ltp_syscalls failed on X/B

[Po-Hsu Lin]

Passed with Xenial SRU tests.


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

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

Title:
  execveat03 in ubuntu_ltp_syscalls failed on X/B

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

Bug description:
  == Justification ==
  The code in cap_inode_getsecurity(), introduced by commit 8db6c34f1dbc
  ("Introduce v3 namespaced file capabilities"), should use
  d_find_any_alias() instead of d_find_alias() do handle unhashed dentry
  correctly. This is needed, for example, if execveat() is called with an
  open but unlinked overlayfs file, because overlayfs unhashes dentry on
  unlink.
  This is a regression of real life application, first reported at
  https://www.spinics.net/lists/linux-unionfs/msg05363.html

  With the execveat03 test in the LTP test suite on an affected kernel, it will 
fail with:
  <<>>
  tag=execveat03 stime=1534135632
  cmdline="execveat03"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1017: INFO: Timeout per run is 0h 05m 00s
  execveat03.c:70: FAIL: execveat() returned unexpected errno: EINVAL

  Summary:
  passed   0
  failed   1
  skipped  0
  warnings 0

  == Fix ==
  355139a8 (cap_inode_getsecurity: use d_find_any_alias() instead of
   d_find_alias())

  It can be cherry-picked for Bionic, but it needs to be backported to
  Xenial along with the logic when we backport 8db6c34f1dbc (bug
  1778286).

  The test kernel for Xenial / Bionic could be found here:
  http://people.canonical.com/~phlin/kernel/lp-1786729-execveat03/

  This patch has already been cherry-picked into Cosmic and Unstable.

  == Regression Potential ==
  Low, this patch just uses a correct function to handle unhashed dentry, and 
it's been applied in both upstream and our newer kernel.

  == Test Case ==
  Run the reproducer in the commit message, or,
  run the execveat03 test in ubuntu_ltp_syscalls test suite. And it will pass 
with the patched kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1064-aws 4.4.0-1064.74
  ProcVersionSignature: User Name 4.4.0-1064.74-aws 4.4.140
  Uname: Linux 4.4.0-1064-aws x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Mon Aug 13 04:51:09 2018
  Ec2AMI: ami-529fb82a
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2b
  Ec2InstanceType: x1e.xlarge
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  SourcePackage: linux-aws
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1793451] Re: mlock203 test in ubuntu_ltp_syscalls failed with Xenial kernel

[Po-Hsu Lin]

Passed with Xenial SRU

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

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

Title:
  mlock203 test in ubuntu_ltp_syscalls failed with Xenial kernel

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

Bug description:
  == Justification ==
  When one vma was with flag VM_LOCKED|VM_LOCKONFAULT (by invoking
  mlock2(,MLOCK_ONFAULT)), it can again be populated with mlock() with
  VM_LOCKED flag only.

  There is a hole in mlock_fixup() which increase mm->locked_vm twice even
  the two operations are on the same vma and both with VM_LOCKED flags.

  The issue can be reproduced by following code:

    mlock2(p, 1024 * 64, MLOCK_ONFAULT); //VM_LOCKED|VM_LOCKONFAULT
    mlock(p, 1024 * 64);  //VM_LOCKED

  Then check the increase VmLck field in /proc/pid/status(to 128k).

  When vma is set with different vm_flags, and the new vm_flags is with
  VM_LOCKED, it is not necessarily be a "new locked" vma.

  There is a dedicated reproducer, the "mlock203" test in
  ubuntu_ltp_syscalls, you can see the failure for all the Ubuntu 4.4
  kernel:

   <<>>
   tag=mlock203 stime=1537369891
   cmdline="mlock203"
   contacts=""
   analysis=exit
   <<>>
   tst_test.c:1063: INFO: Timeout per run is 0h 05m 00s
   mlock203.c:63: FAIL: Locking one memory again increased VmLck

   Summary:
   passed   0
   failed   1
   skipped  0
   warnings 0

  == Fix ==
  b155b4fd (mm: mlock: avoid increase mm->locked_vm on mlock() when already 
mlock2(,MLOCK_ONFAULT))

  A test kernel for Xenial / Xenial-KVM could be found here:
  http://people.canonical.com/~phlin/kernel/lp-1793451-mlock203/

  == Regression Potential ==
  Low, this patch prevents mm->locked_vm from increment just by adding an extra 
check to see if the old vm_flags is already VM_LOCKED.

  == Test Case ==
  Run the mlock203 test in ubuntu_ltp_syscalls test suite. And it will pass 
with the patched kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1068-aws 4.4.0-1068.78
  ProcVersionSignature: User Name 4.4.0-1068.78-aws 4.4.144
  Uname: Linux 4.4.0-1068-aws x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Thu Sep 20 06:44:13 2018
  Ec2AMI: ami-0e32ec5bc225539f5
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2b
  Ec2InstanceType: c3.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  SourcePackage: linux-aws
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1804007] Re: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common

[Seth Arnold]

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

** Information type changed from Private Security to Public

** Also affects: nvidia-graphics-drivers-390 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  package nvidia-340 (not installed) failed to install/upgrade: trying
  to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in
  package nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1

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

Bug description:
  idk why every time i want install graphic card on 18.04 LTS always
  being like this

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-340 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Mon Nov 19 12:10:24 2018
  ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which 
is also in package nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1
  InstallationDate: Installed on 2018-11-17 (2 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 (not installed) failed to install/upgrade: trying 
to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package 
nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1
  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-340/+bug/1804007/+subscriptions

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

[Kernel-packages] [Bug 1802772] Re: linux-lts-trusty: 3.13.0-163.213~precise1 -proposed tracker

[Brad Figg]

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  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: 1802769
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   regression-testing: Testing in progress
security-signoff: Waiting for signoff
verification-testing: Testing in progress

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

Title:
  linux-lts-trusty: 3.13.0-163.213~precise1 -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-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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  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: 1802769
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Waiting for signoff
verification-testing: Testing in progress

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

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

[Kernel-packages] [Bug 1776616] Re: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-Off"

[Guy Rouillier]

Ugh, tab key did a submit!  Launchpad needs some work.

So, in summary:

   - with "acpi=off noapic", all kernels can reboot but hang during shutdown
   
   - without "acpi=off noapic", <= 4.5.7 can reboot and shutdown, but later 
kernels hang during both reboot and shutdown.

Since I can't run the ancient kernels forever, I'm adding "acpi=off
noapic" and will just live with the hang during shutdown.  Fortunately,
the filesystem appears to close before hang, so I don't have filesystem
corruptions when I start up the next time.

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

Title:
  Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-
  Off"

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

Bug description:
  Hardware: HPE ProLiant DL360 gen9
  Ubuntu Version: 18.04

  Problem: When rebooting the server, everything goes well (shutting
  down services, unmounting etc) until the last step where it reads
  "Starting Reboot". At this point the system is getting stuck and
  nothing else can can be done than holding the power button in for a
  long enough time to turn it off. At the same time as the system get
  stuck, a red error light is lightening up on the server. This light is
  green until it reaches this "Starting Reboot" stage. The same happens
  if the server is shutdown, with the difference that the last message
  is "Starting Power-Off" instead of "Starting Reboot".

  The server is installed with a new clean 18.04 installation. This
  server was rebooting/shutting down without a problem with all releases
  between 16.04 and 17.10.

  This problem is serious as it prevents remote reboot.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 13 11:16 seq
   crw-rw 1 root audio 116, 33 Jun 13 11:16 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=none
  MachineType: HP ProLiant DL360 Gen9
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-23-generic 
root=ZFS=rpool/ROOT/ubuntu ro
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/21/2018
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.board.name: ProLiant DL360 Gen9
  dmi.board.vendor: HP
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd05/21/2018:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL360 Gen9
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1802772] Re: linux-lts-trusty: 3.13.0-163.213~precise1 -proposed tracker

[Po-Hsu Lin]

3.13.0-163.213~precise1 - generic
Regression test CMPL, RTB.

Issue to note in amd64:
  ubuntu_qrt_kernel_security - CONFIG_RETPOLINE=y in kernel (bug 1786894)

Issue to note in i386:
  ubuntu_qrt_kernel_security - CONFIG_RETPOLINE=y in kernel (bug 1786894)


** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

** Tags added: regression-testing-passed

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

Title:
  linux-lts-trusty: 3.13.0-163.213~precise1 -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-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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  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: 1802769
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Testing in progress
security-signoff: Waiting for signoff
verification-testing: Testing in progress

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

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

[Kernel-packages] [Bug 1776616] Re: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-Off"

[Guy Rouillier]

I tried with 4.5.7, nothing changes with WiFi on or off

However, back to the original problem, while playing with WiFi, I
discovered that 4.5.7 was now freezing during shutdown (reboot okay).
So, I then tried removing "acpi=off noapic" again, and 4.5.7 was now
able to reboot and shutdown.  But as before, any later kernel now hangs
during both reboot and shutdown.

So, in summary:

   - with "acpi=off noapic", all kernels can reboot but hang during
shutdown

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

Title:
  Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-
  Off"

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

Bug description:
  Hardware: HPE ProLiant DL360 gen9
  Ubuntu Version: 18.04

  Problem: When rebooting the server, everything goes well (shutting
  down services, unmounting etc) until the last step where it reads
  "Starting Reboot". At this point the system is getting stuck and
  nothing else can can be done than holding the power button in for a
  long enough time to turn it off. At the same time as the system get
  stuck, a red error light is lightening up on the server. This light is
  green until it reaches this "Starting Reboot" stage. The same happens
  if the server is shutdown, with the difference that the last message
  is "Starting Power-Off" instead of "Starting Reboot".

  The server is installed with a new clean 18.04 installation. This
  server was rebooting/shutting down without a problem with all releases
  between 16.04 and 17.10.

  This problem is serious as it prevents remote reboot.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 13 11:16 seq
   crw-rw 1 root audio 116, 33 Jun 13 11:16 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=none
  MachineType: HP ProLiant DL360 Gen9
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-23-generic 
root=ZFS=rpool/ROOT/ubuntu ro
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/21/2018
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.board.name: ProLiant DL360 Gen9
  dmi.board.vendor: HP
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd05/21/2018:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL360 Gen9
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1804040] Re: nvidia-dkms-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed to build [ERROR: Kernel configuration is invalid.]

[Daniel van Vugt]

** Summary changed:

- nvidia-dkms-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed to build
+ nvidia-dkms-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed to build 
[ERROR: Kernel configuration is invalid.]

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

Title:
  nvidia-dkms-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed
  to build [ERROR: Kernel configuration is invalid.]

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

Bug description:
  failed to update my system

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-dkms-390 390.77-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-39-generic
  Date: Mon Nov 19 23:00:47 2018
  InstallationDate: Installed on 2018-09-16 (64 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageVersion: 390.77-0ubuntu0.18.04.1
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: nvidia-graphics-drivers-390
  Title: nvidia-dkms-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1802776] Re: linux: 4.4.0-140.166 -proposed tracker

[Taihsiang Ho]

Hardware Certification have begun testing this -proposed kernel.

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => In Progress

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

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

Title:
  linux: 4.4.0-140.166 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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-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:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

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

  backports: bug 1802778 (linux-aws), bug 1802779 (linux-lts-xenial)
  derivatives: bug 1802780 (linux-raspi2), bug 1802781 (linux-snapdragon), bug 
1802783 (linux-euclid), bug 1802785 (linux-aws), bug 1802786 (linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Testing FAILED
certification-testing: Testing in progress
regression-testing: Testing in progress
security-signoff: Waiting for signoff
snap-certification-testing: Ready
verification-testing: Testing in progress

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

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

[Kernel-packages] [Bug 1803678] Re: linux-oem: 4.15.0-1028.33 -proposed tracker

[Taihsiang Ho]

Hardware Certification have begun testing this -proposed kernel.

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => In Progress

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

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

Title:
  linux-oem: 4.15.0-1028.33 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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-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:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  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: 1803592
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Testing FAILED
certification-testing: Testing in progress
regression-testing: Testing in progress
security-signoff: Waiting for signoff
verification-testing: Testing in progress

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

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

[Kernel-packages] [Bug 1803592] Re: linux: 4.15.0-42.45 -proposed tracker

[Taihsiang Ho]

Hardware Certification have begun testing this -proposed kernel.

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => In Progress

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

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

Title:
  linux: 4.15.0-42.45 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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-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:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the 4.15.0-42.45 upload package. This bug
  will contain status and testing results related to that upload.

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

  -- swm properties --
  backports: null
  boot-testing-requested: true
  bugs-spammed: true
  derivatives: bug 1803678 (linux-oem)
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Testing FAILED
certification-testing: Testing in progress
regression-testing: Testing in progress
security-signoff: Waiting for signoff
verification-testing: Testing in progress

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

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

[Kernel-packages] [Bug 1802769] Re: linux: 3.13.0-163.213 -proposed tracker

[Taihsiang Ho]

Hardware Certification have begun testing this -proposed kernel.

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => In Progress

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

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

Title:
  linux: 3.13.0-163.213 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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-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:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

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

  backports: bug 1802772 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Testing FAILED
certification-testing: Testing in progress
regression-testing: Testing in progress
security-signoff: Waiting for signoff
verification-testing: Testing in progress

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

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

[Kernel-packages] [Bug 1585434] Re: ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4]

[dman777]

I am having this bug also and it crashes my system. I have rc = [-5] in
my error output.

Can this be moved to high importance?

one@localhost:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.5 LTS
Release:16.04
Codename:   xenial
one@localhost:~$

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

Title:
  ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4]

  ecryptfs_readpage: Error decrypting page; rc = [-4]

  I dont' have this issue showing in dmesg when using 3.19 kernel,  only
  with later kernels.  Is it related to selecting encrypted home on
  install or something?

   I don't notice any issues with performance because of it or have any
  other error messages.  I am using default ubuntu xenial 16.04 with
  unity.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.40
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  cooloutac   2054 F pulseaudio
   /dev/snd/pcmC0D0p:   cooloutac   2054 F...m pulseaudio
   /dev/snd/controlC0:  cooloutac   2054 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue May 24 22:38:44 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=0118ec29-2bd5-4cbc-9800-9c04bbe083d1
  InstallationDate: Installed on 2016-05-20 (5 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. Studio XPS 7100
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=fcd92967-7d59-44bf-bb88-06efa6fac5f7 ro ipv6.disable=1 quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0NWWY0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd09/10/2010:svnDellInc.:pnStudioXPS7100:pvr:rvnDellInc.:rn0NWWY0:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: Studio XPS 7100
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1802573] Re: Thinkpad x220 - Unable to use 2560x1440 external display connected via DisplayPort due flashing black screen

[Daniel van Vugt]

I suggest trying a more stable newer version in that case, like:
  http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19.2/

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

Title:
  Thinkpad x220 - Unable to use 2560x1440 external display connected via
  DisplayPort due flashing black screen

Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  New

Bug description:
  I have a fresh install of 18.10 on an old Thinkpad x220. Everything
  works fine with the internal display or an external Dell G2410
  (1920x1080) connected via VGA. But when I try to switch to an external
  BenQ PD2710QC (2560x1440) I only see the screen for a few seconds at a
  time and then it flashes to black. This happens consistently for
  minutes--it never "settles down".

  I've tried the default configuration as well as copying xorg.conf from
  /usr/share/doc/xserver-xorg-video-intel into /etc/x11. I've tried both
  xorg configurations with nomodeset in the bootloader and without. I
  have not been able to find any configuration that allows this external
  DisplayPort display to work.

  The same hardware combination works fine in Windows 10.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Fri Nov  9 13:10:59 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21da]
  InstallationDate: Installed on 2018-11-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 42872WU
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=cd4f21be-48dd-48e7-b289-a59a32bd0be3 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
Identifier "Intel"
Driver "intel"
   #Option "AccelMethod" "uxa"
   EndSection
  dmi.bios.date: 06/21/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET76WW (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42872WU
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET76WW(1.46):bd06/21/2018:svnLENOVO:pn42872WU:pvrThinkPadX220:rvnLENOVO:rn42872WU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X220
  dmi.product.name: 42872WU
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
  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 N/A
  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

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

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

[Kernel-packages] [Bug 1776616] Re: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-Off"

[Guy Rouillier]

Hey! I'm typing this from the laptop over WiFi.  I powered on the laptop
with the WiFi off, but then turned it on before booting up 18.04.  I got
connected, then did a reboot.  That went without any issues, and I got
back into Ubuntu 18.04.  After getting back into Ubuntu, I started up
this browser session; Ubuntu remembered my WiFi configuration from the
previous boot.  So, no issues rebooting with WiFi turned on (or off).
Sorry, I no longer have 16.04, so I can't comment on that.  My active
kernel is 4.15.0-39-generic.

You say your laptop freezes on the Toshiba splash screen?  Or did you
mean the Ubuntu splash screen?  Either way, mine is not freezing, either
during power up or reboot.  I doubt the WiFi being on will alter my
hangs on power down, though I'll try that now.  Hmm, I still have 4.5.7,
I'll try rebooting with that to see if it changes anything.  That was a
16.04 kernel.

Hope this helps.

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

Title:
  Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-
  Off"

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

Bug description:
  Hardware: HPE ProLiant DL360 gen9
  Ubuntu Version: 18.04

  Problem: When rebooting the server, everything goes well (shutting
  down services, unmounting etc) until the last step where it reads
  "Starting Reboot". At this point the system is getting stuck and
  nothing else can can be done than holding the power button in for a
  long enough time to turn it off. At the same time as the system get
  stuck, a red error light is lightening up on the server. This light is
  green until it reaches this "Starting Reboot" stage. The same happens
  if the server is shutdown, with the difference that the last message
  is "Starting Power-Off" instead of "Starting Reboot".

  The server is installed with a new clean 18.04 installation. This
  server was rebooting/shutting down without a problem with all releases
  between 16.04 and 17.10.

  This problem is serious as it prevents remote reboot.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 13 11:16 seq
   crw-rw 1 root audio 116, 33 Jun 13 11:16 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=none
  MachineType: HP ProLiant DL360 Gen9
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-23-generic 
root=ZFS=rpool/ROOT/ubuntu ro
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/21/2018
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.board.name: ProLiant DL360 Gen9
  dmi.board.vendor: HP
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd05/21/2018:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL360 Gen9
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th

[AaronMa]

@dr_strangehate, thanks for test details.

I will report this feedback to 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/1791427

Title:
  Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1
  Carbon 6th

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 18.04.1

  Terminology in case we use different terms:
  touchpad - just the rectangular touch-sensitive surface below the keyboard 
(xinput lists it as Synaptics TM3288-011)
  trackpoint - the red thingy built into the keyboard + 3 physical buttons 
below the keyboard (trackpoint and buttons are integrated together; listed in 
xinput as TPPS/2 Elan TrackPoint)

  On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which
  enables proper S3 deep sleep state - users no longer have to patch
  DSDT tables to get it. It can be enabled in the BIOS settings. In X1
  carbon 6th generation models that have NFC, when laptop wakes from
  suspend by opening the lid, in most cases both touchpad and trackpoint
  stop working completely. They are also no longer listed when running
  xinput command. Sometimes just one of them stops working, usually the
  trackpoint. In some rare cases it is possible to bring them back by
  using these commands:

  echo -n none > /sys/devices/platform/i8042/serio1/drvctl
  echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl
  rmmod psmouse
  modprobe psmouse

  These worked properly when waking up from S2Idle sleep state (had
  these in a script that runs after waking the machine from suspend),
  but with S3 deep sleep these rarely work and the only way to bring
  back touchpad and/or trackpoint is turning off the machine and turning
  it on (restart does not help).

  I could not find any pattern that would show when the input devices
  stop working or start working again using the commands mentioned
  above. It's completely random from my perspective.

  This is happening on the standard issue 4.15.0-33-generic kernel that
  shipped with my Ubuntu 18.04 (with updates), as well as with newer
  mainline kernels, such as the newest point versions of 4.17, 4.18 and
  4.19 RC2.

  This happens regardless of whether "blacklist i2c_i801" is commented
  out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of
  whether "psmouse.synaptics_intertouch=1" is passed as grub parameter.
  Presence of TLP does not make it better, nor worse.

  It appears that non-NFC models are not affected. I know at least one
  Arch Linux user who has the exact same model, but without this issue.
  I'm using synaptics driver (no libinput installed), he uses libinput
  and doesn't have synaptics, if that information is of any use.
  Libinput does not seem to help.

  This forum thread also has more details from users who updated their
  BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux-
  Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka-
  Suspend-to/td-p/3998182/page/27

  Another related thread:
  https://bbs.archlinux.org/viewtopic.php?id=236367

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   maciej 2651 F...m pulseaudio
   /dev/snd/controlC0:  maciej 2651 F pulseaudio
  CurrentDesktop: i3
  Date: Sat Sep  8 13:45:43 2018
  HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e
  InstallationDate: Installed on 2018-07-21 (49 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56b2 IMC Networks 
   Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless 
optical mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20KH006KPB
  ProcFB:
   0 EFI VGA
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET55W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KH006KPB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  

[Kernel-packages] [Bug 1800664] Re: Add checksum offload and TSO support for HiNIC adapters

[dann frazier]

** Tags removed: verification-done-cosmic
** Tags added: verification-failed-cosmic

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

Title:
  Add checksum offload and TSO support for HiNIC adapters

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

Bug description:
  [Impact]
  Increases throughput by more than 2x, as measured by the iperf benchmark.

  [Test Case]
  iperf -c 192.168.122.10 -P5

  [Fix]
  cc18a7543d2f6 net-next/hinic: add checksum offload and TSO support

  [Regression Risk]
  Clean cherry-pick restricted to a single driver that has been explicitly 
tested. A regression risk is that these bugs in these new features, which are 
enabled by default, could impact existing deployments. These features can, 
however, be disabled by ethtool which helps mitigate that risk.

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

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

[Kernel-packages] [Bug 1800664] Re: Add checksum offload and TSO support for HiNIC adapters

[dann frazier]

Ike has since done some more extensive testing, and found that
performance actually *drops* with longer iperf runs. With a 900s run,
he's seeing it go down to ~200Mbps, while the kernel emits messages like
these:

[ 1070.047048] ITS queue timeout (65440 65504 1120)
[ 1070.051658] ITS cmd its_build_inv_cmd failed

It's unclear if this is actually an issue with the patch, or a platform-
specific issue, but either way I think we need to change this status to
verification-failed. I've reported this upstream.

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

Title:
  Add checksum offload and TSO support for HiNIC adapters

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

Bug description:
  [Impact]
  Increases throughput by more than 2x, as measured by the iperf benchmark.

  [Test Case]
  iperf -c 192.168.122.10 -P5

  [Fix]
  cc18a7543d2f6 net-next/hinic: add checksum offload and TSO support

  [Regression Risk]
  Clean cherry-pick restricted to a single driver that has been explicitly 
tested. A regression risk is that these bugs in these new features, which are 
enabled by default, could impact existing deployments. These features can, 
however, be disabled by ethtool which helps mitigate that risk.

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

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

[Kernel-packages] [Bug 1804071] Re: linux-aws-edge: 4.15.0-1028.29~16.04.1 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => Fix Released

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

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: Confirmed => Fix Released

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

** Description changed:

  This bug is for tracking the 4.15.0-1028.29~16.04.1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
- kernel-stable-phase:Packaging
- kernel-stable-phase-changed:Monday, 19. November 2018 23:10 UTC
- 
  -- swm properties --
  phase: Packaging
  reason:
prepare-package: Package not yet uploaded
prepare-package-meta: Package not yet uploaded
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Tuesday, 20. November 2018 00:13 UTC

** Description changed:

  This bug is for tracking the 4.15.0-1028.29~16.04.1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
- phase: Packaging
+ phase: Uploaded
  reason:
-   prepare-package: Package not yet uploaded
-   prepare-package-meta: Package not yet uploaded
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Tuesday, 20. November 2018 00:13 UTC
+   promote-to-proposed: 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/1804071

Title:
  linux-aws-edge: 4.15.0-1028.29~16.04.1 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
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 upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  This bug is for tracking the 4.15.0-1028.29~16.04.1 upload package.
  This bug will contain status and testing results related to that
  upload.

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

  -- swm properties --
  phase: Uploaded
  reason:
promote-to-proposed: Builds not complete

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

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

[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th

[dr_strangehate]

So, I've decided to check the new firmware. I installed Windows 10
(wiping out my Ubuntu install in the process), installed Lenovo Vantage
and installed all firmware updates that it allowed me to, including
touchpad and trackpoint firmware.

Then I installed fresh new Ubuntu 18.04.1. One good thing is that the
installer allowed me to use touchpad and trackpoint properly (they did
not work the last time I was running the installer, had to use external
mouse).

Unfortunately, longer suspend (like through the night) still kills
touchpad and/or trackpoint. And even the "none"/"reconnect" trick doe
snot bring them back, neither does rmmod and modprobe on psmouse (module
(which used to be a working solution at some point when S3 did not
work).

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

Title:
  Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1
  Carbon 6th

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 18.04.1

  Terminology in case we use different terms:
  touchpad - just the rectangular touch-sensitive surface below the keyboard 
(xinput lists it as Synaptics TM3288-011)
  trackpoint - the red thingy built into the keyboard + 3 physical buttons 
below the keyboard (trackpoint and buttons are integrated together; listed in 
xinput as TPPS/2 Elan TrackPoint)

  On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which
  enables proper S3 deep sleep state - users no longer have to patch
  DSDT tables to get it. It can be enabled in the BIOS settings. In X1
  carbon 6th generation models that have NFC, when laptop wakes from
  suspend by opening the lid, in most cases both touchpad and trackpoint
  stop working completely. They are also no longer listed when running
  xinput command. Sometimes just one of them stops working, usually the
  trackpoint. In some rare cases it is possible to bring them back by
  using these commands:

  echo -n none > /sys/devices/platform/i8042/serio1/drvctl
  echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl
  rmmod psmouse
  modprobe psmouse

  These worked properly when waking up from S2Idle sleep state (had
  these in a script that runs after waking the machine from suspend),
  but with S3 deep sleep these rarely work and the only way to bring
  back touchpad and/or trackpoint is turning off the machine and turning
  it on (restart does not help).

  I could not find any pattern that would show when the input devices
  stop working or start working again using the commands mentioned
  above. It's completely random from my perspective.

  This is happening on the standard issue 4.15.0-33-generic kernel that
  shipped with my Ubuntu 18.04 (with updates), as well as with newer
  mainline kernels, such as the newest point versions of 4.17, 4.18 and
  4.19 RC2.

  This happens regardless of whether "blacklist i2c_i801" is commented
  out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of
  whether "psmouse.synaptics_intertouch=1" is passed as grub parameter.
  Presence of TLP does not make it better, nor worse.

  It appears that non-NFC models are not affected. I know at least one
  Arch Linux user who has the exact same model, but without this issue.
  I'm using synaptics driver (no libinput installed), he uses libinput
  and doesn't have synaptics, if that information is of any use.
  Libinput does not seem to help.

  This forum thread also has more details from users who updated their
  BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux-
  Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka-
  Suspend-to/td-p/3998182/page/27

  Another related thread:
  https://bbs.archlinux.org/viewtopic.php?id=236367

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   maciej 2651 F...m pulseaudio
   /dev/snd/controlC0:  maciej 2651 F pulseaudio
  CurrentDesktop: i3
  Date: Sat Sep  8 13:45:43 2018
  HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e
  InstallationDate: Installed on 2018-07-21 (49 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56b2 IMC Networks 
   Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless 
optical mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20KH006KPB
  ProcFB:
   0 EFI VGA
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 

[Kernel-packages] [Bug 1802738] Re: cdc_acm driver lacks trival support for Hiro (Conexant) H05228 USB modem

[Maarten Jacobs]

Hello Joseph,

To keep things in sync here (and to make sure the bug doesn't expire due
to inactivity):

1. I worked my way through the process for submitting a kernel patch. (Not for 
the faint hearted I might add ;))
2. The patch has been submitted - now I have to wait and see if there's anybody 
listening.

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

Title:
  cdc_acm driver lacks trival support for Hiro (Conexant) H05228 USB
  modem

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I procured a USB modem manufactured by Hiro (model number H50228).
  This is in fact a Conexant modem, and while some conexant models are
  supported in cdc_adm, this particular type is not.

  Hence, when I connect the modem to my system, cdc_adm does not
  initialize the modem properly, as evidenced by errors reported through
  journalctl:

  
  Nov 10 21:46:10  kernel: usbcore: registered new interface driver 
cdc_acm
  Nov 10 21:46:10  kernel: cdc_acm: USB Abstract Control Model driver for 
USB modems and ISDN adapters
  Nov 10 21:47:01  kernel: cdc_acm 4-2:1.0: Zero length descriptor 
references
  Nov 10 21:47:01  kernel: cdc_acm: probe of 4-2:1.0 failed with error -22

  Similar errors of this type have been reported previously, and
  following the resolution for these errors I recompiled the cdc_acm
  kernel module, after which the modem is successfully registered:

  Nov 10 21:47:48  kernel: usbcore: registered new interface driver 
cdc_acm
  Nov 10 21:47:48  kernel: cdc_acm: USB Abstract Control Model driver for 
USB modems and ISDN adapters
  Nov 10 21:48:17  kernel: cdc_acm 4-2:1.0: ttyACM0: USB ACM device

  With my modified kernel module, the modem works (at least for the
  purposes I need it).

  I will attach the patch once this bug has been opened. I don't know
  how to submit a patch for formal consideration so need some help on
  that front... Neither am I sure how to figure out exactly if this was
  already addressed in an upstream fix.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-138-generic 4.4.0-138.164
  ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155
  Uname: Linux 4.4.0-138-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jacobsma   4053 F pulseaudio
   /dev/snd/controlC0:  jacobsma   4053 F pulseaudio
   /dev/snd/controlC2:  jacobsma   4053 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Nov 11 11:20:40 2018
  HibernationDevice: RESUME=UUID=899fa33b-30cb-41f4-b709-557ad528a5bd
  InstallationDate: Installed on 2016-03-06 (979 days ago)
  InstallationMedia: Xubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-138-generic 
root=UUID=70a8bdf6-e697-4112-b584-4b650002555d ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-138-generic N/A
   linux-backports-modules-4.4.0-138-generic  N/A
   linux-firmware 1.157.20
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2018-03-16 (240 days ago)
  dmi.bios.date: 09/11/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1701
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L-M LX PLUS
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1701:bd09/11/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLXPLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1804071] Re: linux-aws-edge: 4.15.0-1028.29~16.04.1 -proposed tracker

[Brad Figg]

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

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

** Description changed:

  This bug is for tracking the 4.15.0-1028.29~16.04.1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+ 
+ kernel-stable-phase:Packaging
+ kernel-stable-phase-changed:Monday, 19. November 2018 23:10 UTC

** Description changed:

  This bug is for tracking the 4.15.0-1028.29~16.04.1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  kernel-stable-phase:Packaging
  kernel-stable-phase-changed:Monday, 19. November 2018 23:10 UTC
+ 
+ -- swm properties --
+ phase: Packaging
+ reason:
+   prepare-package: Package not yet uploaded
+   prepare-package-meta: 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/1804071

Title:
  linux-aws-edge: 4.15.0-1028.29~16.04.1 -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:
  Confirmed
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 upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  This bug is for tracking the 4.15.0-1028.29~16.04.1 upload package.
  This bug will contain status and testing results related to that
  upload.

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

  kernel-stable-phase:Packaging
  kernel-stable-phase-changed:Monday, 19. November 2018 23:10 UTC

  -- swm properties --
  phase: Packaging
  reason:
prepare-package: Package not yet uploaded
prepare-package-meta: Package not yet uploaded

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

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

[Kernel-packages] [Bug 1804071] [NEW] linux-aws-edge: 4.15.0-1028.29~16.04.1 -proposed tracker

[Kamal Mostafa]

Public bug reported:

This bug is for tracking the 4.15.0-1028.29~16.04.1 upload package. This
bug will contain status and testing results related to that upload.

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

** 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: 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/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/upload-to-ppa
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 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


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live xenial

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

** Tags added: kernel-release-tracking-bug-live

** Tags added: xenial

** 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/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/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   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/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-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)

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

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

** Changed in: kernel-sru-workflow/promote-to-updates
   

[Kernel-packages] [Bug 1782177] Re: Screen sometimes jumps to full brightness on resume from suspend

[Bug Watch Updater]

Launchpad has imported 8 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=108703.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2018-11-10T01:18:16+00:00 Luke-schlather wrote:

At night, I usually turn my brightness down as far as it will go using
the brightness keys. This makes it dim, but visible and not off. When I
walk away for a while, the screen goes to sleep, and when I come back
and move the mouse, the screen jumps to full brightness, which is very
unpleasant at night. Investigating, it seems that the brightness in
intel_backlight is getting reset to 4437, but the one in acpi_video0
reads 0.

This can be triggered by running xset dpms force standby. Here's the
conflicting brightness values:

$ for file in brightness max_brightness actual_brightness;
> do
> for directory in /sys/class/backlight/intel_backlight/ 
/sys/class/backlight/acpi_video0/
> do
> echo $directory$file : $(cat $directory$file)
> done
> done
/sys/class/backlight/intel_backlight/brightness : 4437
/sys/class/backlight/acpi_video0/brightness : 0
/sys/class/backlight/intel_backlight/max_brightness : 4437
/sys/class/backlight/acpi_video0/max_brightness : 15
/sys/class/backlight/intel_backlight/actual_brightness : 4437
/sys/class/backlight/acpi_video0/actual_brightness : 0

After I press the button to increase the brightness one notch, they are
back in sync, and then I can turn it back down as well.

$ for file in brightness max_brightness actual_brightness;
> do
> for directory in /sys/class/backlight/intel_backlight/ 
/sys/class/backlight/acpi_video0/
> do
> echo $directory$file : $(cat $directory$file)
> done
> done
/sys/class/backlight/intel_backlight/brightness : 53
/sys/class/backlight/acpi_video0/brightness : 1
/sys/class/backlight/intel_backlight/max_brightness : 4437
/sys/class/backlight/acpi_video0/max_brightness : 15
/sys/class/backlight/intel_backlight/actual_brightness : 53
/sys/class/backlight/acpi_video0/actual_brightness : 1

This is on a fresh install of Xubuntu 18.04 with default packages
including the latest version of the i915 Intel Driver which is active.
Seems like a regression from Xubuntu 16.04, which I ran on the same
laptop without this issue.

I initially filed this as a bug in XFCE power manager but after some
troubleshooting there I can reproduce the same issue under Gnome as
well.

Original bug with troubleshooting:
https://bugs.launchpad.net/ubuntu/+source/xfce4-power-
manager/+bug/1782177

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782177/comments/7


On 2018-11-12T08:36:35+00:00 Lakshminarayana-vudum wrote:

Luke, Can you set kernel parameters drm.debug=0x1e log_buf_len=4M and
reboot the machine. Reproduce the issue and attach the dmesg log from
boot. This way we know more information about the issue.

BTW have you tried this issue with drm-tip?
(https://cgit.freedesktop.org/drm-tip)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782177/comments/8


On 2018-11-13T18:51:59+00:00 Luke-schlather wrote:

Created attachment 142454
DMESG output with drm.debug enabled

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782177/comments/9


On 2018-11-14T08:01:53+00:00 Lakshminarayana-vudum wrote:

Jani, any comments here? verifying with latest drm-tip will help here?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782177/comments/10


On 2018-11-14T08:30:47+00:00 Jani-nikula wrote:

I don't think we have any fixes in drm-tip that should affect this; for
that matter I don't recall changes in the area that should regress
either. Backlight has been fairly solid for some years now.

1) Please paste the sysfs attributes *before* display gets disabled.

2) Is the behaviour reproducible if you don't go to minimum before
disabling display? I.e. stay at the next higher level. Or, use

# echo 1 > /sys/class/backlight/intel_backlight/brightness

to stay above 0.

We do have a check in place to crank the brightness to max if it's at
the minimum upon encoder enable. However, that bit policy has been in
place for ages.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782177/comments/11


On 2018-11-14T08:31:58+00:00 Jani-nikula wrote:

(In reply to Jani Nikula from comment #4)
> We do have a check in place to 

[Kernel-packages] [Bug 1802573] Re: Thinkpad x220 - Unable to use 2560x1440 external display connected via DisplayPort due flashing black screen

[Adam Kessel]

I installed vmlinuz-4.20.0-042000rc3-generic per your request. The
machine won't boot, and just loops infinitely with the error message:

request_module: kmod_concurrent_max (0) close to 0 (max_modprobes: 50), for 
module binfmt-646c, throttling...
request_module: modprobe binfmt-646c cannot be processed, kmod busy with 50 
threads for more than 5 seconds now

I've done some googling and don't see an obvious fix. Any suggestions?

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

Title:
  Thinkpad x220 - Unable to use 2560x1440 external display connected via
  DisplayPort due flashing black screen

Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  New

Bug description:
  I have a fresh install of 18.10 on an old Thinkpad x220. Everything
  works fine with the internal display or an external Dell G2410
  (1920x1080) connected via VGA. But when I try to switch to an external
  BenQ PD2710QC (2560x1440) I only see the screen for a few seconds at a
  time and then it flashes to black. This happens consistently for
  minutes--it never "settles down".

  I've tried the default configuration as well as copying xorg.conf from
  /usr/share/doc/xserver-xorg-video-intel into /etc/x11. I've tried both
  xorg configurations with nomodeset in the bootloader and without. I
  have not been able to find any configuration that allows this external
  DisplayPort display to work.

  The same hardware combination works fine in Windows 10.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Fri Nov  9 13:10:59 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21da]
  InstallationDate: Installed on 2018-11-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 42872WU
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=cd4f21be-48dd-48e7-b289-a59a32bd0be3 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
Identifier "Intel"
Driver "intel"
   #Option "AccelMethod" "uxa"
   EndSection
  dmi.bios.date: 06/21/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET76WW (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42872WU
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET76WW(1.46):bd06/21/2018:svnLENOVO:pn42872WU:pvrThinkPadX220:rvnLENOVO:rn42872WU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X220
  dmi.product.name: 42872WU
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
  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 N/A
  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

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

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

[Kernel-packages] [Bug 1803827] Re: Cant install from usb or normal upgrade(says not supported)

[jonh]

RE Joseph Salisbury:The links are for 64bit but i tried lubuntu 32bit
19.04 (Disco Dingo) Daily Builds and is still the same bug (displays
same as my other device)

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

Title:
  Cant install from usb or normal upgrade(says not supported)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Cant install lubuntu 32 bit 18.10 or 19.04 (Disco Dingo Daily Builds) from 
usb or normal upgrade from 18.04 to 18.10(says not supported) it displays 
cdrom/casper/filesystem.squashfs error for the Asus Eee PC 904HD
  ---
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-39-generic.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asus725 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf7eb8000 irq 24'
     Mixer name : 'Realtek ALC269'
     Components : 'HDA:10ec0269,1043834a,0014'
     Controls  : 22
     Simple ctrls  : 10
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 18.04
  MachineType: ASUSTeK Computer INC. 904HD
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=d88102d1-73dc-40ae-9e3b-8d09460b1ae5 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-39-generic N/A
   linux-backports-modules-4.15.0-39-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-39-generic i686
  UpgradeStatus: Upgraded to bionic on 2018-11-16 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/22/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 904HD
  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.:bvr1002:bd09/22/2008:svnASUSTeKComputerINC.:pn904HD:pvrx.x:rvnASUSTeKComputerINC.:rn904HD:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: 904HD
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK Computer INC.

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

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

[Kernel-packages] [Bug 1803827] Re: Cant install from usb or normal upgrade(says not supported)

[jonh]

** Description changed:

- Cant install 18.10 from usb or normal upgrade from 18.04 to 18.10(says not 
supported) it displays cdrom/casper/filesystem.squashfs error for the Asus Eee 
PC 904HD
+ Cant install lubuntu 32 bit 18.10 or 19.04 (Disco Dingo Daily Builds) from 
usb or normal upgrade from 18.04 to 18.10(says not supported) it displays 
cdrom/casper/filesystem.squashfs error for the Asus Eee PC 904HD
  ---
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-39-generic.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asus725 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf7eb8000 irq 24'
     Mixer name : 'Realtek ALC269'
     Components : 'HDA:10ec0269,1043834a,0014'
     Controls  : 22
     Simple ctrls  : 10
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 18.04
  MachineType: ASUSTeK Computer INC. 904HD
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=d88102d1-73dc-40ae-9e3b-8d09460b1ae5 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-39-generic N/A
   linux-backports-modules-4.15.0-39-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-39-generic i686
  UpgradeStatus: Upgraded to bionic on 2018-11-16 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/22/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 904HD
  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.:bvr1002:bd09/22/2008:svnASUSTeKComputerINC.:pn904HD:pvrx.x:rvnASUSTeKComputerINC.:rn904HD:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: 904HD
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK Computer INC.

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

Title:
  Cant install from usb or normal upgrade(says not supported)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Cant install lubuntu 32 bit 18.10 or 19.04 (Disco Dingo Daily Builds) from 
usb or normal upgrade from 18.04 to 18.10(says not supported) it displays 
cdrom/casper/filesystem.squashfs error for the Asus Eee PC 904HD
  ---
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-39-generic.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asus725 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf7eb8000 irq 24'
     Mixer name : 'Realtek ALC269'
     Components : 'HDA:10ec0269,1043834a,0014'
     Controls  : 22
     Simple ctrls  : 10
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 18.04
  MachineType: ASUSTeK Computer INC. 904HD
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=d88102d1-73dc-40ae-9e3b-8d09460b1ae5 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-39-generic N/A
   linux-backports-modules-4.15.0-39-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-39-generic i686
  UpgradeStatus: Upgraded to bionic on 2018-11-16 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/22/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 904HD
  dmi.board.vendor: ASUSTeK 

[Kernel-packages] [Bug 1797092] Re: xenial guest on arm64 drops to busybox under openstack bionic-rocky

[dann frazier]

Verified - see attached dmesg.

** Attachment added: "dmesg"
   
https://bugs.launchpad.net/ubuntu/bionic/+source/linux-snapdragon/+bug/1797092/+attachment/5214304/+files/dmesg

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

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

Title:
  xenial guest on arm64 drops to busybox under openstack bionic-rocky

Status in linux package in Ubuntu:
  Fix Released
Status in linux-raspi2 package in Ubuntu:
  Fix Released
Status in linux-snapdragon package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux-raspi2 source package in Xenial:
  Fix Committed
Status in linux-snapdragon source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in linux-raspi2 source package in Bionic:
  Fix Released
Status in linux-snapdragon source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-raspi2 source package in Cosmic:
  Fix Released
Status in linux-snapdragon source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  on openstack rocky-bionic (with patch, see 1771662), xenial guests will fail 
to launch as they drop to the busybox prompt after booting. The reason is that 
the EFI firmware image switched to ACPI mode by default in bionic. We knew that 
was happening, and backported some minimal ACPI support to keep xenial guests 
booting (bug 1744754). But, now we're seeing guests panic when trying to 
initialize PCI.

  [Test Case]
  Deploy rocky-bionic OpenStack and try to launch a xenial guest.

  [Fix]
  Backport ACPI/PCIe support for arm64 from upstream.

  [ Regression Risk ]
  TLDR: Definitely warrants some regression testing on armhf/arm64, but 
regression risk seems low for other architectures. Here's a patch-by-patch risk 
analysis:

  > 0001-UBUNTU-Config-CONFIG_PCI_ECAM-y.patch
  Enables code that will be added in the next patch.

  > 0002-PCI-Provide-common-functions-for-ECAM-mapping.patch
  Only adds new code w/ no callers yet

  > 0003-PCI-generic-thunder-Use-generic-ECAM-API.patch
  As noted in the commit message:
  "The patch does not introduce any functional changes other than a very minor 
one: with the new code, on 64-bit platforms, we do just a single ioremap for 
the whole config space."

  > 0004-PCI-of-Move-PCI-I-O-space-management-to-PCI-core-cod.patch
  As noted, no functional change.

  > 0005-PCI-Move-ecam.h-to-linux-include-pci-ecam.h.patch
  As noted, no functional change.

  > 0006-PCI-Add-parent-device-field-to-ECAM-struct-pci_confi.patch
  This makes changes to the ecam code, but that was added in this series, so no 
regression risk there. The pci-thunder-pem changes will be regression tested on 
the hardware that uses that driver (Cavium ThunderX).

  > 0007-PCI-Add-pci_unmap_iospace-to-unmap-I-O-resources.patch
  Only adds new code, w/ no callers yet

  > 0008-PCI-ACPI-Support-I-O-resources-when-parsing-host-bri.patch
  Adds and calls a new function that is a no-op on !ARM (PCI_IOBASE is only 
defined on ARM). Also adds a call to pci_unmap_iospace(), which was added in a 
previous patch and is also a no-op on !ARM.

  > 0009-UBUNTU-Config-CONFIG_ACPI_MCFG-y.patch
  Enables code that will be added in the next patch.

  > 0010-PCI-ACPI-Add-generic-MCFG-table-handling.patch
  Adds parsing of a new ACPI table. A possible regression risk to platforms an 
MCFG table that were working fine w/ 4.4 and there's a latent bug in this 
parsing code.

  > 0011-PCI-Refactor-pci_bus_assign_domain_nr-for-CONFIG_PCI.patch
  As noted, no functional change intended.

  > 0012-PCI-Factor-DT-specific-pci_bus_find_domain_nr-code-o.patch
  Again, no functional change.

  > 0013-ARM64-PCI-Add-acpi_pci_bus_find_domain_nr.patch
  Only impacts ARM due to CONFIG_PCI_DOMAINS_GENERIC guard

  > 0014-ARM64-PCI-ACPI-support-for-legacy-IRQs-parsing-and-c.patch
  arm64-specific PCI initialization code - mitigate risk by regression testing 
on supported platforms (X-Gene, ThunderX).

  > 0015-ARM64-PCI-Support-ACPI-based-PCI-host-controller.patch
  Adds new code for arm64-ACPI support. We didn't previously support these 
devices, so regression risk is negligible.

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

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

[Kernel-packages] [Bug 1802810] Re: SD card reader not working on Ubuntu 18.10

[Tad Ethan Keller]

Wait, after I updated my system, the reader stopped working. It only
seems to work with a clean install of Ubuntu without any reboots or
updates.

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

Title:
  SD card reader not working on Ubuntu 18.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I upgraded to Ubuntu 18.10 from Ubuntu 18.04, the SD card reader
  on my Macbook pro early 2015 13 inch stopped working. It won't show up
  when I do lspci. The SD card reader won't show up in gparted or gnome-
  disk-utility.

  My Kernel version is 4.18.0-10-generic

  Output of lspci

  00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation Iris Graphics 6100 (rev 
09)
  00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09)
  00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI 
Controller (rev 03)
  00:15.0 DMA controller: Intel Corporation Wildcat Point-LP Serial IO DMA 
Controller (rev 03)
  00:15.4 Serial bus controller [0c80]: Intel Corporation Wildcat Point-LP 
Serial IO GSPI Controller #1 (rev 03)
  00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI 
Controller #1 (rev 03)
  00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition 
Audio Controller (rev 03)
  00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port 
#1 (rev e3)
  00:1c.1 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port 
#2 (rev e3)
  00:1c.2 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port 
#3 (rev e3)
  00:1c.4 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port 
#5 (rev e3)
  00:1c.5 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port 
#6 (rev e3)
  00:1f.0 ISA bridge: Intel Corporation Wildcat Point-LP LPC Controller (rev 03)
  00:1f.3 SMBus: Intel Corporation Wildcat Point-LP SMBus Controller (rev 03)
  00:1f.6 Signal processing controller: Intel Corporation Wildcat Point-LP 
Thermal Management Controller (rev 03)
  02:00.0 Multimedia controller: Broadcom Inc. and subsidiaries 720p FaceTime 
HD Camera
  03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM43602 802.11ac 
Wireless LAN SoC (rev 01)
  04:00.0 SATA controller: Samsung Electronics Co Ltd Device a801 (rev 01)
  05:00.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon 
Ridge 4C 2013]
  06:00.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon 
Ridge 4C 2013]
  06:03.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon 
Ridge 4C 2013]
  06:04.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon 
Ridge 4C 2013]
  06:05.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon 
Ridge 4C 2013]
  06:06.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon 
Ridge 4C 2013]
  07:00.0 System peripheral: Intel Corporation DSL5520 Thunderbolt 2 NHI 
[Falcon Ridge 4C 2013]
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  monter 1583 F pulseaudio
   /dev/snd/controlC0:  monter 1583 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-11-12 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0273 Apple, Inc. 
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/17/2018
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 180.0.0.0.0
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvr180.0.0.0.0:bd09/17/2018:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  

[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

[Joseph Salisbury]

Also, the Ubuntu kernel trees are located at:

4.15:  git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/
4.18:  git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/cosmic/

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

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

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

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

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

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

[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

[Joseph Salisbury]

Regarding my comment #9, I read your comment #7 incorrectly.  I
literally read you don't know how a bisect would work.  I understand
clearly now.

We still should be able to bisect using the azure tree.  I'll review the
commits between 4.15 and 4.18 and see if anything sticks out.

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

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

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

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

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

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

[Kernel-packages] [Bug 1792100] Re: Boot hangs at "loading initial ramdisk..."

[Joseph Salisbury]

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.20 kernel[0].


[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20-rc3

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

Title:
  Boot hangs at "loading initial ramdisk..."

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

Bug description:
  I cannot load a kernel beyond 4.15.0-32-generic on my machine.
  Both 4.15.0-33-generic and 4.15.0-34-generic hang at "loading initial 
ramdisk...".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-34-generic 4.15.0-34.37
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kms2233 F pulseaudio
   /dev/snd/controlC1:  kms2233 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 12 10:52:00 2018
  HibernationDevice: RESUME=UUID=c3d34d19-9e9e-4967-ac45-f1d699cf5eef
  InstallationDate: Installed on 2018-01-05 (249 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Precision Tower 7810
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=90d43be7-a2f7-4500-8b88-9bd7a549d96d ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (132 days ago)
  dmi.bios.date: 06/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A27
  dmi.board.name: 0KJCC5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA27:bd06/25/2018:svnDellInc.:pnPrecisionTower7810:pvr:rvnDellInc.:rn0KJCC5:rvrA00:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 7810
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1784665] Re: mkfs.ext4 over /dev/bcache0 hangs

[Joseph Salisbury]

The 4.20 kernel is now available.  Can you give v4.20-rc3 a test:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20-rc3

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

Title:
  mkfs.ext4 over /dev/bcache0 hangs

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

Bug description:
  $ cat /proc/version_signature 
  Ubuntu 4.15.0-29.31-generic 4.15.18

  $ lsb_release -rd
  Description:  Ubuntu Cosmic Cuttlefish (development branch)
  Release:  18.10

  $ apt-cache policy linux-image-`uname -r`
  linux-image-4.15.0-29-generic:
Installed: 4.15.0-29.31
Candidate: 4.15.0-29.31
Version table:
   *** 4.15.0-29.31 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status

  
  3) mkfs.ext4 /dev/bcache0 returns successful creating an ext4 filesystem on 
top of a bcache device

  4) mkfs.ext4 doesn't return and kernel prints hung process info

  [   58.018099] cloud-init[920]: Running command ['mkfs.ext4', '-F', '-L', 
'root-fs', '-U', 'f01aec97-9457-11e8-b8d6-525400123401', '/dev/bcache0'] with 
allowed return codes [0] (capture=True)
  [  242.652018] INFO: task kworker/u4:0:5 blocked for more than 120 seconds.
  [  242.653767]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  242.655391] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  242.657397] INFO: task kworker/0:2:410 blocked for more than 120 seconds.
  [  242.659126]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  242.660980] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  242.663000] INFO: task bcache_allocato:2326 blocked for more than 120 
seconds.
  [  242.664807]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  242.666516] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  242.668503] INFO: task bcache_writebac:2345 blocked for more than 120 
seconds.
  [  242.670301]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  242.671936] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  242.673909] INFO: task mkfs.ext4:2803 blocked for more than 120 seconds.
  [  242.675414]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  242.677038] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  363.483998] INFO: task kworker/u4:0:5 blocked for more than 120 seconds.
  [  363.488441]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  363.489598] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  363.491043] INFO: task kworker/0:2:410 blocked for more than 120 seconds.
  [  363.492252]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  363.494085] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  363.495659] INFO: task bcache_allocato:2326 blocked for more than 120 
seconds.
  [  363.496957]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  363.498454] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  363.499866] INFO: task bcache_writebac:2345 blocked for more than 120 
seconds.
  [  363.501156]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  363.502597] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  363.504048] INFO: task mkfs.ext4:2803 blocked for more than 120 seconds.
  [  363.505505]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  363.506677] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.

  
  System has two virtio block devices.  bcache was created like so:

  make-bcache -C /dev/vdb
  make-bcache -B /dev/vda2

  resulting in /dev/bcache0

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.15.0-29-generic 4.15.0-29.31
  ProcVersionSignature: User Name 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 31 15:52 seq
   crw-rw 1 root audio 116, 33 Jul 31 15:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu7
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Tue Jul 31 15:53:56 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   

[Kernel-packages] [Bug 1804028] Re: Surface Go - Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not correctly recognized

[Waynexyz]

this is the output of dmesg after replacing the board.bin with the one
from killernetworking.com:

dmesg | grep ath
[4.513563] ath10k_pci :01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 
reset_mode 0
[4.806988] ath10k_pci :01:00.0: qca6174 hw3.2 target 0x0503 chip_id 
0x00340aff sub 168c:3370
[4.806994] ath10k_pci :01:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 
0 testmode 0
[4.807918] ath10k_pci :01:00.0: firmware ver 
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
[4.876632] ath10k_pci :01:00.0: board_file api 1 bmi_id N/A crc32 
70c38a29
[5.593731] ath10k_pci :01:00.0: Unknown eventid: 118809
[5.596743] ath10k_pci :01:00.0: Unknown eventid: 90118
[5.600688] ath10k_pci :01:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp 
max-sta 32 raw 0 hwcrypto 1
[5.691843] ath: EEPROM regdomain: 0x0
[5.691845] ath: EEPROM indicates default country code should be used
[5.691846] ath: doing EEPROM country->regdmn map search
[5.691849] ath: country maps to regdmn code: 0x3a
[5.691850] ath: Country alpha2 being used: US
[5.691851] ath: Regpair used: 0x3a
[6.576740] ath10k_pci :01:00.0 wlp1s0: renamed from wlan0
[7.403038] ath10k_pci :01:00.0: Unknown eventid: 118809
[7.406042] ath10k_pci :01:00.0: Unknown eventid: 90118
[  184.060093] ath10k_pci :01:00.0: Unknown eventid: 118809
[  184.063109] ath10k_pci :01:00.0: Unknown eventid: 90118

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

Title:
  Surface Go - Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not
  correctly recognized

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Output of dmesg on Surface Go fresh installed Ubuntu 18.10.

  "[ 4.242132] ath10k_pci :01:00.0: qca6174 hw3.2 target 0x0503 chip_id 
0x00340aff sub 168c:3370
  [ 4.242138] ath10k_pci :01:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 
0 testmode 0
  [ 4.243006] ath10k_pci :01:00.0: firmware ver 
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
  [ 4.308059] ath10k_pci :01:00.0: failed to fetch board data for 
bus=pci,vendor=168c,device=003e,subsystem-vendor=168c,subsystem-device=3370 
from ath10k/QCA6174/hw3.0/board-2.bin
  [ 4.309354] ath10k_pci :01:00.0: board_file api 1 bmi_id N/A crc32 
ed5f849a"

  There is a board.bin available directly from the vendor
  http://www.killernetworking.com/support/K1535_Debian/board.bin

  The only thing which is missing is getting this added to
  https://wireless.wiki.kernel.org/en/users/drivers/ath10k/boardfiles so
  the official board-2.bin. My problem is that I dont know how to read
  the board files and modify them because I do not know the encoding
  they use.

  Also there have been some updates in the upstream linux-firmware repo.
  https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
  firmware.git/commit/?id=a87eb5f7bac0f70ade57da57d9126d14eee12336 and
  https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0 but
  they also do not help to get the wifi card working/recognized.

  Any ideas how to get this solved?

  Also there is a guide how to port it to Linux
  https://developer.qualcomm.com/download/qca9377/wlan-bluetooth-linux-
  porting-guide.pdf

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

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

[Kernel-packages] [Bug 1782177] Re: Screen sometimes jumps to full brightness on resume from suspend

[Theo Linkspfeifer]

** Bug watch added: freedesktop.org Bugzilla #108703
   https://bugs.freedesktop.org/show_bug.cgi?id=108703

** Also affects: linux via
   https://bugs.freedesktop.org/show_bug.cgi?id=108703
   Importance: Unknown
   Status: Unknown

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

Title:
  Screen sometimes jumps to full brightness on resume from suspend

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

Bug description:
  At night, I usually turn my brightness down as far as it will go using
  the brightness keys. This makes it dim, but visible and not off. When
  I walk away for a while, the screen goes to sleep, and when I come
  back and move the mouse, the screen jumps to full brightness, which is
  very unpleasant at night. Investigating, it seems that the brightness
  in intel_backlight is getting reset to 4437, but the one in
  acpi_video0 reads 0.

  $ for file in brightness max_brightness actual_brightness;
  > do
  >   for directory in /sys/class/backlight/intel_backlight/ 
/sys/class/backlight/acpi_video0/
  > do
  > echo $directory$file : $(cat $directory$file)
  > done
  > done
  /sys/class/backlight/intel_backlight/brightness : 4437
  /sys/class/backlight/acpi_video0/brightness : 0
  /sys/class/backlight/intel_backlight/max_brightness : 4437
  /sys/class/backlight/acpi_video0/max_brightness : 15
  /sys/class/backlight/intel_backlight/actual_brightness : 4437
  /sys/class/backlight/acpi_video0/actual_brightness : 0

  After I press the button to increase the brightness one notch, they
  are back in sync, and then I can turn it back down as well.

  $ for file in brightness max_brightness actual_brightness;
  >  do
  >for directory in /sys/class/backlight/intel_backlight/ 
/sys/class/backlight/acpi_video0/
  >  do
  >  echo $directory$file : $(cat $directory$file)
  >  done
  >  done
  /sys/class/backlight/intel_backlight/brightness : 53
  /sys/class/backlight/acpi_video0/brightness : 1
  /sys/class/backlight/intel_backlight/max_brightness : 4437
  /sys/class/backlight/acpi_video0/max_brightness : 15
  /sys/class/backlight/intel_backlight/actual_brightness : 53
  /sys/class/backlight/acpi_video0/actual_brightness : 1

  This is on a fresh install of xubuntu 18.04. Seems like a regression
  from 16.04, which I ran on the same laptop without this issue.

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

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

[Kernel-packages] [Bug 1802283] Re: system freezes

[jnns]

Thank you for taking your time with this issue.

> Does the Firefox crashing only happens when the system is docked?

No, a few minutes ago a Firefox tab crashed while the laptop was only being 
charged.
Here's a syslog snippet: http://dpaste.com/08ZJZQF.txt

> 1, could you test your laptop without the dock station for one if the
issue can be reproduced?

I don't run the laptop with a real dock. I just connect it to the power
outlet with the AC adapter that came with the laptop. Additionally I am
often connected via Thunderbolt to an external monitor. Do you want me
to try to reproduce the crash without a monitor being connected? I think
I have yet to experience a crash without having an external monitor
connected.

2. I will try and update the Thunderbolt firmware. Thanks for
mentioning!

3. Sure!

Thunderbolt BIOS Assist Mode [Enabled]
Wake by Thunderbolt(TM) 3[Enabled]
Security Level   [User Authori]

Support in Pre Boot Environment: 
Thunderbolt(TM) device   [Disabled]


4. I don't own a Lenovo dock station. The laptop is just connected to a power 
outlet and sometimes to a monitor.

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

Title:
  system freezes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My system freezes once every second day or so.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jnns   2519 F pulseaudio
   /dev/snd/controlC0:  jnns   2519 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Nov  8 12:07:32 2018
  HibernationDevice: RESUME=UUID=18edd09d-0a58-4464-accb-11ff57fc4327
  InstallationDate: Installed on 2018-08-05 (95 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20KGS5DU00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/fish
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-10-10 (29 days ago)
  dmi.bios.date: 09/17/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET56W (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KGS5DU00
  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:bvrN23ET56W(1.31):bd09/17/2018:svnLENOVO:pn20KGS5DU00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGS5DU00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KGS5DU00
  dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1804028] Re: Surface Go - Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not correctly recognized

[Waynexyz]

https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/plain/ath10k/QCA6174/hw3.0/ the files in that folder need
to be modified I think and added the needed information in the
board-2.bin . So if anyone knows which informations are needed, please
let me know and I will help debugging to get the stuff upstream.

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

Title:
  Surface Go - Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not
  correctly recognized

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Output of dmesg on Surface Go fresh installed Ubuntu 18.10.

  "[ 4.242132] ath10k_pci :01:00.0: qca6174 hw3.2 target 0x0503 chip_id 
0x00340aff sub 168c:3370
  [ 4.242138] ath10k_pci :01:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 
0 testmode 0
  [ 4.243006] ath10k_pci :01:00.0: firmware ver 
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
  [ 4.308059] ath10k_pci :01:00.0: failed to fetch board data for 
bus=pci,vendor=168c,device=003e,subsystem-vendor=168c,subsystem-device=3370 
from ath10k/QCA6174/hw3.0/board-2.bin
  [ 4.309354] ath10k_pci :01:00.0: board_file api 1 bmi_id N/A crc32 
ed5f849a"

  There is a board.bin available directly from the vendor
  http://www.killernetworking.com/support/K1535_Debian/board.bin

  The only thing which is missing is getting this added to
  https://wireless.wiki.kernel.org/en/users/drivers/ath10k/boardfiles so
  the official board-2.bin. My problem is that I dont know how to read
  the board files and modify them because I do not know the encoding
  they use.

  Also there have been some updates in the upstream linux-firmware repo.
  https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
  firmware.git/commit/?id=a87eb5f7bac0f70ade57da57d9126d14eee12336 and
  https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0 but
  they also do not help to get the wifi card working/recognized.

  Any ideas how to get this solved?

  Also there is a guide how to port it to Linux
  https://developer.qualcomm.com/download/qca9377/wlan-bluetooth-linux-
  porting-guide.pdf

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

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

[Kernel-packages] [Bug 1804028] Re: Surface Go - Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not correctly recognized

[Waynexyz]

After copying the above
http://www.killernetworking.com/support/K1535_Debian/board.bin to the
following folder "/lib/firmware/ath10k/QCA6174/hw3.0", the wifi works
flawless. Just the "board.bin" and "board-2.bin" in
"/lib/firmware/ath10k/QCA6174/hw3.0" have to be deleted before.

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

Title:
  Surface Go - Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not
  correctly recognized

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Output of dmesg on Surface Go fresh installed Ubuntu 18.10.

  "[ 4.242132] ath10k_pci :01:00.0: qca6174 hw3.2 target 0x0503 chip_id 
0x00340aff sub 168c:3370
  [ 4.242138] ath10k_pci :01:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 
0 testmode 0
  [ 4.243006] ath10k_pci :01:00.0: firmware ver 
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
  [ 4.308059] ath10k_pci :01:00.0: failed to fetch board data for 
bus=pci,vendor=168c,device=003e,subsystem-vendor=168c,subsystem-device=3370 
from ath10k/QCA6174/hw3.0/board-2.bin
  [ 4.309354] ath10k_pci :01:00.0: board_file api 1 bmi_id N/A crc32 
ed5f849a"

  There is a board.bin available directly from the vendor
  http://www.killernetworking.com/support/K1535_Debian/board.bin

  The only thing which is missing is getting this added to
  https://wireless.wiki.kernel.org/en/users/drivers/ath10k/boardfiles so
  the official board-2.bin. My problem is that I dont know how to read
  the board files and modify them because I do not know the encoding
  they use.

  Also there have been some updates in the upstream linux-firmware repo.
  https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
  firmware.git/commit/?id=a87eb5f7bac0f70ade57da57d9126d14eee12336 and
  https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0 but
  they also do not help to get the wifi card working/recognized.

  Any ideas how to get this solved?

  Also there is a guide how to port it to Linux
  https://developer.qualcomm.com/download/qca9377/wlan-bluetooth-linux-
  porting-guide.pdf

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

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

[Kernel-packages] [Bug 1804054] Re: [Hyper-V] kdump is broken on trusty with linux-azure 4.15.0-1032 kernel

[Joseph Salisbury]

** Package changed: linux (Ubuntu) => linux-azure (Ubuntu)

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

** Tags added: kernel-da-key kernel-hyper-v

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

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

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

Title:
  [Hyper-V] kdump is broken on trusty with linux-azure 4.15.0-1032
  kernel

Status in linux-azure package in Ubuntu:
  Triaged

Bug description:
  While testing linux-azure 4.15.0-1032 kernel from proposed we found
  that kdump is no longer working as expected, on trusty only.

  Here are some info and versions.
  We'll have to verify a few more scenarios with other images and try to 
isolate this, but as least the kdump on trusty issue is there.
  Also remains to be checked in which release this regression was introduced.
  The below can be repro'd on Azure.

  On Xenial it works with ubuntu provided latest kexec-tools 2.0.16.

  It looks like the kexec might require some patches from upstream as
  far as I can tell from the data we have so far.

  Distro / kernel: 4.15.0-1032-azure #33~14.04.2-Ubuntu
  Package: kdump-tools1.5.5-2ubuntu1.6

  Errors from logs:
  kdump-config: failed to load kdump kernel
  kernel: [  230.772409] init: kdump-tools main process (1726) terminated with 
status 1

  # cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinuz-4.15.0-1032-azure root=x ro console=tty1 
console=ttyS0 earlyprintk=ttyS0 rootdelay=300 crashkernel=384M

  ---

  This issue looks resolved with the kexec package build from the
  official kernel.org kexec repo, on top of 14.04.

  kexec-tools 2.0.18
  https://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git

  # cat /sys/kernel/kexec_*
  1
  402653184
  And kdump core file gets created when running with 1032 kernel.

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

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

[Kernel-packages] [Bug 1804054] Re: [Hyper-V] kdump is broken on trusty with linux-azure 1032 kernel

[Launchpad Bug Tracker]

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

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

Title:
  [Hyper-V] kdump is broken on trusty with linux-azure 4.15.0-1032
  kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While testing linux-azure 4.15.0-1032 kernel from proposed we found
  that kdump is no longer working as expected, on trusty only.

  Here are some info and versions.
  We'll have to verify a few more scenarios with other images and try to 
isolate this, but as least the kdump on trusty issue is there.
  Also remains to be checked in which release this regression was introduced.
  The below can be repro'd on Azure.

  On Xenial it works with ubuntu provided latest kexec-tools 2.0.16.

  It looks like the kexec might require some patches from upstream as
  far as I can tell from the data we have so far.

  Distro / kernel: 4.15.0-1032-azure #33~14.04.2-Ubuntu
  Package: kdump-tools1.5.5-2ubuntu1.6

  Errors from logs:
  kdump-config: failed to load kdump kernel
  kernel: [  230.772409] init: kdump-tools main process (1726) terminated with 
status 1

  # cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinuz-4.15.0-1032-azure root=x ro console=tty1 
console=ttyS0 earlyprintk=ttyS0 rootdelay=300 crashkernel=384M

  ---

  This issue looks resolved with the kexec package build from the
  official kernel.org kexec repo, on top of 14.04.

  kexec-tools 2.0.18
  https://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git

  # cat /sys/kernel/kexec_*
  1
  402653184
  And kdump core file gets created when running with 1032 kernel.

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

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

[Kernel-packages] [Bug 1804054] Re: [Hyper-V] kdump is broken on trusty with linux-azure 4.15.0-1032 kernel

[Joshua R. Poulson]

** Summary changed:

- [Hyper-V] kdump is broken on trusty with linux-azure 1032 kernel
+ [Hyper-V] kdump is broken on trusty with linux-azure 4.15.0-1032 kernel

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

Title:
  [Hyper-V] kdump is broken on trusty with linux-azure 4.15.0-1032
  kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While testing linux-azure 4.15.0-1032 kernel from proposed we found
  that kdump is no longer working as expected, on trusty only.

  Here are some info and versions.
  We'll have to verify a few more scenarios with other images and try to 
isolate this, but as least the kdump on trusty issue is there.
  Also remains to be checked in which release this regression was introduced.
  The below can be repro'd on Azure.

  On Xenial it works with ubuntu provided latest kexec-tools 2.0.16.

  It looks like the kexec might require some patches from upstream as
  far as I can tell from the data we have so far.

  Distro / kernel: 4.15.0-1032-azure #33~14.04.2-Ubuntu
  Package: kdump-tools1.5.5-2ubuntu1.6

  Errors from logs:
  kdump-config: failed to load kdump kernel
  kernel: [  230.772409] init: kdump-tools main process (1726) terminated with 
status 1

  # cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinuz-4.15.0-1032-azure root=x ro console=tty1 
console=ttyS0 earlyprintk=ttyS0 rootdelay=300 crashkernel=384M

  ---

  This issue looks resolved with the kexec package build from the
  official kernel.org kexec repo, on top of 14.04.

  kexec-tools 2.0.18
  https://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git

  # cat /sys/kernel/kexec_*
  1
  402653184
  And kdump core file gets created when running with 1032 kernel.

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

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

[Kernel-packages] [Bug 1804054] [NEW] [Hyper-V] kdump is broken on trusty with linux-azure 4.15.0-1032 kernel

[Chris Valean]

Public bug reported:

While testing linux-azure 4.15.0-1032 kernel from proposed we found that
kdump is no longer working as expected, on trusty only.

Here are some info and versions.
We'll have to verify a few more scenarios with other images and try to isolate 
this, but as least the kdump on trusty issue is there.
Also remains to be checked in which release this regression was introduced.
The below can be repro'd on Azure.

On Xenial it works with ubuntu provided latest kexec-tools 2.0.16.

It looks like the kexec might require some patches from upstream as far
as I can tell from the data we have so far.

Distro / kernel: 4.15.0-1032-azure #33~14.04.2-Ubuntu
Package: kdump-tools1.5.5-2ubuntu1.6

Errors from logs:
kdump-config: failed to load kdump kernel
kernel: [  230.772409] init: kdump-tools main process (1726) terminated with 
status 1

# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.15.0-1032-azure root=x ro console=tty1 console=ttyS0 
earlyprintk=ttyS0 rootdelay=300 crashkernel=384M

---

This issue looks resolved with the kexec package build from the official
kernel.org kexec repo, on top of 14.04.

kexec-tools 2.0.18
https://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git

# cat /sys/kernel/kexec_*
1
402653184
And kdump core file gets created when running with 1032 kernel.

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


** Tags: hyper-v

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

Title:
  [Hyper-V] kdump is broken on trusty with linux-azure 4.15.0-1032
  kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While testing linux-azure 4.15.0-1032 kernel from proposed we found
  that kdump is no longer working as expected, on trusty only.

  Here are some info and versions.
  We'll have to verify a few more scenarios with other images and try to 
isolate this, but as least the kdump on trusty issue is there.
  Also remains to be checked in which release this regression was introduced.
  The below can be repro'd on Azure.

  On Xenial it works with ubuntu provided latest kexec-tools 2.0.16.

  It looks like the kexec might require some patches from upstream as
  far as I can tell from the data we have so far.

  Distro / kernel: 4.15.0-1032-azure #33~14.04.2-Ubuntu
  Package: kdump-tools1.5.5-2ubuntu1.6

  Errors from logs:
  kdump-config: failed to load kdump kernel
  kernel: [  230.772409] init: kdump-tools main process (1726) terminated with 
status 1

  # cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinuz-4.15.0-1032-azure root=x ro console=tty1 
console=ttyS0 earlyprintk=ttyS0 rootdelay=300 crashkernel=384M

  ---

  This issue looks resolved with the kexec package build from the
  official kernel.org kexec repo, on top of 14.04.

  kexec-tools 2.0.18
  https://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git

  # cat /sys/kernel/kexec_*
  1
  402653184
  And kdump core file gets created when running with 1032 kernel.

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

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

[Kernel-packages] [Bug 1797092] Re: xenial guest on arm64 drops to busybox under openstack bionic-rocky

[dann frazier]

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

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

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

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

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

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

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

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

Title:
  xenial guest on arm64 drops to busybox under openstack bionic-rocky

Status in linux package in Ubuntu:
  Fix Released
Status in linux-raspi2 package in Ubuntu:
  Fix Released
Status in linux-snapdragon package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux-raspi2 source package in Xenial:
  Fix Committed
Status in linux-snapdragon source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in linux-raspi2 source package in Bionic:
  Fix Released
Status in linux-snapdragon source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-raspi2 source package in Cosmic:
  Fix Released
Status in linux-snapdragon source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  on openstack rocky-bionic (with patch, see 1771662), xenial guests will fail 
to launch as they drop to the busybox prompt after booting. The reason is that 
the EFI firmware image switched to ACPI mode by default in bionic. We knew that 
was happening, and backported some minimal ACPI support to keep xenial guests 
booting (bug 1744754). But, now we're seeing guests panic when trying to 
initialize PCI.

  [Test Case]
  Deploy rocky-bionic OpenStack and try to launch a xenial guest.

  [Fix]
  Backport ACPI/PCIe support for arm64 from upstream.

  [ Regression Risk ]
  TLDR: Definitely warrants some regression testing on armhf/arm64, but 
regression risk seems low for other architectures. Here's a patch-by-patch risk 
analysis:

  > 0001-UBUNTU-Config-CONFIG_PCI_ECAM-y.patch
  Enables code that will be added in the next patch.

  > 0002-PCI-Provide-common-functions-for-ECAM-mapping.patch
  Only adds new code w/ no callers yet

  > 0003-PCI-generic-thunder-Use-generic-ECAM-API.patch
  As noted in the commit message:
  "The patch does not introduce any functional changes other than a very minor 
one: with the new code, on 64-bit platforms, we do just a single ioremap for 
the whole config space."

  > 0004-PCI-of-Move-PCI-I-O-space-management-to-PCI-core-cod.patch
  As noted, no functional change.

  > 0005-PCI-Move-ecam.h-to-linux-include-pci-ecam.h.patch
  As noted, no functional change.

  > 0006-PCI-Add-parent-device-field-to-ECAM-struct-pci_confi.patch
  This makes changes to the ecam code, but that was added in this series, so no 
regression risk there. The pci-thunder-pem changes will be regression tested on 
the hardware that uses that driver (Cavium ThunderX).

  > 0007-PCI-Add-pci_unmap_iospace-to-unmap-I-O-resources.patch
  Only adds new code, w/ no callers yet

  > 0008-PCI-ACPI-Support-I-O-resources-when-parsing-host-bri.patch
  Adds and calls a new function that is a no-op on !ARM (PCI_IOBASE is only 
defined on ARM). Also adds a call to pci_unmap_iospace(), which was added in a 
previous patch and is also a no-op on !ARM.

  > 0009-UBUNTU-Config-CONFIG_ACPI_MCFG-y.patch
  Enables code that will be added in the next patch.

  > 0010-PCI-ACPI-Add-generic-MCFG-table-handling.patch
  Adds parsing of a new ACPI table. A possible regression risk to platforms an 
MCFG table that were working fine w/ 4.4 and there's a latent bug in this 
parsing code.

  > 0011-PCI-Refactor-pci_bus_assign_domain_nr-for-CONFIG_PCI.patch
  As noted, no functional change intended.

  > 0012-PCI-Factor-DT-specific-pci_bus_find_domain_nr-code-o.patch
  Again, no functional change.

  > 0013-ARM64-PCI-Add-acpi_pci_bus_find_domain_nr.patch
  Only impacts ARM due to CONFIG_PCI_DOMAINS_GENERIC guard

  > 0014-ARM64-PCI-ACPI-support-for-legacy-IRQs-parsing-and-c.patch
  arm64-specific PCI initialization code - mitigate risk by regression testing 
on supported platforms (X-Gene, ThunderX).

  > 0015-ARM64-PCI-Support-ACPI-based-PCI-host-controller.patch
  Adds new code for arm64-ACPI support. We didn't previously support these 
devices, so regression risk is negligible.

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

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

[Kernel-packages] [Bug 1803268] Re: Ubuntu 18.10 after Blank Screen System Will NOT Unblank

[Lawrence Houston]

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

** This bug has been marked a duplicate of bug 1801609
   Fails to deactivate dpms off mode after user initiated wake-up events(not 
system-suspended, just locked and dpms active)

** Summary changed:

- Ubuntu 18.10 after Blank Screen System Will NOT Unblank
+ Xubuntu 18.10 after Blank Screen, System Will NOT Unblank

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

Title:
  Xubuntu 18.10 after Blank Screen, System Will NOT Unblank

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Toshiba Satellite C650 (embedded Intel HD Graphics 3000) running
  Xubuntu 18.10. Once the Toshiba's Screen has Blanked, it will not
  unblank with normal Keystrokes or Mouse Events.

  My "Work around": Plugging an External Monitor into the Satellite
  C650's VGA Port, which will then unblank the Toshiba's Screen!!!

  version.log   Ubuntu 4.18.0-10.11-generic 4.18.12

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  houston2335 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Nov 13 22:42:09 2018
  InstallationDate: Installed on 2018-11-01 (12 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: TOSHIBA Satellite C650
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=9d27207e-4cea-4a3f-9e73-35d175aa6a19 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/21/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 1.30
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr1.30:bd11/21/2011:svnTOSHIBA:pnSatelliteC650:pvrPSC2EC-07J001:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite C650
  dmi.product.sku: PSC2EC-07J001
  dmi.product.version: PSC2EC-07J001
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power

[Gregor Burger]

** Attachment added: "prime-select query = intel"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1778011/+attachment/5214282/+files/gpu-manager.log

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

Title:
  SRU: PRIME Power Saving mode draws too much power

Status in HWE Next:
  New
Status in gdm3 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in sddm package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in gdm3 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Released
Status in nvidia-prime source package in Bionic:
  Fix Released
Status in nvidia-settings source package in Bionic:
  Fix Released
Status in sddm source package in Bionic:
  Confirmed
Status in ubuntu-drivers-common source package in Bionic:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Relying on the nouveau driver and on the vga switcheroo (to get around a 
change in systemd LP: #1777099) caused increased power consumption, and slowed 
down the switching process.

  Furthermore, if the main X/Xwayland session was started by Gdm when
  the nvidia driver was loaded, the session will keep the nvidia module
  loaded, and prevent the system from switching off the dGPU. Also, the
  nouveau driver will be loaded, if nvidia is not, and this can cause
  problems to unsupported NVIDIA GPUs.

  The solution involves the following changes:

  1) Solving the problem in systemd (LP: #1777099)

  2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia
  modules, and to allow the PCI device to sleep.

  3) Making a slight change to the current patch in Gdm, used to call
  the PRIME scripts before and after a Gdm session (so that gpu-manager
  gets actually called on log out)

  4) Adding code in gpu-manager to kill the main X/Xwayland session on
  log out, if the session is preventing us from unloading the nvidia
  driver. A new X/Xwayland session will be created after unload the
  module.

  5) Removing the systemd service that loads nouveau from the nvidia
  packages.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 *

  2) Make sure the nvidia packages are installed, and enable performance mode 
(if it is already enabled, call "sudo prime-select intel" first):
  sudo prime-select nvidia

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Select power saving mode:
  sudo prime-select intel

  5) Log out and log back in

  6) Check if the nvidia driver is still loaded:
  lsmod | grep nvidia

  [Regression Potential]
  Low, as hybrid graphics support does not work correctly, and the changes only 
affect this use case.

  _
  * Steps to test the updates:

  1) Enable the bionic-proposed repositories

  2) Create /etc/apt/preferences.d/proposed-updates with the following
  content:

  Package: *
  Pin: release a=bionic-proposed
  Pin-Priority: 400

  3) Update the list of packages:

  sudo apt-get update

  4) Install the packages from -proposed using the following command:

  sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic-
  proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-
  proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic-
  proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390
  /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia-
  ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed

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

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

[Kernel-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power

[Gregor Burger]

Hi,

Thinkpad P1 Quadro P1000. prime-select also not working. 
after prime-select intel and a rebeoot nouveau is driving the GPU but not intel.

Thanks

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

Title:
  SRU: PRIME Power Saving mode draws too much power

Status in HWE Next:
  New
Status in gdm3 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in sddm package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in gdm3 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Released
Status in nvidia-prime source package in Bionic:
  Fix Released
Status in nvidia-settings source package in Bionic:
  Fix Released
Status in sddm source package in Bionic:
  Confirmed
Status in ubuntu-drivers-common source package in Bionic:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Relying on the nouveau driver and on the vga switcheroo (to get around a 
change in systemd LP: #1777099) caused increased power consumption, and slowed 
down the switching process.

  Furthermore, if the main X/Xwayland session was started by Gdm when
  the nvidia driver was loaded, the session will keep the nvidia module
  loaded, and prevent the system from switching off the dGPU. Also, the
  nouveau driver will be loaded, if nvidia is not, and this can cause
  problems to unsupported NVIDIA GPUs.

  The solution involves the following changes:

  1) Solving the problem in systemd (LP: #1777099)

  2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia
  modules, and to allow the PCI device to sleep.

  3) Making a slight change to the current patch in Gdm, used to call
  the PRIME scripts before and after a Gdm session (so that gpu-manager
  gets actually called on log out)

  4) Adding code in gpu-manager to kill the main X/Xwayland session on
  log out, if the session is preventing us from unloading the nvidia
  driver. A new X/Xwayland session will be created after unload the
  module.

  5) Removing the systemd service that loads nouveau from the nvidia
  packages.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 *

  2) Make sure the nvidia packages are installed, and enable performance mode 
(if it is already enabled, call "sudo prime-select intel" first):
  sudo prime-select nvidia

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Select power saving mode:
  sudo prime-select intel

  5) Log out and log back in

  6) Check if the nvidia driver is still loaded:
  lsmod | grep nvidia

  [Regression Potential]
  Low, as hybrid graphics support does not work correctly, and the changes only 
affect this use case.

  _
  * Steps to test the updates:

  1) Enable the bionic-proposed repositories

  2) Create /etc/apt/preferences.d/proposed-updates with the following
  content:

  Package: *
  Pin: release a=bionic-proposed
  Pin-Priority: 400

  3) Update the list of packages:

  sudo apt-get update

  4) Install the packages from -proposed using the following command:

  sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic-
  proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-
  proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic-
  proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390
  /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia-
  ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed

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

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

Re: [Kernel-packages] [Bug 1793458] Re: Overlayfs in user namespace leaks directory content of inaccessible directories

[Tyler Hicks]

On 2018-11-19 18:14:43, Philipp Wendler wrote:
> I hope that this is all just a misunderstanding and the message does not
> apply to security problems. In this case please consider changing the
> message or improving the process such that this confusion will be
> avoided for future reports.

Hi Philipp - I'm sorry about the confusion that comment caused. The
comment was created by an automated script that the kernel team uses to
help with the stable release update process. Security fixes do receive
an exception with this policy.

The common case is that we track security fixes with CVE IDs instead of
Launchpad bug reports. In this case, we do have a bug report for this
security issue so it gets lumped in with all of the other non-security
fixes that are subject to this policy.

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

Title:
  Overlayfs in user namespace leaks directory content of inaccessible
  directories

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

Bug description:
  Summary: With a combination of overlayfs and user namespaces, regular
  users can see the content of directories that would otherwise be
  inaccessible to them because of directory permissions (e.g., all users
  can see content of "/root").

  Details: For the exploit it is necessary to create user and mount
  namespaces and mount an overlayfs inside it. Ubuntu allows this for
  regular users. The lower dir of the overlay would be "/", and the
  upper dir an attacker-controlled temporary directory. If the attacker
  wants to see the content of "/root", they would create a directory
  "root" in the upper dir of the overlay. Overlays seems to get confused
  about the permissions, and instead of applying the restrictive
  permissions of "root" from the lower dir, it applies more relaxed
  restrictions of "root" from the upper dir, granting the attacker the
  possibility to list the directory contents of "/root".

  To reproduce, simply run the attached script as regular user. It will show 
the content of "/root", on my system the output is this:
  ```
  /bin/ls: cannot access '/root/.cache': Permission denied
  /bin/ls: cannot access '/root/.bashrc': Permission denied
  /bin/ls: cannot access '/root/snap': Permission denied
  /bin/ls: cannot access '/root/.gnupg': Permission denied
  /bin/ls: cannot access '/root/.aptitude': Permission denied
  /bin/ls: cannot access '/root/.bash_history': Permission denied
  /bin/ls: cannot access '/root/.profile': Permission denied
  /bin/ls: cannot access '/root/.hplip': Permission denied
  total 8
  drwxr-xr-x 1 nobody nogroup 4096 Sep 20 09:02 .
  drwxr-xr-x 1 nobody nogroup 4096 Sep 20 09:02 ..
  d? ? ?  ?  ?? .aptitude
  -? ? ?  ?  ?? .bash_history
  -? ? ?  ?  ?? .bashrc
  d? ? ?  ?  ?? .cache
  d? ? ?  ?  ?? .gnupg
  d? ? ?  ?  ?? .hplip
  -? ? ?  ?  ?? .profile
  d? ? ?  ?  ?? snap
  ```

  The script also has some comments that explain the necessary steps in
  more details.

  I tested on Ubuntu 18.04 with Linux 4.15.0-34-generic, but the bug
  probably affects all Ubuntu versions of the last years. Other
  distributions and the vanilla kernel should not be affected because
  AFAIK only Ubuntu allows mounting of overlayfs inside user namespaces.
  But of course it would be good to apply a potential fix upstream.

  So far I did not succeed in doing more than leaking the directory
  content, but of course that is no guarantee that it is not possible to
  do worse things.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-34-generic 4.15.0-34.37
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  wendler3414 F pulseaudio
   /dev/snd/controlC0:  wendler3414 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Sep 20 08:56:01 2018
  HibernationDevice: RESUME=UUID=f9d1a1f9-50d2-4b7c-b7e4-66dc78d38062
  InstallationDate: Installed on 2016-12-12 (646 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20FXS1B700
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=/dev/mapper/ubuntu--vg-swap_1 swapaccount=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-34-generic 

[Kernel-packages] [Bug 1793458] Re: Overlayfs in user namespace leaks directory content of inaccessible directories

[Philipp Wendler]

I find the demand to test the fix within 5 days, combined with the
threat of dropping the patch otherwise, unreasonable.

In my original report of this security problem I have already provided a
script that allows to reproduce the problem and check if it still
exists.

Requiring an answer within 5 days is too short, after all people can be
on holiday or just busy for other reasons.

And even if I as the original submitter wouldn't respond at all, this is
a real security problem in Ubuntu that was already confirmed. Are you
really going to drop the patch and let CVE-2018-6559 stay unfixed
forever?

Maybe I will find the time to test it on Bionic, but I will certainly
not install a different version of Ubuntu than the one I am currently
running.

I hope that this is all just a misunderstanding and the message does not
apply to security problems. In this case please consider changing the
message or improving the process such that this confusion will be
avoided for future reports.

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

Title:
  Overlayfs in user namespace leaks directory content of inaccessible
  directories

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

Bug description:
  Summary: With a combination of overlayfs and user namespaces, regular
  users can see the content of directories that would otherwise be
  inaccessible to them because of directory permissions (e.g., all users
  can see content of "/root").

  Details: For the exploit it is necessary to create user and mount
  namespaces and mount an overlayfs inside it. Ubuntu allows this for
  regular users. The lower dir of the overlay would be "/", and the
  upper dir an attacker-controlled temporary directory. If the attacker
  wants to see the content of "/root", they would create a directory
  "root" in the upper dir of the overlay. Overlays seems to get confused
  about the permissions, and instead of applying the restrictive
  permissions of "root" from the lower dir, it applies more relaxed
  restrictions of "root" from the upper dir, granting the attacker the
  possibility to list the directory contents of "/root".

  To reproduce, simply run the attached script as regular user. It will show 
the content of "/root", on my system the output is this:
  ```
  /bin/ls: cannot access '/root/.cache': Permission denied
  /bin/ls: cannot access '/root/.bashrc': Permission denied
  /bin/ls: cannot access '/root/snap': Permission denied
  /bin/ls: cannot access '/root/.gnupg': Permission denied
  /bin/ls: cannot access '/root/.aptitude': Permission denied
  /bin/ls: cannot access '/root/.bash_history': Permission denied
  /bin/ls: cannot access '/root/.profile': Permission denied
  /bin/ls: cannot access '/root/.hplip': Permission denied
  total 8
  drwxr-xr-x 1 nobody nogroup 4096 Sep 20 09:02 .
  drwxr-xr-x 1 nobody nogroup 4096 Sep 20 09:02 ..
  d? ? ?  ?  ?? .aptitude
  -? ? ?  ?  ?? .bash_history
  -? ? ?  ?  ?? .bashrc
  d? ? ?  ?  ?? .cache
  d? ? ?  ?  ?? .gnupg
  d? ? ?  ?  ?? .hplip
  -? ? ?  ?  ?? .profile
  d? ? ?  ?  ?? snap
  ```

  The script also has some comments that explain the necessary steps in
  more details.

  I tested on Ubuntu 18.04 with Linux 4.15.0-34-generic, but the bug
  probably affects all Ubuntu versions of the last years. Other
  distributions and the vanilla kernel should not be affected because
  AFAIK only Ubuntu allows mounting of overlayfs inside user namespaces.
  But of course it would be good to apply a potential fix upstream.

  So far I did not succeed in doing more than leaking the directory
  content, but of course that is no guarantee that it is not possible to
  do worse things.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-34-generic 4.15.0-34.37
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  wendler3414 F pulseaudio
   /dev/snd/controlC0:  wendler3414 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Sep 20 08:56:01 2018
  HibernationDevice: RESUME=UUID=f9d1a1f9-50d2-4b7c-b7e4-66dc78d38062
  InstallationDate: Installed on 2016-12-12 (646 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20FXS1B700
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: 

[Kernel-packages] [Bug 1804040] [NEW] nvidia-dkms-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed to build

[Saksham Arneja]

Public bug reported:

failed to update my system

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: nvidia-dkms-390 390.77-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
DKMSKernelVersion: 4.15.0-39-generic
Date: Mon Nov 19 23:00:47 2018
InstallationDate: Installed on 2018-09-16 (64 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageVersion: 390.77-0ubuntu0.18.04.1
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6
SourcePackage: nvidia-graphics-drivers-390
Title: nvidia-dkms-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed to 
build
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  nvidia-dkms-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed
  to build

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

Bug description:
  failed to update my system

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-dkms-390 390.77-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-39-generic
  Date: Mon Nov 19 23:00:47 2018
  InstallationDate: Installed on 2018-09-16 (64 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageVersion: 390.77-0ubuntu0.18.04.1
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: nvidia-graphics-drivers-390
  Title: nvidia-dkms-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1803592] Re: linux: 4.15.0-42.45 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/snap-release-to-candidate
   Status: Confirmed => Fix Released

** Description changed:

  This bug is for tracking the 4.15.0-42.45 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  backports: null
  boot-testing-requested: true
  bugs-spammed: true
  derivatives: bug 1803678 (linux-oem)
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Testing FAILED
certification-testing: Testing in progress
regression-testing: Testing in progress
security-signoff: Waiting for signoff
-   snap-release-to-candidate: Snap not in 18/candidate channel
verification-testing: Testing in progress

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

Title:
  linux: 4.15.0-42.45 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
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-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:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the 4.15.0-42.45 upload package. This bug
  will contain status and testing results related to that upload.

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

  -- swm properties --
  backports: null
  boot-testing-requested: true
  bugs-spammed: true
  derivatives: bug 1803678 (linux-oem)
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Testing FAILED
certification-testing: Testing in progress
regression-testing: Testing in progress
security-signoff: Waiting for signoff
verification-testing: Testing in progress

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

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

[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

[Joseph Salisbury]

I can build you kernels for the bisect.  You test the kernel and post
back if it has the bug or not.  Then I will build the next kernel based
on your results.  Repeat.

To start a bisect, we first need to identify the last good kernel
version and the first bad one.  Can you test the following kernels:

4.15.0-29: 
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/15137612
4.17.0-4: 
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap/+build/15068818


** Changed in: linux (Ubuntu Cosmic)
 Assignee: Marcelo Cerri (mhcerri) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu)
 Assignee: Marcelo Cerri (mhcerri) => Joseph Salisbury (jsalisbury)

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

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

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

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

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

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

[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

[Chris Valean]

If you can point me to the ubuntu kernel sources where we can see how
the 4.15 and 4.18 kernels are found then I can check if a bisect would
be possible as such.

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

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

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

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

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

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

[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension

[Tim Passingham]

I have the same problem on my bionic, and now cosmic, laptop.

Suggesting users raise separate reports for every network interface
isn't helpful.

My ethernet controller is RTL 8111/8168/8411.

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

Title:
  r8169 ethernet card don't work after returning from suspension

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

Bug description:
  ===SRU Justification===
  [Impact]
  Ethernet r8169 stops working after system resumed from suspend.

  [Test]
  User confirmed these patches fix the issue. r8169 continues to work
  after resume from suspend.

  [Regression Potential]
  Medium. The fix is limited to one device, all patches are in mainline.
  The WOL default change might cause regression for users that depend on
  BIOS settings. We can advice them to use userspace tool (systemd,
  ethtool, etc.) instead.

  ===Original Bug Report===
  I have noticed that the network stopped working on my desktop after I've 
suspended the system and woke it up. On dmesg there are messages like:

  [  150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
  [  150.944101] do_IRQ: 3.37 No irq handler for vector
  [  150.944105] r8169 :01:00.0 enp1s0: link down
  [  150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready

  When using Xenial (from a different install), this problem is not
  happening. This is happening on Bionic.

  There are only two ways to restore connectivity:
  1) Reboot the system;
  2) Remove the r8169 module and reinsert it with modprobe.

  The motherboard is a AsRock H55M-LE and the Ethernet controller is:

  01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
  RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.172
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Mar  2 00:21:57 2018
  Dependencies:

  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-10-generic.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1153 F pulseaudio
   /dev/snd/controlC1:  usuario1153 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26'
     Mixer name : 'VIA VT1818S'
     Components : 'HDA:11060440,18492818,0010'
     Controls  : 40
     Simple ctrls  : 17
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27'
     Mixer name : 'ATI R6xx HDMI'
     Components : 'HDA:1002aa01,00aa0100,00100200'
     Controls  : 7
     Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
     Capabilities: pswitch pswitch-joined
     Playback channels: Mono
     Mono: Playback [on]
  CurrentDesktop: LXDE
  Dependencies:

  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux-firmware 1.172
  PackageArchitecture: all
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz 
root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  RfKill:

  Tags:  bionic
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: H55M-LE
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 

[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

[Chris Valean]

What I know is that this is working in azure kernels 4.15 series, but
not in 4.18 since we got the dailies with it for Cosmic.

>From the ubuntu kernel tree if these versions are separate branches then
I don't know how a bisect would work...

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

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

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

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

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

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

[Kernel-packages] [Bug 1803600] Re: Elantech - Touchpad not working after upgrading to 18.10 from 18.04 (ThinkPad L480)

[LGB [Gábor Lénárt]]

I have Lenovo L580. And a similar issue. The install image written to
the USB drive worked fine, but after installation touchpad simply did
not work. I've tried everything suggested (utilizing some google
searches ...), including kernel parameters, blacklisting various i2c hid
modules, and all the combinations, but nothing. It's a fresh 18.10
install, I have no idea if it would work with previous versions, but I
rather wouldn't downgrade, if this bug is expected to be fixed.

In my case, I see this in dmesg:

[2.418397] psmouse serio1: elantech: assuming hardware version 4 (with 
firmware version 0x5f3001)
[2.440307] psmouse serio1: elantech: Synaptics capabilities query result 
0x90, 0x18, 0x10.
[2.456358] psmouse serio1: elantech: Elan sample query result 00, 22, c8
[2.471110] psmouse serio1: elantech: Trying to set up SMBus access
[3.054187] elan_i2c 2-0015: 2-0015 supply vcc not found, using dummy 
regulator
[3.066012] elan_i2c 2-0015: failed to get resolution: -71
[3.066039] elan_i2c: probe of 2-0015 failed with error -71

Interestingly, sometimes the four first lines lines (grep'ing all lines
from dmesg containing strig 'elan'), and not the rest. But it can be,
because I tried to disable/enable touchpad in BIOS to see there is a
difference.

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

Title:
  Elantech - Touchpad not working after upgrading to 18.10 from 18.04
  (ThinkPad L480)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When updating from 18.04 to 18.10 on a ThinkPad L480 the Elantech
  touchpad stopped working. This means it is not recognized at all. This
  problem occured after the first boot in 18.10

  `dmesg | grep -i elantech` shows the following errors:

  [3.409043] psmouse serio1: elantech: assuming hardware version 4 
(with firmware version 0x5f3001)
  [3.427372] psmouse serio1: elantech: Synaptics capabilities query 
result 0x90, 0x18, 0x10.
  [3.447275] psmouse serio1: elantech: Elan sample query result 00, 23, 
c8
  [3.464905] psmouse serio1: elantech: Trying to set up SMBus access
  [5.576149] elan_i2c 0-0015: 0-0015 supply vcc not found, using dummy 
regulator
  [5.586505] elan_i2c 0-0015: failed to get resolution: -71
  [5.586527] elan_i2c: probe of 0-0015 failed with error -71

  uname:

  $ uname -a
  Linux test 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  I found the following thread which solves the problem temporarly (and reports 
the same problem in Arch):
  https://bugs.archlinux.org/task/59714

  Running the following command enables it again for the current
  session:

  sudo sh -c 'echo -n "elantech">
  /sys/bus/serio/devices/serio1/protocol'

  dmesg afterwards:

  [  569.522490] psmouse serio1: elantech: assuming hardware version 4 
(with firmware version 0x5f3001)
  [  569.544584] psmouse serio1: elantech: Synaptics capabilities query 
result 0x90, 0x18, 0x10.
  [  569.565939] psmouse serio1: elantech: Elan sample query result 00, 23, 
c8

  Before running the fix:

  $ cat /sys/bus/serio/devices/serio1/protocol
  ETSMBus

  and after:

  $ cat /sys/bus/serio/devices/serio1/protocol
  ETPS/2

  
  After reboot the command has to be run again, of course.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Thu Nov 15 20:59:36 2018
  DistUpgraded: 2018-11-10 09:56:53,358 DEBUG icon theme changed, re-reading
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.18, 4.15.0-38-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-10-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 620 [17aa:506a]
  InstallationDate: Installed on 2018-08-06 (101 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20LS001AGE
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=a1f97298-a2b8-469d-80ed-7497c6e6 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2018-11-10 (5 days ago)
  dmi.bios.date: 02/09/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0QET37W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 

[Kernel-packages] [Bug 1803863] Re: hid-multitouch

[Mac]

I tested the latest upstream kernel v4.20-rc3. 'kernel-fixed-upstream'

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

Title:
  hid-multitouch

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The cursor hangs from time to time whether I'm watching a video or scrolling 
through a webpage and I have to use the commands "sudo modprobe -r 
hid-multitouch && sudo modprobe multitouch" to keep enabling the touchpad. This 
bug is in kernels 4.15.0-24, 4.15.0-29, 4.15.0-30, 4.15.0-32, 4.15.0-33, 
4.15.0-34, 4.15.0-36, 4.15.0-38 and 4.15.0-39. Touchpad is FTE1200:00 0B05:0201.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   jay1640 F...m pulseaudio
   /dev/snd/controlC0:  jay1640 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=5b7bcf35-5ca6-4af2-a21c-ee9bf1c3b398
  InstallationDate: Installed on 2018-11-15 (3 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 13d3:5a01 IMC Networks 
   Bus 001 Device 005: ID 04ca:3010 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X541NA
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=c00192a2-f322-4512-bf47-91b23cb9aba2 ro modprobe.blacklist=hi 
d_sensor_hub quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-39.42~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-39-generic N/A
   linux-backports-modules-4.15.0-39-generic  N/A
   linux-firmware 1.173
  Tags:  sylvia
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/24/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X541NA.321
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X541NA
  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.:bvrX541NA.321:bd08/24/2018:svnASUSTeKCOMPUTERINC.:pnX541NA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541NA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: X541NA
  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/1803863/+subscriptions

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

[Kernel-packages] [Bug 1804028] Re: Surface Go - Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not correctly recognized

[Waynexyz]

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

** No longer affects: launchpad

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

Title:
  Surface Go - Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not
  correctly recognized

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Output of dmesg on Surface Go fresh installed Ubuntu 18.10.

  "[ 4.242132] ath10k_pci :01:00.0: qca6174 hw3.2 target 0x0503 chip_id 
0x00340aff sub 168c:3370
  [ 4.242138] ath10k_pci :01:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 
0 testmode 0
  [ 4.243006] ath10k_pci :01:00.0: firmware ver 
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
  [ 4.308059] ath10k_pci :01:00.0: failed to fetch board data for 
bus=pci,vendor=168c,device=003e,subsystem-vendor=168c,subsystem-device=3370 
from ath10k/QCA6174/hw3.0/board-2.bin
  [ 4.309354] ath10k_pci :01:00.0: board_file api 1 bmi_id N/A crc32 
ed5f849a"

  There is a board.bin available directly from the vendor
  http://www.killernetworking.com/support/K1535_Debian/board.bin

  The only thing which is missing is getting this added to
  https://wireless.wiki.kernel.org/en/users/drivers/ath10k/boardfiles so
  the official board-2.bin. My problem is that I dont know how to read
  the board files and modify them because I do not know the encoding
  they use.

  Also there have been some updates in the upstream linux-firmware repo.
  https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
  firmware.git/commit/?id=a87eb5f7bac0f70ade57da57d9126d14eee12336 and
  https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0 but
  they also do not help to get the wifi card working/recognized.

  Any ideas how to get this solved?

  Also there is a guide how to port it to Linux
  https://developer.qualcomm.com/download/qca9377/wlan-bluetooth-linux-
  porting-guide.pdf

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

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

[Kernel-packages] [Bug 1803863] Re: hid-multitouch

[Mac]

Yes, jsalisbury. I've noticed that kernel versions 4.15.0-20, 4.15.0-22
and 4.15.0-23 don't have this problem, but every other one in the 4.15
kernel series does.

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

Title:
  hid-multitouch

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The cursor hangs from time to time whether I'm watching a video or scrolling 
through a webpage and I have to use the commands "sudo modprobe -r 
hid-multitouch && sudo modprobe multitouch" to keep enabling the touchpad. This 
bug is in kernels 4.15.0-24, 4.15.0-29, 4.15.0-30, 4.15.0-32, 4.15.0-33, 
4.15.0-34, 4.15.0-36, 4.15.0-38 and 4.15.0-39. Touchpad is FTE1200:00 0B05:0201.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   jay1640 F...m pulseaudio
   /dev/snd/controlC0:  jay1640 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=5b7bcf35-5ca6-4af2-a21c-ee9bf1c3b398
  InstallationDate: Installed on 2018-11-15 (3 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 13d3:5a01 IMC Networks 
   Bus 001 Device 005: ID 04ca:3010 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X541NA
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=c00192a2-f322-4512-bf47-91b23cb9aba2 ro modprobe.blacklist=hi 
d_sensor_hub quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-39.42~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-39-generic N/A
   linux-backports-modules-4.15.0-39-generic  N/A
   linux-firmware 1.173
  Tags:  sylvia
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/24/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X541NA.321
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X541NA
  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.:bvrX541NA.321:bd08/24/2018:svnASUSTeKCOMPUTERINC.:pnX541NA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541NA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: X541NA
  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/1803863/+subscriptions

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

[Kernel-packages] [Bug 1798400] Re: Regression: cannot use impress remote over bluetooth with ubuntu bionic

[Bug Watch Updater]

Launchpad has imported 1 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=120663.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2018-10-17T15:57:39+00:00 Sergio Callegari wrote:

Description:
The fault seems to be on the Libreoffice application running on the computer, 
not on the android impress remote app.

Running libreoffice, the computer reports a bluetoothd error on syslog,
namely

bluetoothd[1491]: RFCOMM server failed for LibreOffice Impress Remote:
rfcomm_bind: Address already in use (98)

After that the remote handset cannot connect via bluetooth to LibO even
if the the bluetooth adapters in the computer and the handset are
paired.

The issue appears in the bug trackers of both Ubuntu and Fedora and
regards Ubuntu 18.04 and Fedora 27.

I am 100% sure that in the past the impress remote was working via
bluetooth on the same hardware (both computer and handset).

It is unclear to me if the issue is with the bluetooth stack of recent
linux distros (bluez? kernel?) or if something has changed in it and
LibO is trying to still use it in some old way that is now wrong.

The issue is now present using any LibO version from 5.4 to 6.1.

See https://bugzilla.redhat.com/show_bug.cgi?id=1581879
and https://bugs.launchpad.net/bugs/1798400

Steps to Reproduce:
See description

Actual Results:
See description

Expected Results:
See description


Reproducible: Always


User Profile Reset: No


Additional Info:
[Information automatically included from LibreOffice]
Locale: en-US
Module: StartModule
[Information guessed from browser]
OS: Linux (All)
OS is 64bit: yes

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1798400/comments/4


** Changed in: df-libreoffice
   Status: Unknown => New

** Changed in: df-libreoffice
   Importance: Unknown => 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/1798400

Title:
  Regression: cannot use impress remote over bluetooth with ubuntu
  bionic

Status in LibreOffice:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in libreoffice package in Fedora:
  Unknown

Bug description:
  Trying to use the impress remote
  (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth
  with libreoffice over ubuntu bionic fails.

  The handset errors out that it cannot connect with Libreoffice on the
  computer even if the bluetooth adapter on the handset and on the
  computer are correctly paired.

  This does not seem to be an issue in the Libreoffice or in the impress
  remote code:

  - I have tested also past LibO versions
  - The Impress remote codebase has not changed recently

  This used to work on the same hardware (headset and laptop) with
  ubuntu 16.04.

  Hence the issue seems to be in a regression in the ubuntu bluetooth
  stack.

  To replicate:

  1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo
  or with the deb packages from the document fundation)

  2) Assure that your computer has bluetooth

  3) Install impress remote on an android handset (either from the play
  store of via fdroid)

  4) Assure that "remote control" is enabled in impress
  Tools>Options>Impress>General

  5) Pair the bluetooth adapters in the laptop and in the computer

  6) Open a presentation on the laptop

  7) Open the remote on the handset, got to the bluetooth pane see the
  computer there, touch it

  8) See the impress remote erroring out

  Most likely you will also get a bluetooth error on dmesg

  RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind:
  Address already in use (98)

  Same issue was reported for fedora

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Oct 17 16:57:29 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-12 (1769 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Notebook W740SU
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/zagar_ssd--vg-root ro quiet splash 
resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago)
  dmi.bios.date: 10/02/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  

[Kernel-packages] [Bug 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] is not supported

[Waynexyz]

Edit:

This terminal ouput is from a Surface Go.

Also there is a guide how to port it to Linux
https://developer.qualcomm.com/download/qca9377/wlan-bluetooth-linux-
porting-guide.pdf

Also there have been some updates in the upstream linux-firmware repo.
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/?id=a87eb5f7bac0f70ade57da57d9126d14eee12336 and
https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0 but
they also do not help to get the wifi card working.

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

Title:
  Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] is not supported

Status in HWE Next:
  Fix Released
Status in HWE Next wily series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in linux source package in Wily:
  Fix Released
Status in linux-firmware source package in Wily:
  Fix Released

Bug description:
  =

  CURRENT STATUS:

  Wily(15.10) could not work with and don't need Adam's dkms package 1.0
  or 1.1

  Wily(15.10) has already fixed the driver part, and the firmware part
  is in progress.

  For now, you guys could use 15.10(purge the ath10k-dkms if you tried
  installing it), and make a copy of
  https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-
  firmware.git/plain/ath10k/QCA6174 into /lib/firmware/ath10k/

  15.10 will work in a week by a simple `apt upgrade`

  Distros before 15.10(lower than 4.2 kernel) please keep using the
  dkms(which will be relocated soon)

  =

  Card detail: Qualcomm Atheros Device [168c:003e] (rev 20)
  Subsystem: Bigfoot Networks, Inc. Device [1a56:1525]

  This is on a fully updated Ubuntu Server 14.04 installation, with the 
ubuntu-desktop environment installed. This happened in order to get the md raid 
drivers for raid0 on my system, as the desktop version doesn't support them.
  ---
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  matanis2333 F pulseaudio
   /dev/snd/controlC0:  matanis2333 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6
  InstallationDate: Installed on 2014-10-16 (3 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig:
   p2p1  no wireless extensions.

   lono wireless extensions.
  MachineType: Micro-Star International Co., Ltd. GT72 2QE
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed 
root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  RfKill:

  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1781IMS.10D
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1781
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.C
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: GT72 2QE
  dmi.product.version: REV:0.C
  dmi.sys.vendor: Micro-Star International Co., Ltd.

  Qualcomm Atheros Device [168c:003e] (rev 20)

  mainline commit d63955b33b3bee45d784ffdfafeb93076c765660

  [6.221281] ath10k_pci :02:00.0: pci irq msi interrupts 1 irq_mode 0 
reset_mode 0
  [6.417386] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/cal-pci-:02:00.0.bin failed with error -2
  [6.417404] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/QCA6174/hw2.1/board-pci-168c:003e:17aa:3044.bin failed with error -2
  [6.417407] ath10k_pci :02:00.0: failed to load spec board file, 
falling back to generic: -2
  [6.417416] ath10k_pci :02:00.0: Direct firmware load for 

[Kernel-packages] [Bug 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] is not supported

[Waynexyz]

Still an issue even four years later.

On Ubuntu 18.10 dmesg outputs:

"[4.242132] ath10k_pci :01:00.0: qca6174 hw3.2 target 0x0503 
chip_id 0x00340aff sub 168c:3370
[4.242138] ath10k_pci :01:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 
0 testmode 0
[4.243006] ath10k_pci :01:00.0: firmware ver 
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
[4.308059] ath10k_pci :01:00.0: failed to fetch board data for 
bus=pci,vendor=168c,device=003e,subsystem-vendor=168c,subsystem-device=3370 
from ath10k/QCA6174/hw3.0/board-2.bin
[4.309354] ath10k_pci :01:00.0: board_file api 1 bmi_id N/A crc32 
ed5f849a"

There is a board.bin available directly from the vendor
http://www.killernetworking.com/support/K1535_Debian/board.bin

The only thing which is missing is getting this added to
https://wireless.wiki.kernel.org/en/users/drivers/ath10k/boardfiles . My
problem is that I dont know how to read the board files and modify them
because I do not know the encoding they use.

Any ideas how to get this solved?

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

Title:
  Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] is not supported

Status in HWE Next:
  Fix Released
Status in HWE Next wily series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in linux source package in Wily:
  Fix Released
Status in linux-firmware source package in Wily:
  Fix Released

Bug description:
  =

  CURRENT STATUS:

  Wily(15.10) could not work with and don't need Adam's dkms package 1.0
  or 1.1

  Wily(15.10) has already fixed the driver part, and the firmware part
  is in progress.

  For now, you guys could use 15.10(purge the ath10k-dkms if you tried
  installing it), and make a copy of
  https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-
  firmware.git/plain/ath10k/QCA6174 into /lib/firmware/ath10k/

  15.10 will work in a week by a simple `apt upgrade`

  Distros before 15.10(lower than 4.2 kernel) please keep using the
  dkms(which will be relocated soon)

  =

  Card detail: Qualcomm Atheros Device [168c:003e] (rev 20)
  Subsystem: Bigfoot Networks, Inc. Device [1a56:1525]

  This is on a fully updated Ubuntu Server 14.04 installation, with the 
ubuntu-desktop environment installed. This happened in order to get the md raid 
drivers for raid0 on my system, as the desktop version doesn't support them.
  ---
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  matanis2333 F pulseaudio
   /dev/snd/controlC0:  matanis2333 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6
  InstallationDate: Installed on 2014-10-16 (3 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig:
   p2p1  no wireless extensions.

   lono wireless extensions.
  MachineType: Micro-Star International Co., Ltd. GT72 2QE
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed 
root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  RfKill:

  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1781IMS.10D
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1781
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.C
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: GT72 2QE
  dmi.product.version: REV:0.C
  dmi.sys.vendor: Micro-Star International Co., Ltd.

  Qualcomm Atheros Device [168c:003e] (rev 20)

  mainline commit 

[Kernel-packages] [Bug 1719545] Re: [P9][LTCTest][Opal][FW910] cpupower monitor shows multiple stop Idle_Stats

[Joseph Salisbury]

I built a test kernel with commit f9652d5cae0.  The test kernel can be 
downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1719545

Can you test this kernel and see if it resolves this bug?

Note about installing test kernels:
* If the test kernel is prior to 4.15(Bionic) you need to install the 
linux-image and linux-image-extra .deb packages.
* If the test kernel is 4.15(Bionic) or newer, you need to install the 
linux-modules, linux-modules-extra and linux-image-unsigned .deb packages.

Thanks in advance!

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

Title:
  [P9][LTCTest][Opal][FW910] cpupower monitor shows multiple stop
  Idle_Stats

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  == Comment: #0 - PAVAMAN SUBRAMANIYAM  - 2017-06-29 
02:30:22 ==
  ---Problem Description---
  cpupower monitor shows multiple stop Idle_Stats
   

   
  ---uname output---
  Linux zz376p1 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:38:48 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = P9 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  Install a P9 8375-42A Hardware with Ubuntu 16.04.3 OS.
  Then execute the cpupower monitor command to fetch all the Idle_Stats values.

  root@zz376p1:~# cpupower monitor
|Idle_Stats
  PKG |CORE|CPU | snoo | stop | stop
 0|   8|   0|  0.00|  0.00|  2.79
 0|   8|   1|  0.00|  0.00| 70.68
 0|   8|   2|  0.00|  0.00| 99.87
 0|   8|   3|  0.00|  0.00| 67.28
 0|  12|   4|  0.00|  0.00|  5.17
 0|  12|   5|  0.00|  0.00| 12.50
 0|  12|   6|  0.00|  0.00| 99.74
 0|  12|   7|  0.00|  0.00|  0.00
 8|2048|   8|  0.00|  0.00| 22.14
 8|2048|   9|  0.00|  0.00| 102.3
 8|2048|  10|  0.00|  0.00|  0.00
 8|2048|  11|  0.00|  0.00| 99.97
 8|2052|  12|  0.00|  0.00| 99.70
 8|2052|  13|  0.00|  0.00| 23.86
 8|2052|  14|  0.00|  0.00| 113.1
 8|2052|  15|  0.00|  0.00|  0.00

  As can be seen it shows 2 columns for stop.

  root@zz376p1:~# uname -a
  Linux zz376p1 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:38:48 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  root@zz376p1:~# cat /etc/os-release
  NAME="Ubuntu"
  VERSION="16.04.2 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.2 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial

  root@zz376p1:~# cat /proc/cpuinfo | tail
  processor   : 15
  cpu : POWER9 (raw), altivec supported
  clock   : 2600.00MHz
  revision: 1.0 (pvr 004e 0100)

  timebase: 51200
  platform: PowerNV
  model   : 8375-42A
  machine : PowerNV 8375-42A
  firmware: OPAL
   
  Userspace tool common name: /usr/bin/cpupower 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: linux-tools-common

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for pavsu...@in.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.
  -Attach ltrace and strace of userspace application.

  
  .
  There are 3 idle_stats (3 states) in this system. 

  root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower monitor -l
  Monitor "Idle_Stats" (3 states) - Might overflow after 4294967295 s
  snoo  [T] -> snooze
  stop  [T] -> stop0_lite
  stop  [T] -> stop1_lite

  root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower idle-info
  CPUidle driver: powernv_idle
  CPUidle governor: menu
  analyzing CPU 0:

  Number of idle states: 3
  Available idle states: snooze stop0_lite stop1_lite
  snooze:
  Flags/Description: snooze
  Latency: 0
  Usage: 224
  Duration: 423
  stop0_lite:
  Flags/Description: stop0_lite
  Latency: 0
  Usage: 1685
  Duration: 530522
  stop1_lite:
  Flags/Description: stop1_lite
  Latency: 4
  Usage: 12693
  Duration: 5405898106

  root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower monitor -l
  Monitor "Idle_Stats" (3 states) - Might overflow after 4294967295 s
  snoo  [T] -> snooze
  stop  [T] -> stop0_lite
  stop  [T] -> stop1_lite
  root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower idle-info
  CPUidle driver: powernv_idle
  CPUidle governor: menu
  analyzing CPU 0:

  Number of idle states: 3
  Available idle states: snooze stop0_lite stop1_lite
  snooze:
  Flags/Description: snooze
  Latency: 0
  Usage: 272
  Duration: 905
  stop0_lite:
  Flags/Description: stop0_lite
  Latency: 0
  Usage: 2141
  Duration: 536399
  stop1_lite:
  Flags/Description: stop1_lite
  Latency: 4
  

[Kernel-packages] [Bug 1787405] Re: [FEAT] Guest-dedicated Crypto Adapters

[Dimitri John Ledkov]

** Tags added: verification-done-cosmic

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

Title:
  [FEAT] Guest-dedicated Crypto Adapters

Status in Ubuntu on IBM z Systems:
  In Progress
Status in libvirt package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in qemu package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  == SRU Justification ==

  (Kernel SRU)

  Allow kvm to dedicate crypto adapters (and domains) as passthrough devices to 
a KVM guest such that the hypervisor cannot observe the communication of the 
guest with the device.
  (Since all kernel patches/commits are from kernel 4.19, they will 
automagically land in 'Disco'.)

  == Fix ==

  9ea5972 ("KVM: s390: vsie: simulate VCPU SIE entry/exit")
  3194cdb ("KVM: s390: introduce and use KVM_REQ_VSIE_RESTART")
  e585b24 ("KVM: s390: refactor crypto initialization")
  1fde573 ("s390: vfio-ap: base implementation of VFIO AP device driver")
  65f0671 ("s390: vfio-ap: register matrix device with VFIO mdev framework")
  96d152b ("s390: vfio-ap: sysfs interfaces to configure adapters")
  3211da0 ("s390: vfio-ap: sysfs interfaces to configure domains")
  3b1eab7 ("s390: vfio-ap: sysfs interfaces to configure control domains")
  81b2b4b ("s390: vfio-ap: sysfs interface to view matrix mdev matrix")
  4210459 ("KVM: s390: interface to clear CRYCB masks")
  258287c ("s390: vfio-ap: implement mediated device open callback")
  e06670c ("s390: vfio-ap: implement VFIO_DEVICE_GET_INFO ioctl")
  46a7263 ("s390: vfio-ap: zeroize the AP queues")
  cd8a377 ("s390: vfio-ap: implement VFIO_DEVICE_RESET ioctl")
  6cc571b ("KVM: s390: Clear Crypto Control Block when using vSIE")
  d6f6959 ("KVM: s390: vsie: Do the CRYCB validation first")
  3af84de ("KVM: s390: vsie: Make use of CRYCB FORMAT2 clear")
  56019f9 ("KVM: s390: vsie: Allow CRYCB FORMAT-2")
  19fd83a ("KVM: s390: vsie: allow CRYCB FORMAT-1")
  6ee7409 ("KVM: s390: vsie: allow CRYCB FORMAT-0")
  c9ba8c2 ("KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-1")
  6b79de4 ("KVM: s390: vsie: allow guest FORMAT-1 CRYCB on host FORMAT-2")
  9ee71f2 ("KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-2")
  37940fb ("KVM: s390: device attrs to enable/disable AP interpretation")
  112c24d ("KVM: s390: CPU model support for AP virtualization")
  492a6be ("s390: doc: detailed specifications for AP virtualization")

  <-- till here in 'kvm/next'
  (https://git.kernel.org/pub/scm/virt/kvm/kvm.git/) -->

  8e41bd5 ("KVM: s390: fix locking for crypto setting error path")
  0e237e4 ("KVM: s390: Tracing APCB changes")
  76c7829 ("s390: vfio-ap: setup APCB mask using KVM dedicated function")

  <-- till here in 'kvms390/next'
  (https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git/)
  -->

  <-- In addition to that some prereqs for the 'ap/crypto' driver are
  necessary -->

  ea3c418 ("s390/zcrypt: Add ZAPQ inline function.")
  df80c03 ("s390/zcrypt: Review inline assembler constraints.")
  f1b0a43 ("s390/zcrypt: Integrate ap_asm.h into include/asm/ap.h.")
  2395103 ("s390/zcrypt: fix ap_instructions_available() returncodes")
  7e0bdbe ("s390/zcrypt: AP bus support for alternate driver(s)")
  3d8f60d3 ("s390/zcrypt: hex string mask improvements for apmask and aqmask.")
  fa108f9 ("s390/zcrypt: remove VLA usage from the AP bus")

  <--
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787405/comments/12
  -->

  == PATCH ==

  Above git commits are all from 4.19.
  The git commands for 4.18 would be:

  $ git cherry-pick 

  (112c24d "KVM: s390: CPU model support for AP virtualization" may have
  a trivial merge conflict with the etoken patch)

  $ git cherry-pick 

  $ git cherry-pick 

  == Regression Potential ==

  Low to mid:

  - mid because in summary there are a lot of changes, but low
  - they are all limited to the s390x architecture
  - and again limited to KVM/s390x, vfio-ap and the zcrypt (aka ap) driver
  - Test kernel was built for testting.

  == Test Case ==

  Setup a system for KVM use on an s390x LPAR that has CryptoExpress (aka 
crypto-) adapters installed.
  Verify that the AP bus created a sysfs device for each APQN, like:
  /sys/devices/ap/card04/04.0006
  /sys/devices/ap/card04/04.0047
  /sys/devices/ap/card0a/0a.0006
  /sys/devices/ap/card0a/0a.0047
  Verify the APQN range via the following two sysfs files:
  /sys/bus/ap/apmask
  /sys/bus/ap/aqmask
  Configure and start a guest.
  More details see: 492a6be ("s390: doc: detailed specifications for AP 
virtualization")
  But for that an updated qemu and libvirt should be in place - that's 
addressed in LP1787405, too.
  (So this is only the kernel part of that ticket.)
  __

  

[Kernel-packages] [Bug 1792100] Re: Boot hangs at "loading initial ramdisk..."

[Joseph Salisbury]

Hmm, OK, thanks for the feedback.  Let me review the bisect results and
see if we went astray at some point.

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

Title:
  Boot hangs at "loading initial ramdisk..."

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

Bug description:
  I cannot load a kernel beyond 4.15.0-32-generic on my machine.
  Both 4.15.0-33-generic and 4.15.0-34-generic hang at "loading initial 
ramdisk...".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-34-generic 4.15.0-34.37
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kms2233 F pulseaudio
   /dev/snd/controlC1:  kms2233 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 12 10:52:00 2018
  HibernationDevice: RESUME=UUID=c3d34d19-9e9e-4967-ac45-f1d699cf5eef
  InstallationDate: Installed on 2018-01-05 (249 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Precision Tower 7810
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=90d43be7-a2f7-4500-8b88-9bd7a549d96d ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (132 days ago)
  dmi.bios.date: 06/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A27
  dmi.board.name: 0KJCC5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA27:bd06/25/2018:svnDellInc.:pnPrecisionTower7810:pvr:rvnDellInc.:rn0KJCC5:rvrA00:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 7810
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1719545] Re: [P9][LTCTest][Opal][FW910] cpupower monitor shows multiple stop Idle_Stats

[Joseph Salisbury]

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

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

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

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Joseph 
Salisbury (jsalisbury)

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

Title:
  [P9][LTCTest][Opal][FW910] cpupower monitor shows multiple stop
  Idle_Stats

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  == Comment: #0 - PAVAMAN SUBRAMANIYAM  - 2017-06-29 
02:30:22 ==
  ---Problem Description---
  cpupower monitor shows multiple stop Idle_Stats
   

   
  ---uname output---
  Linux zz376p1 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:38:48 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = P9 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  Install a P9 8375-42A Hardware with Ubuntu 16.04.3 OS.
  Then execute the cpupower monitor command to fetch all the Idle_Stats values.

  root@zz376p1:~# cpupower monitor
|Idle_Stats
  PKG |CORE|CPU | snoo | stop | stop
 0|   8|   0|  0.00|  0.00|  2.79
 0|   8|   1|  0.00|  0.00| 70.68
 0|   8|   2|  0.00|  0.00| 99.87
 0|   8|   3|  0.00|  0.00| 67.28
 0|  12|   4|  0.00|  0.00|  5.17
 0|  12|   5|  0.00|  0.00| 12.50
 0|  12|   6|  0.00|  0.00| 99.74
 0|  12|   7|  0.00|  0.00|  0.00
 8|2048|   8|  0.00|  0.00| 22.14
 8|2048|   9|  0.00|  0.00| 102.3
 8|2048|  10|  0.00|  0.00|  0.00
 8|2048|  11|  0.00|  0.00| 99.97
 8|2052|  12|  0.00|  0.00| 99.70
 8|2052|  13|  0.00|  0.00| 23.86
 8|2052|  14|  0.00|  0.00| 113.1
 8|2052|  15|  0.00|  0.00|  0.00

  As can be seen it shows 2 columns for stop.

  root@zz376p1:~# uname -a
  Linux zz376p1 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:38:48 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  root@zz376p1:~# cat /etc/os-release
  NAME="Ubuntu"
  VERSION="16.04.2 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.2 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial

  root@zz376p1:~# cat /proc/cpuinfo | tail
  processor   : 15
  cpu : POWER9 (raw), altivec supported
  clock   : 2600.00MHz
  revision: 1.0 (pvr 004e 0100)

  timebase: 51200
  platform: PowerNV
  model   : 8375-42A
  machine : PowerNV 8375-42A
  firmware: OPAL
   
  Userspace tool common name: /usr/bin/cpupower 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: linux-tools-common

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for pavsu...@in.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.
  -Attach ltrace and strace of userspace application.

  
  .
  There are 3 idle_stats (3 states) in this system. 

  root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower monitor -l
  Monitor "Idle_Stats" (3 states) - Might overflow after 4294967295 s
  snoo  [T] -> snooze
  stop  [T] -> stop0_lite
  stop  [T] -> stop1_lite

  root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower idle-info
  CPUidle driver: powernv_idle
  CPUidle governor: menu
  analyzing CPU 0:

  Number of idle states: 3
  Available idle states: snooze stop0_lite stop1_lite
  snooze:
  Flags/Description: snooze
  Latency: 0
  Usage: 224
  Duration: 423
  stop0_lite:
  Flags/Description: stop0_lite
  Latency: 0
  Usage: 1685
  Duration: 530522
  stop1_lite:
  Flags/Description: stop1_lite
  Latency: 4
  Usage: 12693
  Duration: 5405898106

  root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower monitor -l
  Monitor "Idle_Stats" (3 states) - Might overflow after 4294967295 s
  snoo  [T] -> snooze
  stop  [T] -> stop0_lite
  stop  [T] -> stop1_lite
  root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower idle-info
  CPUidle driver: powernv_idle
  CPUidle governor: menu
  analyzing CPU 0:

  Number of idle states: 3
  Available idle states: snooze stop0_lite stop1_lite
  snooze:
  Flags/Description: snooze
  Latency: 0
  Usage: 272
  Duration: 905
  stop0_lite:
  Flags/Description: stop0_lite
  Latency: 0
  Usage: 2141
  Duration: 536399
  stop1_lite:
  Flags/Description: stop1_lite
  Latency: 4
  

[Kernel-packages] [Bug 1803881] Re: thermal thermal_zone4: failed to read out thermal zone (-61)

[Giovanni Caligaris]

I also want to add that my pc is the newest Intel NUC8i5BEH. I will try
the latest kernel and will report back.

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

Title:
  thermal thermal_zone4: failed to read out thermal zone (-61)

Status in linux package in Ubuntu:
  Incomplete
Status in thermald package in Ubuntu:
  New

Bug description:
  Thermald can't read zone4. It's making my fan go crazy, this issue
  seems to be a bit more controlled in 18.10.

  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  Codename: bionic

  sudo apt-cache policy thermald 
  thermald:
Installed: 1.7.0-5ubuntu1
Candidate: 1.7.0-5ubuntu1
Version table:
   *** 1.7.0-5ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  
  cat /sys/class/thermal/thermal_zone4/type
  iwlwifi

  find /sys/class/thermal/thermal_zone4/ -type f -print -exec cat {} \;
  /sys/class/thermal/thermal_zone4/uevent
  /sys/class/thermal/thermal_zone4/trip_point_5_temp
  -32768000
  /sys/class/thermal/thermal_zone4/trip_point_3_type
  passive
  /sys/class/thermal/thermal_zone4/trip_point_4_temp
  -32768000
  /sys/class/thermal/thermal_zone4/trip_point_2_type
  passive
  /sys/class/thermal/thermal_zone4/power/runtime_active_time
  0
  /sys/class/thermal/thermal_zone4/power/runtime_active_kids
  0
  /sys/class/thermal/thermal_zone4/power/runtime_usage
  0
  /sys/class/thermal/thermal_zone4/power/runtime_status
  unsupported
  /sys/class/thermal/thermal_zone4/power/autosuspend_delay_ms
  cat: /sys/class/thermal/thermal_zone4/power/autosuspend_delay_ms: 
Input/output error
  /sys/class/thermal/thermal_zone4/power/async
  disabled
  /sys/class/thermal/thermal_zone4/power/runtime_suspended_time
  0
  /sys/class/thermal/thermal_zone4/power/runtime_enabled
  disabled
  /sys/class/thermal/thermal_zone4/power/control
  auto
  /sys/class/thermal/thermal_zone4/available_policies
  power_allocator user_space bang_bang fair_share step_wise 
  /sys/class/thermal/thermal_zone4/policy
  step_wise
  /sys/class/thermal/thermal_zone4/trip_point_3_temp
  -32768000
  /sys/class/thermal/thermal_zone4/trip_point_1_type
  passive
  /sys/class/thermal/thermal_zone4/k_d
  cat: /sys/class/thermal/thermal_zone4/k_d: Input/output error
  /sys/class/thermal/thermal_zone4/sustainable_power
  cat: /sys/class/thermal/thermal_zone4/sustainable_power: Input/output error
  /sys/class/thermal/thermal_zone4/type
  iwlwifi
  /sys/class/thermal/thermal_zone4/trip_point_7_type
  passive
  /sys/class/thermal/thermal_zone4/offset
  cat: /sys/class/thermal/thermal_zone4/offset: Input/output error
  /sys/class/thermal/thermal_zone4/slope
  cat: /sys/class/thermal/thermal_zone4/slope: Input/output error
  /sys/class/thermal/thermal_zone4/trip_point_2_temp
  -32768000
  /sys/class/thermal/thermal_zone4/trip_point_0_type
  passive
  /sys/class/thermal/thermal_zone4/trip_point_6_type
  passive
  /sys/class/thermal/thermal_zone4/emul_temp
  cat: /sys/class/thermal/thermal_zone4/emul_temp: Permission denied
  /sys/class/thermal/thermal_zone4/k_po
  cat: /sys/class/thermal/thermal_zone4/k_po: Input/output error
  /sys/class/thermal/thermal_zone4/integral_cutoff
  cat: /sys/class/thermal/thermal_zone4/integral_cutoff: Input/output error
  /sys/class/thermal/thermal_zone4/k_i
  cat: /sys/class/thermal/thermal_zone4/k_i: Input/output error
  /sys/class/thermal/thermal_zone4/trip_point_1_temp
  -32768000
  /sys/class/thermal/thermal_zone4/k_pu
  cat: /sys/class/thermal/thermal_zone4/k_pu: Input/output error
  /sys/class/thermal/thermal_zone4/temp
  46000
  /sys/class/thermal/thermal_zone4/trip_point_7_temp
  -32768000
  /sys/class/thermal/thermal_zone4/trip_point_5_type
  passive
  /sys/class/thermal/thermal_zone4/trip_point_0_temp
  -32768000
  /sys/class/thermal/thermal_zone4/trip_point_6_temp
  -32768000
  /sys/class/thermal/thermal_zone4/trip_point_4_type
  passive

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

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

[Kernel-packages] [Bug 1803881] Re: thermal thermal_zone4: failed to read out thermal zone (-61)

[Giovanni Caligaris]

This issue happens with the stock 4.15 kernel. I have upgraded the
kernel to 4.18 and 4.19 and was getting the same issue. I managed to get
rid off the error now. It seems it does not like intel_pstate. I added
intel_pstate=disable to grub and the error has gone away.

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

Title:
  thermal thermal_zone4: failed to read out thermal zone (-61)

Status in linux package in Ubuntu:
  Incomplete
Status in thermald package in Ubuntu:
  New

Bug description:
  Thermald can't read zone4. It's making my fan go crazy, this issue
  seems to be a bit more controlled in 18.10.

  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  Codename: bionic

  sudo apt-cache policy thermald 
  thermald:
Installed: 1.7.0-5ubuntu1
Candidate: 1.7.0-5ubuntu1
Version table:
   *** 1.7.0-5ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  
  cat /sys/class/thermal/thermal_zone4/type
  iwlwifi

  find /sys/class/thermal/thermal_zone4/ -type f -print -exec cat {} \;
  /sys/class/thermal/thermal_zone4/uevent
  /sys/class/thermal/thermal_zone4/trip_point_5_temp
  -32768000
  /sys/class/thermal/thermal_zone4/trip_point_3_type
  passive
  /sys/class/thermal/thermal_zone4/trip_point_4_temp
  -32768000
  /sys/class/thermal/thermal_zone4/trip_point_2_type
  passive
  /sys/class/thermal/thermal_zone4/power/runtime_active_time
  0
  /sys/class/thermal/thermal_zone4/power/runtime_active_kids
  0
  /sys/class/thermal/thermal_zone4/power/runtime_usage
  0
  /sys/class/thermal/thermal_zone4/power/runtime_status
  unsupported
  /sys/class/thermal/thermal_zone4/power/autosuspend_delay_ms
  cat: /sys/class/thermal/thermal_zone4/power/autosuspend_delay_ms: 
Input/output error
  /sys/class/thermal/thermal_zone4/power/async
  disabled
  /sys/class/thermal/thermal_zone4/power/runtime_suspended_time
  0
  /sys/class/thermal/thermal_zone4/power/runtime_enabled
  disabled
  /sys/class/thermal/thermal_zone4/power/control
  auto
  /sys/class/thermal/thermal_zone4/available_policies
  power_allocator user_space bang_bang fair_share step_wise 
  /sys/class/thermal/thermal_zone4/policy
  step_wise
  /sys/class/thermal/thermal_zone4/trip_point_3_temp
  -32768000
  /sys/class/thermal/thermal_zone4/trip_point_1_type
  passive
  /sys/class/thermal/thermal_zone4/k_d
  cat: /sys/class/thermal/thermal_zone4/k_d: Input/output error
  /sys/class/thermal/thermal_zone4/sustainable_power
  cat: /sys/class/thermal/thermal_zone4/sustainable_power: Input/output error
  /sys/class/thermal/thermal_zone4/type
  iwlwifi
  /sys/class/thermal/thermal_zone4/trip_point_7_type
  passive
  /sys/class/thermal/thermal_zone4/offset
  cat: /sys/class/thermal/thermal_zone4/offset: Input/output error
  /sys/class/thermal/thermal_zone4/slope
  cat: /sys/class/thermal/thermal_zone4/slope: Input/output error
  /sys/class/thermal/thermal_zone4/trip_point_2_temp
  -32768000
  /sys/class/thermal/thermal_zone4/trip_point_0_type
  passive
  /sys/class/thermal/thermal_zone4/trip_point_6_type
  passive
  /sys/class/thermal/thermal_zone4/emul_temp
  cat: /sys/class/thermal/thermal_zone4/emul_temp: Permission denied
  /sys/class/thermal/thermal_zone4/k_po
  cat: /sys/class/thermal/thermal_zone4/k_po: Input/output error
  /sys/class/thermal/thermal_zone4/integral_cutoff
  cat: /sys/class/thermal/thermal_zone4/integral_cutoff: Input/output error
  /sys/class/thermal/thermal_zone4/k_i
  cat: /sys/class/thermal/thermal_zone4/k_i: Input/output error
  /sys/class/thermal/thermal_zone4/trip_point_1_temp
  -32768000
  /sys/class/thermal/thermal_zone4/k_pu
  cat: /sys/class/thermal/thermal_zone4/k_pu: Input/output error
  /sys/class/thermal/thermal_zone4/temp
  46000
  /sys/class/thermal/thermal_zone4/trip_point_7_temp
  -32768000
  /sys/class/thermal/thermal_zone4/trip_point_5_type
  passive
  /sys/class/thermal/thermal_zone4/trip_point_0_temp
  -32768000
  /sys/class/thermal/thermal_zone4/trip_point_6_temp
  -32768000
  /sys/class/thermal/thermal_zone4/trip_point_4_type
  passive

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

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

[Kernel-packages] [Bug 1792100] Re: Boot hangs at "loading initial ramdisk..."

[Krister]

Neither the 4.18.0-10 nor the 4.15.0-39 kernel will boot.

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

Title:
  Boot hangs at "loading initial ramdisk..."

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

Bug description:
  I cannot load a kernel beyond 4.15.0-32-generic on my machine.
  Both 4.15.0-33-generic and 4.15.0-34-generic hang at "loading initial 
ramdisk...".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-34-generic 4.15.0-34.37
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kms2233 F pulseaudio
   /dev/snd/controlC1:  kms2233 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 12 10:52:00 2018
  HibernationDevice: RESUME=UUID=c3d34d19-9e9e-4967-ac45-f1d699cf5eef
  InstallationDate: Installed on 2018-01-05 (249 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Precision Tower 7810
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=90d43be7-a2f7-4500-8b88-9bd7a549d96d ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (132 days ago)
  dmi.bios.date: 06/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A27
  dmi.board.name: 0KJCC5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA27:bd06/25/2018:svnDellInc.:pnPrecisionTower7810:pvr:rvnDellInc.:rn0KJCC5:rvrA00:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 7810
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1797367] Re: Ubuntu 18.04.1 - [s390x] Kernel panic while stressing network bonding

[Frank Heimes]

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

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

Title:
  Ubuntu 18.04.1 - [s390x] Kernel panic while stressing network bonding

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  == SRU Justification ==

  While running a series of stress tests for network on a bond device on Ubuntu 
18.04.1 with kernel 4.15.0-36.39,
  kernel panic is observed (btw. also on non-bond devices).
  This looks like a race between disabling a qeth device and accessing debugfs.
  This is critical and leads repeatedly to a crash (sooner or later).

  == Fix ==

  e19e5be8b4ca ("s390/qeth: sanitize strings in debug messages")

  pre-reqs:
  750b162 ("s390/qeth: reduce hard-coded access to ccw channels")
  d857e11 ("s390/qeth: remove outdated portname debug msg")
  9d0a58f ("s390/qeth: avoid using is_multicast_ether_addr_64bits on (u8 *)[6]")
  8174aa8 ("s390/qeth: consolidate qeth MAC address helpers")
  4641b02 ("s390/qeth: don't keep track of MAC address's cast type")

  == Regression Potential ==

  Low, because:

  - limited to s390x
  - and again limited to qeth driver
  - patches a problem identified during testing
  - fix was tested by IBM before submitted

  == Test Case ==

  run:
 #!/bin/bash
 var=0
 while :
 do
  var=$((var + 1))
  echo "DBG count is $var"
  mkdir /tmp/DBGINFO
  dbginfo.sh -d /tmp/DBGINFO
  rm -rf /tmp/DBGINFO*
  echo "chzdev now is $var"
  chzdev -e 
  chzdev -d 
 done
  and in avg. in less than 20 cycles a crash happens (usually < 10).

  __

  == Comment: #0 - Athira Rajeev
  ---Problem Description---
  While running a series of stress tests for network bonding on UBUNTU 18.04.1 
with kernel 4.15.0-36.39, kernel panic is observed.
  There are two instance of panic experienced with the same test procedures one 
of which indicates to be a kernel BUG.

  Contact Information = Athira Rajeev , Waiki
  Wright < wa...@us.ibm.com >

  ---uname output---
  #39-Ubuntu SMP Mon Sep 24 16:13:24 UTC 2018 4.15.0-36.39

  Machine Type = This issue is observed on z13 system
   ---Debugger---
  A debugger was configured,

  ---Steps to Reproduce---
  This happens while running stress tests for network bonding. kernel memory 
exposure attempt is detected and the BUG() is called from the code snippet: 
mm/usercopy.c:72
  dump was configured and crash dump is available.
  Results of few crash commands like bt, log are added in Attachment

  Relevant part of dmesg pointing to kernel BUG

  <<>>
  [14746.977364] kernel BUG at 
/build/linux-PABIrW/linux-4.15.0/mm/usercopy.c:72!
  [14746.977377] illegal operation: 0001 ilc:1 [#1] SMP
  [14746.977378] Modules linked in: macsec vsock_diag vsock sctp_diag sctp 
dccp_diag dccp tcp_diag udp_diag raw_diag inet_diag unix_diag af_packet_diag 
netlink_diag bonding binfmt_misc qeth_l3 8021q garp mrp stp llc xt_tcpudp 
qeth_l2 nf_conntrack_ipv6 nf_defrag_ipv6 scsi_dh_rdac scsi_dh_emc scsi_dh_alua 
s390_trng ghash_s390 prng sha512_s390 sha256_s390 sha1_s390 sha_common chsc_sch 
eadm_sch nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c 
crc32_vx_s390 qeth ccwgroup ip6table_filter ip6_tables vfio_ccw vfio_mdev mdev 
vfio_iommu_type1 vfio iptable_filter sch_fq_codel ip_tables x_tables aes_s390 
des_s390 des_generic dm_crypt dm_service_time dm_multipath zfcp 
scsi_transport_fc qdio dasd_eckd_mod dasd_mod btrfs xor zstd_compress raid6_pq 
zlib_deflate
  [14746.977401] CPU: 1 PID: 20905 Comm: dump2tar Tainted: G   OE
4.15.0-36-generic #39-Ubuntu
  [14746.977403] Hardware name: IBM 3906 M02 757 (LPAR)
  [14746.977404] Krnl PSW : 0f2d230d 6abe14d5 
(__check_object_size+0x15a/0x1e0)
  [14746.977408]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
  [14746.977410] Krnl GPRS: 0002 00e95334 0064 
0001e6518828
  [14746.977412]0037cc8e  00a9577c 

  [14746.977413]647b 0001d8c120a8 0001 
8088
  [14746.977433]0001d8c0a020 0090da38 0037cc8e 
00016fdfbcd0
  [14746.977440] Krnl Code: 0037cc82: c0200038ef69larl
%r2,a9ab54
    0037cc88: c0e5fff32838brasl   
%r14,1e1cf8
   #0037cc8e: a7f40001brc 
15,37cc90
   >0037cc92: e330d0080004lg  
%r3,8(%r13)
    0037cc98: e320d004lg  
%r2,0(%r13)
  

[Kernel-packages] [Bug 1611124] Re: W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module i915

[Franck78]

@Seth Forshee (sforshee)

hello Seth,
now you know where to find them. (message#4)

There is at least LTS 16.04 to fix.

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

Title:
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin
  for module i915

Status in xen:
  Unknown
Status in linux-firmware package in Ubuntu:
  Invalid

Bug description:
  $sudo dpkg -i linux-image-4.8.0-040800rc1-lowlatency

  [...]

  update-initramfs: Generating /boot/initrd.img-4.8.0-040800rc1-lowlatency
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for 
module i915
  W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module 
i915

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-firmware 1.159
  Uname: Linux 4.8.0-040800rc1-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu5
  Architecture: amd64
  Date: Mon Aug  8 17:50:38 2016
  Dependencies:
   
  InstallationDate: Installed on 2015-07-26 (379 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[bugproxy]

--- Comment From boris_fiuczyn...@de.ibm.com 2018-11-19 11:04 EDT---
@paelzer
I am still trying to sort out the vfio-ap required patches for libvirt. I hope 
to get it done by tomorrow.

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

Title:
  [FEAT] Guest-dedicated Crypto Adapters

Status in Ubuntu on IBM z Systems:
  In Progress
Status in libvirt package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in qemu package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  == SRU Justification ==

  (Kernel SRU)

  Allow kvm to dedicate crypto adapters (and domains) as passthrough devices to 
a KVM guest such that the hypervisor cannot observe the communication of the 
guest with the device.
  (Since all kernel patches/commits are from kernel 4.19, they will 
automagically land in 'Disco'.)

  == Fix ==

  9ea5972 ("KVM: s390: vsie: simulate VCPU SIE entry/exit")
  3194cdb ("KVM: s390: introduce and use KVM_REQ_VSIE_RESTART")
  e585b24 ("KVM: s390: refactor crypto initialization")
  1fde573 ("s390: vfio-ap: base implementation of VFIO AP device driver")
  65f0671 ("s390: vfio-ap: register matrix device with VFIO mdev framework")
  96d152b ("s390: vfio-ap: sysfs interfaces to configure adapters")
  3211da0 ("s390: vfio-ap: sysfs interfaces to configure domains")
  3b1eab7 ("s390: vfio-ap: sysfs interfaces to configure control domains")
  81b2b4b ("s390: vfio-ap: sysfs interface to view matrix mdev matrix")
  4210459 ("KVM: s390: interface to clear CRYCB masks")
  258287c ("s390: vfio-ap: implement mediated device open callback")
  e06670c ("s390: vfio-ap: implement VFIO_DEVICE_GET_INFO ioctl")
  46a7263 ("s390: vfio-ap: zeroize the AP queues")
  cd8a377 ("s390: vfio-ap: implement VFIO_DEVICE_RESET ioctl")
  6cc571b ("KVM: s390: Clear Crypto Control Block when using vSIE")
  d6f6959 ("KVM: s390: vsie: Do the CRYCB validation first")
  3af84de ("KVM: s390: vsie: Make use of CRYCB FORMAT2 clear")
  56019f9 ("KVM: s390: vsie: Allow CRYCB FORMAT-2")
  19fd83a ("KVM: s390: vsie: allow CRYCB FORMAT-1")
  6ee7409 ("KVM: s390: vsie: allow CRYCB FORMAT-0")
  c9ba8c2 ("KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-1")
  6b79de4 ("KVM: s390: vsie: allow guest FORMAT-1 CRYCB on host FORMAT-2")
  9ee71f2 ("KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-2")
  37940fb ("KVM: s390: device attrs to enable/disable AP interpretation")
  112c24d ("KVM: s390: CPU model support for AP virtualization")
  492a6be ("s390: doc: detailed specifications for AP virtualization")

  <-- till here in 'kvm/next'
  (https://git.kernel.org/pub/scm/virt/kvm/kvm.git/) -->

  8e41bd5 ("KVM: s390: fix locking for crypto setting error path")
  0e237e4 ("KVM: s390: Tracing APCB changes")
  76c7829 ("s390: vfio-ap: setup APCB mask using KVM dedicated function")

  <-- till here in 'kvms390/next'
  (https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git/)
  -->

  <-- In addition to that some prereqs for the 'ap/crypto' driver are
  necessary -->

  ea3c418 ("s390/zcrypt: Add ZAPQ inline function.")
  df80c03 ("s390/zcrypt: Review inline assembler constraints.")
  f1b0a43 ("s390/zcrypt: Integrate ap_asm.h into include/asm/ap.h.")
  2395103 ("s390/zcrypt: fix ap_instructions_available() returncodes")
  7e0bdbe ("s390/zcrypt: AP bus support for alternate driver(s)")
  3d8f60d3 ("s390/zcrypt: hex string mask improvements for apmask and aqmask.")
  fa108f9 ("s390/zcrypt: remove VLA usage from the AP bus")

  <--
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787405/comments/12
  -->

  == PATCH ==

  Above git commits are all from 4.19.
  The git commands for 4.18 would be:

  $ git cherry-pick 

  (112c24d "KVM: s390: CPU model support for AP virtualization" may have
  a trivial merge conflict with the etoken patch)

  $ git cherry-pick 

  $ git cherry-pick 

  == Regression Potential ==

  Low to mid:

  - mid because in summary there are a lot of changes, but low
  - they are all limited to the s390x architecture
  - and again limited to KVM/s390x, vfio-ap and the zcrypt (aka ap) driver
  - Test kernel was built for testting.

  == Test Case ==

  Setup a system for KVM use on an s390x LPAR that has CryptoExpress (aka 
crypto-) adapters installed.
  Verify that the AP bus created a sysfs device for each APQN, like:
  /sys/devices/ap/card04/04.0006
  /sys/devices/ap/card04/04.0047
  /sys/devices/ap/card0a/0a.0006
  /sys/devices/ap/card0a/0a.0047
  Verify the APQN range via the following two sysfs files:
  /sys/bus/ap/apmask
  /sys/bus/ap/aqmask
  Configure and start a guest.
  More details see: 492a6be ("s390: doc: detailed specifications for AP 
virtualization")
  But for that an updated