[Kernel-packages] [Bug 571770]

2019-01-11 Thread mirh
Many of the linked issues report the problem fixed (broadly, by the time
of ubuntu 14.04).

Is this still a thing?

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

Title:
  Thread [hd-audio0] consuming excessive amounts of CPU, audio crackling

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: linux-image-2.6.32-22-generic

  Sometimes during audio playback, a kernel thread named "[hd-audio0]"
  will consume excessive amounts of CPU and cause  audio crackling. It
  seems to be more easily triggered when displaying video in fullscreen
  (or Rhythmbox visualizations) or dragging windows around while playing
  music, somehow relating it graphics operations (running default radeon
  driver with KMS and Compiz).

  This all started after moving from Ubuntu Karmic to Lucid (never had
  this problem before).

  Setting package to kernel, since it's probably alsa snd_hda_intel
  kernel module which is to blame.

  Ubuntu 10.04 x86, Intel Core Duo 2GHz, 3GB RAM, ATI X1400 Radeon Mobility 
graphics.
  Audio chip: Analog Devices AD1981 [HDA]

  WORKAROUND: Disabling radeon KMS makes all the audio crackling go
  away.

  Attaching:
  * Screenshot of top running over Rhythmbox w/fullscreen visualizations, 
showing [hd-audio0] consuming more CPU than everything else at the time (audio 
crackles).
  * Output of "lspci -vvnn"
  * Output of "dmesg"
  * Contents of /proc/interrupts
  * ALSA info, as provided by the alsa-info.sh script.

  Related to this: https://bugzilla.kernel.org/show_bug.cgi?id=14935 ???

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

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


[Kernel-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power

2019-01-11 Thread Fink Nottle
Attached powertop images. I'm not sure how accurate powertop's values
and distributions are. With prime-select intel, the total estimated
power remains high although it doesn't attribute it to nvidia. bbswitch
also stays on. I've also attached a bbswitch off capture after prime-
select intel. That actually seems to turn the gpu off. There's also a
default capture with nouveau drivers (i.e., the nvidia gpu is not in
use). There are a few other issues with prime-selct too. prime-select
intel glitches the lightdm login screen. You can't see the text entry
field. prime-query is also not accurate always. Sometimes it says it's
nvidia, but nvidia drivers are not loaded.

** Attachment added: "powertop.zip"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1778011/+attachment/5228576/+files/powertop.zip

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

Title:
  SRU: PRIME Power Saving mode draws too much power

Status in HWE Next:
  New
Status in gdm3 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in sddm package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in gdm3 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Released
Status in nvidia-prime source package in Bionic:
  Fix Released
Status in nvidia-settings source package in Bionic:
  Fix Released
Status in sddm source package in Bionic:
  Confirmed
Status in ubuntu-drivers-common source package in Bionic:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Relying on the nouveau driver and on the vga switcheroo (to get around a 
change in systemd LP: #1777099) caused increased power consumption, and slowed 
down the switching process.

  Furthermore, if the main X/Xwayland session was started by Gdm when
  the nvidia driver was loaded, the session will keep the nvidia module
  loaded, and prevent the system from switching off the dGPU. Also, the
  nouveau driver will be loaded, if nvidia is not, and this can cause
  problems to unsupported NVIDIA GPUs.

  The solution involves the following changes:

  1) Solving the problem in systemd (LP: #1777099)

  2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia
  modules, and to allow the PCI device to sleep.

  3) Making a slight change to the current patch in Gdm, used to call
  the PRIME scripts before and after a Gdm session (so that gpu-manager
  gets actually called on log out)

  4) Adding code in gpu-manager to kill the main X/Xwayland session on
  log out, if the session is preventing us from unloading the nvidia
  driver. A new X/Xwayland session will be created after unload the
  module.

  5) Removing the systemd service that loads nouveau from the nvidia
  packages.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 *

  2) Make sure the nvidia packages are installed, and enable performance mode 
(if it is already enabled, call "sudo prime-select intel" first):
  sudo prime-select nvidia

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Select power saving mode:
  sudo prime-select intel

  5) Log out and log back in

  6) Check if the nvidia driver is still loaded:
  lsmod | grep nvidia

  [Regression Potential]
  Low, as hybrid graphics support does not work correctly, and the changes only 
affect this use case.

  _
  * Steps to test the updates:

  1) Enable the bionic-proposed repositories

  2) Create /etc/apt/preferences.d/proposed-updates with the following
  content:

  Package: *
  Pin: release a=bionic-proposed
  Pin-Priority: 400

  3) Update the list of packages:

  sudo apt-get update

  4) Install the packages from -proposed using the following command:

  sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic-
  proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-
  proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic-
  proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390
  /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia-
  ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed

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

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


[Kernel-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind

2019-01-11 Thread Mathew Hodson
** No longer affects: initramfs-tools (Ubuntu)

** No longer affects: initramfs-tools (Ubuntu Xenial)

** No longer affects: initramfs-tools (Ubuntu Zesty)

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

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Xenial:
  Fix Released
Status in dkms source package in Zesty:
  Fix Released
Status in dkms package in Debian:
  New

Bug description:
  [Impact]
  If a dkms package is installed which has REMAKE_INITRD or the same setting 
has be manually configured by a user then when a kernel is removed its possible 
for an ".old-dkms" file to be left in /boot with no associated kernel.

  [Test Case]
  On a system with two old kernels and one new kernel available in -updates:
  1) install r8168-dkms
  2) install the dkms module for the old kernel e.g. 'sudo dkms install -m 
r8168 -v 8.041.00 -k 4.4.0-31-generic'
  3) upgrade your kernel e.g. "sudo apt install linux-image-generic'
  4) sudo apt autoremove
  5) observe something like "initrd.img-4.4.0-31-generic.old-dkms" in /boot 
without a corresponding "initrd.img-4.4.0-31-generic"

  With the version of dkms in -proposed, the .old-dkms file will be
  removed when the kernel is auto removed.

  [Regression Potential]
  Somebody out there might expect the .old-dkms file to be kept, but that seems 
like an odd expectation.

  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  Note:  Filling up the /boot partition causes updates to fail.

  ProblemType: BugDistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: allSourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1519718] Re: Screen doesn't change after connecting a BT mouse and no cursor displayed.

2019-01-11 Thread Launchpad Bug Tracker
[Expired for ubuntu-system-settings (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: ubuntu-system-settings (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Screen doesn't change after connecting a BT mouse and no cursor
  displayed.

Status in bluez package in Ubuntu:
  Won't Fix
Status in ubuntu-system-settings package in Ubuntu:
  Expired

Bug description:
  ~$ system-image-cli -i
  current build number: 177
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-11-25 11:02:09
  version version: 177
  version ubuntu: 20151124
  version device: 20151019-6d4a3ab
  version custom: 2015-918-8-52

  Reproduce steps:
  Setup:Bluetooth mouse set to discovery mode.
  Step 1.Unlock the phone.
  Step 2.Swipe down the Bluetooth indicator.
  Step 3.Tap on Bluetooth settings.
  Step 4.Wait a moment for the device to appear in the list.
  Step 5.App switches to the device page, tap on connect.

  Actual result:Screen doesn't change after connecting a BT mouse and no
  cursor displayed.

  Expected result:App switches to Windowed mode and turns back to the
  Main Setting page for Bluetooth.

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

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


[Kernel-packages] [Bug 1802700] Re: Cannot install graphic drivers

2019-01-11 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Cannot install graphic drivers

Status in linux package in Ubuntu:
  Expired
Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  i just instal linux 18.04 but the graphic drivers not installed, so my
  maximum resolution is 360p. I use Lenovo G50-80 with graphic AMR
  radeon M330

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 11 12:01:41 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   amdgpu, 18.20-673703, 4.15.0-29-generic, x86_64: installed
   amdgpu, 18.20-673703, 4.15.0-38-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:390c]
 Subsystem: Lenovo Radeon R5 M330 [17aa:390c]
  InstallationDate: Installed on 2018-11-11 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO INVALID
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=2c4eae76-fae9-48ac-98de-2dfbd276535b ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/23/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B0CN93WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: NANANANA NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: INVALID
  dmi.modalias: 
dmi:bvnLENOVO:bvrB0CN93WW:bd07/23/2015:svnLENOVO:pnINVALID:pvrINVALID:rvnLENOVO:rnVIUU4:rvrNANANANANODPK:cvnLENOVO:ct10:cvrINVALID:
  dmi.product.family: IDEAPAD
  dmi.product.name: INVALID
  dmi.product.version: INVALID
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Kernel-packages] [Bug 1802700] Re: Cannot install graphic drivers

2019-01-11 Thread Launchpad Bug Tracker
[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Cannot install graphic drivers

Status in linux package in Ubuntu:
  Expired
Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  i just instal linux 18.04 but the graphic drivers not installed, so my
  maximum resolution is 360p. I use Lenovo G50-80 with graphic AMR
  radeon M330

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 11 12:01:41 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   amdgpu, 18.20-673703, 4.15.0-29-generic, x86_64: installed
   amdgpu, 18.20-673703, 4.15.0-38-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:390c]
 Subsystem: Lenovo Radeon R5 M330 [17aa:390c]
  InstallationDate: Installed on 2018-11-11 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO INVALID
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=2c4eae76-fae9-48ac-98de-2dfbd276535b ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/23/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B0CN93WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: NANANANA NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: INVALID
  dmi.modalias: 
dmi:bvnLENOVO:bvrB0CN93WW:bd07/23/2015:svnLENOVO:pnINVALID:pvrINVALID:rvnLENOVO:rnVIUU4:rvrNANANANANODPK:cvnLENOVO:ct10:cvrINVALID:
  dmi.product.family: IDEAPAD
  dmi.product.name: INVALID
  dmi.product.version: INVALID
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Kernel-packages] [Bug 1802832] Re: ethtools report i40e as 10G instead the real 1G

2019-01-11 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  ethtools report i40e  as 10G instead the real 1G

Status in linux package in Ubuntu:
  Expired

Bug description:
  ethtools report i40e  as 10G instead the real 1G on Ubuntu 16.04.5 ga-
  kernel

  With the 4.4 driver, this device reports being a 10Gb device when looking at 
ethtool:
  Settings for enp61s0f0:
Supported ports: [ TP ]
Supported link modes:   1000baseT/Full 
1baseT/Full 
Supported pause frame use: Symmetric
Supports auto-negotiation: Yes
Advertised link modes:  1000baseT/Full 
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: external
Auto-negotiation: on
MDI-X: Unknown
Supports Wake-on: g
Wake-on: g
Current message level: 0x000f (15)
   drv probe link timer
Link detected: yes

  The same device on the same system running Bionic, on the other hand, shows 
the correct speed:
  Settings for enp61s0f0:
Supported ports: [ TP ]
Supported link modes:   1000baseT/Full 
Supported pause frame use: Symmetric
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes:  1000baseT/Full 
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
MDI-X: Unknown
Supports Wake-on: g
Wake-on: d
Current message level: 0x0007 (7)
   drv probe link
Link detected: yes

  We did not check, but I presume that the 4.15 HWE kernel on 16.04 will
  also show the speed correctly.

  This affects certification as we rely on ethtool to accurately relay
  connection speed and supported speeds to verify that the card is being
  tested at the correct speeds.

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

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


[Kernel-packages] [Bug 1810861] Re: USB type C audio adapter (from a Pixel 3) doesn't produce any sound

2019-01-11 Thread Nicholas Johnson
How i fixed the issue was simply reinstalling the OS, i had no personal
files installed onto it, only on the windows dual boot side, so that had
fixed the issue for a while, but after rebooting just after a day of
running the reinstalled os, the bug was back, and simultaneously several
other bugs i had been experiencing at the same time as this one, such
as, terminal not launching (i use xterm to launch it) sometimes nautilus
not launching, having to use xterm for that, even gedit, and all it
takes is a simple reboot, now i'm beginning to think i should not be
using ubuntu 18.10, but i like ubuntu 18.10 so much better than 18.04,
the theme, some better performance and loading times and other things
are much appreciated but i keep getting this bug, i think its not just
an audio glitch, but a system wide thing, and i have no idea how it
happens

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

Title:
  USB type C audio adapter (from a Pixel 3) doesn't produce any sound

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I use a logitech z200 that works fine, i use it with a usb type c adapter 
that came with my pixel 3, my speakers arent shown at all in the settings or 
make sound, its not the usb c adapter because it works fine on my windows dual 
boot and has worked at one point on ubuntu, regardless of the fact that ubuntu 
has never recognized my thunderbolt port, i use ubuntu 18.10 by the way when i 
use lsusb, one of the results is google inc., which is my headphone adapter, i 
can tell because when i unplug it it goes away, even when i plug it into the 
3.5 mm headphone jack it doesn't work, i don't know if im forgetting something 
or not, this is the second time im typing this because i accidentally closed 
the first tab of this, whats interesting, is now that i go to alsamixer, and 
press f6 i see option 1.Headphone Adapter, i select it and set the volume all 
the way up and go to something that makes audio and nothing happens, then i 
unplug it and see if it disappears, surely enough it does
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-10-21 (78 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   lono wireless extensions.
   
   enp37s0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: pulseaudio 1:12.2-0ubuntu4
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=db7dbcfb-4be9-4405-88a9-8d91489e5a68 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/05/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.00
  dmi.board.name: AB350 Gaming K4
  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.:bvrP5.00:bd07/05/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages

[Kernel-packages] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

2019-01-11 Thread Josh Krull
I found a solution to my particular issue. 
DISCLAIMER: I'm not positive that I experienced the same issue as other 
commenters since the problem was more pronounced than others have been 
describing. Since this is a new system, this was the first time I tried to 
install Ubuntu. I'll try to describe what I found in some detail since this was 
thread seemed like the most pertinent to my issue it may help others.

In my case I had neglected to enroll an MDK correctly. I was able to use
the system a little longer by using Ctrl-Alt-F2 to login instead of
using X. Once in the terminal I was able to see some useful messages
when the lockup occured. In one instance I got a hard lockup:

[99.065138] NMI watchdog: Watchdog detected hard LOCKUP on cpu9

The more useful message occurred during another lockup which was a
series of messages from nouveau. Here are the first and last messages:

[28.832124] nouveau :01:00.0: secboot: error during falcon reset: -110
[43.811710] nouveau :01:00.0: systemd-logind[1025]: failed to idle 
channel 2 [systemd-logind[1025]]

Steps to reproduce (from memory, not verified): 
 - Select proprietary drivers during install with UEFI boot mode and Secure 
Boot enabled.
 - Enter password for MDK
 - Reboot
 - MDK management screen displayed, select continue to boot (THIS WAS THE 
MISTAKE)

I had never used an MDK before, so did not know that you had to elect to
"Enroll" the MDK that was generated during the install process. I had
expected to be prompted for a password at some point during the reboot
based on the language in the installer. There is some user interaction
required at that menu to enroll the MDK at which point the user is
prompted for a password and then a reboot can be completed.

Description of MDK with some screenshots:
https://wiki.ubuntu.com/UEFI/SecureBoot/DKMS

Steps to address issue once reproduced (basically remove nouveau,
install NVIDIA official driver):

I blacklisted a number of modules in /etc/modprobe.d/blacklist.conf:

blacklist amd76x_edac 
blacklist vga16fb
blacklist nouveau
blacklist rivafb
blacklist nvidiafb
blacklist rivatv

I got the list of modules from: https://askubuntu.com/questions/481414
/install-nvidia-driver-instead-of-nouveau however I did not download the
driver from NVIDIA, I used one from the repository:

sudo apt install nvidia-driver-410

This laptop uses an i7-8750H which (I think) contains integrated
graphics. The 1060 should be feeding the display, but I'm not sure if
the presence of a second graphics adapter introduced a conflict.

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

Title:
  Random unrecoverable freezes on Ubuntu 18.10

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

Bug description:
  First thing I notice is that the mouse cursor freezes as I'm using it,
  then I hit the CAPS LOCK key and the LED indicator doesn't respond.
  Then I try the "REISUB" command, but it doesn't do anything either.
  Only a hard reset works, pressing down the power button for a few
  seconds.

  How to reproduce?
  I couldn't figure out a consistent method. It is still random to me.

  Version: Ubuntu 4.18.0-10.11-generic 4.18.12
  System information attached.

  Also happens under Arch Linux and Fedora.
  I've talked to another user on IRC who seems to be having the same freezes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsilva 1213 F pulseaudio
   /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 

[Kernel-packages] [Bug 1804841] Re: iwlwifi Microcode SW error detected. Restarting 0x2000000.

2019-01-11 Thread Christian Ehrhardt 
Hi Seth,
to answer at least for me - it never worked on my system.
No "degradation on upgrade" at least for me, just never worked.

I'm considering filing a bug with Intel and or Lenovo (for a remote chance to 
get their FW developers to look at it) - if only I knew where.
If someone did that in the past let me know where the best place to start would 
be.

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

Title:
  iwlwifi Microcode SW error detected.  Restarting 0x200.

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  This seems to be a return of an existing bug, in newer hardware and
  microcode versions.

  Wireless card: Intel Corporation Wireless 8265 / 8275 [8086:24fd] (rev 78)
  Firmware version: 34.0.1
  Description:Ubuntu 18.04.1 LTS

  Frequent errors as soon as I connect to wifi:
  Microcode SW error detected.  Restarting 0x200.

  Expected to happen: Great and stable wifi like a couple of weeks ago
  What happens: very slow, intermittent internet access, lots of ping loss

  Found a suggestion of a workaround: adding these lines to
  /etc/NetworkManager/NetworkManager.conf

  [device]
  wifi.scan-rand-mac-address=no

  These lines were already there, not added by me.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.173.2 [modified: lib/firmware/iwlwifi-8265-36.ucode]
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Fri Nov 23 15:23:54 2018
  Dependencies:

  InstallationDate: Installed on 2018-09-03 (81 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1804841] Re: iwlwifi Microcode SW error detected. Restarting 0x2000000.

2019-01-11 Thread Christian Ehrhardt 
Since some similar issues in the past were reported to be related to
kernel updates lets add a task

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

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

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

Title:
  iwlwifi Microcode SW error detected.  Restarting 0x200.

Status in linux package in Ubuntu:
  New
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  This seems to be a return of an existing bug, in newer hardware and
  microcode versions.

  Wireless card: Intel Corporation Wireless 8265 / 8275 [8086:24fd] (rev 78)
  Firmware version: 34.0.1
  Description:Ubuntu 18.04.1 LTS

  Frequent errors as soon as I connect to wifi:
  Microcode SW error detected.  Restarting 0x200.

  Expected to happen: Great and stable wifi like a couple of weeks ago
  What happens: very slow, intermittent internet access, lots of ping loss

  Found a suggestion of a workaround: adding these lines to
  /etc/NetworkManager/NetworkManager.conf

  [device]
  wifi.scan-rand-mac-address=no

  These lines were already there, not added by me.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.173.2 [modified: lib/firmware/iwlwifi-8265-36.ucode]
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Fri Nov 23 15:23:54 2018
  Dependencies:

  InstallationDate: Installed on 2018-09-03 (81 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1810861] Re: USB type C audio adapter (from a Pixel 3) doesn't produce any sound

2019-01-11 Thread Nicholas Johnson
I was able to fix the issue my own way

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

Title:
  USB type C audio adapter (from a Pixel 3) doesn't produce any sound

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I use a logitech z200 that works fine, i use it with a usb type c adapter 
that came with my pixel 3, my speakers arent shown at all in the settings or 
make sound, its not the usb c adapter because it works fine on my windows dual 
boot and has worked at one point on ubuntu, regardless of the fact that ubuntu 
has never recognized my thunderbolt port, i use ubuntu 18.10 by the way when i 
use lsusb, one of the results is google inc., which is my headphone adapter, i 
can tell because when i unplug it it goes away, even when i plug it into the 
3.5 mm headphone jack it doesn't work, i don't know if im forgetting something 
or not, this is the second time im typing this because i accidentally closed 
the first tab of this, whats interesting, is now that i go to alsamixer, and 
press f6 i see option 1.Headphone Adapter, i select it and set the volume all 
the way up and go to something that makes audio and nothing happens, then i 
unplug it and see if it disappears, surely enough it does
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-10-21 (78 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   lono wireless extensions.
   
   enp37s0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: pulseaudio 1:12.2-0ubuntu4
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=db7dbcfb-4be9-4405-88a9-8d91489e5a68 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/05/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.00
  dmi.board.name: AB350 Gaming K4
  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.:bvrP5.00:bd07/05/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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


[Kernel-packages] [Bug 1805920] Re: iPXE ignores vlan 0 traffic

2019-01-11 Thread Vern Hart
After realizing there are packages in the ci build [1] I installed the
following version from there:

1.0.0+git-20180124.fbe8c52d-0ubuntu4.1

I redefined the testipxe vm from the above test, and it also
successfully pxe booted.

[1]: https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/3560/+packages

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

Title:
  iPXE ignores vlan 0 traffic

Status in MAAS:
  Invalid
Status in ipxe package in Ubuntu:
  Fix Released
Status in ipxe-qemu-256k-compat package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in ipxe source package in Trusty:
  Won't Fix
Status in ipxe source package in Xenial:
  Won't Fix
Status in ipxe source package in Bionic:
  Incomplete
Status in ipxe source package in Cosmic:
  Incomplete
Status in ipxe source package in Disco:
  Fix Released

Bug description:
  [Impact]

   * VLAN 0 is special (for QoS actually, not a real VLAN)
   * Some components in the stack accidentally strip it, so does ipxe in
     this case.
   * Fix by porting a fix that is carried by other distributions as upstream
     didn't follow the suggestion but it is needed for the use case affected
     by the bug here (Thanks Andres)

  [Test Case]

   * Comment #42 contains a virtual test setup to understand the case but it 
 does NOT trigger the isse. That requires special switch HW that adds 
 VLAN 0 tags for QoS. Therefore Vern (reporter) will test that on a 
 customer site with such hardware being affected by this issue.

  [Regression Potential]

   * The only reference to VLAN tags on iPXE boot that we found was on iBFT
     boot for SCSI, we tested that in comment #34 and it still worked fine.
   * We didn't see such cases on review, but there might be use cases that
     made some unexpected use of the headers which are now stripped. But
     that seems wrong.

  [Other Info]

   * n/a

  ---

  I have three MAAS rack/region nodes which are blades in a Cisco UCS
  chassis. This is an FCE deployment where MAAS has two DHCP servers,
  infra1 is the primary and infra3 is the secondary. The pod VMs on
  infra1 and infra3 PXE boot fine but the pod VMs on infra2 fail to PXE
  boot. If I reconfigure the subnet to provide DHCP on infra2 (either as
  primary or secondary) then the pod VMs on infra2 will PXE boot but the
  pod VMs on the demoted infra node (that no longer serves DHCP) now
  fail to PXE boot.

  While commissioning a pod VM on infra2 I captured network traffic with
  tcpdump on the vnet interface.

  Here is the dump when the PXE boot fails (no dhcp server on infra2):
  https://pastebin.canonical.com/p/THW2gTSv4S/

  Here is the dump when PXE boot succeeds (when infra2 is serving dhcp):
  https://pastebin.canonical.com/p/HH3XvZtTGG/

  The only difference I can see is that in the unsuccessful scenario,
  the reply is an 802.1q packet -- it's got a vlan tag for vlan 0.
  Normally vlan 0 traffic is passed as if it is not tagged and indeed, I
  can ping between the blades with no problem. Outgoing packets are
  untagged but incoming packets are tagged vlan 0 -- but the ping works.
  It seems vlan 0 is used as a part of 802.1p to set priority of
  packets. This is separate from vlan, it just happens to use that
  ethertype to do the priority tagging.

  Someone confirmed to me that, in the iPXE source, it drops all packets
  if they are vlan tagged.

  The customer is unable to figure out why the packets between blades is
  getting vlan tagged so we either need to figure out how to allow iPXE
  to accept vlan 0 or the customer will need to use different equipment
  for the MAAS nodes.

  I found a conversation on the ipxe-devel mailing list that suggested a
  commit was submitted and signed off but that was from 2016 so I'm not
  sure what became of it. Notable messages in the thread:

  http://lists.ipxe.org/pipermail/ipxe-devel/2016-April/004916.html
  http://lists.ipxe.org/pipermail/ipxe-devel/2016-July/005099.html

  Would it be possible to install a local patch as part of the FCE
  deployment? I suspect the patch(es) mentioned in the above thread
  would require some modification to apply properly.

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

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


[Kernel-packages] [Bug 1809215] Re: intel wifi 8260 stopped working after bios upgrade

2019-01-11 Thread Seth Forshee
** Changed in: linux-firmware (Ubuntu)
   Status: New => Invalid

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

Title:
  intel wifi 8260 stopped working after bios upgrade

Status in linux-firmware package in Ubuntu:
  Invalid

Bug description:
  Good day, my wifi stopped connecting to WPA2 Enterprise, right after
  I've upgraded BIOS. The BIOS upgrade could cause this; I was also
  playing with bluetooth headphones which could be connected.

  The Wifi works properly in Windows 10, so I assume it's not a hardware
  bug.

  The interesting line in dmesg:

  [  133.921138] iwlwifi :04:00.0: Microcode SW error detected.
  Restarting 0x9200.

  I thought the microcode file could be corrupted, so I've tried apt
  install --reinstall linux-firmware and reboot, but that didn't work.

  dmidecode -s bios-version says N1EET81W (1.54 ); dmesg says LENOVO
  20EN0005MS/20EN0005MS, BIOS N1EET81W (1.54 ) 11/14/2018

  Thank you for providing any pointers...

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-firmware 1.175.1
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 20 08:46:29 2018
  Dependencies:
   
  InstallationDate: Installed on 2016-09-05 (835 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to cosmic on 2018-09-28 (82 days ago)

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

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


[Kernel-packages] [Bug 1811463] Re: Touchpad does not initialize Lenovo Ideapad 320-15

2019-01-11 Thread Andrey
** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  Touchpad does not initialize Lenovo Ideapad 320-15

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  Starting with Mint 18.1, I cannot start the SYNA2b37 touchpad (HID device on 
the I2C bus).
  Were tried all methods from Google

  dmesg:
  andrey@andrey-Lenovo:~$ dmesg |grep i2c
  [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=6303f611-7433-4638-a26e-13c707e21802 ro quiet splash 
i2c_designware_core.dyndbg=+p i2c-hid.debug=1 vt.handoff=1
  [0.00] Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=6303f611-7433-4638-a26e-13c707e21802 ro quiet splash 
i2c_designware_core.dyndbg=+p i2c-hid.debug=1 vt.handoff=1
  [3.847975] i2c /dev entries driver
  [9.197510] i2c_designware i2c_designware.0: Standard-mode HCNT:LCNT = 
552:652
  [9.197515] i2c_designware i2c_designware.0: Fast-mode HCNT:LCNT = 100:200
  [9.201135] i2c_hid i2c-SYNA2B37:00: i2c-SYNA2B37:00 supply vdd not found, 
using dummy regulator
  [9.201170] i2c_designware i2c_designware.0: i2c_dw_xfer: msgs: 1
  [9.201199] i2c_designware i2c_designware.0: enabled=0x1 stat=0x10
  [9.201238] i2c_designware i2c_designware.0: enabled=0x1 stat=0x750
  [9.202144] i2c_designware i2c_designware.0: i2c_dw_handle_tx_abort: slave 
address not acknowledged (7bit mode)

  andrey@andrey-Lenovo:~$ xinput
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Telink 2.4G Mouse Mouse id=8[slave  pointer 
 (2)]
  ⎜   ↳ Telink 2.4G Mouse Consumer Control  id=9[slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Video Bus   id=6[slave  
keyboard (3)]
  ↳ Power Buttonid=7[slave  
keyboard (3)]
  ↳ Telink 2.4G Mouse System Controlid=10   [slave  
keyboard (3)]
  ↳ EasyCamera: EasyCamera  id=11   [slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]
  ↳ Telink 2.4G Mouse Consumer Control  id=14   [slave  
keyboard (3)]

  andrey@andrey-Lenovo:~$ ls /sys/bus/acpi/devices/
  ACPI0003:00  device:12  device:25  device:38  device:4bPNP0B00:00
  device:00device:13  device:26  device:39  device:4cPNP0C02:00
  device:01device:14  device:27  device:3a  IDEA0102:00  PNP0C02:01
  device:02device:15  device:28  device:3b  INT3452:00   PNP0C09:00
  device:03device:16  device:29  device:3c  INT3452:01   PNP0C0A:00
  device:04device:17  device:2a  device:3d  INT3452:02   PNP0C0C:00
  device:05device:18  device:2b  device:3e  INT34D7:00   PNP0C0D:00
  device:06device:19  device:2c  device:3f  LNXCPU:00PNP0C0F:00
  device:07device:1a  device:2d  device:40  LNXCPU:01PNP0C0F:01
  device:08device:1b  device:2e  device:41  LNXCPU:02PNP0C0F:02
  device:09device:1c  device:2f  device:42  LNXCPU:03PNP0C0F:03
  device:0adevice:1d  device:30  device:43  LNXSYBUS:00  PNP0C0F:04
  device:0bdevice:1e  device:31  device:44  LNXSYBUS:01  PNP0C0F:05
  device:0cdevice:1f  device:32  device:45  LNXSYSTM:00  PNP0C0F:06
  device:0ddevice:20  device:33  device:46  LNXVIDEO:00  PNP0C0F:07
  device:0edevice:21  device:34  device:47  PNP:00   PNP0C14:00
  device:0fdevice:22  device:35  device:48  PNP0100:00   SYNA2B37:00
  device:10device:23  device:36  device:49  PNP0103:00   VPC2004:00
  device:11device:24  device:37  device:4a  PNP0A08:00

  
  andrey@andrey-Lenovo:~$ cat /sys/class/input/event*/device/name
  Lid Switch
  HDA Intel PCH Headphone
  HDA Intel PCH HDMI/DP,pcm=3
  HDA Intel PCH HDMI/DP,pcm=7
  HDA Intel PCH HDMI/DP,pcm=8
  HDA Intel PCH HDMI/DP,pcm=9
  HDA Intel PCH HDMI/DP,pcm=10
  Power Button
  AT Translated Set 2 keyboard
  Video Bus
  Telink 2.4G Mouse Mouse
  Telink 2.4G Mouse Consumer Control
  Telink 2.4G Mouse System Control
  Ideapad extra buttons
  EasyCamera: EasyCamera
  HDA Intel PCH Mic

  
  andrey@andrey-Lenovo:~$ sudo acpidump | grep -C3 ELAN
  [sudo] пароль для andrey: 
00F0: 00 00 19 00 23 00 00 00 12 00 5C 5F 53 42 2E 47  #.\_SB.G
0100: 50 4F 30 00 79 00 08 53 42 46 49 11 0E 0A 0B 89  PO0.y..SBFI.
0110: 06 00 05 01 75 00 00 00 79 00 14 41 05 5F 49 4E  u...y..A._IN
0120: 49 00 A0 23 93 54 50 54 59 01 70 

[Kernel-packages] [Bug 1804841] Re: iwlwifi Microcode SW error detected. Restarting 0x2000000.

2019-01-11 Thread Seth Forshee
@Emmanuel: We generally only update firmware in stable releases in
response to specific issues, as new firmware sometimes introduces
regressions. Besides, ucode version 34 is the newest supported in the
4.15-based kernel in 18.04.

@UrkoM: When you say wifi used to be stable, was that prior to upgrading
to bionic? Because the firmware version you're using looks to be the
same one that bionic released with, so there were no updates which could
have caused regressions.

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

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

Title:
  iwlwifi Microcode SW error detected.  Restarting 0x200.

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  This seems to be a return of an existing bug, in newer hardware and
  microcode versions.

  Wireless card: Intel Corporation Wireless 8265 / 8275 [8086:24fd] (rev 78)
  Firmware version: 34.0.1
  Description:Ubuntu 18.04.1 LTS

  Frequent errors as soon as I connect to wifi:
  Microcode SW error detected.  Restarting 0x200.

  Expected to happen: Great and stable wifi like a couple of weeks ago
  What happens: very slow, intermittent internet access, lots of ping loss

  Found a suggestion of a workaround: adding these lines to
  /etc/NetworkManager/NetworkManager.conf

  [device]
  wifi.scan-rand-mac-address=no

  These lines were already there, not added by me.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.173.2 [modified: lib/firmware/iwlwifi-8265-36.ucode]
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Fri Nov 23 15:23:54 2018
  Dependencies:

  InstallationDate: Installed on 2018-09-03 (81 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1805920] Re: iPXE ignores vlan 0 traffic

2019-01-11 Thread Vern Hart
I have run a test on cosmic. The test involved MAAS 2.4.3 installed on
bionic on 3 of the blades of the UCS chassis in the customer's data
center. I installed cosmic, 18.10 on a 4th blade and installed libvirt
and qemu-kvm and defined a VM similar to how maas defines VMs. with this
xml: https://pastebin.ubuntu.com/p/yCTRGDjx2H/

$ lsb_release -d
Description:Ubuntu 18.10

The ipxe-qemu version installed from dist is:

1.0.0+git-20180124.fbe8c52d-0ubuntu4

The attached screenshot is of the failed pxe boot of the testipxe vm.

Added the ppa:andreserl/maas apt repo and installed ipxe-qemu which gave
me version:

1.0.0+git-20180124.fbe8c52d-0ubuntu2.2~18.04.1

Note that I had to edit /etc/apt/sources.list.d/andreserl-ubuntu-maas-
cosmic.list replacing "cosmic" with "bionic" because that repo doesn't
have cosmic packages. And then I had to downgrade the ipxe-qemu because
the cosmic version is greater than the one in the fix repo:

# apt install ipxe-qemu=1.0.0+git-20180124.fbe8c52d-
0ubuntu2.2~18.04.1

Once I jumped through those hoops, I booted the exact same testipxe vm
that failed to pxe boot above and it succeeded in getting an IP and
commission in MAAS.

** Attachment added: "screenshot of failed boot"
   
https://bugs.launchpad.net/maas/+bug/1805920/+attachment/5228521/+files/Screen%20Shot%202019-01-11%20at%207.36.20%20PM.png

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

Title:
  iPXE ignores vlan 0 traffic

Status in MAAS:
  Invalid
Status in ipxe package in Ubuntu:
  Fix Released
Status in ipxe-qemu-256k-compat package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in ipxe source package in Trusty:
  Won't Fix
Status in ipxe source package in Xenial:
  Won't Fix
Status in ipxe source package in Bionic:
  Incomplete
Status in ipxe source package in Cosmic:
  Incomplete
Status in ipxe source package in Disco:
  Fix Released

Bug description:
  [Impact]

   * VLAN 0 is special (for QoS actually, not a real VLAN)
   * Some components in the stack accidentally strip it, so does ipxe in
     this case.
   * Fix by porting a fix that is carried by other distributions as upstream
     didn't follow the suggestion but it is needed for the use case affected
     by the bug here (Thanks Andres)

  [Test Case]

   * Comment #42 contains a virtual test setup to understand the case but it 
 does NOT trigger the isse. That requires special switch HW that adds 
 VLAN 0 tags for QoS. Therefore Vern (reporter) will test that on a 
 customer site with such hardware being affected by this issue.

  [Regression Potential]

   * The only reference to VLAN tags on iPXE boot that we found was on iBFT
     boot for SCSI, we tested that in comment #34 and it still worked fine.
   * We didn't see such cases on review, but there might be use cases that
     made some unexpected use of the headers which are now stripped. But
     that seems wrong.

  [Other Info]

   * n/a

  ---

  I have three MAAS rack/region nodes which are blades in a Cisco UCS
  chassis. This is an FCE deployment where MAAS has two DHCP servers,
  infra1 is the primary and infra3 is the secondary. The pod VMs on
  infra1 and infra3 PXE boot fine but the pod VMs on infra2 fail to PXE
  boot. If I reconfigure the subnet to provide DHCP on infra2 (either as
  primary or secondary) then the pod VMs on infra2 will PXE boot but the
  pod VMs on the demoted infra node (that no longer serves DHCP) now
  fail to PXE boot.

  While commissioning a pod VM on infra2 I captured network traffic with
  tcpdump on the vnet interface.

  Here is the dump when the PXE boot fails (no dhcp server on infra2):
  https://pastebin.canonical.com/p/THW2gTSv4S/

  Here is the dump when PXE boot succeeds (when infra2 is serving dhcp):
  https://pastebin.canonical.com/p/HH3XvZtTGG/

  The only difference I can see is that in the unsuccessful scenario,
  the reply is an 802.1q packet -- it's got a vlan tag for vlan 0.
  Normally vlan 0 traffic is passed as if it is not tagged and indeed, I
  can ping between the blades with no problem. Outgoing packets are
  untagged but incoming packets are tagged vlan 0 -- but the ping works.
  It seems vlan 0 is used as a part of 802.1p to set priority of
  packets. This is separate from vlan, it just happens to use that
  ethertype to do the priority tagging.

  Someone confirmed to me that, in the iPXE source, it drops all packets
  if they are vlan tagged.

  The customer is unable to figure out why the packets between blades is
  getting vlan tagged so we either need to figure out how to allow iPXE
  to accept vlan 0 or the customer will need to use different equipment
  for the MAAS nodes.

  I found a conversation on the ipxe-devel mailing list that suggested a
  commit was submitted and signed off but that was from 2016 so I'm not
  sure what became of it. 

[Kernel-packages] [Bug 1808528] Re: Update linux-firmware in bionic for 18.10 hwe kernel

2019-01-11 Thread Seth Forshee
Confirmed that the updates in the built packages match those needed for
the hwe kernel.

** Tags added: verification-done-bionic

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

Title:
  Update linux-firmware in bionic for 18.10 hwe kernel

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Bionic:
  Fix Committed

Bug description:
  SRU Justification

  Impact: A 4.18-based hwe kernel has been introduced into bionic.
  However some of the firmware files it requires are missing from
  bionic's linux-firmware, rendering the relevant hardware inoperable.

  Fix: Add the missing firmware files.

  Regression Potential: Most of these files will not be used by the
  existing kernels in bionic. A few may be, and while regressions are
  not expected it's possible that new firmware versions might introduce
  regressions.

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

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


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

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

apport-collect 1811463

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

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

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

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

** Tags added: cosmic

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

Title:
  Touchpad does not initialize Lenovo Ideapad 320-15

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  Starting with Mint 18.1, I cannot start the SYNA2b37 touchpad (HID device on 
the I2C bus).
  Were tried all methods from Google

  dmesg:
  andrey@andrey-Lenovo:~$ dmesg |grep i2c
  [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=6303f611-7433-4638-a26e-13c707e21802 ro quiet splash 
i2c_designware_core.dyndbg=+p i2c-hid.debug=1 vt.handoff=1
  [0.00] Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=6303f611-7433-4638-a26e-13c707e21802 ro quiet splash 
i2c_designware_core.dyndbg=+p i2c-hid.debug=1 vt.handoff=1
  [3.847975] i2c /dev entries driver
  [9.197510] i2c_designware i2c_designware.0: Standard-mode HCNT:LCNT = 
552:652
  [9.197515] i2c_designware i2c_designware.0: Fast-mode HCNT:LCNT = 100:200
  [9.201135] i2c_hid i2c-SYNA2B37:00: i2c-SYNA2B37:00 supply vdd not found, 
using dummy regulator
  [9.201170] i2c_designware i2c_designware.0: i2c_dw_xfer: msgs: 1
  [9.201199] i2c_designware i2c_designware.0: enabled=0x1 stat=0x10
  [9.201238] i2c_designware i2c_designware.0: enabled=0x1 stat=0x750
  [9.202144] i2c_designware i2c_designware.0: i2c_dw_handle_tx_abort: slave 
address not acknowledged (7bit mode)

  andrey@andrey-Lenovo:~$ xinput
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Telink 2.4G Mouse Mouse id=8[slave  pointer 
 (2)]
  ⎜   ↳ Telink 2.4G Mouse Consumer Control  id=9[slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Video Bus   id=6[slave  
keyboard (3)]
  ↳ Power Buttonid=7[slave  
keyboard (3)]
  ↳ Telink 2.4G Mouse System Controlid=10   [slave  
keyboard (3)]
  ↳ EasyCamera: EasyCamera  id=11   [slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]
  ↳ Telink 2.4G Mouse Consumer Control  id=14   [slave  
keyboard (3)]

  andrey@andrey-Lenovo:~$ ls /sys/bus/acpi/devices/
  ACPI0003:00  device:12  device:25  device:38  device:4bPNP0B00:00
  device:00device:13  device:26  device:39  device:4cPNP0C02:00
  device:01device:14  device:27  device:3a  IDEA0102:00  PNP0C02:01
  device:02device:15  device:28  device:3b  INT3452:00   PNP0C09:00
  device:03device:16  device:29  device:3c  INT3452:01   PNP0C0A:00
  device:04device:17  device:2a  device:3d  INT3452:02   PNP0C0C:00
  device:05device:18  device:2b  device:3e  INT34D7:00   PNP0C0D:00
  device:06device:19  device:2c  device:3f  LNXCPU:00PNP0C0F:00
  device:07device:1a  device:2d  device:40  LNXCPU:01PNP0C0F:01
  device:08device:1b  device:2e  device:41  LNXCPU:02PNP0C0F:02
  device:09device:1c  device:2f  device:42  LNXCPU:03PNP0C0F:03
  device:0adevice:1d  device:30  device:43  LNXSYBUS:00  PNP0C0F:04
  device:0bdevice:1e  device:31  device:44  LNXSYBUS:01  PNP0C0F:05
  device:0cdevice:1f  device:32  device:45  LNXSYSTM:00  PNP0C0F:06
  device:0ddevice:20  device:33  device:46  LNXVIDEO:00  PNP0C0F:07
  device:0edevice:21  device:34  device:47  PNP:00   PNP0C14:00
  device:0fdevice:22  device:35  device:48  PNP0100:00   SYNA2B37:00
  device:10device:23  device:36  device:49  PNP0103:00   VPC2004:00
  device:11device:24  device:37  device:4a  PNP0A08:00

  
  andrey@andrey-Lenovo:~$ cat /sys/class/input/event*/device/name
  Lid Switch
  HDA Intel PCH Headphone
  HDA Intel PCH HDMI/DP,pcm=3
  HDA Intel PCH HDMI/DP,pcm=7
  HDA Intel PCH HDMI/DP,pcm=8
  HDA Intel PCH HDMI/DP,pcm=9
  HDA Intel PCH HDMI/DP,pcm=10
  Power Button
  AT 

[Kernel-packages] [Bug 1811463] Re: Touchpad does not initialize Lenovo Ideapad 320-15

2019-01-11 Thread Andrey
Hotkey Fn + F6 (touchpad on) does not work, all others 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/1811463

Title:
  Touchpad does not initialize Lenovo Ideapad 320-15

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  Starting with Mint 18.1, I cannot start the SYNA2b37 touchpad (HID device on 
the I2C bus).
  Were tried all methods from Google

  dmesg:
  andrey@andrey-Lenovo:~$ dmesg |grep i2c
  [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=6303f611-7433-4638-a26e-13c707e21802 ro quiet splash 
i2c_designware_core.dyndbg=+p i2c-hid.debug=1 vt.handoff=1
  [0.00] Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=6303f611-7433-4638-a26e-13c707e21802 ro quiet splash 
i2c_designware_core.dyndbg=+p i2c-hid.debug=1 vt.handoff=1
  [3.847975] i2c /dev entries driver
  [9.197510] i2c_designware i2c_designware.0: Standard-mode HCNT:LCNT = 
552:652
  [9.197515] i2c_designware i2c_designware.0: Fast-mode HCNT:LCNT = 100:200
  [9.201135] i2c_hid i2c-SYNA2B37:00: i2c-SYNA2B37:00 supply vdd not found, 
using dummy regulator
  [9.201170] i2c_designware i2c_designware.0: i2c_dw_xfer: msgs: 1
  [9.201199] i2c_designware i2c_designware.0: enabled=0x1 stat=0x10
  [9.201238] i2c_designware i2c_designware.0: enabled=0x1 stat=0x750
  [9.202144] i2c_designware i2c_designware.0: i2c_dw_handle_tx_abort: slave 
address not acknowledged (7bit mode)

  andrey@andrey-Lenovo:~$ xinput
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Telink 2.4G Mouse Mouse id=8[slave  pointer 
 (2)]
  ⎜   ↳ Telink 2.4G Mouse Consumer Control  id=9[slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Video Bus   id=6[slave  
keyboard (3)]
  ↳ Power Buttonid=7[slave  
keyboard (3)]
  ↳ Telink 2.4G Mouse System Controlid=10   [slave  
keyboard (3)]
  ↳ EasyCamera: EasyCamera  id=11   [slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]
  ↳ Telink 2.4G Mouse Consumer Control  id=14   [slave  
keyboard (3)]

  andrey@andrey-Lenovo:~$ ls /sys/bus/acpi/devices/
  ACPI0003:00  device:12  device:25  device:38  device:4bPNP0B00:00
  device:00device:13  device:26  device:39  device:4cPNP0C02:00
  device:01device:14  device:27  device:3a  IDEA0102:00  PNP0C02:01
  device:02device:15  device:28  device:3b  INT3452:00   PNP0C09:00
  device:03device:16  device:29  device:3c  INT3452:01   PNP0C0A:00
  device:04device:17  device:2a  device:3d  INT3452:02   PNP0C0C:00
  device:05device:18  device:2b  device:3e  INT34D7:00   PNP0C0D:00
  device:06device:19  device:2c  device:3f  LNXCPU:00PNP0C0F:00
  device:07device:1a  device:2d  device:40  LNXCPU:01PNP0C0F:01
  device:08device:1b  device:2e  device:41  LNXCPU:02PNP0C0F:02
  device:09device:1c  device:2f  device:42  LNXCPU:03PNP0C0F:03
  device:0adevice:1d  device:30  device:43  LNXSYBUS:00  PNP0C0F:04
  device:0bdevice:1e  device:31  device:44  LNXSYBUS:01  PNP0C0F:05
  device:0cdevice:1f  device:32  device:45  LNXSYSTM:00  PNP0C0F:06
  device:0ddevice:20  device:33  device:46  LNXVIDEO:00  PNP0C0F:07
  device:0edevice:21  device:34  device:47  PNP:00   PNP0C14:00
  device:0fdevice:22  device:35  device:48  PNP0100:00   SYNA2B37:00
  device:10device:23  device:36  device:49  PNP0103:00   VPC2004:00
  device:11device:24  device:37  device:4a  PNP0A08:00

  
  andrey@andrey-Lenovo:~$ cat /sys/class/input/event*/device/name
  Lid Switch
  HDA Intel PCH Headphone
  HDA Intel PCH HDMI/DP,pcm=3
  HDA Intel PCH HDMI/DP,pcm=7
  HDA Intel PCH HDMI/DP,pcm=8
  HDA Intel PCH HDMI/DP,pcm=9
  HDA Intel PCH HDMI/DP,pcm=10
  Power Button
  AT Translated Set 2 keyboard
  Video Bus
  Telink 2.4G Mouse Mouse
  Telink 2.4G Mouse Consumer Control
  Telink 2.4G Mouse System Control
  Ideapad extra buttons
  EasyCamera: EasyCamera
  HDA Intel PCH Mic

  
  andrey@andrey-Lenovo:~$ sudo acpidump | grep -C3 ELAN
  [sudo] пароль для andrey: 
00F0: 00 00 19 00 23 00 00 00 12 00 5C 5F 53 42 2E 47  #.\_SB.G
0100: 50 4F 30 00 79 00 08 53 42 46 49 11 0E 0A 0B 89  PO0.y..SBFI.
0110: 06 00 05 01 75 00 00 00 79 00 14 41 05 5F 49 4E  u...y..A._IN
0120: 49 00 A0 23 93 54 50 54 59 01 70 0D 45 

[Kernel-packages] [Bug 1811463] Re: Touchpad does not initialize Lenovo Ideapad 320-15

2019-01-11 Thread Andrey
** Attachment added: "inxi -Fxz.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811463/+attachment/5228519/+files/inxi%20-Fxz.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/1811463

Title:
  Touchpad does not initialize Lenovo Ideapad 320-15

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  Starting with Mint 18.1, I cannot start the SYNA2b37 touchpad (HID device on 
the I2C bus).
  Were tried all methods from Google

  dmesg:
  andrey@andrey-Lenovo:~$ dmesg |grep i2c
  [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=6303f611-7433-4638-a26e-13c707e21802 ro quiet splash 
i2c_designware_core.dyndbg=+p i2c-hid.debug=1 vt.handoff=1
  [0.00] Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=6303f611-7433-4638-a26e-13c707e21802 ro quiet splash 
i2c_designware_core.dyndbg=+p i2c-hid.debug=1 vt.handoff=1
  [3.847975] i2c /dev entries driver
  [9.197510] i2c_designware i2c_designware.0: Standard-mode HCNT:LCNT = 
552:652
  [9.197515] i2c_designware i2c_designware.0: Fast-mode HCNT:LCNT = 100:200
  [9.201135] i2c_hid i2c-SYNA2B37:00: i2c-SYNA2B37:00 supply vdd not found, 
using dummy regulator
  [9.201170] i2c_designware i2c_designware.0: i2c_dw_xfer: msgs: 1
  [9.201199] i2c_designware i2c_designware.0: enabled=0x1 stat=0x10
  [9.201238] i2c_designware i2c_designware.0: enabled=0x1 stat=0x750
  [9.202144] i2c_designware i2c_designware.0: i2c_dw_handle_tx_abort: slave 
address not acknowledged (7bit mode)

  andrey@andrey-Lenovo:~$ xinput
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Telink 2.4G Mouse Mouse id=8[slave  pointer 
 (2)]
  ⎜   ↳ Telink 2.4G Mouse Consumer Control  id=9[slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Video Bus   id=6[slave  
keyboard (3)]
  ↳ Power Buttonid=7[slave  
keyboard (3)]
  ↳ Telink 2.4G Mouse System Controlid=10   [slave  
keyboard (3)]
  ↳ EasyCamera: EasyCamera  id=11   [slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]
  ↳ Telink 2.4G Mouse Consumer Control  id=14   [slave  
keyboard (3)]

  andrey@andrey-Lenovo:~$ ls /sys/bus/acpi/devices/
  ACPI0003:00  device:12  device:25  device:38  device:4bPNP0B00:00
  device:00device:13  device:26  device:39  device:4cPNP0C02:00
  device:01device:14  device:27  device:3a  IDEA0102:00  PNP0C02:01
  device:02device:15  device:28  device:3b  INT3452:00   PNP0C09:00
  device:03device:16  device:29  device:3c  INT3452:01   PNP0C0A:00
  device:04device:17  device:2a  device:3d  INT3452:02   PNP0C0C:00
  device:05device:18  device:2b  device:3e  INT34D7:00   PNP0C0D:00
  device:06device:19  device:2c  device:3f  LNXCPU:00PNP0C0F:00
  device:07device:1a  device:2d  device:40  LNXCPU:01PNP0C0F:01
  device:08device:1b  device:2e  device:41  LNXCPU:02PNP0C0F:02
  device:09device:1c  device:2f  device:42  LNXCPU:03PNP0C0F:03
  device:0adevice:1d  device:30  device:43  LNXSYBUS:00  PNP0C0F:04
  device:0bdevice:1e  device:31  device:44  LNXSYBUS:01  PNP0C0F:05
  device:0cdevice:1f  device:32  device:45  LNXSYSTM:00  PNP0C0F:06
  device:0ddevice:20  device:33  device:46  LNXVIDEO:00  PNP0C0F:07
  device:0edevice:21  device:34  device:47  PNP:00   PNP0C14:00
  device:0fdevice:22  device:35  device:48  PNP0100:00   SYNA2B37:00
  device:10device:23  device:36  device:49  PNP0103:00   VPC2004:00
  device:11device:24  device:37  device:4a  PNP0A08:00

  
  andrey@andrey-Lenovo:~$ cat /sys/class/input/event*/device/name
  Lid Switch
  HDA Intel PCH Headphone
  HDA Intel PCH HDMI/DP,pcm=3
  HDA Intel PCH HDMI/DP,pcm=7
  HDA Intel PCH HDMI/DP,pcm=8
  HDA Intel PCH HDMI/DP,pcm=9
  HDA Intel PCH HDMI/DP,pcm=10
  Power Button
  AT Translated Set 2 keyboard
  Video Bus
  Telink 2.4G Mouse Mouse
  Telink 2.4G Mouse Consumer Control
  Telink 2.4G Mouse System Control
  Ideapad extra buttons
  EasyCamera: EasyCamera
  HDA Intel PCH Mic

  
  andrey@andrey-Lenovo:~$ sudo acpidump | grep -C3 ELAN
  [sudo] пароль для andrey: 
00F0: 00 00 19 00 23 00 00 00 12 00 5C 5F 53 42 2E 47  #.\_SB.G
0100: 50 4F 30 00 79 00 08 53 42 46 49 11 0E 0A 0B 89  PO0.y..SBFI.
0110: 06 00 05 01 75 00 00 00 79 00 

[Kernel-packages] [Bug 1811463] Re: Touchpad does not initialize Lenovo Ideapad 320-15

2019-01-11 Thread Andrey
** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811463/+attachment/5228518/+files/dmesg.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/1811463

Title:
  Touchpad does not initialize Lenovo Ideapad 320-15

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  Starting with Mint 18.1, I cannot start the SYNA2b37 touchpad (HID device on 
the I2C bus).
  Were tried all methods from Google

  dmesg:
  andrey@andrey-Lenovo:~$ dmesg |grep i2c
  [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=6303f611-7433-4638-a26e-13c707e21802 ro quiet splash 
i2c_designware_core.dyndbg=+p i2c-hid.debug=1 vt.handoff=1
  [0.00] Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=6303f611-7433-4638-a26e-13c707e21802 ro quiet splash 
i2c_designware_core.dyndbg=+p i2c-hid.debug=1 vt.handoff=1
  [3.847975] i2c /dev entries driver
  [9.197510] i2c_designware i2c_designware.0: Standard-mode HCNT:LCNT = 
552:652
  [9.197515] i2c_designware i2c_designware.0: Fast-mode HCNT:LCNT = 100:200
  [9.201135] i2c_hid i2c-SYNA2B37:00: i2c-SYNA2B37:00 supply vdd not found, 
using dummy regulator
  [9.201170] i2c_designware i2c_designware.0: i2c_dw_xfer: msgs: 1
  [9.201199] i2c_designware i2c_designware.0: enabled=0x1 stat=0x10
  [9.201238] i2c_designware i2c_designware.0: enabled=0x1 stat=0x750
  [9.202144] i2c_designware i2c_designware.0: i2c_dw_handle_tx_abort: slave 
address not acknowledged (7bit mode)

  andrey@andrey-Lenovo:~$ xinput
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Telink 2.4G Mouse Mouse id=8[slave  pointer 
 (2)]
  ⎜   ↳ Telink 2.4G Mouse Consumer Control  id=9[slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Video Bus   id=6[slave  
keyboard (3)]
  ↳ Power Buttonid=7[slave  
keyboard (3)]
  ↳ Telink 2.4G Mouse System Controlid=10   [slave  
keyboard (3)]
  ↳ EasyCamera: EasyCamera  id=11   [slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]
  ↳ Telink 2.4G Mouse Consumer Control  id=14   [slave  
keyboard (3)]

  andrey@andrey-Lenovo:~$ ls /sys/bus/acpi/devices/
  ACPI0003:00  device:12  device:25  device:38  device:4bPNP0B00:00
  device:00device:13  device:26  device:39  device:4cPNP0C02:00
  device:01device:14  device:27  device:3a  IDEA0102:00  PNP0C02:01
  device:02device:15  device:28  device:3b  INT3452:00   PNP0C09:00
  device:03device:16  device:29  device:3c  INT3452:01   PNP0C0A:00
  device:04device:17  device:2a  device:3d  INT3452:02   PNP0C0C:00
  device:05device:18  device:2b  device:3e  INT34D7:00   PNP0C0D:00
  device:06device:19  device:2c  device:3f  LNXCPU:00PNP0C0F:00
  device:07device:1a  device:2d  device:40  LNXCPU:01PNP0C0F:01
  device:08device:1b  device:2e  device:41  LNXCPU:02PNP0C0F:02
  device:09device:1c  device:2f  device:42  LNXCPU:03PNP0C0F:03
  device:0adevice:1d  device:30  device:43  LNXSYBUS:00  PNP0C0F:04
  device:0bdevice:1e  device:31  device:44  LNXSYBUS:01  PNP0C0F:05
  device:0cdevice:1f  device:32  device:45  LNXSYSTM:00  PNP0C0F:06
  device:0ddevice:20  device:33  device:46  LNXVIDEO:00  PNP0C0F:07
  device:0edevice:21  device:34  device:47  PNP:00   PNP0C14:00
  device:0fdevice:22  device:35  device:48  PNP0100:00   SYNA2B37:00
  device:10device:23  device:36  device:49  PNP0103:00   VPC2004:00
  device:11device:24  device:37  device:4a  PNP0A08:00

  
  andrey@andrey-Lenovo:~$ cat /sys/class/input/event*/device/name
  Lid Switch
  HDA Intel PCH Headphone
  HDA Intel PCH HDMI/DP,pcm=3
  HDA Intel PCH HDMI/DP,pcm=7
  HDA Intel PCH HDMI/DP,pcm=8
  HDA Intel PCH HDMI/DP,pcm=9
  HDA Intel PCH HDMI/DP,pcm=10
  Power Button
  AT Translated Set 2 keyboard
  Video Bus
  Telink 2.4G Mouse Mouse
  Telink 2.4G Mouse Consumer Control
  Telink 2.4G Mouse System Control
  Ideapad extra buttons
  EasyCamera: EasyCamera
  HDA Intel PCH Mic

  
  andrey@andrey-Lenovo:~$ sudo acpidump | grep -C3 ELAN
  [sudo] пароль для andrey: 
00F0: 00 00 19 00 23 00 00 00 12 00 5C 5F 53 42 2E 47  #.\_SB.G
0100: 50 4F 30 00 79 00 08 53 42 46 49 11 0E 0A 0B 89  PO0.y..SBFI.
0110: 06 00 05 01 75 00 00 00 79 00 14 41 05 5F 

[Kernel-packages] [Bug 1811463] [NEW] Touchpad does not initialize Lenovo Ideapad 320-15

2019-01-11 Thread Andrey
Public bug reported:


Starting with Mint 18.1, I cannot start the SYNA2b37 touchpad (HID device on 
the I2C bus).
Were tried all methods from Google

dmesg:
andrey@andrey-Lenovo:~$ dmesg |grep i2c
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=6303f611-7433-4638-a26e-13c707e21802 ro quiet splash 
i2c_designware_core.dyndbg=+p i2c-hid.debug=1 vt.handoff=1
[0.00] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=6303f611-7433-4638-a26e-13c707e21802 ro quiet splash 
i2c_designware_core.dyndbg=+p i2c-hid.debug=1 vt.handoff=1
[3.847975] i2c /dev entries driver
[9.197510] i2c_designware i2c_designware.0: Standard-mode HCNT:LCNT = 
552:652
[9.197515] i2c_designware i2c_designware.0: Fast-mode HCNT:LCNT = 100:200
[9.201135] i2c_hid i2c-SYNA2B37:00: i2c-SYNA2B37:00 supply vdd not found, 
using dummy regulator
[9.201170] i2c_designware i2c_designware.0: i2c_dw_xfer: msgs: 1
[9.201199] i2c_designware i2c_designware.0: enabled=0x1 stat=0x10
[9.201238] i2c_designware i2c_designware.0: enabled=0x1 stat=0x750
[9.202144] i2c_designware i2c_designware.0: i2c_dw_handle_tx_abort: slave 
address not acknowledged (7bit mode)

andrey@andrey-Lenovo:~$ xinput
⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ Telink 2.4G Mouse Mouse   id=8[slave  pointer  (2)]
⎜   ↳ Telink 2.4G Mouse Consumer Controlid=9[slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ Video Bus id=6[slave  keyboard (3)]
↳ Power Button  id=7[slave  keyboard (3)]
↳ Telink 2.4G Mouse System Control  id=10   [slave  keyboard (3)]
↳ EasyCamera: EasyCameraid=11   [slave  keyboard (3)]
↳ Ideapad extra buttons id=12   [slave  keyboard (3)]
↳ AT Translated Set 2 keyboard  id=13   [slave  keyboard (3)]
↳ Telink 2.4G Mouse Consumer Controlid=14   [slave  keyboard (3)]

andrey@andrey-Lenovo:~$ ls /sys/bus/acpi/devices/
ACPI0003:00  device:12  device:25  device:38  device:4bPNP0B00:00
device:00device:13  device:26  device:39  device:4cPNP0C02:00
device:01device:14  device:27  device:3a  IDEA0102:00  PNP0C02:01
device:02device:15  device:28  device:3b  INT3452:00   PNP0C09:00
device:03device:16  device:29  device:3c  INT3452:01   PNP0C0A:00
device:04device:17  device:2a  device:3d  INT3452:02   PNP0C0C:00
device:05device:18  device:2b  device:3e  INT34D7:00   PNP0C0D:00
device:06device:19  device:2c  device:3f  LNXCPU:00PNP0C0F:00
device:07device:1a  device:2d  device:40  LNXCPU:01PNP0C0F:01
device:08device:1b  device:2e  device:41  LNXCPU:02PNP0C0F:02
device:09device:1c  device:2f  device:42  LNXCPU:03PNP0C0F:03
device:0adevice:1d  device:30  device:43  LNXSYBUS:00  PNP0C0F:04
device:0bdevice:1e  device:31  device:44  LNXSYBUS:01  PNP0C0F:05
device:0cdevice:1f  device:32  device:45  LNXSYSTM:00  PNP0C0F:06
device:0ddevice:20  device:33  device:46  LNXVIDEO:00  PNP0C0F:07
device:0edevice:21  device:34  device:47  PNP:00   PNP0C14:00
device:0fdevice:22  device:35  device:48  PNP0100:00   SYNA2B37:00
device:10device:23  device:36  device:49  PNP0103:00   VPC2004:00
device:11device:24  device:37  device:4a  PNP0A08:00


andrey@andrey-Lenovo:~$ cat /sys/class/input/event*/device/name
Lid Switch
HDA Intel PCH Headphone
HDA Intel PCH HDMI/DP,pcm=3
HDA Intel PCH HDMI/DP,pcm=7
HDA Intel PCH HDMI/DP,pcm=8
HDA Intel PCH HDMI/DP,pcm=9
HDA Intel PCH HDMI/DP,pcm=10
Power Button
AT Translated Set 2 keyboard
Video Bus
Telink 2.4G Mouse Mouse
Telink 2.4G Mouse Consumer Control
Telink 2.4G Mouse System Control
Ideapad extra buttons
EasyCamera: EasyCamera
HDA Intel PCH Mic


andrey@andrey-Lenovo:~$ sudo acpidump | grep -C3 ELAN
[sudo] пароль для andrey: 
  00F0: 00 00 19 00 23 00 00 00 12 00 5C 5F 53 42 2E 47  #.\_SB.G
  0100: 50 4F 30 00 79 00 08 53 42 46 49 11 0E 0A 0B 89  PO0.y..SBFI.
  0110: 06 00 05 01 75 00 00 00 79 00 14 41 05 5F 49 4E  u...y..A._IN
  0120: 49 00 A0 23 93 54 50 54 59 01 70 0D 45 4C 41 4E  I..#.TPTY.p.ELAN
  0130: 30 36 30 39 00 5F 48 49 44 70 0A 15 42 41 44 52  0609._HIDp..BADR
  0140: 70 01 48 49 44 32 A0 25 93 54 50 54 59 0A 02 70  p.HID2.%.TPTY..p
  0150: 0D 53 59 4E 41 32 42 33 37 00 5F 48 49 44 70 0A  .SYNA2B37._HIDp.


andrey@andrey-Lenovo:~$ sudo acpidump | grep -C3 SYNA
  0120: 49 00 A0 23 93 54 50 54 59 01 70 0D 45 4C 41 4E  I..#.TPTY.p.ELAN
  0130: 30 36 30 39 00 5F 48 49 44 70 0A 15 42 41 44 52  0609._HIDp..BADR
  0140: 70 01 48 49 44 32 A0 25 93 54 50 54 59 0A 02 70  p.HID2.%.TPTY..p
  0150: 0D 53 59 4E 41 32 

[Kernel-packages] [Bug 1710390] Re: iwlwifi: Microcode SW error detected. Restarting 0x2000000

2019-01-11 Thread Christian Ehrhardt 
This is actually about two bugs in one and related to bug 1804841
Lets disambiguate them.

One can be avoided by a config in network-manager as mentioned in comment #19
Lets handle this bug here as "that one" - at least in Bionic and later - fixed 
by being set by default.

This was initially fixed in 1.12.4-1ubuntu1
>From changelog:
- NetworkManager.conf: disable MAC randomization feature. There is no
  easy way for desktop users to disable this feature yet. And there are
  reports that it doesn't work well with some systems.
And also became part of Bionic in 1.10.6-2ubuntu1

I'm marking this bug fixed since Bionic due to that.

---

Everyone else still affected despite this workaround has another yet 
unclarified issue.
This shall be tracked in bug 1804841

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

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

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

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

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

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

** Changed in: linux (Ubuntu Xenial)
   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/1710390

Title:
  iwlwifi: Microcode SW error detected. Restarting 0x200

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Incomplete
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  This bug was resolved (see 1588632)  On ubuntu 17.04 recent update
  from kernel 4.10.0-30-generic to 4.10.0-32-generic has resulted in a
  regression, reintroducing this bug.

  iwlwifi :03:00.0: Microcode SW error detected.  Restarting 0x200.
  [   12.294262]  iwl_pcie_irq_handle_error+0x39/0x160 [iwlwifi]
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  janice 1664 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=be1fb904-a9f5-4c1f-a154-349c0a6e63de
  InstallationDate: Installed on 2016-07-12 (396 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160712)
  MachineType: Dell Inc. Dell System XPS 15Z
  Package: linux (not installed)
  ProcFB:
   0 nouveaufb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-30-generic 
root=UUID=c280c3d0-6ec1-4080-9d10-74acc2399bad ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-30-generic N/A
   linux-backports-modules-4.10.0-30-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-30-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-03-11 (153 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev root sambashare sudo www-data
  _MarkForUpload: True
  dmi.bios.date: 09/07/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0XK6HV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemXPS15Z:pvr:rvnDellInc.:rn0XK6HV:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS 15Z
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1804841] Re: iwlwifi Microcode SW error detected. Restarting 0x2000000.

2019-01-11 Thread Christian Ehrhardt 
Note: the workaround of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710390 is in place
by default in Bionic - this needs some other fix.

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

Title:
  iwlwifi Microcode SW error detected.  Restarting 0x200.

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  This seems to be a return of an existing bug, in newer hardware and
  microcode versions.

  Wireless card: Intel Corporation Wireless 8265 / 8275 [8086:24fd] (rev 78)
  Firmware version: 34.0.1
  Description:Ubuntu 18.04.1 LTS

  Frequent errors as soon as I connect to wifi:
  Microcode SW error detected.  Restarting 0x200.

  Expected to happen: Great and stable wifi like a couple of weeks ago
  What happens: very slow, intermittent internet access, lots of ping loss

  Found a suggestion of a workaround: adding these lines to
  /etc/NetworkManager/NetworkManager.conf

  [device]
  wifi.scan-rand-mac-address=no

  These lines were already there, not added by me.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.173.2 [modified: lib/firmware/iwlwifi-8265-36.ucode]
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Fri Nov 23 15:23:54 2018
  Dependencies:

  InstallationDate: Installed on 2018-09-03 (81 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1804841] Re: iwlwifi Microcode SW error detected. Restarting 0x2000000.

2019-01-11 Thread Christian Ehrhardt 
I thought it might be worth to try the other versions of the FW.
So I renamed the files like:
sudo mv /lib/firmware/iwlwifi-8265-36.ucode 
/lib/firmware/DONOTLOAD-iwlwifi-8265-36.ucode

Eventually I ended up with:
-rw-r--r-- 1 root root 1811984 Apr 24  2018 
/lib/firmware/DONOTLOAD-iwlwifi-8265-22.ucode
-rw-r--r-- 1 root root 2234528 Dez  5  2017 
/lib/firmware/DONOTLOAD-iwlwifi-8265-27.ucode
-rw-r--r-- 1 root root 2307104 Dez  6  2017 
/lib/firmware/DONOTLOAD-iwlwifi-8265-31.ucode
-rw-r--r-- 1 root root 2440780 Apr 25  2018 
/lib/firmware/DONOTLOAD-iwlwifi-8265-34.ucode
-rw-r--r-- 1 root root 2498044 Jan 11 10:03 
/lib/firmware/DONOTLOAD-iwlwifi-8265-36.ucode
-rw-r--r-- 1 root root 2389968 Nov 17  2017 /lib/firmware/iwlwifi-8265-21.ucode

All versions >=22 Failed, no change in behavior at all.
When running with only 21 left it failed to load at all, see the following 
dmesg.

[5.651536] iwlwifi :04:00.0: Direct firmware load for 
iwlwifi-8265-36.ucode failed with error -2
[5.651651] iwlwifi :04:00.0: Direct firmware load for 
iwlwifi-8265-35.ucode failed with error -2
[5.652037] iwlwifi :04:00.0: Direct firmware load for 
iwlwifi-8265-34.ucode failed with error -2
[5.652050] iwlwifi :04:00.0: Direct firmware load for 
iwlwifi-8265-33.ucode failed with error -2
[5.652057] iwlwifi :04:00.0: Direct firmware load for 
iwlwifi-8265-32.ucode failed with error -2
[5.652065] iwlwifi :04:00.0: Direct firmware load for 
iwlwifi-8265-31.ucode failed with error -2
[5.652072] iwlwifi :04:00.0: Direct firmware load for 
iwlwifi-8265-30.ucode failed with error -2
[5.652080] iwlwifi :04:00.0: Direct firmware load for 
iwlwifi-8265-29.ucode failed with error -2
[5.652087] iwlwifi :04:00.0: Direct firmware load for 
iwlwifi-8265-28.ucode failed with error -2
[5.652095] iwlwifi :04:00.0: Direct firmware load for 
iwlwifi-8265-27.ucode failed with error -2
[5.652103] iwlwifi :04:00.0: Direct firmware load for 
iwlwifi-8265-26.ucode failed with error -2
[5.652111] iwlwifi :04:00.0: Direct firmware load for 
iwlwifi-8265-25.ucode failed with error -2
[5.652119] iwlwifi :04:00.0: Direct firmware load for 
iwlwifi-8265-24.ucode failed with error -2
[5.652127] iwlwifi :04:00.0: Direct firmware load for 
iwlwifi-8265-23.ucode failed with error -2
[5.652135] iwlwifi :04:00.0: Direct firmware load for 
iwlwifi-8265-22.ucode failed with error -2
[5.652137] iwlwifi :04:00.0: no suitable firmware found!
[5.652140] iwlwifi :04:00.0: minimum version required: iwlwifi-8265-22
[5.652142] iwlwifi :04:00.0: maximum version supported: iwlwifi-8265-36
[5.652144] iwlwifi :04:00.0: check 
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

I thought, well then I run it without recent FW load, but then the
wireless adapter doesn't initialize at all.

No chance to configure it in cmdline or UI tools.

Therefore it seems I know no way to get wireless to work at all on my T580 :-/
is there a Wireless dongle that works well with Linux?

If there is anything I can try to resolve this please let me know.

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

Title:
  iwlwifi Microcode SW error detected.  Restarting 0x200.

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  This seems to be a return of an existing bug, in newer hardware and
  microcode versions.

  Wireless card: Intel Corporation Wireless 8265 / 8275 [8086:24fd] (rev 78)
  Firmware version: 34.0.1
  Description:Ubuntu 18.04.1 LTS

  Frequent errors as soon as I connect to wifi:
  Microcode SW error detected.  Restarting 0x200.

  Expected to happen: Great and stable wifi like a couple of weeks ago
  What happens: very slow, intermittent internet access, lots of ping loss

  Found a suggestion of a workaround: adding these lines to
  /etc/NetworkManager/NetworkManager.conf

  [device]
  wifi.scan-rand-mac-address=no

  These lines were already there, not added by me.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.173.2 [modified: lib/firmware/iwlwifi-8265-36.ucode]
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Fri Nov 23 15:23:54 2018
  Dependencies:

  InstallationDate: Installed on 2018-09-03 (81 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 

[Kernel-packages] [Bug 1738736] Re: ACPI error message flooding syslog

2019-01-11 Thread Alex Garel
I can confirm on my side that it's still there after I also upgrade to
Cosmic.

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

Title:
  ACPI error message flooding syslog

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This message :

  Dec 18 09:20:13 tignasse kernel: [   85.652805] ACPI Error: Needed type 
[Reference], found [Integer] 99eae08481f8 (20170531/exresop-103)
  Dec 18 09:20:13 tignasse kernel: [   85.652831] ACPI Exception: 
AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] 
(20170531/dswexec-461)
  Dec 18 09:20:13 tignasse kernel: [   85.652847] ACPI Error: Method 
parse/execution failed \_SB.PCI0.LPCB.H_EC._Q50, AE_AML_OPERAND_TYPE 
(20170531/psparse-550)

  Is flooding my syslog at a pace of on message every 200 ms !

  This is really annoying.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-19-generic 4.13.0-19.22
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alex   5166 F pulseaudio
   /dev/snd/controlC1:  alex   5166 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Dec 18 09:22:16 2017
  HibernationDevice: RESUME=UUID=870c2fd1-8a8f-49bb-9bf4-dbefaa08e583
  InstallationDate: Installed on 2015-11-10 (768 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Intel Corporation Skylake Platform
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=6814e3c1-8cea-4ecc-964d-535fd18782e9 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-11-23 (24 days ago)
  dmi.bios.date: 11/06/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: WhiteTip Mountain1 Fab2
  dmi.board.vendor: Topstar
  dmi.board.version: RVP7
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 9
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd11/06/2015:svnIntelCorporation:pnSkylakePlatform:pvr0.1:rvnTopstar:rnWhiteTipMountain1Fab2:rvrRVP7:cvnDefaultstring:ct9:cvrDefaultstring:
  dmi.product.family: Skylake System
  dmi.product.name: Skylake Platform
  dmi.product.version: 0.1
  dmi.sys.vendor: Intel Corporation

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

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


[Kernel-packages] [Bug 1795453] Re: [SRU] IO's are issued with incorrect Scatter Gather Buffer

2019-01-11 Thread Michael Reed
** Tags added: cosmic disco xenial

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

Title:
  [SRU] IO's are issued with incorrect Scatter Gather Buffer

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]
  We have observed that OS is sending the IO's (SCSI Read/Write) with incorrect 
Scatter Gather Buffer address .

  i.e

   OS is sending the IO with 64 bit Scatter Gather Buffer address , such
  that if we add the length with buffer address then it causes the roll
  over .

  Here is the data we captured in our driver (Printed the SGE details
  which was sent by OS)

  sgl_ptr->Address = f000
  [14547.313240]
  sgl_ptr->Length = 1000
  [14547.313241]
  sge_count = 18
  [14547.313242]
  cmd->index = 9d9

  Note : This issue is observed only when virtualization is enabled

  Product : Broadcom (LSI) Megaraid H840 controller

  
  [Test Case]
  Steps found in comment #60
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795453/comments/60

  
  [Regression Potential]

  The patches in Comment #59 have been accepted upstream.

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795453/comments/59


  [Other Info]

  Product : Broadcom (LSI) Megaraid H840 controller
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
   crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7415
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro
  ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 09/07/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.2
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr:
  dmi.product.family: PowerEdge
  dmi.product.name: PowerEdge R7415
  dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R7415
  dmi.sys.vendor: Dell Inc.
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
   crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7415
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro
  ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 09/07/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.2
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 

[Kernel-packages] [Bug 1804841] Re: iwlwifi Microcode SW error detected. Restarting 0x2000000.

2019-01-11 Thread Christian Ehrhardt 
I created a PPA for Bionic with the latest firmware (git of today) merged into 
the Package version we have in Disco. That can be found at [1].
But even that didn't help - which means even the very latest upstream will not 
fix the issue for us auto-magically.

[1]: https://launchpad.net/~paelzer/+archive/ubuntu/bug-1804841-iwlwifi-
linux-firmware/+packages

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

Title:
  iwlwifi Microcode SW error detected.  Restarting 0x200.

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  This seems to be a return of an existing bug, in newer hardware and
  microcode versions.

  Wireless card: Intel Corporation Wireless 8265 / 8275 [8086:24fd] (rev 78)
  Firmware version: 34.0.1
  Description:Ubuntu 18.04.1 LTS

  Frequent errors as soon as I connect to wifi:
  Microcode SW error detected.  Restarting 0x200.

  Expected to happen: Great and stable wifi like a couple of weeks ago
  What happens: very slow, intermittent internet access, lots of ping loss

  Found a suggestion of a workaround: adding these lines to
  /etc/NetworkManager/NetworkManager.conf

  [device]
  wifi.scan-rand-mac-address=no

  These lines were already there, not added by me.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.173.2 [modified: lib/firmware/iwlwifi-8265-36.ucode]
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Fri Nov 23 15:23:54 2018
  Dependencies:

  InstallationDate: Installed on 2018-09-03 (81 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1795453] Re: [SRU] IO's are issued with incorrect Scatter Gather Buffer

2019-01-11 Thread Michael Reed
** Summary changed:

- IO's are issued with incorrect Scatter Gather Buffer
+ [SRU] IO's are issued with incorrect Scatter Gather Buffer

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

Title:
  [SRU] IO's are issued with incorrect Scatter Gather Buffer

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]
  We have observed that OS is sending the IO's (SCSI Read/Write) with incorrect 
Scatter Gather Buffer address .

  i.e

   OS is sending the IO with 64 bit Scatter Gather Buffer address , such
  that if we add the length with buffer address then it causes the roll
  over .

  Here is the data we captured in our driver (Printed the SGE details
  which was sent by OS)

  sgl_ptr->Address = f000
  [14547.313240]
  sgl_ptr->Length = 1000
  [14547.313241]
  sge_count = 18
  [14547.313242]
  cmd->index = 9d9

  Note : This issue is observed only when virtualization is enabled

  Product : Broadcom (LSI) Megaraid H840 controller

  
  [Test Case]
  Steps found in comment #60
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795453/comments/60

  
  [Regression Potential]

  The patches in Comment #59 have been accepted upstream.

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795453/comments/59


  [Other Info]

  Product : Broadcom (LSI) Megaraid H840 controller
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
   crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7415
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro
  ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 09/07/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.2
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr:
  dmi.product.family: PowerEdge
  dmi.product.name: PowerEdge R7415
  dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R7415
  dmi.sys.vendor: Dell Inc.
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
   crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7415
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro
  ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 09/07/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.2
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 23
  

[Kernel-packages] [Bug 1807974] Re: Wireless regularly breaking (ath10k firmware crashed!) after upgrade to Cosmic

2019-01-11 Thread Kai-Heng Feng
I think the firmware is the same, so only the board-2.bin file needs to
be copied.

I am still seeing the issue with new board-2.bin.

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

Title:
  Wireless regularly breaking (ath10k firmware crashed!) after upgrade
  to Cosmic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell XPS 13 9370 developer edition (Ubuntu version) running
  Cosmic. A handful of times per day, my wireless stops working ("?"
  appears in the icon in Network Manager). Turning wireless off and then
  on again, or suspending and waking the machine up, makes the wireless
  work again.

  dmesg output is as follows:

  $ dmesg | grep ath10k

  [ 6646.268929] ath10k_pci :02:00.0: firmware crashed! (guid 
6317c652-4817-4fdd-b6d7-c7b8336e493f)
  [ 6646.268982] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 
chip_id 0x00340aff sub 1a56:143a
  [ 6646.268990] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [ 6646.270369] ath10k_pci :02:00.0: firmware ver 
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
  [ 6646.271379] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 
20d869c3
  [ 6646.271393] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal 
otp max-sta 32 raw 0 hwcrypto 1
  [ 6646.28] ath10k_pci :02:00.0: failed to get memcpy hi address for 
firmware address 4: -16
  [ 6646.283336] ath10k_pci :02:00.0: failed to read firmware dump area: -16
  [ 6646.283339] ath10k_pci :02:00.0: Copy Engine register dump:
  [ 6646.283348] ath10k_pci :02:00.0: [00]: 0x00034400  14  14   3   3
  [ 6646.283357] ath10k_pci :02:00.0: [01]: 0x00034800  29  29 106 107
  [ 6646.283365] ath10k_pci :02:00.0: [02]: 0x00034c00  20  19  18  19
  [ 6646.283374] ath10k_pci :02:00.0: [03]: 0x00035000   8   8  10   8
  [ 6646.283386] ath10k_pci :02:00.0: [04]: 0x00035400 2763 2763 167 103
  [ 6646.283394] ath10k_pci :02:00.0: [05]: 0x00035800   0   0  64   0
  [ 6646.283402] ath10k_pci :02:00.0: [06]: 0x00035c00   0   0   6   6
  [ 6646.283412] ath10k_pci :02:00.0: [07]: 0x00036000   0   1   0   1
  [ 6646.301351] ath10k_pci :02:00.0: failed to read hi_board_data address: 
-28
  [ 6647.126841] ath10k_pci :02:00.0: Unknown eventid: 118809
  [ 6647.129850] ath10k_pci :02:00.0: Unknown eventid: 90118
  [ 6647.239340] ath10k_pci :02:00.0: device successfully recovered

  
  [17641.847345] ath10k_pci :02:00.0: firmware crashed! (guid 
03393f2f-0ce1-4017-b711-40dd14f2ec11)
  [17641.847363] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 
chip_id 0x00340aff sub 1a56:143a
  [17641.847367] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [17641.848065] ath10k_pci :02:00.0: firmware ver 
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
  [17641.848585] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 
20d869c3
  [17641.848593] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal 
otp max-sta 32 raw 0 hwcrypto 1
  [17641.860559] ath10k_pci :02:00.0: failed to get memcpy hi address for 
firmware address 4: -16
  [17641.860587] ath10k_pci :02:00.0: failed to read firmware dump area: -16
  [17641.860595] ath10k_pci :02:00.0: Copy Engine register dump:
  [17641.860611] ath10k_pci :02:00.0: [00]: 0x00034400  14  14   3   3
  [17641.860624] ath10k_pci :02:00.0: [01]: 0x00034800   6   6 243 244
  [17641.860639] ath10k_pci :02:00.0: [02]: 0x00034c00  53  52  51  52
  [17641.860656] ath10k_pci :02:00.0: [03]: 0x00035000   5   5   7   5
  [17641.860669] ath10k_pci :02:00.0: [04]: 0x00035400 1231 1231 169 105
  [17641.860681] ath10k_pci :02:00.0: [05]: 0x00035800   0   0  64   0
  [17641.860693] ath10k_pci :02:00.0: [06]: 0x00035c00   0   0  30  30
  [17641.860706] ath10k_pci :02:00.0: [07]: 0x00036000   0   1   0   1
  [17641.890915] ath10k_pci :02:00.0: failed to read hi_board_data address: 
-28
  [17642.714052] ath10k_pci :02:00.0: Unknown eventid: 118809
  [17642.717154] ath10k_pci :02:00.0: Unknown eventid: 90118
  [17642.835601] ath10k_pci :02:00.0: device successfully recovered
  [17894.571696] ath10k_pci :02:00.0: Unknown eventid: 118809
  [17894.574764] ath10k_pci :02:00.0: Unknown eventid: 90118

  I do not recall having any wireless issues before I upgraded (when
  this machine was running Bionic).

  Bug #1730331 - ath10k_pci: firmware crashed!
  Bug #1627474 - ath10k_pci :03:00.0: firmware crashed! (uuid n/a) [16.10]
  could be related, but appear to be related to earlier releases, whereas my 
issue has appeared/become much worse on Cosmic.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  

[Kernel-packages] [Bug 1795453] Re: IO's are issued with incorrect Scatter Gather Buffer

2019-01-11 Thread Michael Reed
** Tags added: verification-needed

** Tags added: tpp

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

Title:
  IO's are issued with incorrect Scatter Gather Buffer

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]
  We have observed that OS is sending the IO's (SCSI Read/Write) with incorrect 
Scatter Gather Buffer address .

  i.e

   OS is sending the IO with 64 bit Scatter Gather Buffer address , such
  that if we add the length with buffer address then it causes the roll
  over .

  Here is the data we captured in our driver (Printed the SGE details
  which was sent by OS)

  sgl_ptr->Address = f000
  [14547.313240]
  sgl_ptr->Length = 1000
  [14547.313241]
  sge_count = 18
  [14547.313242]
  cmd->index = 9d9

  Note : This issue is observed only when virtualization is enabled

  Product : Broadcom (LSI) Megaraid H840 controller

  
  [Test Case]
  Steps found in comment #60
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795453/comments/60

  
  [Regression Potential]

  The patches in Comment #59 have been accepted upstream.

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795453/comments/59


  [Other Info]

  Product : Broadcom (LSI) Megaraid H840 controller
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
   crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7415
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro
  ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 09/07/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.2
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr:
  dmi.product.family: PowerEdge
  dmi.product.name: PowerEdge R7415
  dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R7415
  dmi.sys.vendor: Dell Inc.
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
   crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7415
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro
  ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 09/07/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.2
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 

[Kernel-packages] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

2019-01-11 Thread Josh Krull
I am encountering a similar issue on a new Dell G5 5587. I've installed
Ubuntu 18.10 (fresh download today) alongside Windows 10 on a 1TB nvme
SSD.

I can boot into Ubuntu, but the system hangs shortly after boot, usually
less than 5 minutes.  I have not determined what specifically triggers
the hanging.  I have noticed that it does not happen all at once. By
that I mean that I lose mouse first (touchpad and wireless mouse), but I
can still use the keyboard (sometimes) for a few seconds after the mouse
is gone. This makes me wonder if the system is actually frozen or if
there is just no HID being recognized.  I've also seen the system "lag"
input from the keyboard: no response immediately but 30-40 seconds later
characters that I typed will appear. I also notice that the fans kick on
high, so there may be a runaway processes.

In the current state 18.10 is unusable. I haven't even been able tail
the log files, I encounter the hang before I have time to troubleshoot
the issue. I'm not sure if it's the same issue or something specific to
my hardware, I'll update as I continue to try to troubleshoot.

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

Title:
  Random unrecoverable freezes on Ubuntu 18.10

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

Bug description:
  First thing I notice is that the mouse cursor freezes as I'm using it,
  then I hit the CAPS LOCK key and the LED indicator doesn't respond.
  Then I try the "REISUB" command, but it doesn't do anything either.
  Only a hard reset works, pressing down the power button for a few
  seconds.

  How to reproduce?
  I couldn't figure out a consistent method. It is still random to me.

  Version: Ubuntu 4.18.0-10.11-generic 4.18.12
  System information attached.

  Also happens under Arch Linux and Fedora.
  I've talked to another user on IRC who seems to be having the same freezes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsilva 1213 F pulseaudio
   /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.sku: Inspiron 5458
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1795453] Re: IO's are issued with incorrect Scatter Gather Buffer

2019-01-11 Thread Michael Reed
** Description changed:

- 
+ [Impact]
  We have observed that OS is sending the IO's (SCSI Read/Write) with incorrect 
Scatter Gather Buffer address .
  
  i.e
  
-  OS is sending the IO with 64 bit Scatter Gather Buffer address , such
+  OS is sending the IO with 64 bit Scatter Gather Buffer address , such
  that if we add the length with buffer address then it causes the roll
  over .
  
+ Here is the data we captured in our driver (Printed the SGE details
+ which was sent by OS)
  
- Here is the data we captured in our driver (Printed the SGE details which was 
sent by OS)
+ sgl_ptr->Address = f000
+ [14547.313240]
+ sgl_ptr->Length = 1000
+ [14547.313241]
+ sge_count = 18
+ [14547.313242]
+ cmd->index = 9d9
  
- sgl_ptr->Address = f000 
- [14547.313240] 
- sgl_ptr->Length = 1000 
- [14547.313241] 
- sge_count = 18 
- [14547.313242] 
- cmd->index = 9d9
+ Note : This issue is observed only when virtualization is enabled
+ 
+ Product : Broadcom (LSI) Megaraid H840 controller
  
  
- Note : This issue is observed only when virtualization is enabled 
+ [Test Case]
+ Steps found in comment #60
+ https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795453/comments/60
+ 
+ 
+ [Regression Potential]
+ 
+ The patches in Comment #59 have been accepted upstream.
+ 
+ https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795453/comments/59
+ 
+ 
+ [Other Info]
  
  Product : Broadcom (LSI) Megaraid H840 controller
- --- 
+ ---
  ProblemType: Bug
  AlsaDevices:
-  total 0
-  crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
-  crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
+  total 0
+  crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
+  crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7415
  Package: linux (not installed)
  PciMultimedia:
-  
+ 
  ProcEnviron:
-  TERM=xterm
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro
  ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7
  RelatedPackageVersions:
-  linux-restricted-modules-4.18.0-8-generic N/A
-  linux-backports-modules-4.18.0-8-generic  N/A
-  linux-firmware1.173.1
+  linux-restricted-modules-4.18.0-8-generic N/A
+  linux-backports-modules-4.18.0-8-generic  N/A
+  linux-firmware1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 09/07/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.2
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr:
  dmi.product.family: PowerEdge
  dmi.product.name: PowerEdge R7415
  dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R7415
  dmi.sys.vendor: Dell Inc.
- --- 
+ ---
  ProblemType: Bug
  AlsaDevices:
-  total 0
-  crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
-  crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
+  total 0
+  crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
+  crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7415
  Package: linux (not installed)
  PciMultimedia:
-  
+ 
  ProcEnviron:
-  TERM=xterm
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 

[Kernel-packages] [Bug 1811452] Re: linux: 4.19.0-10.11 -proposed tracker

2019-01-11 Thread 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
  
  backports: 
  derivatives:
+ -- swm properties --
+ phase: Packaging -- packaging in progress
+ phase-changed: Friday, 11. January 2019 18:01 UTC
+ reason:
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
+   prepare-package-signed: Pending -- package not yet uploaded

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

Title:
  linux: 4.19.0-10.11 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  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: 
  derivatives:
  -- swm properties --
  phase: Packaging -- packaging in progress
  phase-changed: Friday, 11. January 2019 18:01 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded

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

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


[Kernel-packages] [Bug 1811452] Re: linux: 4.19.0-10.11 -proposed tracker

2019-01-11 Thread Seth Forshee
** Summary changed:

- linux:  -proposed tracker
+ linux: 4.19.0-10.11 -proposed tracker

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

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

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

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

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

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

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

Title:
  linux: 4.19.0-10.11 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  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: 
  derivatives:

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

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


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

2019-01-11 Thread Seth Forshee
Public bug reported:

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

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

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

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

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

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

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

** Affects: kernel-sru-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

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

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

** Affects: linux (Ubuntu Disco)
 Importance: Medium
 Status: Confirmed


** Tags: disco kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-d2019.01.11-1 kernel-sru-master-kernel

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

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

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

** Tags added: disco

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

** Changed in: kernel-sru-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

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

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

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

** Changed in: kernel-sru-workflow
   Status: New => In Progress

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

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

** Tags added: kernel-sru-cycle-d2019.01.11-1

** Tags added: kernel-sru-master-kernel

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

[Kernel-packages] [Bug 1811337] Re: To reduce the Realtek USB cardreader power consumption

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

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

Title:
  To reduce the Realtek USB cardreader power consumption

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  Fix Committed
Status in linux-oem source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem source package in Disco:
  Invalid

Bug description:
  [Impact]
  Realtek USB cardreader consumes more than 1 Watt during long idle if it's not 
suspended. And it's runtime PM functions are available after v4.20.

  [Fix]
  To avoid conflicts, have to backport some patches for mmc core.

  [Test]
  Note: Inside () are the previous value (non-patch)
  Sort idle: 7.76W (7.88)
  Long idle: 4.658W (5.79)
  S3: 0.5W (0.5)
  S5: 0.20W (0.208)

  [Regression Potential]
  Low, most commits are for rtsx_usb_{sdmmc,ms} and are all small changes.

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

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


[Kernel-packages] [Bug 1687623] Re: linux-4.4.0-77.98 was a phased update in -updates only and may become partially installed (was: 4.4.0-77-generic breaks internet on 16.04.2)

2019-01-11 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Xenial)
   Status: In Progress => Incomplete

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

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

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

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

Title:
  linux-4.4.0-77.98 was a phased update in -updates only and may become
  partially installed (was: 4.4.0-77-generic breaks internet on 16.04.2)

Status in linux package in Ubuntu:
  Incomplete
Status in update-manager package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Incomplete
Status in update-manager source package in Xenial:
  Confirmed

Bug description:
  Hi as per title today I updated to  4.4.0-77-generic on my Lubuntu
  16.04.02 and wifi is not working anymore. When I click on the network
  manager I see "enable networking" (which is toggled) but no more the
  option about wifi.

  I reported this on ubuntuforum:
  https://ubuntuforums.org/showthread.php?t=2360216

  Where a user suggested to revert to an older kernel and see if this
  fixes the problem. I managed to revert to 4.4.0-75-generic via grub
  and everything works perfectly.

  Another user reported a similar issue caused by the same upgrade on
  the same system: https://ubuntuforums.org/showthread.php?t=2360215

  Can someone else confirm this bug?

  If you need more information I will be happy to provide it (I am a
  newbie though so please be patient).

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

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


[Kernel-packages] [Bug 1681904] Re: WLan not working after Kernel update (HWE)

2019-01-11 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Status: In Progress => Incomplete

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

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

Title:
  WLan not working after Kernel update (HWE)

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

Bug description:
  After the update from 4.8.0.44 to newer versions, wifi stopped
  working.

  The controller is still found with `lshw -class network`, but wifi is
  not displayed in Network Manager.

  Hardware is Broadcom BCM4331 802.11a/b/g/n.

  What additional informations do you need to resolve this?

  -

  Apple MacBookPro10,2 from ~2012
  elementary OS 0.4 Loki (based on Ubuntu 16.04 LTS) with HWE-Stack
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  davidak2186 F pulseaudio
  DistroRelease: elementary 0.4
  HibernationDevice: RESUME=UUID=f8624e3d-378a-4777-8889-1f2f01f83989
  InstallationDate: Installed on 2016-10-26 (188 days ago)
  InstallationMedia: elementary OS 0.4 "Loki" - Stable amd64 (20160909)
  IwConfig:
   ens9  no wireless extensions.
   
   docker0   no wireless extensions.
   
   lono wireless extensions.
  MachineType: Apple Inc. MacBookPro10,2
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-20-generic 
root=/dev/mapper/elementary--vg-root ro splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.157.8
  RfKill:
   0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
  Tags:  loki loki
  Uname: Linux 4.10.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: docker
  _MarkForUpload: True
  dmi.bios.date: 09/13/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP102.88Z.0106.B0A.1509130955
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-AFD8A9D944EA4843
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro10,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-AFD8A9D944EA4843
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP102.88Z.0106.B0A.1509130955:bd09/13/2015:svnAppleInc.:pnMacBookPro10,2:pvr1.0:rvnAppleInc.:rnMac-AFD8A9D944EA4843:rvrMacBookPro10,2:cvnAppleInc.:ct10:cvrMac-AFD8A9D944EA4843:
  dmi.product.name: MacBookPro10,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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


[Kernel-packages] [Bug 1687383] Re: Complete computer freeze (screen, mouse, keyboard) after 17.04 upgrade

2019-01-11 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Zesty)
   Status: In Progress => Invalid

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

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

Title:
  Complete computer freeze (screen, mouse, keyboard) after 17.04 upgrade

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Zesty:
  Invalid

Bug description:
  Extract of system log (Oops part)
  Apr 30 12:01:25 salon kernel: [ 8273.281441] Oops:  [#1] SMP
  Apr 30 12:01:25 salon kernel: [ 8273.281447] Modules linked in: ccm gpio_ich 
snd_hda_codec_hdmi joydev input_leds arc4 ath9k ath9k_common coretemp kvm_intel 
ath9k_hw ath kvm irqbypass mac80211 snd_hda_codec_realtek snd_hda_codec_generic 
serio_raw snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep lpc_ich cfg80211 
snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq tpm_infineon 
snd_seq_device snd_timer mac_hid shpchp snd soundcore parport_pc ppdev lp 
parport ip_tables x_tables autofs4 hid_logitech ff_memless psmouse uas nouveau 
firewire_ohci pata_acpi firewire_core crc_itu_t usb_storage mxm_wmi wmi video 
pata_jmicron i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt 
fb_sys_fops drm fjes usbhid hid
  Apr 30 12:01:25 salon kernel: [ 8273.281524] CPU: 1 PID: 1210 Comm: 
InputThread Not tainted 4.10.0-20-generic #22-Ubuntu
  Apr 30 12:01:25 salon kernel: [ 8273.281531] Hardware name: Gigabyte 
Technology Co., Ltd. EP45-DS3R/EP45-DS3R, BIOS F4 05/28/2008
  Apr 30 12:01:25 salon kernel: [ 8273.281538] task: 955c5bad6a40 
task.stack: ac66c1758000
  Apr 30 12:01:25 salon kernel: [ 8273.281545] RIP: 
0010:dma_fence_wait_timeout+0x36/0xf0
  Apr 30 12:01:25 salon kernel: [ 8273.281550] RSP: 0018:ac66c175ba38 
EFLAGS: 00010206
  Apr 30 12:01:25 salon kernel: [ 8273.281556] RAX: 0001 RBX: 
955bc39ca680 RCX: c0351fa0
  Apr 30 12:01:25 salon kernel: [ 8273.281563] RDX: 7fff RSI: 
0001 RDI: 955c5b82f300
  Apr 30 12:01:25 salon kernel: [ 8273.281569] RBP: ac66c175ba58 R08: 
 R09: 955c71c98000
  Apr 30 12:01:25 salon kernel: [ 8273.281575] R10: 955c5286bd40 R11: 
955c727aaa08 R12: 955c5b82f300
  Apr 30 12:01:25 salon kernel: [ 8273.281581] R13: 0001 R14: 
7fff R15: 0001
  Apr 30 12:01:25 salon kernel: [ 8273.281588] FS:  7fa96383f700() 
GS:955c7fc8() knlGS:
  Apr 30 12:01:25 salon kernel: [ 8273.281595] CS:  0010 DS:  ES:  CR0: 
80050033
  Apr 30 12:01:25 salon kernel: [ 8273.281601] CR2: 0021 CR3: 
00011b64f000 CR4: 06e0
  Apr 30 12:01:25 salon kernel: [ 8273.281607] Call Trace:
  Apr 30 12:01:25 salon kernel: [ 8273.281623]  
drm_atomic_helper_wait_for_fences+0x48/0x120 [drm_kms_helper]
  Apr 30 12:01:25 salon kernel: [ 8273.281679]  
nv50_disp_atomic_commit+0x19c/0x2a0 [nouveau]
  Apr 30 12:01:25 salon kernel: [ 8273.281703]  drm_atomic_commit+0x4b/0x50 
[drm]
  Apr 30 12:01:25 salon kernel: [ 8273.281714]  
drm_atomic_helper_update_plane+0xec/0x150 [drm_kms_helper]
  Apr 30 12:01:25 salon kernel: [ 8273.281731]  __setplane_internal+0x1b4/0x280 
[drm]
  Apr 30 12:01:25 salon kernel: [ 8273.281738]  ? 
__ww_mutex_lock_slowpath+0x29a/0x3d0
  Apr 30 12:01:25 salon kernel: [ 8273.281757]  
drm_mode_cursor_universal+0x126/0x210 [drm]
  Apr 30 12:01:25 salon kernel: [ 8273.281774]  
drm_mode_cursor_common+0x86/0x180 [drm]
  Apr 30 12:01:25 salon kernel: [ 8273.281781]  ? ep_poll_callback+0xef/0x1f0
  Apr 30 12:01:25 salon kernel: [ 8273.281797]  drm_mode_cursor_ioctl+0x50/0x70 
[drm]
  Apr 30 12:01:25 salon kernel: [ 8273.281812]  drm_ioctl+0x21b/0x4c0 [drm]
  Apr 30 12:01:25 salon kernel: [ 8273.281828]  ? drm_mode_setplane+0x1a0/0x1a0 
[drm]
  Apr 30 12:01:25 salon kernel: [ 8273.281835]  ? _copy_to_user+0x54/0x60
  Apr 30 12:01:25 salon kernel: [ 8273.281877]  nouveau_drm_ioctl+0x74/0xc0 
[nouveau]
  Apr 30 12:01:25 salon kernel: [ 8273.281884]  do_vfs_ioctl+0xa3/0x610
  Apr 30 12:01:25 salon kernel: [ 8273.281890]  ? 
__check_object_size+0x100/0x1d7
  Apr 30 12:01:25 salon kernel: [ 8273.281895]  SyS_ioctl+0x79/0x90
  Apr 30 12:01:25 salon kernel: [ 8273.281901]  
entry_SYSCALL_64_fastpath+0x1e/0xad
  Apr 30 12:01:25 salon kernel: [ 8273.281907] RIP: 0033:0x7fa96e376987
  Apr 30 12:01:25 salon kernel: [ 8273.281911] RSP: 002b:7fa96383d338 
EFLAGS: 3246 ORIG_RAX: 0010
  Apr 30 12:01:25 salon kernel: [ 8273.281918] RAX: ffda RBX: 
559c9117f930 RCX: 7fa96e376987
  Apr 30 12:01:25 salon kernel: [ 8273.281925] RDX: 7fa96383d370 RSI: 
c01c64a3 RDI: 000e
  Apr 30 12:01:25 salon kernel: [ 8273.281931] RBP:  R08: 
559c908510c0 R09: 0780
  Apr 30 12:01:25 salon kernel: [ 8273.282266] R10: 

[Kernel-packages] [Bug 1811094] Re: iptables connlimit allows more connections than the limit when using multiple CPUs

2019-01-11 Thread Seth Forshee
** Changed in: linux (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  iptables connlimit allows more connections than the limit when using
  multiple CPUs

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * The iptables connection count/limit rules can be breached
     with multithreaded network driver/server/client (common)
     due to a race in the conncount/connlimit code.

   * For example:

     # iptables -A INPUT -p tcp -m tcp --syn --dport  \
   -m connlimit --connlimit-above 2000 --connlimit-mask 0 \
   -j DROP

   * The fix is a backport from an upstream commit that resolves
     the problem (plus dependencies for a cleaner backport) that
     address the race condition:

     commit b36e4523d4d5 ("netfilter: nf_conncount: fix garbage
     collection confirm race").

  [Test Case]

   * Server-side: (relevant kernel side)
     (limit TCP port  to only 2000 connections)

     # iptables -A INPUT -p tcp -m tcp --syn --dport  \
   -m connlimit --connlimit-above 2000 --connlimit-mask 0 \
   -j DROP

     # ulimit -SHn 65000   # increase number of open files
     # ruby server.rb  # multi-threaded server

   * Client-side:

     # ulimit -SHn 65000
     # ruby client.rb<# threads>
     

   * Results with Original kernel:
     (client achieves target of 6000 connections > limit of 2000 connections)

     # ruby client.rb 10.230.56.100  6000 3
     1
     2
     3
     <...>
     6000
     Target reached. Thread finishing
     6001
     Target reached. Thread finishing
     6002
     Target reached. Thread finishing
     Threads done. 6002 connections
     press enter to exit

   * Results with Modified kernel:
     (client is limited to 2000 connections, and times out afterward)

     # ruby client.rb 10.230.56.100  6000 3
     1
     2
     3
     <...>
     2000
     <... blocks for a few minutes ...>
     failed to create connection: Connection timed out - connect(2) for 
"10.230.56.100" port 
     failed to create connection: Connection timed out - connect(2) for 
"10.230.56.100" port 
     failed to create connection: Connection timed out - connect(2) for 
"10.230.56.100" port 
     Threads done. 2000 connections
     press enter to exit

   * Test cases possibly available upon request,
     depending on original author's permission.

  [Regression Potential]

   * The patchset has been reviewed by a netfilter maintainer [1] in
     stable mailing list, and was considered OK for 4.14, and that's
     essentially the same backport for 4.15 and 4.4.

   * The changes are limited to netfilter connlimit/conncount (names
     change between older/newer kernel versions).

  [Other Info]

   * The backport for 4.14 [2] is applied as of 4.14.92.

  [1] https://www.spinics.net/lists/stable/msg276883.html
  [2] https://www.spinics.net/lists/stable/msg276910.html

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

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


[Kernel-packages] [Bug 1811200] Re: Add Cavium ThunderX2 SoC UNCORE PMU driver

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

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

Title:
  Add Cavium ThunderX2 SoC UNCORE PMU driver

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

Bug description:
  [Impact]
  No driver for PMU of L3 cache controller (L3C) and the DDR4 Memory Controller 
(DMC) for Cavium ThunderX2 SoC

  [Test Case]
  sudo perf stat -a -e \
  > uncore_dmc_0/cnt_cycles/,\
  > uncore_dmc_0/data_transfers/,\
  > uncore_dmc_0/read_txns/,\
  > uncore_dmc_0/write_txns/ sleep 1

  sudo perf stat -a -e \
  > uncore_l3c_0/read_request/,\
  > uncore_l3c_0/read_hit/,\
  > uncore_l3c_0/inv_request/,\
  > uncore_l3c_0/inv_hit/ sleep 1

  sudo perf stat -a -e uncore_dmc_0/cnt_cycles/ sleep 1

  [Fix]
  Backport patches
  82975c46da  perf: Export perf_event_update_userpage (only for bionic)
  d6310a3f33  Documentation: perf: Add documentation for ThunderX2 PMU uncore 
driver
  69c32972d5  drivers/perf: Add Cavium ThunderX2 SoC UNCORE PMU driver
  and enable CONFIG_THUNDERX2_PMU=m

  [Regression Risk]
  This driver only loaded when CAV901C in ACPI table, lowest risk for other 
platform.

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

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


[Kernel-packages] [Bug 1811443] Re: Disco update: 4.19.14 upstream stable release

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

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

Title:
  Disco update: 4.19.14 upstream stable release

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  
  SRU Justification

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

 4.19.14 upstream stable release
 from git://git.kernel.org/

  
  Linux 4.19.14
  MIPS: Only include mmzone.h when CONFIG_NEED_MULTIPLE_NODES=y
  spi: bcm2835: Unbreak the build of esoteric configs
  tpm: tpm_i2c_nuvoton: use correct command duration for TPM 2.x
  tpm: tpm_try_transmit() refactor error flow.
  arm64: compat: Avoid sending SIGILL for unallocated syscall numbers
  iommu/arm-smmu-v3: Fix big-endian CMD_SYNC writes
  KVM: arm/arm64: vgic: Fix off-by-one bug in vgic_get_irq()
  KVM: arm/arm64: vgic-v2: Set active_source to 0 when restoring state
  KVM: arm/arm64: vgic: Cap SPIs to the VM-defined maximum
  KVM: arm/arm64: vgic: Do not cond_resched_lock() with IRQs disabled
  rtc: m41t80: Correct alarm month range with RTC reads
  ARM: dts: exynos: Specify I2S assigned clocks in proper node
  arm/arm64: KVM: vgic: Force VM halt when changing the active state of GICv3 
PPIs/SGIs
  arm64: KVM: Avoid setting the upper 32 bits of VTCR_EL2 to 1
  smb3: fix large reads on encrypted connections
  CIFS: Fix error mapping for SMB2_LOCK command which caused OFD lock problem
  MIPS: Fix a R1_LLSC_WAR logic in atomic.h
  MIPS: OCTEON: mark RGMII interface disabled on OCTEON III
  MIPS: Expand MIPS32 ASIDs to 64 bits
  MIPS: Align kernel load address to 64KB
  MIPS: Ensure pmd_present() returns false after pmd_mknotpresent()
  MIPS: c-r4k: Add r4k_blast_scache_node for Loongson-3
  MIPS: math-emu: Write-protect delay slot emulation pages
  tools lib traceevent: Fix processing of dereferenced args in bprintk events
  media: v4l2-tpg: array index could become negative
  media: vb2: check memory model for VIDIOC_CREATE_BUFS
  media: vivid: free bitmap_cap when updating std/timings/etc.
  media: imx274: fix stack corruption in imx274_read_reg
  media: rc: cec devices do not have a lirc chardev
  media: cec-pin: fix broken tx_ignore_nack_until_eom error injection
  media: cec: keep track of outstanding transmits
  serial: uartps: Fix interrupt mask issue to handle the RX interrupts properly
  f2fs: sanity check of xattr entry size
  f2fs: fix validation of the block count in sanity_check_raw_super
  f2fs: read page index before freeing
  dax: Use non-exclusive wait in wait_entry_unlocked()
  dax: Don't access a freed inode
  powerpc/tm: Unset MSR[TS] if not recheckpointing
  brcmfmac: Fix out of bounds memory access during fw load
  brcmfmac: fix roamoff=1 modparam
  Btrfs: send, fix race with transaction commits that create snapshots
  btrfs: run delayed items before dropping the snapshot
  Btrfs: fix fsync of files with multiple hard links in new directories
  btrfs: skip file_extent generation check for free_space_inode in 
run_delalloc_nocow
  btrfs: dev-replace: go back to suspend state if another EXCL_OP is running
  btrfs: dev-replace: go back to suspended state if target device is missing
  cdc-acm: fix abnormal DATA RX issue for Mediatek Preloader.
  cgroup: fix CSS_TASK_ITER_PROCS
  crypto: cfb - fix decryption
  crypto: testmgr - add AES-CFB tests
  crypto: chcr - small packet Tx stalls the queue
  crypto: cavium/nitrox - fix a DMA pool free failure
  clk: sunxi-ng: Use u64 for calculation of NM rate
  clk: rockchip: fix typo in rk3188 spdif_frac parent
  spi: bcm2835: Avoid finishing transfer prematurely in IRQ mode
  spi: bcm2835: Fix book-keeping of DMA termination
  spi: bcm2835: Fix race on DMA termination
  ext4: check for shutdown and r/o file system in ext4_write_inode()
  ext4: force inode writes when nfsd calls commit_metadata()
  ext4: avoid declaring fs inconsistent due to invalid file handles
  ext4: include terminating u32 in size of xattr entries when expanding inodes
  ext4: fix EXT4_IOC_GROUP_ADD ioctl
  ext4: missing unlock/put_page() in ext4_try_to_write_inline_data()
  ext4: fix possible use after free in ext4_quota_enable
  ext4: add ext4_sb_bread() to disambiguate ENOMEM cases
  ocxl: Fix endiannes bug in read_afu_name()
  ocxl: Fix endiannes bug in ocxl_link_update_pe()
  perf env: Also consider env->arch == NULL as local operation
  perf pmu: Suppress potential 

[Kernel-packages] [Bug 1811443] [NEW] Disco update: 4.19.14 upstream stable release

2019-01-11 Thread Seth Forshee
Public bug reported:


SRU Justification

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

   4.19.14 upstream stable release
   from git://git.kernel.org/


Linux 4.19.14
MIPS: Only include mmzone.h when CONFIG_NEED_MULTIPLE_NODES=y
spi: bcm2835: Unbreak the build of esoteric configs
tpm: tpm_i2c_nuvoton: use correct command duration for TPM 2.x
tpm: tpm_try_transmit() refactor error flow.
arm64: compat: Avoid sending SIGILL for unallocated syscall numbers
iommu/arm-smmu-v3: Fix big-endian CMD_SYNC writes
KVM: arm/arm64: vgic: Fix off-by-one bug in vgic_get_irq()
KVM: arm/arm64: vgic-v2: Set active_source to 0 when restoring state
KVM: arm/arm64: vgic: Cap SPIs to the VM-defined maximum
KVM: arm/arm64: vgic: Do not cond_resched_lock() with IRQs disabled
rtc: m41t80: Correct alarm month range with RTC reads
ARM: dts: exynos: Specify I2S assigned clocks in proper node
arm/arm64: KVM: vgic: Force VM halt when changing the active state of GICv3 
PPIs/SGIs
arm64: KVM: Avoid setting the upper 32 bits of VTCR_EL2 to 1
smb3: fix large reads on encrypted connections
CIFS: Fix error mapping for SMB2_LOCK command which caused OFD lock problem
MIPS: Fix a R1_LLSC_WAR logic in atomic.h
MIPS: OCTEON: mark RGMII interface disabled on OCTEON III
MIPS: Expand MIPS32 ASIDs to 64 bits
MIPS: Align kernel load address to 64KB
MIPS: Ensure pmd_present() returns false after pmd_mknotpresent()
MIPS: c-r4k: Add r4k_blast_scache_node for Loongson-3
MIPS: math-emu: Write-protect delay slot emulation pages
tools lib traceevent: Fix processing of dereferenced args in bprintk events
media: v4l2-tpg: array index could become negative
media: vb2: check memory model for VIDIOC_CREATE_BUFS
media: vivid: free bitmap_cap when updating std/timings/etc.
media: imx274: fix stack corruption in imx274_read_reg
media: rc: cec devices do not have a lirc chardev
media: cec-pin: fix broken tx_ignore_nack_until_eom error injection
media: cec: keep track of outstanding transmits
serial: uartps: Fix interrupt mask issue to handle the RX interrupts properly
f2fs: sanity check of xattr entry size
f2fs: fix validation of the block count in sanity_check_raw_super
f2fs: read page index before freeing
dax: Use non-exclusive wait in wait_entry_unlocked()
dax: Don't access a freed inode
powerpc/tm: Unset MSR[TS] if not recheckpointing
brcmfmac: Fix out of bounds memory access during fw load
brcmfmac: fix roamoff=1 modparam
Btrfs: send, fix race with transaction commits that create snapshots
btrfs: run delayed items before dropping the snapshot
Btrfs: fix fsync of files with multiple hard links in new directories
btrfs: skip file_extent generation check for free_space_inode in 
run_delalloc_nocow
btrfs: dev-replace: go back to suspend state if another EXCL_OP is running
btrfs: dev-replace: go back to suspended state if target device is missing
cdc-acm: fix abnormal DATA RX issue for Mediatek Preloader.
cgroup: fix CSS_TASK_ITER_PROCS
crypto: cfb - fix decryption
crypto: testmgr - add AES-CFB tests
crypto: chcr - small packet Tx stalls the queue
crypto: cavium/nitrox - fix a DMA pool free failure
clk: sunxi-ng: Use u64 for calculation of NM rate
clk: rockchip: fix typo in rk3188 spdif_frac parent
spi: bcm2835: Avoid finishing transfer prematurely in IRQ mode
spi: bcm2835: Fix book-keeping of DMA termination
spi: bcm2835: Fix race on DMA termination
ext4: check for shutdown and r/o file system in ext4_write_inode()
ext4: force inode writes when nfsd calls commit_metadata()
ext4: avoid declaring fs inconsistent due to invalid file handles
ext4: include terminating u32 in size of xattr entries when expanding inodes
ext4: fix EXT4_IOC_GROUP_ADD ioctl
ext4: missing unlock/put_page() in ext4_try_to_write_inline_data()
ext4: fix possible use after free in ext4_quota_enable
ext4: add ext4_sb_bread() to disambiguate ENOMEM cases
ocxl: Fix endiannes bug in read_afu_name()
ocxl: Fix endiannes bug in ocxl_link_update_pe()
perf env: Also consider env->arch == NULL as local operation
perf pmu: Suppress potential format-truncation warning
perf script: Use fallbacks for branch stacks
perf tools: Use fallback for sample_addr_correlates_sym() cases
perf thread: Add fallback functions for cases where cpumode is insufficient
perf machine: Record if a arch has a single user/kernel address space
clocksource/drivers/arc_timer: Utilize generic sched_clock
DRM: UDL: get rid of useless vblank initialization
drm/v3d: Skip debugfs dumping GCA on platforms without GCA.
platform-msi: Free descriptors in platform_msi_domain_free()
KVM: nVMX: Free the VMREAD/VMWRITE bitmaps if alloc_kvm_area() 

[Kernel-packages] [Bug 1798352] Re: linux-snapdragon: missing meta packages for this flavour

2019-01-11 Thread Stefan Bader
** Also affects: linux-meta-hwe (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

** Changed in: linux-meta (Ubuntu Bionic)
   Status: New => Invalid

** Changed in: linux-meta-hwe (Ubuntu Cosmic)
   Status: New => Invalid

** Changed in: linux-meta-snapdragon (Ubuntu Bionic)
   Status: New => Invalid

** Changed in: linux-meta-hwe (Ubuntu Bionic)
   Importance: Undecided => Critical

** Changed in: linux-meta-hwe (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: linux-meta-hwe (Ubuntu Bionic)
 Assignee: (unassigned) => Stefan Bader (smb)

** Changed in: linux-meta-hwe (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Changed in: linux-meta-hwe (Ubuntu)
   Status: New => Invalid

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

Title:
  linux-snapdragon: missing meta packages for this flavour

Status in linux-meta package in Ubuntu:
  Fix Released
Status in linux-meta-hwe package in Ubuntu:
  Invalid
Status in linux-meta-snapdragon package in Ubuntu:
  Fix Released
Status in linux-meta source package in Bionic:
  Invalid
Status in linux-meta-hwe source package in Bionic:
  Fix Committed
Status in linux-meta-snapdragon source package in Bionic:
  Invalid
Status in linux-meta source package in Cosmic:
  Fix Released
Status in linux-meta-hwe source package in Cosmic:
  Invalid
Status in linux-meta-snapdragon source package in Cosmic:
  Fix Released

Bug description:
  We are missing all of the meta-packages for the snapdragon flavour.

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

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


[Kernel-packages] [Bug 1811254] Re: HP ProBook 470 G5, LED's in Hotkeys f5, f8 and f11 without function

2019-01-11 Thread kuehhe1
** Attachment added: "rfkill_list.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811254/+attachment/5228486/+files/rfkill_list.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/1811254

Title:
  HP ProBook 470 G5, LED's in Hotkeys f5, f8 and f11 without function

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Notebook: HP ProBook 470 G5 (3KZ03EA)
  Distro: Linux Mint 19.1 Tessa
  Desktop: Cinnamon 4.0.8
  Kernel: 4.15.0-43-generic x86_64 bits: 64

  The functions of all hotkeys are given, but the LEDs in the f5 LS-
  mute, f8 micro-mute and f11 wireless on/off buttons do not show the
  status.  The LED in f11 is permanently lit.

  This is my first bug report to launchpad and I ask for leniency and
  troubleshooting support.

  I created 11 logs, unfortunately the upload did not work at once:

  acpi_listen.txt
  apt-cache-policy
  dmesg.log
  lsb_release
  lsinput.log
  lspci-vnvn.log
  udev-db.txt
  version.log
  xev keypress test.txt
  xkbcomp.txt
  xkbmap.txt

  Information: This problem was previously discussed on
  linuxmintusers.de:
  https://www.linuxmintusers.de/index.php?topic=51737.msg710376#msg710376

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

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


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

2019-01-11 Thread 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
  
  backports: bug 1811429 (linux-azure), bug 1811430 (linux-aws-hwe), bug 
1811431 (linux-azure), bug 1811432 (linux-gcp), bug 1811434 (linux-hwe), bug 
1811435 (linux-hwe-edge), bug 1811436 (linux-oracle)
  derivatives: bug 1811420 (linux-raspi2), bug 1811421 (linux-oem), bug 1811422 
(linux-aws), bug 1811423 (linux-azure), bug 1811424 (linux-gcp), bug 1811425 
(linux-kvm), bug 1811427 (linux-oracle)
  -- swm properties --
+ phase: Packaging -- ready to package
+ phase-changed: Friday, 11. January 2019 16:31 UTC
  reason:
prepare-package: Pending -- version not specified

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
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 1811429 (linux-azure), bug 1811430 (linux-aws-hwe), bug 
1811431 (linux-azure), bug 1811432 (linux-gcp), bug 1811434 (linux-hwe), bug 
1811435 (linux-hwe-edge), bug 1811436 (linux-oracle)
  derivatives: bug 1811420 (linux-raspi2), bug 1811421 (linux-oem), bug 1811422 
(linux-aws), bug 1811423 (linux-azure), bug 1811424 (linux-gcp), bug 1811425 
(linux-kvm), bug 1811427 (linux-oracle)
  -- swm properties --
  phase: Packaging -- ready to package
  phase-changed: Friday, 11. January 2019 16:31 UTC
  reason:
prepare-package: Pending -- version not specified

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

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


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

2019-01-11 Thread 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
  
  backports: bug 1811407 (linux-hwe), bug 1811408 (linux-hwe-edge), bug 1811409 
(linux-aws-edge), bug 1811410 (linux-azure-edge), bug 1811411 (linux-gcp-edge), 
bug 1811418 (linux-azure-edge)
  derivatives: bug 1811412 (linux-raspi2), bug 1811414 (linux-aws), bug 1811415 
(linux-azure), bug 1811416 (linux-gcp), bug 1811417 (linux-kvm)
  -- swm properties --
+ phase: Packaging -- ready to package
+ phase-changed: Friday, 11. January 2019 16:29 UTC
  reason:
prepare-package: Pending -- version not specified

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  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 1811407 (linux-hwe), bug 1811408 (linux-hwe-edge), bug 1811409 
(linux-aws-edge), bug 1811410 (linux-azure-edge), bug 1811411 (linux-gcp-edge), 
bug 1811418 (linux-azure-edge)
  derivatives: bug 1811412 (linux-raspi2), bug 1811414 (linux-aws), bug 1811415 
(linux-azure), bug 1811416 (linux-gcp), bug 1811417 (linux-kvm)
  -- swm properties --
  phase: Packaging -- ready to package
  phase-changed: Friday, 11. January 2019 16:29 UTC
  reason:
prepare-package: Pending -- version not specified

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

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


[Kernel-packages] [Bug 1811421] Re: linux-oem: -proposed tracker

2019-01-11 Thread 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 --
  kernel-stable-master-bug: 1811419
+ reason:
+   prepare-package: Stalled -- waiting for master bug

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

Title:
  linux-oem:  -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:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-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 --
  kernel-stable-master-bug: 1811419
  reason:
prepare-package: Stalled -- waiting for master bug

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

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


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

2019-01-11 Thread 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
  
  backports: bug 1811429 (linux-azure), bug 1811430 (linux-aws-hwe), bug 
1811431 (linux-azure), bug 1811432 (linux-gcp), bug 1811434 (linux-hwe), bug 
1811435 (linux-hwe-edge), bug 1811436 (linux-oracle)
  derivatives: bug 1811420 (linux-raspi2), bug 1811421 (linux-oem), bug 1811422 
(linux-aws), bug 1811423 (linux-azure), bug 1811424 (linux-gcp), bug 1811425 
(linux-kvm), bug 1811427 (linux-oracle)
+ -- swm properties --
+ reason:
+   prepare-package: Pending -- version not specified

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
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 1811429 (linux-azure), bug 1811430 (linux-aws-hwe), bug 
1811431 (linux-azure), bug 1811432 (linux-gcp), bug 1811434 (linux-hwe), bug 
1811435 (linux-hwe-edge), bug 1811436 (linux-oracle)
  derivatives: bug 1811420 (linux-raspi2), bug 1811421 (linux-oem), bug 1811422 
(linux-aws), bug 1811423 (linux-azure), bug 1811424 (linux-gcp), bug 1811425 
(linux-kvm), bug 1811427 (linux-oracle)
  -- swm properties --
  reason:
prepare-package: Pending -- version not specified

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

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


[Kernel-packages] [Bug 1811422] Re: linux-aws: -proposed tracker

2019-01-11 Thread 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 --
  kernel-stable-master-bug: 1811419
+ reason:
+   prepare-package: Stalled -- waiting for master bug

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

Title:
  linux-aws:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow 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 --
  kernel-stable-master-bug: 1811419
  reason:
prepare-package: Stalled -- waiting for master bug

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

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


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

2019-01-11 Thread 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 --
  kernel-stable-master-bug: 1811419
+ reason:
+   prepare-package: Stalled -- waiting for master bug

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

Title:
  linux-kvm:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow 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 --
  kernel-stable-master-bug: 1811419
  reason:
prepare-package: Stalled -- waiting for master bug

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

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


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

2019-01-11 Thread 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 --
  kernel-stable-master-bug: 1811419
+ reason:
+   prepare-package: Stalled -- waiting for master bug

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

Title:
  linux-azure:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-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:
  New
Status in Kernel SRU Workflow stakeholder-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-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 --
  kernel-stable-master-bug: 1811419
  reason:
prepare-package: Stalled -- waiting for master bug

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

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


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

2019-01-11 Thread 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 --
  kernel-stable-master-bug: 1811419
+ reason:
+   prepare-package: Stalled -- waiting for master bug

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

Title:
  linux-azure:  -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1811419
  reason:
prepare-package: Stalled -- waiting for master bug

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

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


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

2019-01-11 Thread 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 --
  kernel-stable-master-bug: 1811419
+ reason:
+   prepare-package: Stalled -- waiting for master bug

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

Title:
  linux-gcp:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-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:
  New
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 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 --
  kernel-stable-master-bug: 1811419
  reason:
prepare-package: Stalled -- waiting for master bug

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

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


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

2019-01-11 Thread 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 --
  kernel-stable-master-bug: 1811419
+ reason:
+   prepare-package: Stalled -- waiting for master bug

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

Title:
  linux-azure:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-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:
  New
Status in Kernel SRU Workflow stakeholder-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-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 --
  kernel-stable-master-bug: 1811419
  reason:
prepare-package: Stalled -- waiting for master bug

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

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


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

2019-01-11 Thread 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 --
  kernel-stable-master-bug: 1811419
+ reason:
+   prepare-package: Stalled -- waiting for master bug

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

Title:
  linux-gcp:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-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:
  New
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: 1811419
  reason:
prepare-package: Stalled -- waiting for master bug

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

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


[Kernel-packages] [Bug 1811432] [NEW] linux-gcp: -proposed tracker

2019-01-11 Thread Stefan Bader
Public bug reported:

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: 1811419
reason:
  prepare-package: Stalled -- waiting for master bug

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

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

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

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

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

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

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

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

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

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

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

** Affects: kernel-sru-workflow/snap-release-to-beta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-candidate
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-edge
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-stable
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

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

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

** Affects: linux-gcp (Ubuntu Xenial)
 Importance: Medium
 Status: Confirmed


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-backport-of-1811419 kernel-sru-cycle-2019.01.14-1 xenial

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

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

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

** Tags added: xenial

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

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

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

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

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

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

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

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

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

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

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

** Also affects: kernel-sru-workflow/snap-release-to-beta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-candidate
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-edge
   Importance: Undecided
   Status: New

** Also affects: 

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

2019-01-11 Thread Stefan Bader
** 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 1811429 (linux-azure), bug 1811430 (linux-aws-hwe), bug 
1811431 (linux-azure), bug 1811432 (linux-gcp), bug 1811434 (linux-hwe), bug 
1811435 (linux-hwe-edge), bug 1811436 (linux-oracle)
+ derivatives: bug 1811420 (linux-raspi2), bug 1811421 (linux-oem), bug 1811422 
(linux-aws), bug 1811423 (linux-azure), bug 1811424 (linux-gcp), bug 1811425 
(linux-kvm), bug 1811427 (linux-oracle)

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
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 1811429 (linux-azure), bug 1811430 (linux-aws-hwe), bug 
1811431 (linux-azure), bug 1811432 (linux-gcp), bug 1811434 (linux-hwe), bug 
1811435 (linux-hwe-edge), bug 1811436 (linux-oracle)
  derivatives: bug 1811420 (linux-raspi2), bug 1811421 (linux-oem), bug 1811422 
(linux-aws), bug 1811423 (linux-azure), bug 1811424 (linux-gcp), bug 1811425 
(linux-kvm), bug 1811427 (linux-oracle)
  -- swm properties --
  reason:
prepare-package: Pending -- version not specified

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

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


[Kernel-packages] [Bug 1811431] [NEW] linux-azure: -proposed tracker

2019-01-11 Thread Stefan Bader
Public bug reported:

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: 1811419
reason:
  prepare-package: Stalled -- waiting for master bug

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

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

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

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

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

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

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

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

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

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

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

** Affects: kernel-sru-workflow/snap-release-to-beta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-candidate
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-edge
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-stable
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/stakeholder-signoff
 Importance: Medium
 Assignee: linux-azure stakeholder signoff (linux-azure-signoff)
 Status: New

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

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

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

** Affects: linux-azure (Ubuntu Xenial)
 Importance: Medium
 Status: Confirmed


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-backport-of-1811419 kernel-sru-cycle-2019.01.14-1 xenial

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

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

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

** Tags added: xenial

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

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

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

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

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

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

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

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

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

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

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

** Also affects: kernel-sru-workflow/snap-release-to-beta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-candidate
   Importance: Undecided
  

[Kernel-packages] [Bug 1806682]

2019-01-11 Thread caravena
Created attachment 280391
$ LANGUAGE=C grep . /sys/class/thermal/thermal*/*

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

Title:
  ACPI: Invalid passive threshold

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  dmesg:
  [1.423794] ACPI: Invalid passive threshold

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2739 F pulseaudio
   /dev/snd/pcmC0D0p:   caravena   2739 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec  4 09:17:14 2018
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.176
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (1 days ago)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1811423] [NEW] linux-azure: -proposed tracker

2019-01-11 Thread Stefan Bader
Public bug reported:

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

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

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

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

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

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

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

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

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

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

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

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

** Affects: kernel-sru-workflow/snap-release-to-beta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-candidate
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-edge
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-stable
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/stakeholder-signoff
 Importance: Medium
 Assignee: linux-azure stakeholder signoff (linux-azure-signoff)
 Status: New

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

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

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

** Affects: linux-azure (Ubuntu Bionic)
 Importance: Medium
 Status: Confirmed


** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2019.01.14-1 kernel-sru-derivative-of-1811419

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

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

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

** Tags added: bionic

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

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

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

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

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

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

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

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

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

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

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

** Also affects: kernel-sru-workflow/snap-release-to-beta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-candidate
   Importance: Undecided
   Status: New

** Also affects: 

[Kernel-packages] [Bug 1811422] [NEW] linux-aws: -proposed tracker

2019-01-11 Thread Stefan Bader
Public bug reported:

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

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

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

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

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

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

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

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

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

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

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

** Affects: kernel-sru-workflow/snap-release-to-beta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-candidate
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-edge
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-stable
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

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

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

** Affects: linux-aws (Ubuntu Bionic)
 Importance: Medium
 Status: Confirmed


** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2019.01.14-1 kernel-sru-derivative-of-1811419

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

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

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

** Tags added: bionic

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

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

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

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

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

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

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

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

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

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

** Also affects: kernel-sru-workflow/snap-release-to-beta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-candidate
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-edge
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-stable
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

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

** Changed in: kernel-sru-workflow/automated-testing
   Importance: 

[Kernel-packages] [Bug 1811424] [NEW] linux-gcp: -proposed tracker

2019-01-11 Thread Stefan Bader
Public bug reported:

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

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

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

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

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

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

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

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

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

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

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

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

** Affects: kernel-sru-workflow/snap-release-to-beta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-candidate
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-edge
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-stable
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

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

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

** Affects: linux-gcp (Ubuntu Bionic)
 Importance: Medium
 Status: Confirmed


** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2019.01.14-1 kernel-sru-derivative-of-1811419

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

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

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

** Tags added: bionic

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

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

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

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

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

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

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

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

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

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

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

** Also affects: kernel-sru-workflow/snap-release-to-beta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-candidate
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-edge
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-stable
   Importance: Undecided
   Status: New

** Also 

[Kernel-packages] [Bug 1811425] [NEW] linux-kvm: -proposed tracker

2019-01-11 Thread Stefan Bader
Public bug reported:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

** Affects: linux-kvm (Ubuntu Bionic)
 Importance: Medium
 Status: Confirmed


** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2019.01.14-1 kernel-sru-derivative-of-1811419

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

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

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

** Tags added: bionic

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

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

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

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

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

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

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

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

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

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

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1811429] [NEW] linux-azure: -proposed tracker

2019-01-11 Thread Stefan Bader
Public bug reported:

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

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

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

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

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

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

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

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

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

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

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

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

** Affects: kernel-sru-workflow/stakeholder-signoff
 Importance: Medium
 Assignee: linux-azure stakeholder signoff (linux-azure-signoff)
 Status: New

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

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

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

** Affects: linux-azure (Ubuntu Trusty)
 Importance: Medium
 Status: Confirmed


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-backport-of-1811419 kernel-sru-cycle-2019.01.14-1 trusty

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

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

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

** Tags added: trusty

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

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

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

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

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

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

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

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

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

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

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

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

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

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

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

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

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

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

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

** Changed in: kernel-sru-workflow/prepare-package
   

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

2019-01-11 Thread 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 --
  kernel-stable-master-bug: 1811406
+ reason:
+   prepare-package: Stalled -- waiting for master bug

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

Title:
  linux-azure:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow 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 Cosmic:
  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: 1811406
  reason:
prepare-package: Stalled -- waiting for master bug

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

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


[Kernel-packages] [Bug 1811414] Re: linux-aws: -proposed tracker

2019-01-11 Thread 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 --
  kernel-stable-master-bug: 1811406
+ reason:
+   prepare-package: Stalled -- waiting for master bug

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

Title:
  linux-aws:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow 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 Cosmic:
  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: 1811406
  reason:
prepare-package: Stalled -- waiting for master bug

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

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


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

2019-01-11 Thread 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
  
  backports: bug 1811407 (linux-hwe), bug 1811408 (linux-hwe-edge), bug 1811409 
(linux-aws-edge), bug 1811410 (linux-azure-edge), bug 1811411 (linux-gcp-edge), 
bug 1811418 (linux-azure-edge)
  derivatives: bug 1811412 (linux-raspi2), bug 1811414 (linux-aws), bug 1811415 
(linux-azure), bug 1811416 (linux-gcp), bug 1811417 (linux-kvm)
+ -- swm properties --
+ reason:
+   prepare-package: Pending -- version not specified

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  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 1811407 (linux-hwe), bug 1811408 (linux-hwe-edge), bug 1811409 
(linux-aws-edge), bug 1811410 (linux-azure-edge), bug 1811411 (linux-gcp-edge), 
bug 1811418 (linux-azure-edge)
  derivatives: bug 1811412 (linux-raspi2), bug 1811414 (linux-aws), bug 1811415 
(linux-azure), bug 1811416 (linux-gcp), bug 1811417 (linux-kvm)
  -- swm properties --
  reason:
prepare-package: Pending -- version not specified

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

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


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

2019-01-11 Thread 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 --
  kernel-stable-master-bug: 1811406
+ reason:
+   prepare-package: Stalled -- waiting for master bug

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

Title:
  linux-gcp:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-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-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Cosmic:
  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: 1811406
  reason:
prepare-package: Stalled -- waiting for master bug

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

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


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

2019-01-11 Thread 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 --
  kernel-stable-master-bug: 1811406
+ reason:
+   prepare-package: Stalled -- waiting for master bug

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

Title:
  linux-kvm:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow 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 Cosmic:
  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: 1811406
  reason:
prepare-package: Stalled -- waiting for master bug

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

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


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

2019-01-11 Thread Stefan Bader
Public bug reported:

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

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

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

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

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

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

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

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

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

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

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

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

** Affects: kernel-sru-workflow/snap-release-to-beta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-candidate
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-edge
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-stable
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Status: Invalid

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

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

** Affects: linux (Ubuntu Bionic)
 Importance: Medium
 Status: Confirmed


** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2019.01.14-1 kernel-sru-master-kernel

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

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

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

** Tags added: bionic

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

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

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

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

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

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

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

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

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

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

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

** Also affects: kernel-sru-workflow/snap-release-to-beta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-candidate
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-edge
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-stable
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: 

[Kernel-packages] [Bug 1811421] [NEW] linux-oem: -proposed tracker

2019-01-11 Thread Stefan Bader
Public bug reported:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

** Affects: linux-oem (Ubuntu Bionic)
 Importance: Medium
 Status: Confirmed


** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2019.01.14-1 kernel-sru-derivative-of-1811419

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

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

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

** Tags added: bionic

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

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

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

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

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

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

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

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

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

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

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

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

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

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

2019-01-11 Thread Stefan Bader
** 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 1811407 (linux-hwe), bug 1811408 (linux-hwe-edge), bug 1811409 
(linux-aws-edge), bug 1811410 (linux-azure-edge), bug 1811411 (linux-gcp-edge), 
bug 1811418 (linux-azure-edge)
+ derivatives: bug 1811412 (linux-raspi2), bug 1811414 (linux-aws), bug 1811415 
(linux-azure), bug 1811416 (linux-gcp), bug 1811417 (linux-kvm)

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  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 1811407 (linux-hwe), bug 1811408 (linux-hwe-edge), bug 1811409 
(linux-aws-edge), bug 1811410 (linux-azure-edge), bug 1811411 (linux-gcp-edge), 
bug 1811418 (linux-azure-edge)
  derivatives: bug 1811412 (linux-raspi2), bug 1811414 (linux-aws), bug 1811415 
(linux-azure), bug 1811416 (linux-gcp), bug 1811417 (linux-kvm)
  -- swm properties --
  reason:
prepare-package: Pending -- version not specified

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

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


[Kernel-packages] [Bug 1811415] [NEW] linux-azure: -proposed tracker

2019-01-11 Thread Stefan Bader
Public bug reported:

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: 1811406
reason:
  prepare-package: Stalled -- waiting for master bug

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

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

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

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

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

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

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

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

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

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

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

** Affects: kernel-sru-workflow/stakeholder-signoff
 Importance: Medium
 Assignee: linux-azure stakeholder signoff (linux-azure-signoff)
 Status: New

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

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

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

** Affects: linux-azure (Ubuntu Cosmic)
 Importance: Medium
 Status: Confirmed


** Tags: cosmic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2019.01.14-1 kernel-sru-derivative-of-1811406

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

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

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

** Tags added: cosmic

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

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

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

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

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

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

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

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

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

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

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

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

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

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

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

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

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

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

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

[Kernel-packages] [Bug 1811416] [NEW] linux-gcp: -proposed tracker

2019-01-11 Thread Stefan Bader
Public bug reported:

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: 1811406
reason:
  prepare-package: Stalled -- waiting for master bug

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

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

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

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

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

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

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

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

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

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

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

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

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

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

** Affects: linux-gcp (Ubuntu Cosmic)
 Importance: Medium
 Status: Confirmed


** Tags: cosmic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2019.01.14-1 kernel-sru-derivative-of-1811406

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

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

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

** Tags added: cosmic

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

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

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

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

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

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

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

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

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

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

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

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

** Changed in: 

[Kernel-packages] [Bug 1811417] [NEW] linux-kvm: -proposed tracker

2019-01-11 Thread Stefan Bader
Public bug reported:

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: 1811406
reason:
  prepare-package: Stalled -- waiting for master bug

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

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

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

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

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

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

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

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

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

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

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

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

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

** Affects: linux-kvm (Ubuntu Cosmic)
 Importance: Medium
 Status: Confirmed


** Tags: cosmic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2019.01.14-1 kernel-sru-derivative-of-1811406

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

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

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

** Tags added: cosmic

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

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

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

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

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

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

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

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

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

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

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

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

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

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

** 

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

2019-01-11 Thread Stefan Bader
Public bug reported:

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 1811407 (linux-hwe), bug 1811408 (linux-hwe-edge), bug 1811409 
(linux-aws-edge), bug 1811410 (linux-azure-edge), bug 1811411 (linux-gcp-edge), 
bug 1811418 (linux-azure-edge)
derivatives: bug 1811412 (linux-raspi2), bug 1811414 (linux-aws), bug 1811415 
(linux-azure), bug 1811416 (linux-gcp), bug 1811417 (linux-kvm)

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

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

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

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

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

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

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

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

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

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

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

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Status: Invalid

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

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

** Affects: linux (Ubuntu Cosmic)
 Importance: Medium
 Status: Confirmed


** Tags: cosmic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2019.01.14-1 kernel-sru-master-kernel

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

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

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

** Tags added: cosmic

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

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

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

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

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

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

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

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

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

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

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

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

** 

[Kernel-packages] [Bug 1807682] Re: system does not start

2019-01-11 Thread g.bruno
Found a possible solution on 
https://ubuntuforums.org/showthread.php?t=2406453
---
Well. Problem is the root folder has user as an owner.
Code:

root@myserver:~# stat -c "%U %G" /
user user

Solution is:
Code:

root@myserver:~# chown root:root /
root@myserver:~# stat -c "%U %G" /
root root

root@myserver:~# systemctl start systemd-tmpfiles-setup
root@myserver:~#
-
For me the result of 'stat -c "%U %G" /' is
nobody nogroup
I changed it to root:root and hope that it will work.
Greetings gbruno

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

Title:
  system does not start

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The System does not start. When starting in recovery mode the error

  "failed to start Create Static Device Nodes in /dev.
  See 'systemctl status systemd-tmpfiles-setupd-dev.service' for details"
  is shown.

  When typing

  systemctl status systemd-tmpfiles-setupd-dev.service

  into the console, the answer is:

  Unit systemd-tmpfiles-setupd-dev.service could not be found.

  The System does only start in recovery mode and I would expect an
  normal start.

  Thanks for help in advance.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-42-generic 4.15.0-42.45
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  administrator   2025 F pulseaudio
   /dev/snd/controlC1:  administrator   2025 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 10 10:42:07 2018
  HibernationDevice: RESUME=UUID=6ffe8604-b66f-421e-afbd-50bcdeb4ff9e
  InstallationDate: Installed on 2012-05-11 (2404 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=0c7307f0-bcbe-4a1e-8d04-3004f27151bc ro recovery nomodeset
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-12-10 (0 days ago)
  dmi.bios.date: 12/27/2011
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0146.2011.1227.1631
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67BL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10189-209
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0146.2011.1227.1631:bd12/27/2011:svnbluechipComputerAG:pn:pvr:rvnIntelCorporation:rnDH67BL:rvrAAG10189-209:cvn:ct3:cvr:
  dmi.sys.vendor: bluechip Computer AG

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

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


[Kernel-packages] [Bug 1811414] [NEW] linux-aws: -proposed tracker

2019-01-11 Thread Stefan Bader
Public bug reported:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

** Affects: linux-aws (Ubuntu Cosmic)
 Importance: Medium
 Status: Confirmed


** Tags: cosmic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2019.01.14-1 kernel-sru-derivative-of-1811406

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

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

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

** Tags added: cosmic

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

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

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

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

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

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

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

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

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

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

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1807682] Re: system does not start

2019-01-11 Thread g.bruno
I got the same issue. "systemctl status systemd-tmpfiles-setupd-dev.service" 
yields the same response. But my system (Ubunutu 18.04.1) is starting properly 
and there are no problems when using it. 
In /var/log/syslog these lines precede the error:
Jan 11 14:37:48 Intel-i5-Tower systemd[1]: Started Apply Kernel Variables.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks 
encountered in /dev/cuse, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks 
encountered in /dev/autofs, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks 
encountered in /dev/btrfs-control, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks 
encountered in /dev/userio, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks 
encountered in /dev/vfio, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks 
encountered in /dev/vfio/vfio, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks 
encountered in /dev/vhci, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks 
encountered in /dev/uhid, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks 
encountered in /dev/vhost-net, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks 
encountered in /dev/vhost-vsock, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks 
encountered in /dev/snd, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks 
encountered in /dev/snd, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks 
encountered in /dev/snd/timer, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks 
encountered in /dev/snd/seq, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd[1]: systemd-tmpfiles-setup-dev.service: 
Main process exited, code=exited, status=1/FAILURE
Jan 11 14:37:48 Intel-i5-Tower systemd[1]: systemd-tmpfiles-setup-dev.service: 
Failed with result 'exit-code'.
Jan 11 14:37:48 Intel-i5-Tower systemd-fsck[584]: Ubuntu/home: sauber, 
316299/66273280 Dateien, 223989723/265086556 Blöcke
Jan 11 14:37:48 Intel-i5-Tower systemd[1]: Failed to start Create Static Device 
Nodes in /dev.
Jan 11 14:37:48 Intel-i5-Tower systemd[1]: Reached target Local File Systems 
(Pre).

Perhaps the error is due to the unsave symlinks?

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

Title:
  system does not start

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The System does not start. When starting in recovery mode the error

  "failed to start Create Static Device Nodes in /dev.
  See 'systemctl status systemd-tmpfiles-setupd-dev.service' for details"
  is shown.

  When typing

  systemctl status systemd-tmpfiles-setupd-dev.service

  into the console, the answer is:

  Unit systemd-tmpfiles-setupd-dev.service could not be found.

  The System does only start in recovery mode and I would expect an
  normal start.

  Thanks for help in advance.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-42-generic 4.15.0-42.45
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  administrator   2025 F pulseaudio
   /dev/snd/controlC1:  administrator   2025 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 10 10:42:07 2018
  HibernationDevice: RESUME=UUID=6ffe8604-b66f-421e-afbd-50bcdeb4ff9e
  InstallationDate: Installed on 2012-05-11 (2404 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=0c7307f0-bcbe-4a1e-8d04-3004f27151bc ro recovery nomodeset
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-12-10 (0 days ago)
  dmi.bios.date: 12/27/2011
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0146.2011.1227.1631
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67BL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10189-209
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0146.2011.1227.1631:bd12/27/2011:svnbluechipComputerAG:pn:pvr:rvnIntelCorporation:rnDH67BL:rvrAAG10189-209:cvn:ct3:cvr:
  dmi.sys.vendor: bluechip Computer AG

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1802260] Re: Please include modules for NVMe and USB HID in pc-kernel snap initrd

2019-01-11 Thread Stefan Bader
Note the previous comment. This bug report will not automatically be
updated because the deb-to-snap related code is no source package in
Launchpad's mind.

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

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

Title:
  Please include modules for NVMe and USB HID in pc-kernel snap initrd

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  When trying Ubuntu Core with the pc-kernel snap, the system showed
  'cannot find writable partition'. The system was stopped at the initrd
  stage and didn't accept any input.

  My system is using a NVMe disk and it seems the pc-kernel doesn't
  provide the related modules in its initrd. Also, it's not possible to
  enter the initramfs environment because of the lacking of USB HID
  modules.

  Is it possible to include these two categories of drivers in the
  initrd of pc-kernel, please?

  Verified both 4.4 and 4.15 (track 18) have the same issue.
  $ squashfuse pc-kernel_162.snap pc-kernel
  $ lsinitramfs pc-kernel/initrd.img |grep -E 'nvme|usbhid'
  [nothing is showed]
  $ fusermount -u pc-kernel
  $ squashfuse pc-kernel_165.snap pc-kernel
  $ lsinitramfs pc-kernel/initrd.img |grep -E 'nvme|usbhid'
  [nothing is showed]
  $ fusermount -u pc-kernel

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

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


[Kernel-packages] [Bug 1808768] Re: Initrd of pc-kernel snap contains out-of-date packages

2019-01-11 Thread Stefan Bader
This bug report was made for tracking changes on how snaps are being produced. 
Unfortunately this is not reflecting well with Launchpad because the required 
changes had to be made in git trees which not directly map to a source package 
in Launchpad's mind.
I have applied the changes to both makefiles (xenial and bionic) so the next 
snaps being done should be fixed. But again there will not be an automatic 
state change on this bug report.

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

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

Title:
  Initrd of pc-kernel snap contains out-of-date packages

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  The build script does not install package updates during generate the
  pc-kernel snap.

  I met this bug #1783810 when I was verify my Ubuntu Core 18 image on KVM.
  The system stuck at resizing the writable partition. the resize script of 
initrd called sgdisk to achieve the resizing. Inside sgdisk, it use libuuid1 to 
get random bytes and generate UUIDs. After I extracted the kernel snap, I found 
it is still using libuuid1 2.31.1-0.4ubuntu3 which is not the latest version. 
At this moment, Bionic has 2.31.1-0.4ubuntu3.2.
  Then I added commands to make the build script installing package updates. 
After that, the system can boot correctly without any problem.

  I am wondering if there is any concern to pull updates before
  building?

  The attachment is my patch to pull updates.

  Snippet of console output, before patch
  [2.491404] usbcore: registered new interface driver usb-storage
  [2.503788] sdhci: Secure Digital Host Controller Interface driver
  [2.505627] sdhci: Copyright(c) Pierre Ossman
  [2.548485] initrd: found more than 10% free space on disk, resizing 
/dev/sda3
  [2.550345] initrd: partition to full disk size, see /dev/kmsg for details
  [2.912472] clocksource: tsc: mask: 0x max_cycles: 
0x255b2dea34c, max_idle_ns: 440795243480 ns
  ## several keystrokes here, or the boot process won't continue
  [  351.361426] random: crng init done
  [  351.423462] fixing backup GPT
  [  352.435735] systemd-udevd[240]: passed device to netlink monitor 
0x55e45653e330
  [  352.443221]  sda: sda1 sda2 sda3
  [  352.445486] The operation has completed successfully.

  Snippet of console output, after patch
  [2.548203] usbcore: registered new interface driver usb-storage
  [2.561439] sdhci: Secure Digital Host Controller Interface driver
  [2.562878] sdhci: Copyright(c) Pierre Ossman
  [2.602093] initrd: found more than 10% free space on disk, resizing 
/dev/sda3
  [2.603900] initrd: partition to full disk size, see /dev/kmsg for details
  ## block a few seconds, until timeout.
  [2.912418] clocksource: tsc: mask: 0x max_cycles: 
0x255b2dea34c, max_idle_ns: 440795243480 ns
  [9.174552] random: fast init done
  [9.179127] random: parted: uninitialized urandom read (16 bytes read)
  [9.183726] random: parted: uninitialized urandom read (16 bytes read)
  [9.190606] random: parted: uninitialized urandom read (16 bytes read)
  [9.230419] fixing backup GPT
  [9.236989] random: crng init done
  [9.238102] random: 5 urandom warning(s) missed due to ratelimiting
  [   10.245047] systemd-udevd[259]: passed device to netlink monitor 
0x56376c45b150
  [   10.253093]  sda: sda1 sda2 sda3
  [   10.256202] The operation has completed successfully.

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

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


[Kernel-packages] [Bug 1810998] Re: CPU hard lockup with rigorous writes to NVMe drive

2019-01-11 Thread Kleber Sacilotto de Souza
** Changed in: linux (Ubuntu Bionic)
   Status: New => Fix Committed

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

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

Title:
  CPU hard lockup with rigorous writes to NVMe drive

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * Users may experience cpu hard lockups when performing
     rigorous writes to NVMe drives.

   * The fix addresses an scheduling issue in the original
     implementation of wbt/writeback throttling

   * The fix is commit 2887e41b910b ("blk-wbt: Avoid lock
     contention and thundering herd issue in wbt_wait"),
     plus its fix commit 38cfb5a45ee0 ("blk-wbt: improve
     waking of tasks").

   * Plus a few dependency commits for each fix.

   * Backports are trivial: mainly replace rq_wait_inc_below()
     with the equivalent atomic_inc_below(), and maintain the
     __wbt_done() signature, both due to the lack of commit
     a79050434b45 ("blk-rq-qos: refactor out common elements
     of blk-wbt"), that changes lots of other/unrelated code.

  [Test Case]

   * This command has been reported to reproduce the problem:

     $ sudo iozone -R -s 5G -r 1m -S 2048 -i 0 -G -c -o -l 128 -u 128 -t
  128

   * It generates stack traces as below in the original kernel,
     and does not generate them in the modified/patched kernel.

   * The user/reporter verified the test kernel with these patches
     resolved the problem.

   * The developer verified in 2 systems (4-core and 24-core but
     no NVMe) for regressions, and no error messages were logged
     to dmesg.

  [Regression Potential]

   * The regression potential is contained within writeback
     throttling mechanism (block/blk-wbt.*).

   * The commits have been verified for fixes in later commits in
     linux-next as of 2019-01-08 and all known fix commits are in.

  [Other Info]

   * The problem has been introduced with the blk-wbt mechanism,
     in v4.10-rc1, and the fix commits in v4.19-rc1 and -rc2,
     so only Bionic and Cosmic needs this.

  [Stack Traces]

  [ 393.628647] NMI watchdog: Watchdog detected hard LOCKUP on cpu 30
  ...
  [ 393.628704] CPU: 30 PID: 0 Comm: swapper/30 Tainted: P OE 4.15.0-20-generic 
#21-Ubuntu
  ...
  [ 393.628720] Call Trace:
  [ 393.628721] 
  [ 393.628724] enqueue_task_fair+0x6c/0x7f0
  [ 393.628726] ? __update_load_avg_blocked_se.isra.37+0xd1/0x150
  [ 393.628728] ? __update_load_avg_blocked_se.isra.37+0xd1/0x150
  [ 393.628731] activate_task+0x57/0xc0
  [ 393.628735] ? sched_clock+0x9/0x10
  [ 393.628736] ? sched_clock+0x9/0x10
  [ 393.628738] ttwu_do_activate+0x49/0x90
  [ 393.628739] try_to_wake_up+0x1df/0x490
  [ 393.628741] default_wake_function+0x12/0x20
  [ 393.628743] autoremove_wake_function+0x12/0x40
  [ 393.628744] __wake_up_common+0x73/0x130
  [ 393.628745] __wake_up_common_lock+0x80/0xc0
  [ 393.628746] __wake_up+0x13/0x20
  [ 393.628749] __wbt_done.part.21+0xa4/0xb0
  [ 393.628749] wbt_done+0x72/0xa0
  [ 393.628753] blk_mq_free_request+0xca/0x1a0
  [ 393.628755] blk_mq_end_request+0x48/0x90
  [ 393.628760] nvme_complete_rq+0x23/0x120 [nvme_core]
  [ 393.628763] nvme_pci_complete_rq+0x7a/0x130 [nvme]
  [ 393.628764] __blk_mq_complete_request+0xd2/0x140
  [ 393.628766] blk_mq_complete_request+0x18/0x20
  [ 393.628767] nvme_process_cq+0xe1/0x1b0 [nvme]
  [ 393.628768] nvme_irq+0x23/0x50 [nvme]
  [ 393.628772] __handle_irq_event_percpu+0x44/0x1a0
  [ 393.628773] handle_irq_event_percpu+0x32/0x80
  [ 393.628774] handle_irq_event+0x3b/0x60
  [ 393.628778] handle_edge_irq+0x7c/0x190
  [ 393.628779] handle_irq+0x20/0x30
  [ 393.628783] do_IRQ+0x46/0xd0
  [ 393.628784] common_interrupt+0x84/0x84
  [ 393.628785] 
  ...
  [ 393.628794] ? cpuidle_enter_state+0x97/0x2f0
  [ 393.628796] cpuidle_enter+0x17/0x20
  [ 393.628797] call_cpuidle+0x23/0x40
  [ 393.628798] do_idle+0x18c/0x1f0
  [ 393.628799] cpu_startup_entry+0x73/0x80
  [ 393.628802] start_secondary+0x1a6/0x200
  [ 393.628804] secondary_startup_64+0xa5/0xb0
  [ 393.628805] Code: ...

  [ 405.981597] nvme nvme1: I/O 393 QID 6 timeout, completion polled

  [ 435.597209] INFO: rcu_sched detected stalls on CPUs/tasks:
  [ 435.602858] 30-...0: (1 GPs behind) idle=e26/1/0 softirq=6834/6834 fqs=4485
  [ 435.610203] (detected by 8, t=15005 jiffies, g=6396, c=6395, q=146818)
  [ 435.617025] Sending NMI from CPU 8 to CPUs 30:
  [ 435.617029] NMI backtrace for cpu 30
  [ 435.617031] CPU: 30 PID: 0 Comm: swapper/30 Tainted: P OE 4.15.0-20-generic 
#21-Ubuntu
  ...
  [ 435.617047] Call Trace:
  [ 435.617048] 
  [ 435.617051] enqueue_entity+0x9f/0x6b0
  [ 435.617053] enqueue_task_fair+0x6c/0x7f0
  [ 435.617056] activate_task+0x57/0xc0
  [ 435.617059] ? sched_clock+0x9/0x10
  [ 435.617060] ? 

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

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

apport-collect 1811394

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

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

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

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

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

Title:
  ipset kernel error: 4.15.0-43-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When running the following script: 
https://github.com/DevelopersPL/pkgbuild/blob/master/ipset-nuclear/ipset-nuclear
 on the 4.15.0-43-generic kernel it leads to a kernel panic.
  Tested the same with 17.10 (4.13 kernel) and 18.10 (4.18 kernel) and no 
problems with those.

  The issue was first mentioned in our forum
  (https://forum.proxmox.com/threads/kernel-panic-
  ip_set_hash_net.50138/#post-234532) on our own kernel that's based on
  the Ubuntu 4.15. After further investigations neither Debian 9 (4.9
  kernel) nor Arch Linux (4.20 kernel) exhibited that same issue.

  The attached log has the errors of one run of the ipset-nuclear script.
  The kernel panic on the host side can also be triggered from an unprivileged 
container (Arch Linux, LXC)

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

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


[Kernel-packages] [Bug 1811394] [NEW] ipset kernel error: 4.15.0-43-generic

2019-01-11 Thread David Limbeck
Public bug reported:

When running the following script: 
https://github.com/DevelopersPL/pkgbuild/blob/master/ipset-nuclear/ipset-nuclear
 on the 4.15.0-43-generic kernel it leads to a kernel panic.
Tested the same with 17.10 (4.13 kernel) and 18.10 (4.18 kernel) and no 
problems with those.

The issue was first mentioned in our forum
(https://forum.proxmox.com/threads/kernel-panic-
ip_set_hash_net.50138/#post-234532) on our own kernel that's based on
the Ubuntu 4.15. After further investigations neither Debian 9 (4.9
kernel) nor Arch Linux (4.20 kernel) exhibited that same issue.

The attached log has the errors of one run of the ipset-nuclear script.
The kernel panic on the host side can also be triggered from an unprivileged 
container (Arch Linux, LXC)

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

** Attachment added: "ipset-nuclear-panic.log"
   
https://bugs.launchpad.net/bugs/1811394/+attachment/5228466/+files/ipset-nuclear-panic.log

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

Title:
  ipset kernel error: 4.15.0-43-generic

Status in linux package in Ubuntu:
  New

Bug description:
  When running the following script: 
https://github.com/DevelopersPL/pkgbuild/blob/master/ipset-nuclear/ipset-nuclear
 on the 4.15.0-43-generic kernel it leads to a kernel panic.
  Tested the same with 17.10 (4.13 kernel) and 18.10 (4.18 kernel) and no 
problems with those.

  The issue was first mentioned in our forum
  (https://forum.proxmox.com/threads/kernel-panic-
  ip_set_hash_net.50138/#post-234532) on our own kernel that's based on
  the Ubuntu 4.15. After further investigations neither Debian 9 (4.9
  kernel) nor Arch Linux (4.20 kernel) exhibited that same issue.

  The attached log has the errors of one run of the ipset-nuclear script.
  The kernel panic on the host side can also be triggered from an unprivileged 
container (Arch Linux, LXC)

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

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


[Kernel-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

2019-01-11 Thread Sofus Albertsen
Confirm solved for kernel 4.20 via Ukuu for Asus Zenbook ux433f

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+subscriptions

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


[Kernel-packages] [Bug 1808729] Re: MAC address pass through on RTL8153-BND for docking station

2019-01-11 Thread Andy Whitcroft
** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

** Also affects: linux (Ubuntu Disco)
   Importance: Undecided
 Assignee: AceLan Kao (acelankao)
   Status: Fix Committed

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

Title:
  MAC address pass through on RTL8153-BND for docking station

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  New
Status in linux source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  A new chip RTL8153-BND on docks require to be added to the whitelist to 
support MAC address pass through.

  [Fix]
  This commit adds check for RTL8153-BND chip which is in v4.20.
  9c27369f4a13 r8152: Add support for MAC address pass through on RTL8153-BND

  [Regression Potential]
  Low. It doesn't change the code flow for the old RTL8153-AD chip, so it won't 
lead to regression.

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

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


[Kernel-packages] [Bug 1775065] Re: No brightness controls and /sys/class/backlight empty after upgrade to Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter acpi_osi= is a workaround)

2019-01-11 Thread PKRakesh
Sorry,

The grub file is:

# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="nomodeset quiet splash acpi_backlight=video 
acpi_osi=Linux"
GRUB_CMDLINE_LINUX=""

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"

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

Title:
  No brightness controls and /sys/class/backlight empty after upgrade to
  Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter
  acpi_osi= is a workaround)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a case of "Backlight control does not work, and there are no
  entries in /sys/class/backlight" for what lspci reports as "NVIDIA
  Corporation GP106M [GeForce GTX 1060 Mobile] (rev a1)" where the
  kernel parameter acpi_osi= is a workaround.  (The workaround is also
  recorded on Ask Ubuntu at https://askubuntu.com/questions/1030526
  /brightness-on-laptop-msi-gt72vr-in-ubuntu-18-04-with-nvidia-gtx-1060
  -mobile-does/1043598#1043598.)

  The problem is new for me after upgrade to Bionic, although the cause
  might be the corresponding update to the NVIDIA drivers.

  I will add attachments following the instructions at
  https://wiki.ubuntu.com/Kernel/Debugging/Backlight, though most of
  them seem to be uninteresting.  If I can provide further information,
  please let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun  4 14:20:34 2018
  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-06-04 (0 days ago)
  --- 
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bgarvin2442 F pulseaudio
   /dev/snd/controlC0:  bgarvin2442 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=1b60cccb-eea7-4d0b-a32b-97d236a5177f
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b5a7 Chicony Electronics Co., Ltd 
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System76, Inc. Oryx Pro
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=557ebdfc-3380-4721-a494-65c34cb70b2f ro i8042.nomux i8042.reset 
acpi_osi=
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-06-04 (1 days ago)
  UserGroups: adm lpadmin sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 09/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.03RSA
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76, Inc.
  dmi.board.version: oryp2
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 

[Kernel-packages] [Bug 1798583] Re: the new Steam Controller driver breaks it on Steam

2019-01-11 Thread Andy Whitcroft
** Also affects: linux (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Disco)
   Importance: Medium
   Status: Fix Released

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

Title:
  the new Steam Controller driver breaks it on Steam

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Cosmic:
  New
Status in linux source package in Disco:
  Fix Released

Bug description:
  ===SRU Justification===
  [Impact]
  New steam-hid driver breaks Unity games.

  [Fix]
  Quote from the commit message:
  "With this commit, when a HID client starts, the input device is removed;
  when the HID client ends the input device is recreated."

  [Test]
  A guy from Valve comfirms the backport works.

  [Regression Potential]
  Low. This fix is specific to hid-steam, which is a new driver introduced
  in v4.18.

  ===Original Bug Report===
  The new hid_steam driver in kernel 4.18 breaks the use of it within Steam.

  Games either:
  - Crash
  - Don't detect it at all
  - Only pick it up as player 2

  To get it working as normal, it needs blacklisting currently.

  See here: https://www.gamingonlinux.com/articles/the-steam-controller-
  on-ubuntu-1810-and-other-distributions-using-linux-kernel-418-needs-
  quick-a-fix.12775

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  liam   2492 F pulseaudio
   /dev/snd/controlC0:  liam   2492 F pulseaudio
   /dev/snd/controlC1:  liam   2492 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 18 12:49:44 2018
  InstallationDate: Installed on 2017-10-18 (364 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
  IwConfig:
   lono wireless extensions.

   enp5s0no wireless extensions.

   eno1  no wireless extensions.
  MachineType: ASUS All Series
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=2a8676f3-0045-4e66-9cd1-186ffc6a8c2a ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-10-18 (0 days ago)
  dmi.bios.date: 08/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1901
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH X99
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: PCS
  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.:bvr1901:bd08/10/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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


[Kernel-packages] [Bug 1775065] Re: No brightness controls and /sys/class/backlight empty after upgrade to Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter acpi_osi= is a workaround)

2019-01-11 Thread PKRakesh
I have bought a new laptop and downloaded the latest LTS version of
Ubuntu. When I tried to install the dual boot for the first time, it
failed, then after adding "nomodeset" to the grub menu I managed to
install the same. But after installation there is no gui brightness
control as well as the brightness button is not working. I tried a lot
of methods to fix this, but none worked. Bellow is my system info:

System:Host: pkrakesh-HP-Pavilion-Gaming-Laptop-15-cx0xxx Kernel: 
4.15.0-43-generic x86_64
   bits: 64 gcc: 7.3.0
   Desktop: Gnome 3.28.2 (Gtk 3.22.30-1ubuntu1) dm: gdm3
   Distro: Ubuntu 18.04.1 LTS
Machine:   Device: laptop System: HP product: HP Pavilion Gaming Laptop 
15-cx0xxx v: Type1ProductConfigId serial: N/A
   Mobo: HP model: 8478 v: 70.39 serial: N/A
   UEFI: Insyde v: F.11 date: 08/13/2018
   Chassis: type: 10 serial: N/A
BatteryBAT1: charge: 48.7 Wh 96.0% condition: 50.8/52.8 Wh (96%)
   volts: 13.2/11.6
   model: Hewlett-Packard PABAS0241231 serial: 41167 status: Charging
CPU:   Quad core Intel Core i5-8300H (-MT-MCP-) arch: Skylake rev.10
   speed/max: 900/4000 MHz
Graphics:  Card-1: Intel Device 3e9b bus-ID: 00:02.0 chip-ID: 8086:3e9b
   Card-2: NVIDIA GP107M [GeForce GTX 1050 Mobile]
   bus-ID: 01:00.0 chip-ID: 10de:1c8d
   Display Server: x11 (X.Org 1.19.6 )
   drivers: fbdev (unloaded: modesetting,vesa)
   Resolution: 1920x1080@77.00hz
   OpenGL: renderer: llvmpipe (LLVM 6.0, 256 bits)
   version: 3.3 Mesa 18.0.5 (compat-v: 3.0) Direct Render: Yes
Network:   Card-1: Intel Device a370
   driver: iwlwifi bus-ID: 00:14.3 chip-ID: 8086:a370
   Card-2: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller
   driver: r8169 v: 2.3LK-NAPI port: 3000
   bus-ID: 03:00.0 chip-ID: 10ec:8168
Drives:HDD Total Size: 1000.2GB (0.8% used)
Info:  Processes: 309 Uptime: 20 min Memory: 1738.6/7865.9MB
   Init: systemd v: 237 runlevel: 5 Gcc sys: N/A
   Client: Shell (bash 4.4.191 running in gnome-terminal-) inxi: 2.3.56 
-

And my grub looks likes this:

System:Host: pkrakesh-HP-Pavilion-Gaming-Laptop-15-cx0xxx Kernel: 
4.15.0-43-generic x86_64
   bits: 64 gcc: 7.3.0
   Desktop: Gnome 3.28.2 (Gtk 3.22.30-1ubuntu1) dm: gdm3
   Distro: Ubuntu 18.04.1 LTS
Machine:   Device: laptop System: HP product: HP Pavilion Gaming Laptop 
15-cx0xxx v: Type1ProductConfigId serial: N/A
   Mobo: HP model: 8478 v: 70.39 serial: N/A
   UEFI: Insyde v: F.11 date: 08/13/2018
   Chassis: type: 10 serial: N/A
BatteryBAT1: charge: 48.7 Wh 96.0% condition: 50.8/52.8 Wh (96%)
   volts: 13.2/11.6
   model: Hewlett-Packard PABAS0241231 serial: 41167 status: Charging
CPU:   Quad core Intel Core i5-8300H (-MT-MCP-) arch: Skylake rev.10
   speed/max: 900/4000 MHz
Graphics:  Card-1: Intel Device 3e9b bus-ID: 00:02.0 chip-ID: 8086:3e9b
   Card-2: NVIDIA GP107M [GeForce GTX 1050 Mobile]
   bus-ID: 01:00.0 chip-ID: 10de:1c8d
   Display Server: x11 (X.Org 1.19.6 )
   drivers: fbdev (unloaded: modesetting,vesa)
   Resolution: 1920x1080@77.00hz
   OpenGL: renderer: llvmpipe (LLVM 6.0, 256 bits)
   version: 3.3 Mesa 18.0.5 (compat-v: 3.0) Direct Render: Yes
Network:   Card-1: Intel Device a370
   driver: iwlwifi bus-ID: 00:14.3 chip-ID: 8086:a370
   Card-2: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller
   driver: r8169 v: 2.3LK-NAPI port: 3000
   bus-ID: 03:00.0 chip-ID: 10ec:8168
Drives:HDD Total Size: 1000.2GB (0.8% used)
Info:  Processes: 309 Uptime: 20 min Memory: 1738.6/7865.9MB
   Init: systemd v: 237 runlevel: 5 Gcc sys: N/A
   Client: Shell (bash 4.4.191 running in gnome-terminal-) inxi: 2.3.56 

If there is any way to fix this, it'll be great. 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/1775065

Title:
  No brightness controls and /sys/class/backlight empty after upgrade to
  Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter
  acpi_osi= is a workaround)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a case of "Backlight control does not work, and there are no
  entries in /sys/class/backlight" for what lspci reports as "NVIDIA
  Corporation GP106M [GeForce GTX 1060 Mobile] (rev a1)" where the
  kernel parameter acpi_osi= is a workaround.  (The workaround is also
  recorded on Ask Ubuntu at https://askubuntu.com/questions/1030526
  /brightness-on-laptop-msi-gt72vr-in-ubuntu-18-04-with-nvidia-gtx-1060
  -mobile-does/1043598#1043598.)

  The problem is new for me after upgrade to Bionic, although the cause
  

[Kernel-packages] [Bug 1810998] Re: CPU hard lockup with rigorous writes to NVMe drive

2019-01-11 Thread Mauricio Faria de Oliveira
Patch v2 series posted to the kernel-team mailing list:

[SRU B][PATCH v2 0/7] blk-wbt: fix for LP#1810998
https://lists.ubuntu.com/archives/kernel-team/2019-January/097831.html

[SRU C][PATCH v2 0/6] blk-wbt: fix for LP#1810998
https://lists.ubuntu.com/archives/kernel-team/2019-January/097840.html

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

Title:
  CPU hard lockup with rigorous writes to NVMe drive

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

Bug description:
  [Impact]

   * Users may experience cpu hard lockups when performing
     rigorous writes to NVMe drives.

   * The fix addresses an scheduling issue in the original
     implementation of wbt/writeback throttling

   * The fix is commit 2887e41b910b ("blk-wbt: Avoid lock
     contention and thundering herd issue in wbt_wait"),
     plus its fix commit 38cfb5a45ee0 ("blk-wbt: improve
     waking of tasks").

   * Plus a few dependency commits for each fix.

   * Backports are trivial: mainly replace rq_wait_inc_below()
     with the equivalent atomic_inc_below(), and maintain the
     __wbt_done() signature, both due to the lack of commit
     a79050434b45 ("blk-rq-qos: refactor out common elements
     of blk-wbt"), that changes lots of other/unrelated code.

  [Test Case]

   * This command has been reported to reproduce the problem:

     $ sudo iozone -R -s 5G -r 1m -S 2048 -i 0 -G -c -o -l 128 -u 128 -t
  128

   * It generates stack traces as below in the original kernel,
     and does not generate them in the modified/patched kernel.

   * The user/reporter verified the test kernel with these patches
     resolved the problem.

   * The developer verified in 2 systems (4-core and 24-core but
     no NVMe) for regressions, and no error messages were logged
     to dmesg.

  [Regression Potential]

   * The regression potential is contained within writeback
     throttling mechanism (block/blk-wbt.*).

   * The commits have been verified for fixes in later commits in
     linux-next as of 2019-01-08 and all known fix commits are in.

  [Other Info]

   * The problem has been introduced with the blk-wbt mechanism,
     in v4.10-rc1, and the fix commits in v4.19-rc1 and -rc2,
     so only Bionic and Cosmic needs this.

  [Stack Traces]

  [ 393.628647] NMI watchdog: Watchdog detected hard LOCKUP on cpu 30
  ...
  [ 393.628704] CPU: 30 PID: 0 Comm: swapper/30 Tainted: P OE 4.15.0-20-generic 
#21-Ubuntu
  ...
  [ 393.628720] Call Trace:
  [ 393.628721] 
  [ 393.628724] enqueue_task_fair+0x6c/0x7f0
  [ 393.628726] ? __update_load_avg_blocked_se.isra.37+0xd1/0x150
  [ 393.628728] ? __update_load_avg_blocked_se.isra.37+0xd1/0x150
  [ 393.628731] activate_task+0x57/0xc0
  [ 393.628735] ? sched_clock+0x9/0x10
  [ 393.628736] ? sched_clock+0x9/0x10
  [ 393.628738] ttwu_do_activate+0x49/0x90
  [ 393.628739] try_to_wake_up+0x1df/0x490
  [ 393.628741] default_wake_function+0x12/0x20
  [ 393.628743] autoremove_wake_function+0x12/0x40
  [ 393.628744] __wake_up_common+0x73/0x130
  [ 393.628745] __wake_up_common_lock+0x80/0xc0
  [ 393.628746] __wake_up+0x13/0x20
  [ 393.628749] __wbt_done.part.21+0xa4/0xb0
  [ 393.628749] wbt_done+0x72/0xa0
  [ 393.628753] blk_mq_free_request+0xca/0x1a0
  [ 393.628755] blk_mq_end_request+0x48/0x90
  [ 393.628760] nvme_complete_rq+0x23/0x120 [nvme_core]
  [ 393.628763] nvme_pci_complete_rq+0x7a/0x130 [nvme]
  [ 393.628764] __blk_mq_complete_request+0xd2/0x140
  [ 393.628766] blk_mq_complete_request+0x18/0x20
  [ 393.628767] nvme_process_cq+0xe1/0x1b0 [nvme]
  [ 393.628768] nvme_irq+0x23/0x50 [nvme]
  [ 393.628772] __handle_irq_event_percpu+0x44/0x1a0
  [ 393.628773] handle_irq_event_percpu+0x32/0x80
  [ 393.628774] handle_irq_event+0x3b/0x60
  [ 393.628778] handle_edge_irq+0x7c/0x190
  [ 393.628779] handle_irq+0x20/0x30
  [ 393.628783] do_IRQ+0x46/0xd0
  [ 393.628784] common_interrupt+0x84/0x84
  [ 393.628785] 
  ...
  [ 393.628794] ? cpuidle_enter_state+0x97/0x2f0
  [ 393.628796] cpuidle_enter+0x17/0x20
  [ 393.628797] call_cpuidle+0x23/0x40
  [ 393.628798] do_idle+0x18c/0x1f0
  [ 393.628799] cpu_startup_entry+0x73/0x80
  [ 393.628802] start_secondary+0x1a6/0x200
  [ 393.628804] secondary_startup_64+0xa5/0xb0
  [ 393.628805] Code: ...

  [ 405.981597] nvme nvme1: I/O 393 QID 6 timeout, completion polled

  [ 435.597209] INFO: rcu_sched detected stalls on CPUs/tasks:
  [ 435.602858] 30-...0: (1 GPs behind) idle=e26/1/0 softirq=6834/6834 fqs=4485
  [ 435.610203] (detected by 8, t=15005 jiffies, g=6396, c=6395, q=146818)
  [ 435.617025] Sending NMI from CPU 8 to CPUs 30:
  [ 435.617029] NMI backtrace for cpu 30
  [ 435.617031] CPU: 30 PID: 0 Comm: swapper/30 Tainted: P OE 4.15.0-20-generic 
#21-Ubuntu
  ...
  [ 435.617047] Call Trace:
  [ 435.617048] 
  [ 435.617051] enqueue_entity+0x9f/0x6b0
  [ 435.617053] 

[Kernel-packages] [Bug 1811236] Re: System wakes from suspend without user initialization

2019-01-11 Thread Janne Jokitalo
An update on the matter, I went through this awesome page [0] regarding
debugging suspend/resume issues, and this particular instruction seems
to have removed the unwanted resume problem in my case:

root@caolila:~# cat /proc/acpi/wakeup
Device  S-state   Status   Sysfs node
...
XHC   S3*enabled   pci::00:14.0
...

root@caolila:~# echo XHC > /proc/acpi/wakeup

root@caolila:~# cat /proc/acpi/wakeup 
Device  S-state   Status   Sysfs node
...
XHC   S3*disabled  pci::00:14.0
...

In other words, disabling USB 3.0 devices' capabilities of resuming the
system keeps the laptop at sleep successfully.

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

Title:
  System wakes from suspend without user initialization

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use `systemctl suspend` for taking my laptop to sleep. Suspend seems
  to work fine, but after a random amount of time, the system resumes
  without me pressing any buttons, moving a mouse etc.

  Some other methods have been attempted, but all end up with the same
  result, ie. system resumes unwanted.

  Here is a /var/log/syslog excerpt, hope I managed to grab everything
  valuable. The bug was filed with `ubuntu-bug linux-
  image-4.18.0-13-generic`, which is the linux image currently in use.
  Please let me know if something is missing due to incorrect package
  selection or otherwise.

  ---

  Jan 10 13:48:35 caolila NetworkManager[869]:   [1547120915.3067] 
manager: sleep: sleep requested (sleeping: no  enabled: yes)
  Jan 10 13:48:35 caolila NetworkManager[869]:   [1547120915.3069] device 
(enp0s20f0u2c2): state change: unavailable -> unmanaged (reason 'sleeping', 
sys-iface-state: 'managed')
  Jan 10 13:48:35 caolila NetworkManager[869]:   [1547120915.3126] device 
(wlp0s20f3): state change: disconnected -> unmanaged (reason 'sleeping', 
sys-iface-state: 'managed')
  Jan 10 13:48:35 caolila NetworkManager[869]:   [1547120915.3415] device 
(enp0s20f0u4): state change: disconnected -> unmanaged (reason 'sleeping', 
sys-iface-state: 'managed')
  Jan 10 13:48:35 caolila NetworkManager[869]:   [1547120915.3453] 
manager: NetworkManager state is now ASLEEP
  Jan 10 13:48:35 caolila systemd[1]: Reached target Sleep.
  Jan 10 13:48:35 caolila systemd[1]: Starting Suspend...
  Jan 10 13:48:35 caolila whoopsie[1352]: [13:48:35] offline
  Jan 10 13:48:35 caolila systemd-sleep[32606]: Suspending system...
  Jan 10 13:48:35 caolila kernel: [19604.933999] PM: suspend entry (deep)
  Jan 10 13:48:35 caolila kernel: [19604.934001] PM: Syncing filesystems ... 
done.
  Jan 10 13:48:35 caolila wpa_supplicant[868]: nl80211: deinit ifname=wlp0s20f3 
disabled_11b_rates=0
  Jan 10 13:53:55 caolila kernel: [19607.067269] Freezing user space processes 
... (elapsed 0.004 seconds) done.
  Jan 10 13:53:55 caolila kernel: [19607.071592] OOM killer disabled.
  Jan 10 13:53:55 caolila kernel: [19607.071593] Freezing remaining freezable 
tasks ... (elapsed 0.001 seconds) done.
  Jan 10 13:53:55 caolila kernel: [19607.072971] Suspending console(s) (use 
no_console_suspend to debug)
  Jan 10 13:53:55 caolila kernel: [19607.160541] e1000e: EEE TX LPI TIMER: 
0011
  Jan 10 13:53:55 caolila kernel: [19607.502557] thunderbolt :07:00.0: 
stopping RX ring 0
  Jan 10 13:53:55 caolila kernel: [19607.502575] thunderbolt :07:00.0: 
disabling interrupt at register 0x38200 bit 12 (0x1001 -> 0x1)
  Jan 10 13:53:55 caolila kernel: [19607.502581] thunderbolt :07:00.0: 
stopping TX ring 0
  Jan 10 13:53:55 caolila kernel: [19607.502605] thunderbolt :07:00.0: 
disabling interrupt at register 0x38200 bit 0 (0x1 -> 0x0)
  Jan 10 13:53:55 caolila kernel: [19607.502608] thunderbolt :07:00.0: 
control channel stopped
  Jan 10 13:53:55 caolila kernel: [19607.502808] ACPI: EC: interrupt blocked
  Jan 10 13:53:55 caolila kernel: [19607.684603] ACPI: Preparing to enter 
system sleep state S3
  Jan 10 13:53:55 caolila kernel: [19607.688265] ACPI: EC: event blocked
  Jan 10 13:53:55 caolila kernel: [19607.688267] ACPI: EC: EC stopped
  Jan 10 13:53:55 caolila kernel: [19607.688268] PM: Saving platform NVS memory
  Jan 10 13:53:55 caolila kernel: [19607.688301] Disabling non-boot CPUs ...
  Jan 10 13:53:55 caolila kernel: [19607.704406] IRQ 122: no longer affine to 
CPU1
  Jan 10 13:53:55 caolila kernel: [19607.704426] IRQ 187: no longer affine to 
CPU1
  Jan 10 13:53:55 caolila kernel: [19607.705447] smpboot: CPU 1 is now offline
  Jan 10 13:53:55 caolila kernel: [19607.728394] IRQ 189: no longer affine to 
CPU2
  Jan 10 13:53:55 caolila kernel: [19607.729415] smpboot: CPU 2 is now offline
  Jan 10 13:53:55 caolila kernel: [19607.752349] IRQ 177: no longer affine to 
CPU3
  Jan 10 13:53:55 caolila kernel: [19607.753377] smpboot: CPU 3 is now offline
  Jan 10 13:53:55 caolila kernel: [19607.780410] IRQ 179: no longer affine to 

[Kernel-packages] [Bug 1811337] Re: To reduce the Realtek USB cardreader power consumption

2019-01-11 Thread Kleber Sacilotto de Souza
** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Changed in: linux (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

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

Title:
  To reduce the Realtek USB cardreader power consumption

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  Fix Committed
Status in linux-oem source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  In Progress
Status in linux-oem source package in Disco:
  Invalid

Bug description:
  [Impact]
  Realtek USB cardreader consumes more than 1 Watt during long idle if it's not 
suspended. And it's runtime PM functions are available after v4.20.

  [Fix]
  To avoid conflicts, have to backport some patches for mmc core.

  [Test]
  Note: Inside () are the previous value (non-patch)
  Sort idle: 7.76W (7.88)
  Long idle: 4.658W (5.79)
  S3: 0.5W (0.5)
  S5: 0.20W (0.208)

  [Regression Potential]
  Low, most commits are for rtsx_usb_{sdmmc,ms} and are all small changes.

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

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


[Kernel-packages] [Bug 1811337] Re: To reduce the Realtek USB cardreader power consumption

2019-01-11 Thread Kleber Sacilotto de Souza
** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

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

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

** Also affects: linux (Ubuntu Disco)
   Importance: Undecided
 Assignee: AceLan Kao (acelankao)
   Status: In Progress

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

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

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

** Changed in: linux-oem (Ubuntu Cosmic)
   Status: New => Invalid

** Changed in: linux-oem (Ubuntu Disco)
   Status: New => Opinion

** Changed in: linux-oem (Ubuntu Disco)
   Status: Opinion => Invalid

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

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

Title:
  To reduce the Realtek USB cardreader power consumption

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux-oem source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress
Status in linux-oem source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  In Progress
Status in linux-oem source package in Disco:
  Invalid

Bug description:
  [Impact]
  Realtek USB cardreader consumes more than 1 Watt during long idle if it's not 
suspended. And it's runtime PM functions are available after v4.20.

  [Fix]
  To avoid conflicts, have to backport some patches for mmc core.

  [Test]
  Note: Inside () are the previous value (non-patch)
  Sort idle: 7.76W (7.88)
  Long idle: 4.658W (5.79)
  S3: 0.5W (0.5)
  S5: 0.20W (0.208)

  [Regression Potential]
  Low, most commits are for rtsx_usb_{sdmmc,ms} and are all small changes.

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

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


[Kernel-packages] [Bug 1806488] Re: Support non-strict iommu mode on arm64

2019-01-11 Thread Kleber Sacilotto de Souza
** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

Title:
  Support non-strict iommu mode on arm64

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

Bug description:
  [Impact]
  The Intel IOMMU driver provides an option for strict mode. When disabled, 
batching of IOTLB flush operations is permitted, allowing the user to trade-off 
isolation for improved performance. Ubuntu's kernel currently lacks a parity 
for this feature for ARM.

  There's a significant performance gain to be had by removing the need
  to flush the IOMMU TLB on every unmap on arm64. I'm seeing a 25%
  performance gain w/ fio reads on a single NVMe device.

  This mode of operation is available for x86 via the
  "intel_iommu=strict" parameter. Upstream now exposes an equivalent
  feature for ARM platforms via the "iommu.strict=[0|1]" parameter,
  while retaining the default strict-enabled mode.

  [Test Case]
  $ cat fio.rc
  [global]
  rw=read
  direct=1
  ioengine=libaio
  iodepth=2048
  numjobs=10
  bs=4k
  group_reporting=1
  group_reporting=1
  cpumask=0xff
  runtime=100
  loops = 1

  [job1]
  filename=/dev/nvme0n1

  [Fix]
  44f6876a00e83 iommu/arm-smmu: Support non-strict mode
  b2dfeba654cb0 iommu/io-pgtable-arm-v7s: Add support for non-strict mode
  9662b99a19abc iommu/arm-smmu-v3: Add support for non-strict mode
  b6b65ca20bc93 iommu/io-pgtable-arm: Add support for non-strict mode
  68a6efe86f6a1 iommu: Add "iommu.strict" command line option
  2da274cdf998a iommu/dma: Add support for non-strict mode
  07fdef34d2be6 iommu/arm-smmu-v3: Implement flush_iotlb_all hook
  85c7a0f1ef624 iommu/io-pgtable-arm: Fix race handling in split_blk_unmap()

  [Regression Risk]
  Most of these patches are specific to ARM, and have been regression tested on 
both arm64 (HiSilicon D06) and armhf (QEMU virt) using "stress-ng --vm $(nproc)"

  2 patches do touch arch-indep code however:

  > 68a6efe86f6a1 iommu: Add "iommu.strict" command line option
  Adds a new command line option and sets an attribute that iommu drivers can 
optionally react to. Doesn't change default behavior.

  > 2da274cdf998a iommu/dma: Add support for non-strict mode
  This driver is only built for arm64 and ppc64el (determined by looking at the 
build logs). Most of this patch only changes behavior in the non-default (and 
new) iommu.strict=0 case. The exception, which is called out in the commit 
message, is this hunk:

  -   WARN_ON(iommu_unmap(domain, dma_addr, size) != size);
  +   WARN_ON(iommu_unmap_fast(domain, dma_addr, size) != size);
  +   if (!cookie->fq_domain)
  +   iommu_tlb_sync(domain);

  
  In the default case, where fq_domain will be NULl, we are now factoring 
iommu_unmap() into:
iommu_unmap_fast()
iommu_tlb_sync()

  Looking at the source to iommu_unmap() confirms that this is
  functionally equivalent.

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

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


[Kernel-packages] [Bug 1806488] Re: Support non-strict iommu mode on arm64

2019-01-11 Thread Kleber Sacilotto de Souza
** Changed in: linux (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

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

Title:
  Support non-strict iommu mode on arm64

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

Bug description:
  [Impact]
  The Intel IOMMU driver provides an option for strict mode. When disabled, 
batching of IOTLB flush operations is permitted, allowing the user to trade-off 
isolation for improved performance. Ubuntu's kernel currently lacks a parity 
for this feature for ARM.

  There's a significant performance gain to be had by removing the need
  to flush the IOMMU TLB on every unmap on arm64. I'm seeing a 25%
  performance gain w/ fio reads on a single NVMe device.

  This mode of operation is available for x86 via the
  "intel_iommu=strict" parameter. Upstream now exposes an equivalent
  feature for ARM platforms via the "iommu.strict=[0|1]" parameter,
  while retaining the default strict-enabled mode.

  [Test Case]
  $ cat fio.rc
  [global]
  rw=read
  direct=1
  ioengine=libaio
  iodepth=2048
  numjobs=10
  bs=4k
  group_reporting=1
  group_reporting=1
  cpumask=0xff
  runtime=100
  loops = 1

  [job1]
  filename=/dev/nvme0n1

  [Fix]
  44f6876a00e83 iommu/arm-smmu: Support non-strict mode
  b2dfeba654cb0 iommu/io-pgtable-arm-v7s: Add support for non-strict mode
  9662b99a19abc iommu/arm-smmu-v3: Add support for non-strict mode
  b6b65ca20bc93 iommu/io-pgtable-arm: Add support for non-strict mode
  68a6efe86f6a1 iommu: Add "iommu.strict" command line option
  2da274cdf998a iommu/dma: Add support for non-strict mode
  07fdef34d2be6 iommu/arm-smmu-v3: Implement flush_iotlb_all hook
  85c7a0f1ef624 iommu/io-pgtable-arm: Fix race handling in split_blk_unmap()

  [Regression Risk]
  Most of these patches are specific to ARM, and have been regression tested on 
both arm64 (HiSilicon D06) and armhf (QEMU virt) using "stress-ng --vm $(nproc)"

  2 patches do touch arch-indep code however:

  > 68a6efe86f6a1 iommu: Add "iommu.strict" command line option
  Adds a new command line option and sets an attribute that iommu drivers can 
optionally react to. Doesn't change default behavior.

  > 2da274cdf998a iommu/dma: Add support for non-strict mode
  This driver is only built for arm64 and ppc64el (determined by looking at the 
build logs). Most of this patch only changes behavior in the non-default (and 
new) iommu.strict=0 case. The exception, which is called out in the commit 
message, is this hunk:

  -   WARN_ON(iommu_unmap(domain, dma_addr, size) != size);
  +   WARN_ON(iommu_unmap_fast(domain, dma_addr, size) != size);
  +   if (!cookie->fq_domain)
  +   iommu_tlb_sync(domain);

  
  In the default case, where fq_domain will be NULl, we are now factoring 
iommu_unmap() into:
iommu_unmap_fast()
iommu_tlb_sync()

  Looking at the source to iommu_unmap() confirms that this is
  functionally equivalent.

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

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


[Kernel-packages] [Bug 1801102] Re: Bionic shows incorrect warning about number of pointers in TFD

2019-01-11 Thread Stefan Bader
** Summary changed:

- Please include this patch in bionic kernel 
https://www.spinics.net/lists/linux-wireless/msg169994.html
+ Bionic shows incorrect warning about number of pointers in TFD

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

Title:
  Bionic shows incorrect warning about number of pointers in TFD

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  ===SRU Justification===
  [Impact]
  iwlwifi spews "Too many chunks: 20" in dmesg.

  [Fix] 
  From the patch description:
  "
  When we free the TFD, we check its number of valid pointers
  and make sure it doesn't exceed the number of pointers the
  hardware support.
  This check had an off by one bug: it is perfectly valid to
  free the 20 pointers if the TFD has 20 pointers.
  "

  [Test]
  User confirms the patch solves the problem.

  [Regression Potential]
  Low. The fix is limited to iwlwifi, and the patch is in mainline for a
  while.

  ===Original Bug Report===
  Hi:

  I am having the same issue i.e. when downloading torrent with
  KTorrent. Please include this fix https://www.spinics.net/lists/linux-
  wireless/msg169994.html in the release kernel.

  Thanks

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

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


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

2019-01-11 Thread Shirish S
Kai-Heng,

Am able to see "xHCI host controller not responding, assume dead" pretty
much regularly during suspend/resume.

I verified that the kernel am using has patches mentioned in
https://patchwork.ozlabs.org/project/ubuntu-kernel/list/?series=53395
and am using amd platform.

I also have iommu disabled.  Impact being system hangs for a while,
watchdog kicks in and reboot.

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

Title:
  xhci hangs; reset results in NULL pointer dereference

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Confirmed
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux package in Arch Linux:
  New

Bug description:
  ===SRU Justification===
  [Impact]
  xHC stops to work after some time. This happens when the xHC gets
  runtime resumed/suspended constantly.

  [Test]
  User reports this backport fixes the issue.

  [Fix]
  In addition to check EINT, also check ports' status.

  [Regression Potential]
  Low. It fixes a known bug and it's in -stable.

  ===Original Bug Report===

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

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

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

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

  But doing this today resulted in a kernel bug:

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

  1   2   >