[Kernel-packages] [Bug 1815562] [NEW] BIOS boot sequence changed by update

2019-02-11 Thread Søren Bredlund Caspersen
Public bug reported:

During the two last updates my boot-order has been changed.

I dual-boot windows and ubuntu on my secure-boot laptop.

This is a work-laptop, and I need it to boot windows first, so that is the 
setup i have chosen in the bios.
When I need Ubuntu, I manually choose that option when booting.
I don't think the ubuntu update should change boot-order in the bios, to put 
Ubuntu first.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-45-generic 4.15.0-45.48
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  sbc1502 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 12 08:25:35 2019
InstallationDate: Installed on 2019-01-14 (28 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: LENOVO 20L8S9N300
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=f68671ab-b47f-48a5-8a68-a5e26c61bdac ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-45-generic N/A
 linux-backports-modules-4.15.0-45-generic  N/A
 linux-firmware 1.173.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/07/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N22ET50W (1.27 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20L8S9N300
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET50W(1.27):bd11/07/2018:svnLENOVO:pn20L8S9N300:pvrThinkPadT480s:rvnLENOVO:rn20L8S9N300:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T480s
dmi.product.name: 20L8S9N300
dmi.product.version: ThinkPad T480s
dmi.sys.vendor: LENOVO

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


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

Title:
  BIOS boot sequence changed by update

Status in linux package in Ubuntu:
  New

Bug description:
  During the two last updates my boot-order has been changed.

  I dual-boot windows and ubuntu on my secure-boot laptop.

  This is a work-laptop, and I need it to boot windows first, so that is the 
setup i have chosen in the bios.
  When I need Ubuntu, I manually choose that option when booting.
  I don't think the ubuntu update should change boot-order in the bios, to put 
Ubuntu first.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sbc1502 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 12 08:25:35 2019
  InstallationDate: Installed on 2019-01-14 (28 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20L8S9N300
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=f68671ab-b47f-48a5-8a68-a5e26c61bdac ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/07/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET50W (1.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S9N300
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET50W(1.27):bd11/07/2018:svnLENOVO:pn20L8S9N300:pvrThinkPadT480s:rvnLENOVO:rn20L8S9N300:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S9N300
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1778844] Re: nvme multipath does not report path relationships

2019-02-11 Thread Andrew Cloke
Thanks. Closing out the bug.

** Changed in: ubuntu-power-systems
   Status: In Progress => Won't Fix

** Changed in: initramfs-tools (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: initramfs-tools (Ubuntu Bionic)
   Status: Confirmed => Invalid

** Changed in: initramfs-tools (Ubuntu Cosmic)
   Status: Confirmed => Invalid

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

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

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

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

Title:
  nvme multipath does not report path relationships

Status in The Ubuntu-power-systems project:
  Won't Fix
Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  Invalid
Status in initramfs-tools source package in Bionic:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in makedumpfile source package in Bionic:
  Invalid
Status in initramfs-tools source package in Cosmic:
  Invalid
Status in linux source package in Cosmic:
  Invalid
Status in makedumpfile source package in Cosmic:
  Invalid

Bug description:
  Problem Description:
  ===
  After triggering crash ,kdump is not working & system enters into initramfs 
state

  Steps to re-create:
  ==

  >. woo is installed ubuntu180401 kernel

  root@woo:~# uname -a
  Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
  root@woo:~#

  >. Crashkernel value as below

  root@woo:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   503G2.0G501G 13M279M
499G
  Swap:  2.0G  0B2.0G

  root@woo:~# cat /proc/cmdline
  root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
crashkernel=8192M

  >  kdump status

  root@woo:~#  kdump-config status
  current state   : ready to kdump

  root@woo:~#  kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.15.0-23-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  root@woo:~# dmesg | grep Reser
  [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System 
RAM: 524288MB)
  [0.00] cma: Reserved 26224 MiB at 0x20399500
  [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The 
term "Broadcom" refers to Broadcom Limited and/or its subsidiaries.

  > Triggered crash

  root@woo:~# echo 1 > /proc/sys/kernel/sysrq
  root@woo:~# echo c > /proc/sysrq-trigger
  [   73.056308] sysrq: SysRq : Trigger a crash
  [   73.056357] Unable to handle kernel paging request for data at address 
0x
  [   73.056459] Faulting instruction address: 0xc07f24c8
  [   73.056543] Oops: Kernel access of bad area, sig: 11 [#1]
  [   73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV
  [   73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 
esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) 
mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx 
vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 
powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd 
auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables 
autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc 
ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink 
syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops 
nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc
  [   73.057601]  tg3 libahci nvme_core pnv_php
  [   73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G   OE
4.15.0-23-generic #25-Ubuntu
  [   73.057767] NIP:  c07f24c8 LR: c07f3568 CTR: 
c07f24a0
  [   73.057868] REGS: c03f8269f9f0 TRAP: 0300   Tainted: G   OE
 (4.15.0-23-generic)
  [   73.057986] MSR:  90009033   CR: 2822 
 XER: 2004
  [   73.058099] CFAR: c07f3564 DAR:  DSISR: 4200 
SOFTE: 1
  [   73.058099] GPR00: c07f3568 

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

2019-02-11 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/1815561

Title:
  touchpad not recognized

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  touchpad not recognized.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 12 02:25:52 2019
  MachineType: I-Life Digital Technologies LLC ZED AIR
  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-45-generic 
root=UUID=8e451b7e-1777-4606-a6af-3218b2a90d72 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.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: ilife.Wi314.NANNEBN09
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: ZED AIR
  dmi.board.vendor: I-Life Digital Technologies LLC
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrilife.Wi314.NANNEBN09:bd08/20/2016:svnI-LifeDigitalTechnologiesLLC:pnZEDAIR:pvrV1.00.01:rvnI-LifeDigitalTechnologiesLLC:rnZEDAIR:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: 10.1 Tablet PC
  dmi.product.name: ZED AIR
  dmi.product.version: V1.00.01
  dmi.sys.vendor: I-Life Digital Technologies LLC

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

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


[Kernel-packages] [Bug 1815561] [NEW] touchpad not recognized

2019-02-11 Thread kutbi...@gmail.com
Public bug reported:

touchpad not recognized.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-45-generic 4.15.0-45.48
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 12 02:25:52 2019
MachineType: I-Life Digital Technologies LLC ZED AIR
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-45-generic 
root=UUID=8e451b7e-1777-4606-a6af-3218b2a90d72 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.
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-45-generic N/A
 linux-backports-modules-4.15.0-45-generic  N/A
 linux-firmware 1.173.3
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/20/2016
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: ilife.Wi314.NANNEBN09
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: ZED AIR
dmi.board.vendor: I-Life Digital Technologies LLC
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnINSYDECorp.:bvrilife.Wi314.NANNEBN09:bd08/20/2016:svnI-LifeDigitalTechnologiesLLC:pnZEDAIR:pvrV1.00.01:rvnI-LifeDigitalTechnologiesLLC:rnZEDAIR:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: 10.1 Tablet PC
dmi.product.name: ZED AIR
dmi.product.version: V1.00.01
dmi.sys.vendor: I-Life Digital Technologies LLC

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

Title:
  touchpad not recognized

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  touchpad not recognized.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 12 02:25:52 2019
  MachineType: I-Life Digital Technologies LLC ZED AIR
  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-45-generic 
root=UUID=8e451b7e-1777-4606-a6af-3218b2a90d72 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.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: ilife.Wi314.NANNEBN09
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: ZED AIR
  dmi.board.vendor: I-Life Digital Technologies LLC
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrilife.Wi314.NANNEBN09:bd08/20/2016:svnI-LifeDigitalTechnologiesLLC:pnZEDAIR:pvrV1.00.01:rvnI-LifeDigitalTechnologiesLLC:rnZEDAIR:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: 10.1 Tablet PC
  dmi.product.name: ZED AIR
  dmi.product.version: V1.00.01
  dmi.sys.vendor: I-Life Digital Technologies LLC

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1811660] Re: [SRU] Unable to modify/create-namespace over NVDIMM-N

2019-02-11 Thread Sujith Pandel
Another issue pops-up, looks like there are a few nvdimm patches that
require backporting:

# ndctl create-namespace -e "namespace0.0" -m fsdax -f -vvv
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(256 byte) labels
libndctl: ndctl_dimm_enable: nmem0: failed to enable
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(128 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(128 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(128 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(128 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(128 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(128 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(128 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(128 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(128 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(128 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(128 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(128 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(128 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(128 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(128 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(128 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(128 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(128 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(128 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(128 byte) labels
libndctl: ndctl_dimm_enable: nmem0: failed to enable
enable_labels:945: region0: failed to initialize labels
namespace_reconfig:977: region0: no idle namespace seed
failed to reconfigure namespace: No such device

root@ubuntu:~# ndctl -v
61.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/1811660

Title:
  [SRU] Unable to modify/create-namespace over NVDIMM-N

Status in The Dell-poweredge project:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  Users are unable to modify or create namespaces over NVDIMM-N

  [Test Case]

  Steps to Reproduce:
  1. Setup a Dell EMC 14G server R740xd server with NVDIMM-N, update BIOS & 
NVDIMM firmware to latest available to customers.
  2. Install and boot to Ubuntu 18.04
  3. Notice that no pmems are enumerated.
  4. Try #ndctl create-namespace -> Failure with 

[Kernel-packages] [Bug 1771431]

2019-02-11 Thread mpolovka
Keyboard is sending extra byte with each key-press, as temporary workaaround 
you can use mapping in this repository (tested on Fedora 28 with 4.20 kernel)
https://github.com/miskopo/lenovo-professional-wireless-kbd-linux-driver

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

Title:
  Lenovo Essential Wireless Keyboard doesn't works (Primax Electronics
  manufacturer)

Status in linux:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in linux package in Fedora:
  Unknown

Bug description:
  Hi
  I got an issue on Ubuntu 18.04 with latest packages.
  uname -a:
  Linux MyLaptop 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  lshw:
    *-usb:0
     description: Keyboard
     product: Lenovo USB Receiver
     vendor: Lenovo
     physical id: 3
     bus info: usb@1:3
     version: 1.05
     capabilities: usb-2.00
     configuration: driver=usbhid maxpower=100mA speed=12Mbit/s

  My wireless keyboard is not working, Ubuntu only recognize some
  special keys (Super, Ctrl, Shift, Alt)

  This is a Mouse+Keyboard combo using a wireless receiver by usb:

  lsusb:
  Bus 001 Device 005: ID 17ef:609b Lenovo

  Mouse works fine, and in Windows 10 it works with no issues.

  I found multiple reported problems with this keyboard in other distros (and 
from Asus too, as the real manufacturer is Primax Electronics).
  
https://forums.lenovo.com/t5/Linux-Discussion/Professional-Wireless-Keyboard-not-working-on-Linux/td-p/3726486
  https://ubuntuforums.org/showthread.php?t=2378862
  
https://askubuntu.com/questions/897729/lenovo-professional-wireless-keyboard-and-mouse-combo-not-working-in-ubuntu
  
https://forums.linuxmint.com/viewtopic.php?f=49=260093=20a073d5dd8abb1b7f23be608d7fdfd7
  
https://unix.stackexchange.com/questions/377830/linux-hid-driver-for-primax-wireless-keyboards/

  REPORTS ON KERNEL MAILING LISTS:
  https://www.spinics.net/lists/linux-usb/msg168719.html
  https://www.spinics.net/lists/linux-input/msg56210.html
  https://www.spinics.net/lists/linux-usb/msg173012.html
  https://www.spinics.net/lists/linux-input/msg58221.html

  There is a workaround (I still didn't tried) but it needs to compile an 
specific driver.
  https://github.com/y-trudeau/linux_lenovo_ultraslim_plus

  There is already a kernel report about this.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-generic 4.15.0.20.23
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  julian 1342 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 15 15:53:41 2018
  InstallationDate: Installed on 2018-05-14 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20FJS0NT07
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=818481db-36cb-4dba-8da5-8ecf15750b3b ro noapic acpi=off vt.handoff=1
  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
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/27/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET38W (1.25 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FJS0NT07
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET38W(1.25):bd03/27/2018:svnLENOVO:pn20FJS0NT07:pvrThinkPadT560:rvnLENOVO:rn20FJS0NT07:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T560
  dmi.product.name: 20FJS0NT07
  dmi.product.version: ThinkPad T560
  dmi.sys.vendor: LENOVO

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

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


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

2019-02-11 Thread bugproxy
--- Comment From hbath...@in.ibm.com 2019-02-12 01:11 EDT---
(In reply to comment #83)
[...]
> Will try to increase to some more above 4096M and retry it.

The recommendations are based on a few assumptions that don't apply to all 
machines.
So, hitting OOM in this case is not surprising in that sense. As increasing 
crashkernel
value helped, we can consider the original issue reported here resolved..

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

Title:
  nvme multipath does not report path relationships

Status in The Ubuntu-power-systems project:
  In Progress
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in makedumpfile package in Ubuntu:
  Invalid
Status in initramfs-tools source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in makedumpfile source package in Bionic:
  Invalid
Status in initramfs-tools source package in Cosmic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed
Status in makedumpfile source package in Cosmic:
  Invalid

Bug description:
  Problem Description:
  ===
  After triggering crash ,kdump is not working & system enters into initramfs 
state

  Steps to re-create:
  ==

  >. woo is installed ubuntu180401 kernel

  root@woo:~# uname -a
  Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
  root@woo:~#

  >. Crashkernel value as below

  root@woo:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   503G2.0G501G 13M279M
499G
  Swap:  2.0G  0B2.0G

  root@woo:~# cat /proc/cmdline
  root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
crashkernel=8192M

  >  kdump status

  root@woo:~#  kdump-config status
  current state   : ready to kdump

  root@woo:~#  kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.15.0-23-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  root@woo:~# dmesg | grep Reser
  [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System 
RAM: 524288MB)
  [0.00] cma: Reserved 26224 MiB at 0x20399500
  [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The 
term "Broadcom" refers to Broadcom Limited and/or its subsidiaries.

  > Triggered crash

  root@woo:~# echo 1 > /proc/sys/kernel/sysrq
  root@woo:~# echo c > /proc/sysrq-trigger
  [   73.056308] sysrq: SysRq : Trigger a crash
  [   73.056357] Unable to handle kernel paging request for data at address 
0x
  [   73.056459] Faulting instruction address: 0xc07f24c8
  [   73.056543] Oops: Kernel access of bad area, sig: 11 [#1]
  [   73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV
  [   73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 
esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) 
mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx 
vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 
powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd 
auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables 
autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc 
ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink 
syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops 
nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc
  [   73.057601]  tg3 libahci nvme_core pnv_php
  [   73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G   OE
4.15.0-23-generic #25-Ubuntu
  [   73.057767] NIP:  c07f24c8 LR: c07f3568 CTR: 
c07f24a0
  [   73.057868] REGS: c03f8269f9f0 TRAP: 0300   Tainted: G   OE
 (4.15.0-23-generic)
  [   73.057986] MSR:  90009033   CR: 2822 
 XER: 2004
  [   73.058099] CFAR: c07f3564 DAR:  DSISR: 4200 
SOFTE: 1
  [   73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 
0063
  [   73.058099] GPR04: c03fef47ce18 c03fef494368 90009033 
31da0058
  [  

[Kernel-packages] [Bug 1811660] Re: [SRU] Unable to modify/create-namespace over NVDIMM-N

2019-02-11 Thread Khaled El Mously
I have built a bionic test kernel with those fixes (+2 others needed for
backporting) for testing.

The kernel can be found at:

https://kernel.ubuntu.com/~kmously/1811660/kernel-kmously-96d0cc8-l7Et/

@Sujith Pandel can you please confirm of this kernel fixes the problem
or not?


Thanks.

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

Title:
  [SRU] Unable to modify/create-namespace over NVDIMM-N

Status in The Dell-poweredge project:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  Users are unable to modify or create namespaces over NVDIMM-N

  [Test Case]

  Steps to Reproduce:
  1. Setup a Dell EMC 14G server R740xd server with NVDIMM-N, update BIOS & 
NVDIMM firmware to latest available to customers.
  2. Install and boot to Ubuntu 18.04
  3. Notice that no pmems are enumerated.
  4. Try #ndctl create-namespace -> Failure with device or resource busy.

  Actual results:
  No pmems are enumerated, cannot create namespaces.
  If pmems are already present, then cannot modify the namespaces.

  Expected results:
  namespace creation should be possible

  
  [Regression Potential] 

  The Regression Risk is low, Intel not impacted but Dell is.

  
  [Other Info]
  Additional Info:
  * Seen with upstream linux-4.20.2 also.

  * Upstream bug report -
  https://github.com/pmem/ndctl/issues/78

  * Upstream kernel patch:
  https://lists.01.org/pipermail/linux-nvdimm/2019-January/019435.html

  Request you to incorporate it in bionic and xenial kernels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-poweredge/+bug/1811660/+subscriptions

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


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

2019-02-11 Thread Alan Diggs
apport information

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

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

Title:
  System lag/stuttering, mouse movement and window drag choppiness with
  Vega 64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In Ubuntu 18.10 and beyond, the desktop is quite laggy and choppy, to
  the point where moving windows around the screen appears to be a stop-
  motion at 5FPS or so. Mouse movement is choppy, animations are
  grindingly slow, and this overall slowness does seem to affect text
  input into GUI dialogs (missed keys, etc). However, performance is
  fine in TTY, even with more active programs like HTOP and full-screen
  text images like NCURSES looking stuff. This issue wasn't present in
  18.04(.1) but could be triggered by using a newer kernel or updating
  the MESA stack. I'm using a STRIX Vega 64 for my GPU and I've
  installed Ubuntu 19.04 and only run updates and installed inxi and lm-
  sensors so I can provide more data if possible. (EDIT: Would also like
  to note that CPU usage is pretty low, and there's nothing pinning the
  CPU or spiking it from time to time. I believe this is solely
  graphical, but I am *not* 100% certain at any rate.)

  System:
    Host: schyken-ryzen-horizon Kernel: 4.19.0-12-generic x86_64 bits: 64
    compiler: gcc v: 8.2.0 Desktop: Gnome 3.30.2
    Distro: Ubuntu 19.04 (Disco Dingo)
  Machine:
    Type: Desktop Mobo: ASUSTeK model: PRIME B350-PLUS v: Rev X.0x
    serial:  UEFI: American Megatrends v: 4207 date: 12/07/2018
  CPU:
    Topology: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+
    rev: 2 L2 cache: 4096 KiB
    flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
    bogomips: 111784
    Speed: 1374 MHz min/max: 1550/3500 MHz Core speeds (MHz): 1: 1375 2: 1374
    3: 2779 4: 1700 5: 2793 6: 2625 7: 1270 8: 1270 9: 1375 10: 1375 11: 1375
    12: 1375 13: 1375 14: 1370 15: 1267 16: 1270
  Graphics:
    Device-1: AMD Vega 10 XT [Radeon RX Vega 64] vendor: ASUSTeK
    driver: amdgpu v: kernel bus ID: 0c:00.0
    Display: x11 server: X.Org 1.20.3 driver: amdgpu
    resolution: 2560x1440~60Hz
    OpenGL:
    renderer: Radeon RX Vega (VEGA10 DRM 3.27.0 4.19.0-12-generic LLVM 7.0.1)
    v: 4.5 Mesa 18.3.2 direct render: Yes
  Audio:
    Device-1: Creative Labs Sound Core3D [Sound Blaster Recon3D / Z-Series]
    driver: snd_hda_intel v: kernel bus ID: 09:00.0
    Device-2: AMD driver: snd_hda_intel v: kernel bus ID: 0c:00.1
    Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel bus ID: 0e:00.3
    Device-4: Logitech HD Pro Webcam C920 type: USB
    driver: snd-usb-audio,uvcvideo bus ID: 3-3:3
    Device-5: C-Media type: USB driver: hid-generic,snd-usb-audio,usbhid
    bus ID: 1-1:2
    Sound Server: ALSA v: k4.19.0-12-generic
  Network:
    Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK driver: r8169 v: kernel port: f000 bus ID: 04:00.0
    IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: 
  Drives:
    Local Storage: total: 2.05 TiB used: 6.93 GiB (0.3%)
    ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 EVO 250GB
    size: 232.89 GiB
    ID-2: /dev/sda vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 22 C
    ID-3: /dev/sdb vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 19 C
    ID-4: /dev/sdc vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 21 C
    ID-5: /dev/sdd vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 21 C
  Partition:
    ID-1: / size: 91.29 GiB used: 6.92 GiB (7.6%) fs: ext4 dev: /dev/nvme0n1p3
  Sensors:
    System Temperatures: cpu: 27.2 C mobo: N/A gpu: amdgpu temp: 29 C
    Fan Speeds (RPM): cpu: 0 gpu: amdgpu fan: 720
  Info:
    Processes: 373 Uptime: 2m Memory: 31.41 GiB used: 1.40 GiB (4.5%)
    Init: systemd runlevel: 5 Compilers: gcc: 8.2.0 Shell: bash v: 5.0.2
    inxi: 3.0.32
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-02-11 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-generic 
root=UUID=66ecdf59-50f0-49c7-befa-d800622a2e25 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
  

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

2019-02-11 Thread Alan Diggs
apport information

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

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

Title:
  System lag/stuttering, mouse movement and window drag choppiness with
  Vega 64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In Ubuntu 18.10 and beyond, the desktop is quite laggy and choppy, to
  the point where moving windows around the screen appears to be a stop-
  motion at 5FPS or so. Mouse movement is choppy, animations are
  grindingly slow, and this overall slowness does seem to affect text
  input into GUI dialogs (missed keys, etc). However, performance is
  fine in TTY, even with more active programs like HTOP and full-screen
  text images like NCURSES looking stuff. This issue wasn't present in
  18.04(.1) but could be triggered by using a newer kernel or updating
  the MESA stack. I'm using a STRIX Vega 64 for my GPU and I've
  installed Ubuntu 19.04 and only run updates and installed inxi and lm-
  sensors so I can provide more data if possible. (EDIT: Would also like
  to note that CPU usage is pretty low, and there's nothing pinning the
  CPU or spiking it from time to time. I believe this is solely
  graphical, but I am *not* 100% certain at any rate.)

  System:
    Host: schyken-ryzen-horizon Kernel: 4.19.0-12-generic x86_64 bits: 64
    compiler: gcc v: 8.2.0 Desktop: Gnome 3.30.2
    Distro: Ubuntu 19.04 (Disco Dingo)
  Machine:
    Type: Desktop Mobo: ASUSTeK model: PRIME B350-PLUS v: Rev X.0x
    serial:  UEFI: American Megatrends v: 4207 date: 12/07/2018
  CPU:
    Topology: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+
    rev: 2 L2 cache: 4096 KiB
    flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
    bogomips: 111784
    Speed: 1374 MHz min/max: 1550/3500 MHz Core speeds (MHz): 1: 1375 2: 1374
    3: 2779 4: 1700 5: 2793 6: 2625 7: 1270 8: 1270 9: 1375 10: 1375 11: 1375
    12: 1375 13: 1375 14: 1370 15: 1267 16: 1270
  Graphics:
    Device-1: AMD Vega 10 XT [Radeon RX Vega 64] vendor: ASUSTeK
    driver: amdgpu v: kernel bus ID: 0c:00.0
    Display: x11 server: X.Org 1.20.3 driver: amdgpu
    resolution: 2560x1440~60Hz
    OpenGL:
    renderer: Radeon RX Vega (VEGA10 DRM 3.27.0 4.19.0-12-generic LLVM 7.0.1)
    v: 4.5 Mesa 18.3.2 direct render: Yes
  Audio:
    Device-1: Creative Labs Sound Core3D [Sound Blaster Recon3D / Z-Series]
    driver: snd_hda_intel v: kernel bus ID: 09:00.0
    Device-2: AMD driver: snd_hda_intel v: kernel bus ID: 0c:00.1
    Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel bus ID: 0e:00.3
    Device-4: Logitech HD Pro Webcam C920 type: USB
    driver: snd-usb-audio,uvcvideo bus ID: 3-3:3
    Device-5: C-Media type: USB driver: hid-generic,snd-usb-audio,usbhid
    bus ID: 1-1:2
    Sound Server: ALSA v: k4.19.0-12-generic
  Network:
    Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK driver: r8169 v: kernel port: f000 bus ID: 04:00.0
    IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: 
  Drives:
    Local Storage: total: 2.05 TiB used: 6.93 GiB (0.3%)
    ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 EVO 250GB
    size: 232.89 GiB
    ID-2: /dev/sda vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 22 C
    ID-3: /dev/sdb vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 19 C
    ID-4: /dev/sdc vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 21 C
    ID-5: /dev/sdd vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 21 C
  Partition:
    ID-1: / size: 91.29 GiB used: 6.92 GiB (7.6%) fs: ext4 dev: /dev/nvme0n1p3
  Sensors:
    System Temperatures: cpu: 27.2 C mobo: N/A gpu: amdgpu temp: 29 C
    Fan Speeds (RPM): cpu: 0 gpu: amdgpu fan: 720
  Info:
    Processes: 373 Uptime: 2m Memory: 31.41 GiB used: 1.40 GiB (4.5%)
    Init: systemd runlevel: 5 Compilers: gcc: 8.2.0 Shell: bash v: 5.0.2
    inxi: 3.0.32
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-02-11 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-generic 
root=UUID=66ecdf59-50f0-49c7-befa-d800622a2e25 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
  

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

2019-02-11 Thread Alan Diggs
apport information

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

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

Title:
  System lag/stuttering, mouse movement and window drag choppiness with
  Vega 64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In Ubuntu 18.10 and beyond, the desktop is quite laggy and choppy, to
  the point where moving windows around the screen appears to be a stop-
  motion at 5FPS or so. Mouse movement is choppy, animations are
  grindingly slow, and this overall slowness does seem to affect text
  input into GUI dialogs (missed keys, etc). However, performance is
  fine in TTY, even with more active programs like HTOP and full-screen
  text images like NCURSES looking stuff. This issue wasn't present in
  18.04(.1) but could be triggered by using a newer kernel or updating
  the MESA stack. I'm using a STRIX Vega 64 for my GPU and I've
  installed Ubuntu 19.04 and only run updates and installed inxi and lm-
  sensors so I can provide more data if possible. (EDIT: Would also like
  to note that CPU usage is pretty low, and there's nothing pinning the
  CPU or spiking it from time to time. I believe this is solely
  graphical, but I am *not* 100% certain at any rate.)

  System:
    Host: schyken-ryzen-horizon Kernel: 4.19.0-12-generic x86_64 bits: 64
    compiler: gcc v: 8.2.0 Desktop: Gnome 3.30.2
    Distro: Ubuntu 19.04 (Disco Dingo)
  Machine:
    Type: Desktop Mobo: ASUSTeK model: PRIME B350-PLUS v: Rev X.0x
    serial:  UEFI: American Megatrends v: 4207 date: 12/07/2018
  CPU:
    Topology: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+
    rev: 2 L2 cache: 4096 KiB
    flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
    bogomips: 111784
    Speed: 1374 MHz min/max: 1550/3500 MHz Core speeds (MHz): 1: 1375 2: 1374
    3: 2779 4: 1700 5: 2793 6: 2625 7: 1270 8: 1270 9: 1375 10: 1375 11: 1375
    12: 1375 13: 1375 14: 1370 15: 1267 16: 1270
  Graphics:
    Device-1: AMD Vega 10 XT [Radeon RX Vega 64] vendor: ASUSTeK
    driver: amdgpu v: kernel bus ID: 0c:00.0
    Display: x11 server: X.Org 1.20.3 driver: amdgpu
    resolution: 2560x1440~60Hz
    OpenGL:
    renderer: Radeon RX Vega (VEGA10 DRM 3.27.0 4.19.0-12-generic LLVM 7.0.1)
    v: 4.5 Mesa 18.3.2 direct render: Yes
  Audio:
    Device-1: Creative Labs Sound Core3D [Sound Blaster Recon3D / Z-Series]
    driver: snd_hda_intel v: kernel bus ID: 09:00.0
    Device-2: AMD driver: snd_hda_intel v: kernel bus ID: 0c:00.1
    Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel bus ID: 0e:00.3
    Device-4: Logitech HD Pro Webcam C920 type: USB
    driver: snd-usb-audio,uvcvideo bus ID: 3-3:3
    Device-5: C-Media type: USB driver: hid-generic,snd-usb-audio,usbhid
    bus ID: 1-1:2
    Sound Server: ALSA v: k4.19.0-12-generic
  Network:
    Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK driver: r8169 v: kernel port: f000 bus ID: 04:00.0
    IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: 
  Drives:
    Local Storage: total: 2.05 TiB used: 6.93 GiB (0.3%)
    ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 EVO 250GB
    size: 232.89 GiB
    ID-2: /dev/sda vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 22 C
    ID-3: /dev/sdb vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 19 C
    ID-4: /dev/sdc vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 21 C
    ID-5: /dev/sdd vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 21 C
  Partition:
    ID-1: / size: 91.29 GiB used: 6.92 GiB (7.6%) fs: ext4 dev: /dev/nvme0n1p3
  Sensors:
    System Temperatures: cpu: 27.2 C mobo: N/A gpu: amdgpu temp: 29 C
    Fan Speeds (RPM): cpu: 0 gpu: amdgpu fan: 720
  Info:
    Processes: 373 Uptime: 2m Memory: 31.41 GiB used: 1.40 GiB (4.5%)
    Init: systemd runlevel: 5 Compilers: gcc: 8.2.0 Shell: bash v: 5.0.2
    inxi: 3.0.32
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-02-11 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-generic 
root=UUID=66ecdf59-50f0-49c7-befa-d800622a2e25 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
  

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

2019-02-11 Thread Alan Diggs
apport information

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

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

Title:
  System lag/stuttering, mouse movement and window drag choppiness with
  Vega 64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In Ubuntu 18.10 and beyond, the desktop is quite laggy and choppy, to
  the point where moving windows around the screen appears to be a stop-
  motion at 5FPS or so. Mouse movement is choppy, animations are
  grindingly slow, and this overall slowness does seem to affect text
  input into GUI dialogs (missed keys, etc). However, performance is
  fine in TTY, even with more active programs like HTOP and full-screen
  text images like NCURSES looking stuff. This issue wasn't present in
  18.04(.1) but could be triggered by using a newer kernel or updating
  the MESA stack. I'm using a STRIX Vega 64 for my GPU and I've
  installed Ubuntu 19.04 and only run updates and installed inxi and lm-
  sensors so I can provide more data if possible. (EDIT: Would also like
  to note that CPU usage is pretty low, and there's nothing pinning the
  CPU or spiking it from time to time. I believe this is solely
  graphical, but I am *not* 100% certain at any rate.)

  System:
    Host: schyken-ryzen-horizon Kernel: 4.19.0-12-generic x86_64 bits: 64
    compiler: gcc v: 8.2.0 Desktop: Gnome 3.30.2
    Distro: Ubuntu 19.04 (Disco Dingo)
  Machine:
    Type: Desktop Mobo: ASUSTeK model: PRIME B350-PLUS v: Rev X.0x
    serial:  UEFI: American Megatrends v: 4207 date: 12/07/2018
  CPU:
    Topology: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+
    rev: 2 L2 cache: 4096 KiB
    flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
    bogomips: 111784
    Speed: 1374 MHz min/max: 1550/3500 MHz Core speeds (MHz): 1: 1375 2: 1374
    3: 2779 4: 1700 5: 2793 6: 2625 7: 1270 8: 1270 9: 1375 10: 1375 11: 1375
    12: 1375 13: 1375 14: 1370 15: 1267 16: 1270
  Graphics:
    Device-1: AMD Vega 10 XT [Radeon RX Vega 64] vendor: ASUSTeK
    driver: amdgpu v: kernel bus ID: 0c:00.0
    Display: x11 server: X.Org 1.20.3 driver: amdgpu
    resolution: 2560x1440~60Hz
    OpenGL:
    renderer: Radeon RX Vega (VEGA10 DRM 3.27.0 4.19.0-12-generic LLVM 7.0.1)
    v: 4.5 Mesa 18.3.2 direct render: Yes
  Audio:
    Device-1: Creative Labs Sound Core3D [Sound Blaster Recon3D / Z-Series]
    driver: snd_hda_intel v: kernel bus ID: 09:00.0
    Device-2: AMD driver: snd_hda_intel v: kernel bus ID: 0c:00.1
    Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel bus ID: 0e:00.3
    Device-4: Logitech HD Pro Webcam C920 type: USB
    driver: snd-usb-audio,uvcvideo bus ID: 3-3:3
    Device-5: C-Media type: USB driver: hid-generic,snd-usb-audio,usbhid
    bus ID: 1-1:2
    Sound Server: ALSA v: k4.19.0-12-generic
  Network:
    Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK driver: r8169 v: kernel port: f000 bus ID: 04:00.0
    IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: 
  Drives:
    Local Storage: total: 2.05 TiB used: 6.93 GiB (0.3%)
    ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 EVO 250GB
    size: 232.89 GiB
    ID-2: /dev/sda vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 22 C
    ID-3: /dev/sdb vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 19 C
    ID-4: /dev/sdc vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 21 C
    ID-5: /dev/sdd vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 21 C
  Partition:
    ID-1: / size: 91.29 GiB used: 6.92 GiB (7.6%) fs: ext4 dev: /dev/nvme0n1p3
  Sensors:
    System Temperatures: cpu: 27.2 C mobo: N/A gpu: amdgpu temp: 29 C
    Fan Speeds (RPM): cpu: 0 gpu: amdgpu fan: 720
  Info:
    Processes: 373 Uptime: 2m Memory: 31.41 GiB used: 1.40 GiB (4.5%)
    Init: systemd runlevel: 5 Compilers: gcc: 8.2.0 Shell: bash v: 5.0.2
    inxi: 3.0.32
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-02-11 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-generic 
root=UUID=66ecdf59-50f0-49c7-befa-d800622a2e25 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 

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

2019-02-11 Thread Alan Diggs
apport information

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

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

Title:
  System lag/stuttering, mouse movement and window drag choppiness with
  Vega 64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In Ubuntu 18.10 and beyond, the desktop is quite laggy and choppy, to
  the point where moving windows around the screen appears to be a stop-
  motion at 5FPS or so. Mouse movement is choppy, animations are
  grindingly slow, and this overall slowness does seem to affect text
  input into GUI dialogs (missed keys, etc). However, performance is
  fine in TTY, even with more active programs like HTOP and full-screen
  text images like NCURSES looking stuff. This issue wasn't present in
  18.04(.1) but could be triggered by using a newer kernel or updating
  the MESA stack. I'm using a STRIX Vega 64 for my GPU and I've
  installed Ubuntu 19.04 and only run updates and installed inxi and lm-
  sensors so I can provide more data if possible. (EDIT: Would also like
  to note that CPU usage is pretty low, and there's nothing pinning the
  CPU or spiking it from time to time. I believe this is solely
  graphical, but I am *not* 100% certain at any rate.)

  System:
    Host: schyken-ryzen-horizon Kernel: 4.19.0-12-generic x86_64 bits: 64
    compiler: gcc v: 8.2.0 Desktop: Gnome 3.30.2
    Distro: Ubuntu 19.04 (Disco Dingo)
  Machine:
    Type: Desktop Mobo: ASUSTeK model: PRIME B350-PLUS v: Rev X.0x
    serial:  UEFI: American Megatrends v: 4207 date: 12/07/2018
  CPU:
    Topology: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+
    rev: 2 L2 cache: 4096 KiB
    flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
    bogomips: 111784
    Speed: 1374 MHz min/max: 1550/3500 MHz Core speeds (MHz): 1: 1375 2: 1374
    3: 2779 4: 1700 5: 2793 6: 2625 7: 1270 8: 1270 9: 1375 10: 1375 11: 1375
    12: 1375 13: 1375 14: 1370 15: 1267 16: 1270
  Graphics:
    Device-1: AMD Vega 10 XT [Radeon RX Vega 64] vendor: ASUSTeK
    driver: amdgpu v: kernel bus ID: 0c:00.0
    Display: x11 server: X.Org 1.20.3 driver: amdgpu
    resolution: 2560x1440~60Hz
    OpenGL:
    renderer: Radeon RX Vega (VEGA10 DRM 3.27.0 4.19.0-12-generic LLVM 7.0.1)
    v: 4.5 Mesa 18.3.2 direct render: Yes
  Audio:
    Device-1: Creative Labs Sound Core3D [Sound Blaster Recon3D / Z-Series]
    driver: snd_hda_intel v: kernel bus ID: 09:00.0
    Device-2: AMD driver: snd_hda_intel v: kernel bus ID: 0c:00.1
    Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel bus ID: 0e:00.3
    Device-4: Logitech HD Pro Webcam C920 type: USB
    driver: snd-usb-audio,uvcvideo bus ID: 3-3:3
    Device-5: C-Media type: USB driver: hid-generic,snd-usb-audio,usbhid
    bus ID: 1-1:2
    Sound Server: ALSA v: k4.19.0-12-generic
  Network:
    Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK driver: r8169 v: kernel port: f000 bus ID: 04:00.0
    IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: 
  Drives:
    Local Storage: total: 2.05 TiB used: 6.93 GiB (0.3%)
    ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 EVO 250GB
    size: 232.89 GiB
    ID-2: /dev/sda vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 22 C
    ID-3: /dev/sdb vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 19 C
    ID-4: /dev/sdc vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 21 C
    ID-5: /dev/sdd vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 21 C
  Partition:
    ID-1: / size: 91.29 GiB used: 6.92 GiB (7.6%) fs: ext4 dev: /dev/nvme0n1p3
  Sensors:
    System Temperatures: cpu: 27.2 C mobo: N/A gpu: amdgpu temp: 29 C
    Fan Speeds (RPM): cpu: 0 gpu: amdgpu fan: 720
  Info:
    Processes: 373 Uptime: 2m Memory: 31.41 GiB used: 1.40 GiB (4.5%)
    Init: systemd runlevel: 5 Compilers: gcc: 8.2.0 Shell: bash v: 5.0.2
    inxi: 3.0.32
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-02-11 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-generic 
root=UUID=66ecdf59-50f0-49c7-befa-d800622a2e25 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
  

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

2019-02-11 Thread Alan Diggs
apport information

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

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

Title:
  System lag/stuttering, mouse movement and window drag choppiness with
  Vega 64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In Ubuntu 18.10 and beyond, the desktop is quite laggy and choppy, to
  the point where moving windows around the screen appears to be a stop-
  motion at 5FPS or so. Mouse movement is choppy, animations are
  grindingly slow, and this overall slowness does seem to affect text
  input into GUI dialogs (missed keys, etc). However, performance is
  fine in TTY, even with more active programs like HTOP and full-screen
  text images like NCURSES looking stuff. This issue wasn't present in
  18.04(.1) but could be triggered by using a newer kernel or updating
  the MESA stack. I'm using a STRIX Vega 64 for my GPU and I've
  installed Ubuntu 19.04 and only run updates and installed inxi and lm-
  sensors so I can provide more data if possible. (EDIT: Would also like
  to note that CPU usage is pretty low, and there's nothing pinning the
  CPU or spiking it from time to time. I believe this is solely
  graphical, but I am *not* 100% certain at any rate.)

  System:
    Host: schyken-ryzen-horizon Kernel: 4.19.0-12-generic x86_64 bits: 64
    compiler: gcc v: 8.2.0 Desktop: Gnome 3.30.2
    Distro: Ubuntu 19.04 (Disco Dingo)
  Machine:
    Type: Desktop Mobo: ASUSTeK model: PRIME B350-PLUS v: Rev X.0x
    serial:  UEFI: American Megatrends v: 4207 date: 12/07/2018
  CPU:
    Topology: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+
    rev: 2 L2 cache: 4096 KiB
    flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
    bogomips: 111784
    Speed: 1374 MHz min/max: 1550/3500 MHz Core speeds (MHz): 1: 1375 2: 1374
    3: 2779 4: 1700 5: 2793 6: 2625 7: 1270 8: 1270 9: 1375 10: 1375 11: 1375
    12: 1375 13: 1375 14: 1370 15: 1267 16: 1270
  Graphics:
    Device-1: AMD Vega 10 XT [Radeon RX Vega 64] vendor: ASUSTeK
    driver: amdgpu v: kernel bus ID: 0c:00.0
    Display: x11 server: X.Org 1.20.3 driver: amdgpu
    resolution: 2560x1440~60Hz
    OpenGL:
    renderer: Radeon RX Vega (VEGA10 DRM 3.27.0 4.19.0-12-generic LLVM 7.0.1)
    v: 4.5 Mesa 18.3.2 direct render: Yes
  Audio:
    Device-1: Creative Labs Sound Core3D [Sound Blaster Recon3D / Z-Series]
    driver: snd_hda_intel v: kernel bus ID: 09:00.0
    Device-2: AMD driver: snd_hda_intel v: kernel bus ID: 0c:00.1
    Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel bus ID: 0e:00.3
    Device-4: Logitech HD Pro Webcam C920 type: USB
    driver: snd-usb-audio,uvcvideo bus ID: 3-3:3
    Device-5: C-Media type: USB driver: hid-generic,snd-usb-audio,usbhid
    bus ID: 1-1:2
    Sound Server: ALSA v: k4.19.0-12-generic
  Network:
    Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK driver: r8169 v: kernel port: f000 bus ID: 04:00.0
    IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: 
  Drives:
    Local Storage: total: 2.05 TiB used: 6.93 GiB (0.3%)
    ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 EVO 250GB
    size: 232.89 GiB
    ID-2: /dev/sda vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 22 C
    ID-3: /dev/sdb vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 19 C
    ID-4: /dev/sdc vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 21 C
    ID-5: /dev/sdd vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 21 C
  Partition:
    ID-1: / size: 91.29 GiB used: 6.92 GiB (7.6%) fs: ext4 dev: /dev/nvme0n1p3
  Sensors:
    System Temperatures: cpu: 27.2 C mobo: N/A gpu: amdgpu temp: 29 C
    Fan Speeds (RPM): cpu: 0 gpu: amdgpu fan: 720
  Info:
    Processes: 373 Uptime: 2m Memory: 31.41 GiB used: 1.40 GiB (4.5%)
    Init: systemd runlevel: 5 Compilers: gcc: 8.2.0 Shell: bash v: 5.0.2
    inxi: 3.0.32
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-02-11 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-generic 
root=UUID=66ecdf59-50f0-49c7-befa-d800622a2e25 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
  

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

2019-02-11 Thread Alan Diggs
apport information

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

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

Title:
  System lag/stuttering, mouse movement and window drag choppiness with
  Vega 64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In Ubuntu 18.10 and beyond, the desktop is quite laggy and choppy, to
  the point where moving windows around the screen appears to be a stop-
  motion at 5FPS or so. Mouse movement is choppy, animations are
  grindingly slow, and this overall slowness does seem to affect text
  input into GUI dialogs (missed keys, etc). However, performance is
  fine in TTY, even with more active programs like HTOP and full-screen
  text images like NCURSES looking stuff. This issue wasn't present in
  18.04(.1) but could be triggered by using a newer kernel or updating
  the MESA stack. I'm using a STRIX Vega 64 for my GPU and I've
  installed Ubuntu 19.04 and only run updates and installed inxi and lm-
  sensors so I can provide more data if possible. (EDIT: Would also like
  to note that CPU usage is pretty low, and there's nothing pinning the
  CPU or spiking it from time to time. I believe this is solely
  graphical, but I am *not* 100% certain at any rate.)

  System:
    Host: schyken-ryzen-horizon Kernel: 4.19.0-12-generic x86_64 bits: 64
    compiler: gcc v: 8.2.0 Desktop: Gnome 3.30.2
    Distro: Ubuntu 19.04 (Disco Dingo)
  Machine:
    Type: Desktop Mobo: ASUSTeK model: PRIME B350-PLUS v: Rev X.0x
    serial:  UEFI: American Megatrends v: 4207 date: 12/07/2018
  CPU:
    Topology: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+
    rev: 2 L2 cache: 4096 KiB
    flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
    bogomips: 111784
    Speed: 1374 MHz min/max: 1550/3500 MHz Core speeds (MHz): 1: 1375 2: 1374
    3: 2779 4: 1700 5: 2793 6: 2625 7: 1270 8: 1270 9: 1375 10: 1375 11: 1375
    12: 1375 13: 1375 14: 1370 15: 1267 16: 1270
  Graphics:
    Device-1: AMD Vega 10 XT [Radeon RX Vega 64] vendor: ASUSTeK
    driver: amdgpu v: kernel bus ID: 0c:00.0
    Display: x11 server: X.Org 1.20.3 driver: amdgpu
    resolution: 2560x1440~60Hz
    OpenGL:
    renderer: Radeon RX Vega (VEGA10 DRM 3.27.0 4.19.0-12-generic LLVM 7.0.1)
    v: 4.5 Mesa 18.3.2 direct render: Yes
  Audio:
    Device-1: Creative Labs Sound Core3D [Sound Blaster Recon3D / Z-Series]
    driver: snd_hda_intel v: kernel bus ID: 09:00.0
    Device-2: AMD driver: snd_hda_intel v: kernel bus ID: 0c:00.1
    Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel bus ID: 0e:00.3
    Device-4: Logitech HD Pro Webcam C920 type: USB
    driver: snd-usb-audio,uvcvideo bus ID: 3-3:3
    Device-5: C-Media type: USB driver: hid-generic,snd-usb-audio,usbhid
    bus ID: 1-1:2
    Sound Server: ALSA v: k4.19.0-12-generic
  Network:
    Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK driver: r8169 v: kernel port: f000 bus ID: 04:00.0
    IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: 
  Drives:
    Local Storage: total: 2.05 TiB used: 6.93 GiB (0.3%)
    ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 EVO 250GB
    size: 232.89 GiB
    ID-2: /dev/sda vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 22 C
    ID-3: /dev/sdb vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 19 C
    ID-4: /dev/sdc vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 21 C
    ID-5: /dev/sdd vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 21 C
  Partition:
    ID-1: / size: 91.29 GiB used: 6.92 GiB (7.6%) fs: ext4 dev: /dev/nvme0n1p3
  Sensors:
    System Temperatures: cpu: 27.2 C mobo: N/A gpu: amdgpu temp: 29 C
    Fan Speeds (RPM): cpu: 0 gpu: amdgpu fan: 720
  Info:
    Processes: 373 Uptime: 2m Memory: 31.41 GiB used: 1.40 GiB (4.5%)
    Init: systemd runlevel: 5 Compilers: gcc: 8.2.0 Shell: bash v: 5.0.2
    inxi: 3.0.32
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-02-11 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-generic 
root=UUID=66ecdf59-50f0-49c7-befa-d800622a2e25 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
  

[Kernel-packages] [Bug 1815510] AudioDevicesInUse.txt

2019-02-11 Thread Alan Diggs
apport information

** Attachment added: "AudioDevicesInUse.txt"
   
https://bugs.launchpad.net/bugs/1815510/+attachment/5237889/+files/AudioDevicesInUse.txt

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

Title:
  System lag/stuttering, mouse movement and window drag choppiness with
  Vega 64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In Ubuntu 18.10 and beyond, the desktop is quite laggy and choppy, to
  the point where moving windows around the screen appears to be a stop-
  motion at 5FPS or so. Mouse movement is choppy, animations are
  grindingly slow, and this overall slowness does seem to affect text
  input into GUI dialogs (missed keys, etc). However, performance is
  fine in TTY, even with more active programs like HTOP and full-screen
  text images like NCURSES looking stuff. This issue wasn't present in
  18.04(.1) but could be triggered by using a newer kernel or updating
  the MESA stack. I'm using a STRIX Vega 64 for my GPU and I've
  installed Ubuntu 19.04 and only run updates and installed inxi and lm-
  sensors so I can provide more data if possible. (EDIT: Would also like
  to note that CPU usage is pretty low, and there's nothing pinning the
  CPU or spiking it from time to time. I believe this is solely
  graphical, but I am *not* 100% certain at any rate.)

  System:
    Host: schyken-ryzen-horizon Kernel: 4.19.0-12-generic x86_64 bits: 64
    compiler: gcc v: 8.2.0 Desktop: Gnome 3.30.2
    Distro: Ubuntu 19.04 (Disco Dingo)
  Machine:
    Type: Desktop Mobo: ASUSTeK model: PRIME B350-PLUS v: Rev X.0x
    serial:  UEFI: American Megatrends v: 4207 date: 12/07/2018
  CPU:
    Topology: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+
    rev: 2 L2 cache: 4096 KiB
    flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
    bogomips: 111784
    Speed: 1374 MHz min/max: 1550/3500 MHz Core speeds (MHz): 1: 1375 2: 1374
    3: 2779 4: 1700 5: 2793 6: 2625 7: 1270 8: 1270 9: 1375 10: 1375 11: 1375
    12: 1375 13: 1375 14: 1370 15: 1267 16: 1270
  Graphics:
    Device-1: AMD Vega 10 XT [Radeon RX Vega 64] vendor: ASUSTeK
    driver: amdgpu v: kernel bus ID: 0c:00.0
    Display: x11 server: X.Org 1.20.3 driver: amdgpu
    resolution: 2560x1440~60Hz
    OpenGL:
    renderer: Radeon RX Vega (VEGA10 DRM 3.27.0 4.19.0-12-generic LLVM 7.0.1)
    v: 4.5 Mesa 18.3.2 direct render: Yes
  Audio:
    Device-1: Creative Labs Sound Core3D [Sound Blaster Recon3D / Z-Series]
    driver: snd_hda_intel v: kernel bus ID: 09:00.0
    Device-2: AMD driver: snd_hda_intel v: kernel bus ID: 0c:00.1
    Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel bus ID: 0e:00.3
    Device-4: Logitech HD Pro Webcam C920 type: USB
    driver: snd-usb-audio,uvcvideo bus ID: 3-3:3
    Device-5: C-Media type: USB driver: hid-generic,snd-usb-audio,usbhid
    bus ID: 1-1:2
    Sound Server: ALSA v: k4.19.0-12-generic
  Network:
    Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK driver: r8169 v: kernel port: f000 bus ID: 04:00.0
    IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: 
  Drives:
    Local Storage: total: 2.05 TiB used: 6.93 GiB (0.3%)
    ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 EVO 250GB
    size: 232.89 GiB
    ID-2: /dev/sda vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 22 C
    ID-3: /dev/sdb vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 19 C
    ID-4: /dev/sdc vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 21 C
    ID-5: /dev/sdd vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 21 C
  Partition:
    ID-1: / size: 91.29 GiB used: 6.92 GiB (7.6%) fs: ext4 dev: /dev/nvme0n1p3
  Sensors:
    System Temperatures: cpu: 27.2 C mobo: N/A gpu: amdgpu temp: 29 C
    Fan Speeds (RPM): cpu: 0 gpu: amdgpu fan: 720
  Info:
    Processes: 373 Uptime: 2m Memory: 31.41 GiB used: 1.40 GiB (4.5%)
    Init: systemd runlevel: 5 Compilers: gcc: 8.2.0 Shell: bash v: 5.0.2
    inxi: 3.0.32
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-02-11 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-generic 
root=UUID=66ecdf59-50f0-49c7-befa-d800622a2e25 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 

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

2019-02-11 Thread Alan Diggs
apport information

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

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

Title:
  System lag/stuttering, mouse movement and window drag choppiness with
  Vega 64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In Ubuntu 18.10 and beyond, the desktop is quite laggy and choppy, to
  the point where moving windows around the screen appears to be a stop-
  motion at 5FPS or so. Mouse movement is choppy, animations are
  grindingly slow, and this overall slowness does seem to affect text
  input into GUI dialogs (missed keys, etc). However, performance is
  fine in TTY, even with more active programs like HTOP and full-screen
  text images like NCURSES looking stuff. This issue wasn't present in
  18.04(.1) but could be triggered by using a newer kernel or updating
  the MESA stack. I'm using a STRIX Vega 64 for my GPU and I've
  installed Ubuntu 19.04 and only run updates and installed inxi and lm-
  sensors so I can provide more data if possible. (EDIT: Would also like
  to note that CPU usage is pretty low, and there's nothing pinning the
  CPU or spiking it from time to time. I believe this is solely
  graphical, but I am *not* 100% certain at any rate.)

  System:
    Host: schyken-ryzen-horizon Kernel: 4.19.0-12-generic x86_64 bits: 64
    compiler: gcc v: 8.2.0 Desktop: Gnome 3.30.2
    Distro: Ubuntu 19.04 (Disco Dingo)
  Machine:
    Type: Desktop Mobo: ASUSTeK model: PRIME B350-PLUS v: Rev X.0x
    serial:  UEFI: American Megatrends v: 4207 date: 12/07/2018
  CPU:
    Topology: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+
    rev: 2 L2 cache: 4096 KiB
    flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
    bogomips: 111784
    Speed: 1374 MHz min/max: 1550/3500 MHz Core speeds (MHz): 1: 1375 2: 1374
    3: 2779 4: 1700 5: 2793 6: 2625 7: 1270 8: 1270 9: 1375 10: 1375 11: 1375
    12: 1375 13: 1375 14: 1370 15: 1267 16: 1270
  Graphics:
    Device-1: AMD Vega 10 XT [Radeon RX Vega 64] vendor: ASUSTeK
    driver: amdgpu v: kernel bus ID: 0c:00.0
    Display: x11 server: X.Org 1.20.3 driver: amdgpu
    resolution: 2560x1440~60Hz
    OpenGL:
    renderer: Radeon RX Vega (VEGA10 DRM 3.27.0 4.19.0-12-generic LLVM 7.0.1)
    v: 4.5 Mesa 18.3.2 direct render: Yes
  Audio:
    Device-1: Creative Labs Sound Core3D [Sound Blaster Recon3D / Z-Series]
    driver: snd_hda_intel v: kernel bus ID: 09:00.0
    Device-2: AMD driver: snd_hda_intel v: kernel bus ID: 0c:00.1
    Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel bus ID: 0e:00.3
    Device-4: Logitech HD Pro Webcam C920 type: USB
    driver: snd-usb-audio,uvcvideo bus ID: 3-3:3
    Device-5: C-Media type: USB driver: hid-generic,snd-usb-audio,usbhid
    bus ID: 1-1:2
    Sound Server: ALSA v: k4.19.0-12-generic
  Network:
    Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK driver: r8169 v: kernel port: f000 bus ID: 04:00.0
    IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: 
  Drives:
    Local Storage: total: 2.05 TiB used: 6.93 GiB (0.3%)
    ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 EVO 250GB
    size: 232.89 GiB
    ID-2: /dev/sda vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 22 C
    ID-3: /dev/sdb vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 19 C
    ID-4: /dev/sdc vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 21 C
    ID-5: /dev/sdd vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 21 C
  Partition:
    ID-1: / size: 91.29 GiB used: 6.92 GiB (7.6%) fs: ext4 dev: /dev/nvme0n1p3
  Sensors:
    System Temperatures: cpu: 27.2 C mobo: N/A gpu: amdgpu temp: 29 C
    Fan Speeds (RPM): cpu: 0 gpu: amdgpu fan: 720
  Info:
    Processes: 373 Uptime: 2m Memory: 31.41 GiB used: 1.40 GiB (4.5%)
    Init: systemd runlevel: 5 Compilers: gcc: 8.2.0 Shell: bash v: 5.0.2
    inxi: 3.0.32
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-02-11 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-generic 
root=UUID=66ecdf59-50f0-49c7-befa-d800622a2e25 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
  

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

2019-02-11 Thread Alan Diggs
apport information

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

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

Title:
  System lag/stuttering, mouse movement and window drag choppiness with
  Vega 64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In Ubuntu 18.10 and beyond, the desktop is quite laggy and choppy, to
  the point where moving windows around the screen appears to be a stop-
  motion at 5FPS or so. Mouse movement is choppy, animations are
  grindingly slow, and this overall slowness does seem to affect text
  input into GUI dialogs (missed keys, etc). However, performance is
  fine in TTY, even with more active programs like HTOP and full-screen
  text images like NCURSES looking stuff. This issue wasn't present in
  18.04(.1) but could be triggered by using a newer kernel or updating
  the MESA stack. I'm using a STRIX Vega 64 for my GPU and I've
  installed Ubuntu 19.04 and only run updates and installed inxi and lm-
  sensors so I can provide more data if possible. (EDIT: Would also like
  to note that CPU usage is pretty low, and there's nothing pinning the
  CPU or spiking it from time to time. I believe this is solely
  graphical, but I am *not* 100% certain at any rate.)

  System:
    Host: schyken-ryzen-horizon Kernel: 4.19.0-12-generic x86_64 bits: 64
    compiler: gcc v: 8.2.0 Desktop: Gnome 3.30.2
    Distro: Ubuntu 19.04 (Disco Dingo)
  Machine:
    Type: Desktop Mobo: ASUSTeK model: PRIME B350-PLUS v: Rev X.0x
    serial:  UEFI: American Megatrends v: 4207 date: 12/07/2018
  CPU:
    Topology: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+
    rev: 2 L2 cache: 4096 KiB
    flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
    bogomips: 111784
    Speed: 1374 MHz min/max: 1550/3500 MHz Core speeds (MHz): 1: 1375 2: 1374
    3: 2779 4: 1700 5: 2793 6: 2625 7: 1270 8: 1270 9: 1375 10: 1375 11: 1375
    12: 1375 13: 1375 14: 1370 15: 1267 16: 1270
  Graphics:
    Device-1: AMD Vega 10 XT [Radeon RX Vega 64] vendor: ASUSTeK
    driver: amdgpu v: kernel bus ID: 0c:00.0
    Display: x11 server: X.Org 1.20.3 driver: amdgpu
    resolution: 2560x1440~60Hz
    OpenGL:
    renderer: Radeon RX Vega (VEGA10 DRM 3.27.0 4.19.0-12-generic LLVM 7.0.1)
    v: 4.5 Mesa 18.3.2 direct render: Yes
  Audio:
    Device-1: Creative Labs Sound Core3D [Sound Blaster Recon3D / Z-Series]
    driver: snd_hda_intel v: kernel bus ID: 09:00.0
    Device-2: AMD driver: snd_hda_intel v: kernel bus ID: 0c:00.1
    Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel bus ID: 0e:00.3
    Device-4: Logitech HD Pro Webcam C920 type: USB
    driver: snd-usb-audio,uvcvideo bus ID: 3-3:3
    Device-5: C-Media type: USB driver: hid-generic,snd-usb-audio,usbhid
    bus ID: 1-1:2
    Sound Server: ALSA v: k4.19.0-12-generic
  Network:
    Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK driver: r8169 v: kernel port: f000 bus ID: 04:00.0
    IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: 
  Drives:
    Local Storage: total: 2.05 TiB used: 6.93 GiB (0.3%)
    ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 EVO 250GB
    size: 232.89 GiB
    ID-2: /dev/sda vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 22 C
    ID-3: /dev/sdb vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 19 C
    ID-4: /dev/sdc vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 21 C
    ID-5: /dev/sdd vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 21 C
  Partition:
    ID-1: / size: 91.29 GiB used: 6.92 GiB (7.6%) fs: ext4 dev: /dev/nvme0n1p3
  Sensors:
    System Temperatures: cpu: 27.2 C mobo: N/A gpu: amdgpu temp: 29 C
    Fan Speeds (RPM): cpu: 0 gpu: amdgpu fan: 720
  Info:
    Processes: 373 Uptime: 2m Memory: 31.41 GiB used: 1.40 GiB (4.5%)
    Init: systemd runlevel: 5 Compilers: gcc: 8.2.0 Shell: bash v: 5.0.2
    inxi: 3.0.32
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-02-11 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-generic 
root=UUID=66ecdf59-50f0-49c7-befa-d800622a2e25 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 

[Kernel-packages] [Bug 1815510] Re: System lag/stuttering, mouse movement and window drag choppiness with Vega 64

2019-02-11 Thread Alan Diggs
apport information

** Tags added: apport-collected

** Description changed:

  In Ubuntu 18.10 and beyond, the desktop is quite laggy and choppy, to
  the point where moving windows around the screen appears to be a stop-
  motion at 5FPS or so. Mouse movement is choppy, animations are
  grindingly slow, and this overall slowness does seem to affect text
  input into GUI dialogs (missed keys, etc). However, performance is fine
  in TTY, even with more active programs like HTOP and full-screen text
  images like NCURSES looking stuff. This issue wasn't present in
  18.04(.1) but could be triggered by using a newer kernel or updating the
  MESA stack. I'm using a STRIX Vega 64 for my GPU and I've installed
  Ubuntu 19.04 and only run updates and installed inxi and lm-sensors so I
  can provide more data if possible. (EDIT: Would also like to note that
  CPU usage is pretty low, and there's nothing pinning the CPU or spiking
  it from time to time. I believe this is solely graphical, but I am *not*
  100% certain at any rate.)
  
  System:
    Host: schyken-ryzen-horizon Kernel: 4.19.0-12-generic x86_64 bits: 64
    compiler: gcc v: 8.2.0 Desktop: Gnome 3.30.2
    Distro: Ubuntu 19.04 (Disco Dingo)
  Machine:
    Type: Desktop Mobo: ASUSTeK model: PRIME B350-PLUS v: Rev X.0x
    serial:  UEFI: American Megatrends v: 4207 date: 12/07/2018
  CPU:
    Topology: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+
    rev: 2 L2 cache: 4096 KiB
    flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
    bogomips: 111784
    Speed: 1374 MHz min/max: 1550/3500 MHz Core speeds (MHz): 1: 1375 2: 1374
    3: 2779 4: 1700 5: 2793 6: 2625 7: 1270 8: 1270 9: 1375 10: 1375 11: 1375
    12: 1375 13: 1375 14: 1370 15: 1267 16: 1270
  Graphics:
    Device-1: AMD Vega 10 XT [Radeon RX Vega 64] vendor: ASUSTeK
    driver: amdgpu v: kernel bus ID: 0c:00.0
    Display: x11 server: X.Org 1.20.3 driver: amdgpu
    resolution: 2560x1440~60Hz
    OpenGL:
    renderer: Radeon RX Vega (VEGA10 DRM 3.27.0 4.19.0-12-generic LLVM 7.0.1)
    v: 4.5 Mesa 18.3.2 direct render: Yes
  Audio:
    Device-1: Creative Labs Sound Core3D [Sound Blaster Recon3D / Z-Series]
    driver: snd_hda_intel v: kernel bus ID: 09:00.0
    Device-2: AMD driver: snd_hda_intel v: kernel bus ID: 0c:00.1
    Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel bus ID: 0e:00.3
    Device-4: Logitech HD Pro Webcam C920 type: USB
    driver: snd-usb-audio,uvcvideo bus ID: 3-3:3
    Device-5: C-Media type: USB driver: hid-generic,snd-usb-audio,usbhid
    bus ID: 1-1:2
    Sound Server: ALSA v: k4.19.0-12-generic
  Network:
    Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK driver: r8169 v: kernel port: f000 bus ID: 04:00.0
    IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: 
  Drives:
    Local Storage: total: 2.05 TiB used: 6.93 GiB (0.3%)
    ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 EVO 250GB
    size: 232.89 GiB
    ID-2: /dev/sda vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 22 C
    ID-3: /dev/sdb vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 19 C
    ID-4: /dev/sdc vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 21 C
    ID-5: /dev/sdd vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 21 C
  Partition:
    ID-1: / size: 91.29 GiB used: 6.92 GiB (7.6%) fs: ext4 dev: /dev/nvme0n1p3
  Sensors:
    System Temperatures: cpu: 27.2 C mobo: N/A gpu: amdgpu temp: 29 C
    Fan Speeds (RPM): cpu: 0 gpu: amdgpu fan: 720
  Info:
    Processes: 373 Uptime: 2m Memory: 31.41 GiB used: 1.40 GiB (4.5%)
    Init: systemd runlevel: 5 Compilers: gcc: 8.2.0 Shell: bash v: 5.0.2
    inxi: 3.0.32
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu20
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 19.04
+ InstallationDate: Installed on 2019-02-11 (0 days ago)
+ InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
+ IwConfig:
+  enp4s0no wireless extensions.
+  
+  lono wireless extensions.
+ MachineType: System manufacturer System Product Name
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 amdgpudrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-generic 
root=UUID=66ecdf59-50f0-49c7-befa-d800622a2e25 ro quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
+ RelatedPackageVersions:
+  linux-restricted-modules-4.19.0-12-generic N/A
+  linux-backports-modules-4.19.0-12-generic  N/A
+  linux-firmware 1.177
+ RfKill:
+  0: hci0: Bluetooth
+   Soft blocked: no
+   Hard blocked: no
+ Tags:  disco
+ Uname: Linux 4.19.0-12-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ 

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

2019-02-11 Thread Alan Diggs
apport information

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

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

Title:
  System lag/stuttering, mouse movement and window drag choppiness with
  Vega 64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In Ubuntu 18.10 and beyond, the desktop is quite laggy and choppy, to
  the point where moving windows around the screen appears to be a stop-
  motion at 5FPS or so. Mouse movement is choppy, animations are
  grindingly slow, and this overall slowness does seem to affect text
  input into GUI dialogs (missed keys, etc). However, performance is
  fine in TTY, even with more active programs like HTOP and full-screen
  text images like NCURSES looking stuff. This issue wasn't present in
  18.04(.1) but could be triggered by using a newer kernel or updating
  the MESA stack. I'm using a STRIX Vega 64 for my GPU and I've
  installed Ubuntu 19.04 and only run updates and installed inxi and lm-
  sensors so I can provide more data if possible. (EDIT: Would also like
  to note that CPU usage is pretty low, and there's nothing pinning the
  CPU or spiking it from time to time. I believe this is solely
  graphical, but I am *not* 100% certain at any rate.)

  System:
    Host: schyken-ryzen-horizon Kernel: 4.19.0-12-generic x86_64 bits: 64
    compiler: gcc v: 8.2.0 Desktop: Gnome 3.30.2
    Distro: Ubuntu 19.04 (Disco Dingo)
  Machine:
    Type: Desktop Mobo: ASUSTeK model: PRIME B350-PLUS v: Rev X.0x
    serial:  UEFI: American Megatrends v: 4207 date: 12/07/2018
  CPU:
    Topology: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+
    rev: 2 L2 cache: 4096 KiB
    flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
    bogomips: 111784
    Speed: 1374 MHz min/max: 1550/3500 MHz Core speeds (MHz): 1: 1375 2: 1374
    3: 2779 4: 1700 5: 2793 6: 2625 7: 1270 8: 1270 9: 1375 10: 1375 11: 1375
    12: 1375 13: 1375 14: 1370 15: 1267 16: 1270
  Graphics:
    Device-1: AMD Vega 10 XT [Radeon RX Vega 64] vendor: ASUSTeK
    driver: amdgpu v: kernel bus ID: 0c:00.0
    Display: x11 server: X.Org 1.20.3 driver: amdgpu
    resolution: 2560x1440~60Hz
    OpenGL:
    renderer: Radeon RX Vega (VEGA10 DRM 3.27.0 4.19.0-12-generic LLVM 7.0.1)
    v: 4.5 Mesa 18.3.2 direct render: Yes
  Audio:
    Device-1: Creative Labs Sound Core3D [Sound Blaster Recon3D / Z-Series]
    driver: snd_hda_intel v: kernel bus ID: 09:00.0
    Device-2: AMD driver: snd_hda_intel v: kernel bus ID: 0c:00.1
    Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel bus ID: 0e:00.3
    Device-4: Logitech HD Pro Webcam C920 type: USB
    driver: snd-usb-audio,uvcvideo bus ID: 3-3:3
    Device-5: C-Media type: USB driver: hid-generic,snd-usb-audio,usbhid
    bus ID: 1-1:2
    Sound Server: ALSA v: k4.19.0-12-generic
  Network:
    Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK driver: r8169 v: kernel port: f000 bus ID: 04:00.0
    IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: 
  Drives:
    Local Storage: total: 2.05 TiB used: 6.93 GiB (0.3%)
    ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 EVO 250GB
    size: 232.89 GiB
    ID-2: /dev/sda vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 22 C
    ID-3: /dev/sdb vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 19 C
    ID-4: /dev/sdc vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 21 C
    ID-5: /dev/sdd vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 21 C
  Partition:
    ID-1: / size: 91.29 GiB used: 6.92 GiB (7.6%) fs: ext4 dev: /dev/nvme0n1p3
  Sensors:
    System Temperatures: cpu: 27.2 C mobo: N/A gpu: amdgpu temp: 29 C
    Fan Speeds (RPM): cpu: 0 gpu: amdgpu fan: 720
  Info:
    Processes: 373 Uptime: 2m Memory: 31.41 GiB used: 1.40 GiB (4.5%)
    Init: systemd runlevel: 5 Compilers: gcc: 8.2.0 Shell: bash v: 5.0.2
    inxi: 3.0.32
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-02-11 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-generic 
root=UUID=66ecdf59-50f0-49c7-befa-d800622a2e25 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
 

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

2019-02-11 Thread Alan Diggs
apport information

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

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

Title:
  System lag/stuttering, mouse movement and window drag choppiness with
  Vega 64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In Ubuntu 18.10 and beyond, the desktop is quite laggy and choppy, to
  the point where moving windows around the screen appears to be a stop-
  motion at 5FPS or so. Mouse movement is choppy, animations are
  grindingly slow, and this overall slowness does seem to affect text
  input into GUI dialogs (missed keys, etc). However, performance is
  fine in TTY, even with more active programs like HTOP and full-screen
  text images like NCURSES looking stuff. This issue wasn't present in
  18.04(.1) but could be triggered by using a newer kernel or updating
  the MESA stack. I'm using a STRIX Vega 64 for my GPU and I've
  installed Ubuntu 19.04 and only run updates and installed inxi and lm-
  sensors so I can provide more data if possible. (EDIT: Would also like
  to note that CPU usage is pretty low, and there's nothing pinning the
  CPU or spiking it from time to time. I believe this is solely
  graphical, but I am *not* 100% certain at any rate.)

  System:
    Host: schyken-ryzen-horizon Kernel: 4.19.0-12-generic x86_64 bits: 64
    compiler: gcc v: 8.2.0 Desktop: Gnome 3.30.2
    Distro: Ubuntu 19.04 (Disco Dingo)
  Machine:
    Type: Desktop Mobo: ASUSTeK model: PRIME B350-PLUS v: Rev X.0x
    serial:  UEFI: American Megatrends v: 4207 date: 12/07/2018
  CPU:
    Topology: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+
    rev: 2 L2 cache: 4096 KiB
    flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
    bogomips: 111784
    Speed: 1374 MHz min/max: 1550/3500 MHz Core speeds (MHz): 1: 1375 2: 1374
    3: 2779 4: 1700 5: 2793 6: 2625 7: 1270 8: 1270 9: 1375 10: 1375 11: 1375
    12: 1375 13: 1375 14: 1370 15: 1267 16: 1270
  Graphics:
    Device-1: AMD Vega 10 XT [Radeon RX Vega 64] vendor: ASUSTeK
    driver: amdgpu v: kernel bus ID: 0c:00.0
    Display: x11 server: X.Org 1.20.3 driver: amdgpu
    resolution: 2560x1440~60Hz
    OpenGL:
    renderer: Radeon RX Vega (VEGA10 DRM 3.27.0 4.19.0-12-generic LLVM 7.0.1)
    v: 4.5 Mesa 18.3.2 direct render: Yes
  Audio:
    Device-1: Creative Labs Sound Core3D [Sound Blaster Recon3D / Z-Series]
    driver: snd_hda_intel v: kernel bus ID: 09:00.0
    Device-2: AMD driver: snd_hda_intel v: kernel bus ID: 0c:00.1
    Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel bus ID: 0e:00.3
    Device-4: Logitech HD Pro Webcam C920 type: USB
    driver: snd-usb-audio,uvcvideo bus ID: 3-3:3
    Device-5: C-Media type: USB driver: hid-generic,snd-usb-audio,usbhid
    bus ID: 1-1:2
    Sound Server: ALSA v: k4.19.0-12-generic
  Network:
    Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK driver: r8169 v: kernel port: f000 bus ID: 04:00.0
    IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: 
  Drives:
    Local Storage: total: 2.05 TiB used: 6.93 GiB (0.3%)
    ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 EVO 250GB
    size: 232.89 GiB
    ID-2: /dev/sda vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 22 C
    ID-3: /dev/sdb vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 19 C
    ID-4: /dev/sdc vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 21 C
    ID-5: /dev/sdd vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 21 C
  Partition:
    ID-1: / size: 91.29 GiB used: 6.92 GiB (7.6%) fs: ext4 dev: /dev/nvme0n1p3
  Sensors:
    System Temperatures: cpu: 27.2 C mobo: N/A gpu: amdgpu temp: 29 C
    Fan Speeds (RPM): cpu: 0 gpu: amdgpu fan: 720
  Info:
    Processes: 373 Uptime: 2m Memory: 31.41 GiB used: 1.40 GiB (4.5%)
    Init: systemd runlevel: 5 Compilers: gcc: 8.2.0 Shell: bash v: 5.0.2
    inxi: 3.0.32
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-02-11 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-generic 
root=UUID=66ecdf59-50f0-49c7-befa-d800622a2e25 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
  

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

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

apport-collect 1815510

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

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

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

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

** Tags added: disco

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

Title:
  System lag/stuttering, mouse movement and window drag choppiness with
  Vega 64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In Ubuntu 18.10 and beyond, the desktop is quite laggy and choppy, to
  the point where moving windows around the screen appears to be a stop-
  motion at 5FPS or so. Mouse movement is choppy, animations are
  grindingly slow, and this overall slowness does seem to affect text
  input into GUI dialogs (missed keys, etc). However, performance is
  fine in TTY, even with more active programs like HTOP and full-screen
  text images like NCURSES looking stuff. This issue wasn't present in
  18.04(.1) but could be triggered by using a newer kernel or updating
  the MESA stack. I'm using a STRIX Vega 64 for my GPU and I've
  installed Ubuntu 19.04 and only run updates and installed inxi and lm-
  sensors so I can provide more data if possible. (EDIT: Would also like
  to note that CPU usage is pretty low, and there's nothing pinning the
  CPU or spiking it from time to time. I believe this is solely
  graphical, but I am *not* 100% certain at any rate.)

  System:
    Host: schyken-ryzen-horizon Kernel: 4.19.0-12-generic x86_64 bits: 64
    compiler: gcc v: 8.2.0 Desktop: Gnome 3.30.2
    Distro: Ubuntu 19.04 (Disco Dingo)
  Machine:
    Type: Desktop Mobo: ASUSTeK model: PRIME B350-PLUS v: Rev X.0x
    serial:  UEFI: American Megatrends v: 4207 date: 12/07/2018
  CPU:
    Topology: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+
    rev: 2 L2 cache: 4096 KiB
    flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
    bogomips: 111784
    Speed: 1374 MHz min/max: 1550/3500 MHz Core speeds (MHz): 1: 1375 2: 1374
    3: 2779 4: 1700 5: 2793 6: 2625 7: 1270 8: 1270 9: 1375 10: 1375 11: 1375
    12: 1375 13: 1375 14: 1370 15: 1267 16: 1270
  Graphics:
    Device-1: AMD Vega 10 XT [Radeon RX Vega 64] vendor: ASUSTeK
    driver: amdgpu v: kernel bus ID: 0c:00.0
    Display: x11 server: X.Org 1.20.3 driver: amdgpu
    resolution: 2560x1440~60Hz
    OpenGL:
    renderer: Radeon RX Vega (VEGA10 DRM 3.27.0 4.19.0-12-generic LLVM 7.0.1)
    v: 4.5 Mesa 18.3.2 direct render: Yes
  Audio:
    Device-1: Creative Labs Sound Core3D [Sound Blaster Recon3D / Z-Series]
    driver: snd_hda_intel v: kernel bus ID: 09:00.0
    Device-2: AMD driver: snd_hda_intel v: kernel bus ID: 0c:00.1
    Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel bus ID: 0e:00.3
    Device-4: Logitech HD Pro Webcam C920 type: USB
    driver: snd-usb-audio,uvcvideo bus ID: 3-3:3
    Device-5: C-Media type: USB driver: hid-generic,snd-usb-audio,usbhid
    bus ID: 1-1:2
    Sound Server: ALSA v: k4.19.0-12-generic
  Network:
    Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK driver: r8169 v: kernel port: f000 bus ID: 04:00.0
    IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: 
  Drives:
    Local Storage: total: 2.05 TiB used: 6.93 GiB (0.3%)
    ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 EVO 250GB
    size: 232.89 GiB
    ID-2: /dev/sda vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 22 C
    ID-3: /dev/sdb vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 19 C
    ID-4: /dev/sdc vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 21 C
    ID-5: /dev/sdd vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 21 C
  Partition:
    ID-1: / size: 91.29 GiB used: 6.92 GiB (7.6%) fs: ext4 dev: /dev/nvme0n1p3
  Sensors:
    System Temperatures: cpu: 27.2 C mobo: N/A gpu: amdgpu temp: 29 C
    Fan Speeds (RPM): cpu: 0 gpu: amdgpu fan: 720
  Info:
    Processes: 373 Uptime: 2m Memory: 31.41 GiB used: 1.40 GiB (4.5%)
    Init: systemd runlevel: 5 Compilers: gcc: 8.2.0 Shell: bash v: 5.0.2
    inxi: 3.0.32

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

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

[Kernel-packages] [Bug 1782206] Re: KVM enable SnowRidge Accelerator Interfacing Architecture (AIA)

2019-02-11 Thread quanxian
The detail git commits of Qemu are as below:

1c65775ffc2dbd276a8bffe592feba0e186a151c

==> x86/cpu: Enable MOVDIR64B cpu feature

24261de4916596d8ab5f5fee67e9e7a19e8325a5

==> x86/cpu: Enable MOVDIRI cpu feature

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

Title:
  KVM enable SnowRidge Accelerator Interfacing Architecture (AIA)

Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  Triaged
Status in xen package in Ubuntu:
  Incomplete

Bug description:
  CPU core (Tremont) includes Accelerator Interfacing Architecture (AIA) 
features including:
  - UMONITOR/UMWAIT: Ring-3 MONITOR/MWAIT with timeout. For memory-based synch 
with accelerators
  - TPAUSE: Monitor-less wait (with timeout). For wait-on-multiple or 
wait-for-interrupt usages
  - MOVDIRI: 8B streaming doorbell write capability. For streaming accelerator 
usages.
  - MOVDIR64B: Non-temporal write with 64B guaranteed write-atomicity. For 
latency critical accelerator usages

  Upstream target linux 4.20/Qemu-3.10

  Target Release: 19.04

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

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


[Kernel-packages] [Bug 1804804] Re: Screen rotation does not rotate all input devices and needs custom user commands (iio-sensor-proxy or libinput should probably handle this?)

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

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

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

Title:
  Screen rotation does not rotate all input devices and needs custom
  user commands (iio-sensor-proxy or libinput should probably handle
  this?)

Status in linux package in Ubuntu:
  Expired

Bug description:
  Ubuntu 18.10
  GNOME Shell 3.30.1
  Cinnamon 3.8.8

  Hardware: ASUS Transformer Mini.

  Also confirmed problematic for Yoga Series tablet/laptop hybrids.
  (https://github.com/linuxmint/cinnamon-settings-daemon/issues/188)

  Screen rotation works fine, but tablet coords including touch screen
  and pen coords do not rotate with it.

  Gnome gets touch screen rotation correct, but not pen coords
  Cinnamon gets touch screen rotation and peen coords wrong

  User can correct using convoluted xinput commands like:
  xinput set-prop "ELAN22A6:00 04F3:22A6" --type=float "Coordinate 
Transformation Matrix" 0 1 0 -1 0 1 0 0 1

  I spoke with Mint devs who said I should file it against iio-sensor-
  proxy or libinput, which I assume is a better solution that asking
  various wm developers to fix it individually.

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

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


[Kernel-packages] [Bug 1779756] Re: Intel XL710 - i40e driver does not work with kernel 4.15 (Ubuntu 18.04)

2019-02-11 Thread Nivedita Singhvi
Any update on a Bionic fix?

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

Title:
  Intel XL710 - i40e driver does not work with kernel 4.15 (Ubuntu
  18.04)

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

Bug description:
  Today Ubuntu 16.04 LTS Enablement Stacks has moved from the Kernel
  4.13 to the Kernel 4.15.0-24-generic.

  On a "Dell PowerEdge R330" server with a network adapter "Intel
  Ethernet Converged Network Adapter X710-DA2" (driver i40e) the network
  card no longer works and permanently displays these three lines :

  
  [   98.012098] i40e :01:00.0 enp1s0f0: tx_timeout: VSI_seid: 388, Q 8, 
NTC: 0x0, HWB: 0x0, NTU: 0x1, TAIL: 0x1, INT: 0x1
  [   98.012119] i40e :01:00.0 enp1s0f0: tx_timeout recovery level 11, 
hung_queue 8
  [   98.012125] i40e :01:00.0 enp1s0f0: tx_timeout recovery unsuccessful

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

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


[Kernel-packages] [Bug 1815510] Re: System lag/stuttering, mouse movement and window drag choppiness with Vega 64

2019-02-11 Thread Alan Diggs
Was told to include a package name. Though it's quite difficult to
actually narrow down a specific *package* that causes this issue, the
linked wiki document  suggests 'linux' if I'm filing this against the
kernel, which I guess I am as versions with older kernels are alright.

** Package changed: ubuntu => linux (Ubuntu)

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

Title:
  System lag/stuttering, mouse movement and window drag choppiness with
  Vega 64

Status in linux package in Ubuntu:
  New

Bug description:
  In Ubuntu 18.10 and beyond, the desktop is quite laggy and choppy, to
  the point where moving windows around the screen appears to be a stop-
  motion at 5FPS or so. Mouse movement is choppy, animations are
  grindingly slow, and this overall slowness does seem to affect text
  input into GUI dialogs (missed keys, etc). However, performance is
  fine in TTY, even with more active programs like HTOP and full-screen
  text images like NCURSES looking stuff. This issue wasn't present in
  18.04(.1) but could be triggered by using a newer kernel or updating
  the MESA stack. I'm using a STRIX Vega 64 for my GPU and I've
  installed Ubuntu 19.04 and only run updates and installed inxi and lm-
  sensors so I can provide more data if possible. (EDIT: Would also like
  to note that CPU usage is pretty low, and there's nothing pinning the
  CPU or spiking it from time to time. I believe this is solely
  graphical, but I am *not* 100% certain at any rate.)

  System:
    Host: schyken-ryzen-horizon Kernel: 4.19.0-12-generic x86_64 bits: 64
    compiler: gcc v: 8.2.0 Desktop: Gnome 3.30.2
    Distro: Ubuntu 19.04 (Disco Dingo)
  Machine:
    Type: Desktop Mobo: ASUSTeK model: PRIME B350-PLUS v: Rev X.0x
    serial:  UEFI: American Megatrends v: 4207 date: 12/07/2018
  CPU:
    Topology: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+
    rev: 2 L2 cache: 4096 KiB
    flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
    bogomips: 111784
    Speed: 1374 MHz min/max: 1550/3500 MHz Core speeds (MHz): 1: 1375 2: 1374
    3: 2779 4: 1700 5: 2793 6: 2625 7: 1270 8: 1270 9: 1375 10: 1375 11: 1375
    12: 1375 13: 1375 14: 1370 15: 1267 16: 1270
  Graphics:
    Device-1: AMD Vega 10 XT [Radeon RX Vega 64] vendor: ASUSTeK
    driver: amdgpu v: kernel bus ID: 0c:00.0
    Display: x11 server: X.Org 1.20.3 driver: amdgpu
    resolution: 2560x1440~60Hz
    OpenGL:
    renderer: Radeon RX Vega (VEGA10 DRM 3.27.0 4.19.0-12-generic LLVM 7.0.1)
    v: 4.5 Mesa 18.3.2 direct render: Yes
  Audio:
    Device-1: Creative Labs Sound Core3D [Sound Blaster Recon3D / Z-Series]
    driver: snd_hda_intel v: kernel bus ID: 09:00.0
    Device-2: AMD driver: snd_hda_intel v: kernel bus ID: 0c:00.1
    Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel bus ID: 0e:00.3
    Device-4: Logitech HD Pro Webcam C920 type: USB
    driver: snd-usb-audio,uvcvideo bus ID: 3-3:3
    Device-5: C-Media type: USB driver: hid-generic,snd-usb-audio,usbhid
    bus ID: 1-1:2
    Sound Server: ALSA v: k4.19.0-12-generic
  Network:
    Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK driver: r8169 v: kernel port: f000 bus ID: 04:00.0
    IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: 
  Drives:
    Local Storage: total: 2.05 TiB used: 6.93 GiB (0.3%)
    ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 EVO 250GB
    size: 232.89 GiB
    ID-2: /dev/sda vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 22 C
    ID-3: /dev/sdb vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 19 C
    ID-4: /dev/sdc vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 21 C
    ID-5: /dev/sdd vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 21 C
  Partition:
    ID-1: / size: 91.29 GiB used: 6.92 GiB (7.6%) fs: ext4 dev: /dev/nvme0n1p3
  Sensors:
    System Temperatures: cpu: 27.2 C mobo: N/A gpu: amdgpu temp: 29 C
    Fan Speeds (RPM): cpu: 0 gpu: amdgpu fan: 720
  Info:
    Processes: 373 Uptime: 2m Memory: 31.41 GiB used: 1.40 GiB (4.5%)
    Init: systemd runlevel: 5 Compilers: gcc: 8.2.0 Shell: bash v: 5.0.2
    inxi: 3.0.32

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

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


[Kernel-packages] [Bug 1815510] [NEW] System lag/stuttering, mouse movement and window drag choppiness with Vega 64

2019-02-11 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

In Ubuntu 18.10 and beyond, the desktop is quite laggy and choppy, to
the point where moving windows around the screen appears to be a stop-
motion at 5FPS or so. Mouse movement is choppy, animations are
grindingly slow, and this overall slowness does seem to affect text
input into GUI dialogs (missed keys, etc). However, performance is fine
in TTY, even with more active programs like HTOP and full-screen text
images like NCURSES looking stuff. This issue wasn't present in
18.04(.1) but could be triggered by using a newer kernel or updating the
MESA stack. I'm using a STRIX Vega 64 for my GPU and I've installed
Ubuntu 19.04 and only run updates and installed inxi and lm-sensors so I
can provide more data if possible. (EDIT: Would also like to note that
CPU usage is pretty low, and there's nothing pinning the CPU or spiking
it from time to time. I believe this is solely graphical, but I am *not*
100% certain at any rate.)

System:
  Host: schyken-ryzen-horizon Kernel: 4.19.0-12-generic x86_64 bits: 64
  compiler: gcc v: 8.2.0 Desktop: Gnome 3.30.2
  Distro: Ubuntu 19.04 (Disco Dingo)
Machine:
  Type: Desktop Mobo: ASUSTeK model: PRIME B350-PLUS v: Rev X.0x
  serial:  UEFI: American Megatrends v: 4207 date: 12/07/2018
CPU:
  Topology: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+
  rev: 2 L2 cache: 4096 KiB
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  bogomips: 111784
  Speed: 1374 MHz min/max: 1550/3500 MHz Core speeds (MHz): 1: 1375 2: 1374
  3: 2779 4: 1700 5: 2793 6: 2625 7: 1270 8: 1270 9: 1375 10: 1375 11: 1375
  12: 1375 13: 1375 14: 1370 15: 1267 16: 1270
Graphics:
  Device-1: AMD Vega 10 XT [Radeon RX Vega 64] vendor: ASUSTeK
  driver: amdgpu v: kernel bus ID: 0c:00.0
  Display: x11 server: X.Org 1.20.3 driver: amdgpu
  resolution: 2560x1440~60Hz
  OpenGL:
  renderer: Radeon RX Vega (VEGA10 DRM 3.27.0 4.19.0-12-generic LLVM 7.0.1)
  v: 4.5 Mesa 18.3.2 direct render: Yes
Audio:
  Device-1: Creative Labs Sound Core3D [Sound Blaster Recon3D / Z-Series]
  driver: snd_hda_intel v: kernel bus ID: 09:00.0
  Device-2: AMD driver: snd_hda_intel v: kernel bus ID: 0c:00.1
  Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel
  v: kernel bus ID: 0e:00.3
  Device-4: Logitech HD Pro Webcam C920 type: USB
  driver: snd-usb-audio,uvcvideo bus ID: 3-3:3
  Device-5: C-Media type: USB driver: hid-generic,snd-usb-audio,usbhid
  bus ID: 1-1:2
  Sound Server: ALSA v: k4.19.0-12-generic
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
  vendor: ASUSTeK driver: r8169 v: kernel port: f000 bus ID: 04:00.0
  IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: 
Drives:
  Local Storage: total: 2.05 TiB used: 6.93 GiB (0.3%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 EVO 250GB
  size: 232.89 GiB
  ID-2: /dev/sda vendor: Western Digital model: WDS500G2B0A-00SM50
  size: 465.76 GiB temp: 22 C
  ID-3: /dev/sdb vendor: Western Digital model: WDS500G2B0A-00SM50
  size: 465.76 GiB temp: 19 C
  ID-4: /dev/sdc vendor: Western Digital model: WDS500G2B0A-00SM50
  size: 465.76 GiB temp: 21 C
  ID-5: /dev/sdd vendor: Western Digital model: WDS500G2B0A-00SM50
  size: 465.76 GiB temp: 21 C
Partition:
  ID-1: / size: 91.29 GiB used: 6.92 GiB (7.6%) fs: ext4 dev: /dev/nvme0n1p3
Sensors:
  System Temperatures: cpu: 27.2 C mobo: N/A gpu: amdgpu temp: 29 C
  Fan Speeds (RPM): cpu: 0 gpu: amdgpu fan: 720
Info:
  Processes: 373 Uptime: 2m Memory: 31.41 GiB used: 1.40 GiB (4.5%)
  Init: systemd runlevel: 5 Compilers: gcc: 8.2.0 Shell: bash v: 5.0.2
  inxi: 3.0.32

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


** Tags: bot-comment
-- 
System lag/stuttering, mouse movement and window drag choppiness with Vega 64
https://bugs.launchpad.net/bugs/1815510
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 1815258] Re: 4.18.0-14-generic unbootable on Toshiba

2019-02-11 Thread shanen (Shannon Jacobs)
Okay, after the latest update (from the 0-13 kernel) it now seems to be
booting normally. I hope that means the problem has been corrected and
this bug can be closed. Perhaps some kind of regression bug?

If anyone over there wants me to collect any additional information
about what was going on, please let me know what you need and how to
collect it. Minimum might be some confirmation if you have a hypothesis
of what got broken and want to make sure you squashed the bug.

P.S. I'd be more enthusiastic if I had a few bucks on the table (for
example, via that imaginary charity share brokerage). I don't really
feel that I have much skin in the game beyond the fuzzy philosophy that
freedom involves choice and Linux is one of the choices I should
understand and consider.

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

Title:
  4.18.0-14-generic unbootable on Toshiba

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After the update for the 4.18.0-14-generic kernel the machine freezes
  on booting. Machine still books under the 0-13 kernel. Booting in
  Recovery Mode seems go normally to the Recovery Menu. At that point it
  reports "Starting Avahi mDNS-SD Stack" and gets an OK response. That
  is repeated with another OK. Then it says "Starting Daily apt upgrade
  and clean activities" followed by an OK. Next is a second attempt for
  the same "apt upgrade" and it appears to be frozen. No OK ever
  received and no further progress towards booting.

  Not sure how additional details can be acquired.

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

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


[Kernel-packages] [Bug 1814069] Re: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2

2019-02-11 Thread Chunk
The original report would have to be gen 1 since Rene is using Win
Server 2008.

My failure is also with gen 1. (I'm using 2012, not 2012 R2, so gen 2
isn't an option for me.)

Since Graham is on 2012 R2, perhaps he can confirm whether his VMs (both
the failed one and the newly-created working one) are gen 1 or 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/1814069

Title:
  kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu stuck on booting on HyperV Server 2008R2.
  I saw kernel messages, seems to load ram image the boot is stuck.
  Seems to be a problem with hyperv drivers propably harddrive.
  Reverted back to the previous kernel.

  Description:Ubuntu 18.04.1 LTS
  Release:18.04Description:Ubuntu 18.04.1 LTS
  Release:18.04
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 31 08:52 seq
   crw-rw 1 root audio 116, 33 Jan 31 08:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=86036ccb-bc11-11e8-93c9-00155dfd7535 ro maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  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
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/19/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090004
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 8531-7125-9206-2460-7819-2663-90
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090004:bd03/19/2009:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

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

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


[Kernel-packages] [Bug 1814759] Re: linux-gcp: 4.18.0-1007.8 -proposed tracker

2019-02-11 Thread Brad Figg
** Changed in: kernel-sru-workflow/upload-to-ppa-dnu
   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: 1814749
  phase: Packaging
  phase-changed: Friday, 08. February 2019 01:08 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-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1814759

Title:
  linux-gcp: 4.18.0-1007.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 upload-to-ppa-dnu series:
  Invalid
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: 1814749
  phase: Packaging
  phase-changed: Friday, 08. February 2019 01:08 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/1814759/+subscriptions

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


[Kernel-packages] [Bug 1814759] Re: linux-gcp: 4.18.0-1007.8 -proposed tracker

2019-02-11 Thread Khaled El Mously
** Summary changed:

- linux-gcp:  -proposed tracker
+ linux-gcp: 4.18.0-1007.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) => Khaled El 
Mously (kmously)

** 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) => Khaled El 
Mously (kmously)

** 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) => Khaled El 
Mously (kmously)

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

Title:
  linux-gcp: 4.18.0-1007.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 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: 1814749
  phase: Packaging
  phase-changed: Friday, 08. February 2019 01:08 UTC
  reason:
prepare-package: Pending -- version not specified

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

-- 
Mailing list: https://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 1814069] Re: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2

2019-02-11 Thread Terry Rudd
On 02/11/2019 05:18 PM, Marcelo Cerri wrote:
> Does the problem happen in a gen1 or gen2 VM?
> 
Will ask
Terry

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

Title:
  kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu stuck on booting on HyperV Server 2008R2.
  I saw kernel messages, seems to load ram image the boot is stuck.
  Seems to be a problem with hyperv drivers propably harddrive.
  Reverted back to the previous kernel.

  Description:Ubuntu 18.04.1 LTS
  Release:18.04Description:Ubuntu 18.04.1 LTS
  Release:18.04
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 31 08:52 seq
   crw-rw 1 root audio 116, 33 Jan 31 08:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=86036ccb-bc11-11e8-93c9-00155dfd7535 ro maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  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
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/19/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090004
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 8531-7125-9206-2460-7819-2663-90
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090004:bd03/19/2009:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

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

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


[Kernel-packages] [Bug 1814749] Re: linux: 4.18.0-16.17 -proposed tracker

2019-02-11 Thread Khaled El Mously
** Tags removed: kernel-sru-cycle-2019.02.04

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

Title:
  linux: 4.18.0-16.17 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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 1814750 (linux-hwe), bug 1814751 (linux-hwe-edge), bug 1814752 
(linux-aws-edge), bug 1814753 (linux-azure-edge), bug 1814754 (linux-gcp-edge), 
bug 1814761 (linux-azure-edge)
  derivatives: bug 1814755 (linux-raspi2), bug 1814757 (linux-aws), bug 1814758 
(linux-azure), bug 1814759 (linux-gcp), bug 1814760 (linux-kvm)
  -- swm properties --
  backports: bug 1815537 (linux-aws-edge)
  boot-testing-requested: true
  bugs-spammed: true
  derivatives: null
  phase: Testing
  phase-changed: Tuesday, 12. February 2019 00:34 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1814749] Re: linux: 4.18.0-16.17 -proposed tracker

2019-02-11 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => 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 1814750 (linux-hwe), bug 1814751 (linux-hwe-edge), bug 1814752 
(linux-aws-edge), bug 1814753 (linux-azure-edge), bug 1814754 (linux-gcp-edge), 
bug 1814761 (linux-azure-edge)
  derivatives: bug 1814755 (linux-raspi2), bug 1814757 (linux-aws), bug 1814758 
(linux-azure), bug 1814759 (linux-gcp), bug 1814760 (linux-kvm)
  -- swm properties --
+ backports: bug 1815537 (linux-aws-edge)
  boot-testing-requested: true
  bugs-spammed: true
+ derivatives: null
  phase: Testing
- phase-changed: Monday, 11. February 2019 11:05 UTC
+ phase-changed: Tuesday, 12. February 2019 00:34 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
- backports: bug 1815536 (linux-aws-edge)
- derivatives:
- backports: bug 1815537 (linux-aws-edge)
- derivatives:

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

Title:
  linux: 4.18.0-16.17 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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 1814750 (linux-hwe), bug 1814751 (linux-hwe-edge), bug 1814752 
(linux-aws-edge), bug 1814753 (linux-azure-edge), bug 1814754 (linux-gcp-edge), 
bug 1814761 (linux-azure-edge)
  derivatives: bug 1814755 (linux-raspi2), bug 1814757 (linux-aws), bug 1814758 
(linux-azure), bug 1814759 (linux-gcp), bug 1814760 (linux-kvm)
  -- swm properties --
  backports: bug 1815537 (linux-aws-edge)
  boot-testing-requested: true
  bugs-spammed: true
  derivatives: null
  phase: Testing
  phase-changed: Tuesday, 12. February 2019 00:34 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1814749] Re: linux: 4.18.0-16.17 -proposed tracker

2019-02-11 Thread Khaled El Mously
** 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 1814750 (linux-hwe), bug 1814751 (linux-hwe-edge), bug 1814752 
(linux-aws-edge), bug 1814753 (linux-azure-edge), bug 1814754 (linux-gcp-edge), 
bug 1814761 (linux-azure-edge)
  derivatives: bug 1814755 (linux-raspi2), bug 1814757 (linux-aws), bug 1814758 
(linux-azure), bug 1814759 (linux-gcp), bug 1814760 (linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Monday, 11. February 2019 11:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  backports: bug 1815536 (linux-aws-edge)
  derivatives:
+ backports: bug 1815537 (linux-aws-edge)
+ derivatives:

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

Title:
  linux: 4.18.0-16.17 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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 1814750 (linux-hwe), bug 1814751 (linux-hwe-edge), bug 1814752 
(linux-aws-edge), bug 1814753 (linux-azure-edge), bug 1814754 (linux-gcp-edge), 
bug 1814761 (linux-azure-edge)
  derivatives: bug 1814755 (linux-raspi2), bug 1814757 (linux-aws), bug 1814758 
(linux-azure), bug 1814759 (linux-gcp), bug 1814760 (linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Monday, 11. February 2019 11:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  backports: bug 1815536 (linux-aws-edge)
  derivatives:
  backports: bug 1815537 (linux-aws-edge)
  derivatives:

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

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


[Kernel-packages] [Bug 1814069] Re: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2

2019-02-11 Thread Marcelo Cerri
Does the problem happen in a gen1 or gen2 VM?

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

Title:
  kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu stuck on booting on HyperV Server 2008R2.
  I saw kernel messages, seems to load ram image the boot is stuck.
  Seems to be a problem with hyperv drivers propably harddrive.
  Reverted back to the previous kernel.

  Description:Ubuntu 18.04.1 LTS
  Release:18.04Description:Ubuntu 18.04.1 LTS
  Release:18.04
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 31 08:52 seq
   crw-rw 1 root audio 116, 33 Jan 31 08:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=86036ccb-bc11-11e8-93c9-00155dfd7535 ro maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  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
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/19/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090004
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 8531-7125-9206-2460-7819-2663-90
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090004:bd03/19/2009:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

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

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


[Kernel-packages] [Bug 1814749] Re: linux: 4.18.0-16.17 -proposed tracker

2019-02-11 Thread Khaled El Mously
** Changed in: kernel-sru-workflow/prepare-package
   Status: Fix Released => Confirmed

** Tags added: kernel-sru-cycle-2019.02.04

** 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 1814750 (linux-hwe), bug 1814751 (linux-hwe-edge), bug 1814752 
(linux-aws-edge), bug 1814753 (linux-azure-edge), bug 1814754 (linux-gcp-edge), 
bug 1814761 (linux-azure-edge)
  derivatives: bug 1814755 (linux-raspi2), bug 1814757 (linux-aws), bug 1814758 
(linux-azure), bug 1814759 (linux-gcp), bug 1814760 (linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Monday, 11. February 2019 11:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
+ backports: bug 1815536 (linux-aws-edge)
+ derivatives:

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

Title:
  linux: 4.18.0-16.17 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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 1814750 (linux-hwe), bug 1814751 (linux-hwe-edge), bug 1814752 
(linux-aws-edge), bug 1814753 (linux-azure-edge), bug 1814754 (linux-gcp-edge), 
bug 1814761 (linux-azure-edge)
  derivatives: bug 1814755 (linux-raspi2), bug 1814757 (linux-aws), bug 1814758 
(linux-azure), bug 1814759 (linux-gcp), bug 1814760 (linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Monday, 11. February 2019 11:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  backports: bug 1815536 (linux-aws-edge)
  derivatives:

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

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


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

2019-02-11 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/1815535

Title:
  16.04 on Dell Precision shuts down during suspend if AC is unplugged

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My Dell Precision 5510 laptop has recent drivers for graphics. I
  installed a lot of updates this week, and I have been finding that the
  laptop shuts down in the "Suspend" state if at any point AC power is
  unplugged.

  Steps to reproduce:
  1. With laptop plugged in to AC power and Ubuntu running, use the GUI to 
enter the suspend state.
  2. With the laptop suspended, unplug AC power.
  3. Plug in AC power again.
  4. Press the ACPI power button to trigger a wake from suspend.

  Expected behavior:
  Login screen to resume the pre-suspend session.

  Actual behavior:
  Laptop goes through POST. During startup, fsck-like text flashes on the 
screen indicating that a "hard shutdown" occurred.

  What I've done:
  (I boot with GRUB from an encrypted LVM partition.) My grub config already 
has the "acpi_sleep=nonvs" option from the last time I had a suspend-related 
issue. Most online fora will recommend this as a fix, but I am still having 
these problems. I even re-ran grub-update just to be sure.

  uname -a output:
  Linux simon-Precision-5510 4.4.0-142-generic #168-Ubuntu SMP Wed Jan 16 
21:00:45 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-142-generic 4.4.0-142.168
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  Uname: Linux 4.4.0-142-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  simon  3648 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Feb 11 15:40:27 2019
  HibernationDevice: RESUME=UUID=1c08d766-1118-4cc3-90dc-7671d83d7ae0
  InstallationDate: Installed on 2016-06-23 (963 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 004: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 5510
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-142-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro acpi_sleep=nonvs quiet splash 
acpi_sleep=nonvs vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-142-generic N/A
   linux-backports-modules-4.4.0-142-generic  N/A
   linux-firmware 1.157.21
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2019-01-05 (37 days ago)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N8J4R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0N8J4R:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 5510
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1815535] [NEW] 16.04 on Dell Precision shuts down during suspend if AC is unplugged

2019-02-11 Thread Simon Kuang
Public bug reported:

My Dell Precision 5510 laptop has recent drivers for graphics. I
installed a lot of updates this week, and I have been finding that the
laptop shuts down in the "Suspend" state if at any point AC power is
unplugged.

Steps to reproduce:
1. With laptop plugged in to AC power and Ubuntu running, use the GUI to enter 
the suspend state.
2. With the laptop suspended, unplug AC power.
3. Plug in AC power again.
4. Press the ACPI power button to trigger a wake from suspend.

Expected behavior:
Login screen to resume the pre-suspend session.

Actual behavior:
Laptop goes through POST. During startup, fsck-like text flashes on the screen 
indicating that a "hard shutdown" occurred.

What I've done:
(I boot with GRUB from an encrypted LVM partition.) My grub config already has 
the "acpi_sleep=nonvs" option from the last time I had a suspend-related issue. 
Most online fora will recommend this as a fix, but I am still having these 
problems. I even re-ran grub-update just to be sure.

uname -a output:
Linux simon-Precision-5510 4.4.0-142-generic #168-Ubuntu SMP Wed Jan 16 
21:00:45 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-142-generic 4.4.0-142.168
ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
Uname: Linux 4.4.0-142-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  simon  3648 F pulseaudio
CurrentDesktop: Unity
Date: Mon Feb 11 15:40:27 2019
HibernationDevice: RESUME=UUID=1c08d766-1118-4cc3-90dc-7671d83d7ae0
InstallationDate: Installed on 2016-06-23 (963 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
 Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 004: ID 0c45:6713 Microdia 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Precision 5510
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-142-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro acpi_sleep=nonvs quiet splash 
acpi_sleep=nonvs vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-142-generic N/A
 linux-backports-modules-4.4.0-142-generic  N/A
 linux-firmware 1.157.21
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2019-01-05 (37 days ago)
dmi.bios.date: 04/07/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 01.02.00
dmi.board.name: 0N8J4R
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0N8J4R:rvrA01:cvnDellInc.:ct9:cvr:
dmi.product.name: Precision 5510
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug xenial

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

Title:
  16.04 on Dell Precision shuts down during suspend if AC is unplugged

Status in linux package in Ubuntu:
  New

Bug description:
  My Dell Precision 5510 laptop has recent drivers for graphics. I
  installed a lot of updates this week, and I have been finding that the
  laptop shuts down in the "Suspend" state if at any point AC power is
  unplugged.

  Steps to reproduce:
  1. With laptop plugged in to AC power and Ubuntu running, use the GUI to 
enter the suspend state.
  2. With the laptop suspended, unplug AC power.
  3. Plug in AC power again.
  4. Press the ACPI power button to trigger a wake from suspend.

  Expected behavior:
  Login screen to resume the pre-suspend session.

  Actual behavior:
  Laptop goes through POST. During startup, fsck-like text flashes on the 
screen indicating that a "hard shutdown" occurred.

  What I've done:
  (I boot with GRUB from an encrypted LVM partition.) My grub config already 
has the "acpi_sleep=nonvs" option from the last time I had a suspend-related 
issue. Most online fora will recommend this as a fix, but I am still having 
these problems. I even re-ran grub-update just to be sure.

  uname -a output:
  Linux simon-Precision-5510 4.4.0-142-generic #168-Ubuntu SMP Wed Jan 16 
21:00:45 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-142-generic 4.4.0-142.168
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  Uname: Linux 4.4.0-142-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  simon  

[Kernel-packages] [Bug 1773184] Re: Starting a KVM guest in a guest (nested VM) crash the kernel

2019-02-11 Thread sean mooney
just adding some more info.
i also deploy openstack rocky on a ubuntu 18.04 host

Linux cloud-5 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux

with ubuntu 18.04 l1 guest running 
Linux numa-migration-1 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

and when i lauch a cirros l2 guest i get very similar kvm_intel call
traces.

if i upgrade the l1 guest kernel to the latest linux-virtual-hwe-18.04-edge 
kernel
which is currently

Linux numa-migration-2 4.18.0-15-generic #16~18.04.1-Ubuntu SMP Thu Feb
7 14:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

i still get the same crashes when i launch the l2 cirros image


i was originally wondering if this was some how related to the gust cpu model

so i tried seting the l1 and l2 guest cpu_mode to host-passthough
to maximies the feature that were availabel tot he guest

i then also tried to limit the  l2 guest to the kvm64 cpu-model so that the l2 
guest
used the minium set of kvm feature but this  did not seam to have an benifical
effect.

the host is useign

Intel(R) Xeon(R) CPU E5-2697 v2 @ 2.70GHz cpus which i have used in the past 
with
ubuntu 16.04 and nested virt without issue so this seams to be related to the 
18.04 kenel in some way.

the fact that i am seeing the same issue on a ubuntu 18.04 host with an
18.04  l1 guest

and that gyurco is only seeing this with an 18.04 l1 guest makes me
think that this is likely an issue with kvm in the l1 guests kernel not
the hosts kernel.

im going to try and confrim that with a centos 7 l1 guest tommorow but since i 
would like to be
able to do python 3.6/3.7 testing in my local settup i would prefer to use a 
Ubuntu 18.04 l1 guest in the long run so i hope this can be resolved.

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

Title:
  Starting a KVM guest in a guest (nested VM) crash the kernel

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

Bug description:
  linux-image-4.15.0.22 (20, and probably earlier, too) panics when
  starting a guest VM in a nested manner.

  compute1 login: [ 4847.733004] general protection fault:  [#1] SMP PTI
  [ 4847.736595] Modules linked in: vxlan ip6_udp_tunnel udp_tunnel ebt_arp 
ebt_among ip6table_raw nf_conntrack_ipv6 nf_defrag_ipv6 xt_CT xt_mac xt_comment 
xt_physdev xt_set ip_set_hash_net ip_set nfnetlink vhost_net vhost tap 
xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat 
nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack 
ipt_REJECT nf_reject_ipv4 xt_tcpudp kvm_intel ip6table_filter ip6_tables 
iptable_filter ebtable_filter ebtable_nat ebtables iptable_raw br_netfilter 
bridge stp llc nls_iso8859_1 kvm irqbypass joydev input_leds serio_raw 
sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp 
libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor
  [ 4847.756237]  async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc 
aesni_intel aes_x86_64 crypto_simd glue_helper cryptd psmouse virtio_blk 
virtio_net floppy [last unloaded: kvm_intel]
  [ 4847.762893] CPU: 1 PID: 13789 Comm: CPU 0/KVM Not tainted 
4.15.0-22-generic #24-Ubuntu
  [ 4847.765154] Hardware name: OpenStack Foundation OpenStack Nova, BIOS 
1.10.2-1ubuntu1~cloud0 04/01/2014
  [ 4847.767764] RIP: 0010:native_write_cr4+0x4/0x10
  [ 4847.769085] RSP: 0018:9daf4119bb70 EFLAGS: 00010006
  [ 4847.770629] RAX: 000626e0 RBX: 0046 RCX: 
8edcbfc8
  [ 4847.772771] RDX: 8edcbfc94020 RSI: 8edcbfca5040 RDI: 
000606e0
  [ 4847.774965] RBP: 9daf4119bb70 R08: fff8 R09: 
000d
  [ 4847.777175] R10: c078c76e2000 R11: 0cd0 R12: 
00025040
  [ 4847.779213] R13:  R14: 8edc438409a0 R15: 
8edc43855278
  [ 4847.781230] FS:  7f9a09a02700() GS:8edcbfc8() 
knlGS:
  [ 4847.783548] CS:  0010 DS:  ES:  CR0: 80050033
  [ 4847.785233] CR2: 7f99fb80cd50 CR3: 000152e0a002 CR4: 
000626e0
  [ 4847.787225] Call Trace:
  [ 4847.788062]  hardware_disable+0xaa/0xc0 [kvm_intel]
  [ 4847.789460]  ? vcpu_stat_get_per_vm_open+0x20/0x20 [kvm]
  [ 4847.791025]  kvm_arch_hardware_disable+0x19/0x40 [kvm]
  [ 4847.792664]  hardware_disable_nolock+0x2b/0x30 [kvm]
  [ 4847.794260]  on_each_cpu+0x46/0x60
  [ 4847.795302]  hardware_disable_all_nolock+0x35/0x40 [kvm]
  [ 4847.796896]  hardware_disable_all+0x1a/0x30 [kvm]
  [ 4847.798267]  kvm_put_kvm+0x1f8/0x260 [kvm]
  [ 4847.799470]  kvm_vm_release+0x21/0x30 [kvm]
  [ 4847.800758]  __fput+0xea/0x220
  [ 4847.801681]  

[Kernel-packages] [Bug 1802050] Re: Kernel module crash 4.18.0-10 after upgrade from 18.04 to 18.10

2019-02-11 Thread kenorb
My OS details:
$ uname -a
Linux Ubuntu-PC 4.18.0-15-generic #16-Ubuntu SMP Thu Feb 7 10:56:39 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

$ lsb_release -a 
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.10
Release:18.10
Codename:   cosmic

$ lsmod | grep nvidia
nvidia_uvm786432  0
nvidia_drm 40960  8
nvidia_modeset   1110016  12 nvidia_drm
nvidia  14368768  696 nvidia_uvm,nvidia_modeset
drm_kms_helper172032  1 nvidia_drm
drm   458752  11 drm_kms_helper,nvidia_drm
ipmi_msghandler   102400  2 ipmi_devintf,nvidia

$ modinfo nvidia
filename:   /lib/modules/4.18.0-15-generic/updates/dkms/nvidia.ko
alias:  char-major-195-*
version:390.87
supported:  external
license:NVIDIA
srcversion: 9680830EEE0BAB392576E99
alias:  pci:v10DEd0E00sv*sd*bc04sc80i00*
alias:  pci:v10DEd*sv*sd*bc03sc02i00*
alias:  pci:v10DEd*sv*sd*bc03sc00i00*
depends:ipmi_msghandler
retpoline:  Y
name:   nvidia
vermagic:   4.18.0-15-generic SMP mod_unload

$ lspci -v | grep NVIDIA
17:00.0 VGA compatible controller: NVIDIA Corporation GP102 [GeForce GTX 1080 
Ti] (rev a1) (prog-if 00 [VGA controller])
17:00.1 Audio device: NVIDIA Corporation GP102 HDMI Audio Controller (rev a1)
18:00.0 VGA compatible controller: NVIDIA Corporation GP102 [GeForce GTX 1080 
Ti] (rev a1) (prog-if 00 [VGA controller])
18:00.1 Audio device: NVIDIA Corporation GP102 HDMI Audio Controller (rev a1)
65:00.0 VGA compatible controller: NVIDIA Corporation GP102 [GeForce GTX 1080 
Ti] (rev a1) (prog-if 00 [VGA controller])
65:00.1 Audio device: NVIDIA Corporation GP102 HDMI Audio Controller (rev a1)
b4:00.0 VGA compatible controller: NVIDIA Corporation GP102 [GeForce GTX 1080 
Ti] (rev a1) (prog-if 00 [VGA controller])
b4:00.1 Audio device: NVIDIA Corporation GP102 HDMI Audio Controller (rev a1)

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

Title:
  Kernel module crash 4.18.0-10 after upgrade from 18.04 to 18.10

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

Bug description:
  [   56.996976] [ cut here ]
  [   56.996978] Bad or missing usercopy whitelist? Kernel memory exposure 
attempt detected from SLUB object 'nvidia_stack_cache' (offset 11440, size 3)!
  [   56.996985] WARNING: CPU: 3 PID: 2547 at mm/usercopy.c:81 
usercopy_warn+0x81/0xa0
  [   56.996985] Modules linked in: ebtable_filter ebtables ip6table_filter 
ip6_tables iptable_filter devlink bpfilter pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) nvidia_uvm(POE) eeepc_wmi asus_wmi 
snd_hda_codec_hdmi mxm_wmi wmi_bmof sparse_keymap nvidia_drm(POE) 
nvidia_modeset(POE) snd_hda_codec_realtek intel_rapl nvidia(POE) 
snd_hda_codec_generic x86_pkg_temp_thermal intel_powerclamp coretemp 
snd_hda_intel kvm_intel kvm snd_hda_codec joydev snd_hda_core snd_usb_audio 
snd_usbmidi_lib irqbypass snd_hwdep input_leds crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel snd_pcm pcbc aesni_intel snd_seq_midi snd_seq_midi_event 
aes_x86_64 snd_rawmidi crypto_simd cryptd snd_seq glue_helper drm_kms_helper 
intel_cstate drm ipmi_devintf ipmi_msghandler intel_rapl_perf snd_seq_device 
snd_timer fb_sys_fops
  [   56.997003]  syscopyarea sysfillrect sysimgblt snd mac_hid soundcore wmi 
video mei_me mei acpi_pad sch_fq_codel parport_pc ppdev lp parport ip_tables 
x_tables autofs4 raid10 multipath linear raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq raid0 libcrc32c raid1 hid_generic 
usbhid hid gpio_ich r8169 i2c_i801 mii lpc_ich ahci libahci
  [   56.997016] CPU: 3 PID: 2547 Comm: Xorg Tainted: P   OE 
4.18.0-10-generic #11-Ubuntu
  [   56.997017] Hardware name: ASUS All Series/Z97-K, BIOS 2902 03/31/2016
  [   56.997018] RIP: 0010:usercopy_warn+0x81/0xa0
  [   56.997018] Code: b0 aa 41 51 4d 89 d8 48 c7 c0 89 8d af aa 49 89 f1 48 89 
f9 48 0f 45 c2 48 c7 c7 f0 a1 b0 aa 4c 89 d2 48 89 c6 e8 f1 cf df ff <0f> 0b 48 
83 c4 18 c9 c3 48 c7 c6 b2 8a b2 aa 49 89 f1 49 89 f3 eb 
  [   56.997030] RSP: 0018:b9550248bb08 EFLAGS: 00010286
  [   56.997031] RAX:  RBX: 90fdc8535cb0 RCX: 
0006
  [   56.997032] RDX: 0007 RSI: 0096 RDI: 
90fdded964b0
  [   56.997032] RBP: b9550248bb20 R08: 0001 R09: 
038f
  [   56.997032] R10: 0004 R11:  R12: 
0003
  [   56.997033] R13: 0001 R14: 90fdc8535cb3 R15: 
90fdc8535cf8
  [   56.997033] FS:  7f854792ba80() GS:90fdded8() 
knlGS:
  [   56.997034] CS:  0010 DS:  ES:  CR0: 80050033
  [   56.997034] CR2: 7f8543fd2110 CR3: 000406668006 CR4: 
001606e0
  [  

[Kernel-packages] [Bug 1812561] Re: [MacBookPro11, 5] wakes up and suspends in a loop while closed

2019-02-11 Thread Christopher M. Penalver
Selwyn, one may follow the below to confirm results for your hardware:
https://wiki.ubuntu.com/Kernel/KernelBisection

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

Title:
  [MacBookPro11,5] wakes up and suspends in a loop while closed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Similar bug:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507472/

  The first time suspending works great but after that suspending causes
  the laptop to wake up regardless of the method used to suspend.

  Sidenote: thanks to penalvch for explaining how to report this!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-13-generic 4.18.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  siilwyn1852 F pulseaudio
   /dev/snd/controlC1:  siilwyn1852 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 20 13:40:14 2019
  InstallationDate: Installed on 2019-01-19 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc.
   Bus 001 Device 003: ID 05ac:0274 Apple, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro11,5
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=57f2dc4c-30f7-40b6-a9db-9b6f93c214cb ro quiet splash vt.handoff=1
  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
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/18/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP114.88Z.0172.B25.1706181512
  dmi.board.name: Mac-06F11F11946D27C5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,5
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-06F11F11946D27C5
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B25.1706181512:bd06/18/2017:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro11,5
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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


[Kernel-packages] [Bug 830915] Re: Error during kernel upgrade: Could not locate dkms.conf file

2019-02-11 Thread cement_head
@nazar-pc I have no idea what you are talking about. "remove any
directories from old modules you had in past and do not have installed
anymore" doesn't mean anything to me at all. What "any directories"?
Can someone please provide step-by-step instructions for all of this?

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

Title:
  Error during kernel upgrade: Could not locate dkms.conf file

Status in dkms package in Ubuntu:
  Incomplete

Bug description:
  Настраивается пакет linux-image-3.0.0-9-generic (3.0.0-9.12) ...
  Running depmod.
  update-initramfs: deferring update (hook will be called later)
  Examining /etc/kernel/postinst.d.
  run-parts: executing /etc/kernel/postinst.d/dkms 3.0.0-9-generic 
/boot/vmlinuz-3.0.0-9-generic
  Error! Could not locate dkms.conf file.
  File:  does not exist.
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.0.0-9-generic 
/boot/vmlinuz-3.0.0-9-generic
  update-initramfs: Generating /boot/initrd.img-3.0.0-9-generic
  run-parts: executing /etc/kernel/postinst.d/pm-utils 3.0.0-9-generic 
/boot/vmlinuz-3.0.0-9-generic
  run-parts: executing /etc/kernel/postinst.d/update-notifier 3.0.0-9-generic 
/boot/vmlinuz-3.0.0-9-generic
  run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.0.0-9-generic 
/boot/vmlinuz-3.0.0-9-generic
  Generating grub.cfg ...
  Found linux image: /boot/vmlinuz-3.0.0-9-generic
  Found initrd image: /boot/initrd.img-3.0.0-9-generic
  Found linux image: /boot/vmlinuz-3.0.0-8-generic
  Found initrd image: /boot/initrd.img-3.0.0-8-generic
  Found linux image: /boot/vmlinuz-2.6.38-10-generic
  Found initrd image: /boot/initrd.img-2.6.38-10-generic
  Found memtest86+ image: /boot/memtest86+.bin
  Found Ubuntu Natty (development branch) (11.04) on /dev/sdb5
  done

  This, however, doesn't seem to be fatal.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: dkms 2.2.0.2-1
  ProcVersionSignature: Ubuntu 3.0.0-8.11-generic 3.0.1
  Uname: Linux 3.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Mon Aug 22 12:43:31 2011
  InstallationMedia: Xubuntu 10.10 "Maverick Meerkat" - Release amd64 
(20101008.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: dkms
  UpgradeStatus: Upgraded to oneiric on 2011-08-10 (11 days ago)

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

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


[Kernel-packages] [Bug 1812561] Re: [MacBookPro11, 5] wakes up and suspends in a loop while closed

2019-02-11 Thread Selwyn
There should be multiple dmesg attachments, do I have to make them public or 
something? For me the following are shown:
dmesg-2-systemctl-suspend-keywake.txt
dmesg-2-usbcore-dyndbg.txt
dmesg-core.txt
dmesg-devices.txt
dmesg-freezer.txt
dmesg-none.txt
dmesg-processors.txt

I'll see if I can figure out how to try that particular commit but since
the Mathias confirmed it having the exact same issue I'm pretty sure.

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

Title:
  [MacBookPro11,5] wakes up and suspends in a loop while closed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Similar bug:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507472/

  The first time suspending works great but after that suspending causes
  the laptop to wake up regardless of the method used to suspend.

  Sidenote: thanks to penalvch for explaining how to report this!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-13-generic 4.18.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  siilwyn1852 F pulseaudio
   /dev/snd/controlC1:  siilwyn1852 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 20 13:40:14 2019
  InstallationDate: Installed on 2019-01-19 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc.
   Bus 001 Device 003: ID 05ac:0274 Apple, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro11,5
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=57f2dc4c-30f7-40b6-a9db-9b6f93c214cb ro quiet splash vt.handoff=1
  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
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/18/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP114.88Z.0172.B25.1706181512
  dmi.board.name: Mac-06F11F11946D27C5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,5
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-06F11F11946D27C5
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B25.1706181512:bd06/18/2017:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro11,5
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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


[Kernel-packages] [Bug 1802050] Re: Kernel module crash 4.18.0-10 after upgrade from 18.04 to 18.10

2019-02-11 Thread kenorb
Also, worth to note, I had similar crashes before upgrading to nVidia,
by using Nouveau driver. See:
https://bugs.freedesktop.org/show_bug.cgi?id=100567

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

Title:
  Kernel module crash 4.18.0-10 after upgrade from 18.04 to 18.10

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

Bug description:
  [   56.996976] [ cut here ]
  [   56.996978] Bad or missing usercopy whitelist? Kernel memory exposure 
attempt detected from SLUB object 'nvidia_stack_cache' (offset 11440, size 3)!
  [   56.996985] WARNING: CPU: 3 PID: 2547 at mm/usercopy.c:81 
usercopy_warn+0x81/0xa0
  [   56.996985] Modules linked in: ebtable_filter ebtables ip6table_filter 
ip6_tables iptable_filter devlink bpfilter pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) nvidia_uvm(POE) eeepc_wmi asus_wmi 
snd_hda_codec_hdmi mxm_wmi wmi_bmof sparse_keymap nvidia_drm(POE) 
nvidia_modeset(POE) snd_hda_codec_realtek intel_rapl nvidia(POE) 
snd_hda_codec_generic x86_pkg_temp_thermal intel_powerclamp coretemp 
snd_hda_intel kvm_intel kvm snd_hda_codec joydev snd_hda_core snd_usb_audio 
snd_usbmidi_lib irqbypass snd_hwdep input_leds crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel snd_pcm pcbc aesni_intel snd_seq_midi snd_seq_midi_event 
aes_x86_64 snd_rawmidi crypto_simd cryptd snd_seq glue_helper drm_kms_helper 
intel_cstate drm ipmi_devintf ipmi_msghandler intel_rapl_perf snd_seq_device 
snd_timer fb_sys_fops
  [   56.997003]  syscopyarea sysfillrect sysimgblt snd mac_hid soundcore wmi 
video mei_me mei acpi_pad sch_fq_codel parport_pc ppdev lp parport ip_tables 
x_tables autofs4 raid10 multipath linear raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq raid0 libcrc32c raid1 hid_generic 
usbhid hid gpio_ich r8169 i2c_i801 mii lpc_ich ahci libahci
  [   56.997016] CPU: 3 PID: 2547 Comm: Xorg Tainted: P   OE 
4.18.0-10-generic #11-Ubuntu
  [   56.997017] Hardware name: ASUS All Series/Z97-K, BIOS 2902 03/31/2016
  [   56.997018] RIP: 0010:usercopy_warn+0x81/0xa0
  [   56.997018] Code: b0 aa 41 51 4d 89 d8 48 c7 c0 89 8d af aa 49 89 f1 48 89 
f9 48 0f 45 c2 48 c7 c7 f0 a1 b0 aa 4c 89 d2 48 89 c6 e8 f1 cf df ff <0f> 0b 48 
83 c4 18 c9 c3 48 c7 c6 b2 8a b2 aa 49 89 f1 49 89 f3 eb 
  [   56.997030] RSP: 0018:b9550248bb08 EFLAGS: 00010286
  [   56.997031] RAX:  RBX: 90fdc8535cb0 RCX: 
0006
  [   56.997032] RDX: 0007 RSI: 0096 RDI: 
90fdded964b0
  [   56.997032] RBP: b9550248bb20 R08: 0001 R09: 
038f
  [   56.997032] R10: 0004 R11:  R12: 
0003
  [   56.997033] R13: 0001 R14: 90fdc8535cb3 R15: 
90fdc8535cf8
  [   56.997033] FS:  7f854792ba80() GS:90fdded8() 
knlGS:
  [   56.997034] CS:  0010 DS:  ES:  CR0: 80050033
  [   56.997034] CR2: 7f8543fd2110 CR3: 000406668006 CR4: 
001606e0
  [   56.997035] Call Trace:
  [   56.997038]  __check_heap_object+0xc2/0x110
  [   56.997039]  __check_object_size+0x14c/0x178
  [   56.997148]  os_memcpy_to_user+0x26/0x50 [nvidia]
  [   56.997254]  _nv009384rm+0xbf/0xe0 [nvidia]
  [   56.997255] WARNING: kernel stack frame pointer at 8fe294b8 in 
Xorg:2547 has bad value 5fea09aa
  [   56.997256] unwind stack type:0 next_sp:  (null) mask:0x2 
graph_idx:0
  [   56.997257] 1bbff756: b9550248bb30 (0xb9550248bb30)
  [   56.997258] 21ffd201: a9c69a82 
(__check_heap_object+0xc2/0x110)
  [   56.997258] 2ec89026: b9550248bb60 (0xb9550248bb60)
  [   56.997259] 297b0120: a9c91abc 
(__check_object_size+0x14c/0x178)
  [   56.997259] 8569feab: 0003 (0x3)
  [   56.997260] b2feea66: 90fdc8535cb0 (0x90fdc8535cb0)
  [   56.997260] a5345c20: 55924226a63e (0x55924226a63e)
  [   56.997260] 798de38a:  ...
  [   56.997261] 871cf253: b9550248bb88 (0xb9550248bb88)
  [   56.997311] 5645fcd2: c0b305b6 
(os_memcpy_to_user+0x26/0x50 [nvidia])
  [   56.997311] 929e7969: 0003 (0x3)
  [   56.997312] cbb9721c: 55924226a63e (0x55924226a63e)
  [   56.997312] cf624d15: 90fdc8535cb0 (0x90fdc8535cb0)
  [   56.997312] 8fe294b8: 90fdc8535ca8 (0x90fdc8535ca8)
  [   56.997417] 7dbcdd8d: c110087f (_nv009384rm+0xbf/0xe0 
[nvidia])
  [   56.997418] c0dd2ba2: 90fdc8535c88 (0x90fdc8535c88)
  [   56.997418] a931d446:  ...
  [   56.997418] 28151017: 90fda8ed62e8 (0x90fda8ed62e8)
  [   56.997419] f1c853ed: 90fdc8535db8 (0x90fdc8535db8)
  [   

[Kernel-packages] [Bug 1802050] Re: Kernel module crash 4.18.0-10 after upgrade from 18.04 to 18.10

2019-02-11 Thread kenorb
Related: https://forums.geforce.com/default/topic/1098094/geforce-
drivers/kernel-crash-at-_nv009384rm-os_memcpy_to_user-bad-or-missing-
usercopy-whitelist-/

Here are the full logs:
- 1st crash: https://gist.github.com/kenorb/4b7c333e648498f3d31c3ed8dc6625f4
- 2nd crash (posted above): 
https://gist.github.com/kenorb/8ff664d2cb439ad624b438a954b11c62

Logs:
caller os_map_kernel_space.part.9+0xdb/0x120 [nvidia] mapping multiple BARs
Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from 
SLUB object 'nvidia_stack_cache' (offset 11440, size 3)!
WARNING: CPU: 11 PID: 7002 at mm/usercopy.c:81 usercopy_warn+0x81/0xa0
CPU: 11 PID: 7002 Comm: Xorg Tainted: P   O  4.18.0-15-generic 
#16-Ubuntu
Hardware name: Punch technology 646-716-44/ROG RAMPAGE VI EXTREME, BIOS 1401 
05/10/2018
RIP: 0010:usercopy_warn+0x81/0xa0
RSP: 0018:b1a54aa5fb08 EFLAGS: 00010286
RAX:  RBX: 936a9e355cb0 RCX: 0006
RDX: 0007 RSI: 0096 RDI: 936b1f2d64b0
RBP: b1a54aa5fb20 R08: 0001 R09: 0692
R10: 0004 R11:  R12: 0003
R13: 0001 R14: 936a9e355cb3 R15: 936a9e355cf8
FS:  7f7c7ce35a80() GS:936b1f2c() knlGS:
CS:  0010 DS:  ES:  CR0: 80050033
CR2: 7f7c794d0110 CR3: 001f8b2d0006 CR4: 003606e0
DR0:  DR1:  DR2: 
DR3:  DR6: fffe0ff0 DR7: 0400
Call Trace:
 __check_heap_object+0xc2/0x110
 __check_object_size+0x14c/0x178
 os_memcpy_to_user+0x26/0x50 [nvidia]
 _nv009384rm+0xbf/0xe0 [nvidia]
WARNING: kernel stack frame pointer at 9e6b26f6 in Xorg:7002 has bad 
value d8fadd4b
unwind stack type:0 next_sp:  (null) mask:0x2 graph_idx:0
3b11c2d2: b1a54aa5fb30 (0xb1a54aa5fb30)
764c1375: ad469e02 (__check_heap_object+0xc2/0x110)
...
 ? _nv028097rm+0x79/0x90 [nvidia]
 ? _nv028097rm+0x55/0x90 [nvidia]
 ? _nv013699rm+0xee/0x100 [nvidia]
 ? _nv015347rm+0x154/0x270 [nvidia]
 ? _nv008317rm+0x134/0x1a0 [nvidia]
 ? _nv008296rm+0x29c/0x2b0 [nvidia]
 ? _nv001072rm+0xe/0x20 [nvidia]
 ? _nv007324rm+0xd8/0x100 [nvidia]
 ? _nv001171rm+0x627/0x830 [nvidia]
 ? rm_ioctl+0x73/0x100 [nvidia]
 ? __check_object_size+0x91/0x178
 ? nvidia_ioctl+0x56a/0x720 [nvidia]
 ? nvidia_frontend_unlocked_ioctl+0x3e/0x50 [nvidia]
 ? do_vfs_ioctl+0xa8/0x620
 ? handle_mm_fault+0xe1/0x210
 ? ksys_ioctl+0x67/0x90
 ? __x64_sys_ioctl+0x1a/0x20
 ? do_syscall_64+0x5a/0x110
 ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
---[ end trace e0cf3a831124a7e9 ]---

** Bug watch added: freedesktop.org Bugzilla #100567
   https://bugs.freedesktop.org/show_bug.cgi?id=100567

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

Title:
  Kernel module crash 4.18.0-10 after upgrade from 18.04 to 18.10

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

Bug description:
  [   56.996976] [ cut here ]
  [   56.996978] Bad or missing usercopy whitelist? Kernel memory exposure 
attempt detected from SLUB object 'nvidia_stack_cache' (offset 11440, size 3)!
  [   56.996985] WARNING: CPU: 3 PID: 2547 at mm/usercopy.c:81 
usercopy_warn+0x81/0xa0
  [   56.996985] Modules linked in: ebtable_filter ebtables ip6table_filter 
ip6_tables iptable_filter devlink bpfilter pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) nvidia_uvm(POE) eeepc_wmi asus_wmi 
snd_hda_codec_hdmi mxm_wmi wmi_bmof sparse_keymap nvidia_drm(POE) 
nvidia_modeset(POE) snd_hda_codec_realtek intel_rapl nvidia(POE) 
snd_hda_codec_generic x86_pkg_temp_thermal intel_powerclamp coretemp 
snd_hda_intel kvm_intel kvm snd_hda_codec joydev snd_hda_core snd_usb_audio 
snd_usbmidi_lib irqbypass snd_hwdep input_leds crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel snd_pcm pcbc aesni_intel snd_seq_midi snd_seq_midi_event 
aes_x86_64 snd_rawmidi crypto_simd cryptd snd_seq glue_helper drm_kms_helper 
intel_cstate drm ipmi_devintf ipmi_msghandler intel_rapl_perf snd_seq_device 
snd_timer fb_sys_fops
  [   56.997003]  syscopyarea sysfillrect sysimgblt snd mac_hid soundcore wmi 
video mei_me mei acpi_pad sch_fq_codel parport_pc ppdev lp parport ip_tables 
x_tables autofs4 raid10 multipath linear raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq raid0 libcrc32c raid1 hid_generic 
usbhid hid gpio_ich r8169 i2c_i801 mii lpc_ich ahci libahci
  [   56.997016] CPU: 3 PID: 2547 Comm: Xorg Tainted: P   OE 
4.18.0-10-generic #11-Ubuntu
  [   56.997017] Hardware name: ASUS All Series/Z97-K, BIOS 2902 03/31/2016
  [   56.997018] RIP: 0010:usercopy_warn+0x81/0xa0
  [   56.997018] Code: b0 aa 41 51 4d 89 d8 48 c7 c0 89 8d af aa 49 89 f1 48 89 
f9 48 0f 45 c2 48 c7 c7 f0 a1 b0 aa 4c 

[Kernel-packages] [Bug 1814733] Re: linux-azure: 4.18.0-1009.9~18.04.1 -proposed tracker

2019-02-11 Thread Brad Figg
** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1814726
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 11. February 2019 20:09 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete
+   promote-to-proposed: Holding -- master bug not ready for proposed

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

Title:
  linux-azure: 4.18.0-1009.9~18.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814726
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 11. February 2019 20:09 UTC
  reason:
promote-to-proposed: Holding -- master bug not ready for proposed

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

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


[Kernel-packages] [Bug 1814743] Re: linux-azure: 4.15.0-1038.41 -proposed tracker

2019-02-11 Thread Brad Figg
** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814726
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 11. February 2019 18:36 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete
+   promote-to-proposed: Holding -- master bug not ready for proposed

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814726
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 11. February 2019 18:36 UTC
  reason:
promote-to-proposed: Holding -- master bug not ready for proposed

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

-- 
Mailing list: https://launchpad.net/~kernel-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-02-11 Thread Mauricio Faria de Oliveira
Verification successful on trusty-proposed.

Updates kernel (goes above 2000 connections)
---

root@petilil:~# uname -a
Linux petilil 3.13.0-165-generic #215-Ubuntu SMP Wed Jan 16 11:46:47 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux
root@petilil:~# iptables -F
root@petilil:~# iptables -A INPUT -p tcp -m tcp --syn --dport  -m connlimit 
--connlimit-above 2000 --connlimit-mask 0 -j DROP
root@petilil:~# ulimit -SHn 65000
root@petilil:~# ruby ~ubuntu/server.rb 

root@rotom:~# ulimit -SHn 65000
root@rotom:~# 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


Proposed kernel (stops at 2000 connections)
---

root@petilil:~# uname -a
Linux petilil 3.13.0-166-generic #216-Ubuntu SMP Thu Feb 7 14:07:53 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux
root@petilil:~# iptables -F
root@petilil:~# iptables -A INPUT -p tcp -m tcp --syn --dport  -m connlimit 
--connlimit-above 2000 --connlimit-mask 0 -j DROP 
root@petilil:~# ulimit -SHn 65000
root@petilil:~# ruby ~ubuntu/server.rb 

root@rotom:~# ulimit -SHn 65000 

root@rotom:~# ruby client.rb 10.230.56.100  6000 3
ruby: No such file or directory -- client.rb (LoadError)
root@rotom:~# cd /home/mfo/sf192750/
root@rotom:/home/mfo/sf192750# ruby client.rb 10.230.56.100  6000 3
Connecting to ["10.230.56.100"]: 6000 times with 3
1
2
3
...
2000

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


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

-- 
You 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 Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

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
    

[Kernel-packages] [Bug 1812561] Re: [MacBookPro11, 5] wakes up and suspends in a loop while closed

2019-02-11 Thread Christopher M. Penalver
Selwyn:
>"...all information is in the attachments of the post."

No, its not. You posted one dmesg (multiple requested in article) on a
now old version of upstream kernel (i.e. nearly impossible to keep
upstreams attention as you aren't using a version supported upstream).

>"Anyways this is confirmed to be a regression: https://marc.info/?l
=linux-usb=154915973623396=2"

If you haven't tested a commit reversion on your hardware, then nothing
has been confirmed. Hence, have you personally tested a revert of
potential bad commit cc8b329fef53c74a4abf98b0755b3832d572d6ce and
confirmed you may then suspend consecutive times?

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

Title:
  [MacBookPro11,5] wakes up and suspends in a loop while closed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Similar bug:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507472/

  The first time suspending works great but after that suspending causes
  the laptop to wake up regardless of the method used to suspend.

  Sidenote: thanks to penalvch for explaining how to report this!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-13-generic 4.18.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  siilwyn1852 F pulseaudio
   /dev/snd/controlC1:  siilwyn1852 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 20 13:40:14 2019
  InstallationDate: Installed on 2019-01-19 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc.
   Bus 001 Device 003: ID 05ac:0274 Apple, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro11,5
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=57f2dc4c-30f7-40b6-a9db-9b6f93c214cb ro quiet splash vt.handoff=1
  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
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/18/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP114.88Z.0172.B25.1706181512
  dmi.board.name: Mac-06F11F11946D27C5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,5
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-06F11F11946D27C5
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B25.1706181512:bd06/18/2017:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro11,5
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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


[Kernel-packages] [Bug 1814749] Re: linux: 4.18.0-16.17 -proposed tracker

2019-02-11 Thread Steve Beattie
** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  linux: 4.18.0-16.17 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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 1814750 (linux-hwe), bug 1814751 (linux-hwe-edge), bug 1814752 
(linux-aws-edge), bug 1814753 (linux-azure-edge), bug 1814754 (linux-gcp-edge), 
bug 1814761 (linux-azure-edge)
  derivatives: bug 1814755 (linux-raspi2), bug 1814757 (linux-aws), bug 1814758 
(linux-azure), bug 1814759 (linux-gcp), bug 1814760 (linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Monday, 11. February 2019 11:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1814645] Re: linux: 3.13.0-166.216 -proposed tracker

2019-02-11 Thread Steve Beattie
** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  linux: 3.13.0-166.216 -proposed tracker

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

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

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

  backports: bug 1814646 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Monday, 11. February 2019 20:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1814760] Re: linux-kvm: 4.18.0-1008.8 -proposed tracker

2019-02-11 Thread Steve Beattie
** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  linux-kvm: 4.18.0-1008.8 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814749
  phase: Testing
  phase-changed: Monday, 11. February 2019 14:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1814645] Re: linux: 3.13.0-166.216 -proposed tracker

2019-02-11 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: In Progress => Incomplete

** 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 1814646 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Monday, 11. February 2019 20:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
+   automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux: 3.13.0-166.216 -proposed tracker

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

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

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

  backports: bug 1814646 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Monday, 11. February 2019 20:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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


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

2019-02-11 Thread Andy Whitcroft
** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux-azure:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow 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 stakeholder-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Invalid

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: 1814692
  phase: Holding before Packaging
  phase-changed: Tuesday, 05. February 2019 11:03 UTC
  reason:
prepare-package: Stalled -- waiting for master bug

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

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


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

2019-02-11 Thread Andy Whitcroft
** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux-gcp:  -proposed tracker

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

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

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

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


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

2019-02-11 Thread Andy Whitcroft
** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux-gcp:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow 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:
  Invalid
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  Invalid

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: 1814658
  phase: Holding before Packaging
  phase-changed: Tuesday, 05. February 2019 10:31 UTC
  reason:
prepare-package: Stalled -- waiting for master bug

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

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


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

2019-02-11 Thread Andy Whitcroft
** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux-gcp:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow 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:
  Invalid
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  Invalid

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: 1814692
  phase: Holding before Packaging
  phase-changed: Tuesday, 05. February 2019 11:03 UTC

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

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


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

2019-02-11 Thread Andy Whitcroft
** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux-kvm:  -proposed tracker

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

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

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

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


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

2019-02-11 Thread Andy Whitcroft
** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux-kvm:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Cosmic:
  Invalid

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

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

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


[Kernel-packages] [Bug 1785171] Re: Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection

2019-02-11 Thread Mikko
I would like to add that I noticed quite weird connection between this
issue and SD card reader in nuc. When the reader was disabled in bios,
the issue persists and when it's enabled, the issue does not occur. More
info here in the community thread in Intel forum:
https://forums.intel.com/s/question/0D50P4D4D6BSAV/really-weird-
problem-in-ethernet-adapter-in-nuc8i5beh-help-needed-in-debugging

I returned my nuc so this is no more important for me, but clearly there
is some bugs in device-bios-driver combo. Propably enabling sd card
reader disables some power saving feture and because of tht the bug is
not visible?

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

Title:
  Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver
  keeps Dropping Internet Connection

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

Bug description:
  I've turned up many, many new server and workstation systems over the
  years on both Linux and Windows. Never seen anything like this
  behaviour I'm witnessing on Ubuntu Server 18.04 before where I simply
  lose Internet connectivity while using a browser.  Ethernet interfaces
  usually either work or they don't work.

  I've configured the Intel I219-V Ethernet interface (wired Ethernet
  connection, there is no wifi on this system) using the e1000e driver
  for Ubuntu.  The Ethernet connection is configured to use
  NetworkManager via Netplan on Ubuntu 18.04 LTS Server version.  ASRock
  Z370m Pro4 motherboard.

  The Ethernet interface will drop the Internet connectivity when I'm
  using either the Firefox or Chrome browser.  It usually happens when
  I'm using the search features of the browser. I can't figure out what
  would cause this type of behaviour.  When the Internet connection
  drops, the only way to get back Internet connectivity is to disconnect
  the wired connection using the Ubuntu features and then re-connect
  (this restarts the NetworkManager service I notice).

  In the NetworkManager logs I do notice an "auth" error about a file or
  directory not found. I've never seen that before.

  Note:  The auth error does not coincide with the loss of Internet
  connectivity, but it does proceed it.  Often there can be many hours
  between the auth error and the actual loss of Internet connectivity.

  After I reconnect the connection (via re-starting the NetworkManager
  service) all will be fine for up to a day or so, but then I stress
  test it with a bunch of searches using the browser and usually I can
  get the Internet connectivity to drop again.  Repeat the disconnect
  and reconnect process again (aka re-start NetworkManager) and the
  Internet connectivity will be fine again.  The longest I've seen it go
  without an "Internet connectivity drop" issue is about 36 hours.

  I notice that the e1000e driver does not list the I219-V as a
  supported Ethernet interface in the Intel documentation for the Linux
  version of the driver.  I'm not sure why that is.  The I219-V is
  supposed to used another driver, but it's not clear there's a Linux
  version for of the driver for the I219-V.

  I'm really disappointed that I've run into this issue with Ubuntu
  Server LTS 18.04 on this motherboard.  I had CentOS Server 7.4 (my
  standard server OS, a great Linux distro) on this same motherboard for
  a week with no issues, so I know the motherboard and the I219-V
  Ethernet interface are 100% good hardware wise and can work properly.
  CentOS 7.4 uses NetworkManager as the default for managing the
  Ethernet interface.

  The only reason I'm using Ubuntu Server 18.04 on this motherboard is
  because of a specific package that Ubuntu has a newer packaged version
  than CentOS. CentOS is extremely stable when it comes to basic server
  functionality.

  Hopefully, this bug with the I219-V Ethernet interface using the
  e1000e drive for Linux can be verified and a fix rolled out.

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

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


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

2019-02-11 Thread Andy Whitcroft
** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux-azure:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  Invalid

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

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

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


[Kernel-packages] [Bug 1793901] Re: kernel oops in bcache module

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

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

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


** Tags added: verification-needed-trusty

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

Title:
  kernel oops in bcache module

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  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:
  SRU Justification
  =

  [Impact]

  Some users see panics like the following when performing fstrim on a
  bcached volume:

  [  529.803060] BUG: unable to handle kernel NULL pointer dereference at 
0008
  [  530.183928] #PF error: [normal kernel read fault]
  [  530.412392] PGD 801f42163067 P4D 801f42163067 PUD 1f42168067 PMD 0
  [  530.750887] Oops:  [#1] SMP PTI
  [  530.920869] CPU: 10 PID: 4167 Comm: fstrim Kdump: loaded Not tainted 
5.0.0-rc1+ #3
  [  531.290204] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, 
BIOS P89 12/27/2015
  [  531.693137] RIP: 0010:blk_queue_split+0x148/0x620
  [  531.922205] Code: 60 38 89 55 a0 45 31 db 45 31 f6 45 31 c9 31 ff 89 4d 98 
85 db 0f 84 7f 04 00 00 44 8b 6d 98 4c 89 ee 48 c1 e6 04 49 03 70 78 <8b> 46 08 
44 8b 56 0c 48
  8b 16 44 29 e0 39 d8 48 89 55 a8 0f 47 c3
  [  532.838634] RSP: 0018:b9b708df39b0 EFLAGS: 00010246
  [  533.093571] RAX:  RBX: 00046000 RCX: 

  [  533.441865] RDX: 0200 RSI:  RDI: 

  [  533.789922] RBP: b9b708df3a48 R08: 940d3b3fdd20 R09: 

  [  534.137512] R10: b9b708df3958 R11:  R12: 

  [  534.485329] R13:  R14:  R15: 
940d39212020
  [  534.833319] FS:  7efec26e3840() GS:940d1f48() 
knlGS:
  [  535.224098] CS:  0010 DS:  ES:  CR0: 80050033
  [  535.504318] CR2: 0008 CR3: 001f4e256004 CR4: 
001606e0
  [  535.851759] Call Trace:
  [  535.970308]  ? mempool_alloc_slab+0x15/0x20
  [  536.174152]  ? bch_data_insert+0x42/0xd0 [bcache]
  [  536.403399]  blk_mq_make_request+0x97/0x4f0
  [  536.607036]  generic_make_request+0x1e2/0x410
  [  536.819164]  submit_bio+0x73/0x150
  [  536.980168]  ? submit_bio+0x73/0x150
  [  537.149731]  ? bio_associate_blkg_from_css+0x3b/0x60
  [  537.391595]  ? _cond_resched+0x1a/0x50
  [  537.573774]  submit_bio_wait+0x59/0x90
  [  537.756105]  blkdev_issue_discard+0x80/0xd0
  [  537.959590]  ext4_trim_fs+0x4a9/0x9e0
  [  538.137636]  ? ext4_trim_fs+0x4a9/0x9e0
  [  538.324087]  ext4_ioctl+0xea4/0x1530
  [  538.497712]  ? _copy_to_user+0x2a/0x40
  [  538.679632]  do_vfs_ioctl+0xa6/0x600
  [  538.853127]  ? __do_sys_newfstat+0x44/0x70
  [  539.051951]  ksys_ioctl+0x6d/0x80
  [  539.212785]  __x64_sys_ioctl+0x1a/0x20
  [  539.394918]  do_syscall_64+0x5a/0x110
  [  539.568674]  entry_SYSCALL_64_after_hwframe+0x44/0xa9

  [Fix]

  Under certain conditions, the test for whether an operation should be
  written back to the underlying device was incorrect. Specifically, in
  should_writeback(), we were hitting a case where an optimisation for
  partial stripe conditions was returning true and so should_writeback()
  was returning true early. This caused the code to go down an incorrect
  path and create bios that contained NULL pointers.

  To fix this issue, make sure that should_writeback() on a discard op
  never returns true.

  
  [Test Case]

  We have observed it on some systems where both:
  1) LVM/devmapper is involved (bcache backing device is LVM volume) and
  2) writeback cache is involved (bcache cache_mode is writeback)

  Not every machine exhibits the bug. On one machine that does exhibit
  the bug, we can reliably reproduce it with:

   # echo writeback > /sys/block/bcache0/bcache/cache_mode
   # mount /dev/bcache0 /test
   # for i in {0..10}; do file="$(mktemp /test/zero.XXX)"; dd if=/dev/zero 
of="$file" bs=1M count=256; sync; rm $file; done; fstrim -v /test

  
  [Regression Potential]

  This could affect any device where bcache is used.

  In mitigation, however: the patch is simple, is limited to considering
  discard operations. The patch has been accepted 

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

2019-02-11 Thread Andy Whitcroft
** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux-oem:  -proposed tracker

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

Bug description:
  This bug 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: 1814658
  phase: Holding before Packaging
  phase-changed: Tuesday, 05. February 2019 10:02 UTC
  reason:
prepare-package: Stalled -- waiting for master bug

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

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


[Kernel-packages] [Bug 1814685] Re: linux-raspi2: -proposed tracker

2019-02-11 Thread Andy Whitcroft
** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux-raspi2:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Cosmic:
  Invalid

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

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

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


[Kernel-packages] [Bug 1815268] Re: hot add VF to net_failover - could not rename interface '8' from 'eth0' to 'ens4': Device or resource busy

2019-02-11 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch

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

Title:
  hot add VF to net_failover - could not rename interface '8' from
  'eth0' to 'ens4': Device or resource busy

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Host has a QEMU/KVM setup with standby virtio-net [1]:

  # qemu-system-x86_64 -name guest=ubuntu-xenial,debug-threads=on
  -machine pc,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off
  -smp 4,sockets=1,cores=2,threads=2 -monitor stdio -vnc :1 -boot
  order=n,menu=on -serial telnet:127.0.0.1:4567,server -netdev
  tap,fd=20,id=hostnet0,vhost=on,vhostfd=21 -device virtio-net-
  pci,netdev=hostnet0,id=net0,mac=d6:36:08:7f:b4:d9,standby=on

  Guest is loaded with Xenial Xerus (16.04.5),

  vsbalakr@ubuntu-16:~$ uname -a
  Linux ubuntu-16 4.15.0-1007-oracle #9~16.04.1-Ubuntu SMP Wed Dec 12 19:49:55 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  vsbalakr@ubuntu-16:~$ cat /proc/version_signature
  Ubuntu 4.15.0-1007.9~16.04.1-oracle 4.15.18
  vsbalakr@ubuntu-16:~$ cat /etc/os*release
  NAME="Ubuntu"
  VERSION="16.04.5 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.5 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial
  vsbalakr@ubuntu-16:~$ 

  ens3 is the master interface of net_failover, while ens3nsby is its
  standby slave [2]:

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2154sec preferred_lft 2154sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever

  Now we hot plug a Virtual Function (with MAC set to same address
  d6:36:08:7f:b4:d9 in prior) into the guest, via QEMU HMP console:

  (qemu) device_add vfio-pci,host=02:10.1,id=hostdev_vf0
  (qemu)

  VF now shows up in guest as "eth0" instead of the expected "ens4":

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 2606:b400:400:3451:61b8:3bbd:dba3:7f93/64 scope global temporary 
dynamicvalid_lft 604753sec preferred_lft 86209sec
  inet6 2606:b400:400:3451:d436:8ff:fe7f:b4d9/64 scope global mngtmpaddr 
dynamicvalid_lft 2591959sec preferred_lft 604759sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2072sec preferred_lft 2072sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  6: eth0:  mtu 1500 qdisc mq master ens3 
state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  vsbalakr@ubuntu-16:~$

  /var/log/syslog shows that renaming to "ens4" had failed because of
  "Device or resource busy",

  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.231623] ixgbevf :00:04.0: NIC 
Link is Up 10 Gbps
  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.233188] IPv6: ADDRCONF(NETDEV_UP): 
eth0: link is not ready
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: RUN 'ifupdown-hotplug' 
/lib/udev/rules.d/80-ifupdown.rules:5
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: IMPORT builtin 'path_id' 
/lib/udev/rules.d/80-net-setup-link.rules:5
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: IMPORT builtin 
'net_setup_link' 

[Kernel-packages] [Bug 1764794] Re: signing: only install a signed kernel

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

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

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


** Tags added: verification-needed-trusty

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

Title:
  signing: only install a signed kernel

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

Bug description:
  We should switch the default kernel install to the signed kernel.
  This makes it much harder to uninstall the signed kernel in
  environments which enforce the kernel to be signed.  Boot loaders
  which can understand and validate it want the signed image, those
  which do not should ignore the appended signature.

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

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


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

2019-02-11 Thread Andy Whitcroft
** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux-azure:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Cosmic:
  Invalid

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

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

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


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

2019-02-11 Thread Andy Whitcroft
** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux:  -proposed tracker

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

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 --
  phase: Packaging
  phase-changed: Tuesday, 05. February 2019 11:32 UTC
  reason:
prepare-package: Pending -- version not specified

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

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


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

2019-02-11 Thread Andy Whitcroft
** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux-azure:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow 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 stakeholder-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Invalid

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: 1814658
  phase: Holding before Packaging
  phase-changed: Tuesday, 05. February 2019 10:31 UTC
  reason:
prepare-package: Stalled -- waiting for master bug

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

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


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

2019-02-11 Thread Andy Whitcroft
** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux-aws:  -proposed tracker

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

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

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

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


[Kernel-packages] [Bug 1806380] Re: linux-buildinfo: pull out ABI information into its own package

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

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

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


** Tags added: verification-needed-trusty

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

Title:
  linux-buildinfo: pull out ABI information into its own package

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

Bug description:
  We have an increasing amount of ABI information which is currently
  exposed via the primary binary packages.  Little to none of this is
  relevant to the end-user and does not deserve to use up space on their
  system.  Also the kernel developer who needs to update this data does
  not want to downloads 10s of Megabytes of binary packages to extract
  this information.  Pull it all out and generate all data that would
  require the actual binaries at kernel build time, package all of this
  information into a new linux-buildinfo package for consumption.  This
  package is not installed by default.

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

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


[Kernel-packages] [Bug 1814733] Re: linux-azure: 4.18.0-1009.9~18.04.1 -proposed tracker

2019-02-11 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

** 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: 1814726
- phase: Packaging
- phase-changed: Wednesday, 06. February 2019 10:34 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Monday, 11. February 2019 20:09 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
-   prepare-package-signed: Pending -- package not yet uploaded
+   promote-to-proposed: Ongoing -- builds not complete

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

Title:
  linux-azure: 4.18.0-1009.9~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
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: 1814726
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 11. February 2019 20:09 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/1814733/+subscriptions

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


[Kernel-packages] [Bug 1813001] Re: test_095_kernel_symbols_missing_proc_self_stack failed on P-LTS

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

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

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


** Tags added: verification-needed-trusty

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

Title:
  test_095_kernel_symbols_missing_proc_self_stack failed on P-LTS

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  The testcase test_095_kernel_symbols_missing_proc_self_stack from
  ubuntu_qrt_kernel_security testsuite started to fail with Trusty
  kernel (3.13) after the fix for CVE-2018-17972 ("proc: restrict kernel
  stack dumps to root"), which prevents a regular user to read from
  /proc/self/stack.

  Kernel: 3.13.0-165.215~precise1
  The test failed with:
  AssertionError: cat: /proc/self/stack: Permission denied

  FAIL: test_095_kernel_symbols_missing_proc_self_stack 
(__main__.KernelSecurityTest)
  kernel addresses in /proc/self/stack are zeroed out
  --
  Traceback (most recent call last):
  File "./test-kernel-security.py", line 1364, in 
test_095_kernel_symbols_missing_proc_self_stack
  self._check_pK_files(self._095_kernel_symbols_missing_proc_self_stack, 
expected=expected)
  File "./test-kernel-security.py", line 1209, in _check_pK_files
  test_function(expected_restricted)
  File "./test-kernel-security.py", line 1320, in 
_095_kernel_symbols_missing_proc_self_stack
  expected, retry=True)
  File "./test-kernel-security.py", line 1146, in _read_twice
  self.assertEqual(rc, 0, regular)
  AssertionError: cat: /proc/self/stack: Permission denied

  The testcase checks the file permission before trying to read it, and
  for kernel 3.13 the permissions became inconsistent with what the user
  can actually do:

  $ cat /proc/self/stack
  cat: /proc/self/stack: Permission denied
  $ ls -l /proc/self/stack
  -r--r--r-- 1 ubuntu ubuntu 0 Jan 24 04:06 /proc/self/stack

  [Test Case]
  Run 'cat' and 'ls' on the file as stated above, or run the 
ubuntu_qrt_kernel_security testsuite and check for the results of the 
test_095_kernel_symbols_missing_proc_self_stack testcase.

  [Fix]
  Upstream commit 35a35046e4f9 ("procfs: make 
/proc/*/{stack,syscall,personality} 0400") applied for v3.15-rc1 fixes the 
issue.

  [Regression Potential]
  The upstream fix changes the permissions of the files 
/proc/*/{stack,syscall,personality}, so userspace which relies on reading these 
files as regular users might fail. However, this fixes a security issue and is 
already applied on our later series.

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

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


[Kernel-packages] [Bug 1815508] Re: Xorg freezes due to kernel hung task in the i915 driver

2019-02-11 Thread Shivaram Lingamneni
Following advice I saw on Stackexchange, I've been setting
`intel_iommu=igfx_off` on the kernel command line; this seems to
mitigate, but the bug still occurs.

I've submitted a redacted version of the apport-collect output, which I
hope is enough. I will tentatively mark the bug confirmed.

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

Title:
  Xorg freezes due to kernel hung task in the i915 driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This bug is present in 18.04 and is triggered by specific actions, in
  particular, paging through image galleries in Eye of Gnome. When the
  bug is triggered, Xorg freezes completely and goes into the D
  (uninterruptible sleep) state. The machine continues to respond to
  ping and ssh. When triggering a shutdown or reboot over ssh, the
  shutdown process continues normally until most userspace processes
  (including systemd-journald) have been stopped, but then hangs. The
  system can still be rebooted with the magic sysrq technique.

  Here's some dmesg output:

  [0.00] Linux version 4.15.0-45-generic (buildd@lgw01-amd64-031) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 
2019 (Ubuntu 4.15.0-45.48-generic 4.15.18)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/good--fortune--vg-root ro intel_iommu=igfx_off

  ###
  # This error happens regularly and may be irrelevant:
  ###

  [  345.680936] [ cut here ]
  [  345.680938] Failed to release pages: bind_count=1, pages_pin_count=1, 
pin_global=0
  [  345.680998] WARNING: CPU: 1 PID: 241 at 
/build/linux-uQJ2um/linux-4.15.0/drivers/gpu/drm/i915/i915_gem_userptr.c:89 
cancel_userptr+0xe8/0xf0 [i915]
  [  345.680999] Modules linked in: zfs(PO) zunicode(PO) zavl(PO) icp(PO) 
zcommon(PO) znvpair(PO) spl(O) nls_iso8859_1 xt_hl ip6t_rt intel_rapl 
x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass intel_cstate 
intel_rapl_perf eeepc_wmi asus_wmi sparse_keymap wmi_bmof nf_conntrack_ipv6 
snd_hda_codec_hdmi nf_defrag_ipv6 snd_hda_codec_realtek snd_hda_codec_generic 
xt_limit uvcvideo xt_tcpudp xt_addrtype videobuf2_vmalloc snd_hda_intel 
snd_hda_codec videobuf2_memops videobuf2_v4l2 snd_hda_core snd_usb_audio 
videobuf2_core snd_usbmidi_lib joydev snd_hwdep videodev snd_rawmidi shpchp 
snd_seq_device media snd_pcm snd_timer input_leds usblp snd soundcore mei_me 
mei acpi_pad mac_hid sch_fq_codel nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack 
ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi
  [  345.681028]  scsi_transport_iscsi coretemp ip6table_filter ip6_tables 
nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat 
nf_conntrack_ftp nf_conntrack parport_pc ppdev lp parport iptable_filter 
ip_tables x_tables autofs4 btrfs zstd_compress algif_skcipher af_alg dm_crypt 
hid_microsoft raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor hid_generic usbhid hid raid6_pq libcrc32c raid1 raid0 multipath 
linear i915 crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i2c_algo_bit 
drm_kms_helper syscopyarea sysfillrect aesni_intel mxm_wmi sysimgblt 
fb_sys_fops e1000e aes_x86_64 crypto_simd ptp glue_helper nvme cryptd drm 
pps_core ahci nvme_core libahci wmi video
  [  345.681059] CPU: 1 PID: 241 Comm: kworker/u8:5 Tainted: P   O 
4.15.0-45-generic #48-Ubuntu
  [  345.681059] Hardware name: System manufacturer System Product Name/PRIME 
B250M-C, BIOS 1402 11/16/2018
  [  345.681081] Workqueue: i915-userptr-release cancel_userptr [i915]
  [  345.681096] RIP: 0010:cancel_userptr+0xe8/0xf0 [i915]
  [  345.681097] RSP: 0018:afc441edbe60 EFLAGS: 00010282
  [  345.681098] RAX:  RBX: 8fb681b17600 RCX: 
0006
  [  345.681099] RDX: 0007 RSI: 0082 RDI: 
8fb6b6c96490
  [  345.681100] RBP: afc441edbe78 R08: 0001 R09: 
03c4
  [  345.681101] R10: e28d5018ef80 R11:  R12: 
8fb681b177a8
  [  345.681101] R13:  R14: 8fb698eba500 R15: 

  [  345.681102] FS:  () GS:8fb6b6c8() 
knlGS:
  [  345.681103] CS:  0010 DS:  ES:  CR0: 80050033
  [  345.681104] CR2: 7f18205d3857 CR3: 22e0a002 CR4: 
003606e0
  [  345.681105] Call Trace:
  [  345.681110]  process_one_work+0x1de/0x410
  [  345.68]  worker_thread+0x32/0x410
  [  345.681113]  kthread+0x121/0x140
  [  345.681115]  ? process_one_work+0x410/0x410
  [  345.681116]  ? kthread_create_worker_on_cpu+0x70/0x70
  [  345.681119]  ret_from_fork+0x35/0x40
  [  345.681120] Code: bf 46 ff ff eb c9 8b 93 c8 01 00 00 8b 8b a4 01 00 00 48 
c7 c7 40 44 7a c0 8b b3 9c 01 00 00 c6 05 b5 

[Kernel-packages] [Bug 1814645] Re: linux: 3.13.0-166.216 -proposed tracker

2019-02-11 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

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

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

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

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

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

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

** 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 1814646 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
- phase: Promote to Proposed
- phase-changed: Friday, 08. February 2019 00:05 UTC
+ bugs-spammed: true
+ phase: Testing
+ phase-changed: Monday, 11. February 2019 20:03 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   certification-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   verification-testing: Ongoing -- testing 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/1814645

Title:
  linux: 3.13.0-166.216 -proposed tracker

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

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

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

  backports: bug 1814646 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Monday, 11. February 2019 20:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

-- 
Mailing list: https://launchpad.net/~kernel-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-02-11 Thread Brad Figg
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'. If the problem still exists,
change the tag 'verification-needed-trusty' to 'verification-failed-
trusty'.

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

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


** Tags added: verification-needed-trusty

-- 
You 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 Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

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 1815508] Re: Xorg freezes due to kernel hung task in the i915 driver

2019-02-11 Thread Shivaram Lingamneni
redacted copy of apport-collect output

** Attachment added: "apport.redacted.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815508/+attachment/5237750/+files/apport.redacted.txt

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

Title:
  Xorg freezes due to kernel hung task in the i915 driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This bug is present in 18.04 and is triggered by specific actions, in
  particular, paging through image galleries in Eye of Gnome. When the
  bug is triggered, Xorg freezes completely and goes into the D
  (uninterruptible sleep) state. The machine continues to respond to
  ping and ssh. When triggering a shutdown or reboot over ssh, the
  shutdown process continues normally until most userspace processes
  (including systemd-journald) have been stopped, but then hangs. The
  system can still be rebooted with the magic sysrq technique.

  Here's some dmesg output:

  [0.00] Linux version 4.15.0-45-generic (buildd@lgw01-amd64-031) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 
2019 (Ubuntu 4.15.0-45.48-generic 4.15.18)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/good--fortune--vg-root ro intel_iommu=igfx_off

  ###
  # This error happens regularly and may be irrelevant:
  ###

  [  345.680936] [ cut here ]
  [  345.680938] Failed to release pages: bind_count=1, pages_pin_count=1, 
pin_global=0
  [  345.680998] WARNING: CPU: 1 PID: 241 at 
/build/linux-uQJ2um/linux-4.15.0/drivers/gpu/drm/i915/i915_gem_userptr.c:89 
cancel_userptr+0xe8/0xf0 [i915]
  [  345.680999] Modules linked in: zfs(PO) zunicode(PO) zavl(PO) icp(PO) 
zcommon(PO) znvpair(PO) spl(O) nls_iso8859_1 xt_hl ip6t_rt intel_rapl 
x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass intel_cstate 
intel_rapl_perf eeepc_wmi asus_wmi sparse_keymap wmi_bmof nf_conntrack_ipv6 
snd_hda_codec_hdmi nf_defrag_ipv6 snd_hda_codec_realtek snd_hda_codec_generic 
xt_limit uvcvideo xt_tcpudp xt_addrtype videobuf2_vmalloc snd_hda_intel 
snd_hda_codec videobuf2_memops videobuf2_v4l2 snd_hda_core snd_usb_audio 
videobuf2_core snd_usbmidi_lib joydev snd_hwdep videodev snd_rawmidi shpchp 
snd_seq_device media snd_pcm snd_timer input_leds usblp snd soundcore mei_me 
mei acpi_pad mac_hid sch_fq_codel nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack 
ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi
  [  345.681028]  scsi_transport_iscsi coretemp ip6table_filter ip6_tables 
nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat 
nf_conntrack_ftp nf_conntrack parport_pc ppdev lp parport iptable_filter 
ip_tables x_tables autofs4 btrfs zstd_compress algif_skcipher af_alg dm_crypt 
hid_microsoft raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor hid_generic usbhid hid raid6_pq libcrc32c raid1 raid0 multipath 
linear i915 crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i2c_algo_bit 
drm_kms_helper syscopyarea sysfillrect aesni_intel mxm_wmi sysimgblt 
fb_sys_fops e1000e aes_x86_64 crypto_simd ptp glue_helper nvme cryptd drm 
pps_core ahci nvme_core libahci wmi video
  [  345.681059] CPU: 1 PID: 241 Comm: kworker/u8:5 Tainted: P   O 
4.15.0-45-generic #48-Ubuntu
  [  345.681059] Hardware name: System manufacturer System Product Name/PRIME 
B250M-C, BIOS 1402 11/16/2018
  [  345.681081] Workqueue: i915-userptr-release cancel_userptr [i915]
  [  345.681096] RIP: 0010:cancel_userptr+0xe8/0xf0 [i915]
  [  345.681097] RSP: 0018:afc441edbe60 EFLAGS: 00010282
  [  345.681098] RAX:  RBX: 8fb681b17600 RCX: 
0006
  [  345.681099] RDX: 0007 RSI: 0082 RDI: 
8fb6b6c96490
  [  345.681100] RBP: afc441edbe78 R08: 0001 R09: 
03c4
  [  345.681101] R10: e28d5018ef80 R11:  R12: 
8fb681b177a8
  [  345.681101] R13:  R14: 8fb698eba500 R15: 

  [  345.681102] FS:  () GS:8fb6b6c8() 
knlGS:
  [  345.681103] CS:  0010 DS:  ES:  CR0: 80050033
  [  345.681104] CR2: 7f18205d3857 CR3: 22e0a002 CR4: 
003606e0
  [  345.681105] Call Trace:
  [  345.681110]  process_one_work+0x1de/0x410
  [  345.68]  worker_thread+0x32/0x410
  [  345.681113]  kthread+0x121/0x140
  [  345.681115]  ? process_one_work+0x410/0x410
  [  345.681116]  ? kthread_create_worker_on_cpu+0x70/0x70
  [  345.681119]  ret_from_fork+0x35/0x40
  [  345.681120] Code: bf 46 ff ff eb c9 8b 93 c8 01 00 00 8b 8b a4 01 00 00 48 
c7 c7 40 44 7a c0 8b b3 9c 01 00 00 c6 05 b5 56 10 00 01 e8 e8 2a fc fa <0f> 0b 
eb bc 0f 1f 40 00 0f 1f 44 00 00 55 ba 08 00 00 00 48 89 
  [  345.681144] ---[ end trace f92d63918dad1269 ]---

  ###
  # This is 

[Kernel-packages] [Bug 1815268] Re: hot add VF to net_failover - could not rename interface '8' from 'eth0' to 'ens4': Device or resource busy

2019-02-11 Thread Si-Wei Liu
Please find attached a patch (from Oracle Linux) that mitigates the race
with a tunable delay of 100ms.

** Patch added: 
"0001-net_failover-delay-taking-over-primary-device-to-acc.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815268/+attachment/5237749/+files/0001-net_failover-delay-taking-over-primary-device-to-acc.patch

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

Title:
  hot add VF to net_failover - could not rename interface '8' from
  'eth0' to 'ens4': Device or resource busy

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Host has a QEMU/KVM setup with standby virtio-net [1]:

  # qemu-system-x86_64 -name guest=ubuntu-xenial,debug-threads=on
  -machine pc,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off
  -smp 4,sockets=1,cores=2,threads=2 -monitor stdio -vnc :1 -boot
  order=n,menu=on -serial telnet:127.0.0.1:4567,server -netdev
  tap,fd=20,id=hostnet0,vhost=on,vhostfd=21 -device virtio-net-
  pci,netdev=hostnet0,id=net0,mac=d6:36:08:7f:b4:d9,standby=on

  Guest is loaded with Xenial Xerus (16.04.5),

  vsbalakr@ubuntu-16:~$ uname -a
  Linux ubuntu-16 4.15.0-1007-oracle #9~16.04.1-Ubuntu SMP Wed Dec 12 19:49:55 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  vsbalakr@ubuntu-16:~$ cat /proc/version_signature
  Ubuntu 4.15.0-1007.9~16.04.1-oracle 4.15.18
  vsbalakr@ubuntu-16:~$ cat /etc/os*release
  NAME="Ubuntu"
  VERSION="16.04.5 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.5 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial
  vsbalakr@ubuntu-16:~$ 

  ens3 is the master interface of net_failover, while ens3nsby is its
  standby slave [2]:

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2154sec preferred_lft 2154sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever

  Now we hot plug a Virtual Function (with MAC set to same address
  d6:36:08:7f:b4:d9 in prior) into the guest, via QEMU HMP console:

  (qemu) device_add vfio-pci,host=02:10.1,id=hostdev_vf0
  (qemu)

  VF now shows up in guest as "eth0" instead of the expected "ens4":

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 2606:b400:400:3451:61b8:3bbd:dba3:7f93/64 scope global temporary 
dynamicvalid_lft 604753sec preferred_lft 86209sec
  inet6 2606:b400:400:3451:d436:8ff:fe7f:b4d9/64 scope global mngtmpaddr 
dynamicvalid_lft 2591959sec preferred_lft 604759sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2072sec preferred_lft 2072sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  6: eth0:  mtu 1500 qdisc mq master ens3 
state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  vsbalakr@ubuntu-16:~$

  /var/log/syslog shows that renaming to "ens4" had failed because of
  "Device or resource busy",

  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.231623] ixgbevf :00:04.0: NIC 
Link is Up 10 Gbps
  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.233188] IPv6: ADDRCONF(NETDEV_UP): 
eth0: link 

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

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

apport-collect 1815508

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

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

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

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

** Tags added: bionic

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

Title:
  Xorg freezes due to kernel hung task in the i915 driver

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This bug is present in 18.04 and is triggered by specific actions, in
  particular, paging through image galleries in Eye of Gnome. When the
  bug is triggered, Xorg freezes completely and goes into the D
  (uninterruptible sleep) state. The machine continues to respond to
  ping and ssh. When triggering a shutdown or reboot over ssh, the
  shutdown process continues normally until most userspace processes
  (including systemd-journald) have been stopped, but then hangs. The
  system can still be rebooted with the magic sysrq technique.

  Here's some dmesg output:

  [0.00] Linux version 4.15.0-45-generic (buildd@lgw01-amd64-031) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 
2019 (Ubuntu 4.15.0-45.48-generic 4.15.18)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/good--fortune--vg-root ro intel_iommu=igfx_off

  ###
  # This error happens regularly and may be irrelevant:
  ###

  [  345.680936] [ cut here ]
  [  345.680938] Failed to release pages: bind_count=1, pages_pin_count=1, 
pin_global=0
  [  345.680998] WARNING: CPU: 1 PID: 241 at 
/build/linux-uQJ2um/linux-4.15.0/drivers/gpu/drm/i915/i915_gem_userptr.c:89 
cancel_userptr+0xe8/0xf0 [i915]
  [  345.680999] Modules linked in: zfs(PO) zunicode(PO) zavl(PO) icp(PO) 
zcommon(PO) znvpair(PO) spl(O) nls_iso8859_1 xt_hl ip6t_rt intel_rapl 
x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass intel_cstate 
intel_rapl_perf eeepc_wmi asus_wmi sparse_keymap wmi_bmof nf_conntrack_ipv6 
snd_hda_codec_hdmi nf_defrag_ipv6 snd_hda_codec_realtek snd_hda_codec_generic 
xt_limit uvcvideo xt_tcpudp xt_addrtype videobuf2_vmalloc snd_hda_intel 
snd_hda_codec videobuf2_memops videobuf2_v4l2 snd_hda_core snd_usb_audio 
videobuf2_core snd_usbmidi_lib joydev snd_hwdep videodev snd_rawmidi shpchp 
snd_seq_device media snd_pcm snd_timer input_leds usblp snd soundcore mei_me 
mei acpi_pad mac_hid sch_fq_codel nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack 
ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi
  [  345.681028]  scsi_transport_iscsi coretemp ip6table_filter ip6_tables 
nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat 
nf_conntrack_ftp nf_conntrack parport_pc ppdev lp parport iptable_filter 
ip_tables x_tables autofs4 btrfs zstd_compress algif_skcipher af_alg dm_crypt 
hid_microsoft raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor hid_generic usbhid hid raid6_pq libcrc32c raid1 raid0 multipath 
linear i915 crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i2c_algo_bit 
drm_kms_helper syscopyarea sysfillrect aesni_intel mxm_wmi sysimgblt 
fb_sys_fops e1000e aes_x86_64 crypto_simd ptp glue_helper nvme cryptd drm 
pps_core ahci nvme_core libahci wmi video
  [  345.681059] CPU: 1 PID: 241 Comm: kworker/u8:5 Tainted: P   O 
4.15.0-45-generic #48-Ubuntu
  [  345.681059] Hardware name: System manufacturer System Product Name/PRIME 
B250M-C, BIOS 1402 11/16/2018
  [  345.681081] Workqueue: i915-userptr-release cancel_userptr [i915]
  [  345.681096] RIP: 0010:cancel_userptr+0xe8/0xf0 [i915]
  [  345.681097] RSP: 0018:afc441edbe60 EFLAGS: 00010282
  [  345.681098] RAX:  RBX: 8fb681b17600 RCX: 
0006
  [  345.681099] RDX: 0007 RSI: 0082 RDI: 
8fb6b6c96490
  [  345.681100] RBP: afc441edbe78 R08: 0001 R09: 
03c4
  [  345.681101] R10: e28d5018ef80 R11:  R12: 
8fb681b177a8
  [  345.681101] R13:  R14: 8fb698eba500 R15: 

  [  345.681102] FS:  () GS:8fb6b6c8() 
knlGS:
  [  345.681103] CS:  0010 DS:  ES:  CR0: 80050033
  [  345.681104] CR2: 7f18205d3857 CR3: 22e0a002 CR4: 
003606e0
  [  345.681105] Call Trace:
  [  345.681110]  process_one_work+0x1de/0x410
  [  345.68]  worker_thread+0x32/0x410
  [  345.681113]  kthread+0x121/0x140
  [  

[Kernel-packages] [Bug 1812561] Re: [MacBookPro11, 5] wakes up and suspends in a loop while closed

2019-02-11 Thread Selwyn
What? I spend an hour going through that page, all information is in the
attachments of the post. Anyways this is confirmed to be a regression:
https://marc.info/?l=linux-usb=154915973623396=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/1812561

Title:
  [MacBookPro11,5] wakes up and suspends in a loop while closed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Similar bug:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507472/

  The first time suspending works great but after that suspending causes
  the laptop to wake up regardless of the method used to suspend.

  Sidenote: thanks to penalvch for explaining how to report this!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-13-generic 4.18.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  siilwyn1852 F pulseaudio
   /dev/snd/controlC1:  siilwyn1852 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 20 13:40:14 2019
  InstallationDate: Installed on 2019-01-19 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc.
   Bus 001 Device 003: ID 05ac:0274 Apple, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro11,5
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=57f2dc4c-30f7-40b6-a9db-9b6f93c214cb ro quiet splash vt.handoff=1
  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
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/18/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP114.88Z.0172.B25.1706181512
  dmi.board.name: Mac-06F11F11946D27C5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,5
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-06F11F11946D27C5
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B25.1706181512:bd06/18/2017:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro11,5
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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


[Kernel-packages] [Bug 1815508] [NEW] Xorg freezes due to kernel hung task in the i915 driver

2019-02-11 Thread Shivaram Lingamneni
Public bug reported:

This bug is present in 18.04 and is triggered by specific actions, in
particular, paging through image galleries in Eye of Gnome. When the bug
is triggered, Xorg freezes completely and goes into the D
(uninterruptible sleep) state. The machine continues to respond to ping
and ssh. When triggering a shutdown or reboot over ssh, the shutdown
process continues normally until most userspace processes (including
systemd-journald) have been stopped, but then hangs. The system can
still be rebooted with the magic sysrq technique.

Here's some dmesg output:

[0.00] Linux version 4.15.0-45-generic (buildd@lgw01-amd64-031) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 
2019 (Ubuntu 4.15.0-45.48-generic 4.15.18)
[0.00] Command line: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/good--fortune--vg-root ro intel_iommu=igfx_off

###
# This error happens regularly and may be irrelevant:
###

[  345.680936] [ cut here ]
[  345.680938] Failed to release pages: bind_count=1, pages_pin_count=1, 
pin_global=0
[  345.680998] WARNING: CPU: 1 PID: 241 at 
/build/linux-uQJ2um/linux-4.15.0/drivers/gpu/drm/i915/i915_gem_userptr.c:89 
cancel_userptr+0xe8/0xf0 [i915]
[  345.680999] Modules linked in: zfs(PO) zunicode(PO) zavl(PO) icp(PO) 
zcommon(PO) znvpair(PO) spl(O) nls_iso8859_1 xt_hl ip6t_rt intel_rapl 
x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass intel_cstate 
intel_rapl_perf eeepc_wmi asus_wmi sparse_keymap wmi_bmof nf_conntrack_ipv6 
snd_hda_codec_hdmi nf_defrag_ipv6 snd_hda_codec_realtek snd_hda_codec_generic 
xt_limit uvcvideo xt_tcpudp xt_addrtype videobuf2_vmalloc snd_hda_intel 
snd_hda_codec videobuf2_memops videobuf2_v4l2 snd_hda_core snd_usb_audio 
videobuf2_core snd_usbmidi_lib joydev snd_hwdep videodev snd_rawmidi shpchp 
snd_seq_device media snd_pcm snd_timer input_leds usblp snd soundcore mei_me 
mei acpi_pad mac_hid sch_fq_codel nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack 
ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi
[  345.681028]  scsi_transport_iscsi coretemp ip6table_filter ip6_tables 
nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat 
nf_conntrack_ftp nf_conntrack parport_pc ppdev lp parport iptable_filter 
ip_tables x_tables autofs4 btrfs zstd_compress algif_skcipher af_alg dm_crypt 
hid_microsoft raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor hid_generic usbhid hid raid6_pq libcrc32c raid1 raid0 multipath 
linear i915 crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i2c_algo_bit 
drm_kms_helper syscopyarea sysfillrect aesni_intel mxm_wmi sysimgblt 
fb_sys_fops e1000e aes_x86_64 crypto_simd ptp glue_helper nvme cryptd drm 
pps_core ahci nvme_core libahci wmi video
[  345.681059] CPU: 1 PID: 241 Comm: kworker/u8:5 Tainted: P   O 
4.15.0-45-generic #48-Ubuntu
[  345.681059] Hardware name: System manufacturer System Product Name/PRIME 
B250M-C, BIOS 1402 11/16/2018
[  345.681081] Workqueue: i915-userptr-release cancel_userptr [i915]
[  345.681096] RIP: 0010:cancel_userptr+0xe8/0xf0 [i915]
[  345.681097] RSP: 0018:afc441edbe60 EFLAGS: 00010282
[  345.681098] RAX:  RBX: 8fb681b17600 RCX: 0006
[  345.681099] RDX: 0007 RSI: 0082 RDI: 8fb6b6c96490
[  345.681100] RBP: afc441edbe78 R08: 0001 R09: 03c4
[  345.681101] R10: e28d5018ef80 R11:  R12: 8fb681b177a8
[  345.681101] R13:  R14: 8fb698eba500 R15: 
[  345.681102] FS:  () GS:8fb6b6c8() 
knlGS:
[  345.681103] CS:  0010 DS:  ES:  CR0: 80050033
[  345.681104] CR2: 7f18205d3857 CR3: 22e0a002 CR4: 003606e0
[  345.681105] Call Trace:
[  345.681110]  process_one_work+0x1de/0x410
[  345.68]  worker_thread+0x32/0x410
[  345.681113]  kthread+0x121/0x140
[  345.681115]  ? process_one_work+0x410/0x410
[  345.681116]  ? kthread_create_worker_on_cpu+0x70/0x70
[  345.681119]  ret_from_fork+0x35/0x40
[  345.681120] Code: bf 46 ff ff eb c9 8b 93 c8 01 00 00 8b 8b a4 01 00 00 48 
c7 c7 40 44 7a c0 8b b3 9c 01 00 00 c6 05 b5 56 10 00 01 e8 e8 2a fc fa <0f> 0b 
eb bc 0f 1f 40 00 0f 1f 44 00 00 55 ba 08 00 00 00 48 89 
[  345.681144] ---[ end trace f92d63918dad1269 ]---

###
# This is the hang. 2 minutes before this happened, X became completely 
unresponsive and
# went into the D (uninterruptible sleep) state. The machine still responded to 
ping and ssh.
###

[110684.322375] INFO: task Xorg:13866 blocked for more than 120 seconds.
[110684.322384]   Tainted: PW  O 4.15.0-45-generic #48-Ubuntu
[110684.322388] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
[110684.322393] XorgD0 13866  13865 0x0004
[110684.322399] Call Trace:
[110684.322411]  __schedule+0x291/0x8a0

[Kernel-packages] [Bug 1815501] Re: ixgbe: Kernel Oops when attempting to disable spoofchk in a non-existing VF

2019-02-11 Thread Eric Desrochers
** Also affects: linux (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

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

** Changed in: linux (Ubuntu Trusty)
 Assignee: (unassigned) => Heitor R. Alves de Siqueira (halves)

** Tags added: sts

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

Title:
  ixgbe: Kernel Oops when attempting to disable spoofchk in a non-
  existing VF

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  In Progress

Bug description:
  [Impact]
  Trusty 3.13 kernel Oops due to ixgbe driver failing to check non-existing VF

  [Description]
  In the current Trusty kernel, when the ixgbe driver tries to enable or 
disable spoofchk for a non-existing VF, it causes a kernel oops. This is due to 
a missing check in ixgbe_ndo_set_vf_spoofchk() before dereferencing the VF. 
There is an upstream commit to fix this issue (600a507ddcb99 ixgbe: check for 
vfs outside of sriov_num_vfs before dereference), but it needs to be 
cherry-picked into 3.13 for Trusty.

  Upstream commit:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=600a507ddcb99

  $ git describe --contains 600a507ddcb99
  Ubuntu-lts-3.19.0-7.7_14.04.1~1051^2~26^2

  $ rmadison linux-generic
  => linux-generic | 3.13.0.24.28   | trusty   | amd64, ...
  => linux-generic | 3.13.0.165.175 | trusty-security  | amd64, ...
  => linux-generic | 3.13.0.165.175 | trusty-updates   | amd64, ...
 linux-generic | 4.4.0.21.22| xenial   | amd64, ...
 linux-generic | 4.15.0.20.23   | bionic   | amd64, ...
 linux-generic | 4.18.0.10.11   | cosmic   | amd64, ...
 linux-generic | 4.19.0.12.13   | disco| amd64, ...

  [Fix]
  The fix is to check if the requested VF exists before dereferencing it in the 
driver. Upstream commit 600a507ddcb99 introduced this check, and it's a clean 
cherry pick into the latest Trusty kernel.

  [Test Case]
  1) Deploy a Trusty system with an ixgbe adapter and latest kernel from 
-updates:
  # lsb_release  -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.04.5 LTS
  Release:14.04
  Codename:   trusty
  # uname -r
  3.13.0-165-generic
  # lspci -v -s 04:00.0
  04:00.0 Ethernet controller: Intel Corporation Ethernet Controller 10-Gigabit 
X540-AT2 (rev 01)
  Subsystem: Hewlett-Packard Company 561FLR-T 2-port 10Gb Ethernet 
Adapter
  Flags: bus master, fast devsel, latency 0, IRQ 16
  Memory at 92e0 (32-bit, prefetchable) [size=2M]
  Memory at 93004000 (32-bit, prefetchable) [size=16K]
  [virtual] Expansion ROM at 9308 [disabled] [size=512K]
  Capabilities: [40] Power Management version 3
  Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
  Capabilities: [70] MSI-X: Enable+ Count=64 Masked-
  Capabilities: [a0] Express Endpoint, MSI 00
  Capabilities: [e0] Vital Product Data
  Capabilities: [100] Advanced Error Reporting
  Capabilities: [150] Alternative Routing-ID Interpretation (ARI)
  Capabilities: [160] Single Root I/O Virtualization (SR-IOV)
  Capabilities: [1d0] Access Control Services
  Kernel driver in use: ixgbe

  2) Attempt to disable spoofchk with VF -1:
  # ip link set dev eth4 vf -1 spoofchk off
  Killed
  # dmesg
  [  241.066440] BUG: unable to handle kernel paging request at fffa
  [  241.066880] IP: [] ixgbe_ndo_set_vf_spoofchk+0x3c/0xc0 
[ixgbe]
  [  241.067331] PGD 2c13067 PUD 2c15067 PMD 0
  [  241.067591] Oops: 0002 [#1] SMP
  [  241.067793] Modules linked in: ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad 
ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi dm_crypt 
gpio_ich x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm hpilo 
lpc_ich ioatdma ipmi_si shpchp acpi_power_meter mac_hid nls_iso8859_1 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw 
gf128mul glue_helper ablk_helper cryptd ixgbe tg3 dca ptp pps_core hpsa nvme 
mdio wmi
  [  241.070462] CPU: 43 PID: 2214 Comm: ip Not tainted 3.13.0-165-generic 
#215-Ubuntu
  [  241.070908] Hardware name: HP ProLiant DL360 Gen9, BIOS P89 05/06/2015
  [  241.071302] task: 880035c4c800 ti: 8810275c8000 task.ti: 
8810275c8000
  [  241.071751] RIP: 0010:[]  [] 
ixgbe_ndo_set_vf_spoofchk+0x3c/0xc0 [ixgbe]
  [  241.072349] RSP: 0018:8810275c9858  EFLAGS: 00010283
  [  241.072663] RAX:  RBX: 88102236 RCX: 

  [  241.073090] RDX:  RSI: 81fc RDI: 
88102236
  [  241.073522] RBP: 8810275c9858 R08: fffb R09: 
ffa8
  [  241.073953] R10: 

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

2019-02-11 Thread Andy Whitcroft
** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux-gcp:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow 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:
  Invalid
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  Invalid

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

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

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


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

2019-02-11 Thread Andy Whitcroft
** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux-aws:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow 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:
  Invalid
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  Invalid

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: 1814692
  phase: Holding before Packaging
  phase-changed: Tuesday, 05. February 2019 11:00 UTC
  reason:
prepare-package: Stalled -- waiting for master bug

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

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


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

2019-02-11 Thread Andy Whitcroft
** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux-azure:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow 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 stakeholder-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Invalid

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

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

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


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

2019-02-11 Thread Andy Whitcroft
** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux-kvm:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Cosmic:
  Invalid

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

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

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


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

2019-02-11 Thread Andy Whitcroft
** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux-azure:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow 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 stakeholder-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Invalid

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: 1814658
  phase: Holding before Packaging
  phase-changed: Tuesday, 05. February 2019 10:36 UTC
  reason:
prepare-package: Stalled -- waiting for master bug

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

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


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

2019-02-11 Thread Andy Whitcroft
** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux-kvm:  -proposed tracker

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

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: 1814658
  phase: Holding before Packaging
  phase-changed: Tuesday, 05. February 2019 10:32 UTC
  reason:
prepare-package: Stalled -- waiting for master bug

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

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


[Kernel-packages] [Bug 1814693] Re: linux-raspi2: -proposed tracker

2019-02-11 Thread Andy Whitcroft
** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux-raspi2:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow snap-certification-testing series:
  Invalid
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:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Bionic:
  Invalid

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: 1814692
  phase: Holding before Packaging
  phase-changed: Tuesday, 05. February 2019 11:03 UTC
  reason:
prepare-package: Stalled -- waiting for master bug

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

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


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

2019-02-11 Thread Andy Whitcroft
** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux:  -proposed tracker

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

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 --
  phase: Packaging
  phase-changed: Tuesday, 05. February 2019 10:33 UTC
  reason:
prepare-package: Pending -- version not specified

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

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


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

2019-02-11 Thread Andy Whitcroft
** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux-azure:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  Invalid

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: 1814658
  phase: Holding before Packaging
  phase-changed: Tuesday, 05. February 2019 10:31 UTC
  reason:
prepare-package: Stalled -- waiting for master bug

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

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


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

2019-02-11 Thread Andy Whitcroft
** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow snap-certification-testing series:
  Invalid
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:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

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 --
  phase: Packaging
  phase-changed: Tuesday, 05. February 2019 11:03 UTC
  reason:
prepare-package: Pending -- version not specified

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

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


[Kernel-packages] [Bug 1814660] Re: linux-raspi2: -proposed tracker

2019-02-11 Thread Andy Whitcroft
** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux-raspi2:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow snap-certification-testing series:
  Invalid
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:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Bionic:
  Invalid

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: 1814658
  phase: Holding before Packaging
  phase-changed: Tuesday, 05. February 2019 10:03 UTC
  reason:
prepare-package: Stalled -- waiting for master bug

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

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


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

2019-02-11 Thread Andy Whitcroft
** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux-gcp:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow 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:
  Invalid
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  Invalid

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: 1814658
  phase: Holding before Packaging
  phase-changed: Tuesday, 05. February 2019 10:33 UTC
  reason:
prepare-package: Stalled -- waiting for master bug

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

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


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

2019-02-11 Thread Andy Whitcroft
** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux-aws:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow 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:
  Invalid
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  Invalid

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: 1814658
  phase: Holding before Packaging
  phase-changed: Tuesday, 05. February 2019 10:00 UTC
  reason:
prepare-package: Stalled -- waiting for master bug

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

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


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

2019-02-11 Thread Andy Whitcroft
** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux-oem:  -proposed tracker

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

Bug description:
  This bug 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: 1814692
  phase: Holding before Packaging
  phase-changed: Tuesday, 05. February 2019 11:04 UTC

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

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


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

2019-02-11 Thread Andy Whitcroft
** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux-aws:  -proposed tracker

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

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

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

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


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

2019-02-11 Thread Andy Whitcroft
** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux-azure:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Cosmic:
  Invalid

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

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

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


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

2019-02-11 Thread Andy Whitcroft
** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux-gcp:  -proposed tracker

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

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

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

-- 
Mailing list: https://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   >