[Kernel-packages] [Bug 1811646] Re: x86/kvm: Backport fixup and missing commits

2019-01-14 Thread Juerg Haefliger
** Summary changed:

- x86/kvm:  Backport fixup and missing commits
+ x86/kvm: Backport fixup and missing commits

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

Title:
  x86/kvm: Backport fixup and missing commits

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  == SRU Justification ==

  The update to stable 4.4.168 contains a couple of x86/kvm related
  commits that have later fixup commits in upstream. Also, there are a
  couple of commits in stable 4.4. that we're missing.

  == Fix ==

  Cherry-pick or backport the relevant commits.

  == Regression Potential ==

  Low. The relevant commits have been in upstream for quite a while.

  == Test Case ==

  Not available. It's unclear what the impact is of not having those
  fixups but it's clear from upstream's commit messages that they fix
  real issues.

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

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


[Kernel-packages] [Bug 1810619] Re: Sleep mode doesn't work

2019-01-14 Thread Grentz
> > - no really suspend mode (the battery continue to discharge like the laptop 
> > is in activity)
>How much does it use during suspend? 

About 4 - 6 hours.

> > - resume by touch the keyboard
> This is intended. Both macOS and Windows do this. 
With 4.18-10, I don't have this behavior. Is it right ?

I've read 
https://www.kernel.org/doc/Documentation/admin-guide/pm/sleep-states.rst
$ sudo sh -c 'echo mem > /sys/power/state'
$ sudo sh -c 'echo deep > /sys/power/mem_sleep'

With this two lines, my Dell XPS 13 9370 go in a sleep mode : no really
battery discharge during 5 - 6 hours, resume only with power button or
by opening the screen. The resume take just a more time than before.

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

Title:
  Sleep mode doesn't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my Dell XPS 13 laptop (9370), the sleep mode dosn't work anymore with 
linux-image-4.18.0-13.
  The screen goes off correctly but any touch resume the laptop.

  This is the log :
  Jan  5 11:15:25 skeleton systemd[1]: Reached target Sleep.
  Jan  5 11:15:25 skeleton systemd[1]: Starting Suspend...
  Jan  5 11:15:25 skeleton systemd[1]: Starting Network Manager Script 
Dispatcher Service...
  Jan  5 11:15:25 skeleton systemd-sleep[6229]: Suspending system...
  Jan  5 11:15:25 skeleton kernel: [ 6176.006021] PM: suspend entry (s2idle)
  an  5 11:15:25 skeleton dbus-daemon[1051]: [system] Successfully activated 
service 'org.freedesktop.nm_dispatcher'
  Jan  5 11:15:25 skeleton systemd[1]: Started Network Manager Script 
Dispatcher Service.
  Jan  5 11:15:25 skeleton nm-dispatcher: req:1 'down' [wlp2s0]: new request (1 
scripts)
  Jan  5 11:15:25 skeleton nm-dispatcher: req:1 'down' [wlp2s0]: start running 
ordered scripts...

  [...]
  Resume :

  Jan  5 12:00:02 skeleton kernel: [ 6176.006023] PM: Syncing filesystems ... 
done.
  Jan  5 12:00:02 skeleton kernel: [ 6176.016581] Freezing user space processes 
... (elapsed 0.088 seconds) done.
  Jan  5 12:00:02 skeleton kernel: [ 6176.104653] OOM killer disabled.
  Jan  5 12:00:02 skeleton kernel: [ 6176.104654] Freezing remaining freezable 
tasks ... (elapsed 0.001 seconds) done.
  Jan  5 12:00:02 skeleton kernel: [ 6176.106070] Suspending console(s) (use 
no_console_suspend to debug)
  Jan  5 12:00:02 skeleton kernel: [ 8852.990035] OOM killer enabled.
  Jan  5 12:00:02 skeleton kernel: [ 8852.990037] Restarting tasks ... done.
  Jan  5 12:00:02 skeleton kernel: [ 8853.015639] r8152 2-1.2:1.0 
enxe4b97acfa7e9: carrier on
  Jan  5 12:00:02 skeleton kernel: [ 8853.084055] PM: suspend exit


  
  With linux-image-4.18.0-10, it works correcly (but no with 4.18.0-11 and 
4.18.0-12).
  Thanks,

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

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


[Kernel-packages] [Bug 1811080] Re: Xenial update: 4.4.168 upstream stable release

2019-01-14 Thread Juerg Haefliger
The modifications from the following patches are already present (from previous 
SAUCE/embargoed patches):
  * x86/KVM/VMX: Expose SPEC_CTRL Bit(2) to the guest
  * x86/bugs, KVM: Support the combination of guest and host IBRS

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

Title:
  Xenial update: 4.4.168 upstream stable release

Status in linux package in Ubuntu:
  Invalid

Bug description:
  
  SRU Justification

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

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

  
  Linux 4.4.168
  selftests: Move networking/timestamping from Documentation
  rocker: fix rocker_tlv_put_* functions for KASAN
  staging: speakup: Replace strncpy with memcpy
  matroxfb: fix size of memcpy
  media: dvb-frontends: fix i2c access helpers for KASAN
  proc: do not access cmdline nor environ from file-backed areas
  proc: don't use FOLL_FORCE for reading cmdline and environment
  mm: replace access_remote_vm() write parameter with gup_flags
  mm: replace __access_remote_vm() write parameter with gup_flags
  mm: replace get_user_pages() write/force parameters with gup_flags
  mm: replace get_vaddr_frames() write/force parameters with gup_flags
  mm: replace get_user_pages_locked() write/force parameters with gup_flags
  mm: replace get_user_pages_unlocked() write/force parameters with gup_flags
  mm/nommu.c: Switch __get_user_pages_unlocked() to use __get_user_pages()
  mm: remove write/force parameters from __get_user_pages_unlocked()
  mm: remove write/force parameters from __get_user_pages_locked()
  sr: pass down correctly sized SCSI sense buffer
  swiotlb: clean up reporting
  hugetlbfs: fix bug in pgoff overflow checking
  hugetlbfs: check for pgoff value overflow
  hugetlbfs: fix offset overflow in hugetlbfs mmap
  mm/hugetlb.c: don't call region_abort if region_chg fails
  posix-timers: Sanitize overrun handling
  wil6210: missing length check in wmi_set_ie
  bpf: Prevent memory disambiguation attack
  bpf/verifier: Pass instruction index to check_mem_access() and check_xadd()
  bpf/verifier: Add spi variable to check_stack_write()
  bpf: support 8-byte metafield access
  KVM: SVM: Implement VIRT_SPEC_CTRL support for SSBD
  x86/speculation: Use synthetic bits for IBRS/IBPB/STIBP
  x86/bugs, KVM: Extend speculation control for VIRT_SPEC_CTRL
  KVM: SVM: Move spec control call after restore of GS
  x86/KVM/VMX: Expose SPEC_CTRL Bit(2) to the guest
  x86/bugs, KVM: Support the combination of guest and host IBRS
  x86/uaccess: Use __uaccess_begin_nospec() and uaccess_try_nospec
  x86/usercopy: Replace open coded stac/clac with __uaccess_{begin, end}
  x86: Introduce __uaccess_begin_nospec() and uaccess_try_nospec
  x86: fix SMAP in 32-bit environments
  x86: reorganize SMAP handling in user space accesses
  KVM/x86: Remove indirect MSR op calls from SPEC_CTRL
  KVM/SVM: Allow direct access to MSR_IA32_SPEC_CTRL
  KVM/VMX: Allow direct access to MSR_IA32_SPEC_CTRL
  KVM/VMX: Emulate MSR_IA32_ARCH_CAPABILITIES
  KVM/x86: Add IBPB support
  KVM: VMX: make MSR bitmaps per-VCPU
  KVM: VMX: introduce alloc_loaded_vmcs
  KVM: nVMX: Eliminate vmcs02 pool
  KVM: nVMX: mark vmcs12 pages dirty on L2 exit
  KVM: nVMX: fix msr bitmaps to prevent L2 from accessing L0 x2APIC
  ALSA: pcm: remove SNDRV_PCM_IOCTL1_INFO internal command
  pstore: Convert console write to use ->write_buf
  ocfs2: fix potential use after free
  debugobjects: avoid recursive calls with kmemleak
  hfsplus: do not free node before using
  hfs: do not free node before using
  ocfs2: fix deadlock caused by ocfs2_defrag_extent()
  fscache, cachefiles: remove redundant variable 'cache'
  fscache: fix race between enablement and dropping of object
  xen: xlate_mmu: add missing header to fix 'W=1' warning
  drm/ast: fixed reading monitor EDID not stable issue
  net: hisilicon: remove unexpected free_netdev
  ixgbe: recognize 1000BaseLX SFP modules as 1Gbps
  net: thunderx: fix NULL pointer dereference in nic_remove
  KVM: x86: fix empty-body warnings
  USB: omap_udc: fix USB gadget functionality on Palm Tungsten E
  USB: omap_udc: fix omap_udc_start() on 15xx machines
  USB: omap_udc: fix crashes on probe error and module removal
  USB: omap_udc: use devm_request_irq()
  bpf: fix check of allowed specifiers in bpf_trace_printk
  exportfs: do not read dentry after free
  ASoC: omap-dmic: Add pm_qos handling to avoid overruns with CPU_IDLE
  ASoC: omap-mcpdm: Add pm_qos handling to 

[Kernel-packages] [Bug 1811252] Re: Xenial update: 4.4.169 upstream stable release

2019-01-14 Thread Juerg Haefliger
Added SAUCE patch:
  * UBUNTU: [Config] Remove CONFIG_CIFS_POSIX=y

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

Title:
  Xenial update: 4.4.169 upstream stable release

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  SRU Justification

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

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

  
  Linux 4.4.169
  ALSA: isa/wavefront: prevent some out of bound writes
  rtc: snvs: Add timeouts to avoid kernel lockups
  rtc: snvs: add a missing write sync
  i2c: scmi: Fix probe error on devices with an empty SMB0001 ACPI device node
  i2c: axxia: properly handle master timeout
  cifs: In Kconfig CONFIG_CIFS_POSIX needs depends on legacy (insecure cifs)
  ARM: 8814/1: mm: improve/fix ARM v7_dma_inv_range() unaligned address handling
  mv88e6060: disable hardware level MAC learning
  libata: whitelist all SAMSUNG MZ7KM* solid-state disks
  Input: omap-keypad - fix keyboard debounce configuration
  clk: mmp: Off by one in mmp_clk_add()
  ide: pmac: add of_node_put()
  drivers/tty: add missing of_node_put()
  drivers/sbus/char: add of_node_put()
  sbus: char: add of_node_put()
  SUNRPC: Fix a potential race in xprt_connect()
  bonding: fix 802.3ad state sent to partner when unbinding slave
  ARC: io.h: Implement reads{x}()/writes{x}()
  drm/msm: Grab a vblank reference when waiting for commit_done
  x86/earlyprintk/efi: Fix infinite loop on some screen widths
  scsi: vmw_pscsi: Rearrange code to avoid multiple calls to free_irq during 
unload
  scsi: libiscsi: Fix NULL pointer dereference in iscsi_eh_session_reset
  mac80211_hwsim: fix module init error paths for netlink
  mac80211: Fix condition validating WMM IE
  mac80211: don't WARN on bad WMM parameters from buggy APs
  f2fs: fix a panic caused by NULL flush_cmd_control
  Revert "drm/rockchip: Allow driver to be shutdown on reboot/kexec"
  powerpc/msi: Fix NULL pointer access in teardown code
  tracing: Fix memory leak of instance function hash filters
  tracing: Fix memory leak in set_trigger_filter()
  MMC: OMAP: fix broken MMC on OMAP15XX/OMAP5910/OMAP310
  aio: fix spectre gadget in lookup_ioctx
  pinctrl: sunxi: a83t: Fix IRQ offset typo for PH11
  powerpc/boot: Fix random libfdt related build errors
  timer/debug: Change /proc/timer_list from 0444 to 0400
  lib/interval_tree_test.c: allow users to limit scope of endpoint
  lib/rbtree-test: lower default params
  lib/rbtree_test.c: make input module parameters
  lib/interval_tree_test.c: allow full tree search
  lib/interval_tree_test.c: make test options module parameters

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

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


[Kernel-packages] [Bug 1811080] Re: Xenial update: 4.4.168 upstream stable release

2019-01-14 Thread Juerg Haefliger
The following already present commits are incomplete and need fixing:
  * KVM: SVM: Implement VIRT_SPEC_CTRL support for SSBD
  * x86/uaccess: Use __uaccess_begin_nospec() and uaccess_try_nospec

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

Title:
  Xenial update: 4.4.168 upstream stable release

Status in linux package in Ubuntu:
  Invalid

Bug description:
  
  SRU Justification

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

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

  
  Linux 4.4.168
  selftests: Move networking/timestamping from Documentation
  rocker: fix rocker_tlv_put_* functions for KASAN
  staging: speakup: Replace strncpy with memcpy
  matroxfb: fix size of memcpy
  media: dvb-frontends: fix i2c access helpers for KASAN
  proc: do not access cmdline nor environ from file-backed areas
  proc: don't use FOLL_FORCE for reading cmdline and environment
  mm: replace access_remote_vm() write parameter with gup_flags
  mm: replace __access_remote_vm() write parameter with gup_flags
  mm: replace get_user_pages() write/force parameters with gup_flags
  mm: replace get_vaddr_frames() write/force parameters with gup_flags
  mm: replace get_user_pages_locked() write/force parameters with gup_flags
  mm: replace get_user_pages_unlocked() write/force parameters with gup_flags
  mm/nommu.c: Switch __get_user_pages_unlocked() to use __get_user_pages()
  mm: remove write/force parameters from __get_user_pages_unlocked()
  mm: remove write/force parameters from __get_user_pages_locked()
  sr: pass down correctly sized SCSI sense buffer
  swiotlb: clean up reporting
  hugetlbfs: fix bug in pgoff overflow checking
  hugetlbfs: check for pgoff value overflow
  hugetlbfs: fix offset overflow in hugetlbfs mmap
  mm/hugetlb.c: don't call region_abort if region_chg fails
  posix-timers: Sanitize overrun handling
  wil6210: missing length check in wmi_set_ie
  bpf: Prevent memory disambiguation attack
  bpf/verifier: Pass instruction index to check_mem_access() and check_xadd()
  bpf/verifier: Add spi variable to check_stack_write()
  bpf: support 8-byte metafield access
  KVM: SVM: Implement VIRT_SPEC_CTRL support for SSBD
  x86/speculation: Use synthetic bits for IBRS/IBPB/STIBP
  x86/bugs, KVM: Extend speculation control for VIRT_SPEC_CTRL
  KVM: SVM: Move spec control call after restore of GS
  x86/KVM/VMX: Expose SPEC_CTRL Bit(2) to the guest
  x86/bugs, KVM: Support the combination of guest and host IBRS
  x86/uaccess: Use __uaccess_begin_nospec() and uaccess_try_nospec
  x86/usercopy: Replace open coded stac/clac with __uaccess_{begin, end}
  x86: Introduce __uaccess_begin_nospec() and uaccess_try_nospec
  x86: fix SMAP in 32-bit environments
  x86: reorganize SMAP handling in user space accesses
  KVM/x86: Remove indirect MSR op calls from SPEC_CTRL
  KVM/SVM: Allow direct access to MSR_IA32_SPEC_CTRL
  KVM/VMX: Allow direct access to MSR_IA32_SPEC_CTRL
  KVM/VMX: Emulate MSR_IA32_ARCH_CAPABILITIES
  KVM/x86: Add IBPB support
  KVM: VMX: make MSR bitmaps per-VCPU
  KVM: VMX: introduce alloc_loaded_vmcs
  KVM: nVMX: Eliminate vmcs02 pool
  KVM: nVMX: mark vmcs12 pages dirty on L2 exit
  KVM: nVMX: fix msr bitmaps to prevent L2 from accessing L0 x2APIC
  ALSA: pcm: remove SNDRV_PCM_IOCTL1_INFO internal command
  pstore: Convert console write to use ->write_buf
  ocfs2: fix potential use after free
  debugobjects: avoid recursive calls with kmemleak
  hfsplus: do not free node before using
  hfs: do not free node before using
  ocfs2: fix deadlock caused by ocfs2_defrag_extent()
  fscache, cachefiles: remove redundant variable 'cache'
  fscache: fix race between enablement and dropping of object
  xen: xlate_mmu: add missing header to fix 'W=1' warning
  drm/ast: fixed reading monitor EDID not stable issue
  net: hisilicon: remove unexpected free_netdev
  ixgbe: recognize 1000BaseLX SFP modules as 1Gbps
  net: thunderx: fix NULL pointer dereference in nic_remove
  KVM: x86: fix empty-body warnings
  USB: omap_udc: fix USB gadget functionality on Palm Tungsten E
  USB: omap_udc: fix omap_udc_start() on 15xx machines
  USB: omap_udc: fix crashes on probe error and module removal
  USB: omap_udc: use devm_request_irq()
  bpf: fix check of allowed specifiers in bpf_trace_printk
  exportfs: do not read dentry after free
  ASoC: omap-dmic: Add pm_qos handling to avoid overruns with CPU_IDLE
  ASoC: omap-mcpdm: Add pm_qos handling to avoid under/overruns with 

[Kernel-packages] [Bug 1811646] Re: x86/kvm: Backport fixups and bugfixes

2019-01-14 Thread Juerg Haefliger
** Summary changed:

- x86/kvm:  Backport fixup commits
+ x86/kvm:  Backport fixups and bugfixes

** Summary changed:

- x86/kvm:  Backport fixups and bugfixes
+ x86/kvm:  Backport fixup and missing commits

** Description changed:

  == SRU Justification ==
  
  The update to stable 4.4.168 contains a couple of x86/kvm related
- commits that have later fixup commits in upstream.
+ commits that have later fixup commits in upstream. Also, there are a
+ couple of commits in stable 4.4. that we're missing.
  
  == Fix ==
  
  Cherry-pick or backport the relevant commits.
  
  == Regression Potential ==
  
  Low. The relevant commits have been in upstream for quite a while.
  
  == Test Case ==
  
  Not available. It's unclear what the impact is of not having those
  fixups but it's clear from upstream's commit messages that they fix real
  issues.

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

Title:
  x86/kvm:  Backport fixup and missing commits

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  == SRU Justification ==

  The update to stable 4.4.168 contains a couple of x86/kvm related
  commits that have later fixup commits in upstream. Also, there are a
  couple of commits in stable 4.4. that we're missing.

  == Fix ==

  Cherry-pick or backport the relevant commits.

  == Regression Potential ==

  Low. The relevant commits have been in upstream for quite a while.

  == Test Case ==

  Not available. It's unclear what the impact is of not having those
  fixups but it's clear from upstream's commit messages that they fix
  real issues.

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

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


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

2019-01-14 Thread Christian Weinberger
I just updated to Debian "4.19.0-0.bpo.1-amd64 #1 SMP Debian
4.19.12-1~bpo9+1 (2018-12-30) x86_64 GNU/Linux"

Even without the "rootdelay" boot option, the boot process proceeds now
as it should again.

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

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

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

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

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

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

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

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

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


[Kernel-packages] [Bug 1811646] Re: x86/kvm: Backport fixup commits

2019-01-14 Thread Juerg Haefliger
** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Juerg Haefliger (juergh)

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

Title:
  x86/kvm:  Backport fixup commits

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  == SRU Justification ==

  The update to stable 4.4.168 contains a couple of x86/kvm related
  commits that have later fixup commits in upstream.

  == Fix ==

  Cherry-pick or backport the relevant commits.

  == Regression Potential ==

  Low. The relevant commits have been in upstream for quite a while.

  == Test Case ==

  Not available. It's unclear what the impact is of not having those
  fixups but it's clear from upstream's commit messages that they fix
  real issues.

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

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


[Kernel-packages] [Bug 1811647] Re: Xenial update: 4.4.170 upstream stable release

2019-01-14 Thread Juerg Haefliger
** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Juerg Haefliger (juergh)

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

Title:
  Xenial update: 4.4.170 upstream stable release

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  SRU Justification

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

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

  Linux 4.4.170
  power: supply: olpc_battery: correct the temperature units
  intel_th: msu: Fix an off-by-one in attribute store
  genwqe: Fix size check
  ceph: don't update importing cap's mseq when handing cap export
  iommu/vt-d: Handle domain agaw being less than iommu agaw
  9p/net: put a lower bound on msize
  b43: Fix error in cordic routine
  gfs2: Fix loop in gfs2_rbm_find
  dlm: memory leaks on error path in dlm_user_request()
  dlm: lost put_lkb on error path in receive_convert() and receive_unlock()
  dlm: possible memory leak on error path in create_lkb()
  dlm: fixed memory leaks after failed ls_remove_names allocation
  ALSA: usb-audio: Fix an out-of-bound read in create_composite_quirks
  ALSA: usb-audio: Avoid access before bLength check in build_audio_procunit()
  ALSA: cs46xx: Potential NULL dereference in probe
  crypto: x86/chacha20 - avoid sleeping with preemption disabled
  sunrpc: use SVC_NET() in svcauth_gss_* functions
  sunrpc: fix cache_head leak due to queued request
  mm, devm_memremap_pages: kill mapping "System RAM" support
  mm, devm_memremap_pages: mark devm_memremap_pages() EXPORT_SYMBOL_GPL
  hwpoison, memory_hotplug: allow hwpoisoned pages to be offlined
  fork: record start_time late
  scsi: zfcp: fix posting too many status read buffers leading to adapter 
shutdown
  Input: omap-keypad - fix idle configuration to not block SoC idle states
  scsi: bnx2fc: Fix NULL dereference in error handling
  xfrm: Fix bucket count reported to userspace
  checkstack.pl: fix for aarch64
  Input: restore EV_ABS ABS_RESERVED
  ARM: imx: update the cpu power up timing setting on i.mx6sx
  powerpc: Fix COFF zImage booting on old powermacs
  spi: bcm2835: Unbreak the build of esoteric configs
  x86/kvm/vmx: do not use vm-exit instruction length for fast MMIO when running 
nested
  CIFS: Fix error mapping for SMB2_LOCK command which caused OFD lock problem
  MIPS: Align kernel load address to 64KB
  MIPS: Ensure pmd_present() returns false after pmd_mknotpresent()
  media: vivid: free bitmap_cap when updating std/timings/etc.
  cdc-acm: fix abnormal DATA RX issue for Mediatek Preloader.
  spi: bcm2835: Avoid finishing transfer prematurely in IRQ mode
  spi: bcm2835: Fix book-keeping of DMA termination
  spi: bcm2835: Fix race on DMA termination
  ext4: force inode writes when nfsd calls commit_metadata()
  ext4: fix EXT4_IOC_GROUP_ADD ioctl
  ext4: missing unlock/put_page() in ext4_try_to_write_inline_data()
  ext4: fix possible use after free in ext4_quota_enable
  perf pmu: Suppress potential format-truncation warning
  KVM: x86: Use jmp to invoke kvm_spurious_fault() from .fixup
  Input: elan_i2c - add ACPI ID for touchpad in ASUS Aspire F5-573G
  usb: r8a66597: Fix a possible concurrency use-after-free bug in 
r8a66597_endpoint_disable()
  USB: serial: option: add Fibocom NL678 series
  USB: serial: pl2303: add ids for Hewlett-Packard HP POS pole displays
  ALSA: hda/tegra: clear pending irq handlers
  ALSA: hda: add mute LED support for HP EliteBook 840 G4
  ALSA: emux: Fix potential Spectre v1 vulnerabilities
  ALSA: pcm: Fix potential Spectre v1 vulnerability
  ALSA: emu10k1: Fix potential Spectre v1 vulnerabilities
  ALSA: rme9652: Fix potential Spectre v1 vulnerability
  sock: Make sock->sk_stamp thread-safe
  gro_cell: add napi_disable in gro_cells_destroy
  xen/netfront: tolerate frags with no data
  VSOCK: Send reset control packet when socket is partially bound
  vhost: make sure used idx is seen before log in vhost_add_used_n()
  sctp: initialize sin6_flowinfo for ipv6 addrs in sctp_inet6addr_event
  packet: validate address length if non-zero
  packet: validate address length
  netrom: fix locking in nr_find_socket()
  isdn: fix kernel-infoleak in capi_unlocked_ioctl
  ipv6: explicitly initialize udp6_addr in udp_sock_create6()
  ieee802154: lowpan_header_create check must check daddr
  ibmveth: fix DMA unmap error in ibmveth_xmit_start error path
  ax25: fix a use-after-free in ax25_fillin_cb()
  ipv4: Fix potential Spectre v1 vulnerability
  ip6mr: Fix potential Spectre 

[Kernel-packages] [Bug 1811755] Re: X1 Extreme: only one of the two SSDs is loaded

2019-01-14 Thread Kai-Heng Feng
This commit can fix your issue:

commit 6299358d198a0635da2dd3c4b3ec37789e811e44
Author: James Dingwall 
Date:   Tue Jan 8 10:20:51 2019 -0700

nvme: introduce NVME_QUIRK_IGNORE_DEV_SUBNQN

If a device provides an NQN it is expected to be globally unique.
Unfortunately some firmware revisions for Intel 760p/Pro 7600p devices did
not satisfy this requirement.  In these circumstances if a system has >1
affected device then only one device is enabled.  If this quirk is enabled
then the device supplied subnqn is ignored and we fallback to generating
one as if the field was empty.  In this case we also suppress the version
check so we don't print a warning when the quirk is enabled.

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

Title:
  X1 Extreme: only one of the two SSDs is loaded

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I bought a new Thinkpad X1 Extreme, and had it come with two SSDs, one
  256G and the other 512G with the intention of keeping the windows on
  the 256G disk and using the 512G for linux.

  When dealing with the installer, it only ever saw one of the SSDs. I
  did manged to get bionic installed on the 512, but on boot, sometimes
  it doesn't find the 512G disk and I just get a blank screen.  After a
  hard power-off, and reboot, it drops into the grub selector, and
  choosing linux, it failed again, but this time dropped into a VT.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tim2003 F pulseaudio
   /dev/snd/controlC0:  tim2003 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 15 18:53:34 2019
  InstallationDate: Installed on 2019-01-14 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Beta amd64 (20190109)
  MachineType: LENOVO 20MFCTO1WW
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=9254da2f-0220-4b41-8770-ae4b0df0d114 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET35W (1.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET35W(1.17):bd12/21/2018:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme
  dmi.product.name: 20MFCTO1WW
  dmi.product.version: ThinkPad X1 Extreme
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1811755] Re: X1 Extreme: only one of the two SSDs is loaded

2019-01-14 Thread Brad Figg
** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Anthony Wong (anthonywong)

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

Title:
  X1 Extreme: only one of the two SSDs is loaded

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I bought a new Thinkpad X1 Extreme, and had it come with two SSDs, one
  256G and the other 512G with the intention of keeping the windows on
  the 256G disk and using the 512G for linux.

  When dealing with the installer, it only ever saw one of the SSDs. I
  did manged to get bionic installed on the 512, but on boot, sometimes
  it doesn't find the 512G disk and I just get a blank screen.  After a
  hard power-off, and reboot, it drops into the grub selector, and
  choosing linux, it failed again, but this time dropped into a VT.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tim2003 F pulseaudio
   /dev/snd/controlC0:  tim2003 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 15 18:53:34 2019
  InstallationDate: Installed on 2019-01-14 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Beta amd64 (20190109)
  MachineType: LENOVO 20MFCTO1WW
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=9254da2f-0220-4b41-8770-ae4b0df0d114 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET35W (1.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET35W(1.17):bd12/21/2018:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme
  dmi.product.name: 20MFCTO1WW
  dmi.product.version: ThinkPad X1 Extreme
  dmi.sys.vendor: LENOVO

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

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


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

2019-01-14 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  X1 Extreme: only one of the two SSDs is loaded

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I bought a new Thinkpad X1 Extreme, and had it come with two SSDs, one
  256G and the other 512G with the intention of keeping the windows on
  the 256G disk and using the 512G for linux.

  When dealing with the installer, it only ever saw one of the SSDs. I
  did manged to get bionic installed on the 512, but on boot, sometimes
  it doesn't find the 512G disk and I just get a blank screen.  After a
  hard power-off, and reboot, it drops into the grub selector, and
  choosing linux, it failed again, but this time dropped into a VT.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tim2003 F pulseaudio
   /dev/snd/controlC0:  tim2003 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 15 18:53:34 2019
  InstallationDate: Installed on 2019-01-14 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Beta amd64 (20190109)
  MachineType: LENOVO 20MFCTO1WW
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=9254da2f-0220-4b41-8770-ae4b0df0d114 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET35W (1.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET35W(1.17):bd12/21/2018:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme
  dmi.product.name: 20MFCTO1WW
  dmi.product.version: ThinkPad X1 Extreme
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1811755] [NEW] X1 Extreme: only one of the two SSDs is loaded

2019-01-14 Thread Tim Penhey
Public bug reported:

I bought a new Thinkpad X1 Extreme, and had it come with two SSDs, one
256G and the other 512G with the intention of keeping the windows on the
256G disk and using the 512G for linux.

When dealing with the installer, it only ever saw one of the SSDs. I did
manged to get bionic installed on the 512, but on boot, sometimes it
doesn't find the 512G disk and I just get a blank screen.  After a hard
power-off, and reboot, it drops into the grub selector, and choosing
linux, it failed again, but this time dropped into a VT.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-43-generic 4.15.0-43.46
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  tim2003 F pulseaudio
 /dev/snd/controlC0:  tim2003 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 15 18:53:34 2019
InstallationDate: Installed on 2019-01-14 (0 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Beta amd64 (20190109)
MachineType: LENOVO 20MFCTO1WW
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=9254da2f-0220-4b41-8770-ae4b0df0d114 ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-43-generic N/A
 linux-backports-modules-4.15.0-43-generic  N/A
 linux-firmware 1.173.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/21/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N2EET35W (1.17 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20MFCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32862 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET35W(1.17):bd12/21/2018:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Extreme
dmi.product.name: 20MFCTO1WW
dmi.product.version: ThinkPad X1 Extreme
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug bionic

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

Title:
  X1 Extreme: only one of the two SSDs is loaded

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I bought a new Thinkpad X1 Extreme, and had it come with two SSDs, one
  256G and the other 512G with the intention of keeping the windows on
  the 256G disk and using the 512G for linux.

  When dealing with the installer, it only ever saw one of the SSDs. I
  did manged to get bionic installed on the 512, but on boot, sometimes
  it doesn't find the 512G disk and I just get a blank screen.  After a
  hard power-off, and reboot, it drops into the grub selector, and
  choosing linux, it failed again, but this time dropped into a VT.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tim2003 F pulseaudio
   /dev/snd/controlC0:  tim2003 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 15 18:53:34 2019
  InstallationDate: Installed on 2019-01-14 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Beta amd64 (20190109)
  MachineType: LENOVO 20MFCTO1WW
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=9254da2f-0220-4b41-8770-ae4b0df0d114 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET35W (1.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET35W(1.17):bd12/21/2018:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme
  dmi.product.name: 20MFCTO1WW
  dmi.product.version: ThinkPad X1 Extreme
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1811721] Re: Mainline Kernel Builds Failing for > v4.20 for amd64 on kernel.ubuntu.com

2019-01-14 Thread Robert Strube
Unfortunately the bug appears to be in on the build system that
kernel.ubuntu.com uses, so we'll be unable to provide logs from our
systems.  We did point out the build log on kernel.ubuntu.com that shows
the build errors.

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

Title:
  Mainline Kernel Builds Failing for > v4.20 for amd64 on
  kernel.ubuntu.com

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It appears that mainline kernel builds (on kernel.ubuntu.com) have
  been failing for amd64 since v4.20.1.  Interestingly enough v4.20 was
  able to build successfully.

  Note: this also includes 5.0rc builds as well.

  You can see the build logs here:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20.1/BUILD.LOG.amd64
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20.2/BUILD.LOG.amd64

  Looking at the build logs it appears that the kernel and all the in-
  tree modules build successfully, but the build fails when trying to
  build the proprietary nvidia kernel modules.  With v4.20 building
  these modules does not appear in the log.  Perhaps this build step was
  added more recently?

  Here are the relevant lines from the end of the build log for v4.20.2 (which 
I've also attached):
  
-

  2019-01-10 03:38:12 (105 MB/s) - 'nvidia-kernel-source-
  390_390.87-0ubuntu4_amd64.deb' saved [8433608/8433608]

  II: dkms-build downloading nvidia-390 
(nvidia-dkms-390_390.87-0ubuntu4_amd64.deb)
  --2019-01-10 03:38:13--  
http://us.archive.ubuntu.com/ubuntu/pool/restricted/n/nvidia-graphics-drivers-390/nvidia-dkms-390_390.87-0ubuntu4_amd64.deb
  Resolving us.archive.ubuntu.com (us.archive.ubuntu.com)... 91.189.91.26, 
91.189.91.23, 2001:67c:1562::16, ...
  Connecting to us.archive.ubuntu.com 
(us.archive.ubuntu.com)|91.189.91.26|:80... connected.
  HTTP request sent, awaiting response... 200 OK
  Length: 27288 (27K) [application/x-debian-package]
  Saving to: 'nvidia-dkms-390_390.87-0ubuntu4_amd64.deb'

   0K .. .. ..  100%
  9.46M=0.003s

  2019-01-10 03:38:13 (9.46 MB/s) - 'nvidia-dkms-
  390_390.87-0ubuntu4_amd64.deb' saved [27288/27288]

  linux:BuiltUsing=nvidia-kernel-source-390 (= 390.87-0ubuntu4), 
  II: dkms-build building nvidia-390

  Creating symlink 
/home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/source
 ->
   
/home/kernel/COD/linux/debian/build/build-generic/__dkms/source/nvidia-390.87

  DKMS: add completed.
  applying patch buildfix_kernel_4.18.patch...patching file conftest.sh
  patching file nvidia-drm/nvidia-drm-connector.c
  patching file nvidia-drm/nvidia-drm-encoder.c
  patching file nvidia-drm/nvidia-drm-helper.h
  patching file nvidia-drm/nvidia-drm.Kbuild

  
  Building module:
  cleaning build area...(bad exit status: 2)
  unset ARCH; env NV_VERBOSE=1 'make' -j16 NV_EXCLUDE_BUILD_MODULES='' 
KERNEL_UNAME=4.20.1-042001-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 
SYSSRC=/home/kernel/COD/linux/debian/build/build-generic/__dkms/headers/linux-headers-4.20.1-042001-generic
 LD=/usr/bin/ld.bfd modules.(bad exit status: 2)
  Error! Bad return status for module build on kernel: 4.20.1-042001-generic 
(x86_64)
  Consult 
/home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/build/make.log
 for more information.
  debian/scripts/dkms-build: line 121: 
/home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/4.20.1-042001-generic/*/log/make.log:
 No such file or directory
  make: *** [debian/rules.d/2-binary-arch.mk:201: install-generic] Error 1

  Thanks!
  Rob

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

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


[Kernel-packages] [Bug 1810619] Re: Sleep mode doesn't work

2019-01-14 Thread Kai-Heng Feng
> - no really suspend mode (the battery continue to discharge like the laptop 
> is in activity)
How much does it use during suspend?

> - resume by touch the keyboard
This is intended. Both macOS and Windows do this.

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

Title:
  Sleep mode doesn't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my Dell XPS 13 laptop (9370), the sleep mode dosn't work anymore with 
linux-image-4.18.0-13.
  The screen goes off correctly but any touch resume the laptop.

  This is the log :
  Jan  5 11:15:25 skeleton systemd[1]: Reached target Sleep.
  Jan  5 11:15:25 skeleton systemd[1]: Starting Suspend...
  Jan  5 11:15:25 skeleton systemd[1]: Starting Network Manager Script 
Dispatcher Service...
  Jan  5 11:15:25 skeleton systemd-sleep[6229]: Suspending system...
  Jan  5 11:15:25 skeleton kernel: [ 6176.006021] PM: suspend entry (s2idle)
  an  5 11:15:25 skeleton dbus-daemon[1051]: [system] Successfully activated 
service 'org.freedesktop.nm_dispatcher'
  Jan  5 11:15:25 skeleton systemd[1]: Started Network Manager Script 
Dispatcher Service.
  Jan  5 11:15:25 skeleton nm-dispatcher: req:1 'down' [wlp2s0]: new request (1 
scripts)
  Jan  5 11:15:25 skeleton nm-dispatcher: req:1 'down' [wlp2s0]: start running 
ordered scripts...

  [...]
  Resume :

  Jan  5 12:00:02 skeleton kernel: [ 6176.006023] PM: Syncing filesystems ... 
done.
  Jan  5 12:00:02 skeleton kernel: [ 6176.016581] Freezing user space processes 
... (elapsed 0.088 seconds) done.
  Jan  5 12:00:02 skeleton kernel: [ 6176.104653] OOM killer disabled.
  Jan  5 12:00:02 skeleton kernel: [ 6176.104654] Freezing remaining freezable 
tasks ... (elapsed 0.001 seconds) done.
  Jan  5 12:00:02 skeleton kernel: [ 6176.106070] Suspending console(s) (use 
no_console_suspend to debug)
  Jan  5 12:00:02 skeleton kernel: [ 8852.990035] OOM killer enabled.
  Jan  5 12:00:02 skeleton kernel: [ 8852.990037] Restarting tasks ... done.
  Jan  5 12:00:02 skeleton kernel: [ 8853.015639] r8152 2-1.2:1.0 
enxe4b97acfa7e9: carrier on
  Jan  5 12:00:02 skeleton kernel: [ 8853.084055] PM: suspend exit


  
  With linux-image-4.18.0-10, it works correcly (but no with 4.18.0-11 and 
4.18.0-12).
  Thanks,

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

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


[Kernel-packages] [Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2019-01-14 Thread GrzesiekC
Intel HD Graphics 520 - Internal

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

Title:
  Unable to unlock the desktop session: systemd-logind: got pause for
  13:69

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  When this issue happens, you won't be able to unlock your desktop session (VT 
works fine).
  This happened twice today for me, one is after a suspend, one is just a 
screen lock. Not sure what is the trigger yet.

  Syndrome:
  On the login screen after typing the correct password, you will see a small 
circle keep spinning and that's it. I need to restart my computer to get it 
back to normal.

  
  In the syslog this error message looks fishy:
  Aug  8 10:44:57 Leggiero gnome-shell[2118]: g_array_unref: assertion 'array' 
failed

  
  This is part of the syslog fetching from a VT after a GUI unlock attempt 
(session 24 is the desktop login attempt):

  Aug  8 10:44:42 Leggiero systemd[1]: Started Session 24 of user sam.
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 226:0
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) AIGLX: 
Resuming AIGLX clients after VT switch
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
EDID vendor "AUO", prod id 4204
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Printing DDC gathered Modelines:
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Modeline "1366x768"x0.0   76.20  1366 1404 1426 1590  768 771 777 798 +hsync 
-vsync (47.9 kHz eP)
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Modeline "1366x768"x0.0   76.20  1366 1404 1426 1988  768 771 777 798 +hsync 
-vsync (38.3 kHz e)
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:78
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - 
Dell WMI hotkeys: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - 
Dell WMI hotkeys: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:66
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2  - 
Sleep Button: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2  - 
Sleep Button: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:79
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - 
Integrated_Webcam_HD: Integrate: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - 
Integrated_Webcam_HD: Integrate: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:68
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4  - AT 
Translated Set 2 keyboard: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4  - AT 
Translated Set 2 keyboard: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:67
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3  - 
Power Button: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3  - 
Power Button: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:71
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7  - 
AlpsPS/2 ALPS GlidePoint: is tagged by udev as: Touchpad
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7  - 
AlpsPS/2 ALPS GlidePoint: device is a touchpad
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:72
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8  - 
DELL Wireless hotkeys: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8  - 
DELL Wireless hotkeys: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) libinput: 
PixArt Microsoft USB Optical Mouse: SetProperty on 286 called but device is 
disabled.
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: This driver 
cannot change properties on a disabled device
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:65
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event1  - 
Power Button: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero 

[Kernel-packages] [Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2019-01-14 Thread Pavlushka
Is all the affected one's have external graphics card and made any
switch from external to integrated or from external to integrated then
back or any kind of switch between external and integrated Graphics
Cards?

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

Title:
  Unable to unlock the desktop session: systemd-logind: got pause for
  13:69

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  When this issue happens, you won't be able to unlock your desktop session (VT 
works fine).
  This happened twice today for me, one is after a suspend, one is just a 
screen lock. Not sure what is the trigger yet.

  Syndrome:
  On the login screen after typing the correct password, you will see a small 
circle keep spinning and that's it. I need to restart my computer to get it 
back to normal.

  
  In the syslog this error message looks fishy:
  Aug  8 10:44:57 Leggiero gnome-shell[2118]: g_array_unref: assertion 'array' 
failed

  
  This is part of the syslog fetching from a VT after a GUI unlock attempt 
(session 24 is the desktop login attempt):

  Aug  8 10:44:42 Leggiero systemd[1]: Started Session 24 of user sam.
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 226:0
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) AIGLX: 
Resuming AIGLX clients after VT switch
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
EDID vendor "AUO", prod id 4204
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Printing DDC gathered Modelines:
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Modeline "1366x768"x0.0   76.20  1366 1404 1426 1590  768 771 777 798 +hsync 
-vsync (47.9 kHz eP)
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Modeline "1366x768"x0.0   76.20  1366 1404 1426 1988  768 771 777 798 +hsync 
-vsync (38.3 kHz e)
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:78
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - 
Dell WMI hotkeys: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - 
Dell WMI hotkeys: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:66
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2  - 
Sleep Button: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2  - 
Sleep Button: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:79
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - 
Integrated_Webcam_HD: Integrate: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - 
Integrated_Webcam_HD: Integrate: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:68
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4  - AT 
Translated Set 2 keyboard: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4  - AT 
Translated Set 2 keyboard: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:67
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3  - 
Power Button: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3  - 
Power Button: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:71
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7  - 
AlpsPS/2 ALPS GlidePoint: is tagged by udev as: Touchpad
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7  - 
AlpsPS/2 ALPS GlidePoint: device is a touchpad
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:72
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8  - 
DELL Wireless hotkeys: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8  - 
DELL Wireless hotkeys: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) libinput: 
PixArt Microsoft USB Optical Mouse: SetProperty on 286 called but device is 
disabled.
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: This driver 
cannot change properties on a disabled device
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: 

[Kernel-packages] [Bug 1791904] Re: no detecta

2019-01-14 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/1791904

Title:
  no detecta

Status in linux package in Ubuntu:
  Expired

Bug description:
  no detecta wireless y el bluethoot se desactiva automaticamente

  Google translation:
  it does not detect wireless and the bluethoot is automatically deactivated

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

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


[Kernel-packages] [Bug 1802669] Re: brightness controll didn't work

2019-01-14 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/1802669

Title:
  brightness controll didn't work

Status in linux package in Ubuntu:
  Expired

Bug description:
  ubuntu 16.04.5 lts
  asus x55u with amd c-60 & radeon graphic hd6290

  -> the brightness volume seems be set to 100 % and it is not possible
  to change it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-105.128-generic 4.4.98
  Uname: Linux 4.4.0-105-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Nov 10 19:42:47 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6290] [1002:9807] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Wrestler [Radeon HD 6290] [1043:14e7]
  InstallationDate: Installed on 2017-12-12 (333 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 001 Device 002: ID 1bcf:2883 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X55U
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-105-generic 
root=UUID=38a3e077-62b8-4d4a-98f6-6a371e67801c ro quiet splash acpi_osi=Linux 
acpi_backlight=vendor
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/03/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X55U.410
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X55U
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX55U.410:bd09/03/2012:svnASUSTeKCOMPUTERINC.:pnX55U:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX55U:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X55U
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Nov 10 19:35:24 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: radeon

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

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


[Kernel-packages] [Bug 1798934] Re: Keyboard/tochpad issues

2019-01-14 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/1798934

Title:
  Keyboard/tochpad issues

Status in linux package in Ubuntu:
  Expired

Bug description:
  I have been running Unbuntu 18 for some time now. Everything works
  great. But I do have a few issues.

  Acer Aspire E3-111 with 8MB DDR3 L Memory.

  #1 Keyboards seems to lose its mapping. Backspace/Del and arrow keys
  seem to not work sometimes. I might use the "FN' with Arrow up/Volume
  up. But only sometimes.

  #2 My Touchpad will stop working all of the sudden. So I have a USB
  wireless mouse and it always works. From time to time the mouse might
  start working again.

  I have wanted to do a clean install to see if the problems continue,
  however, I am unable to. For some reason after installing Ubuntu, I am
  not able to access the Bios. Somehow an Admin password has been set. I
  found a site https://bios-pw.org/ that I can get a key and I can
  access however it will not let me chance boot options and save. So I
  am unable to boot from USB or USB-CDRom. I wish I knew how to flash
  the Bios. The only way that I found is to create a Windows 10 boot USB
  and upgrade. But I cannot boot from USB :).  is there a way to
  install/Factory Reset, over Ubuntu from with in? Kind of a clean
  install?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-36-generic 4.15.0-36.39
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  benjamin   3908 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 19 23:25:07 2018
  InstallationDate: Installed on 2017-11-13 (340 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Acer Aspire E3-111
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=153127f8-254f-4133-975b-4a08f470f5f9 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-05-12 (160 days ago)
  dmi.bios.date: 04/11/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.05
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Roxy
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.05:bd04/11/2014:svnAcer:pnAspireE3-111:pvrV1.05:rvnAcer:rnRoxy:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: Aspire E3-111
  dmi.product.version: V1.05
  dmi.sys.vendor: Acer

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

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


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

2019-01-14 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/1801922

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

Status in linux package in Ubuntu:
  Expired

Bug description:
  I've tried to install nvidia-304 and the system told me that was
  impossible, and I couldn't remove the kernel 4.15.0.36.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-36-generic 4.15.0-36.39
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: snd_hda_codec_via snd_hda_codec_generic snd_hda_intel 
snd_hda_codec snd_hda_core snd_hwdep snd_pcm edac_mce_amd kvm_amd snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device k8temp kvm irqbypass 
input_leds serio_raw snd_timer snd soundcore shpchp mac_hid sch_fq_codel 
parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid hid 
nouveau mxm_wmi wmi video i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops drm psmouse pata_acpi forcedeth pata_amd 
sata_nv i2c_nforce2
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jota   1271 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Tue Nov  6 11:44:00 2018
  ErrorMessage: installed linux-image-4.15.0-36-generic package pre-removal 
script subprocess returned error exit status 1
  InstallationDate: Installed on 2018-11-04 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IwConfig:
   lono wireless extensions.
   
   enp0s7no wireless extensions.
  Lsusb:
   Bus 001 Device 025: ID 04e8:6865 Samsung Electronics Co., Ltd GT-I9300 Phone 
[Galaxy S III] (PTP mode)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 192f:0416 Avago Technologies, Pte. ADNS-5700 Optical 
Mouse Controller (3-button)
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=a0615c99-82b5-44b1-8410-4861f5b6b168 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions: grub-pc 2.02-2ubuntu8.7
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.15.0-36-generic 4.15.0-36.39 failed to 
install/upgrade: installed linux-image-4.15.0-36-generic package pre-removal 
script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/21/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: N68-S
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd09/21/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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


[Kernel-packages] [Bug 1801577] Re: package linux-headers-4.4.0-96 4.4.0-96.119 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting confi

2019-01-14 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/1801577

Title:
  package linux-headers-4.4.0-96 4.4.0-96.119 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in linux package in Ubuntu:
  Expired

Bug description:
  Linux Ubuntu mate.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-headers-4.4.0-96 4.4.0-96.119
  ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155
  Uname: Linux 4.4.0-138-generic i686
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   johnnyreb   1872 F...m pulseaudio
   /dev/snd/controlC0:  johnnyreb   1872 F pulseaudio
  Date: Sun Nov  4 08:20:41 2018
  DpkgHistoryLog:
   Start-Date: 2018-11-04  08:19:40
   Commandline: aptdaemon role='role-commit-packages' sender=':1.66'
   Install: ubuntu-advantage-tools:i386 (10ubuntu0.16.04.1, automatic)
   Upgrade: update-manager-core:i386 (1:16.04.14, 1:16.04.15), 
friendly-recovery:i386 (0.2.31ubuntu1, 0.2.31ubuntu2), update-manager:i386 
(1:16.04.14, 1:16.04.15), ubuntu-standard:i386 (1.361.1, 1.361.2), 
ubuntu-minimal:i386 (1.361.1, 1.361.2), dpkg:i386 (1.18.4ubuntu1.4, 
1.18.4ubuntu1.5), python3-update-manager:i386 (1:16.04.14, 1:16.04.15), 
libdpkg-perl:i386 (1.18.4ubuntu1.4, 1.18.4ubuntu1.5), secureboot-db:i386 (1.1, 
1.4~ubuntu0.16.04.1), dpkg-dev:i386 (1.18.4ubuntu1.4, 1.18.4ubuntu1.5)
  DuplicateSignature:
   package:linux-headers-4.4.0-96:4.4.0-96.119
   Processing triggers for mime-support (3.59ubuntu1) ...
   dpkg: error processing package linux-headers-4.4.0-96 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  HibernationDevice: RESUME=UUID=6783c982-9133-4a7b-b7fb-a98cc9f16216
  InstallationDate: Installed on 2016-09-06 (788 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  MachineType: System manufacturer System Product Name
  PackageArchitecture: all
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-138-generic 
root=UUID=f010cd2c-4c9f-4785-b4ce-c0df263752d3 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.18
  SourcePackage: linux
  Title: package linux-headers-4.4.0-96 4.4.0-96.119 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/01/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1221
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5B-Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1221:bd11/01/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Kernel-packages] [Bug 1801537] Re: Mouse input lag and stuttering audio USB ('irq 18: nobody cared')

2019-01-14 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/1801537

Title:
  Mouse input lag and stuttering audio USB ('irq 18: nobody cared')

Status in linux package in Ubuntu:
  Expired

Bug description:
  With both the latest lowlatency kernel on 18.10 (4.18.0-10) and
  previously with 4.15 on 18.04 the system is barely usable due to input
  lag from the mouse and stuttering audio. This only starts a minute or
  two after startup. Despite this graphics performance seems unaffected
  and the CPU usage isn't abnormal. Both my mouse and audio device are
  USB devices, and the dmesg log shows problems with the irq I think is
  associated with the USB controller.

  This issue does not exist in any mainline kernel I've tried -
  4.16.0-041600-lowlatency, 4.18.0-041800-lowlatency,
  4.19.0-041900-lowlatency. This suggests the issue is specific to the
  Ubuntu kernel.

  I've tried booting with the 'irqpoll' option but this didn't make any
  difference.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-lowlatency 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-lowlatency 4.18.12
  Uname: Linux 4.18.0-10-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Sat Nov  3 16:14:59 2018
  HibernationDevice: RESUME=UUID=5aef3b9a-9e9b-4c08-a3e1-f31df4b6e48e
  InstallationDate: Installed on 2012-12-15 (2148 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-lowlatency 
root=UUID=9f8c3efb-2f3f-41f1-955f-146d48b41a16 ro quiet splash vt.handoff=1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-lowlatency N/A
   linux-backports-modules-4.18.0-10-lowlatency  N/A
   linux-firmware1.175
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-11-01 (1 days ago)
  dmi.bios.date: 03/08/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2001
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A87TD/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2001:bd03/08/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A87TD/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Kernel-packages] [Bug 1802026] Re: Kernel bug - possible race or inode issue - 4.15.0-38

2019-01-14 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/1802026

Title:
  Kernel bug - possible race or inode issue - 4.15.0-38

Status in linux package in Ubuntu:
  Expired

Bug description:
  Release: Ubuntu 18.04 
  /proc/version_signature:  Ubuntu 4.15.0-38.41-generic 4.15.18

  
  Issue was triggered when running the following:
  . IO intensive application (steamos)
  . Virtualization application (VMware workstation)
  . Heavy IO between various FS/LVs  atop of MD devices
  . Out of Space situation -  an FS/LV resize was executed to alleviate

  Attached is kern.log which captures the sequence of the Kernel WARNINGS/BUGS
  . Notable items in kern.log (attached) -
  Nov  6 10:05:30 FrankWorkstation0 kernel: [588291.771562] WARNING: CPU: 4 
PID: 15553 at /build/linux-CuEUJv/linux-4.15.0/fs/ext4/inode.c:3892 
ext4_set_page_dirty+0x44/0x60
  Nov  6 15:02:15 FrankWorkstation0 kernel: [606096.787691] WARNING: CPU: 5 
PID: 15552 at /build/linux-CuEUJv/linux-4.15.0/fs/ext4/inode.c:3893 
ext4_set_page_dirty+0x4e/0x60
  Nov  6 15:02:16 FrankWorkstation0 kernel: [606097.800925] kernel BUG at 
/build/linux-CuEUJv/linux-4.15.0/fs/ext4/inode.c:2680!
  Nov  6 15:02:16 FrankWorkstation0 kernel: [606097.853375] WARNING: CPU: 9 
PID: 20503 at /build/linux-CuEUJv/linux-4.15.0/kernel/exit.c:771 
do_exit+0x51/0xb40

  This led to an application crash/halt situation - steamos hung, vmware-vmx 
hung, and during shutdown an unclean power off due to vmware-vmx not allowing a 
clean umount.
  Slight FS corruption occurred.

  
  Please advise if BUG confirmed, or if other items to check.

  unable to attempt to recreat bug - not able to risk data loss on
  working system

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-38-generic 4.15.0-38.41
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  frank  2689 F pulseaudio
   /dev/snd/controlC2:  frank  2689 F pulseaudio
   /dev/snd/controlC1:  frank  2689 F pulseaudio
   /dev/snd/controlC0:  frank  2689 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  6 18:14:59 2018
  HibernationDevice: RESUME=/dev/mapper/FrankWorkstation0--vg-swap_1
  InstallationDate: Installed on 2018-10-26 (11 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Precision 5820 Tower
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=/dev/mapper/hostname--vg-root ro ipv6.disable=1 ipv6.disable=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-38-generic N/A
   linux-backports-modules-4.15.0-38-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/04/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.2
  dmi.board.name: 0X8DXD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.2:bd09/04/2018:svnDellInc.:pnPrecision5820Tower:pvr:rvnDellInc.:rn0X8DXD:rvrA01:cvnDellInc.:ct3:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5820 Tower
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1803353] Re: Display freezes (possible i915 freeze/hang)

2019-01-14 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/1803353

Title:
  Display freezes (possible i915 freeze/hang)

Status in linux package in Ubuntu:
  Expired

Bug description:
  Xorg suddenly stops updating the display and CTRL+ALT+F1 does not
  work. The issue happens randomly and does not seem to be related to
  content being rendered. This time the display hang occurred while I
  was typing in gnome-terminal.

  I can successfully ssh into the system from another computer and run
  ubuntu-bug xorg while the display is frozen.

  Disconnecting the display port cable and reconnecting does not
  successfully restore the image. However, after disconnecting the cable
  and reconnecting, the monitor never resumed from DPMS suspend so the
  signal emitted did in fact change when I disconnected the cable.

  The problem occurs both with official lowlatency Ubuntu kernel and
  custom kernel built from vanilla kernel sources. I haven't found a way
  to deduce if this is in reality caused by kernel, xorg or the
  hardware. However, considering that this happens with many different
  kernel versions, I'd assume this is caused by xorg, instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  Uname: Linux 4.18.0-memalloc-watchdog+ x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,regex,mousepoll,move,resize,imgpng,wall,animation,grid,fade,place,vpswitch,gnomecompat,session,workarounds,expo,scale,ezoom]
  Date: Wed Nov 14 15:23:50 2018
  DistUpgraded: 2016-06-10 11:06:21,514 WARNING no activity on terminal for 300 
seconds (Applying changes)
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca]
  InstallationDate: Installed on 2015-02-23 (1360 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-memalloc-watchdog+ 
root=UUID=254cacdb-f61b-45a6-9885-37afd2b598ce ro libata.noacpi=1 quiet splash 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-06-10 (887 days ago)
  dmi.bios.date: 02/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1101
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1101:bd02/04/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Sep  6 15:40:48 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   41047 
   vendor DEL
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1

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

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


[Kernel-packages] [Bug 1811415] Re: linux-azure: 4.18.0-1008.8 -proposed tracker

2019-01-14 Thread Brad Figg
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-cosmic

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1811406
- phase: Packaging -- uploaded
- phase-changed: Monday, 14. January 2019 23:04 UTC
+ phase: Promote to Proposed -- release to Proposed ready
+ phase-changed: Tuesday, 15. January 2019 03:31 UTC
  reason:
-   promote-to-proposed: Pending -- source package tags missing
+   promote-to-proposed: Pending -- ready for review

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

Title:
  linux-azure: 4.18.0-1008.8 -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 stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Cosmic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811406
  phase: Promote to Proposed -- release to Proposed ready
  phase-changed: Tuesday, 15. January 2019 03:31 UTC
  reason:
promote-to-proposed: Pending -- ready for review

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

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


[Kernel-packages] [Bug 1811415] Re: linux-azure: 4.18.0-1008.8 -proposed tracker

2019-01-14 Thread Brad Figg
** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1811406
  phase: Packaging -- uploaded
  phase-changed: Monday, 14. January 2019 23:04 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete
+   promote-to-proposed: Pending -- source package tags missing

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

Title:
  linux-azure: 4.18.0-1008.8 -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 stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Cosmic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1811406
  phase: Packaging -- uploaded
  phase-changed: Monday, 14. January 2019 23:04 UTC
  reason:
promote-to-proposed: Pending -- source package tags missing

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

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


[Kernel-packages] [Bug 1811566] Re: Backported commit breaks audio (fixed upstream)

2019-01-14 Thread Po-Hsu Lin
** Description changed:

+ == Justification ==
+ Commit 648e921888ad96ea3dc922739e96716ad3225d7f (clk: x86: Stop marking 
clocks as CLK_IS_CRITICAL) backported to Cosmic kernel fixed the bug that keeps 
unused clocks on, but it is breaking the audio support on some Chromebooks 
(Swanky / Clapper/ Gnawty) since we were not using
+ the right clock in the cht_bsw_max98090_ti machine driver.
+ 
+ == Fix ==
+ a182ecd (ASoC: intel: cht_bsw_max98090_ti: Add quirk for boards
+  using pmc_plt_clk_0)
+ 984bfb3 (ASoC: intel: cht_bsw_max98090_ti: Add pmc_plt_clk_0 quirk)
+ 94ea56c (ASoC: intel: cht_bsw_max98090_ti: Add pmc_plt_clk_0 quirk)
+ 
+ These 3 patches can be cherry-picked to Cosmic.
+ 
+ == Test ==
+ Test kernel with these 3 patches could be found in:
+ http://people.canonical.com/~phlin/kernel/lp-1811566-chromebook-Gnawty/
+ 
+ Bug reporter stated that this kernel can fix the audio issue as
+ expected.
+ 
+ == Regression potential ==
+ Low,
+ changes are limited in the cht_bsw_max98090_ti driver with a new DMI based 
quirk table that contains these 3 Chromebook models and some logic to determine 
the right clock to use.
+ 
+ 
  It seems that commit 648e921888ad96ea3dc922739e96716ad3225d7f was
  backported to ubuntu's 4.18 kernel. That commit breaks audio for some
  devices (chromebook gnawty) (from 4.19 on). Now 4.19, 4.20, 5.0 are
  fixed, with patch  on commit:
  
  47148001ae12292984ba1b38d9babefb9a46cd3e
  ASoC: intel: cht_bsw_max98090_ti: Add pmc_plt_clk_0 quirk for Chromebook 
Gnawty
  
  Bug reported:
  
  https://bugzilla.kernel.org/show_bug.cgi?id=201787

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

Title:
  Backported commit breaks audio (fixed upstream)

Status in linux package in Ubuntu:
  In Progress

Bug description:
  == Justification ==
  Commit 648e921888ad96ea3dc922739e96716ad3225d7f (clk: x86: Stop marking 
clocks as CLK_IS_CRITICAL) backported to Cosmic kernel fixed the bug that keeps 
unused clocks on, but it is breaking the audio support on some Chromebooks 
(Swanky / Clapper/ Gnawty) since we were not using
  the right clock in the cht_bsw_max98090_ti machine driver.

  == Fix ==
  a182ecd (ASoC: intel: cht_bsw_max98090_ti: Add quirk for boards
   using pmc_plt_clk_0)
  984bfb3 (ASoC: intel: cht_bsw_max98090_ti: Add pmc_plt_clk_0 quirk)
  94ea56c (ASoC: intel: cht_bsw_max98090_ti: Add pmc_plt_clk_0 quirk)

  These 3 patches can be cherry-picked to Cosmic.

  == Test ==
  Test kernel with these 3 patches could be found in:
  http://people.canonical.com/~phlin/kernel/lp-1811566-chromebook-Gnawty/

  Bug reporter stated that this kernel can fix the audio issue as
  expected.

  == Regression potential ==
  Low,
  changes are limited in the cht_bsw_max98090_ti driver with a new DMI based 
quirk table that contains these 3 Chromebook models and some logic to determine 
the right clock to use.


  It seems that commit 648e921888ad96ea3dc922739e96716ad3225d7f was
  backported to ubuntu's 4.18 kernel. That commit breaks audio for some
  devices (chromebook gnawty) (from 4.19 on). Now 4.19, 4.20, 5.0 are
  fixed, with patch  on commit:

  47148001ae12292984ba1b38d9babefb9a46cd3e
  ASoC: intel: cht_bsw_max98090_ti: Add pmc_plt_clk_0 quirk for Chromebook 
Gnawty

  Bug reported:

  https://bugzilla.kernel.org/show_bug.cgi?id=201787

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

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


[Kernel-packages] [Bug 1810546] Re: AMDGPU VMC page fault with Athlon 200GE APU

2019-01-14 Thread experimancer
I have it too: (random hangups of whole system either under load/idle)
- Ryzen5 2400 G
- Ubuntu 18.04 and 18.10
- kernel 4.18

Log: /var/log/syslog (or kern.log) juts before the freeze, after which
only har reset, power off/on makes ysstem boot agian:

Jan 15 02:34:13 elrond kernel: [  476.185425] gmc_v9_0_process_interrupt: 32 
callbacks suppressed
Jan 15 02:34:13 elrond kernel: [  476.185429] amdgpu :0b:00.0: [gfxhub] VMC 
page fault (src_id:0 ring:24 v
mid:3 pasid:32768)
Jan 15 02:34:13 elrond kernel: [  476.185433] amdgpu :0b:00.0:   at page 
0x00010780a000 from 27
Jan 15 02:34:13 elrond kernel: [  476.185434] amdgpu :0b:00.0: 
VM_L2_PROTECTION_FAULT_STATUS:0x00301031
Jan 15 02:34:13 elrond kernel: [  476.185440] amdgpu :0b:00.0: [gfxhub] VMC 
page fault (src_id:0 ring:24 v
mid:3 pasid:32768)
Jan 15 02:34:13 elrond kernel: [  476.185441] amdgpu :0b:00.0:   at page 
0x00010780b000 from 27
Jan 15 02:34:13 elrond kernel: [  476.185443] amdgpu :0b:00.0: 
VM_L2_PROTECTION_FAULT_STATUS:0x
Jan 15 02:34:13 elrond kernel: [  476.185448] amdgpu :0b:00.0: [gfxhub] VMC 
page fault (src_id:0 ring:24 v
mid:3 pasid:32768)
Jan 15 02:34:13 elrond kernel: [  476.185449] amdgpu :0b:00.0:   at page 
0x000107805000 from 27
Jan 15 02:34:13 elrond kernel: [  476.185450] amdgpu :0b:00.0: 
VM_L2_PROTECTION_FAULT_STATUS:0x
Jan 15 02:34:13 elrond kernel: [  476.185455] amdgpu :0b:00.0: [gfxhub] VMC 
page fault (src_id:0 ring:24 vmid:3 pasid:32768)
Jan 15 02:34:13 elrond kernel: [  476.185457] amdgpu :0b:00.0:   at page 
0x000107806000 from 27
Jan 15 02:34:13 elrond kernel: [  476.185458] amdgpu :0b:00.0: 
VM_L2_PROTECTION_FAULT_STATUS:0x
Jan 15 02:34:13 elrond kernel: [  476.185463] amdgpu :0b:00.0: [gfxhub] VMC 
page fault (src_id:0 ring:24 vmid:3 pasid:32768)
Jan 15 02:34:13 elrond kernel: [  476.185464] amdgpu :0b:00.0:   at page 
0x000107808000 from 27
Jan 15 02:34:13 elrond kernel: [  476.185465] amdgpu :0b:00.0: 
VM_L2_PROTECTION_FAULT_STATUS:0x
Jan 15 02:34:13 elrond kernel: [  476.185470] amdgpu :0b:00.0: [gfxhub] VMC 
page fault (src_id:0 ring:24 vmid:3 pasid:32768)
Jan 15 02:34:13 elrond kernel: [  476.185471] amdgpu :0b:00.0:   at page 
0x000107809000 from 27
Jan 15 02:34:13 elrond kernel: [  476.185473] amdgpu :0b:00.0: 
VM_L2_PROTECTION_FAULT_STATUS:0x
Jan 15 02:34:13 elrond kernel: [  476.185478] amdgpu :0b:00.0: [gfxhub] VMC 
page fault (src_id:0 ring:24 vmid:3 pasid:32768)
Jan 15 02:34:13 elrond kernel: [  476.185479] amdgpu :0b:00.0:   at page 
0x000107803000 from 27
Jan 15 02:34:13 elrond kernel: [  476.185480] amdgpu :0b:00.0: 
VM_L2_PROTECTION_FAULT_STATUS:0x
Jan 15 02:34:13 elrond kernel: [  476.185485] amdgpu :0b:00.0: [gfxhub] VMC 
page fault (src_id:0 ring:24 vmid:3 pasid:32768)
Jan 15 02:34:13 elrond kernel: [  476.185486] amdgpu :0b:00.0:   at page 
0x000107804000 from 27
Jan 15 02:34:13 elrond kernel: [  476.185487] amdgpu :0b:00.0: 
VM_L2_PROTECTION_FAULT_STATUS:0x
Jan 15 02:34:13 elrond kernel: [  476.185492] amdgpu :0b:00.0: [gfxhub] VMC 
page fault (src_id:0 ring:24 vmid:3 pasid:32768)
Jan 15 02:34:13 elrond kernel: [  476.185493] amdgpu :0b:00.0:   at page 
0x000107809000 from 27
Jan 15 02:34:13 elrond kernel: [  476.185494] amdgpu :0b:00.0: 
VM_L2_PROTECTION_FAULT_STATUS:0x
Jan 15 02:34:13 elrond kernel: [  476.185500] amdgpu :0b:00.0: [gfxhub] VMC 
page fault (src_id:0 ring:24 vmid:3 pasid:32768)
Jan 15 02:34:13 elrond kernel: [  476.185501] amdgpu :0b:00.0:   at page 
0x000107808000 from 27
Jan 15 02:34:13 elrond kernel: [  476.185502] amdgpu :0b:00.0: 
VM_L2_PROTECTION_FAULT_STATUS:0x
Jan 15 02:34:23 elrond kernel: [  486.421830] [drm:amdgpu_job_timedout 
[amdgpu]] *ERROR* ring gfx timeout, last signaled seq=41331, last emitted 
seq=41333
Jan 15 02:34:23 elrond kernel: [  486.421834] [drm] GPU recovery disabled.

$ sudo lshw -c video
  *-display 
   description: VGA compatible controller
   product: Advanced Micro Devices, Inc. [AMD/ATI]
   vendor: Advanced Micro Devices, Inc. [AMD/ATI]
   physical id: 0
   bus info: pci@:0b:00.0
   version: c6
   width: 64 bits
   clock: 33MHz
   capabilities: pm pciexpress msi msix vga_controller bus_master cap_list 
rom
   configuration: driver=amdgpu latency=0
   resources: irq:88 memory:e000-efff memory:f000-f01f 
ioport:d000(size=256) memory:fe30-fe37 memory:c-dfff

$ uname -a
Linux elrond 4.18.20-041820-generic #201812030624 SMP Mon Dec 3 11:25:55 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

$ glxinfo | grep Mesa
client glx vendor string: Mesa Project and SGI
OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.2.2
OpenGL version string: 4.4 (Compatibility Profile) Mesa 18.2.2
OpenGL ES profile version string: OpenGL ES 3.2 

[Kernel-packages] [Bug 1810546] Re: AMDGPU VMC page fault with Athlon 200GE APU

2019-01-14 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  AMDGPU VMC page fault with Athlon 200GE APU

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

Bug description:
  System
   - AMD Athlon 200GE
   - Gigabyte GA-B450M-S2H board - latest F2c Firmware
   - Ubuntu 18.04.1 LTS

  Reproducible with kernels 
   - linux-image-generic-hwe-18.04 version 4.18.0.13.63 
   - 
linux-image-unsigned-4.20.0-042000rc4-generic_4.20.0-042000rc4.201812030528_amd64.deb
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2016-08-15 (872 days ago)
  InstallationMedia: Mythbuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Package: linux (not installed)
  Tags:  bionic
  Uname: Linux 4.20.0-042000rc4-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to bionic on 2019-01-03 (1 days ago)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mythfe 2175 F mythfrontend.re
mythfe 2181 F pulseaudio
   /dev/snd/pcmC0D3p:   mythfe 2175 F...m mythfrontend.re
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=/dev/mythnew/swap
  InstallationDate: Installed on 2016-08-15 (872 days ago)
  InstallationMedia: Mythbuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. B450M S2H
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/mythnew-myth_root ro verbose
  ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2019-01-03 (1 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2c
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M S2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2c:bd12/04/2018:svnGigabyteTechnologyCo.,Ltd.:pnB450MS2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MS2H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Kernel-packages] [Bug 1811414] Re: linux-aws: 4.18.0-1008.10 -proposed tracker

2019-01-14 Thread Brad Figg
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-cosmic

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1811406
- phase: Packaging -- uploaded
- phase-changed: Monday, 14. January 2019 23:02 UTC
+ phase: Promote to Proposed -- release to Proposed ready
+ phase-changed: Tuesday, 15. January 2019 02:04 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete
+   promote-to-proposed: Pending -- ready for review

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

Title:
  linux-aws: 4.18.0-1008.10 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811406
  phase: Promote to Proposed -- release to Proposed ready
  phase-changed: Tuesday, 15. January 2019 02:04 UTC
  reason:
promote-to-proposed: Pending -- ready for review

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

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


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

2019-01-14 Thread Daniel van Vugt
OK, if "realtime-scheduling = no" didn't work then at least we still
know that you have:

Pulseaudio:
  Installed - Yes (/usr/bin/pulseaudio)
  Running - No   <---  most likely crashed

so next please:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

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

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

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

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

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

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

[Kernel-packages] [Bug 1804505] Re: Kubuntu 18.04.01 - Ryzen 2400G / AMDGPU - Random system freezes

2019-01-14 Thread experimancer
More info about my system:

$ cat /proc/cpuinfo 
processor   : 0
vendor_id   : AuthenticAMD
cpu family  : 23
model   : 17
model name  : AMD Ryzen 5 2400G with Radeon Vega Graphics
stepping: 0
microcode   : 0x810100b
cpu MHz : 3531.252
cache size  : 512 KB
physical id : 0
siblings: 8
core id : 0
cpu cores   : 4
apicid  : 0
initial apicid  : 0
fpu : yes
fpu_exception   : yes
cpuid level : 13
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf 
pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx 
f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 
3dnowprefetch osvw skinit wdt tce topoext perfctr_core perfctr_nb bpext 
perfctr_llc mwaitx hw_pstate sme ssbd sev ibpb vmmcall fsgsbase bmi1 avx2 smep 
bmi2 rdseed adx smap clflushopt sha_ni xsaveopt xsavec xgetbv1 xsaves clzero 
irperf xsaveerptr arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean 
flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif 
overflow_recov succor smca
bugs: sysret_ss_attrs null_seg spectre_v1 spectre_v2 
spec_store_bypass
bogomips: 7400.52
TLB size: 2560 4K pages
clflush size: 64
cache_alignment : 64
address sizes   : 43 bits physical, 48 bits virtual
power management: ts ttp tm hwpstate eff_freq_ro [13] [14]


$ glxinfo | grep Mesa
client glx vendor string: Mesa Project and SGI
OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.2.2
OpenGL version string: 4.4 (Compatibility Profile) Mesa 18.2.2
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 18.2.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/1804505

Title:
  Kubuntu 18.04.01 - Ryzen 2400G / AMDGPU - Random system freezes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am experiencing some stray lockups which are most likely related to
  AMDGPU. There is no apparent logic in the pattern with wich the system
  hangs and I cannot provide any steps to reproduce the problem. One
  time it happened as I clicked a link in Firefox, new tab opened and
  the system froze. Another time, Firefox was not open and I was about
  to edit a text file by clicking "F4 Edit" in Krusader and the system
  froze. When the system freezes, it is completely unresponsive and
  there are no other options than to reset and reboot. The system
  generates no error reports as far as I can figure out and the only
  apparent info are some entries in the syslog. I have appended relevant
  info below, if further info may be needed please ask :)

  [b]inxi -Fz[/b]

  System:Host: computername Kernel: 4.19.1-041901-generic x86_64 bits: 64 
Desktop: KDE Plasma 5.12.6
 Distro: Ubuntu 18.04.1 LTS
  Machine:   Device: desktop Mobo: ASUSTeK model: PRIME A320M-A v: Rev X.0x 
serial: N/A
 UEFI: American Megatrends v: 4023 date: 08/20/2018
  Batteryhidpp__0: charge: 80% condition: NA/NA Wh
  CPU:   Quad core AMD Ryzen 5 2400G with Radeon Vega Graphics (-MT-MCP-) 
cache: 2048 KB
 clock speeds: max: 3600 MHz 1: 1454 MHz 2: 1418 MHz 3: 1419 MHz 4: 
1419 MHz 5: 1419 MHz 6: 1419 MHz
 7: 1436 MHz 8: 1582 MHz
  Graphics:  Card: Advanced Micro Devices [AMD/ATI] Vega [Radeon Vega 8 Mobile]
 Display Server: x11 (X.Org 1.19.6 ) drivers: ati,amdgpu (unloaded: 
modesetting,fbdev,vesa,radeon)
 Resolution: 1680x1050@59.88hz
 OpenGL: renderer: AMD RAVEN (DRM 3.27.0 / 4.19.1-041901-generic, 
LLVM 6.0.0) version: 4.5 Mesa 18.0.5
  Audio: Card-1 Advanced Micro Devices [AMD] Device 15e3 driver: 
snd_hda_intel
 Card-2 Advanced Micro Devices [AMD/ATI] Device 15de driver: 
snd_hda_intel
 Sound: Advanced Linux Sound Architecture v: k4.19.1-041901-generic
  Network:   Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
Controller driver: r8169
 IF: enp5s0 state: up speed: 100 Mbps duplex: full mac: 
  Drives:HDD Total Size: 250.1GB (26.2% used)
 ID-1: /dev/nvme0n1 model: Samsung_SSD_970_EVO_250GB size: 250.1GB
  Partition: ID-1: / size: 228G used: 61G (29%) fs: ext4 dev: /dev/nvme0n1p2
  RAID:  No RAID devices: /proc/mdstat, md_mod kernel module present
  Sensors:   System Temperatures: cpu: N/A mobo: N/A gpu: 26.0
 Fan Speeds (in rpm): cpu: 0
  Info:  Processes: 232 Uptime: 22 min Memory: 1176.8/6960.8MB Client: 
Shell (bash) inxi: 2.3.56 

  
  [b]SYSLOG[/b]

  Prior to the first relevant entry posted here is a CRON entry @
  13:18:01 which seems unrelated to the issue. All entries where
  preceeded with "Nov 21 13:23:13 

[Kernel-packages] [Bug 1784082] Re: Ubuntu is overheating my laptop

2019-01-14 Thread indigocat
Related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768976

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

Title:
  Ubuntu is overheating my laptop

Status in linux package in Ubuntu:
  Expired

Bug description:
  Ubuntu is overheating my laptop.
  Same problem as 1768976
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768976

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.21
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Sat Jul 28 01:35:57 2018
  InstallationDate: Installed on 2016-06-11 (776 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to bionic on 2018-07-27 (0 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: communitheme:ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2016-06-11 (776 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: ubuntu-release-upgrader (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Tags:  bionic dist-upgrade
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-07-27 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Kernel-packages] [Bug 1803360] Re: Fanless systems with DPTF shutdown before using any passive cooling device

2019-01-14 Thread Launchpad Bug Tracker
This bug was fixed in the package thermald - 1.8.0-1ubuntu1

---
thermald (1.8.0-1ubuntu1) disco; urgency=medium

  * Honor ACPI _CRT for processor thermal zone (LP: #1803360)
There are some new fanless platforms use DPTF's virtual sensor
instead of INT340X devices. Because of that, the _PSV is no
longer in use, at least not directly, hence its value may set
higher then _CRT. To a fanless system that means no cooling
device gets activated before _CRT, so the system will be
considered overheated by Linux kernel, and gets shutdown by the
kernel.  Upstream fix:
 - 97976782dd26 Honor ACPI _CRT for processor thermal zone

 -- Colin King   Mon, 14 Jan 2019 23:29:41
+

** Changed in: thermald (Ubuntu Disco)
   Status: In Progress => Fix Released

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

Title:
  Fanless systems with DPTF shutdown before using any passive cooling
  device

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Xenial:
  New
Status in thermald source package in Bionic:
  New
Status in thermald source package in Cosmic:
  In Progress
Status in thermald source package in Disco:
  Fix Released

Bug description:
  == SRU Justification, Cosmic, Bionic, Xenial ==

  There are some new fanless platforms use DPTF's virtual sensor instead
  of INT340X devices.

  Because of that, the _PSV is no longer in use, at least not directly,
  hence its value may set higher then _CRT. To a fanless system that means
  no cooling device gets activated before _CRT, so the system will be
  considered overheated by Linux kernel, and gets shutdown by the kernel.

  == Fix ==
   
  Upstream fix 
https://github.com/intel/thermal_daemon/commit/97976782dd26b4d592ccb97eb89c2a3a871a22a9

  == Testing ==

  Exercise CPUs on a fanless INT340X device with _CRT ACPI objects and
  try and reach the trip point. Without the fix thermal overrun occurs
  and this trips CPU shutdown. With the fix, thermald will start to
  throttle the system and get it out of the thermal overrun zone.

  == Regression Potential ==

  This modifies the behavior for just INT340X devices with ACPI _CRT
  objects, specifically, now to honor this setting.  This is a small
  subset of devices with these objects and the change will in face make
  thermald catch systems before they hit thermal overrun, so the risk of
  regression is small. This fix also has been reviewed by the thermal
  experts at Intel, so it seems like a very reasonable workaround for
  these specific use cases.

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

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


[Kernel-packages] [Bug 1804505] Re: Kubuntu 18.04.01 - Ryzen 2400G / AMDGPU - Random system freezes

2019-01-14 Thread experimancer
I have it too: (random hangups of whole system either under load/idle)
- Ryzen5 2400 G
- Ubuntu 18.04
- kernel 4.18

$ sudo lshw -c video
  *-display 
   description: VGA compatible controller
   product: Advanced Micro Devices, Inc. [AMD/ATI]
   vendor: Advanced Micro Devices, Inc. [AMD/ATI]
   physical id: 0
   bus info: pci@:0b:00.0
   version: c6
   width: 64 bits
   clock: 33MHz
   capabilities: pm pciexpress msi msix vga_controller bus_master cap_list 
rom
   configuration: driver=amdgpu latency=0
   resources: irq:88 memory:e000-efff memory:f000-f01f 
ioport:d000(size=256) memory:fe30-fe37 memory:c-dfff

$ $ lspci -v
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 15d0
Subsystem: ASUSTeK Computer Inc. Device 876b
Flags: fast devsel

00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Device 15d1
Subsystem: Advanced Micro Devices, Inc. [AMD] Device 15d1
Flags: bus master, fast devsel, latency 0, IRQ 27
Capabilities: 

00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 
00h-0fh) PCIe Dummy Host Bridge
Flags: fast devsel

00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 15d3 (prog-if 00 
[Normal decode])
Flags: bus master, fast devsel, latency 0, IRQ 28
Bus: primary=00, secondary=01, subordinate=09, sec-latency=0
I/O behind bridge: e000-efff
Memory behind bridge: fe40-fe7f
Capabilities: 
Kernel driver in use: pcieport

00:01.6 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 15d3 (prog-if 00 
[Normal decode])
Flags: bus master, fast devsel, latency 0, IRQ 29
Bus: primary=00, secondary=0a, subordinate=0a, sec-latency=0
Memory behind bridge: fe90-fe9f
Capabilities: 
Kernel driver in use: pcieport

00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 
00h-0fh) PCIe Dummy Host Bridge
Flags: fast devsel

00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 15db (prog-if 00 
[Normal decode])
Flags: bus master, fast devsel, latency 0, IRQ 26
Bus: primary=00, secondary=0b, subordinate=0b, sec-latency=0
I/O behind bridge: d000-dfff
Memory behind bridge: fe00-fe3f
Prefetchable memory behind bridge: e000-f01f
Capabilities: 
Kernel driver in use: pcieport

00:08.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 15dc (prog-if 00 
[Normal decode])
Flags: bus master, fast devsel, latency 0, IRQ 26
Bus: primary=00, secondary=0c, subordinate=0c, sec-latency=0
Memory behind bridge: fe80-fe8f
Capabilities: 
Kernel driver in use: pcieport

00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61)
Subsystem: ASUSTeK Computer Inc. FCH SMBus Controller
Flags: 66MHz, medium devsel
Kernel driver in use: piix4_smbus
Kernel modules: i2c_piix4, sp5100_tco

00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
Subsystem: ASUSTeK Computer Inc. FCH LPC Bridge
Flags: bus master, 66MHz, medium devsel, latency 0

00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 15e8
Flags: fast devsel

00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 15e9
Flags: fast devsel

00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 15ea
Flags: fast devsel

00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 15eb
Flags: fast devsel
Kernel driver in use: k10temp
Kernel modules: k10temp

00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 15ec
Flags: fast devsel

00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 15ed
Flags: fast devsel

00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 15ee
Flags: fast devsel

00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 15ef
Flags: fast devsel

01:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] Device 43d0 (rev 01) 
(prog-if 30 [XHCI])
Subsystem: ASMedia Technology Inc. Device 1142
Flags: bus master, fast devsel, latency 0, IRQ 42
Memory at fe7a (64-bit, non-prefetchable) [size=32K]
Capabilities: 
Kernel driver in use: xhci_hcd

01:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] Device 43c8 (rev 
01) (prog-if 01 [AHCI 1.0])
Subsystem: ASMedia Technology Inc. Device 1062
Flags: bus master, fast devsel, latency 0, IRQ 85
Memory at fe78 (32-bit, non-prefetchable) [size=128K]
Expansion ROM at fe70 [disabled] [size=512K]
Capabilities: 
Kernel driver in use: ahci
Kernel modules: ahci

01:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 

[Kernel-packages] [Bug 1811721] Re: Mainline Kernel Builds Failing for > v4.20 for amd64 on kernel.ubuntu.com

2019-01-14 Thread 賴家亨
How do we offer the missing required logs if we are running linux
mainline?

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

Title:
  Mainline Kernel Builds Failing for > v4.20 for amd64 on
  kernel.ubuntu.com

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It appears that mainline kernel builds (on kernel.ubuntu.com) have
  been failing for amd64 since v4.20.1.  Interestingly enough v4.20 was
  able to build successfully.

  Note: this also includes 5.0rc builds as well.

  You can see the build logs here:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20.1/BUILD.LOG.amd64
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20.2/BUILD.LOG.amd64

  Looking at the build logs it appears that the kernel and all the in-
  tree modules build successfully, but the build fails when trying to
  build the proprietary nvidia kernel modules.  With v4.20 building
  these modules does not appear in the log.  Perhaps this build step was
  added more recently?

  Here are the relevant lines from the end of the build log for v4.20.2 (which 
I've also attached):
  
-

  2019-01-10 03:38:12 (105 MB/s) - 'nvidia-kernel-source-
  390_390.87-0ubuntu4_amd64.deb' saved [8433608/8433608]

  II: dkms-build downloading nvidia-390 
(nvidia-dkms-390_390.87-0ubuntu4_amd64.deb)
  --2019-01-10 03:38:13--  
http://us.archive.ubuntu.com/ubuntu/pool/restricted/n/nvidia-graphics-drivers-390/nvidia-dkms-390_390.87-0ubuntu4_amd64.deb
  Resolving us.archive.ubuntu.com (us.archive.ubuntu.com)... 91.189.91.26, 
91.189.91.23, 2001:67c:1562::16, ...
  Connecting to us.archive.ubuntu.com 
(us.archive.ubuntu.com)|91.189.91.26|:80... connected.
  HTTP request sent, awaiting response... 200 OK
  Length: 27288 (27K) [application/x-debian-package]
  Saving to: 'nvidia-dkms-390_390.87-0ubuntu4_amd64.deb'

   0K .. .. ..  100%
  9.46M=0.003s

  2019-01-10 03:38:13 (9.46 MB/s) - 'nvidia-dkms-
  390_390.87-0ubuntu4_amd64.deb' saved [27288/27288]

  linux:BuiltUsing=nvidia-kernel-source-390 (= 390.87-0ubuntu4), 
  II: dkms-build building nvidia-390

  Creating symlink 
/home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/source
 ->
   
/home/kernel/COD/linux/debian/build/build-generic/__dkms/source/nvidia-390.87

  DKMS: add completed.
  applying patch buildfix_kernel_4.18.patch...patching file conftest.sh
  patching file nvidia-drm/nvidia-drm-connector.c
  patching file nvidia-drm/nvidia-drm-encoder.c
  patching file nvidia-drm/nvidia-drm-helper.h
  patching file nvidia-drm/nvidia-drm.Kbuild

  
  Building module:
  cleaning build area...(bad exit status: 2)
  unset ARCH; env NV_VERBOSE=1 'make' -j16 NV_EXCLUDE_BUILD_MODULES='' 
KERNEL_UNAME=4.20.1-042001-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 
SYSSRC=/home/kernel/COD/linux/debian/build/build-generic/__dkms/headers/linux-headers-4.20.1-042001-generic
 LD=/usr/bin/ld.bfd modules.(bad exit status: 2)
  Error! Bad return status for module build on kernel: 4.20.1-042001-generic 
(x86_64)
  Consult 
/home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/build/make.log
 for more information.
  debian/scripts/dkms-build: line 121: 
/home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/4.20.1-042001-generic/*/log/make.log:
 No such file or directory
  make: *** [debian/rules.d/2-binary-arch.mk:201: install-generic] Error 1

  Thanks!
  Rob

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

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


[Kernel-packages] [Bug 1803360] Re: Fanless systems with DPTF shutdown before using any passive cooling device

2019-01-14 Thread Colin Ian King
** Changed in: thermald (Ubuntu Xenial)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: thermald (Ubuntu Bionic)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: thermald (Ubuntu Cosmic)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: thermald (Ubuntu Cosmic)
   Status: New => In Progress

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

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

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

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

Title:
  Fanless systems with DPTF shutdown before using any passive cooling
  device

Status in thermald package in Ubuntu:
  In Progress
Status in thermald source package in Xenial:
  New
Status in thermald source package in Bionic:
  New
Status in thermald source package in Cosmic:
  In Progress
Status in thermald source package in Disco:
  In Progress

Bug description:
  == SRU Justification, Cosmic, Bionic, Xenial ==

  There are some new fanless platforms use DPTF's virtual sensor instead
  of INT340X devices.

  Because of that, the _PSV is no longer in use, at least not directly,
  hence its value may set higher then _CRT. To a fanless system that means
  no cooling device gets activated before _CRT, so the system will be
  considered overheated by Linux kernel, and gets shutdown by the kernel.

  == Fix ==
   
  Upstream fix 
https://github.com/intel/thermal_daemon/commit/97976782dd26b4d592ccb97eb89c2a3a871a22a9

  == Testing ==

  Exercise CPUs on a fanless INT340X device with _CRT ACPI objects and
  try and reach the trip point. Without the fix thermal overrun occurs
  and this trips CPU shutdown. With the fix, thermald will start to
  throttle the system and get it out of the thermal overrun zone.

  == Regression Potential ==

  This modifies the behavior for just INT340X devices with ACPI _CRT
  objects, specifically, now to honor this setting.  This is a small
  subset of devices with these objects and the change will in face make
  thermald catch systems before they hit thermal overrun, so the risk of
  regression is small. This fix also has been reviewed by the thermal
  experts at Intel, so it seems like a very reasonable workaround for
  these specific use cases.

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

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


[Kernel-packages] [Bug 1803360] Re: Fanless systems with DPTF shutdown before using any passive cooling device

2019-01-14 Thread Colin Ian King
** Description changed:

+ == SRU Justification, Cosmic, Bionic, Xenial ==
+ 
  There are some new fanless platforms use DPTF's virtual sensor instead
  of INT340X devices.
  
  Because of that, the _PSV is no longer in use, at least not directly,
  hence its value may set higher then _CRT. To a fanless system that means
  no cooling device gets activated before _CRT, so the system will be
  considered overheated by Linux kernel, and gets shutdown by the kernel.
+ 
+ == Fix ==
+  
+ Upstream fix 
https://github.com/intel/thermal_daemon/commit/97976782dd26b4d592ccb97eb89c2a3a871a22a9
+ 
+ == Testing ==
+ 
+ Exercise CPUs on a fanless INT340X device with _CRT ACPI objects and try
+ and reach the trip point. Without the fix thermal overrun occurs and
+ this trips CPU shutdown. With the fix, thermald will start to throttle
+ the system and get it out of the thermal overrun zone.
+ 
+ == Regression Potential ==
+ 
+ This modifies the behavior for just INT340X devices with ACPI _CRT
+ objects, specifically, now to honor this setting.  This is a small
+ subset of devices with these objects and the change will in face make
+ thermald catch systems before they hit thermal overrun, so the risk of
+ regression is small. This fix also has been reviewed by the thermal
+ experts at Intel, so it seems like a very reasonable workaround for
+ these specific use cases.

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

Title:
  Fanless systems with DPTF shutdown before using any passive cooling
  device

Status in thermald package in Ubuntu:
  In Progress
Status in thermald source package in Xenial:
  New
Status in thermald source package in Bionic:
  New
Status in thermald source package in Cosmic:
  In Progress
Status in thermald source package in Disco:
  In Progress

Bug description:
  == SRU Justification, Cosmic, Bionic, Xenial ==

  There are some new fanless platforms use DPTF's virtual sensor instead
  of INT340X devices.

  Because of that, the _PSV is no longer in use, at least not directly,
  hence its value may set higher then _CRT. To a fanless system that means
  no cooling device gets activated before _CRT, so the system will be
  considered overheated by Linux kernel, and gets shutdown by the kernel.

  == Fix ==
   
  Upstream fix 
https://github.com/intel/thermal_daemon/commit/97976782dd26b4d592ccb97eb89c2a3a871a22a9

  == Testing ==

  Exercise CPUs on a fanless INT340X device with _CRT ACPI objects and
  try and reach the trip point. Without the fix thermal overrun occurs
  and this trips CPU shutdown. With the fix, thermald will start to
  throttle the system and get it out of the thermal overrun zone.

  == Regression Potential ==

  This modifies the behavior for just INT340X devices with ACPI _CRT
  objects, specifically, now to honor this setting.  This is a small
  subset of devices with these objects and the change will in face make
  thermald catch systems before they hit thermal overrun, so the risk of
  regression is small. This fix also has been reviewed by the thermal
  experts at Intel, so it seems like a very reasonable workaround for
  these specific use cases.

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

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


[Kernel-packages] [Bug 1803360] Re: Fanless systems with DPTF shutdown before using any passive cooling device

2019-01-14 Thread Colin Ian King
** Also affects: thermald (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

** Also affects: thermald (Ubuntu Disco)
   Importance: High
 Assignee: Colin Ian King (colin-king)
   Status: In Progress

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

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

Title:
  Fanless systems with DPTF shutdown before using any passive cooling
  device

Status in thermald package in Ubuntu:
  In Progress
Status in thermald source package in Xenial:
  New
Status in thermald source package in Bionic:
  New
Status in thermald source package in Cosmic:
  New
Status in thermald source package in Disco:
  In Progress

Bug description:
  There are some new fanless platforms use DPTF's virtual sensor instead
  of INT340X devices.

  Because of that, the _PSV is no longer in use, at least not directly,
  hence its value may set higher then _CRT. To a fanless system that means
  no cooling device gets activated before _CRT, so the system will be
  considered overheated by Linux kernel, and gets shutdown by the kernel.

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

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


[Kernel-packages] [Bug 1810930] Re: ath10k_pci reports error - WiFi stops working

2019-01-14 Thread Arno N. Uehm
The behaviour is no longer reproducible.

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

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

Title:
  ath10k_pci reports error - WiFi stops working

Status in linux package in Ubuntu:
  Invalid

Bug description:
  After upgrading Ubuntu 16.04.5 LTS from linux 4.4.0-140 to 4.4.0-141 I
  noticed that when issuing larger (several GB) downloads over the WiFi
  the wireless network hangs and cannot be brought to live again (e. g.
  with systemctl restart networking). Rebooting (with and without
  powering off) helps, but the problem reappears as soon as you start
  downloading within minutes.

  So I fear there might be a problem with the latest changes in
  ath10k_pci. When booting 4.4.0-140 again (which is still available
  from the boot-menu) the problem does not appear. Booting 4.4.0.141
  again let's the problem re-appear. Between boots I powered off the
  notebook (Dell XPS13).

  Please be kind . this is my first bug report. If I did something wrong
  or leave something out please tell me, I'll try to get better.

  In parallel I see messages in syslog like this:
  Jan  8 11:32:39 ubuntu kernel: [ 8719.011791] ath10k_pci :3a:00.0: failed 
to receive scan abortion completion: timed out
  Jan  8 11:32:39 ubuntu kernel: [ 8719.011805] ath10k_pci :3a:00.0: failed 
to stop scan: -110
  Jan  8 11:32:39 ubuntu kernel: [ 8719.011812] ath10k_pci :3a:00.0: failed 
to start hw scan: -110
  Jan  8 11:32:39 ubuntu wpa_supplicant[2317]: wlp58s0: CTRL-EVENT-SCAN-FAILED 
ret=-110 retry=1
  Jan  8 11:32:43 ubuntu wpa_supplicant[2317]: wlp58s0: CTRL-EVENT-SCAN-FAILED 
ret=-11 retry=1
  Jan  8 11:32:43 ubuntu kernel: [ 8723.011899] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:32:47 ubuntu kernel: [ 8727.011988] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:32:51 ubuntu kernel: [ 8731.012052] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:32:55 ubuntu kernel: [ 8735.012256] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:32:59 ubuntu kernel: [ 8739.012328] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:03 ubuntu kernel: [ 8743.012433] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:07 ubuntu kernel: [ 8747.012702] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:11 ubuntu kernel: [ 8751.012744] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:15 ubuntu kernel: [ 8755.012917] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:19 ubuntu kernel: [ 8759.013002] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:23 ubuntu kernel: [ 8763.013066] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:27 ubuntu kernel: [ 8767.013085] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:31 ubuntu kernel: [ 8771.013103] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:35 ubuntu kernel: [ 8775.013401] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:39 ubuntu kernel: [ 8779.013286] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:43 ubuntu kernel: [ 8783.013625] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:43 ubuntu wpa_supplicant[2317]: message repeated 15 times: [ 
wlp58s0: CTRL-EVENT-SCAN-FAILED ret=-11 retry=1]
  Jan  8 11:33:46 ubuntu gnome-session[2834]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Jan  8 11:33:47 ubuntu wpa_supplicant[2317]: wlp58s0: CTRL-EVENT-SCAN-FAILED 
ret=-11 retry=1
  Jan  8 11:33:47 ubuntu kernel: [ 8787.013715] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:51 ubuntu kernel: [ 8791.013592] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:55 ubuntu kernel: [ 8795.013699] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:55 ubuntu wpa_supplicant[2317]: message repeated 2 times: [ 
wlp58s0: CTRL-EVENT-SCAN-FAILED ret=-11 retry=1]
  Jan  8 11:33:59 ubuntu wpa_supplicant[2317]: wlp58s0: CTRL-EVENT-SCAN-FAILED 
ret=-11 retry=1
  Jan  8 11:33:59 ubuntu kernel: [ 8799.014036] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:34:03 ubuntu wpa_supplicant[2317]: wlp58s0: CTRL-EVENT-SCAN-FAILED 
ret=-11 retry=1
  Jan  8 11:34:03 ubuntu kernel: [ 8803.014115] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:34:07 ubuntu wpa_supplicant[2317]: wlp58s0: CTRL-EVENT-SCAN-FAILED 
ret=-11 retry=1
  Jan  8 11:34:07 ubuntu kernel: [ 8807.014142] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:34:11 ubuntu wpa_supplicant[2317]: wlp58s0: CTRL-EVENT-SCAN-FAILED 
ret=-11 retry=1
  Jan  8 11:34:11 ubuntu kernel: [ 8811.014251] ath10k_pci :3a:00.0: failed 
to 

[Kernel-packages] [Bug 1803360] Re: Fanless systems with DPTF shutdown before using any passive cooling device

2019-01-14 Thread Colin Ian King
OK, will sort that out this week.

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

Title:
  Fanless systems with DPTF shutdown before using any passive cooling
  device

Status in thermald package in Ubuntu:
  In Progress

Bug description:
  There are some new fanless platforms use DPTF's virtual sensor instead
  of INT340X devices.

  Because of that, the _PSV is no longer in use, at least not directly,
  hence its value may set higher then _CRT. To a fanless system that means
  no cooling device gets activated before _CRT, so the system will be
  considered overheated by Linux kernel, and gets shutdown by the kernel.

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

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


[Kernel-packages] [Bug 1811730] [NEW] Thermald does not set max CPU after reseting the voltage using RAPL

2019-01-14 Thread Pablo Catalina
Public bug reported:

Hi,

I was using Ubuntu 18.10 thermald package, but I noted that, after few
seconds at max CPU usage (max temp), thermald send the signal to RALP to
reduce the voltage of the CPU. It set the freq to minimum (800MHz in my
case). But when the CPU is idle and temp is lowered (35-40ºC) it did not
send the signal to resume normal operation of the CPU.

I compiled the latest version of thermald from git
(https://github.com/intel/thermal_daemon) and now everything works fine.

I started to thought that the problem was the hardware or BIOS problem,
as I disabled the CPU scaling on the BIOS, but intel_pstate continued
doing freq scaling (I think for Turbo mode).

But the real problem was Thermald. The latest version from git works
really fine and it automatically disables and enable the Intel Turbo
state and balance the freqs and fan control fine.

My hardware is a Lenovo Thinkpad P52 with i7-8850H.

I tested it using Ubuntu kernel and Kernel 4.20 optimized for i7
processor but with Ubuntu default config (except processor
family="Core2/newer Xeon", Preemption Model="Preemptible Kernel (Low-
Latency Desktop)" and Timer frequency="1000HZ". (Only changed those
settings from make oldconfig and make deb-pkg).

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: thermald (not installed)
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan 14 23:45:01 2019
InstallationDate: Installed on 2018-12-11 (34 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: thermald
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug cosmic

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

Title:
  Thermald does not set max CPU after reseting the voltage using RAPL

Status in thermald package in Ubuntu:
  New

Bug description:
  Hi,

  I was using Ubuntu 18.10 thermald package, but I noted that, after few
  seconds at max CPU usage (max temp), thermald send the signal to RALP
  to reduce the voltage of the CPU. It set the freq to minimum (800MHz
  in my case). But when the CPU is idle and temp is lowered (35-40ºC) it
  did not send the signal to resume normal operation of the CPU.

  I compiled the latest version of thermald from git
  (https://github.com/intel/thermal_daemon) and now everything works
  fine.

  I started to thought that the problem was the hardware or BIOS
  problem, as I disabled the CPU scaling on the BIOS, but intel_pstate
  continued doing freq scaling (I think for Turbo mode).

  But the real problem was Thermald. The latest version from git works
  really fine and it automatically disables and enable the Intel Turbo
  state and balance the freqs and fan control fine.

  My hardware is a Lenovo Thinkpad P52 with i7-8850H.

  I tested it using Ubuntu kernel and Kernel 4.20 optimized for i7
  processor but with Ubuntu default config (except processor
  family="Core2/newer Xeon", Preemption Model="Preemptible Kernel (Low-
  Latency Desktop)" and Timer frequency="1000HZ". (Only changed those
  settings from make oldconfig and make deb-pkg).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: thermald (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 14 23:45:01 2019
  InstallationDate: Installed on 2018-12-11 (34 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: thermald
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1811730] Re: Thermald does not set max CPU after reseting the voltage using RAPL

2019-01-14 Thread Pablo Catalina
Seems similar (but probably not the same):
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1769236

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

Title:
  Thermald does not set max CPU after reseting the voltage using RAPL

Status in thermald package in Ubuntu:
  New

Bug description:
  Hi,

  I was using Ubuntu 18.10 thermald package, but I noted that, after few
  seconds at max CPU usage (max temp), thermald send the signal to RALP
  to reduce the voltage of the CPU. It set the freq to minimum (800MHz
  in my case). But when the CPU is idle and temp is lowered (35-40ºC) it
  did not send the signal to resume normal operation of the CPU.

  I compiled the latest version of thermald from git
  (https://github.com/intel/thermal_daemon) and now everything works
  fine.

  I started to thought that the problem was the hardware or BIOS
  problem, as I disabled the CPU scaling on the BIOS, but intel_pstate
  continued doing freq scaling (I think for Turbo mode).

  But the real problem was Thermald. The latest version from git works
  really fine and it automatically disables and enable the Intel Turbo
  state and balance the freqs and fan control fine.

  My hardware is a Lenovo Thinkpad P52 with i7-8850H.

  I tested it using Ubuntu kernel and Kernel 4.20 optimized for i7
  processor but with Ubuntu default config (except processor
  family="Core2/newer Xeon", Preemption Model="Preemptible Kernel (Low-
  Latency Desktop)" and Timer frequency="1000HZ". (Only changed those
  settings from make oldconfig and make deb-pkg).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: thermald (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 14 23:45:01 2019
  InstallationDate: Installed on 2018-12-11 (34 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: thermald
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1769236] Re: CPU frequency stuck at minimum value

2019-01-14 Thread Pablo Catalina
Seems similar to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1811730

I fixed the problem using the latest version of thermald from git.

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

Title:
  CPU frequency stuck at minimum value

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

Bug description:
  I installed the Kubuntu variant of Ubuntu 18.04 on a new HP Spectre 13
  laptop.  Performance is poor.  The CPU (an i7-8550U) is running at
  400MHz, and never speeds up, even when running some of the Phoronix
  Test Suite benchmarks.

  I can use cpupower to switch to the "performance" cpufreq governor,
  but cannot change the frequency with either governor.

  Here is the output of some experiments I ran while Phoronix's c-ray test was 
running.
  __

  gjditchf@copperplate:/var/log$ cat /proc/cpuinfo | grep MHz
  cpu MHz : 400.008
  cpu MHz : 400.002
  cpu MHz : 400.002
  cpu MHz : 400.003
  cpu MHz : 400.005
  cpu MHz : 400.003
  cpu MHz : 400.001
  cpu MHz : 400.004

  gjditchf@copperplate:/var/log$ cpupower frequency-info
  analyzing CPU 0:
driver: intel_pstate
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency:  Cannot determine or is not supported.
hardware limits: 400 MHz - 4.00 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 400 MHz and 1.60 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 400 MHz (asserted by call to kernel)
boost state support:
  Supported: yes
  Active: yes

  gjditchf@copperplate:/var/log$ sudo cpupower frequency-set -f 1.60GHz
  Setting cpu: 0
  Error setting new values. Common errors:
  - Do you have proper administration rights? (super-user?)
  - Is the governor you requested available and modprobed?
  - Trying to set an invalid policy?
  - Trying to set a specific frequency, but userspace governor is not available,
 for example because of hardware which cannot be set to a specific frequency
 or because the userspace governor isn't loaded?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri May  4 12:57:25 2018
  InstallationDate: Installed on 2018-04-28 (6 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gjditchf   1190 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-28 (10 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 0bda:564e Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0bda:564f Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre Laptop 13-af0xx
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=ab54f00a-7dd6-4d75-a664-682f777c841c ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin monotone plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/13/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 83A2
  dmi.board.vendor: HP
  dmi.board.version: 55.24
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.06:bd10/13/2017:svnHP:pnHPSpectreLaptop13-af0xx:pvrType1ProductConfigId:rvnHP:rn83A2:rvr55.24:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre Laptop 

[Kernel-packages] [Bug 1811415] Re: linux-azure: 4.18.0-1008.8 -proposed tracker

2019-01-14 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1811406
- phase: Packaging -- packaging in progress
- phase-changed: Monday, 14. January 2019 15:34 UTC
+ phase: Packaging -- uploaded
+ phase-changed: Monday, 14. January 2019 23:04 UTC
  reason:
-   prepare-package-meta: Pending -- package not yet uploaded
-   promote-to-proposed: Pending -- source package tags missing
+   promote-to-proposed: Ongoing -- builds not complete

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

Title:
  linux-azure: 4.18.0-1008.8 -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 stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Cosmic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1811406
  phase: Packaging -- uploaded
  phase-changed: Monday, 14. January 2019 23:04 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete

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

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


[Kernel-packages] [Bug 1811414] Re: linux-aws: 4.18.0-1008.10 -proposed tracker

2019-01-14 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Released

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1811406
- phase: Packaging -- packaging in progress
- phase-changed: Monday, 14. January 2019 11:04 UTC
+ phase: Packaging -- uploaded
+ phase-changed: Monday, 14. January 2019 23:02 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
+   promote-to-proposed: Ongoing -- builds not complete

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

Title:
  linux-aws: 4.18.0-1008.10 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1811406
  phase: Packaging -- uploaded
  phase-changed: Monday, 14. January 2019 23:02 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete

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

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


[Kernel-packages] [Bug 1811545] Re: Immediate resume from suspend when wifi enabled

2019-01-14 Thread Steffen Neumann
Correction, the immediate resume behaviour now 
re-appeared on 4.15.0-42.45.

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

Title:
  Immediate resume from suspend when wifi enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  on a current and update 18.04.01 my 
  Acer TravelMate P648-M/BAD40_SL, BIOS V1.21 07/21/2017
  resumes immediately from suspend. 

  I can successfully enter suspend if I set laptop into flight mode.

  This symptom only appeared the last few days, 
  earlier the same system suspended just fine. 

  There are no differences in  /proc/acpi/wakeup 
  with and without flight mode.

  => What other debugging information would be needed 
 to figure what caused the resume with wifi enabled ?

  Yours, Steffen

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   sneumann   2816 F...m pulseaudio
   /dev/snd/controlC0:  sneumann   2816 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 13 01:41:00 2019
  HibernationDevice: RESUME=UUID=045e8ed5-08d8-46a0-8ed4-606bd3be42a1
  InstallationDate: Installed on 2018-05-17 (240 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Acer TravelMate P648-M
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic 
root=/dev/mapper/lvmssd-bioinic ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: BAD40_SL
  dmi.board.vendor: Acer
  dmi.board.version: V1.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.21
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.21:bd07/21/2017:svnAcer:pnTravelMateP648-M:pvrV1.21:rvnAcer:rnBAD40_SL:rvrV1.21:cvnAcer:ct10:cvrV1.21:
  dmi.product.family: SKL
  dmi.product.name: TravelMate P648-M
  dmi.product.version: V1.21
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1811415] Re: linux-azure: 4.18.0-1008.8 -proposed tracker

2019-01-14 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Released

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1811406
  phase: Packaging -- packaging in progress
  phase-changed: Monday, 14. January 2019 15:34 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: Pending -- source package tags missing

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

Title:
  linux-azure: 4.18.0-1008.8 -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:
  In Progress
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 upload-to-ppa-dnu series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Cosmic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1811406
  phase: Packaging -- packaging in progress
  phase-changed: Monday, 14. January 2019 15:34 UTC
  reason:
prepare-package-meta: Pending -- package not yet uploaded
promote-to-proposed: Pending -- source package tags missing

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

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


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

2019-01-14 Thread Brad Figg
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-bionic

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1811419
- phase: Packaging -- uploaded
- phase-changed: Monday, 14. January 2019 21:31 UTC
+ phase: Promote to Proposed -- release to Proposed ready
+ phase-changed: Monday, 14. January 2019 22:30 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete
+   promote-to-proposed: Pending -- ready for review

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811419
  phase: Promote to Proposed -- release to Proposed ready
  phase-changed: Monday, 14. January 2019 22:30 UTC
  reason:
promote-to-proposed: Pending -- ready for review

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

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


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

2019-01-14 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Released

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1811419
- phase: Packaging -- packaging in progress
- phase-changed: Monday, 14. January 2019 15:32 UTC
+ phase: Packaging -- uploaded
+ phase-changed: Monday, 14. January 2019 21:31 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
+   promote-to-proposed: Ongoing -- builds not complete

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1811419
  phase: Packaging -- uploaded
  phase-changed: Monday, 14. January 2019 21:31 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete

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

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


[Kernel-packages] [Bug 1811721] Re: Mainline Kernel Builds Failing for > v4.20 for amd64 on kernel.ubuntu.com

2019-01-14 Thread Robert Strube
** Summary changed:

- Mainline Kernel Builds Failing for > v4.20.1 for amd64 on kernel.ubuntu.com
+ Mainline Kernel Builds Failing for > v4.20 for amd64 on kernel.ubuntu.com

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

Title:
  Mainline Kernel Builds Failing for > v4.20 for amd64 on
  kernel.ubuntu.com

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It appears that mainline kernel builds (on kernel.ubuntu.com) have
  been failing for amd64 since v4.20.1.  Interestingly enough v4.20 was
  able to build successfully.

  Note: this also includes 5.0rc builds as well.

  You can see the build logs here:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20.1/BUILD.LOG.amd64
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20.2/BUILD.LOG.amd64

  Looking at the build logs it appears that the kernel and all the in-
  tree modules build successfully, but the build fails when trying to
  build the proprietary nvidia kernel modules.  With v4.20 building
  these modules does not appear in the log.  Perhaps this build step was
  added more recently?

  Here are the relevant lines from the end of the build log for v4.20.2 (which 
I've also attached):
  
-

  2019-01-10 03:38:12 (105 MB/s) - 'nvidia-kernel-source-
  390_390.87-0ubuntu4_amd64.deb' saved [8433608/8433608]

  II: dkms-build downloading nvidia-390 
(nvidia-dkms-390_390.87-0ubuntu4_amd64.deb)
  --2019-01-10 03:38:13--  
http://us.archive.ubuntu.com/ubuntu/pool/restricted/n/nvidia-graphics-drivers-390/nvidia-dkms-390_390.87-0ubuntu4_amd64.deb
  Resolving us.archive.ubuntu.com (us.archive.ubuntu.com)... 91.189.91.26, 
91.189.91.23, 2001:67c:1562::16, ...
  Connecting to us.archive.ubuntu.com 
(us.archive.ubuntu.com)|91.189.91.26|:80... connected.
  HTTP request sent, awaiting response... 200 OK
  Length: 27288 (27K) [application/x-debian-package]
  Saving to: 'nvidia-dkms-390_390.87-0ubuntu4_amd64.deb'

   0K .. .. ..  100%
  9.46M=0.003s

  2019-01-10 03:38:13 (9.46 MB/s) - 'nvidia-dkms-
  390_390.87-0ubuntu4_amd64.deb' saved [27288/27288]

  linux:BuiltUsing=nvidia-kernel-source-390 (= 390.87-0ubuntu4), 
  II: dkms-build building nvidia-390

  Creating symlink 
/home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/source
 ->
   
/home/kernel/COD/linux/debian/build/build-generic/__dkms/source/nvidia-390.87

  DKMS: add completed.
  applying patch buildfix_kernel_4.18.patch...patching file conftest.sh
  patching file nvidia-drm/nvidia-drm-connector.c
  patching file nvidia-drm/nvidia-drm-encoder.c
  patching file nvidia-drm/nvidia-drm-helper.h
  patching file nvidia-drm/nvidia-drm.Kbuild

  
  Building module:
  cleaning build area...(bad exit status: 2)
  unset ARCH; env NV_VERBOSE=1 'make' -j16 NV_EXCLUDE_BUILD_MODULES='' 
KERNEL_UNAME=4.20.1-042001-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 
SYSSRC=/home/kernel/COD/linux/debian/build/build-generic/__dkms/headers/linux-headers-4.20.1-042001-generic
 LD=/usr/bin/ld.bfd modules.(bad exit status: 2)
  Error! Bad return status for module build on kernel: 4.20.1-042001-generic 
(x86_64)
  Consult 
/home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/build/make.log
 for more information.
  debian/scripts/dkms-build: line 121: 
/home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/4.20.1-042001-generic/*/log/make.log:
 No such file or directory
  make: *** [debian/rules.d/2-binary-arch.mk:201: install-generic] Error 1

  Thanks!
  Rob

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

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


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

2019-01-14 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 1811721

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

Title:
  Mainline Kernel Builds Failing for > v4.20 for amd64 on
  kernel.ubuntu.com

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It appears that mainline kernel builds (on kernel.ubuntu.com) have
  been failing for amd64 since v4.20.1.  Interestingly enough v4.20 was
  able to build successfully.

  Note: this also includes 5.0rc builds as well.

  You can see the build logs here:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20.1/BUILD.LOG.amd64
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20.2/BUILD.LOG.amd64

  Looking at the build logs it appears that the kernel and all the in-
  tree modules build successfully, but the build fails when trying to
  build the proprietary nvidia kernel modules.  With v4.20 building
  these modules does not appear in the log.  Perhaps this build step was
  added more recently?

  Here are the relevant lines from the end of the build log for v4.20.2 (which 
I've also attached):
  
-

  2019-01-10 03:38:12 (105 MB/s) - 'nvidia-kernel-source-
  390_390.87-0ubuntu4_amd64.deb' saved [8433608/8433608]

  II: dkms-build downloading nvidia-390 
(nvidia-dkms-390_390.87-0ubuntu4_amd64.deb)
  --2019-01-10 03:38:13--  
http://us.archive.ubuntu.com/ubuntu/pool/restricted/n/nvidia-graphics-drivers-390/nvidia-dkms-390_390.87-0ubuntu4_amd64.deb
  Resolving us.archive.ubuntu.com (us.archive.ubuntu.com)... 91.189.91.26, 
91.189.91.23, 2001:67c:1562::16, ...
  Connecting to us.archive.ubuntu.com 
(us.archive.ubuntu.com)|91.189.91.26|:80... connected.
  HTTP request sent, awaiting response... 200 OK
  Length: 27288 (27K) [application/x-debian-package]
  Saving to: 'nvidia-dkms-390_390.87-0ubuntu4_amd64.deb'

   0K .. .. ..  100%
  9.46M=0.003s

  2019-01-10 03:38:13 (9.46 MB/s) - 'nvidia-dkms-
  390_390.87-0ubuntu4_amd64.deb' saved [27288/27288]

  linux:BuiltUsing=nvidia-kernel-source-390 (= 390.87-0ubuntu4), 
  II: dkms-build building nvidia-390

  Creating symlink 
/home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/source
 ->
   
/home/kernel/COD/linux/debian/build/build-generic/__dkms/source/nvidia-390.87

  DKMS: add completed.
  applying patch buildfix_kernel_4.18.patch...patching file conftest.sh
  patching file nvidia-drm/nvidia-drm-connector.c
  patching file nvidia-drm/nvidia-drm-encoder.c
  patching file nvidia-drm/nvidia-drm-helper.h
  patching file nvidia-drm/nvidia-drm.Kbuild

  
  Building module:
  cleaning build area...(bad exit status: 2)
  unset ARCH; env NV_VERBOSE=1 'make' -j16 NV_EXCLUDE_BUILD_MODULES='' 
KERNEL_UNAME=4.20.1-042001-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 
SYSSRC=/home/kernel/COD/linux/debian/build/build-generic/__dkms/headers/linux-headers-4.20.1-042001-generic
 LD=/usr/bin/ld.bfd modules.(bad exit status: 2)
  Error! Bad return status for module build on kernel: 4.20.1-042001-generic 
(x86_64)
  Consult 
/home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/build/make.log
 for more information.
  debian/scripts/dkms-build: line 121: 
/home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/4.20.1-042001-generic/*/log/make.log:
 No such file or directory
  make: *** [debian/rules.d/2-binary-arch.mk:201: install-generic] Error 1

  Thanks!
  Rob

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

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


[Kernel-packages] [Bug 1811721] [NEW] Mainline Kernel Builds Failing for > v4.20 for amd64 on kernel.ubuntu.com

2019-01-14 Thread Robert Strube
Public bug reported:

It appears that mainline kernel builds (on kernel.ubuntu.com) have been
failing for amd64 since v4.20.1.  Interestingly enough v4.20 was able to
build successfully.

Note: this also includes 5.0rc builds as well.

You can see the build logs here:

https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20.1/BUILD.LOG.amd64
https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20.2/BUILD.LOG.amd64

Looking at the build logs it appears that the kernel and all the in-tree
modules build successfully, but the build fails when trying to build the
proprietary nvidia kernel modules.  With v4.20 building these modules
does not appear in the log.  Perhaps this build step was added more
recently?

Here are the relevant lines from the end of the build log for v4.20.2 (which 
I've also attached):
-

2019-01-10 03:38:12 (105 MB/s) - 'nvidia-kernel-source-
390_390.87-0ubuntu4_amd64.deb' saved [8433608/8433608]

II: dkms-build downloading nvidia-390 
(nvidia-dkms-390_390.87-0ubuntu4_amd64.deb)
--2019-01-10 03:38:13--  
http://us.archive.ubuntu.com/ubuntu/pool/restricted/n/nvidia-graphics-drivers-390/nvidia-dkms-390_390.87-0ubuntu4_amd64.deb
Resolving us.archive.ubuntu.com (us.archive.ubuntu.com)... 91.189.91.26, 
91.189.91.23, 2001:67c:1562::16, ...
Connecting to us.archive.ubuntu.com (us.archive.ubuntu.com)|91.189.91.26|:80... 
connected.
HTTP request sent, awaiting response... 200 OK
Length: 27288 (27K) [application/x-debian-package]
Saving to: 'nvidia-dkms-390_390.87-0ubuntu4_amd64.deb'

 0K .. .. ..  100%
9.46M=0.003s

2019-01-10 03:38:13 (9.46 MB/s) - 'nvidia-dkms-
390_390.87-0ubuntu4_amd64.deb' saved [27288/27288]

linux:BuiltUsing=nvidia-kernel-source-390 (= 390.87-0ubuntu4), 
II: dkms-build building nvidia-390

Creating symlink 
/home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/source
 ->
 
/home/kernel/COD/linux/debian/build/build-generic/__dkms/source/nvidia-390.87

DKMS: add completed.
applying patch buildfix_kernel_4.18.patch...patching file conftest.sh
patching file nvidia-drm/nvidia-drm-connector.c
patching file nvidia-drm/nvidia-drm-encoder.c
patching file nvidia-drm/nvidia-drm-helper.h
patching file nvidia-drm/nvidia-drm.Kbuild


Building module:
cleaning build area...(bad exit status: 2)
unset ARCH; env NV_VERBOSE=1 'make' -j16 NV_EXCLUDE_BUILD_MODULES='' 
KERNEL_UNAME=4.20.1-042001-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 
SYSSRC=/home/kernel/COD/linux/debian/build/build-generic/__dkms/headers/linux-headers-4.20.1-042001-generic
 LD=/usr/bin/ld.bfd modules.(bad exit status: 2)
Error! Bad return status for module build on kernel: 4.20.1-042001-generic 
(x86_64)
Consult 
/home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/build/make.log
 for more information.
debian/scripts/dkms-build: line 121: 
/home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/4.20.1-042001-generic/*/log/make.log:
 No such file or directory
make: *** [debian/rules.d/2-binary-arch.mk:201: install-generic] Error 1

Thanks!
Rob

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

** Attachment added: "Build log from kernel.ubuntu.com for kernel v4.20.2 
(amd64)"
   
https://bugs.launchpad.net/bugs/1811721/+attachment/5229052/+files/v4.20.2_BUILD.LOG.amd64

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

Title:
  Mainline Kernel Builds Failing for > v4.20 for amd64 on
  kernel.ubuntu.com

Status in linux package in Ubuntu:
  New

Bug description:
  It appears that mainline kernel builds (on kernel.ubuntu.com) have
  been failing for amd64 since v4.20.1.  Interestingly enough v4.20 was
  able to build successfully.

  Note: this also includes 5.0rc builds as well.

  You can see the build logs here:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20.1/BUILD.LOG.amd64
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20.2/BUILD.LOG.amd64

  Looking at the build logs it appears that the kernel and all the in-
  tree modules build successfully, but the build fails when trying to
  build the proprietary nvidia kernel modules.  With v4.20 building
  these modules does not appear in the log.  Perhaps this build step was
  added more recently?

  Here are the relevant lines from the end of the build log for v4.20.2 (which 
I've also attached):
  
-

  2019-01-10 03:38:12 (105 MB/s) - 'nvidia-kernel-source-
  

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

2019-01-14 Thread Brad Figg
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-bionic

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1811429 (linux-azure), bug 1811430 (linux-aws-hwe), bug 
1811431 (linux-azure), bug 1811432 (linux-gcp), bug 1811434 (linux-hwe), bug 
1811435 (linux-hwe-edge), bug 1811436 (linux-oracle)
  derivatives: bug 1811420 (linux-raspi2), bug 1811421 (linux-oem), bug 1811422 
(linux-aws), bug 1811423 (linux-azure), bug 1811424 (linux-gcp), bug 1811425 
(linux-kvm), bug 1811427 (linux-oracle)
  -- swm properties --
- phase: Packaging -- uploaded
- phase-changed: Monday, 14. January 2019 11:48 UTC
+ boot-testing-requested: true
+ phase: Promote to Proposed -- release to Proposed ready
+ phase-changed: Monday, 14. January 2019 21:04 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete
+   promote-to-proposed: Pending -- ready for review

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

Title:
  linux: 4.15.0-44.47 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

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

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

  backports: bug 1811429 (linux-azure), bug 1811430 (linux-aws-hwe), bug 
1811431 (linux-azure), bug 1811432 (linux-gcp), bug 1811434 (linux-hwe), bug 
1811435 (linux-hwe-edge), bug 1811436 (linux-oracle)
  derivatives: bug 1811420 (linux-raspi2), bug 1811421 (linux-oem), bug 1811422 
(linux-aws), bug 1811423 (linux-azure), bug 1811424 (linux-gcp), bug 1811425 
(linux-kvm), bug 1811427 (linux-oracle)
  -- swm properties --
  boot-testing-requested: true
  phase: Promote to Proposed -- release to Proposed ready
  phase-changed: Monday, 14. January 2019 21:04 UTC
  reason:
promote-to-proposed: Pending -- ready for review

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

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


Re: [Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

2019-01-14 Thread Ryan Harper
On Mon, Jan 14, 2019 at 1:55 PM Thiago Martins 
wrote:

> @Ryan,
>
>  The working XML file is attached here, with 2048 MB of RAM.
>
>  NOTE: This XML was created using Virt-Manager, then, MaaS took it over
> after being "refreshed".
>

Thanks!

If you drop the  section (which is what tells libvirt to boot via UEFI)
does your VM still work?


hvm
/usr/share/OVMF/OVMF_CODE.fd
/var/lib/libvirt/qemu/nvram/vunft-1_VARS.fd


Note that MAAS boots UEFI images with grub2[1], not pxeboot/ipxe/seabios;
so I think we can narrow down the
error to the non-uefi case which may help find the issue.


1.
http://images.maas.io/ephemeral-v3/daily/bootloaders/uefi/amd64/20181123.0/


>
> Cheers!
> Thiago
>
> ** Attachment added: "vunft-1.xml"
>
> https://bugs.launchpad.net/maas/+bug/1797581/+attachment/5229030/+files/vunft-1.xml
>
> --
> You received this bug notification because you are subscribed to qemu in
> Ubuntu.
> https://bugs.launchpad.net/bugs/1797581
>
> Title:
>   Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
>   kernel panic
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1797581/+subscriptions
>

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

Title:
  Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
  kernel panic

Status in MAAS:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  Using latest MAAS master, I'm unable to compose a VM over the UI
  successfully when composed with 2048 MB of RAM. By that I mean that
  the VM is created, but it fails with a kernel panic.

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

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


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

2019-01-14 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Released

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

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

** Tags added: block-proposed-cosmic

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1811407 (linux-hwe), bug 1811408 (linux-hwe-edge), bug 1811409 
(linux-aws-edge), bug 1811410 (linux-azure-edge), bug 1811411 (linux-gcp-edge), 
bug 1811418 (linux-azure-edge)
  derivatives: bug 1811412 (linux-raspi2), bug 1811414 (linux-aws), bug 1811415 
(linux-azure), bug 1811416 (linux-gcp), bug 1811417 (linux-kvm)
  -- swm properties --
- phase: Packaging -- packaging in progress
- phase-changed: Monday, 14. January 2019 02:04 UTC
+ boot-testing-requested: true
+ phase: Promote to Proposed -- release to Proposed ready
+ phase-changed: Monday, 14. January 2019 20:04 UTC
  reason:
-   prepare-package-meta: Pending -- package not yet uploaded
-   prepare-package-signed: Pending -- package not yet uploaded
+   promote-to-proposed: Pending -- ready for review

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

Title:
  linux: 4.18.0-14.15 -proposed tracker

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

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

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

  backports: bug 1811407 (linux-hwe), bug 1811408 (linux-hwe-edge), bug 1811409 
(linux-aws-edge), bug 1811410 (linux-azure-edge), bug 1811411 (linux-gcp-edge), 
bug 1811418 (linux-azure-edge)
  derivatives: bug 1811412 (linux-raspi2), bug 1811414 (linux-aws), bug 1811415 
(linux-azure), bug 1811416 (linux-gcp), bug 1811417 (linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  phase: Promote to Proposed -- release to Proposed ready
  phase-changed: Monday, 14. January 2019 20:04 UTC
  reason:
promote-to-proposed: Pending -- ready for review

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

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


[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

2019-01-14 Thread Thiago Martins
@Ryan,

 The working XML file is attached here, with 2048 MB of RAM.

 NOTE: This XML was created using Virt-Manager, then, MaaS took it over
after being "refreshed".

Cheers!
Thiago

** Attachment added: "vunft-1.xml"
   
https://bugs.launchpad.net/maas/+bug/1797581/+attachment/5229030/+files/vunft-1.xml

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

Title:
  Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
  kernel panic

Status in MAAS:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  Using latest MAAS master, I'm unable to compose a VM over the UI
  successfully when composed with 2048 MB of RAM. By that I mean that
  the VM is created, but it fails with a kernel panic.

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

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


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

2019-01-14 Thread Mauricio Faria de Oliveira
[SRU T][PATCH 0/3] netfilter: nf_conncount: fix for LP#1811094
https://lists.ubuntu.com/archives/kernel-team/2019-January/097878.html

[SRU X][PATCH 0/6] netfilter: nf_conncount: fix for LP#1811094
https://lists.ubuntu.com/archives/kernel-team/2019-January/097698.html

[SRU B][PATCH 0/5] netfilter: nf_conncount: fix for LP#1811094
https://lists.ubuntu.com/archives/kernel-team/2019-January/097705.html

[SRU C, D/Unstable][PATCH 0/1] netfilter: nf_conncount: fix for LP#1811094
https://lists.ubuntu.com/archives/kernel-team/2019-January/097711.html

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

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

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

Bug description:
  [Impact]

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

   * For example:

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

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

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

  [Test Case]

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

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

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

   * Client-side:

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

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

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

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

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

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

  [Regression Potential]

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

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

  [Other Info]

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

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

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

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


[Kernel-packages] [Bug 1811566] Re: Backported commit breaks audio (fixed upstream)

2019-01-14 Thread Jaime Pérez
It does, as expected

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

Title:
  Backported commit breaks audio (fixed upstream)

Status in linux package in Ubuntu:
  In Progress

Bug description:
  It seems that commit 648e921888ad96ea3dc922739e96716ad3225d7f was
  backported to ubuntu's 4.18 kernel. That commit breaks audio for some
  devices (chromebook gnawty) (from 4.19 on). Now 4.19, 4.20, 5.0 are
  fixed, with patch  on commit:

  47148001ae12292984ba1b38d9babefb9a46cd3e
  ASoC: intel: cht_bsw_max98090_ti: Add pmc_plt_clk_0 quirk for Chromebook 
Gnawty

  Bug reported:

  https://bugzilla.kernel.org/show_bug.cgi?id=201787

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

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


[Kernel-packages] [Bug 1777586] Re: Ubuntu Server 18.04 LTS aacraid error

2019-01-14 Thread Makere
I have this same issue after upgrading 16.04 to 18.04. I have the
Adaptec 5805 controller and my computer freezes at fairly random, might
be every 1-2 days or 3-4 weeks.

After checking the syslog for freeze reasons, the aacraid seems to be
the culpript.

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

Title:
  Ubuntu Server 18.04 LTS aacraid error

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

Bug description:
  I upgraded from a previous version of Ubuntu 14.04LTS to 18.04LTS and
  am now running into these raid adapter driver errors.   The server ran
  fine in older version.  My apologies as I lost the exact version, but
  it never had any errors like this version.

  Now when ever I try to copy files to the RAID 5 drive, or untar a
  file, I get these errors now after a few MB's of written data.

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

  batboat:/var/log$ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  I have tried the IRQ debugging tips to no avail.   I loaded in
  Debian9.4.0 and it only briefly showed this error once.   But appears
  to be much more resilient and appears to work fine.


  Jun 19 00:02:21 batboat kernel: [  498.770839] aacraid: Host adapter reset 
request. SCSI hang ?
  Jun 19 00:02:37 batboat kernel: [  514.139167] aacraid: Host adapter reset 
request. SCSI hang ?
  Jun 19 00:02:37 batboat kernel: [  514.795083] aacraid :03:09.0: Adapter 
health - 199
  Jun 19 00:02:37 batboat kernel: [  514.800376] aacraid :03:09.0: 
outstanding cmd: midlevel-0
  Jun 19 00:02:37 batboat kernel: [  514.800378] aacraid :03:09.0: 
outstanding cmd: lowlevel-0
  Jun 19 00:02:37 batboat kernel: [  514.800381] aacraid :03:09.0: 
outstanding cmd: error handler-0
  Jun 19 00:02:37 batboat kernel: [  514.800383] aacraid :03:09.0: 
outstanding cmd: firmware-5
  Jun 19 00:02:37 batboat kernel: [  514.800385] aacraid :03:09.0: 
outstanding cmd: kernel-0
  Jun 19 00:02:37 batboat kernel: [  514.800391] sd 4:0:0:0: Device offlined - 
not ready after error recovery
  Jun 19 00:02:37 batboat kernel: [  514.800394] sd 4:0:0:0: Device offlined - 
not ready after error recovery
  Jun 19 00:02:37 batboat kernel: [  514.800396] sd 4:0:0:0: Device offlined - 
not ready after error recovery
  Jun 19 00:02:37 batboat kernel: [  514.800399] sd 4:0:0:0: Device offlined - 
not ready after error recovery
  Jun 19 00:02:37 batboat kernel: [  514.800401] sd 4:0:0:0: Device offlined - 
not ready after error recovery

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

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


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

2019-01-14 Thread bugproxy
--- Comment From gcwil...@us.ibm.com 2019-01-14 12:51 EDT---
This old feature request was verified but never updated and closed.

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

Title:
  Please disable unnecessary config options in the Ubuntu 17.04 kernel
  config

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  ---Problem Description---
  Some krnel config options for IMA should not be enabled in the Ubuntu 17.04 
kernel as they are at best experimental and at worst dangerous:

CONFIG_IMA_APPRAISE_SIGNED_INIT
CONFIG_IMA_BLACKLIST_KEYRING
CONFIG_IMA_KEYRINGS_PERMIT_SIGNED_BY_BUILTIN_OR_SECONDARY
CONFIG_IIMA_READ_POLICY
CONFIG_IIMA_WRITE_POLICY

  Please disable these config options in the Ubuntu 17.04 kernel config.
   
  ---uname output---
  Linux briggs-rtp-2 4.9.0-15-generic #16-Ubuntu SMP Fri Jan 20 15:28:49 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = S822LC 8001-22C

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

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


[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

2019-01-14 Thread Ryan Harper
@Thiago, 
Can you attach your guest XML that's working successfully with 2048MB?

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

Title:
  Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
  kernel panic

Status in MAAS:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  Using latest MAAS master, I'm unable to compose a VM over the UI
  successfully when composed with 2048 MB of RAM. By that I mean that
  the VM is created, but it fails with a kernel panic.

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

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


[Kernel-packages] [Bug 1808418] Re: Thinkpad T430u won't boot without noapic workaround

2019-01-14 Thread bmaupin
I'm assuming I should add apic=debug to a kernel that has the bug (and
not one that boots fine), correct?

Should I used apic=debug with or without noapic?

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

Title:
  Thinkpad T430u won't boot without noapic workaround

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've used Ubuntu on this specific machine for years without problems,
  but starting with the 4.13 kernel that came with the 17.10 HWE and
  continuing into 18.04 kernels my computer would no longer boot,
  hanging at various screens:

  - A blank screen with a flashing cursor
  - A screen with this message:
  Loading Linux 4.13.0.36-generic ...
  Loading initial ramdisk ...
  - A screen with kernel messages, ending in:
  APCI: EC: interrupt blocked

  I've encountered the bug in a number of kernels, including:
  - 4.13.0-32
  - 4.13.0-36
  - 4.13.0-37
  - 4.15.0-24
  - 4.15.0-34
  - 4.15.0-36
  - 4.15.0-38
  - 4.15.0-42
  - 4.20.0-rc7

  I was able to work around the issue by adding noapic to
  GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic"

  I'm not entirely sure of the consequences of this workaround, but one
  thing I've noticed is significantly reduced battery life.

  This bug seems very similar to what's described here for the Thinkpad
  E485/E585: https://evilazrael.de/node/401

  I'll attach screenshots of various times I've encountered this bug
  over the last year.

  $ lsb_release -rd
  Description:Ubuntu 18.04.1 LTS
  Release:18.04

  $ apt-cache policy linux-image-4.15.0-42-generic
  linux-image-4.15.0-42-generic:
    Installed: 4.15.0-42.45
    Candidate: 4.15.0-42.45
    Version table:
   *** 4.15.0-42.45 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-42-generic 4.15.0-42.45
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bryan  2349 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Dec 13 15:31:15 2018
  HibernationDevice: RESUME=UUID=4afa8032-cfe5-45f4-a626-738ab33904ac
  InstallationDate: Installed on 2014-05-08 (1680 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 3351CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=cffbc87d-956b-4986-94df-b3b64ae5237f ro quiet splash noapic 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-07-12 (154 days ago)
  dmi.bios.date: 06/01/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H6ETA0WW (2.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 3351CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH6ETA0WW(2.18):bd06/01/2018:svnLENOVO:pn3351CTO:pvrThinkPadT430u:rvnLENOVO:rn3351CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430u
  dmi.product.name: 3351CTO
  dmi.product.version: ThinkPad T430u
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

2019-01-14 Thread Thiago Martins
I'm also facing this problem.

My workaround is to compose VMs using Virt-Manager, Firmware = UEFI for
the VM and then, refreshing the MaaS Pod.

There is a need to install ovmf

sudo apt install ovmf

On MaaS Pod.

Then, no more Kernel Panic!

Details:

https://discourse.maas.io/t/maas-2-5-bionic-pod-composing-guests-kernel-
panic-no-init/302

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

Title:
  Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
  kernel panic

Status in MAAS:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  Using latest MAAS master, I'm unable to compose a VM over the UI
  successfully when composed with 2048 MB of RAM. By that I mean that
  the VM is created, but it fails with a kernel panic.

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

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


[Kernel-packages] [Bug 1804280] Re: intermittent periods of packet loss and high latency

2019-01-14 Thread Dan Candeto
Possibly the same issue as bug #1666432, but I can't confirm that it
occurs on the wireless interface, just Ethernet interfaces.

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

Title:
  intermittent periods of packet loss and high latency

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Intermittently and unpredictably, ping response times and packet loss
  will spike to unusable levels.  Normal ping times are about .25 ms for
  other hosts on the local network, with essentially no packet loss.
  During the problematic periods (usually lasting 2-10 minutes), packet
  loss jumps to about 50% and ping response times on the packets that
  aren't dropped jump to between 250 and 750 ms.

  This behavior started when I upgraded from Kubuntu 16.04 to Kubuntu
  18.04.  Changing which host on the network I test this with has no
  effect (and during this, those other hosts are able to use the network
  without any problem).  Replacing the cable changes nothing.  Using a
  different Ethernet interface changes nothing.  Replacing the switch
  changes nothing.  This is almost certainly not a hardware problem.

  There is a chance that using wireless instead of Ethernet would fix
  the issue, but I have been avoiding that since the wired connection is
  much faster when Kubuntu is not malfunctioning.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Nov 20 12:48:05 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-12-09 (711 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via [removed] dev enp0s31f6 proto dhcp metric 100
   169.254.0.0/16 dev enp0s31f6 scope link metric 1000
   [removed]/24 dev enp0s31f6 proto kernel scope link src [removed] metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to bionic on 2018-08-19 (92 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTION  CON-UUID  CON-PATH
   enp0s31f6  ethernet  connected 
/org/freedesktop/NetworkManager/Devices/2  Wired connection 1  
2e0d0ce3-8ee2-3c06-815d-eb9a42873b3b  
/org/freedesktop/NetworkManager/ActiveConnection/5
   [removed]  btdisconnected  /org/freedesktop/NetworkManager/Devices/5 
 --  ----
   wlp3s0 wifi  disconnected  
/org/freedesktop/NetworkManager/Devices/4  --  --   
 --
   lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan2053 F pulseaudio
   /dev/snd/pcmC1D0c:   dan2053 F...m pulseaudio
   /dev/snd/controlC1:  dan2053 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=4eadd7fe-e046-471d-b0ee-f1c85365411e
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-12-09 (712 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.4.1 dev enp0s31f6 proto dhcp metric 100 
   169.254.0.0/16 dev enp0s31f6 scope link metric 1000 
   192.168.4.0/24 dev enp0s31f6 proto kernel scope link src 192.168.4.42 metric 
100
  MachineType: Dell Inc. Precision Tower 3420
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.1
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=89b1b98c-8c19-4200-966b-190a0ca0 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-39-generic N/A
   linux-backports-modules-4.15.0-39-generic  N/A
   linux-firmware

[Kernel-packages] [Bug 1807375]

2019-01-14 Thread vasthusya
Created attachment 280459
Kernel messages from various boot states.

Yes, the coldboot lmp_subver=8221 & hci_rev=c are correct and Bluetooth
works on vanilla kernel.

Unfortunately, I must restart the computer in order to gain CPU clock boost on 
my Ryzen 5 2500u.
Separate issue, haven't checked around here for that bug yet.
https://community.amd.com/thread/229980#2893988

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

Title:
  Bluetooth: hci0: RTL: rtl: unknown IC info, lmp subver a99e, hci rev
  826c, hci ver 0008

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

Bug description:
  Hello,

  dmesg:
  [   13.388386] Bluetooth: hci0: RTL: rtl: unknown IC info, lmp subver a99e, 
hci rev 826c, hci ver 0008

  Best regards,
  --
  Cristian Aravena Romero (caravena)

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

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

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


[Kernel-packages] [Bug 1807375]

2019-01-14 Thread kai.heng.feng
vasthusya,

I also see this issue, but this only happens to reboot.

Do you see this on cold boot?

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

Title:
  Bluetooth: hci0: RTL: rtl: unknown IC info, lmp subver a99e, hci rev
  826c, hci ver 0008

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

Bug description:
  Hello,

  dmesg:
  [   13.388386] Bluetooth: hci0: RTL: rtl: unknown IC info, lmp subver a99e, 
hci rev 826c, hci ver 0008

  Best regards,
  --
  Cristian Aravena Romero (caravena)

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

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

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


[Kernel-packages] [Bug 1811690] Re: glibc tst-cputimer regressions with 4.19.0-10.11

2019-01-14 Thread Seth Forshee
** Changed in: linux (Ubuntu)
   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/1811690

Title:
  glibc tst-cputimer regressions with 4.19.0-10.11

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Regression caused by upstream stable patch "posix-timers: Fix division
  by zero bug". Fix available at:

  https://lkml.kernel.org/r/2019033500.840117...@linutronix.de

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

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


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

2019-01-14 Thread Brad Figg
** Changed in: kernel-sru-workflow/snap-release-to-stable
   Status: New => Invalid

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1811419
- phase: Packaging -- ready to package
- phase-changed: Monday, 14. January 2019 11:34 UTC
+ phase: Packaging -- packaging in progress
+ phase-changed: Monday, 14. January 2019 16:01 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

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

Title:
  linux-azure: 4.15.0-1037.39 -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-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1811419
  phase: Packaging -- packaging in progress
  phase-changed: Monday, 14. January 2019 16:01 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded

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

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


[Kernel-packages] [Bug 1811545] Re: Immediate resume from suspend when wifi enabled

2019-01-14 Thread Steffen Neumann
Hi, I can confirm that suspend works without immediate wakeup 
on a previous 4.15.0-42.45 
and resumes after 2-3 secs in suspend as described above on 4.15.0-43.46

Yours, Steffen.

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

Title:
  Immediate resume from suspend when wifi enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  on a current and update 18.04.01 my 
  Acer TravelMate P648-M/BAD40_SL, BIOS V1.21 07/21/2017
  resumes immediately from suspend. 

  I can successfully enter suspend if I set laptop into flight mode.

  This symptom only appeared the last few days, 
  earlier the same system suspended just fine. 

  There are no differences in  /proc/acpi/wakeup 
  with and without flight mode.

  => What other debugging information would be needed 
 to figure what caused the resume with wifi enabled ?

  Yours, Steffen

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   sneumann   2816 F...m pulseaudio
   /dev/snd/controlC0:  sneumann   2816 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 13 01:41:00 2019
  HibernationDevice: RESUME=UUID=045e8ed5-08d8-46a0-8ed4-606bd3be42a1
  InstallationDate: Installed on 2018-05-17 (240 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Acer TravelMate P648-M
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic 
root=/dev/mapper/lvmssd-bioinic ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: BAD40_SL
  dmi.board.vendor: Acer
  dmi.board.version: V1.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.21
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.21:bd07/21/2017:svnAcer:pnTravelMateP648-M:pvrV1.21:rvnAcer:rnBAD40_SL:rvrV1.21:cvnAcer:ct10:cvrV1.21:
  dmi.product.family: SKL
  dmi.product.name: TravelMate P648-M
  dmi.product.version: V1.21
  dmi.sys.vendor: Acer

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

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


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

2019-01-14 Thread Kleber Sacilotto de Souza
** Summary changed:

- linux-azure:  -proposed tracker
+ linux-azure: 4.15.0-1037.39 -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) => Kleber 
Sacilotto de Souza (kleber-souza)

** 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) => Kleber 
Sacilotto de Souza (kleber-souza)

** 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) => Kleber 
Sacilotto de Souza (kleber-souza)

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

Title:
  linux-azure: 4.15.0-1037.39 -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-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1811419
  phase: Packaging -- ready to package
  phase-changed: Monday, 14. January 2019 11:34 UTC
  reason:
prepare-package: Pending -- version not specified

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

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


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

2019-01-14 Thread Brad Figg
** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1811429 (linux-azure), bug 1811430 (linux-aws-hwe), bug 
1811431 (linux-azure), bug 1811432 (linux-gcp), bug 1811434 (linux-hwe), bug 
1811435 (linux-hwe-edge), bug 1811436 (linux-oracle)
  derivatives: bug 1811420 (linux-raspi2), bug 1811421 (linux-oem), bug 1811422 
(linux-aws), bug 1811423 (linux-azure), bug 1811424 (linux-gcp), bug 1811425 
(linux-kvm), bug 1811427 (linux-oracle)
  -- swm properties --
  phase: Packaging -- uploaded
  phase-changed: Monday, 14. January 2019 11:48 UTC
  reason:
-   promote-to-proposed: Pending -- source package tags missing
+   promote-to-proposed: Ongoing -- builds not complete

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

Title:
  linux: 4.15.0-44.47 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

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

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

  backports: bug 1811429 (linux-azure), bug 1811430 (linux-aws-hwe), bug 
1811431 (linux-azure), bug 1811432 (linux-gcp), bug 1811434 (linux-hwe), bug 
1811435 (linux-hwe-edge), bug 1811436 (linux-oracle)
  derivatives: bug 1811420 (linux-raspi2), bug 1811421 (linux-oem), bug 1811422 
(linux-aws), bug 1811423 (linux-azure), bug 1811424 (linux-gcp), bug 1811425 
(linux-kvm), bug 1811427 (linux-oracle)
  -- swm properties --
  phase: Packaging -- uploaded
  phase-changed: Monday, 14. January 2019 11:48 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete

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

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


[Kernel-packages] [Bug 1811415] Re: linux-azure: 4.18.0-1008.8 -proposed tracker

2019-01-14 Thread Brad Figg
** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1811406
- phase: Packaging -- ready to package
- phase-changed: Monday, 14. January 2019 10:06 UTC
+ phase: Packaging -- packaging in progress
+ phase-changed: Monday, 14. January 2019 15:34 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

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

Title:
  linux-azure: 4.18.0-1008.8 -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-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Cosmic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1811406
  phase: Packaging -- packaging in progress
  phase-changed: Monday, 14. January 2019 15:34 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded

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

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


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

2019-01-14 Thread Brad Figg
** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1811419
- phase: Packaging -- ready to package
- phase-changed: Monday, 14. January 2019 11:48 UTC
+ phase: Packaging -- packaging in progress
+ phase-changed: Monday, 14. January 2019 15:32 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded

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

Title:
  linux-kvm: 4.15.0-1029.29 -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 upload-to-ppa-dnu series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Bionic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1811419
  phase: Packaging -- packaging in progress
  phase-changed: Monday, 14. January 2019 15:32 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded

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

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


[Kernel-packages] [Bug 1811415] Re: linux-azure: 4.18.0-1008.8 -proposed tracker

2019-01-14 Thread Stefan Bader
** Summary changed:

- linux-azure:  -proposed tracker
+ linux-azure: 4.18.0-1008.8 -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) => Stefan Bader 
(smb)

** 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) => Stefan Bader 
(smb)

** 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) => Stefan Bader 
(smb)

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

Title:
  linux-azure: 4.18.0-1008.8 -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-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Cosmic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1811406
  phase: Packaging -- ready to package
  phase-changed: Monday, 14. January 2019 10:06 UTC
  reason:
prepare-package: Pending -- version not specified

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

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


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

2019-01-14 Thread Kleber Sacilotto de Souza
** Summary changed:

- linux-kvm:  -proposed tracker
+ linux-kvm: 4.15.0-1029.29 -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) => Kleber 
Sacilotto de Souza (kleber-souza)

** 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) => Kleber 
Sacilotto de Souza (kleber-souza)

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

Title:
  linux-kvm: 4.15.0-1029.29 -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 upload-to-ppa-dnu series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Bionic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1811419
  phase: Packaging -- ready to package
  phase-changed: Monday, 14. January 2019 11:48 UTC
  reason:
prepare-package: Pending -- version not specified

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

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


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

2019-01-14 Thread Brad Figg
** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1811429 (linux-azure), bug 1811430 (linux-aws-hwe), bug 
1811431 (linux-azure), bug 1811432 (linux-gcp), bug 1811434 (linux-hwe), bug 
1811435 (linux-hwe-edge), bug 1811436 (linux-oracle)
  derivatives: bug 1811420 (linux-raspi2), bug 1811421 (linux-oem), bug 1811422 
(linux-aws), bug 1811423 (linux-azure), bug 1811424 (linux-gcp), bug 1811425 
(linux-kvm), bug 1811427 (linux-oracle)
  -- swm properties --
  phase: Packaging -- uploaded
  phase-changed: Monday, 14. January 2019 11:48 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete
+   promote-to-proposed: Pending -- source package tags missing

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

Title:
  linux: 4.15.0-44.47 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

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

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

  backports: bug 1811429 (linux-azure), bug 1811430 (linux-aws-hwe), bug 
1811431 (linux-azure), bug 1811432 (linux-gcp), bug 1811434 (linux-hwe), bug 
1811435 (linux-hwe-edge), bug 1811436 (linux-oracle)
  derivatives: bug 1811420 (linux-raspi2), bug 1811421 (linux-oem), bug 1811422 
(linux-aws), bug 1811423 (linux-azure), bug 1811424 (linux-gcp), bug 1811425 
(linux-kvm), bug 1811427 (linux-oracle)
  -- swm properties --
  phase: Packaging -- uploaded
  phase-changed: Monday, 14. January 2019 11:48 UTC
  reason:
promote-to-proposed: Pending -- source package tags missing

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

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


[Kernel-packages] [Bug 1811690] [NEW] glibc tst-cputimer regressions with 4.19.0-10.11

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

Regression caused by upstream stable patch "posix-timers: Fix division
by zero bug". Fix available at:

https://lkml.kernel.org/r/2019033500.840117...@linutronix.de

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

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

Title:
  glibc tst-cputimer regressions with 4.19.0-10.11

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Regression caused by upstream stable patch "posix-timers: Fix division
  by zero bug". Fix available at:

  https://lkml.kernel.org/r/2019033500.840117...@linutronix.de

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

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


[Kernel-packages] [Bug 1811692] [NEW] udev coldplug will interrupt makedumpfile

2019-01-14 Thread Thadeu Lima de Souza Cascardo
Public bug reported:

After introducing the udev rules to restart kdump-tools service when
there is memory or cpu hotplug, it will be restarted during coldplug as
well. This will cause the dump capture itself to be interrupted after a
crash. When it is restarted and tries to dump again, it will find an
existing dump file and will fail to dump.

My proposed solution is to use a different systemd service for the real
capture.

** Affects: makedumpfile (Ubuntu)
 Importance: High
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: In Progress

** Changed in: makedumpfile (Ubuntu)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

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

** Changed in: makedumpfile (Ubuntu)
   Status: New => In Progress

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

Title:
  udev coldplug will interrupt makedumpfile

Status in makedumpfile package in Ubuntu:
  In Progress

Bug description:
  After introducing the udev rules to restart kdump-tools service when
  there is memory or cpu hotplug, it will be restarted during coldplug
  as well. This will cause the dump capture itself to be interrupted
  after a crash. When it is restarted and tries to dump again, it will
  find an existing dump file and will fail to dump.

  My proposed solution is to use a different systemd service for the
  real capture.

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

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


[Kernel-packages] [Bug 1760099] Re: Additional spectre and meltdown patches

2019-01-14 Thread Manoj Iyer
** Changed in: linux (Ubuntu Trusty)
   Status: Triaged => Won't Fix

** Changed in: ubuntu-power-systems
   Status: Incomplete => Fix Released

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

Title:
  Additional spectre and meltdown patches

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  Fix Released

Bug description:
  == Comment: #0 - Breno Leitao  - 2018-03-29 08:53:56 ==
  Hi Canonical,

  There are some additional patches for Spectre and Meltdown that is
  required on ppc64el. We would need to have them included on all Ubuntu
  kernels.

  This is the patch series:

  [v2,10/10] powerpc/64s: Wire up cpu_show_spectre_v2()   [v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown 
   
  [v2,09/10] powerpc/64s: Wire up cpu_show_spectre_v1()   [v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown
  [v2,08/10] powerpc/pseries: Use the security flags in 
pseries_setup_rfi_flush() [v2,01/10] powerpc: Add security feature 
flags for Spectre/Meltdown
  [v2,07/10] powerpc/powernv: Use the security flags in pnv_setup_rfi_flush()   
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,06/10] powerpc/64s: Enhance the information in cpu_show_meltdown()  
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,05/10] powerpc/64s: Move cpu_show_meltdown()[v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown
  [v2,04/10] powerpc/powernv: Set or clear security feature flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,03/10] powerpc/pseries: Set or clear security feature flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,02/10] powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 

  http://patchwork.ozlabs.org/project/linuxppc-
  dev/list/?series=36012=*

  == Comment: #1 - Breno Leitao  - 2018-03-29 08:55:48 ==
  This is a better formatted patch series list:

  [v2,10/10] powerpc/64s: Wire up cpu_show_spectre_v2() 

 
  [v2,09/10] powerpc/64s: Wire up cpu_show_spectre_v1()   
  [v2,08/10] powerpc/pseries: Use the security flags in 
pseries_setup_rfi_flush() 
  [v2,07/10] powerpc/powernv: Use the security flags in pnv_setup_rfi_flus()
  
  [v2,06/10] powerpc/64s: Enhance the information in cpu_show_meltdown()  
  [v2,05/10] powerpc/64s: Move cpu_show_meltdown()
  [v2,04/10] powerpc/powernv: Set or clear security feature flags 
  [v2,03/10] powerpc/pseries: Set or clear security feature flags 
  [v2,02/10] powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags 
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown

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

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


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

2019-01-14 Thread Alberto Milone
@Fink: I would like to see powertop when you don't use bbswitch (and the
Nvidia GPU is on). More specifically, I would like to know if you can
disable the Nvidia GPU using the "Tunables" tab from powertop.

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

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

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

Bug description:
  SRU Request:

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

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

  The solution involves the following changes:

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

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

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

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

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

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

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

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

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

  5) Log out and log back in

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

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

  _
  * Steps to test the updates:

  1) Enable the bionic-proposed repositories

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

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

  3) Update the list of packages:

  sudo apt-get update

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

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

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

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


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

2019-01-14 Thread Alberto Milone
Pe4enko: Here is your problem:

NVRM: API mismatch: the client has the version 410.66, but
NVRM: this kernel module has the version 390.87. Please
NVRM: make sure that this kernel module and all NVIDIA driver
NVRM: components have the same version.

It looks like you installed the 410.66 driver (maybe using the installer
from Nvidia's website), and then tried to install the 390 driver from
the Ubuntu archive. This is not going to work. Please uninstall the
nvidia packages (sudo apt-get remove --purge '*nvidia*') and then use
the Nvidia installer to uninstall the other driver.

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

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

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

Bug description:
  SRU Request:

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

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

  The solution involves the following changes:

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

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

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

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

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

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

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

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

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

  5) Log out and log back in

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

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

  _
  * Steps to test the updates:

  1) Enable the bionic-proposed repositories

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

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

  3) Update the list of packages:

  sudo apt-get update

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

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

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

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


[Kernel-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's

2019-01-14 Thread Łukasz Zemczak
Hello Timo, or anyone else affected,

Accepted mesa into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/18.2.8-0ubuntu0~18.10.1 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-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. 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: mesa (Ubuntu Cosmic)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed-cosmic

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

Title:
  Missing Intel GPU pci-id's

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server source package in Bionic:
  Fix Released
Status in libdrm source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in mesa source package in Cosmic:
  Fix Committed
Status in xorg-server source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  There are some new Intel GPU pci-id's that need to be added to several places:

  0x3E98
  0x87C0

  and to make future additions easier, add platform definitions for
  Whiskey Lake and Amber Lake too.

  [Test case]
  Check that the user session uses the proper driver on these systems.

  [Regression potential]
  none, these just add pci-id's and platform definitions

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

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


[Kernel-packages] [Bug 1787460] Re: Unattended upgrades removed linux-image-generic

2019-01-14 Thread Julian Andres Klode
** Description changed:

- On a fairly fresh install of 18.04 with no modifications whatsoever to
- the unattended-upgrades configuration, it decided to remove linux-image-
- generic which also removed linux-modules-extra which caused sound
- drivers to disappear, etc.
+ [Impact]
+ If a user accidentally removed linux-generic, unattended-upgrades will also 
autoremove linux-image-generic, leaving them without kernel upgrades.
+ 
+ [Test Case]
+ 1. Remove all reverse dependencies of linux-image-generic
+ 2. Mark linux-image-generic as automatically installed
+ 3. Run unattended-upgrades -v --dry-run --debug to ensure that 
linux-image-generic is not removed (after verifying that it is, with old apt)
+ 
+ [Regression potential]
+ This adds two regular expressions to the list of packages that must not be 
automatically removed. As such, the only possible regression is that some 
packages starting with linux-image, not containing any dots, are not removed
+ 
+ [Original bug report]
+ On a fairly fresh install of 18.04 with no modifications whatsoever to the 
unattended-upgrades configuration, it decided to remove linux-image-generic 
which also removed linux-modules-extra which caused sound drivers to disappear, 
etc.
  
  The relative snippet from /var/log/unattended-upgrades/unattended-
  upgrades.log is:
  
  2018-08-15 06:18:00,048 INFO Starting unattended upgrades script
  2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, 
o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic
  2018-08-15 06:18:01,552 INFO Removing unused kernel packages: 
linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic 
linux-headers-4.15.0-32
  2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic 
package(s) because it would also remove the following packages which should be 
kept in this step: libxml2 linux-image-4.15.0-32-generic 
linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic
  2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: 
linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic 
linux-image-generic
  2018-08-15 06:18:09,477 INFO Packages that are kept back: 
linux-headers-generic
  2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 
linux-image-generic
  2018-08-15 06:18:10,300 INFO Writing dpkg log to 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  2018-08-15 06:18:39,238 INFO All upgrades installed
  2018-08-15 06:18:42,818 INFO Packages that were successfully auto-removed: 
linux-image-generic linux-modules-extra-4.15.0-32-generic
  2018-08-15 06:18:42,818 INFO Packages that are kept back:
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: unattended-upgrades 1.1ubuntu1.18.04.5
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 16 13:17:30 2018
  InstallationDate: Installed on 2018-07-24 (23 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  PackageArchitecture: all
  ProcEnviron:
-  TERM=xterm
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

** Changed in: apt (Ubuntu Cosmic)
   Status: New => Triaged

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

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

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

Title:
  Unattended upgrades removed linux-image-generic

Status in apt package in Ubuntu:
  Fix Released
Status in linux-meta package in Ubuntu:
  Triaged
Status in linux-meta-hwe package in Ubuntu:
  Triaged
Status in apt source package in Xenial:
  Triaged
Status in linux-meta source package in Xenial:
  New
Status in linux-meta-hwe source package in Xenial:
  New
Status in apt source package in Bionic:
  Triaged
Status in linux-meta source package in Bionic:
  New
Status in linux-meta-hwe source package in Bionic:
  New
Status in apt source package in Cosmic:
  Triaged
Status in linux-meta source package in Cosmic:
  New
Status in linux-meta-hwe source package in Cosmic:
  New
Status in apt source package in Disco:
  Fix Released
Status in linux-meta source package in Disco:
  Triaged
Status in linux-meta-hwe source package in Disco:
  Triaged

Bug description:
  [Impact]
  If a user accidentally removed linux-generic, unattended-upgrades will also 
autoremove linux-image-generic, leaving them without kernel upgrades.

  [Test Case]
  1. Remove all reverse 

[Kernel-packages] [Bug 1811259] Re: 4.20 kernel on s390x VM crashes

2019-01-14 Thread Colin Ian King
5.0-rc2 also fails to boot:

[0.761280] CPU: 0 PID: 7 Comm: kworker/u6:0 Not tainted 5.0.0-rc2 #1
[0.761282] Hardware name: IBM 2964 N63 400 (KVM/Linux)
[0.761288] Workqueue: events_unbound call_usermodehelper_exec_work
[0.761291] Krnl PSW : 0404e0018000 0016a360 
(release_task_stack+0x78/0x1b0)
[0.761297]R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 
RI:0 EA:3
[0.761301] Krnl GPRS: f000 01ee6320 0700 

[0.761303]fffc 7f26 7ff92300 
7f9e6790
[0.761306]0080 01c15d00 01cd9000 
0003
[0.761309]0008 008f1228 0016a3ae 
03e00034fb40
[0.761320] Krnl Code: 0016a34e: e320f0a4lg  
%r2,160(%r15)
[0.761320]0016a354: c004brcl0,16a354
[0.761320]   #0016a35a: e35003b4lg  %r5,944
[0.761320]   >0016a360: e3103514lg  
%r1,1296(%r3)
[0.761320]0016a366: a71b0118aghi%r1,280
[0.761320]0016a36a: b9040041lgr %r4,%r1
[0.761320]0016a36e: e3454004lg  
%r4,0(%r5,%r4)
[0.761320]0016a374: a74bfffcaghi%r4,-4
[0.761343] Call Trace:
[0.761346] ([<0016a3ae>] release_task_stack+0xc6/0x1b0)
[0.761352]  [<0019c914>] finish_task_switch+0x274/0x308 
[0.761356]  [<008deb4e>] __schedule+0x46e/0x8e8 
[0.761359]  [<008df00a>] schedule+0x42/0xa0 
[0.761363]  [<00173036>] do_wait+0x1f6/0x288 
[0.761366]  [<00174382>] kernel_wait4+0x9a/0x130 
[0.761370]  [<001887ac>] call_usermodehelper_exec_work+0x94/0xd8 
[0.761373]  [<0018c5d8>] process_one_work+0x278/0x4b8 
[0.761376]  [<0018c868>] worker_thread+0x50/0x4e0 
[0.761380]  [<001936ac>] kthread+0x144/0x160 
[0.761383]  [<008e3cc2>] kernel_thread_starter+0xa/0x10 
[0.761386]  [<008e3cb8>] kernel_thread_starter+0x0/0x10 
[0.761387] Last Breaking-Event-Address:
[0.761435]  [<0016a3ae>] release_task_stack+0xc6/0x1b0

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

Title:
  4.20 kernel on s390x VM crashes

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

Bug description:
  Booting with  4.20.0-2-generic on a s390x 2 CPU VM we hit a panic:

  [0.394835] Linux version 4.20.0-2-generic (buildd@bos02-s390x-015) (gcc 
version 8.2.0 (Ubuntu 8.2.0-13ubuntu1)) #3-Ubuntu SMP Thu Jan 3 18:43:01 UTC 
2019 (Ubuntu 4.20.0-2.3-generic 4.20.0)
  [0.394838] setup.289988: Linux is running under KVM in 64-bit mode
  [0.394846] setup.b050d0: The maximum memory size is 2048MB
  [0.394866] numa.196305: NUMA mode: plain
  [0.394893] cpu.33a262: 2 configured CPUs, 0 standby CPUs
  [0.394999] Write protected kernel read-only data: 10464k
  [0.395034] Zone ranges:
  [0.395035]   DMA  [mem 0x-0x7fff]
  [0.395037]   Normal   empty
  [0.395038] Movable zone start for each node
  [0.395039] Early memory node ranges
  [0.395041]   node   0: [mem 0x-0x7fff]
  [0.395042] Initmem setup node 0 [mem 
0x-0x7fff]
  [0.413802] percpu: Embedded 25 pages/cpu @(ptrval) s62208 r8192 
d32000 u102400
  [0.413824] Built 1 zonelists, mobility grouping on.  Total pages: 516096
  [0.413825] Policy zone: DMA
  [0.413827] Kernel command line: root=LABEL=cloudimg-rootfs
  [0.450276] Memory: 2034164K/2097152K available (8116K kernel code, 1079K 
rwdata, 2344K rodata, 992K init, 772K bss, 62988K reserved, 0K cma-reserved)
  [0.450283] random: get_random_u64 called from kmem_cache_open+0x4c/0x4f0 
with crng_init=0
  [0.450432] SLUB: HWalign=256, Order=0-3, MinObjects=0, CPUs=3, Nodes=1
  [0.450434] ftrace: allocating 27385 entries in 107 pages
  [0.473325] rcu: Hierarchical RCU implementation.
  [0.473327] rcu:   RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=3.
  [0.473328]Tasks RCU enabled.
  [0.473329] rcu: RCU calculated value of scheduler-enlistment delay is 10 
jiffies.
  [0.473330] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=3
  [0.475371] NR_IRQS: 3, nr_irqs: 3, preallocated irqs: 3
  [0.475402] clocksource: tod: mask: 0x max_cycles: 
0x3b0a9be803b0a9, max_idle_ns: 1805497147909793 ns
  [0.475558] printk: console [ttyS1] enabled
  [0.475623] pid_max: default: 32768 minimum: 301
  [0.475658] LSM: Security Framework 

[Kernel-packages] [Bug 1787460] Re: Unattended upgrades removed linux-image-generic

2019-01-14 Thread Julian Andres Klode
** Also affects: apt (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

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

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

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

** Also affects: apt (Ubuntu Disco)
   Importance: Critical
   Status: Fix Released

** Also affects: linux-meta (Ubuntu Disco)
   Importance: Critical
   Status: Triaged

** Also affects: linux-meta-hwe (Ubuntu Disco)
   Importance: Critical
   Status: Triaged

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

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

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

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

Title:
  Unattended upgrades removed linux-image-generic

Status in apt package in Ubuntu:
  Fix Released
Status in linux-meta package in Ubuntu:
  Triaged
Status in linux-meta-hwe package in Ubuntu:
  Triaged
Status in apt source package in Xenial:
  New
Status in linux-meta source package in Xenial:
  New
Status in linux-meta-hwe source package in Xenial:
  New
Status in apt source package in Bionic:
  New
Status in linux-meta source package in Bionic:
  New
Status in linux-meta-hwe source package in Bionic:
  New
Status in apt source package in Cosmic:
  New
Status in linux-meta source package in Cosmic:
  New
Status in linux-meta-hwe source package in Cosmic:
  New
Status in apt source package in Disco:
  Fix Released
Status in linux-meta source package in Disco:
  Triaged
Status in linux-meta-hwe source package in Disco:
  Triaged

Bug description:
  [Impact]
  If a user accidentally removed linux-generic, unattended-upgrades will also 
autoremove linux-image-generic, leaving them without kernel upgrades.

  [Test Case]
  1. Remove all reverse dependencies of linux-image-generic
  2. Mark linux-image-generic as automatically installed
  3. Run unattended-upgrades -v --dry-run --debug to ensure that 
linux-image-generic is not removed (after verifying that it is, with old apt)

  [Regression potential]
  This adds two regular expressions to the list of packages that must not be 
automatically removed. As such, the only possible regression is that some 
packages starting with linux-image, not containing any dots, are not removed

  [Original bug report]
  On a fairly fresh install of 18.04 with no modifications whatsoever to the 
unattended-upgrades configuration, it decided to remove linux-image-generic 
which also removed linux-modules-extra which caused sound drivers to disappear, 
etc.

  The relative snippet from /var/log/unattended-upgrades/unattended-
  upgrades.log is:

  2018-08-15 06:18:00,048 INFO Starting unattended upgrades script
  2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, 
o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic
  2018-08-15 06:18:01,552 INFO Removing unused kernel packages: 
linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic 
linux-headers-4.15.0-32
  2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic 
package(s) because it would also remove the following packages which should be 
kept in this step: libxml2 linux-image-4.15.0-32-generic 
linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic
  2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: 
linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic 
linux-image-generic
  2018-08-15 06:18:09,477 INFO Packages that are kept back: 
linux-headers-generic
  2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 
linux-image-generic
  2018-08-15 06:18:10,300 INFO Writing dpkg log to 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  2018-08-15 06:18:39,238 INFO All upgrades installed
  2018-08-15 06:18:42,818 INFO Packages that were successfully auto-removed: 
linux-image-generic linux-modules-extra-4.15.0-32-generic
  2018-08-15 06:18:42,818 INFO Packages that are kept back:

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: unattended-upgrades 1.1ubuntu1.18.04.5
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 16 13:17:30 2018
  InstallationDate: Installed on 2018-07-24 (23 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic 

[Kernel-packages] [Bug 1804280] Re: intermittent periods of packet loss and high latency

2019-01-14 Thread Dan Candeto
Persists with 4.15.0-43-generic.

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

Title:
  intermittent periods of packet loss and high latency

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Intermittently and unpredictably, ping response times and packet loss
  will spike to unusable levels.  Normal ping times are about .25 ms for
  other hosts on the local network, with essentially no packet loss.
  During the problematic periods (usually lasting 2-10 minutes), packet
  loss jumps to about 50% and ping response times on the packets that
  aren't dropped jump to between 250 and 750 ms.

  This behavior started when I upgraded from Kubuntu 16.04 to Kubuntu
  18.04.  Changing which host on the network I test this with has no
  effect (and during this, those other hosts are able to use the network
  without any problem).  Replacing the cable changes nothing.  Using a
  different Ethernet interface changes nothing.  Replacing the switch
  changes nothing.  This is almost certainly not a hardware problem.

  There is a chance that using wireless instead of Ethernet would fix
  the issue, but I have been avoiding that since the wired connection is
  much faster when Kubuntu is not malfunctioning.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Nov 20 12:48:05 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-12-09 (711 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via [removed] dev enp0s31f6 proto dhcp metric 100
   169.254.0.0/16 dev enp0s31f6 scope link metric 1000
   [removed]/24 dev enp0s31f6 proto kernel scope link src [removed] metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to bionic on 2018-08-19 (92 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTION  CON-UUID  CON-PATH
   enp0s31f6  ethernet  connected 
/org/freedesktop/NetworkManager/Devices/2  Wired connection 1  
2e0d0ce3-8ee2-3c06-815d-eb9a42873b3b  
/org/freedesktop/NetworkManager/ActiveConnection/5
   [removed]  btdisconnected  /org/freedesktop/NetworkManager/Devices/5 
 --  ----
   wlp3s0 wifi  disconnected  
/org/freedesktop/NetworkManager/Devices/4  --  --   
 --
   lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan2053 F pulseaudio
   /dev/snd/pcmC1D0c:   dan2053 F...m pulseaudio
   /dev/snd/controlC1:  dan2053 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=4eadd7fe-e046-471d-b0ee-f1c85365411e
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-12-09 (712 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.4.1 dev enp0s31f6 proto dhcp metric 100 
   169.254.0.0/16 dev enp0s31f6 scope link metric 1000 
   192.168.4.0/24 dev enp0s31f6 proto kernel scope link src 192.168.4.42 metric 
100
  MachineType: Dell Inc. Precision Tower 3420
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.1
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=89b1b98c-8c19-4200-966b-190a0ca0 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-39-generic N/A
   linux-backports-modules-4.15.0-39-generic  N/A
   linux-firmware 1.173.2
  Tags:  bionic
  Uname: Linux 4.15.0-39-generic x86_64
  

[Kernel-packages] [Bug 1770294] Re: linux-azure: 4.15.0-1011.11 -proposed tracker

2019-01-14 Thread Andy Whitcroft
** Changed in: kernel-sru-workflow/upload-to-ppa-dnu
   Status: New => Invalid

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

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

Status in Kernel SRU Workflow:
  Fix Released
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:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1772932] Re: linux-kvm: 4.15.0-1011.11 -proposed tracker

2019-01-14 Thread Andy Whitcroft
** Changed in: kernel-sru-workflow/upload-to-ppa-dnu
   Status: New => Invalid

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

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

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Fix Released
Status in linux-kvm source package in Bionic:
  Fix Released

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1772927
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1772931] Re: linux-aws: 4.15.0-1010.10 -proposed tracker

2019-01-14 Thread Andy Whitcroft
** Changed in: kernel-sru-workflow/upload-to-ppa-dnu
   Status: New => Invalid

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

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

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux-aws source package in Bionic:
  Fix Released

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1772927
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1772934] Re: linux-gcp: 4.15.0-1009.9 -proposed tracker

2019-01-14 Thread Andy Whitcroft
** Changed in: kernel-sru-workflow/upload-to-ppa-dnu
   Status: New => Invalid

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

Title:
  linux-gcp: 4.15.0-1009.9 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-edge series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Fix Released
Status in linux-gcp source package in Bionic:
  Fix Released

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1772927
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1772930] Re: linux-azure: 4.15.0-1013.13 -proposed tracker

2019-01-14 Thread Andy Whitcroft
** Changed in: kernel-sru-workflow/upload-to-ppa-dnu
   Status: New => Invalid

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

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

Status in Kernel SRU Workflow:
  Fix Released
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:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
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:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1772927
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


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

2019-01-14 Thread Brad Figg
** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1811406
  phase: Packaging -- ready to package
  phase-changed: Monday, 14. January 2019 10:01 UTC
  reason:
prepare-package: Pending -- version not specified
-   upload-to-ppa-dnu: unknown workflow task

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

Title:
  linux-gcp:  -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1811406
  phase: Packaging -- ready to package
  phase-changed: Monday, 14. January 2019 10:01 UTC
  reason:
prepare-package: Pending -- version not specified

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

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


[Kernel-packages] [Bug 1810370] Re: linux-oem: 4.15.0-1031.36 -proposed tracker

2019-01-14 Thread Brad Figg
** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Testing -- automated-testing FAILED
  phase-changed: Wednesday, 09. January 2019 14:55 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
-   upload-to-ppa-dnu: unknown workflow task

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

Title:
  linux-oem: 4.15.0-1031.36 -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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Testing -- automated-testing FAILED
  phase-changed: Wednesday, 09. January 2019 14:55 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress

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

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


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

2019-01-14 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1811419
+ phase: Packaging -- ready to package
+ phase-changed: Monday, 14. January 2019 11:47 UTC
  reason:
-   prepare-package: Stalled -- waiting for master bug
-   upload-to-ppa-dnu: unknown workflow task
+   prepare-package: Pending -- version not specified

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

Title:
  linux-oem:  -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1811419
  phase: Packaging -- ready to package
  phase-changed: Monday, 14. January 2019 11:47 UTC
  reason:
prepare-package: Pending -- version not specified

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

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


[Kernel-packages] [Bug 1811414] Re: linux-aws: 4.18.0-1008.10 -proposed tracker

2019-01-14 Thread Brad Figg
** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1811406
  phase: Packaging -- packaging in progress
  phase-changed: Monday, 14. January 2019 11:04 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
-   upload-to-ppa-dnu: unknown workflow task

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

Title:
  linux-aws: 4.18.0-1008.10 -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 upload-to-ppa-dnu series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Cosmic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1811406
  phase: Packaging -- packaging in progress
  phase-changed: Monday, 14. January 2019 11:04 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded

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

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


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

2019-01-14 Thread Brad Figg
** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1811407 (linux-hwe), bug 1811408 (linux-hwe-edge), bug 1811409 
(linux-aws-edge), bug 1811410 (linux-azure-edge), bug 1811411 (linux-gcp-edge), 
bug 1811418 (linux-azure-edge)
  derivatives: bug 1811412 (linux-raspi2), bug 1811414 (linux-aws), bug 1811415 
(linux-azure), bug 1811416 (linux-gcp), bug 1811417 (linux-kvm)
  -- swm properties --
  phase: Packaging -- packaging in progress
  phase-changed: Monday, 14. January 2019 02:04 UTC
  reason:
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
-   upload-to-ppa-dnu: unknown workflow task

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

Title:
  linux: 4.18.0-14.15 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  Confirmed

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

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

  backports: bug 1811407 (linux-hwe), bug 1811408 (linux-hwe-edge), bug 1811409 
(linux-aws-edge), bug 1811410 (linux-azure-edge), bug 1811411 (linux-gcp-edge), 
bug 1811418 (linux-azure-edge)
  derivatives: bug 1811412 (linux-raspi2), bug 1811414 (linux-aws), bug 1811415 
(linux-azure), bug 1811416 (linux-gcp), bug 1811417 (linux-kvm)
  -- swm properties --
  phase: Packaging -- packaging in progress
  phase-changed: Monday, 14. January 2019 02:04 UTC
  reason:
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded

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

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


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

2019-01-14 Thread Brad Figg
** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1811406
  phase: Packaging -- ready to package
  phase-changed: Monday, 14. January 2019 10:06 UTC
  reason:
prepare-package: Pending -- version not specified
-   upload-to-ppa-dnu: unknown workflow task

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

Title:
  linux-azure:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Cosmic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1811406
  phase: Packaging -- ready to package
  phase-changed: Monday, 14. January 2019 10:06 UTC
  reason:
prepare-package: Pending -- version not specified

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

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


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

2019-01-14 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Released

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1811429 (linux-azure), bug 1811430 (linux-aws-hwe), bug 
1811431 (linux-azure), bug 1811432 (linux-gcp), bug 1811434 (linux-hwe), bug 
1811435 (linux-hwe-edge), bug 1811436 (linux-oracle)
  derivatives: bug 1811420 (linux-raspi2), bug 1811421 (linux-oem), bug 1811422 
(linux-aws), bug 1811423 (linux-azure), bug 1811424 (linux-gcp), bug 1811425 
(linux-kvm), bug 1811427 (linux-oracle)
  -- swm properties --
- phase: Packaging -- packaging in progress
- phase-changed: Sunday, 13. January 2019 21:33 UTC
+ phase: Packaging -- uploaded
+ phase-changed: Monday, 14. January 2019 11:48 UTC
  reason:
-   prepare-package-meta: Pending -- package not yet uploaded
-   prepare-package-signed: Pending -- package not yet uploaded
-   upload-to-ppa-dnu: unknown workflow task
+   promote-to-proposed: Ongoing -- builds not complete

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

Title:
  linux: 4.15.0-44.47 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

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

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

  backports: bug 1811429 (linux-azure), bug 1811430 (linux-aws-hwe), bug 
1811431 (linux-azure), bug 1811432 (linux-gcp), bug 1811434 (linux-hwe), bug 
1811435 (linux-hwe-edge), bug 1811436 (linux-oracle)
  derivatives: bug 1811420 (linux-raspi2), bug 1811421 (linux-oem), bug 1811422 
(linux-aws), bug 1811423 (linux-azure), bug 1811424 (linux-gcp), bug 1811425 
(linux-kvm), bug 1811427 (linux-oracle)
  -- swm properties --
  phase: Packaging -- uploaded
  phase-changed: Monday, 14. January 2019 11:48 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete

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

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


  1   2   3   4   >