[Kernel-packages] [Bug 1752026] Re: Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default machine type(pseries-bionic) complaining "KVM implementation does not support Transactional Memo

[ChristianEhrhardt]

Fix pushed to bionic proposed, I'll track migration after it built and
some time for the tests have passed.

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

Title:
  Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default
  machine type(pseries-bionic) complaining "KVM implementation does not
  support Transactional Memory, try cap-htm=off" (kvm)

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  In Progress

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2018-02-23 
08:31:06 ==
  ---Problem Description---
  libvirt unable to start a KVM guest complaining about cap-htm machine 
property to be off

  Host Env:
  # lscpu
  Architecture:ppc64le
  Byte Order:  Little Endian
  CPU(s):  160
  On-line CPU(s) list: 0-159
  Thread(s) per core:  4
  Core(s) per socket:  20
  Socket(s):   2
  NUMA node(s):2
  Model:   2.2 (pvr 004e 1202)
  Model name:  POWER9 (raw), altivec supported
  CPU max MHz: 3800.
  CPU min MHz: 2166.
  L1d cache:   32K
  L1i cache:   32K
  L2 cache:512K
  L3 cache:10240K
  NUMA node0 CPU(s):   0-79
  NUMA node8 CPU(s):   80-159

  ii  qemu-kvm  1:2.11+dfsg-1ubuntu2
  ppc64el  QEMU Full virtualization on x86 hardware

  ii  libvirt-bin   4.0.0-1ubuntu3
  ppc64el  programs for the libvirt library

  # lsmcode
  Version of System Firmware : 
   Product Name  : OpenPOWER Firmware
   Product Version   : open-power-SUPERMICRO-P9DSU-V1.03-20180205-imp
   Product Extra :  occ-577915f
   Product Extra :  skiboot-v5.9-240-g081882690163-pcbedce4
   Product Extra :  petitboot-v1.6.6-p019c87e
   Product Extra :  sbe-095e608
   Product Extra :  machine-xml-fb5f933
   Product Extra :  hostboot-9bfb201
   Product Extra :  linux-4.14.13-openpower1-p78d7eee

  
   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  4.15.0-10-generic
   
  Machine Type = power9 boston 2.2 (pvr 004e 1202) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Boot a guest from libvirt with default pseries machine type or 
pseries-bionic

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

  Starting install...
  ERRORinternal error: process exited while connecting to monitor: 
,id=scsi0-0-0-0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=26 
-device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:77:78:79,bus=pci.0,addr=0x1 
-chardev pty,id=charserial0 -device 
spapr-vty,chardev=charserial0,id=serial0,reg=0x3000 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on
  2018-02-23T14:21:11.081809Z qemu-system-ppc64: KVM implementation does not 
support Transactional Memory, try cap-htm=off
  Domain installation does not appear to have been successful.
  If it was, you can restart your domain by running:
virsh --connect qemu:///system start virt-tests-vm1
  otherwise, please restart your installation.

  2. Fails to boot..

  Note: if we specify machine type as pseries=2.12 it boots fine like
  below

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries-2.12 --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

  qemu-cmd line:

  libvirt+   4283  1 99 09:26 ?00:00:38 qemu-system-ppc64
  -enable-kvm -name guest=virt-tests-vm1,debug-threads=on -S -object
  secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-4
  -virt-tests-vm1/master-key.aes -machine 

[Kernel-packages] [Bug 1752026] Re: Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default machine type(pseries-bionic) complaining "KVM implementation does not support Transactional Memo

[ChristianEhrhardt]

BTW - tests on P8 are already good on my side, and since the request
from IBM came fro P9 I have to assume it will be good there. But e.g.
cross release migration X->B and such I had tested explicitly to be
sure.

That said, please be aware that this will be a remaining "itch" for you at the 
current solution.
If somebody had guests on pre-Xenial it will have HTM enabled by default.
If those users migrate to a P9 system on Bionic they will still carry the 
feature of HTM being enabled and run into the issue, but there is nothing we 
can do about it other than getting your kernel fix completed and integrated. 
But I thought I make you aware to be 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/1752026

Title:
  Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default
  machine type(pseries-bionic) complaining "KVM implementation does not
  support Transactional Memory, try cap-htm=off" (kvm)

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  In Progress

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2018-02-23 
08:31:06 ==
  ---Problem Description---
  libvirt unable to start a KVM guest complaining about cap-htm machine 
property to be off

  Host Env:
  # lscpu
  Architecture:ppc64le
  Byte Order:  Little Endian
  CPU(s):  160
  On-line CPU(s) list: 0-159
  Thread(s) per core:  4
  Core(s) per socket:  20
  Socket(s):   2
  NUMA node(s):2
  Model:   2.2 (pvr 004e 1202)
  Model name:  POWER9 (raw), altivec supported
  CPU max MHz: 3800.
  CPU min MHz: 2166.
  L1d cache:   32K
  L1i cache:   32K
  L2 cache:512K
  L3 cache:10240K
  NUMA node0 CPU(s):   0-79
  NUMA node8 CPU(s):   80-159

  ii  qemu-kvm  1:2.11+dfsg-1ubuntu2
  ppc64el  QEMU Full virtualization on x86 hardware

  ii  libvirt-bin   4.0.0-1ubuntu3
  ppc64el  programs for the libvirt library

  # lsmcode
  Version of System Firmware : 
   Product Name  : OpenPOWER Firmware
   Product Version   : open-power-SUPERMICRO-P9DSU-V1.03-20180205-imp
   Product Extra :  occ-577915f
   Product Extra :  skiboot-v5.9-240-g081882690163-pcbedce4
   Product Extra :  petitboot-v1.6.6-p019c87e
   Product Extra :  sbe-095e608
   Product Extra :  machine-xml-fb5f933
   Product Extra :  hostboot-9bfb201
   Product Extra :  linux-4.14.13-openpower1-p78d7eee

  
   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  4.15.0-10-generic
   
  Machine Type = power9 boston 2.2 (pvr 004e 1202) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Boot a guest from libvirt with default pseries machine type or 
pseries-bionic

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

  Starting install...
  ERRORinternal error: process exited while connecting to monitor: 
,id=scsi0-0-0-0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=26 
-device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:77:78:79,bus=pci.0,addr=0x1 
-chardev pty,id=charserial0 -device 
spapr-vty,chardev=charserial0,id=serial0,reg=0x3000 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on
  2018-02-23T14:21:11.081809Z qemu-system-ppc64: KVM implementation does not 
support Transactional Memory, try cap-htm=off
  Domain installation does not appear to have been successful.
  If it was, you can restart your domain by running:
virsh --connect qemu:///system start virt-tests-vm1
  otherwise, please restart your installation.

  2. Fails to boot..

  Note: if we specify machine type as pseries=2.12 it boots fine like
  below

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries-2.12 --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 

[Kernel-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) by an insufficient compiler!

[lithorus]

I had the same problem with zfs too.

Changed :
CONFIG_RETPOLINE=y
to
CONFIG_RETPOLINE=n
in 
/boot/config-4.4.0-116-generic

and reinstalled the nvidia/zfs kernel modules.

To me it seems that the config file shipped with the kernel is not
matching the version used for compiling.

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

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04) by an insufficient compiler!

Status in gcc:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  The root cause of the problem has been found to be installing the -116
  kernel without a sufficiently updated version of gcc.  In my case, my
  system received the gcc update AFTER the kernel update.

  Uninstalling the -116 kernel and reinstalling it with the updated
  version of gcc solved the problem for me.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

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

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

[Kernel-packages] [Bug 1752061] Re: nfp: prioritize stats updates

[Imran Khakoo]

Hi, Joseph, I'm hitting a 404 on your link. Please assist with a new
link.

Imran Khakoo

Netronome

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

Title:
  nfp: prioritize stats updates

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

Bug description:
  This is a backport request from Netronome for Ubuntu 18.04 LTS.

  Description: Previously it was possible to interrupt processing stats updates 
because they were handled in a work queue. Interrupting the stats updates could 
lead to a situation where we backup the control message queue. This patch
  moves the stats update processing out of the work queue to be processed as 
soon as hardware sends a request.

  The following fix for the above has been accepted into upstream for
  v4.16. This ticket requests backporting it to Ubuntu 18.04 LTS.

  01c15e93a78c ("nfp: flower: prioritize stats updates")

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

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

[Kernel-packages] [Bug 1645540] Re: [Feature] Crystal Ridge 2LM error reporting

[Alice Liu]

** Description changed:

  In 2LM configurations we need to error reports to differentiate between
  errors in the "near" memory (DRAM used as cache) and "far" memory
  (Crystal ridge memory)
  
  HW: Apache Pass
  
  Upstream schedule:
- kernel: 4.15
+ kernel: 4.17
  
  Target Release: 18.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/1645540

Title:
  [Feature] Crystal Ridge 2LM error reporting

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Artful:
  Invalid
Status in linux source package in Bionic:
  Fix Released

Bug description:
  In 2LM configurations we need to error reports to differentiate
  between errors in the "near" memory (DRAM used as cache) and "far"
  memory (Crystal ridge memory)

  HW: Apache Pass

  Upstream schedule:
  kernel: 4.17

  Target Release: 18.04

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

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

[Kernel-packages] [Bug 1577140] Re: Wifi Ralink R3290 disabled by default in ubuntu 16.04

[Shankey]

I don't have an perfect idea about that..But yes, as per my experience
may be there is something wrong from v4.0 kernels because this problem
started from the initial release of ubuntu 16.04 which came along with
the kernel v4.2...The problem was ralink wifi "disabled by
default"..when you go on to settings you find that airplaine mode is
enabled by default and you cant disable it. Even when you compile
another driver for this WIFI card somehow it shows up but still its
useless because it doesn’t detect the wifi connections nearbybecause
its blocked.

Something is messing up with Ralink or there is some bug in kernel
itself which preventing this wifi from activating.

This problem is still present in Ubuntu and its derivatives which are
based from 16.04 to the present builds. #1745636 problem is same. the
wifi key doesn't unlocks the wifi nor even Rfkill command. I have been
filling this bug from last 2 year but still the problem exists.

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

Title:
  Wifi Ralink R3290 disabled by default in ubuntu 16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have my personal laptop and it contains PCI Ralink r3290 wifi
  adaptor with bluetooth and when i have installed the fresh version of
  Ubuntu 16.04x64 it doesn’t work at all on boot up. The wifi is
  disabled by default and the it doesn’t activates even by pressing the
  key and when i go the network settings airplane mode is also enabled
  and when i try to disable airplane mode it switches back on. I dont
  know whats going wrong. Earlier my wifi works on ubuntu 15.04. I have
  tried almost every solution and none works in the latest LTS release.

  Please help I am unable to use internet in ubuntu

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: 
boot/vmlinuz-4.4.0-21-generic]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shankey1536 F pulseaudio
   /dev/snd/controlC1:  shankey1536 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun May  1 17:02:12 2016
  HibernationDevice: RESUME=UUID=9fdda691-a6ae-4494-99e3-b76fde1f33a6
  InstallationDate: Installed on 2016-04-24 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 001 Device 003: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd 
(Foxlink) Webcam
   Bus 001 Device 002: ID 8087:8000 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard Compaq 15 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=609ae58a-a43f-4f7b-9a61-e21d3caf457a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.39
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2211
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 86.52
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.39:bd05/26/2015:svnHewlett-Packard:pnCompaq15NotebookPC:pvr0991100600087:rvnHewlett-Packard:rn2211:rvr86.52:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: Compaq 15 Notebook PC
  dmi.product.version: 0991100600087
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1751838] Re: linux: 3.13.0-143.192 -proposed tracker

[Po-Hsu Lin]

3.13.0-143.192 - generic
Regression test CMPL.

Issue to note in amd64:
  ubuntu_kvm_smoke_test - uvt-kvm wait issue, bug 1732883
  ubuntu_kvm_unit_tests - 40 failed on amaura, 39 failed on pepe
  ubuntu_qrt_apparmor - failed on KVM instance, deb-src not enabled, not a bug 

Issue to note in arm64:
  hwclock - issue for HP m400 (bug 1716603)
  libhugetlbfs - noresv-preserve-resv-page failed (bug 1747823), 
chunk-overcommit failed (bug 1747828), shmoverride_linked timed out (bug 
1739560)
  ubuntu_cts_kernel - lp1262692 failed, bug for iproute2 (bug 1715376)
  ubuntu_kvm_smoke_test - uvt-kvm wait issue (bug 1732883)
  ubuntu_qrt_apparmor - test_old_trusty_regression_testsuite failed to build 
(bug 1699987)
  ubuntu_qrt_kernel_security - test 072 (bug 1747852) test 82 (bug 1747853) 
test 140 (bug 1747855) test 050 (bug 1684776) test 060 should be skipped (bug 
1712038) test 072 (bug 1747850) test 075 (bug 1712007) test 021, 022 (bug 
1747847)

Issue to note in i386:
  ubuntu_kvm_smoke_test - uvt-kvm wait issue, bug 1732883
  ubuntu_kvm_unit_tests - 15 failed on pepe (vmexit*, msr, realmode, syscall, 
tsc, hyperv_clock)

Issue to note in ppc64le:
  ubuntu_cts_kernel - lp1262692 failed, bug for iproute2, bug 1715376
  ubuntu_kvm_smoke_test - no supported architecture for 'hvm', bug 1752550
  ubuntu_zram_smoke_test - zram module not found on ppc64le, bug 1752551


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

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

** Tags added: regression-testing-passed

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

Title:
  linux: 3.13.0-143.192 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-ports-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa 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 1751839 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1745081] Re: Add support for Realtek WiFi device [10ec:b822]

[Hui Wang]

@Erik,

this driver is not in the upstream kernel yet, so it isn't in the artful
kernel (4.13.0-36-generic) yet as well.

this driver is going to be merged to ubuntu linux-oem kernel, So please
wait for linux-image-4.13.0-1023-oem or later version kernel.

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

Title:
   Add support for Realtek WiFi device [10ec:b822]

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Triaged

Bug description:
  05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 
[10ec:b822]
Subsystem: Lenovo Device [17aa:b023]
Flags: fast devsel, IRQ 255
I/O ports at c000 [disabled] [size=256]
Memory at f200 (64-bit, non-prefetchable) [disabled] [size=64K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [148] Device Serial Number 00-e0-4c-ff-fe-b8-22-01
Capabilities: [158] Latency Tolerance Reporting
Capabilities: [160] L1 PM Substates

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

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

[Kernel-packages] [Bug 1753705] Re: stress-ng will make an Ubuntu on LPAR s390x Bionic system become very slow

[Po-Hsu Lin]

SSH key imported, please find the information in your mailbox.
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/1753705

Title:
  stress-ng will make an Ubuntu on LPAR s390x Bionic system become very
  slow

Status in linux package in Ubuntu:
  In Progress

Bug description:
  On an Ubuntu on LPAR s390x node, s2lp4, boot with Bionic kernel.

  When trying to run the ubuntu_stress_smoke test on it. This test will cause 
error like:
    
/home/ubuntu/autotest/client/tests/ubuntu_stress_smoke_test/ubuntu_stress_smoke_test.sh:
 fork: retry: Resource temporarily unavailable

  Not sure which test is the cause, but the system will become very slow
  after running this test suite. And it seems that the test suite will
  terminates itself before walking through all the test cases.

  1st run: terminates after the epoll test
  2nd run: crashed and rebooted after the branch test
  3rd run: terminates after the eventfd test
  4th run: terminates after the enosys test

  Command to run the test:
    AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/ubuntu_stress_smoke_test/control

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-11-generic 4.15.0-11.12
  ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
  Uname: Linux 4.15.0-11-generic s390x
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:

  Date: Tue Mar  6 09:31:39 2018
  HibernationDevice: RESUME=UUID=e2735dd1-cbbc-4424-9c25-d37d073d9414
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:

  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=38f7d570-2973-4055-b668-12a9ace1e0c7 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-11-generic N/A
   linux-backports-modules-4.15.0-11-generic  N/A
   linux-firmware 1.172
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 362075] Re: session logout after suspend

[Simon]

Hey Christopher, I've created a new version of this bug for 16.04

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1753884

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

Title:
  session logout after suspend

Status in linux package in Ubuntu:
  Invalid

Bug description:
  In Kubuntu 9.04 Jaunty, my laptop lid down is set to suspend via
  guidance-power-manager. After I lid up, I am at the login screen,
  instead of the unlock screen dialog.

  WORKAROUND: Disable the "Lock screen on resume" option in the power
  management settings.

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

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

[Kernel-packages] [Bug 1729010] Re: USB hub stops working after suspend(s?)

[Joe Barnett]

I can, but can't promise an SLA ;)

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

Title:
  USB hub stops working after suspend(s?)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On initial boot, my usb hub works fine, but after a (series of?)
  suspends, I stop being able to see devices that are plugged into it.
  journalctl output on plugging it in:

  Oct 31 07:08:36 spiny kernel: usb 1-1: new high-speed USB device number 21 
using xhci_hcd
  Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device found, idVendor=0409, 
idProduct=005a
  Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device strings: Mfr=0, 
Product=0, SerialNumber=0
  Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: USB hub found
  Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: 4 ports detected
  Oct 31 07:08:36 spiny kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= 
SRC=fe80::::a299:9bff:fe17:9047 
DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 
FLOWLBL=32325 PROTO=UDP SPT=8612 DPT=8612 LEN=24 
  Oct 31 07:08:36 spiny kernel: usb 1-1.1: new high-speed USB device number 22 
using xhci_hcd
  Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device found, idVendor=0b95, 
idProduct=772a
  Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device strings: Mfr=1, 
Product=2, SerialNumber=3
  Oct 31 07:08:36 spiny kernel: usb 1-1.1: Product: AX88x72A
  Oct 31 07:08:36 spiny kernel: usb 1-1.1: Manufacturer: ASIX Elec. Corp.
  Oct 31 07:08:36 spiny kernel: usb 1-1.1: SerialNumber: 47EDE2
  Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 eth0: register 'asix' at 
usb-:00:14.0-1.1, ASIX AX88772 USB 2.0 Ethernet, 00:50:b6:47:ed:e2
  Oct 31 07:08:37 spiny NetworkManager[11575]:   [1509458917.0438] 
manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/7)
  Oct 31 07:08:37 spiny mtp-probe[13207]: checking bus 1, device 22: 
"/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1"
  Oct 31 07:08:37 spiny mtp-probe[13207]: bus: 1, device: 22 was not an MTP 
device
  Oct 31 07:08:37 spiny systemd-udevd[13206]: link_config: autonegotiation is 
unset or enabled, the speed and duplex are not writable.
  Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 enx0050b647ede2: renamed from 
eth0
  Oct 31 07:08:37 spiny pkexec[13215]: pam_unix(polkit-1:session): session 
opened for user root by (uid=1000)
  Oct 31 07:08:37 spiny pkexec[13215]: jbarnett: Executing command [USER=root] 
[TTY=unknown] [CWD=/home/jbarnett] 
[COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 
31]
  Oct 31 07:08:37 spiny pkexec[13214]: gdm: Error executing command as another 
user: Not authorized [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] 
[COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 
48]
  Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: Error 
executing command as another user: Not authorized
  Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: This 
incident has been reported.
  Oct 31 07:08:37 spiny systemd-networkd[1119]: eth0: Renamed to enx0050b647ede2
  Oct 31 07:08:37 spiny NetworkManager[11575]:   [1509458917.1066] device 
(eth0): interface index 10 renamed iface from 'eth0' to 'enx0050b647ede2'
  Oct 31 07:08:37 spiny NetworkManager[11575]:   [1509458917.1214] 
devices added (path: 
/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2,
 iface: enx0050b647ede2)
  Oct 31 07:08:37 spiny NetworkManager[11575]:   [1509458917.1214] device 
added (path: 
/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2,
 iface: enx0050b647ede2): no ifupdown configuration found.
  Oct 31 07:08:37 spiny NetworkManager[11575]:   [1509458917.1217] device 
(enx0050b647ede2): state change: unmanaged -> unavailable (reason 'managed', 
internal state 'external')
  Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: 
link is not ready
  Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: 
link is not ready
  Oct 31 07:08:37 spiny NetworkManager[11575]:   [1509458917.1274] 
keyfile: add connection in-memory (9365f42f-9dd9-3bdc-bbad-e7062efcaf7c,"Wired 
connection 4")
  Oct 31 07:08:37 spiny NetworkManager[11575]:   [1509458917.1284] 
settings: (enx0050b647ede2): created default wired connection 'Wired connection 
4'
  Oct 31 07:08:37 spiny systemd[1]: Starting 
systemd-resolved-update-resolvconf.service...
  Oct 31 07:08:37 spiny systemd[1]: Started 
systemd-resolved-update-resolvconf.service.
  Oct 31 07:08:37 spiny kernel: usb 1-1.2: new full-speed USB device number 23 
using xhci_hcd
  Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device found, idVendor=0d8c, 
idProduct=0105
  Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device strings: Mfr=3, 
Product=1, SerialNumber=0
  Oct 31 07:08:37 spiny kernel: usb 1-1.2: Product: USB Multimedia 

[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions

[Nobuto Murata]

I run an overnight test with v4.12 just to make sure it really fixed the
issue. It happened sometimes, but way less frequencies. We may need to
test it longer for "good" cases since the patch may not be only one.
Anyway, the current status is:

v4.12-rc1 with i40e 2.1.14 - bad (3 out of 3)
v4.12 with i40e 2.1.14 - relatively good (5 out of 68)

The next test would be with v4.12-rc4.

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

Title:
  [i40e] LACP bonding start up race conditions

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

Bug description:
  When provisioning Ubuntu servers with MAAS at once, some bonding pairs
  will have unexpected LACP status such as "Expired". It randomly
  happens at each provisioning with the default xenial kernel(4.4), but
  not reproducible with HWE kernel(4.13). I'm using Intel X710 cards
  (Dell-branded).

  Using the HWE kernel works as a workaround for short term, but it's
  not ideal since 4.13 is not covered by Canonical Livepatch service.

  How to reproduce:
  1. configure LACP bonding with MAAS
  2. provision machines
  3. check the bonding status in /proc/net/bonding/bond*

  frequency of occurrence:
  About 5 bond pairs in 22 pairs at each provisioning.

  [reproducible combination]
  $ uname -a
  Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 1.4.25-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  [non-reproducible combination]
  $ uname -a
  Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 2.1.14-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-116-generic 4.4.0-116.140
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  6 06:37 seq
   crw-rw 1 root audio 116, 33 Mar  6 06:37 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Mar  6 06:46:32 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R730
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed 
root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 
console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-116-generic N/A
   linux-backports-modules-4.4.0-116-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/16/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.5
  dmi.board.name: 072T6D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.asset.tag: 0018880
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R730
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1729010] Re: USB hub stops working after suspend(s?)

[Kai-Heng Feng]

Great. We should still backport fixes to Artful though. It might be time 
consuming to install and test multiple kernels.
Are you up to the task? ;)

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

Title:
  USB hub stops working after suspend(s?)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On initial boot, my usb hub works fine, but after a (series of?)
  suspends, I stop being able to see devices that are plugged into it.
  journalctl output on plugging it in:

  Oct 31 07:08:36 spiny kernel: usb 1-1: new high-speed USB device number 21 
using xhci_hcd
  Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device found, idVendor=0409, 
idProduct=005a
  Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device strings: Mfr=0, 
Product=0, SerialNumber=0
  Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: USB hub found
  Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: 4 ports detected
  Oct 31 07:08:36 spiny kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= 
SRC=fe80::::a299:9bff:fe17:9047 
DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 
FLOWLBL=32325 PROTO=UDP SPT=8612 DPT=8612 LEN=24 
  Oct 31 07:08:36 spiny kernel: usb 1-1.1: new high-speed USB device number 22 
using xhci_hcd
  Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device found, idVendor=0b95, 
idProduct=772a
  Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device strings: Mfr=1, 
Product=2, SerialNumber=3
  Oct 31 07:08:36 spiny kernel: usb 1-1.1: Product: AX88x72A
  Oct 31 07:08:36 spiny kernel: usb 1-1.1: Manufacturer: ASIX Elec. Corp.
  Oct 31 07:08:36 spiny kernel: usb 1-1.1: SerialNumber: 47EDE2
  Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 eth0: register 'asix' at 
usb-:00:14.0-1.1, ASIX AX88772 USB 2.0 Ethernet, 00:50:b6:47:ed:e2
  Oct 31 07:08:37 spiny NetworkManager[11575]:   [1509458917.0438] 
manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/7)
  Oct 31 07:08:37 spiny mtp-probe[13207]: checking bus 1, device 22: 
"/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1"
  Oct 31 07:08:37 spiny mtp-probe[13207]: bus: 1, device: 22 was not an MTP 
device
  Oct 31 07:08:37 spiny systemd-udevd[13206]: link_config: autonegotiation is 
unset or enabled, the speed and duplex are not writable.
  Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 enx0050b647ede2: renamed from 
eth0
  Oct 31 07:08:37 spiny pkexec[13215]: pam_unix(polkit-1:session): session 
opened for user root by (uid=1000)
  Oct 31 07:08:37 spiny pkexec[13215]: jbarnett: Executing command [USER=root] 
[TTY=unknown] [CWD=/home/jbarnett] 
[COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 
31]
  Oct 31 07:08:37 spiny pkexec[13214]: gdm: Error executing command as another 
user: Not authorized [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] 
[COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 
48]
  Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: Error 
executing command as another user: Not authorized
  Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: This 
incident has been reported.
  Oct 31 07:08:37 spiny systemd-networkd[1119]: eth0: Renamed to enx0050b647ede2
  Oct 31 07:08:37 spiny NetworkManager[11575]:   [1509458917.1066] device 
(eth0): interface index 10 renamed iface from 'eth0' to 'enx0050b647ede2'
  Oct 31 07:08:37 spiny NetworkManager[11575]:   [1509458917.1214] 
devices added (path: 
/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2,
 iface: enx0050b647ede2)
  Oct 31 07:08:37 spiny NetworkManager[11575]:   [1509458917.1214] device 
added (path: 
/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2,
 iface: enx0050b647ede2): no ifupdown configuration found.
  Oct 31 07:08:37 spiny NetworkManager[11575]:   [1509458917.1217] device 
(enx0050b647ede2): state change: unmanaged -> unavailable (reason 'managed', 
internal state 'external')
  Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: 
link is not ready
  Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: 
link is not ready
  Oct 31 07:08:37 spiny NetworkManager[11575]:   [1509458917.1274] 
keyfile: add connection in-memory (9365f42f-9dd9-3bdc-bbad-e7062efcaf7c,"Wired 
connection 4")
  Oct 31 07:08:37 spiny NetworkManager[11575]:   [1509458917.1284] 
settings: (enx0050b647ede2): created default wired connection 'Wired connection 
4'
  Oct 31 07:08:37 spiny systemd[1]: Starting 
systemd-resolved-update-resolvconf.service...
  Oct 31 07:08:37 spiny systemd[1]: Started 
systemd-resolved-update-resolvconf.service.
  Oct 31 07:08:37 spiny kernel: usb 1-1.2: new full-speed USB device number 23 
using xhci_hcd
  Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device found, idVendor=0d8c, 
idProduct=0105
  Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB 

[Kernel-packages] [Bug 1745828] Re: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

[Daniel van Vugt]

See also bug 1747336, where a closely-related rtl bluetooth chip just
got a fix.

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

Title:
  [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

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

Bug description:
  It is ON and VISIBLE in the control panel.  My iPhone can see two
  other devices but it can't see the computer, and the computer  can't
  see anything, even if left searching for tens of minutes.

  The previous answers listed below suggest the following diagnostics

  Bluetooth not working after update
  How can I make my bluetooth works on Ubuntu 16.04?
  Ubuntu 16.04 bluetooth not working (Dell XPS13)
  Bluetooth (Atheros AR3012) not working on Ubuntu 16.04
  Bluetooth not working on Ubuntu 16.04 LTS
  Bluetooth cannot find any devices
  Stuck on a bluetooth problem

  The service seems to be running

  /home >sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
     Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
   Docs: man:bluetoothd(8)
   Main PID: 790 (bluetoothd)
     Status: "Running"
     CGroup: /system.slice/bluetooth.service
     └─790 /usr/lib/bluetooth/bluetoothd

  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.

  and not blocked

  /home >rfkill list
  0: hci0: Bluetooth
   Soft blocked: no
   Hard blocked: no
  1: phy0: Wireless LAN
   Soft blocked: no
   Hard blocked: no

  I have edited /etc/bluetooth/main.conf to include

  AutoEnable=true

  but I noted that the entire file was commented out.

  The kernel seems reasonably up to date

   >uname -a
  Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 
22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  I wonder if I need a device driver, but I have no idea how to find
  out.  The following diagnostics may help some of you knowledgeable
  people find out.

   >hcitool dev
  Devices:
   hci0 24:0A:64:F5:EE:86

  and the output of dmsg is

  >dmesg | grep Blue
  [2.030855] usb 1-1.4: Product: Bluetooth Radio
  [   13.806355] Bluetooth: Core ver 2.22
  [   13.806369] Bluetooth: HCI device and connection manager initialized
  [   13.806372] Bluetooth: HCI socket layer initialized
  [   13.806373] Bluetooth: L2CAP socket layer initialized
  [   13.806377] Bluetooth: SCO socket layer initialized
  [   13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a 
lmp_ver=06 lmp_subver=8821
  [   13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
  [   13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin
  [   13.877382] Bluetooth: hci0: rom_version status=0 version=1
  [   13.877387] Bluetooth: cfg_sz 0, total size 17428
  [   16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   16.550281] Bluetooth: BNEP filters: protocol multicast
  [   16.550284] Bluetooth: BNEP socket layer initialized
  [   27.868345] Bluetooth: RFCOMM TTY layer initialized
  [   27.868350] Bluetooth: RFCOMM socket layer initialized
  [   27.868354] Bluetooth: RFCOMM ver 1.11

  and of lsusb is

  >lsusb
  Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 004: ID 13d3:3414 IMC Networks
  Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Thanking you in anticipation
  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: 

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

[Leonardo Müller]

The last version working properly is 4.15-rc4. 4.15-rc5 don't suspend
(it fails to) and, starting from 4.15-rc6, this problem with the
Ethernet card appears.

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

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

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.172
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Mar  2 00:21:57 2018
  Dependencies:
   
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-10-generic.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1153 F pulseaudio
   /dev/snd/controlC1:  usuario1153 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26'
 Mixer name : 'VIA VT1818S'
 Components : 'HDA:11060440,18492818,0010'
 Controls  : 40
 Simple ctrls  : 17
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 7
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined
 Playback channels: Mono
 Mono: Playback [on]
  CurrentDesktop: LXDE
  Dependencies:
   
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux-firmware 1.172
  PackageArchitecture: all
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz 
root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: H55M-LE
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH55M-LE:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772/+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 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) by an insufficient compiler!

[Arna Ghosh]

Hello everyone,
Thanks to your answers and this discussion. I ran into this problem yesterday. 
Although I tried the instructions by @cjjefcoat on #57, it didn't give me back 
my display as expected. Unity got screwed up and although I could see the 
display, the rendering was not proper. The windows didn't have the title bar 
and most keyboard functionality won't work. I didn't even have the task bar. 
I went back to -112 version of the kernel but only found the same result. So I 
reinstalled all NVIDIA drviers and uninstalled CUDA with no luck at all. 
Finally I tried restarting Unity by following #14 here - 
https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1569357/comments/14

and it worked for me :D 
Now I tried running everything on 116 kernel and it works. So in case unity 
screws up for any of you after you reinstall the 116 kernel, try restarting 
Unity and hope it works :D

Cheers

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

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04) by an insufficient compiler!

Status in gcc:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  The root cause of the problem has been found to be installing the -116
  kernel without a sufficiently updated version of gcc.  In my case, my
  system received the gcc update AFTER the kernel update.

  Uninstalling the -116 kernel and reinstalling it with the updated
  version of gcc solved the problem for me.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: 

[Kernel-packages] [Bug 1752026] Re: Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default machine type(pseries-bionic) complaining "KVM implementation does not support Transactional Memo

[ChristianEhrhardt]

FYI: There is bug 1753826 which postponed the release/testing of this one a bit.
Currently in rebuild/test together.

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

Title:
  Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default
  machine type(pseries-bionic) complaining "KVM implementation does not
  support Transactional Memory, try cap-htm=off" (kvm)

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  In Progress

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2018-02-23 
08:31:06 ==
  ---Problem Description---
  libvirt unable to start a KVM guest complaining about cap-htm machine 
property to be off

  Host Env:
  # lscpu
  Architecture:ppc64le
  Byte Order:  Little Endian
  CPU(s):  160
  On-line CPU(s) list: 0-159
  Thread(s) per core:  4
  Core(s) per socket:  20
  Socket(s):   2
  NUMA node(s):2
  Model:   2.2 (pvr 004e 1202)
  Model name:  POWER9 (raw), altivec supported
  CPU max MHz: 3800.
  CPU min MHz: 2166.
  L1d cache:   32K
  L1i cache:   32K
  L2 cache:512K
  L3 cache:10240K
  NUMA node0 CPU(s):   0-79
  NUMA node8 CPU(s):   80-159

  ii  qemu-kvm  1:2.11+dfsg-1ubuntu2
  ppc64el  QEMU Full virtualization on x86 hardware

  ii  libvirt-bin   4.0.0-1ubuntu3
  ppc64el  programs for the libvirt library

  # lsmcode
  Version of System Firmware : 
   Product Name  : OpenPOWER Firmware
   Product Version   : open-power-SUPERMICRO-P9DSU-V1.03-20180205-imp
   Product Extra :  occ-577915f
   Product Extra :  skiboot-v5.9-240-g081882690163-pcbedce4
   Product Extra :  petitboot-v1.6.6-p019c87e
   Product Extra :  sbe-095e608
   Product Extra :  machine-xml-fb5f933
   Product Extra :  hostboot-9bfb201
   Product Extra :  linux-4.14.13-openpower1-p78d7eee

  
   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  4.15.0-10-generic
   
  Machine Type = power9 boston 2.2 (pvr 004e 1202) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Boot a guest from libvirt with default pseries machine type or 
pseries-bionic

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

  Starting install...
  ERRORinternal error: process exited while connecting to monitor: 
,id=scsi0-0-0-0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=26 
-device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:77:78:79,bus=pci.0,addr=0x1 
-chardev pty,id=charserial0 -device 
spapr-vty,chardev=charserial0,id=serial0,reg=0x3000 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on
  2018-02-23T14:21:11.081809Z qemu-system-ppc64: KVM implementation does not 
support Transactional Memory, try cap-htm=off
  Domain installation does not appear to have been successful.
  If it was, you can restart your domain by running:
virsh --connect qemu:///system start virt-tests-vm1
  otherwise, please restart your installation.

  2. Fails to boot..

  Note: if we specify machine type as pseries=2.12 it boots fine like
  below

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries-2.12 --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

  qemu-cmd line:

  libvirt+   4283  1 99 09:26 ?00:00:38 qemu-system-ppc64
  -enable-kvm -name guest=virt-tests-vm1,debug-threads=on -S -object
  secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-4
  -virt-tests-vm1/master-key.aes -machine 

[Kernel-packages] [Bug 1753797] Re: package linux-firmware 1.157.16 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

** Changed in: linux-firmware (Ubuntu)
   Importance: Undecided => Low

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

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

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

Status in linux-firmware package in Ubuntu:
  Invalid

Bug description:
  My system is a toshiba satellite that was originally windows and i
  converted to ubuntu after several errors led to me erasing my
  harddrive and installing ubuntu. I frequently need to manually fsck
  /dev/sda2. I have also found that it is difficult to install updates
  on this system. I typically need to reboot and manually fsck then
  attempt reinstall. I believe that I am running ubuntu 16.43.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware 1.157.16
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Tue Mar  6 06:57:06 2018
  Dependencies:
   
  DuplicateSignature:
   package:linux-firmware:1.157.16
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package linux-firmware (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-12-25 (70 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: linux-firmware
  Title: package linux-firmware 1.157.16 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[bugproxy]

--- Comment From stefan.ra...@de.ibm.com 2018-03-06 14:43 EDT---
Hi Frank,
We have actually contributed some some patches which improve python3 support, 
so that's definitely on our minds. These patches certainly don't make things 
worse. I did a quick test, and kvm_stat as is after applying above patches 
would run with python3. Whether there's a conscious decision to support python3 
or not is ultimately up to the community, though.

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

Title:
  [18.04 FEAT] Add kvm_stat from kernel tree

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Improves RAS characterics of systems running KVM by providing kvm_stat script:
  https://github.com/torvalds/linux/tree/master/tools/kvm/kvm_stat

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1734130/+subscriptions

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

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

[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/1753804

Title:
  versions 4.4.0-108 and up hang on reboot; HP 8300 Elite CMT

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Shutdown works fine. 
  On Reboot, the system hangs.

  This is a problem on the current kernel (4.4.0.116) and appears to
  have been introduced in 4.4.0.106, 107 or 108. I make this assertion
  because I have version 4.4.0.105 and version 4.4.0.108 available on my
  computer. versions 105 and below work, versions 108 and up do not
  work.

  I will upload a screen shot of the trace, since it occurs after drives
  are dismounted.

  I started by making sure I have the most current firmware (BIOS) for
  this computer. It is on the most recent version.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-116-generic 4.4.0-116.140
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nickf  2552 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Mar  6 12:52:16 2018
  HibernationDevice: RESUME=UUID=8f1f8ead-e0d0-4468-b7fb-1328c0495e93
  InstallationDate: Installed on 2012-09-27 (1986 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  MachineType: Hewlett-Packard HP Compaq Elite 8300 CMT
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=9766c23d-8567-48c0-a1eb-b01e0eed0170 ro acpi=force
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-116-generic N/A
   linux-backports-modules-4.4.0-116-generic  N/A
   linux-firmware 1.157.17
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 10/05/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: K01 v03.04
  dmi.board.asset.tag: 2UA23822YR
  dmi.board.name: 3396
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: 2UA23822YR
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrK01v03.04:bd10/05/2016:svnHewlett-Packard:pnHPCompaqElite8300CMT:pvr:rvnHewlett-Packard:rn3396:rvr:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: HP Compaq Elite 8300 CMT
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1751834] Re: Power9 DD 2.2 needs HMI fixup backport of upstream patch(d075745d893c78730e4a3b7a60fca23c2f764081) into kernel

[Manoj Iyer]

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

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

Title:
  Power9 DD 2.2 needs HMI fixup backport of upstream
  patch(d075745d893c78730e4a3b7a60fca23c2f764081) into kernel

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

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2018-02-23 
06:55:23 ==
  ---Problem Description---
  Power9 DD 2.2 needs HMI fixup backport of upstream 
patch(d075745d893c78730e4a3b7a60fca23c2f764081) into kernel
   
  ---uname output---
  4.15.0-10-generic
   
  Machine Type = power9 boston 2.2 (pvr 004e 1202) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   commit d075745d893c78730e4a3b7a60fca23c2f764081
  Author: Paul Mackerras 
  Date:   Wed Jan 17 20:51:13 2018 +1100

  KVM: PPC: Book3S HV: Improve handling of debug-trigger HMIs on POWER9
  

  Dependancy commit, looks like already present.
  commit 5080332c2c893118dbc18755f35c8b0131cf0fc4
  Author: Michael Neuling 
  Date:   Fri Sep 15 15:25:48 2017 +1000

  powerpc/64s: Add workaround for P9 vector CI load issue
  

   
  Contact Information = sathe...@in.ibm.com 
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for sathe...@in.ibm.com: 
  -Attach sysctl -a output output to the bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1751834/+subscriptions

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

[Kernel-packages] [Bug 1745349] Re: Hard lockup during boot with linux-image-4.4.0-112-generic

[Mike Turner]

Linux golf 4.4.0-110-generic #133~lp1745349Commit49bb7a3cbf5 SMP Tue Mar
6 16:37:00 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux doesn't seem to have
the problem,.

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

Title:
  Hard lockup during boot with linux-image-4.4.0-112-generic

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

Bug description:
  Systems on ASUS H110M-C Boards don't boot here with Kernel 4.4.0-112
  instead they show

  NMI watchdog: Watchdog detected hard lockup on cpu 0
  NMI watchdog: Watchdog detected hard lockup on cpu 1
  NMI watchdog: Watchdog detected hard lockup on cpu 3
  NMI watchdog: Watchdog detected hard lockup on cpu 2

  I cannot provide any logs of course.

  Booting with 4.4.0-109 works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lr3200 2013 F pulseaudio
  Date: Thu Jan 25 11:38:55 2018
  HibernationDevice: RESUME=UUID=8e35131d-6d40-4f4f-a3db-c7336e72cbce
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   enp3s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
root=UUID=4dc5bb0a-ab7c-48fa-ac23-bcdf23755d93 ro
  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.4.0-109-generic N/A
   linux-backports-modules-4.4.0-109-generic  N/A
   linux-firmware 1.157.15
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3601
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-C
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3601:bd12/12/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-C:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1753804] Re: versions 4.4.0-108 and up hang on reboot; HP 8300 Elite CMT

[Nick Fankhauser]

Additional info: This is the line I added to /etc/default/grub to search
for a working kernel and  revert to 105 until this is fixed:

GRUB_DEFAULT="Advanced options for Ubuntu>Ubuntu, with Linux 4.4.0-105-generic"
#GRUB_DEFAULT=0

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

Title:
  versions 4.4.0-108 and up hang on reboot; HP 8300 Elite CMT

Status in linux package in Ubuntu:
  New

Bug description:
  Shutdown works fine. 
  On Reboot, the system hangs.

  This is a problem on the current kernel (4.4.0.116) and appears to
  have been introduced in 4.4.0.106, 107 or 108. I make this assertion
  because I have version 4.4.0.105 and version 4.4.0.108 available on my
  computer. versions 105 and below work, versions 108 and up do not
  work.

  I will upload a screen shot of the trace, since it occurs after drives
  are dismounted.

  I started by making sure I have the most current firmware (BIOS) for
  this computer. It is on the most recent version.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-116-generic 4.4.0-116.140
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nickf  2552 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Mar  6 12:52:16 2018
  HibernationDevice: RESUME=UUID=8f1f8ead-e0d0-4468-b7fb-1328c0495e93
  InstallationDate: Installed on 2012-09-27 (1986 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  MachineType: Hewlett-Packard HP Compaq Elite 8300 CMT
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=9766c23d-8567-48c0-a1eb-b01e0eed0170 ro acpi=force
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-116-generic N/A
   linux-backports-modules-4.4.0-116-generic  N/A
   linux-firmware 1.157.17
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 10/05/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: K01 v03.04
  dmi.board.asset.tag: 2UA23822YR
  dmi.board.name: 3396
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: 2UA23822YR
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrK01v03.04:bd10/05/2016:svnHewlett-Packard:pnHPCompaqElite8300CMT:pvr:rvnHewlett-Packard:rn3396:rvr:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: HP Compaq Elite 8300 CMT
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1753804] [NEW] versions 4.4.0-108 and up hang on reboot; HP 8300 Elite CMT

[Nick Fankhauser]

Public bug reported:

Shutdown works fine. 
On Reboot, the system hangs.

This is a problem on the current kernel (4.4.0.116) and appears to have
been introduced in 4.4.0.106, 107 or 108. I make this assertion because
I have version 4.4.0.105 and version 4.4.0.108 available on my computer.
versions 105 and below work, versions 108 and up do not work.

I will upload a screen shot of the trace, since it occurs after drives
are dismounted.

I started by making sure I have the most current firmware (BIOS) for
this computer. It is on the most recent version.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-116-generic 4.4.0-116.140
ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
Uname: Linux 4.4.0-116-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  nickf  2552 F pulseaudio
CurrentDesktop: Unity
Date: Tue Mar  6 12:52:16 2018
HibernationDevice: RESUME=UUID=8f1f8ead-e0d0-4468-b7fb-1328c0495e93
InstallationDate: Installed on 2012-09-27 (1986 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
IwConfig:
 lono wireless extensions.
 
 eth0  no wireless extensions.
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
   Users in the 'systemd-journal' group can see all messages. Pass -q to
   turn off this notice.
 No journal files were opened due to insufficient permissions.
MachineType: Hewlett-Packard HP Compaq Elite 8300 CMT
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=9766c23d-8567-48c0-a1eb-b01e0eed0170 ro acpi=force
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-116-generic N/A
 linux-backports-modules-4.4.0-116-generic  N/A
 linux-firmware 1.157.17
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
WifiSyslog:
 
dmi.bios.date: 10/05/2016
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: K01 v03.04
dmi.board.asset.tag: 2UA23822YR
dmi.board.name: 3396
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: 2UA23822YR
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrK01v03.04:bd10/05/2016:svnHewlett-Packard:pnHPCompaqElite8300CMT:pvr:rvnHewlett-Packard:rn3396:rvr:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: HP Compaq Elite 8300 CMT
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-bug third-party-packages xenial

** Attachment added: "Screen shot of lockup during reboot"
   
https://bugs.launchpad.net/bugs/1753804/+attachment/5070940/+files/2018-03-06%2012.48.17.jpg

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

Title:
  versions 4.4.0-108 and up hang on reboot; HP 8300 Elite CMT

Status in linux package in Ubuntu:
  New

Bug description:
  Shutdown works fine. 
  On Reboot, the system hangs.

  This is a problem on the current kernel (4.4.0.116) and appears to
  have been introduced in 4.4.0.106, 107 or 108. I make this assertion
  because I have version 4.4.0.105 and version 4.4.0.108 available on my
  computer. versions 105 and below work, versions 108 and up do not
  work.

  I will upload a screen shot of the trace, since it occurs after drives
  are dismounted.

  I started by making sure I have the most current firmware (BIOS) for
  this computer. It is on the most recent version.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-116-generic 4.4.0-116.140
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nickf  2552 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Mar  6 12:52:16 2018
  HibernationDevice: RESUME=UUID=8f1f8ead-e0d0-4468-b7fb-1328c0495e93
  InstallationDate: Installed on 2012-09-27 (1986 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  MachineType: Hewlett-Packard HP Compaq Elite 8300 CMT
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: 

[Kernel-packages] [Bug 1753797] Re: package linux-firmware 1.157.16 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Apport retracing service]

** Tags removed: need-duplicate-check

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

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

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  My system is a toshiba satellite that was originally windows and i
  converted to ubuntu after several errors led to me erasing my
  harddrive and installing ubuntu. I frequently need to manually fsck
  /dev/sda2. I have also found that it is difficult to install updates
  on this system. I typically need to reboot and manually fsck then
  attempt reinstall. I believe that I am running ubuntu 16.43.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware 1.157.16
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Tue Mar  6 06:57:06 2018
  Dependencies:
   
  DuplicateSignature:
   package:linux-firmware:1.157.16
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package linux-firmware (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-12-25 (70 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: linux-firmware
  Title: package linux-firmware 1.157.16 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1752350] Re: Bionic x86_64 Linux Kernel 4.15 fails to boot on Xen

[Alejandro Mery]

@jsalibury, your kernel fixed my domUs =)

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

Title:
  Bionic x86_64 Linux Kernel 4.15 fails to boot on Xen

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

Bug description:
  The Linux Kernel 4.15 from bionic on x86_64 immediately crashes when
  booted as a dom0 under Xen.

  A similar bug was reported by someone else for archlinux
  (https://bugs.archlinux.org/task/57500).

  A patch exists for 4.16. I tried this patch on 4.15.0-10-generic, it
  fixes the problem for me.
  
(https://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git/patch/?id=4f277295e54c5b7340e48efea3fc5cc21a2872b7).

  Xen output:

  (XEN) Xen version 4.9.0 (Ubuntu 4.9.0-0ubuntu3) (stefan.ba...@canonical.com) 
(gcc (Ubuntu 7.2.0-8ubuntu2) 7.2.0) debug=n  Fri Oct 13 15:58:41 UTC 2017
  (XEN) Bootloader: GRUB 2.02~beta2-36ubuntu3.9
  (XEN) Command line: placeholder com1=115200,8N1 console=com1,vga
  (XEN) Xen image load base address: 0
  (XEN) Video information:
  (XEN)  VGA is text mode 80x25, font 8x16
  (XEN)  VBE/DDC methods: none; EDID transfer time: 0 seconds
  (XEN)  EDID info not retrieved because no DDC retrieval method detected
  (XEN) Disc information:
  (XEN)  Found 1 MBR signatures
  (XEN)  Found 1 EDD information structures
  (XEN) Xen-e820 RAM map:
  (XEN)   - 0009ec00 (usable)
  (XEN)  000f - 0010 (reserved)
  (XEN)  0010 - cb6cfc00 (usable)
  (XEN)  cb6cfc00 - cb723c00 (ACPI NVS)
  (XEN)  cb723c00 - cb725c00 (ACPI data)
  (XEN)  cb725c00 - cc00 (reserved)
  (XEN)  f800 - fc00 (reserved)
  (XEN)  fec0 - fed00400 (reserved)
  (XEN)  fed2 - feda (reserved)
  (XEN)  fee0 - fef0 (reserved)
  (XEN)  ffb0 - 0001 (reserved)
  (XEN)  0001 - 00013000 (usable)
  (XEN) New Xen image base address: 0xcb00
  (XEN) ACPI: RSDP 000FEC00, 0024 (r2 DELL  )
  (XEN) ACPI: XSDT 000FC7E7, 006C (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: FACP 000FC8D7, 00F4 (r3 DELLB11K  15 ASL61)
  (XEN) ACPI: DSDT FFDC89E4, 47BC (r1   DELLdt_ex 1000 INTL 20050624)
  (XEN) ACPI: FACS CB6CFC00, 0040
  (XEN) ACPI: SSDT FFDCD2C1, 00AC (r1   DELLst_ex 1000 INTL 20050624)
  (XEN) ACPI: APIC 000FC9CB, 0092 (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: BOOT 000FCA5D, 0028 (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: ASF! 000FCA85, 0096 (r32 DELLB11K  15 ASL61)
  (XEN) ACPI: MCFG 000FCB1B, 003E (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: HPET 000FCB59, 0038 (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: TCPA 000FCDB5, 0032 (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: DMAR 000FCDE7, 0068 (r1 DELLB11K  15 ASL61)
  (XEN) System RAM: 4022MB (4118964kB)
  (XEN) Domain heap initialised
  (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec0, GSI 0-23
  (XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
  (XEN) Using scheduler: SMP Credit Scheduler (credit)
  (XEN) Platform timer is 14.318MHz HPET
  (XEN) Detected 2926.007 MHz processor.
  (XEN) Initing memory sharing.
  (XEN) Intel VT-d iommu 0 supported page sizes: 4kB.
  (XEN) Intel VT-d Snoop Control enabled.
  (XEN) Intel VT-d Dom0 DMA Passthrough not enabled.
  (XEN) Intel VT-d Queued Invalidation enabled.
  (XEN) Intel VT-d Interrupt Remapping not enabled.
  (XEN) Intel VT-d Posted Interrupt not enabled.
  (XEN) Intel VT-d Shared EPT tables not enabled.
  (XEN) :04:00.0: unknown type 4
  (XEN) I/O virtualisation enabled
  (XEN)  - Dom0 mode: Relaxed
  (XEN) Interrupt remapping disabled
  (XEN) ENABLING IO-APIC IRQs
  (XEN)  -> Using new ACK method
  (XEN) Allocated console ring of 16 KiB.
  (XEN) VMX: Supported advanced features:
  (XEN)  - APIC MMIO access virtualisation
  (XEN)  - APIC TPR shadow
  (XEN)  - Extended Page Tables (EPT)
  (XEN)  - Virtual-Processor Identifiers (VPID)
  (XEN)  - Virtual NMI
  (XEN)  - MSR direct-access bitmap
  (XEN) HVM: ASIDs enabled.
  (XEN) HVM: VMX enabled
  (XEN) HVM: Hardware Assisted Paging (HAP) detected
  (XEN) HVM: HAP page sizes: 4kB, 2MB
  (XEN) Brought up 4 CPUs
  (XEN) Dom0 has maximum 600 PIRQs
  (XEN) *** LOADING DOMAIN 0 ***
  (XEN)  Xen  kernel: 64-bit, lsb, compat32
  (XEN)  Dom0 kernel: 64-bit, PAE, lsb, paddr 0x100 -> 0x2b69000
  (XEN) PHYSICAL MEMORY ARRANGEMENT:
  (XEN)  Dom0 alloc.:   00012000->00012400 (952940 pages to be 
allocated)
  (XEN)  Init. ramdisk: 00012d251000->00012575
  (XEN) VIRTUAL MEMORY ARRANGEMENT:
  (XEN)  Loaded kernel: 8100->82b69000
  (XEN)  Init. ramdisk: 

[Kernel-packages] [Bug 1753797] [NEW] package linux-firmware 1.157.16 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Fabien Perez]

Public bug reported:

My system is a toshiba satellite that was originally windows and i
converted to ubuntu after several errors led to me erasing my harddrive
and installing ubuntu. I frequently need to manually fsck /dev/sda2. I
have also found that it is difficult to install updates on this system.
I typically need to reboot and manually fsck then attempt reinstall. I
believe that I am running ubuntu 16.43.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-firmware 1.157.16
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Tue Mar  6 06:57:06 2018
Dependencies:
 
DuplicateSignature:
 package:linux-firmware:1.157.16
 Processing triggers for man-db (2.7.5-1) ...
 dpkg: error processing package linux-firmware (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-12-25 (70 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: linux-firmware
Title: package linux-firmware 1.157.16 failed to install/upgrade: package is in 
a very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

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

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  My system is a toshiba satellite that was originally windows and i
  converted to ubuntu after several errors led to me erasing my
  harddrive and installing ubuntu. I frequently need to manually fsck
  /dev/sda2. I have also found that it is difficult to install updates
  on this system. I typically need to reboot and manually fsck then
  attempt reinstall. I believe that I am running ubuntu 16.43.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware 1.157.16
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Tue Mar  6 06:57:06 2018
  Dependencies:
   
  DuplicateSignature:
   package:linux-firmware:1.157.16
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package linux-firmware (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-12-25 (70 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: linux-firmware
  Title: package linux-firmware 1.157.16 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1753583] Re: Ubuntu 16.04.4 HWE kernel lockup: Upstream commit missing

[Per Allansson]

I can confirm that your build works (as described in my previous
comment).

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

Title:
  Ubuntu 16.04.4 HWE kernel lockup: Upstream commit missing

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

Bug description:
  I experience random lockups when disabling CPUs, with symptoms very
  much as described here:

  See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733662

  and when double-checking the source code for 4.13.0-36.40~16.04.1 I can see 
that upstream commit d47924417319e3b6a728c0b690f183e75bc2a702 is indeed missing.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  5 19:30 seq
   crw-rw 1 root audio 116, 33 Mar  5 19:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: FUJITSU PRIMERGY RX2530 M4
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/image1/kernel root=/dev/czvg/image1 ro 
console=tty0 console=ttyS0,115200 earlyprintk=ttyS0 rootdelay=300 net.ifnames=0 
biosdevname=0 nomodeset scsi_mod.scan=sync cz-boot-fs=/dev/sda1 
cz-state-fs=/dev/czvg/state1
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/05/2017
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V5.0.0.12 R1.11.0 for D3383-A1x
  dmi.board.name: D3383-A1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3383-A12 WGS03 GS04
  dmi.chassis.asset.tag: System Asset Tag
  dmi.chassis.type: 23
  dmi.chassis.vendor: FUJITSU
  dmi.chassis.version: RX2530M4R1
  dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.12R1.11.0forD3383-A1x:bd10/05/2017:svnFUJITSU:pnPRIMERGYRX2530M4:pvrGS01:rvnFUJITSU:rnD3383-A1:rvrS26361-D3383-A12WGS03GS04:cvnFUJITSU:ct23:cvrRX2530M4R1:
  dmi.product.family: SERVER
  dmi.product.name: PRIMERGY RX2530 M4
  dmi.product.version: GS01
  dmi.sys.vendor: FUJITSU

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

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

[Kernel-packages] [Bug 1746463] Re: apparmor profile load in stacked policy container fails

[Launchpad Bug Tracker]

This bug was fixed in the package linux-gcp - 4.15.0-1001.1

---
linux-gcp (4.15.0-1001.1) bionic; urgency=medium

  * linux-gcp: 4.15.0-1001.1 -proposed tracker (LP: #1752101)

  * linux xenial derivatives fail to build (LP: #1691814) // Prepare linux-gcp
for bionic (LP: #1752069)
- [Packaging] Set do_tools_common in common vars

  * Prepare linux-gcp for bionic (LP: #1752069)
- linux-gcp: Update base kernel version
- [Config] linux-gcp: Reset config annotations to master
- [Config] linux-gcp: Add annotations overlay
- [Config] linux-gcp: updateconfigs after rebase to Ubuntu-4.15.0-10.11
- Ubuntu: linux-gcp: Revert build_arch=x86
- [Packaging] linux-gcp: Update Vcs-Git for bionic

  * CVE-2017-5715 (Spectre v2 retpoline)
- [Config] linux-gcp: disable retpoline checks for first upload

  * [Packaging] Allow overlay of config annotations (LP: #1752072)
- [Packaging] config-check: allow overlay annotations files

  [ Ubuntu: 4.15.0-10.11 ]

  * linux: 4.15.0-10.11 -proposed tracker (LP: #1749250)
  * "swiotlb: coherent allocation failed" dmesg spam with linux 4.15.0-9.10
(LP: #1749202)
- swiotlb: suppress warning when __GFP_NOWARN is set
- drm/ttm: specify DMA_ATTR_NO_WARN for huge page pools
  * linux-tools: perf incorrectly linking libbfd (LP: #1748922)
- SAUCE: tools -- add ability to disable libbfd
- [Packaging] correct disablement of libbfd
  * [Artful] Realtek ALC225: 2 secs noise when a headset plugged in
(LP: #1744058)
- ALSA: hda/realtek - update ALC225 depop optimize
  * [Artful] Support headset mode for DELL WYSE (LP: #1723913)
- SAUCE: ALSA: hda/realtek - Add support headset mode for DELL WYSE
  * headset mic can't be detected on two Dell machines (LP: #1748807)
- ALSA: hda/realtek - Support headset mode for ALC215/ALC285/ALC289
- ALSA: hda - Fix headset mic detection problem for two Dell machines
  * Bionic update to v4.15.3 stable release (LP: #1749191)
- ip6mr: fix stale iterator
- net: igmp: add a missing rcu locking section
- qlcnic: fix deadlock bug
- qmi_wwan: Add support for Quectel EP06
- r8169: fix RTL8168EP take too long to complete driver initialization.
- tcp: release sk_frag.page in tcp_disconnect
- vhost_net: stop device during reset owner
- ipv6: addrconf: break critical section in addrconf_verify_rtnl()
- ipv6: change route cache aging logic
- Revert "defer call to mem_cgroup_sk_alloc()"
- net: ipv6: send unsolicited NA after DAD
- rocker: fix possible null pointer dereference in
  rocker_router_fib_event_work
- tcp_bbr: fix pacing_gain to always be unity when using lt_bw
- cls_u32: add missing RCU annotation.
- ipv6: Fix SO_REUSEPORT UDP socket with implicit sk_ipv6only
- soreuseport: fix mem leak in reuseport_add_sock()
- net_sched: get rid of rcu_barrier() in tcf_block_put_ext()
- net: sched: fix use-after-free in tcf_block_put_ext
- media: mtk-vcodec: add missing MODULE_LICENSE/DESCRIPTION
- media: soc_camera: soc_scale_crop: add missing
  MODULE_DESCRIPTION/AUTHOR/LICENSE
- media: tegra-cec: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE
- gpio: uniphier: fix mismatch between license text and MODULE_LICENSE
- crypto: tcrypt - fix S/G table for test_aead_speed()
- Linux 4.15.3
  * bnx2x_attn_int_deasserted3:4323 MC assert! (LP: #1715519) //
CVE-2018-126
- net: create skb_gso_validate_mac_len()
- bnx2x: disable GSO where gso_size is too big for hardware
  * ethtool -p fails to light NIC LED on HiSilicon D05 systems (LP: #1748567)
- net: hns: add ACPI mode support for ethtool -p
  * CVE-2017-5715 (Spectre v2 Intel)
- [Packaging] retpoline files must be sorted
- [Packaging] pull in retpoline files
  * [Feature] PXE boot with Intel Omni-Path (LP: #1712031)
- d-i: Add hfi1 to nic-modules
  * CVE-2017-5715 (Spectre v2 retpoline)
- [Packaging] retpoline -- add call site validation
- [Config] disable retpoline checks for first upload
  * Do not duplicate changelog entries assigned to more than one bug or CVE
(LP: #1743383)
- [Packaging] git-ubuntu-log -- handle multiple bugs/cves better

  [ Ubuntu: 4.15.0-9.10 ]

  * linux: 4.15.0-9.10 -proposed tracker (LP: #1748244)
  * Miscellaneous Ubuntu changes
- [Debian] tests -- remove gcc-multilib dependency for arm64

  [ Ubuntu: 4.15.0-8.9 ]

  * linux: 4.15.0-8.9 -proposed tracker (LP: #1748075)
  * Bionic update to v4.15.2 stable release (LP: #1748072)
- KVM: x86: Make indirect calls in emulator speculation safe
- KVM: VMX: Make indirect call speculation safe
- module/retpoline: Warn about missing retpoline in module
- x86/cpufeatures: Add CPUID_7_EDX CPUID leaf
- x86/cpufeatures: Add Intel feature bits for Speculation Control
- x86/cpufeatures: Add AMD feature bits for Speculation Control
- x86/msr: Add definitions for new speculation control MSRs
- x86/pti: Do 

[Kernel-packages] [Bug 1752072] Re: [Packaging] Allow overlay of config annotations

[Launchpad Bug Tracker]

This bug was fixed in the package linux-gcp - 4.15.0-1001.1

---
linux-gcp (4.15.0-1001.1) bionic; urgency=medium

  * linux-gcp: 4.15.0-1001.1 -proposed tracker (LP: #1752101)

  * linux xenial derivatives fail to build (LP: #1691814) // Prepare linux-gcp
for bionic (LP: #1752069)
- [Packaging] Set do_tools_common in common vars

  * Prepare linux-gcp for bionic (LP: #1752069)
- linux-gcp: Update base kernel version
- [Config] linux-gcp: Reset config annotations to master
- [Config] linux-gcp: Add annotations overlay
- [Config] linux-gcp: updateconfigs after rebase to Ubuntu-4.15.0-10.11
- Ubuntu: linux-gcp: Revert build_arch=x86
- [Packaging] linux-gcp: Update Vcs-Git for bionic

  * CVE-2017-5715 (Spectre v2 retpoline)
- [Config] linux-gcp: disable retpoline checks for first upload

  * [Packaging] Allow overlay of config annotations (LP: #1752072)
- [Packaging] config-check: allow overlay annotations files

  [ Ubuntu: 4.15.0-10.11 ]

  * linux: 4.15.0-10.11 -proposed tracker (LP: #1749250)
  * "swiotlb: coherent allocation failed" dmesg spam with linux 4.15.0-9.10
(LP: #1749202)
- swiotlb: suppress warning when __GFP_NOWARN is set
- drm/ttm: specify DMA_ATTR_NO_WARN for huge page pools
  * linux-tools: perf incorrectly linking libbfd (LP: #1748922)
- SAUCE: tools -- add ability to disable libbfd
- [Packaging] correct disablement of libbfd
  * [Artful] Realtek ALC225: 2 secs noise when a headset plugged in
(LP: #1744058)
- ALSA: hda/realtek - update ALC225 depop optimize
  * [Artful] Support headset mode for DELL WYSE (LP: #1723913)
- SAUCE: ALSA: hda/realtek - Add support headset mode for DELL WYSE
  * headset mic can't be detected on two Dell machines (LP: #1748807)
- ALSA: hda/realtek - Support headset mode for ALC215/ALC285/ALC289
- ALSA: hda - Fix headset mic detection problem for two Dell machines
  * Bionic update to v4.15.3 stable release (LP: #1749191)
- ip6mr: fix stale iterator
- net: igmp: add a missing rcu locking section
- qlcnic: fix deadlock bug
- qmi_wwan: Add support for Quectel EP06
- r8169: fix RTL8168EP take too long to complete driver initialization.
- tcp: release sk_frag.page in tcp_disconnect
- vhost_net: stop device during reset owner
- ipv6: addrconf: break critical section in addrconf_verify_rtnl()
- ipv6: change route cache aging logic
- Revert "defer call to mem_cgroup_sk_alloc()"
- net: ipv6: send unsolicited NA after DAD
- rocker: fix possible null pointer dereference in
  rocker_router_fib_event_work
- tcp_bbr: fix pacing_gain to always be unity when using lt_bw
- cls_u32: add missing RCU annotation.
- ipv6: Fix SO_REUSEPORT UDP socket with implicit sk_ipv6only
- soreuseport: fix mem leak in reuseport_add_sock()
- net_sched: get rid of rcu_barrier() in tcf_block_put_ext()
- net: sched: fix use-after-free in tcf_block_put_ext
- media: mtk-vcodec: add missing MODULE_LICENSE/DESCRIPTION
- media: soc_camera: soc_scale_crop: add missing
  MODULE_DESCRIPTION/AUTHOR/LICENSE
- media: tegra-cec: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE
- gpio: uniphier: fix mismatch between license text and MODULE_LICENSE
- crypto: tcrypt - fix S/G table for test_aead_speed()
- Linux 4.15.3
  * bnx2x_attn_int_deasserted3:4323 MC assert! (LP: #1715519) //
CVE-2018-126
- net: create skb_gso_validate_mac_len()
- bnx2x: disable GSO where gso_size is too big for hardware
  * ethtool -p fails to light NIC LED on HiSilicon D05 systems (LP: #1748567)
- net: hns: add ACPI mode support for ethtool -p
  * CVE-2017-5715 (Spectre v2 Intel)
- [Packaging] retpoline files must be sorted
- [Packaging] pull in retpoline files
  * [Feature] PXE boot with Intel Omni-Path (LP: #1712031)
- d-i: Add hfi1 to nic-modules
  * CVE-2017-5715 (Spectre v2 retpoline)
- [Packaging] retpoline -- add call site validation
- [Config] disable retpoline checks for first upload
  * Do not duplicate changelog entries assigned to more than one bug or CVE
(LP: #1743383)
- [Packaging] git-ubuntu-log -- handle multiple bugs/cves better

  [ Ubuntu: 4.15.0-9.10 ]

  * linux: 4.15.0-9.10 -proposed tracker (LP: #1748244)
  * Miscellaneous Ubuntu changes
- [Debian] tests -- remove gcc-multilib dependency for arm64

  [ Ubuntu: 4.15.0-8.9 ]

  * linux: 4.15.0-8.9 -proposed tracker (LP: #1748075)
  * Bionic update to v4.15.2 stable release (LP: #1748072)
- KVM: x86: Make indirect calls in emulator speculation safe
- KVM: VMX: Make indirect call speculation safe
- module/retpoline: Warn about missing retpoline in module
- x86/cpufeatures: Add CPUID_7_EDX CPUID leaf
- x86/cpufeatures: Add Intel feature bits for Speculation Control
- x86/cpufeatures: Add AMD feature bits for Speculation Control
- x86/msr: Add definitions for new speculation control MSRs
- x86/pti: Do 

[Kernel-packages] [Bug 1745349] Re: Hard lockup during boot with linux-image-4.4.0-112-generic

[Joseph Salisbury]

I built the next test kernel, up to the following commit:
49bb7a3cbf55099e79b27c611176b8db5533d566

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1745349

Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on your test results.

Thanks in advance

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

Title:
  Hard lockup during boot with linux-image-4.4.0-112-generic

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

Bug description:
  Systems on ASUS H110M-C Boards don't boot here with Kernel 4.4.0-112
  instead they show

  NMI watchdog: Watchdog detected hard lockup on cpu 0
  NMI watchdog: Watchdog detected hard lockup on cpu 1
  NMI watchdog: Watchdog detected hard lockup on cpu 3
  NMI watchdog: Watchdog detected hard lockup on cpu 2

  I cannot provide any logs of course.

  Booting with 4.4.0-109 works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lr3200 2013 F pulseaudio
  Date: Thu Jan 25 11:38:55 2018
  HibernationDevice: RESUME=UUID=8e35131d-6d40-4f4f-a3db-c7336e72cbce
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   enp3s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
root=UUID=4dc5bb0a-ab7c-48fa-ac23-bcdf23755d93 ro
  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.4.0-109-generic N/A
   linux-backports-modules-4.4.0-109-generic  N/A
   linux-firmware 1.157.15
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3601
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-C
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3601:bd12/12/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-C:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

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

[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/1753791

Title:
  Requesting a backport of SMB2/SMB3 bugfix for DFS support

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  16.04 x64 with 4.4.0-112 or 4.4.0-116 - cannot traverse a DFS link for
  a cifs.mount from windows if vers is anything other than 1.0 default.
  (This submission was from a 112 host, but it's confirmed to still
  exist on anything less than 4.11.)

  Fix exists in 4.13.x in Ubuntu 18.x and works fine.

  Issue is that once you mount with vers=2 or greater, you cannot
  traverse the dfs root directory to any file server, and you cannot
  mount the dfs path directly - only a direct mount to the backend
  fileservers will work.

  Requesting a backport of the fix as described below as this makes it
  impossible to move forward with security action disabling SMB1 on our
  windows environment. If we do that now, will be unable to use that
  storage from all of our windows systems without directly mapping to
  individual file servers.

  https://www.spinics.net/lists/linux-cifs/msg13825.html

  1: https://bugzilla.samba.org/show_bug.cgi?id=12917

  Aurelien Aptel (3):
CIFS: set SERVER_NAME_LENGTH to serverName actual size
CIFS: make IPC a regular tcon
CIFS: use tcon_ipc instead of use_ipc parameter from SMB2_ioctl


  It's unclear if this should be treated as a security issue since it's
  not directly a security problem itself, but rather prevents taking
  security related action.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.112.118
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb  8 23:26 seq
   crw-rw 1 root audio 116, 33 Feb  8 23:26 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Mar  6 10:29:20 2018
  HibernationDevice: RESUME=/dev/mapper/main-swap
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-112-generic 
root=/dev/mapper/main-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-112-generic N/A
   linux-backports-modules-4.4.0-112-generic  N/A
   linux-firmware 1.157.15
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/21/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

[Kernel-packages] [Bug 1752376] Re: Dell Vostro 5568 - Sound device disappears after connecting headphones

[Sorfrost]

Only seems to occur when the PC has been connected to AC charger for a
very long time. Unfortunately I cannot reproduce that situation at the
moment.

** Attachment added: "acpidump.gz"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752376/+attachment/5070862/+files/acpidump.gz

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

Title:
  Dell Vostro 5568 - Sound device disappears after connecting headphones

Status in linux package in Ubuntu:
  Triaged

Bug description:
  With all kernel versions so far tested including mainline v4.15.4 the
  audio device permanently disappears even after a cold reboot once the
  headphones have been plugged/unplugged.

  Looks to be a firmware issue; latest firmware has been installed but
  issue remains.

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

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

[Kernel-packages] [Bug 1752376] Re: Dell Vostro 5568 - Sound device disappears after connecting headphones

[TJ]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => TJ (tj)

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

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

Title:
  Dell Vostro 5568 - Sound device disappears after connecting headphones

Status in linux package in Ubuntu:
  Triaged

Bug description:
  With all kernel versions so far tested including mainline v4.15.4 the
  audio device permanently disappears even after a cold reboot once the
  headphones have been plugged/unplugged.

  Looks to be a firmware issue; latest firmware has been installed but
  issue remains.

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

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

[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions

[Nobuto Murata]

Correction. I thought v4.12-rc1 had i40e 2.1.7 because of:
https://github.com/torvalds/linux/commit/15990832cd3e7e8904f8dacdabfa33adb9a836d6
But it actually has 2.1.14 from the log output.

So the correct status is:

v4.12-rc1 with i40e 2.1.14 - bad
v4.12 with i40e 2.1.14 - good

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

Title:
  [i40e] LACP bonding start up race conditions

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

Bug description:
  When provisioning Ubuntu servers with MAAS at once, some bonding pairs
  will have unexpected LACP status such as "Expired". It randomly
  happens at each provisioning with the default xenial kernel(4.4), but
  not reproducible with HWE kernel(4.13). I'm using Intel X710 cards
  (Dell-branded).

  Using the HWE kernel works as a workaround for short term, but it's
  not ideal since 4.13 is not covered by Canonical Livepatch service.

  How to reproduce:
  1. configure LACP bonding with MAAS
  2. provision machines
  3. check the bonding status in /proc/net/bonding/bond*

  frequency of occurrence:
  About 5 bond pairs in 22 pairs at each provisioning.

  [reproducible combination]
  $ uname -a
  Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 1.4.25-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  [non-reproducible combination]
  $ uname -a
  Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 2.1.14-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-116-generic 4.4.0-116.140
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  6 06:37 seq
   crw-rw 1 root audio 116, 33 Mar  6 06:37 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Mar  6 06:46:32 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R730
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed 
root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 
console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-116-generic N/A
   linux-backports-modules-4.4.0-116-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/16/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.5
  dmi.board.name: 072T6D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.asset.tag: 0018880
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R730
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1753791] [NEW] Requesting a backport of SMB2/SMB3 bugfix for DFS support

[Nathan Neulinger]

Public bug reported:

16.04 x64 with 4.4.0-112 or 4.4.0-116 - cannot traverse a DFS link for a
cifs.mount from windows if vers is anything other than 1.0 default.
(This submission was from a 112 host, but it's confirmed to still exist
on anything less than 4.11.)

Fix exists in 4.13.x in Ubuntu 18.x and works fine.

Issue is that once you mount with vers=2 or greater, you cannot traverse
the dfs root directory to any file server, and you cannot mount the dfs
path directly - only a direct mount to the backend fileservers will
work.

Requesting a backport of the fix as described below as this makes it
impossible to move forward with security action disabling SMB1 on our
windows environment. If we do that now, will be unable to use that
storage from all of our windows systems without directly mapping to
individual file servers.

https://www.spinics.net/lists/linux-cifs/msg13825.html

1: https://bugzilla.samba.org/show_bug.cgi?id=12917

Aurelien Aptel (3):
  CIFS: set SERVER_NAME_LENGTH to serverName actual size
  CIFS: make IPC a regular tcon
  CIFS: use tcon_ipc instead of use_ipc parameter from SMB2_ioctl


It's unclear if this should be treated as a security issue since it's
not directly a security problem itself, but rather prevents taking
security related action.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-generic 4.4.0.112.118
ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
Uname: Linux 4.4.0-112-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Feb  8 23:26 seq
 crw-rw 1 root audio 116, 33 Feb  8 23:26 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
Date: Tue Mar  6 10:29:20 2018
HibernationDevice: RESUME=/dev/mapper/main-swap
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: VMware, Inc. VMware Virtual Platform
PciMultimedia:
 
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-112-generic 
root=/dev/mapper/main-root ro
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-112-generic N/A
 linux-backports-modules-4.4.0-112-generic  N/A
 linux-firmware 1.157.15
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/21/2015
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/21/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, 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/1753791

Title:
  Requesting a backport of SMB2/SMB3 bugfix for DFS support

Status in linux package in Ubuntu:
  New

Bug description:
  16.04 x64 with 4.4.0-112 or 4.4.0-116 - cannot traverse a DFS link for
  a cifs.mount from windows if vers is anything other than 1.0 default.
  (This submission was from a 112 host, but it's confirmed to still
  exist on anything less than 4.11.)

  Fix exists in 4.13.x in Ubuntu 18.x and works fine.

  Issue is that once you mount with vers=2 or greater, you cannot
  traverse the dfs root directory to any file server, and you cannot
  mount the dfs path directly - only a direct mount to the backend
  fileservers will work.

  Requesting a backport of the fix as described below as this makes it
  impossible to move forward with security action disabling SMB1 on our
  windows environment. If we do that now, will be unable to use that
  storage from all of our windows systems without directly mapping to
  individual file servers.

  https://www.spinics.net/lists/linux-cifs/msg13825.html

  1: https://bugzilla.samba.org/show_bug.cgi?id=12917

  Aurelien Aptel (3):
CIFS: set SERVER_NAME_LENGTH to serverName actual size
CIFS: make IPC a regular tcon
CIFS: use tcon_ipc instead of use_ipc parameter from SMB2_ioctl


  It's unclear if this should be treated as a security issue since it's
  not directly a security problem itself, but rather prevents taking
  security related action.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 

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

[bugproxy]

--- Comment From mu...@br.ibm.com 2018-03-06 11:15 EDT---
(In reply to comment #45)
> Hi, Murilo.
>
> Can you test it on 16.04 using kdump-tools from xenial-proposed? Maybe the
> noirqdistrib option might be related to the EEH issues.
>

Ok, I'll give it a try.

(In reply to comment #46)
> Looking at the log, I noticed the EEH is frozen right after finding the
> Broadcom card. Is that one the tg3?
>
> [  OK  ] Found device NetXtreme BCM5719 Gigabit Ethernet PCIe.
> [8.191135] EEH: Frozen PE#7 on PHB#21 detected
> [8.191280] EEH: PE location: S00210f, PHB location: N/A

Yeah correct, this is the tg3 device. But the EEH is seen in a PHB
different then the one the adapter is in. This adapter is PHB#01, where
the EEH is seen in the PHB#21.

>
> Also, the recovery problem seems to be caused by ast.
>
> [   18.267005] EEH: 210 reads ignored for recovering device at
> location=S00210f driver=ast pci addr=0021:10:00.0
> [   18.267334] EEH: Might be infinite loop in ast driver
>
> Looking at the upstream logs, one commit came up. Can you open a new bug for
> it?
>
> commit 298360af3dab45659810fdc51aba0c9f4097e4f6
> Author: Russell Currey 
> Date:   Thu Dec 15 16:12:41 2016 +1100
>
> drivers/gpu/drm/ast: Fix infinite loop if read fails

Cascardo, about the mentioned patch, it is already in this kernel, when I look 
at the changelog for linux-image-4.4.0-116-generic:
* Xenial update to v4.4.41 stable release (LP: #1655041)
- drivers/gpu/drm/ast: Fix infinite loop if read fails

And also this is not the only device that is hitting the EEH, when I
blacklisted the ast module I still see the EEH hitting the other slots
behind the PLX switch

I was able to collect a full dmesg output by adding the dmesg command to
the KDUMP_FAIL_CMD option, still no luck in getting it to drop to a
shell.

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

Title:
  dump is not captured in remote host when kdump over ssh is configured
  on firestone.

Status in The Ubuntu-power-systems project:
  Incomplete
Status in makedumpfile package in Ubuntu:
  New

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH  - 2017-03-07 
05:00:29 ==
  ---Problem Description---

  Ubuntu 17.04: dump is not captured in remote host when kdump over ssh
  is configured on firestone.

  ---Steps to Reproduce---

  1. Configure kdump.
  2. Check whether kdump is operational using ?# kdump-config show?.
  3. Install ?kernel-debuginfo? and ?kernel-debuginfo-common? rpms.
  4. Setup password less ssh connection, generate rsa key.
  # ssh-keygen -t rsa
  5. verify id_rsa and id_rsa.pub are created under /root/.ssh/
  6. Edit /etc/default/kdump-tools and add below entries.
  SSH="ubuntu@9.114.15.239"
  SSH_KEY=/root/.ssh/id_rsa
  7. Propagate RSA key.
  # kdump-config propagate
  8. Restart kdump service.
  # kdump-config load
  9. Trigger Crash using below commands.
  # echo "1" > /proc/sys/kernel/sysrq
  # echo "c" > /proc/sysrq-trigger
  10. Verify dump is available in remote server in configured path.

  Machine details
  ===

  $ ipmitool -I lanplus -H  9.47.70.3 -U ADMIN -P admin sol activate

  $ ssh ubuntu@9.47.70.29

  PW: shriya101

  
  Attaching logs

  == Comment: #1 - PAVITHRA R. PRAKASH  -
  2017-03-07 05:01:42 ==

  
  == Comment: #5 - PAVITHRA R. PRAKASH  - 2017-03-07 
23:19:46 ==
  Hi, 

  Attaching the logs.

  Network info:

  root@ltc-firep3:~# hwinfo --network
  36: None 00.0: 10700 Loopback   
[Created at net.126]
Unique ID: ZsBS.GQNx7L4uPNA
SysFS ID: /class/net/lo
Hardware Class: network interface
Model: "Loopback network interface"
Device File: lo
Link detected: yes
Config Status: cfg=new, avail=yes, need=no, active=unknown

  37: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: 2lHw.ndpeucax6V1
Parent ID: mIXc.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f2
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.2
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f2
HW Address: 98:be:94:03:18:4a
Permanent HW Address: 98:be:94:03:18:4a
Link detected: no
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #15 (Ethernet controller)

  38: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: 7Onn.ndpeucax6V1
Parent ID: sx0U.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f0
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.0
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f0
HW Address: 

[Kernel-packages] [Bug 1681909] Dmesg - Kdump failed attempt with Ubuntu 16.04

[bugproxy]

--- Comment (attachment only) From mu...@br.ibm.com 2018-03-06 11:18 
EDT---


** Attachment added: "Dmesg - Kdump failed attempt with Ubuntu 16.04"
   
https://bugs.launchpad.net/bugs/1681909/+attachment/5070860/+files/dmesg_kdump_ubuntu1604.txt

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

Title:
  dump is not captured in remote host when kdump over ssh is configured
  on firestone.

Status in The Ubuntu-power-systems project:
  Incomplete
Status in makedumpfile package in Ubuntu:
  New

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH  - 2017-03-07 
05:00:29 ==
  ---Problem Description---

  Ubuntu 17.04: dump is not captured in remote host when kdump over ssh
  is configured on firestone.

  ---Steps to Reproduce---

  1. Configure kdump.
  2. Check whether kdump is operational using ?# kdump-config show?.
  3. Install ?kernel-debuginfo? and ?kernel-debuginfo-common? rpms.
  4. Setup password less ssh connection, generate rsa key.
  # ssh-keygen -t rsa
  5. verify id_rsa and id_rsa.pub are created under /root/.ssh/
  6. Edit /etc/default/kdump-tools and add below entries.
  SSH="ubuntu@9.114.15.239"
  SSH_KEY=/root/.ssh/id_rsa
  7. Propagate RSA key.
  # kdump-config propagate
  8. Restart kdump service.
  # kdump-config load
  9. Trigger Crash using below commands.
  # echo "1" > /proc/sys/kernel/sysrq
  # echo "c" > /proc/sysrq-trigger
  10. Verify dump is available in remote server in configured path.

  Machine details
  ===

  $ ipmitool -I lanplus -H  9.47.70.3 -U ADMIN -P admin sol activate

  $ ssh ubuntu@9.47.70.29

  PW: shriya101

  
  Attaching logs

  == Comment: #1 - PAVITHRA R. PRAKASH  -
  2017-03-07 05:01:42 ==

  
  == Comment: #5 - PAVITHRA R. PRAKASH  - 2017-03-07 
23:19:46 ==
  Hi, 

  Attaching the logs.

  Network info:

  root@ltc-firep3:~# hwinfo --network
  36: None 00.0: 10700 Loopback   
[Created at net.126]
Unique ID: ZsBS.GQNx7L4uPNA
SysFS ID: /class/net/lo
Hardware Class: network interface
Model: "Loopback network interface"
Device File: lo
Link detected: yes
Config Status: cfg=new, avail=yes, need=no, active=unknown

  37: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: 2lHw.ndpeucax6V1
Parent ID: mIXc.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f2
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.2
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f2
HW Address: 98:be:94:03:18:4a
Permanent HW Address: 98:be:94:03:18:4a
Link detected: no
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #15 (Ethernet controller)

  38: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: 7Onn.ndpeucax6V1
Parent ID: sx0U.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f0
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.0
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f0
HW Address: 98:be:94:03:18:48
Permanent HW Address: 98:be:94:03:18:48
Link detected: yes
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #16 (Ethernet controller)

  39: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: VwX_.ndpeucax6V1
Parent ID: DUng.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f3
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.3
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f3
HW Address: 98:be:94:03:18:4b
Permanent HW Address: 98:be:94:03:18:4b
Link detected: no
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #25 (Ethernet controller)

  40: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: bZ1s.ndpeucax6V1
Parent ID: J7HY.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f1
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.1
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f1
HW Address: 98:be:94:03:18:49
Permanent HW Address: 98:be:94:03:18:49
Link detected: no
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #4 (Ethernet controller)
  root@ltc-firep3:~# 


  Thanks,
  Pavithra

  == Comment: #6 - PAVITHRA R. PRAKASH  -
  2017-03-07 23:20:47 ==

  
  == Comment: #7 - PAVITHRA R. PRAKASH 

[Kernel-packages] [Bug 1752350] Re: Bionic x86_64 Linux Kernel 4.15 fails to boot on Xen

[Johannes Krude]

@jsalibury, the Kernel you provided does successfully boot on Xen.

...
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to 
Xen)
(XEN) Freed 460kB init memory
mapping kernel into physical memory
about to get started...
[0.00] Linux version 4.15.0-10-generic (root@kathleen) (gcc version 
7.3.0 (Ubuntu 7.3.0-5ubuntu1)) #11~lp1752350 SMP Mon Mar 5 08:26:15 UTC 2018 
(Ubuntu 4.15.0-10.11~lp1752350-generic 4.15.3)
[0.00] Command line: placeholder root=/dev/mapper/vg-xen--nfo--dom0 ro 
rootflags=data=journal console=hvc0 console=tty0 kgdboc=hvc0 early_printk=xen 
ignore_loglevel
...

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

Title:
  Bionic x86_64 Linux Kernel 4.15 fails to boot on Xen

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

Bug description:
  The Linux Kernel 4.15 from bionic on x86_64 immediately crashes when
  booted as a dom0 under Xen.

  A similar bug was reported by someone else for archlinux
  (https://bugs.archlinux.org/task/57500).

  A patch exists for 4.16. I tried this patch on 4.15.0-10-generic, it
  fixes the problem for me.
  
(https://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git/patch/?id=4f277295e54c5b7340e48efea3fc5cc21a2872b7).

  Xen output:

  (XEN) Xen version 4.9.0 (Ubuntu 4.9.0-0ubuntu3) (stefan.ba...@canonical.com) 
(gcc (Ubuntu 7.2.0-8ubuntu2) 7.2.0) debug=n  Fri Oct 13 15:58:41 UTC 2017
  (XEN) Bootloader: GRUB 2.02~beta2-36ubuntu3.9
  (XEN) Command line: placeholder com1=115200,8N1 console=com1,vga
  (XEN) Xen image load base address: 0
  (XEN) Video information:
  (XEN)  VGA is text mode 80x25, font 8x16
  (XEN)  VBE/DDC methods: none; EDID transfer time: 0 seconds
  (XEN)  EDID info not retrieved because no DDC retrieval method detected
  (XEN) Disc information:
  (XEN)  Found 1 MBR signatures
  (XEN)  Found 1 EDD information structures
  (XEN) Xen-e820 RAM map:
  (XEN)   - 0009ec00 (usable)
  (XEN)  000f - 0010 (reserved)
  (XEN)  0010 - cb6cfc00 (usable)
  (XEN)  cb6cfc00 - cb723c00 (ACPI NVS)
  (XEN)  cb723c00 - cb725c00 (ACPI data)
  (XEN)  cb725c00 - cc00 (reserved)
  (XEN)  f800 - fc00 (reserved)
  (XEN)  fec0 - fed00400 (reserved)
  (XEN)  fed2 - feda (reserved)
  (XEN)  fee0 - fef0 (reserved)
  (XEN)  ffb0 - 0001 (reserved)
  (XEN)  0001 - 00013000 (usable)
  (XEN) New Xen image base address: 0xcb00
  (XEN) ACPI: RSDP 000FEC00, 0024 (r2 DELL  )
  (XEN) ACPI: XSDT 000FC7E7, 006C (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: FACP 000FC8D7, 00F4 (r3 DELLB11K  15 ASL61)
  (XEN) ACPI: DSDT FFDC89E4, 47BC (r1   DELLdt_ex 1000 INTL 20050624)
  (XEN) ACPI: FACS CB6CFC00, 0040
  (XEN) ACPI: SSDT FFDCD2C1, 00AC (r1   DELLst_ex 1000 INTL 20050624)
  (XEN) ACPI: APIC 000FC9CB, 0092 (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: BOOT 000FCA5D, 0028 (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: ASF! 000FCA85, 0096 (r32 DELLB11K  15 ASL61)
  (XEN) ACPI: MCFG 000FCB1B, 003E (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: HPET 000FCB59, 0038 (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: TCPA 000FCDB5, 0032 (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: DMAR 000FCDE7, 0068 (r1 DELLB11K  15 ASL61)
  (XEN) System RAM: 4022MB (4118964kB)
  (XEN) Domain heap initialised
  (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec0, GSI 0-23
  (XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
  (XEN) Using scheduler: SMP Credit Scheduler (credit)
  (XEN) Platform timer is 14.318MHz HPET
  (XEN) Detected 2926.007 MHz processor.
  (XEN) Initing memory sharing.
  (XEN) Intel VT-d iommu 0 supported page sizes: 4kB.
  (XEN) Intel VT-d Snoop Control enabled.
  (XEN) Intel VT-d Dom0 DMA Passthrough not enabled.
  (XEN) Intel VT-d Queued Invalidation enabled.
  (XEN) Intel VT-d Interrupt Remapping not enabled.
  (XEN) Intel VT-d Posted Interrupt not enabled.
  (XEN) Intel VT-d Shared EPT tables not enabled.
  (XEN) :04:00.0: unknown type 4
  (XEN) I/O virtualisation enabled
  (XEN)  - Dom0 mode: Relaxed
  (XEN) Interrupt remapping disabled
  (XEN) ENABLING IO-APIC IRQs
  (XEN)  -> Using new ACK method
  (XEN) Allocated console ring of 16 KiB.
  (XEN) VMX: Supported advanced features:
  (XEN)  - APIC MMIO access virtualisation
  (XEN)  - APIC TPR shadow
  (XEN)  - 

[Kernel-packages] [Bug 1722269] Re: No graphical boot with 4.4.0-96 or -116 and NVIDIA GeForce 840M

[YS1]

This is still happening with 4.4.0-116 !!

Here is the status of gpu-manager.service :

● gpu-manager.service - Detect the available GPUs and deal with any system 
changes
   Loaded: loaded (/lib/systemd/system/gpu-manager.service; enabled; vendor 
preset: enabled)
   Active: inactive (dead) since mar. 2018-03-06 17:24:02 CET; 2min 43s ago
  Process: 1400 ExecStart=/usr/bin/gpu-manager --log /var/log/gpu-manager.log 
(code=exited, status=0/SUCCESS)
 Main PID: 1400 (code=exited, status=0/SUCCESS)

mars 06 17:24:02 ysalm gpu-manager[1400]: /etc/modprobe.d is not a file
mars 06 17:24:02 ysalm gpu-manager[1400]: /etc/modprobe.d is not a file
mars 06 17:24:02 ysalm gpu-manager[1400]: /etc/modprobe.d is not a file
mars 06 17:24:02 ysalm gpu-manager[1400]: /etc/modprobe.d is not a file
mars 06 17:24:02 ysalm gpu-manager[1400]: update-alternatives: erreur: pas 
d'alternatives pour x86_64-linux-gnu_gfxcore_conf
mars 06 17:24:02 ysalm gpu-manager[1400]: modprobe: ERROR: could not insert 
'bbswitch': No such device
mars 06 17:24:02 ysalm gpu-manager[1400]: modprobe: ERROR: could not insert 
'bbswitch': No such device
mars 06 17:24:02 ysalm systemd[1]: Started Detect the available GPUs and deal 
with any system changes.
mars 06 17:24:03 ysalm systemd[1]: gpu-manager.service: Start request repeated 
too quickly.
mars 06 17:24:03 ysalm systemd[1]: Failed to start Detect the available GPUs 
and deal with any system changes.

** Summary changed:

- No graphical boot with 4.4.0-96 and NVIDIA GeForce 840M
+ No graphical boot with 4.4.0-96 or -116 and NVIDIA GeForce 840M

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

Title:
  No graphical boot with 4.4.0-96 or -116 and NVIDIA GeForce 840M

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My computer (using XUbuntu 16.04) boots and works normally with kernel
  4.4.0-92 but upgrading to 4.4.0-96 prevents lightdm from starting. In
  fact, the GPU detection service fails.

  The problem also appears with proposed 4.4.0-97.

  I tested with mainline kernel 4.13. It boots to lightdm but it is
  difficult to exactly tell what happens as some modules for my hardware
  were not found/compiled/installed (as a result, I cannot connect to
  wifi with this kernel).

  GPU is GEForce 840M with proprietary nvidia 475 drivers (purged and
  reinstalled once).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-92-generic 4.4.0-92.115
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  NonfreeKernelModules: wl nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  yann   1476 F pulseaudio
   /dev/snd/controlC0:  yann   1476 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct  9 15:40:16 2017
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (448 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-92-generic N/A
   linux-backports-modules-4.4.0-92-generic  N/A
   linux-firmware1.157.12
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0NC6G7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/05/2017:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0NC6G7:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yann   1438 F pulseaudio
   /dev/snd/controlC1:  yann   1438 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (450 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-97-generic N/A
   

[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions

[Nobuto Murata]

v4.12-rc1 with i40e 2.1.7 - bad
v4.12 with i40e 2.1.14 - good

I'm running out of time. So more bisections are for tomorrow.

** Attachment added: "bond_check_xenial_mainline_4.12-rc1.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5070861/+files/bond_check_xenial_mainline_4.12-rc1.log

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

Title:
  [i40e] LACP bonding start up race conditions

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

Bug description:
  When provisioning Ubuntu servers with MAAS at once, some bonding pairs
  will have unexpected LACP status such as "Expired". It randomly
  happens at each provisioning with the default xenial kernel(4.4), but
  not reproducible with HWE kernel(4.13). I'm using Intel X710 cards
  (Dell-branded).

  Using the HWE kernel works as a workaround for short term, but it's
  not ideal since 4.13 is not covered by Canonical Livepatch service.

  How to reproduce:
  1. configure LACP bonding with MAAS
  2. provision machines
  3. check the bonding status in /proc/net/bonding/bond*

  frequency of occurrence:
  About 5 bond pairs in 22 pairs at each provisioning.

  [reproducible combination]
  $ uname -a
  Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 1.4.25-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  [non-reproducible combination]
  $ uname -a
  Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 2.1.14-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-116-generic 4.4.0-116.140
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  6 06:37 seq
   crw-rw 1 root audio 116, 33 Mar  6 06:37 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Mar  6 06:46:32 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R730
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed 
root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 
console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-116-generic N/A
   linux-backports-modules-4.4.0-116-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/16/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.5
  dmi.board.name: 072T6D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.asset.tag: 0018880
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R730
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1745349] Re: Hard lockup during boot with linux-image-4.4.0-112-generic

[Mike Turner]

That one (e233e...) failed.

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

Title:
  Hard lockup during boot with linux-image-4.4.0-112-generic

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

Bug description:
  Systems on ASUS H110M-C Boards don't boot here with Kernel 4.4.0-112
  instead they show

  NMI watchdog: Watchdog detected hard lockup on cpu 0
  NMI watchdog: Watchdog detected hard lockup on cpu 1
  NMI watchdog: Watchdog detected hard lockup on cpu 3
  NMI watchdog: Watchdog detected hard lockup on cpu 2

  I cannot provide any logs of course.

  Booting with 4.4.0-109 works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lr3200 2013 F pulseaudio
  Date: Thu Jan 25 11:38:55 2018
  HibernationDevice: RESUME=UUID=8e35131d-6d40-4f4f-a3db-c7336e72cbce
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   enp3s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
root=UUID=4dc5bb0a-ab7c-48fa-ac23-bcdf23755d93 ro
  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.4.0-109-generic N/A
   linux-backports-modules-4.4.0-109-generic  N/A
   linux-firmware 1.157.15
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3601
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-C
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3601:bd12/12/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-C:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1752350] Re: Bionic x86_64 Linux Kernel 4.15 fails to boot on Xen

[Alejandro Mery]

I wanted to mention that installing v4.16-rc4 from
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc4/ solved the
problem for me.

# uname -a
Linux de2 4.16.0-041600rc4-generic #201803041930 SMP Mon Mar 5 00:32:34 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
# dmesg | grep Xen
...
[0.00] Hypervisor detected: Xen PV
[0.00] Setting APIC routing to Xen PV.
[0.00] Booting paravirtualized kernel on Xen
[0.00] Xen version: 4.9.0 (preserve-AD)
[0.004000] Xen: using vcpuop timer interface

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

Title:
  Bionic x86_64 Linux Kernel 4.15 fails to boot on Xen

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

Bug description:
  The Linux Kernel 4.15 from bionic on x86_64 immediately crashes when
  booted as a dom0 under Xen.

  A similar bug was reported by someone else for archlinux
  (https://bugs.archlinux.org/task/57500).

  A patch exists for 4.16. I tried this patch on 4.15.0-10-generic, it
  fixes the problem for me.
  
(https://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git/patch/?id=4f277295e54c5b7340e48efea3fc5cc21a2872b7).

  Xen output:

  (XEN) Xen version 4.9.0 (Ubuntu 4.9.0-0ubuntu3) (stefan.ba...@canonical.com) 
(gcc (Ubuntu 7.2.0-8ubuntu2) 7.2.0) debug=n  Fri Oct 13 15:58:41 UTC 2017
  (XEN) Bootloader: GRUB 2.02~beta2-36ubuntu3.9
  (XEN) Command line: placeholder com1=115200,8N1 console=com1,vga
  (XEN) Xen image load base address: 0
  (XEN) Video information:
  (XEN)  VGA is text mode 80x25, font 8x16
  (XEN)  VBE/DDC methods: none; EDID transfer time: 0 seconds
  (XEN)  EDID info not retrieved because no DDC retrieval method detected
  (XEN) Disc information:
  (XEN)  Found 1 MBR signatures
  (XEN)  Found 1 EDD information structures
  (XEN) Xen-e820 RAM map:
  (XEN)   - 0009ec00 (usable)
  (XEN)  000f - 0010 (reserved)
  (XEN)  0010 - cb6cfc00 (usable)
  (XEN)  cb6cfc00 - cb723c00 (ACPI NVS)
  (XEN)  cb723c00 - cb725c00 (ACPI data)
  (XEN)  cb725c00 - cc00 (reserved)
  (XEN)  f800 - fc00 (reserved)
  (XEN)  fec0 - fed00400 (reserved)
  (XEN)  fed2 - feda (reserved)
  (XEN)  fee0 - fef0 (reserved)
  (XEN)  ffb0 - 0001 (reserved)
  (XEN)  0001 - 00013000 (usable)
  (XEN) New Xen image base address: 0xcb00
  (XEN) ACPI: RSDP 000FEC00, 0024 (r2 DELL  )
  (XEN) ACPI: XSDT 000FC7E7, 006C (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: FACP 000FC8D7, 00F4 (r3 DELLB11K  15 ASL61)
  (XEN) ACPI: DSDT FFDC89E4, 47BC (r1   DELLdt_ex 1000 INTL 20050624)
  (XEN) ACPI: FACS CB6CFC00, 0040
  (XEN) ACPI: SSDT FFDCD2C1, 00AC (r1   DELLst_ex 1000 INTL 20050624)
  (XEN) ACPI: APIC 000FC9CB, 0092 (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: BOOT 000FCA5D, 0028 (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: ASF! 000FCA85, 0096 (r32 DELLB11K  15 ASL61)
  (XEN) ACPI: MCFG 000FCB1B, 003E (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: HPET 000FCB59, 0038 (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: TCPA 000FCDB5, 0032 (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: DMAR 000FCDE7, 0068 (r1 DELLB11K  15 ASL61)
  (XEN) System RAM: 4022MB (4118964kB)
  (XEN) Domain heap initialised
  (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec0, GSI 0-23
  (XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
  (XEN) Using scheduler: SMP Credit Scheduler (credit)
  (XEN) Platform timer is 14.318MHz HPET
  (XEN) Detected 2926.007 MHz processor.
  (XEN) Initing memory sharing.
  (XEN) Intel VT-d iommu 0 supported page sizes: 4kB.
  (XEN) Intel VT-d Snoop Control enabled.
  (XEN) Intel VT-d Dom0 DMA Passthrough not enabled.
  (XEN) Intel VT-d Queued Invalidation enabled.
  (XEN) Intel VT-d Interrupt Remapping not enabled.
  (XEN) Intel VT-d Posted Interrupt not enabled.
  (XEN) Intel VT-d Shared EPT tables not enabled.
  (XEN) :04:00.0: unknown type 4
  (XEN) I/O virtualisation enabled
  (XEN)  - Dom0 mode: Relaxed
  (XEN) Interrupt remapping disabled
  (XEN) ENABLING IO-APIC IRQs
  (XEN)  -> Using new ACK method
  (XEN) Allocated console ring of 16 KiB.
  (XEN) VMX: Supported advanced features:
  (XEN)  - APIC MMIO access virtualisation
  (XEN)  - APIC TPR shadow
  (XEN)  - Extended Page Tables (EPT)
  (XEN)  - Virtual-Processor Identifiers (VPID)
  (XEN)  - Virtual NMI
  (XEN)  - MSR direct-access bitmap
  (XEN) HVM: ASIDs enabled.
  (XEN) HVM: VMX enabled
  (XEN) HVM: Hardware Assisted Paging (HAP) detected
  (XEN) HVM: HAP page sizes: 4kB, 2MB
  (XEN) Brought up 4 CPUs
  (XEN) 

[Kernel-packages] [Bug 1751834] Re: Power9 DD 2.2 needs HMI fixup backport of upstream patch(d075745d893c78730e4a3b7a60fca23c2f764081) into kernel

[Manoj Iyer]

** Changed in: ubuntu-power-systems
   Status: Fix Committed => Triaged

** Tags removed: triage-g
** Tags added: triage-r

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

Title:
  Power9 DD 2.2 needs HMI fixup backport of upstream
  patch(d075745d893c78730e4a3b7a60fca23c2f764081) into kernel

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

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2018-02-23 
06:55:23 ==
  ---Problem Description---
  Power9 DD 2.2 needs HMI fixup backport of upstream 
patch(d075745d893c78730e4a3b7a60fca23c2f764081) into kernel
   
  ---uname output---
  4.15.0-10-generic
   
  Machine Type = power9 boston 2.2 (pvr 004e 1202) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   commit d075745d893c78730e4a3b7a60fca23c2f764081
  Author: Paul Mackerras 
  Date:   Wed Jan 17 20:51:13 2018 +1100

  KVM: PPC: Book3S HV: Improve handling of debug-trigger HMIs on POWER9
  

  Dependancy commit, looks like already present.
  commit 5080332c2c893118dbc18755f35c8b0131cf0fc4
  Author: Michael Neuling 
  Date:   Fri Sep 15 15:25:48 2017 +1000

  powerpc/64s: Add workaround for P9 vector CI load issue
  

   
  Contact Information = sathe...@in.ibm.com 
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for sathe...@in.ibm.com: 
  -Attach sysctl -a output output to the bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1751834/+subscriptions

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

[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions

[Joseph Salisbury]

If v4.12-rc1 is still bad, we would need to test some of the other
release candidates, such as rc2, rc3, rc4, etc.

Once we have the last bad and first good, I'll start the reverse bisect
and build a kernel.

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

Title:
  [i40e] LACP bonding start up race conditions

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

Bug description:
  When provisioning Ubuntu servers with MAAS at once, some bonding pairs
  will have unexpected LACP status such as "Expired". It randomly
  happens at each provisioning with the default xenial kernel(4.4), but
  not reproducible with HWE kernel(4.13). I'm using Intel X710 cards
  (Dell-branded).

  Using the HWE kernel works as a workaround for short term, but it's
  not ideal since 4.13 is not covered by Canonical Livepatch service.

  How to reproduce:
  1. configure LACP bonding with MAAS
  2. provision machines
  3. check the bonding status in /proc/net/bonding/bond*

  frequency of occurrence:
  About 5 bond pairs in 22 pairs at each provisioning.

  [reproducible combination]
  $ uname -a
  Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 1.4.25-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  [non-reproducible combination]
  $ uname -a
  Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 2.1.14-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-116-generic 4.4.0-116.140
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  6 06:37 seq
   crw-rw 1 root audio 116, 33 Mar  6 06:37 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Mar  6 06:46:32 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R730
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed 
root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 
console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-116-generic N/A
   linux-backports-modules-4.4.0-116-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/16/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.5
  dmi.board.name: 072T6D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.asset.tag: 0018880
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R730
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://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 1745464] Re: Random reboots with 4.13.0-26 on Ubuntu 16.04 LTS

[Joseph Hom]

Jim/Christine,

Please look into this.


From:   Joseph Salisbury 
To: j...@us.ibm.com
Date:   03/06/2018 09:27 AM
Subject:[Bug 1745464] Re: Random reboots with 4.13.0-26 on Ubuntu 16.04
LTS
Sent by:boun...@canonical.com


Would it be possible for you to test the latest upstream kernel? Refer
to
https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.ubuntu.com_KernelMainlineBuilds=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=CJEdoL-rwJef2imkYZDMTg=kWOu479yyXgkYCuA3cjtxYr1u6gJZ912yJG8rtvZBoE=Hkhru8wewXVpuBhsvhsmjA_AlIiovjnjQ0Et9aYrFJs=
 . Please test the latest
v4.16 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0]
https://urldefense.proofpoint.com/v2/url?u=http-3A__kernel.ubuntu.com_-7Ekernel-2Dppa_mainline_v4.16-2Drc4=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=CJEdoL-rwJef2imkYZDMTg=kWOu479yyXgkYCuA3cjtxYr1u6gJZ912yJG8rtvZBoE=JsIbFNx75DnKSRHgrmeQdjz90X8oRKZ83ZRBooxKtUE=


--
You received this bug notification because you are subscribed to the bug
report.
https://urldefense.proofpoint.com/v2/url?u=https-3A__bugs.launchpad.net_bugs_1745464=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=CJEdoL-rwJef2imkYZDMTg=kWOu479yyXgkYCuA3cjtxYr1u6gJZ912yJG8rtvZBoE=rH79xWtZ5MQfW7JXfx3w5wslTCRv9yOwF0WXYvpEDok=


Title:
  Random reboots with 4.13.0-26 on Ubuntu 16.04 LTS

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

Bug description:
  After installing kernel 4.13.0-26 (and 4.13.0-31) we are seeing random
reboots on virtual machines (VSIs) hosted by SoftLayer.  The physical hosts
were patched earlier this month but I don't have the details yet or access
to the hypervisors.  We noticed 4.13.0-31 was rebooting frequently and went
to 4.13.0-26 instead which was performing better but still suffering from
the random reboots.  The VMs still on the old 4.4 kernels haven't had any
random reboots at all.  We don't have any intel-microcode package
installed, and I'm not sure it would make a difference for VMs...?  We have
seen this on both Broadwell and Haswell systems.  The attached apport file
is from one of the Broadwell servers.
  ---
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 25 11:43 seq
   crw-rw 1 root audio 116, 33 Jan 25 11:43 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci:

  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  ProcFB:

  ProcKernelCmdLine: root=UUID=52c6959b-79b0-4bdd-8ed6-71e0ba782fb4 ro
console=hvc0 elevator=noop
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-26-generic N/A
   linux-backports-modules-4.13.0-26-generic  N/A
   linux-firmware 1.157.8
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images xenial uec-images xenial uec-images
  Uname: Linux 4.13.0-26-generic x86_64
  UnreportableReason: The report belongs to a package that is not
installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: False

To manage notifications about this bug go to:
https://urldefense.proofpoint.com/v2/url?u=https-3A__bugs.launchpad.net_ubuntu_-2Bsource_linux_-2Bbug_1745464_-2Bsubscriptions=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=CJEdoL-rwJef2imkYZDMTg=kWOu479yyXgkYCuA3cjtxYr1u6gJZ912yJG8rtvZBoE=w38S0BUJHIZmWhFC3e1J8SCsujRITGKrrMCb2xxiND0=



** Attachment added: "graycol.gif"
   
https://bugs.launchpad.net/bugs/1745464/+attachment/5070834/+files/graycol.gif

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

Title:
  Random reboots with 4.13.0-26 on Ubuntu 16.04 LTS

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

Bug description:
  After installing kernel 4.13.0-26 (and 4.13.0-31) we are seeing random 
reboots on virtual machines (VSIs) hosted by SoftLayer.  The physical hosts 
were patched earlier this month but I don't have the details yet or access to 
the hypervisors.  We noticed 4.13.0-31 was rebooting frequently and went to 
4.13.0-26 instead which was performing better but still suffering from the 
random reboots.  The 

[Kernel-packages] [Bug 1752101] Re: linux-gcp: 4.15.0-1001.1 -proposed tracker

[Brad Figg]

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

** Description changed:

  This bug is for tracking the 4.15.0-1001.1 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: Uploaded
+ kernel-phase:Promoted to proposed
+ kernel-phase-changed:Tuesday, 06. March 2018 16:00 UTC

** Description changed:

  This bug is for tracking the 4.15.0-1001.1 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: Uploaded
- kernel-phase:Promoted to proposed
- kernel-phase-changed:Tuesday, 06. March 2018 16:00 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux-gcp: 4.15.0-1001.1 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Confirmed
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Invalid
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New

Bug description:
  This bug is for tracking the 4.15.0-1001.1 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: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions

[Nobuto Murata]

v4.11 with i40e 1.6.27 - bad
v4.12 with i40e 2.1.14 - good

next: v4.12-rc1 with i40e 2.1.7 - ?

** Attachment added: "bond_check_xenial_mainline_4.12.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5070835/+files/bond_check_xenial_mainline_4.12.log

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

Title:
  [i40e] LACP bonding start up race conditions

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

Bug description:
  When provisioning Ubuntu servers with MAAS at once, some bonding pairs
  will have unexpected LACP status such as "Expired". It randomly
  happens at each provisioning with the default xenial kernel(4.4), but
  not reproducible with HWE kernel(4.13). I'm using Intel X710 cards
  (Dell-branded).

  Using the HWE kernel works as a workaround for short term, but it's
  not ideal since 4.13 is not covered by Canonical Livepatch service.

  How to reproduce:
  1. configure LACP bonding with MAAS
  2. provision machines
  3. check the bonding status in /proc/net/bonding/bond*

  frequency of occurrence:
  About 5 bond pairs in 22 pairs at each provisioning.

  [reproducible combination]
  $ uname -a
  Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 1.4.25-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  [non-reproducible combination]
  $ uname -a
  Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 2.1.14-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-116-generic 4.4.0-116.140
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  6 06:37 seq
   crw-rw 1 root audio 116, 33 Mar  6 06:37 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Mar  6 06:46:32 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R730
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed 
root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 
console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-116-generic N/A
   linux-backports-modules-4.4.0-116-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/16/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.5
  dmi.board.name: 072T6D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.asset.tag: 0018880
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R730
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1734130] Re: [18.04 FEAT] Add kvm_stat from kernel tree

[Frank Heimes]

Please make sure that the updates/patches to that script do not break python3 
compatibility
and that the script stays kernel independent. 
Potentially new python scripts to be shipped should be python3 (compatible).

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

Title:
  [18.04 FEAT] Add kvm_stat from kernel tree

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Improves RAS characterics of systems running KVM by providing kvm_stat script:
  https://github.com/torvalds/linux/tree/master/tools/kvm/kvm_stat

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1734130/+subscriptions

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

[Kernel-packages] [Bug 1745349] Re: Hard lockup during boot with linux-image-4.4.0-112-generic

[Joseph Salisbury]

I built the next test kernel, up to the following commit:
e233ec086ab77c1fc5714368e93a0d6c99d92226

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1745349

Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on your test results.

Thanks in advance

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

Title:
  Hard lockup during boot with linux-image-4.4.0-112-generic

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

Bug description:
  Systems on ASUS H110M-C Boards don't boot here with Kernel 4.4.0-112
  instead they show

  NMI watchdog: Watchdog detected hard lockup on cpu 0
  NMI watchdog: Watchdog detected hard lockup on cpu 1
  NMI watchdog: Watchdog detected hard lockup on cpu 3
  NMI watchdog: Watchdog detected hard lockup on cpu 2

  I cannot provide any logs of course.

  Booting with 4.4.0-109 works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lr3200 2013 F pulseaudio
  Date: Thu Jan 25 11:38:55 2018
  HibernationDevice: RESUME=UUID=8e35131d-6d40-4f4f-a3db-c7336e72cbce
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   enp3s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
root=UUID=4dc5bb0a-ab7c-48fa-ac23-bcdf23755d93 ro
  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.4.0-109-generic N/A
   linux-backports-modules-4.4.0-109-generic  N/A
   linux-firmware 1.157.15
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3601
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-C
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3601:bd12/12/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-C:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1400463] Re: [Medion Akoya P2214T] Touchpad not properly recognized

[Full Name]

everlasting bug

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

Title:
  [Medion Akoya P2214T] Touchpad not properly recognized

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The ELAN (not Elantech) touchpad in my Medion Akoya P2214T (MD 99430)
  laptop/tablet hybrid is not properly recognized. Both the touchscreen
  and the touchpad function as a regular mouse, but the touchpad shows
  up as an ITE Tech. Inc. ITE Device(8910) pointer in xinput (see
  attachment). Multitouch and scrolling however, do not function, nor do
  options for this show up in the Mouse & Touchpad options in Ubuntu
  14.10 64-bit.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xserver-xorg-input-synaptics 1.8.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Dec  8 20:02:14 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  InstallationDate: Installed on 2014-11-12 (26 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Medion Akoya P2214T
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=06056019-c592-4d2d-9738-54e729126d7d ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/26/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 205
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Akoya P2214T
  dmi.board.vendor: Medion
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Medion
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr205:bd08/26/2014:svnMedion:pnAkoyaP2214T:pvr1.0:rvnMedion:rnAkoyaP2214T:rvr1.0:cvnMedion:ct8:cvrToBeFilledByO.E.M.:
  dmi.product.name: Akoya P2214T
  dmi.product.version: 1.0
  dmi.sys.vendor: Medion
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Mon Dec  8 18:30:57 2014
  xserver.configfile: default
  xserver.errors:
   Error loading keymap 
/var/lib/xkb/server-992DCD2811F9928D990F91F3229E52A1EC62B72A.xkm
   Error loading keymap 
/var/lib/xkb/server-992DCD2811F9928D990F91F3229E52A1EC62B72A.xkm
   Error loading keymap 
/var/lib/xkb/server-992DCD2811F9928D990F91F3229E52A1EC62B72A.xkm
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12637
   vendor AUO
  xserver.version: 2:1.16.0-1ubuntu1
  --- 
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mizuti 2439 F pulseaudio
  CRDA:
   country EU:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=325a292a-ad2c-493d-b148-aff85b17b41e
  InstallationDate: Installed on 2015-10-15 (616 days ago)
  InstallationMedia: Linux Mint 17.2 "Rafaela" - Release amd64 20150627
  MachineType: Medion Akoya P2214T
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=727a143b-7e46-4f81-8cc9-c37b396d582e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-24-generic N/A
   linux-backports-modules-3.16.0-24-generic  N/A
   linux-firmware 1.127.23
  Tags:  rafaela
  Uname: Linux 3.16.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/13/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 702
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Akoya P2214T
  dmi.board.vendor: Medion
  dmi.board.version: 1.0
  

[Kernel-packages] [Bug 1752912] Re: bionic-proposed block to publish supported kernels in main

[Steve Langasek]

** No longer affects: linux-azure (Ubuntu)

** No longer affects: linux-gke (Ubuntu)

** No longer affects: linux-hwe (Ubuntu)

** No longer affects: linux-kvm (Ubuntu)

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

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

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

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

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

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

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

Title:
  bionic-proposed block to publish supported kernels in main

Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-meta-aws package in Ubuntu:
  Invalid
Status in linux-meta-azure package in Ubuntu:
  Invalid
Status in linux-meta-gke package in Ubuntu:
  Invalid
Status in linux-meta-hwe package in Ubuntu:
  Invalid
Status in linux-meta-kvm package in Ubuntu:
  Invalid

Bug description:
  bionic-proposed block to publish supported kernels in main

  The following kernels should be available, installable, and in main,
  in bionic.

  linux-aws
  linux-azure
  linux-gke
  linux-hwe
  linux-kvm

  Once all of these are published, with their metas, and are actually
  installable, this bug can be closed to trigger migration into the
  release pocket.

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

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

[Kernel-packages] [Bug 1745349] Re: Hard lockup during boot with linux-image-4.4.0-112-generic

[Lars Behrens]

Yay!

Three boots in a row worked with
linux-image-4.4.0-110-generic_4.4.0-110.133~lp1745349Commit7de295e2a47849_amd64

Was only able to test on one machine though, all my users are logged in.
More testing tomorrow.

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

Title:
  Hard lockup during boot with linux-image-4.4.0-112-generic

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

Bug description:
  Systems on ASUS H110M-C Boards don't boot here with Kernel 4.4.0-112
  instead they show

  NMI watchdog: Watchdog detected hard lockup on cpu 0
  NMI watchdog: Watchdog detected hard lockup on cpu 1
  NMI watchdog: Watchdog detected hard lockup on cpu 3
  NMI watchdog: Watchdog detected hard lockup on cpu 2

  I cannot provide any logs of course.

  Booting with 4.4.0-109 works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lr3200 2013 F pulseaudio
  Date: Thu Jan 25 11:38:55 2018
  HibernationDevice: RESUME=UUID=8e35131d-6d40-4f4f-a3db-c7336e72cbce
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   enp3s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
root=UUID=4dc5bb0a-ab7c-48fa-ac23-bcdf23755d93 ro
  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.4.0-109-generic N/A
   linux-backports-modules-4.4.0-109-generic  N/A
   linux-firmware 1.157.15
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3601
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-C
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3601:bd12/12/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-C:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1752101] Packages outside of proper component

[Brad Figg]

The following packages ended up in the wrong component in the -proposed
pocket:

linux-cloud-tools-gcp 4.15.0.1001.2 - is in universe instead of main
linux-cloud-tools-gke 4.15.0.1001.2 - is in universe instead of main
linux-gcp 4.15.0.1001.2 - is in universe instead of main
linux-gke 4.15.0.1001.2 - is in universe instead of main
linux-headers-gcp 4.15.0.1001.2 - is in universe instead of main
linux-headers-gke 4.15.0.1001.2 - is in universe instead of main
linux-image-gcp 4.15.0.1001.2 - is in universe instead of main
linux-image-gke 4.15.0.1001.2 - is in universe instead of main
linux-tools-gcp 4.15.0.1001.2 - is in universe instead of main
linux-tools-gke 4.15.0.1001.2 - is in universe instead of main

Once this is fixed, set the promote-to-proposed to Fix Released again

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

Title:
  linux-gcp: 4.15.0-1001.1 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Confirmed
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Invalid
Status in Kernel Development Workflow promote-to-proposed series:
  Incomplete
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New

Bug description:
  This bug is for tracking the 4.15.0-1001.1 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: Uploaded

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

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

[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions

[Nobuto Murata]

Not reproducible with 4.13-rc1 with 5 reboots.

4.10 - bad
4.11 - bad
4.13-rc1 - good

The next is 4.12.

** Attachment added: "bond_check_xenial_mainline_4.13-rc1.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5070827/+files/bond_check_xenial_mainline_4.13-rc1.log

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

Title:
  [i40e] LACP bonding start up race conditions

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

Bug description:
  When provisioning Ubuntu servers with MAAS at once, some bonding pairs
  will have unexpected LACP status such as "Expired". It randomly
  happens at each provisioning with the default xenial kernel(4.4), but
  not reproducible with HWE kernel(4.13). I'm using Intel X710 cards
  (Dell-branded).

  Using the HWE kernel works as a workaround for short term, but it's
  not ideal since 4.13 is not covered by Canonical Livepatch service.

  How to reproduce:
  1. configure LACP bonding with MAAS
  2. provision machines
  3. check the bonding status in /proc/net/bonding/bond*

  frequency of occurrence:
  About 5 bond pairs in 22 pairs at each provisioning.

  [reproducible combination]
  $ uname -a
  Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 1.4.25-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  [non-reproducible combination]
  $ uname -a
  Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 2.1.14-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-116-generic 4.4.0-116.140
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  6 06:37 seq
   crw-rw 1 root audio 116, 33 Mar  6 06:37 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Mar  6 06:46:32 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R730
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed 
root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 
console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-116-generic N/A
   linux-backports-modules-4.4.0-116-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/16/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.5
  dmi.board.name: 072T6D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.asset.tag: 0018880
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R730
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1681909] Re: dump is not captured in remote host when kdump over ssh is configured on firestone.

[Thadeu Lima de Souza Cascardo]

Looking at the log, I noticed the EEH is frozen right after finding the
Broadcom card. Is that one the tg3?

[  OK  ] Found device NetXtreme BCM5719 Gigabit Ethernet PCIe.
[8.191135] EEH: Frozen PE#7 on PHB#21 detected
[8.191280] EEH: PE location: S00210f, PHB location: N/A

Also, the recovery problem seems to be caused by ast.

[   18.267005] EEH: 210 reads ignored for recovering device at 
location=S00210f driver=ast pci addr=0021:10:00.0
[   18.267334] EEH: Might be infinite loop in ast driver

Looking at the upstream logs, one commit came up. Can you open a new bug
for it?

commit 298360af3dab45659810fdc51aba0c9f4097e4f6
Author: Russell Currey 
Date:   Thu Dec 15 16:12:41 2016 +1100

drivers/gpu/drm/ast: Fix infinite loop if read fails

ast_get_dram_info() configures a window in order to access BMC memory.
A BMC register can be configured to disallow this, and if so, causes
an infinite loop in the ast driver which renders the system unusable.

Fix this by erroring out if an error is detected.  On powerpc systems with
EEH, this leads to the device being fenced and the system continuing to
operate.

Cc:  # 3.10+
Signed-off-by: Russell Currey 
Reviewed-by: Joel Stanley 
Signed-off-by: Daniel Vetter 
Link: 
http://patchwork.freedesktop.org/patch/msgid/20161215051241.20815-1-rus...@russell.cc

diff --git a/drivers/gpu/drm/ast/ast_main.c b/drivers/gpu/drm/ast/ast_main.c
index 904beaa932d03..f75c6421db623 100644
--- a/drivers/gpu/drm/ast/ast_main.c
+++ b/drivers/gpu/drm/ast/ast_main.c
@@ -223,7 +223,8 @@ static int ast_get_dram_info(struct drm_device *dev)
ast_write32(ast, 0x1, 0xfc600309);
 
do {
-   ;
+   if (pci_channel_offline(dev->pdev))
+   return -EIO;
} while (ast_read32(ast, 0x1) != 0x01);
data = ast_read32(ast, 0x10004);
 
@@ -428,7 +429,9 @@ int ast_driver_load(struct drm_device *dev, unsigned long 
flags)
ast_detect_chip(dev, _post);
 
if (ast->chip != AST1180) {
-   ast_get_dram_info(dev);
+   ret = ast_get_dram_info(dev);

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

Title:
  dump is not captured in remote host when kdump over ssh is configured
  on firestone.

Status in The Ubuntu-power-systems project:
  Incomplete
Status in makedumpfile package in Ubuntu:
  New

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH  - 2017-03-07 
05:00:29 ==
  ---Problem Description---

  Ubuntu 17.04: dump is not captured in remote host when kdump over ssh
  is configured on firestone.

  ---Steps to Reproduce---

  1. Configure kdump.
  2. Check whether kdump is operational using ?# kdump-config show?.
  3. Install ?kernel-debuginfo? and ?kernel-debuginfo-common? rpms.
  4. Setup password less ssh connection, generate rsa key.
  # ssh-keygen -t rsa
  5. verify id_rsa and id_rsa.pub are created under /root/.ssh/
  6. Edit /etc/default/kdump-tools and add below entries.
  SSH="ubuntu@9.114.15.239"
  SSH_KEY=/root/.ssh/id_rsa
  7. Propagate RSA key.
  # kdump-config propagate
  8. Restart kdump service.
  # kdump-config load
  9. Trigger Crash using below commands.
  # echo "1" > /proc/sys/kernel/sysrq
  # echo "c" > /proc/sysrq-trigger
  10. Verify dump is available in remote server in configured path.

  Machine details
  ===

  $ ipmitool -I lanplus -H  9.47.70.3 -U ADMIN -P admin sol activate

  $ ssh ubuntu@9.47.70.29

  PW: shriya101

  
  Attaching logs

  == Comment: #1 - PAVITHRA R. PRAKASH  -
  2017-03-07 05:01:42 ==

  
  == Comment: #5 - PAVITHRA R. PRAKASH  - 2017-03-07 
23:19:46 ==
  Hi, 

  Attaching the logs.

  Network info:

  root@ltc-firep3:~# hwinfo --network
  36: None 00.0: 10700 Loopback   
[Created at net.126]
Unique ID: ZsBS.GQNx7L4uPNA
SysFS ID: /class/net/lo
Hardware Class: network interface
Model: "Loopback network interface"
Device File: lo
Link detected: yes
Config Status: cfg=new, avail=yes, need=no, active=unknown

  37: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: 2lHw.ndpeucax6V1
Parent ID: mIXc.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f2
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.2
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f2
HW Address: 98:be:94:03:18:4a
Permanent HW Address: 98:be:94:03:18:4a
Link detected: no
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #15 (Ethernet controller)

  38: None 

[Kernel-packages] [Bug 1750245] Re: i915 kbl_guc_ver9_14.bin does not load

[Seth Forshee]

Closing invalid as the cause appears to have been local file corruption.

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

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

Title:
  i915 kbl_guc_ver9_14.bin does not load

Status in linux-firmware package in Ubuntu:
  Invalid

Bug description:
  The provided i915/kbl_guc_ver9_14.bin does not load when configured to
  do so . If the file is replaced by manually installing with the
  included script from 01.org, it loads properly:
  https://01.org/linuxgraphics/downloads/kabylake-guc-9.14

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

  After:
  GuC firmware status:
  path: i915/kbl_guc_ver9_14.bin
  fetch: SUCCESS
  load: SUCCESS
  version wanted: 9.14
  version found: 9.14
  header: offset is 0; size = 128
  uCode: offset is 128; size = 142272
  RSA: offset is 142400; size = 256

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

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

[Kernel-packages] [Bug 1681909] Re: dump is not captured in remote host when kdump over ssh is configured on firestone.

[Thadeu Lima de Souza Cascardo]

Hi, Murilo.

Can you test it on 16.04 using kdump-tools from xenial-proposed? Maybe
the noirqdistrib option might be related to the EEH issues.

As this was reported to 17.04, and I don't know why there was a problem
with the network, we don't know if it was something that needed fixing
in the driver instead of kdump. And, then, looking at the xenial 4.4
kernel, we could maybe see if the issue has been fixed in latest
kernels, but still affects it.

If you continue hitting the EEH when using noirqdistrib (with kdump-
tools from -proposed), then we might look into that, with a different
bug.

Thanks.
Cascardo.

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

Title:
  dump is not captured in remote host when kdump over ssh is configured
  on firestone.

Status in The Ubuntu-power-systems project:
  Incomplete
Status in makedumpfile package in Ubuntu:
  New

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH  - 2017-03-07 
05:00:29 ==
  ---Problem Description---

  Ubuntu 17.04: dump is not captured in remote host when kdump over ssh
  is configured on firestone.

  ---Steps to Reproduce---

  1. Configure kdump.
  2. Check whether kdump is operational using ?# kdump-config show?.
  3. Install ?kernel-debuginfo? and ?kernel-debuginfo-common? rpms.
  4. Setup password less ssh connection, generate rsa key.
  # ssh-keygen -t rsa
  5. verify id_rsa and id_rsa.pub are created under /root/.ssh/
  6. Edit /etc/default/kdump-tools and add below entries.
  SSH="ubuntu@9.114.15.239"
  SSH_KEY=/root/.ssh/id_rsa
  7. Propagate RSA key.
  # kdump-config propagate
  8. Restart kdump service.
  # kdump-config load
  9. Trigger Crash using below commands.
  # echo "1" > /proc/sys/kernel/sysrq
  # echo "c" > /proc/sysrq-trigger
  10. Verify dump is available in remote server in configured path.

  Machine details
  ===

  $ ipmitool -I lanplus -H  9.47.70.3 -U ADMIN -P admin sol activate

  $ ssh ubuntu@9.47.70.29

  PW: shriya101

  
  Attaching logs

  == Comment: #1 - PAVITHRA R. PRAKASH  -
  2017-03-07 05:01:42 ==

  
  == Comment: #5 - PAVITHRA R. PRAKASH  - 2017-03-07 
23:19:46 ==
  Hi, 

  Attaching the logs.

  Network info:

  root@ltc-firep3:~# hwinfo --network
  36: None 00.0: 10700 Loopback   
[Created at net.126]
Unique ID: ZsBS.GQNx7L4uPNA
SysFS ID: /class/net/lo
Hardware Class: network interface
Model: "Loopback network interface"
Device File: lo
Link detected: yes
Config Status: cfg=new, avail=yes, need=no, active=unknown

  37: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: 2lHw.ndpeucax6V1
Parent ID: mIXc.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f2
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.2
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f2
HW Address: 98:be:94:03:18:4a
Permanent HW Address: 98:be:94:03:18:4a
Link detected: no
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #15 (Ethernet controller)

  38: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: 7Onn.ndpeucax6V1
Parent ID: sx0U.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f0
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.0
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f0
HW Address: 98:be:94:03:18:48
Permanent HW Address: 98:be:94:03:18:48
Link detected: yes
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #16 (Ethernet controller)

  39: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: VwX_.ndpeucax6V1
Parent ID: DUng.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f3
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.3
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f3
HW Address: 98:be:94:03:18:4b
Permanent HW Address: 98:be:94:03:18:4b
Link detected: no
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #25 (Ethernet controller)

  40: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: bZ1s.ndpeucax6V1
Parent ID: J7HY.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f1
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.1
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f1
HW Address: 

[Kernel-packages] [Bug 1729010] Re: USB hub stops working after suspend(s?)

[Joe Barnett]

appears to be gone in 4.15.0-11 as well

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

Title:
  USB hub stops working after suspend(s?)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On initial boot, my usb hub works fine, but after a (series of?)
  suspends, I stop being able to see devices that are plugged into it.
  journalctl output on plugging it in:

  Oct 31 07:08:36 spiny kernel: usb 1-1: new high-speed USB device number 21 
using xhci_hcd
  Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device found, idVendor=0409, 
idProduct=005a
  Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device strings: Mfr=0, 
Product=0, SerialNumber=0
  Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: USB hub found
  Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: 4 ports detected
  Oct 31 07:08:36 spiny kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= 
SRC=fe80::::a299:9bff:fe17:9047 
DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 
FLOWLBL=32325 PROTO=UDP SPT=8612 DPT=8612 LEN=24 
  Oct 31 07:08:36 spiny kernel: usb 1-1.1: new high-speed USB device number 22 
using xhci_hcd
  Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device found, idVendor=0b95, 
idProduct=772a
  Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device strings: Mfr=1, 
Product=2, SerialNumber=3
  Oct 31 07:08:36 spiny kernel: usb 1-1.1: Product: AX88x72A
  Oct 31 07:08:36 spiny kernel: usb 1-1.1: Manufacturer: ASIX Elec. Corp.
  Oct 31 07:08:36 spiny kernel: usb 1-1.1: SerialNumber: 47EDE2
  Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 eth0: register 'asix' at 
usb-:00:14.0-1.1, ASIX AX88772 USB 2.0 Ethernet, 00:50:b6:47:ed:e2
  Oct 31 07:08:37 spiny NetworkManager[11575]:   [1509458917.0438] 
manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/7)
  Oct 31 07:08:37 spiny mtp-probe[13207]: checking bus 1, device 22: 
"/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1"
  Oct 31 07:08:37 spiny mtp-probe[13207]: bus: 1, device: 22 was not an MTP 
device
  Oct 31 07:08:37 spiny systemd-udevd[13206]: link_config: autonegotiation is 
unset or enabled, the speed and duplex are not writable.
  Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 enx0050b647ede2: renamed from 
eth0
  Oct 31 07:08:37 spiny pkexec[13215]: pam_unix(polkit-1:session): session 
opened for user root by (uid=1000)
  Oct 31 07:08:37 spiny pkexec[13215]: jbarnett: Executing command [USER=root] 
[TTY=unknown] [CWD=/home/jbarnett] 
[COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 
31]
  Oct 31 07:08:37 spiny pkexec[13214]: gdm: Error executing command as another 
user: Not authorized [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] 
[COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 
48]
  Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: Error 
executing command as another user: Not authorized
  Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: This 
incident has been reported.
  Oct 31 07:08:37 spiny systemd-networkd[1119]: eth0: Renamed to enx0050b647ede2
  Oct 31 07:08:37 spiny NetworkManager[11575]:   [1509458917.1066] device 
(eth0): interface index 10 renamed iface from 'eth0' to 'enx0050b647ede2'
  Oct 31 07:08:37 spiny NetworkManager[11575]:   [1509458917.1214] 
devices added (path: 
/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2,
 iface: enx0050b647ede2)
  Oct 31 07:08:37 spiny NetworkManager[11575]:   [1509458917.1214] device 
added (path: 
/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2,
 iface: enx0050b647ede2): no ifupdown configuration found.
  Oct 31 07:08:37 spiny NetworkManager[11575]:   [1509458917.1217] device 
(enx0050b647ede2): state change: unmanaged -> unavailable (reason 'managed', 
internal state 'external')
  Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: 
link is not ready
  Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: 
link is not ready
  Oct 31 07:08:37 spiny NetworkManager[11575]:   [1509458917.1274] 
keyfile: add connection in-memory (9365f42f-9dd9-3bdc-bbad-e7062efcaf7c,"Wired 
connection 4")
  Oct 31 07:08:37 spiny NetworkManager[11575]:   [1509458917.1284] 
settings: (enx0050b647ede2): created default wired connection 'Wired connection 
4'
  Oct 31 07:08:37 spiny systemd[1]: Starting 
systemd-resolved-update-resolvconf.service...
  Oct 31 07:08:37 spiny systemd[1]: Started 
systemd-resolved-update-resolvconf.service.
  Oct 31 07:08:37 spiny kernel: usb 1-1.2: new full-speed USB device number 23 
using xhci_hcd
  Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device found, idVendor=0d8c, 
idProduct=0105
  Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device strings: Mfr=3, 
Product=1, SerialNumber=0
  Oct 31 07:08:37 spiny kernel: usb 1-1.2: Product: USB 

[Kernel-packages] [Bug 1745464] Re: Random reboots with 4.13.0-26 on Ubuntu 16.04 LTS

[Joseph Salisbury]

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc4

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

Title:
  Random reboots with 4.13.0-26 on Ubuntu 16.04 LTS

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

Bug description:
  After installing kernel 4.13.0-26 (and 4.13.0-31) we are seeing random 
reboots on virtual machines (VSIs) hosted by SoftLayer.  The physical hosts 
were patched earlier this month but I don't have the details yet or access to 
the hypervisors.  We noticed 4.13.0-31 was rebooting frequently and went to 
4.13.0-26 instead which was performing better but still suffering from the 
random reboots.  The VMs still on the old 4.4 kernels haven't had any random 
reboots at all.  We don't have any intel-microcode package installed, and I'm 
not sure it would make a difference for VMs...?  We have seen this on both 
Broadwell and Haswell systems.  The attached apport file is from one of the 
Broadwell servers.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 25 11:43 seq
   crw-rw 1 root audio 116, 33 Jan 25 11:43 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  ProcFB:
   
  ProcKernelCmdLine: root=UUID=52c6959b-79b0-4bdd-8ed6-71e0ba782fb4 ro 
console=hvc0 elevator=noop
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-26-generic N/A
   linux-backports-modules-4.13.0-26-generic  N/A
   linux-firmware 1.157.8
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images xenial uec-images xenial uec-images
  Uname: Linux 4.13.0-26-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False

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

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

[Kernel-packages] [Bug 1745123] Re: Elasticsearch 2.4.6 cause a Oops: 0010 [#37] SMP NOPTI

[Joseph Salisbury]

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc4

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

Title:
  Elasticsearch 2.4.6 cause a Oops: 0010 [#37] SMP NOPTI

Status in elasticsearch package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in elasticsearch source package in Artful:
  Confirmed
Status in linux source package in Artful:
  Triaged

Bug description:
  Elasticsearch 2.4.6 can't start since new kernel upgrade
  (4.13.0-31-generic #34~16.04.1-Ubuntu)

  Kernel log contains :

  [ 4308.595429] Oops: 0010 [#37] SMP NOPTI
  [ 4308.595430] Modules linked in: btrfs xor raid6_pq ufs qnx4 hfsplus hfs 
minix ntfs msdos jfs xfs libcrc32c bnep pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) bluetooth ecdh_generic binfmt_misc nls_iso8859_1 
snd_hda_codec_hdmi edac_mce_amd snd_hda_codec_realtek snd_hda_codec_generic 
snd_hda_intel eeepc_wmi kvm_amd asus_wmi snd_hda_codec sparse_keymap 
snd_hda_core video wmi_bmof kvm input_leds joydev snd_hwdep snd_pcm irqbypass 
crct10dif_pclmul snd_seq_midi crc32_pclmul snd_seq_midi_event 
ghash_clmulni_intel snd_rawmidi pcbc nvidia_uvm(POE) snd_seq aesni_intel 
snd_seq_device snd_timer snd aes_x86_64 crypto_simd soundcore ccp glue_helper 
cryptd shpchp i2c_piix4 8250_dw wmi mac_hid parport_pc ppdev lp parport autofs4 
hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE)
  [ 4308.595462]  drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops 
drm r8169 ahci mii libahci gpio_amdpt gpio_generic
  [ 4308.595468] CPU: 0 PID: 9314 Comm: java Tainted: P  DOE   
4.13.0-31-generic #34~16.04.1-Ubuntu
  [ 4308.595470] Hardware name: System manufacturer System Product Name/PRIME 
B350M-A, BIOS 0502 02/24/2017
  [ 4308.595471] task: 8dfa07b945c0 task.stack: b2b6033f4000
  [ 4308.595472] RIP: 0010:0x6987877
  [ 4308.595473] RSP: 0018:b2b6033f7f50 EFLAGS: 00010202
  [ 4308.595474] RAX: 03e7 RBX:  RCX: 
7f20e3d314d9
  [ 4308.595475] RDX: 7f20dc6686c0 RSI: 4d73aa93 RDI: 

  [ 4308.595476] RBP:  R08: 7f20e319caa4 R09: 
000c
  [ 4308.595477] R10: 06987877 R11: 8dfa07b945c0 R12: 

  [ 4308.595478] R13:  R14:  R15: 

  [ 4308.595479] FS:  7f20e4823700() GS:8dfac660() 
knlGS:
  [ 4308.595480] CS:  0010 DS:  ES:  CR0: 80050033
  [ 4308.595481] CR2: 06987877 CR3: 0003b723e000 CR4: 
003406f0
  [ 4308.595482] Call Trace:
  [ 4308.595487]  ? entry_SYSCALL_64_fastpath+0x33/0xa3
  [ 4308.595489] Code:  Bad RIP value.
  [ 4308.595490] RIP: 0x6987877 RSP: b2b6033f7f50
  [ 4308.595491] CR2: 06987877
  [ 4308.595493] ---[ end trace ba92d9f3b2090708 ]---

  
  It related to new kernel update, it work when starting with an older kernel.

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

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

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

[bugproxy]

--- Comment From heinz-werner_se...@de.ibm.com 2018-03-06 10:02 EDT---
Not able to test this kernel, but this patch was verified upfront, before 
posting..

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

Title:
  qeth: fix calculation of required buffer elements for skb

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Description:  qeth: fix calculation of required buffer elements for
  skb

  Symptom:  Repeated device recovery due to Subchannel Program
  Checks

  Problem:  skbs of certain lengths cause qeth to miscalculate the
number of needed IO buffer elements, resulting in
malformed TX buffer descriptors. When such a buffer is
presented to the HW, it triggers a Subchannel Program
Check. qeth handles this by starting device recovery.

  Solution: Fix the buffer element calculation, so that qeth builds
proper TX buffer descriptors.

  Reproduction: Occurs for skbs where the last byte of the linear data
range / of a page frag sits on a page boundary.

  Upstream Git Commit:
  89271c65edd599207dd982007900506283c90ae3
  kernel 4.16


  backported to xenial/master-next

  Here's a backport of the upstream commit for pre-4.8 kernels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1750810/+subscriptions

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

[Kernel-packages] [Bug 1752101] Packages outside of proper component

[Brad Figg]

The following packages ended up in the wrong component in the -proposed
pocket:

linux-cloud-tools-gcp 4.15.0.1001.2 - is in universe instead of main
linux-cloud-tools-gke 4.15.0.1001.2 - is in universe instead of main
linux-gcp 4.15.0.1001.2 - is in universe instead of main
linux-gke 4.15.0.1001.2 - is in universe instead of main
linux-headers-gcp 4.15.0.1001.2 - is in universe instead of main
linux-headers-gke 4.15.0.1001.2 - is in universe instead of main
linux-image-gcp 4.15.0.1001.2 - is in universe instead of main
linux-image-gke 4.15.0.1001.2 - is in universe instead of main
linux-tools-gcp 4.15.0.1001.2 - is in universe instead of main
linux-tools-gke 4.15.0.1001.2 - is in universe instead of main

Once this is fixed, set the promote-to-proposed to Fix Released again

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

Title:
  linux-gcp: 4.15.0-1001.1 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Confirmed
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Invalid
Status in Kernel Development Workflow promote-to-proposed series:
  Incomplete
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New

Bug description:
  This bug is for tracking the 4.15.0-1001.1 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: Uploaded

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

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

[Kernel-packages] [Bug 1745349] Re: Hard lockup during boot with linux-image-4.4.0-112-generic

[Mike Turner]

That one, Linux golf 4.4.0-110-generic
#133~lp1745349Commit7de295e2a47849 SMP Tue Mar 6 13:00:57 UTC 20 x86_64
x86_64 x86_64 GNU/Linux doesn't appear to have the problem.

It has been running for a lot longer than it usually does.

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

Title:
  Hard lockup during boot with linux-image-4.4.0-112-generic

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

Bug description:
  Systems on ASUS H110M-C Boards don't boot here with Kernel 4.4.0-112
  instead they show

  NMI watchdog: Watchdog detected hard lockup on cpu 0
  NMI watchdog: Watchdog detected hard lockup on cpu 1
  NMI watchdog: Watchdog detected hard lockup on cpu 3
  NMI watchdog: Watchdog detected hard lockup on cpu 2

  I cannot provide any logs of course.

  Booting with 4.4.0-109 works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lr3200 2013 F pulseaudio
  Date: Thu Jan 25 11:38:55 2018
  HibernationDevice: RESUME=UUID=8e35131d-6d40-4f4f-a3db-c7336e72cbce
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   enp3s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
root=UUID=4dc5bb0a-ab7c-48fa-ac23-bcdf23755d93 ro
  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.4.0-109-generic N/A
   linux-backports-modules-4.4.0-109-generic  N/A
   linux-firmware 1.157.15
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3601
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-C
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3601:bd12/12/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-C:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1753583] Re: Ubuntu 16.04.4 HWE kernel lockup: Upstream commit missing

[Per Allansson]

I tested it yesterday with my own build - ie applied d47924417319 on the
latest hwe kernel - and it worked[1] for me. But I will test your build
too.

[1] ie I ended up getting another kernel issue - which is that the
megaraid driver can't handle CPUs being disabled - which is discussed in
detail here (and not solved upstream afaict):
https://lkml.org/lkml/2017/8/8/884

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

Title:
  Ubuntu 16.04.4 HWE kernel lockup: Upstream commit missing

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

Bug description:
  I experience random lockups when disabling CPUs, with symptoms very
  much as described here:

  See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733662

  and when double-checking the source code for 4.13.0-36.40~16.04.1 I can see 
that upstream commit d47924417319e3b6a728c0b690f183e75bc2a702 is indeed missing.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  5 19:30 seq
   crw-rw 1 root audio 116, 33 Mar  5 19:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: FUJITSU PRIMERGY RX2530 M4
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/image1/kernel root=/dev/czvg/image1 ro 
console=tty0 console=ttyS0,115200 earlyprintk=ttyS0 rootdelay=300 net.ifnames=0 
biosdevname=0 nomodeset scsi_mod.scan=sync cz-boot-fs=/dev/sda1 
cz-state-fs=/dev/czvg/state1
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/05/2017
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V5.0.0.12 R1.11.0 for D3383-A1x
  dmi.board.name: D3383-A1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3383-A12 WGS03 GS04
  dmi.chassis.asset.tag: System Asset Tag
  dmi.chassis.type: 23
  dmi.chassis.vendor: FUJITSU
  dmi.chassis.version: RX2530M4R1
  dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.12R1.11.0forD3383-A1x:bd10/05/2017:svnFUJITSU:pnPRIMERGYRX2530M4:pvrGS01:rvnFUJITSU:rnD3383-A1:rvrS26361-D3383-A12WGS03GS04:cvnFUJITSU:ct23:cvrRX2530M4R1:
  dmi.product.family: SERVER
  dmi.product.name: PRIMERGY RX2530 M4
  dmi.product.version: GS01
  dmi.sys.vendor: FUJITSU

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

-- 
Mailing list: https://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 1750245] Re: i915 kbl_guc_ver9_14.bin does not load

[Andrew Crouthamel]

This appears to work, thanks!


---
Andrew Crouthamel

On Tue, Mar 6, 2018 at 3:54 AM, Seth Forshee 
wrote:

> I'd be very surprised if there was, more likely the file from our
> package got corrupted somehow on your machine. You could force
> reinstallation of the package (sudo apt install --reinstall linux-
> firmware) and see if that fixes the problem.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1750245
>
> Title:
>   i915 kbl_guc_ver9_14.bin does not load
>
> Status in linux-firmware package in Ubuntu:
>   Confirmed
>
> Bug description:
>   The provided i915/kbl_guc_ver9_14.bin does not load when configured to
>   do so . If the file is replaced by manually installing with the
>   included script from 01.org, it loads properly:
>   https://01.org/linuxgraphics/downloads/kabylake-guc-9.14
>
>   Before:
>   GuC firmware status:
>   path: i915/kbl_guc_ver9_14.bin
>   fetch: FAIL
>   load: NONE
>   version wanted: 9.14
>   version found: 0.0
>   header: offset is 0; size = 0
>   uCode: offset is 0; size = 0
>   RSA: offset is 0; size = 0
>
>   After:
>   GuC firmware status:
>   path: i915/kbl_guc_ver9_14.bin
>   fetch: SUCCESS
>   load: SUCCESS
>   version wanted: 9.14
>   version found: 9.14
>   header: offset is 0; size = 128
>   uCode: offset is 128; size = 142272
>   RSA: offset is 142400; size = 256
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux-firmware/
> +bug/1750245/+subscriptions
>

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

Title:
  i915 kbl_guc_ver9_14.bin does not load

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  The provided i915/kbl_guc_ver9_14.bin does not load when configured to
  do so . If the file is replaced by manually installing with the
  included script from 01.org, it loads properly:
  https://01.org/linuxgraphics/downloads/kabylake-guc-9.14

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

  After:
  GuC firmware status:
  path: i915/kbl_guc_ver9_14.bin
  fetch: SUCCESS
  load: SUCCESS
  version wanted: 9.14
  version found: 9.14
  header: offset is 0; size = 128
  uCode: offset is 128; size = 142272
  RSA: offset is 142400; size = 256

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

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

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

[bugproxy]

--- Comment From drbr...@us.ibm.com 2018-03-06 09:43 EDT---
This will be added to canonical bug scrub list for 3/08.

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

Title:
  Power9 DD 2.2 needs HMI fixup backport of upstream
  patch(d075745d893c78730e4a3b7a60fca23c2f764081) into kernel

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

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2018-02-23 
06:55:23 ==
  ---Problem Description---
  Power9 DD 2.2 needs HMI fixup backport of upstream 
patch(d075745d893c78730e4a3b7a60fca23c2f764081) into kernel
   
  ---uname output---
  4.15.0-10-generic
   
  Machine Type = power9 boston 2.2 (pvr 004e 1202) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   commit d075745d893c78730e4a3b7a60fca23c2f764081
  Author: Paul Mackerras 
  Date:   Wed Jan 17 20:51:13 2018 +1100

  KVM: PPC: Book3S HV: Improve handling of debug-trigger HMIs on POWER9
  

  Dependancy commit, looks like already present.
  commit 5080332c2c893118dbc18755f35c8b0131cf0fc4
  Author: Michael Neuling 
  Date:   Fri Sep 15 15:25:48 2017 +1000

  powerpc/64s: Add workaround for P9 vector CI load issue
  

   
  Contact Information = sathe...@in.ibm.com 
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for sathe...@in.ibm.com: 
  -Attach sysctl -a output output to the bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1751834/+subscriptions

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

[Kernel-packages] [Bug 1750810] Re: qeth: fix calculation of required buffer elements for skb

[Frank Heimes]

** Changed in: ubuntu-z-systems
   Status: Triaged => 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/1750810

Title:
  qeth: fix calculation of required buffer elements for skb

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Description:  qeth: fix calculation of required buffer elements for
  skb

  Symptom:  Repeated device recovery due to Subchannel Program
  Checks

  Problem:  skbs of certain lengths cause qeth to miscalculate the
number of needed IO buffer elements, resulting in
malformed TX buffer descriptors. When such a buffer is
presented to the HW, it triggers a Subchannel Program
Check. qeth handles this by starting device recovery.

  Solution: Fix the buffer element calculation, so that qeth builds
proper TX buffer descriptors.

  Reproduction: Occurs for skbs where the last byte of the linear data
range / of a page frag sits on a page boundary.

  Upstream Git Commit:
  89271c65edd599207dd982007900506283c90ae3
  kernel 4.16


  backported to xenial/master-next

  Here's a backport of the upstream commit for pre-4.8 kernels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1750810/+subscriptions

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

[Kernel-packages] [Bug 1681909] Console log - Kdump failure attempt with Ubuntu 16.04

[bugproxy]

--- Comment (attachment only) From mu...@br.ibm.com 2018-03-06 09:39 
EDT---


** Attachment added: "Console log - Kdump failure attempt with Ubuntu 16.04"
   
https://bugs.launchpad.net/bugs/1681909/+attachment/5070786/+files/console_kdump_1604.log

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

Title:
  dump is not captured in remote host when kdump over ssh is configured
  on firestone.

Status in The Ubuntu-power-systems project:
  Incomplete
Status in makedumpfile package in Ubuntu:
  New

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH  - 2017-03-07 
05:00:29 ==
  ---Problem Description---

  Ubuntu 17.04: dump is not captured in remote host when kdump over ssh
  is configured on firestone.

  ---Steps to Reproduce---

  1. Configure kdump.
  2. Check whether kdump is operational using ?# kdump-config show?.
  3. Install ?kernel-debuginfo? and ?kernel-debuginfo-common? rpms.
  4. Setup password less ssh connection, generate rsa key.
  # ssh-keygen -t rsa
  5. verify id_rsa and id_rsa.pub are created under /root/.ssh/
  6. Edit /etc/default/kdump-tools and add below entries.
  SSH="ubuntu@9.114.15.239"
  SSH_KEY=/root/.ssh/id_rsa
  7. Propagate RSA key.
  # kdump-config propagate
  8. Restart kdump service.
  # kdump-config load
  9. Trigger Crash using below commands.
  # echo "1" > /proc/sys/kernel/sysrq
  # echo "c" > /proc/sysrq-trigger
  10. Verify dump is available in remote server in configured path.

  Machine details
  ===

  $ ipmitool -I lanplus -H  9.47.70.3 -U ADMIN -P admin sol activate

  $ ssh ubuntu@9.47.70.29

  PW: shriya101

  
  Attaching logs

  == Comment: #1 - PAVITHRA R. PRAKASH  -
  2017-03-07 05:01:42 ==

  
  == Comment: #5 - PAVITHRA R. PRAKASH  - 2017-03-07 
23:19:46 ==
  Hi, 

  Attaching the logs.

  Network info:

  root@ltc-firep3:~# hwinfo --network
  36: None 00.0: 10700 Loopback   
[Created at net.126]
Unique ID: ZsBS.GQNx7L4uPNA
SysFS ID: /class/net/lo
Hardware Class: network interface
Model: "Loopback network interface"
Device File: lo
Link detected: yes
Config Status: cfg=new, avail=yes, need=no, active=unknown

  37: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: 2lHw.ndpeucax6V1
Parent ID: mIXc.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f2
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.2
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f2
HW Address: 98:be:94:03:18:4a
Permanent HW Address: 98:be:94:03:18:4a
Link detected: no
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #15 (Ethernet controller)

  38: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: 7Onn.ndpeucax6V1
Parent ID: sx0U.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f0
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.0
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f0
HW Address: 98:be:94:03:18:48
Permanent HW Address: 98:be:94:03:18:48
Link detected: yes
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #16 (Ethernet controller)

  39: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: VwX_.ndpeucax6V1
Parent ID: DUng.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f3
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.3
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f3
HW Address: 98:be:94:03:18:4b
Permanent HW Address: 98:be:94:03:18:4b
Link detected: no
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #25 (Ethernet controller)

  40: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: bZ1s.ndpeucax6V1
Parent ID: J7HY.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f1
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.1
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f1
HW Address: 98:be:94:03:18:49
Permanent HW Address: 98:be:94:03:18:49
Link detected: no
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #4 (Ethernet controller)
  root@ltc-firep3:~# 


  Thanks,
  Pavithra

  == Comment: #6 - PAVITHRA R. PRAKASH  -
  2017-03-07 23:20:47 ==

  
  == Comment: #7 - PAVITHRA R. PRAKASH 

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

[bugproxy]

--- Comment From mu...@br.ibm.com 2018-03-06 09:38 EDT---
Cascardo, I gave a try with kdump in Ubuntu 16.04 and it seems to occasionally 
fail.

It seems to be kind of random when it decides to fail, I see that we are
hitting an EEH in slots behind a PLX switch, but even in successful
attempts we hit the EEH as well. So not sure how much it is related. I
collected the console log of the failure attempt (I am attaching it).

I am attempting to drop into a shell by setting sh or bash to run in the
KDUMP_FAIL_CMD option, but it seems to just hang and not give me a
console.I want to collect more logs and see if the adapter is able to
reach the peer to see if it is possibly a timing issue. Is there a
proper way to drop to a shell in case of a kdump failure?

Also I am attempting to reinstall Ubuntu 18.04 to reattempt kdump a few
more times to make sure I didn't get lucky, but I am hitting IBM Bug
165336 - Canonical LP 1753449, which is preventing from reinstalling
Ubuntu 18.04.

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

Title:
  dump is not captured in remote host when kdump over ssh is configured
  on firestone.

Status in The Ubuntu-power-systems project:
  Incomplete
Status in makedumpfile package in Ubuntu:
  New

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH  - 2017-03-07 
05:00:29 ==
  ---Problem Description---

  Ubuntu 17.04: dump is not captured in remote host when kdump over ssh
  is configured on firestone.

  ---Steps to Reproduce---

  1. Configure kdump.
  2. Check whether kdump is operational using ?# kdump-config show?.
  3. Install ?kernel-debuginfo? and ?kernel-debuginfo-common? rpms.
  4. Setup password less ssh connection, generate rsa key.
  # ssh-keygen -t rsa
  5. verify id_rsa and id_rsa.pub are created under /root/.ssh/
  6. Edit /etc/default/kdump-tools and add below entries.
  SSH="ubuntu@9.114.15.239"
  SSH_KEY=/root/.ssh/id_rsa
  7. Propagate RSA key.
  # kdump-config propagate
  8. Restart kdump service.
  # kdump-config load
  9. Trigger Crash using below commands.
  # echo "1" > /proc/sys/kernel/sysrq
  # echo "c" > /proc/sysrq-trigger
  10. Verify dump is available in remote server in configured path.

  Machine details
  ===

  $ ipmitool -I lanplus -H  9.47.70.3 -U ADMIN -P admin sol activate

  $ ssh ubuntu@9.47.70.29

  PW: shriya101

  
  Attaching logs

  == Comment: #1 - PAVITHRA R. PRAKASH  -
  2017-03-07 05:01:42 ==

  
  == Comment: #5 - PAVITHRA R. PRAKASH  - 2017-03-07 
23:19:46 ==
  Hi, 

  Attaching the logs.

  Network info:

  root@ltc-firep3:~# hwinfo --network
  36: None 00.0: 10700 Loopback   
[Created at net.126]
Unique ID: ZsBS.GQNx7L4uPNA
SysFS ID: /class/net/lo
Hardware Class: network interface
Model: "Loopback network interface"
Device File: lo
Link detected: yes
Config Status: cfg=new, avail=yes, need=no, active=unknown

  37: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: 2lHw.ndpeucax6V1
Parent ID: mIXc.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f2
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.2
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f2
HW Address: 98:be:94:03:18:4a
Permanent HW Address: 98:be:94:03:18:4a
Link detected: no
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #15 (Ethernet controller)

  38: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: 7Onn.ndpeucax6V1
Parent ID: sx0U.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f0
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.0
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f0
HW Address: 98:be:94:03:18:48
Permanent HW Address: 98:be:94:03:18:48
Link detected: yes
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #16 (Ethernet controller)

  39: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: VwX_.ndpeucax6V1
Parent ID: DUng.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f3
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.3
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f3
HW Address: 98:be:94:03:18:4b
Permanent HW Address: 98:be:94:03:18:4b
Link detected: no
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #25 (Ethernet controller)

  40: None 00.0: 10701 Ethernet
[Created at 

[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions

[Nobuto Murata]

Reproducible with:
v4.11 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11/

The next is v4.13-rc1.

** Attachment added: "bond_check_xenial_mainline_4.11.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5070785/+files/bond_check_xenial_mainline_4.11.log

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

Title:
  [i40e] LACP bonding start up race conditions

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

Bug description:
  When provisioning Ubuntu servers with MAAS at once, some bonding pairs
  will have unexpected LACP status such as "Expired". It randomly
  happens at each provisioning with the default xenial kernel(4.4), but
  not reproducible with HWE kernel(4.13). I'm using Intel X710 cards
  (Dell-branded).

  Using the HWE kernel works as a workaround for short term, but it's
  not ideal since 4.13 is not covered by Canonical Livepatch service.

  How to reproduce:
  1. configure LACP bonding with MAAS
  2. provision machines
  3. check the bonding status in /proc/net/bonding/bond*

  frequency of occurrence:
  About 5 bond pairs in 22 pairs at each provisioning.

  [reproducible combination]
  $ uname -a
  Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 1.4.25-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  [non-reproducible combination]
  $ uname -a
  Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 2.1.14-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-116-generic 4.4.0-116.140
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  6 06:37 seq
   crw-rw 1 root audio 116, 33 Mar  6 06:37 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Mar  6 06:46:32 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R730
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed 
root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 
console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-116-generic N/A
   linux-backports-modules-4.4.0-116-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/16/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.5
  dmi.board.name: 072T6D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.asset.tag: 0018880
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R730
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1753756] Re: general protection fault: 0000 [#1] SMP PTI

[Joseph Salisbury]

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc4


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

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

** Tags added: kernel-da-key

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

Title:
  general protection fault:  [#1] SMP PTI

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  general protection fault:  [#1] SMP PTI

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1123 F pulseaudio
marge  1530 F pulseaudio
   /dev/snd/controlC1:  gdm1123 F pulseaudio
marge  1530 F pulseaudio
  Date: Tue Mar  6 15:13:23 2018
  Failure: oops
  InstallationDate: Installed on 2017-10-20 (136 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS All Series
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=16439337-51ef-4bcb-954c-acacc49e546f 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: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: general protection fault:  [#1] SMP PTI
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2903
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97M-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2903:bd02/22/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97M-PLUS:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Kernel-packages] [Bug 1753745] Re: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [Xorg:4873]

[Joseph Salisbury]

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc4


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

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

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

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [Xorg:4873]

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  during startup or before cold boot. System used a lot of resources,
  necessitating a reboot

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-11-generic 4.15.0-11.12
  ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
  Uname: Linux 4.15.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_uvm 
nvidia_drm nvidia_modeset nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  erik  22879 F pulseaudio
gdm   31270 F pulseaudio
   /dev/snd/controlC0:  erik  22879 F pulseaudio
gdm   31270 F pulseaudio
  Date: Tue Mar  6 13:04:17 2018
  Failure: oops
  HibernationDevice: RESUME=UUID=fb731a76-d649-4283-9a48-91fda418f5d4
  InstallationDate: Installed on 2018-02-25 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225)
  IwConfig:
   enp3s0no wireless extensions.
   
   enp8s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-11-generic 
root=UUID=269d199c-0dea-47bc-89fb-5388d4361c0e 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: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [Xorg:4873]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/11/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: U1n
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z68X-UD3H-B3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrU1n:bd07/11/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ68X-UD3H-B3:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1743027] Re: error loading realtime clock since upgrading to 17.10

[Alexandre BELLONI]

The issue is caused by CONFIG_WDAT_WDT which driver is stealing the RTC
resources before the RTC driver is probed. Disabling CONFIG_WDAT_WDT
will solve that issue.

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

Title:
  error loading realtime clock since upgrading to 17.10

Status in linux package in Ubuntu:
  Triaged

Bug description:
  (originally asked over at askubuntu.com, but is still unresolved:
  https://askubuntu.com/questions/971349/problem-with-real-time-clock-
  since-upgrading-to-ubuntu-17-10)

  I recently upgraded from Ubuntu 17.04 to Ubuntu 17.10 using the
  software update process. The update completed without any errors, and
  Ubuntu 17.10 is now running without any major issues.

  However, I was running a script previously that uses rtcwake which has
  since stopped working. The script automatically hibernates my laptop
  after a set period of time in sleep mode, and was working perfectly in
  Ubuntu 17.04.

  In the process of troubleshooting, I discovered that the problem was
  with rtcwake which is complaining about /dev/rtc0 missing.

  Here is output from a sample rtcwake command:

  peter@haven:~$ rtcwake -m no -s 1300
  rtcwake: assuming RTC uses UTC ...
  rtcwake: /dev/rtc0: unable to find device: No such file or directory

  I verified that in fact, that directory is missing. Since this was
  working prior to the upgrade, I have to assume that it was there
  previously, but I don't know for sure.

  In researching the error, I found some suggestions to get further
  information with timedatectl and hwclock, so here are the results from
  those commands as well.

  Output of timedatectl:

  peter@haven:~$ timedatectl
Local time: Fri 2017-10-27 19:06:26 EDT
Universal time: Fri 2017-10-27 23:06:26 UTC
  RTC time: n/a
 Time zone: America/New_York (EDT, -0400)
   Network time on: yes
  NTP synchronized: yes
   RTC in local TZ: no

  Output of hwclock --debug:

  peter@haven:~$ sudo hwclock --debug
  [sudo] password for peter: 
  hwclock from util-linux 2.30.1
  Trying to open: /dev/rtc0
  Trying to open: /dev/rtc
  Trying to open: /dev/misc/rtc
  No usable clock interface found.
  hwclock: Cannot access the Hardware Clock via any known method.

  UPDATE

  When I boot with my old kernel, 4.10.0-37-generic the real-time clock
  works fine.

  I get the following RTC messages in dmesg when I boot the
  4.13.0-16-generic kernel:

  peter@haven:~$ dmesg | grep -i rtc
  [0.089393] RTC time: 17:03:55, date: 11/01/17
  [1.238784] rtc_cmos 00:01: RTC can wake from S4
  [1.238794] rtc_cmos: probe of 00:01 failed with error -16
  [1.295459] hctosys: unable to open rtc device (rtc0)

  UPDATE #2

  Well, I was starting to believe that I had a hardware issue, since
  discovering I was unable to save changes to my BIOS and could not boot
  from USB. As it turns out, my laptop was bitten by this bug:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147 causing
  my BIOS to be locked in a read-only state.

  Once I resolved the BIOS issue, and fixed the USB boot problem, I did
  a live boot of Ubuntu 17.10. The issue with my real time clock still
  exists under this clean boot scenario, yet when I boot other distros,
  like Linux Mint 18.3 and the real time clock works fine. I feel this
  definitely has something to do with the Ubuntu install, perhaps even a
  kernel bug.

  UPDATE #3

  More evidence to suggest this is a kernel bug: I live-booted a copy of
  Antergos Linux, which was using the Arch kernel 4.14.12-1-ARCH and it
  exhibited the same problem with the real time clock as Ubuntu 17.10.
  In addition, I confirmed that the Linux Mint version I booted earlier
  (see Update #2) was on the Ubuntu kernel 4.10.0-38-generic.

  So, I suspect that sometime between kernels 4.10 and 4.13 this bug was 
introduced.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peter  1832 F pulseaudio
   /dev/snd/controlC1:  peter  1832 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=a602efe1-467d-4ac4-806f-1b931c91cdad
  InstallationDate: Installed on 2017-04-05 (292 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: LENOVO 20354
  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 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic.efi.signed 
root=UUID=fa5454aa-9072-475d-b515-acd51a6166cc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   

[Kernel-packages] [Bug 1744173] Re: artful: rfi-flush: Switch to new linear fallback flush

[Joseph Salisbury]

I built Xenial and Artful test kernels with the patch sets provided in
comments #2 and #4.  The test kernels can be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1744173

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

Note, to test this kernel, you need to install both the linux-image and
linux-image-extra .deb packages.

Thanks in advance!

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

Title:
  artful: rfi-flush: Switch to new linear fallback flush

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  Change flush from congruence-first with dependencies to linear with
  no dependencies, which increases flush performance by 8x on P8, and
  3x on P9 (as measured with null syscall loop, which will have the
  flush area in the L2).

  The flush also becomes simpler and more adaptable to different cache
  geometries.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1744173/+subscriptions

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

[Kernel-packages] [Bug 1752101] Packages outside of proper component

[Brad Figg]

The following packages ended up in the wrong component in the -proposed
pocket:

linux-cloud-tools-gcp 4.15.0.1001.2 - is in universe instead of main
linux-cloud-tools-gke 4.15.0.1001.2 - is in universe instead of main
linux-gcp 4.15.0.1001.2 - is in universe instead of main
linux-gke 4.15.0.1001.2 - is in universe instead of main
linux-headers-gcp 4.15.0.1001.2 - is in universe instead of main
linux-headers-gke 4.15.0.1001.2 - is in universe instead of main
linux-image-gcp 4.15.0.1001.2 - is in universe instead of main
linux-image-gke 4.15.0.1001.2 - is in universe instead of main
linux-tools-gcp 4.15.0.1001.2 - is in universe instead of main
linux-tools-gke 4.15.0.1001.2 - is in universe instead of main

Once this is fixed, set the promote-to-proposed to Fix Released again

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

Title:
  linux-gcp: 4.15.0-1001.1 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Confirmed
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Invalid
Status in Kernel Development Workflow promote-to-proposed series:
  Incomplete
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New

Bug description:
  This bug is for tracking the 4.15.0-1001.1 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: Uploaded

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

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

[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions

[Nobuto Murata]

Reproducible with:
4.10 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10/

The next test will be with:
v4.11 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11/

** Attachment added: "bond_check_xenial_mainline_4.10.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5070741/+files/bond_check_xenial_mainline_4.10.log

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

Title:
  [i40e] LACP bonding start up race conditions

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

Bug description:
  When provisioning Ubuntu servers with MAAS at once, some bonding pairs
  will have unexpected LACP status such as "Expired". It randomly
  happens at each provisioning with the default xenial kernel(4.4), but
  not reproducible with HWE kernel(4.13). I'm using Intel X710 cards
  (Dell-branded).

  Using the HWE kernel works as a workaround for short term, but it's
  not ideal since 4.13 is not covered by Canonical Livepatch service.

  How to reproduce:
  1. configure LACP bonding with MAAS
  2. provision machines
  3. check the bonding status in /proc/net/bonding/bond*

  frequency of occurrence:
  About 5 bond pairs in 22 pairs at each provisioning.

  [reproducible combination]
  $ uname -a
  Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 1.4.25-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  [non-reproducible combination]
  $ uname -a
  Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 2.1.14-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-116-generic 4.4.0-116.140
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  6 06:37 seq
   crw-rw 1 root audio 116, 33 Mar  6 06:37 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Mar  6 06:46:32 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R730
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed 
root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 
console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-116-generic N/A
   linux-backports-modules-4.4.0-116-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/16/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.5
  dmi.board.name: 072T6D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.asset.tag: 0018880
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R730
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions

[Joseph Salisbury]

To narrow it down further, can you also test the following kernels:

v4.11 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11/
v4.13-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc1/

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

Title:
  [i40e] LACP bonding start up race conditions

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

Bug description:
  When provisioning Ubuntu servers with MAAS at once, some bonding pairs
  will have unexpected LACP status such as "Expired". It randomly
  happens at each provisioning with the default xenial kernel(4.4), but
  not reproducible with HWE kernel(4.13). I'm using Intel X710 cards
  (Dell-branded).

  Using the HWE kernel works as a workaround for short term, but it's
  not ideal since 4.13 is not covered by Canonical Livepatch service.

  How to reproduce:
  1. configure LACP bonding with MAAS
  2. provision machines
  3. check the bonding status in /proc/net/bonding/bond*

  frequency of occurrence:
  About 5 bond pairs in 22 pairs at each provisioning.

  [reproducible combination]
  $ uname -a
  Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 1.4.25-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  [non-reproducible combination]
  $ uname -a
  Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 2.1.14-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-116-generic 4.4.0-116.140
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  6 06:37 seq
   crw-rw 1 root audio 116, 33 Mar  6 06:37 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Mar  6 06:46:32 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R730
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed 
root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 
console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-116-generic N/A
   linux-backports-modules-4.4.0-116-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/16/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.5
  dmi.board.name: 072T6D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.asset.tag: 0018880
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R730
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1753346] Re: AMD 7 1800X system (Dell Inspiron 5675) randomly freezes

[Pragnesh Sampat]

Most of the freezes are when the system was idle.  I caught one free as
I was typing "cat /proc/cpuinfo" (froze somewhere in the middle of
that).  But IIRC, that was one time, all other freezes were idle.

It has not yet frozen since:

$ uptime
 09:07:18 up 1 day, 14:32,  1 user,  load average: 0.18, 0.19, 0.16

That bugzilla link you showed me has lots of information, I think C6
states could be relevant and interesting, thanks for that link!  Per
discussion in that thread, I have the zenstates.py installed and
working, but have not changed anything yet, just listed the states.

Will review the thread more closely and see where we go.

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

Title:
  AMD 7 1800X system (Dell Inspiron 5675) randomly freezes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is happening every day or so.  I cannot see anything in the
  kern.log or syslog that give me a clue on where/what the issue might.
  I was using Ubuntu 17.10 earlier and upgraded to Ubuntu 18.04 on
  3/3/2018, since I thought kernel 4.15 might have better support for
  the ryzen 7 and also maybe amdgpu for the radeon 580 might be newer.
  I have removed most external devices except for networking and HDMI
  and audio out.

  Attached a tarball of info, although I believe that since I used
  'ubuntu-bug linux' command, the information might be duplicated,
  apologize for any extra attachments.

  $ ls -l dell-5675-sysinfo/
  total 168
  -rw-r--r-- 1 pss pss 83139 Mar  4 19:47 dmesg
  -rw-r--r-- 1 pss pss 26154 Mar  4 19:44 dmidecode
  -rw-r--r-- 1 pss pss  1507 Mar  4 19:45 gpu-manager.log
  -rw-r--r-- 1 pss pss   110 Mar  4 19:44 lsb-release-a
  -rw-r--r-- 1 pss pss  1464 Mar  4 19:44 lscpu
  -rw-r--r-- 1 pss pss  4353 Mar  4 19:46 lspci
  -rw-r--r-- 1 pss pss  4105 Mar  4 20:05 lspci-vvv-radeon-580.txt
  -rw-r--r-- 1 pss pss 19318 Mar  4 19:48 
mprime-p95v294b8.linux64-results-2018-03-04.txt
  -rw-r--r-- 1 pss pss   104 Mar  4 19:44 uname-a
  -rw-r--r-- 1 pss pss35 Mar  4 20:27 version.log

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pss1801 F pulseaudio
   /dev/snd/controlC0:  pss1801 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar  4 20:21:55 2018
  InstallationDate: Installed on 2018-02-16 (16 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Dell Inc. Inspiron 5675
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.utf8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=d6a2ae1e-5421-435f-8e4c-e377133cebc9 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-03-04 (1 days ago)
  dmi.bios.date: 12/04/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.6
  dmi.board.name: 07PR60
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.3.6
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.6:bd12/04/2017:svnDellInc.:pnInspiron5675:pvr1.3.6:rvnDellInc.:rn07PR60:rvrA00:cvnDellInc.:ct3:cvr1.3.6:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5675
  dmi.product.version: 1.3.6
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1752101] Packages outside of proper component

[Brad Figg]

The following packages ended up in the wrong component in the -proposed
pocket:

linux-cloud-tools-gcp 4.15.0.1001.2 - is in universe instead of main
linux-cloud-tools-gke 4.15.0.1001.2 - is in universe instead of main
linux-gcp 4.15.0.1001.2 - is in universe instead of main
linux-gke 4.15.0.1001.2 - is in universe instead of main
linux-headers-gcp 4.15.0.1001.2 - is in universe instead of main
linux-headers-gke 4.15.0.1001.2 - is in universe instead of main
linux-image-gcp 4.15.0.1001.2 - is in universe instead of main
linux-image-gke 4.15.0.1001.2 - is in universe instead of main
linux-tools-gcp 4.15.0.1001.2 - is in universe instead of main
linux-tools-gke 4.15.0.1001.2 - is in universe instead of main

Once this is fixed, set the promote-to-proposed to Fix Released again

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

Title:
  linux-gcp: 4.15.0-1001.1 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Confirmed
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Invalid
Status in Kernel Development Workflow promote-to-proposed series:
  Incomplete
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New

Bug description:
  This bug is for tracking the 4.15.0-1001.1 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: Uploaded

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

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

[Kernel-packages] [Bug 1744173] artful wave2 patches

[bugproxy]

--- Comment (attachment only) From bren...@br.ibm.com 2018-01-19 07:39 
EDT---


** Attachment added: "artful wave2 patches"
   
https://bugs.launchpad.net/bugs/1744173/+attachment/5070736/+files/artful_wave2.tgz

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

Title:
  artful: rfi-flush: Switch to new linear fallback flush

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  Change flush from congruence-first with dependencies to linear with
  no dependencies, which increases flush performance by 8x on P8, and
  3x on P9 (as measured with null syscall loop, which will have the
  flush area in the L2).

  The flush also becomes simpler and more adaptable to different cache
  geometries.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1744173/+subscriptions

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

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

[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/1753756

Title:
  general protection fault:  [#1] SMP PTI

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  general protection fault:  [#1] SMP PTI

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1123 F pulseaudio
marge  1530 F pulseaudio
   /dev/snd/controlC1:  gdm1123 F pulseaudio
marge  1530 F pulseaudio
  Date: Tue Mar  6 15:13:23 2018
  Failure: oops
  InstallationDate: Installed on 2017-10-20 (136 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS All Series
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=16439337-51ef-4bcb-954c-acacc49e546f 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: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: general protection fault:  [#1] SMP PTI
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2903
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97M-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2903:bd02/22/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97M-PLUS:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

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

[Brad Figg]

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+ 
+ kernel-stable-phase-changed:Tuesday, 06. March 2018 14:00 UTC
+ kernel-stable-phase:Packaging

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  kernel-stable-phase-changed:Tuesday, 06. March 2018 14:00 UTC
  kernel-stable-phase:Packaging
+ 
+ -- swm properties --
+ phase: Packaging

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

Title:
  linux:  -proposed tracker

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

  kernel-stable-phase-changed:Tuesday, 06. March 2018 14:00 UTC
  kernel-stable-phase:Packaging

  -- swm properties --
  phase: Packaging

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

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

[Kernel-packages] [Bug 1753762] [NEW] stlouis-kernel: snap tracker

[Kleber Sacilotto de Souza]

Public bug reported:

This bug is for tracking the  kernel snap. This
bug will contain status and testing results related to that publication.

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

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

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

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

Title:
  stlouis-kernel:  snap tracker

Status in linux package in Ubuntu:
  Invalid

Bug description:
  This bug is for tracking the  kernel snap. This
  bug will contain status and testing results related to that
  publication.

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

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

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

[Kernel-packages] [Bug 1744173] Re: artful: rfi-flush: Switch to new linear fallback flush

[Joseph Salisbury]

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

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

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

** Changed in: linux (Ubuntu Artful)
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

Title:
  artful: rfi-flush: Switch to new linear fallback flush

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  Change flush from congruence-first with dependencies to linear with
  no dependencies, which increases flush performance by 8x on P8, and
  3x on P9 (as measured with null syscall loop, which will have the
  flush area in the L2).

  The flush also becomes simpler and more adaptable to different cache
  geometries.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1744173/+subscriptions

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

[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions

[Nobuto Murata]

Thanks, I was running some tests with existing HWE kernels in xenial
repo like linux-image-4.8.0-58-generic, linux-image-4.10.0-42-generic
and linux-image-4.13.0-36-generic. It looks like 4.10 is the last bad
one and 4.13 is the first good one.

Let me double-check with those two:
4.10 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10/
4.13 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13/

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

Title:
  [i40e] LACP bonding start up race conditions

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

Bug description:
  When provisioning Ubuntu servers with MAAS at once, some bonding pairs
  will have unexpected LACP status such as "Expired". It randomly
  happens at each provisioning with the default xenial kernel(4.4), but
  not reproducible with HWE kernel(4.13). I'm using Intel X710 cards
  (Dell-branded).

  Using the HWE kernel works as a workaround for short term, but it's
  not ideal since 4.13 is not covered by Canonical Livepatch service.

  How to reproduce:
  1. configure LACP bonding with MAAS
  2. provision machines
  3. check the bonding status in /proc/net/bonding/bond*

  frequency of occurrence:
  About 5 bond pairs in 22 pairs at each provisioning.

  [reproducible combination]
  $ uname -a
  Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 1.4.25-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  [non-reproducible combination]
  $ uname -a
  Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 2.1.14-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-116-generic 4.4.0-116.140
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  6 06:37 seq
   crw-rw 1 root audio 116, 33 Mar  6 06:37 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Mar  6 06:46:32 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R730
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed 
root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 
console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-116-generic N/A
   linux-backports-modules-4.4.0-116-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/16/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.5
  dmi.board.name: 072T6D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.asset.tag: 0018880
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R730
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1750810] Re: qeth: fix calculation of required buffer elements for skb

[Joseph Salisbury]

I built a Xenial test kernel with the back port posted in comment #2.

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1750810


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

Note, to test this kernel, you need to install both the linux-image and
linux-image-extra .deb packages.

Thanks in advance!

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

Title:
  qeth: fix calculation of required buffer elements for skb

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Description:  qeth: fix calculation of required buffer elements for
  skb

  Symptom:  Repeated device recovery due to Subchannel Program
  Checks

  Problem:  skbs of certain lengths cause qeth to miscalculate the
number of needed IO buffer elements, resulting in
malformed TX buffer descriptors. When such a buffer is
presented to the HW, it triggers a Subchannel Program
Check. qeth handles this by starting device recovery.

  Solution: Fix the buffer element calculation, so that qeth builds
proper TX buffer descriptors.

  Reproduction: Occurs for skbs where the last byte of the linear data
range / of a page frag sits on a page boundary.

  Upstream Git Commit:
  89271c65edd599207dd982007900506283c90ae3
  kernel 4.16


  backported to xenial/master-next

  Here's a backport of the upstream commit for pre-4.8 kernels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1750810/+subscriptions

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

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

[Kleber Sacilotto de Souza]

Public bug reported:

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

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

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

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

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

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

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

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

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

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

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

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

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

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Status: Invalid

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

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

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


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

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

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

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

** Tags added: xenial

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

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

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

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

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

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

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

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

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

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

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

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

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

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

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

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

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

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

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

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

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

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

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

** Changed in: 

[Kernel-packages] [Bug 1752101] Packages outside of proper component

[Brad Figg]

The following packages ended up in the wrong component in the -proposed
pocket:

linux-cloud-tools-gcp 4.15.0.1001.2 - is in universe instead of main
linux-cloud-tools-gke 4.15.0.1001.2 - is in universe instead of main
linux-gcp 4.15.0.1001.2 - is in universe instead of main
linux-gke 4.15.0.1001.2 - is in universe instead of main
linux-headers-gcp 4.15.0.1001.2 - is in universe instead of main
linux-headers-gke 4.15.0.1001.2 - is in universe instead of main
linux-image-gcp 4.15.0.1001.2 - is in universe instead of main
linux-image-gke 4.15.0.1001.2 - is in universe instead of main
linux-tools-gcp 4.15.0.1001.2 - is in universe instead of main
linux-tools-gke 4.15.0.1001.2 - is in universe instead of main

Once this is fixed, set the promote-to-proposed to Fix Released again

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

Title:
  linux-gcp: 4.15.0-1001.1 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Confirmed
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Invalid
Status in Kernel Development Workflow promote-to-proposed series:
  Incomplete
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New

Bug description:
  This bug is for tracking the 4.15.0-1001.1 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: Uploaded

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

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

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

[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/1753745

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [Xorg:4873]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  during startup or before cold boot. System used a lot of resources,
  necessitating a reboot

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-11-generic 4.15.0-11.12
  ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
  Uname: Linux 4.15.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_uvm 
nvidia_drm nvidia_modeset nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  erik  22879 F pulseaudio
gdm   31270 F pulseaudio
   /dev/snd/controlC0:  erik  22879 F pulseaudio
gdm   31270 F pulseaudio
  Date: Tue Mar  6 13:04:17 2018
  Failure: oops
  HibernationDevice: RESUME=UUID=fb731a76-d649-4283-9a48-91fda418f5d4
  InstallationDate: Installed on 2018-02-25 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225)
  IwConfig:
   enp3s0no wireless extensions.
   
   enp8s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-11-generic 
root=UUID=269d199c-0dea-47bc-89fb-5388d4361c0e 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: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [Xorg:4873]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/11/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: U1n
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z68X-UD3H-B3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrU1n:bd07/11/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ68X-UD3H-B3:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

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

[Kleber Sacilotto de Souza]

Public bug reported:

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

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

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

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

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

Title:
  linux:  -proposed tracker

Status in linux package in Ubuntu:
  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

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

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

[Kernel-packages] [Bug 1753756] [NEW] general protection fault: 0000 [#1] SMP PTI

[marge]

Public bug reported:

general protection fault:  [#1] SMP PTI

ProblemType: KernelOops
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-10-generic 4.15.0-10.11
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm1123 F pulseaudio
  marge  1530 F pulseaudio
 /dev/snd/controlC1:  gdm1123 F pulseaudio
  marge  1530 F pulseaudio
Date: Tue Mar  6 15:13:23 2018
Failure: oops
InstallationDate: Installed on 2017-10-20 (136 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
IwConfig:
 lono wireless extensions.
 
 eno1  no wireless extensions.
MachineType: ASUS All Series
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=16439337-51ef-4bcb-954c-acacc49e546f 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: kerneloops-daemon N/A
RfKill:
 
SourcePackage: linux
Title: general protection fault:  [#1] SMP PTI
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/22/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2903
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97M-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2903:bd02/22/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97M-PLUS:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS

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


** Tags: amd64 apport-kerneloops bionic kernel-oops

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

Title:
  general protection fault:  [#1] SMP PTI

Status in linux package in Ubuntu:
  New

Bug description:
  general protection fault:  [#1] SMP PTI

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1123 F pulseaudio
marge  1530 F pulseaudio
   /dev/snd/controlC1:  gdm1123 F pulseaudio
marge  1530 F pulseaudio
  Date: Tue Mar  6 15:13:23 2018
  Failure: oops
  InstallationDate: Installed on 2017-10-20 (136 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS All Series
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=16439337-51ef-4bcb-954c-acacc49e546f 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: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: general protection fault:  [#1] SMP PTI
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2903
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97M-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2903:bd02/22/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97M-PLUS:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Kernel-packages] [Bug 1726362] Re: CONFIG_EFI=y on armhf

[Seth Forshee]

** Changed in: linux (Ubuntu Bionic)
 Assignee: Canonical Kernel (canonical-kernel) => Seth Forshee (sforshee)

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

Title:
  CONFIG_EFI=y on armhf

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

Bug description:
  [Impact]

   * Please enable CONFIG_EFI on the armhf generic kernels
   * This may enable using armhf kernels with an armhf cloud-image and 
qemu-efi-arm under qemu-system-arm

  [Test Case]

   * Kernel config has CONFIG_EFI=y

  [Regression Potential]

   * Kernel config/image/modules will become larger in size due to more
  features enabled on the arm kernel.

  [Other Info]
   
   * qemu-efi-arm is available, experimental cloud-images are being produced, 
but not yet released to cloud-images.
   * expectations for cloud images to land into bb and then enabled on 
xenial/zesty/artful as well.

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

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

[Kernel-packages] [Bug 1745349] Re: Hard lockup during boot with linux-image-4.4.0-112-generic

[Joseph Salisbury]

I built the next test kernel, up to the following commit:
7de295e2a47849488acec80fc7c9973a4dca204e

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1745349

Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on your test results.

Thanks in advance

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

Title:
  Hard lockup during boot with linux-image-4.4.0-112-generic

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

Bug description:
  Systems on ASUS H110M-C Boards don't boot here with Kernel 4.4.0-112
  instead they show

  NMI watchdog: Watchdog detected hard lockup on cpu 0
  NMI watchdog: Watchdog detected hard lockup on cpu 1
  NMI watchdog: Watchdog detected hard lockup on cpu 3
  NMI watchdog: Watchdog detected hard lockup on cpu 2

  I cannot provide any logs of course.

  Booting with 4.4.0-109 works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lr3200 2013 F pulseaudio
  Date: Thu Jan 25 11:38:55 2018
  HibernationDevice: RESUME=UUID=8e35131d-6d40-4f4f-a3db-c7336e72cbce
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   enp3s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
root=UUID=4dc5bb0a-ab7c-48fa-ac23-bcdf23755d93 ro
  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.4.0-109-generic N/A
   linux-backports-modules-4.4.0-109-generic  N/A
   linux-firmware 1.157.15
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3601
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-C
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3601:bd12/12/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-C:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1750810] Re: qeth: fix calculation of required buffer elements for skb

[Joseph Salisbury]

** Changed in: linux (Ubuntu)
 Assignee: Skipper Bug Screeners (skipper-screen-team) => Joseph Salisbury 
(jsalisbury)

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

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

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

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

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

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

Title:
  qeth: fix calculation of required buffer elements for skb

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Description:  qeth: fix calculation of required buffer elements for
  skb

  Symptom:  Repeated device recovery due to Subchannel Program
  Checks

  Problem:  skbs of certain lengths cause qeth to miscalculate the
number of needed IO buffer elements, resulting in
malformed TX buffer descriptors. When such a buffer is
presented to the HW, it triggers a Subchannel Program
Check. qeth handles this by starting device recovery.

  Solution: Fix the buffer element calculation, so that qeth builds
proper TX buffer descriptors.

  Reproduction: Occurs for skbs where the last byte of the linear data
range / of a page frag sits on a page boundary.

  Upstream Git Commit:
  89271c65edd599207dd982007900506283c90ae3
  kernel 4.16


  backported to xenial/master-next

  Here's a backport of the upstream commit for pre-4.8 kernels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1750810/+subscriptions

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

[Kernel-packages] [Bug 1748513] Re: BUG: unable to handle kernel paging request at 00007f29ec101010

[Maksim Chumakov]

Hi,

I've encountered very similar issue on one of our GCE boxes with kernel
4.4.0-111-generic

Feb 27 11:55:10 userverlua-gce-sc-97 kernel: [54055.129348] BUG: unable to 
handle kernel paging request at 87ff364673b0
Feb 27 11:55:10 userverlua-gce-sc-97 kernel: [54055.136723] IP: 
[] kmem_cache_alloc_trace+0x7d/0x220
Feb 27 11:55:10 userverlua-gce-sc-97 kernel: [54055.143470] PGD 0
Feb 27 11:55:10 userverlua-gce-sc-97 kernel: [54055.145708] Oops:  [#1] SMP
Feb 27 11:55:10 userverlua-gce-sc-97 kernel: [54055.149268] Modules linked in: 
tcp_diag inet_diag xt_comment xt_tcpudp nf_conntrack_ip
v4 nf_defrag_ipv4 xt_conntrack xt_CT nf_conntrack xt_multiport iptable_raw 
ip6table_filter ip6_tables iptable_filter ip_tables x_table
s dm_crypt ppdev parport_pc parport 8250_fintek pvpanic input_leds i2c_piix4 
mac_hid serio_raw crct10dif_pclmul crc32_pclmul ghash_clm
ulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd 
psmouse virtio_scsi
Feb 27 11:55:10 userverlua-gce-sc-97 kernel: [54055.193555] CPU: 2 PID: 27781 
Comm: sshd Not tainted 4.4.0-111-generic #134~14.04.1-Ub
untu
Feb 27 11:55:10 userverlua-gce-sc-97 kernel: [54055.201928] Hardware name: 
Google Google Compute Engine/Google Compute Engine, BIOS Go
ogle 01/01/2011
Feb 27 11:55:10 userverlua-gce-sc-97 kernel: [54055.211254] task: 
8800ba585400 ti: 8800b9f8c000 task.ti: 8800b9f8c000
Feb 27 11:55:10 userverlua-gce-sc-97 kernel: [54055.218834] RIP: 
0010:[]  [] kmem_cache_alloc_trac
e+0x7d/0x220
Feb 27 11:55:10 userverlua-gce-sc-97 kernel: [54055.228010] RSP: 
0018:8800b9f8faf0  EFLAGS: 00010286
Feb 27 11:55:10 userverlua-gce-sc-97 kernel: [54055.233419] RAX: 
 RBX: 024000c0 RCX: 00079622
Feb 27 11:55:10 userverlua-gce-sc-97 kernel: [54055.240653] RDX: 
00079621 RSI: 024000c0 RDI: 88020c403d00
Feb 27 11:55:10 userverlua-gce-sc-97 kernel: [54055.247922] RBP: 
8800b9f8fb30 R08: 0001a580 R09: 88020c403d00
Feb 27 11:55:10 userverlua-gce-sc-97 kernel: [54055.255153] R10: 
814dfdcc R11: ead79200 R12: 024000c0
Feb 27 11:55:10 userverlua-gce-sc-97 kernel: [54055.262386] R13: 
8800ab077400 R14: 87ff364673b0 R15: 88020c403d00
Feb 27 14:21:32 userverlua-gce-sc-97 rsyslogd: [origin software="rsyslogd" 
swVersion="7.4.4" x-pid="1194" x-info="http://www.rsyslog.c
om"] start
Feb 27 14:21:32 userverlua-gce-sc-97 rsyslogd-2307: warning: ~ action is 
deprecated, consider using the 'stop' statement instead [try
http://www.rsyslog.com/e/2307 ]

There is no stack trace in syslog and no any crash reports in /var/crash&. The 
issue happened only once on Feb 27 at 11:55 UTC and till Feb 27 14:21 the box 
was in hanged state totally unresponsive.
So at 14:21 it was cold restarted and after restart the box works fine at the 
moment.

I'm interested if my issue actually related to this bug. If some one
could help with this I will really appreciate.

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

Title:
  BUG: unable to handle kernel paging request at 7f29ec101010

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Got this bug/oops while running with the linux-image-4.4.0-113-generic
  (4.4.0-113.136) kernel from -proposed:

  BUG: unable to handle kernel paging request at 7f29ec101010
  IP: [] csum_and_copy_from_iter+0x55/0x4c0
  PGD 82fcef6f9067 PUD 2fd1615e067 PMD 2fcef77e067 PTE 82fd0009f867
  Oops: 0001 [#1] SMP 
  Modules linked in: binfmt_misc nf_log_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 
ip6table_filter ip6_tables nf_log_ipv4 nf_log_common xt_LOG xt_tcpudp 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner xt_conntrack nf_
   fjes wmi
  CPU: 39 PID: 27347 Comm: fping Not tainted 4.4.0-113-generic #136-Ubuntu
  Hardware name: Dell Inc. PowerEdge R830/0VVT0H, BIOS 1.3.4 11/09/2016
  task: 88bd1125e200 ti: 897d0285 task.ti: 897d0285
  RIP: 0010:[]  [] 
csum_and_copy_from_iter+0x55/0x4c0
  RSP: 0018:897d02853a18  EFLAGS: 00010246
  RAX: 0018 RBX: 0006 RCX: 897d02853e98
  RDX: 897d02853a94 RSI: 0040 RDI: 8afcfba4ea24
  RBP: 897d02853a80 R08:  R09: 8afcfba4ea24
  R10: 8afcfba4ea24 R11: 8afcfba4ea00 R12: 897d02853e98
  R13:  R14: 1ee730fc3e9fb34c R15: 7f29ec101008
  FS:  7f29ec282700() GS:8afd7ec4() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 7f29ec101010 CR3: 02fce5462000 CR4: 00360670
  DR0:  DR1:  DR2: 
  DR3:  DR6: fffe0ff0 DR7: 0400
  Stack:
   88bd7ec07340 9772d1d7 8afcf02d8f00 897d02853aaf
   897d02853a94 01c0  1ee730fc3e9fb34c
   0040 

[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions

[Joseph Salisbury]

To perform a "Reverse" bisect, we need to identify the last kernel
version that had the bug and the first kernel version that does not.

Can you test the following upstream kernels:

4.4 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-wily/
4.6 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/
4.8 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8/
4.10 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10/
4.13 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13/

You don't have to test everyone, just up until we know the first kernel
version that does not have the bug.

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

Title:
  [i40e] LACP bonding start up race conditions

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

Bug description:
  When provisioning Ubuntu servers with MAAS at once, some bonding pairs
  will have unexpected LACP status such as "Expired". It randomly
  happens at each provisioning with the default xenial kernel(4.4), but
  not reproducible with HWE kernel(4.13). I'm using Intel X710 cards
  (Dell-branded).

  Using the HWE kernel works as a workaround for short term, but it's
  not ideal since 4.13 is not covered by Canonical Livepatch service.

  How to reproduce:
  1. configure LACP bonding with MAAS
  2. provision machines
  3. check the bonding status in /proc/net/bonding/bond*

  frequency of occurrence:
  About 5 bond pairs in 22 pairs at each provisioning.

  [reproducible combination]
  $ uname -a
  Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 1.4.25-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  [non-reproducible combination]
  $ uname -a
  Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 2.1.14-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-116-generic 4.4.0-116.140
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  6 06:37 seq
   crw-rw 1 root audio 116, 33 Mar  6 06:37 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Mar  6 06:46:32 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R730
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed 
root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 
console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-116-generic N/A
   linux-backports-modules-4.4.0-116-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/16/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.5
  dmi.board.name: 072T6D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.asset.tag: 0018880
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R730
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753705] Re: stress-ng will make an Ubuntu on LPAR s390x Bionic system become very slow

[Colin Ian King]

Can I get access to this hardware to start to debug this issue?

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

** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/1753705

Title:
  stress-ng will make an Ubuntu on LPAR s390x Bionic system become very
  slow

Status in linux package in Ubuntu:
  In Progress

Bug description:
  On an Ubuntu on LPAR s390x node, s2lp4, boot with Bionic kernel.

  When trying to run the ubuntu_stress_smoke test on it. This test will cause 
error like:
    
/home/ubuntu/autotest/client/tests/ubuntu_stress_smoke_test/ubuntu_stress_smoke_test.sh:
 fork: retry: Resource temporarily unavailable

  Not sure which test is the cause, but the system will become very slow
  after running this test suite. And it seems that the test suite will
  terminates itself before walking through all the test cases.

  1st run: terminates after the epoll test
  2nd run: crashed and rebooted after the branch test
  3rd run: terminates after the eventfd test
  4th run: terminates after the enosys test

  Command to run the test:
    AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/ubuntu_stress_smoke_test/control

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-11-generic 4.15.0-11.12
  ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
  Uname: Linux 4.15.0-11-generic s390x
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:

  Date: Tue Mar  6 09:31:39 2018
  HibernationDevice: RESUME=UUID=e2735dd1-cbbc-4424-9c25-d37d073d9414
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:

  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=38f7d570-2973-4055-b668-12a9ace1e0c7 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-11-generic N/A
   linux-backports-modules-4.15.0-11-generic  N/A
   linux-firmware 1.172
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1752101] Packages outside of proper component

[Brad Figg]

The following packages ended up in the wrong component in the -proposed
pocket:

linux-cloud-tools-gcp 4.15.0.1001.2 - is in universe instead of main
linux-cloud-tools-gke 4.15.0.1001.2 - is in universe instead of main
linux-gcp 4.15.0.1001.2 - is in universe instead of main
linux-gke 4.15.0.1001.2 - is in universe instead of main
linux-headers-gcp 4.15.0.1001.2 - is in universe instead of main
linux-headers-gke 4.15.0.1001.2 - is in universe instead of main
linux-image-gcp 4.15.0.1001.2 - is in universe instead of main
linux-image-gke 4.15.0.1001.2 - is in universe instead of main
linux-tools-gcp 4.15.0.1001.2 - is in universe instead of main
linux-tools-gke 4.15.0.1001.2 - is in universe instead of main

Once this is fixed, set the promote-to-proposed to Fix Released again

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

Title:
  linux-gcp: 4.15.0-1001.1 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Confirmed
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Invalid
Status in Kernel Development Workflow promote-to-proposed series:
  Incomplete
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New

Bug description:
  This bug is for tracking the 4.15.0-1001.1 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: Uploaded

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

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

[Kernel-packages] [Bug 1753745] [NEW] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [Xorg:4873]

[emk2203]

Public bug reported:

during startup or before cold boot. System used a lot of resources,
necessitating a reboot

ProblemType: KernelOops
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-11-generic 4.15.0-11.12
ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
Uname: Linux 4.15.0-11-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_uvm 
nvidia_drm nvidia_modeset nvidia
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  erik  22879 F pulseaudio
  gdm   31270 F pulseaudio
 /dev/snd/controlC0:  erik  22879 F pulseaudio
  gdm   31270 F pulseaudio
Date: Tue Mar  6 13:04:17 2018
Failure: oops
HibernationDevice: RESUME=UUID=fb731a76-d649-4283-9a48-91fda418f5d4
InstallationDate: Installed on 2018-02-25 (9 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225)
IwConfig:
 enp3s0no wireless extensions.
 
 enp8s0no wireless extensions.
 
 lono wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-11-generic 
root=UUID=269d199c-0dea-47bc-89fb-5388d4361c0e 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: kerneloops-daemon N/A
RfKill:
 
SourcePackage: linux
Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [Xorg:4873]
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/11/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: U1n
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z68X-UD3H-B3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrU1n:bd07/11/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ68X-UD3H-B3:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-kerneloops bionic kernel-oops package-from-proposed

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

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [Xorg:4873]

Status in linux package in Ubuntu:
  New

Bug description:
  during startup or before cold boot. System used a lot of resources,
  necessitating a reboot

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-11-generic 4.15.0-11.12
  ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
  Uname: Linux 4.15.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_uvm 
nvidia_drm nvidia_modeset nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  erik  22879 F pulseaudio
gdm   31270 F pulseaudio
   /dev/snd/controlC0:  erik  22879 F pulseaudio
gdm   31270 F pulseaudio
  Date: Tue Mar  6 13:04:17 2018
  Failure: oops
  HibernationDevice: RESUME=UUID=fb731a76-d649-4283-9a48-91fda418f5d4
  InstallationDate: Installed on 2018-02-25 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225)
  IwConfig:
   enp3s0no wireless extensions.
   
   enp8s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-11-generic 
root=UUID=269d199c-0dea-47bc-89fb-5388d4361c0e 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: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [Xorg:4873]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/11/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: U1n
  dmi.board.asset.tag: To be filled by