[Kernel-packages] [Bug 1778486] Re: x86/kvm: fix LAPIC timer drift when guest uses periodic mode

[Markus Schade]

Thanks Joseph.

I tested the kernel with OpenBSD and FreeBSD virtual machines and this
patch seems to fix the timing issues.

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

Title:
  x86/kvm: fix LAPIC timer drift when guest uses periodic mode

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

Bug description:
  OpenBSD guests encounter timing issues when running under bionic
  kernel.

  This issue is actually present since 4.10 and is fixed by:

  https://patchwork.kernel.org/patch/10411125/

  See also

  https://www.spinics.net/lists/kvm/msg161311.html

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

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

[Kernel-packages] [Bug 1768431] Re: Request to revert SAUCE patches in the 18.04 SRU and update with upstream version

[Frank Heimes]

** Changed in: ubuntu-power-systems
   Status: In Progress => Fix Committed

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

Title:
  Request to revert SAUCE patches in the 18.04 SRU and update with
  upstream version

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification ==
  This SRU was requested by IBM.  It contains one SAUCE patch and three
  commits from linux.next.

  IBM requested that we revert a set of SAUCE patches from 18.04 and
  replace them with patches from linux-next.  Based on review comments,
  there has been minor changes from the original SAUCE patches and the
  versions in linux-next.

  The first SAUCE patch contains all the changes between the current version
  of SAUCE patches for latest cxlflash patches in bionic and the latest
  version accepted by the community. This only has the needed changes and
  makes it so we don't have to revert and re-apply a high number of patches.
  In addition to the SAUCE patch, IBM requested the 3 additional new patches
  from the linux-next tree.

  == Fixes ==
  UBUNTU: SAUCE: (no-up) cxlflash: OCXL diff between v2 and v3
  a3feb6ef50de ("scsi: cxlflash: Synchronize reset and remove ops")
  9a597cd4c0ce ("scsi: cxlflash: Remove commmands from pending list on timeout)"
  d2d354a606d5 ("scsi: cxlflash: Handle spurious interrupts")

  == Regression Potential ==
  Medium.  All the patches are specific to the cxlflash driver, but there
  are four of them and one is a SAUCE patch.

  == Test Case ==
  A test kernel was built with these patches and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  == Comment: #0 - UMA KRISHNAN  - 2018-04-30 14:41:30 ==
  ---Problem Description---
  Request to revert SAUCE patches from 18.04 and apply the patches from 
next/master.

  Below set of cxlflash patches were submitted to Canonical after they
  were sent to the community. Based on review comments, there has been
  minor changes from that version. This BZ is to request reverting those
  SAUCE patches with the ones that are queued in next/master tree for
  4.18.

  - SAUCE: cxlflash: Preserve number of interrupts for master contexts
  - SAUCE: cxlflash: Avoid clobbering context control register value
  - SAUCE: cxlflash: Add argument identifier names
  - SAUCE: cxlflash: Introduce OCXL backend
  - SAUCE: cxlflash: Hardware AFU for OCXL
  - SAUCE: cxlflash: Read host function configuration
  - SAUCE: cxlflash: Setup function acTag range
  - SAUCE: cxlflash: Read host AFU configuration
  - SAUCE: cxlflash: Setup AFU acTag range
  - SAUCE: cxlflash: Setup AFU PASID
  - SAUCE: cxlflash: Adapter context support for OCXL
  - SAUCE: cxlflash: Use IDR to manage adapter contexts
  - SAUCE: cxlflash: Support adapter file descriptors for OCXL
  - SAUCE: cxlflash: Support adapter context discovery
  - SAUCE: cxlflash: Support image reload policy modification
  - SAUCE: cxlflash: MMIO map the AFU
  - SAUCE: cxlflash: Support starting an adapter context
  - SAUCE: cxlflash: Support process specific mappings
  - SAUCE: cxlflash: Support AFU state toggling
  - SAUCE: cxlflash: Support reading adapter VPD data
  - SAUCE: cxlflash: Setup function OCXL link
  - SAUCE: cxlflash: Setup OCXL transaction layer
  - SAUCE: cxlflash: Support process element lifecycle
  - SAUCE: cxlflash: Support AFU interrupt management
  - SAUCE: cxlflash: Support AFU interrupt mapping and registration
  - SAUCE: cxlflash: Support starting user contexts
  - SAUCE: cxlflash: Support adapter context polling
  - SAUCE: cxlflash: Support adapter context reading
  - SAUCE: cxlflash: Support adapter context mmap and release
  - SAUCE: cxlflash: Support file descriptor mapping
  - SAUCE: cxlflash: Introduce object handle fop
  - SAUCE: cxlflash: Setup LISNs for user contexts
  - SAUCE: cxlflash: Setup LISNs for master contexts
  - SAUCE: cxlflash: Update synchronous interrupt status bits
  - SAUCE: cxlflash: Introduce OCXL context state machine
  - SAUCE: cxlflash: Register for translation errors
  - SAUCE: cxlflash: Support AFU reset
  - SAUCE: cxlflash: Enable OCXL operations

  Also, there are 3 additional patches added to end of this series that we 
would like to request being pulled into the SRU stream. These 3 patches address 
bug fixes.
  The commit ids for the patches queued in next/master tree are,

  768999d6b1eadc6a13b1fba1886f1708f433d82b scsi: cxlflash: Preserve number of 
interrupts for master contexts
  6c2b116dd38e3fbda10c3e3d5ac80ea7442e4f4d scsi: cxlflash: Avoid clobbering 
context control register value
  fcace1d5e11f518c6f91dd245fa1ac37393b47d3 scsi: cxlflash: Add argument 
identifier names
  863dbdc0552f8bc100df48bb231089c382b89004 scsi: cxlflash: Introduce OCXL 
backend

[Kernel-packages] [Bug 1778475] Re: i40e: restore workaround for removing default MAC filter

[Markus Schade]

Apparently not, but this was the only mentioning of this bug and the it
can be reproduced just the same way (bonding + vlan)

But after trying the mainline 4.18rc2 kernel, the bug is still present
their. So it needs to be fixed upstream first (again).

For reference:

# uname -a
Linux hostname 4.18.0-041800rc2-generic #201806241430 SMP Sun Jun 24 14:33:07 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

# dmesg:
[Thu Jun 28 08:08:45 2018] i40e :3d:00.1: Error I40E_AQ_RC_EINVAL adding RX 
filters on PF, promiscuous mode forced on
[Thu Jun 28 08:08:45 2018] i40e :3d:00.0: Error I40E_AQ_RC_EINVAL adding RX 
filters on PF, promiscuous mode forced on

# lspci -nn | grep -i eth
3d:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection X722 
for 10GbE SFP+ [8086:37d3] (rev 08)
3d:00.1 Ethernet controller [0200]: Intel Corporation Ethernet Connection X722 
for 10GbE SFP+ [8086:37d3] (rev 08)

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

Title:
  i40e: restore workaround for removing default MAC filter

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

Bug description:
  Ubuntu Bionic kernel (4.15.0-23) lacks upstream patch for i40e which
  results in forced promiscous mode when adding a vlan.

  
  [   10.847381] i40e :3d:00.0: Error I40E_AQ_RC_EINVAL adding RX filters 
on PF, promiscuous mode forced on

  Steps to reproduce and patch here:

  https://patchwork.ozlabs.org/patch/692499/

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

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

[Kernel-packages] [Bug 1770095] Re: Need fix to aacraid driver to prevent panic

[Frank Heimes]

** Changed in: ubuntu-power-systems
   Status: In Progress => Fix Committed

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

Title:
  Need fix to aacraid driver to prevent panic

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  
  == SRU Justification ==
  A commit introduced in mainline v4.14-rc1 to aacraid
  (b60710ec7d7ab1ca277b458338563ac21b393906) introduced a regression whereby a
  panic may happen under certain recovery situations.

  This regression is fixed by linux-next commit  7d3af7d96af7.

  
  == Fix ==
  7d3af7d96af7 ("scsi: aacraid: Correct hba_send to include iu_type")

  == Regression Potential ==
  Low.  This patch fixes a current regression.  It was cc'd to upstream
  stable, so it has had additonal upstream review.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  
  == Comment: #0 - Douglas Miller  - 2018-05-08 15:45:13 ==
  +++ This bug was initially created as a clone of Bug #167565 +++

  A recent commit to aacraid (b60710ec7d7ab1ca277b458338563ac21b393906)
  introduced a bug whereby a panic may happen under certain recovery
  situations. The following commit fixes that:

  
https://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git/commit/?h=fixes&id=7d3af7d96af7b9f51e1ef67b6f4725f545737da2

  We need this commit backported to Ubuntu 18.04

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

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

[Kernel-packages] [Bug 1776076] Re: package virtualbox-dkms 5.2.10-dfsg-6 failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess was killed by signal (Killed)

[Jack Hardcastle]

FWIW mine appears to have hung during a hidden (invisible to me) step
where it was attempting to set a MOK.  I had to first kill the existing
dpkg, then edit /usr/sbin/update-secureboot-policy to change #!/bin/sh
to #!/bin/bash (I was getting a local variable error), then manually run
/usr/bin/perl -w /usr/share/debconf/frontend /usr/sbin/update-
secureboot-policy --enroll-key, then reboot, install the key, finish
booting, and dpkg --configure -a.

I have no idea if the terminal-gui app that is attempting to ask for a
password for the MOK can be surfaced into the apt/dpkg configurating
process, but that seems to be the missing link for me.

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

Title:
  package virtualbox-dkms 5.2.10-dfsg-6 failed to install/upgrade:
  installed virtualbox-dkms package post-installation script subprocess
  was killed by signal (Killed)

Status in dkms package in Ubuntu:
  Confirmed

Bug description:
  virtualbox installation getting stuck

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: virtualbox-dkms 5.2.10-dfsg-6
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Sun Jun 10 19:11:06 2018
  ErrorMessage: installed virtualbox-dkms package post-installation script 
subprocess was killed by signal (Killed)
  InstallationDate: Installed on 2018-06-10 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: virtualbox
  Title: package virtualbox-dkms 5.2.10-dfsg-6 failed to install/upgrade: 
installed virtualbox-dkms package post-installation script subprocess was 
killed by signal (Killed)
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1763594] Re: xhci hangs; reset results in NULL pointer dereference

[Kai-Heng Feng]

I don't see "xhci_hcd :00:14.0: xHCI host controller not responding,
assume dead" in the logs you attached, so it's quite possibly another
issue.

Please file a new bug for that, thanks!

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

Title:
  xhci hangs; reset results in NULL pointer dereference

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

Bug description:
  Now and then, my xhci bus will hang, resulting in these kinds of
  messages in dmesg:

  [252220.002102] xhci_hcd :00:14.0: xHC is not running.
  [252220.037491] xhci_hcd :00:14.0: xHCI host controller not responding, 
assume dead
  [252220.037500] xhci_hcd :00:14.0: HC died; cleaning up
  [252220.133794] usb 1-2: USB disconnect, device number 2
  [252220.135042] usb 1-7: USB disconnect, device number 3
  [252220.137455] usb 1-8: USB disconnect, device number 4
  [252220.243317] usb 1-9: USB disconnect, device number 5

  Usually, I can fix this bij resetting the bus by calling a script
  reset-xhci:

  for xhci in /sys/bus/pci/drivers/?hci_hcd ; do
cd $xhci
echo Resetting devices from $xhci...
for i in :??:??.? ; do
  echo -n "$i" > unbind
  echo -n "$i" > bind
done
  done

  But doing this today resulted in a kernel bug:

  [252243.401814] xhci_hcd :00:14.0: remove, state 4
  [252243.401887] usb usb2: USB disconnect, device number 1
  [252243.470365] xhci_hcd :00:14.0: USB bus 2 deregistered
  [252243.470378] xhci_hcd :00:14.0: remove, state 4
  [252243.470383] usb usb1: USB disconnect, device number 1
  [252243.470831] xhci_hcd :00:14.0: Host halt failed, -19
  [252243.470837] xhci_hcd :00:14.0: Host not accessible, reset failed.
  [252243.475918] xhci_hcd :00:14.0: USB bus 1 deregistered
  [252243.475938] [ cut here ]
  [252243.475939] xhci_hcd :00:14.0: disabling already-disabled device
  [252243.475951] WARNING: CPU: 2 PID: 1787 at 
/build/linux-bdpCf2/linux-4.15.0/drivers/pci/pci.c:1642 
pci_disable_device+0x9c/0xc0
  [252243.475951] Modules linked in: cpuid snd_seq_dummy usb_storage 
hid_generic hidp ip6t_REJECT nf_reject_ipv6 ip6table_nat nf_nat_ipv6 
ip6table_mangle xt_hashlimit ip6table_raw nf_conntrack_ipv6 nf_defrag_ipv6 
nf_log_ipv6 xt_recent xt_comment ipt_REJECT nf_reject_ipv4 xt_mark 
iptable_mangle xt_tcpudp xt_CT iptable_raw xt_multiport xt_NFLOG nfnetlink_log 
nf_log_ipv4 nf_log_common xt_LOG nf_conntrack_sane nf_conntrack_netlink 
nfnetlink nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip 
nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda 
nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_proto_gre 
nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_irc 
nf_conntrack_h323 nf_conntrack_ftp ts_kmp nf_conntrack_amanda ipt_MASQUERADE 
nf_nat_masquerade_ipv4
  [252243.475984]  xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype xt_conntrack nf_nat nf_conntrack 
br_netfilter aufs vhost_net vhost tap ccm rfcomm bridge stp llc devlink 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter msr cmac bnep 
binfmt_misc snd_hda_codec_hdmi nls_iso8859_1 arc4 snd_soc_skl 
snd_hda_codec_realtek snd_soc_skl_ipc snd_hda_ext_core snd_hda_codec_generic 
snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core snd_compress ac97_bus 
snd_pcm_dmaengine snd_hda_intel dell_laptop dell_smbios_smm dcdbas 
snd_hda_codec dell_smm_hwmon snd_hda_core snd_hwdep snd_pcm intel_rapl 
snd_seq_midi snd_seq_midi_event x86_pkg_temp_thermal intel_powerclamp coretemp 
snd_rawmidi kvm_intel kvm btusb irqbypass intel_cstate intel_rapl_perf snd_seq 
btrtl
  [252243.476023]  iwlmvm btbcm btintel mac80211 hid_multitouch uvcvideo joydev 
input_leds dell_smbios_wmi snd_seq_device dell_wmi bluetooth serio_raw 
snd_timer videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 dell_smbios 
videobuf2_core iwlwifi sparse_keymap ecdh_generic snd wmi_bmof 
dell_wmi_descriptor videodev cfg80211 media soundcore rtsx_pci_ms memstick 
shpchp mei_me mei processor_thermal_device intel_pch_thermal intel_soc_dts_iosf 
int3400_thermal acpi_thermal_rel dell_rbtn mac_hid acpi_pad int3403_thermal 
int340x_thermal_zone tpm_crb sch_fq_codel cuse parport_pc ppdev nfsd lp parport 
auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs 
zstd_compress algif_skcipher af_alg dm_crypt raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1
  [252243.476067]  raid0 multipath linear dm_mirror dm_region_hash dm_log 
usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 
rtsx_pci_sdmmc i2c_algo_bit drm_kms_helper e1000e syscopyarea sysfillrect 
sysimgblt fb_sys_fops ptp aesni_intel psmouse drm pps_core rtsx_pci aes_x86_64 
ahci crypto_simd glue_helper lib

[Kernel-packages] [Bug 1776076] Re: package virtualbox-dkms 5.2.10-dfsg-6 failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess was killed by signal (Killed)

[Jack Hardcastle]

Hey folks, just piping in that I am also having this problem.  I am on
an encrypted disk, and the build of the kernel modules just hangs.
Please let me know if there is anything I can provide to assist in
debugging.

Note that there appear to be two other related / duplicate bugs: 1769327
and 1775672.

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

Title:
  package virtualbox-dkms 5.2.10-dfsg-6 failed to install/upgrade:
  installed virtualbox-dkms package post-installation script subprocess
  was killed by signal (Killed)

Status in dkms package in Ubuntu:
  Confirmed

Bug description:
  virtualbox installation getting stuck

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: virtualbox-dkms 5.2.10-dfsg-6
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Sun Jun 10 19:11:06 2018
  ErrorMessage: installed virtualbox-dkms package post-installation script 
subprocess was killed by signal (Killed)
  InstallationDate: Installed on 2018-06-10 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: virtualbox
  Title: package virtualbox-dkms 5.2.10-dfsg-6 failed to install/upgrade: 
installed virtualbox-dkms package post-installation script subprocess was 
killed by signal (Killed)
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1769610] Re: Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

[Shrirang Bagul]

@Denis,

Have you looked at the RFC patch submitted to linux-serial (see bug 
Description)?
The driver provided as fix for this issue will only attach if the BIOS on your 
HW describes virtual serial devices with HID's INT3511/INT3512.

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

Title:
  Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

  On systems using Intel Atom (Baytrail-I) SoC's, slave devices connected on
  HSUART1/2 ports are described by the ACPI BIOS as virtual hardware using
  HID's INT3511/INT3512 [1].

  As a consequence, HW manufacturers have complete freedom to install any
  devices on-board as long as they can be accessed over serial tty
  interface. Once such device is Dell Edge 3002 IoT Gateway which sports
  ZigBee & GPS devices on the HS-UART ports 1 & 2 respectively.

  Post 4.15, with CONFIG_SERIAL_DEV_BUS=y, serdev port controller driver
  handles the enumeration for the slaves connected on these ports. Also,
  /dev/ttySx device nodes for these ports are no longer exposed to the
  userspace.

  This driver has been submitted upstream and is under review. This issue has
  been identified as a regression in 4.15 and multiple solutions are being
  explored. Meanwhile, to support customer and maintain release schedule,
  this driver needs to be in Ubuntu 4.15 based kernels.

  The impact is limited to systems based on Intel Atom E38XX (Baytrail-I)
  SoC's.

  More info:
  https://marc.info/?t=15245587167&r=1&w=2

  Please don't triage, this bug is for tracking purposes only.

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

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

[Kernel-packages] [Bug 1725154] Re: mwifiex cannot connect to wifi AP when keeping wireless connection idle for more than 60 seconds

[Anthony Wong]

Bionic kernel has the fix already.

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

** Changed in: hwe-next
   Status: New => Fix Released

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

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

Title:
  mwifiex cannot connect to wifi AP when keeping wireless connection
  idle for more than 60 seconds

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Won't Fix
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  Issue happens every time we get connected to any WPA network and stay
  idle for more than 60 seconds.

  We are working with upstream for a real fix:
  https://www.spinics.net/lists/linux-wireless/msg167017.html, please
  don't triage.

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

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

[Kernel-packages] [Bug 1779021] [NEW] bcmwl 6.30.223.271+bdcom-0ubuntu1~1.2 ADT test failure with linux-hwe 4.15.0-24.26~16.04.1

[Khaled El Mously]

Public bug reported:

Testing failed on:
amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/b/bcmwl/20180618_150357_00839@/log.gz
i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/b/bcmwl/20180618_150412_00839@/log.gz

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  bcmwl 6.30.223.271+bdcom-0ubuntu1~1.2 ADT test failure with linux-hwe
  4.15.0-24.26~16.04.1

Status in bcmwl package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/b/bcmwl/20180618_150357_00839@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/b/bcmwl/20180618_150412_00839@/log.gz

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

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  BUG - vboxdrv.sh - failed: modprobe vboxdrv failed. Please use 'dmesg'
  to find out why.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  romulorafa@romulorafa:~$ virtualbox virtualbox/delete-old-modules boolean true
  WARNING: The vboxdrv kernel module is not loaded. Either there is no module
   available for the current kernel (4.15.0-23-generic) or it failed to
   load. Please recompile the kernel module and install it by

 sudo /sbin/vboxconfig

   You will not be able to start VMs until this problem is fixed.
  romulorafa@romulorafa:~$ sudo /sbin/vboxconfig
  vboxdrv.sh: Stopping VirtualBox services.
  vboxdrv.sh: Building VirtualBox kernel modules.
  vboxdrv.sh: Starting VirtualBox services.
  vboxdrv.sh: Building VirtualBox kernel modules.
  vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out 
why.

  There were problems setting up VirtualBox.  To re-start the set-up process, 
run
/sbin/vboxconfig
  as root.


  romulorafa@romulorafa:~$ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  romulorafa@romulorafa:~$ cat /proc/version_signature
  Ubuntu 4.15.0-23.25-generic 4.15.18

  romulorafa@romulorafa:~$ sudo lspci -vnvn
  00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [8086:5904] (rev 02)
Subsystem: Acer Incorporated [ALI] Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [1025:1193]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

  00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 
[8086:5916] (rev 02) (prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] HD Graphics 620 [1025:1193]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee00018  Data: 
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] Process Address Space ID (PASID)
PASIDCap: Exec- Priv-, Max PASID Width: 14
PASIDCtl: Enable- Exec- Priv-
Capabilities: [200 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable-, Smallest Translation Unit: 00
Capabilities: [300 v1] Page Request Interface (PRI)
PRICtl: Enable- Reset-
PRISta: RF- UPRGI- Stopped+
Page Request Capacity: 8000, Page Request Allocation: 

Kernel driver in use: i915
Kernel modules: i915

  00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 
xHCI Controller [8086:9d2f] (rev 21) (prog-if 30 [XHCI])
Subsystem: Acer Incorporated [ALI] Sunrise Point-LP USB 3.0 xHCI 
Controller [1025:1193]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

  00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise 
Point-LP Serial IO I2C Controller #1 [8086:9d61] (rev 21)
Subsystem: Acer Incorporated [ALI] Sunrise Point-LP Serial IO I2C 
Controller [1025:1193]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modu

[Kernel-packages] [Bug 1779007] [NEW] BUG - vboxdrv.sh - failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.

[Rômulo Rafael da Silva]

Public bug reported:

romulorafa@romulorafa:~$ virtualbox virtualbox/delete-old-modules boolean true
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
 available for the current kernel (4.15.0-23-generic) or it failed to
 load. Please recompile the kernel module and install it by

   sudo /sbin/vboxconfig

 You will not be able to start VMs until this problem is fixed.
romulorafa@romulorafa:~$ sudo /sbin/vboxconfig
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.

There were problems setting up VirtualBox.  To re-start the set-up process, run
  /sbin/vboxconfig
as root.


romulorafa@romulorafa:~$ lsb_release -rd
Description:Ubuntu 18.04 LTS
Release:18.04

romulorafa@romulorafa:~$ cat /proc/version_signature
Ubuntu 4.15.0-23.25-generic 4.15.18

romulorafa@romulorafa:~$ sudo lspci -vnvn
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [8086:5904] (rev 02)
Subsystem: Acer Incorporated [ALI] Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [1025:1193]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 
[8086:5916] (rev 02) (prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] HD Graphics 620 [1025:1193]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee00018  Data: 
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] Process Address Space ID (PASID)
PASIDCap: Exec- Priv-, Max PASID Width: 14
PASIDCtl: Enable- Exec- Priv-
Capabilities: [200 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable-, Smallest Translation Unit: 00
Capabilities: [300 v1] Page Request Interface (PRI)
PRICtl: Enable- Reset-
PRISta: RF- UPRGI- Stopped+
Page Request Capacity: 8000, Page Request Allocation: 

Kernel driver in use: i915
Kernel modules: i915

00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller [8086:9d2f] (rev 21) (prog-if 30 [XHCI])
Subsystem: Acer Incorporated [ALI] Sunrise Point-LP USB 3.0 xHCI 
Controller [1025:1193]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP 
Serial IO I2C Controller #1 [8086:9d61] (rev 21)
Subsystem: Acer Incorporated [ALI] Sunrise Point-LP Serial IO I2C 
Controller [1025:1193]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP 
CSME HECI #1 [8086:9d3a] (rev 21)
Subsystem: Acer Incorporated [ALI] Sunrise Point-LP CSME HECI 
[1025:1193]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- Reset- Fast

[Kernel-packages] [Bug 1754913] Re: ASUS w/ Atom N270 - Ubuntu 16.04.4 doesn't work properly.

[Wilfred F. Drouin Jr.]

Same issue with Gateway LT20 Netbook (Intel 945GM chipset and 1024x600 display) 
running Xubuntu 16.04
Problem began with latest update to Linux 4.13.0-45-generic kernel.
Using recovery mode barely usable but stretches 800x600 across the display.
Booting with 4.10.0-42-generic eliminates the problem.

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

Title:
  ASUS w/ Atom N270 - Ubuntu 16.04.4 doesn't work properly.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 16.04.4, then restarted my netbook.
  After restart, ubuntu 16.04.4 doesn't work properly.

  See Imgur images.

  https://i.imgur.com/nayCd6X.jpg

  --

  ASUS 1000HE

  CPU: Single Core Intel Atom N270
  Graphics: Card: Intel Mobile 945GSE Express Integrated Graphics Controller

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

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

[Kernel-packages] [Bug 1773392] Re: zfs hangs on mount/unmount

[James Buren]

It's an issue for my server too. LXD hangs when I try to restart
containers at times. I'm switching to libvirt until this is resolved.

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

Title:
  zfs hangs on mount/unmount

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am running lxd 3.0 on ubuntu 18.04 with kernel 4.15.0-22-generic and
  4.15.0-20-generic (same behaviour) with zfs backend (0.7.5-1ubuntu16;
  also tried 0.7.9).

  Sometimes lxd hangs when I try to stop / restart or "stop && move"
  some containers. Furhter investigation showed that problem is in zfs
  mount or unmount: it just hangs and lxd just wait it. Also commands
  like "zfs list" hangs to.

  It seems that it is not lxd or zfs issue, but kernel bug?
  https://github.com/lxc/lxd/issues/4104#issuecomment-392072939

  I have one test ct that always hangs on restart, so here is info:

  dmesg:
  [ 1330.390938] INFO: task txg_sync:9944 blocked for more than 120 seconds.
  [ 1330.390994]   Tainted: P   O 4.15.0-22-generic #24-Ubuntu
  [ 1330.391044] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 1330.391101] txg_syncD0  9944  2 0x8000
  [ 1330.391105] Call Trace:
  [ 1330.391117]  __schedule+0x297/0x8b0
  [ 1330.391122]  schedule+0x2c/0x80
  [ 1330.391136]  cv_wait_common+0x11e/0x140 [spl]
  [ 1330.391141]  ? wait_woken+0x80/0x80
  [ 1330.391152]  __cv_wait+0x15/0x20 [spl]
  [ 1330.391234]  rrw_enter_write+0x3c/0xa0 [zfs]
  [ 1330.391306]  rrw_enter+0x13/0x20 [zfs]
  [ 1330.391380]  spa_sync+0x7c9/0xd80 [zfs]
  [ 1330.391457]  txg_sync_thread+0x2cd/0x4a0 [zfs]
  [ 1330.391534]  ? txg_quiesce_thread+0x3d0/0x3d0 [zfs]
  [ 1330.391543]  thread_generic_wrapper+0x74/0x90 [spl]
  [ 1330.391549]  kthread+0x121/0x140
  [ 1330.391558]  ? __thread_exit+0x20/0x20 [spl]
  [ 1330.391562]  ? kthread_create_worker_on_cpu+0x70/0x70
  [ 1330.391566]  ? kthread_create_worker_on_cpu+0x70/0x70
  [ 1330.391569]  ret_from_fork+0x35/0x40
  [ 1330.391582] INFO: task lxd:12419 blocked for more than 120 seconds.
  [ 1330.391630]   Tainted: P   O 4.15.0-22-generic #24-Ubuntu
  [ 1330.391679] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 1330.391735] lxd D0 12419  1 0x
  [ 1330.391739] Call Trace:
  [ 1330.391745]  __schedule+0x297/0x8b0
  [ 1330.391749]  schedule+0x2c/0x80
  [ 1330.391752]  rwsem_down_write_failed+0x162/0x360
  [ 1330.391808]  ? dbuf_rele_and_unlock+0x1a8/0x4b0 [zfs]
  [ 1330.391814]  call_rwsem_down_write_failed+0x17/0x30
  [ 1330.391817]  ? call_rwsem_down_write_failed+0x17/0x30
  [ 1330.391821]  down_write+0x2d/0x40
  [ 1330.391825]  grab_super+0x30/0x90
  [ 1330.391901]  ? zpl_create+0x160/0x160 [zfs]
  [ 1330.391905]  sget_userns+0x91/0x490
  [ 1330.391908]  ? get_anon_bdev+0x100/0x100
  [ 1330.391983]  ? zpl_create+0x160/0x160 [zfs]
  [ 1330.391987]  sget+0x7d/0xa0
  [ 1330.391990]  ? get_anon_bdev+0x100/0x100
  [ 1330.392066]  zpl_mount+0xa8/0x160 [zfs]
  [ 1330.392071]  mount_fs+0x37/0x150
  [ 1330.392077]  vfs_kern_mount.part.23+0x5d/0x110
  [ 1330.392080]  do_mount+0x5ed/0xce0
  [ 1330.392083]  ? copy_mount_options+0x2c/0x220
  [ 1330.392086]  SyS_mount+0x98/0xe0
  [ 1330.392092]  do_syscall_64+0x73/0x130
  [ 1330.392096]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [ 1330.392099] RIP: 0033:0x4db36a
  [ 1330.392101] RSP: 002b:00c4207fa768 EFLAGS: 0216 ORIG_RAX: 
00a5
  [ 1330.392104] RAX: ffda RBX:  RCX: 
004db36a
  [ 1330.392106] RDX: 00c4205984cc RSI: 00c420a6ee00 RDI: 
00c420a23b60
  [ 1330.392108] RBP: 00c4207fa808 R08: 00c4209d4960 R09: 

  [ 1330.392110] R10:  R11: 0216 R12: 

  [ 1330.392112] R13: 0039 R14: 0038 R15: 
0080
  [ 1330.392123] INFO: task lxd:16725 blocked for more than 120 seconds.
  [ 1330.392171]   Tainted: P   O 4.15.0-22-generic #24-Ubuntu
  [ 1330.392220] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 1330.392276] lxd D0 16725  1 0x0002
  [ 1330.392279] Call Trace:
  [ 1330.392284]  __schedule+0x297/0x8b0
  [ 1330.392289]  ? irq_work_queue+0x8d/0xa0
  [ 1330.392293]  schedule+0x2c/0x80
  [ 1330.392297]  io_schedule+0x16/0x40
  [ 1330.392302]  wait_on_page_bit_common+0xd8/0x160
  [ 1330.392305]  ? page_cache_tree_insert+0xe0/0xe0
  [ 1330.392309]  __filemap_fdatawait_range+0xfa/0x160
  [ 1330.392313]  ? _cond_resched+0x19/0x40
  [ 1330.392317]  ? bdi_split_work_to_wbs+0x45/0x2c0
  [ 1330.392321]  ? _cond_resched+0x19/0x40
  [ 1330.392324]  filemap_fdatawait_keep_errors+0x1e/0x40
  [ 1330.392327]  sync_inodes_sb+0x20d/0x2b0
  [ 1330.392333]  __sync_filesystem+0x1b/0x60
  [ 1330.392336]  sync_filesystem

[Kernel-packages] [Bug 1778851] Re: package linux-headers-4.15.0-23-generic 4.15.0-23.25 failed to install/upgrade: installed linux-headers-4.15.0-23-generic package post-installation script subproces

[Anatoly Kupriyanov]

I guess it caused by shim-signed:


Running in non-interactive mode, doing nothing.
--- /var/lib/shim-signed/dkms-list  2018-06-27 22:31:11.289407651 +0100
+++ /var/lib/shim-signed/dkms-list.new  2018-06-27 22:31:11.289407651 +0100
@@ -1,3 +1,3 @@
 /var/lib/dkms
 /var/lib/dkms/bbswitch
-/var/lib/dkms/nvidia-384
+/var/lib/dkms/nvidia
dpkg: error processing package shim-signed (--configure):
 installed shim-signed package post-installation script subprocess returned 
error exit status 1
Errors were encountered while processing:
 shim-signed
E: Sub-process /usr/bin/dpkg returned an error code (1)

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

Title:
  package linux-headers-4.15.0-23-generic 4.15.0-23.25 failed to
  install/upgrade: installed linux-headers-4.15.0-23-generic package
  post-installation script subprocess was killed by signal (Terminated)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've done update to 18.04 from 17.10

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-headers-4.15.0-23-generic 4.15.0-23.25
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kan1695 F pulseaudio
  Date: Wed Jun 27 07:54:34 2018
  ErrorMessage: installed linux-headers-4.15.0-23-generic package 
post-installation script subprocess was killed by signal (Terminated)
  InstallationDate: Installed on 2017-09-19 (281 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 1bcf:28c0 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 7560
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=9dca5be7-8f3d-4249-90e0-b2058e40d97d ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-headers-4.15.0-23-generic 4.15.0-23.25 failed to 
install/upgrade: installed linux-headers-4.15.0-23-generic package 
post-installation script subprocess was killed by signal (Terminated)
  UpgradeStatus: Upgraded to bionic on 2018-06-27 (0 days ago)
  dmi.bios.date: 01/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.4
  dmi.board.name: 07T996
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.4:bd01/31/2018:svnDellInc.:pnInspiron7560:pvr:rvnDellInc.:rn07T996:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7560
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1778997] Re: Cosmic update to v4.17.3 stable release

[Seth Forshee]

** Description changed:

  SRU Justification
  
  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The v4.17.3 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.
  
     git://git.kernel.org/
  
  TEST CASE: TBD
  
     The following patches from the v4.17.3 stable release shall be
  applied:
  
  net: aquantia: fix unsigned numvecs comparison with less than zero
  bonding: re-evaluate force_primary when the primary slave name changes
  cdc_ncm: avoid padding beyond end of skb
  ipv6: allow PMTU exceptions to local routes
  net: dsa: add error handling for pskb_trim_rcsum
  net: phy: dp83822: use BMCR_ANENABLE instead of BMSR_ANEGCAPABLE for DP83620
  net/sched: act_simple: fix parsing of TCA_DEF_DATA
  tcp: verify the checksum of the first data segment in a new connection
  tls: fix use-after-free in tls_push_record
  tls: fix waitall behavior in tls_sw_recvmsg
  socket: close race condition between sock_close() and sockfs_setattr()
  udp: fix rx queue len reported by diag and proc interface
  net: in virtio_net_hdr only add VLAN_HLEN to csum_start if payload holds vlan
  hv_netvsc: Fix a network regression after ifdown/ifup
  ACPICA: AML parser: attempt to continue loading table after error
  ext4: fix hole length detection in ext4_ind_map_blocks()
  ext4: update mtime in ext4_punch_hole even if no blocks are released
  ext4: do not allow external inodes for inline data
  ext4: bubble errors from ext4_find_inline_data_nolock() up to ext4_iget()
  ext4: correctly handle a zero-length xattr with a non-zero e_value_offs
  ext4: fix fencepost error in check for inode count overflow during resize
  driver core: Don't ignore class_dir_create_and_add() failure.
  Btrfs: allow empty subvol= again
  Btrfs: fix clone vs chattr NODATASUM race
  Btrfs: fix memory and mount leak in btrfs_ioctl_rm_dev_v2()
  btrfs: return error value if create_io_em failed in cow_file_range
  btrfs: scrub: Don't use inode pages for device replace
  ALSA: usb-audio: Disable the quirk for Nura headset
- ALSA: hda/realtek - Enable mic-mute hotkey for several Lenovo AIOs
  ALSA: hda/conexant - Add fixup for HP Z2 G4 workstation
  ALSA: hda - Handle kzalloc() failure in snd_hda_attach_pcm_stream()
  ALSA: hda: add dock and led support for HP EliteBook 830 G5
  ALSA: hda: add dock and led support for HP ProBook 640 G4
  x86/MCE: Fix stack out-of-bounds write in mce-inject.c: Flags_read()
  smb3: fix various xid leaks
  smb3: on reconnect set PreviousSessionId field
  CIFS: 511c54a2f69195b28afb9dd119f03787b1625bb4 adds a check for session expiry
  cifs: For SMB2 security informaion query, check for minimum sized security 
descriptor instead of sizeof FileAllInformation class
  nbd: fix nbd device deletion
  nbd: update size when connected
  nbd: use bd_set_size when updating disk size
  blk-mq: reinit q->tag_set_list entry only after grace period
  bdi: Move cgroup bdi_writeback to a dedicated low concurrency workqueue
  cpufreq: Fix new policy initialization during limits updates via sysfs
  cpufreq: ti-cpufreq: Fix an incorrect error return value
  cpufreq: governors: Fix long idle detection logic in load calculation
  libata: zpodd: small read overflow in eject_tray()
  libata: Drop SanDisk SD7UB3Q*G1001 NOLPM quirk
  nvme/pci: Sync controller reset for AER slot_reset
  w1: mxc_w1: Enable clock before calling clk_get_rate() on it
  x86/vector: Fix the args of vector_alloc tracepoint
  x86/apic/vector: Prevent hlist corruption and leaks
  x86/apic: Provide apic_ack_irq()
  x86/ioapic: Use apic_ack_irq()
  x86/platform/uv: Use apic_ack_irq()
  irq_remapping: Use apic_ack_irq()
  genirq/generic_pending: Do not lose pending affinity update
  genirq/affinity: Defer affinity setting if irq chip is busy
  genirq/migration: Avoid out of line call if pending is not set
  x86/intel_rdt: Enable CMT and MBM on new Skylake stepping
  media: uvcvideo: Prevent setting unavailable flags
  media: rc: ensure input/lirc device can be opened after register
  iwlwifi: fw: harden page loading code
  orangefs: set i_size on new symlink
  orangefs: report attributes_mask and attributes for statx
  HID: intel_ish-hid: ipc: register more pm callbacks to support hibernation
  HID: wacom: Correct logical maximum Y for 2nd-gen Intuos Pro large
  vhost: fix info leak due to uninitialized memory
- fs/binfmt_misc.c: do not allow offset overflow
  mm, page_alloc: do not break __GFP_THISNODE by zonelist reset
  Linux 4.17.3
+ 
+    The following patches from the v4.17.3 stable release had already
+ been applied:
+ 
+ ALSA: hda/realtek - Enable mic-mute hotkey for several Lenovo AIOs
+ fs/binfmt_mis

[Kernel-packages] [Bug 1777245] Re: X freezes with kernel 4.15.0-23-generic (AMDGPU)

[Olaf Seibert]

@jsalisbury: I had the machine tested with this kernel:

Linux xa-xubu 4.18.0-041800rc1-generic #201806162031 SMP Sun Jun 17
00:34:22 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

that I found via your link [0].

The result is that in this kernel, the problem is gone. So that sounds
like good news!

I think there was another commenter asking me to try a (probably
different) upstream kernel, but it seems gone now. To them I can report
that I didn't try building a kernel myself, but hopefully their proposal
was close enough to using the Ubuntu mainline kernel that this test
gives them the answer they are looking for.


** Tags added: 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/1777245

Title:
  X freezes with kernel 4.15.0-23-generic (AMDGPU)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is on my parents machine; I only have remote access and not
  continuously, so this may slow down providing additional information.

  Since the latest kernel upgrade (from
   Linux version 4.13.0-43-generic (buildd@lgw01-amd64-026) (gcc version 7.2.0 
(Ubuntu 7.2.0-8ubuntu3.2)) #48-Ubuntu SMP Wed May 16 12:18:48 UTC 2018 (Ubuntu 
4.13.0-43.48-generic 4.13.16)  
  to  
  Linux version 4.15.0-23-generic (buildd@lgw01-amd64-055) (gcc version 7.3.0 
(Ubuntu 7.3.0-16ubuntu3)) #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 (Ubuntu 
4.15.0-23.25-generic 4.15.18)
  the machine appears to freezes some time soon after booting. It is just X; 
the machine is still reachable via ssh.

  I filed this bug using apport-cli, running the older (working) kernel,
  not the newer (failing) one.

  In /var/log/kernel I can see the following:

  Jun 15 23:26:23 xa-xubu kernel: [ 2417.562386] INFO: task Xorg:757 blocked 
for more than 120 seconds.
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.562396]   Not tainted 
4.15.0-23-generic #25-Ubuntu
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.562399] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.562403] XorgD0   757   
 724 0x0044
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.562408] Call Trace:
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.562424]  __schedule+0x297/0x8b0
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.562430]  ? __kfifo_in+0x37/0x50
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.562434]  schedule+0x2c/0x80
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.562559]  
amd_sched_entity_push_job+0xad/0xf0 [amdgpu]
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.562565]  ? wait_woken+0x80/0x80
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.562653]  amdgpu_job_submit+0x9f/0xc0 
[amdgpu]
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.562723]  
amdgpu_vm_bo_update_mapping+0x389/0x3f0 [amdgpu]
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.562793]  ? 
amdgpu_vm_it_iter_first+0x40/0x40 [amdgpu]
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.562863]  
amdgpu_vm_bo_update+0x325/0x5b0 [amdgpu]
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.562930]  
amdgpu_gem_va_ioctl+0x524/0x540 [amdgpu]
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.562962]  ? 
drm_gem_handle_create_tail+0x120/0x190 [drm]
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.563028]  ? 
amdgpu_gem_create_ioctl+0xc1/0x270 [amdgpu]
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.563096]  ? 
amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu]
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.563115]  drm_ioctl_kernel+0x5f/0xb0 
[drm]
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.563134]  ? drm_ioctl_kernel+0x5f/0xb0 
[drm]
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.563154]  drm_ioctl+0x31b/0x3d0 [drm]
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.563220]  ? 
amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu]
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.563225]  ? update_load_avg+0x57f/0x6e0
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.563231]  ? futex_wake+0x8f/0x180
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.563290]  amdgpu_drm_ioctl+0x4f/0x90 
[amdgpu]
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.563296]  do_vfs_ioctl+0xa8/0x630
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.563300]  ? __schedule+0x29f/0x8b0
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.563304]  SyS_ioctl+0x79/0x90
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.563309]  do_syscall_64+0x73/0x130
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.563313]  
entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.563317] RIP: 0033:0x7fbd7ddcf5d7
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.563319] RSP: 002b:7fff67e69aa8 
EFLAGS: 3246 ORIG_RAX: 0010
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.563322] RAX: ffda RBX: 
0002 RCX: 7fbd7ddcf5d7
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.563324] RDX: 7fff67e69af0 RSI: 
c0286448 RDI: 000e
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.563326] RBP: 7fff67e69af0 R08: 
00010144 R09: 

[Kernel-packages] [Bug 1778997] [NEW] Cosmic update to v4.17.3 stable release

[Seth Forshee]

Public bug reported:

SRU Justification

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

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the v4.17.3 stable release shall be
applied:

net: aquantia: fix unsigned numvecs comparison with less than zero
bonding: re-evaluate force_primary when the primary slave name changes
cdc_ncm: avoid padding beyond end of skb
ipv6: allow PMTU exceptions to local routes
net: dsa: add error handling for pskb_trim_rcsum
net: phy: dp83822: use BMCR_ANENABLE instead of BMSR_ANEGCAPABLE for DP83620
net/sched: act_simple: fix parsing of TCA_DEF_DATA
tcp: verify the checksum of the first data segment in a new connection
tls: fix use-after-free in tls_push_record
tls: fix waitall behavior in tls_sw_recvmsg
socket: close race condition between sock_close() and sockfs_setattr()
udp: fix rx queue len reported by diag and proc interface
net: in virtio_net_hdr only add VLAN_HLEN to csum_start if payload holds vlan
hv_netvsc: Fix a network regression after ifdown/ifup
ACPICA: AML parser: attempt to continue loading table after error
ext4: fix hole length detection in ext4_ind_map_blocks()
ext4: update mtime in ext4_punch_hole even if no blocks are released
ext4: do not allow external inodes for inline data
ext4: bubble errors from ext4_find_inline_data_nolock() up to ext4_iget()
ext4: correctly handle a zero-length xattr with a non-zero e_value_offs
ext4: fix fencepost error in check for inode count overflow during resize
driver core: Don't ignore class_dir_create_and_add() failure.
Btrfs: allow empty subvol= again
Btrfs: fix clone vs chattr NODATASUM race
Btrfs: fix memory and mount leak in btrfs_ioctl_rm_dev_v2()
btrfs: return error value if create_io_em failed in cow_file_range
btrfs: scrub: Don't use inode pages for device replace
ALSA: usb-audio: Disable the quirk for Nura headset
ALSA: hda/realtek - Enable mic-mute hotkey for several Lenovo AIOs
ALSA: hda/conexant - Add fixup for HP Z2 G4 workstation
ALSA: hda - Handle kzalloc() failure in snd_hda_attach_pcm_stream()
ALSA: hda: add dock and led support for HP EliteBook 830 G5
ALSA: hda: add dock and led support for HP ProBook 640 G4
x86/MCE: Fix stack out-of-bounds write in mce-inject.c: Flags_read()
smb3: fix various xid leaks
smb3: on reconnect set PreviousSessionId field
CIFS: 511c54a2f69195b28afb9dd119f03787b1625bb4 adds a check for session expiry
cifs: For SMB2 security informaion query, check for minimum sized security 
descriptor instead of sizeof FileAllInformation class
nbd: fix nbd device deletion
nbd: update size when connected
nbd: use bd_set_size when updating disk size
blk-mq: reinit q->tag_set_list entry only after grace period
bdi: Move cgroup bdi_writeback to a dedicated low concurrency workqueue
cpufreq: Fix new policy initialization during limits updates via sysfs
cpufreq: ti-cpufreq: Fix an incorrect error return value
cpufreq: governors: Fix long idle detection logic in load calculation
libata: zpodd: small read overflow in eject_tray()
libata: Drop SanDisk SD7UB3Q*G1001 NOLPM quirk
nvme/pci: Sync controller reset for AER slot_reset
w1: mxc_w1: Enable clock before calling clk_get_rate() on it
x86/vector: Fix the args of vector_alloc tracepoint
x86/apic/vector: Prevent hlist corruption and leaks
x86/apic: Provide apic_ack_irq()
x86/ioapic: Use apic_ack_irq()
x86/platform/uv: Use apic_ack_irq()
irq_remapping: Use apic_ack_irq()
genirq/generic_pending: Do not lose pending affinity update
genirq/affinity: Defer affinity setting if irq chip is busy
genirq/migration: Avoid out of line call if pending is not set
x86/intel_rdt: Enable CMT and MBM on new Skylake stepping
media: uvcvideo: Prevent setting unavailable flags
media: rc: ensure input/lirc device can be opened after register
iwlwifi: fw: harden page loading code
orangefs: set i_size on new symlink
orangefs: report attributes_mask and attributes for statx
HID: intel_ish-hid: ipc: register more pm callbacks to support hibernation
HID: wacom: Correct logical maximum Y for 2nd-gen Intuos Pro large
vhost: fix info leak due to uninitialized memory
fs/binfmt_misc.c: do not allow offset overflow
mm, page_alloc: do not break __GFP_THISNODE by zonelist reset
Linux 4.17.3

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

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

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+  

[Kernel-packages] [Bug 1763594] Re: xhci hangs; reset results in NULL pointer dereference

[Szobonya Csaba]

I reproduced the same(?) issue by passing by passing an usb controller
to kvm.(https://www.redhat.com/archives/vfio-
users/2018-February/msg00030.html) When I shut down the virtual machine
and try to start again it always fails. Tested your kernel and still the
same issue. Hope this helps.

** Attachment added: "before.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763594/+attachment/5157190/+files/before.log

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

Title:
  xhci hangs; reset results in NULL pointer dereference

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

Bug description:
  Now and then, my xhci bus will hang, resulting in these kinds of
  messages in dmesg:

  [252220.002102] xhci_hcd :00:14.0: xHC is not running.
  [252220.037491] xhci_hcd :00:14.0: xHCI host controller not responding, 
assume dead
  [252220.037500] xhci_hcd :00:14.0: HC died; cleaning up
  [252220.133794] usb 1-2: USB disconnect, device number 2
  [252220.135042] usb 1-7: USB disconnect, device number 3
  [252220.137455] usb 1-8: USB disconnect, device number 4
  [252220.243317] usb 1-9: USB disconnect, device number 5

  Usually, I can fix this bij resetting the bus by calling a script
  reset-xhci:

  for xhci in /sys/bus/pci/drivers/?hci_hcd ; do
cd $xhci
echo Resetting devices from $xhci...
for i in :??:??.? ; do
  echo -n "$i" > unbind
  echo -n "$i" > bind
done
  done

  But doing this today resulted in a kernel bug:

  [252243.401814] xhci_hcd :00:14.0: remove, state 4
  [252243.401887] usb usb2: USB disconnect, device number 1
  [252243.470365] xhci_hcd :00:14.0: USB bus 2 deregistered
  [252243.470378] xhci_hcd :00:14.0: remove, state 4
  [252243.470383] usb usb1: USB disconnect, device number 1
  [252243.470831] xhci_hcd :00:14.0: Host halt failed, -19
  [252243.470837] xhci_hcd :00:14.0: Host not accessible, reset failed.
  [252243.475918] xhci_hcd :00:14.0: USB bus 1 deregistered
  [252243.475938] [ cut here ]
  [252243.475939] xhci_hcd :00:14.0: disabling already-disabled device
  [252243.475951] WARNING: CPU: 2 PID: 1787 at 
/build/linux-bdpCf2/linux-4.15.0/drivers/pci/pci.c:1642 
pci_disable_device+0x9c/0xc0
  [252243.475951] Modules linked in: cpuid snd_seq_dummy usb_storage 
hid_generic hidp ip6t_REJECT nf_reject_ipv6 ip6table_nat nf_nat_ipv6 
ip6table_mangle xt_hashlimit ip6table_raw nf_conntrack_ipv6 nf_defrag_ipv6 
nf_log_ipv6 xt_recent xt_comment ipt_REJECT nf_reject_ipv4 xt_mark 
iptable_mangle xt_tcpudp xt_CT iptable_raw xt_multiport xt_NFLOG nfnetlink_log 
nf_log_ipv4 nf_log_common xt_LOG nf_conntrack_sane nf_conntrack_netlink 
nfnetlink nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip 
nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda 
nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_proto_gre 
nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_irc 
nf_conntrack_h323 nf_conntrack_ftp ts_kmp nf_conntrack_amanda ipt_MASQUERADE 
nf_nat_masquerade_ipv4
  [252243.475984]  xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype xt_conntrack nf_nat nf_conntrack 
br_netfilter aufs vhost_net vhost tap ccm rfcomm bridge stp llc devlink 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter msr cmac bnep 
binfmt_misc snd_hda_codec_hdmi nls_iso8859_1 arc4 snd_soc_skl 
snd_hda_codec_realtek snd_soc_skl_ipc snd_hda_ext_core snd_hda_codec_generic 
snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core snd_compress ac97_bus 
snd_pcm_dmaengine snd_hda_intel dell_laptop dell_smbios_smm dcdbas 
snd_hda_codec dell_smm_hwmon snd_hda_core snd_hwdep snd_pcm intel_rapl 
snd_seq_midi snd_seq_midi_event x86_pkg_temp_thermal intel_powerclamp coretemp 
snd_rawmidi kvm_intel kvm btusb irqbypass intel_cstate intel_rapl_perf snd_seq 
btrtl
  [252243.476023]  iwlmvm btbcm btintel mac80211 hid_multitouch uvcvideo joydev 
input_leds dell_smbios_wmi snd_seq_device dell_wmi bluetooth serio_raw 
snd_timer videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 dell_smbios 
videobuf2_core iwlwifi sparse_keymap ecdh_generic snd wmi_bmof 
dell_wmi_descriptor videodev cfg80211 media soundcore rtsx_pci_ms memstick 
shpchp mei_me mei processor_thermal_device intel_pch_thermal intel_soc_dts_iosf 
int3400_thermal acpi_thermal_rel dell_rbtn mac_hid acpi_pad int3403_thermal 
int340x_thermal_zone tpm_crb sch_fq_codel cuse parport_pc ppdev nfsd lp parport 
auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs 
zstd_compress algif_skcipher af_alg dm_crypt raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1
  [252243.476067]  raid0 multipath linear dm_mirror dm_region_hash dm_log 
usbhid hid crct10dif_

[Kernel-packages] [Bug 1763594] Re: xhci hangs; reset results in NULL pointer dereference

[Szobonya Csaba]

** Attachment added: "after.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763594/+attachment/5157191/+files/after.log

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

Title:
  xhci hangs; reset results in NULL pointer dereference

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

Bug description:
  Now and then, my xhci bus will hang, resulting in these kinds of
  messages in dmesg:

  [252220.002102] xhci_hcd :00:14.0: xHC is not running.
  [252220.037491] xhci_hcd :00:14.0: xHCI host controller not responding, 
assume dead
  [252220.037500] xhci_hcd :00:14.0: HC died; cleaning up
  [252220.133794] usb 1-2: USB disconnect, device number 2
  [252220.135042] usb 1-7: USB disconnect, device number 3
  [252220.137455] usb 1-8: USB disconnect, device number 4
  [252220.243317] usb 1-9: USB disconnect, device number 5

  Usually, I can fix this bij resetting the bus by calling a script
  reset-xhci:

  for xhci in /sys/bus/pci/drivers/?hci_hcd ; do
cd $xhci
echo Resetting devices from $xhci...
for i in :??:??.? ; do
  echo -n "$i" > unbind
  echo -n "$i" > bind
done
  done

  But doing this today resulted in a kernel bug:

  [252243.401814] xhci_hcd :00:14.0: remove, state 4
  [252243.401887] usb usb2: USB disconnect, device number 1
  [252243.470365] xhci_hcd :00:14.0: USB bus 2 deregistered
  [252243.470378] xhci_hcd :00:14.0: remove, state 4
  [252243.470383] usb usb1: USB disconnect, device number 1
  [252243.470831] xhci_hcd :00:14.0: Host halt failed, -19
  [252243.470837] xhci_hcd :00:14.0: Host not accessible, reset failed.
  [252243.475918] xhci_hcd :00:14.0: USB bus 1 deregistered
  [252243.475938] [ cut here ]
  [252243.475939] xhci_hcd :00:14.0: disabling already-disabled device
  [252243.475951] WARNING: CPU: 2 PID: 1787 at 
/build/linux-bdpCf2/linux-4.15.0/drivers/pci/pci.c:1642 
pci_disable_device+0x9c/0xc0
  [252243.475951] Modules linked in: cpuid snd_seq_dummy usb_storage 
hid_generic hidp ip6t_REJECT nf_reject_ipv6 ip6table_nat nf_nat_ipv6 
ip6table_mangle xt_hashlimit ip6table_raw nf_conntrack_ipv6 nf_defrag_ipv6 
nf_log_ipv6 xt_recent xt_comment ipt_REJECT nf_reject_ipv4 xt_mark 
iptable_mangle xt_tcpudp xt_CT iptable_raw xt_multiport xt_NFLOG nfnetlink_log 
nf_log_ipv4 nf_log_common xt_LOG nf_conntrack_sane nf_conntrack_netlink 
nfnetlink nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip 
nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda 
nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_proto_gre 
nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_irc 
nf_conntrack_h323 nf_conntrack_ftp ts_kmp nf_conntrack_amanda ipt_MASQUERADE 
nf_nat_masquerade_ipv4
  [252243.475984]  xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype xt_conntrack nf_nat nf_conntrack 
br_netfilter aufs vhost_net vhost tap ccm rfcomm bridge stp llc devlink 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter msr cmac bnep 
binfmt_misc snd_hda_codec_hdmi nls_iso8859_1 arc4 snd_soc_skl 
snd_hda_codec_realtek snd_soc_skl_ipc snd_hda_ext_core snd_hda_codec_generic 
snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core snd_compress ac97_bus 
snd_pcm_dmaengine snd_hda_intel dell_laptop dell_smbios_smm dcdbas 
snd_hda_codec dell_smm_hwmon snd_hda_core snd_hwdep snd_pcm intel_rapl 
snd_seq_midi snd_seq_midi_event x86_pkg_temp_thermal intel_powerclamp coretemp 
snd_rawmidi kvm_intel kvm btusb irqbypass intel_cstate intel_rapl_perf snd_seq 
btrtl
  [252243.476023]  iwlmvm btbcm btintel mac80211 hid_multitouch uvcvideo joydev 
input_leds dell_smbios_wmi snd_seq_device dell_wmi bluetooth serio_raw 
snd_timer videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 dell_smbios 
videobuf2_core iwlwifi sparse_keymap ecdh_generic snd wmi_bmof 
dell_wmi_descriptor videodev cfg80211 media soundcore rtsx_pci_ms memstick 
shpchp mei_me mei processor_thermal_device intel_pch_thermal intel_soc_dts_iosf 
int3400_thermal acpi_thermal_rel dell_rbtn mac_hid acpi_pad int3403_thermal 
int340x_thermal_zone tpm_crb sch_fq_codel cuse parport_pc ppdev nfsd lp parport 
auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs 
zstd_compress algif_skcipher af_alg dm_crypt raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1
  [252243.476067]  raid0 multipath linear dm_mirror dm_region_hash dm_log 
usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 
rtsx_pci_sdmmc i2c_algo_bit drm_kms_helper e1000e syscopyarea sysfillrect 
sysimgblt fb_sys_fops ptp aesni_intel psmouse drm pps_core rtsx_pci aes_x86_64 
ahci crypto_simd glue_helper libahci wmi cryptd video
  [252243.476089] CPU: 2 PID: 1787

[Kernel-packages] [Bug 1776822] Re: linux: 4.4.0-130.156 -proposed tracker

[Steve Beattie]

** Changed in: kernel-sru-workflow/security-signoff
   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/1776822

Title:
  linux: 4.4.0-130.156 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
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:
  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 1776823 (linux-lts-xenial), bug 1776824 (linux-aws)
  derivatives: bug 1776357 (linux-euclid), bug 1776826 (linux-kvm), bug 1776359 
(linux-raspi2), bug 1776361 (linux-snapdragon), bug 1776829 (linux-aws)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1778584] Re: linux-image-3.13.0-151-generic fails to boot

[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.18 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc2


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

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

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

** Tags added: kernel-da-key

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

Title:
  linux-image-3.13.0-151-generic fails to boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Our machine rebooted over the weekend and fails to boot the new
  3.13.0-151-generic kernel.

  I have fallen back to 3.13.0-149-generic kernel in the meantime.

  Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39
  --- 
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  carmen 1815 F pulseaudio
   /dev/snd/controlC0:  carmen 1815 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=0d9024d4-384e-4eea-b1ee-f7a36ce05e7f
  InstallationDate: Installed on 2013-07-08 (1812 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-A75-D3H
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic 
root=UUID=056dd0ad-a7cd-4b07-a922-9de9da3e17df ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-149-generic N/A
   linux-backports-modules-3.13.0-149-generic  N/A
   linux-firmware  1.127.24
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-149-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2015-09-23 (1006 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True
  dmi.bios.date: 06/13/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F1
  dmi.board.name: GA-A75-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd06/13/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-A75-D3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-A75-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-A75-D3H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1776829] Re: linux-aws: 4.4.0-1062.71 -proposed tracker

[Steve Beattie]

** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

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

Title:
  linux-aws: 4.4.0-1062.71 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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:
  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:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
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:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws 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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1776822
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1778610] Re: package linux-image-4.15.0-23-generic 4.15.0-23.25 failed to install/upgrade: installed linux-image-4.15.0-23-generic package pre-removal script subprocess returned

[Joseph Salisbury]

Also, linux-image-ex is not a valid package name.  You can see the
kernels you have install with:

sudo dpkg -l | grep linux-image

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

Title:
  package linux-image-4.15.0-23-generic 4.15.0-23.25 failed to
  install/upgrade: installed linux-image-4.15.0-23-generic package pre-
  removal script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  sudo apt-get remove linux-image-ex
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  E: Unable to locate package linux-image-ex

  I'm trying to free up space in my hard drive and i got this error i was 
expecting to remove the selected image provided in the report and instead 
gotten this message 
  I am using  4.15.0-23-generic image 
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-23-generic 4.15.0-23.25
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: snd_hda_codec_hdmi edac_mce_amd snd_hda_codec_realtek 
snd_hda_codec_generic snd_hda_intel snd_hda_codec wmi_bmof snd_hda_core k10temp 
shpchp mac_hid nouveau mxm_wmi pata_acpi firewire_ohci r8169 firewire_core 
pata_atiixp i2c_piix4 wmi
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1029 F pulseaudio
ghost  1451 F pulseaudio
   /dev/snd/controlC0:  gdm1029 F pulseaudio
ghost  1451 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Mon Jun 25 18:46:37 2018
  ErrorMessage: installed linux-image-4.15.0-23-generic package pre-removal 
script subprocess returned error exit status 1
  HibernationDevice: RESUME=UUID=ba74b561-39bb-4df6-900d-369614ad28a3
  InstallationDate: Installed on 2018-06-24 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-MA785GPMT-UD2H
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions: grub-pc 2.02-2ubuntu8
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.15.0-23-generic 4.15.0-23.25 failed to 
install/upgrade: installed linux-image-4.15.0-23-generic package pre-removal 
script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to bionic on 2018-06-24 (1 days ago)
  dmi.bios.date: 08/06/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-MA785GPMT-UD2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd08/06/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA785GPMT-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA785GPMT-UD2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA785GPMT-UD2H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1778851] Re: package linux-headers-4.15.0-23-generic 4.15.0-23.25 failed to install/upgrade: installed linux-headers-4.15.0-23-generic package post-installation script subproces

[Joseph Salisbury]

You may need to run the following from a terminal:

sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

Then re-install the package or updates.

If that does not resolve your issue, please mark the bug as "Confirmed"


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

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

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

Title:
  package linux-headers-4.15.0-23-generic 4.15.0-23.25 failed to
  install/upgrade: installed linux-headers-4.15.0-23-generic package
  post-installation script subprocess was killed by signal (Terminated)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've done update to 18.04 from 17.10

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-headers-4.15.0-23-generic 4.15.0-23.25
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kan1695 F pulseaudio
  Date: Wed Jun 27 07:54:34 2018
  ErrorMessage: installed linux-headers-4.15.0-23-generic package 
post-installation script subprocess was killed by signal (Terminated)
  InstallationDate: Installed on 2017-09-19 (281 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 1bcf:28c0 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 7560
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=9dca5be7-8f3d-4249-90e0-b2058e40d97d ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-headers-4.15.0-23-generic 4.15.0-23.25 failed to 
install/upgrade: installed linux-headers-4.15.0-23-generic package 
post-installation script subprocess was killed by signal (Terminated)
  UpgradeStatus: Upgraded to bionic on 2018-06-27 (0 days ago)
  dmi.bios.date: 01/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.4
  dmi.board.name: 07T996
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.4:bd01/31/2018:svnDellInc.:pnInspiron7560:pvr:rvnDellInc.:rn07T996:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7560
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1778610] Re: package linux-image-4.15.0-23-generic 4.15.0-23.25 failed to install/upgrade: installed linux-image-4.15.0-23-generic package pre-removal script subprocess returned

[Joseph Salisbury]

You may need to run the following from a terminal:

sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

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

Title:
  package linux-image-4.15.0-23-generic 4.15.0-23.25 failed to
  install/upgrade: installed linux-image-4.15.0-23-generic package pre-
  removal script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  sudo apt-get remove linux-image-ex
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  E: Unable to locate package linux-image-ex

  I'm trying to free up space in my hard drive and i got this error i was 
expecting to remove the selected image provided in the report and instead 
gotten this message 
  I am using  4.15.0-23-generic image 
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-23-generic 4.15.0-23.25
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: snd_hda_codec_hdmi edac_mce_amd snd_hda_codec_realtek 
snd_hda_codec_generic snd_hda_intel snd_hda_codec wmi_bmof snd_hda_core k10temp 
shpchp mac_hid nouveau mxm_wmi pata_acpi firewire_ohci r8169 firewire_core 
pata_atiixp i2c_piix4 wmi
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1029 F pulseaudio
ghost  1451 F pulseaudio
   /dev/snd/controlC0:  gdm1029 F pulseaudio
ghost  1451 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Mon Jun 25 18:46:37 2018
  ErrorMessage: installed linux-image-4.15.0-23-generic package pre-removal 
script subprocess returned error exit status 1
  HibernationDevice: RESUME=UUID=ba74b561-39bb-4df6-900d-369614ad28a3
  InstallationDate: Installed on 2018-06-24 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-MA785GPMT-UD2H
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions: grub-pc 2.02-2ubuntu8
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.15.0-23-generic 4.15.0-23.25 failed to 
install/upgrade: installed linux-image-4.15.0-23-generic package pre-removal 
script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to bionic on 2018-06-24 (1 days ago)
  dmi.bios.date: 08/06/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-MA785GPMT-UD2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd08/06/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA785GPMT-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA785GPMT-UD2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA785GPMT-UD2H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1776826] Re: linux-kvm: 4.4.0-1029.34 -proposed tracker

[Steve Beattie]

** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

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

Title:
  linux-kvm: 4.4.0-1029.34 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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:
  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:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm 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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1776822
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1778584] Re: linux-image-3.13.0-151-generic fails to boot

[Joseph Salisbury]

Also, can you post a screen shot or digital picture of the error you see
while trying to 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/1778584

Title:
  linux-image-3.13.0-151-generic fails to boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Our machine rebooted over the weekend and fails to boot the new
  3.13.0-151-generic kernel.

  I have fallen back to 3.13.0-149-generic kernel in the meantime.

  Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39
  --- 
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  carmen 1815 F pulseaudio
   /dev/snd/controlC0:  carmen 1815 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=0d9024d4-384e-4eea-b1ee-f7a36ce05e7f
  InstallationDate: Installed on 2013-07-08 (1812 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-A75-D3H
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic 
root=UUID=056dd0ad-a7cd-4b07-a922-9de9da3e17df ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-149-generic N/A
   linux-backports-modules-3.13.0-149-generic  N/A
   linux-firmware  1.127.24
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-149-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2015-09-23 (1006 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True
  dmi.bios.date: 06/13/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F1
  dmi.board.name: GA-A75-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd06/13/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-A75-D3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-A75-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-A75-D3H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1776824] Re: linux-aws: 4.4.0-1024.25 -proposed tracker

[Steve Beattie]

** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

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

Title:
  linux-aws: 4.4.0-1024.25 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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:
  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:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws 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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1776822
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1778765] Re: Ubuntu 18.04 NVMe disks are not displayed on lsblk

[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.18 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc2


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

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

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

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

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

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

** Tags added: kernel-da-key

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

Title:
  Ubuntu 18.04 NVMe disks are not displayed on lsblk

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

Bug description:
  Following the suggestion #12 on bug 1758205 to raise a new one

  
  I have updated kernel to 4.15.0-23-generic and still see the problem reported 
in 1758205:

  root@localhost:/sys/block# nvme list
  Node SN Model Namespace Usage Format FW Rev
    
 - -- 
 
  /dev/nvme0n1 CJH0020005EB HUSMR7616BDP301 1 1.92 TB / 1.92 TB 512 B + 8 B 
KNECD105

  root@localhost:/sys/block# lsblk
  NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
  sda 8:0 0 465.8G 0 disk
  ├─sda1 8:1 0 476M 0 part /boot
  ├─sda2 8:2 0 30.8G 0 part [SWAP]
  └─sda3 8:3 0 434.6G 0 part /
  sdb 8:16 0 931.5G 0 disk
  sr0 11:0 1 1024M 0 rom
  root@localhost:/sys/block# ls -l /sys/block/
  total 0
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop0 -> ../devices/virtual/block/loop0
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop1 -> ../devices/virtual/block/loop1
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop2 -> ../devices/virtual/block/loop2
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop3 -> ../devices/virtual/block/loop3
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop4 -> ../devices/virtual/block/loop4
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop5 -> ../devices/virtual/block/loop5
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop6 -> ../devices/virtual/block/loop6
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop7 -> ../devices/virtual/block/loop7
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 nvme0n1 -> 
../devices/pci:00/:00:01.1/:02:00.0/nvme/nvme0/nvme0n1
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 sda -> 
../devices/pci:00/:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sda
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 sdb -> 
../devices/pci:00/:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdb
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 sr0 -> 
../devices/pci:00/:00:1f.2/ata5/host4/target4:0:0/4:0:0:0/block/sr0
  root@localhost:/sys/block# lspci -nn | grep -i Non
  02:00.0 Non-Volatile memory controller [0108]: HGST, Inc. Ultrastar SN200 
Series NVMe SSD [1c58:0023] (rev 02)
  root@localhost:/sys/block# blockdev --getsize64 /dev/nvme0n1
  0
  root@localhost:/sys/block#

  # cat /proc/version_signature
  Ubuntu 4.15.0-23.25-generic 4.15.18

  
  # dmidecode -t 2
  # dmidecode 3.1
  Getting SMBIOS data from sysfs.
  SMBIOS 2.6 present.

  Handle 0x0002, DMI type 2, 15 bytes
  Base Board Information
  Manufacturer: ASUSTeK Computer INC.
  Product Name: P8Z68-V PRO
  Version: Rev 1.xx
  Serial Number: 11010417300
  Asset Tag: To be filled by O.E.M.
  Features:
  Board is a hosting board
  Board is replaceable
  Location In Chassis: To be filled by O.E.M.
  Chassis Handle: 0x0003
  Type: Motherboard
  Contained Object Handles: 0

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

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

[Kernel-packages] [Bug 1778705] Re: skey in ubuntu-kvm-unit-test failed on Xenial zVM

[Joseph Salisbury]

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

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

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

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

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

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

Title:
  skey in ubuntu-kvm-unit-test failed on Xenial zVM

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  TESTNAME=skey TIMEOUT=90s ACCEL= ./s390x/run s390x/skey.elf -smp 1
  FAIL skey (2 tests)

  This is the only failure in this test suite on Xenial zVM, need to run
  it manually to see what's going on.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-130-generic 4.4.0-130.156
  ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
  Uname: Linux 4.4.0-130-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.
  CurrentDmesg:
   [ 3288.479241] audit_printk_skb: 153 callbacks suppressed
   [ 3288.479246] audit: type=1400 audit(1530011067.825:63): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="/usr/lib/snapd/snap-confine" pid=6480 comm="apparmor_parser"
   [ 3288.510095] audit: type=1400 audit(1530011067.865:64): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" pid=6480 
comm="apparmor_parser"
  Date: Tue Jun 26 07:05:34 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=44b0b919-a1a4-4849-9425-e71d4ac87d85 
crashkernel=196M nobp=1 BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-130-generic N/A
   linux-backports-modules-4.4.0-130-generic  N/A
   linux-firmware 1.157.19
  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/1778705/+subscriptions

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

[Kernel-packages] [Bug 1778717] Re: Ubuntu 18.04 guest hangs during diskio stress

[Joseph Salisbury]

I'd like to perform a bisect to figure out what commit caused this
regression. We need to identify the earliest kernel where the issue
started happening as well as the last kernel that did not have this
issue.

Can you test the following kernels and report back? We are looking for
the first kernel version that exhibits this bug:

4.5 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-wily/
4.8 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8/
4.10 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10/

You don't have to test every kernel, just up until the kernel that first
has this bug.

Thanks in advance!


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

** Also affects: linux (Ubuntu Cosmic)
   Importance: High
   Status: Confirmed

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

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

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

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

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

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu Cosmic)
 Assignee: (unassigned) => 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/1778717

Title:
  Ubuntu 18.04 guest hangs during diskio stress

Status in dellserver:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged
Status in linux source package in Cosmic:
  Triaged

Bug description:
  Setup - A Dell EMC 14th Gen AMD server, with ESXi 6.7 as host and
  Ubuntu 18.04 (latest updates) guest.

  Guest has 3 data disks apart from the boot disk. All these disks are exposed 
through "ParaVirtual SCSI controller" from the host ESXi 6.7.
  Run diskio stress on all the 3 data disks for overnight.
  Guest goes unresponsive (even ping fails) in between.
  Only way to recover is to reset the guest.

  Logs do not indicate much on this error.
  Rarely we get a crash on the Guest-screen. Attaching 2 screenshots of 
different hits.

  We have tried mainline kernel v4.18-rc-2 and have hit the issue there
  as well.

  Changing the SCSI controller to "LSI Logic SAS adapter" helps and we
  have not seen any crash/hang here.

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

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

[Kernel-packages] [Bug 1778534] Re: Touchpad not working (Elantech ELAN0618)

[Joseph Salisbury]

Thank you for providing a patch, and making Ubuntu better.

Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?

o submit your patch, send your patch with the detailed
description/changelog and your Signoff (ending with Signed-off-by: your
name ), to the emails listed from ./scripts/get_maintainer.pl
drivers/SUBSYSTEM-DETAILS (the get_maintainer.pl is from the kernel
sources). Once you have sent the patch upstream and it's accepted,
please drop a note here so that we can cherry-pick/include the patch
into Ubuntu kernel.

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

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

** Also affects: linux (Ubuntu Cosmic)
   Importance: Medium
   Status: Triaged

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

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

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

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

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

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

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

Title:
  Touchpad not working (Elantech ELAN0618)

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

Bug description:
  For a fresh installed Ubuntu 16 (and 18), touchpad doesn't work for
  Elantech ELAN0618.

  We have modified the struct elan_acpi_id, by adding ELAN0618 to the
  list of the supported models (in the file
  drivers/input/mouse/elan_i2c_core.c from the kernel source)

  static const struct acpi_device_id elan_acpi_id[] = {
{ "ELAN", 0 },
{ "ELAN0100", 0 },
{ "ELAN0600", 0 },
{ "ELAN0602", 0 },
{ "ELAN0605", 0 },
{ "ELAN0608", 0 },
{ "ELAN0605", 0 },
{ "ELAN0609", 0 },
{ "ELAN060B", 0 },
{ "ELAN060C", 0 },
{ "ELAN0611", 0 },
{ "ELAN0618", 0 },
{ "ELAN1000", 0 },
{ }
  };

  and then built the kernel, and our problem solved.

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

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

[Kernel-packages] [Bug 1778475] Re: i40e: restore workaround for removing default MAC filter

[Joseph Salisbury]

Are you sure you posted the correct commit?  The commit in the bug
description has been in mainline as of v4.10-rc1, so it has always been
in bionic as:

1596b5d i40e: restore workaround for removing default MAC filter


** Tags added: kernel-da-key

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

Title:
  i40e: restore workaround for removing default MAC filter

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

Bug description:
  Ubuntu Bionic kernel (4.15.0-23) lacks upstream patch for i40e which
  results in forced promiscous mode when adding a vlan.

  
  [   10.847381] i40e :3d:00.0: Error I40E_AQ_RC_EINVAL adding RX filters 
on PF, promiscuous mode forced on

  Steps to reproduce and patch here:

  https://patchwork.ozlabs.org/patch/692499/

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

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

[Kernel-packages] [Bug 1777242] Re: 4.15.0-23-generic fails to boot in qemu on amd64 host (kernel panic)

[Joseph Salisbury]

I built a v2 test kernel. The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1777242

Can you test this kernel and see if it resolves this bug?


Also, can you post the output from dmesg?

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

Title:
  4.15.0-23-generic fails to boot in qemu on amd64 host (kernel panic)

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

Bug description:
  Trying to boot bionic with 4.15.0-23-generic fails with a kernel panic in 
qemu on an Debian amd64 host.
  The version of qemu is the current in Debian Testing: 2.12+dfsg-3.

  Booting with 4.15.0-22-generic works fine.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zouzou 1274 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-07-12 (338 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170710)
  IwConfig:
   lono wireless extensions.
   
   ens3  no wireless extensions.
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux-signed (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=26da642a-bbc4-440b-bed3-a911bbbfe582 ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-02-07 (128 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.11.1-1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.8
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.11.1-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.8:cvnQEMU:ct1:cvrpc-i440fx-2.8:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.8
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1776887] Re: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend

[Paulo Marcel Coelho Aragão]

I mistakenly filed this exact same bug against xorg-server [1], until
Alan Jenkins made a comment [2] about this one. I'm surprised that not
more people have reported it or registered as affected users.

[1] https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1775593
[2] 
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1775593/comments/10

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

Title:
  Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash
  after suspend

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

Bug description:
  This upstream bug has been confirmed to affect Ubuntu users[1].  As
  per the fix commit (below), the most frequent symptom is a crash of
  Xorg/Xwayland, i.e. killing the entire GUI, when a laptop is woken
  from system sleep.  Frequency of the bug is described as once every
  few days[2].

  [1] E.g. this user confirms the bug & very specific workaround: 
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1760450/comments/11
  [2] E.g. this log of crashes: 
https://bugzilla.redhat.com/show_bug.cgi?id=1553979#c23

  This is a bug in blk-core.c.  It is not specific to any one hardware
  driver.  Technically the suspend bug is triggered by the SCSI core -
  which is used by *all SATA devices*.

  The commit also includes a test which quickly and reliably proves the
  existence of a horrifying bug.

  I guess you might avoid this bug only if you have root on NVMe.  The
  other way to not hit the Xorg crash is if you don't use all your RAM,
  so there's no pressure that leads to cold pages of Xorg being swapped.
  Also, you won't reproduce the Xorg crash if you suspend+resume
  immediately.  (This frustrated my tests at one point, it only
  triggered after left the system suspended over lunch :).

  Fix: "block: do not use interruptible wait anywhere"

  in kernel 4.17:
  
https://github.com/torvalds/linux/commit/1dc3039bc87ae7d19a990c3ee71cfd8a9068f428

  in kernel 4.16.8:
  https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
  stable.git/commit/?h=linux-4.16.y&id=7859056bc73dea2c3714b00c83b253d4c22bf7b6

  lack of fix in 4.15.0-24.26 (ubuntu 18.04): https://git.launchpad.net
  /~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/block/blk-
  core.c?id=Ubuntu-4.15.0-24.26#n856

  I.e., this bug is still present in Ubuntu source package
  linux-4.15.0-24.26 (and 4.15.0-23.25).  I attach hardware details
  (lspci-vnvn.log) of a system where this bug is known to happen.

  Regards
  Alan

  WORKAROUND: Use kernel parameter:
  scsi_mod.scan=sync

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

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

[Kernel-packages] [Bug 1770423] Re: Please cherry-pick upstream patch for HDMI on Dell XPS 9360

[Joseph Salisbury]

When you applied the patch to the 4.4.0-122 kernel did you have to
perform any backporting?  I had to with my test kernel, so maybe I
didn't perform the backport properly.

I'll do some investigating to see if a prereq patch is needed, so we
don't have to do any backporting.

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

Title:
  Please cherry-pick upstream patch for HDMI on Dell XPS 9360

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

Bug description:
  Connecting the Dell USB-C HDMI/LAN/VGA/USB adapter to my XPS 9360
  doesn’t quite work: I could not get my monitor to display a picture at
  all, regardless of which resolution I tried.

  A quick search on the internet revealed this patch:
  https://lists.freedesktop.org/archives/intel-
  gfx/2017-March/124077.html. Applying it to the 4.4.0-122 kernel does
  indeed make the HDMI work

  Could you please cherry-pick this patch into the Ubuntu kernel?
  Thanks!

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

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

[Kernel-packages] [Bug 1777338] Re: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message

[Joseph Salisbury]

I started a kernel bisect between v4.15.0-22 and v4.15.0-23. The kernel
bisect will require testing of about 7-10 test kernels.

I built the first test kernel, up to the following commit:
8eca6add0defde203282476d7969a7c13bbd7d91

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1777338

Can you test that kernel and report back if it has the bug or not?  I
will build the next test kernel based on your test results.


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

Title:
  Linux 4.15.0-23 crashes during the boot process with a "Unable to
  handle kernel NULL pointer dereference" message

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

Bug description:
  I went to boot my computer today and it wouldn't boot.

  I get an "Unable to handle kernel NULL pointer dereference" message
  during the boot process, and, a bit after that, a message from the
  kernel watchdog about CPU #0 being stuck. Then the boot process stops
  completely.

  I was able to boot the system by telling Grub to load 4.15.0-22, which
  works perfectly fine, so there has been a regression.

  I am running Ubuntu as a Xen dom0, if that matters. I haven't tried
  booting the offending kernel version without Xen.

  I'm not sure where, if anywhere, these messages go on disk, for
  posting.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-23-generic 4.15.0-23.25
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 17 10:12:58 2018
  InstallationDate: Installed on 2017-08-06 (314 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago)

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

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

[Kernel-packages] [Bug 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered

[Joseph Salisbury]

I built the next test kernel, up to the following commit:
24040a58379e2f2fa6aa9466911b758073b6bdfa

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1752961

Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on your test results.

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

Title:
  With kernel 4.13 btrfs scans for devices before all devices have been
  discovered

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

Bug description:
  See attached dmesg outputs for booting kernels 4.11.x (working) and
  4.13.x (not working).

  dmesg-4.11.0-14-good.txt shows the dmesg output when booting kernel 4.11.x.
  btrfs scans for devices after all 4 (sda, sdb, sdc, sdd) of the devices have 
been discovered by the kernel.  The btrfs RAID1 filesystem mounts, and 
everything is good.

  dmesg-4.13.0-36-fail.txt shows the dmesg output when booting kernel 4.13.x.
  btrfs scans for devices after only 2 (sda, sdb) of the devices have been 
discovered by the kernel.  The btrfs RAID1 filesystem fails to mount ("failed 
to read the system array: -5").  The remaining 2 devices (sdc, sdd) are 
discovered by the kernel immediately afterward.  At the end of the log, I run 
`btrfs device scan` and mount the filesystem manually.

  Hardware:
HP ProLiant MicroServer Gen8
4x WDC WD20EFRX
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: aplay: device_list:270: no soundcards found...
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  ArecordDevices: arecord: device_list:270: no soundcards found...
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2015-10-15 (933 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  MachineType: HP ProLiant MicroServer Gen8
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d976ab07-8377-46dd-ac6c-f5f7312a8305 ro rootflags=subvol=@ 
rootdelay=10
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  bionic apport-hook-error
  Uname: Linux 4.15.0-20-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: HP
  dmi.bios.version: J06
  dmi.chassis.type: 7
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrJ06:bd07/16/2015:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant MicroServer Gen8
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1748689] Re: Mounting SMB shares with vers=3.0 in fstab gives "ioctl error in smb2_get_dfs_refer rc=-2"

[Sujith Pandel]

I see this on 4.13.0-45-generic of Ubuntu 16.04 HWE kernels.

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

Title:
  Mounting SMB shares with vers=3.0 in fstab gives "ioctl error in
  smb2_get_dfs_refer rc=-2"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu 17.10 artful
  Kernel: x86_64 Linux 4.13.0-32.35-generic
  cifs-utils 2:6.7-1
  smbclient  2:4.6.7+dfsg-1ubuntu3.1

  Mounting an SMB share with
  
sec=ntlmssp,vers=3.0,credentials=/home/.smbcredentials,dir_mode=0777,file_mode=0777

  in /etc/fstab gives the error: "CIFS VFS: ioctl error in
  smb2_get_dfs_refer rc=-2" in dmesg.

  Shares mounted this way are readable, but writing data to them (or using 
programs such as EasyTAG to write to them) ultimately fails. This bug did not 
occur in kernel 4.10. Mounting the share(s) with vers=1.0 does not give the 
error, but this is a haphazard fix as SMB v3.0 carries many security features 
with it not avaliable in SMB 1.0.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=/dev/mapper/DeusVitam--vg-swap_1
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  MachineType: ASUS All Series
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=/dev/mapper/hostname--vg-root ro splash quiet amdgpu.cik_support=1 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  RfKill:
   
  Tags:  artful
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to artful on 2018-02-05 (7 days ago)
  UserGroups: libvirt libvirtd sudo wireshark
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0701
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-E/USB 3.1
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  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.:bvr0701:bd03/16/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-E/USB3.1:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Kernel-packages] [Bug 1763594] Re: xhci hangs; reset results in NULL pointer dereference

[Kai-Heng Feng]

Please try this kernel, which has some back ported commits to solve the issue:
https://people.canonical.com/~khfeng/lp1763594/

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

Title:
  xhci hangs; reset results in NULL pointer dereference

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

Bug description:
  Now and then, my xhci bus will hang, resulting in these kinds of
  messages in dmesg:

  [252220.002102] xhci_hcd :00:14.0: xHC is not running.
  [252220.037491] xhci_hcd :00:14.0: xHCI host controller not responding, 
assume dead
  [252220.037500] xhci_hcd :00:14.0: HC died; cleaning up
  [252220.133794] usb 1-2: USB disconnect, device number 2
  [252220.135042] usb 1-7: USB disconnect, device number 3
  [252220.137455] usb 1-8: USB disconnect, device number 4
  [252220.243317] usb 1-9: USB disconnect, device number 5

  Usually, I can fix this bij resetting the bus by calling a script
  reset-xhci:

  for xhci in /sys/bus/pci/drivers/?hci_hcd ; do
cd $xhci
echo Resetting devices from $xhci...
for i in :??:??.? ; do
  echo -n "$i" > unbind
  echo -n "$i" > bind
done
  done

  But doing this today resulted in a kernel bug:

  [252243.401814] xhci_hcd :00:14.0: remove, state 4
  [252243.401887] usb usb2: USB disconnect, device number 1
  [252243.470365] xhci_hcd :00:14.0: USB bus 2 deregistered
  [252243.470378] xhci_hcd :00:14.0: remove, state 4
  [252243.470383] usb usb1: USB disconnect, device number 1
  [252243.470831] xhci_hcd :00:14.0: Host halt failed, -19
  [252243.470837] xhci_hcd :00:14.0: Host not accessible, reset failed.
  [252243.475918] xhci_hcd :00:14.0: USB bus 1 deregistered
  [252243.475938] [ cut here ]
  [252243.475939] xhci_hcd :00:14.0: disabling already-disabled device
  [252243.475951] WARNING: CPU: 2 PID: 1787 at 
/build/linux-bdpCf2/linux-4.15.0/drivers/pci/pci.c:1642 
pci_disable_device+0x9c/0xc0
  [252243.475951] Modules linked in: cpuid snd_seq_dummy usb_storage 
hid_generic hidp ip6t_REJECT nf_reject_ipv6 ip6table_nat nf_nat_ipv6 
ip6table_mangle xt_hashlimit ip6table_raw nf_conntrack_ipv6 nf_defrag_ipv6 
nf_log_ipv6 xt_recent xt_comment ipt_REJECT nf_reject_ipv4 xt_mark 
iptable_mangle xt_tcpudp xt_CT iptable_raw xt_multiport xt_NFLOG nfnetlink_log 
nf_log_ipv4 nf_log_common xt_LOG nf_conntrack_sane nf_conntrack_netlink 
nfnetlink nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip 
nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda 
nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_proto_gre 
nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_irc 
nf_conntrack_h323 nf_conntrack_ftp ts_kmp nf_conntrack_amanda ipt_MASQUERADE 
nf_nat_masquerade_ipv4
  [252243.475984]  xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype xt_conntrack nf_nat nf_conntrack 
br_netfilter aufs vhost_net vhost tap ccm rfcomm bridge stp llc devlink 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter msr cmac bnep 
binfmt_misc snd_hda_codec_hdmi nls_iso8859_1 arc4 snd_soc_skl 
snd_hda_codec_realtek snd_soc_skl_ipc snd_hda_ext_core snd_hda_codec_generic 
snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core snd_compress ac97_bus 
snd_pcm_dmaengine snd_hda_intel dell_laptop dell_smbios_smm dcdbas 
snd_hda_codec dell_smm_hwmon snd_hda_core snd_hwdep snd_pcm intel_rapl 
snd_seq_midi snd_seq_midi_event x86_pkg_temp_thermal intel_powerclamp coretemp 
snd_rawmidi kvm_intel kvm btusb irqbypass intel_cstate intel_rapl_perf snd_seq 
btrtl
  [252243.476023]  iwlmvm btbcm btintel mac80211 hid_multitouch uvcvideo joydev 
input_leds dell_smbios_wmi snd_seq_device dell_wmi bluetooth serio_raw 
snd_timer videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 dell_smbios 
videobuf2_core iwlwifi sparse_keymap ecdh_generic snd wmi_bmof 
dell_wmi_descriptor videodev cfg80211 media soundcore rtsx_pci_ms memstick 
shpchp mei_me mei processor_thermal_device intel_pch_thermal intel_soc_dts_iosf 
int3400_thermal acpi_thermal_rel dell_rbtn mac_hid acpi_pad int3403_thermal 
int340x_thermal_zone tpm_crb sch_fq_codel cuse parport_pc ppdev nfsd lp parport 
auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs 
zstd_compress algif_skcipher af_alg dm_crypt raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1
  [252243.476067]  raid0 multipath linear dm_mirror dm_region_hash dm_log 
usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 
rtsx_pci_sdmmc i2c_algo_bit drm_kms_helper e1000e syscopyarea sysfillrect 
sysimgblt fb_sys_fops ptp aesni_intel psmouse drm pps_core rtsx_pci aes_x86_64 
ahci crypto_simd glue_helper libahci wmi cryptd video
  [252243.476089] CPU: 2 PID: 1787 Comm: r

[Kernel-packages] [Bug 1778772] Re: linux-gcp: 4.15.0-1010.10~16.04.1 -proposed tracker

[Brad Figg]

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

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

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

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Fix Released

** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 4.15.0-1010.10~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
  kernel-stable-master-bug: 1776333
  phase: Uploaded
+ kernel-stable-phase-changed:Wednesday, 27. June 2018 15:30 UTC
+ kernel-stable-phase:Promoted to proposed

** Description changed:

  This bug is for tracking the 4.15.0-1010.10~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
  kernel-stable-master-bug: 1776333
- phase: Uploaded
- kernel-stable-phase-changed:Wednesday, 27. June 2018 15:30 UTC
- kernel-stable-phase:Promoted to proposed
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux-gcp: 4.15.0-1010.10~16.04.1 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.15.0-1010.10~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
  kernel-stable-master-bug: 1776333
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1775152] Re: Fix "Unable to handle kernel paging request" in AMD MP2 driver

[Kai-Heng Feng]

Reboot several times, not seeing this issue anymore.

** 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-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1775152

Title:
  Fix "Unable to handle kernel paging request" in AMD MP2 driver

Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Committed

Bug description:
  ===SRU Justification===
  [Impact]
  Touchpad doesn't work after boot. Roughly 1/10 fail rate.

  [Test]
  With the patch, I no longer see the issue in 30 times reboot.

  [Fix]
  Factor out the pointer in the union, so the pointer value won't get changed 
by other union member.

  [Regression Potential]
  Low. It's specific to a single driver, which only enabled in OEM-A kernel.

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

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

[Kernel-packages] [Bug 1768103] Re: Lancer A0 Asic HBA's won't boot with 18.04

[Kleber Sacilotto de Souza]

Hi Laurie,

The easiest way to install the latest update kernel is to enable the
-proposed pocket and install the kernel packages from there, as
documented on https://wiki.ubuntu.com/Testing/EnableProposed.

Thank you,
Kleber

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

Title:
  Lancer A0 Asic HBA's won't boot with 18.04

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

Bug description:
  == SRU Justification ==
  It was reported by Broadcom that an early asic model (A0) of their 16/32GB
  HBA's doesn't boot with the lpfc driver in Ubuntu 18.04.

  Bionic with the lpfc driver 12.0.0.0 can't see LPe16002-M6 but can see
  LPe16002B-M6.

  This bug is fixed by commits bf316c78517d and c221768bd49a, which are
  both still in linux-next.  Broadcom tested with this two commits and
  confirmed they resolve the bug and allow the system to boot.

  == Fixes ==
  Currently in linux-next:
  bf316c78517d ("scsi: lpfc: Fix WQ/CQ creation for older asic's.")
  c221768bd49a ("scsi: lpfc: Fix 16gb hbas failing cq create.")

  == Regression Potential ==
  Low.  Patches fix a current regression and are limited to lpfc.

  == Test Case ==
  A test kernel was built with these patches and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  
  We have discovered that an early asic model (A0) of our 16/32GB HBA's doesn't 
boot with the lpfc driver in Ubuntu 18.04.

  After further review and discussion, this has been deemed a low risk
  issue since early A0 HBA's were only ever shipped to OEMs for test
  purposes.  These cards were never shipped to end customers.   We have
  been working to replace those cards whenever we discover them.

  We'll leave it up to Canonical to decide whether they want to pull
  this in this single patch to an 18.04 subsequent update.

  Symptom: Ubuntu 18.04 with lpfc driver 12.0.0.0 they can't see LPe16002-M6 
but can see LPe16002B-M6
  Resolution: new lpfc driver patch update.

  scsi: lpfc: Fix WQ/CQ creation for older asic's.
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=4.18/scsi-queue&id=83fae8ca4ae09403bfb99542f1aaa292c06cb111

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

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

[Kernel-packages] [Bug 1772991] Re: [Ubuntu 18.04.1] POWER9 - Nvidia Volta - Kernel changes to enable Nvidia driver on bare metal

[Kleber Sacilotto de Souza]

Thank you Douglas for the verification!

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

Title:
  [Ubuntu 18.04.1] POWER9 - Nvidia Volta - Kernel changes to enable
  Nvidia driver on bare metal

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

Bug description:
  == SRU Justification ==
  12 kernel patches have been identified as needed to support Nvidia Volta 
  on bare metal. All are accepted upstream in 4.17. Three of those are 
  already in bionic, leaving a total of 9 remaining commits needed in bionic.
  This pull request is for those other 9 commits.

  == Regression Potential ==
  All of the commits are specific to powerpc.

  == Test Case ==
  A test kernel was built with these patches and tested by IBM.


  == Comment: #0 - Barry B. Arndt  - 2018-05-23 13:40:33 ==
  12 kernel patches have been identified as needed to support Nvidia Volta on 
bare metal.  All are accepted upstream in 4.17.  Three of those are already in 
bionic, leaving a total of 9 remaining commits needed in bionic.  Those 9 
commits are:

  720c84046c26  powerpc/npu-dma.c: Fix crash after __mmu_notifier_register 
failure
  2b74e2a9b39d  powerpc/powernv/npu: Fix deadlock in mmio_invalidate()
  5ee573e8ef03  powerpc/powernv/mce: Don't silently restart the machine
  fb5924fddf9e  powerpc/mm: Flush cache on memory hot(un)plug
  7fd6641de28f  powerpc/powernv/memtrace: Let the arch hotunplug code flush 
cache
  28a5933e8d36  powerpc/powernv/npu: Add lock to prevent race in concurrent 
context init/destroy
  a1409adac748  powerpc/powernv/npu: Prevent overwriting of 
pnv_npu2_init_contex() callback parameters
  d0cf9b561ca9  powerpc/powernv/npu: Do a PID GPU TLB flush when invalidating a 
large address range
  75ecfb49516c  powerpc/mce: Fix a bug where mce loops on memory UE.

  We cherry-picked the commits, and all applied cleanly.  The resultant
  kernel built successfully and loaded.

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

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

[Kernel-packages] [Bug 1774583] Re: Resuming does not work with kernel 3.13.0-149-generic

[Bruno Sevennec]

The only thing that worked for me was downgrading the intel-microcode
package update (using Synaptic and its "force version" option in package
menu), and in particular upgrading to 151 kernel was not a fix for me
(and others apparently).

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

Title:
  Resuming does not work with kernel 3.13.0-149-generic

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  On my laptop MSI GE40 (MS-1492) with Ubuntu 14.04.5 LTS and kernel
  3.13.0-149-generic resuming after a suspend no longer works. It hangs
  on a blank screen and is unresponsive. The only option is to hold the
  power button for 6 seconds to shut it down. It worked fine on
  3.13.0-147-generic.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-149-generic 3.13.0-149.199
  ProcVersionSignature: Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-149-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.28
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  j-p3041 F pulseaudio
   /dev/snd/controlC1:  j-p3041 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jun  1 09:22:59 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=d0b66801-6479-4dc4-aae2-9bd97799b4a4
  InstallationDate: Installed on 2013-11-20 (1653 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Micro-Star International Co., Ltd. CR42 2M/GE40 2OC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic 
root=UUID=3a8ce5b7-2d9e-441f-a3a6-16627d17cfa0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-149-generic N/A
   linux-backports-modules-3.13.0-149-generic  N/A
   linux-firmware  1.127.24
  SourcePackage: linux
  StagingDrivers: rts5139
  UpgradeStatus: Upgraded to trusty on 2014-11-17 (1291 days ago)
  dmi.bios.date: 08/05/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1492IMS.10H
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1492
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: CR42 2M/GE40 2OC
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1492IMS.10H:bd08/05/2013:svnMicro-StarInternationalCo.,Ltd.:pnCR422M/GE402OC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1492:rvrREV1.0:cvnCR422M/GE402OC:ct10:cvrN/A:
  dmi.product.name: CR42 2M/GE40 2OC
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Kernel-packages] [Bug 1413440] Re: USB stops working after a while (xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command)

[Kai-Heng Feng]

For those who see "xhci_hcd :00:14.0: xHCI host controller not
responding, assume dead" in the dmesg, please subscribe to LP: #1763594.

I am building a test kernel for that bug.

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

Title:
  USB stops working after a while (xhci_hcd :00:14.0: Timeout while
  waiting for setup device command)

Status in System76:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  On my laptop the kernel will sometimes drop the USB hub. After this,
  the laptop doesn't recognise any device plugged in to the USB ports -
  plugging and unplugging any device I've tried into any of the USB
  ports produces no response, not even dmesg entries.

  Strangely this also applies to bluetooth - it no longer works once USB
  has dropped (possibly the module is hung of the bus internally).

  Once this has happened only a reboot fixes it; I've not managed to
  find any combination of module unload/reload or suspend cycles to
  reinitialise things correctly.

  Relevant snippet of dmesg:
  [48830.625057] xhci_hcd :00:14.0: Timeout while waiting for setup device 
command
  [48838.079718] xhci_hcd :00:14.0: Stopped the command ring failed, maybe 
the host is dead
  [48838.079742] xhci_hcd :00:14.0: Abort command ring failed
  [48838.079746] xhci_hcd :00:14.0: HC died; cleaning up
  [48838.079770] xhci_hcd :00:14.0: Timeout while waiting for setup device 
command
  [48838.079806] sched: RT throttling activated
  [48838.079981] usb 1-1: USB disconnect, device number 16
  [48838.079985] usb 1-1.2: USB disconnect, device number 18
  [48838.079987] usb 1-1.2.3: USB disconnect, device number 19
  [48838.080285] usb 1-1.2.4: USB disconnect, device number 20
  [48838.111892] usb 1-1.4: USB disconnect, device number 17
  [48838.191292] usb 1-4: USB disconnect, device number 6
  [48838.267550] usb 1-10: USB disconnect, device number 8
  [48838.282968] usb 2-1: device not accepting address 8, error -62
  [48838.282983] usb 2-1: USB disconnect, device number 8
  [48838.282986] usb 2-1.2: USB disconnect, device number 9

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.18.0-9-generic 3.18.0-9.10
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chris  4255 F pulseaudio
   /dev/snd/controlC0:  chris  4255 F pulseaudio
  CRDA:
   country AU: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20), (N/A)
(5170 - 5250 @ 40), (3, 23), (N/A)
(5250 - 5330 @ 40), (3, 23), (0 ms), DFS
(5735 - 5835 @ 40), (3, 30), (N/A)
  CurrentDesktop: Unity
  Date: Thu Jan 22 12:59:27 2015
  InstallationDate: Installed on 2013-08-06 (533 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: System76, Inc. Galago UltraPro
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic.efi.signed 
root=UUID=92c2fa03-f29c-4bcc-87ab-f0fe28c134f2 ro quiet splash vt.handoff=7 
init=/lib/systemd/systemd break=mount
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-9-generic N/A
   linux-backports-modules-3.18.0-9-generic  N/A
   linux-firmware1.141
  RfKill:
   1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2013-08-06 (533 days ago)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Galago UltraPro
  dmi.board.vendor: System76, Inc.
  dmi.board.version: galu1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: System76, Inc,
  dmi.chassis.version: galu1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/09/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnSystem76,Inc.:rnGalagoUltraPro:rvrgalu1:cvnSystem76,Inc,:ct9:cvrgalu1:
  dmi.product.name: Galago UltraPro
  dmi.product.version: galu1
  dmi.sys.vendor: System76, Inc.

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

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

[Kernel-packages] [Bug 1597415] Re: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument

[Marco Ochse]

Confirming the same issue on Ubuntu Server 18.04 LTS:

Error calling EVIOCSKEYCODE on device node '/dev/input/event2' (scan code 
0x9004c, key code 162): Invalid argument
CODE_FILE   ../src/udev/udev-builtin-keyboard.c
CODE_FUNC   map_keycode
CODE_LINE   103
ERRNO   22
PRIORITY3
SYSLOG_FACILITY 3
SYSLOG_IDENTIFIER   systemd-udevd
_BOOT_ID8561955e61444adea66c6983c7972f60
_CAP_EFFECTIVE  3f
_CMDLINE/lib/systemd/systemd-udevd
_COMM   systemd-udevd
_EXE/lib/systemd/systemd-udevd
_GID0
_HOSTNAME   blueeyebrows
_MACHINE_ID 3c83a050931347c59c2d930c491afdc7
_PID340
_SELINUX_CONTEXTunconfined
_SOURCE_REALTIME_TIMESTAMP  1530104311822252
_SYSTEMD_CGROUP /system.slice/systemd-udevd.service
_SYSTEMD_INVOCATION_ID  da5926014fa944509d5e10a8d9a6adf2
_SYSTEMD_SLICE  system.slice
_SYSTEMD_UNIT   systemd-udevd.service
_TRANSPORT  journal
_UID0
__CURSOR
s=b7551ec2b2f942ae94a42e8501582e71;i=1784;b=8561955e61444adea66c6983c7972f60;m=868e2f;t=56f9f2bf9bcec;x=626cfce2d4ede039
__MONOTONIC_TIMESTAMP   8818223
__REALTIME_TIMESTAMP1530104311823596


Kernel: 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 x86_64 
x86_64 x86_64 GNU/Linux

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

Title:
  systemd-udevd: Error calling EVIOCSKEYCODE on device node
  '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument

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

Bug description:
  Hi,

  the symptom is this error message in my system's logs:

  juin 29 16:56:39 vougeot systemd-udevd[522]: Error calling
  EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key
  code 190): Invalid argument

  According to /proc/bus/input/devices the corresponding input device
  is:

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Dell WMI hotkeys"
  P: Phys=wmi/input0
  S: Sysfs=/devices/virtual/input/input10
  U: Uniq=
  H: Handlers=kbd event9 
  B: PROP=0
  B: EV=13
  B: KEY=1000b0400 0 e 0
  B: MSC=10

  This laptop is a Dell Latitude E6520.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu6
  Uname: Linux 4.6.3-040603-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  CustomUdevRuleFiles: 60-ssd-scheduler.rules
  Date: Wed Jun 29 17:43:01 2016
  EcryptfsInUse: Yes
  MachineType: Dell Inc. Latitude E6520
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.3-040603-generic 
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro enable_mtrr_cleanup 
mtrr_spare_reg_nr=1 mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (80 days ago)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0NVF5K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1774150] Re: 3.13.0-149-generic: suspend/resume issue on 14.04

[Bruno Sevennec]

Sorry to be late, but to downgrade intel-microcode I used synaptic,
which in the packages menu has the option to force version of a package
and then (after applying change) to hold it against updates. I chose the
only other version listed (2.2014something) and it worked. 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/1774150

Title:
  3.13.0-149-generic: suspend/resume issue on 14.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 14.04.5 LTS, the most recent kernel update to
  3.13.0-149-generic means that my laptop (Acer Aspire V5) does not
  resume once suspended - all I get is a blank screen, unresponsive to
  keypresses, and I need to reboot.

  The 144 kernel is OK, and this question:
  
https://askubuntu.com/questions/1040169/experiencing-suspend-resume-problem-after-latest-kernel-update-ubuntu-14-04
  suggests that 147 is OK too.

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

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

[Kernel-packages] [Bug 1778772] Re: linux-gcp: 4.15.0-1010.10~16.04.1 -proposed tracker

[Łukasz Zemczak]

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => Fix Committed

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

Title:
  linux-gcp: 4.15.0-1010.10~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:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.15.0-1010.10~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
  kernel-stable-master-bug: 1776333
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1777863] Re: [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit

[Haug Bürger]

I currently run on mainline 4.17.3-041703-generic #201806252030 SMP Tue
Jun 26 00:33:17 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux and it didn't
occur again. With the 4.15.0-23 I had up to 4 spontaneous reboots an
office day.

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

Title:
  [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI
  BUF C idle bit

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  System reboot. This could be related to putting the NB back into the docking 
station.
  Search for [ cut here ] to find the final error 
message before reboot.

  Linux mymachine4 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16
  UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Using vrefresh ranges from config file
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Printing DDC gathered Modelines:
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "1920x1080"x0.0  148.50  1920 2008 2052 2200  1080 1084 1089 1125 
+hsync +vsync (67.5 kHz eP)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync 
(37.9 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync 
(37.5 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync 
(31.5 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync 
(31.5 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "1280x1024"x0.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 
+hsync +vsync (80.0 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync 
+vsync (60.0 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync 
-vsync (48.4 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync 
(46.9 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "1152x864"x0.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync 
+vsync (67.5 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 
+hsync +vsync (64.0 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "1600x900"x60.0  119.00  1600 1696 1864 2128  900 901 904 932 -hsync 
+vsync (55.9 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "1920x1080"x60.0  172.80  1920 2040 2248 2576  1080 1081 1084 1118 
-hsync +vsync (67.1 kHz e)
  Jun 20 12:05:18 mymachine kernel: [drm:intel_wait_ddi_buf_idle [i915]] 
*ERROR* Timeout waiting for DDI BUF C idle bit
  Jun 20 12:05:18 mymachine kernel: [ cut here ]
  Jun 20 12:05:18 mymachine kernel: vblank wait timed out on crtc 2
  Jun 20 12:05:18 mymachine kernel: WARNING: CPU: 2 PID: 4445 at 
/build/linux-uT8zSN/linux-4.15.0/drivers/gpu/drm/drm_vblank.c:1073 
drm_wait_one_vblank+0x181/0x190 [drm]
  Jun 20 12:05:18 mymachine kernel: Modules linked in: msr rfcomm ccm veth 
nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo br_netfilter bridge stp llc 
overlay thunderbolt cmac bnep btusb btrtl btbcm uvcvideo 
  Jun 20 12:05:18 mymachine kernel:  intel_cstate mac80211 intel_rapl_perf 
snd_compress ac97_bus snd_pcm_dmaengine snd_seq_midi snd_seq_midi_event 
snd_hda_intel snd_rawmidi snd_hda_codec snd_hda_core snd_hwdep i
  Jun 20 12:05:18 mymachine kernel:  pps_core drm nvme_core wmi video
  Jun 20 12:05:18 mymachine kernel: CPU: 2 PID: 4445 Comm: Xorg Tainted: G  
  W4.15.0-23-generic #25-Ubuntu
  Jun 20 12:05:18 mymachine kernel: Hardware name: LENOVO 
20HGS30X00/20HGS30X00, BIOS N1WET34W (1.13 ) 06/26/2017
  Jun 20 12:05:18 mymachine kernel: RIP: 0010:drm_wait_one_vblank+0x181/0x190 
[drm]
  Jun 20 12:05:18 mymachine kernel: RSP: 0018:a32ac3b83a68 EFLAGS: 00010282
  Jun 20 12:05:18 mymachine kernel: RAX:  RBX: 8c5175a38000 
RCX: 0006
  Jun 20 12:05:18 mymachine kernel: RDX: 0007 RSI: 0096 
RDI: 8c519e516490
  Jun 20 12:05:18 mymachine kernel: RBP: f

[Kernel-packages] [Bug 1778476] Re: [bionic] high cpu load HP probook iio-sensor-proxy

[Ludwin Janvier]

I now have 4.18.0-041800rc2-generic #201806241430 SMP Sun Jun 24
14:33:07 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux.

No change.

Edit: I just change my description : my idle is > 99% but my load
average is =~ 1.1 (any kernel)

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

Title:
  [bionic] high cpu load HP probook  iio-sensor-proxy

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a many HP ProBook 450 G1 and HP ProBook 650 G3 with fresh
  install of Ubuntu Desktop.

  They all have a load average of 1.0 when idle (no graphical session
  opened).

  vmstat shows idle =~ 100%

  The process which uses most CPU time is iio-sensor-proxy (about 1%)
  and it's constantly in D state (uninterruptible sleep).

  Manually starting this command shows that the sensor (lis3lv02d on
  both products) is constantly sending garbage informations (see
  attachment).

  With iio-sensor-proxy service stopped, the CPU load is ~ 0%

  As the service is 'static' and can not be disabled, the only workaround is to 
remove the 'iios-sensor-proxy' package.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1371 F pulseaudio
    ljanvier   2104 F pulseaudio
   /dev/snd/controlC0:  gdm1371 F pulseaudio
    ljanvier   2104 F pulseaudio
  DistroRelease: Ubuntu 18.04
  MachineType: Hewlett-Packard HP ProBook 650 G1
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=e375b9cb-3776-455a-bb2e-24f826528047 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  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
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UnreportableReason: Ce rapport concerne un paquet qui n'est pas installé.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: False
  dmi.bios.date: 12/24/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L77 Ver. 01.31
  dmi.board.name: 1993
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3A
  dmi.chassis.asset.tag: 5CG5124FWZ
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL77Ver.01.31:bd12/24/2014:svnHewlett-Packard:pnHPProBook650G1:pvrA3009DD10303:rvnHewlett-Packard:rn1993:rvrKBCVersion16.3A:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP ProBook 650 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1778476] Re: [bionic] high cpu load HP probook iio-sensor-proxy

[Ludwin Janvier]

** Description changed:

  I have a many HP ProBook 450 G1 and HP ProBook 650 G3 with fresh install
  of Ubuntu Desktop.
  
  They all have a load average of 1.0 when idle (no graphical session
  opened).
  
- vmstat shows idle=0% and waiting=~ 100%
+ vmstat shows idle =~ 100%
  
  The process which uses most CPU time is iio-sensor-proxy (about 1%) and
  it's constantly in D state (uninterruptible sleep).
  
  Manually starting this command shows that the sensor (lis3lv02d on both
  products) is constantly sending garbage informations (see attachment).
  
  With iio-sensor-proxy service stopped, the CPU load is ~ 0%
  
  As the service is 'static' and can not be disabled, the only workaround is to 
remove the 'iios-sensor-proxy' package.
- --- 
+ ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  gdm1371 F pulseaudio
-   ljanvier   2104 F pulseaudio
-  /dev/snd/controlC0:  gdm1371 F pulseaudio
-   ljanvier   2104 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  gdm1371 F pulseaudio
+   ljanvier   2104 F pulseaudio
+  /dev/snd/controlC0:  gdm1371 F pulseaudio
+   ljanvier   2104 F pulseaudio
  DistroRelease: Ubuntu 18.04
  MachineType: Hewlett-Packard HP ProBook 650 G1
  Package: linux (not installed)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  LANG=fr_FR.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=fr_FR.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=e375b9cb-3776-455a-bb2e-24f826528047 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  PulseList:
-  Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
-  No PulseAudio daemon running, or not running as session daemon.
+  Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
+  No PulseAudio daemon running, or not running as session daemon.
  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
+  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
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UnreportableReason: Ce rapport concerne un paquet qui n'est pas installé.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
-  
+ 
  _MarkForUpload: False
  dmi.bios.date: 12/24/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L77 Ver. 01.31
  dmi.board.name: 1993
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3A
  dmi.chassis.asset.tag: 5CG5124FWZ
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL77Ver.01.31:bd12/24/2014:svnHewlett-Packard:pnHPProBook650G1:pvrA3009DD10303:rvnHewlett-Packard:rn1993:rvrKBCVersion16.3A:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP ProBook 650 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

Title:
  [bionic] high cpu load HP probook  iio-sensor-proxy

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a many HP ProBook 450 G1 and HP ProBook 650 G3 with fresh
  install of Ubuntu Desktop.

  They all have a load average of 1.0 when idle (no graphical session
  opened).

  vmstat shows idle =~ 100%

  The process which uses most CPU time is iio-sensor-proxy (about 1%)
  and it's constantly in D state (uninterruptible sleep).

  Manually starting this command shows that the sensor (lis3lv02d on
  both products) is constantly sending garbage informations (see
  attachment).

  With iio-sensor-proxy service stopped, the CPU load is ~ 0%

  As the service is 'static' and can not be disabled, the only workaround is to 
remove the 'iios-sensor-proxy' package.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1371 F pulseaudio
    ljanvier   2104 F pulseaudio
   /dev/snd/controlC0:  gdm1371 F pulseaudio
    ljanvier   2104 F pulseaudio
  DistroRelease: Ubuntu 18.04
  MachineType: Hewlett-Packard HP ProBook 650 G1
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custo

[Kernel-packages] [Bug 1778642] Re: ubuntu_lttng_smoke_test failed on Azure 4.15

[Po-Hsu Lin]

Comment #1 is invalid, this test does not work on xenial/Azure because
of the module build issue (bug 1765673)

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

Title:
  ubuntu_lttng_smoke_test failed on Azure 4.15

Status in lttng-modules:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux-azure package in Ubuntu:
  New

Bug description:
  ***THIS IS A POTENTIAL REGRESSION***

  This test will pass with the older kernel, 4.15.0-1013-azure, but not
  the 4.15.0-1014-azure in -proposed.

  It looks like the kernel module can be installed, but four tests have
  failed:

  == lttng smoke test of session create/destroy ==
  Session test-kernel-session created.
  Traces will be written in /tmp/lttng-kernel-trace-14716-session
  PASSED (lttng create)
  Session test-kernel-session destroyed
  PASSED (lttng destroy)

  == lttng smoke test list kernel events ==
  FAILED (lttng list --kernel)
  FAILED (lttng list --kernel more output expected)

  == lttng smoke test trace open/close system calls ==
  Session test-kernel-session created.
  Traces will be written in /tmp/lttng-kernel-trace-14716-session
  PASSED (lttng create)
  FAILED (lttng enable-event)
  Session test-kernel-session destroyed

  == lttng smoke test trace context switches ==
  Session test-kernel-session created.
  Traces will be written in /tmp/lttng-kernel-trace-14716-session
  PASSED (lttng create)
  FAILED (lttng enable-event)
  Session test-kernel-session destroyed

  Summary: 4 passed, 4 failed

  http://10.246.72.46/4.15.0-1014.14-azure/bionic-linux-azure-
  
azure-4.15.0-Standard_D12-ubuntu_lttng_smoke_test/ubuntu_lttng_smoke_test/results/ubuntu_lttng_smoke_test
  .lttng-smoke-test/debug/ubuntu_lttng_smoke_test.lttng-smoke-
  test.DEBUG.html

  Error message from /var/log/syslog:

   kernel: [  639.531889] PKCS#7 signature not signed with a trusted key
   kernel: [  639.538251] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0)
   kernel: [  639.538280] lttng_tracer: Unknown symbol lttng_hp_online (err 0)
   lttng-sessiond[1097]: Error: Unable to load required module 
lttng-ring-buffer-client-discard
   lttng-sessiond[1097]: Warning: No kernel tracer available
   kernel: [  639.606845] PKCS#7 signature not signed with a trusted key
   kernel: [  639.613331] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0)
   kernel: [  639.613360] lttng_tracer: Unknown symbol lttng_hp_online (err 0)
   lttng-sessiond[1097]: Error: Unable to load required module 
lttng-ring-buffer-client-discard
   lttng-sessiond[1097]: Warning: No kernel tracer available
   kernel: [  639.677124] PKCS#7 signature not signed with a trusted key
   kernel: [  639.680857] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0)
   kernel: [  639.680886] lttng_tracer: Unknown symbol lttng_hp_online (err 0)
   lttng-sessiond[1097]: Error: Unable to load required module 
lttng-ring-buffer-client-discard
   lttng-sessiond[1097]: Warning: No kernel tracer available
   kernel: [  639.737914] PKCS#7 signature not signed with a trusted key
   kernel: [  639.753366] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0)
   kernel: [  639.753394] lttng_tracer: Unknown symbol lttng_hp_online (err 0)
   lttng-sessiond[1097]: Error: Unable to load required module 
lttng-ring-buffer-client-discard
   lttng-sessiond[1097]: Warning: No kernel tracer available
   kernel: [  639.829710] PKCS#7 signature not signed with a trusted key
   kernel: [  639.843736] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0)
   kernel: [  639.843765] lttng_tracer: Unknown symbol lttng_hp_online (err 0)
   lttng-sessiond[1097]: Error: Unable to load required module 
lttng-ring-buffer-client-discard
   lttng-sessiond[1097]: Warning: No kernel tracer available

To manage notifications about this bug go to:
https://bugs.launchpad.net/lttng-modules/+bug/1778642/+subscriptions

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

[Kernel-packages] [Bug 1690085]

[ryan]

I was able to capture a soft-lock with sysrq-l [1]. Networking and mouse
were still functional, but focusing windows and window activity in
Plasma were locked.

https://gist.github.com/rphillips/fae9540a8e7a3a83731c9a9809a98df4

Notes:
 * AMD Ryzen 2700X
 * SuperNOVA 650 G3 650W (Eco switch set to Off)
 * Asus ROG Crosshair VII Hero Wifi (BIOS 0601 04/19/2018, Typical Current set 
in the BIOS)

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

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

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

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 
stuck (mentioning the CPU core id, which is random).
  Crash is happening randomly, but in general after some hours (3-4h).

  Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning 
and waiting for crash...
  For now, the machine is not "used", at least, it's not CPU stressed...

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-04110

[Kernel-packages] [Bug 1769610] Re: Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

[Denis Turischev]

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

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

Title:
  Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

  On systems using Intel Atom (Baytrail-I) SoC's, slave devices connected on
  HSUART1/2 ports are described by the ACPI BIOS as virtual hardware using
  HID's INT3511/INT3512 [1].

  As a consequence, HW manufacturers have complete freedom to install any
  devices on-board as long as they can be accessed over serial tty
  interface. Once such device is Dell Edge 3002 IoT Gateway which sports
  ZigBee & GPS devices on the HS-UART ports 1 & 2 respectively.

  Post 4.15, with CONFIG_SERIAL_DEV_BUS=y, serdev port controller driver
  handles the enumeration for the slaves connected on these ports. Also,
  /dev/ttySx device nodes for these ports are no longer exposed to the
  userspace.

  This driver has been submitted upstream and is under review. This issue has
  been identified as a regression in 4.15 and multiple solutions are being
  explored. Meanwhile, to support customer and maintain release schedule,
  this driver needs to be in Ubuntu 4.15 based kernels.

  The impact is limited to systems based on Intel Atom E38XX (Baytrail-I)
  SoC's.

  More info:
  https://marc.info/?t=15245587167&r=1&w=2

  Please don't triage, this bug is for tracking purposes only.

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

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

[Kernel-packages] [Bug 1776342] Re: linux-azure: 4.15.0-1014.14 -proposed tracker

[Po-Hsu Lin]

Mark this task as Incomplete for the lttng issue (bug 1778642)

4.15.0-1014.14 - azure
Regression test CMPL, RTB.

Issue to note in x86_64 (azure):
  ebizzy - failed on Standard_A0, passed on the rest
  monotonic_time - tsc failed on some instances, clock failed on 
Standard_E4s_v3, Standard_E64-16s(bug 1774959), passed on the rest
  ubuntu_kvm_unit_tests - test skipped due to no KVM support, vmx_control will 
crash E4 nodes (bug 1747892)
  ubuntu_ltp - test disabled on azure
  ubuntu_ltp_syscalls - inotify08 failed with X/X-LTS/X-HWE/A/B kernel (bug 
1775784)
  ubuntu_lttng_smoke_test - ubuntu_lttng_smoke_test failed on Azure 4.15 (bug 
1778642)
  ubuntu_lxc - lxc-test-usernic.in failed on Bionic (bug 1775809)
  ubuntu_quota_smoke_test - need the -extra package (bug 1777114)
  ubuntu_ramfs_stress - failed on Standard_B1s only, passed on the rest
  ubuntu_stress_smoke_test - sysfs caused kernel oopsed on some instances (bug 
1757057)
  ubuntu_unionmount_overlayfs_suite - File unexpectedly on union layer (bug 
1751243)
  ubuntu_zram_smoke_test - zram module missing (bug 1762756)

Skipped / blacklisted:
  * libhugetlbfs
  * ubuntu_nbd_smoke_test
  * ubuntu_seccomp

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

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

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

Title:
  linux-azure: 4.15.0-1014.14 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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:
  Incomplete
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow stakeholder-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-azure package in Ubuntu:
  Invalid
Status in linux-azure 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: 1776338
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1778642] Re: ubuntu_lttng_smoke_test failed on Azure 4.15

[Po-Hsu Lin]

This issue could be found on 4.15.0-1014.14~16.04.1 Azure as well.

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

Title:
  ubuntu_lttng_smoke_test failed on Azure 4.15

Status in lttng-modules:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux-azure package in Ubuntu:
  New

Bug description:
  ***THIS IS A POTENTIAL REGRESSION***

  This test will pass with the older kernel, 4.15.0-1013-azure, but not
  the 4.15.0-1014-azure in -proposed.

  It looks like the kernel module can be installed, but four tests have
  failed:

  == lttng smoke test of session create/destroy ==
  Session test-kernel-session created.
  Traces will be written in /tmp/lttng-kernel-trace-14716-session
  PASSED (lttng create)
  Session test-kernel-session destroyed
  PASSED (lttng destroy)

  == lttng smoke test list kernel events ==
  FAILED (lttng list --kernel)
  FAILED (lttng list --kernel more output expected)

  == lttng smoke test trace open/close system calls ==
  Session test-kernel-session created.
  Traces will be written in /tmp/lttng-kernel-trace-14716-session
  PASSED (lttng create)
  FAILED (lttng enable-event)
  Session test-kernel-session destroyed

  == lttng smoke test trace context switches ==
  Session test-kernel-session created.
  Traces will be written in /tmp/lttng-kernel-trace-14716-session
  PASSED (lttng create)
  FAILED (lttng enable-event)
  Session test-kernel-session destroyed

  Summary: 4 passed, 4 failed

  http://10.246.72.46/4.15.0-1014.14-azure/bionic-linux-azure-
  
azure-4.15.0-Standard_D12-ubuntu_lttng_smoke_test/ubuntu_lttng_smoke_test/results/ubuntu_lttng_smoke_test
  .lttng-smoke-test/debug/ubuntu_lttng_smoke_test.lttng-smoke-
  test.DEBUG.html

  Error message from /var/log/syslog:

   kernel: [  639.531889] PKCS#7 signature not signed with a trusted key
   kernel: [  639.538251] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0)
   kernel: [  639.538280] lttng_tracer: Unknown symbol lttng_hp_online (err 0)
   lttng-sessiond[1097]: Error: Unable to load required module 
lttng-ring-buffer-client-discard
   lttng-sessiond[1097]: Warning: No kernel tracer available
   kernel: [  639.606845] PKCS#7 signature not signed with a trusted key
   kernel: [  639.613331] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0)
   kernel: [  639.613360] lttng_tracer: Unknown symbol lttng_hp_online (err 0)
   lttng-sessiond[1097]: Error: Unable to load required module 
lttng-ring-buffer-client-discard
   lttng-sessiond[1097]: Warning: No kernel tracer available
   kernel: [  639.677124] PKCS#7 signature not signed with a trusted key
   kernel: [  639.680857] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0)
   kernel: [  639.680886] lttng_tracer: Unknown symbol lttng_hp_online (err 0)
   lttng-sessiond[1097]: Error: Unable to load required module 
lttng-ring-buffer-client-discard
   lttng-sessiond[1097]: Warning: No kernel tracer available
   kernel: [  639.737914] PKCS#7 signature not signed with a trusted key
   kernel: [  639.753366] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0)
   kernel: [  639.753394] lttng_tracer: Unknown symbol lttng_hp_online (err 0)
   lttng-sessiond[1097]: Error: Unable to load required module 
lttng-ring-buffer-client-discard
   lttng-sessiond[1097]: Warning: No kernel tracer available
   kernel: [  639.829710] PKCS#7 signature not signed with a trusted key
   kernel: [  639.843736] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0)
   kernel: [  639.843765] lttng_tracer: Unknown symbol lttng_hp_online (err 0)
   lttng-sessiond[1097]: Error: Unable to load required module 
lttng-ring-buffer-client-discard
   lttng-sessiond[1097]: Warning: No kernel tracer available

To manage notifications about this bug go to:
https://bugs.launchpad.net/lttng-modules/+bug/1778642/+subscriptions

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

[Kernel-packages] [Bug 1778642] Re: ubuntu_lttng_smoke_test failed on Azure 4.15

[Po-Hsu Lin]

** Description changed:

+ ***THIS IS A POTENTIAL REGRESSION***
+ 
+ This test will pass with the older kernel, 4.15.0-1013-azure, but not
+ the 4.15.0-1014-azure in -proposed.
+ 
  It looks like the kernel module can be installed, but four tests have
  failed:
  
  == lttng smoke test of session create/destroy ==
  Session test-kernel-session created.
  Traces will be written in /tmp/lttng-kernel-trace-14716-session
  PASSED (lttng create)
  Session test-kernel-session destroyed
  PASSED (lttng destroy)
  
  == lttng smoke test list kernel events ==
  FAILED (lttng list --kernel)
  FAILED (lttng list --kernel more output expected)
  
  == lttng smoke test trace open/close system calls ==
  Session test-kernel-session created.
  Traces will be written in /tmp/lttng-kernel-trace-14716-session
  PASSED (lttng create)
  FAILED (lttng enable-event)
  Session test-kernel-session destroyed
  
  == lttng smoke test trace context switches ==
  Session test-kernel-session created.
  Traces will be written in /tmp/lttng-kernel-trace-14716-session
  PASSED (lttng create)
  FAILED (lttng enable-event)
  Session test-kernel-session destroyed
  
  Summary: 4 passed, 4 failed
  
- 
  http://10.246.72.46/4.15.0-1014.14-azure/bionic-linux-azure-
  
azure-4.15.0-Standard_D12-ubuntu_lttng_smoke_test/ubuntu_lttng_smoke_test/results/ubuntu_lttng_smoke_test
  .lttng-smoke-test/debug/ubuntu_lttng_smoke_test.lttng-smoke-
  test.DEBUG.html
+ 
+ Error message from /var/log/syslog:
+ 
+  kernel: [  639.531889] PKCS#7 signature not signed with a trusted key
+  kernel: [  639.538251] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0)
+  kernel: [  639.538280] lttng_tracer: Unknown symbol lttng_hp_online (err 0)
+  lttng-sessiond[1097]: Error: Unable to load required module 
lttng-ring-buffer-client-discard
+  lttng-sessiond[1097]: Warning: No kernel tracer available
+  kernel: [  639.606845] PKCS#7 signature not signed with a trusted key
+  kernel: [  639.613331] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0)
+  kernel: [  639.613360] lttng_tracer: Unknown symbol lttng_hp_online (err 0)
+  lttng-sessiond[1097]: Error: Unable to load required module 
lttng-ring-buffer-client-discard
+  lttng-sessiond[1097]: Warning: No kernel tracer available
+  kernel: [  639.677124] PKCS#7 signature not signed with a trusted key
+  kernel: [  639.680857] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0)
+  kernel: [  639.680886] lttng_tracer: Unknown symbol lttng_hp_online (err 0)
+  lttng-sessiond[1097]: Error: Unable to load required module 
lttng-ring-buffer-client-discard
+  lttng-sessiond[1097]: Warning: No kernel tracer available
+  kernel: [  639.737914] PKCS#7 signature not signed with a trusted key
+  kernel: [  639.753366] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0)
+  kernel: [  639.753394] lttng_tracer: Unknown symbol lttng_hp_online (err 0)
+  lttng-sessiond[1097]: Error: Unable to load required module 
lttng-ring-buffer-client-discard
+  lttng-sessiond[1097]: Warning: No kernel tracer available
+  kernel: [  639.829710] PKCS#7 signature not signed with a trusted key
+  kernel: [  639.843736] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0)
+  kernel: [  639.843765] lttng_tracer: Unknown symbol lttng_hp_online (err 0)
+  lttng-sessiond[1097]: Error: Unable to load required module 
lttng-ring-buffer-client-discard
+  lttng-sessiond[1097]: Warning: No kernel tracer available

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

Title:
  ubuntu_lttng_smoke_test failed on Azure 4.15

Status in lttng-modules:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux-azure package in Ubuntu:
  New

Bug description:
  ***THIS IS A POTENTIAL REGRESSION***

  This test will pass with the older kernel, 4.15.0-1013-azure, but not
  the 4.15.0-1014-azure in -proposed.

  It looks like the kernel module can be installed, but four tests have
  failed:

  == lttng smoke test of session create/destroy ==
  Session test-kernel-session created.
  Traces will be written in /tmp/lttng-kernel-trace-14716-session
  PASSED (lttng create)
  Session test-kernel-session destroyed
  PASSED (lttng destroy)

  == lttng smoke test list kernel events ==
  FAILED (lttng list --kernel)
  FAILED (lttng list --kernel more output expected)

  == lttng smoke test trace open/close system calls ==
  Session test-kernel-session created.
  Traces will be written in /tmp/lttng-kernel-trace-14716-session
  PASSED (lttng create)
  FAILED (lttng enable-event)
  Session test-kernel-session destroyed

  == lttng smoke test trace context switches ==
  Session test-kernel-session created.
  Traces will be written in /tmp/lttng-kernel-trace-14716-session
  PASSED (lttng create)
  FAILED (lttng enable-event)
  Session test-kernel-session destroyed

  Summary: 4 passed, 4 failed

  http://10.246.72.46/4.15.0-1014.14-azure/bionic-linux-azure-
 

[Kernel-packages] [Bug 1768143] Re: vmxnet3: update to latest ToT

[Kleber Sacilotto de Souza]

Hi Ronak,

Which of the two kernels have you tested?

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

Title:
  vmxnet3: update to latest ToT

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

Bug description:
  == SRU Justification ==
  Recently, a couple of fixes went in vmxnet3 driver related to LRO, transmit
  reset and rxvlan disabled fix.  VMWare is requesting these fixes in
  Bionic and Xenial.

  A backport was needed to update version info in vmxnet3_int.h

  == Fixes ==
  7a4c003d6921 ("vmxnet3: avoid xmit reset due to a race in vmxnet3)"
  034f40579389 ("vmxnet3: use correct flag to indicate LRO feature")
  65ec0bd1c7c1 ("vmxnet3: fix incorrect dereference when rxvlan is disabled")

  == Regression Potential ==
  Low.  Limited to vmxnet3 driver.

  == Test Case ==
  A test kernel was built with these patches and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  Recently, a couple of fixes went in vmxnet3 driver related to LRO, transmit
  reset and rxvlan disabled fix. Below are the commits:

  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=7a4c003d6921e2af215f4790aa43a292bdc78be0

  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=034f405793897a3c8f642935f5494b86c340cde7

  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=65ec0bd1c7c14522670a5294de35710fb577a7fd

  This is a request to bring Ubuntu vmxnet3 driver up to date with ToT
  Linux kernel. Could you please backport it to 16.04 and 18.04 LTS releases?

  Thanks,
  Ronak

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

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

[Kernel-packages] [Bug 1776337] Re: linux-oem: 4.13.0-1031.35 -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/1776337

Title:
  linux-oem: 4.13.0-1031.35 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
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 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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1776333
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1769610] Re: Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

[Denis Turischev]

Hi,
I have an Intel Atom E3930 system, /dev/ttyS6 device node is no longer exposed 
to the userspace starting from 4.15+ Ubuntu kernels.

BTW, it works fine on Debian kernels, for example on 4.16.0-2-amd64

I've tried supposed linux-oem-4.15.0-1006.9 but device node is still
missing, although appears in /proc/tty/driver/serial

$ uname -r
4.15.0-1006-oem

$ sudo cat /proc/tty/driver/serial | grep -v unknown
serinfo:1.0 driver revision:
4: uart:16550A mmio:0x716000 irq:4 tx:0 rx:0
5: uart:16550A mmio:0x714000 irq:5 tx:0 rx:0 RTS|CTS|DTR
6: uart:16550A mmio:0x28000 irq:6 tx:0 rx:0 RTS|DTR
7: uart:16550A mmio:0x712000 irq:7 tx:0 rx:0 CTS

$ stat /dev/ttyS6
stat: cannot stat '/dev/ttyS6': No such file or directory

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

Title:
  Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

  On systems using Intel Atom (Baytrail-I) SoC's, slave devices connected on
  HSUART1/2 ports are described by the ACPI BIOS as virtual hardware using
  HID's INT3511/INT3512 [1].

  As a consequence, HW manufacturers have complete freedom to install any
  devices on-board as long as they can be accessed over serial tty
  interface. Once such device is Dell Edge 3002 IoT Gateway which sports
  ZigBee & GPS devices on the HS-UART ports 1 & 2 respectively.

  Post 4.15, with CONFIG_SERIAL_DEV_BUS=y, serdev port controller driver
  handles the enumeration for the slaves connected on these ports. Also,
  /dev/ttySx device nodes for these ports are no longer exposed to the
  userspace.

  This driver has been submitted upstream and is under review. This issue has
  been identified as a regression in 4.15 and multiple solutions are being
  explored. Meanwhile, to support customer and maintain release schedule,
  this driver needs to be in Ubuntu 4.15 based kernels.

  The impact is limited to systems based on Intel Atom E38XX (Baytrail-I)
  SoC's.

  More info:
  https://marc.info/?t=15245587167&r=1&w=2

  Please don't triage, this bug is for tracking purposes only.

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

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

[Kernel-packages] [Bug 1707409] Re: testsuite fails under qemu (SIGILL) works fine on real hw [missing getrandom 384 syscall]

[ Christian Ehrhardt ]

Setting qemu task to invalid per Colins explanation that the LP case
doesn't use it.

** Changed in: qemu (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  testsuite fails under qemu (SIGILL) works fine on real hw [missing
  getrandom 384 syscall]

Status in launchpad-buildd:
  New
Status in linux package in Ubuntu:
  Invalid
Status in qemu package in Ubuntu:
  Invalid

Bug description:
  Hello, after spending a lot of time debugging notmuch failure under
  armhf, we came to a conclusion:

  it started to fail when the infra moved to a new kernel 3.2 to a 4.2,
  and moved under qemu/kvm environment.

  the latest successful build is here  created on 2016-03-13
  https://launchpad.net/ubuntu/+source/notmuch/0.21-3ubuntu2/+build/9344826

  and the first bad is this one:  Started on 2016-08-31
  https://launchpad.net/ubuntu/+source/notmuch/0.22.1-2ubuntu1/+build/1062

  Kernel version: Linux kishi10 3.2.0-98-highbank #138-Ubuntu SMP PREEMPT Mon 
Jan 11 13:24:41 UTC 2016 armv7l
  Kernel version: Linux bos01-arm64-024 4.2.0-42-generic #49-Ubuntu SMP Tue Jun 
28 21:24:20 UTC 2016 aarch64

  so, in the first case armhf was ran on top of an armv7 kernel, in the other 
case it became an arm64 one
  this might not even be a regression in qemu/kvm, but rather a change in 
buildd system that spot a new bug

  doing a xenial build failed aswell, so I presume this is not a
  toolchain regression (also because it works fine on real HW), but a
  qemu/linux bug.

  I did run the test under strace/valgrind, I can't do much more testing, but I 
hope the logs can be useful for you
  
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+build/13169431
  
https://launchpadlibrarian.net/331134898/buildlog_ubuntu-artful-armhf.notmuch_0.25-2ubuntu1_BUILDING.txt.gz

  You can see the strace/valgrind outputs between "BEGIN" and "END"
  keywords

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad-buildd/+bug/1707409/+subscriptions

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

[Kernel-packages] [Bug 1776337] Re: linux-oem: 4.13.0-1031.35 -proposed tracker

[Po-Hsu Lin]

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

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

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

Title:
  linux-oem: 4.13.0-1031.35 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
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 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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1776333
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1775858] Re: hwclock test failed on Power9 system with Bionic kernel

[Po-Hsu Lin]

In this cycle the test failed with time difference:

TestFail: Failed to set hwclock back to Warthog's birthday. Output of
hwclock is '2004-10-20 04:09:59.590277+'

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

Title:
  hwclock test failed on Power9 system with Bionic kernel

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

Bug description:
  $ /sbin/hwclock --debug --set --date "2004/10/20 04:10:00"
  hwclock from util-linux 2.31.1
  System Time: 1528467313.266333
  Trying to open: /dev/rtc0
  No usable clock interface found.
  hwclock: Cannot access the Hardware Clock via any known method.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic ppc64le
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: ppc64el
  Date: Fri Jun  8 14:05:13 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcLoadAvg: 0.04 0.67 0.79 1/1401 6691
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -2
  ProcVersion: Linux version 4.15.0-22-generic (buildd@bos02-ppc64el-009) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #24-Ubuntu SMP Wed May 16 12:12:37 UTC 
2018
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDump_list: total 0
  cpu_cores: Number of cores present = 40
  cpu_coreson: Number of cores online = 40
  cpu_dscr: DSCR is 0
  cpu_freq:
   min: 2.796 GHz (cpu 79)
   max: 2.850 GHz (cpu 81)
   avg: 2.823 GHz
  cpu_runmode:
   Could not retrieve current diagnostics mode,
   No kernel interface to firmware
  cpu_smt: SMT=4

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

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

[Kernel-packages] [Bug 1775153] Re: fanotify09 in LTP syscall test failed with T/X/A kernel

[Po-Hsu Lin]

** Summary changed:

- fanotify09 in LTP syscall test failed with T/X/A/B kernel
+ fanotify09 in LTP syscall test failed with T/X/A 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/1775153

Title:
  fanotify09 in LTP syscall test failed with T/X/A kernel

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  The "fanotify09" from the LTP syscall tests has failed on a testing
  node with A/T kernel installed.

  Steps (with root):
    1. sudo apt-get install git xfsprogs -y
    2. git clone --depth=1 https://github.com/linux-test-project/ltp.git
    3. cd ltp
    4. make autotools
    5. ./configure
    6. make; make install
    7. cd /opt/ltp
    8. echo "fanotify09" > /tmp/jobs
    9. ./runltp -f /tmp/jobs

  <<>>
  tag=fanotify09 stime=1528192114
  cmdline="fanotify09"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s
  fanotify09.c:134: PASS: group 0 get event: mask 2 pid=43803 fd=9
  fanotify09.c:182: FAIL: group 1 got event
  fanotify09.c:182: FAIL: group 2 got event

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-43-generic 4.13.0-43.48
  ProcVersionSignature: User Name 4.13.0-43.48-generic 4.13.16
  Uname: Linux 4.13.0-43-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun  5 08:30 seq
   crw-rw 1 root audio 116, 33 Jun  5 08:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.9
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Jun  5 09:14:07 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Cavium ThunderX CRB
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 EFI VGA
   1 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic 
root=UUID=ddcb8b36-6267-4392-a1f9-74d9203b742e ro
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-43-generic N/A
   linux-backports-modules-4.13.0-43-generic  N/A
   linux-firmware 1.169.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 0
  dmi.chassis.vendor: Cavium
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd12/12/2012:svnCavium:pnThunderXCRB:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnCavium:ct0:cvrTobefilledbyO.E.M.:
  dmi.product.family: Default string
  dmi.product.name: ThunderX CRB
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Cavium

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

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

[Kernel-packages] [Bug 1775153] Re: fanotify09 in LTP syscall test failed with T/X/A/B kernel

[Po-Hsu Lin]

This issue has passed on Bionic in this cycle:

  <<>>
  tag=inotify09 stime=1529086352
  cmdline="inotify09"
  contacts=""
  analysis=exit
  <<>>
  tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s
  ../../../../include/tst_fuzzy_sync.h:109: INFO: avg_diff = 12ns, avg_dev = 
29ns, delay = 00076 loops
  ../../../../include/tst_fuzzy_sync.h:109: INFO: avg_diff = -5ns, avg_dev = 
22ns, delay = 00082 loops
  ../../../../include/tst_fuzzy_sync.h:109: INFO: avg_diff = 14ns, avg_dev = 
31ns, delay = 00072 loops
  ../../../../include/tst_fuzzy_sync.h:109: INFO: avg_diff = -44ns, avg_dev = 
36ns, delay = 00066 loops
  ../../../../include/tst_fuzzy_sync.h:109: INFO: avg_diff = 5ns, avg_dev = 
25ns, delay = 00054 loops
  ../../../../include/tst_fuzzy_sync.h:109: INFO: avg_diff = 4ns, avg_dev = 
10ns, delay = 00078 loops
  inotify09.c:117: PASS: kernel survived inotify beating
  
  Summary:
  passed   1
  failed   0
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=2 termination_type=exited termination_id=0 corefile=no
  cutime=125 cstime=120
  <<>>

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

Title:
  fanotify09 in LTP syscall test failed with T/X/A kernel

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  The "fanotify09" from the LTP syscall tests has failed on a testing
  node with A/T kernel installed.

  Steps (with root):
    1. sudo apt-get install git xfsprogs -y
    2. git clone --depth=1 https://github.com/linux-test-project/ltp.git
    3. cd ltp
    4. make autotools
    5. ./configure
    6. make; make install
    7. cd /opt/ltp
    8. echo "fanotify09" > /tmp/jobs
    9. ./runltp -f /tmp/jobs

  <<>>
  tag=fanotify09 stime=1528192114
  cmdline="fanotify09"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s
  fanotify09.c:134: PASS: group 0 get event: mask 2 pid=43803 fd=9
  fanotify09.c:182: FAIL: group 1 got event
  fanotify09.c:182: FAIL: group 2 got event

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-43-generic 4.13.0-43.48
  ProcVersionSignature: User Name 4.13.0-43.48-generic 4.13.16
  Uname: Linux 4.13.0-43-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun  5 08:30 seq
   crw-rw 1 root audio 116, 33 Jun  5 08:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.9
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Jun  5 09:14:07 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Cavium ThunderX CRB
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 EFI VGA
   1 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic 
root=UUID=ddcb8b36-6267-4392-a1f9-74d9203b742e ro
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-43-generic N/A
   linux-backports-modules-4.13.0-43-generic  N/A
   linux-firmware 1.169.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 0
  dmi.chassis.vendor: Cavium
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd12/12/2012:svnCavium:pnThunderXCRB:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnCavium:ct0:cvrTobefilledbyO.E.M.:
  dmi.product.family: Default string
  dmi.product.name: ThunderX CRB
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Cavium

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

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

[Kernel-packages] [Bug 1776340] Re: linux-oem: 4.15.0-1009.12 -proposed tracker

[Po-Hsu Lin]

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

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

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
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: 1776338
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1778851] Re: package linux-headers-4.15.0-23-generic 4.15.0-23.25 failed to install/upgrade: installed linux-headers-4.15.0-23-generic package post-installation script subproces

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-headers-4.15.0-23-generic 4.15.0-23.25 failed to
  install/upgrade: installed linux-headers-4.15.0-23-generic package
  post-installation script subprocess was killed by signal (Terminated)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've done update to 18.04 from 17.10

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-headers-4.15.0-23-generic 4.15.0-23.25
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kan1695 F pulseaudio
  Date: Wed Jun 27 07:54:34 2018
  ErrorMessage: installed linux-headers-4.15.0-23-generic package 
post-installation script subprocess was killed by signal (Terminated)
  InstallationDate: Installed on 2017-09-19 (281 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 1bcf:28c0 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 7560
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=9dca5be7-8f3d-4249-90e0-b2058e40d97d ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-headers-4.15.0-23-generic 4.15.0-23.25 failed to 
install/upgrade: installed linux-headers-4.15.0-23-generic package 
post-installation script subprocess was killed by signal (Terminated)
  UpgradeStatus: Upgraded to bionic on 2018-06-27 (0 days ago)
  dmi.bios.date: 01/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.4
  dmi.board.name: 07T996
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.4:bd01/31/2018:svnDellInc.:pnInspiron7560:pvr:rvnDellInc.:rn07T996:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7560
  dmi.sys.vendor: Dell Inc.

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

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  package linux-headers-4.15.0-23-generic 4.15.0-23.25 failed to
  install/upgrade: installed linux-headers-4.15.0-23-generic package
  post-installation script subprocess was killed by signal (Terminated)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've done update to 18.04 from 17.10

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-headers-4.15.0-23-generic 4.15.0-23.25
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kan1695 F pulseaudio
  Date: Wed Jun 27 07:54:34 2018
  ErrorMessage: installed linux-headers-4.15.0-23-generic package 
post-installation script subprocess was killed by signal (Terminated)
  InstallationDate: Installed on 2017-09-19 (281 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 1bcf:28c0 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 7560
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=9dca5be7-8f3d-4249-90e0-b2058e40d97d ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-headers-4.15.0-23-generic 4.15.0-23.25 failed to 
install/upgrade: installed linux-headers-4.15.0-23-generic package 
post-installation script subprocess was killed by signal (Terminated)
  UpgradeStatus: Upgraded to bionic on 2018-06-27 (0 days ago)
  dmi.bios.date: 01/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.4
  dmi.board.name: 07T996
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.4:bd01/31/2018:svnDellInc.:pnInspiron7560:pvr:rvnDellInc.:rn07T996:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7560
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1778658] Re: Nvidia fails after switching its mode

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Triaged

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

Title:
  Nvidia fails after switching its mode

Status in HWE Next:
  Triaged
Status in linux package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  Switch Nvidia mode requires rebooting the system. It's because of losing some 
of its status while switching mode if runtime PM is enabled. It's a generic 
issue that would happen on some other devices, too. This patch restores 
devices' config space on runtime resume.

  [Test]
  Test and verify it on machines with Nvidia discrete graphics.

  [Fix]
  Fix by saving and restoring config space over a runtime suspend cycle even if 
the device is not bound.

  [Regression Potential]
  Low. It saves and restores states during suspending and resuming.

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

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

[Kernel-packages] [Bug 1778851] [NEW] package linux-headers-4.15.0-23-generic 4.15.0-23.25 failed to install/upgrade: installed linux-headers-4.15.0-23-generic package post-installation script subproc

[Anatoly Kupriyanov]

Public bug reported:

I've done update to 18.04 from 17.10

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-headers-4.15.0-23-generic 4.15.0-23.25
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  kan1695 F pulseaudio
Date: Wed Jun 27 07:54:34 2018
ErrorMessage: installed linux-headers-4.15.0-23-generic package 
post-installation script subprocess was killed by signal (Terminated)
InstallationDate: Installed on 2017-09-19 (281 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 002: ID 1bcf:28c0 Sunplus Innovation Technology Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Inspiron 7560
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=9dca5be7-8f3d-4249-90e0-b2058e40d97d ro quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-headers-4.15.0-23-generic 4.15.0-23.25 failed to 
install/upgrade: installed linux-headers-4.15.0-23-generic package 
post-installation script subprocess was killed by signal (Terminated)
UpgradeStatus: Upgraded to bionic on 2018-06-27 (0 days ago)
dmi.bios.date: 01/31/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.5.4
dmi.board.name: 07T996
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.4:bd01/31/2018:svnDellInc.:pnInspiron7560:pvr:rvnDellInc.:rn07T996:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 7560
dmi.sys.vendor: Dell Inc.

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


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

Title:
  package linux-headers-4.15.0-23-generic 4.15.0-23.25 failed to
  install/upgrade: installed linux-headers-4.15.0-23-generic package
  post-installation script subprocess was killed by signal (Terminated)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've done update to 18.04 from 17.10

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-headers-4.15.0-23-generic 4.15.0-23.25
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kan1695 F pulseaudio
  Date: Wed Jun 27 07:54:34 2018
  ErrorMessage: installed linux-headers-4.15.0-23-generic package 
post-installation script subprocess was killed by signal (Terminated)
  InstallationDate: Installed on 2017-09-19 (281 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 1bcf:28c0 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 7560
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=9dca5be7-8f3d-4249-90e0-b2058e40d97d ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-headers-4.15.0-23-generic 4.15.0-23.25 failed to 
install/upgrade: installed linux-headers-4.15.0-23-generic package 
post-installation script subprocess was killed by signal (Terminated)
  UpgradeStatus: Upgraded to bionic on 2018-06-27 (0 days ago)
  dmi.bios.date: 01/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.4
  dmi.board.name: 07T996
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.

[Kernel-packages] [Bug 1775152] Re: Fix "Unable to handle kernel paging request" in AMD MP2 driver

[AceLan Kao]

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

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

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


** Tags added: verification-needed-xenial

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

Title:
  Fix "Unable to handle kernel paging request" in AMD MP2 driver

Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Committed

Bug description:
  ===SRU Justification===
  [Impact]
  Touchpad doesn't work after boot. Roughly 1/10 fail rate.

  [Test]
  With the patch, I no longer see the issue in 30 times reboot.

  [Fix]
  Factor out the pointer in the union, so the pointer value won't get changed 
by other union member.

  [Regression Potential]
  Low. It's specific to a single driver, which only enabled in OEM-A kernel.

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

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

[Kernel-packages] [Bug 1778772] Re: linux-gcp: 4.15.0-1010.10~16.04.1 -proposed tracker

[Łukasz Zemczak]

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

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

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

Title:
  linux-gcp: 4.15.0-1010.10~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:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.15.0-1010.10~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
  kernel-stable-master-bug: 1776333
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1762989] Re: Display Port issues - screen blackouts

[thet]

Unattached from this bug being closed because of inactivity I tried
again the DisplayPort adapter under kernel 4.17.3. That didn't work at
all, screen blackouts blinking from the beginning.

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

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

Title:
  Display Port issues - screen blackouts

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I use a Philips BDM4037U 40'', 4k monitor.
  Connecting it via DP to my Lenovo 910 4k gives me random blackouts.

  It appears to me that this mostly happens after some time of work,
  also more likely when the CPU has to handle more than average load,
  sooner in 30Hz than in 60Hz mode. But it happens for sure after some
  time, each day.

  I was unsure if this is a problem with the monitor itself (although when 
connected via HDMI this isn't an issue).
  I found similar bug reports for Windows, where it was suggested to update the 
firmware.
  My laptop has updated everything - a current BIOS (which dates back to June 
2017 or so), updated Windows, latest Ubuntu.
  The same problem existed in 17.10, with x-org and Wayland sessions.

  Note, there is another issue with this monitor filed by me, but
  unrelated AFAIK:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762986

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: 
boot/vmlinuz-4.15.0-13-generic]
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thet   1429 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 11 12:07:06 2018
  HibernationDevice: RESUME=UUID=bedd1248-32dd-43ca-be9f-28337086ea86
  InstallationDate: Installed on 2018-04-09 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  MachineType: LENOVO 80VF
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=998520ff-c841-45ab-8312-2bb876ae2a0b ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 2JCN39WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Agera
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 910-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr2JCN39WW:bd05/31/2017:svnLENOVO:pn80VF:pvrLenovoYOGA910-13IKB:rvnLENOVO:rnAgera:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA910-13IKB:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80VF
  dmi.product.version: Lenovo YOGA 910-13IKB
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1762989] Re: Display Port issues - screen blackouts

[thet]

If there is any more info I can provide, please let me know.

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

Title:
  Display Port issues - screen blackouts

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I use a Philips BDM4037U 40'', 4k monitor.
  Connecting it via DP to my Lenovo 910 4k gives me random blackouts.

  It appears to me that this mostly happens after some time of work,
  also more likely when the CPU has to handle more than average load,
  sooner in 30Hz than in 60Hz mode. But it happens for sure after some
  time, each day.

  I was unsure if this is a problem with the monitor itself (although when 
connected via HDMI this isn't an issue).
  I found similar bug reports for Windows, where it was suggested to update the 
firmware.
  My laptop has updated everything - a current BIOS (which dates back to June 
2017 or so), updated Windows, latest Ubuntu.
  The same problem existed in 17.10, with x-org and Wayland sessions.

  Note, there is another issue with this monitor filed by me, but
  unrelated AFAIK:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762986

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: 
boot/vmlinuz-4.15.0-13-generic]
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thet   1429 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 11 12:07:06 2018
  HibernationDevice: RESUME=UUID=bedd1248-32dd-43ca-be9f-28337086ea86
  InstallationDate: Installed on 2018-04-09 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  MachineType: LENOVO 80VF
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=998520ff-c841-45ab-8312-2bb876ae2a0b ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 2JCN39WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Agera
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 910-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr2JCN39WW:bd05/31/2017:svnLENOVO:pn80VF:pvrLenovoYOGA910-13IKB:rvnLENOVO:rnAgera:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA910-13IKB:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80VF
  dmi.product.version: Lenovo YOGA 910-13IKB
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1778844] Re: ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering crash, kdump is not working and system enters into initramfs state

[Andrew Cloke]

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

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

** Tags added: p9 triage-g

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

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

Title:
  ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering
  crash,kdump is not working and system enters into initramfs state

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

Bug description:
  Problem Description:
  ===
  After triggering crash ,kdump is not working & system enters into initramfs 
state

  Steps to re-create:
  ==

  >. woo is installed ubuntu180401 kernel

  root@woo:~# uname -a
  Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
  root@woo:~#

  >. Crashkernel value as below

  root@woo:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   503G2.0G501G 13M279M
499G
  Swap:  2.0G  0B2.0G

  root@woo:~# cat /proc/cmdline
  root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
crashkernel=8192M

  >  kdump status

  root@woo:~#  kdump-config status
  current state   : ready to kdump

  root@woo:~#  kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.15.0-23-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  root@woo:~# dmesg | grep Reser
  [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System 
RAM: 524288MB)
  [0.00] cma: Reserved 26224 MiB at 0x20399500
  [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The 
term "Broadcom" refers to Broadcom Limited and/or its subsidiaries.

  > Triggered crash

  root@woo:~# echo 1 > /proc/sys/kernel/sysrq
  root@woo:~# echo c > /proc/sysrq-trigger
  [   73.056308] sysrq: SysRq : Trigger a crash
  [   73.056357] Unable to handle kernel paging request for data at address 
0x
  [   73.056459] Faulting instruction address: 0xc07f24c8
  [   73.056543] Oops: Kernel access of bad area, sig: 11 [#1]
  [   73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV
  [   73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 
esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) 
mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx 
vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 
powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd 
auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables 
autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc 
ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink 
syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops 
nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc
  [   73.057601]  tg3 libahci nvme_core pnv_php
  [   73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G   OE
4.15.0-23-generic #25-Ubuntu
  [   73.057767] NIP:  c07f24c8 LR: c07f3568 CTR: 
c07f24a0
  [   73.057868] REGS: c03f8269f9f0 TRAP: 0300   Tainted: G   OE
 (4.15.0-23-generic)
  [   73.057986] MSR:  90009033   CR: 2822 
 XER: 2004
  [   73.058099] CFAR: c07f3564 DAR:  DSISR: 4200 
SOFTE: 1
  [   73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 
0063
  [   73.058099] GPR04: c03fef47ce18 c03fef494368 90009033 
31da0058
  [   73.058099] GPR08: 0007 0001  
90001003
  [   73.058099] GPR12: c07f24a0 c7a2e400 0e4fa497c900 

  [   73.058099] GPR16: 0e4f79cc94b0 0e4f79d567e0 0e4f79d88204 
0e4f79d56818
  [   73.058099] GPR20: 0e4f79d8d5d8 0001  
7efce644
  [   73.058099] GPR24: 7efce640 0e4f79d8afb4 c15e9aa8 
0002
  [   73.058099] GPR28: 0063 0004 c00