[Kernel-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

[Mathew Garland]

Ubuntu 18.04 
Mate & XFCE
Running Nvidia 390 - NVIDIA Corporation GM107M [GeForce GTX 850M] (rev a2)

Same issue faced here. Initially everything was running well until I
tried installing the CUDA libraries for Machine Learning purposes. This
was the start of this disaster.

This Issue should be considered a show stopper!

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

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

[Kernel-packages] [Bug 1773113] Re: nvidia-390 does not show GUI

[Mathew Garland]

Ubuntu 18.04
Mate & XFCE
Running Nvidia 390 - NVIDIA Corporation GM107M [GeForce GTX 850M] (rev a2)

Same issue faced here. Initially everything was running well until I
tried installing the CUDA libraries for Machine Learning purposes. This
was the start of this disaster.

This Issue should be considered a show stopper!

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

Title:
   nvidia-390 does not show GUI

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

Bug description:
  I know this bug is a duplicate, I am opening it because it seems that for # 
#1752053 it is marked as "Fix Released" although many people are still affected 
and complaining about it and nobody can or will change that status. So it is an 
attempt to raise more attention, as HDMI currently isn't usable for me on 
Ubuntu 18.04 (it affected me on 16.04 as well).
  Put in short, after Nvidia drivers are installed and I switch from Nvidia 
card to the intel one, the GUI can't be opened anymore

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

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

[Kernel-packages] [Bug 1780219] Re: xhci_pci module not workable regression

[andrew glaeser]

Last login: Fri Jul  6 07:49:13 2018 from 192.168.0.58
user@OptiPlex-580:~$ uname -a
Linux OptiPlex-580 4.18.0-041800rc3-generic #201807012030 SMP Mon Jul 2 
00:33:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
user@OptiPlex-580:~$ dmesg
[0.00] Linux version 4.18.0-041800rc3-generic (kernel@tangerine) (gcc 
version 7.3.0 (Ubuntu 7.3.0-24ubuntu1)) #201807012030 SMP Mon Jul 2 00:33:15 
UTC 2018
[0.00] Command line: BOOT_IMAGE=/vmlinuz-4.18.0-041800rc3-generic 
root=UUID=11ce9123-025c-4420-ba85-dee2799c0a2f ro rootflags=subvol=@ quiet 
splash vt.handoff=1
[0.00] KERNEL supported cpus:
[0.00]   Intel GenuineIntel
[0.00]   AMD AuthenticAMD
[0.00]   Centaur CentaurHauls
[0.00] x86/fpu: x87 FPU will use FXSAVE
[0.00] BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x000997ff] usable
[0.00] BIOS-e820: [mem 0x00099800-0x0009] reserved
[0.00] BIOS-e820: [mem 0x000e6000-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0xcfd4] usable
[0.00] BIOS-e820: [mem 0xcfd5-0xcfd5dfff] ACPI data
[0.00] BIOS-e820: [mem 0xcfd5e000-0xcfda7fff] ACPI NVS
[0.00] BIOS-e820: [mem 0xcfda8000-0xcfdd] reserved
[0.00] BIOS-e820: [mem 0xcfdec000-0xcfef] reserved
[0.00] BIOS-e820: [mem 0xfff0-0x] reserved
[0.00] BIOS-e820: [mem 0x0001-0x00011fff] usable
[0.00] NX (Execute Disable) protection: active
[0.00] SMBIOS 2.6 present.
[0.00] DMI: Dell Inc. OptiPlex 580/0YKH50, BIOS A05 06/16/2011
[0.00] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.00] e820: remove [mem 0x000a-0x000f] usable
[0.00] AGP: No AGP bridge found
[0.00] last_pfn = 0x12 max_arch_pfn = 0x4
[0.00] MTRR default type: uncachable
[0.00] MTRR fixed ranges enabled:
[0.00]   0-9 write-back
[0.00]   A-E uncachable
[0.00]   F-F write-protect
[0.00] MTRR variable ranges enabled:
[0.00]   0 base  mask 8000 write-back
[0.00]   1 base 8000 mask C000 write-back
[0.00]   2 base C000 mask F000 write-back
[0.00]   3 disabled
[0.00]   4 disabled
[0.00]   5 disabled
[0.00]   6 disabled
[0.00]   7 disabled
[0.00] TOM2: 00013000 aka 4864M
[0.00] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
[0.00] e820: update [mem 0xd000-0x] usable ==> reserved
[0.00] last_pfn = 0xcfd50 max_arch_pfn = 0x4
[0.00] found SMP MP-table at [mem 0x000ff780-0x000ff78f] mapped at 
[(ptrval)]
[0.00] Scanning 1 areas for low memory corruption
[0.00] Base memory trampoline at [(ptrval)] 93000 size 24576
[0.00] Using GB pages for direct mapping
[0.00] BRK [0x0815a000, 0x0815afff] PGTABLE
[0.00] BRK [0x0815b000, 0x0815bfff] PGTABLE
[0.00] BRK [0x0815c000, 0x0815cfff] PGTABLE
[0.00] BRK [0x0815d000, 0x0815dfff] PGTABLE
[0.00] BRK [0x0815e000, 0x0815efff] PGTABLE
[0.00] RAMDISK: [mem 0x31a77000-0x34d32fff]
[0.00] ACPI: Early table checksum verification disabled
[0.00] ACPI: RSDP 0x000FAD00 14 (v00 ACPIAM)
[0.00] ACPI: RSDT 0xCFD5 40 (v01 DELL   MC09 
20110616 MSFT 0097)
[0.00] ACPI: FACP 0xCFD50200 84 (v01 DELL   MC09 
20110616 MSFT 0097)
[0.00] ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has 
valid Length but zero Address: 0x/0x1 (20180531/tbfadt-624)
[0.00] ACPI: DSDT 0xCFD507C0 00600E (v01 D4330  D4330A05 
0A05 INTL 20051117)
[0.00] ACPI: FACS 0xCFD5E000 40
[0.00] ACPI: APIC 0xCFD50390 7C (v01 DELL   MC09 
20110616 MSFT 0097)
[0.00] ACPI: MCFG 0xCFD50410 3C (v01 DELL   MC09 
20110616 MSFT 0097)
[0.00] ACPI: SLIC 0xCFD50450 000176 (v01 DELL   MC09 
20110616 MSFT 0097)
[0.00] ACPI: OEMB 0xCFD5E040 72 (v01 DELL   MC09 
20110616 MSFT 0097)
[0.00] ACPI: HPET 0xCFD5A7C0 38 (v01 DELL   MC09 
20110616 MSFT 0097)
[0.00] ACPI: SSDT 0xCFD5A800 000672 (v01 A M I  POWERNOW 
0001 AMD  0001)
[0.00] ACPI: Local APIC address 0xfee0
[0.00] Scanning NUMA topology in Northbridge 24
[0.00] No NUMA configuration found
[0.00] Faking a node at [mem 0x-0x00011fff]
[0.00] NODE_DATA(0) allocated [mem 0x11ffd3000-0x11fffdfff]
[0.00] tsc: Fast TSC calibratio

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

[Nataraj]

I have tested 4.15.0-26-generic from the -proposed repository and it
runs fine under kvm/qemu.  The -24 version did not boot for me under
kvm/kemu.  Not sure if I am supposed to change the tag to verification-
done-bionic or if that is supposed to be done by the person who
originally filed the bug report.  The one that I filed got marked as a
duplicate.  Thank you for your support in resolving this issue.

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

Title:
  failure to boot with linux-image-4.15.0-24-generic

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

Bug description:
  This was the last OK then my 18.04 hangs after an update this morning.
  07:00 AM CEST

  Last Ok in boot was Started gnome display manager. dispatcher service
  .. tem changes.pp link was shut down

  Tried install lightdm from command line and the  response was lastest
  already installed.

  Probably it is what is coming after the lastest OK which is to be the
  error. And here I have lots of guesses..

  Any Ideas ? I need to do some work and I may not be waiting long.

  Search and browsed and now close to give up. Yeah it is a Lenovo.

  Guys: turn of auto update it is a machine killer.

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

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

[Kernel-packages] [Bug 1780219] Re: xhci_pci module not workable regression

[andrew glaeser]

Last login: Thu Jul  5 11:16:37 2018 from 192.168.0.58
user@OptiPlex-580:~$ wget 
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc3/linux-image-unsigned-4.18.0-041800rc3-generic_4.18.0-041800rc3.201807012030_amd64.deb
--2018-07-06 07:50:20--  
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc3/linux-image-unsigned-4.18.0-041800rc3-generic_4.18.0-041800rc3.201807012030_amd64.deb
Resolving kernel.ubuntu.com (kernel.ubuntu.com)... 91.189.94.216
Connecting to kernel.ubuntu.com (kernel.ubuntu.com)|91.189.94.216|:80... 
connected.
HTTP request sent, awaiting response... 200 OK
Length: 8124800 (7,7M) [application/x-debian-package]
Saving to: 
‘linux-image-unsigned-4.18.0-041800rc3-generic_4.18.0-041800rc3.201807012030_amd64.deb’

linux-image-unsigned- 100%[=>]   7,75M  5,04MB/s
in 1,5s

2018-07-06 07:50:22 (5,04 MB/s) - ‘linux-image-
unsigned-4.18.0-041800rc3-generic_4.18.0-041800rc3.201807012030_amd64.deb’
saved [8124800/8124800]

user@OptiPlex-580:~$ wget 
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc3/linux-modules-4.18.0-041800rc3-generic_4.18.0-041800rc3.201807012030_amd64.deb
--2018-07-06 07:51:08--  
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc3/linux-modules-4.18.0-041800rc3-generic_4.18.0-041800rc3.201807012030_amd64.deb
Resolving kernel.ubuntu.com (kernel.ubuntu.com)... 91.189.94.216
Connecting to kernel.ubuntu.com (kernel.ubuntu.com)|91.189.94.216|:80... 
connected. 
HTTP request sent, awaiting response... 200 OK  

Length: 44567496 (43M) [application/x-debian-package]   

Saving to: 
‘linux-modules-4.18.0-041800rc3-generic_4.18.0-041800rc3.201807012030_amd64.deb’

 


linux-modules-4.18.0- 100%[=>]  42,50M  4,11MB/sin 
7,2s 


2018-07-06 07:51:15 (5,94 MB/s) - 
‘linux-modules-4.18.0-041800rc3-generic_4.18.0-041800rc3.201807012030_amd64.deb’
 saved [44567496/44567496]


user@OptiPlex-580:~$ sudo dpkg -i *.deb 

[sudo] password for user:   

Selecting previously unselected package 
linux-image-unsigned-4.18.0-041800rc3-generic.
(Reading database ... 233689 files and directories currently installed.)
Preparing to unpack 
linux-image-unsigned-4.18.0-041800rc3-generic_4.18.0-041800rc3.201807012030_amd64.deb
 ...
Unpacking linux-image-unsigned-4.18.0-041800rc3-generic 
(4.18.0-041800rc3.201807012030) ...
Selecting previously unselected package linux-modules-4.18.0-041800rc3-generic.
Preparing to unpack 
linux-modules-4.18.0-041800rc3-generic_4.18.0-041800rc3.201807012030_amd64.deb 
...
Unpacking linux-modules-4.18.0-041800rc3-generic 
(4.18.0-041800rc3.201807012030) ...
Setting up linux-modules-4.18.0-041800rc3-generic 
(4.18.0-041800rc3.201807012030) ...
Setting up linux-image-unsigned-4.18.0-041800rc3-generic 
(4.18.0-041800rc3.201807012030) ...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-4.15.0-23-generic
I: /initrd.img.old is now a symlink to boot/initrd.img-4.15.0-23-generic
I: /vmlinuz is now a symlink to boot/vmlinuz-4.18.0-041800rc3-generic
I: /initrd.img is now a symlink to boot/initrd.img-4.18.0-041800rc3-generic
Processing triggers for linux-image-unsigned-4.18.0-041800rc3-generic 
(4.18.0-041800rc3.201807012030) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.18.0-041800rc3-generic
/etc/kernel/postinst.d/zz-update-grub:
Generating grub configuration file ...
Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is 
set is no longer supported.
Found linux image: /boot/vmlinuz-4.18.0-041800rc3-generic
Found initrd image: /boot/initrd.img-4.18.0-041800rc3-generic
Found linux image: /boot/vmlinuz-4.15.0-23-generic
Found initrd image: /boot/initrd.img-4.15.0-23-generic
Found linux image: /boot/vmlinuz-4.15.0-20-generic
Found initrd image: /boot/initrd.img-4.15.0-20-generic
Found memtest86+ image: /memtest86+.elf
Found memtest86+ image: /memtest86+.bin
done
user@OptiPlex-580:~$

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

Title:
  xhci_pci module not workable regression

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a follow-up to this installation-report at Debian:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902870
  I am using Xubuntu-Mate, installed from Ubuntu-MAte 18.04-LTS
  This is a regression, because the Renesas-USB3-pcie adap

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

[Wes Newell]

After turning on developer options for pre-release upgrades and
installing a lot of stuff, I still have the same problem with the slow
boot on the 2 machines I updated. uname-a shows same as before.Is that
normal? I turned off developer stuff afterwards. Since 4.15.0-23 works
fine, should I just delete the -24 til this gets straightened out?

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

Title:
  failure to boot with linux-image-4.15.0-24-generic

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

Bug description:
  This was the last OK then my 18.04 hangs after an update this morning.
  07:00 AM CEST

  Last Ok in boot was Started gnome display manager. dispatcher service
  .. tem changes.pp link was shut down

  Tried install lightdm from command line and the  response was lastest
  already installed.

  Probably it is what is coming after the lastest OK which is to be the
  error. And here I have lots of guesses..

  Any Ideas ? I need to do some work and I may not be waiting long.

  Search and browsed and now close to give up. Yeah it is a Lenovo.

  Guys: turn of auto update it is a machine killer.

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

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

[Kernel-packages] [Bug 1752507] Re: add i915/glk_dmc_ver1_04.bin

[Anthony Wong]

** Changed in: linux-firmware (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  add i915/glk_dmc_ver1_04.bin

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Xenial:
  Fix Released
Status in linux-firmware source package in Artful:
  Fix Committed

Bug description:
  SRU Justification

  Impact: New firmware is needed to fix issues with S3 for i915 on
  Geminilake hardware.

  Fix: Add the mising firmware.

  Test Case: Test S3 on affected hardware.

  Regression Potential: Limited as the firmware is only loaded for
  specific hardware. Regressions are possible, but none are known, and
  the new firmware does fix a known problem.

  ---

  Intel Gemini Lake needs DMC firmware to fix some S3 issues on xenial.

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

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

[Kernel-packages] [Bug 1780374] [NEW] package nvidia-utils-390 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-340 340.1

[Karl I Lopes]

Public bug reported:

Crash occurred while installing the graphics driver. I am using Ubuntu
18.04 LTS. Desktop

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: nvidia-utils-390 (not installed)
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
AptOrdering:
 libcuda1-340:amd64: Remove
 nvidia-opencl-icd-340:amd64: Remove
 libnvidia-compute-390:amd64: Install
 nvidia-utils-390:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Thu Jul  5 20:54:18 2018
ErrorMessage: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is 
also in package nvidia-340 340.106-0ubuntu3
InstallationDate: Installed on 2018-07-06 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
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.2
SourcePackage: nvidia-graphics-drivers-390
Title: package nvidia-utils-390 (not installed) failed to install/upgrade: 
trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package 
nvidia-340 340.106-0ubuntu3
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  package nvidia-utils-390 (not installed) failed to install/upgrade:
  trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in
  package nvidia-340 340.106-0ubuntu3

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

Bug description:
  Crash occurred while installing the graphics driver. I am using Ubuntu
  18.04 LTS. Desktop

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-utils-390 (not installed)
  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
  AptOrdering:
   libcuda1-340:amd64: Remove
   nvidia-opencl-icd-340:amd64: Remove
   libnvidia-compute-390:amd64: Install
   nvidia-utils-390:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Jul  5 20:54:18 2018
  ErrorMessage: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is 
also in package nvidia-340 340.106-0ubuntu3
  InstallationDate: Installed on 2018-07-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  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.2
  SourcePackage: nvidia-graphics-drivers-390
  Title: package nvidia-utils-390 (not installed) failed to install/upgrade: 
trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package 
nvidia-340 340.106-0ubuntu3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1728238] Re: update-initramfs not adding i915 GuC firmware for Kaby Lake, firmware fails to load

[spike speigel]

So this is now broken again?

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

Title:
  update-initramfs not adding i915 GuC firmware for Kaby Lake, firmware
  fails to load

Status in initramfs-tools:
  Invalid
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  == SRU Justification ==
  This firmware was optional when the MODULE_FIRMWARE statements were
  removed in bug 1626740 by Bionic commit dc0f16f9b50.  The firmware is now
  available and in use, so these statements need to be added back.

  Without these statements, The i915 Kabylake GuC firmware is failing to load
  on boot, and generating dmesg errors.

  == Fix ==
  Revert Bionic commit dc0f16f9b5084e6be2b8c79f8c6cd499a3451791.

  == Regression Potential ==
  Low.  Adding a statement back that was removed by a SAUCE patch.

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

  
  == Original Bug Report ==
  The i915 Kabylake GuC firmware is failing to load on boot, and generating 
dmesg errors.  The Kabylake HuC firmware succeeds.  All files exist.  I've also 
verified the Kabylake GuC firmware matches the correct file size and md5 listed 
on 01.org.

  I then ran update-initramfs verbosely, and see that only
  /lib/firmware/i915/skl_guc_ver6_1.bin is being added.
  /lib/firmware/i915/bxt_guc_ver8_7.bin and
  /lib/firmware/i915/kbl_guc_ver9_14.bin seem to be ignored.

  I'm running a Dell XPS 13 9360 w/ Kabylake on Ubuntu 17.10 and
  initramfs-tools 0.125ubuntu12.  Perhaps Broxton systems might have the
  same issue?

  Output and logs:
  -

  ls -al /lib/firmware/i915/kbl_*

  -rw-r--r-- 1 root root   8616 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1_01.bin
  lrwxrwxrwx 1 root root 19 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1.bin -> kbl_dmc_ver1_01.bin
  -rw-r--r-- 1 root root 142656 Oct 20 21:12 
/lib/firmware/i915/kbl_guc_ver9_14.bin
  -rw-r--r-- 1 root root 218688 Aug 17 11:09 
/lib/firmware/i915/kbl_huc_ver02_00_1810.bin

  sudo cat /sys/kernel/debug/dri/0/i915_guc_load_status

  GuC firmware status:
  path: i915/kbl_guc_ver9_14.bin
  fetch: FAIL
  load: NONE
  version wanted: 9.14
  version found: 0.0
  header: offset is 0; size = 0
  uCode: offset is 0; size = 0
  RSA: offset is 0; size = 0

  GuC status 0x0001:
  Bootrom status = 0x0
  uKernel status = 0x0
  MIA Core status = 0x0

  Scratch registers:
  0: 0x0
  1: 0x0
  2: 0x0
  3: 0x0
  4: 0x0
  5: 0x0
  6: 0x0
  7: 0x0
  8: 0x0
  9: 0x0
  10: 0x0
  11: 0x0
  12: 0x0
  13: 0x0
  14: 0x0
  15: 0x0

  sudo cat /sys/kernel/debug/dri/0/i915_huc_load_status

  HuC firmware status:
  path: i915/kbl_huc_ver02_00_1810.bin
  fetch: SUCCESS
  load: SUCCESS
  version wanted: 2.0
  version found: 2.0
  header: offset is 0; size = 128
  uCode: offset is 128; size = 218304
  RSA: offset is 218432; size = 256

  HuC status 0x6000:

  dmesg

  [1.052879] hidraw: raw HID events driver (C) Jiri Kosina
  [1.056426] wmi_bus wmi_bus-PNP0C14:01: WQBC data block query control 
method not found
  [1.080320] rtsx_pci :3b:00.0: enabling device ( -> 0002)
  [1.082308] nvme nvme0: pci function :3c:00.0
  [1.095073] Setting dangerous option enable_guc_loading - tainting kernel
  [1.095075] Setting dangerous option enable_guc_submission - tainting 
kernel
  [1.097867] [drm] Memory usable by graphics device = 4078M
  [1.097869] checking generic (9000 1fb) vs hw (9000 1000)
  [1.097869] fb: switching to inteldrmfb from EFI VGA
  [1.097899] Console: switching to colour dummy device 80x25
  [1.098049] [drm] Replacing VGA console driver
  [1.104157] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [1.104157] [drm] Driver supports precise vblank timestamp query.
  [1.112506] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin 
(v1.1)
  [1.113055] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [1.284194] usb 1-1: new low-speed USB device number 2 using xhci_hcd
  [1.298572]  nvme0n1: p1 p2
  [1.433241] usb 1-1: New USB device found, idVendor=0d62, idProduct=001c
  [1.433242] usb 1-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [1.433243] usb 1-1: Product: USB+PS2 Keyboard
  [1.433244] usb 1-1: Manufacturer: Generic
  [1.446460] usbcore: registered new interface driver usbhid
  [1.446461] usbhid: USB HID core driver
  [1.448067] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:0D62:001C.0001/input/input7
  [1.508451] hid-generic 0003:0D62:001C.0001: input,hidraw0: USB HID v1.10 
Keyboard [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input0
 

[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension

[Kai-Heng Feng]

Martin,
Please file an new bug, since it's a different ethernet chip.

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

Title:
  r8169 ethernet card don't work after returning from suspension

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

Bug description:
  ===SRU Justification===
  [Impact]
  Ethernet r8169 stops working after system resumed from suspend.

  [Test]
  User confirmed these patches fix the issue. r8169 continues to work
  after resume from suspend.

  [Regression Potential]
  Medium. The fix is limited to one device, all patches are in mainline.
  The WOL default change might cause regression for users that depend on
  BIOS settings. We can advice them to use userspace tool (systemd,
  ethtool, etc.) instead.

  ===Original Bug Report===
  I have noticed that the network stopped working on my desktop after I've 
suspended the system and woke it up. On dmesg there are messages like:

  [  150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
  [  150.944101] do_IRQ: 3.37 No irq handler for vector
  [  150.944105] r8169 :01:00.0 enp1s0: link down
  [  150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready

  When using Xenial (from a different install), this problem is not
  happening. This is happening on Bionic.

  There are only two ways to restore connectivity:
  1) Reboot the system;
  2) Remove the r8169 module and reinsert it with modprobe.

  The motherboard is a AsRock H55M-LE and the Ethernet controller is:

  01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
  RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.172
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Mar  2 00:21:57 2018
  Dependencies:

  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-10-generic.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1153 F pulseaudio
   /dev/snd/controlC1:  usuario1153 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26'
     Mixer name : 'VIA VT1818S'
     Components : 'HDA:11060440,18492818,0010'
     Controls  : 40
     Simple ctrls  : 17
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27'
     Mixer name : 'ATI R6xx HDMI'
     Components : 'HDA:1002aa01,00aa0100,00100200'
     Controls  : 7
     Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
     Capabilities: pswitch pswitch-joined
     Playback channels: Mono
     Mono: Playback [on]
  CurrentDesktop: LXDE
  Dependencies:

  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux-firmware 1.172
  PackageArchitecture: all
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz 
root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  RfKill:

  Tags:  bionic
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: H55M-LE
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH55M-LE:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name

[Kernel-packages] [Bug 1774306] Re: enable mic-mute hotkey and led on Lenovo M820z and M920z

[Hui Wang]

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

Title:
  enable mic-mute hotkey and led on Lenovo M820z and M920z

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
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:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  M810z, M820z and M920z are Lenovo AIO machines, there is a mic-mute button 
with
  led on them, without this patch, the hotkey and led only works on M810z, if we
  want 820z and 920z to work, we need to add their subsystem id in the driver, 
but
  since they use same codec with same pin conf, we use a better way than adding 
id.

  [Fix]
  With this patch, all 3 machines applied ALC233_FIXUP_LENOVO_LINE2_MIC_HOTKEY.

  [Test Case]
  press mic-mute button, then check sound-setting, we found the input will mute 
or
  unmute as users press button, and led will on or off to indicate the input 
status.

  [Regression Potential]
  Very low, through the strictly match the pin conf, codec id and vendor id, 
this
  fix only apply to M810z, M820z and M920z.

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

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

[Kernel-packages] [Bug 1779817] Re: no internet after suspending

[Kai-Heng Feng]

Jan, does you issue fixed by mainline kernel v4.18-rc3?

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

Title:
  no internet after suspending

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When my computer wakes up from suspending, there's no internet. Unplugging 
and replugging cable doesn't work, restarting network service doesn't work 
also. Only after restarting the computer, internet comes back.
  It only started happening after I freshly installed Ubuntu Budgie (18.04) and 
did all the system updates. Before I was using Ubuntu with Unity (16.04) and 
there was no problems with my internet.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-24-generic 4.15.0-24.26
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  minihydra   2085 F pulseaudio
   /dev/snd/controlC0:  minihydra   2085 F pulseaudio
   /dev/snd/controlC1:  minihydra   2085 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Tue Jul  3 10:13:19 2018
  HibernationDevice: RESUME=UUID=3747bab8-c258-4600-bc24-5d1f56a642dd
  InstallationDate: Installed on 2018-07-02 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=a5ceb36e-76f7-4bd4-a37b-0b91b995c635 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/28/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A77T
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2103:bd06/28/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A77T:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1779476] Re: Boot process hangs indefinitely. Never finishes.

[Daniel van Vugt]

Someone please test:
https://packages.debian.org/sid/amd64/plymouth/download

If that fixes the problem then we know how to proceed.

** Summary changed:

- Ubuntu 18.04:  gdm3 does not switch to graphics after update
+ Boot process hangs indefinitely. Never finishes.

** Changed in: plymouth (Ubuntu)
Milestone: None => ubuntu-18.04.1

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

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

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

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

Title:
  Boot process hangs indefinitely. Never finishes.

Status in gdm3 package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in plymouth package in Ubuntu:
  Incomplete
Status in plymouth package in Debian:
  Unknown

Bug description:
  After update of gdm and kernel gdm3 no longer enables graphics.

  What happens:
  =
  With and without:
 WaylandEnable=false
  in /etc/gdm3/custom.conf
  gdm3 does not switch to graphics.
  In both cases I case the X process running (Xwayland or Xorg) but no vt has 
it.
  lightdm does work, but barely. It takes up to a minute to get to the login 
screen.

  What I expected to happen:
  ==
  gdm3 switching to graphics in ~20 after boot like pre-update.

  Release:
  
  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  $ apt-cache policy kernel-common gdm3 lightdm xorg xwayland
  kernel-common:
Installed: (none)
Candidate: 13.018+nmu1
Version table:
   13.018+nmu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
  gdm3:
Installed: 3.28.2-0ubuntu1.3
Candidate: 3.28.2-0ubuntu1.3
Version table:
   *** 3.28.2-0ubuntu1.3 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.2-0ubuntu1.2 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
   3.28.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  lightdm:
Installed: 1.26.0-0ubuntu1
Candidate: 1.26.0-0ubuntu1
Version table:
   *** 1.26.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status
  xorg:
Installed: 1:7.7+19ubuntu7
Candidate: 1:7.7+19ubuntu7
Version table:
   *** 1:7.7+19ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  xwayland:
Installed: 2:1.19.6-1ubuntu4
Candidate: 2:1.19.6-1ubuntu4
Version table:
   *** 2:1.19.6-1ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status


  
  Attaching journalctl -b.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-27 (673 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NonfreeKernelModules: wl
  Package: gdm3 3.28.2-0ubuntu1.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Tags:  bionic package-from-proposed
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-27 (674 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NonfreeKernelModules: wl
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Tags:  bionic package-from-proposed
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.gdm3.custom.conf: [modified]
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424

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

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

[Kernel-packages] [Bug 1774306] Re: enable mic-mute hotkey and led on Lenovo M820z and M920z

[AceLan Kao]

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

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

Title:
  enable mic-mute hotkey and led on Lenovo M820z and M920z

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
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:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  M810z, M820z and M920z are Lenovo AIO machines, there is a mic-mute button 
with
  led on them, without this patch, the hotkey and led only works on M810z, if we
  want 820z and 920z to work, we need to add their subsystem id in the driver, 
but
  since they use same codec with same pin conf, we use a better way than adding 
id.

  [Fix]
  With this patch, all 3 machines applied ALC233_FIXUP_LENOVO_LINE2_MIC_HOTKEY.

  [Test Case]
  press mic-mute button, then check sound-setting, we found the input will mute 
or
  unmute as users press button, and led will on or off to indicate the input 
status.

  [Regression Potential]
  Very low, through the strictly match the pin conf, codec id and vendor id, 
this
  fix only apply to M810z, M820z and M920z.

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

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

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

[Daniel van Vugt]

I agree, if plymouth turns out to be the real problem then no kernel
change is necessary. Changing the kernel would be only a workaround for
the plymouth hang.

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

Title:
  failure to boot with linux-image-4.15.0-24-generic

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

Bug description:
  This was the last OK then my 18.04 hangs after an update this morning.
  07:00 AM CEST

  Last Ok in boot was Started gnome display manager. dispatcher service
  .. tem changes.pp link was shut down

  Tried install lightdm from command line and the  response was lastest
  already installed.

  Probably it is what is coming after the lastest OK which is to be the
  error. And here I have lots of guesses..

  Any Ideas ? I need to do some work and I may not be waiting long.

  Search and browsed and now close to give up. Yeah it is a Lenovo.

  Guys: turn of auto update it is a machine killer.

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

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

[Kernel-packages] [Bug 1779476] Re: Ubuntu 18.04: gdm3 does not switch to graphics after update

[Mark]

Bug #1779827 appears to be a duplicate of this.

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

Title:
  Ubuntu 18.04:  gdm3 does not switch to graphics after update

Status in gdm3 package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in plymouth package in Ubuntu:
  Incomplete
Status in plymouth package in Debian:
  Unknown

Bug description:
  After update of gdm and kernel gdm3 no longer enables graphics.

  What happens:
  =
  With and without:
 WaylandEnable=false
  in /etc/gdm3/custom.conf
  gdm3 does not switch to graphics.
  In both cases I case the X process running (Xwayland or Xorg) but no vt has 
it.
  lightdm does work, but barely. It takes up to a minute to get to the login 
screen.

  What I expected to happen:
  ==
  gdm3 switching to graphics in ~20 after boot like pre-update.

  Release:
  
  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  $ apt-cache policy kernel-common gdm3 lightdm xorg xwayland
  kernel-common:
Installed: (none)
Candidate: 13.018+nmu1
Version table:
   13.018+nmu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
  gdm3:
Installed: 3.28.2-0ubuntu1.3
Candidate: 3.28.2-0ubuntu1.3
Version table:
   *** 3.28.2-0ubuntu1.3 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.2-0ubuntu1.2 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
   3.28.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  lightdm:
Installed: 1.26.0-0ubuntu1
Candidate: 1.26.0-0ubuntu1
Version table:
   *** 1.26.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status
  xorg:
Installed: 1:7.7+19ubuntu7
Candidate: 1:7.7+19ubuntu7
Version table:
   *** 1:7.7+19ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  xwayland:
Installed: 2:1.19.6-1ubuntu4
Candidate: 2:1.19.6-1ubuntu4
Version table:
   *** 2:1.19.6-1ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status


  
  Attaching journalctl -b.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-27 (673 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NonfreeKernelModules: wl
  Package: gdm3 3.28.2-0ubuntu1.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Tags:  bionic package-from-proposed
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-27 (674 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NonfreeKernelModules: wl
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Tags:  bionic package-from-proposed
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.gdm3.custom.conf: [modified]
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424

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

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

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

[Mark]

This appears to be a duplicate of bug #1779476.

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

Title:
  failure to boot with linux-image-4.15.0-24-generic

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

Bug description:
  This was the last OK then my 18.04 hangs after an update this morning.
  07:00 AM CEST

  Last Ok in boot was Started gnome display manager. dispatcher service
  .. tem changes.pp link was shut down

  Tried install lightdm from command line and the  response was lastest
  already installed.

  Probably it is what is coming after the lastest OK which is to be the
  error. And here I have lots of guesses..

  Any Ideas ? I need to do some work and I may not be waiting long.

  Search and browsed and now close to give up. Yeah it is a Lenovo.

  Guys: turn of auto update it is a machine killer.

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

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

[Kernel-packages] [Bug 1770475] Re: linux 4.15.0-21-generic messes up plymouth and no logo on luks password prompt

[Daniel van Vugt]

Please run:

  apport-collect 1770475

on the machine. If you can't then please describe in more detail why the
command isn't working.

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

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

** Changed in: kubuntu-settings (Ubuntu)
   Status: New => Incomplete

** Changed in: kubuntu-default-settings (Ubuntu)
   Status: New => Incomplete

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

Title:
   linux 4.15.0-21-generic messes up plymouth and no logo on luks
  password prompt

Status in kubuntu-default-settings package in Ubuntu:
  Incomplete
Status in kubuntu-settings package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in plymouth package in Ubuntu:
  Incomplete

Bug description:
  Old problem with 4.15.0-20-generic:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768647

  New problem with 4.15.0-21-generic: installing packages as specified
  in mentioned bug, the kde logo does not display properly at password
  prompt for luks. See attachment.

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

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

[Kernel-packages] [Bug 1779476] Re: Ubuntu 18.04: gdm3 does not switch to graphics after update

[Daniel van Vugt]

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

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

** Also affects: gdm3 (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897572
   Importance: Unknown
   Status: Unknown

** Package changed: gdm3 (Debian) => plymouth (Debian)

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

Title:
  Ubuntu 18.04:  gdm3 does not switch to graphics after update

Status in gdm3 package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in plymouth package in Ubuntu:
  Incomplete
Status in plymouth package in Debian:
  Unknown

Bug description:
  After update of gdm and kernel gdm3 no longer enables graphics.

  What happens:
  =
  With and without:
 WaylandEnable=false
  in /etc/gdm3/custom.conf
  gdm3 does not switch to graphics.
  In both cases I case the X process running (Xwayland or Xorg) but no vt has 
it.
  lightdm does work, but barely. It takes up to a minute to get to the login 
screen.

  What I expected to happen:
  ==
  gdm3 switching to graphics in ~20 after boot like pre-update.

  Release:
  
  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  $ apt-cache policy kernel-common gdm3 lightdm xorg xwayland
  kernel-common:
Installed: (none)
Candidate: 13.018+nmu1
Version table:
   13.018+nmu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
  gdm3:
Installed: 3.28.2-0ubuntu1.3
Candidate: 3.28.2-0ubuntu1.3
Version table:
   *** 3.28.2-0ubuntu1.3 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.2-0ubuntu1.2 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
   3.28.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  lightdm:
Installed: 1.26.0-0ubuntu1
Candidate: 1.26.0-0ubuntu1
Version table:
   *** 1.26.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status
  xorg:
Installed: 1:7.7+19ubuntu7
Candidate: 1:7.7+19ubuntu7
Version table:
   *** 1:7.7+19ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  xwayland:
Installed: 2:1.19.6-1ubuntu4
Candidate: 2:1.19.6-1ubuntu4
Version table:
   *** 2:1.19.6-1ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status


  
  Attaching journalctl -b.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-27 (673 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NonfreeKernelModules: wl
  Package: gdm3 3.28.2-0ubuntu1.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Tags:  bionic package-from-proposed
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-27 (674 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NonfreeKernelModules: wl
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Tags:  bionic package-from-proposed
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.gdm3.custom.conf: [modified]
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424

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

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

[Kernel-packages] [Bug 1779476] Re: Ubuntu 18.04: gdm3 does not switch to graphics after update

[Daniel van Vugt]

Comment #34 indeed sounds like the problem.

Does installing this package fix the bug?;
https://packages.debian.org/sid/amd64/plymouth/download

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

Title:
  Ubuntu 18.04:  gdm3 does not switch to graphics after update

Status in gdm3 package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in plymouth package in Ubuntu:
  Incomplete
Status in plymouth package in Debian:
  Unknown

Bug description:
  After update of gdm and kernel gdm3 no longer enables graphics.

  What happens:
  =
  With and without:
 WaylandEnable=false
  in /etc/gdm3/custom.conf
  gdm3 does not switch to graphics.
  In both cases I case the X process running (Xwayland or Xorg) but no vt has 
it.
  lightdm does work, but barely. It takes up to a minute to get to the login 
screen.

  What I expected to happen:
  ==
  gdm3 switching to graphics in ~20 after boot like pre-update.

  Release:
  
  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  $ apt-cache policy kernel-common gdm3 lightdm xorg xwayland
  kernel-common:
Installed: (none)
Candidate: 13.018+nmu1
Version table:
   13.018+nmu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
  gdm3:
Installed: 3.28.2-0ubuntu1.3
Candidate: 3.28.2-0ubuntu1.3
Version table:
   *** 3.28.2-0ubuntu1.3 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.2-0ubuntu1.2 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
   3.28.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  lightdm:
Installed: 1.26.0-0ubuntu1
Candidate: 1.26.0-0ubuntu1
Version table:
   *** 1.26.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status
  xorg:
Installed: 1:7.7+19ubuntu7
Candidate: 1:7.7+19ubuntu7
Version table:
   *** 1:7.7+19ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  xwayland:
Installed: 2:1.19.6-1ubuntu4
Candidate: 2:1.19.6-1ubuntu4
Version table:
   *** 2:1.19.6-1ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status


  
  Attaching journalctl -b.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-27 (673 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NonfreeKernelModules: wl
  Package: gdm3 3.28.2-0ubuntu1.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Tags:  bionic package-from-proposed
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-27 (674 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NonfreeKernelModules: wl
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Tags:  bionic package-from-proposed
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.gdm3.custom.conf: [modified]
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424

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

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

[Kernel-packages] [Bug 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume

[Daniel van Vugt]

Thanks. Someone also needs to scroll up and change the tag from
verification-needed-bionic to verification-done-bionic. Ideally someone
who has verified the fix.

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

Title:
   bluez regression: Bluetooth audio fails to reconnect after resume

Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Bionic:
  Fix Committed
Status in bluez package in Fedora:
  Fix Released
Status in Suse:
  Fix Released

Bug description:
  [Impact]

  Users of Bluetooth audio have no sound after they suspend and resume
  the system.

  [Test Case]

   1. Connect to Bluetooth audio device
   2. Suspend & Resume
   3. Reconnect to Bluetooth device.

  [Regression Potential]

  Low. Although common Bluetooth code is modified in the fix, it has
  been released as a patch in other distros for some time already.

  [Other Info]

  Already released to cosmic as part of bluez version 5.50.

  This regression in bluez 5.48 has already been identified and fixed
  upstream. Report is here  and patch is here
  
.

  Syslog reports messages as follows when this issue is happening (I have 
replaced my device's MAC address with [MAC]):
  Mar 28 12:34:29 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:29 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 28 12:34:33 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:33 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments

  Workaround is to run sudo systemctl restart bluetooth after resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 28 12:37:11 2018
  InstallationDate: Installed on 2018-03-23 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: 80:00:0B:C7:4D:1C  ACL MTU: 310:10  SCO MTU: 64:8
    UP RUNNING PSCAN
    RX bytes:5025 acl:32 sco:0 events:202 errors:0
    TX bytes:5785 acl:32 sco:0 commands:103 errors:0

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

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

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

[Kristijan Žic ]

Any workaround besides the haveged? haveged didn't work for me.

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

Title:
  failure to boot with linux-image-4.15.0-24-generic

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

Bug description:
  This was the last OK then my 18.04 hangs after an update this morning.
  07:00 AM CEST

  Last Ok in boot was Started gnome display manager. dispatcher service
  .. tem changes.pp link was shut down

  Tried install lightdm from command line and the  response was lastest
  already installed.

  Probably it is what is coming after the lastest OK which is to be the
  error. And here I have lots of guesses..

  Any Ideas ? I need to do some work and I may not be waiting long.

  Search and browsed and now close to give up. Yeah it is a Lenovo.

  Guys: turn of auto update it is a machine killer.

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

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

[Kernel-packages] [Bug 1780112] Re: linux: 4.15.0-26.28 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   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/1780112

Title:
  linux: 4.15.0-26.28 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow snap-certification-testing series:
  New
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:
  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 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

  backports: bug 1780120 (linux-azure), bug 1780122 (linux-azure-edge), bug 
1780124 (linux-gcp), bug 1780126 (linux-hwe), bug 1780128 (linux-hwe-edge)
  derivatives: bug 1780113 (linux-raspi2), bug 1780114 (linux-oem), bug 1780115 
(linux-aws), bug 1780117 (linux-azure), bug 1780118 (linux-gcp), bug 1780119 
(linux-kvm)
  -- 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/1780112/+subscriptions

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

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

[Alan Van Art]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1780358/+attachment/5160248/+files/PulseList.txt

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

Title:
  4.15.0-24 kernel doesn't return from sleep mode

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux Mint 18.3 Cinnamon Lenovo Thinkpad Yoga 11e doesn't return from sleep 
mode after updating from 4.13.0-45 kernel to 4.15.0-24. The power light never 
indicates that the laptop is in sleep mode in the first place (it usually 
blinks). Then it won't wake up, black screen, ctrl-alt-f1 ctrl-alt-f8 have no 
effect. Must force power off and restart.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alan   1315 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=1b994e5a-820b-4d88-90e8-574ba5c5a3c2
  InstallationDate: Installed on 2018-04-13 (83 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: LENOVO 
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-45-generic 
root=UUID=c8750a76-04e5-4a28-a47d-9c8682606471 ro quiet splash 
intel_idle.max_cstate=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-45-generic N/A
   linux-backports-modules-4.13.0-45-generic  N/A
   linux-firmware 1.157.19
  Tags:  sylvia
  Uname: Linux 4.13.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom crontab dialout dip disk lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/17/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N15ET66W (1.26)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrN15ET66W(1.26):bd12/17/2015:svnLENOVO:pn:pvrThinkPadYoga11e:rvnLENOVO:rn:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad Yoga 11e
  dmi.product.name: 
  dmi.product.version: ThinkPad Yoga 11e
  dmi.sys.vendor: LENOVO

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

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

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

[Alan Van Art]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1780358/+attachment/5160250/+files/UdevDb.txt

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

Title:
  4.15.0-24 kernel doesn't return from sleep mode

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux Mint 18.3 Cinnamon Lenovo Thinkpad Yoga 11e doesn't return from sleep 
mode after updating from 4.13.0-45 kernel to 4.15.0-24. The power light never 
indicates that the laptop is in sleep mode in the first place (it usually 
blinks). Then it won't wake up, black screen, ctrl-alt-f1 ctrl-alt-f8 have no 
effect. Must force power off and restart.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alan   1315 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=1b994e5a-820b-4d88-90e8-574ba5c5a3c2
  InstallationDate: Installed on 2018-04-13 (83 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: LENOVO 
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-45-generic 
root=UUID=c8750a76-04e5-4a28-a47d-9c8682606471 ro quiet splash 
intel_idle.max_cstate=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-45-generic N/A
   linux-backports-modules-4.13.0-45-generic  N/A
   linux-firmware 1.157.19
  Tags:  sylvia
  Uname: Linux 4.13.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom crontab dialout dip disk lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/17/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N15ET66W (1.26)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrN15ET66W(1.26):bd12/17/2015:svnLENOVO:pn:pvrThinkPadYoga11e:rvnLENOVO:rn:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad Yoga 11e
  dmi.product.name: 
  dmi.product.version: ThinkPad Yoga 11e
  dmi.sys.vendor: LENOVO

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

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

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

[Alan Van Art]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1780358/+attachment/5160242/+files/Lsusb.txt

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

Title:
  4.15.0-24 kernel doesn't return from sleep mode

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux Mint 18.3 Cinnamon Lenovo Thinkpad Yoga 11e doesn't return from sleep 
mode after updating from 4.13.0-45 kernel to 4.15.0-24. The power light never 
indicates that the laptop is in sleep mode in the first place (it usually 
blinks). Then it won't wake up, black screen, ctrl-alt-f1 ctrl-alt-f8 have no 
effect. Must force power off and restart.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alan   1315 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=1b994e5a-820b-4d88-90e8-574ba5c5a3c2
  InstallationDate: Installed on 2018-04-13 (83 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: LENOVO 
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-45-generic 
root=UUID=c8750a76-04e5-4a28-a47d-9c8682606471 ro quiet splash 
intel_idle.max_cstate=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-45-generic N/A
   linux-backports-modules-4.13.0-45-generic  N/A
   linux-firmware 1.157.19
  Tags:  sylvia
  Uname: Linux 4.13.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom crontab dialout dip disk lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/17/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N15ET66W (1.26)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrN15ET66W(1.26):bd12/17/2015:svnLENOVO:pn:pvrThinkPadYoga11e:rvnLENOVO:rn:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad Yoga 11e
  dmi.product.name: 
  dmi.product.version: ThinkPad Yoga 11e
  dmi.sys.vendor: LENOVO

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

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

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

[Alan Van Art]

apport information

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

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

Title:
  4.15.0-24 kernel doesn't return from sleep mode

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux Mint 18.3 Cinnamon Lenovo Thinkpad Yoga 11e doesn't return from sleep 
mode after updating from 4.13.0-45 kernel to 4.15.0-24. The power light never 
indicates that the laptop is in sleep mode in the first place (it usually 
blinks). Then it won't wake up, black screen, ctrl-alt-f1 ctrl-alt-f8 have no 
effect. Must force power off and restart.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alan   1315 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=1b994e5a-820b-4d88-90e8-574ba5c5a3c2
  InstallationDate: Installed on 2018-04-13 (83 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: LENOVO 
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-45-generic 
root=UUID=c8750a76-04e5-4a28-a47d-9c8682606471 ro quiet splash 
intel_idle.max_cstate=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-45-generic N/A
   linux-backports-modules-4.13.0-45-generic  N/A
   linux-firmware 1.157.19
  Tags:  sylvia
  Uname: Linux 4.13.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom crontab dialout dip disk lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/17/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N15ET66W (1.26)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrN15ET66W(1.26):bd12/17/2015:svnLENOVO:pn:pvrThinkPadYoga11e:rvnLENOVO:rn:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad Yoga 11e
  dmi.product.name: 
  dmi.product.version: ThinkPad Yoga 11e
  dmi.sys.vendor: LENOVO

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

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

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

[Alan Van Art]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1780358/+attachment/5160243/+files/ProcCpuinfo.txt

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

Title:
  4.15.0-24 kernel doesn't return from sleep mode

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux Mint 18.3 Cinnamon Lenovo Thinkpad Yoga 11e doesn't return from sleep 
mode after updating from 4.13.0-45 kernel to 4.15.0-24. The power light never 
indicates that the laptop is in sleep mode in the first place (it usually 
blinks). Then it won't wake up, black screen, ctrl-alt-f1 ctrl-alt-f8 have no 
effect. Must force power off and restart.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alan   1315 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=1b994e5a-820b-4d88-90e8-574ba5c5a3c2
  InstallationDate: Installed on 2018-04-13 (83 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: LENOVO 
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-45-generic 
root=UUID=c8750a76-04e5-4a28-a47d-9c8682606471 ro quiet splash 
intel_idle.max_cstate=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-45-generic N/A
   linux-backports-modules-4.13.0-45-generic  N/A
   linux-firmware 1.157.19
  Tags:  sylvia
  Uname: Linux 4.13.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom crontab dialout dip disk lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/17/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N15ET66W (1.26)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrN15ET66W(1.26):bd12/17/2015:svnLENOVO:pn:pvrThinkPadYoga11e:rvnLENOVO:rn:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad Yoga 11e
  dmi.product.name: 
  dmi.product.version: ThinkPad Yoga 11e
  dmi.sys.vendor: LENOVO

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

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

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

[Alan Van Art]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1780358/+attachment/5160238/+files/CRDA.txt

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

Title:
  4.15.0-24 kernel doesn't return from sleep mode

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux Mint 18.3 Cinnamon Lenovo Thinkpad Yoga 11e doesn't return from sleep 
mode after updating from 4.13.0-45 kernel to 4.15.0-24. The power light never 
indicates that the laptop is in sleep mode in the first place (it usually 
blinks). Then it won't wake up, black screen, ctrl-alt-f1 ctrl-alt-f8 have no 
effect. Must force power off and restart.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alan   1315 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=1b994e5a-820b-4d88-90e8-574ba5c5a3c2
  InstallationDate: Installed on 2018-04-13 (83 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: LENOVO 
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-45-generic 
root=UUID=c8750a76-04e5-4a28-a47d-9c8682606471 ro quiet splash 
intel_idle.max_cstate=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-45-generic N/A
   linux-backports-modules-4.13.0-45-generic  N/A
   linux-firmware 1.157.19
  Tags:  sylvia
  Uname: Linux 4.13.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom crontab dialout dip disk lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/17/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N15ET66W (1.26)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrN15ET66W(1.26):bd12/17/2015:svnLENOVO:pn:pvrThinkPadYoga11e:rvnLENOVO:rn:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad Yoga 11e
  dmi.product.name: 
  dmi.product.version: ThinkPad Yoga 11e
  dmi.sys.vendor: LENOVO

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

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

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

[Alan Van Art]

apport information

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

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

Title:
  4.15.0-24 kernel doesn't return from sleep mode

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux Mint 18.3 Cinnamon Lenovo Thinkpad Yoga 11e doesn't return from sleep 
mode after updating from 4.13.0-45 kernel to 4.15.0-24. The power light never 
indicates that the laptop is in sleep mode in the first place (it usually 
blinks). Then it won't wake up, black screen, ctrl-alt-f1 ctrl-alt-f8 have no 
effect. Must force power off and restart.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alan   1315 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=1b994e5a-820b-4d88-90e8-574ba5c5a3c2
  InstallationDate: Installed on 2018-04-13 (83 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: LENOVO 
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-45-generic 
root=UUID=c8750a76-04e5-4a28-a47d-9c8682606471 ro quiet splash 
intel_idle.max_cstate=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-45-generic N/A
   linux-backports-modules-4.13.0-45-generic  N/A
   linux-firmware 1.157.19
  Tags:  sylvia
  Uname: Linux 4.13.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom crontab dialout dip disk lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/17/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N15ET66W (1.26)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrN15ET66W(1.26):bd12/17/2015:svnLENOVO:pn:pvrThinkPadYoga11e:rvnLENOVO:rn:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad Yoga 11e
  dmi.product.name: 
  dmi.product.version: ThinkPad Yoga 11e
  dmi.sys.vendor: LENOVO

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

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

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

[Alan Van Art]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1780358/+attachment/5160246/+files/ProcInterrupts.txt

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

Title:
  4.15.0-24 kernel doesn't return from sleep mode

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux Mint 18.3 Cinnamon Lenovo Thinkpad Yoga 11e doesn't return from sleep 
mode after updating from 4.13.0-45 kernel to 4.15.0-24. The power light never 
indicates that the laptop is in sleep mode in the first place (it usually 
blinks). Then it won't wake up, black screen, ctrl-alt-f1 ctrl-alt-f8 have no 
effect. Must force power off and restart.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alan   1315 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=1b994e5a-820b-4d88-90e8-574ba5c5a3c2
  InstallationDate: Installed on 2018-04-13 (83 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: LENOVO 
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-45-generic 
root=UUID=c8750a76-04e5-4a28-a47d-9c8682606471 ro quiet splash 
intel_idle.max_cstate=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-45-generic N/A
   linux-backports-modules-4.13.0-45-generic  N/A
   linux-firmware 1.157.19
  Tags:  sylvia
  Uname: Linux 4.13.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom crontab dialout dip disk lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/17/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N15ET66W (1.26)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrN15ET66W(1.26):bd12/17/2015:svnLENOVO:pn:pvrThinkPadYoga11e:rvnLENOVO:rn:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad Yoga 11e
  dmi.product.name: 
  dmi.product.version: ThinkPad Yoga 11e
  dmi.sys.vendor: LENOVO

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

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

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

[Alan Van Art]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1780358/+attachment/5160240/+files/IwConfig.txt

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

Title:
  4.15.0-24 kernel doesn't return from sleep mode

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux Mint 18.3 Cinnamon Lenovo Thinkpad Yoga 11e doesn't return from sleep 
mode after updating from 4.13.0-45 kernel to 4.15.0-24. The power light never 
indicates that the laptop is in sleep mode in the first place (it usually 
blinks). Then it won't wake up, black screen, ctrl-alt-f1 ctrl-alt-f8 have no 
effect. Must force power off and restart.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alan   1315 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=1b994e5a-820b-4d88-90e8-574ba5c5a3c2
  InstallationDate: Installed on 2018-04-13 (83 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: LENOVO 
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-45-generic 
root=UUID=c8750a76-04e5-4a28-a47d-9c8682606471 ro quiet splash 
intel_idle.max_cstate=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-45-generic N/A
   linux-backports-modules-4.13.0-45-generic  N/A
   linux-firmware 1.157.19
  Tags:  sylvia
  Uname: Linux 4.13.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom crontab dialout dip disk lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/17/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N15ET66W (1.26)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrN15ET66W(1.26):bd12/17/2015:svnLENOVO:pn:pvrThinkPadYoga11e:rvnLENOVO:rn:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad Yoga 11e
  dmi.product.name: 
  dmi.product.version: ThinkPad Yoga 11e
  dmi.sys.vendor: LENOVO

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

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

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

[Alan Van Art]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1780358/+attachment/5160245/+files/ProcEnviron.txt

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

Title:
  4.15.0-24 kernel doesn't return from sleep mode

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux Mint 18.3 Cinnamon Lenovo Thinkpad Yoga 11e doesn't return from sleep 
mode after updating from 4.13.0-45 kernel to 4.15.0-24. The power light never 
indicates that the laptop is in sleep mode in the first place (it usually 
blinks). Then it won't wake up, black screen, ctrl-alt-f1 ctrl-alt-f8 have no 
effect. Must force power off and restart.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alan   1315 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=1b994e5a-820b-4d88-90e8-574ba5c5a3c2
  InstallationDate: Installed on 2018-04-13 (83 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: LENOVO 
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-45-generic 
root=UUID=c8750a76-04e5-4a28-a47d-9c8682606471 ro quiet splash 
intel_idle.max_cstate=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-45-generic N/A
   linux-backports-modules-4.13.0-45-generic  N/A
   linux-firmware 1.157.19
  Tags:  sylvia
  Uname: Linux 4.13.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom crontab dialout dip disk lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/17/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N15ET66W (1.26)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrN15ET66W(1.26):bd12/17/2015:svnLENOVO:pn:pvrThinkPadYoga11e:rvnLENOVO:rn:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad Yoga 11e
  dmi.product.name: 
  dmi.product.version: ThinkPad Yoga 11e
  dmi.sys.vendor: LENOVO

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

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

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

[Alan Van Art]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1780358/+attachment/5160239/+files/CurrentDmesg.txt

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

Title:
  4.15.0-24 kernel doesn't return from sleep mode

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux Mint 18.3 Cinnamon Lenovo Thinkpad Yoga 11e doesn't return from sleep 
mode after updating from 4.13.0-45 kernel to 4.15.0-24. The power light never 
indicates that the laptop is in sleep mode in the first place (it usually 
blinks). Then it won't wake up, black screen, ctrl-alt-f1 ctrl-alt-f8 have no 
effect. Must force power off and restart.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alan   1315 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=1b994e5a-820b-4d88-90e8-574ba5c5a3c2
  InstallationDate: Installed on 2018-04-13 (83 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: LENOVO 
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-45-generic 
root=UUID=c8750a76-04e5-4a28-a47d-9c8682606471 ro quiet splash 
intel_idle.max_cstate=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-45-generic N/A
   linux-backports-modules-4.13.0-45-generic  N/A
   linux-firmware 1.157.19
  Tags:  sylvia
  Uname: Linux 4.13.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom crontab dialout dip disk lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/17/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N15ET66W (1.26)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrN15ET66W(1.26):bd12/17/2015:svnLENOVO:pn:pvrThinkPadYoga11e:rvnLENOVO:rn:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad Yoga 11e
  dmi.product.name: 
  dmi.product.version: ThinkPad Yoga 11e
  dmi.sys.vendor: LENOVO

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

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

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

[Alan Van Art]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1780358/+attachment/5160244/+files/ProcCpuinfoMinimal.txt

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

Title:
  4.15.0-24 kernel doesn't return from sleep mode

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux Mint 18.3 Cinnamon Lenovo Thinkpad Yoga 11e doesn't return from sleep 
mode after updating from 4.13.0-45 kernel to 4.15.0-24. The power light never 
indicates that the laptop is in sleep mode in the first place (it usually 
blinks). Then it won't wake up, black screen, ctrl-alt-f1 ctrl-alt-f8 have no 
effect. Must force power off and restart.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alan   1315 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=1b994e5a-820b-4d88-90e8-574ba5c5a3c2
  InstallationDate: Installed on 2018-04-13 (83 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: LENOVO 
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-45-generic 
root=UUID=c8750a76-04e5-4a28-a47d-9c8682606471 ro quiet splash 
intel_idle.max_cstate=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-45-generic N/A
   linux-backports-modules-4.13.0-45-generic  N/A
   linux-firmware 1.157.19
  Tags:  sylvia
  Uname: Linux 4.13.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom crontab dialout dip disk lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/17/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N15ET66W (1.26)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrN15ET66W(1.26):bd12/17/2015:svnLENOVO:pn:pvrThinkPadYoga11e:rvnLENOVO:rn:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad Yoga 11e
  dmi.product.name: 
  dmi.product.version: ThinkPad Yoga 11e
  dmi.sys.vendor: LENOVO

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

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

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

[Alan Van Art]

apport information

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

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

Title:
  4.15.0-24 kernel doesn't return from sleep mode

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux Mint 18.3 Cinnamon Lenovo Thinkpad Yoga 11e doesn't return from sleep 
mode after updating from 4.13.0-45 kernel to 4.15.0-24. The power light never 
indicates that the laptop is in sleep mode in the first place (it usually 
blinks). Then it won't wake up, black screen, ctrl-alt-f1 ctrl-alt-f8 have no 
effect. Must force power off and restart.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alan   1315 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=1b994e5a-820b-4d88-90e8-574ba5c5a3c2
  InstallationDate: Installed on 2018-04-13 (83 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: LENOVO 
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-45-generic 
root=UUID=c8750a76-04e5-4a28-a47d-9c8682606471 ro quiet splash 
intel_idle.max_cstate=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-45-generic N/A
   linux-backports-modules-4.13.0-45-generic  N/A
   linux-firmware 1.157.19
  Tags:  sylvia
  Uname: Linux 4.13.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom crontab dialout dip disk lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/17/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N15ET66W (1.26)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrN15ET66W(1.26):bd12/17/2015:svnLENOVO:pn:pvrThinkPadYoga11e:rvnLENOVO:rn:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad Yoga 11e
  dmi.product.name: 
  dmi.product.version: ThinkPad Yoga 11e
  dmi.sys.vendor: LENOVO

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

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

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

[Alan Van Art]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1780358/+attachment/5160247/+files/ProcModules.txt

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

Title:
  4.15.0-24 kernel doesn't return from sleep mode

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux Mint 18.3 Cinnamon Lenovo Thinkpad Yoga 11e doesn't return from sleep 
mode after updating from 4.13.0-45 kernel to 4.15.0-24. The power light never 
indicates that the laptop is in sleep mode in the first place (it usually 
blinks). Then it won't wake up, black screen, ctrl-alt-f1 ctrl-alt-f8 have no 
effect. Must force power off and restart.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alan   1315 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=1b994e5a-820b-4d88-90e8-574ba5c5a3c2
  InstallationDate: Installed on 2018-04-13 (83 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: LENOVO 
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-45-generic 
root=UUID=c8750a76-04e5-4a28-a47d-9c8682606471 ro quiet splash 
intel_idle.max_cstate=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-45-generic N/A
   linux-backports-modules-4.13.0-45-generic  N/A
   linux-firmware 1.157.19
  Tags:  sylvia
  Uname: Linux 4.13.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom crontab dialout dip disk lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/17/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N15ET66W (1.26)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrN15ET66W(1.26):bd12/17/2015:svnLENOVO:pn:pvrThinkPadYoga11e:rvnLENOVO:rn:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad Yoga 11e
  dmi.product.name: 
  dmi.product.version: ThinkPad Yoga 11e
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1780358] Re: 4.15.0-24 kernel doesn't return from sleep mode

[Alan Van Art]

apport information

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

** Tags added: apport-collected sylvia

** Description changed:

- Linux Mint 18.3 Cinnamon Lenovo Thinkpad Yoga 11e doesn't return from
- sleep mode after updating from 4.13.0-45 kernel to 4.15.0-24. The power
- light never indicates that the laptop is in sleep mode in the first
- place (it usually blinks). Then it won't wake up, black screen, ctrl-
- alt-f1 ctrl-alt-f8 have no effect. Must force power off and restart.
+ Linux Mint 18.3 Cinnamon Lenovo Thinkpad Yoga 11e doesn't return from sleep 
mode after updating from 4.13.0-45 kernel to 4.15.0-24. The power light never 
indicates that the laptop is in sleep mode in the first place (it usually 
blinks). Then it won't wake up, black screen, ctrl-alt-f1 ctrl-alt-f8 have no 
effect. Must force power off and restart.
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.18
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  alan   1315 F pulseaudio
+ CurrentDesktop: X-Cinnamon
+ DistroRelease: Linux 18.3
+ HibernationDevice: RESUME=UUID=1b994e5a-820b-4d88-90e8-574ba5c5a3c2
+ InstallationDate: Installed on 2018-04-13 (83 days ago)
+ InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
+ MachineType: LENOVO 
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-45-generic 
root=UUID=c8750a76-04e5-4a28-a47d-9c8682606471 ro quiet splash 
intel_idle.max_cstate=1 vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
+ RelatedPackageVersions:
+  linux-restricted-modules-4.13.0-45-generic N/A
+  linux-backports-modules-4.13.0-45-generic  N/A
+  linux-firmware 1.157.19
+ Tags:  sylvia
+ Uname: Linux 4.13.0-45-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom crontab dialout dip disk lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 12/17/2015
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: N15ET66W (1.26)
+ dmi.board.asset.tag: Not Available
+ dmi.board.name: 
+ dmi.board.vendor: LENOVO
+ dmi.board.version: Not Defined
+ dmi.chassis.asset.tag: No Asset Information
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: Not Available
+ dmi.modalias: 
dmi:bvnLENOVO:bvrN15ET66W(1.26):bd12/17/2015:svnLENOVO:pn:pvrThinkPadYoga11e:rvnLENOVO:rn:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
+ dmi.product.family: ThinkPad Yoga 11e
+ dmi.product.name: 
+ dmi.product.version: ThinkPad Yoga 11e
+ dmi.sys.vendor: LENOVO

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1780358/+attachment/5160237/+files/AlsaInfo.txt

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

Title:
  4.15.0-24 kernel doesn't return from sleep mode

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux Mint 18.3 Cinnamon Lenovo Thinkpad Yoga 11e doesn't return from sleep 
mode after updating from 4.13.0-45 kernel to 4.15.0-24. The power light never 
indicates that the laptop is in sleep mode in the first place (it usually 
blinks). Then it won't wake up, black screen, ctrl-alt-f1 ctrl-alt-f8 have no 
effect. Must force power off and restart.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alan   1315 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=1b994e5a-820b-4d88-90e8-574ba5c5a3c2
  InstallationDate: Installed on 2018-04-13 (83 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: LENOVO 
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-45-generic 
root=UUID=c8750a76-04e5-4a28-a47d-9c8682606471 ro quiet splash 
intel_idle.max_cstate=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-45-generic N/A
   linux-backports-modules-4.13.0-45-generic  N/A
   linux-firmware 1.157.19
  Tags:  sylvia
  Uname: Linux 4.13.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom crontab dialout dip disk lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/17/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N15ET66W (1.26)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrN15ET66W(1.26):bd12/17/2015:svnLENOVO:p

[Kernel-packages] [Bug 1780115] Re: linux-aws: 4.15.0-1013.13 -proposed tracker

[Brad Figg]

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

** Tags added: block-proposed-bionic

** Tags added: block-proposed

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

Title:
  linux-aws: 4.15.0-1013.13 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow 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-aws package in Ubuntu:
  Invalid
Status in linux-aws 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: 1780112
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1780112] Re: linux: 4.15.0-26.28 -proposed tracker

[Brad Figg]

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

** Changed in: kernel-sru-workflow/certification-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 => Confirmed

** 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  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 1780120 (linux-azure), bug 1780122 (linux-azure-edge), bug 
1780124 (linux-gcp), bug 1780126 (linux-hwe), bug 1780128 (linux-hwe-edge)
  derivatives: bug 1780113 (linux-raspi2), bug 1780114 (linux-oem), bug 1780115 
(linux-aws), bug 1780117 (linux-azure), bug 1780118 (linux-gcp), bug 1780119 
(linux-kvm)
- kernel-stable-phase-changed:Wednesday, 04. July 2018 16:31 UTC
- kernel-stable-phase:Uploaded
- 
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Friday, 06. July 2018 00:31 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1780120 (linux-azure), bug 1780122 (linux-azure-edge), bug 
1780124 (linux-gcp), bug 1780126 (linux-hwe), bug 1780128 (linux-hwe-edge)
  derivatives: bug 1780113 (linux-raspi2), bug 1780114 (linux-oem), bug 1780115 
(linux-aws), bug 1780117 (linux-azure), bug 1780118 (linux-gcp), bug 1780119 
(linux-kvm)
  -- swm properties --
  boot-testing-requested: true
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Friday, 06. July 2018 00:31 UTC
+ bugs-spammed: true
+ 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1780112

Title:
  linux: 4.15.0-26.28 -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow snap-certification-testing series:
  New
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:
  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 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

  backports: bug 1780120 (linux-azure), bug 1780122 (linux-azure-edge), bug 
1780124 (linux-gcp), bug 1780126 (linux-hwe), bug 1780128 (linux-hwe-edge)
  derivatives: bug 1780113 (linux-raspi2), bug 1780114 (linux-oem), bug 1780115 
(linux-aws), bug 1780117 (linux-azure), bug 1780118 (linux-gcp), bug 1780119 
(linux-kvm)
  -- 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/1780112/+subscriptions

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

[Kernel-packages] [Bug 1779357] Re: linux-oem: 4.15.0-1010.13 -proposed tracker

[Brad Figg]

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

** Tags added: block-proposed-bionic

** Tags added: block-proposed

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-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: 1780112
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1780117] Re: linux-azure: 4.15.0-1016.16 -proposed tracker

[Brad Figg]

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

** Tags added: block-proposed-bionic

** Tags added: block-proposed

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

Title:
  linux-azure: 4.15.0-1016.16 -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 prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow 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 stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in 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: 1780112
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

[Brad Figg]

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

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

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


** Tags added: verification-needed-bionic

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

Title:
  failure to boot with linux-image-4.15.0-24-generic

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

Bug description:
  This was the last OK then my 18.04 hangs after an update this morning.
  07:00 AM CEST

  Last Ok in boot was Started gnome display manager. dispatcher service
  .. tem changes.pp link was shut down

  Tried install lightdm from command line and the  response was lastest
  already installed.

  Probably it is what is coming after the lastest OK which is to be the
  error. And here I have lots of guesses..

  Any Ideas ? I need to do some work and I may not be waiting long.

  Search and browsed and now close to give up. Yeah it is a Lenovo.

  Guys: turn of auto update it is a machine killer.

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

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

[Kernel-packages] [Bug 1780062] Re: Cloud-init causes potentially huge boot delays with 4.15 kernels

[Brad Figg]

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

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

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


** Tags added: verification-needed-bionic

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

Title:
  Cloud-init causes potentially huge boot delays with 4.15 kernels

Status in cloud-init package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in cloud-init source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  Newer 4.15 kernels contain the following fix for CVE-2018-1108:
43838a23a05fb ("random: fix crng_ready() test")

  This causes cloud-init to stall for a potentially long time during
  boot (waiting for entropy I presume). Google reported boot delays of
  75 minutes.

  I've tracked this down to the following import in templater.py which causes 
the delay:
  from jinja2 import Template as JTemplate

  Which is called when cc_update_etc_hosts is imported.

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

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

[Kernel-packages] [Bug 1780118] Re: linux-gcp: 4.15.0-1012.12 -proposed tracker

[Brad Figg]

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

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

Title:
  linux-gcp: 4.15.0-1012.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 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:
  Confirmed
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 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: 1780112
  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/1780118/+subscriptions

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

[Kernel-packages] [Bug 1780119] Re: linux-kvm: 4.15.0-1014.14 -proposed tracker

[Brad Figg]

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

** Tags added: block-proposed-bionic

** Tags added: block-proposed

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm 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: 1780112
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1780120] Re: linux-azure: 4.15.0-1016.16~16.04.1 -proposed tracker

[Brad Figg]

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

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

Title:
  linux-azure: 4.15.0-1016.16~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow 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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
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 stakeholder-signoff series:
  Confirmed
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 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: 1780112
  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/1780120/+subscriptions

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

[Kernel-packages] [Bug 1780124] Re: linux-gcp: 4.15.0-1012.12~16.04.2 -proposed tracker

[Brad Figg]

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

** Tags added: block-proposed-xenial

** Tags added: block-proposed

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

Title:
  linux-gcp: 4.15.0-1012.12~16.04.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow 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  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: 1780112
  phase: Uploaded

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1780358

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

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

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

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

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

Title:
  4.15.0-24 kernel doesn't return from sleep mode

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Linux Mint 18.3 Cinnamon Lenovo Thinkpad Yoga 11e doesn't return from
  sleep mode after updating from 4.13.0-45 kernel to 4.15.0-24. The
  power light never indicates that the laptop is in sleep mode in the
  first place (it usually blinks). Then it won't wake up, black screen,
  ctrl-alt-f1 ctrl-alt-f8 have no effect. Must force power off and
  restart.

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

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

[Kernel-packages] [Bug 1780358] [NEW] 4.15.0-24 kernel doesn't return from sleep mode

[Alan Van Art]

Public bug reported:

Linux Mint 18.3 Cinnamon Lenovo Thinkpad Yoga 11e doesn't return from
sleep mode after updating from 4.13.0-45 kernel to 4.15.0-24. The power
light never indicates that the laptop is in sleep mode in the first
place (it usually blinks). Then it won't wake up, black screen, ctrl-
alt-f1 ctrl-alt-f8 have no effect. Must force power off and restart.

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


** Tags: kernel-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/1780358

Title:
  4.15.0-24 kernel doesn't return from sleep mode

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Linux Mint 18.3 Cinnamon Lenovo Thinkpad Yoga 11e doesn't return from
  sleep mode after updating from 4.13.0-45 kernel to 4.15.0-24. The
  power light never indicates that the laptop is in sleep mode in the
  first place (it usually blinks). Then it won't wake up, black screen,
  ctrl-alt-f1 ctrl-alt-f8 have no effect. Must force power off and
  restart.

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

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

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

[Mark]

Reverting the fix for CVE-2018-1108 to get this to work is not necessary
and not a good idea. The root cause has been identified upstream in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897572 and fixes
committed.

Turns out it was fontconfig generating a uuid that tripped over the CVE
fix. One commited fix is to copy the necessary fonts to initramfs so
genuuid is not needed. Another is a fix to randutils. Those are the
changes that need to be pushed to Ubuntu users.

How did this regression ever get into an Ubuntu software update for the
masses?

** Bug watch added: Debian Bug tracker #897572
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897572

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

Title:
  failure to boot with linux-image-4.15.0-24-generic

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

Bug description:
  This was the last OK then my 18.04 hangs after an update this morning.
  07:00 AM CEST

  Last Ok in boot was Started gnome display manager. dispatcher service
  .. tem changes.pp link was shut down

  Tried install lightdm from command line and the  response was lastest
  already installed.

  Probably it is what is coming after the lastest OK which is to be the
  error. And here I have lots of guesses..

  Any Ideas ? I need to do some work and I may not be waiting long.

  Search and browsed and now close to give up. Yeah it is a Lenovo.

  Guys: turn of auto update it is a machine killer.

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

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

[Dorian Scholz]

Same problem on an IB8000 Atom Braswell board using 16.04.
Also shows the two ports when checking with acpidump, but the bionic OEM kernel 
mentioned here did not fix it when installed on my 16.04. It booted fine but no 
ttyS or ttyHS...
What really did the trick was the Debian 4.16.0-2 mentioned above as well. This 
one brought back the ports on the normal ttyS names on 16.04!

-- 
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 1752772] Re: r8169 ethernet card don't work after returning from suspension

[Martin Johnson]

Not 100% sure if this is exactly related to the RTL issue although it
does seem from the posts that other drivers are affected.

I am on an iMac late 2006 with sky2 module and I have also noticed
similar issue appear since 4.15.0-24-generic whereas before ethernet
worked rock solid on resume from suspend.

[1.886780] sky2: driver version 1.30
[1.886993] sky2 :02:00.0: Yukon-2 EC chip revision 2

uninstalling the sky2 module and reloading it brings it back into a
working state.

70% of the time it will fail on suspend / resume, dmesg also shows an
IRQ problem when the issue appears:

[ 7008.495941] do_IRQ: 1.35 No irq handler for vector

Previous kernels appear to work fine, so this is clearly something very
recently introduced.

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

Title:
  r8169 ethernet card don't work after returning from suspension

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

Bug description:
  ===SRU Justification===
  [Impact]
  Ethernet r8169 stops working after system resumed from suspend.

  [Test]
  User confirmed these patches fix the issue. r8169 continues to work
  after resume from suspend.

  [Regression Potential]
  Medium. The fix is limited to one device, all patches are in mainline.
  The WOL default change might cause regression for users that depend on
  BIOS settings. We can advice them to use userspace tool (systemd,
  ethtool, etc.) instead.

  ===Original Bug Report===
  I have noticed that the network stopped working on my desktop after I've 
suspended the system and woke it up. On dmesg there are messages like:

  [  150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
  [  150.944101] do_IRQ: 3.37 No irq handler for vector
  [  150.944105] r8169 :01:00.0 enp1s0: link down
  [  150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready

  When using Xenial (from a different install), this problem is not
  happening. This is happening on Bionic.

  There are only two ways to restore connectivity:
  1) Reboot the system;
  2) Remove the r8169 module and reinsert it with modprobe.

  The motherboard is a AsRock H55M-LE and the Ethernet controller is:

  01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
  RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.172
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Mar  2 00:21:57 2018
  Dependencies:

  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-10-generic.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1153 F pulseaudio
   /dev/snd/controlC1:  usuario1153 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26'
     Mixer name : 'VIA VT1818S'
     Components : 'HDA:11060440,18492818,0010'
     Controls  : 40
     Simple ctrls  : 17
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27'
     Mixer name : 'ATI R6xx HDMI'
     Components : 'HDA:1002aa01,00aa0100,00100200'
     Controls  : 7
     Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
     Capabilities: pswitch pswitch-joined
     Playback channels: Mono
     Mono: Playback [on]
  CurrentDesktop: LXDE
  Dependencies:

  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux-firmware 1.172
  PackageArchitecture: all
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz 
root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  RfKill:

  Tags:  bionic
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh in

[Kernel-packages] [Bug 1780137] Re: [Regression] EXT4-fs error (device sda1): ext4_validate_inode_bitmap:99: comm stress-ng: Corrupt inode bitmap

[dann frazier]

The significant difference in the cert test wrapper actually appears to
be that it creates a directory in which to run the test, vs. running it
at the root of the mount point. I'm able to reproduce the failure
outside of cert after a fresh reboot with the following script. The fs
.aio-max-nr sysctl was a red herring.

mkdir -p /tmp/mnt
# My script does a mkfs.ext4 -F, but omitting that here in case someone blindly 
cut & pastes
mkfs.ext4 /dev/sda1
mount /dev/sda1 /tmp/mnt
# Running directly under /tmp/mnt doesn't trigger the issue, we need
# this subdirectory for some reason
mkdir -p /tmp/mnt/tmp/disk_stress_ng_f70f0f26-b332-4c48-9e07-67c529770e3d
stress-ng --aggressive --verify --timeout 240 --temp-path 
/tmp/mnt/tmp/disk_stress_ng_f70f0f26-b332-4c48-9e07-67c529770e3d --chdir 0 
--hdd-opts dsync --readahead-bytes 16M -k

@Colin: I updated the description to note that we have seen this on 2
different HiSilicon servers that use different HiSilicon SoCs. We've
also tested on a Cavium Sabre (ThunderX2-based) board, and were unable
to reproduce it there.

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

Title:
  [Regression] EXT4-fs error (device sda1):
  ext4_validate_inode_bitmap:99: comm stress-ng: Corrupt inode bitmap

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

Bug description:
  We're seeing a very reproducible regression in the bionic kernel
  triggered by the stress-ng chdir test performed by the Ubuntu
  certification suite. We see this on both the HiSilicon D05 arm64
  server and the HiSilicon D06 arm64 server. We have been unable to
  reproduce on other servers so far.

  [Test Case]
  $ sudo apt-add-repository -y ppa:hardware-certification/public
  $ sudo apt install -y canonical-certification-server
  $ sudo mkfs.ext4 /dev/sda1 (Obviously, this should not be your root disk!!)
  $ sudo /usr/lib/plainbox-provider-checkbox/bin/disk_stress_ng sda --base-time 
240 --really-run

  This test runs a series of stress-ng tests against /dev/sda, and fails
  on the "chdir" test. To speed up reproduction, reduce the test list to
  just "chdir" in the disk_stress_ng script. Attempts to reproduce this
  directly with stress-ng have failed - presumably because of other
  environment setup that this script performs (e.g. setting aio-max-nr
  to 524288).

  Our reproduction test is to use a non-root disk because it can lead to
  corruption, and mkfs.ext4'ing the partition just before running the
  test, to get to a pristine fs state.

  I bisected this down to the following commit:

  commit 555bc9b1421f10d94a1192c7eea4a59faca3e711
  Author: Theodore Ts'o 
  Date:   Mon Feb 19 14:16:47 2018 -0500

  ext4: don't update checksum of new initialized bitmaps

  BugLink: http://bugs.launchpad.net/bugs/1773233

  commit 044e6e3d74a3d7103a0c8a9305dfd94d64000660 upstream.

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

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

[Kernel-packages] [Bug 1780137] Re: [Regression] EXT4-fs error (device sda1): ext4_validate_inode_bitmap:99: comm stress-ng: Corrupt inode bitmap

[dann frazier]

** Description changed:

  We're seeing a very reproducible regression in the bionic kernel
  triggered by the stress-ng chdir test performed by the Ubuntu
- certification suite. Platform is a HiSilicon D05 arm64 server, but we
- don't have reason to believe it is platform specific at this time.
+ certification suite. We see this on both the HiSilicon D05 arm64 server
+ and the HiSilicon D06 arm64 server. We have been unable to reproduce on
+ other servers so far.
  
  [Test Case]
  $ sudo apt-add-repository -y ppa:hardware-certification/public
  $ sudo apt install -y canonical-certification-server
  $ sudo mkfs.ext4 /dev/sda1 (Obviously, this should not be your root disk!!)
  $ sudo /usr/lib/plainbox-provider-checkbox/bin/disk_stress_ng sda --base-time 
240 --really-run
  
  This test runs a series of stress-ng tests against /dev/sda, and fails
  on the "chdir" test. To speed up reproduction, reduce the test list to
  just "chdir" in the disk_stress_ng script. Attempts to reproduce this
  directly with stress-ng have failed - presumably because of other
  environment setup that this script performs (e.g. setting aio-max-nr to
  524288).
  
  Our reproduction test is to use a non-root disk because it can lead to
  corruption, and mkfs.ext4'ing the partition just before running the
  test, to get to a pristine fs state.
  
  I bisected this down to the following commit:
  
  commit 555bc9b1421f10d94a1192c7eea4a59faca3e711
  Author: Theodore Ts'o 
  Date:   Mon Feb 19 14:16:47 2018 -0500
  
- ext4: don't update checksum of new initialized bitmaps
- 
- BugLink: http://bugs.launchpad.net/bugs/1773233
- 
- commit 044e6e3d74a3d7103a0c8a9305dfd94d64000660 upstream.
+ ext4: don't update checksum of new initialized bitmaps
+ 
+ BugLink: http://bugs.launchpad.net/bugs/1773233
+ 
+ commit 044e6e3d74a3d7103a0c8a9305dfd94d64000660 upstream.

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

Title:
  [Regression] EXT4-fs error (device sda1):
  ext4_validate_inode_bitmap:99: comm stress-ng: Corrupt inode bitmap

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

Bug description:
  We're seeing a very reproducible regression in the bionic kernel
  triggered by the stress-ng chdir test performed by the Ubuntu
  certification suite. We see this on both the HiSilicon D05 arm64
  server and the HiSilicon D06 arm64 server. We have been unable to
  reproduce on other servers so far.

  [Test Case]
  $ sudo apt-add-repository -y ppa:hardware-certification/public
  $ sudo apt install -y canonical-certification-server
  $ sudo mkfs.ext4 /dev/sda1 (Obviously, this should not be your root disk!!)
  $ sudo /usr/lib/plainbox-provider-checkbox/bin/disk_stress_ng sda --base-time 
240 --really-run

  This test runs a series of stress-ng tests against /dev/sda, and fails
  on the "chdir" test. To speed up reproduction, reduce the test list to
  just "chdir" in the disk_stress_ng script. Attempts to reproduce this
  directly with stress-ng have failed - presumably because of other
  environment setup that this script performs (e.g. setting aio-max-nr
  to 524288).

  Our reproduction test is to use a non-root disk because it can lead to
  corruption, and mkfs.ext4'ing the partition just before running the
  test, to get to a pristine fs state.

  I bisected this down to the following commit:

  commit 555bc9b1421f10d94a1192c7eea4a59faca3e711
  Author: Theodore Ts'o 
  Date:   Mon Feb 19 14:16:47 2018 -0500

  ext4: don't update checksum of new initialized bitmaps

  BugLink: http://bugs.launchpad.net/bugs/1773233

  commit 044e6e3d74a3d7103a0c8a9305dfd94d64000660 upstream.

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

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

[Kernel-packages] [Bug 1686837] Re: ubuntu fails to boot with btrfs root (unable to mount root)

[Shelby Cain]

I have indeed tried unplugging/swapping connected USB peripherals and
that never appeared to help.  The only thing that worked reliably for me
was pinning the old .67 kernel.  Something changed after that and the
one thing that did stand out is a huge increase in the initrd image size
of later kernels.

Anyway, out of all the systems I run 16.04 on only two suffer from this
issue and they are completely different beasts (one is a home brew
server and the other is a dell optiplex workstation - they are also the
only ones that run root on btrfs).  I've updated the home brew system to
18.04 and it appears to no longer suffer from the issue but then again I
don't reboot it very often either so who really knows.

The Dell still requires me to hit 'e' and hang out in the grub editor
for a period of time before continuing to boot reliably.  It is very
strange because manually adding sleep statements to the generated
grub.cfg does not work.

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

Title:
  ubuntu fails to boot with btrfs root (unable to mount root)

Status in linux package in Ubuntu:
  Expired

Bug description:
  Hello,

  Failing to mount / as btrfs has been haunting btrfs users on ubuntu
  for some time. Coming and going with kernel updates.

  After I upgraded to 17.04, it seems that the problem is back.

  It seems that a non-clean umount reboot always leads to a non-bootable 
system. If I boot into rescue (selecting in grub, not a livecd), kernel can 
find the root partition. I can also boot normally if root=... kernel parameter 
is set with the device name (/dev/sda6) instead of UUID=.
  So, there might be a bug in kernel that does not allow linux to identify the 
boot partition using UUID in some circumstances (probably after a dirt reboot).

  Maybe other distros do some magic at initrd that cleans the btrfs
  problem because some, like opensuse, do uses btrfs as default root fs.
  Anyway, even ubuntu own rescue can boot normally.

  This is a tricky bug to debug as I get no logs written and no
  emergency shell. Just an ugly kernel error and a backstack.

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

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

[Kernel-packages] [Bug 1779817] Re: no internet after suspending

[Jan Rathmann]

Kai-Heng:
I have tried the kernel under https://people.canonical.com/~khfeng/lp1779817/ 
and I see no change on my system (bug still there; reloading network driver 
after resume from suspend is still necessary).

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

Title:
  no internet after suspending

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When my computer wakes up from suspending, there's no internet. Unplugging 
and replugging cable doesn't work, restarting network service doesn't work 
also. Only after restarting the computer, internet comes back.
  It only started happening after I freshly installed Ubuntu Budgie (18.04) and 
did all the system updates. Before I was using Ubuntu with Unity (16.04) and 
there was no problems with my internet.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-24-generic 4.15.0-24.26
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  minihydra   2085 F pulseaudio
   /dev/snd/controlC0:  minihydra   2085 F pulseaudio
   /dev/snd/controlC1:  minihydra   2085 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Tue Jul  3 10:13:19 2018
  HibernationDevice: RESUME=UUID=3747bab8-c258-4600-bc24-5d1f56a642dd
  InstallationDate: Installed on 2018-07-02 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=a5ceb36e-76f7-4bd4-a37b-0b91b995c635 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/28/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A77T
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2103:bd06/28/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A77T:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1780137] Re: [Regression] EXT4-fs error (device sda1): ext4_validate_inode_bitmap:99: comm stress-ng: Corrupt inode bitmap

[Colin Ian King]

It may be worth grabbing a copy of the /proc/sys on a clean boot and
then a copy after the sysctl changes so we can get and idea of any
specific tweaks that may have occurred.

Just to note, I've been running the stress-ng command as noted in
comment #3 on a 24 CPU ARM64 Synquacer box with the alleged faulty
kernel and cannot reproduce the issue.

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

Title:
  [Regression] EXT4-fs error (device sda1):
  ext4_validate_inode_bitmap:99: comm stress-ng: Corrupt inode bitmap

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

Bug description:
  We're seeing a very reproducible regression in the bionic kernel
  triggered by the stress-ng chdir test performed by the Ubuntu
  certification suite. Platform is a HiSilicon D05 arm64 server, but we
  don't have reason to believe it is platform specific at this time.

  [Test Case]
  $ sudo apt-add-repository -y ppa:hardware-certification/public
  $ sudo apt install -y canonical-certification-server
  $ sudo mkfs.ext4 /dev/sda1 (Obviously, this should not be your root disk!!)
  $ sudo /usr/lib/plainbox-provider-checkbox/bin/disk_stress_ng sda --base-time 
240 --really-run

  This test runs a series of stress-ng tests against /dev/sda, and fails
  on the "chdir" test. To speed up reproduction, reduce the test list to
  just "chdir" in the disk_stress_ng script. Attempts to reproduce this
  directly with stress-ng have failed - presumably because of other
  environment setup that this script performs (e.g. setting aio-max-nr
  to 524288).

  Our reproduction test is to use a non-root disk because it can lead to
  corruption, and mkfs.ext4'ing the partition just before running the
  test, to get to a pristine fs state.

  I bisected this down to the following commit:

  commit 555bc9b1421f10d94a1192c7eea4a59faca3e711
  Author: Theodore Ts'o 
  Date:   Mon Feb 19 14:16:47 2018 -0500

  ext4: don't update checksum of new initialized bitmaps
  
  BugLink: http://bugs.launchpad.net/bugs/1773233
  
  commit 044e6e3d74a3d7103a0c8a9305dfd94d64000660 upstream.

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

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

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

[Vance Morris]

The install of package haveged workaround also did not work for me - I
was getting boot hangs in my KVM guest installation, waiting for 3
services to start.

After installing haveged, I only hang on something called "hold until
start processes finish up" for about 15 seconds, then a permanent hang
on "Stopping User Manager for UID 119".

I'm also interested to know how long it will take for the kernel fix to
land in the repo so I can retry. 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/1779827

Title:
  failure to boot with linux-image-4.15.0-24-generic

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

Bug description:
  This was the last OK then my 18.04 hangs after an update this morning.
  07:00 AM CEST

  Last Ok in boot was Started gnome display manager. dispatcher service
  .. tem changes.pp link was shut down

  Tried install lightdm from command line and the  response was lastest
  already installed.

  Probably it is what is coming after the lastest OK which is to be the
  error. And here I have lots of guesses..

  Any Ideas ? I need to do some work and I may not be waiting long.

  Search and browsed and now close to give up. Yeah it is a Lenovo.

  Guys: turn of auto update it is a machine killer.

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

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

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

[Vance Morris]

"haveged"

Is this a joke? I went to college dammit! ;D

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

Title:
  failure to boot with linux-image-4.15.0-24-generic

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

Bug description:
  This was the last OK then my 18.04 hangs after an update this morning.
  07:00 AM CEST

  Last Ok in boot was Started gnome display manager. dispatcher service
  .. tem changes.pp link was shut down

  Tried install lightdm from command line and the  response was lastest
  already installed.

  Probably it is what is coming after the lastest OK which is to be the
  error. And here I have lots of guesses..

  Any Ideas ? I need to do some work and I may not be waiting long.

  Search and browsed and now close to give up. Yeah it is a Lenovo.

  Guys: turn of auto update it is a machine killer.

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

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

[Kernel-packages] [Bug 1780124] Re: linux-gcp: 4.15.0-1012.12~16.04.2 -proposed tracker

[Brad Figg]

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1780112
  phase: Uploaded

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

Title:
  linux-gcp: 4.15.0-1012.12~16.04.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow 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  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: 1780112
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

[Kristijan Žic ]

How long will it take for that fix to reach the end users?

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

Title:
  failure to boot with linux-image-4.15.0-24-generic

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

Bug description:
  This was the last OK then my 18.04 hangs after an update this morning.
  07:00 AM CEST

  Last Ok in boot was Started gnome display manager. dispatcher service
  .. tem changes.pp link was shut down

  Tried install lightdm from command line and the  response was lastest
  already installed.

  Probably it is what is coming after the lastest OK which is to be the
  error. And here I have lots of guesses..

  Any Ideas ? I need to do some work and I may not be waiting long.

  Search and browsed and now close to give up. Yeah it is a Lenovo.

  Guys: turn of auto update it is a machine killer.

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

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

[Kernel-packages] [Bug 1779605] Re: [Ubuntu 18.04] Error parsing PCC subspaces from PPCT" is splashed to screen

[Joseph Salisbury]

I built a test kernel the with v4 3/3 patch.  The test kernel can be downloaded 
from:
http://kernel.ubuntu.com/~jsalisbury/lp1779605

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

Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you need to install the 
linux-image and linux-image-extra .deb packages.
• If the test kernel is 4.15(Bionic) or newer, you need to install the 
linux-modules, linux-modules-extra and linux-image-unsigned .deb packages.

Thanks in advance!

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

Title:
  [Ubuntu 18.04] Error parsing PCC subspaces from PPCT" is splashed to
  screen

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

Bug description:
  When installing and booting to Ubuntu 18.04 Server, we see this error
  being shown on screen (Attached Screenshot)

  Setup details- Take a DellEMC 14G server and start installation of
  Ubuntu 18.04 Server. Observe this message in #dmesg.

  Cosmetic error message, no functionality loss.

  Upstream patch details:
  https://www.spinics.net/lists/linux-acpi/msg81863.html
  Please include these in future builds of Ubuntu 18.04.

  Uploading the #dmesg logs.

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

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

I built a v2 Xenial test kernel with commit 
9a86cda07af2c63649932f0a4fc757701ef54c42. The test kernel can be downloaded 
from:
http://kernel.ubuntu.com/~jsalisbury/lp1770423

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

Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you need to install the 
linux-image and linux-image-extra .deb packages.
• If the test kernel is 4.15(Bionic) or newer, you need to install the 
linux-modules, linux-modules-extra and linux-image-unsigned .deb packages.

Thanks in advance!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 1779830] Re: vfio/pci: cannot assign a i40e pf device to a vm using vfio-pci

[Joseph Salisbury]

I built a test kernel with commit 450744051d20.  The test kernel can be 
downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1779830

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

Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you need to install the 
linux-image and linux-image-extra .deb packages.
• If the test kernel is 4.15(Bionic) or newer, you need to install the 
linux-modules, linux-modules-extra and linux-image-unsigned .deb packages.

Thanks in advance!

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

Title:
  vfio/pci: cannot assign a i40e pf device to a vm using vfio-pci

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

Bug description:
  The following upstream patch (v4.7) is missing in xenial:

  450744051d20 ("vfio/pci: Hide broken INTx support from user")
  http://scm/kernels/linux-upstream/commit/?id=450744051d20

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

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

[Kernel-packages] [Bug 1774225] Re: netns: unable to follow an interface that moves to another netns

[Joseph Salisbury]

Xenial appears to have some prereq commits necessary and requires
backporting of commits.  Is it possible to use the HWE kernel with
Xenial instead of backporting the commits to 4.4?

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

Title:
  netns: unable to follow an interface that moves to another netns

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

Bug description:
  The following upstream patches are missing (v4.16):

  6621dd29eb9b ("dev: advertise the new nsid when the netns iface changes")
  c36ac8e23073 ("dev: always advertise the new nsid when the netns iface 
changes")
  38e01b30563a ("dev: advertise the new ifindex when the netns iface changes")

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6621dd29eb9b
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c36ac8e23073
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=38e01b30563a

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

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

[Kernel-packages] [Bug 1779357] Re: linux-oem: 4.15.0-1010.13 -proposed tracker

[Brad Figg]

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1780112
  phase: Uploaded

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-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: 1780112
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1757008] Re: Broadcom wireless drivers failed to build [error: implicit declaration of function ‘init_timer’]

[Vincent Ladeuil]

Same here (broadcom-sta vs bcmwl).

Can a kind soul explains if one can be used instead of the other and
why/how they differ ?

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

Title:
  Broadcom wireless drivers failed to build [error: implicit declaration
  of function ‘init_timer’]

Status in bcmwl package in Ubuntu:
  Confirmed
Status in broadcom-sta package in Ubuntu:
  Confirmed

Bug description:
  The module fails to build, as it is missing the necessary patches for
  the latest HWE kernel.

  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In 
function ‘wl_init_timer’:
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2: 
error: implicit declaration of function ‘init_timer’ 
[-Werror=implicit-function-declaration]
init_timer(&t->timer);
^

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-13-generic
  Date: Mon Mar 19 15:02:46 2018
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.2:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2:
 error: implicit declaration of function ‘init_timer’ 
[-Werror=implicit-function-declaration]
  InstallationDate: Installed on 2017-06-05 (287 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1780227] Re: locking sockets broken due to missing AppArmor socket mediation patches

[John Johansen]

Okay, so lets split this between upstream and ubuntu kernels

previous upstream kernels did not have socket mediation and could NOT
have generated the denial message being seen.


Jul 04 15:11:11 host audit[28404]: AVC apparmor="DENIED" operation="file_lock" 
profile="lxc-container-default-cgns" pid=28404 comm="(true)" family="unix" 
sock_type="dgram" protocol=0 addr=none

4.17 has socket mediation code but there is no released userspace that
supports it. It requires apparmor 3 dev, so in all existing userspaces
the 4.17 socket mediation is not being enforced.

The ubuntu kernels Xenial and Bionic carry a variant of the socket
mediation patch that is in 4.17 but with a different abi. The ubuntu
4.17 kernel carries a compatibility patch and will have the Bionic and
Xenial behavior under current 2.x apparmor userspaces.

The correct solution looks to be patching the current 2.x userspace to
support locking on abstract and anonymous sockets

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

Title:
  locking sockets broken due to missing AppArmor socket mediation
  patches

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

Bug description:
  Hey,

  Newer systemd makes use of locks placed on AF_UNIX sockets created
  with the socketpair() syscall to synchronize various bits and pieces
  when isolating services. On kernels prior to 4.18 that do not have
  backported the AppArmor socket mediation patchset this will cause the
  locks to be denied with EACCESS. This causes systemd to be broken in
  LXC and LXD containers that do not run unconfined which is a pretty
  big deal. We have seen various bug reports related to this. See for
  example [1] and [2].

  If feasible it would be excellent if we could backport the socket
  mediation patchset to all LTS kernels. Afaict, this should be 4.4 and
  4.15. This will unbreak a whole range of use-cases.

  The socket mediation patchset is available here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=80a17a5f501ea048d86f81d629c94062b76610d4

  
  [1]: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1575779
  [2]: https://github.com/systemd/systemd/issues/9493

  Thanks!
  Christian

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

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

[Kernel-packages] [Bug 1780309] [NEW] [Hyper-V] Please set CONFIG_BLK_DEV_DRBD to "m"

[Joshua R. Poulson]

Public bug reported:

DRBD modules are not loadable nor are they in extras. Please set
CONFIG_BLK_DEV_DRBD to "m" in the linux-azure kernel config.

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

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

Title:
  [Hyper-V] Please set CONFIG_BLK_DEV_DRBD to "m"

Status in linux-azure package in Ubuntu:
  New

Bug description:
  DRBD modules are not loadable nor are they in extras. Please set
  CONFIG_BLK_DEV_DRBD to "m" in the linux-azure kernel config.

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

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

[Kernel-packages] [Bug 1779640] Re: [Hyper-V] KVP daemon crashes at startup

[Joseph Salisbury]

Would it be possible for you to test some prior kernels to see if we can
bisect this issue down?  If so, the following kernels would be a good
starting point:

Artful: 
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/15007007
Early Bionic: 
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable/+build/13870786

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

Title:
  [Hyper-V] KVP daemon crashes at startup

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

Bug description:
  While testing Bionic daily build with kernel 4.15.0-20-generic we saw
  the following issue with the KVP daemon:

  KVP daemon crashes after approximatively 2 minutes of uptime and it enters in 
a failed state. The daemon can be manually started and it enters back in active 
(running) state.
  The error messages from /var/log/syslog after the daemon enters the failed 
state are the following:

  Apr 25 04:28:46 bionicDaily KVP: read failed; error:9 Bad file descriptor
  Apr 25 04:28:46 bionicDaily systemd[1]: hv-kvp-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Apr 25 04:28:46 bionicDaily systemd[1]: hv-kvp-daemon.service: Failed with 
result 'exit-code'.
  Apr 25 04:28:59 bionicDaily systemd[1]: Started Hyper-V KVP Protocol Daemon.

  Note: There was a simmilar issue discussed on this thread
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664663, but the
  fixing commit seems to be inclued in this Bionic build.

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

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

[Kernel-packages] [Bug 1776642] Re: Temporal dithering and impaired graphical performance started appearing on Intel HD 530 graphics

[Patrick Wigmore]

So, to summarise, the bug in regard to Xorg seems to be fixed in
4.15.0-25 and in 4.18-rc3. The bug appears to have always been present
under virtual terminals (only tested as far back as 4.13.0-31.

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

Title:
  Temporal dithering and impaired graphical performance started
  appearing on Intel HD 530 graphics

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am experiencing a regression in linux-image-generic-hwe-16.04 with
  Intel HD Graphics 530 (Core i5-6600T), starting in 4.13.0-43
  (considering only kernels which appear in my GRUB menu).

  Some form of spatio-temporal dithering has been enabled. This is
  causing a shimmering effect and visible dithering patterns (like woven
  textile) which are noticeable on photographs and areas of similar
  colour. 1px borders in the UI can appear to have a "marching ants"
  effect.

  The effect is visible under Xorg if the displayed colours are suitable
  to trigger it.

  The effect is also visible in a virtual console (Ctrl+Alt+F1) if
  suitable colours are displayed, but it seems that the presence of the
  effect in virtual consoles predates its appearance under Xorg and the
  reporting of this bug, going back at least as far as 4.13.0-31, but
  with no reason to believe it does not go back further (besides lack of
  testing).

  Reverting from 4.13.0-43 by booting 4.13.0-41 eliminates the temporal
  dithering in Xorg.

  This occurs on a (presumed) 6bpp laptop LCD panel, so dithering is
  necessary, but in previous kernels only a form of spatial dithering is
  applied, which is less visually obvious.

  Concurrent with the temporal dithering, I have also noticed general poor 
graphical performance with the affected kernels. E.g. 50fps and 60fps video 
playback is choppy, sometimes slow redraw and other graphical glitches on UI 
elements. Like the temporal dithering, these additional problems disappear if I 
revert to 4.13.0-41.
  ---
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  patrick1976 F pulseaudio
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=72e179a8-b27c-42d3-9523-8f1cceacaa64
  InstallationDate: Installed on 2016-09-16 (634 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: PC Specialist Limited N350DW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-45-generic 
root=UUID=deeef076-c1e1-47ec-8ee4-d3b56fa179f9 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-45-generic N/A
   linux-backports-modules-4.13.0-45-generic  N/A
   linux-firmware 1.157.19
  Tags:  xenial xenial
  Uname: Linux 4.13.0-45-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: False
  dmi.bios.date: 05/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N350DW
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd05/26/2016:svnPCSpecialistLimited:pnN350DW:pvrNotApplicable:rvnCLEVO:rnN350DW:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: N350DW
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist Limited

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

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

[Kernel-packages] [Bug 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)

[pHeLiOn]

@kaihengfeng - no problem, here's the results:

First kernel (with the commit) - Hibernation starts but then system
seizes with power LED on requiring forced shutdown. Upon restart,
hibernation resumes from where you left off as if nothing went wrong.


Second kernel (without the commit) - Hibernation starts and shutsdown by 
itself. Upon restart, hibernate resumes as expected.


In both cases, hibernation is resuming without issue but with the first kernel 
(with the commit) a forced shutdown is required. Machine will 'hang' 
indefinitely with the screen off and the power LED on.

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

Title:
  Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and
  Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have installed Kubuntu 18.04 on 3 different machines (my friend's
  and my own) with no suspend problems but my HP Pavilion 11 x360 does
  not suspend.

  It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse,
  Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu
  18.04.

  I have also tried suspend using a live USB of 18.04 on this machine
  and it fails in the same way, so does not appear to be caused by any
  additional programs that I had installed.

  By installing an older kernel (4.14) on Kubuntu 18.04 the suspend
  function works as expected.

  Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the
  suspend failure that freezes the machine and requires a hard reset.

  
  Correct behaviour is - 

  Screen goes blank, fan goes off, power LED flashes to show machine is
  in suspend. Pressing power button triggers 'resume' function.

  
  What happens - 

  Screen goes blank, fan stays on, power LED stays on. Machine stays in
  this state and does not respond to any keyboard interaction, mouse
  movement or power button presses.

  
  Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response.

  The only way to use the machine is to shut down by holding down the
  power button.

  
  Checking the logs suggests that the machine believes it is in suspend mode 
sleep [deep] when it isn't.

  Having to hard reset to get any response means that the kernel logs
  say no more than sleep [deep]

  pm-suspend also results in the same problems with kernels 4.15 and
  4.16, but works fine with 4.14.

  It is curious that a machine that suspends fine on an earlier 4.14
  kernel no longer works with 4.15 and above, whilst 3 other machines
  (including one with pretty similar hardware) do not exhibit this
  problem.

  There are only a handful of questions about it on the forums but at
  least 3 other people have the same problem:

  https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on-
  resuming-from-suspend

  https://askubuntu.com/questions/1041369/after-upgrading-
  from-17-10-ubuntu-18-04-wont-sleep-suspend

  I am attempting to round up anyone else with the same issue and point
  them to this bug report.

  My laptop is HP Pavilion x360 11-n013na 
  Matalaks is Acer Aspire ES1-511
  collisionTwo has XPS 9560

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

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

[Kernel-packages] [Bug 1776642] Re: Temporal dithering and impaired graphical performance started appearing on Intel HD 530 graphics

[Patrick Wigmore]

Under 4.18-rc3 from http://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.18-rc3/ the symptoms appear identical to those under
4.15.0-25-generic.

I tested mainline 4.17, 4.17.2, 4.17.3, 4.17.4 and 4.18-rc2 from the
kernel.ubuntu.com, which all displayed the original symptoms reported
for this bug.

Correction/clarification: Previously, I failed to test whether the
temporal dithering appeared in virtual consoles under 4.13.0-41. I only
tested to see whether it affected virtual consoles on kernels where it
also affected X. It turns out that the dithering has always been present
in virtual consoles at least as far back as 4.13.0-31, but it did not
appear under X until 4.13.0-43. I will amend the bug description to
reflect this.

The issue with semi-transparent backgrounds in Plasma widgets may be
unrelated, as this is now appearing under all kernels I've tried
booting.

** Description changed:

  I am experiencing a regression in linux-image-generic-hwe-16.04 with
  Intel HD Graphics 530 (Core i5-6600T), starting in 4.13.0-43
  (considering only kernels which appear in my GRUB menu).
  
  Some form of spatio-temporal dithering has been enabled. This is causing
  a shimmering effect and visible dithering patterns (like woven textile)
  which are noticeable on photographs and areas of similar colour. 1px
  borders in the UI can appear to have a "marching ants" effect.
  
- The effect is visible both under Xorg and in a virtual console
- (Ctrl+Alt+F1), if the displayed colours are suitable to trigger it.
+ The effect is visible under Xorg if the displayed colours are suitable
+ to trigger it.
  
- Booting 4.13.0-41 eliminates the temporal dithering.
+ The effect is also visible a virtual console (Ctrl+Alt+F1) if suitable
+ colours are displayed, but it seems that the presence of the effect in
+ virtual consoles predates its appearance under Xorg and the reporting of
+ this bug, going back at least as far as 4.13.0-31, but with no reason to
+ believe it does not go back further (besides lack of testing).
+ 
+ Reverting from 4.13.0-43 by booting 4.13.0-41 eliminates the temporal
+ dithering in Xorg.
  
  This occurs on a (presumed) 6bpp laptop LCD panel, so dithering is
  necessary, but in previous kernels only a form of spatial dithering is
  applied, which is less visually obvious.
  
  Concurrent with the temporal dithering, I have also noticed general poor 
graphical performance with the affected kernels. E.g. 50fps and 60fps video 
playback is choppy, sometimes slow redraw and other graphical glitches on UI 
elements. Like the temporal dithering, these additional problems disappear if I 
revert to 4.13.0-41.
  ---
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  patrick1976 F pulseaudio
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=72e179a8-b27c-42d3-9523-8f1cceacaa64
  InstallationDate: Installed on 2016-09-16 (634 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: PC Specialist Limited N350DW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-45-generic 
root=UUID=deeef076-c1e1-47ec-8ee4-d3b56fa179f9 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-45-generic N/A
   linux-backports-modules-4.13.0-45-generic  N/A
   linux-firmware 1.157.19
  Tags:  xenial xenial
  Uname: Linux 4.13.0-45-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: False
  dmi.bios.date: 05/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N350DW
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd05/26/2016:svnPCSpecialistLimited:pnN350DW:pvrNotApplicable:rvnCLEVO:rnN350DW:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: N350DW
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist Limited

** Description changed:

  I am experiencing a regression in linux-image-generic-hwe-16.04 with
  Intel HD Graphics 530 (Core i5-6600T), starting in 4.13.0-43
  (considering only kernels which appear in my GRUB menu).
  
  Some form of spatio-temporal dithering has been enabled. This is causing
  a shimmering effect and visible dithering patterns (like woven textile)
  which are noticeable on photographs and areas of similar colour. 1px
  borders in 

[Kernel-packages] [Bug 1690085]

[robert]

Interestingly,

I had a nicely running system, uptime about 30 days, and I just decided
to upgrade the Kernel to the latest (Fedora 28), and "what the heck" I
will just upgrade the motherboard BIOS too.

Mobo: ASUSTeK model: PRIME B350M-A
6 core AMD Ryzen 5 1600X Six-Core (-MT-MCP-) arch: Zen rev.1

So, now I have BIOS version 4104  (previous was 3801 I think)

And after like 10 minutes of doing stuff (i.e. not idle), LOCKED UP !!!

So I went into the BIOS and changed the Global C-State to Disabled, and
right under that is the power profile, changed it to Typical.

We shall see how long it lasts !

I guess "don't fix what ain't broken" applied to my activity today lol.

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

[Kernel-packages] [Bug 1690085]

[alexandre9099]

(In reply to Robert Hoffmann from comment #386)
> Interestingly,
> 
> I had a nicely running system, uptime about 30 days, and I just decided to
> upgrade the Kernel to the latest (Fedora 28), and "what the heck" I will
> just upgrade the motherboard BIOS too.
> 
> Mobo: ASUSTeK model: PRIME B350M-A
> 6 core AMD Ryzen 5 1600X Six-Core (-MT-MCP-) arch: Zen rev.1
> 
> So, now I have BIOS version 4104  (previous was 3801 I think)
> 
> And after like 10 minutes of doing stuff (i.e. not idle), LOCKED UP !!!
> 
> So I went into the BIOS and changed the Global C-State to Disabled, and
> right under that is the power profile, changed it to Typical.
> 
> We shall see how long it lasts !
> 
> I guess "don't fix what ain't broken" applied to my activity today lol.

My case is similar, but i don't recall updating the BIOS/UEFI firmware,
it was after a kernel upgrade that the system started locking up :/

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

[Kernel-packages] [Bug 1690085]

[dev]

Did the ppl with the new BIOSes double test the 'Power Supply Idle
Control' option by disabling it temporary? Because, it could also be
fixed by that Agesa update some of you mentioned (also mentioned in [1])

tl;dr: 
Had soft lockup at full load, BIOS-update seems to help, but it doesn't have 
the 'Power Supply Idle Control'-option.

More details:
My HP 17-ca0202ng (Ryzen 2500U) was stable by starting up with "idle=nomwait" 
Kernel-parameter for 2~3 weeks until *something*[2] happened and from one day 
to the next it was hard-locking again and on another testrun it threw the 
soft-lock-error (NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s!) while 
it was transcoding x264-stuff to x265 (kind of full load; 95% @ all 8 threads). 
It was bootet up by "nomodeset" at the time the errors occur, so I'm quite sure 
it can't be amdgpu-related.
The time the soft-lock occurred, the system was kind of responsive, just 
freezing after a amount of seconds with unfreezing after another amount of 
seconds. I was able to run dmesg and just saw that NMI watchdog: BUG: soft 
lockup - CPU#0 stuck for 23s! for all threads, before more freezings in shorter 
amount of seconds appeared and the system completely froze. Strange!

But: HP provided a BIOS-Update (F4 > F10) some days ago, I was able to update 
it yesterday and I've done 8 hours of full-load testing, 8 hours of idle 
testing and 7,5 hours of partial-load testing. No lockup so far and no 
Kernel-parameters needed (running Ubuntu's mainline build kernel 4.17.2, the 
stuff from Padoka stable ppa and ravenridge firmware from [3] to prevent 
amdgpu-freezes). As any lockup occurred within 3 hours, the laptop seems to be 
stable (or at least "more stable" than before).
Can't say anything about the changes HP made in that update, because they don't 
provide a changelog. But it's a laptop, so it has 3 or 4 BIOS-options 
(something virtualisation something, something secure boot something and some 
boot order options) and for sure no 'Power Supply Idle Control'. Allow me to 
point out, that Laptops usually have power adapters special designed for the 
device. So it can't be power supply related as AMD said (IMO).


[1] https://community.amd.com/thread/225795 , 
https://community.amd.com/thread/224000
[2] May be microcode-update related provided by Ubuntu, but I can't remember 
for sure.
[3] 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu

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

[Kernel-packages] [Bug 1779476] Re: Ubuntu 18.04: gdm3 does not switch to graphics after update

[njsf]

Installed linux-headers-4.15.0-23-generic, now dkms runs properly.

Re-tested w/ 4.15.0-23-generic: gdm3 STILL does not come up, just bounces 
between black screen and the systemd progress messages.
So, going back to 4.15.0-23-generic does NOT solve the original issue.

I will continue w/ haveged and lightdm workaround, but the bug should
remain open.

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

Title:
  Ubuntu 18.04:  gdm3 does not switch to graphics after update

Status in gdm3 package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After update of gdm and kernel gdm3 no longer enables graphics.

  What happens:
  =
  With and without:
 WaylandEnable=false
  in /etc/gdm3/custom.conf
  gdm3 does not switch to graphics.
  In both cases I case the X process running (Xwayland or Xorg) but no vt has 
it.
  lightdm does work, but barely. It takes up to a minute to get to the login 
screen.

  What I expected to happen:
  ==
  gdm3 switching to graphics in ~20 after boot like pre-update.

  Release:
  
  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  $ apt-cache policy kernel-common gdm3 lightdm xorg xwayland
  kernel-common:
Installed: (none)
Candidate: 13.018+nmu1
Version table:
   13.018+nmu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
  gdm3:
Installed: 3.28.2-0ubuntu1.3
Candidate: 3.28.2-0ubuntu1.3
Version table:
   *** 3.28.2-0ubuntu1.3 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.2-0ubuntu1.2 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
   3.28.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  lightdm:
Installed: 1.26.0-0ubuntu1
Candidate: 1.26.0-0ubuntu1
Version table:
   *** 1.26.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status
  xorg:
Installed: 1:7.7+19ubuntu7
Candidate: 1:7.7+19ubuntu7
Version table:
   *** 1:7.7+19ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  xwayland:
Installed: 2:1.19.6-1ubuntu4
Candidate: 2:1.19.6-1ubuntu4
Version table:
   *** 2:1.19.6-1ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status


  
  Attaching journalctl -b.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-27 (673 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NonfreeKernelModules: wl
  Package: gdm3 3.28.2-0ubuntu1.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Tags:  bionic package-from-proposed
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-27 (674 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NonfreeKernelModules: wl
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Tags:  bionic package-from-proposed
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.gdm3.custom.conf: [modified]
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424

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

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

[Kernel-packages] [Bug 1779476] Re: Ubuntu 18.04: gdm3 does not switch to graphics after update

[monkeybrain2012]

It affected lightdm as well. I run unity in 18.04 and use lighdm and the
boot time has gone from 4 secs to 4 minutes with 4.15.0-24. Brad's
workaround(#21) by installing haveged also works for lightdm.

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

Title:
  Ubuntu 18.04:  gdm3 does not switch to graphics after update

Status in gdm3 package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After update of gdm and kernel gdm3 no longer enables graphics.

  What happens:
  =
  With and without:
 WaylandEnable=false
  in /etc/gdm3/custom.conf
  gdm3 does not switch to graphics.
  In both cases I case the X process running (Xwayland or Xorg) but no vt has 
it.
  lightdm does work, but barely. It takes up to a minute to get to the login 
screen.

  What I expected to happen:
  ==
  gdm3 switching to graphics in ~20 after boot like pre-update.

  Release:
  
  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  $ apt-cache policy kernel-common gdm3 lightdm xorg xwayland
  kernel-common:
Installed: (none)
Candidate: 13.018+nmu1
Version table:
   13.018+nmu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
  gdm3:
Installed: 3.28.2-0ubuntu1.3
Candidate: 3.28.2-0ubuntu1.3
Version table:
   *** 3.28.2-0ubuntu1.3 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.2-0ubuntu1.2 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
   3.28.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  lightdm:
Installed: 1.26.0-0ubuntu1
Candidate: 1.26.0-0ubuntu1
Version table:
   *** 1.26.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status
  xorg:
Installed: 1:7.7+19ubuntu7
Candidate: 1:7.7+19ubuntu7
Version table:
   *** 1:7.7+19ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  xwayland:
Installed: 2:1.19.6-1ubuntu4
Candidate: 2:1.19.6-1ubuntu4
Version table:
   *** 2:1.19.6-1ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status


  
  Attaching journalctl -b.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-27 (673 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NonfreeKernelModules: wl
  Package: gdm3 3.28.2-0ubuntu1.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Tags:  bionic package-from-proposed
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-27 (674 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NonfreeKernelModules: wl
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Tags:  bionic package-from-proposed
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.gdm3.custom.conf: [modified]
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424

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

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

[Kernel-packages] [Bug 1780117] Re: linux-azure: 4.15.0-1016.16 -proposed tracker

[Joshua R. Poulson]

** Changed in: kernel-sru-workflow/stakeholder-signoff
   Status: New => Confirmed

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

Title:
  linux-azure: 4.15.0-1016.16 -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 prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow 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 stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in 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: 1780112
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1779476] Re: Ubuntu 18.04: gdm3 does not switch to graphics after update

[njsf]

Processing triggers for linux-image-4.15.0-23-generic (4.15.0-23.25) ...
/etc/kernel/postinst.d/dkms:
Error! Your kernel headers for kernel 4.15.0-23-generic cannot be found.
Please install the linux-headers-4.15.0-23-generic package,
or use the --kernelsourcedir option to tell DKMS where it's located

root@postel:~# dpkg-query -s linux-headers-4.15.0-23
Package: linux-headers-4.15.0-23
Status: install ok installed
Priority: optional
Section: devel
Installed-Size: 75198

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

Title:
  Ubuntu 18.04:  gdm3 does not switch to graphics after update

Status in gdm3 package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After update of gdm and kernel gdm3 no longer enables graphics.

  What happens:
  =
  With and without:
 WaylandEnable=false
  in /etc/gdm3/custom.conf
  gdm3 does not switch to graphics.
  In both cases I case the X process running (Xwayland or Xorg) but no vt has 
it.
  lightdm does work, but barely. It takes up to a minute to get to the login 
screen.

  What I expected to happen:
  ==
  gdm3 switching to graphics in ~20 after boot like pre-update.

  Release:
  
  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  $ apt-cache policy kernel-common gdm3 lightdm xorg xwayland
  kernel-common:
Installed: (none)
Candidate: 13.018+nmu1
Version table:
   13.018+nmu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
  gdm3:
Installed: 3.28.2-0ubuntu1.3
Candidate: 3.28.2-0ubuntu1.3
Version table:
   *** 3.28.2-0ubuntu1.3 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.2-0ubuntu1.2 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
   3.28.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  lightdm:
Installed: 1.26.0-0ubuntu1
Candidate: 1.26.0-0ubuntu1
Version table:
   *** 1.26.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status
  xorg:
Installed: 1:7.7+19ubuntu7
Candidate: 1:7.7+19ubuntu7
Version table:
   *** 1:7.7+19ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  xwayland:
Installed: 2:1.19.6-1ubuntu4
Candidate: 2:1.19.6-1ubuntu4
Version table:
   *** 2:1.19.6-1ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status


  
  Attaching journalctl -b.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-27 (673 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NonfreeKernelModules: wl
  Package: gdm3 3.28.2-0ubuntu1.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Tags:  bionic package-from-proposed
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-27 (674 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NonfreeKernelModules: wl
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Tags:  bionic package-from-proposed
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.gdm3.custom.conf: [modified]
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424

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

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

[Kernel-packages] [Bug 1764645] Re: Bluetooth not working

[Daniel Buchmann]

Jeremy, I did it right now (#56), but the issue persists. Here's the
updated output: https://tinyurl.com/ycsv97tv

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

Title:
  Bluetooth not working

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

Bug description:
  == SRU Justification ==
  A regression was discovered in Bionic.  The regression was introduced by
  mainline commit f44cb4b19ed4, which then made it's way into Bionic in
  4.15.0-14 as commit c91729972ac6 via stable updates.

  This regression is fixed by mainline commit 803cdb8ce584.  Commit
  803cdb8ce584 was also cc'd to stable.  However, it has not landed in
  upstream stable 4.15 or Bionic.

  
  == Fix ==
  803cdb8ce584 ("Bluetooth: btusb: Apply QCA Rome patches for some ATH3012 
models")

  
  == Regression Potential ==
  Low.  This fix has also been 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.



  I've installed the Ubuntu Bionic Beta 2 and everything works fine but
  the bluetooth (perfectly working with Xenial). In bluetooth control
  panel the slider is impossible to move to "on".

  1) Ubuntu Release (via 'lsb_release -rd')
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  2) Version of package (apt-cache policy gnome-bluetooth)
  gnome-bluetooth:
    Installato: 3.28.0-2
    Candidato:  3.28.0-2
    Tabella versione:
   *** 3.28.0-2 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen
  I expected to switch on the bluetooth.

  4) What happened instead
  Bluetooth won't switch on.

  5) Output of rfkill list is:
  0: hci0: Bluetooth
     Soft blocked: no
     Hard blocked: no
  1: phy0: Wireless LAN
     Soft blocked: no
     Hard blocked: no

  6) Output of lspci -knn | grep Net -A3; lsusb; dmesg | grep -i blue is:
  03:00.0 Network controller [0280]: Qualcomm Atheros AR9462 Wireless
  Network Adapter [168c:0034] (rev 01)
  Subsystem: Bigfoot Networks, Inc. Killer Wireless-N 1202 Half-
  size Mini PCIe Card [1a56:2003]
  Kernel driver in use: ath9k
  Kernel modules: ath9k
  04:00.0 Ethernet controller [0200]: Qualcomm Atheros QCA8171 Gigabit
  Ethernet [1969:10a1] (rev 10)
  Bus 002 Device 002: ID 8087:8000 Intel Corp.
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 002: ID 8087:8008 Intel Corp.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 004: ID 04f2:b414 Chicony Electronics Co., Ltd
  Bus 003 Device 003: ID 0cf3:3004 Atheros Communications, Inc.
  AR3012 Bluetooth 4.0
  Bus 003 Device 002: ID 0b05:17c4 ASUSTek Computer, Inc.
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [   17.715399] Bluetooth: Core ver 2.22
  [   17.715414] Bluetooth: HCI device and connection manager initialized
  [   17.715416] Bluetooth: HCI socket layer initialized
  [   17.715418] Bluetooth: L2CAP socket layer initialized
  [   17.715422] Bluetooth: SCO socket layer initialized
  [   17.723207] Bluetooth: hci0: don't support firmware rome 0x1102
  [   18.600648] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   18.600649] Bluetooth: BNEP filters: protocol multicast
  [   18.600651] Bluetooth: BNEP socket layer initialized

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stormy 1484 F pulseaudio
   /dev/snd/controlC0:  stormy 1484 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 17 08:46:30 2018
  HibernationDevice: RESUME=UUID=3f513ca9-6817-4099-9718-fee68d68ec11
  InstallationDate: Installed on 2018-04-16 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  MachineType: ASUSTeK COMPUTER INC. G750JH
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-15-generic N/A
   linux-backports-modules-4.15.0-15-generic  N/A
   l

[Kernel-packages] [Bug 1779476] Re: Ubuntu 18.04: gdm3 does not switch to graphics after update

[njsf]

Going back to kernel 4.15.0-23 DOES NOT solve the gdm3 issue.
Hence the issue I reported is not solved.

Has for the _workaround_ of using lightdm in 4.15.0-23, yes, it boots faster 
HOWEVER, once I installed 4.15.0-23 the bcmwl DID NOT GET BUILT/INSTALLED which 
is also VERY bad, as _no WIFI_.
How then can a _regular_ user go back on kernels and use dkms ?
When providing such suggestions of previous kernels you need to make sure the 
dkms machinery will work!!!

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

Title:
  Ubuntu 18.04:  gdm3 does not switch to graphics after update

Status in gdm3 package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After update of gdm and kernel gdm3 no longer enables graphics.

  What happens:
  =
  With and without:
 WaylandEnable=false
  in /etc/gdm3/custom.conf
  gdm3 does not switch to graphics.
  In both cases I case the X process running (Xwayland or Xorg) but no vt has 
it.
  lightdm does work, but barely. It takes up to a minute to get to the login 
screen.

  What I expected to happen:
  ==
  gdm3 switching to graphics in ~20 after boot like pre-update.

  Release:
  
  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  $ apt-cache policy kernel-common gdm3 lightdm xorg xwayland
  kernel-common:
Installed: (none)
Candidate: 13.018+nmu1
Version table:
   13.018+nmu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
  gdm3:
Installed: 3.28.2-0ubuntu1.3
Candidate: 3.28.2-0ubuntu1.3
Version table:
   *** 3.28.2-0ubuntu1.3 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.2-0ubuntu1.2 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
   3.28.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  lightdm:
Installed: 1.26.0-0ubuntu1
Candidate: 1.26.0-0ubuntu1
Version table:
   *** 1.26.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status
  xorg:
Installed: 1:7.7+19ubuntu7
Candidate: 1:7.7+19ubuntu7
Version table:
   *** 1:7.7+19ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  xwayland:
Installed: 2:1.19.6-1ubuntu4
Candidate: 2:1.19.6-1ubuntu4
Version table:
   *** 2:1.19.6-1ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status


  
  Attaching journalctl -b.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-27 (673 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NonfreeKernelModules: wl
  Package: gdm3 3.28.2-0ubuntu1.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Tags:  bionic package-from-proposed
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-27 (674 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NonfreeKernelModules: wl
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Tags:  bionic package-from-proposed
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.gdm3.custom.conf: [modified]
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424

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

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

Re: [Kernel-packages] [Bug 1780227] Re: locking sockets broken due to missing AppArmor socket mediation patches

[Christian Brauner]

On Thu, Jul 05, 2018 at 04:16:20PM -, John Johansen wrote:
> The 4.17 patch set did not have any changes that should affect this. I
> will have to investigate what is going on further. At this time DO NOT
> backport the 4.17 patchset.

Thanks John. Sorry for jumping the gun then.
What is weird though is that this bug is present in prior kernels and
gone with 4.17 and there's a bunch of socket related codepaths that
would explain the changed behavior. In any case, thanks for helping!

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

Title:
  locking sockets broken due to missing AppArmor socket mediation
  patches

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

Bug description:
  Hey,

  Newer systemd makes use of locks placed on AF_UNIX sockets created
  with the socketpair() syscall to synchronize various bits and pieces
  when isolating services. On kernels prior to 4.18 that do not have
  backported the AppArmor socket mediation patchset this will cause the
  locks to be denied with EACCESS. This causes systemd to be broken in
  LXC and LXD containers that do not run unconfined which is a pretty
  big deal. We have seen various bug reports related to this. See for
  example [1] and [2].

  If feasible it would be excellent if we could backport the socket
  mediation patchset to all LTS kernels. Afaict, this should be 4.4 and
  4.15. This will unbreak a whole range of use-cases.

  The socket mediation patchset is available here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=80a17a5f501ea048d86f81d629c94062b76610d4

  
  [1]: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1575779
  [2]: https://github.com/systemd/systemd/issues/9493

  Thanks!
  Christian

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

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

[Kernel-packages] [Bug 1780062] Re: Cloud-init causes potentially huge boot delays with 4.15 kernels

[Magnus Helander]

Can confirm - the weirdest bug, moving my finger on mousepad enables normal 
boot times.
Thinkpad T420
4.15.0-24-generic #26-Ubuntu SMP Wed Jun 13 08:44:47 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/1780062

Title:
  Cloud-init causes potentially huge boot delays with 4.15 kernels

Status in cloud-init package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in cloud-init source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  Newer 4.15 kernels contain the following fix for CVE-2018-1108:
43838a23a05fb ("random: fix crng_ready() test")

  This causes cloud-init to stall for a potentially long time during
  boot (waiting for entropy I presume). Google reported boot delays of
  75 minutes.

  I've tracked this down to the following import in templater.py which causes 
the delay:
  from jinja2 import Template as JTemplate

  Which is called when cc_update_etc_hosts is imported.

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

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

[Kernel-packages] [Bug 1779830] Re: vfio/pci: cannot assign a i40e pf device to a vm using vfio-pci

[Joseph Salisbury]

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

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

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

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

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

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

Title:
  vfio/pci: cannot assign a i40e pf device to a vm using vfio-pci

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

Bug description:
  The following upstream patch (v4.7) is missing in xenial:

  450744051d20 ("vfio/pci: Hide broken INTx support from user")
  http://scm/kernels/linux-upstream/commit/?id=450744051d20

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

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

[Kernel-packages] [Bug 1780227] Re: locking sockets broken due to missing AppArmor socket mediation patches

[John Johansen]

The 4.17 patch set did not have any changes that should affect this. I
will have to investigate what is going on further. At this time DO NOT
backport the 4.17 patchset.

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

Title:
  locking sockets broken due to missing AppArmor socket mediation
  patches

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

Bug description:
  Hey,

  Newer systemd makes use of locks placed on AF_UNIX sockets created
  with the socketpair() syscall to synchronize various bits and pieces
  when isolating services. On kernels prior to 4.18 that do not have
  backported the AppArmor socket mediation patchset this will cause the
  locks to be denied with EACCESS. This causes systemd to be broken in
  LXC and LXD containers that do not run unconfined which is a pretty
  big deal. We have seen various bug reports related to this. See for
  example [1] and [2].

  If feasible it would be excellent if we could backport the socket
  mediation patchset to all LTS kernels. Afaict, this should be 4.4 and
  4.15. This will unbreak a whole range of use-cases.

  The socket mediation patchset is available here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=80a17a5f501ea048d86f81d629c94062b76610d4

  
  [1]: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1575779
  [2]: https://github.com/systemd/systemd/issues/9493

  Thanks!
  Christian

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

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

[Kernel-packages] [Bug 1779640] Re: [Hyper-V] KVP daemon crashes at startup

[Ionut Lenghel]

We haven't seen it in Xenial, but we managed to reproduce it back to the
daily Bionic build from the 2nd of March. We haven't tested Bionic daily
builds before the 2nd of March, nor did I try to reproduce it on Zesty
or or Artful.

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

Title:
  [Hyper-V] KVP daemon crashes at startup

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

Bug description:
  While testing Bionic daily build with kernel 4.15.0-20-generic we saw
  the following issue with the KVP daemon:

  KVP daemon crashes after approximatively 2 minutes of uptime and it enters in 
a failed state. The daemon can be manually started and it enters back in active 
(running) state.
  The error messages from /var/log/syslog after the daemon enters the failed 
state are the following:

  Apr 25 04:28:46 bionicDaily KVP: read failed; error:9 Bad file descriptor
  Apr 25 04:28:46 bionicDaily systemd[1]: hv-kvp-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Apr 25 04:28:46 bionicDaily systemd[1]: hv-kvp-daemon.service: Failed with 
result 'exit-code'.
  Apr 25 04:28:59 bionicDaily systemd[1]: Started Hyper-V KVP Protocol Daemon.

  Note: There was a simmilar issue discussed on this thread
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664663, but the
  fixing commit seems to be inclued in this Bionic build.

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

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

Re: [Kernel-packages] [Bug 1780137] Re: [Regression] EXT4-fs error (device sda1): ext4_validate_inode_bitmap:99: comm stress-ng: Corrupt inode bitmap

[dann frazier]

On Thu, Jul 5, 2018 at 9:35 AM Colin Ian King
<1780...@bugs.launchpad.net> wrote:
>
> What is the stress-ng command that is being run by /usr/lib/plainbox-
> provider-checkbox/bin/disk_stress_ng - without knowing that it's hard to
> figure out the initial stressor conditions

It runs several stress-ng tests against the target. In my
reproduction, I've disabled all but one, and that is 'chdir'. Here's
the invocation:

stress-ng --aggressive --verify --timeout 240 --aio 0 --hdd-opts dsync
--readahead-bytes 16M -k

This is the only stress-ng command that runs after boot/fresh-mkfs.
However, as I mentioned, this stress-ng command alone did not appear
to trigger the issue. I suspect that this is due to sysctls that cert
sets before the running the test, but I have not attempted to prove
that yet.

  -dann

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

Title:
  [Regression] EXT4-fs error (device sda1):
  ext4_validate_inode_bitmap:99: comm stress-ng: Corrupt inode bitmap

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

Bug description:
  We're seeing a very reproducible regression in the bionic kernel
  triggered by the stress-ng chdir test performed by the Ubuntu
  certification suite. Platform is a HiSilicon D05 arm64 server, but we
  don't have reason to believe it is platform specific at this time.

  [Test Case]
  $ sudo apt-add-repository -y ppa:hardware-certification/public
  $ sudo apt install -y canonical-certification-server
  $ sudo mkfs.ext4 /dev/sda1 (Obviously, this should not be your root disk!!)
  $ sudo /usr/lib/plainbox-provider-checkbox/bin/disk_stress_ng sda --base-time 
240 --really-run

  This test runs a series of stress-ng tests against /dev/sda, and fails
  on the "chdir" test. To speed up reproduction, reduce the test list to
  just "chdir" in the disk_stress_ng script. Attempts to reproduce this
  directly with stress-ng have failed - presumably because of other
  environment setup that this script performs (e.g. setting aio-max-nr
  to 524288).

  Our reproduction test is to use a non-root disk because it can lead to
  corruption, and mkfs.ext4'ing the partition just before running the
  test, to get to a pristine fs state.

  I bisected this down to the following commit:

  commit 555bc9b1421f10d94a1192c7eea4a59faca3e711
  Author: Theodore Ts'o 
  Date:   Mon Feb 19 14:16:47 2018 -0500

  ext4: don't update checksum of new initialized bitmaps
  
  BugLink: http://bugs.launchpad.net/bugs/1773233
  
  commit 044e6e3d74a3d7103a0c8a9305dfd94d64000660 upstream.

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

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

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

[Magnus]

Thanks for the quick response to this issue

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

Title:
  failure to boot with linux-image-4.15.0-24-generic

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

Bug description:
  This was the last OK then my 18.04 hangs after an update this morning.
  07:00 AM CEST

  Last Ok in boot was Started gnome display manager. dispatcher service
  .. tem changes.pp link was shut down

  Tried install lightdm from command line and the  response was lastest
  already installed.

  Probably it is what is coming after the lastest OK which is to be the
  error. And here I have lots of guesses..

  Any Ideas ? I need to do some work and I may not be waiting long.

  Search and browsed and now close to give up. Yeah it is a Lenovo.

  Guys: turn of auto update it is a machine killer.

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

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

[Kernel-packages] [Bug 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device

[Steve Langasek]

$ dpkg -c 
/home/lp_archive/ubuntu/pool/main/l/linux/scsi-modules-4.15.0-23-generic-di_4.15.0-23.25_ppc64el.udeb
 |grep mpt3sas
$

** Package changed: debian-installer (Ubuntu) => linux (Ubuntu)

** Changed in: ubuntu-power-systems
 Assignee: Canonical Foundations Team (canonical-foundations) => 
(unassigned)

** Changed in: linux (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
Canonical Kernel (canonical-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/1779815

Title:
  [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI
  based SAS/md raid device

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

Bug description:
  == Comment: #0 - ABDUL HALEEM  - 2018-07-02 03:55:33 ==
  ---Problem Description---
  Ubuntu 18.04.01 ppc64el installer does not detect LSI3008  base SAS disks / 
MD RAID devices 

  Used 20101020ubuntu543 version to install
  
http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/

  Contact Information = abdha...@in.ibm.com 
   
  ---uname output---
  Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = BostonLC
   
  ---boot type---
  Network boot
   

  Installer fails to detect the LSI SAS disks / RAID MD device

  ===console error log===

?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
? /dev/nvme0n1 - 491.5 GB NVMe Device ?
? /dev/nvme1n1 - 98.3 GB NVMe Device  ?
? ?
??
? ?
???



   moves;  selects;  activates buttons

  
  To make sure it detects the disks I had to 
  
  
  Detect disks-->Guided partitioning--> Guided - use entire disk 

  
?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
?  /dev/nvme0n1 - 491.5 GB NVMe Device?
?  /dev/nvme1n1 - 98.3 GB NVMe Device ?
?  SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075  ?
?  SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume  ?
?  SCSI3 (0,2,0) (sdc) - 2.0 TB ATA ST2000NM0125-1YZ  ?
? ?
??
? ?
???

  IPR had similar issue reported  #164932 and fixed with 4.15.0-20,
  looks installer need a fix for LSI (mpt3sas) devices too

  == Comment: #2 - SEETEENA THOUFEEK  - 2018-07-03 
02:01:47 ==
  164932 - refers LP1751813

  == Comment: #3 - SEETEENA THOUFEEK  - 2018-07-03 
02:02:51 ==
  Jul  2 08:49:52 anna-install: Installing mdadm-udeb
  Jul  2 08:49:52 disk-detect: No Intel/DDF RAID disks detected.
  Jul  2 08:49:52 anna-install: Installing dmraid-udeb
  Jul  2 08:49:52 disk-detect: No Serial ATA RAID disks detected
  Jul  2 08:49:53 check-missing-firmware: looking at dmesg again, restarting 
from \[  330.659712\]
  Jul  2 08:49:53 check-missing-firmware: timestamp found, truncating dmesg 
accordingly
  Jul  2 08:49:53 check-missing-firmware: saving timestamp for a later use: 
  Jul  2 08:49:53 check-missing-firmware: /dev/.udev/firmware-missing does not 
exist, skipping
  Jul  2 08:49:53 check-missing-firmware: /run/udev/firmware-missing does not 
exist,

[Kernel-packages] [Bug 1385113] Re: hid-generic 0005:099A:0500.0001: unknown main item tag 0x0

[DevX]

I'm also seeing this issue on a Thinkpad X1 Gen 6-

$ dmesg |grep magicmouse
[ 4650.889726] magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0
[ 4650.890454] magicmouse 0005:05AC:030E.0009: input,hidraw4: BLUETOOTH HID 
v1.60 Mouse [A1339 trackpad] on b4:6b:fc:f3:79:96
[ 4675.733322] magicmouse 0005:05AC:030E.000A: unknown main item tag 0x0
[ 4675.734254] magicmouse 0005:05AC:030E.000A: input,hidraw4: BLUETOOTH HID 
v1.60 Mouse [A1339 trackpad] on b4:6b:fc:f3:79:96
[ 4971.850262] magicmouse 0005:05AC:030E.000B: unknown main item tag 0x0
[ 4971.851130] magicmouse 0005:05AC:030E.000B: input,hidraw4: BLUETOOTH HID 
v1.60 Mouse [A1339 trackpad] on b4:6b:fc:f3:79:96
[ 6591.909033] magicmouse 0005:05AC:030E.000E: unknown main item tag 0x0
[ 6591.909763] magicmouse 0005:05AC:030E.000E: input,hidraw4: BLUETOOTH HID 
v1.60 Mouse [A1339 trackpad] on b4:6b:fc:f3:79:96


Please let me know if you need me to provide additional information.

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

Title:
  hid-generic 0005:099A:0500.0001: unknown main item tag 0x0

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

Bug description:
  Message with Mouse Bluetooth

  [   32.960478] hid-generic 0005:099A:0500.0001: unknown main item tag
  0x0

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-23-generic 3.16.0-23.31
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   3344 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Oct 24 05:22:54 2014
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2014-09-25 (29 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140923)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-23-generic 
root=UUID=0fb75fae-baa3-428b-ace4-498e69ff7fb6 ro rootflags=subvol=@ quiet 
splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-23-generic N/A
   linux-backports-modules-3.16.0-23-generic  N/A
   linux-firmware 1.138
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1779815] [NEW] [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

== Comment: #0 - ABDUL HALEEM  - 2018-07-02 03:55:33 ==
---Problem Description---
Ubuntu 18.04.01 ppc64el installer does not detect LSI3008  base SAS disks / MD 
RAID devices 

Used 20101020ubuntu543 version to install
http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/

Contact Information = abdha...@in.ibm.com 
 
---uname output---
Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
 
Machine Type = BostonLC
 
---boot type---
Network boot
 

Installer fails to detect the LSI SAS disks / RAID MD device

===console error log===

  ?? [!!] Partition disks ???
  ? ?
  ? Note that all data on the disk you select will be erased, but not   ?
  ? before you have confirmed that you really want to make the changes. ?
  ? ?
  ? Select disk to partition:   ?
  ? ?
  ? /dev/nvme0n1 - 491.5 GB NVMe Device ?
  ? /dev/nvme1n1 - 98.3 GB NVMe Device  ?
  ? ?
  ??
  ? ?
  ???



 moves;  selects;  activates buttons


To make sure it detects the disks I had to 


Detect disks-->Guided partitioning--> Guided - use entire disk 


  ?? [!!] Partition disks ???
  ? ?
  ? Note that all data on the disk you select will be erased, but not   ?
  ? before you have confirmed that you really want to make the changes. ?
  ? ?
  ? Select disk to partition:   ?
  ? ?
  ?  /dev/nvme0n1 - 491.5 GB NVMe Device?
  ?  /dev/nvme1n1 - 98.3 GB NVMe Device ?
  ?  SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075  ?
  ?  SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume  ?
  ?  SCSI3 (0,2,0) (sdc) - 2.0 TB ATA ST2000NM0125-1YZ  ?
  ? ?
  ??
  ? ?
  ???

IPR had similar issue reported  #164932 and fixed with 4.15.0-20, looks
installer need a fix for LSI (mpt3sas) devices too

== Comment: #2 - SEETEENA THOUFEEK  - 2018-07-03 02:01:47 
==
164932 - refers LP1751813

== Comment: #3 - SEETEENA THOUFEEK  - 2018-07-03 02:02:51 
==
Jul  2 08:49:52 anna-install: Installing mdadm-udeb
Jul  2 08:49:52 disk-detect: No Intel/DDF RAID disks detected.
Jul  2 08:49:52 anna-install: Installing dmraid-udeb
Jul  2 08:49:52 disk-detect: No Serial ATA RAID disks detected
Jul  2 08:49:53 check-missing-firmware: looking at dmesg again, restarting from 
\[  330.659712\]
Jul  2 08:49:53 check-missing-firmware: timestamp found, truncating dmesg 
accordingly
Jul  2 08:49:53 check-missing-firmware: saving timestamp for a later use: 
Jul  2 08:49:53 check-missing-firmware: /dev/.udev/firmware-missing does not 
exist, skipping
Jul  2 08:49:53 check-missing-firmware: /run/udev/firmware-missing does not 
exist, skipping
Jul  2 08:49:53 check-missing-firmware: no missing firmware in loaded kernel 
modules
Jul  2 08:49:53 main-menu[1425]: (process:8933): ERROR: unsupported sector size 
4096 on /dev/sda.
Jul  2 08:49:53 main-menu[1425]: (process:8933): File descriptor 3 
(pipe:[38926]) leaked on pvs invocation. Parent PID 8940: /bin/sh
Jul  2 08:49:53 main-menu[1425]: (process:8933): File descriptor 4 (/dev/hvc0) 
leaked on pvs invocation. Parent PID 8940: /bin/sh
Jul  2 08:49:53 main-menu[1425]: (process:8933): File descriptor 5 (/dev/hvc0) 
leaked on pvs invocation. Parent PID 8940: /bin/sh
Jul  2 08:49:53 main-menu[1425]: (process:8933): File descriptor 6 (/dev/hvc0) 
leaked on pvs invocation. Parent PID 8940: /bin/sh
Jul  2 08:49:53 main-menu[1425]: (process:8933): ERROR: unsupported sector size 
4096 on /dev/sda.
Jul  2 08:49:53 main-menu[1425]: (process:8933): File descriptor 3 
(pipe:[38926]) leaked on pvs invocation. Parent 

[Kernel-packages] [Bug 1776642] Re: Temporal dithering and impaired graphical performance started appearing on Intel HD 530 graphics

[Patrick Wigmore]

In 4.15.0-25-generic, the symptoms have changed. The objectionable
temporal dithering persists in virtual terminals (e.g. Ctrl+Alt+F1) but
under KDE Plasma 5 it has disappeared or become imperceptible, and high
fps video playback is no longer choppy.

However, with this kernel, the blurring effect applied to semi-
transparent Plasma widget backgrounds has stopped working (replaced with
opaque background).

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

Title:
  Temporal dithering and impaired graphical performance started
  appearing on Intel HD 530 graphics

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am experiencing a regression in linux-image-generic-hwe-16.04 with
  Intel HD Graphics 530 (Core i5-6600T), starting in 4.13.0-43
  (considering only kernels which appear in my GRUB menu).

  Some form of spatio-temporal dithering has been enabled. This is
  causing a shimmering effect and visible dithering patterns (like woven
  textile) which are noticeable on photographs and areas of similar
  colour. 1px borders in the UI can appear to have a "marching ants"
  effect.

  The effect is visible both under Xorg and in a virtual console
  (Ctrl+Alt+F1), if the displayed colours are suitable to trigger it.

  Booting 4.13.0-41 eliminates the temporal dithering.

  This occurs on a (presumed) 6bpp laptop LCD panel, so dithering is
  necessary, but in previous kernels only a form of spatial dithering is
  applied, which is less visually obvious.

  Concurrent with the temporal dithering, I have also noticed general poor 
graphical performance with the affected kernels. E.g. 50fps and 60fps video 
playback is choppy, sometimes slow redraw and other graphical glitches on UI 
elements. Like the temporal dithering, these additional problems disappear if I 
revert to 4.13.0-41.
  ---
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  patrick1976 F pulseaudio
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=72e179a8-b27c-42d3-9523-8f1cceacaa64
  InstallationDate: Installed on 2016-09-16 (634 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: PC Specialist Limited N350DW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-45-generic 
root=UUID=deeef076-c1e1-47ec-8ee4-d3b56fa179f9 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-45-generic N/A
   linux-backports-modules-4.13.0-45-generic  N/A
   linux-firmware 1.157.19
  Tags:  xenial xenial
  Uname: Linux 4.13.0-45-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: False
  dmi.bios.date: 05/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N350DW
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd05/26/2016:svnPCSpecialistLimited:pnN350DW:pvrNotApplicable:rvnCLEVO:rnN350DW:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: N350DW
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist Limited

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

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

Here are the md5sum hashes of the files needed to install the test
kernel:

d5f16dcf0080db1268d3b3477c911cd7  linux-image-
unsigned-4.15.0-23-generic_4.15.0-23.26~lp1777338Commit8eca6add0_amd64.deb

1d7504d8e691ba64d552a2d507179882  linux-
modules-4.15.0-23-generic_4.15.0-23.26~lp1777338Commit8eca6add0_amd64.deb

b004fa6244e3e038b0d67c86e0218536  linux-modules-
extra-4.15.0-23-generic_4.15.0-23.26~lp1777338Commit8eca6add0_amd64.deb

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 1780137] Re: [Regression] EXT4-fs error (device sda1): ext4_validate_inode_bitmap:99: comm stress-ng: Corrupt inode bitmap

[Colin Ian King]

What is the stress-ng command that is being run by /usr/lib/plainbox-
provider-checkbox/bin/disk_stress_ng - without knowing that it's hard to
figure out the initial stressor conditions

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

Title:
  [Regression] EXT4-fs error (device sda1):
  ext4_validate_inode_bitmap:99: comm stress-ng: Corrupt inode bitmap

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

Bug description:
  We're seeing a very reproducible regression in the bionic kernel
  triggered by the stress-ng chdir test performed by the Ubuntu
  certification suite. Platform is a HiSilicon D05 arm64 server, but we
  don't have reason to believe it is platform specific at this time.

  [Test Case]
  $ sudo apt-add-repository -y ppa:hardware-certification/public
  $ sudo apt install -y canonical-certification-server
  $ sudo mkfs.ext4 /dev/sda1 (Obviously, this should not be your root disk!!)
  $ sudo /usr/lib/plainbox-provider-checkbox/bin/disk_stress_ng sda --base-time 
240 --really-run

  This test runs a series of stress-ng tests against /dev/sda, and fails
  on the "chdir" test. To speed up reproduction, reduce the test list to
  just "chdir" in the disk_stress_ng script. Attempts to reproduce this
  directly with stress-ng have failed - presumably because of other
  environment setup that this script performs (e.g. setting aio-max-nr
  to 524288).

  Our reproduction test is to use a non-root disk because it can lead to
  corruption, and mkfs.ext4'ing the partition just before running the
  test, to get to a pristine fs state.

  I bisected this down to the following commit:

  commit 555bc9b1421f10d94a1192c7eea4a59faca3e711
  Author: Theodore Ts'o 
  Date:   Mon Feb 19 14:16:47 2018 -0500

  ext4: don't update checksum of new initialized bitmaps
  
  BugLink: http://bugs.launchpad.net/bugs/1773233
  
  commit 044e6e3d74a3d7103a0c8a9305dfd94d64000660 upstream.

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

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

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 1780067] Re: zfcp: fix infinite iteration on ERP ready list

[Joseph Salisbury]

built a test kernel with commit
fa89adba1941e4f3b213399b81732a5c12fd9131.  The test kernel can be
downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1780067

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

Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you need to install the 
linux-image and linux-image-extra .deb packages.
• If the test kernel is 4.15(Bionic) or newer, you need to install the 
linux-modules, linux-modules-extra and linux-image-unsigned .deb packages.

Thanks in advance!

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

Title:
  zfcp: fix infinite iteration on ERP ready list

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  Please backport:
  commit fa89adba1941e4f3b213399b81732a5c12fd9131
  scsi: zfcp: fix infinite iteration on ERP ready list
  
  zfcp_erp_adapter_reopen() schedules blocking of all of the adapter's
  rports via zfcp_scsi_schedule_rports_block() and enqueues a reopen
  adapter ERP action via zfcp_erp_action_enqueue(). Both are separately
  processed asynchronously and concurrently.
  
  Blocking of rports is done in a kworker by zfcp_scsi_rport_work(). It
  calls zfcp_scsi_rport_block(), which then traces a DBF REC "scpdely" via
  zfcp_dbf_rec_trig().  zfcp_dbf_rec_trig() acquires the DBF REC spin lock
  and then iterates with list_for_each() over the adapter's ERP ready list
  without holding the ERP lock. This opens a race window in which the
  current list entry can be moved to another list, causing list_for_each()
  to iterate forever on the wrong list, as the erp_ready_head is never
  encountered as terminal condition.
  
  Meanwhile the ERP action can be processed in the ERP thread by
  zfcp_erp_thread(). It calls zfcp_erp_strategy(), which acquires the ERP
  lock and then calls zfcp_erp_action_to_running() to move the ERP action
  from the ready to the running list.  zfcp_erp_action_to_running() can
  move the ERP action using list_move() just during the aforementioned
  race window. It then traces a REC RUN "erator1" via zfcp_dbf_rec_run().
  zfcp_dbf_rec_run() tries to acquire the DBF REC spin lock. If this is
  held by the infinitely looping kworker, it effectively spins forever.
  
  Example Sequence Diagram:
  
  ProcessERP Thread rport_work
  ---------
  zfcp_erp_adapter_reopen()
  zfcp_erp_adapter_block()
  zfcp_scsi_schedule_rports_block()
  lock ERP  zfcp_scsi_rport_work()
  zfcp_erp_action_enqueue(ZFCP_ERP_ACTION_REOPEN_ADAPTER)
  list_add_tail() on ready  !(rport_task==RPORT_ADD)
  wake_up() ERP thread  zfcp_scsi_rport_block()
  zfcp_dbf_rec_trig()zfcp_erp_strategy()zfcp_dbf_rec_trig()
  unlock ERPlock DBF REC
  zfcp_erp_wait()lock ERP
  |  zfcp_erp_action_to_running()
  | list_for_each() ready
  |  list_move()  current entry
  |ready to running
  |  zfcp_dbf_rec_run()   endless loop over running
  |  zfcp_dbf_rec_run_lvl()
  |  lock DBF REC spins forever
  
  Any adapter recovery can trigger this, such as setting the device offline
  or reboot.
  
  V4.9 commit 4eeaa4f3f1d6 ("zfcp: close window with unblocked rport
  during rport gone") introduced additional tracing of (un)blocking of
  rports. It missed that the adapter->erp_lock must be held when calling
  zfcp_dbf_rec_trig().
  
  This fix uses the approach formerly introduced by commit aa0fec62391c
  ("[SCSI] zfcp: Fix sparse warning by providing new entry in dbf") that got
  later removed by commit ae0904f60fab ("[SCSI] zfcp: Redesign of the debug
  tracing for recovery actions.").
  
  Introduce zfcp_dbf_rec_trig_lock(), a wrapper for zfcp_dbf_rec_trig() that
  acquires and releases the adapter->erp_lock for read.
  
  Reported-by: Sebastian Ott 
  Signed-off-by: Jens Remus 
  Fixes: 4eeaa4f3f1d6 ("zfcp: close window with unblocked rport during 
rport gone")
  Cc:  # 2.6.32+
  Reviewed-by: Benjamin Block 
  Signed-off-by: Steffen Maier 
  Signed-off-by: Martin K. Petersen 

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

-- 
Mailing list: https://launchpad.net/~kernel-packa

[Kernel-packages] [Bug 1780124] Re: linux-gcp: 4.15.0-1012.12~16.04.2 -proposed tracker

[Brad Figg]

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

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

Title:
  linux-gcp: 4.15.0-1012.12~16.04.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow 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  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 --
  kernel-stable-master-bug: 1780112
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1779353] Re: linux-oem: 4.13.0-1032.36 -proposed tracker

[Brad Figg]

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1779349
  phase: Uploaded

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-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: 1779349
  phase: Uploaded

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

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