[Kernel-packages] [Bug 1827417] Re: Ubuntu 16.04 - EMU10K1 / CT4832 lost ability to listen stereo on headphones - there is upmixed surround only.

2019-09-12 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/1827417

Title:
  Ubuntu 16.04 -  EMU10K1 / CT4832 lost ability to listen stereo on
  headphones -  there is upmixed  surround only.

Status in linux package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Hello,

  I have a problem - after one of the updates (sorry for being not precise - I 
can only track it back to the time I have been surely listening something on 
headphones - it has to be beginning of this year because last time I have been 
listening more on my SB Live for sure was in last one-two weeks of February 
2019 - I have suddenly lost "stereo" on my headphones.
  I have speakers connected to on-board sound card and headphones connected to 
SB Live Value for few years, so I did not mess with outputs or something - one 
day I changed Audacious output to SbLive in pavucontrol (as usually) and that 
time the sound was weirdly filtered.
  I have found that this must be "surround upmix" which I do not need and tried 
to disable it,
  enable-remixing = no and the same for "LFE remixing" in 
/etc/pulse/daemon.conf did not work.
  It does not matter what configuration I choose in pavucontrol- analog stereo 
duplex, "analog stereo output", "Analog surround 5.1" or 4.1 - for all "Analog 
output" scenarios the output is the same except for "mono" (no sound at all).
  I have tried do "skip" pulseaudio choosing "ALSA" output in Audacious + the 
alsa configuration for stereo but the upmix is still present.

  I have followed the old thread in Launchpad Answers:
  https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/169428
  =
  Hello,

  i'm on ubuntu 16.04LTS (AMD64, with emu10k1 based soundcard) and since the 
last update I have similar problem - I have lost ability to listen stereo music 
on my Soundblaster Live Value (i use earphones).
  Even system sounds , web browser content and mp3 files are up-mixed.
  Few days ago it was no problem to choose "analag stereo output" in 
pavucontrol, now it seems that at this output have rear surround channel only 
(as I suppose, there is "stereo" but vocals are like heard from the other room 
and there is sometimes reverb as in the bathroom) :/.
  I had tried adding "set enable-remixing=no" in both /etc/pulse/daemon.conf 
and in the home directory configuration file without success.
  I have purged pulseaudio but with the ALSA there is the same problem, I have 
tried purging alsa and reinstalling without effect.
  So i thought that it can be emu10k1 driver specific, after digging in the 
network for solutions I have had tried adding 
"hint.emu10kx.0.multichannel_disabled " to the module configuration file 
without visible (or rather soundible ;) effect.
  I have tried to check EMU10K1 configuration with aweset, but it gives error 
message, so maybe the bad magic sits somewhere around?

  aweset
  /dev/sequencer: No such file or directory

  Once again - everything worked fine until the last update. I use
  xubuntu desktop as my machine is quite old, in despair I have
  installed unity to find the sound settings / speaker configuration etc
  and button to "disable all effects" as I have seen somewhere, but
  there were no such options.

  Help me Obi Wan Kenobi, you're my only hope...
  =

  I have next tried to follow the path from ubuntu sound troubleshooting
  guide, I have purged everything, installed back and now I'm  here
  again with this "upmix" on SBLive! Value.

  Thanks in advance for help :)
  Tom
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=654027ee-6ab0-41ba-8537-452da07cda0e
  InstallationDate: Installed on 2011-10-07 (2765 days ago)
  InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 
(20110720.1)
  IwConfig:
   lono wireless extensions.
   
   lxcbr0no wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. M68MT-S2
  Package: pulseaudio 1:8.0-0ubuntu3.10
  PackageArchitecture: amd64
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-146-generic 
root=UUID=4559c496-f083-41a2-ad7c-1e03334389fd ro plymouth 
usbcore.autosuspend=-1
  ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-146-generic N/A
   linux-backports-modules-4.4.0-146-generic  N/A
   linux-firmware 1.157.21
  RfKill:
   
  Tags: xenial third-party-packages xenial
  Uname: Linux 4.4.0-146-generic x86_64
  UpgradeStatus: Upgraded to 

[Kernel-packages] [Bug 1827417] Re: Ubuntu 16.04 - EMU10K1 / CT4832 lost ability to listen stereo on headphones - there is upmixed surround only.

2019-09-12 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

** Changed in: pulseaudio (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/1827417

Title:
  Ubuntu 16.04 -  EMU10K1 / CT4832 lost ability to listen stereo on
  headphones -  there is upmixed  surround only.

Status in linux package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Hello,

  I have a problem - after one of the updates (sorry for being not precise - I 
can only track it back to the time I have been surely listening something on 
headphones - it has to be beginning of this year because last time I have been 
listening more on my SB Live for sure was in last one-two weeks of February 
2019 - I have suddenly lost "stereo" on my headphones.
  I have speakers connected to on-board sound card and headphones connected to 
SB Live Value for few years, so I did not mess with outputs or something - one 
day I changed Audacious output to SbLive in pavucontrol (as usually) and that 
time the sound was weirdly filtered.
  I have found that this must be "surround upmix" which I do not need and tried 
to disable it,
  enable-remixing = no and the same for "LFE remixing" in 
/etc/pulse/daemon.conf did not work.
  It does not matter what configuration I choose in pavucontrol- analog stereo 
duplex, "analog stereo output", "Analog surround 5.1" or 4.1 - for all "Analog 
output" scenarios the output is the same except for "mono" (no sound at all).
  I have tried do "skip" pulseaudio choosing "ALSA" output in Audacious + the 
alsa configuration for stereo but the upmix is still present.

  I have followed the old thread in Launchpad Answers:
  https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/169428
  =
  Hello,

  i'm on ubuntu 16.04LTS (AMD64, with emu10k1 based soundcard) and since the 
last update I have similar problem - I have lost ability to listen stereo music 
on my Soundblaster Live Value (i use earphones).
  Even system sounds , web browser content and mp3 files are up-mixed.
  Few days ago it was no problem to choose "analag stereo output" in 
pavucontrol, now it seems that at this output have rear surround channel only 
(as I suppose, there is "stereo" but vocals are like heard from the other room 
and there is sometimes reverb as in the bathroom) :/.
  I had tried adding "set enable-remixing=no" in both /etc/pulse/daemon.conf 
and in the home directory configuration file without success.
  I have purged pulseaudio but with the ALSA there is the same problem, I have 
tried purging alsa and reinstalling without effect.
  So i thought that it can be emu10k1 driver specific, after digging in the 
network for solutions I have had tried adding 
"hint.emu10kx.0.multichannel_disabled " to the module configuration file 
without visible (or rather soundible ;) effect.
  I have tried to check EMU10K1 configuration with aweset, but it gives error 
message, so maybe the bad magic sits somewhere around?

  aweset
  /dev/sequencer: No such file or directory

  Once again - everything worked fine until the last update. I use
  xubuntu desktop as my machine is quite old, in despair I have
  installed unity to find the sound settings / speaker configuration etc
  and button to "disable all effects" as I have seen somewhere, but
  there were no such options.

  Help me Obi Wan Kenobi, you're my only hope...
  =

  I have next tried to follow the path from ubuntu sound troubleshooting
  guide, I have purged everything, installed back and now I'm  here
  again with this "upmix" on SBLive! Value.

  Thanks in advance for help :)
  Tom
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=654027ee-6ab0-41ba-8537-452da07cda0e
  InstallationDate: Installed on 2011-10-07 (2765 days ago)
  InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 
(20110720.1)
  IwConfig:
   lono wireless extensions.
   
   lxcbr0no wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. M68MT-S2
  Package: pulseaudio 1:8.0-0ubuntu3.10
  PackageArchitecture: amd64
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-146-generic 
root=UUID=4559c496-f083-41a2-ad7c-1e03334389fd ro plymouth 
usbcore.autosuspend=-1
  ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-146-generic N/A
   linux-backports-modules-4.4.0-146-generic  N/A
   linux-firmware 1.157.21
  RfKill:
   
  Tags: xenial third-party-packages xenial
  Uname: Linux 4.4.0-146-generic x86_64
  UpgradeStatus: 

[Kernel-packages] [Bug 1843860] Re: 5.3.0-10 doesn't boot on my t480s with secure boot enabled

2019-09-12 Thread Michael Hudson-Doyle
mwhudson@anduril:~$ apport-collect 1843860
dpkg-query: no packages found matching linux


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

Title:
  5.3.0-10 doesn't boot on my t480s with secure boot enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have no further information, sadly. The boot stops at the message
  "EFI stub: UEFI Secure Boot is enabled". Disabling secure boot or
  selecting an older kernel both work fine.

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

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


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

2019-09-12 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 1843860

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

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

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

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

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

Title:
  5.3.0-10 doesn't boot on my t480s with secure boot enabled

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have no further information, sadly. The boot stops at the message
  "EFI stub: UEFI Secure Boot is enabled". Disabling secure boot or
  selecting an older kernel both work fine.

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

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


[Kernel-packages] [Bug 1843860] [NEW] 5.3.0-10 doesn't boot on my t480s with secure boot enabled

2019-09-12 Thread Michael Hudson-Doyle
Public bug reported:

I have no further information, sadly. The boot stops at the message "EFI
stub: UEFI Secure Boot is enabled". Disabling secure boot or selecting
an older kernel both work fine.

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

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

Title:
  5.3.0-10 doesn't boot on my t480s with secure boot enabled

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have no further information, sadly. The boot stops at the message
  "EFI stub: UEFI Secure Boot is enabled". Disabling secure boot or
  selecting an older kernel both work fine.

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

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


[Kernel-packages] [Bug 1842799] Re: bionic/linux-raspi2: 4.15.0-1046.50 -proposed tracker

2019-09-12 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-bionic

** Tags added: block-proposed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1842828
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
- phase: Holding before Promote to Proposed
- phase-changed: Thursday, 12. September 2019 22:56 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Friday, 13. September 2019 02:00 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa main:building
+   promote-to-proposed: Pending -- ready for review
  replaces: bug 1842566
  trackers:
bionic/linux-raspi2/pi-kernel: bug 1842798
  variant: debs

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

Title:
  bionic/linux-raspi2: 4.15.0-1046.50 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842828
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Ready for Promote to Proposed
  phase-changed: Friday, 13. September 2019 02:00 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  replaces: bug 1842566
  trackers:
bionic/linux-raspi2/pi-kernel: bug 1842798
  variant: debs

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

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


[Kernel-packages] [Bug 1584479] Re: [MSI GP72 6QE Leopard Pro] acpi=off required to boot

2019-09-12 Thread oscar
Same thing MSI laptop, no apcioff required ( or it wont boot) and it
affects launchpad... Any solutions known?

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

Title:
  [MSI GP72 6QE Leopard Pro] acpi=off required to boot

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hi,
  I just install Ubuntu 16.04 on my new MSI laptop G72 6QE.
  My touchpad doesn't work and recognize at all.

  I try :
  - Fn+F3 to activate my touchpad
  - xinput list and is not listed
  - xev and nothing append (no signal)
  - cat /proc/bus/input/devices ddoesn't display touchpad (only HDMI, mic, 
headphone, external mouse and keyboard)
  - I don't know if there is a link, but some buttons of my keyboard don't work 
(like Fn+arrows to manage sound and luminosity) :
  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input0
  U: Uniq=
  H: Handlers=sysrq kbd event0 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=60070290 8380207af040d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  
  Thanks
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1305 F pulseaudio
moi1668 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=9649bbed-2d32-42cd-a446-43abaa9ab1f3
  InstallationDate: Installed on 2016-05-20 (2 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: Micro-Star International Co., Ltd. GP72 6QE
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-22-generic 
root=UUID=80432220-0bdf-49f0-a145-0c015ad36c2a ro rootflags=subvol=@ acpi=off 
acpi_osi=! acpi_backlight=native i8042.nopnp quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  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.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  Tags:  xenial
  Uname: Linux 4.4.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1795IMS.10C
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-1795
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.A
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1795IMS.10C:bd12/10/2015:svnMicro-StarInternationalCo.,Ltd.:pnGP726QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1795:rvrREV0.A:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:
  dmi.product.name: GP72 6QE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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


[Kernel-packages] [Bug 1750479] Re: 'perf record' does not work

2019-09-12 Thread Trent Lloyd
*** This bug is a duplicate of bug 1823281 ***
https://bugs.launchpad.net/bugs/1823281

** This bug has been marked a duplicate of bug 1823281
   perf-archive is not shipped in the linux-tools package

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

Title:
  'perf record' does not work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  $ perf archive
  perf: 'archive' is not a perf-command. See 'perf --help'.

  $ perf --help

   usage: perf [--version] [--help] [OPTIONS] COMMAND [ARGS]

   The most commonly used perf commands are:
 annotateRead perf.data (created by perf record) and display 
annotated code
 archive Create archive with object files with build-ids found in 
perf.data file <-
 bench   General framework for benchmark suites
 buildid-cache   Manage build-id cache.
 buildid-listList the buildids in a perf.data file
 c2c Shared Data C2C/HITM Analyzer.
 config  Get and set variables in a configuration file.
 dataData file related processing
 diffRead perf.data files and display the differential profile
 evlist  List the event names in a perf.data file
 ftrace  simple wrapper for kernel's ftrace functionality
 inject  Filter to augment the events stream with additional 
information
 kallsymsSearches running kernel for symbols
 kmemTool to trace/measure kernel memory properties
 kvm Tool to trace/measure kvm guest os
 listList all symbolic event types
 lockAnalyze lock events
 mem Profile memory accesses
 record  Run a command and record its profile into perf.data
 report  Read perf.data (created by perf record) and display the 
profile
 sched   Tool to trace/measure scheduler properties (latencies)
 script  Read perf.data (created by perf record) and display trace 
output
 statRun a command and gather performance counter statistics
 testRuns sanity tests.
 timechart   Tool to visualize total system behavior during a workload
 top System profiling tool.
 probe   Define new dynamic tracepoints
 trace   strace inspired tool

   See 'perf help COMMAND' for more information on a specific command.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-tools-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sbarcomb   2227 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 19 20:53:27 2018
  HibernationDevice: RESUME=UUID=ac3f108f-4494-4f48-ae8c-fbab8a509ffc
  InstallationDate: Installed on 2017-10-19 (123 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   tun0  no wireless extensions.
  MachineType: Alienware Aurora-R4
  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.13.0-32-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/26/2013
  dmi.bios.vendor: Alienware
  dmi.bios.version: A11
  dmi.board.name: 07JNH0
  dmi.board.vendor: Alienware
  dmi.board.version: A02
  dmi.chassis.type: 3
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: 00
  dmi.modalias: 
dmi:bvnAlienware:bvrA11:bd11/26/2013:svnAlienware:pnAurora-R4:pvr00:rvnAlienware:rn07JNH0:rvrA02:cvnAlienware:ct3:cvr00:
  dmi.product.family: 0
  dmi.product.name: Aurora-R4
  dmi.product.version: 00
  dmi.sys.vendor: Alienware

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

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


[Kernel-packages] [Bug 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes

2019-09-12 Thread Ben Bromley
Another error message from a flicker

Sep 12 20:28:01 shadeball org.gnome.Shell.desktop[5959]:
[6514:6514:0912/202801.632870:ERROR:gl_surface_presentation_helper.cc(259)]
GetVSyncParametersIfAvailable() failed for 1280 times!

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

Title:
  Dell XPS 13 9380 - Screen brightness flashes

Status in gnome-settings-daemon package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu
  edition from Dell which came with 18.04, but I've since wiped it and
  installed 19.04 from a fresh ISO download. This is the non-touch non-
  4K version (13-inch 1080p).

  Every so often (maybe a couple of times per minute), the screen
  flashes brighter, as if the brightness has been turned up momentarily
  and then back down again.

  I previously had an issue with the brightness / colours changing
  slightly when I opened menus or if the screen content changed
  slightly, but I fixed that by disabling Dynamic Brightness in the
  BIOS. It is definitely a better experience with that turned off.

  However the screen flashing still persists.

  I booted a live image of Fedora 30 now that it has been released, and
  so far I have not seen the screen flashing, so I do not think the
  hardware is faulty.

  I ran apport-bug, so hopefully the collected information has been
  attached.

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  5 15:59:45 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 
[VGA controller])
 Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af]
  InstallationDate: Installed on 2019-04-28 (6 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. XPS 13 9380
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/29/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 0KTW76
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.product.sku: 08AF
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Kernel-packages] [Bug 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes

2019-09-12 Thread Ben Bromley
I ran "journalctl --user" after the last flicker and this is the output
from the time around the flicker

Sep 12 20:12:34 shadeball org.gnome.Shell.desktop[5959]: 
[1:1:0912/201234.077664:ERROR:child_process_sandbox_support_impl_linux.cc(81)] 
FontService unique font name matching request did not receive a response.
Sep 12 20:12:34 shadeball org.gnome.Shell.desktop[5959]: 
[1:1:0912/201234.078033:ERROR:child_process_sandbox_support_impl_linux.cc(81)] 
FontService unique font name matching request did not receive a response.
Sep 12 20:12:34 shadeball org.gnome.Shell.desktop[5959]: 
[1:1:0912/201234.084532:ERROR:child_process_sandbox_support_impl_linux.cc(81)] 
FontService unique font name matching request did not receive a response.
Sep 12 20:12:34 shadeball org.gnome.Shell.desktop[5959]: 
[1:1:0912/201234.084847:ERROR:child_process_sandbox_support_impl_linux.cc(81)] 
FontService unique font name matching request did not receive a response.

I can post the full multi-day output of journalctl --user if that would
be useful to you all.

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

Title:
  Dell XPS 13 9380 - Screen brightness flashes

Status in gnome-settings-daemon package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu
  edition from Dell which came with 18.04, but I've since wiped it and
  installed 19.04 from a fresh ISO download. This is the non-touch non-
  4K version (13-inch 1080p).

  Every so often (maybe a couple of times per minute), the screen
  flashes brighter, as if the brightness has been turned up momentarily
  and then back down again.

  I previously had an issue with the brightness / colours changing
  slightly when I opened menus or if the screen content changed
  slightly, but I fixed that by disabling Dynamic Brightness in the
  BIOS. It is definitely a better experience with that turned off.

  However the screen flashing still persists.

  I booted a live image of Fedora 30 now that it has been released, and
  so far I have not seen the screen flashing, so I do not think the
  hardware is faulty.

  I ran apport-bug, so hopefully the collected information has been
  attached.

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  5 15:59:45 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 
[VGA controller])
 Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af]
  InstallationDate: Installed on 2019-04-28 (6 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. XPS 13 9380
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/29/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 0KTW76
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.product.sku: 08AF
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Kernel-packages] [Bug 1842799] Re: bionic/linux-raspi2: 4.15.0-1046.50 -proposed tracker

2019-09-12 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1842828
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 12. September 2019 22:56 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:building
+   promote-to-proposed: Ongoing -- builds not complete in ppa main:building
  replaces: bug 1842566
  trackers:
bionic/linux-raspi2/pi-kernel: bug 1842798
  variant: debs

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

Title:
  bionic/linux-raspi2: 4.15.0-1046.50 -proposed tracker

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

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

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

  -- swm properties --
  kernel-stable-master-bug: 1842828
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 12. September 2019 22:56 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa main:building
  replaces: bug 1842566
  trackers:
bionic/linux-raspi2/pi-kernel: bug 1842798
  variant: debs

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

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


[Kernel-packages] [Bug 1830961] Re: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible]

2019-09-12 Thread Seth Forshee
Hmm, I guess we should SRU the --fcf-protection=none change to the 19.04
and 18.04 kernels in that case. I will get this done.

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

Title:
  Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect-
  branch’ and ‘-fcf-protection’ are not compatible]

Status in gcc-9 package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in virtualbox package in Ubuntu:
  Won't Fix
Status in xtables-addons package in Ubuntu:
  Won't Fix

Bug description:
  Compiling kernels & kernel modules fails due to these errors:

  ./include/linux/compiler.h:193:1: error: ‘-mindirect-branch’ and
  ‘-fcf-protection’ are not compatible

  (This happens with any kernel modules.)

  This appears to be due to the changes in 9.1.0-3ubuntu1 enabling -fcf-
  protection by default on 19.10's gcc-9.

  Switching to gcc-8 allows compilation to proceed.

  WORKAROUND:

  sudo ln -fs gcc-8 /usr/bin/gcc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1830961/+subscriptions

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


[Kernel-packages] [Bug 1840619] Re: skb_warn_bad_offload kernel splat due to CHECKSUM target not compatible with GSO skbs

2019-09-12 Thread Matthew Ruffell
I installed 4.4.0-163-generic from xenial -proposed to a xenial VM, with
the following uname -rv:

4.4.0-163-generic #191-Ubuntu SMP Wed Sep 11 17:06:27 UTC 2019

>From there I enabled a iptsables rule with the CHECKSUM target, for tcp
port 8000:

sudo iptables -t mangle -A POSTROUTING -p tcp -m tcp --sport 8000 -j
CHECKSUM --checksum-fill

After running that command, dmesg now prints the correct warning against
use of the CHECKSUM target:

[   99.606968] xt_CHECKSUM: CHECKSUM should be avoided.  If really
needed, restrict with "-p udp" and only use in OUTPUT

I bound a port to 8000 with netcat, and ran traffic over it. Everything
worked fine and was stable with no crashes seen.

This fixes the issue in this bug, and I am happy to mark it as verified.

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

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

Title:
  skb_warn_bad_offload kernel splat due to CHECKSUM target not
  compatible with GSO skbs

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1840619

  [Impact]

  In environments which have CHECKSUM iptables rules set, the following
  kernel call trace will be created when a GSO skb is processed by the
  CHECKSUM target:

  WARNING: CPU: 34 PID: 806048 at 
/build/linux-zdslHp/linux-4.4.0/net/core/dev.c:2456 
skb_warn_bad_offload+0xcf/0x110()
  qr-f78bfdf7-fe: caps=(0x0fdb58e9, 0x0fdb58e9) len=1955 
data_len=479 gso_size=1448 gso_type=1 ip_summed=3
  CPU: 34 PID: 806048 Comm: haproxy Tainted: GW  OE   4.4.0-138-generic 
#164-Ubuntu
  Call Trace:
   dump_stack+0x63/0x90
   warn_slowpath_common+0x82/0xc0
   warn_slowpath_fmt+0x5c/0x80
   ? ___ratelimit+0xa2/0xe0
   skb_warn_bad_offload+0xcf/0x110
   skb_checksum_help+0x185/0x1a0
   checksum_tg+0x22/0x29 [xt_CHECKSUM]
   ipt_do_table+0x301/0x730 [ip_tables]
   ? ipt_do_table+0x349/0x730 [ip_tables]
   iptable_mangle_hook+0x39/0x107 [iptable_mangle]
   nf_iterate+0x68/0x80
   nf_hook_slow+0x73/0xd0
   ip_output+0xcf/0xe0
   ? __ip_flush_pending_frames.isra.43+0x90/0x90
   ip_local_out+0x3b/0x50
   ip_queue_xmit+0x154/0x390
   __tcp_transmit_skb+0x52b/0x9b0
   tcp_write_xmit+0x1dd/0xf50
   __tcp_push_pending_frames+0x31/0xd0
   tcp_push+0xec/0x110
   tcp_sendmsg+0x749/0xba0
   inet_sendmsg+0x6b/0xa0
   sock_sendmsg+0x3e/0x50
   SYSC_sendto+0x101/0x190
   ? __sys_sendmsg+0x51/0x90
   SyS_sendto+0xe/0x10
   entry_SYSCALL_64_fastpath+0x22/0xc1

  The CHECKSUM target does not support GSO skbs, and when a GSO skb is
  passed to skb_checksum_help(), it errors out and
  skb_warn_bad_offload() is called.

  The above call trace was found in a customer environment which has an
  Openstack deployment, with the following sorts of iptables rules set:

  -A neutron-l3-agent-POSTROUTING -o qr-+ -p tcp -m tcp --sport 9697 -j 
CHECKSUM --checksum-fill
  -A neutron-dhcp-age-POSTROUTING -p udp -m udp --dport 68 -j CHECKSUM 
--checksum-fill

  This was causing haproxy running on the node to crash and restart
  every time a GSO skb was processed by the CHECKSUM target.

  I recommend reading the netdev mailing list thread for more details:
  https://www.spinics.net/lists/netdev/msg517366.html

  [Fix]

  This was fixed in 4.19 upstream with the below commit:

  commit 10568f6c5761db24249c610c94d6e44d5505a0ba
  Author: Florian Westphal 
  Date:   Wed Aug 22 11:33:27 2018 +0200
  Subject: netfilter: xt_checksum: ignore gso skbs

  This commit adds a check to see if the current skb is a gso skb, and
  if it is, skips skb_checksum_help(). It then continues on to check if
  the packet uses udp, and if it does, exits early. Otherwise it prints
  a single warning that CHECKSUM should be avoided, and if really
  needed, only for use with outbound udp.

  Note, 10568f6c5761db24249c610c94d6e44d5505a0ba was included in
  upstream stable version 4.18.13, and was backported to bionic in
  4.15.0-58.64 by LP #1836426.

  This patch required minor backporting for 4.4, by slightly adjusting
  the context in the final patch hunk.

  [Testcase]

  You can reproduce this by adding the following iptables rule to the
  mangle table:

  -t mangle -A POSTROUTING -p tcp -m tcp --sport 80 -j CHECKSUM
  --checksum-fill

  and running traffic over port 80 with incorrect checksums in the ip
  header.

  I built a test kernel, which is available here:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf216537-test

  For unpatched kernels, this causes the process which was handling the
  socket to crash, as seen by haproxy crashing on a node in production
  which hits this issue.

  On patched kernels you see the below warning printed to dmesg and no
  crashes occur.

  xt_CHECKSUM: CHECKSUM should be avoided.  If really needed, restrict
  with "-p udp" and only use 

[Kernel-packages] [Bug 1842799] Re: bionic/linux-raspi2: 4.15.0-1046.50 -proposed tracker

2019-09-12 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Committed

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1842828
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
- phase: Packaging
- phase-changed: Thursday, 12. September 2019 18:30 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Thursday, 12. September 2019 22:56 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:building
  replaces: bug 1842566
  trackers:
bionic/linux-raspi2/pi-kernel: bug 1842798
  variant: debs

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

Title:
  bionic/linux-raspi2: 4.15.0-1046.50 -proposed tracker

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

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

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

  -- swm properties --
  kernel-stable-master-bug: 1842828
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 12. September 2019 22:56 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:building
  replaces: bug 1842566
  trackers:
bionic/linux-raspi2/pi-kernel: bug 1842798
  variant: debs

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

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


[Kernel-packages] [Bug 1842785] Re: Freeze after waking up from suspend on a Ryzen 3000 based system

2019-09-12 Thread Don Gi Min
Hey sorry for the lack of updates. Been busy with school... I'll
hopefully get that thing done Friday night (US time)

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

Title:
  Freeze after waking up from suspend on a Ryzen 3000 based system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My system is a newly build Ryzen 3600 based system with Vega 56
  graphics.

  On suspend wakeup, the entire system locks up. A workaround is booting
  with linux kernel version 4.19.69.

  Using newer linux versions (5.3-rc7) did not fix the issue.

  The motherboard is an MSI B450I gaming plus ac board; I've loaded up
  both the official non-beta BIOS (7A40vA8) and  the newest beta BIOS
  (7A40vA91) and both have this issue.

  No dmesg logs are available after the suspend wakeup (last message is
  putting the system to sleep)

  I have a r8169 and iwlwifi based ethernet and wifi cards, but I've
  tentatively isolated that those two are not an issue by blacklisting
  the respective modules.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-27-generic 5.0.0-27.28
  ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hatsu  2282 F pulseaudio
   /dev/snd/controlC2:  hatsu  2282 F pulseaudio
   /dev/snd/controlC0:  hatsu  2282 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  4 23:14:34 2019
  InstallationDate: Installed on 2019-08-27 (9 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Micro-Star International Co., Ltd. MS-7A40
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-generic 
root=UUID=4b8b9e96-fd23-4ade-bcd2-19b9795bd4e6 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-27-generic N/A
   linux-backports-modules-5.0.0-27-generic  N/A
   linux-firmware1.178.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-08-27 (9 days ago)
  dmi.bios.date: 08/19/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.91
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450I GAMING PLUS AC (MS-7A40)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.91:bd08/19/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A40:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450IGAMINGPLUSAC(MS-7A40):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A40
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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


[Kernel-packages] [Bug 1842553] Re: disco/linux-gcp: 5.0.0-1016.16 -proposed tracker

2019-09-12 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-disco

** Tags added: block-proposed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1842561
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
- phase: Holding before Promote to Proposed
- phase-changed: Thursday, 12. September 2019 17:11 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Thursday, 12. September 2019 21:56 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait
+   promote-to-proposed: Pending -- ready for review
  trackers:
bionic/linux-gcp: bug 1842549
bionic/linux-gke-5.0: bug 1842840
  variant: debs

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

Title:
  disco/linux-gcp: 5.0.0-1016.16 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842561
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Ready for Promote to Proposed
  phase-changed: Thursday, 12. September 2019 21:56 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  trackers:
bionic/linux-gcp: bug 1842549
bionic/linux-gke-5.0: bug 1842840
  variant: debs

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

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


[Kernel-packages] [Bug 1842598] Re: xenial/linux-kvm: 4.4.0-1057.64 -proposed tracker

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1842608
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Packaging
- phase-changed: Tuesday, 10. September 2019 11:15 UTC
+ phase-changed: Thursday, 12. September 2019 21:16 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
  variant: debs

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

Title:
  xenial/linux-kvm: 4.4.0-1057.64 -proposed tracker

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

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

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

  -- swm properties --
  kernel-stable-master-bug: 1842608
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Packaging
  phase-changed: Thursday, 12. September 2019 21:16 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
  variant: debs

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

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


[Kernel-packages] [Bug 1842600] Re: xenial/linux-raspi2: 4.4.0-1121.130 -proposed tracker

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1842608
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Packaging
- phase-changed: Tuesday, 10. September 2019 08:01 UTC
+ phase-changed: Thursday, 12. September 2019 21:16 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
  trackers:
xenial/linux-raspi2/pi2-kernel: bug 1842599
  variant: debs

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

Title:
  xenial/linux-raspi2: 4.4.0-1121.130 -proposed tracker

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

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

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

  -- swm properties --
  kernel-stable-master-bug: 1842608
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Packaging
  phase-changed: Thursday, 12. September 2019 21:16 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
  trackers:
xenial/linux-raspi2/pi2-kernel: bug 1842599
  variant: debs

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

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


[Kernel-packages] [Bug 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes

2019-09-12 Thread Ben Bromley
I am running Ubuntu 19.04 with an XPS 13 9380 with Intel graphics. I
installed the kernel mentioned above, and the problem is still
occurring. I do a dmesg everytime I see it happen, but I don't see a
consistent message every time it happens. I am more than willing to do
any and all testing you all need, so if you think of something I could
do to further investigate, let me know!

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

Title:
  Dell XPS 13 9380 - Screen brightness flashes

Status in gnome-settings-daemon package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu
  edition from Dell which came with 18.04, but I've since wiped it and
  installed 19.04 from a fresh ISO download. This is the non-touch non-
  4K version (13-inch 1080p).

  Every so often (maybe a couple of times per minute), the screen
  flashes brighter, as if the brightness has been turned up momentarily
  and then back down again.

  I previously had an issue with the brightness / colours changing
  slightly when I opened menus or if the screen content changed
  slightly, but I fixed that by disabling Dynamic Brightness in the
  BIOS. It is definitely a better experience with that turned off.

  However the screen flashing still persists.

  I booted a live image of Fedora 30 now that it has been released, and
  so far I have not seen the screen flashing, so I do not think the
  hardware is faulty.

  I ran apport-bug, so hopefully the collected information has been
  attached.

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  5 15:59:45 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 
[VGA controller])
 Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af]
  InstallationDate: Installed on 2019-04-28 (6 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. XPS 13 9380
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/29/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 0KTW76
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.product.sku: 08AF
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Kernel-packages] [Bug 1842603] Re: xenial/linux-snapdragon: 4.4.0-1125.131 -proposed tracker

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1842608
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Packaging
- phase-changed: Tuesday, 10. September 2019 08:55 UTC
+ phase-changed: Thursday, 12. September 2019 21:16 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1842602
  variant: debs

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

Title:
  xenial/linux-snapdragon: 4.4.0-1125.131 -proposed tracker

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

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

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

  -- swm properties --
  kernel-stable-master-bug: 1842608
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Packaging
  phase-changed: Thursday, 12. September 2019 21:16 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1842602
  variant: debs

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

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


[Kernel-packages] [Bug 1842592] Re: xenial/linux-deeplens: -proposed tracker

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1842593
  packages:
main: linux-deeplens
meta: linux-meta-deeplens
- phase: Holding before Packaging
- phase-changed: Wednesday, 04. September 2019 04:59 UTC
+ phase: Ready for Packaging
+ phase-changed: Thursday, 12. September 2019 21:12 UTC
  reason:
-   prepare-package: Holding -- waiting for master bug
+   prepare-package: Pending -- version not specified
  variant: debs

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

Title:
  xenial/linux-deeplens:  -proposed tracker

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

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

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

  -- swm properties --
  kernel-stable-master-bug: 1842593
  packages:
main: linux-deeplens
meta: linux-meta-deeplens
  phase: Ready for Packaging
  phase-changed: Thursday, 12. September 2019 21:12 UTC
  reason:
prepare-package: Pending -- version not specified
  variant: debs

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

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


[Kernel-packages] [Bug 1842600] Re: xenial/linux-raspi2: 4.4.0-1121.130 -proposed tracker

2019-09-12 Thread Andy Whitcroft
** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => New

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

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

Title:
  xenial/linux-raspi2: 4.4.0-1121.130 -proposed tracker

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

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

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

  -- swm properties --
  kernel-stable-master-bug: 1842608
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Packaging
  phase-changed: Thursday, 12. September 2019 21:16 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
  trackers:
xenial/linux-raspi2/pi2-kernel: bug 1842599
  variant: debs

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

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


[Kernel-packages] [Bug 1842598] Re: xenial/linux-kvm: 4.4.0-1057.64 -proposed tracker

2019-09-12 Thread Andy Whitcroft
** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => New

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

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

Title:
  xenial/linux-kvm: 4.4.0-1057.64 -proposed tracker

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

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

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

  -- swm properties --
  kernel-stable-master-bug: 1842608
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Packaging
  phase-changed: Thursday, 12. September 2019 21:16 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
  variant: debs

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

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


[Kernel-packages] [Bug 1842603] Re: xenial/linux-snapdragon: 4.4.0-1125.131 -proposed tracker

2019-09-12 Thread Andy Whitcroft
** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => New

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

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

Title:
  xenial/linux-snapdragon: 4.4.0-1125.131 -proposed tracker

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

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

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

  -- swm properties --
  kernel-stable-master-bug: 1842608
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Packaging
  phase-changed: Thursday, 12. September 2019 21:16 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1842602
  variant: debs

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

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


[Kernel-packages] [Bug 1842553] Re: disco/linux-gcp: 5.0.0-1016.16 -proposed tracker

2019-09-12 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1842561
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 12. September 2019 17:11 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,signed:depwait
+   promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait
  trackers:
bionic/linux-gcp: bug 1842549
bionic/linux-gke-5.0: bug 1842840
  variant: debs

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

Title:
  disco/linux-gcp: 5.0.0-1016.16 -proposed tracker

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

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

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

  -- swm properties --
  kernel-stable-master-bug: 1842561
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 12. September 2019 17:11 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait
  trackers:
bionic/linux-gcp: bug 1842549
bionic/linux-gke-5.0: bug 1842840
  variant: debs

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

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


[Kernel-packages] [Bug 1842799] Re: bionic/linux-raspi2: 4.15.0-1046.50 -proposed tracker

2019-09-12 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1842828
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
- phase: Ready for Packaging
- phase-changed: Friday, 06. September 2019 10:31 UTC
+ phase: Packaging
+ phase-changed: Thursday, 12. September 2019 18:30 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
  replaces: bug 1842566
  trackers:
bionic/linux-raspi2/pi-kernel: bug 1842798
  variant: debs

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

Title:
  bionic/linux-raspi2: 4.15.0-1046.50 -proposed tracker

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

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

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

  -- swm properties --
  kernel-stable-master-bug: 1842828
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Packaging
  phase-changed: Thursday, 12. September 2019 18:30 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
  replaces: bug 1842566
  trackers:
bionic/linux-raspi2/pi-kernel: bug 1842798
  variant: debs

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

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


[Kernel-packages] [Bug 1842799] Re: bionic/linux-raspi2: 4.15.0-1046.50 -proposed tracker

2019-09-12 Thread Marcelo Cerri
** Summary changed:

- bionic/linux-raspi2:  -proposed tracker
+ bionic/linux-raspi2: 4.15.0-1046.50 -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) => Marcelo Cerri 
(mhcerri)

** 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) => Marcelo Cerri 
(mhcerri)

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

Title:
  bionic/linux-raspi2: 4.15.0-1046.50 -proposed tracker

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

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

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

  -- swm properties --
  kernel-stable-master-bug: 1842828
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Packaging
  phase-changed: Thursday, 12. September 2019 18:30 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
  replaces: bug 1842566
  trackers:
bionic/linux-raspi2/pi-kernel: bug 1842798
  variant: debs

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

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


[Kernel-packages] [Bug 1842834] Re: bionic/linux-azure: 5.0.0-1019.20~18.04.1 -proposed tracker

2019-09-12 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

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

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

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842546
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Promote to Proposed
- phase-changed: Thursday, 12. September 2019 12:05 UTC
+ phase: Testing
+ phase-changed: Thursday, 12. September 2019 18:16 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Stalled -- testing FAILED
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   stakeholder-signoff: Pending -- waiting for signoff
+   verification-testing: Ongoing -- testing in progress
  replaces: bug 1842545
  trackers:
bionic/linux-azure-edge: bug 1842833
bionic/linux-azure/azure-kernel: bug 1842832
  variant: debs

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

Title:
  bionic/linux-azure: 5.0.0-1019.20~18.04.1 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842546
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Thursday, 12. September 2019 18:16 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  replaces: bug 1842545
  trackers:
bionic/linux-azure-edge: bug 1842833
bionic/linux-azure/azure-kernel: bug 1842832
  variant: debs

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

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


[Kernel-packages] [Bug 1842553] Re: disco/linux-gcp: 5.0.0-1016.16 -proposed tracker

2019-09-12 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1842561
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 12. September 2019 17:11 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:building,signed:building
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,signed:depwait
  trackers:
bionic/linux-gcp: bug 1842549
bionic/linux-gke-5.0: bug 1842840
  variant: debs

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

Title:
  disco/linux-gcp: 5.0.0-1016.16 -proposed tracker

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

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

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

  -- swm properties --
  kernel-stable-master-bug: 1842561
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 12. September 2019 17:11 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,signed:depwait
  trackers:
bionic/linux-gcp: bug 1842549
bionic/linux-gke-5.0: bug 1842840
  variant: debs

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

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


[Kernel-packages] [Bug 1842553] Re: disco/linux-gcp: 5.0.0-1016.16 -proposed tracker

2019-09-12 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Committed

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

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1842561
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
- phase: Packaging
- phase-changed: Wednesday, 11. September 2019 15:51 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Thursday, 12. September 2019 17:11 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
-   prepare-package-signed: Pending -- package not yet uploaded
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:building,signed:building
  trackers:
bionic/linux-gcp: bug 1842549
bionic/linux-gke-5.0: bug 1842840
  variant: debs

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

Title:
  disco/linux-gcp: 5.0.0-1016.16 -proposed tracker

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

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

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

  -- swm properties --
  kernel-stable-master-bug: 1842561
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 12. September 2019 17:11 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:building,signed:building
  trackers:
bionic/linux-gcp: bug 1842549
bionic/linux-gke-5.0: bug 1842840
  variant: debs

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

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


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

2019-09-12 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 1843792

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

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

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

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

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

Title:
  [USB][CML] USB under thunderbolt devices double free of interrupts
  when executed S4 sleep

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

Bug description:
  Description

  USB2.0/3.0 under TBT devices.

  Executed S4 sleep, found some "free already-free IRQ" dmesg Call
  Trace, which was not exist as before.

  [ 100.830955] PM: hibernation entry
  [ 122.538028] xhci_hcd :1a:00.0: Host halt failed, -19
  [ 122.538032] xhci_hcd :1a:00.0: Host not accessible, reset failed.
  [ 122.538033] ---[ cut here ]---
  [ 122.538033] Trying to free already-free IRQ 18
  [ 122.538039] WARNING: CPU: 0 PID: 200 at kernel/irq/manage.c:1708 
__free_irq+0x9c/0x2c0
  [ 122.538075] Call Trace:
  [ 122.538077] free_irq+0x3b/0x70
  [ 122.538079] xhci_cleanup_msix+0xa0/0xc0
  [ 122.538080] xhci_stop+0x9d/0x1b0
  [ 122.538103] ? irq_finalize_oneshot.part.46+0xf0/0xf0
  [ 122.538104] irq_thread_fn+0x24/0x60
  [ 133.311150] PM: hibernation exit
  [ 135.226643] xhci_hcd :10:00.0: remove, state 4
  [ 135.232679] usb usb9: USB disconnect, device number 1
  [ 135.323624] xhci_hcd :10:00.0: Host halt failed, -19
  [ 135.330102] xhci_hcd :10:00.0: Host not accessible, reset failed.
  [ 135.337672] ---[ cut here ]---
  [ 135.343526] Trying to free already-free IRQ 19
  [ 135.836669] xhci_hcd :0e:00.0: Host halt failed, -19
  [ 135.843486] xhci_hcd :0e:00.0: Host not accessible, reset failed.
  [ 135.851434] ---[ cut here ]---
  [ 135.857480] Trying to free already-free IRQ 17
  [ 136.124814] Call Trace:
  [ 136.129008] free_irq+0x3b/0x70
  [ 136.368933] xhci_hcd :0b:00.0: remove, state 4
  [ 136.375386] usb usb5: USB disconnect, device number 1
  [ 136.382245] xhci_hcd :0b:00.0: Host halt failed, -19
  [ 136.389166] xhci_hcd :0b:00.0: Host not accessible, reset failed.
  [ 136.397195] ---[ cut here ]---
  [ 136.403488] Trying to free already-free IRQ 19

   
  Target Kernel: TBD
  Target Release: 20.04

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

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


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

2019-09-12 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 1843790

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

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

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

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

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

Title:
  [Thunderbolt][CML-U/S] After freeze sleep finished more than 30s,
  lspci trigger tbt in D0, "TX ring 0 is already enabled" Call Trace
  generated and then failed to send driver ready to ICM

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

Bug description:
  Description
  Platform: CML-U (CML-S no need TR AIC)

  TR AIC: rev41

  Linux kernel: 5.3.0-rc1

  No TBT device connected.

  Executed freeze sleep successfully, after freeze exit more than 30s,

  cat /sys/bus/thunderbolt/devices/domain0/boot_acl  and lspci to
  trigger TBT root port in D0.

  Then "TX ring 0 is already enabled" Call Trace generated, then failed
  to send driver ready to  ICM.

  Thunderbolt driver was down.
   

  [ 263.903342] LTP: starting TBT_XS_FUNC_RTD3_freeze_test (tbt_rtd3.sh -c 0 -s 
rtd3_host_freeze)
  [ 264.010613] PM: suspend entry (s2idle)
  [ 286.868539] PM: suspend exit
  [ 313.202856] thunderbolt :03:00.0: stopping RX ring 0
  [ 313.204135] thunderbolt :03:00.0: disabling interrupt at register 
0x38200 bit 12 (0x1001 -> 0x1)
  [ 313.205565] thunderbolt :03:00.0: stopping TX ring 0
  [ 313.206842] thunderbolt :03:00.0: disabling interrupt at register 
0x38200 bit 0 (0x1 -> 0x0)
  [ 313.208018] thunderbolt :03:00.0: control channel stopped
  [ 321.432230] pcieport :02:01.0: pciehp: Slot(1): Link Up
  [ 321.433559] pcieport :02:04.0: pciehp: Slot(4-1): Link Up
  [ 322.550092] xhci_hcd :39:00.0: Refused to change power state, currently 
in D3
  [ 322.671084] thunderbolt :03:00.0: control channel starting...
  [ 322.672343] thunderbolt :03:00.0: starting TX ring 0
  [ 322.673601] thunderbolt :03:00.0: enabling interrupt at register 
0x38200 bit 0 (0x -> 0x)
  [ 322.674912] ---[ cut here ]---
  [ 322.676173] thunderbolt :03:00.0: interrupt for TX ring 0 is already 
enabled
  [ 322.706970] Call Trace:
  [ 322.708542] tb_ring_start+0x110/0x1a0 [thunderbolt]
  [ 322.710166] tb_ctl_start+0x36/0xc0 [thunderbolt]
  [ 322.711762] ? pci_restore_standard_config+0x50/0x50
  [ 322.71] ? pci_restore_standard_config+0x50/0x50
  [ 322.748162] thunderbolt :03:00.0: interrupt for RX ring 0 is already 
enabled
  [ 322.788047] ? pci_restore_standard_config+0x50/0x50
  [ 322.789901] ? pci_restore_standard_config+0x50/0x50
  [ 404.405929] thunderbolt :03:00.0: failed to send driver ready to ICM
  [ 405.596681] LTP: starting TBT_XS_FUNC_RTD3_S3_test (tbt_rtd3.sh -c 0 -s 
rtd3_host_s3)

  
  Target Release: 20.04
  Target Kernel: TBD

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

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


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

2019-09-12 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 1843794

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

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

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

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

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

Title:
  CML CPUIDs

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

Bug description:
  Description
  Please upstream CPUID for all CML SKUs.

  CML-U/CML-S/CML-Y/CML-H

  Target Release: 20.04
  Target Kernel: TBD

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

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


[Kernel-packages] [Bug 1843794] [NEW] CML CPUIDs

2019-09-12 Thread quanxian
Public bug reported:

Description
Please upstream CPUID for all CML SKUs.

CML-U/CML-S/CML-Y/CML-H

Target Release: 20.04
Target Kernel: TBD

** Affects: intel
 Importance: Undecided
 Status: New

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


** Tags: intel-kernel-20.04

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

Title:
  CML CPUIDs

Status in intel:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Description
  Please upstream CPUID for all CML SKUs.

  CML-U/CML-S/CML-Y/CML-H

  Target Release: 20.04
  Target Kernel: TBD

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

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


[Kernel-packages] [Bug 1843792] [NEW] [USB][CML] USB under thunderbolt devices double free of interrupts when executed S4 sleep

2019-09-12 Thread quanxian
Public bug reported:

Description

USB2.0/3.0 under TBT devices.

Executed S4 sleep, found some "free already-free IRQ" dmesg Call Trace,
which was not exist as before.

[ 100.830955] PM: hibernation entry
[ 122.538028] xhci_hcd :1a:00.0: Host halt failed, -19
[ 122.538032] xhci_hcd :1a:00.0: Host not accessible, reset failed.
[ 122.538033] ---[ cut here ]---
[ 122.538033] Trying to free already-free IRQ 18
[ 122.538039] WARNING: CPU: 0 PID: 200 at kernel/irq/manage.c:1708 
__free_irq+0x9c/0x2c0
[ 122.538075] Call Trace:
[ 122.538077] free_irq+0x3b/0x70
[ 122.538079] xhci_cleanup_msix+0xa0/0xc0
[ 122.538080] xhci_stop+0x9d/0x1b0
[ 122.538103] ? irq_finalize_oneshot.part.46+0xf0/0xf0
[ 122.538104] irq_thread_fn+0x24/0x60
[ 133.311150] PM: hibernation exit
[ 135.226643] xhci_hcd :10:00.0: remove, state 4
[ 135.232679] usb usb9: USB disconnect, device number 1
[ 135.323624] xhci_hcd :10:00.0: Host halt failed, -19
[ 135.330102] xhci_hcd :10:00.0: Host not accessible, reset failed.
[ 135.337672] ---[ cut here ]---
[ 135.343526] Trying to free already-free IRQ 19
[ 135.836669] xhci_hcd :0e:00.0: Host halt failed, -19
[ 135.843486] xhci_hcd :0e:00.0: Host not accessible, reset failed.
[ 135.851434] ---[ cut here ]---
[ 135.857480] Trying to free already-free IRQ 17
[ 136.124814] Call Trace:
[ 136.129008] free_irq+0x3b/0x70
[ 136.368933] xhci_hcd :0b:00.0: remove, state 4
[ 136.375386] usb usb5: USB disconnect, device number 1
[ 136.382245] xhci_hcd :0b:00.0: Host halt failed, -19
[ 136.389166] xhci_hcd :0b:00.0: Host not accessible, reset failed.
[ 136.397195] ---[ cut here ]---
[ 136.403488] Trying to free already-free IRQ 19

 
Target Kernel: TBD
Target Release: 20.04

** Affects: intel
 Importance: Undecided
 Status: New

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


** Tags: intel-kernel-20.04

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

Title:
  [USB][CML] USB under thunderbolt devices double free of interrupts
  when executed S4 sleep

Status in intel:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Description

  USB2.0/3.0 under TBT devices.

  Executed S4 sleep, found some "free already-free IRQ" dmesg Call
  Trace, which was not exist as before.

  [ 100.830955] PM: hibernation entry
  [ 122.538028] xhci_hcd :1a:00.0: Host halt failed, -19
  [ 122.538032] xhci_hcd :1a:00.0: Host not accessible, reset failed.
  [ 122.538033] ---[ cut here ]---
  [ 122.538033] Trying to free already-free IRQ 18
  [ 122.538039] WARNING: CPU: 0 PID: 200 at kernel/irq/manage.c:1708 
__free_irq+0x9c/0x2c0
  [ 122.538075] Call Trace:
  [ 122.538077] free_irq+0x3b/0x70
  [ 122.538079] xhci_cleanup_msix+0xa0/0xc0
  [ 122.538080] xhci_stop+0x9d/0x1b0
  [ 122.538103] ? irq_finalize_oneshot.part.46+0xf0/0xf0
  [ 122.538104] irq_thread_fn+0x24/0x60
  [ 133.311150] PM: hibernation exit
  [ 135.226643] xhci_hcd :10:00.0: remove, state 4
  [ 135.232679] usb usb9: USB disconnect, device number 1
  [ 135.323624] xhci_hcd :10:00.0: Host halt failed, -19
  [ 135.330102] xhci_hcd :10:00.0: Host not accessible, reset failed.
  [ 135.337672] ---[ cut here ]---
  [ 135.343526] Trying to free already-free IRQ 19
  [ 135.836669] xhci_hcd :0e:00.0: Host halt failed, -19
  [ 135.843486] xhci_hcd :0e:00.0: Host not accessible, reset failed.
  [ 135.851434] ---[ cut here ]---
  [ 135.857480] Trying to free already-free IRQ 17
  [ 136.124814] Call Trace:
  [ 136.129008] free_irq+0x3b/0x70
  [ 136.368933] xhci_hcd :0b:00.0: remove, state 4
  [ 136.375386] usb usb5: USB disconnect, device number 1
  [ 136.382245] xhci_hcd :0b:00.0: Host halt failed, -19
  [ 136.389166] xhci_hcd :0b:00.0: Host not accessible, reset failed.
  [ 136.397195] ---[ cut here ]---
  [ 136.403488] Trying to free already-free IRQ 19

   
  Target Kernel: TBD
  Target Release: 20.04

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

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


[Kernel-packages] [Bug 1843790] [NEW] [Thunderbolt][CML-U/S] After freeze sleep finished more than 30s, lspci trigger tbt in D0, "TX ring 0 is already enabled" Call Trace generated and then failed to

2019-09-12 Thread quanxian
Public bug reported:

Description
Platform: CML-U (CML-S no need TR AIC)

TR AIC: rev41

Linux kernel: 5.3.0-rc1

No TBT device connected.

Executed freeze sleep successfully, after freeze exit more than 30s,

cat /sys/bus/thunderbolt/devices/domain0/boot_acl  and lspci to trigger
TBT root port in D0.

Then "TX ring 0 is already enabled" Call Trace generated, then failed to
send driver ready to  ICM.

Thunderbolt driver was down.
 

[ 263.903342] LTP: starting TBT_XS_FUNC_RTD3_freeze_test (tbt_rtd3.sh -c 0 -s 
rtd3_host_freeze)
[ 264.010613] PM: suspend entry (s2idle)
[ 286.868539] PM: suspend exit
[ 313.202856] thunderbolt :03:00.0: stopping RX ring 0
[ 313.204135] thunderbolt :03:00.0: disabling interrupt at register 0x38200 
bit 12 (0x1001 -> 0x1)
[ 313.205565] thunderbolt :03:00.0: stopping TX ring 0
[ 313.206842] thunderbolt :03:00.0: disabling interrupt at register 0x38200 
bit 0 (0x1 -> 0x0)
[ 313.208018] thunderbolt :03:00.0: control channel stopped
[ 321.432230] pcieport :02:01.0: pciehp: Slot(1): Link Up
[ 321.433559] pcieport :02:04.0: pciehp: Slot(4-1): Link Up
[ 322.550092] xhci_hcd :39:00.0: Refused to change power state, currently 
in D3
[ 322.671084] thunderbolt :03:00.0: control channel starting...
[ 322.672343] thunderbolt :03:00.0: starting TX ring 0
[ 322.673601] thunderbolt :03:00.0: enabling interrupt at register 0x38200 
bit 0 (0x -> 0x)
[ 322.674912] ---[ cut here ]---
[ 322.676173] thunderbolt :03:00.0: interrupt for TX ring 0 is already 
enabled
[ 322.706970] Call Trace:
[ 322.708542] tb_ring_start+0x110/0x1a0 [thunderbolt]
[ 322.710166] tb_ctl_start+0x36/0xc0 [thunderbolt]
[ 322.711762] ? pci_restore_standard_config+0x50/0x50
[ 322.71] ? pci_restore_standard_config+0x50/0x50
[ 322.748162] thunderbolt :03:00.0: interrupt for RX ring 0 is already 
enabled
[ 322.788047] ? pci_restore_standard_config+0x50/0x50
[ 322.789901] ? pci_restore_standard_config+0x50/0x50
[ 404.405929] thunderbolt :03:00.0: failed to send driver ready to ICM
[ 405.596681] LTP: starting TBT_XS_FUNC_RTD3_S3_test (tbt_rtd3.sh -c 0 -s 
rtd3_host_s3)


Target Release: 20.04
Target Kernel: TBD

** Affects: intel
 Importance: Undecided
 Status: New

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


** Tags: intel-kernel-20.04

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

Title:
  [Thunderbolt][CML-U/S] After freeze sleep finished more than 30s,
  lspci trigger tbt in D0, "TX ring 0 is already enabled" Call Trace
  generated and then failed to send driver ready to ICM

Status in intel:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Description
  Platform: CML-U (CML-S no need TR AIC)

  TR AIC: rev41

  Linux kernel: 5.3.0-rc1

  No TBT device connected.

  Executed freeze sleep successfully, after freeze exit more than 30s,

  cat /sys/bus/thunderbolt/devices/domain0/boot_acl  and lspci to
  trigger TBT root port in D0.

  Then "TX ring 0 is already enabled" Call Trace generated, then failed
  to send driver ready to  ICM.

  Thunderbolt driver was down.
   

  [ 263.903342] LTP: starting TBT_XS_FUNC_RTD3_freeze_test (tbt_rtd3.sh -c 0 -s 
rtd3_host_freeze)
  [ 264.010613] PM: suspend entry (s2idle)
  [ 286.868539] PM: suspend exit
  [ 313.202856] thunderbolt :03:00.0: stopping RX ring 0
  [ 313.204135] thunderbolt :03:00.0: disabling interrupt at register 
0x38200 bit 12 (0x1001 -> 0x1)
  [ 313.205565] thunderbolt :03:00.0: stopping TX ring 0
  [ 313.206842] thunderbolt :03:00.0: disabling interrupt at register 
0x38200 bit 0 (0x1 -> 0x0)
  [ 313.208018] thunderbolt :03:00.0: control channel stopped
  [ 321.432230] pcieport :02:01.0: pciehp: Slot(1): Link Up
  [ 321.433559] pcieport :02:04.0: pciehp: Slot(4-1): Link Up
  [ 322.550092] xhci_hcd :39:00.0: Refused to change power state, currently 
in D3
  [ 322.671084] thunderbolt :03:00.0: control channel starting...
  [ 322.672343] thunderbolt :03:00.0: starting TX ring 0
  [ 322.673601] thunderbolt :03:00.0: enabling interrupt at register 
0x38200 bit 0 (0x -> 0x)
  [ 322.674912] ---[ cut here ]---
  [ 322.676173] thunderbolt :03:00.0: interrupt for TX ring 0 is already 
enabled
  [ 322.706970] Call Trace:
  [ 322.708542] tb_ring_start+0x110/0x1a0 [thunderbolt]
  [ 322.710166] tb_ctl_start+0x36/0xc0 [thunderbolt]
  [ 322.711762] ? pci_restore_standard_config+0x50/0x50
  [ 322.71] ? pci_restore_standard_config+0x50/0x50
  [ 322.748162] thunderbolt :03:00.0: interrupt for RX ring 0 is already 
enabled
  [ 322.788047] ? pci_restore_standard_config+0x50/0x50
  [ 322.789901] ? pci_restore_standard_config+0x50/0x50
  [ 404.405929] thunderbolt 

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

2019-09-12 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 1843778

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

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

Title:
  [CML-U] sdhci-pci :00:14.5: failed to setup card detect gpio

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

Bug description:
  Description
  on the following comet lake u 6+2 platform, there is sdio warning: "sdhci-pci 
:00:14.5: failed to setup card detect gpio"

  Patch has been submit
  "
  pinctrl: intel: Allow to request locked pins

  Some firmwares would like to protect pins from being modified by OS
  and at the same time provide them to OS as a resource. So, the driver
  in such circumstances may request pin and may not change its state.
  "

  Target Kernel: 5.3
  Target Release: 19.10

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

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


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

2019-09-12 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 1843774

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

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

Title:
  [CML] New device IDs for CML-U and CMP-H

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

Bug description:
  Description
  This task is to identify what new device IDs are required for CML.

  CML PCH-LP: CML-U
  CML PCH-H: CML-S
  CML PCH-V: 

  ControllerKernel Version  Commit  Approved to be
  published Comments
  USB device/xDCI   0x02ee   
  SMBus 0x02a3  v5.1-rc35cd1c56c42be 
  I²C   0x02c5 0x02c6 0x02e8 0x02e9 0x02ea 0x02eb   v5.2
dd6629073a97https://lkml.org/lkml/2019/4/9/548 
  I²C (CMP-H)   0x06c5 0x06c6 0x60e8? 0x60e9? 0x06ea 0x06eb 
 
  HS-UART   0x02a8 0x02a9 0x02c7v5.2dd6629073a97
https://lkml.org/lkml/2019/4/9/548
  HS-UART (CMP-H)   0x06a8 0x06a9 0x06c7
 
  SPI   0x02aa 0x02ab 0x02fbv5.2dd6629073a97 41a918026407   
 
  SPI (CMP-H)   0x06aa 0x06ab 0x06fb 
  SPI Flash Controller  0x02a4  
https://lore.kernel.org/linux-mtd/20190410073923.35693-1-mika.westerb...@linux.intel.com/
 
  GPIO  INT34BB It seems the same as for CNL. 
Does it have same IDs? According to dump from Wendy the ID is INT34BB which is 
CNL-LP. Nothing needs to be done here. 
Chap03_CMP-H_Pins_Chap18_GPIO_Automation_v3 1.0.xlsx is in use
  GPIO (CMP-H)  
  UFS   Is there a CML design with UFS 
this has been only POR for IoTG? 
  NPK   0x02a6  v5.2e60e9a4b231a 
  NPK (CMP-H)   0xa326  v4.14   84331e1390b6 
  AHCI  Not Needed supported by Class 
ID. 
  XHCI  Not needed supported by Class 
ID. 
  eMMC  0x02c4  v5.2-rc1765c59675ab5
https://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc.git/commit/?h=next=765c59675ab571caf7ada456bbfd23a73136b535
  SD Card   0x02f5  v5.2-rc1765c59675ab5
https://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc.git/commit/?h=next=765c59675ab571caf7ada456bbfd23a73136b535
  SD Card (CMP-H)   0x06f5  
https://patchwork.kernel.org/patch/11065085/

  Target Kernel: 5.2
  Target Release: 19.10

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

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


[Kernel-packages] [Bug 1842603] Re: xenial/linux-snapdragon: 4.4.0-1125.131 -proposed tracker

2019-09-12 Thread Paolo Pisati
** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Paolo Pisati (p-pisati) => (unassigned)

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Paolo Pisati (p-pisati) => (unassigned)

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

Title:
  xenial/linux-snapdragon: 4.4.0-1125.131 -proposed tracker

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

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

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

  -- swm properties --
  kernel-stable-master-bug: 1842608
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Packaging
  phase-changed: Tuesday, 10. September 2019 08:55 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1842602
  variant: debs

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

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


[Kernel-packages] [Bug 1842598] Re: xenial/linux-kvm: 4.4.0-1057.64 -proposed tracker

2019-09-12 Thread Paolo Pisati
** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Paolo Pisati (p-pisati) => (unassigned)

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Paolo Pisati (p-pisati) => (unassigned)

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

Title:
  xenial/linux-kvm: 4.4.0-1057.64 -proposed tracker

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

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

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

  -- swm properties --
  kernel-stable-master-bug: 1842608
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Packaging
  phase-changed: Tuesday, 10. September 2019 11:15 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
  variant: debs

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

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


[Kernel-packages] [Bug 1842600] Re: xenial/linux-raspi2: 4.4.0-1121.130 -proposed tracker

2019-09-12 Thread Paolo Pisati
** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Paolo Pisati (p-pisati) => (unassigned)

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Paolo Pisati (p-pisati) => (unassigned)

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

Title:
  xenial/linux-raspi2: 4.4.0-1121.130 -proposed tracker

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

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

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

  -- swm properties --
  kernel-stable-master-bug: 1842608
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Packaging
  phase-changed: Tuesday, 10. September 2019 08:01 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
  trackers:
xenial/linux-raspi2/pi2-kernel: bug 1842599
  variant: debs

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

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


[Kernel-packages] [Bug 1830961] Re: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible]

2019-09-12 Thread Christoph Reiter
Just for the record, this still breaks upgrades from 19.04 (I updated
today) because dkms tries to build things (nvidia and virtualbox here)
for the 19.04 kernel and fails.

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

Title:
  Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect-
  branch’ and ‘-fcf-protection’ are not compatible]

Status in gcc-9 package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in virtualbox package in Ubuntu:
  Won't Fix
Status in xtables-addons package in Ubuntu:
  Won't Fix

Bug description:
  Compiling kernels & kernel modules fails due to these errors:

  ./include/linux/compiler.h:193:1: error: ‘-mindirect-branch’ and
  ‘-fcf-protection’ are not compatible

  (This happens with any kernel modules.)

  This appears to be due to the changes in 9.1.0-3ubuntu1 enabling -fcf-
  protection by default on 19.10's gcc-9.

  Switching to gcc-8 allows compilation to proceed.

  WORKAROUND:

  sudo ln -fs gcc-8 /usr/bin/gcc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1830961/+subscriptions

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


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

2019-09-12 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 1843773

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

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

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

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

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

Title:
  [WHL-U|CML-U][ICL][Thunderbolt] AHCI SATA link down after S4 sleep and
  platform could not recover

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

Bug description:
  Description
  Platform: WHL-U
  BIOS: CNLSFWR1.R00.X147.B00.1806200058
  TBT: native PCIe tbt user mode
  AR AIC: rev 35.1
  Linux kernel: 4.18.0-rc8-intel-next+

  1. Approve all thunderbolt device to access, which contain SATA SSD(sda) and 
USB2.0/3.0
  2. Executed S4 sleep: rtcwake -m disk -s 50
  3. After S4 sleep ok and then wake to recover, and then “SATA link down 
(SStatus  SControl )”
  AHCI controller unavailable!
  …
  [sda] Start/Stop Unit failed

  Due to platform could not recover, could not get the dmesg log, and just 
caught the dmesg pictures in attached.
  After that platform could not recover and action timeout, call trace 
generated.

  Target Release: 20.04
  Target Kernel: TBD

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

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


[Kernel-packages] [Bug 1842320] Re: Out of Memory on boot with 5.2.0 kernel

2019-09-12 Thread Gordon Mckeown
Issue appears to be related to display resolution. Grub was booting into
3840x2160 mode, with the resulting tiny, near-unreadable font. So I set
GFXMODE=800x600 and now - unexpectedly - kernel 5.2.0 is able to boot
without the memory errors.

Not sure why the high resolution causes an out-of-memory error; a
3840x2160x32 framebuffer should only require ~32MB of RAM.

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

Title:
  Out of Memory on boot with 5.2.0 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgraded from 19.04 to current 19.10 using "do-release-upgrade -d".
  Can still boot using the previous 5.0.0-25-generic kernel, but the
  5.2.0-15-generic fails to start.

  On selecting Ubuntu from Grub, the message "error: out of memory." is
  immediately shown. Pressing a key attempts to start boot-up but fails
  to mount root fs.

  Machine is HP Spectre X360 with 8GB RAM. Under kernel 5.0.0, free
  shows the following (run from Gnome terminal):

    totalusedfree  shared  buff/cache   
available
  Mem:7906564 1761196 3833240 1020216 2312128 
4849224
  Swap:   1003516   0 1003516

  Kernel packages installed:

  linux-generic  5.2.0.15.16 amd64
  linux-headers-5.2.0-15 5.2.0-15.16 all
  linux-headers-5.2.0-15-generic 5.2.0-15.16 amd64
  linux-headers-generic  5.2.0.15.16 amd64
  linux-image-5.0.0-25-generic   5.0.0-25.26 amd64
  linux-image-5.2.0-15-generic   5.2.0-15.16+signed1 amd64
  linux-image-generic5.2.0.15.16 amd64
  linux-modules-5.0.0-25-generic 5.0.0-25.26 amd64
  linux-modules-5.2.0-15-generic 5.2.0-15.16 amd64
  linux-modules-extra-5.0.0-25-generic   5.0.0-25.26 amd64
  linux-modules-extra-5.2.0-15-generic   5.2.0-15.16 amd64

  Photo of kernel panic attached.

  NVMe drive partition layout (GPT):

  Device   StartEnd   Sectors   Size Type
  /dev/nvme0n1p120481050623   1048576   512M EFI System
  /dev/nvme0n1p2 10506242549759   1499136   732M Linux filesystem
  /dev/nvme0n1p3 2549760 1000214527 997664768 475.7G Linux filesystem

  $ sudo pvs
    PV  VGFmt  Attr PSizePFree
    /dev/mapper/nvme0n1p3_crypt ubuntu-vg lvm2 a--  <475.71g0

  $ sudo lvs
    LV VGAttr   LSize   Pool Origin Data%  Meta%  Move Log 
Cpy%Sync Convert
    root   ubuntu-vg -wi-ao 474.75g
    swap_1 ubuntu-vg -wi-ao 980.00m

  Partition 3 is LUKS encrypted. Root LV is ext4.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gmckeown   1647 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-08-15 (18 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd HP Wide Vision 
FHD Camera
   Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-25-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-25-generic N/A
   linux-backports-modules-5.0.0-25-generic  N/A
   linux-firmware1.181
  Tags:  eoan
  Uname: Linux 5.0.0-25-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-02 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/17/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.25
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.43
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.25:bd05/17/2019:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.43:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.product.sku: 2QH38EA#ABU
  dmi.sys.vendor: HP

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

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

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

2019-09-12 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 1843775

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

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

Title:
  [CML-U] Comet lake platform need ISH driver support

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description
  Track ISH driver in Comet lake platform

  CML-U ISH device_ID is: 02fc

  a50e8e2ecc1428df28c748c6af6255eb65faf9f3

  
  Target Release: 19.10
  Target Kernel: 5.1

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

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


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

2019-09-12 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 1843776

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

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

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

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

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

Title:
  [CML-U62] pcieport :00:1d.0: link reset at upstream device
  :00:1d.0 failed during resuming from S2idle

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

Bug description:
  Description
  Test Environment:

  Board ID 0x3 (CometLake U DDR4 HR RVP)
  Processor CometLake ULT Intel (R) Core(TM) i7-10710U CPU 1.10GHz A0 stepping
  Mem 16 GB DDR4 2666MT/s (2x8 GB)
  Storage 512GB Intel® SSD Pro 660P Series FW:002C
  PCH CML PCH-LP A0 stepping
  Kernel : Intel Next v5.2-rc6
  OS: Clear Linux OS
  BIOS: CMLSFWR1.R00.1245.D00.1906150738
  CML-U62 Windows BKC web: 
https://onebkc.intel.com/#/kit/CML-U62-CMP-19H1-CONS-2019WW26.1.202

  Issue description:
  Put system into S2idle, and will detect below failure during resume back, 
which will cause S2idle resuming fail:

  [ 81.394723] pcieport :00:1d.0: Data Link Layer Link Active not 0xCDE1
  [ 81.625395] pcieport :00:1d.0: link reset at upstream device 
:00:1d.0 failed
  [ 81.625427] pcieport :00:1d.0: AER: Device recovery failed
  [ 81.625439] pcieport :00:1d.0: DPC: containment event, status:0x1f01 
source:0x
  [ 81.658727] atkbd serio0: Failed to enable keyboard on isa0060/serio0
  [ 81.661857] pcieport :00:1d.0: DPC: unmasked uncorrectable error detected
  [ 82.309492] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction atus/mask=0020/0001
  [ 82.333019] pcieport :00:1d.0: AER: [21] ACSViol (First)

  Full serial log, please refer to cml 6+2 freeze issue.log

  root@p-cml02~ # lspci -vvv -s1d.0
  00:1d.0 PCI bridge: Intel Corporation Device 02b0 (rev f0) (prog-if 00 
[Normal decode])
  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- 
SERR- FastB2B- DisINTx+
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
  PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
  Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
  DevCap: MaxPayload 256 bytes, PhantFunc 0
  ExtTag- RBE+
  DevCtl: CorrErr+ NonFatalErr+ FatalErr+ UnsupReq+
  RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
  MaxPayload 128 bytes, MaxReadReq 128 bytes
  DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ TransPend-
  LnkCap: Port #9, Speed 8GT/s, Width x4, ASPM L0s L1, Exit Latency L0s <1us, 
L1 <16us
  ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+
  LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+
  ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
  LnkSta: Speed 8GT/s (ok), Width x4 (ok)
  TrErr- Train- SlotClk+ DLActive+ BWMgmt+ ABWMgmt-
  SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise-
  Slot #8, PowerLimit 25.000W; Interlock- NoCompl+
  SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg-
  Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
  SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock-
  Changed: MRL- PresDet- LinkState+
  RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible-
  RootCap: CRSVisible-
  RootSta: PME ReqID , PMEStatus- PMEPending-
  DevCap2: Completion Timeout: Range ABC, TimeoutDis+, LTR+, OBFF Not Supported 
ARIFwd+
  AtomicOpsCap: Routing- 32bit- 64bit- 128bitCAS-
  DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled 
ARIFwd-
  AtomicOpsCtl: ReqEn- EgressBlck-
  LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-
  Transmit Margin: Normal Operating Range, EnterModifiedCompliance- 
ComplianceSOS-
  Compliance De-emphasis: -6dB
  LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete+, 
EqualizationPhase1+
  EqualizationPhase2+, EqualizationPhase3+, LinkEqualizationRequest-
  Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
  Address: fee00218 Data: 
  Capabilities: [90] Subsystem: Intel Corporation Device 7270
  Capabilities: [a0] Power Management version 3
  Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
  Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
  Capabilities: [100 v1] Advanced Error Reporting
  UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- 
ECRC- UnsupReq- ACSViol-
  UEMsk: DLP- SDES- 

[Kernel-packages] [Bug 1843777] [NEW] [CML-U62] Need enable intel_pmc_core driver patch for Comet lake- U 6+2

2019-09-12 Thread quanxian
Public bug reported:

Description
Cometlake -U 6+2 is using a different CPU Model number: DEC 166, HEX: A6

We need the intel_pmc_core driver patch to support CML-U6+2

[ 13.053877] calling pmc_core_init+0x0/0x5f @ 1
[ 13.053878] initcall pmc_core_init+0x0/0x5f returned -19 after 0 usecs

root@p-cml02~ # cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 166
model name : Intel(R) Core(TM) i7-10710U CPU @ 1.10GHz
stepping : 0
microcode : 0xb0
cpu MHz : 2301.349
cache size : 12288 KB
physical id : 0
siblings : 12
core id : 0
cpu cores : 6
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 22
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 
clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm 
constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc 
cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma 
cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes 
xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single 
ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad 
fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap 
clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp 
hwp_notify hwp_act_window hwp_epp md_clear flush_l1d arch_capabilities
bugs : spectre_v1 spectre_v2 spec_store_bypass
bogomips : 3200.00
clflush size : 64
cache_alignment : 64
address sizes : 39 bits physical, 48 bits virtual

Target Kernel: 5.4
Target Release: 20.04

** Affects: intel
 Importance: Undecided
 Status: New

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


** Tags: intel-kenrel-20.04

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

Title:
  [CML-U62] Need enable intel_pmc_core driver patch for Comet lake- U
  6+2

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

Bug description:
  Description
  Cometlake -U 6+2 is using a different CPU Model number: DEC 166, HEX: A6

  We need the intel_pmc_core driver patch to support CML-U6+2

  [ 13.053877] calling pmc_core_init+0x0/0x5f @ 1
  [ 13.053878] initcall pmc_core_init+0x0/0x5f returned -19 after 0 usecs

  root@p-cml02~ # cat /proc/cpuinfo
  processor : 0
  vendor_id : GenuineIntel
  cpu family : 6
  model : 166
  model name : Intel(R) Core(TM) i7-10710U CPU @ 1.10GHz
  stepping : 0
  microcode : 0xb0
  cpu MHz : 2301.349
  cache size : 12288 KB
  physical id : 0
  siblings : 12
  core id : 0
  cpu cores : 6
  apicid : 0
  initial apicid : 0
  fpu : yes
  fpu_exception : yes
  cpuid level : 22
  wp : yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat 
pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp 
lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc 
cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma 
cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes 
xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single 
ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad 
fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap 
clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp 
hwp_notify hwp_act_window hwp_epp md_clear flush_l1d arch_capabilities
  bugs : spectre_v1 spectre_v2 spec_store_bypass
  bogomips : 3200.00
  clflush size : 64
  cache_alignment : 64
  address sizes : 39 bits physical, 48 bits virtual

  Target Kernel: 5.4
  Target Release: 20.04

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

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


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

2019-09-12 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 1843777

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

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

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

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

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

Title:
  [CML-U62] Need enable intel_pmc_core driver patch for Comet lake- U
  6+2

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

Bug description:
  Description
  Cometlake -U 6+2 is using a different CPU Model number: DEC 166, HEX: A6

  We need the intel_pmc_core driver patch to support CML-U6+2

  [ 13.053877] calling pmc_core_init+0x0/0x5f @ 1
  [ 13.053878] initcall pmc_core_init+0x0/0x5f returned -19 after 0 usecs

  root@p-cml02~ # cat /proc/cpuinfo
  processor : 0
  vendor_id : GenuineIntel
  cpu family : 6
  model : 166
  model name : Intel(R) Core(TM) i7-10710U CPU @ 1.10GHz
  stepping : 0
  microcode : 0xb0
  cpu MHz : 2301.349
  cache size : 12288 KB
  physical id : 0
  siblings : 12
  core id : 0
  cpu cores : 6
  apicid : 0
  initial apicid : 0
  fpu : yes
  fpu_exception : yes
  cpuid level : 22
  wp : yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat 
pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp 
lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc 
cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma 
cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes 
xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single 
ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad 
fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap 
clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp 
hwp_notify hwp_act_window hwp_epp md_clear flush_l1d arch_capabilities
  bugs : spectre_v1 spectre_v2 spec_store_bypass
  bogomips : 3200.00
  clflush size : 64
  cache_alignment : 64
  address sizes : 39 bits physical, 48 bits virtual

  Target Kernel: 5.4
  Target Release: 20.04

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

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


[Kernel-packages] [Bug 1843776] [NEW] [CML-U62] pcieport 0000:00:1d.0: link reset at upstream device 0000:00:1d.0 failed during resuming from S2idle

2019-09-12 Thread quanxian
Public bug reported:

Description
Test Environment:

Board ID 0x3 (CometLake U DDR4 HR RVP)
Processor CometLake ULT Intel (R) Core(TM) i7-10710U CPU 1.10GHz A0 stepping
Mem 16 GB DDR4 2666MT/s (2x8 GB)
Storage 512GB Intel® SSD Pro 660P Series FW:002C
PCH CML PCH-LP A0 stepping
Kernel : Intel Next v5.2-rc6
OS: Clear Linux OS
BIOS: CMLSFWR1.R00.1245.D00.1906150738
CML-U62 Windows BKC web: 
https://onebkc.intel.com/#/kit/CML-U62-CMP-19H1-CONS-2019WW26.1.202

Issue description:
Put system into S2idle, and will detect below failure during resume back, which 
will cause S2idle resuming fail:

[ 81.394723] pcieport :00:1d.0: Data Link Layer Link Active not 0xCDE1
[ 81.625395] pcieport :00:1d.0: link reset at upstream device :00:1d.0 
failed
[ 81.625427] pcieport :00:1d.0: AER: Device recovery failed
[ 81.625439] pcieport :00:1d.0: DPC: containment event, status:0x1f01 
source:0x
[ 81.658727] atkbd serio0: Failed to enable keyboard on isa0060/serio0
[ 81.661857] pcieport :00:1d.0: DPC: unmasked uncorrectable error detected
[ 82.309492] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction atus/mask=0020/0001
[ 82.333019] pcieport :00:1d.0: AER: [21] ACSViol (First)

Full serial log, please refer to cml 6+2 freeze issue.log

root@p-cml02~ # lspci -vvv -s1d.0
00:1d.0 PCI bridge: Intel Corporation Device 02b0 (rev f0) (prog-if 00 [Normal 
decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- 
SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: CorrErr+ NonFatalErr+ FatalErr+ UnsupReq+
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ TransPend-
LnkCap: Port #9, Speed 8GT/s, Width x4, ASPM L0s L1, Exit Latency L0s <1us, L1 
<16us
ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+
LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 8GT/s (ok), Width x4 (ok)
TrErr- Train- SlotClk+ DLActive+ BWMgmt+ ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise-
Slot #8, PowerLimit 25.000W; Interlock- NoCompl+
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock-
Changed: MRL- PresDet- LinkState+
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID , PMEStatus- PMEPending-
DevCap2: Completion Timeout: Range ABC, TimeoutDis+, LTR+, OBFF Not Supported 
ARIFwd+
AtomicOpsCap: Routing- 32bit- 64bit- 128bitCAS-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled 
ARIFwd-
AtomicOpsCtl: ReqEn- EgressBlck-
LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-
Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete+, 
EqualizationPhase1+
EqualizationPhase2+, EqualizationPhase3+, LinkEqualizationRequest-
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee00218 Data: 
Capabilities: [90] Subsystem: Intel Corporation Device 7270
Capabilities: [a0] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- 
UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt+ RxOF- MalfTLP- ECRC- 
UnsupReq- ACSViol-
UESvrt: DLP+ SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- 
UnsupReq- ACSViol-
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr-
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
AERCap: First Error Pointer: 00, ECRCGenCap- ECRCGenEn- ECRCChkCap- ECRCChkEn-
MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
HeaderLog:    
RootCmd: CERptEn+ NFERptEn+ FERptEn+
RootSta: CERcvd- MultCERcvd- UERcvd- MultUERcvd-
FirstFatal- NonFatalMsg- FatalMsg- IntMsg 0
ErrorSrc: ERR_COR:  ERR_FATAL/NONFATAL: 
Capabilities: [140 v1] Access Control Services
ACSCap: SrcValid+ TransBlk+ ReqRedir+ CmpltRedir+ UpstreamFwd- EgressCtrl- 
DirectTrans-
ACSCtl: SrcValid+ TransBlk- ReqRedir+ CmpltRedir+ UpstreamFwd- EgressCtrl- 
DirectTrans-
Capabilities: [150 v1] Precision Time Measurement
PTMCap: Requester:- Responder:+ Root:+
PTMClockGranularity: 4ns
PTMControl: Enabled:+ RootSelected:+
PTMEffectiveGranularity: Unknown
Capabilities: [200 

[Kernel-packages] [Bug 1843778] [NEW] [CML-U] sdhci-pci 0000:00:14.5: failed to setup card detect gpio

2019-09-12 Thread quanxian
Public bug reported:

Description
on the following comet lake u 6+2 platform, there is sdio warning: "sdhci-pci 
:00:14.5: failed to setup card detect gpio"

Patch has been submit
"
pinctrl: intel: Allow to request locked pins

Some firmwares would like to protect pins from being modified by OS
and at the same time provide them to OS as a resource. So, the driver
in such circumstances may request pin and may not change its state.
"

Target Kernel: 5.3
Target Release: 19.10

** Affects: intel
 Importance: Undecided
 Status: New

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


** Tags: intel-kernel-19.10

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

Title:
  [CML-U] sdhci-pci :00:14.5: failed to setup card detect gpio

Status in intel:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Description
  on the following comet lake u 6+2 platform, there is sdio warning: "sdhci-pci 
:00:14.5: failed to setup card detect gpio"

  Patch has been submit
  "
  pinctrl: intel: Allow to request locked pins

  Some firmwares would like to protect pins from being modified by OS
  and at the same time provide them to OS as a resource. So, the driver
  in such circumstances may request pin and may not change its state.
  "

  Target Kernel: 5.3
  Target Release: 19.10

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

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


[Kernel-packages] [Bug 1843774] [NEW] [CML] New device IDs for CML-U and CMP-H

2019-09-12 Thread quanxian
Public bug reported:

Description
This task is to identify what new device IDs are required for CML.

CML PCH-LP: CML-U
CML PCH-H: CML-S
CML PCH-V: 

Controller  Kernel Version  Commit  Approved to be
published   Comments
USB device/xDCI 0x02ee   
SMBus   0x02a3  v5.1-rc35cd1c56c42be 
I²C 0x02c5 0x02c6 0x02e8 0x02e9 0x02ea 0x02eb   v5.2
dd6629073a97https://lkml.org/lkml/2019/4/9/548 
I²C (CMP-H) 0x06c5 0x06c6 0x60e8? 0x60e9? 0x06ea 0x06eb 
 
HS-UART 0x02a8 0x02a9 0x02c7v5.2dd6629073a97
https://lkml.org/lkml/2019/4/9/548
HS-UART (CMP-H) 0x06a8 0x06a9 0x06c7 
SPI 0x02aa 0x02ab 0x02fbv5.2dd6629073a97 41a918026407   
 
SPI (CMP-H) 0x06aa 0x06ab 0x06fb 
SPI Flash Controller0x02a4  
https://lore.kernel.org/linux-mtd/20190410073923.35693-1-mika.westerb...@linux.intel.com/
 
GPIOINT34BB It seems the same as for CNL. 
Does it have same IDs? According to dump from Wendy the ID is INT34BB which is 
CNL-LP. Nothing needs to be done here. 
Chap03_CMP-H_Pins_Chap18_GPIO_Automation_v3 1.0.xlsx is in use
GPIO (CMP-H)
UFS Is there a CML design with UFS 
this has been only POR for IoTG? 
NPK 0x02a6  v5.2e60e9a4b231a 
NPK (CMP-H) 0xa326  v4.14   84331e1390b6 
AHCINot Needed supported by Class 
ID. 
XHCINot needed supported by Class 
ID. 
eMMC0x02c4  v5.2-rc1765c59675ab5
https://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc.git/commit/?h=next=765c59675ab571caf7ada456bbfd23a73136b535
SD Card 0x02f5  v5.2-rc1765c59675ab5
https://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc.git/commit/?h=next=765c59675ab571caf7ada456bbfd23a73136b535
SD Card (CMP-H) 0x06f5  
https://patchwork.kernel.org/patch/11065085/

Target Kernel: 5.2
Target Release: 19.10

** Affects: intel
 Importance: Undecided
 Status: New

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


** Tags: eoan intel-kernel-19.10

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

Title:
  [CML] New device IDs for CML-U and CMP-H

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

Bug description:
  Description
  This task is to identify what new device IDs are required for CML.

  CML PCH-LP: CML-U
  CML PCH-H: CML-S
  CML PCH-V: 

  ControllerKernel Version  Commit  Approved to be
  published Comments
  USB device/xDCI   0x02ee   
  SMBus 0x02a3  v5.1-rc35cd1c56c42be 
  I²C   0x02c5 0x02c6 0x02e8 0x02e9 0x02ea 0x02eb   v5.2
dd6629073a97https://lkml.org/lkml/2019/4/9/548 
  I²C (CMP-H)   0x06c5 0x06c6 0x60e8? 0x60e9? 0x06ea 0x06eb 
 
  HS-UART   0x02a8 0x02a9 0x02c7v5.2dd6629073a97
https://lkml.org/lkml/2019/4/9/548
  HS-UART (CMP-H)   0x06a8 0x06a9 0x06c7
 
  SPI   0x02aa 0x02ab 0x02fbv5.2dd6629073a97 41a918026407   
 
  SPI (CMP-H)   0x06aa 0x06ab 0x06fb 
  SPI Flash Controller  0x02a4  
https://lore.kernel.org/linux-mtd/20190410073923.35693-1-mika.westerb...@linux.intel.com/
 
  GPIO  INT34BB It seems the same as for CNL. 
Does it have same IDs? According to dump from Wendy the ID is INT34BB which is 
CNL-LP. Nothing needs to be done here. 
Chap03_CMP-H_Pins_Chap18_GPIO_Automation_v3 1.0.xlsx is in use
  GPIO (CMP-H)  
  UFS   Is there a CML design with UFS 
this has been only POR for IoTG? 
  NPK   0x02a6  v5.2e60e9a4b231a 
  NPK (CMP-H)   0xa326  v4.14   84331e1390b6 
  AHCI  Not Needed supported by Class 
ID. 
  XHCI  Not needed supported by Class 
ID. 
  eMMC  0x02c4  v5.2-rc1765c59675ab5
https://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc.git/commit/?h=next=765c59675ab571caf7ada456bbfd23a73136b535
  SD Card   0x02f5  v5.2-rc1765c59675ab5

[Kernel-packages] [Bug 1843775] [NEW] [CML-U] Comet lake platform need ISH driver support

2019-09-12 Thread quanxian
Public bug reported:

Description
Track ISH driver in Comet lake platform

CML-U ISH device_ID is: 02fc

a50e8e2ecc1428df28c748c6af6255eb65faf9f3


Target Release: 19.10
Target Kernel: 5.1

** Affects: intel
 Importance: Undecided
 Status: Fix Committed

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


** Tags: eoan intel-kernel-19.10

** Description changed:

  Description
  Track ISH driver in Comet lake platform
  
  CML-U ISH device_ID is: 02fc
  
+ a50e8e2ecc1428df28c748c6af6255eb65faf9f3
+ 
+ 
  Target Release: 19.10
  Target Kernel: 5.1

** Changed in: intel
   Status: New => Fix Committed

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

Title:
  [CML-U] Comet lake platform need ISH driver support

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description
  Track ISH driver in Comet lake platform

  CML-U ISH device_ID is: 02fc

  a50e8e2ecc1428df28c748c6af6255eb65faf9f3

  
  Target Release: 19.10
  Target Kernel: 5.1

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

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


[Kernel-packages] [Bug 1843773] [NEW] [WHL-U|CML-U][ICL][Thunderbolt] AHCI SATA link down after S4 sleep and platform could not recover

2019-09-12 Thread quanxian
Public bug reported:

Description
Platform: WHL-U
BIOS: CNLSFWR1.R00.X147.B00.1806200058
TBT: native PCIe tbt user mode
AR AIC: rev 35.1
Linux kernel: 4.18.0-rc8-intel-next+

1. Approve all thunderbolt device to access, which contain SATA SSD(sda) and 
USB2.0/3.0
2. Executed S4 sleep: rtcwake -m disk -s 50
3. After S4 sleep ok and then wake to recover, and then “SATA link down 
(SStatus  SControl )”
AHCI controller unavailable!
…
[sda] Start/Stop Unit failed

Due to platform could not recover, could not get the dmesg log, and just caught 
the dmesg pictures in attached.
After that platform could not recover and action timeout, call trace generated.

Target Release: 20.04
Target Kernel: TBD

** Affects: intel
 Importance: Undecided
 Status: New

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


** Tags: intel-kerel-20.04

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

Title:
  [WHL-U|CML-U][ICL][Thunderbolt] AHCI SATA link down after S4 sleep and
  platform could not recover

Status in intel:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Description
  Platform: WHL-U
  BIOS: CNLSFWR1.R00.X147.B00.1806200058
  TBT: native PCIe tbt user mode
  AR AIC: rev 35.1
  Linux kernel: 4.18.0-rc8-intel-next+

  1. Approve all thunderbolt device to access, which contain SATA SSD(sda) and 
USB2.0/3.0
  2. Executed S4 sleep: rtcwake -m disk -s 50
  3. After S4 sleep ok and then wake to recover, and then “SATA link down 
(SStatus  SControl )”
  AHCI controller unavailable!
  …
  [sda] Start/Stop Unit failed

  Due to platform could not recover, could not get the dmesg log, and just 
caught the dmesg pictures in attached.
  After that platform could not recover and action timeout, call trace 
generated.

  Target Release: 20.04
  Target Kernel: TBD

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

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


[Kernel-packages] [Bug 1842834] Re: bionic/linux-azure: 5.0.0-1019.20~18.04.1 -proposed tracker

2019-09-12 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842546
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Promote to Proposed
  phase-changed: Thursday, 12. September 2019 12:05 UTC
  reason:
-   promote-to-proposed: Pending -- package copied to Proposed signed:queued
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  replaces: bug 1842545
  trackers:
bionic/linux-azure-edge: bug 1842833
bionic/linux-azure/azure-kernel: bug 1842832
  variant: debs

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

Title:
  bionic/linux-azure: 5.0.0-1019.20~18.04.1 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842546
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Promote to Proposed
  phase-changed: Thursday, 12. September 2019 12:05 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  replaces: bug 1842545
  trackers:
bionic/linux-azure-edge: bug 1842833
bionic/linux-azure/azure-kernel: bug 1842832
  variant: debs

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

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


[Kernel-packages] [Bug 1842465] Re: Watchdog error about hard lockup

2019-09-12 Thread Manoj Iyer
** Changed in: linux (Ubuntu)
   Importance: Undecided => High

** Changed in: linux (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
Canonical Kernel Team (canonical-kernel-team)

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

Title:
  Watchdog error about hard lockup

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

Bug description:
  ---Problem Description---
  Got a message from Watchdog about self-detected hard LOCKUP
   
  ---uname output---
  Linux power 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:08:34 UTC 
2019 ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  Architecture:ppc64le
  Byte Order:  Little Endian
  CPU(s):  128
  On-line CPU(s) list: 0-127
  Thread(s) per core:  4
  Core(s) per socket:  16
  Socket(s):   2
  NUMA node(s):6
  Model:   2.2 (pvr 004e 1202)
  Model name:  POWER9, altivec supported
  CPU max MHz: 3800.
  CPU min MHz: 2300.
  L1d cache:   32K
  L1i cache:   32K
  L2 cache:512K
  L3 cache:10240K
  NUMA node0 CPU(s):   0-63
  NUMA node8 CPU(s):   64-127
  NUMA node252 CPU(s):
  NUMA node253 CPU(s):
  NUMA node254 CPU(s):
  NUMA node255 CPU(s):
  ---
  free
totalusedfree  shared  buff/cache   
available
  Mem: 1071807104 5110016   985192768 622944081504320  
1056273664
  Swap:   2097088   0 2097088
  --
  lsblk
  NAMEMAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
  sda   8:01 894.3G  0 disk
  ??sda18:11 7M  0 part
  ??sda28:21 894.3G  0 part /
  sdb   8:16   1 894.3G  0 disk
  nvme0n1 259:10   2.9T  0 disk /nvmdisk1
  ---
   
  Machine Type = AC922, bare metal 
   
  ---Steps to Reproduce---
   This problem I encountered when running customer workload and I switched SMT 
levels from SMT2 to SMT1 and I got a 
  lockup error right away!! this seems to be a different one... postgresql DB 
daemon was running on the system.
   
  Stack trace output:
   [756383.688067] watchdog: CPU 53 self-detected hard LOCKUP @ 
_raw_spin_lock+0x54/0xe0
  [756383.688068] watchdog: CPU 53 TB:387344180861438, last heartbeat 
TB:387337108856720 (13812ms ago)
  [756383.688069] Modules linked in: binfmt_misc veth ipt_MASQUERADE 
nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat_ipv4 
xt_addrtype iptable_filter bpfilter xt_conntrack nf_nat nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter bridge stp llc aufs overlay 
vmx_crypto ofpart cmdlinepart powernv_flash ipmi_powernv opal_prd mtd 
ipmi_devintf at24 ibmpowernv ipmi_msghandler uio_pdrv_genirq uio sch_fq_codel 
ib_iser rdma_cm iw_cm ib_cm iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear mlx5_ib ib_uverbs ib_core ast 
crct10dif_vpmsum i2c_algo_bit crc32c_vpmsum ttm mlx5_core drm_kms_helper 
syscopyarea nvme sysfillrect sysimgblt fb_sys_fops drm nvme_core ahci libahci 
tls mlxfw devlink tg3 drm_panel_orientation_quirks
  [756383.688088] CPU: 53 PID: 119744 Comm: postgres Not tainted 
5.0.0-23-generic #24~18.04.1-Ubuntu
  [756383.688088] NIP:  c0e0fcc4 LR: c015fd90 CTR: 
c0600460
  [756383.688089] REGS: c07fffb3bd70 TRAP: 0900   Not tainted  
(5.0.0-23-generic)
  [756383.688089] MSR:  90009033   CR: 
28242824  XER: 
  [756383.688091] CFAR: c0e0fcec IRQMASK: 1 
  [756383.688092] GPR00: c015fd90 c000206f2cdf7970 c185c700 
c00020732ea49100 
  [756383.688093] GPR04: c000206f2cdf7a38  c000206f2cdf7b00 
0001 
  [756383.688095] GPR08: 0003 807d 8035 
fffd 
  [756383.688096] GPR12: 2000 c07c5080 7cde07504dd8 
0f495eee0d68 
  [756383.688097] GPR16: 7fffc0eb2bd7 7fffc0eb2aa0 0f496c289088 
7fffc0eb2a74 
  [756383.688098] GPR20:  0001 0001 
 
  [756383.688099] GPR24:  c000206f2cdf7a38 c1349100 
20732d70 
  [756383.688100] GPR28: c1891c70 c000206f36d8b400 c1895c78 
c00020732ea49100 
  [756383.688102] NIP [c0e0fcc4] _raw_spin_lock+0x54/0xe0
  [756383.688102] LR [c015fd90] __task_rq_lock+0x80/0x150
  [756383.688102] Call Trace:
  [756383.688103] [c000206f2cdf7970] [c000206f2cdf79d0] 0xc000206f2cdf79d0 
(unreliable)
  [756383.688103] [c000206f2cdf79a0] [c07fd3847818] 0xc07fd3847818
  [756383.688104] [c000206f2cdf7a10] [c01649c0] 
try_to_wake_up+0x380/0x710
  [756383.688105] 

[Kernel-packages] [Bug 1842465] Re: Watchdog error about hard lockup

2019-09-12 Thread Frank Heimes
** Changed in: ubuntu-power-systems
   Status: Confirmed => Fix Committed

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

Title:
  Watchdog error about hard lockup

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

Bug description:
  ---Problem Description---
  Got a message from Watchdog about self-detected hard LOCKUP
   
  ---uname output---
  Linux power 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:08:34 UTC 
2019 ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  Architecture:ppc64le
  Byte Order:  Little Endian
  CPU(s):  128
  On-line CPU(s) list: 0-127
  Thread(s) per core:  4
  Core(s) per socket:  16
  Socket(s):   2
  NUMA node(s):6
  Model:   2.2 (pvr 004e 1202)
  Model name:  POWER9, altivec supported
  CPU max MHz: 3800.
  CPU min MHz: 2300.
  L1d cache:   32K
  L1i cache:   32K
  L2 cache:512K
  L3 cache:10240K
  NUMA node0 CPU(s):   0-63
  NUMA node8 CPU(s):   64-127
  NUMA node252 CPU(s):
  NUMA node253 CPU(s):
  NUMA node254 CPU(s):
  NUMA node255 CPU(s):
  ---
  free
totalusedfree  shared  buff/cache   
available
  Mem: 1071807104 5110016   985192768 622944081504320  
1056273664
  Swap:   2097088   0 2097088
  --
  lsblk
  NAMEMAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
  sda   8:01 894.3G  0 disk
  ??sda18:11 7M  0 part
  ??sda28:21 894.3G  0 part /
  sdb   8:16   1 894.3G  0 disk
  nvme0n1 259:10   2.9T  0 disk /nvmdisk1
  ---
   
  Machine Type = AC922, bare metal 
   
  ---Steps to Reproduce---
   This problem I encountered when running customer workload and I switched SMT 
levels from SMT2 to SMT1 and I got a 
  lockup error right away!! this seems to be a different one... postgresql DB 
daemon was running on the system.
   
  Stack trace output:
   [756383.688067] watchdog: CPU 53 self-detected hard LOCKUP @ 
_raw_spin_lock+0x54/0xe0
  [756383.688068] watchdog: CPU 53 TB:387344180861438, last heartbeat 
TB:387337108856720 (13812ms ago)
  [756383.688069] Modules linked in: binfmt_misc veth ipt_MASQUERADE 
nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat_ipv4 
xt_addrtype iptable_filter bpfilter xt_conntrack nf_nat nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter bridge stp llc aufs overlay 
vmx_crypto ofpart cmdlinepart powernv_flash ipmi_powernv opal_prd mtd 
ipmi_devintf at24 ibmpowernv ipmi_msghandler uio_pdrv_genirq uio sch_fq_codel 
ib_iser rdma_cm iw_cm ib_cm iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear mlx5_ib ib_uverbs ib_core ast 
crct10dif_vpmsum i2c_algo_bit crc32c_vpmsum ttm mlx5_core drm_kms_helper 
syscopyarea nvme sysfillrect sysimgblt fb_sys_fops drm nvme_core ahci libahci 
tls mlxfw devlink tg3 drm_panel_orientation_quirks
  [756383.688088] CPU: 53 PID: 119744 Comm: postgres Not tainted 
5.0.0-23-generic #24~18.04.1-Ubuntu
  [756383.688088] NIP:  c0e0fcc4 LR: c015fd90 CTR: 
c0600460
  [756383.688089] REGS: c07fffb3bd70 TRAP: 0900   Not tainted  
(5.0.0-23-generic)
  [756383.688089] MSR:  90009033   CR: 
28242824  XER: 
  [756383.688091] CFAR: c0e0fcec IRQMASK: 1 
  [756383.688092] GPR00: c015fd90 c000206f2cdf7970 c185c700 
c00020732ea49100 
  [756383.688093] GPR04: c000206f2cdf7a38  c000206f2cdf7b00 
0001 
  [756383.688095] GPR08: 0003 807d 8035 
fffd 
  [756383.688096] GPR12: 2000 c07c5080 7cde07504dd8 
0f495eee0d68 
  [756383.688097] GPR16: 7fffc0eb2bd7 7fffc0eb2aa0 0f496c289088 
7fffc0eb2a74 
  [756383.688098] GPR20:  0001 0001 
 
  [756383.688099] GPR24:  c000206f2cdf7a38 c1349100 
20732d70 
  [756383.688100] GPR28: c1891c70 c000206f36d8b400 c1895c78 
c00020732ea49100 
  [756383.688102] NIP [c0e0fcc4] _raw_spin_lock+0x54/0xe0
  [756383.688102] LR [c015fd90] __task_rq_lock+0x80/0x150
  [756383.688102] Call Trace:
  [756383.688103] [c000206f2cdf7970] [c000206f2cdf79d0] 0xc000206f2cdf79d0 
(unreliable)
  [756383.688103] [c000206f2cdf79a0] [c07fd3847818] 0xc07fd3847818
  [756383.688104] [c000206f2cdf7a10] [c01649c0] 
try_to_wake_up+0x380/0x710
  [756383.688105] [c000206f2cdf7aa0] [c0164de0] wake_up_q+0x70/0xd0
  

[Kernel-packages] [Bug 1838921] Autopkgtest regression report (dkms/2.6.1-4ubuntu2.3)

2019-09-12 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted dkms (2.6.1-4ubuntu2.3) for disco have 
finished running.
The following regressions have been reported in tests triggered by the package:

dahdi-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/disco/update_excuses.html#dkms

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  priority of OBSOLETE_BY should higher than "force"

Status in OEM Priority Project:
  New
Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Bionic:
  Fix Committed
Status in dkms source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  the priority of OBSOLETE_BY should higher than "force". #89 
https://github.com/dell/dkms/issues/89

  [Test case]
  1. install the dkms package which already patched (also can be found from my 
test ppa[1])
  2. install a DKMS which has OBSOLETE_BY and FORCE
  e.g.ath10k of my testing ppa : [2]
   - the target dkms defined OBSOLETE_BY and FORCE
   - user install dkms on a system which installed kernel version less than 
OBSOLETE_BY and another kernel higher than OBSOLETE_BY
   - the dkms can be installed well.

  [Regression potential]
  medium as it touched the version sanity. This change land a change from 
upstream.

  [1]:https://code.launchpad.net/~alextu/+recipe/2.3-3ubuntu9.5-closes89
  [2]:https://code.launchpad.net/~alextu/+recipe/2.3-3ubuntu9.5-closes89-dkms

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1838921/+subscriptions

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


[Kernel-packages] [Bug 1843742] [NEW] irda-utils ftbfs in eoan

2019-09-12 Thread Matthias Klose
Public bug reported:

https://launchpadlibrarian.net/441262268/buildlog_ubuntu-eoan-amd64
.irda-utils_0.9.18-15ubuntu1_BUILDING.txt.gz

gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fgnu89-inline 
-W -Wall -I. `pkg-config --cflags glib-2.0` -I/usr/include -I../include/ -c 
irdadump.c
irdadump.c: In function ‘print_time’:
irdadump.c:82:13: warning: g_string_append_printf
   82 |  g_string_sprintfa(str, "%02d:%02d:%02d.%06u ",
  | ^~~~
irdadump.c: In function ‘print_diff_time’:
irdadump.c:108:13: warning: g_string_append_printf
  108 |  g_string_sprintfa(str, "(%07.2f ms) ", diff);
  | ^~~~
irdadump.c: In function ‘parse_irda_frame’:
irdadump.c:178:13: warning: g_string_append_printf
  178 | g_string_sprintfa(str, "(%d) ", len);
  | ^~~~
irdadump.c:189:13: warning: g_string_append_printf
  189 |g_string_sprintfa(str, "%02x", frame_buf->head[i]);
  | ^~~~
irdadump.c:196:13: warning: g_string_append_printf
  196 |g_string_sprintfa(str, " %c", c);
  | ^~~~
irdadump.c:207:13: warning: g_string_append_printf
  207 |g_string_sprintfa(str, "%02x ", frame_buf->head[i]);
  | ^~~~
irdadump.c: In function ‘irdadump_loop’:
irdadump.c:286:16: error: ‘SIOCGSTAMP’ undeclared (first use in this function); 
did you mean ‘SIOCGARP’?
  286 |  if (ioctl(fd, SIOCGSTAMP, curr_time) < 0) {
  |^~
  |SIOCGARP
irdadump.c:286:16: note: each undeclared identifier is reported only once for 
each function it appears in
make[1]: *** [Makefile:48: irdadump.o] Error 1
make[1]: Leaving directory '/<>/irdadump'

** Affects: irda-utils (Ubuntu)
 Importance: High
 Status: Confirmed


** Tags: ftbfs rls-ee-incoming

** Changed in: irda-utils (Ubuntu)
   Status: New => Confirmed

** Changed in: irda-utils (Ubuntu)
   Importance: Undecided => High

** Tags added: ftbfs rls-ee-incoming

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

Title:
  irda-utils ftbfs in eoan

Status in irda-utils package in Ubuntu:
  Confirmed

Bug description:
  https://launchpadlibrarian.net/441262268/buildlog_ubuntu-eoan-amd64
  .irda-utils_0.9.18-15ubuntu1_BUILDING.txt.gz

  gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fgnu89-inline 
-W -Wall -I. `pkg-config --cflags glib-2.0` -I/usr/include -I../include/ -c 
irdadump.c
  irdadump.c: In function ‘print_time’:
  irdadump.c:82:13: warning: g_string_append_printf
 82 |  g_string_sprintfa(str, "%02d:%02d:%02d.%06u ",
| ^~~~
  irdadump.c: In function ‘print_diff_time’:
  irdadump.c:108:13: warning: g_string_append_printf
108 |  g_string_sprintfa(str, "(%07.2f ms) ", diff);
| ^~~~
  irdadump.c: In function ‘parse_irda_frame’:
  irdadump.c:178:13: warning: g_string_append_printf
178 | g_string_sprintfa(str, "(%d) ", len);
| ^~~~
  irdadump.c:189:13: warning: g_string_append_printf
189 |g_string_sprintfa(str, "%02x", frame_buf->head[i]);
| ^~~~
  irdadump.c:196:13: warning: g_string_append_printf
196 |g_string_sprintfa(str, " %c", c);
| ^~~~
  irdadump.c:207:13: warning: g_string_append_printf
207 |g_string_sprintfa(str, "%02x ", frame_buf->head[i]);
| ^~~~
  irdadump.c: In function ‘irdadump_loop’:
  irdadump.c:286:16: error: ‘SIOCGSTAMP’ undeclared (first use in this 
function); did you mean ‘SIOCGARP’?
286 |  if (ioctl(fd, SIOCGSTAMP, curr_time) < 0) {
|^~
|SIOCGARP
  irdadump.c:286:16: note: each undeclared identifier is reported only once for 
each function it appears in
  make[1]: *** [Makefile:48: irdadump.o] Error 1
  make[1]: Leaving directory '/<>/irdadump'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irda-utils/+bug/1843742/+subscriptions

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


[Kernel-packages] [Bug 1842605] Re: xenial/linux-fips: 4.4.0-1020.25 -proposed tracker

2019-09-12 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1842608
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 12. September 2019 10:51 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
meta:building,signed:building
+   promote-to-proposed: Holding -- master bug not ready for proposed
  variant: debs

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

Title:
  xenial/linux-fips: 4.4.0-1020.25 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842608
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 12. September 2019 10:51 UTC
  reason:
promote-to-proposed: Holding -- master bug not ready for proposed
  variant: debs

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

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


[Kernel-packages] [Bug 1842569] Re: bionic/linux-oem: -proposed tracker

2019-09-12 Thread Ubuntu Kernel Bot
*** This bug is a duplicate of bug 1842802 ***
https://bugs.launchpad.net/bugs/1842802

** This bug has been marked a duplicate of bug 1842802
   bionic/linux-oem: 4.15.0-1055.64 -proposed tracker

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

Title:
  bionic/linux-oem:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-lrm series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Invalid

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

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

  -- swm properties --
  kernel-stable-master-bug: 1842828
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Holding before Packaging
  phase-changed: Thursday, 05. September 2019 04:20 UTC
  reason:
prepare-package: Holding -- waiting for master bug
  variant: debs

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

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


[Kernel-packages] [Bug 1842834] Re: bionic/linux-azure: 5.0.0-1019.20~18.04.1 -proposed tracker

2019-09-12 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842546
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Promote to Proposed
  phase-changed: Thursday, 12. September 2019 12:05 UTC
  reason:
-   promote-to-proposed: Ongoing -- review in progress
+   promote-to-proposed: Pending -- package copied to Proposed signed:queued
  replaces: bug 1842545
  trackers:
bionic/linux-azure-edge: bug 1842833
bionic/linux-azure/azure-kernel: bug 1842832
  variant: debs

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

Title:
  bionic/linux-azure: 5.0.0-1019.20~18.04.1 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842546
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Promote to Proposed
  phase-changed: Thursday, 12. September 2019 12:05 UTC
  reason:
promote-to-proposed: Pending -- package copied to Proposed signed:queued
  replaces: bug 1842545
  trackers:
bionic/linux-azure-edge: bug 1842833
bionic/linux-azure/azure-kernel: bug 1842832
  variant: debs

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

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


[Kernel-packages] [Bug 1842802] Re: bionic/linux-oem: 4.15.0-1055.64 -proposed tracker

2019-09-12 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842828
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 12. September 2019 08:32 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,meta:depwait,signed:depwait
- replaces: bug 1842569
+   promote-to-proposed: Stalled -- another kernel is currently pending in 
Proposed
  variant: debs

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

Title:
  bionic/linux-oem: 4.15.0-1055.64 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow 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 will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842828
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 12. September 2019 08:32 UTC
  reason:
promote-to-proposed: Stalled -- another kernel is currently pending in 
Proposed
  variant: debs

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

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


[Kernel-packages] [Bug 1842834] Re: bionic/linux-azure: 5.0.0-1019.20~18.04.1 -proposed tracker

2019-09-12 Thread Łukasz Zemczak
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => Fix Committed

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

Title:
  bionic/linux-azure: 5.0.0-1019.20~18.04.1 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842546
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Promote to Proposed
  phase-changed: Thursday, 12. September 2019 12:05 UTC
  reason:
promote-to-proposed: Pending -- package copied to Proposed signed:queued
  replaces: bug 1842545
  trackers:
bionic/linux-azure-edge: bug 1842833
bionic/linux-azure/azure-kernel: bug 1842832
  variant: debs

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

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


[Kernel-packages] [Bug 1842605] Re: xenial/linux-fips: 4.4.0-1020.25 -proposed tracker

2019-09-12 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1842608
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 12. September 2019 10:51 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:depwait,signed:depwait
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
meta:building,signed:building
  variant: debs

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

Title:
  xenial/linux-fips: 4.4.0-1020.25 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid

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

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

  -- swm properties --
  kernel-stable-master-bug: 1842608
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 12. September 2019 10:51 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
meta:building,signed:building
  variant: debs

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

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


[Kernel-packages] [Bug 1842155] Re: disco/linux-oracle: 5.0.0-1002.3 -proposed tracker

2019-09-12 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1840826 (bionic/linux-oracle-edge)
  
  -- swm properties --
  kernel-stable-master-bug: 1840816
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Testing
  phase-changed: Monday, 02. September 2019 11:19 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
-   regression-testing: Ongoing -- testing in progress
stakeholder-signoff: Stalled -- waiting for signoff
  trackers:
bionic/linux-oracle-edge: bug 1840826
  variant: debs

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

Title:
  disco/linux-oracle: 5.0.0-1002.3 -proposed tracker

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

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

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

  backports: bug 1840826 (bionic/linux-oracle-edge)

  -- swm properties --
  kernel-stable-master-bug: 1840816
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Testing
  phase-changed: Monday, 02. September 2019 11:19 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
stakeholder-signoff: Stalled -- waiting for signoff
  trackers:
bionic/linux-oracle-edge: bug 1840826
  variant: debs

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

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


[Kernel-packages] [Bug 1842155] Re: disco/linux-oracle: 5.0.0-1002.3 -proposed tracker

2019-09-12 Thread Sean Feole
** Tags added: regression-testing-passed

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

Title:
  disco/linux-oracle: 5.0.0-1002.3 -proposed tracker

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

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

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

  backports: bug 1840826 (bionic/linux-oracle-edge)

  -- swm properties --
  kernel-stable-master-bug: 1840816
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Testing
  phase-changed: Monday, 02. September 2019 11:19 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
stakeholder-signoff: Stalled -- waiting for signoff
  trackers:
bionic/linux-oracle-edge: bug 1840826
  variant: debs

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

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


[Kernel-packages] [Bug 1842590] Re: xenial/linux-gcp: 4.15.0-1043.45 -proposed tracker

2019-09-12 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842828
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
- phase: Testing
- phase-changed: Thursday, 12. September 2019 11:07 UTC
+ phase: Signoff
+ phase-changed: Thursday, 12. September 2019 12:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-gcp: bug 1842838
bionic/linux-gke-5.0: bug 1842840
xenial/linux-gcp/gcp-kernel: bug 1842588
xenial/linux-gcp/gke-kernel: bug 1842589
  variant: debs

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

Title:
  xenial/linux-gcp: 4.15.0-1043.45 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842828
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Signoff
  phase-changed: Thursday, 12. September 2019 12:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-gcp: bug 1842838
bionic/linux-gke-5.0: bug 1842840
xenial/linux-gcp/gcp-kernel: bug 1842588
xenial/linux-gcp/gke-kernel: bug 1842589
  variant: debs

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

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


[Kernel-packages] [Bug 1838278] Re: zfs-initramfs wont mount rpool

2019-09-12 Thread Francis Ginther
** Tags added: id-5d79bf699cc0451cfad6b4a9

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

Title:
  zfs-initramfs wont mount rpool

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  1. Eoan

  2. http://archive.ubuntu.com/ubuntu eoan/main amd64 zfs-initramfs
  amd64 0.8.1-1ubuntu7 [23.1 kB]

  3. ZFS rootfs rpool is mounted at boot

  4. Booting an image with a rootfs rpool:

  [0.00] Linux version 5.2.0-8-generic (buildd@lgw01-amd64-015) (gcc 
version 9.1.0 (Ubuntu 9.1.0-6ubuntu2)) #9-Ubuntu SMP Mon Jul 8 13:07:27 UTC 
2019 (Ubuntu 5.2.0-8.9-generic 5.2.0)
  [0.00] Command line: 
BOOT_IMAGE=/ROOT/zfsroot@/boot/vmlinuz-5.2.0-8-generic 
root=ZFS=rpool/ROOT/zfsroot ro console=ttyS0

  
  Command: /sbin/zpool import -N   'rpool'
  Message: cannot import 'rpool': pool was previously in use from another 
system.
  Last accessed by ubuntu (hostid=d24775ba) at Mon Jul 29 05:21:19 2019
  The pool can be imported, use 'zpool import -f' to import the pool.
  Error: 1

  Failed to import pool 'rpool'.
  Manually import the pool and exit.

  
  Note, this works fine under Disco, 

  http://archive.ubuntu.com/ubuntu disco/main amd64 zfs-initramfs amd64
  0.7.12-1ubuntu5 [22.2 kB]

  [4.773077] spl: loading out-of-tree module taints kernel.  
  [4.777256] SPL: Loaded module v0.7.12-1ubuntu3
  [4.779433] znvpair: module license 'CDDL' taints kernel.
  [4.780333] Disabling lock debugging due to kernel taint
  [5.713830] ZFS: Loaded module v0.7.12-1ubuntu5, ZFS pool version 5000, 
ZFS filesystem version 5
  Begin: Sleeping for ... done.
  Begin: Importing ZFS root pool 'rpool' ... Begin: Importing pool 'rpool' 
using defaults ... done.
  Begin: Mounting 'rpool/ROOT/zfsroot' on '/root//' ... done.

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

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


[Kernel-packages] [Bug 1842834] Re: bionic/linux-azure: 5.0.0-1019.20~18.04.1 -proposed tracker

2019-09-12 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842546
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Ready for Promote to Proposed
- phase-changed: Thursday, 12. September 2019 11:51 UTC
+ phase: Promote to Proposed
+ phase-changed: Thursday, 12. September 2019 12:05 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Ongoing -- review in progress
  replaces: bug 1842545
  trackers:
bionic/linux-azure-edge: bug 1842833
bionic/linux-azure/azure-kernel: bug 1842832
  variant: debs

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

Title:
  bionic/linux-azure: 5.0.0-1019.20~18.04.1 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842546
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Promote to Proposed
  phase-changed: Thursday, 12. September 2019 12:05 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  replaces: bug 1842545
  trackers:
bionic/linux-azure-edge: bug 1842833
bionic/linux-azure/azure-kernel: bug 1842832
  variant: debs

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

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


[Kernel-packages] [Bug 1838921] Please test proposed package

2019-09-12 Thread Łukasz Zemczak
Hello Alex, or anyone else affected,

Accepted dkms into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/dkms/2.3-3ubuntu9.6 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  priority of OBSOLETE_BY should higher than "force"

Status in OEM Priority Project:
  New
Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Bionic:
  Fix Committed
Status in dkms source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  the priority of OBSOLETE_BY should higher than "force". #89 
https://github.com/dell/dkms/issues/89

  [Test case]
  1. install the dkms package which already patched (also can be found from my 
test ppa[1])
  2. install a DKMS which has OBSOLETE_BY and FORCE
  e.g.ath10k of my testing ppa : [2]
   - the target dkms defined OBSOLETE_BY and FORCE
   - user install dkms on a system which installed kernel version less than 
OBSOLETE_BY and another kernel higher than OBSOLETE_BY
   - the dkms can be installed well.

  [Regression potential]
  medium as it touched the version sanity. This change land a change from 
upstream.

  [1]:https://code.launchpad.net/~alextu/+recipe/2.3-3ubuntu9.5-closes89
  [2]:https://code.launchpad.net/~alextu/+recipe/2.3-3ubuntu9.5-closes89-dkms

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1838921/+subscriptions

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


[Kernel-packages] [Bug 1838921] Re: priority of OBSOLETE_BY should higher than "force"

2019-09-12 Thread Łukasz Zemczak
Hello Alex, or anyone else affected,

Accepted dkms into disco-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/dkms/2.6.1-4ubuntu2.3
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-disco to verification-done-disco. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-disco. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

** Tags added: verification-needed verification-needed-disco

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

** Tags added: verification-needed-bionic

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

Title:
  priority of OBSOLETE_BY should higher than "force"

Status in OEM Priority Project:
  New
Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Bionic:
  Fix Committed
Status in dkms source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  the priority of OBSOLETE_BY should higher than "force". #89 
https://github.com/dell/dkms/issues/89

  [Test case]
  1. install the dkms package which already patched (also can be found from my 
test ppa[1])
  2. install a DKMS which has OBSOLETE_BY and FORCE
  e.g.ath10k of my testing ppa : [2]
   - the target dkms defined OBSOLETE_BY and FORCE
   - user install dkms on a system which installed kernel version less than 
OBSOLETE_BY and another kernel higher than OBSOLETE_BY
   - the dkms can be installed well.

  [Regression potential]
  medium as it touched the version sanity. This change land a change from 
upstream.

  [1]:https://code.launchpad.net/~alextu/+recipe/2.3-3ubuntu9.5-closes89
  [2]:https://code.launchpad.net/~alextu/+recipe/2.3-3ubuntu9.5-closes89-dkms

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1838921/+subscriptions

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


[Kernel-packages] [Bug 1842834] Re: bionic/linux-azure: 5.0.0-1019.20~18.04.1 -proposed tracker

2019-09-12 Thread Łukasz Zemczak
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => In Progress

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

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

Title:
  bionic/linux-azure: 5.0.0-1019.20~18.04.1 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842546
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Promote to Proposed
  phase-changed: Thursday, 12. September 2019 12:05 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  replaces: bug 1842545
  trackers:
bionic/linux-azure-edge: bug 1842833
bionic/linux-azure/azure-kernel: bug 1842832
  variant: debs

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

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


[Kernel-packages] [Bug 1690085]

2019-09-12 Thread albertogomezmarin
I have freezes in ryzen 7 2700u in the acer swift sf315-41 model,
kernels tested, 5.2

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

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

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

Bug description:
  Hi,

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

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

  native 17.04 kernel
  4.10.15

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

  Here is kern.log entry when happening :

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

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

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

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-041100-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

-- 
Mailing 

[Kernel-packages] [Bug 1842834] Re: bionic/linux-azure: 5.0.0-1019.20~18.04.1 -proposed tracker

2019-09-12 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-bionic

** Tags added: block-proposed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1842546
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Holding before Promote to Proposed
- phase-changed: Thursday, 12. September 2019 08:10 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Thursday, 12. September 2019 11:51 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,signed:depwait
+   promote-to-proposed: Pending -- ready for review
  replaces: bug 1842545
  trackers:
bionic/linux-azure-edge: bug 1842833
bionic/linux-azure/azure-kernel: bug 1842832
  variant: debs

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

Title:
  bionic/linux-azure: 5.0.0-1019.20~18.04.1 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842546
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Promote to Proposed
  phase-changed: Thursday, 12. September 2019 11:51 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  replaces: bug 1842545
  trackers:
bionic/linux-azure-edge: bug 1842833
bionic/linux-azure/azure-kernel: bug 1842832
  variant: debs

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

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


[Kernel-packages] [Bug 1805670] Re: 18.04 LTS - ACPI parsing errors in ZBook G5 Mobile Workstation: issues ex. suspend, touchpad

2019-09-12 Thread Hugo Ferreira
Updated to latest BIOS.

[0.00] DMI: HP HP ZBook Studio G5/8427, BIOS Q71 Ver. 01.08.00
07/15/2019

Same errors as above:

[0.445469] ACPI Error: Field [CAP1] at bit offset/length 64/32 exceeds size 
of target Buffer (64 bits) (20181213/dsopcode-201)
[0.445489] ACPI Error: Method parse/execution failed \_SB._OSC, 
AE_AML_BUFFER_LIMIT (20181213/psparse-531)
[4.938367] ACPI Error: AE_AML_PACKAGE_LIMIT, Index (0x5) is beyond 
end of object (length 0x5) (20181213/exoparg2-396)
[4.938387] ACPI Error: Method parse/execution failed \_TZ.GETP, 
AE_AML_PACKAGE_LIMIT (20181213/psparse-531)
[4.938391] ACPI Error: Method parse/execution failed \_TZ.CHGZ._CRT, 
AE_AML_PACKAGE_LIMIT (20181213/psparse-531)
[4.940322] ACPI Error: AE_AML_PACKAGE_LIMIT, Index (0x5) is beyond 
end of object (length 0x5) (20181213/exoparg2-396)
[4.940340] ACPI Error: Method parse/execution failed \_TZ.GETP, 
AE_AML_PACKAGE_LIMIT (20181213/psparse-531)
[4.940345] ACPI Error: Method parse/execution failed \_TZ.CHGZ._CRT, 
AE_AML_PACKAGE_LIMIT (20181213/psparse-531)
[5.056279] RAS: Correctable Errors collector initialized.
[8.029093] EXT4-fs (nvme0n1p2): re-mounted. Opts: errors=remount-ro
[8.210987] hp_wmi: query 0x4 returned error 0x5
[8.230452] hp_wmi: query 0x4 returned error 0x5
[8.238602] hp_wmi: query 0xd returned error 0x5
[   12.624466] xhci_hcd :00:14.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 4
h

TIA

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

Title:
  18.04 LTS - ACPI parsing errors in ZBook G5 Mobile Workstation: issues
  ex. suspend, touchpad

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Some background information:
  I have a new Ubuntu 18.04 installation that did not go too well.
  The Live-USB installation would hang with ACPi related errors.
  I finally installed (barring a GRUB install error) using the acpi=off kernel 
flag.
  I also tested with acpi=force and no acpi settings (only worked after the 
last kernel update).
  I report here with
  - no changes in the kernel parameters
  - no changes in BIOS except of graphics set to hybrid (Nvidia + Intel) 
otherwise I could not get it to work

  I am following the indications here:
  https://wiki.ubuntu.com/DebuggingACPI

  So here is the initial information I have (kernel version, kernel
  parameters, ACPI errors):

  ..

  uname -a
  Linux gandalf 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=82d8b6b9-1f12-4651--3639a6b76683 ro quiet splash vt.handoff=1

  dmesg | grep -i acpi | grep -i error
  [0.00] ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup 
failure, AE_NOT_FOUND (20170831/dswload-210)
  [0.00] ACPI Error: 1 table load failures, 19 successful 
(20170831/tbxfload-246)
  [0.164845] ACPI Error: Field [CAP1] at bit offset/length 64/32 exceeds 
size of target Buffer (64 bits) (20170831/dsopcode-235)
  [0.164874] ACPI Error: Method parse/execution failed \_SB._OSC, 
AE_AML_BUFFER_LIMIT (20170831/psparse-550)
  [3.528032] ACPI Error: Method parse/execution failed 
\_SB.PCI0.SPI1.FPNT._CRS, AE_AML_INVALID_RESOURCE_TYPE (20170831/psparse-550)
  [3.528042] ACPI Error: Method execution failed \_SB.PCI0.SPI1.FPNT._CRS, 
AE_AML_INVALID_RESOURCE_TYPE (20170831/uteval-103)
  [3.529831] ACPI Error: Method parse/execution failed 
\_SB.PCI0.SPI2.FPNT._CRS, AE_AML_INVALID_RESOURCE_TYPE (20170831/psparse-550)
  [3.529840] ACPI Error: Method execution failed \_SB.PCI0.SPI2.FPNT._CRS, 
AE_AML_INVALID_RESOURCE_TYPE (20170831/uteval-103)
  [4.610629] ACPI Error: Method parse/execution failed \_TZ.GETP, 
AE_AML_PACKAGE_LIMIT (20170831/psparse-550)
  [4.610635] ACPI Error: Method parse/execution failed \_TZ.CHGZ._CRT, 
AE_AML_PACKAGE_LIMIT (20170831/psparse-550)
  [4.611513] ACPI Error: Method parse/execution failed \_TZ.GETP, 
AE_AML_PACKAGE_LIMIT (20170831/psparse-550)
  [4.611518] ACPI Error: Method parse/execution failed \_TZ.CHGZ._CRT, 
AE_AML_PACKAGE_LIMIT (20170831/psparse-550)
  [8.206279] ACPI Error: Needed [Buffer/String/Package], found [Integer] 
85bce4f4 (20170831/exresop-593)
  [8.206309] ACPI Error: Method parse/execution failed \_SB.WMIV.WVPO, 
AE_AML_OPERAND_TYPE (20170831/psparse-550)
  [8.206315] ACPI Error: Method parse/execution failed \_SB.WMIV.WMPV, 
AE_AML_OPERAND_TYPE (20170831/psparse-550)
  [8.210629] ACPI Error: Needed [Buffer/String/Package], found [Integer] 
352a9487 (20170831/exresop-593)
  [8.210660] ACPI Error: Method parse/execution failed \_SB.WMIV.WVPO, 
AE_AML_OPERAND_TYPE (20170831/psparse-550)
  [8.210666] ACPI Error: Method parse/execution 

[Kernel-packages] [Bug 1840236]

2019-09-12 Thread Lakshminarayana-vudum
(In reply to Jani Saarinen from comment #8)
> You mean Lakshmi if 103167 is same?

Sorry, yes it's Bug 103167 .

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

Title:
  Horizontal corrupted line at top of screen caused by framebuffer
  compression

Status in HWE Next:
  New
Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Invalid
Status in linux-oem-osp1 source package in Disco:
  New
Status in linux source package in Eoan:
  Fix Released
Status in linux-oem-osp1 source package in Eoan:
  New

Bug description:
  SRU Justification:

  [Impact]
  On IceLake platforms there might be a thin, horizon strap of corruption
  image at the top of screen randomly after some series of window
  operations and disappears within a second or so. This is found on
  multiple platforms and is quite annonying that results in bad user
  experience.

  [Fix]
  The upstream bug has been filed for previous platforms, e.g. GeminiLake
  for an year or so, still working in progress, and so far this only known
  work-around is to turn off framebuffer compression on affected platforms.

  [Test Case]
  The most easy way is to observe if such corruption appears during the
  transition from GDM to gnome-shell.

  [Regression Risk]
  Low. The work-around for GeminiLake was landed to Linux stable 4.14.125
  and has been backported to B/D.

  === Original Description ==

  This is an follow-up for
  https://bugs.freedesktop.org/show_bug.cgi?id-108085 but found on
  IceLake platforms.

  Right after GDM is login screen is rendered, there might be a thin
  strap of corrupted image at top of the display for a short while. Like
  f-d-o bug 108085, sometimes it can also be reproduced by clicking the
  date/time repeatedly to open and close the calendar several times.
  Etc.

  Known work-around so far is to append kernel boot param
  "i915.enable_fbc=0".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-1018-oem-osp1 5.0.0-1018.20
  ProcVersionSignature: Ubuntu 5.0.0-1018.20-oem-osp1 5.0.18
  Uname: Linux 5.0.0-1018-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 15 16:41:01 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X14
  InstallationDate: Installed on 2019-08-12 (3 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  SourcePackage: linux-signed-oem-osp1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1842802] Re: bionic/linux-oem: 4.15.0-1055.64 -proposed tracker

2019-09-12 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842828
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 12. September 2019 08:32 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,meta:depwait,signed:depwait
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,meta:depwait,signed:depwait
  replaces: bug 1842569
  variant: debs

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

Title:
  bionic/linux-oem: 4.15.0-1055.64 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow 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 will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842828
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 12. September 2019 08:32 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,meta:depwait,signed:depwait
  replaces: bug 1842569
  variant: debs

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

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


[Kernel-packages] [Bug 1842606] Re: trusty/linux-aws: 4.4.0-1053.57 -proposed tracker

2019-09-12 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1842608
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 12. September 2019 09:21 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa main:building
+   promote-to-proposed: Holding -- master bug not ready for proposed
  variant: debs

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

Title:
  trusty/linux-aws: 4.4.0-1053.57 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842608
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 12. September 2019 09:21 UTC
  reason:
promote-to-proposed: Holding -- master bug not ready for proposed
  variant: debs

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

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


[Kernel-packages] [Bug 1840619] Re: skb_warn_bad_offload kernel splat due to CHECKSUM target not compatible with GSO skbs

2019-09-12 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

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

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


** Tags added: verification-needed-xenial

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

Title:
  skb_warn_bad_offload kernel splat due to CHECKSUM target not
  compatible with GSO skbs

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1840619

  [Impact]

  In environments which have CHECKSUM iptables rules set, the following
  kernel call trace will be created when a GSO skb is processed by the
  CHECKSUM target:

  WARNING: CPU: 34 PID: 806048 at 
/build/linux-zdslHp/linux-4.4.0/net/core/dev.c:2456 
skb_warn_bad_offload+0xcf/0x110()
  qr-f78bfdf7-fe: caps=(0x0fdb58e9, 0x0fdb58e9) len=1955 
data_len=479 gso_size=1448 gso_type=1 ip_summed=3
  CPU: 34 PID: 806048 Comm: haproxy Tainted: GW  OE   4.4.0-138-generic 
#164-Ubuntu
  Call Trace:
   dump_stack+0x63/0x90
   warn_slowpath_common+0x82/0xc0
   warn_slowpath_fmt+0x5c/0x80
   ? ___ratelimit+0xa2/0xe0
   skb_warn_bad_offload+0xcf/0x110
   skb_checksum_help+0x185/0x1a0
   checksum_tg+0x22/0x29 [xt_CHECKSUM]
   ipt_do_table+0x301/0x730 [ip_tables]
   ? ipt_do_table+0x349/0x730 [ip_tables]
   iptable_mangle_hook+0x39/0x107 [iptable_mangle]
   nf_iterate+0x68/0x80
   nf_hook_slow+0x73/0xd0
   ip_output+0xcf/0xe0
   ? __ip_flush_pending_frames.isra.43+0x90/0x90
   ip_local_out+0x3b/0x50
   ip_queue_xmit+0x154/0x390
   __tcp_transmit_skb+0x52b/0x9b0
   tcp_write_xmit+0x1dd/0xf50
   __tcp_push_pending_frames+0x31/0xd0
   tcp_push+0xec/0x110
   tcp_sendmsg+0x749/0xba0
   inet_sendmsg+0x6b/0xa0
   sock_sendmsg+0x3e/0x50
   SYSC_sendto+0x101/0x190
   ? __sys_sendmsg+0x51/0x90
   SyS_sendto+0xe/0x10
   entry_SYSCALL_64_fastpath+0x22/0xc1

  The CHECKSUM target does not support GSO skbs, and when a GSO skb is
  passed to skb_checksum_help(), it errors out and
  skb_warn_bad_offload() is called.

  The above call trace was found in a customer environment which has an
  Openstack deployment, with the following sorts of iptables rules set:

  -A neutron-l3-agent-POSTROUTING -o qr-+ -p tcp -m tcp --sport 9697 -j 
CHECKSUM --checksum-fill
  -A neutron-dhcp-age-POSTROUTING -p udp -m udp --dport 68 -j CHECKSUM 
--checksum-fill

  This was causing haproxy running on the node to crash and restart
  every time a GSO skb was processed by the CHECKSUM target.

  I recommend reading the netdev mailing list thread for more details:
  https://www.spinics.net/lists/netdev/msg517366.html

  [Fix]

  This was fixed in 4.19 upstream with the below commit:

  commit 10568f6c5761db24249c610c94d6e44d5505a0ba
  Author: Florian Westphal 
  Date:   Wed Aug 22 11:33:27 2018 +0200
  Subject: netfilter: xt_checksum: ignore gso skbs

  This commit adds a check to see if the current skb is a gso skb, and
  if it is, skips skb_checksum_help(). It then continues on to check if
  the packet uses udp, and if it does, exits early. Otherwise it prints
  a single warning that CHECKSUM should be avoided, and if really
  needed, only for use with outbound udp.

  Note, 10568f6c5761db24249c610c94d6e44d5505a0ba was included in
  upstream stable version 4.18.13, and was backported to bionic in
  4.15.0-58.64 by LP #1836426.

  This patch required minor backporting for 4.4, by slightly adjusting
  the context in the final patch hunk.

  [Testcase]

  You can reproduce this by adding the following iptables rule to the
  mangle table:

  -t mangle -A POSTROUTING -p tcp -m tcp --sport 80 -j CHECKSUM
  --checksum-fill

  and running traffic over port 80 with incorrect checksums in the ip
  header.

  I built a test kernel, which is available here:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf216537-test

  For unpatched kernels, this causes the process which was handling the
  socket to crash, as seen by haproxy crashing on a node in production
  which hits this issue.

  On patched kernels you see the below warning printed to dmesg and no
  crashes occur.

  xt_CHECKSUM: CHECKSUM should be avoided.  If really needed, restrict
  with "-p udp" and only use in OUTPUT

  [Regression Potential]

  The changes are limited only to users which have CHECKSUM rules
  enabled in their iptables configs. Openstack commonly configures such
  rules on deployment, 

[Kernel-packages] [Bug 1842590] Re: xenial/linux-gcp: 4.15.0-1043.45 -proposed tracker

2019-09-12 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

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

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842828
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
- phase: Promote to Proposed
- phase-changed: Thursday, 12. September 2019 08:00 UTC
+ phase: Testing
+ phase-changed: Thursday, 12. September 2019 11:07 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-gcp: bug 1842838
bionic/linux-gke-5.0: bug 1842840
xenial/linux-gcp/gcp-kernel: bug 1842588
xenial/linux-gcp/gke-kernel: bug 1842589
  variant: debs

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

Title:
  xenial/linux-gcp: 4.15.0-1043.45 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842828
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Thursday, 12. September 2019 11:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-gcp: bug 1842838
bionic/linux-gke-5.0: bug 1842840
xenial/linux-gcp/gcp-kernel: bug 1842588
xenial/linux-gcp/gke-kernel: bug 1842589
  variant: debs

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

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


[Kernel-packages] [Bug 1843583] Re: xenial/linux: 4.4.0-163.191 -proposed tracker

2019-09-12 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

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

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

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
+ bugs-spammed: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
- phase: Promote to Proposed
- phase-changed: Thursday, 12. September 2019 08:46 UTC
+ phase: Testing
+ phase-changed: Thursday, 12. September 2019 11:07 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Stalled -- testing FAILED
+   certification-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   verification-testing: Ongoing -- testing in progress
  replaces: 1842608
  trackers:
xenial/linux/pc-kernel: bug 1843581
  variant: debs

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

Title:
  xenial/linux: 4.4.0-163.191 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Thursday, 12. September 2019 11:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  replaces: 1842608
  trackers:
xenial/linux/pc-kernel: bug 1843581
  variant: debs

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

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


[Kernel-packages] [Bug 1842605] Re: xenial/linux-fips: 4.4.0-1020.25 -proposed tracker

2019-09-12 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Committed

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

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1842608
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
- phase: Packaging
- phase-changed: Thursday, 12. September 2019 09:55 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Thursday, 12. September 2019 10:51 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
-   prepare-package-signed: Pending -- package not yet uploaded
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:depwait,signed:depwait
  variant: debs

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

Title:
  xenial/linux-fips: 4.4.0-1020.25 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid

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

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

  -- swm properties --
  kernel-stable-master-bug: 1842608
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 12. September 2019 10:51 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:depwait,signed:depwait
  variant: debs

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

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


[Kernel-packages] [Bug 1842806] Re: bionic/linux-aws: 4.15.0-1049.51 -proposed tracker

2019-09-12 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: In Progress => Incomplete

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842828
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Thursday, 12. September 2019 10:16 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
+   automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  replaces: bug 1842573
  trackers:
bionic/linux-aws-fips: bug 1842804
bionic/linux-aws/aws-kernel: bug 1842803
xenial/linux-aws-hwe: bug 1842572
  variant: debs

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

Title:
  bionic/linux-aws: 4.15.0-1049.51 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842828
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Thursday, 12. September 2019 10:16 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  replaces: bug 1842573
  trackers:
bionic/linux-aws-fips: bug 1842804
bionic/linux-aws/aws-kernel: bug 1842803
xenial/linux-aws-hwe: bug 1842572
  variant: debs

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

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


[Kernel-packages] [Bug 1827314] Re: Ubuntu 19.04 Background and lockscreen image turns into white noise after sleep and wakeup

2019-09-12 Thread Yevhen
*** This bug is a duplicate of bug 1809407 ***
https://bugs.launchpad.net/bugs/1809407

I have same issue on my laptop (Dell Precision 5530) when using nVidia
graphics, with latest official proprietary driver. But it does not
appear when using integrated Intel graphics, everything works fine in
that case.

** Attachment added: "IMG_20190910_130806.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827314/+attachment/5288233/+files/IMG_20190910_130806.jpg

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

Title:
  Ubuntu 19.04 Background and lockscreen image turns into white noise
  after sleep and wakeup

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

Bug description:
  Ubuntu 19.04 Background and lockscreen image turns into white noise after 
sleep and wakeup
  the lock screen is Disco Dingo default image and bg is custom but both turn 
into a noisy broken image
  my laptop is MSI CX627QL
  Core i5 7th gen
  Ram 12 gb

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

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


[Kernel-packages] [Bug 1842806] Re: bionic/linux-aws: 4.15.0-1049.51 -proposed tracker

2019-09-12 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

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

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842828
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
- phase: Promote to Proposed
- phase-changed: Thursday, 12. September 2019 07:55 UTC
+ phase: Testing
+ phase-changed: Thursday, 12. September 2019 10:16 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   verification-testing: Ongoing -- testing in progress
  replaces: bug 1842573
  trackers:
bionic/linux-aws-fips: bug 1842804
bionic/linux-aws/aws-kernel: bug 1842803
xenial/linux-aws-hwe: bug 1842572
  variant: debs

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

Title:
  bionic/linux-aws: 4.15.0-1049.51 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842828
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Thursday, 12. September 2019 10:16 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  replaces: bug 1842573
  trackers:
bionic/linux-aws-fips: bug 1842804
bionic/linux-aws/aws-kernel: bug 1842803
xenial/linux-aws-hwe: bug 1842572
  variant: debs

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

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


[Kernel-packages] [Bug 1843655] Re: Regression in suspend on Lenovo T460s

2019-09-12 Thread Pedro Côrte-Real
The BIOS update probably made no difference. I just had the computer
suspend and then be stuck suspended with the glowing light but no way to
resume. The lid open did not wake it and neither did pressing the power
button. A hard reset (long press power) was needed.

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

Title:
  Regression in suspend on Lenovo T460s

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In one of the recent updates suspend is now sometimes broken on the
  Lenovo T460s. I've updated the BIOS to the latest but the problem
  remains. Sometimes suspend works correctly and other times it just
  fails completely. Before the BIOS update it seemed to be stuck on
  resume and needed to be forced to reset. After the BIOS update it just
  seems to turn off by itself on resume.

  I haven't been able to find anything relevant in the logs. They just
  show normal suspend and then a boot instead of resume. I'm assuming a
  kernel regression but there's also been some systemd updates recently.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-generic 5.0.0.27.28
  ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pedrocr2699 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Sep 12 00:38:59 2019
  InstallationDate: Installed on 2019-05-09 (125 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0090 Validity Sensors, Inc. VFS7500 Touch 
Fingerprint Sensor
   Bus 001 Device 003: ID 5986:0706 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FAS5TS00
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-27-generic 
root=UUID=3819189f-6ddf-4730-b629-f67c85b114a4 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-27-generic N/A
   linux-backports-modules-5.0.0-27-generic  N/A
   linux-firmware1.178.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1CET77W (1.45 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FAS5TS00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1CET77W(1.45):bd08/06/2019:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460s
  dmi.product.name: 20FAS5TS00
  dmi.product.sku: LENOVO_MT_20FA_BU_Think_FM_ThinkPad T460s
  dmi.product.version: ThinkPad T460s
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1842606] Re: trusty/linux-aws: 4.4.0-1053.57 -proposed tracker

2019-09-12 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1842608
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 12. September 2019 09:21 UTC
  reason:
-   promote-to-proposed: Pending -- builds not complete in ppa 
main:building,meta:queued
+   promote-to-proposed: Ongoing -- builds not complete in ppa main:building
  variant: debs

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

Title:
  trusty/linux-aws: 4.4.0-1053.57 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  Confirmed

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

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

  -- swm properties --
  kernel-stable-master-bug: 1842608
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 12. September 2019 09:21 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa main:building
  variant: debs

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

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


[Kernel-packages] [Bug 1842605] Re: xenial/linux-fips: 4.4.0-1020.25 -proposed tracker

2019-09-12 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Invalid

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1842608
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
- phase: Ready for Packaging
- phase-changed: Friday, 06. September 2019 05:34 UTC
+ phase: Packaging
+ phase-changed: Thursday, 12. September 2019 09:55 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
+   prepare-package-signed: Pending -- package not yet uploaded
  variant: debs

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

Title:
  xenial/linux-fips: 4.4.0-1020.25 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid

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

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

  -- swm properties --
  kernel-stable-master-bug: 1842608
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Packaging
  phase-changed: Thursday, 12. September 2019 09:55 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
  variant: debs

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

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


[Kernel-packages] [Bug 1842605] Re: xenial/linux-fips: 4.4.0-1020.25 -proposed tracker

2019-09-12 Thread Marcelo Cerri
** Summary changed:

- xenial/linux-fips:  -proposed tracker
+ xenial/linux-fips: 4.4.0-1020.25 -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) => Marcelo Cerri 
(mhcerri)

** 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) => Marcelo Cerri 
(mhcerri)

** 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) => Marcelo Cerri 
(mhcerri)

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

Title:
  xenial/linux-fips: 4.4.0-1020.25 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid

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

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

  -- swm properties --
  kernel-stable-master-bug: 1842608
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Packaging
  phase-changed: Thursday, 12. September 2019 09:55 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
  variant: debs

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

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


[Kernel-packages] [Bug 1842834] Re: bionic/linux-azure: 5.0.0-1019.20~18.04.1 -proposed tracker

2019-09-12 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1842546
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 12. September 2019 08:10 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,signed:depwait
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,signed:depwait
  replaces: bug 1842545
  trackers:
bionic/linux-azure-edge: bug 1842833
bionic/linux-azure/azure-kernel: bug 1842832
  variant: debs

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

Title:
  bionic/linux-azure: 5.0.0-1019.20~18.04.1 -proposed tracker

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

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

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

  -- swm properties --
  kernel-stable-master-bug: 1842546
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 12. September 2019 08:10 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,signed:depwait
  replaces: bug 1842545
  trackers:
bionic/linux-azure-edge: bug 1842833
bionic/linux-azure/azure-kernel: bug 1842832
  variant: debs

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

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


[Kernel-packages] [Bug 1842590] Re: xenial/linux-gcp: 4.15.0-1043.45 -proposed tracker

2019-09-12 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842828
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Promote to Proposed
  phase-changed: Thursday, 12. September 2019 08:00 UTC
  reason:
-   promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
+   promote-to-proposed: Pending -- package copied to Proposed signed:queued
  trackers:
bionic/linux-gcp: bug 1842838
bionic/linux-gke-5.0: bug 1842840
xenial/linux-gcp/gcp-kernel: bug 1842588
xenial/linux-gcp/gke-kernel: bug 1842589
  variant: debs

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842828
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Promote to Proposed
  phase-changed: Thursday, 12. September 2019 08:00 UTC
  reason:
-   promote-to-proposed: Pending -- package copied to Proposed signed:queued
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  trackers:
bionic/linux-gcp: bug 1842838
bionic/linux-gke-5.0: bug 1842840
xenial/linux-gcp/gcp-kernel: bug 1842588
xenial/linux-gcp/gke-kernel: bug 1842589
  variant: debs

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

Title:
  xenial/linux-gcp: 4.15.0-1043.45 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow 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 will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842828
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Promote to Proposed
  phase-changed: Thursday, 12. September 2019 08:00 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  trackers:
bionic/linux-gcp: bug 1842838
bionic/linux-gke-5.0: bug 1842840
xenial/linux-gcp/gcp-kernel: bug 1842588
xenial/linux-gcp/gke-kernel: bug 1842589
  variant: debs

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

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


[Kernel-packages] [Bug 1843583] Re: xenial/linux: 4.4.0-163.191 -proposed tracker

2019-09-12 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Thursday, 12. September 2019 08:46 UTC
  reason:
-   promote-to-proposed: Pending -- package copied to Proposed signed:queued
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  replaces: 1842608
  trackers:
xenial/linux/pc-kernel: bug 1843581
  variant: debs

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

Title:
  xenial/linux: 4.4.0-163.191 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Thursday, 12. September 2019 08:46 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  replaces: 1842608
  trackers:
xenial/linux/pc-kernel: bug 1843581
  variant: debs

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

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


[Kernel-packages] [Bug 1842606] Re: trusty/linux-aws: 4.4.0-1053.57 -proposed tracker

2019-09-12 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Committed

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1842608
  packages:
main: linux-aws
meta: linux-meta-aws
- phase: Packaging
- phase-changed: Thursday, 12. September 2019 08:30 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Thursday, 12. September 2019 09:21 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
+   promote-to-proposed: Pending -- builds not complete in ppa 
main:building,meta:queued
  variant: debs

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

Title:
  trusty/linux-aws: 4.4.0-1053.57 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  Confirmed

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

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

  -- swm properties --
  kernel-stable-master-bug: 1842608
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 12. September 2019 09:21 UTC
  reason:
promote-to-proposed: Pending -- builds not complete in ppa 
main:building,meta:queued
  variant: debs

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

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


[Kernel-packages] [Bug 1843583] Re: xenial/linux: 4.4.0-163.191 -proposed tracker

2019-09-12 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Thursday, 12. September 2019 08:46 UTC
  reason:
-   promote-to-proposed: Stalled -- review in progress
+   promote-to-proposed: Pending -- package copies requested to Proposed 
meta:missing,signed:missing
  replaces: 1842608
  trackers:
xenial/linux/pc-kernel: bug 1843581
  variant: debs

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Thursday, 12. September 2019 08:46 UTC
  reason:
-   promote-to-proposed: Pending -- package copies requested to Proposed 
meta:missing,signed:missing
+   promote-to-proposed: Pending -- package copied to Proposed signed:queued
  replaces: 1842608
  trackers:
xenial/linux/pc-kernel: bug 1843581
  variant: debs

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

Title:
  xenial/linux: 4.4.0-163.191 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Thursday, 12. September 2019 08:46 UTC
  reason:
promote-to-proposed: Pending -- package copied to Proposed signed:queued
  replaces: 1842608
  trackers:
xenial/linux/pc-kernel: bug 1843581
  variant: debs

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

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


[Kernel-packages] [Bug 1843583] Re: xenial/linux: 4.4.0-163.191 -proposed tracker

2019-09-12 Thread Łukasz Zemczak
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => Fix Committed

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

Title:
  xenial/linux: 4.4.0-163.191 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Thursday, 12. September 2019 08:46 UTC
  reason:
promote-to-proposed: Pending -- package copies requested to Proposed 
meta:missing,signed:missing
  replaces: 1842608
  trackers:
xenial/linux/pc-kernel: bug 1843581
  variant: debs

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

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


[Kernel-packages] [Bug 1842590] Re: xenial/linux-gcp: 4.15.0-1043.45 -proposed tracker

2019-09-12 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842828
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Promote to Proposed
  phase-changed: Thursday, 12. September 2019 08:00 UTC
  reason:
-   promote-to-proposed: Stalled -- review in progress
+   promote-to-proposed: Pending -- package copies requested to Proposed 
main:missing,meta:missing,signed:missing
  trackers:
bionic/linux-gcp: bug 1842838
bionic/linux-gke-5.0: bug 1842840
xenial/linux-gcp/gcp-kernel: bug 1842588
xenial/linux-gcp/gke-kernel: bug 1842589
  variant: debs

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842828
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Promote to Proposed
  phase-changed: Thursday, 12. September 2019 08:00 UTC
  reason:
-   promote-to-proposed: Pending -- package copies requested to Proposed 
main:missing,meta:missing,signed:missing
+   promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
  trackers:
bionic/linux-gcp: bug 1842838
bionic/linux-gke-5.0: bug 1842840
xenial/linux-gcp/gcp-kernel: bug 1842588
xenial/linux-gcp/gke-kernel: bug 1842589
  variant: debs

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

Title:
  xenial/linux-gcp: 4.15.0-1043.45 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow 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 will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842828
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Promote to Proposed
  phase-changed: Thursday, 12. September 2019 08:00 UTC
  reason:
promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
  trackers:
bionic/linux-gcp: bug 1842838
bionic/linux-gke-5.0: bug 1842840
xenial/linux-gcp/gcp-kernel: bug 1842588
xenial/linux-gcp/gke-kernel: bug 1842589
  variant: debs

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

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


[Kernel-packages] [Bug 1843583] Re: xenial/linux: 4.4.0-163.191 -proposed tracker

2019-09-12 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
- phase: Ready for Promote to Proposed
- phase-changed: Thursday, 12. September 2019 01:51 UTC
+ phase: Promote to Proposed
+ phase-changed: Thursday, 12. September 2019 08:46 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Stalled -- review in progress
  replaces: 1842608
  trackers:
xenial/linux/pc-kernel: bug 1843581
  variant: debs

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

Title:
  xenial/linux: 4.4.0-163.191 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Thursday, 12. September 2019 08:46 UTC
  reason:
promote-to-proposed: Stalled -- review in progress
  replaces: 1842608
  trackers:
xenial/linux/pc-kernel: bug 1843581
  variant: debs

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

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


[Kernel-packages] [Bug 1842590] Re: xenial/linux-gcp: 4.15.0-1043.45 -proposed tracker

2019-09-12 Thread Łukasz Zemczak
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => Fix Committed

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

Title:
  xenial/linux-gcp: 4.15.0-1043.45 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow 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 will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842828
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Promote to Proposed
  phase-changed: Thursday, 12. September 2019 08:00 UTC
  reason:
promote-to-proposed: Pending -- package copies requested to Proposed 
main:missing,meta:missing,signed:missing
  trackers:
bionic/linux-gcp: bug 1842838
bionic/linux-gke-5.0: bug 1842840
xenial/linux-gcp/gcp-kernel: bug 1842588
xenial/linux-gcp/gke-kernel: bug 1842589
  variant: debs

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

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


[Kernel-packages] [Bug 1843583] Re: xenial/linux: 4.4.0-163.191 -proposed tracker

2019-09-12 Thread Łukasz Zemczak
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => In Progress

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

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

Title:
  xenial/linux: 4.4.0-163.191 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Thursday, 12. September 2019 08:46 UTC
  reason:
promote-to-proposed: Stalled -- review in progress
  replaces: 1842608
  trackers:
xenial/linux/pc-kernel: bug 1843581
  variant: debs

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

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


[Kernel-packages] [Bug 1842806] Re: bionic/linux-aws: 4.15.0-1049.51 -proposed tracker

2019-09-12 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842828
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Promote to Proposed
  phase-changed: Thursday, 12. September 2019 07:55 UTC
  reason:
-   promote-to-proposed: Pending -- package copies requested to Proposed 
lrm:missing,main:missing,meta:missing
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  replaces: bug 1842573
  trackers:
bionic/linux-aws-fips: bug 1842804
bionic/linux-aws/aws-kernel: bug 1842803
xenial/linux-aws-hwe: bug 1842572
  variant: debs

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

Title:
  bionic/linux-aws: 4.15.0-1049.51 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow 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 will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842828
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Promote to Proposed
  phase-changed: Thursday, 12. September 2019 07:55 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  replaces: bug 1842573
  trackers:
bionic/linux-aws-fips: bug 1842804
bionic/linux-aws/aws-kernel: bug 1842803
xenial/linux-aws-hwe: bug 1842572
  variant: debs

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

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


  1   2   >