[Kernel-packages] [Bug 1664217] naumann (amd64) - tests ran: 7, failed: 3

2017-02-15 Thread Brad Figg
tests ran:   7, failed: 3;
  
http://kernel.ubuntu.com/testing/4.10.0-8.10-generic/naumann__4.10.0-8.10__2017-02-16_01-21-00/results-index.html

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

Title:
  linux: 4.10.0-8.10 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Fix Released
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:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: 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-development-workflow/+bug/1664217/+subscriptions

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


[Kernel-packages] [Bug 1665211] Re: Upgrade Redpine RS9113 driver to support AP mode

2017-02-15 Thread Shrirang Bagul
** Changed in: hwe-next
   Status: New => In Progress

** Changed in: hwe-next
   Importance: Undecided => Critical

** Changed in: hwe-next
 Assignee: (unassigned) => Shrirang Bagul (shrirang-bagul)

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

Title:
  Upgrade Redpine RS9113 driver to support AP mode

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress

Bug description:
  Redpine WLAN/BT RS9113 driver in Ubuntu Xenial kernel which supports Host AP 
mode.
  Release version: 0.9.8.2

  This is the latest version of the driver provided by Redpine. For now,
  this driver is enabled only on x86, x86_64 architectures.

  This bug is used for tracking purposes, please do not triage.

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

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


[Kernel-packages] [Bug 1630245] Re: after starting ubuntu 16.10 -- no keyboard, no mouse

2017-02-15 Thread Mentis
I have similar problem with 16.04.
I've tried following kernels 
4.4.0-63-generic
4.8.0-36-generic

The only kernel that works is:
4.9.0-040900-generic which I've installed long time ago

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

Title:
  after starting ubuntu 16.10 -- no keyboard, no mouse

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Yakkety:
  Incomplete

Bug description:
  After starting Ubuntu 16.10 keyboard and mouse are dead. Since it
  works with an older kernel but not with the latest one, I'd assume the
  newer kernel does not initialize the devices the right way.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9git1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Tue Oct  4 15:27:52 2016
  InstallationDate: Installed on 2012-12-12 (1391 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic 
root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago)
  dmi.bios.date: 07/02/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:bd07/02/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/1630245/+subscriptions

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


[Kernel-packages] [Bug 1665211] Re: Upgrade Redpine RS9113 driver to support AP mode

2017-02-15 Thread Shrirang Bagul
** Tags added: originate-from-1629193 plano

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

Title:
  Upgrade Redpine RS9113 driver to support AP mode

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  Redpine WLAN/BT RS9113 driver in Ubuntu Xenial kernel which supports Host AP 
mode.
  Release version: 0.9.8.2

  This is the latest version of the driver provided by Redpine. For now,
  this driver is enabled only on x86, x86_64 architectures.

  This bug is used for tracking purposes, please do not triage.

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

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


[Kernel-packages] [Bug 892544] Re: Unity slow after resume from suspend

2017-02-15 Thread Samir M
Bug is still present in Ubuntu 16.04 as of:
Linux 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:47:47 UTC 2017 x86_64 x86_64 
x86_64 GNU/Linux

As a note, the solution here fixes the slowdown:
http://askubuntu.com/questions/792605/ubuntu-16-04-lts-too-slow-after-suspend-and-resume

Seems like some problem with resetting the msr register after a suspend. More 
here :
https://bbs.archlinux.org/viewtopic.php?id=199922

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

Title:
  Unity slow after resume from suspend

Status in linux package in Ubuntu:
  Expired

Bug description:
  After resuming from suspend unity feels like it is very slow.

  How to play:

  Go to Unity Dash, show all applications, move icons up and down with
  the scroll bar, suspend and resume, perform the same operation and
  notice that is very slow.

  This already happens with the (cd or usb) of installation.

  This bug only happens with free radeon driver with driver fglrx does
  not happen.

  This only happens in unity, this does not happen in either Gnome Shell
  or Unity 2D.

  I do not know if it's a bug in Unity or compiz, but "unity --reset"
  solves the problem until the next suspend / resume.

  I do not know if this bug may be related to #782810 or #803943, but I
  did not notice any increase in CPU consumption.

  This bug occurs on a clean install of 11.10 [64 bits]   with a ATI
  Radeon 5770 graphics card,  Asus P6T Deluxe V2 Motherboard, Micro
  Intel Core™ i7-950 y SSD OCZ Vertex2.

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

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


[Kernel-packages] [Bug 1624339] Re: Elantech v4 trackpad no longer working after resuming for hibernate

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

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

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

Title:
  Elantech v4 trackpad no longer working after resuming for hibernate

Status in linux package in Ubuntu:
  Expired

Bug description:
  This is a Gigabyte AERO 14 laptop (http://www.gigabyte.com.au/products
  /product-page.aspx?pid=5902#kf)

  When laptop goes into hibernate mode, the trackpad will no longer work. 
Rebooting will not make the trackpad work again.
  The only work around I've found so far is to reboot into windows and then 
reboot into ubuntu.

  It is similar to bug 1490130; however here it's with hibernating and can't be 
recovered with rebooting (additionally, the kernel patch provided there doesn't 
work)
  Suspend works just fine.

  *** before hibernate

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab83
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input0
  U: Uniq=
  H: Handlers=sysrq kbd leds event0
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: 
Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:18/PNP0C09:01/PNP0C0D:00/input/input2
  U: Uniq=
  H: Handlers=event1
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0003 Version=
  N: Name="Sleep Button"
  P: Phys=PNP0C0E/button/input0
  S: 
Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:18/PNP0C09:01/PNP0C0E:00/input/input3
  U: Uniq=
  H: Handlers=kbd event2
  B: PROP=0
  B: EV=3
  B: KEY=4000 0 0

  I: Bus=0019 Vendor= Product=0003 Version=
  N: Name="Sleep Button"
  P: Phys=PNP0C0E/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:01/input/input4
  U: Uniq=
  H: Handlers=kbd event3
  B: PROP=0
  B: EV=3
  B: KEY=4000 0 0

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=PNP0C0C/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input5
  U: Uniq=
  H: Handlers=kbd event4
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input6
  U: Uniq=
  H: Handlers=kbd event5
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input8
  U: Uniq=
  H: Handlers=kbd event6
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus=0011 Vendor=0002 Product=000e Version=
  N: Name="ETPS/2 Elantech Touchpad"
  P: Phys=isa0060/serio1/input0
  S: Sysfs=/devices/platform/i8042/serio1/input/input7
  U: Uniq=
  H: Handlers=mouse1 event8
  B: PROP=5
  B: EV=b
  B: KEY=e420 1 0 0 0 0
  B: ABS=66180001103

  I: Bus=0003 Vendor=1044 Product=7a06 Version=0110
  N: Name="E-Signal Keyboard"
  P: Phys=usb-:00:14.0-5/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/0003:1044:7A06.0002/input/input10
  U: Uniq=
  H: Handlers=sysrq kbd leds event9
  B: PROP=0
  B: EV=120013
  B: KEY=10007 ff9f207ac14057ff febeffdfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0003 Vendor=1044 Product=7a06 Version=0110
  N: Name="E-Signal Keyboard"
  P: Phys=usb-:00:14.0-5/input1
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.1/0003:1044:7A06.0003/input/input11
  U: Uniq=
  H: Handlers=kbd mouse2 event10 js0
  B: PROP=0
  B: EV=10001f
  B: KEY=3f0003007f 0 0 48317aff32d bf56 1f0001 130f938b17c000 
677bfad9415fed 9ed6804400 1002
  B: REL=1c0
  B: ABS=10003
  B: MSC=10

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Headphone"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input12
  U: Uniq=
  H: Handlers=event11
  B: PROP=0
  B: EV=21
  B: SW=4

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=3"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input13
  U: Uniq=
  H: Handlers=event12
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=7"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input14
  U: Uniq=
  H: Handlers=event13
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=8"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input15
  U: Uniq=
  H: 

[Kernel-packages] [Bug 1615361] Re: Ubuntu 16.04 fails to boot on HP Envy 15-ah150sa laptop

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

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

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

Title:
  Ubuntu 16.04 fails to boot on HP Envy 15-ah150sa laptop

Status in linux package in Ubuntu:
  Expired

Bug description:
  Ubuntu 16.04.1 fails to boot on HP Envy 15-ah150sa laptop right after
  the installation.

  I tried to install Ubuntu v. 16.04.1 on my HP Envy 15-ah150sa. It
  successfully booted from the flash drive with default params (however,
  if I tried to edit command line params, for example, to disable acpi
  or add nomodeset flag, it fails to boot regardless if I made some
  changes in the command or not).

  Installation passes without errors, but during the first boot from hard 
drive, right after the GRUB, any of the following happens (absolutely randomly):
  1. Screen starts to blink constantly, boot doesn't proceeds
  2. Screen remains blank (the same background color as grub have) and capslock 
starts to turning on and off
  3. Screen remains blank and no more requests to HDD being performing

  In any of these three cases, laptop doesn't responds to ctrl-alt-del

  I tried to:
  0. Test memory, HDD and ISO image, install different versions of Ubuntu from 
different USB Flash drives.
  1. Update BIOS (now it is of latest version (F.14)) - only after that update 
Ubuntu booted from USB Flash drive.
  2. Disable/enable secure boot
  3. Add nomodeset
  4. Add acpi=off
  5. Boot in different modes

  Booting in recovery mode results to a lot of "General Protection Fault" 
errors.
  Booting in upstart mode once was successfull

  Not sure if this info will help, but I also tried to install latest
  Debian. It boots, but CPU usage appears to be constantly high. Same
  issue wasn't found when ran Ubuntu from USB.

  WORKAROUND: Use kernel boot parameter:
  acpi_no_static_ssdt

  ---
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 2249 F pulseaudio
   /dev/snd/controlC0:  ubuntu 2249 F pulseaudio
  CasperVersion: 1.378
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160902)
  MachineType: HP HP ENVY Notebook
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-9136-generic N/A
   linux-backports-modules-4.4.0-9136-generic  N/A
   linux-firmware  1.160
  Tags:  yakkety
  Uname: Linux 4.4.0-9136-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/28/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80BA
  dmi.board.vendor: HP
  dmi.board.version: 80.35
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd03/28/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn80BA:rvr80.35:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1584407] Re: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20150930/dswload-210)

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

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

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

Title:
  ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure,
  AE_NOT_FOUND (20150930/dswload-210)

Status in linux package in Ubuntu:
  Expired

Bug description:
  [ 0.016192] ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, 
AE_NOT_FOUND (20150930/dswload-210)
  [ 0.016195] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog 
(20150930/psobject-227)
  [ 0.016222] ACPI Exception: AE_NOT_FOUND, (SSDT:xh_rvp08) while loading table 
(20150930/tbxfload-193)
  [ 0.021348] ACPI Error: 1 table load failures, 7 successful 
(20150930/tbxfload-214)

  
  I have noticed this ACPI error persisting in my syslog and dmesg. Based on 
what I have learnt from  ACPI, acpitool -w and lspci, I think the error is 
related to Namespaces provided in the DDST on \_SB_.PCI0.XHC_.RHUB.HS11, which 
I think concerns the Root → System bus tree → PCI bus  → USB controller: Intel 
Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31) in my system. I 
have not found what .RHUB.HS11 refers too. I have tried changing my UEFI USB 
settings but to no avail. Appreciate help to fix this bug. 

  I reported it as a question
  https://answers.launchpad.net/ubuntu/+question/293489 and to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1553690.
  https://launchpad.net/~penalvch advice me to make this ubuntu-bug
  report.

  
  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  $ uname -r
  4.4.0-22-generic

  MB Bios: ASUS z170m-plus version 0704

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.40
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sunbear1604   1905 F pulseaudio
   /dev/snd/controlC0:  sunbear1604   1905 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun May 22 07:48:53 2016
  HibernationDevice: RESUME=UUID=c1eef599-9978-461e-a399-a04370b6ae59
  InstallationDate: Installed on 2016-05-01 (20 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp0s31f6  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB:
   0 EFI VGA
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=69a55da3-4a70-4239-8e7e-2430ceac525d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0704
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170M-PLUS
  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.:bvr0704:bd02/18/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170M-PLUS: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/1584407/+subscriptions

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


[Kernel-packages] [Bug 1620422] Re: Macbook Pro Retina 12, 1 SD Card Reader Doesn't Work

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

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

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

Title:
   Macbook Pro Retina 12,1 SD Card Reader Doesn't Work

Status in linux package in Ubuntu:
  Expired

Bug description:
  SD card reader doesn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.4.0-9136-generic 4.4.0-9136.55
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graingert   2672 F pulseaudio
   /dev/snd/controlC1:  graingert   2672 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Sep  6 00:39:03 2016
  InstallationDate: Installed on 2016-01-05 (244 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0273 Apple, Inc.
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic.efi.signed 
root=UUID=665d68d7-0c44-48e6-9e4c-9496a5c21d21 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-9136-generic N/A
   linux-backports-modules-4.4.0-9136-generic  N/A
   linux-firmware  1.160
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-09-05 (0 days ago)
  dmi.bios.date: 10/26/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B15.1510261437
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B15.1510261437:bd10/26/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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


[Kernel-packages] [Bug 1610028] Re: Power usage 50% worse than 14.04 on MacBook Air 6, 2

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

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

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

Title:
  Power usage 50% worse than 14.04 on MacBook Air 6,2

Status in linux package in Ubuntu:
  Expired

Bug description:
  Hi,

  I do not know which package/condition to attribute this behaviour to,
  but MBA running Ubuntu 14.04 is using about 50% of power that needs to
  be delivered for 16.04. (minumum 10W power draw vs minimum ~5W draw).

  Otherwise 16.04 works well.

  Any clue how to tackle this?

  
  Best,
  b.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bostjan3629 F pulseaudio
   /dev/snd/controlC1:  bostjan3629 F pulseaudio
  Date: Fri Aug  5 02:29:33 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=a1169bd1-3502-4168-a9f9-639255a224c0
  InstallationDate: Installed on 2016-08-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Apple Inc. MacBookAir6,2
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic.efi.signed 
root=/dev/mapper/as--u--vg-root ro quiet splash vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/07/2014
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA61.88Z.0099.B09.1402071141
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-7DF21CB3ED6977E5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir6,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-7DF21CB3ED6977E5
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA61.88Z.0099.B09.1402071141:bd02/07/2014:svnAppleInc.:pnMacBookAir6,2:pvr1.0:rvnAppleInc.:rnMac-7DF21CB3ED6977E5:rvrMacBookAir6,2:cvnAppleInc.:ct10:cvrMac-7DF21CB3ED6977E5:
  dmi.product.name: MacBookAir6,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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


[Kernel-packages] [Bug 1665211] [NEW] Upgrade Redpine RS9113 driver to support AP mode

2017-02-15 Thread Shrirang Bagul
Public bug reported:

Redpine WLAN/BT RS9113 driver in Ubuntu Xenial kernel which supports Host AP 
mode.
Release version: 0.9.8.2

This is the latest version of the driver provided by Redpine. For now,
this driver is enabled only on x86, x86_64 architectures.

This bug is used for tracking purposes, please do not triage.

** Affects: linux (Ubuntu)
 Importance: Critical
 Assignee: Shrirang Bagul (shrirang-bagul)
 Status: In Progress

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

Title:
  Upgrade Redpine RS9113 driver to support AP mode

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Redpine WLAN/BT RS9113 driver in Ubuntu Xenial kernel which supports Host AP 
mode.
  Release version: 0.9.8.2

  This is the latest version of the driver provided by Redpine. For now,
  this driver is enabled only on x86, x86_64 architectures.

  This bug is used for tracking purposes, please do not triage.

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

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


[Kernel-packages] [Bug 1664217] modoc (ppc64el) - tests ran: 10, failed: 0

2017-02-15 Thread Brad Figg
tests ran:  10, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-8.10-generic/modoc__4.10.0-8.10__2017-02-16_02-37-00/results-index.html

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

Title:
  linux: 4.10.0-8.10 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Fix Released
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:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: 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-development-workflow/+bug/1664217/+subscriptions

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


[Kernel-packages] [Bug 1660704] rumford (amd64) - tests ran: 34, failed: 0

2017-02-15 Thread Brad Figg
tests ran:  34, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-63.84-generic/rumford__4.4.0-63.84__2017-02-16_01-33-00/results-index.html

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

Title:
  linux: 4.4.0-63.84 -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-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
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 Xenial:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: 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/1660704/+subscriptions

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


[Kernel-packages] [Bug 1665097] Re: [Hyper-V] SAUCE: pci-hyperv fixes for SR-IOV on Azure

2017-02-15 Thread Dexuan Cui
I happened to see this bug and want to add one more patch:
https://git.kernel.org/cgit/linux/kernel/git/helgaas/pci.git/commit/?h=pci/host-hv=60e2e2fbafdd1285ae1b4ad39ded41603e0c74d0

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

Title:
  [Hyper-V] SAUCE: pci-hyperv fixes for SR-IOV on Azure

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

Bug description:
  The following two patches to pci-hyperv were submitted upstream but
  missed getting pulled into Bjorn's tree. They are needed to fix an
  issue discovered working on SR-IOV on Azure.

  Patch 1: hv_pci_devices_present is called in hv_pci_remove when we
  remove a PCI device from host (e.g. by disabling SRIOV on a device).
  In hv_pci_remove, the bus is already removed before the call, so we
  don't need to rescan the bus in the workqueue scheduled from
  hv_pci_devices_present. By introducing status hv_pcibus_removed, we
  can avoid this situation.

  Patch 2: A PCI_EJECT message can arrive at the same time we are
  calling pci_scan_child_bus in the workqueue for the previous
  PCI_BUS_RELATIONS message or in create_root_hv_pci_bus(), in this case
  we could potentailly modify the bus from multiple places. Properly
  lock the bus access.

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

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


[Kernel-packages] [Bug 1491654] Re: Intel P3700 PCIe SSD string shows ''Unknown'' during Ubuntu 14.04 installation

2017-02-15 Thread AaronLan
Leo will try the following kernels.

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

Title:
  Intel P3700 PCIe SSD string shows ''Unknown'' during Ubuntu 14.04
  installation

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  Current Behavior
  ==
  1. Intel P3700 PCIe SSD string shows "Unknow" during Ubuntu 14.04 install.

  Reference Verification
  ==
  1. Which version of previous BIOS/BMC/HW passed/failed? 1st Test
  2. Which similar project/product passed/failed? NA

  Steps to reproduce the problem
  ==
  1. Install Intel P3700 PCIe SSD*2 and SAS 12G HDD*8 with LSI 3108 into SUT.
  2. Power on system and install Ubuntu 14.04.
  3. Intel P3700 PCIe SSD string shows "Unknown" during OS install.

  Expected Behavior
  ==
  1. Intel P3700 PCIe SSD string should not show "Unknown" during Ubuntu 14.04 
install.

  Pcie SSD config:HDD/SSD:Intel,SSDPE2MD016T4,PCI-e,1.6TB,Gen3

  Copied from private bug:
  https://bugs.launchpad.net/quantatw/+bug/1454965

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

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


[Kernel-packages] [Bug 1647694] Re: Broadcom 4352 not installing module for Kernel 4.8.0-30

2017-02-15 Thread Jeff
This is resolved or at least not reproducible in the 4.8.0.36 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/1647694

Title:
  Broadcom 4352 not installing module for Kernel 4.8.0-30

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When installing Kernel 4.8.0-30, over existing Kernel 4.4.0-51 with a
  Broadcom 4352 wireless device, the kernel install fails to install the
  kernel module, resulting in wireless connectivity being inoperative.

  lscpi-vnvn.log attached.  Version log is not the kernel in question.
  Linux Mint 18 Sarah  RELEASE 18

  Expected the WL driver module to be installed for the 4.8.0-30 kernel and for 
wireless networking to function as a result.   Actual result, error in install, 
prevents kernel module from installing correctly and precludes wireless 
networking functionality.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jag2030 F pulseaudio
   /dev/snd/controlC3:  jag2030 F pulseaudio
   /dev/snd/controlC2:  jag2030 F pulseaudio
   /dev/snd/controlC0:  jag2030 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18
  HibernationDevice: RESUME=UUID=bc762603-aa60-4343-a125-bbda5dcf5340
  InstallationDate: Installed on 2016-07-04 (155 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  MachineType: ASUS All Series
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=a414df14-dae7-4f65-8614-a21b2e4a2061 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-53-generic N/A
   linux-backports-modules-4.4.0-53-generic  N/A
   linux-firmware1.157.5
  Tags:  sarah
  Uname: Linux 4.4.0-53-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2702
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-PRO(Wi-Fi ac)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO(Wi-Fiac):rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jag2006 F pulseaudio
   /dev/snd/controlC3:  jag2006 F pulseaudio
   /dev/snd/controlC2:  jag2006 F pulseaudio
   /dev/snd/controlC0:  jag2006 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18
  HibernationDevice: RESUME=UUID=bc762603-aa60-4343-a125-bbda5dcf5340
  InstallationDate: Installed on 2016-07-04 (155 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  MachineType: ASUS All Series
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=a414df14-dae7-4f65-8614-a21b2e4a2061 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-53-generic N/A
   linux-backports-modules-4.4.0-53-generic  N/A
   linux-firmware1.157.5
  Tags:  sarah
  Uname: Linux 4.4.0-53-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2702
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-PRO(Wi-Fi ac)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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: 

[Kernel-packages] [Bug 1664217] modoc (ppc64el) - tests ran: 19, failed: 1

2017-02-15 Thread Brad Figg
tests ran:  19, failed: 1;
  
http://kernel.ubuntu.com/testing/4.10.0-8.10-generic/modoc__4.10.0-8.10__2017-02-16_01-19-00/results-index.html

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

Title:
  linux: 4.10.0-8.10 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Fix Released
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:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: 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-development-workflow/+bug/1664217/+subscriptions

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


[Kernel-packages] [Bug 1650058] Re: [Hyper-V/Azure] Please include Mellanox OFED drivers in Azure kernel and image

2017-02-15 Thread Joseph Salisbury
I built a Xenial test kernel with the four patches. The test kernel can
be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1650058/xenial/

Can you test this kernel and see if it resolves this 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/1650058

Title:
  [Hyper-V/Azure] Please include Mellanox OFED drivers in Azure kernel
  and image

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

Bug description:
  In order to have the correct VF driver to support SR-IOV in Azure, the
  Mellanox OFED distribution needs to be included in the kernel and the
  image. Mellanox's drivers are not upstream, but they are available
  from here:

  
https://www.mellanox.com/page/products_dyn?product_family=26=linux_sw_drivers=3nnhohirh5htv6dnp1uk7tf487

  While this configuration is not explicitly listed as supported in the
  release notes, Microsoft and Mellanox engineers are working on the
  corresponding Windows Server 2016 PF driver to support this VF driver
  in operation in Ubuntu guests.

  I file file a corresponding rebase request to pick up the PCI
  passthrough and other SR-IOV work done for the Hyper-V capabilities in
  the upstream 4.9 kernel.

  Only 64-bit support for Ubuntu 16.04's HWE kernel is needed.

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

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


[Kernel-packages] [Bug 1664217] gonzo (amd64) - tests ran: 64, failed: 0

2017-02-15 Thread Brad Figg
tests ran:  64, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-8.10-generic/gonzo__4.10.0-8.10__2017-02-16_01-10-00/results-index.html

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

Title:
  linux: 4.10.0-8.10 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Fix Released
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:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: 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-development-workflow/+bug/1664217/+subscriptions

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


[Kernel-packages] [Bug 1665097] Re: [Hyper-V] SAUCE: pci-hyperv fixes for SR-IOV on Azure

2017-02-15 Thread Joseph Salisbury
I built a Xenial test kernel with the two patches.  The test kernel can
be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1665097/xenial/

Can you test this kernel and see if it resolves this 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/1665097

Title:
  [Hyper-V] SAUCE: pci-hyperv fixes for SR-IOV on Azure

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

Bug description:
  The following two patches to pci-hyperv were submitted upstream but
  missed getting pulled into Bjorn's tree. They are needed to fix an
  issue discovered working on SR-IOV on Azure.

  Patch 1: hv_pci_devices_present is called in hv_pci_remove when we
  remove a PCI device from host (e.g. by disabling SRIOV on a device).
  In hv_pci_remove, the bus is already removed before the call, so we
  don't need to rescan the bus in the workqueue scheduled from
  hv_pci_devices_present. By introducing status hv_pcibus_removed, we
  can avoid this situation.

  Patch 2: A PCI_EJECT message can arrive at the same time we are
  calling pci_scan_child_bus in the workqueue for the previous
  PCI_BUS_RELATIONS message or in create_root_hv_pci_bus(), in this case
  we could potentailly modify the bus from multiple places. Properly
  lock the bus access.

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

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


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

2017-02-15 Thread Brad Figg
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/1665182

Title:
  package linux-image-4.4.0-62-generic 4.4.0-62.83 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I had been cleaning out old kernel images because my /boot/ directory
  was full and I couldn't install updates.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-62-generic 4.4.0-62.83
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  user   2387 F pulseaudio
   /dev/snd/controlC0:  user   2387 F pulseaudio
  Date: Wed Feb 15 10:37:33 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  InstallationDate: Installed on 2016-02-20 (361 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Dell Inc. Inspiron 7547
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-62-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-image-4.4.0-62-generic 4.4.0-62.83 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to xenial on 2016-10-04 (134 days ago)
  dmi.bios.date: 05/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0AM670
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd05/15/2015:svnDellInc.:pnInspiron7547:pvrNotSpecified:rvnDellInc.:rn0AM670:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 7547
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1665182] Re: package linux-image-4.4.0-62-generic 4.4.0-62.83 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2017-02-15 Thread 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1665182

Title:
  package linux-image-4.4.0-62-generic 4.4.0-62.83 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I had been cleaning out old kernel images because my /boot/ directory
  was full and I couldn't install updates.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-62-generic 4.4.0-62.83
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  user   2387 F pulseaudio
   /dev/snd/controlC0:  user   2387 F pulseaudio
  Date: Wed Feb 15 10:37:33 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  InstallationDate: Installed on 2016-02-20 (361 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Dell Inc. Inspiron 7547
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-62-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-image-4.4.0-62-generic 4.4.0-62.83 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to xenial on 2016-10-04 (134 days ago)
  dmi.bios.date: 05/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0AM670
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd05/15/2015:svnDellInc.:pnInspiron7547:pvrNotSpecified:rvnDellInc.:rn0AM670:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 7547
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1661699] Re: linux: 3.19.0-81.89 -proposed tracker

2017-02-15 Thread Taihsiang Ho
Set the status of "Certification-testing" as "Invalid" according to the
sync up meeting of Cert and 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/1661699

Title:
  linux: 3.19.0-81.89 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: 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/1661699/+subscriptions

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


[Kernel-packages] [Bug 1665182] [NEW] package linux-image-4.4.0-62-generic 4.4.0-62.83 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2017-02-15 Thread druddha
Public bug reported:

I had been cleaning out old kernel images because my /boot/ directory
was full and I couldn't install updates.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-62-generic 4.4.0-62.83
ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
Uname: Linux 4.4.0-62-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  user   2387 F pulseaudio
 /dev/snd/controlC0:  user   2387 F pulseaudio
Date: Wed Feb 15 10:37:33 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 2
InstallationDate: Installed on 2016-02-20 (361 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
MachineType: Dell Inc. Inspiron 7547
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-62-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-image-4.4.0-62-generic 4.4.0-62.83 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: Upgraded to xenial on 2016-10-04 (134 days ago)
dmi.bios.date: 05/15/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0AM670
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd05/15/2015:svnDellInc.:pnInspiron7547:pvrNotSpecified:rvnDellInc.:rn0AM670:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 7547
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.

** Affects: linux (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 in Ubuntu.
https://bugs.launchpad.net/bugs/1665182

Title:
  package linux-image-4.4.0-62-generic 4.4.0-62.83 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in linux package in Ubuntu:
  New

Bug description:
  I had been cleaning out old kernel images because my /boot/ directory
  was full and I couldn't install updates.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-62-generic 4.4.0-62.83
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  user   2387 F pulseaudio
   /dev/snd/controlC0:  user   2387 F pulseaudio
  Date: Wed Feb 15 10:37:33 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  InstallationDate: Installed on 2016-02-20 (361 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Dell Inc. Inspiron 7547
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-62-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-image-4.4.0-62-generic 4.4.0-62.83 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to xenial on 2016-10-04 (134 days ago)
  dmi.bios.date: 05/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0AM670
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd05/15/2015:svnDellInc.:pnInspiron7547:pvrNotSpecified:rvnDellInc.:rn0AM670:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 7547
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1661699] Re: linux: 3.19.0-81.89 -proposed tracker

2017-02-15 Thread Taihsiang Ho
** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => Invalid

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

Title:
  linux: 3.19.0-81.89 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: 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/1661699/+subscriptions

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


[Kernel-packages] [Bug 1664217] naumann (amd64) - tests ran: 10, failed: 1

2017-02-15 Thread Brad Figg
tests ran:  10, failed: 1;
  
http://kernel.ubuntu.com/testing/4.10.0-8.10-generic/naumann__4.10.0-8.10__2017-02-15_22-19-00/results-index.html

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

Title:
  linux: 4.10.0-8.10 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Fix Released
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:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: 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-development-workflow/+bug/1664217/+subscriptions

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


[Kernel-packages] [Bug 1664217] modoc (ppc64el) - tests ran: 1, failed: 0

2017-02-15 Thread Brad Figg
tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-8.10-generic/modoc__4.10.0-8.10__2017-02-16_00-34-00/results-index.html

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

Title:
  linux: 4.10.0-8.10 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Fix Released
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:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: 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-development-workflow/+bug/1664217/+subscriptions

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


[Kernel-packages] [Bug 1664217] gonzo (i386) - tests ran: 2, failed: 2

2017-02-15 Thread Brad Figg
tests ran:   2, failed: 2;
  
http://kernel.ubuntu.com/testing/4.10.0-8.10-generic/gonzo__4.10.0-8.10__2017-02-16_00-29-00/results-index.html

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

Title:
  linux: 4.10.0-8.10 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Fix Released
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:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: 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-development-workflow/+bug/1664217/+subscriptions

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


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

2017-02-15 Thread Brad Figg
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1664912

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

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

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

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

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

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

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

Title:
  linux-lts-xenial 4.4.0-63.84~14.04.2 ADT test failure with linux-lts-
  xenial 4.4.0-63.84~14.04.2

Status in linux package in Ubuntu:
  Incomplete
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Invalid
Status in linux-lts-xenial source package in Trusty:
  New
Status in linux source package in Xenial:
  Incomplete
Status in linux-lts-xenial source package in Xenial:
  Invalid
Status in linux source package in Yakkety:
  Incomplete
Status in linux-lts-xenial source package in Yakkety:
  Invalid
Status in linux source package in Zesty:
  Incomplete
Status in linux-lts-xenial source package in Zesty:
  Invalid

Bug description:
  Testing failed on:
amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/linux-lts-xenial/20170214_051856_a19a2@/log.gz

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

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


[Kernel-packages] [Bug 1664912] Re: linux-lts-xenial 4.4.0-63.84~14.04.2 ADT test failure with linux-lts-xenial 4.4.0-63.84~14.04.2

2017-02-15 Thread John Johansen
** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

** Also affects: linux-lts-xenial (Ubuntu Zesty)
   Importance: High
   Status: New

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

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

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

** Also affects: linux-lts-xenial (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

** Changed in: linux-lts-xenial (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Zesty)
   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/1664912

Title:
  linux-lts-xenial 4.4.0-63.84~14.04.2 ADT test failure with linux-lts-
  xenial 4.4.0-63.84~14.04.2

Status in linux package in Ubuntu:
  Incomplete
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Invalid
Status in linux-lts-xenial source package in Trusty:
  New
Status in linux source package in Xenial:
  Incomplete
Status in linux-lts-xenial source package in Xenial:
  Invalid
Status in linux source package in Yakkety:
  Incomplete
Status in linux-lts-xenial source package in Yakkety:
  Invalid
Status in linux source package in Zesty:
  Incomplete
Status in linux-lts-xenial source package in Zesty:
  Invalid

Bug description:
  Testing failed on:
amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/linux-lts-xenial/20170214_051856_a19a2@/log.gz

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

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


[Kernel-packages] [Bug 1641235] Re: Ubuntu 16.10: kdump over nfs did not generate complete vmcore

2017-02-15 Thread bugproxy
--- Comment From ru...@us.ibm.com 2017-02-15 18:17 EDT---
Verified version 1:1.5.9-5ubuntu0.4.  NFS vmcore saved with no issues and with 
new settings.

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

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

Title:
  Ubuntu 16.10: kdump over nfs did not generate complete vmcore

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Trusty:
  Confirmed
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in makedumpfile source package in Yakkety:
  Confirmed

Bug description:
  == Comment: #0 - HARSHA THYAGARAJA - 2016-11-03 08:05:59 ==
  ---Problem Description---
  kdump over nfs did not generate complete vmcore
   
  ---uname output---
  Linux ltciofvtr-firestone1 4.8.0-26-generic #28-Ubuntu SMP Tue Oct 18 
14:41:40 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = PowerNV (Baremetal) - Firestone 
   
  ---Steps to Reproduce---
   1. Setup NFS
  2. Trigger crash: echo c > /proc/sysrq-trigger

  
  == Comment: #6 - Kevin W. Rudd - 2016-11-04 16:30:49 ==

  Hi Harsha.

  It looks like the base kdump NFS functionality works just fine.  The
  known issue with makedumpfile is causing it to drop back to using "cp"
  to transfer the entire, non-compressed /proc/vmcore image.  That's a
  rather large amount of data to send over to the remote server, and it
  appears to be sending back an I/O error after the first 122G.

  Further debug would need to be done to determine if this is a client-
  side or server-side issue.  I recommend first bringing your remote NFS
  server up to the current release as it is currently a bit down-rev.

  == Comment: #8 - HARSHA THYAGARAJA  - 2016-11-10 02:02:31 ==

  Hi Kevin,
  I updated my peer to Ubuntu 16.10 and still saw the same observation. 
  A snippet of the problem at hand is pasted below. 

  [   20.610748] kdump-tools[4559]: Starting kdump-tools:  * Mounting NFS 
mountpoint 150.1.1.20:/home/tools ...
  [   53.400516] kdump-tools[4559]:  * Dumping to NFS mountpoint 
150.1.1.20:/home/tools/201611100158
  [   53.409242] kdump-tools[4559]:  * running makedumpfile -c -d 31 
/proc/vmcore /mnt/var/crash/9.47.84.18-201611100158/dump-incomplete
  [   53.526593] kdump-tools[4559]: get_mem_map: Can't distinguish the memory 
type.
  [   53.527154] kdump-tools[4559]: The kernel version is not supported.
  [   53.527488] kdump-tools[4559]: The makedumpfile operation may be 
incomplete.
  [   53.527813] kdump-tools[4559]: makedumpfile Failed.
  [   53.528117] kdump-tools[4559]:  * kdump-tools: makedumpfile failed, 
falling back to 'cp'
  [   90.754092] kdump-tools[4559]: cp: error writing 
'/mnt/var/crash/9.47.84.18-201611100158/vmcore-incomplete': Input/output error
  [   90.754857] kdump-tools[4559]:  * kdump-tools: failed to save vmcore in 
/mnt/var/crash/9.47.84.18-201611100158
  [   90.756155] kdump-tools[4559]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /mnt/var/crash/9.47.84.18-201611100158/dmesg.201611100158
  [   90.758731] kdump-tools[4559]: get_mem_map: Can't distinguish the memory 
type.
  [   90.759089] kdump-tools[4559]: The kernel version is not supported.
  [   90.759436] kdump-tools[4559]: The makedumpfile operation may be 
incomplete.
  [   90.759780] kdump-tools[4559]: makedumpfile Failed.
  [   90.760094] kdump-tools[4559]:  * kdump-tools: makedumpfile --dump-dmesg 
failed. dmesg content will be unavailable
  [   90.760668] kdump-tools[4559]:  * kdump-tools: failed to save dmesg 
content in /mnt/var/crash/9.47.84.18-201611100158
  [   90.846117] kdump-tools[4559]: Thu, 10 Nov 2016 01:59:56 -0500
  [   90.886629] kdump-tools[4559]: Failed to read reboot parameter file: No 
such file or directory
  [   90.887070] kdump-tools[4559]: Rebooting.

  == Comment: #13 - Kevin W. Rudd  - 2016-11-11 17:12:33 ==

  I was able to replicate this with debugging at both the kdump client
  and remote NFS server.  The server was perfectly happy with the data
  coming at it, and appeared to be processing a COMMIT request from the
  client when the client shut down the connection.

  Looking at the client-side logs after a failure showed that it was
  logging "server ... not responding" messages, and bailed on the
  connection within the span of just a few seconds.

  This appears to be due to a very over-aggressive timeout being
  specified in /usr/sbin/kdump-config:

  mount -t nfs -o nolock -o tcp -o soft -o timeo=5 -o retrans=5 $NFS
  $KDUMP_COREDIR

  The timeo value is deciseconds, and "5" is far too aggressive for this
  type of connection.  From my observations, the COMMIT was not issued
  until about 60G was transferred, and most remote servers will take a
  lot longer than 5 tenths of a second to flush that amount of data and
  respond to the COMMIT.

  I'm not sure what problem specifying this timeo 

[Kernel-packages] [Bug 1239109] Re: aarch64 clock_gettime with CLOCK_REALTIME_COARSE or CLOCK_MONOTONIC_COARSE fails with SIGBUS or SIGSEGV

2017-02-15 Thread Jon Grimm
Any idea if this is really fixed now or not.  Asking as there appears to
be a workaround patch carried around in libqb that seems possible to
drop if so:

"
- debian/patches/aarch64_no_coarse_clock.patch: Avoid
  CLOCK_REALTIME_COARSE on aarch64 due to a kernel bug.
"

Adding libqb task to help remember to remove that patch if this bug
closes .

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

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

Title:
  aarch64 clock_gettime with CLOCK_REALTIME_COARSE or
  CLOCK_MONOTONIC_COARSE fails with SIGBUS or SIGSEGV

Status in libqb package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The aarch64 vDSO __kernel_clock_gettime implementation crashes when
  clock_gettime is called with CLOCK_MONOTONIC_COARSE or
  CLOCK_REALTIME_COARSE, with a SIGSEGV or SIGBUS respectively.

  In the implementation
  
(http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm64/kernel/vdso/gettimeofday.S#n89)
  a value other than CLOCK_REALTIME or CLOCK_MONOTONIC branches past the
  usual "mov x2, x30" which preserves lr for return later. Anything
  other than CLOCK_REALTIME_COARSE and CLOCK_MONOTONIC_COARSE then
  branches directly to the svc call, which correctly returns to the
  caller. But CLOCK_REALTIME_COARSE and CLOCK_MONOTONIC_COARSE execute
  the special coarse path then fall through to the normal
  CLOCK_REALTIME/CLOCK_MONOTONIC path, which does a 'ret x2' at the end,
  despite not having saved x30 to x2 in the _COARSE case. So it ends up
  setting pc to clk_id, which is either 4 or 5, giving a translation or
  alignment fault.

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

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


[Kernel-packages] [Bug 1664217] amura (amd64) - tests ran: 2, failed: 0

2017-02-15 Thread Brad Figg
tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-8.10-generic/amura__4.10.0-8.10__2017-02-15_21-47-00/results-index.html

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

Title:
  linux: 4.10.0-8.10 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Fix Released
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:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: 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-development-workflow/+bug/1664217/+subscriptions

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


[Kernel-packages] [Bug 1634449] Re: Black flicker when leaving monitor

2017-02-15 Thread Max Goodman
I am experiencing this issue as well on 16.10 on my X1 Carbon 3rd gen
(Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz / HD Graphics 5500 (rev 09)).
Tried mainline kernels 4.9.9, 4.9.10, and 4.10.0-997-drm-intel-next, and
reproduced the issue on all. Also tried pinning libdrm2/linux-firmware
/xserver-xorg-* to zesty versions, as well as installing intel-
microcode, which made no difference. Xorg is running the modesetting
driver.

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

Title:
  Black flicker when leaving monitor

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Sometimes, when moving cursor from one monitor to the other, the
  external monitor turns black and gets back on again.

  The hardware is Dell Latitude E5470 with Docking Station and monitor
  connected via DisplayPort (checked both ports and happens on both of
  them).

  Everything worked correctly on Ubuntu 16.04, but it happens on Ubuntu
  16.10. Kernel 4.8.0-25-generic.

  The bug isn't related to cursor only, if focus changes by alt+tab it
  sometimes happens as well.

  
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1553503 This is the same 
bug as this one, but closed.
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   vessel 5602 F...m pulseaudio
   /dev/snd/controlC0:  vessel 5602 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=56fab9c8-7226-47b9-91cb-a2c865f81bc0
  InstallationDate: Installed on 2016-08-31 (47 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Latitude E5470
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-25-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-25-generic N/A
   linux-backports-modules-4.8.0-25-generic  N/A
   linux-firmware1.161
  Tags:  yakkety
  Uname: Linux 4.8.0-25-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (3 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/15/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.3
  dmi.board.name: 0P88J9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.3:bd06/15/2016:svnDellInc.:pnLatitudeE5470:pvr:rvnDellInc.:rn0P88J9:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5470
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1634449] Re: Black flicker when leaving monitor

2017-02-15 Thread Max Goodman
This appears to be a problem with the modesetting Xorg driver. After
switching back to the intel driver (sudo cp /usr/share/doc/xserver-xorg-
video-intel/xorg.conf /etc/X11/) I haven't seen this recur yet.

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

Title:
  Black flicker when leaving monitor

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Sometimes, when moving cursor from one monitor to the other, the
  external monitor turns black and gets back on again.

  The hardware is Dell Latitude E5470 with Docking Station and monitor
  connected via DisplayPort (checked both ports and happens on both of
  them).

  Everything worked correctly on Ubuntu 16.04, but it happens on Ubuntu
  16.10. Kernel 4.8.0-25-generic.

  The bug isn't related to cursor only, if focus changes by alt+tab it
  sometimes happens as well.

  
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1553503 This is the same 
bug as this one, but closed.
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   vessel 5602 F...m pulseaudio
   /dev/snd/controlC0:  vessel 5602 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=56fab9c8-7226-47b9-91cb-a2c865f81bc0
  InstallationDate: Installed on 2016-08-31 (47 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Latitude E5470
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-25-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-25-generic N/A
   linux-backports-modules-4.8.0-25-generic  N/A
   linux-firmware1.161
  Tags:  yakkety
  Uname: Linux 4.8.0-25-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (3 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/15/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.3
  dmi.board.name: 0P88J9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.3:bd06/15/2016:svnDellInc.:pnLatitudeE5470:pvr:rvnDellInc.:rn0P88J9:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5470
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1651981] Re: shaking screen

2017-02-15 Thread Christopher M. Penalver
** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/1651981

Title:
  shaking screen

Status in linux package in Ubuntu:
  Triaged

Bug description:
  After login into Ubuntu the screen starts to shake permanently.
  The login screen is still fine, problem start after log in.
  The problem is caused by last kernel update: running Ubuntu with the older 
kernel 4.8.0-30-generic fixes the issue.

  Upstream patch submission:
  https://lists.freedesktop.org/archives/dri-devel/2016-December/128331.html

  WORKAROUND: Revert:
  # first bad commit: [9cc4fd5b9fbb0d74e77c81521da1e2fe712f6787] 
drm/radeon/si_dpm: workaround for SI kickers

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-32-generic 4.8.0-32.34
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  afiergol   7797 F pulseaudio
   /dev/snd/controlC1:  afiergol   7797 F pulseaudio
   /dev/snd/seq:timidity   6155 F timidity
  Date: Thu Dec 22 10:02:30 2016
  HibernationDevice: RESUME=UUID=7ca97ca1-ca2d-43f6-9b4c-cd61421c0831
  InstallationDate: Installed on 2015-04-02 (629 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Hewlett-Packard HP ZBook 15 G2
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-32-generic 
root=/dev/mapper/ubuntu--vg-root ro radeon.dpm=1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-32-generic N/A
   linux-backports-modules-4.8.0-32-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-16 (66 days ago)
  dmi.bios.date: 04/25/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M70 Ver. 01.15
  dmi.board.name: 2253
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 03.12
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM70Ver.01.15:bd04/25/2016:svnHewlett-Packard:pnHPZBook15G2:pvrA3008CD10003:rvnHewlett-Packard:rn2253:rvrKBCVersion03.12:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ZBook 15 G2
  dmi.product.version: A3008CD10003
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1660704] rumford (amd64) - tests ran: 19, failed: 0

2017-02-15 Thread Brad Figg
tests ran:  19, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-63.84-generic/rumford__4.4.0-63.84__2017-02-15_20-48-00/results-index.html

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

Title:
  linux: 4.4.0-63.84 -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-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
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 Xenial:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: 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/1660704/+subscriptions

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


[Kernel-packages] [Bug 1664217] secchi (amd64) - tests ran: 19, failed: 1

2017-02-15 Thread Brad Figg
tests ran:  19, failed: 1;
  
http://kernel.ubuntu.com/testing/4.10.0-8.10-generic/secchi__4.10.0-8.10__2017-02-15_20-44-00/results-index.html

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

Title:
  linux: 4.10.0-8.10 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Fix Released
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:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: 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-development-workflow/+bug/1664217/+subscriptions

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


[Kernel-packages] [Bug 1664217] gonzo (amd64) - tests ran: 141, failed: 0

2017-02-15 Thread Brad Figg
tests ran: 141, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-8.10-generic/gonzo__4.10.0-8.10__2017-02-15_20-51-00/results-index.html

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

Title:
  linux: 4.10.0-8.10 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Fix Released
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:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: 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-development-workflow/+bug/1664217/+subscriptions

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


[Kernel-packages] [Bug 1664217] naumann (amd64) - tests ran: 19, failed: 1

2017-02-15 Thread Brad Figg
tests ran:  19, failed: 1;
  
http://kernel.ubuntu.com/testing/4.10.0-8.10-generic/naumann__4.10.0-8.10__2017-02-15_20-52-00/results-index.html

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

Title:
  linux: 4.10.0-8.10 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Fix Released
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:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: 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-development-workflow/+bug/1664217/+subscriptions

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


[Kernel-packages] [Bug 1650058] Re: [Hyper-V/Azure] Please include Mellanox OFED drivers in Azure kernel and image

2017-02-15 Thread Joshua R. Poulson
Mellanox just sent me another one:
6496bbf0ec48 net/mlx4_en: Fix bad WQE 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/1650058

Title:
  [Hyper-V/Azure] Please include Mellanox OFED drivers in Azure kernel
  and image

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

Bug description:
  In order to have the correct VF driver to support SR-IOV in Azure, the
  Mellanox OFED distribution needs to be included in the kernel and the
  image. Mellanox's drivers are not upstream, but they are available
  from here:

  
https://www.mellanox.com/page/products_dyn?product_family=26=linux_sw_drivers=3nnhohirh5htv6dnp1uk7tf487

  While this configuration is not explicitly listed as supported in the
  release notes, Microsoft and Mellanox engineers are working on the
  corresponding Windows Server 2016 PF driver to support this VF driver
  in operation in Ubuntu guests.

  I file file a corresponding rebase request to pick up the PCI
  passthrough and other SR-IOV work done for the Hyper-V capabilities in
  the upstream 4.9 kernel.

  Only 64-bit support for Ubuntu 16.04's HWE kernel is needed.

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

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


[Kernel-packages] [Bug 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument

2017-02-15 Thread Mike Rushton
@Christian

The qemu fix is still necessary in order to resolve the issue.

While I do have access to the hardware, it is currently having issues
booting. Once we resolve the issue with IBM, I plan on testing out the
qemu fix from the PPA.

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

Title:
  Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu
  failed: Invalid argument

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

Bug description:
  Upon running the virtualization test from the certification test
  suite, the kvm guest test fails with the following error:

  kvm_init_vcpu failed: Invalid argument

  This same test works on multiple other IBM Power 8 and Openpower
  servers. kvm-ok tells us that kvm virtualization is supported. I have
  tried with SMT enabled and disabled. I have tried the latest cloud
  image as well as previous onces we had saved. I have tried running the
  qemu-system-ppc64 command found below manually with the same error.

  
  The full output from the test is as follows:

  Executing KVM Test
  DEBUG:root:Starting KVM Test
  DEBUG:root:Cloud image location specified: 
http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img.
  DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from 
http://10.1.10.2
  DEBUG:root:Creating cloud user-data
  DEBUG:root:Creating cloud meta-data
  I: -input-charset not specified, using utf-8 (detected in locale settings)
  Total translation table size: 0
  Total rockridge attributes bytes: 331
  Total directory bytes: 0
  Path table size(bytes): 10
  Max brk space used 0
  183 extents written (0 MB)
  DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img
  DEBUG:root:Attaching Cloud config disk
  DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic 
-net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 
-enable-kvm -machine pseries,usb=off -cpu POWER8 -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  INFO:root:Storing VM console output in 
/home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 22:18 seq
   crw-rw 1 root audio 116, 33 Jan 12 22:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: ppc64el
  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: Thu Jan 12 22:45:34 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 
Pro
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard 
and Mouse
   Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1
  ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 3709 00:14:665 0 EOF
   2: POSIX  ADVISORY  WRITE 3593 00:14:655 0 EOF
   3: POSIX  ADVISORY  WRITE 1658 00:14:376 0 EOF
   4: FLOCK  ADVISORY  WRITE 3560 00:14:637 0 EOF
   5: POSIX  ADVISORY  WRITE 3571 00:14:640 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc 
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri 
Jan 6 17:35:59 UTC 2017
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_dscr: DSCR is 0
  cpu_freq:
   min: 3.959 GHz (cpu 79)
   max: 3.988 GHz (cpu 81)
   avg: 3.974 GHz
  cpu_runmode:
   Could 

[Kernel-packages] [Bug 1664217] gonzo (i386) - tests ran: 6, failed: 2

2017-02-15 Thread Brad Figg
tests ran:   6, failed: 2;
  
http://kernel.ubuntu.com/testing/4.10.0-8.10-generic/gonzo__4.10.0-8.10__2017-02-15_19-38-00/results-index.html

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

Title:
  linux: 4.10.0-8.10 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Fix Released
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:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: 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-development-workflow/+bug/1664217/+subscriptions

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


[Kernel-packages] [Bug 1664217] naumann (amd64) - tests ran: 1, failed: 0

2017-02-15 Thread Brad Figg
tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-8.10-generic/naumann__4.10.0-8.10__2017-02-15_20-25-00/results-index.html

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

Title:
  linux: 4.10.0-8.10 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Fix Released
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:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: 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-development-workflow/+bug/1664217/+subscriptions

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


[Kernel-packages] [Bug 1664217] fozzie (i386) - tests ran: 19, failed: 0

2017-02-15 Thread Brad Figg
tests ran:  19, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-8.10-generic/fozzie__4.10.0-8.10__2017-02-15_19-29-00/results-index.html

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

Title:
  linux: 4.10.0-8.10 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Fix Released
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:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: 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-development-workflow/+bug/1664217/+subscriptions

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


[Kernel-packages] [Bug 1665097] Re: [Hyper-V] SAUCE: pci-hyperv fixes for SR-IOV on Azure

2017-02-15 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch

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

Title:
  [Hyper-V] SAUCE: pci-hyperv fixes for SR-IOV on Azure

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

Bug description:
  The following two patches to pci-hyperv were submitted upstream but
  missed getting pulled into Bjorn's tree. They are needed to fix an
  issue discovered working on SR-IOV on Azure.

  Patch 1: hv_pci_devices_present is called in hv_pci_remove when we
  remove a PCI device from host (e.g. by disabling SRIOV on a device).
  In hv_pci_remove, the bus is already removed before the call, so we
  don't need to rescan the bus in the workqueue scheduled from
  hv_pci_devices_present. By introducing status hv_pcibus_removed, we
  can avoid this situation.

  Patch 2: A PCI_EJECT message can arrive at the same time we are
  calling pci_scan_child_bus in the workqueue for the previous
  PCI_BUS_RELATIONS message or in create_root_hv_pci_bus(), in this case
  we could potentailly modify the bus from multiple places. Properly
  lock the bus access.

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

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


[Kernel-packages] [Bug 1664217] secchi (amd64) - tests ran: 1, failed: 0

2017-02-15 Thread Brad Figg
tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-8.10-generic/secchi__4.10.0-8.10__2017-02-15_20-19-00/results-index.html

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

Title:
  linux: 4.10.0-8.10 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Fix Released
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:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: 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-development-workflow/+bug/1664217/+subscriptions

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


[Kernel-packages] [Bug 1665097] Re: [Hyper-V] SAUCE: pci-hyperv fixes for SR-IOV on Azure

2017-02-15 Thread Joseph Salisbury
** Tags added: kernel-da-key kernel-hyper-v 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/1665097

Title:
  [Hyper-V] SAUCE: pci-hyperv fixes for SR-IOV on Azure

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

Bug description:
  The following two patches to pci-hyperv were submitted upstream but
  missed getting pulled into Bjorn's tree. They are needed to fix an
  issue discovered working on SR-IOV on Azure.

  Patch 1: hv_pci_devices_present is called in hv_pci_remove when we
  remove a PCI device from host (e.g. by disabling SRIOV on a device).
  In hv_pci_remove, the bus is already removed before the call, so we
  don't need to rescan the bus in the workqueue scheduled from
  hv_pci_devices_present. By introducing status hv_pcibus_removed, we
  can avoid this situation.

  Patch 2: A PCI_EJECT message can arrive at the same time we are
  calling pci_scan_child_bus in the workqueue for the previous
  PCI_BUS_RELATIONS message or in create_root_hv_pci_bus(), in this case
  we could potentailly modify the bus from multiple places. Properly
  lock the bus access.

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

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


[Kernel-packages] [Bug 1654135] Re: zfs-dkms 0.6.5.6-0ubuntu15: zfs kernel module failed to build - I get this error at login just after the main desktop loads

2017-02-15 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  zfs-dkms 0.6.5.6-0ubuntu15: zfs kernel module failed to build - I get
  this error at login just after the main desktop loads

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  I guess this is ZFS related,  however upon checking I still have read write 
access to my ZFS pools etc. So not entirely sure if this is a major bug or not.
  Please note it has only started occurring after update from 15.10 (Wily) to 
Xenial
  Cheers

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: zfs-dkms 0.6.5.6-0ubuntu15
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  DKMSBuildLog:
   DKMS make.log for zfs-0.6.5.6 for kernel 4.4.0-57-generic (x86_64)
   Thursday 5 January  10:22:49 AEST 2017
   make: *** No targets specified and no makefile found.  Stop.
  DKMSKernelVersion: 4.4.0-57-generic
  Date: Thu Jan  5 10:22:53 2017
  InstallationDate: Installed on 2016-02-01 (338 days ago)
  InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  PackageVersion: 0.6.5.6-0ubuntu15
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: zfs-linux
  Title: zfs-dkms 0.6.5.6-0ubuntu15: zfs kernel module failed to build
  UpgradeStatus: Upgraded to xenial on 2017-01-05 (0 days ago)

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

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


[Kernel-packages] [Bug 1661699] rumford (amd64) - tests ran: 141, failed: 0

2017-02-15 Thread Brad Figg
tests ran: 141, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-81.89-generic/rumford__3.19.0-81.89__2017-02-15_19-26-00/results-index.html

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

Title:
  linux: 3.19.0-81.89 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: 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/1661699/+subscriptions

-- 
Mailing list: https://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 1665113] [NEW] [Ubuntu 17.04] Kernel panics when large number of hugepages is passed as an boot argument to kernel.

2017-02-15 Thread Michael Hohnbaum
Leann,

Another one for the Kernel team to track.

 Michael


On 02/15/2017 12:10 PM, Launchpad Bug Tracker wrote:
> bugproxy (bugproxy) has assigned this bug to you for Ubuntu:
>
> Issue:
> ---
> Kernel unable to handle paging request and panic occurs when more number of 
> hugepages is passed as a boot argument to the kernel .
>
> Environment:
> --
> Power NV : Habanaro Bare metal
> OS : Ubuntu 17.04
> Kernel Version : 4.9.0-11-generic
>
> Steps To reproduce:
> ---
>
> 1 - When the ubuntu Kernel boots try to add the boot argument 'hugepages
> = 1200'.
>
> The Kernel Panics and displays call traces like as below.
>
> [5.030274] Unable to handle kernel paging request for data at address 
> 0x
> [5.030323] Faulting instruction address: 0xc0302848
> [5.030366] Oops: Kernel access of bad area, sig: 11 [#1]
> [5.030399] SMP NR_CPUS=2048 [5.030416] NUMA 
> [5.039443] PowerNV
> [5.039461] Modules linked in:
> [5.050091] CPU: 0 PID: 4 Comm: kworker/0:0 Not tainted 4.9.0-11-generic 
> #12-Ubuntu
> [5.053266] Workqueue: events pcpu_balance_workfn
> [5.080647] task: c03c8fe9b800 task.stack: c03ffb118000
> [5.090876] NIP: c0302848 LR: c02709d4 CTR: 
> c016cef0
> [5.094175] REGS: c03ffb11b410 TRAP: 0300   Not tainted  
> (4.9.0-11-generic)
> [5.103040] MSR: 92009033 [
> 5.114466]   CR: 22424222  XER: 
> [5.124932] CFAR: c0008a60 DAR:  DSISR: 4000 
> SOFTE: 1 
> GPR00: c02709d4 c03ffb11b690 c141a400 c03fff50e300 
> GPR04:  024001c2 c03ffb11b780 00219df5 
> GPR08: 003ffb09 c1454fd8   
> GPR12: 4400 c7b6 024001c2 024001c2 
> GPR16: 024001c2   0002 
> GPR20: 000c   024200c0 
> GPR24: c16eef48  c03fff50fd00 024001c2 
> GPR28:  c03fff50fd00 c03fff50e300 c03ffb11b820 
> NIP [c0302848] mem_cgroup_soft_limit_reclaim+0xf8/0x4f0
> [5.213613] LR [c02709d4] do_try_to_free_pages+0x1b4/0x450
> [5.230521] Call Trace:
> [5.230643] [c03ffb11b760] [c02709d4] 
> do_try_to_free_pages+0x1b4/0x450
> [5.254184] [c03ffb11b800] [c0270d68] 
> try_to_free_pages+0xf8/0x270
> [5.281896] [c03ffb11b890] [c0259b88] 
> __alloc_pages_nodemask+0x7a8/0xff0
> [5.321407] [c03ffb11bab0] [c0282cd0] 
> pcpu_populate_chunk+0x110/0x520
> [5.336262] [c03ffb11bb50] [c02841b8] 
> pcpu_balance_workfn+0x758/0x960
> [5.351526] [c03ffb11bc50] [c00ecdd0] 
> process_one_work+0x2b0/0x5a0
> [5.362561] [c03ffb11bce0] [c00ed168] worker_thread+0xa8/0x660
> [5.374007] [c03ffb11bd80] [c00f5320] kthread+0x110/0x130
> [5.385160] [c03ffb11be30] [c000c0e8] 
> ret_from_kernel_thread+0x5c/0x74
> [5.389456] Instruction dump:
> [5.410036] eb81ffe0 eba1ffe8 ebc1fff0 ebe1fff8 4e800020 3d230001 e9499a42 
> 3d220004 
> [5.423598] 3929abd8 794a1f24 7d295214 eac90100  2fa9 
> 419eff74 3b20 
> [5.436503] ---[ end trace 23b650e96be5c549 ]---
> [5.439700] 
>
> This is purely a negative scenario where the system does not have enough
> memory as the hugepages is given a very large argument.
>
> Free output in a system:
> free -h
>   totalusedfree  shared  buff/cache   
> available
> Mem:   251G2.1G248G5.2M502M
> 248G
> Swap:  2.0G159M1.8G
>
> The same scenario when tried after the linux is up like as,
>
> echo 1200 > /proc/sys/vm/nr_hugepages
>
> HugePages_Total:   15069
> HugePages_Free:15069
> HugePages_Rsvd:0
> HugePages_Surp:0
> Hugepagesize:  16384 kB
> root@ltc-haba2:~# free -h
>   totalusedfree  shared  buff/cache   
> available
> Mem:   251G237G 13G5.6M311M 
> 13G
> Swap:  2.0G159M1.8G
>
> In this case the kernel is able to allocate around 237 Gb for hugetlb.
>
> But while the system is booting it gives us panic so please let know if
> this scenario  is expected  to be handled.
>
> I identified the root cause of the panic.
> When the system is running with low memory during mem cgroup initialisation, 
> because most of the page have been grabbed to be huge pages, we hit a chicken 
> and egg issue because when trying to allocate memory for the node's cgroup 
> descriptor, we try to free some memory and in this path cgroup's services are 
> called which assume node's cgroup descriptor is 

[Kernel-packages] [Bug 1665113] Attached the boot console kernel oops traces

2017-02-15 Thread bugproxy
Default Comment by Bridge

** Attachment added: "Attached the boot console kernel oops traces"
   
https://bugs.launchpad.net/bugs/1665113/+attachment/4819769/+files/Ubuntu_oops

** Changed in: ubuntu
 Assignee: (unassigned) => Taco Screen team (taco-screen-team)

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

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

Title:
  [Ubuntu 17.04] Kernel panics when large number of hugepages is passed
  as an boot argument to kernel.

Status in linux package in Ubuntu:
  New

Bug description:
  Issue:
  ---
  Kernel unable to handle paging request and panic occurs when more number of 
hugepages is passed as a boot argument to the kernel .

  Environment:
  --
  Power NV : Habanaro Bare metal
  OS : Ubuntu 17.04
  Kernel Version : 4.9.0-11-generic

  Steps To reproduce:
  ---

  1 - When the ubuntu Kernel boots try to add the boot argument
  'hugepages = 1200'.

  The Kernel Panics and displays call traces like as below.

  [5.030274] Unable to handle kernel paging request for data at address 
0x
  [5.030323] Faulting instruction address: 0xc0302848
  [5.030366] Oops: Kernel access of bad area, sig: 11 [#1]
  [5.030399] SMP NR_CPUS=2048 [5.030416] NUMA 
  [5.039443] PowerNV
  [5.039461] Modules linked in:
  [5.050091] CPU: 0 PID: 4 Comm: kworker/0:0 Not tainted 4.9.0-11-generic 
#12-Ubuntu
  [5.053266] Workqueue: events pcpu_balance_workfn
  [5.080647] task: c03c8fe9b800 task.stack: c03ffb118000
  [5.090876] NIP: c0302848 LR: c02709d4 CTR: 
c016cef0
  [5.094175] REGS: c03ffb11b410 TRAP: 0300   Not tainted  
(4.9.0-11-generic)
  [5.103040] MSR: 92009033 [
5.114466]   CR: 22424222  XER: 
  [5.124932] CFAR: c0008a60 DAR:  DSISR: 4000 
SOFTE: 1 
  GPR00: c02709d4 c03ffb11b690 c141a400 c03fff50e300 
  GPR04:  024001c2 c03ffb11b780 00219df5 
  GPR08: 003ffb09 c1454fd8   
  GPR12: 4400 c7b6 024001c2 024001c2 
  GPR16: 024001c2   0002 
  GPR20: 000c   024200c0 
  GPR24: c16eef48  c03fff50fd00 024001c2 
  GPR28:  c03fff50fd00 c03fff50e300 c03ffb11b820 
  NIP [c0302848] mem_cgroup_soft_limit_reclaim+0xf8/0x4f0
  [5.213613] LR [c02709d4] do_try_to_free_pages+0x1b4/0x450
  [5.230521] Call Trace:
  [5.230643] [c03ffb11b760] [c02709d4] 
do_try_to_free_pages+0x1b4/0x450
  [5.254184] [c03ffb11b800] [c0270d68] 
try_to_free_pages+0xf8/0x270
  [5.281896] [c03ffb11b890] [c0259b88] 
__alloc_pages_nodemask+0x7a8/0xff0
  [5.321407] [c03ffb11bab0] [c0282cd0] 
pcpu_populate_chunk+0x110/0x520
  [5.336262] [c03ffb11bb50] [c02841b8] 
pcpu_balance_workfn+0x758/0x960
  [5.351526] [c03ffb11bc50] [c00ecdd0] 
process_one_work+0x2b0/0x5a0
  [5.362561] [c03ffb11bce0] [c00ed168] worker_thread+0xa8/0x660
  [5.374007] [c03ffb11bd80] [c00f5320] kthread+0x110/0x130
  [5.385160] [c03ffb11be30] [c000c0e8] 
ret_from_kernel_thread+0x5c/0x74
  [5.389456] Instruction dump:
  [5.410036] eb81ffe0 eba1ffe8 ebc1fff0 ebe1fff8 4e800020 3d230001 e9499a42 
3d220004 
  [5.423598] 3929abd8 794a1f24 7d295214 eac90100  2fa9 
419eff74 3b20 
  [5.436503] ---[ end trace 23b650e96be5c549 ]---
  [5.439700] 

  This is purely a negative scenario where the system does not have
  enough memory as the hugepages is given a very large argument.

  Free output in a system:
  free -h
totalusedfree  shared  buff/cache   
available
  Mem:   251G2.1G248G5.2M502M
248G
  Swap:  2.0G159M1.8G

  The same scenario when tried after the linux is up like as,

  echo 1200 > /proc/sys/vm/nr_hugepages

  HugePages_Total:   15069
  HugePages_Free:15069
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:  16384 kB
  root@ltc-haba2:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   251G237G 13G5.6M311M 
13G
  Swap:  2.0G159M1.8G

  In this case the kernel is able to allocate around 237 Gb for hugetlb.

  But while the system is booting it gives us panic so please let know
  if this scenario  is expected  to be handled.

  I identified the 

[Kernel-packages] [Bug 1630924] Re: Kdump through NMI SMP and single core not working on Ubuntu16.10

2017-02-15 Thread Joshua R. Poulson
We will verify this fix is in.

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

Title:
  Kdump through NMI SMP and single core not working on Ubuntu16.10

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  In Progress

Bug description:
  During some tests I've encountered an issue with kdump through NMI SMP
  and single core. After kdump configuration, when I trigger the crash
  through an NMI call from the host, the VM will panic, however it will
  not write the vmcore dump files and neither reboot.

  REPRO STEPS:

  1. configure kdump
   - crashkernel=512M-:384M  /boot/grub/grub.cfg
   - USE_KDUMP=1 /etc/default/kdump-tools

  2. after configuration reboot the VM

  3. check kdump status
   - cat /sys/kernel/kexec_*
   - service kdump-tools status

  4. configure NMI
   - sysctl -w kernel.unknown_nmi_panic=1

  5. trigger a crash from host
   - Debug-VM -Name $vmName -InjectNonMaskableInterrupt -ComputerName $hvServer 
-Force

  This case also applies to:
  -Ubuntu 16.10 generation 2(kernel version: 4.8.0-17-generic)
  -Ubuntu 16.04.1(kernel: 4.4.0-38-generic)
  -Ubuntu 14.04.5(kernel: 3.19.0-69-generic)

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

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


[Kernel-packages] [Bug 1665097] Re: [Hyper-V] SAUCE: pci-hyperv fixes for SR-IOV on Azure

2017-02-15 Thread Joseph Salisbury
** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

Title:
  [Hyper-V] SAUCE: pci-hyperv fixes for SR-IOV on Azure

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

Bug description:
  The following two patches to pci-hyperv were submitted upstream but
  missed getting pulled into Bjorn's tree. They are needed to fix an
  issue discovered working on SR-IOV on Azure.

  Patch 1: hv_pci_devices_present is called in hv_pci_remove when we
  remove a PCI device from host (e.g. by disabling SRIOV on a device).
  In hv_pci_remove, the bus is already removed before the call, so we
  don't need to rescan the bus in the workqueue scheduled from
  hv_pci_devices_present. By introducing status hv_pcibus_removed, we
  can avoid this situation.

  Patch 2: A PCI_EJECT message can arrive at the same time we are
  calling pci_scan_child_bus in the workqueue for the previous
  PCI_BUS_RELATIONS message or in create_root_hv_pci_bus(), in this case
  we could potentailly modify the bus from multiple places. Properly
  lock the bus access.

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

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


[Kernel-packages] [Bug 1657540] Re: [Hyper-V] netvsc: add rcu_read locked to netvsc callback

2017-02-15 Thread Joshua R. Poulson
We will verify this fix is in.

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

Title:
  [Hyper-V] netvsc: add rcu_read locked to netvsc callback

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

Bug description:
  Please add the following upstream commit (and its prerequisites) for
  SR-IOV on Azure:

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=0719e72ccb801829a3d735d187ca8417f0930459

  author
  stephen hemminger 
  2017-01-11 17:16:32 (GMT)
  committer
  David S. Miller 
  2017-01-11 21:13:53 (GMT)
  commit
  0719e72ccb801829a3d735d187ca8417f0930459 (patch)
  tree
  a4f718fefcb15433fa59f6d4add44ae220edb806
  parent
  4ecb1d83f6abe8d49163427f4d431ebe98f8bd5f (diff)
  netvsc: add rcu_read locking to netvsc callback
  The receive callback (in tasklet context) is using RCU to get reference
  to associated VF network device but this is not safe. RCU read lock
  needs to be held. Found by running with full lockdep debugging
  enabled.

  Fixes: f207c10d9823 ("hv_netvsc: use RCU to protect vf_netdev")
  Signed-off-by: Stephen Hemminger 
  Signed-off-by: David S. Miller 

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

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


[Kernel-packages] [Bug 1665113] [NEW] [Ubuntu 17.04] Kernel panics when large number of hugepages is passed as an boot argument to kernel.

2017-02-15 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Issue:
---
Kernel unable to handle paging request and panic occurs when more number of 
hugepages is passed as a boot argument to the kernel .

Environment:
--
Power NV : Habanaro Bare metal
OS : Ubuntu 17.04
Kernel Version : 4.9.0-11-generic

Steps To reproduce:
---

1 - When the ubuntu Kernel boots try to add the boot argument 'hugepages
= 1200'.

The Kernel Panics and displays call traces like as below.

[5.030274] Unable to handle kernel paging request for data at address 
0x
[5.030323] Faulting instruction address: 0xc0302848
[5.030366] Oops: Kernel access of bad area, sig: 11 [#1]
[5.030399] SMP NR_CPUS=2048 [5.030416] NUMA 
[5.039443] PowerNV
[5.039461] Modules linked in:
[5.050091] CPU: 0 PID: 4 Comm: kworker/0:0 Not tainted 4.9.0-11-generic 
#12-Ubuntu
[5.053266] Workqueue: events pcpu_balance_workfn
[5.080647] task: c03c8fe9b800 task.stack: c03ffb118000
[5.090876] NIP: c0302848 LR: c02709d4 CTR: c016cef0
[5.094175] REGS: c03ffb11b410 TRAP: 0300   Not tainted  
(4.9.0-11-generic)
[5.103040] MSR: 92009033 [
5.114466]   CR: 22424222  XER: 
[5.124932] CFAR: c0008a60 DAR:  DSISR: 4000 
SOFTE: 1 
GPR00: c02709d4 c03ffb11b690 c141a400 c03fff50e300 
GPR04:  024001c2 c03ffb11b780 00219df5 
GPR08: 003ffb09 c1454fd8   
GPR12: 4400 c7b6 024001c2 024001c2 
GPR16: 024001c2   0002 
GPR20: 000c   024200c0 
GPR24: c16eef48  c03fff50fd00 024001c2 
GPR28:  c03fff50fd00 c03fff50e300 c03ffb11b820 
NIP [c0302848] mem_cgroup_soft_limit_reclaim+0xf8/0x4f0
[5.213613] LR [c02709d4] do_try_to_free_pages+0x1b4/0x450
[5.230521] Call Trace:
[5.230643] [c03ffb11b760] [c02709d4] 
do_try_to_free_pages+0x1b4/0x450
[5.254184] [c03ffb11b800] [c0270d68] 
try_to_free_pages+0xf8/0x270
[5.281896] [c03ffb11b890] [c0259b88] 
__alloc_pages_nodemask+0x7a8/0xff0
[5.321407] [c03ffb11bab0] [c0282cd0] 
pcpu_populate_chunk+0x110/0x520
[5.336262] [c03ffb11bb50] [c02841b8] 
pcpu_balance_workfn+0x758/0x960
[5.351526] [c03ffb11bc50] [c00ecdd0] 
process_one_work+0x2b0/0x5a0
[5.362561] [c03ffb11bce0] [c00ed168] worker_thread+0xa8/0x660
[5.374007] [c03ffb11bd80] [c00f5320] kthread+0x110/0x130
[5.385160] [c03ffb11be30] [c000c0e8] 
ret_from_kernel_thread+0x5c/0x74
[5.389456] Instruction dump:
[5.410036] eb81ffe0 eba1ffe8 ebc1fff0 ebe1fff8 4e800020 3d230001 e9499a42 
3d220004 
[5.423598] 3929abd8 794a1f24 7d295214 eac90100  2fa9 419eff74 
3b20 
[5.436503] ---[ end trace 23b650e96be5c549 ]---
[5.439700] 

This is purely a negative scenario where the system does not have enough
memory as the hugepages is given a very large argument.

Free output in a system:
free -h
  totalusedfree  shared  buff/cache   available
Mem:   251G2.1G248G5.2M502M248G
Swap:  2.0G159M1.8G

The same scenario when tried after the linux is up like as,

echo 1200 > /proc/sys/vm/nr_hugepages

HugePages_Total:   15069
HugePages_Free:15069
HugePages_Rsvd:0
HugePages_Surp:0
Hugepagesize:  16384 kB
root@ltc-haba2:~# free -h
  totalusedfree  shared  buff/cache   available
Mem:   251G237G 13G5.6M311M 13G
Swap:  2.0G159M1.8G

In this case the kernel is able to allocate around 237 Gb for hugetlb.

But while the system is booting it gives us panic so please let know if
this scenario  is expected  to be handled.

I identified the root cause of the panic.
When the system is running with low memory during mem cgroup initialisation, 
because most of the page have been grabbed to be huge pages, we hit a chicken 
and egg issue because when trying to allocate memory for the node's cgroup 
descriptor, we try to free some memory and in this path cgroup's services are 
called which assume node's cgroup descriptor is allocated.

I'm working on a patch which fixes this panic, but I think it is
expected that the system fail due to OOM when all the pages are assigned
to huge pages.

Patch sent upstream, waiting for review : 
https://patchwork.kernel.org/patch/9573799/

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
 

[Kernel-packages] [Bug 1665097] Re: [Hyper-V] SAUCE: pci-hyperv fixes for SR-IOV on Azure

2017-02-15 Thread Joshua R. Poulson
** 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/1665097

Title:
  [Hyper-V] SAUCE: pci-hyperv fixes for SR-IOV on Azure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The following two patches to pci-hyperv were submitted upstream but
  missed getting pulled into Bjorn's tree. They are needed to fix an
  issue discovered working on SR-IOV on Azure.

  Patch 1: hv_pci_devices_present is called in hv_pci_remove when we
  remove a PCI device from host (e.g. by disabling SRIOV on a device).
  In hv_pci_remove, the bus is already removed before the call, so we
  don't need to rescan the bus in the workqueue scheduled from
  hv_pci_devices_present. By introducing status hv_pcibus_removed, we
  can avoid this situation.

  Patch 2: A PCI_EJECT message can arrive at the same time we are
  calling pci_scan_child_bus in the workqueue for the previous
  PCI_BUS_RELATIONS message or in create_root_hv_pci_bus(), in this case
  we could potentailly modify the bus from multiple places. Properly
  lock the bus access.

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

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


[Kernel-packages] [Bug 1665097] [NEW] [Hyper-V] SAUCE: pci-hyperv fixes for SR-IOV on Azure

2017-02-15 Thread Joshua R. Poulson
Public bug reported:

The following two patches to pci-hyperv were submitted upstream but
missed getting pulled into Bjorn's tree. They are needed to fix an issue
discovered working on SR-IOV on Azure.

Patch 1: hv_pci_devices_present is called in hv_pci_remove when we
remove a PCI device from host (e.g. by disabling SRIOV on a device). In
hv_pci_remove, the bus is already removed before the call, so we don't
need to rescan the bus in the workqueue scheduled from
hv_pci_devices_present. By introducing status hv_pcibus_removed, we can
avoid this situation.

Patch 2: A PCI_EJECT message can arrive at the same time we are calling
pci_scan_child_bus in the workqueue for the previous PCI_BUS_RELATIONS
message or in create_root_hv_pci_bus(), in this case we could
potentailly modify the bus from multiple places. Properly lock the bus
access.

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

** Patch added: "0001-pci-hyperv-properly-handle-pci-bus-remove.patch"
   
https://bugs.launchpad.net/bugs/1665097/+attachment/4819743/+files/0001-pci-hyperv-properly-handle-pci-bus-remove.patch

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

Title:
  [Hyper-V] SAUCE: pci-hyperv fixes for SR-IOV on Azure

Status in linux package in Ubuntu:
  New

Bug description:
  The following two patches to pci-hyperv were submitted upstream but
  missed getting pulled into Bjorn's tree. They are needed to fix an
  issue discovered working on SR-IOV on Azure.

  Patch 1: hv_pci_devices_present is called in hv_pci_remove when we
  remove a PCI device from host (e.g. by disabling SRIOV on a device).
  In hv_pci_remove, the bus is already removed before the call, so we
  don't need to rescan the bus in the workqueue scheduled from
  hv_pci_devices_present. By introducing status hv_pcibus_removed, we
  can avoid this situation.

  Patch 2: A PCI_EJECT message can arrive at the same time we are
  calling pci_scan_child_bus in the workqueue for the previous
  PCI_BUS_RELATIONS message or in create_root_hv_pci_bus(), in this case
  we could potentailly modify the bus from multiple places. Properly
  lock the bus access.

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

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


[Kernel-packages] [Bug 1665097] Re: [Hyper-V] SAUCE: pci-hyperv fixes for SR-IOV on Azure

2017-02-15 Thread Joshua R. Poulson
** Patch added: "0002-pci-hyperv-lock-pci-bus-on-device-eject.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1665097/+attachment/4819744/+files/0002-pci-hyperv-lock-pci-bus-on-device-eject.patch

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

Title:
  [Hyper-V] SAUCE: pci-hyperv fixes for SR-IOV on Azure

Status in linux package in Ubuntu:
  New

Bug description:
  The following two patches to pci-hyperv were submitted upstream but
  missed getting pulled into Bjorn's tree. They are needed to fix an
  issue discovered working on SR-IOV on Azure.

  Patch 1: hv_pci_devices_present is called in hv_pci_remove when we
  remove a PCI device from host (e.g. by disabling SRIOV on a device).
  In hv_pci_remove, the bus is already removed before the call, so we
  don't need to rescan the bus in the workqueue scheduled from
  hv_pci_devices_present. By introducing status hv_pcibus_removed, we
  can avoid this situation.

  Patch 2: A PCI_EJECT message can arrive at the same time we are
  calling pci_scan_child_bus in the workqueue for the previous
  PCI_BUS_RELATIONS message or in create_root_hv_pci_bus(), in this case
  we could potentailly modify the bus from multiple places. Properly
  lock the bus access.

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

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


[Kernel-packages] [Bug 1664960] Re: Xenial update to v4.4.49 stable release

2017-02-15 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

Title:
  Xenial update to v4.4.49 stable release

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

Bug description:
  SRU Justification

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

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the v4.4.49 stable release shall be
  applied:

  ARC: [arcompact] brown paper bag bug in unaligned access delay slot fixup
  selinux: fix off-by-one in setprocattr
  Revert "x86/ioapic: Restore IO-APIC irq_chip retrigger callback"
  cpumask: use nr_cpumask_bits for parsing functions
  hns: avoid stack overflow with CONFIG_KASAN
  ARM: 8643/3: arm/ptrace: Preserve previous registers for short regset write
  target: Don't BUG_ON during NodeACL dynamic -> explicit conversion
  target: Use correct SCSI status during EXTENDED_COPY exception
  target: Fix early transport_generic_handle_tmr abort scenario
  target: Fix COMPARE_AND_WRITE ref leak for non GOOD status
  ARM: 8642/1: LPAE: catch pending imprecise abort on unmask
  mac80211: Fix adding of mesh vendor IEs
  netvsc: Set maximum GSO size in the right place
  scsi: zfcp: fix use-after-free by not tracing WKA port open/close on failed 
send
  scsi: aacraid: Fix INTx/MSI-x issue with older controllers
  scsi: mpt3sas: disable ASPM for MPI2 controllers
  xen-netfront: Delete rx_refill_timer in xennet_disconnect_backend()
  ALSA: seq: Fix race at creating a queue
  ALSA: seq: Don't handle loop timeout at snd_seq_pool_done()
  drm/i915: fix use-after-free in page_flip_completed()
  Linux 4.4.49

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

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


[Kernel-packages] [Bug 1664960] Re: Xenial update to v4.4.49 stable release

2017-02-15 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Xenial update to v4.4.49 stable release

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

Bug description:
  SRU Justification

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

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the v4.4.49 stable release shall be
  applied:

  ARC: [arcompact] brown paper bag bug in unaligned access delay slot fixup
  selinux: fix off-by-one in setprocattr
  Revert "x86/ioapic: Restore IO-APIC irq_chip retrigger callback"
  cpumask: use nr_cpumask_bits for parsing functions
  hns: avoid stack overflow with CONFIG_KASAN
  ARM: 8643/3: arm/ptrace: Preserve previous registers for short regset write
  target: Don't BUG_ON during NodeACL dynamic -> explicit conversion
  target: Use correct SCSI status during EXTENDED_COPY exception
  target: Fix early transport_generic_handle_tmr abort scenario
  target: Fix COMPARE_AND_WRITE ref leak for non GOOD status
  ARM: 8642/1: LPAE: catch pending imprecise abort on unmask
  mac80211: Fix adding of mesh vendor IEs
  netvsc: Set maximum GSO size in the right place
  scsi: zfcp: fix use-after-free by not tracing WKA port open/close on failed 
send
  scsi: aacraid: Fix INTx/MSI-x issue with older controllers
  scsi: mpt3sas: disable ASPM for MPI2 controllers
  xen-netfront: Delete rx_refill_timer in xennet_disconnect_backend()
  ALSA: seq: Fix race at creating a queue
  ALSA: seq: Don't handle loop timeout at snd_seq_pool_done()
  drm/i915: fix use-after-free in page_flip_completed()
  Linux 4.4.49

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

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


[Kernel-packages] [Bug 1649718] Re: Linux rtc self test fails in a VM under xenial

2017-02-15 Thread Seth Forshee
Verified fix in 4.4.0-63.84.

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

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

Title:
  Linux rtc self test fails in a VM under xenial

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

Bug description:
  == SRU Justification ==

  Impact: A race in kvm can result in the EOI signal for the rtc irq to
  be lost. After this happens no more rtc interrupts will be delivered
  to the guest.

  Fix: Three upstream cherry picks which fix the problem.

  Regression Potential: These patches have been upstream since 4.6, so
  they're well-tested at this point. Thus regressions are unlikely.

  ---

  ADT testing for the linux package hangs at the kernel's rtc selftest,
  for example:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-zesty/zesty/amd64/l/linux/20161212_132117_a258d@/log.gz

  Running this test manually, I've observed that this will hang in me
  with various kernel versions going back to 4.4 in a VM on my machine
  which is running xenial. The test runs to completion in a VM on a
  different machine running zesty.

  This is the section of the test which produces the hang:

  /* Turn on update interrupts (one per second) */
  retval = ioctl(fd, RTC_UIE_ON, 0);
  if (retval == -1) {
  if (errno == EINVAL) {
  fprintf(stderr,
  "\n...Update IRQs not supported.\n");
  goto test_READ;
  }
  perror("RTC_UIE_ON ioctl");
  exit(errno);
  }

  fprintf(stderr, "Counting 5 update (1/sec) interrupts from reading 
%s:",
  rtc);
  fflush(stderr);
  for (i=1; i<6; i++) {
  /* This read will block */
  retval = read(fd, , sizeof(unsigned long));
  if (retval == -1) {
  perror("read");
  exit(errno);
  }
  fprintf(stderr, " %d",i);
  fflush(stderr);
  irqcount++;
  }

  The read blocks indefinitely most of the time. After boot it might
  return once or twice before it hangs, but running the test
  subsequently always hangs on the first read. I'll attach the full
  source for the test (rtctest.c).

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

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


[Kernel-packages] [Bug 1650058] Re: [Hyper-V/Azure] Please include Mellanox OFED drivers in Azure kernel and image

2017-02-15 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Status: Triaged => In Progress

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

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

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

Title:
  [Hyper-V/Azure] Please include Mellanox OFED drivers in Azure kernel
  and image

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

Bug description:
  In order to have the correct VF driver to support SR-IOV in Azure, the
  Mellanox OFED distribution needs to be included in the kernel and the
  image. Mellanox's drivers are not upstream, but they are available
  from here:

  
https://www.mellanox.com/page/products_dyn?product_family=26=linux_sw_drivers=3nnhohirh5htv6dnp1uk7tf487

  While this configuration is not explicitly listed as supported in the
  release notes, Microsoft and Mellanox engineers are working on the
  corresponding Windows Server 2016 PF driver to support this VF driver
  in operation in Ubuntu guests.

  I file file a corresponding rebase request to pick up the PCI
  passthrough and other SR-IOV work done for the Hyper-V capabilities in
  the upstream 4.9 kernel.

  Only 64-bit support for Ubuntu 16.04's HWE kernel is needed.

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

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


[Kernel-packages] [Bug 1664217] gonzo (amd64) - tests ran: 19, failed: 1

2017-02-15 Thread Brad Figg
tests ran:  19, failed: 1;
  
http://kernel.ubuntu.com/testing/4.10.0-8.10-generic/gonzo__4.10.0-8.10__2017-02-15_18-10-00/results-index.html

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

Title:
  linux: 4.10.0-8.10 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Fix Released
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:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: 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-development-workflow/+bug/1664217/+subscriptions

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


[Kernel-packages] [Bug 1664217] fozzie (amd64) - tests ran: 19, failed: 0

2017-02-15 Thread Brad Figg
tests ran:  19, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-8.10-generic/fozzie__4.10.0-8.10__2017-02-15_18-10-00/results-index.html

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

Title:
  linux: 4.10.0-8.10 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Fix Released
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:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: 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-development-workflow/+bug/1664217/+subscriptions

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


[Kernel-packages] [Bug 1663975] Re: XHCI errors causes dock USB and network adapter dropouts

2017-02-15 Thread Joseph Salisbury
Did this issue start happening after an update/upgrade? Was there a
kernel version where you were not having this particular problem? This
will help determine if the problem you are seeing is the result of a
regression, and when this regression was introduced.   If this is a
regression, we can perform a kernel bisect to identify the commit that
introduced 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/1663975

Title:
  XHCI errors causes dock USB and network adapter dropouts

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Machine: Dell XPS 15 (9560) - released 2017 January
  Install: disk completely erased
   Ubuntu 16.04.1 installed over wireless with:
 - download updates while installing ubuntu
 - install third-party hardware
 - full disk crypto+luks
   Note 1: Installation process did not realize there exists a GTX 1050
   so we are solely using Intel integrated graphics.
   Note 2: Installation done not on Dell TB16 Dock to isolate wireless
   problems alone first.
  First Boot: update/upgrade/dist-upgrade'd after first boot and rebooted

  


  After testing wireless problems and being able to reproduce them,
  machine was rebooted to the login screen, and then plugged into a Dell
  TB16 dock.

  1. Turn down wireless networking.
  2. Turn up wired networking.
  3. Browse things until this happens, after which the wired interface no 
longer works and can sometimes be successfully `down/up`ed but at other times 
locks up and requires a reboot:

  [  598.238303] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not 
part of current TD ep_index 2 comp_code 13
  [  598.238307] xhci_hcd :0e:00.0: Looking for event-dma 000855403010 
trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 
seg-end 0008550aaff0
  [  598.238634] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not 
part of current TD ep_index 2 comp_code 13
  [  598.238639] xhci_hcd :0e:00.0: Looking for event-dma 000855403020 
trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 
seg-end 0008550aaff0
  [  598.239248] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not 
part of current TD ep_index 2 comp_code 13
  [  598.239253] xhci_hcd :0e:00.0: Looking for event-dma 000855403030 
trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 
seg-end 0008550aaff0
  [  598.239571] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not 
part of current TD ep_index 2 comp_code 13
  [  598.239576] xhci_hcd :0e:00.0: Looking for event-dma 000855403040 
trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 
seg-end 0008550aaff0
  [  598.239792] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not 
part of current TD ep_index 2 comp_code 13
  [  598.239794] xhci_hcd :0e:00.0: Looking for event-dma 000855403050 
trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 
seg-end 0008550aaff0
  [  598.240186] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not 
part of current TD ep_index 2 comp_code 13
  [  598.240191] xhci_hcd :0e:00.0: Looking for event-dma 000855403060 
trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 
seg-end 0008550aaff0
  [  598.240326] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not 
part of current TD ep_index 2 comp_code 13
  [  598.240328] xhci_hcd :0e:00.0: Looking for event-dma 000855403070 
trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 
seg-end 0008550aaff0
  [  598.240698] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not 
part of current TD ep_index 2 comp_code 13
  [  598.240703] xhci_hcd :0e:00.0: Looking for event-dma 000855403080 
trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 
seg-end 0008550aaff0
  [  605.601884] [ cut here ]
  [  605.601890] WARNING: CPU: 1 PID: 0 at 
/build/linux-W6HB68/linux-4.4.0/net/sched/sch_generic.c:306 
dev_watchdog+0x237/0x240()
  [  605.601892] NETDEV WATCHDOG: enxd481d70e6a39 (r8152): transmit queue 0 
timed out
  [  605.601892] Modules linked in: hid_logitech_hidpp snd_usb_audio 
snd_usbmidi_lib hid_generic hid_logitech_dj cdc_ether usbnet r8152 mii ctr ccm 
arc4 rfcomm bnep nls_iso8859_1 i2c_designware_platform i2c_designware_core 
dell_wmi dcdbas ath10k_pci ath10k_core ath snd_hda_codec_hdmi mac80211 dell_led 
snd_hda_codec_realtek snd_hda_codec_generic cfg80211 rtsx_pci_ms memstick 
snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm x86_pkg_temp_thermal 
coretemp snd_seq_midi 

[Kernel-packages] [Bug 1659623] Re: Shutdown/reboot hang on Dell XPS 15 9550 BIOS 1.2.18+

2017-02-15 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Status: Incomplete => Fix Committed

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

Title:
  Shutdown/reboot hang on Dell XPS 15 9550 BIOS 1.2.18+

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  On Dell XPS 15 9550 BIOS 1.2.18+, shutdown/reboot job is delayed for
  several seconds in Ubuntu kernel. After shutdown screen appears and
  all shutdown sequence had been done, the power LED turns off; however
  the front LED is flashing in orange for several seconds and the system
  finally turns off. Rebooting is also not working: front LED flashes in
  orange and the system just turns off.

  Switching to mainline kernel 4.9.6, or downgrading to BIOS 1.2.16
  solved the problem. Other Linux distro users didn't observed the
  problem, see also:

  * 
https://www.reddit.com/r/Dell/comments/5przxq/new_dell_xps_15_9550_bios_1219/
  * 
https://www.reddit.com/r/Dell/comments/5l9n3b/xps_15_9550_bios_1218_ubuntu_1610_shutdown_problem/

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-34-generic 4.8.0-34.36
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  psj5638 F pulseaudio
  CurrentDesktop: KDE
  Date: Thu Jan 26 19:17:24 2017
  HibernationDevice: RESUME=UUID=2cfb78ae-e2b8-4d3a-9ab2-a61ae1a79fd1
  InstallationDate: Installed on 2016-01-21 (371 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Dell Inc. XPS 15 9550
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic 
root=UUID=db90ced3-4cfe-4001-b877-d4aa35e7260f ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-34-generic N/A
   linux-backports-modules-4.8.0-34-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (103 days ago)
  dmi.bios.date: 12/22/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.19
  dmi.board.asset.tag: ainazi
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: ainazi
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.19:bd12/22/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1653576] Re: 4.9.0-11#12 kernel boot error on x86 with raid1 disk timeout

2017-02-15 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Zesty)
   Status: Confirmed => Fix Released

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

Title:
  4.9.0-11#12 kernel boot error on x86 with raid1 disk timeout

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  Dec 25 10:08:41 holywen.duckdns.org kernel: [ cut here 
]
  Dec 25 10:08:41 holywen.duckdns.org kernel: WARNING: CPU: 1 PID: 1 at 
/build/linux-YwmxP9/linux-4.9.0/arch/x86/mm/dump_pagetables.c:225 
note_page+0x6a1/0x880
  Dec 25 10:08:41 holywen.duckdns.org kernel: x86/mm: Found insecure W+X 
mapping at address c00a/0xc00a
  Dec 25 10:08:41 holywen.duckdns.org kernel: Modules linked in:
  Dec 25 10:08:41 holywen.duckdns.org kernel: CPU: 1 PID: 1 Comm: swapper/0 Not 
tainted 4.9.0-11-generic #12-Ubuntu
  Dec 25 10:08:41 holywen.duckdns.org kernel:  f5cafe70 d23e1935 f5cafeb4 
d2a26148 f5cafea0 d2072aaa d2a26110 f5cafed4
  Dec 25 10:08:41 holywen.duckdns.org kernel:  0001 d2a26148 00e1 
d2068e21 00e1 f5caff34 8000 
  Dec 25 10:08:41 holywen.duckdns.org kernel:  f5cafec0 d2072b16 0009 
 f5cafeb4 d2a26110 f5cafed4 9ff9230c
  Dec 25 10:08:41 holywen.duckdns.org kernel: Call Trace:
  Dec 25 10:08:41 holywen.duckdns.org kernel:  [] dump_stack+0x58/0x73
  Dec 25 10:08:41 holywen.duckdns.org kernel:  [] __warn+0xea/0x110
  Dec 25 10:08:41 holywen.duckdns.org kernel:  [] ? 
note_page+0x6a1/0x880
  Dec 25 10:08:41 holywen.duckdns.org kernel:  [] 
warn_slowpath_fmt+0x46/0x60
  Dec 25 10:08:41 holywen.duckdns.org kernel:  [] 
note_page+0x6a1/0x880
  Dec 25 10:08:41 holywen.duckdns.org kernel:  [] 
ptdump_walk_pgd_level_core+0x1f5/0x300
  Dec 25 10:08:41 holywen.duckdns.org kernel:  [] 
ptdump_walk_pgd_level_checkwx+0x16/0x20
  Dec 25 10:08:41 holywen.duckdns.org kernel:  [] 
mark_rodata_ro+0xfd/0x130
  Dec 25 10:08:41 holywen.duckdns.org kernel:  [] ? 
rest_init+0x70/0x70
  Dec 25 10:08:41 holywen.duckdns.org kernel:  [] 
kernel_init+0x2c/0x100
  Dec 25 10:08:41 holywen.duckdns.org kernel:  [] ? 
schedule_tail+0x11/0x50
  Dec 25 10:08:41 holywen.duckdns.org kernel:  [] ? 
rest_init+0x70/0x70
  Dec 25 10:08:41 holywen.duckdns.org kernel:  [] 
ret_from_fork+0x1b/0x28
  Dec 25 10:08:41 holywen.duckdns.org kernel: ---[ end trace 111835f101a591e4 
]---
  Dec 25 10:08:41 holywen.duckdns.org kernel: x86/mm: Checked W+X mappings: 
FAILED, 96 W+X pages found.


  Dec 25 10:08:44 holywen.duckdns.org kernel: ppdev: user-space parallel port 
driver
  Dec 25 10:10:10 holywen.duckdns.org systemd[1]: 
dev-disk-by\x2duuid-7162f5d7\x2d9728\x2d41ed\x2d9e95\x2daebca08a39b7.device: 
Job 
dev-disk-by\x2duuid-7162f5d7\x2d9728\x2d41ed\x2d9e95\x2daebca08a39b7.device/start
 timed out.
  Dec 25 10:10:10 holywen.duckdns.org systemd[1]: Timed out waiting for device 
dev-disk-by\x2duuid-7162f5d7\x2d9728\x2d41ed\x2d9e95\x2daebca08a39b7.device.
  -- Subject: Unit 
dev-disk-by\x2duuid-7162f5d7\x2d9728\x2d41ed\x2d9e95\x2daebca08a39b7.device has 
failed

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-57-generic 4.4.0-57.78
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-57-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Date: Tue Jan  3 10:52:34 2017
  HibernationDevice: RESUME=UUID=2c5fa26b-c600-4726-9cee-af128f108823
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=ffe9508f-88ce-4c42-85e2-19d49978e46a ro splash quiet vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-57-generic N/A
   linux-backports-modules-4.4.0-57-generic  N/A
   linux-firmware1.157.6
  RfKill: Error: [Errno 2] No such file or directory: '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/1653576/+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 1655241] Re: Ubuntu 17.04: "Oops: Exception in kernel mode, sig: 5 [#1]" seen during fadump over ssh on Alpine machine.

2017-02-15 Thread Tim Gardner
I applied the patch in comment #7

** Also affects: linux (Ubuntu Zesty)
   Importance: High
 Assignee: Canonical Kernel Team (canonical-kernel-team)
   Status: Triaged

** Also affects: makedumpfile (Ubuntu Zesty)
   Importance: Critical
   Status: Fix Released

** Changed in: linux (Ubuntu Zesty)
   Status: Triaged => Fix Committed

** Changed in: linux (Ubuntu Zesty)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner 
(timg-tpi)

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

Title:
  Ubuntu 17.04: "Oops: Exception in kernel mode, sig: 5 [#1]" seen
  during fadump over ssh on Alpine machine.

Status in linux package in Ubuntu:
  Fix Committed
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Committed
Status in makedumpfile source package in Zesty:
  Fix Released

Bug description:
  Problem Description
  
  "Oops: Exception in kernel mode, sig: 5 [#1]" seen during fadump over ssh on 
Alpine machine.

  Steps to Reproduce
  
  1. Configure fadump over ssh on Alpine machine.
  ssh-keygen -t rsa

  Add below lines in /etc/default/kdump-tools
  SSH="ubuntu@9.114.15.240"
  SSH_KEY=/root/.ssh/id_rsa

  # kdump-config propagate

  # kdump-config load

  # kdump-config show

  2. Trigger crash

  Logs
  ===
  ubuntu@alp9:~$ [   41.884641] usercopy: kernel memory exposure attempt 
detected from c000fb001020 (task_struct) (61408 bytes)
  [   41.884668] kernel BUG at /build/linux-okcqyo/linux-4.9.0/mm/usercopy.c:75!
  [   41.884672] Oops: Exception in kernel mode, sig: 5 [#1]
  [   41.884674] SMP NR_CPUS=2048 [   41.884676] NUMA 
  [   41.884677] pSeries
  [   41.884679] Modules linked in: pseries_rng vmx_crypto ib_iser rdma_cm 
iw_cm ib_cm ib_core configfs iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi ip_tables x_tables autofs4 btrfs raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear ibmvscsi lpfc crc32c_vpmsum 
scsi_transport_fc
  [   41.884714] CPU: 8 PID: 3977 Comm: makedumpfile Not tainted 
4.9.0-11-generic #12-Ubuntu
  [   41.884717] task: c00151fcdc00 task.stack: c00150064000
  [   41.884719] NIP: c0312978 LR: c0312974 CTR: 
006338e4
  [   41.884722] REGS: c001500678d0 TRAP: 0700   Not tainted  
(4.9.0-11-generic)
  [   41.884725] MSR: 80029033 [   41.884732]   
CR: 2800  XER: 0004
  [   41.884734] CFAR: c0b26cac SOFTE: 1 
  GPR00: c0312974 c00150067b50 c141a400 0063 
  GPR04: c00179a0ade8 c00179a1fc40 00a1b6ef  
  GPR08: 0007 c0f7f87c 000178a9 3ff0 
  GPR12: 2200 ce794800 3fff7f4d0010 3fff7f4d0010 
  GPR16: bb01 54150c98 5412da08 0001 
  GPR20: 540fea40 38448150 0001 c1717798 
  GPR24: 0001 c00150067cf0  1020 
  GPR28: c000fb01 0001 efe0 c000fb001020 
  NIP [c0312978] __check_object_size+0x88/0x2c0
  [   41.884777] LR [c0312974] __check_object_size+0x84/0x2c0
  [   41.884780] Call Trace:
  [   41.884782] [c00150067b50] [c0312974] 
__check_object_size+0x84/0x2c0 (unreliable)
  [   41.884787] [c00150067bd0] [c006aea4] copy_to_user+0x64/0xa0
  [   41.884791] [c00150067c10] [c0042360] 
copy_oldmem_page+0x140/0x1d0
  [   41.884796] [c00150067c60] [c03cd5a8] 
read_from_oldmem.part.0+0x138/0x150
  [   41.884800] [c00150067cd0] [c03cd6fc] read_vmcore+0x13c/0x270
  [   41.884803] [c00150067d40] [c03b8918] proc_reg_read+0x88/0xd0
  [   41.884807] [c00150067d70] [c0318f4c] __vfs_read+0x3c/0x70
  [   41.884811] [c00150067d90] [c031a1ac] vfs_read+0xbc/0x1b0
  [   41.884814] [c00150067de0] [c031bdc8] SyS_read+0x68/0x110
  [   41.884818] [c00150067e30] [c000bd84] system_call+0x38/0xe0
  [   41.884820] Instruction dump:
  [   41.884823] 6000 6042 3c82ff93 3ca2ff9d 38847130 38a5b3f8 3c62ff94 
7fc8f378 
  [   41.884830] 7fe6fb78 38635f20 488142dd 6000 <0fe0> 6042 
2ba30010 409d017c 
  [   41.884838] ---[ end trace c33ccad89db3894a ]---
  [   41.884840] 
  Copying data   : [ 43.7 %] -889527+439 records in
  [   41.805683] kdump-tools[3621]: 889744+1 records out
  [   41.805920] kdump-tools[3621]: 455549276 bytes (456 MB, 434 MiB) copied, 
24.5065 s, 18.6 MB/s
  [   42.263162] kdump-tools[3621]:  * kdump-tools: saved vmcore in 
ubuntu@9.114.15.240:/home/ubuntu/9.114.15.239-201701090710
  [   42.264882] kdump-tools[3621]:  * 

[Kernel-packages] [Bug 1584597] Re: [Hyper-V] Memory Ballooning re-broken in 16.04

2017-02-15 Thread Joshua R. Poulson
** Changed in: linux (Ubuntu)
   Status: Triaged => Incomplete

** Changed in: linux (Ubuntu Xenial)
   Status: Triaged => 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/1584597

Title:
  [Hyper-V] Memory Ballooning re-broken in 16.04

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

Bug description:
  Regression: #1294283 fixed memory ballooning in Hyper-V in 14.04, but
  the bug has returned in 16.04.

  
  Steps to reproduce:

  1. Create Gen2 Hyper-V VM
  2. Install Ubuntu 16.04
  3. modprobe hv_balloon
  Memory usage according to Hyper-V Manager will not change

  
  This has been reproduced on 2 fresh Ubuntu Server 16.04 instances.

  I installed linux-generic-xenial on a 14.04 instance, rebooted,
  modprobe'd hv_balloon and memory usage in Hyper-V Manager reduced to
  the correct level.

  Environment:
  Host: Windows NanoServer 2016

  Ubuntu Server 16.04 version_signature: `Ubuntu 4.4.0-21.37-generic 4.4.6`
  Ubuntu Server 14.04 version_signature: `Ubuntu 4.4.0-22.40~14.04.1-generic 
4.4.8`

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

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


[Kernel-packages] [Bug 1650058] Re: [Hyper-V/Azure] Please include Mellanox OFED drivers in Azure kernel and image

2017-02-15 Thread Joshua R. Poulson
Mellanox has told me that the following three commits are needed for SR-IOV in 
Azure:
1.  d585df1c5ccf net/mlx4_core: Avoid command timeouts during VF driver 
device shutdown
2.  7c3945bc2073 net/mlx4_core: Fix when to save some qp context flags for 
dynamic VST to VGT transitions
3.  291c566a2891 net/mlx4_core: Fix racy CQ (Completion Queue) free

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

Title:
  [Hyper-V/Azure] Please include Mellanox OFED drivers in Azure kernel
  and image

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

Bug description:
  In order to have the correct VF driver to support SR-IOV in Azure, the
  Mellanox OFED distribution needs to be included in the kernel and the
  image. Mellanox's drivers are not upstream, but they are available
  from here:

  
https://www.mellanox.com/page/products_dyn?product_family=26=linux_sw_drivers=3nnhohirh5htv6dnp1uk7tf487

  While this configuration is not explicitly listed as supported in the
  release notes, Microsoft and Mellanox engineers are working on the
  corresponding Windows Server 2016 PF driver to support this VF driver
  in operation in Ubuntu guests.

  I file file a corresponding rebase request to pick up the PCI
  passthrough and other SR-IOV work done for the Hyper-V capabilities in
  the upstream 4.9 kernel.

  Only 64-bit support for Ubuntu 16.04's HWE kernel is needed.

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

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


[Kernel-packages] [Bug 1662589] Re: Touchpad not working correctly after kernel upgrade

2017-02-15 Thread Joseph Salisbury
I built a 4.4.0-56 kernel. It can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1662589/

Can you give this kernel a test.

That will tell us if we need to bisect between -55 and -56 or -56 and
-57.

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

Title:
  Touchpad not working correctly after kernel upgrade

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

Bug description:
  Since the kernel upgraded from 4.4.0-31-generic the touchpad on my
  Toshiba Tecra laptop has not been functioning correctly.

  Whenever I try and do two finger srcolling it also thinks I'm doing a
  two finger tap to to rightclick, making two finger scrolling almost
  impossible.

  It is the same for both kernel updates since 4.4.0-31.  If I boot from
  4.4.0-31 then the touchpad works fine.

  If I do an xinput in the later kernels it shows :-
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Microsoft Wired Keyboard 600id=10   [slave  pointer 
 (2)]
  ⎜   ↳ Microsoft Comfort Mouse 6000id=11   [slave  pointer 
 (2)]
  ⎜   ↳ AlpsPS/2 ALPS DualPoint Stick   id=15   [slave  pointer 
 (2)]
  ⎜   ↳ AlpsPS/2 ALPS DualPoint TouchPadid=14   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Microsoft Wired Keyboard 600id=9[slave  
keyboard (3)]
  ↳ TOSHIBA Web Camera - FHDid=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]
  ↳ Toshiba input device  

  
  The AlpsPS/2 devices aren't aren't present when booting with 4.4.0.31:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Microsoft Wired Keyboard 600id=10   [slave  pointer 
 (2)]
  ⎜   ↳ Microsoft Comfort Mouse 6000id=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  id=14   [slave  pointer  (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Microsoft Wired Keyboard 600id=9[slave  
keyboard (3)]
  ↳ TOSHIBA Web Camera - FHDid=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]
  ↳ Toshiba input deviceid=15 [slave  keyboard 
(3)]

  Any ideas?

  Thanks.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nick   1867 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=5f888cc2-be17-45fe-9b4c-c8cf49eb1db8
  InstallationDate: Installed on 2017-02-03 (4 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: TOSHIBA TECRA A40-C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic.efi.signed 
root=UUID=7c18c2ca-0cc6-4c2c-80ba-194bbbc22646 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-62-generic N/A
   linux-backports-modules-4.4.0-62-generic  N/A
   linux-firmware1.157.6
  Tags:  xenial xenial
  Uname: Linux 4.4.0-62-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/12/2016
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 7.40
  dmi.board.asset.tag: 00
  dmi.board.name: TECRA A40-C
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 

[Kernel-packages] [Bug 1655241] patch backported on linux-image-4.9.0-15-generic kernel source

2017-02-15 Thread bugproxy
--- Comment (attachment only) From hbath...@in.ibm.com 2017-02-15 12:49 
EDT---


** Attachment added: "patch backported on linux-image-4.9.0-15-generic kernel 
source"
   
https://bugs.launchpad.net/bugs/1655241/+attachment/4819705/+files/001-put-a-hardlimit-on-memory-reserve-for-fadump.patch

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

Title:
  Ubuntu 17.04: "Oops: Exception in kernel mode, sig: 5 [#1]" seen
  during fadump over ssh on Alpine machine.

Status in linux package in Ubuntu:
  Triaged
Status in makedumpfile package in Ubuntu:
  Fix Released

Bug description:
  Problem Description
  
  "Oops: Exception in kernel mode, sig: 5 [#1]" seen during fadump over ssh on 
Alpine machine.

  Steps to Reproduce
  
  1. Configure fadump over ssh on Alpine machine.
  ssh-keygen -t rsa

  Add below lines in /etc/default/kdump-tools
  SSH="ubuntu@9.114.15.240"
  SSH_KEY=/root/.ssh/id_rsa

  # kdump-config propagate

  # kdump-config load

  # kdump-config show

  2. Trigger crash

  Logs
  ===
  ubuntu@alp9:~$ [   41.884641] usercopy: kernel memory exposure attempt 
detected from c000fb001020 (task_struct) (61408 bytes)
  [   41.884668] kernel BUG at /build/linux-okcqyo/linux-4.9.0/mm/usercopy.c:75!
  [   41.884672] Oops: Exception in kernel mode, sig: 5 [#1]
  [   41.884674] SMP NR_CPUS=2048 [   41.884676] NUMA 
  [   41.884677] pSeries
  [   41.884679] Modules linked in: pseries_rng vmx_crypto ib_iser rdma_cm 
iw_cm ib_cm ib_core configfs iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi ip_tables x_tables autofs4 btrfs raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear ibmvscsi lpfc crc32c_vpmsum 
scsi_transport_fc
  [   41.884714] CPU: 8 PID: 3977 Comm: makedumpfile Not tainted 
4.9.0-11-generic #12-Ubuntu
  [   41.884717] task: c00151fcdc00 task.stack: c00150064000
  [   41.884719] NIP: c0312978 LR: c0312974 CTR: 
006338e4
  [   41.884722] REGS: c001500678d0 TRAP: 0700   Not tainted  
(4.9.0-11-generic)
  [   41.884725] MSR: 80029033 [   41.884732]   
CR: 2800  XER: 0004
  [   41.884734] CFAR: c0b26cac SOFTE: 1 
  GPR00: c0312974 c00150067b50 c141a400 0063 
  GPR04: c00179a0ade8 c00179a1fc40 00a1b6ef  
  GPR08: 0007 c0f7f87c 000178a9 3ff0 
  GPR12: 2200 ce794800 3fff7f4d0010 3fff7f4d0010 
  GPR16: bb01 54150c98 5412da08 0001 
  GPR20: 540fea40 38448150 0001 c1717798 
  GPR24: 0001 c00150067cf0  1020 
  GPR28: c000fb01 0001 efe0 c000fb001020 
  NIP [c0312978] __check_object_size+0x88/0x2c0
  [   41.884777] LR [c0312974] __check_object_size+0x84/0x2c0
  [   41.884780] Call Trace:
  [   41.884782] [c00150067b50] [c0312974] 
__check_object_size+0x84/0x2c0 (unreliable)
  [   41.884787] [c00150067bd0] [c006aea4] copy_to_user+0x64/0xa0
  [   41.884791] [c00150067c10] [c0042360] 
copy_oldmem_page+0x140/0x1d0
  [   41.884796] [c00150067c60] [c03cd5a8] 
read_from_oldmem.part.0+0x138/0x150
  [   41.884800] [c00150067cd0] [c03cd6fc] read_vmcore+0x13c/0x270
  [   41.884803] [c00150067d40] [c03b8918] proc_reg_read+0x88/0xd0
  [   41.884807] [c00150067d70] [c0318f4c] __vfs_read+0x3c/0x70
  [   41.884811] [c00150067d90] [c031a1ac] vfs_read+0xbc/0x1b0
  [   41.884814] [c00150067de0] [c031bdc8] SyS_read+0x68/0x110
  [   41.884818] [c00150067e30] [c000bd84] system_call+0x38/0xe0
  [   41.884820] Instruction dump:
  [   41.884823] 6000 6042 3c82ff93 3ca2ff9d 38847130 38a5b3f8 3c62ff94 
7fc8f378 
  [   41.884830] 7fe6fb78 38635f20 488142dd 6000 <0fe0> 6042 
2ba30010 409d017c 
  [   41.884838] ---[ end trace c33ccad89db3894a ]---
  [   41.884840] 
  Copying data   : [ 43.7 %] -889527+439 records in
  [   41.805683] kdump-tools[3621]: 889744+1 records out
  [   41.805920] kdump-tools[3621]: 455549276 bytes (456 MB, 434 MiB) copied, 
24.5065 s, 18.6 MB/s
  [   42.263162] kdump-tools[3621]:  * kdump-tools: saved vmcore in 
ubuntu@9.114.15.240:/home/ubuntu/9.114.15.239-201701090710
  [   42.264882] kdump-tools[3621]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /tmp/dmesg.201701090710
  [   42.268482] kdump-tools[3621]: The kernel version is not supported.
  [   42.268810] kdump-tools[3621]: The makedumpfile operation may be 
incomplete.
  [   42.269050] kdump-tools[3621]: The dmesg log is saved to 

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

2017-02-15 Thread bugproxy
--- Comment From hbath...@in.ibm.com 2017-02-15 12:46 EDT---
The issue is reproducible only when memory reserved for fadump is more than 50%
of the total available memory. Posted the fix patch upstream at

https://lists.ozlabs.org/pipermail/linuxppc-
dev/2017-February/154111.html

Thanks
Hari

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

Title:
  Ubuntu 17.04: "Oops: Exception in kernel mode, sig: 5 [#1]" seen
  during fadump over ssh on Alpine machine.

Status in linux package in Ubuntu:
  Triaged
Status in makedumpfile package in Ubuntu:
  Fix Released

Bug description:
  Problem Description
  
  "Oops: Exception in kernel mode, sig: 5 [#1]" seen during fadump over ssh on 
Alpine machine.

  Steps to Reproduce
  
  1. Configure fadump over ssh on Alpine machine.
  ssh-keygen -t rsa

  Add below lines in /etc/default/kdump-tools
  SSH="ubuntu@9.114.15.240"
  SSH_KEY=/root/.ssh/id_rsa

  # kdump-config propagate

  # kdump-config load

  # kdump-config show

  2. Trigger crash

  Logs
  ===
  ubuntu@alp9:~$ [   41.884641] usercopy: kernel memory exposure attempt 
detected from c000fb001020 (task_struct) (61408 bytes)
  [   41.884668] kernel BUG at /build/linux-okcqyo/linux-4.9.0/mm/usercopy.c:75!
  [   41.884672] Oops: Exception in kernel mode, sig: 5 [#1]
  [   41.884674] SMP NR_CPUS=2048 [   41.884676] NUMA 
  [   41.884677] pSeries
  [   41.884679] Modules linked in: pseries_rng vmx_crypto ib_iser rdma_cm 
iw_cm ib_cm ib_core configfs iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi ip_tables x_tables autofs4 btrfs raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear ibmvscsi lpfc crc32c_vpmsum 
scsi_transport_fc
  [   41.884714] CPU: 8 PID: 3977 Comm: makedumpfile Not tainted 
4.9.0-11-generic #12-Ubuntu
  [   41.884717] task: c00151fcdc00 task.stack: c00150064000
  [   41.884719] NIP: c0312978 LR: c0312974 CTR: 
006338e4
  [   41.884722] REGS: c001500678d0 TRAP: 0700   Not tainted  
(4.9.0-11-generic)
  [   41.884725] MSR: 80029033 [   41.884732]   
CR: 2800  XER: 0004
  [   41.884734] CFAR: c0b26cac SOFTE: 1 
  GPR00: c0312974 c00150067b50 c141a400 0063 
  GPR04: c00179a0ade8 c00179a1fc40 00a1b6ef  
  GPR08: 0007 c0f7f87c 000178a9 3ff0 
  GPR12: 2200 ce794800 3fff7f4d0010 3fff7f4d0010 
  GPR16: bb01 54150c98 5412da08 0001 
  GPR20: 540fea40 38448150 0001 c1717798 
  GPR24: 0001 c00150067cf0  1020 
  GPR28: c000fb01 0001 efe0 c000fb001020 
  NIP [c0312978] __check_object_size+0x88/0x2c0
  [   41.884777] LR [c0312974] __check_object_size+0x84/0x2c0
  [   41.884780] Call Trace:
  [   41.884782] [c00150067b50] [c0312974] 
__check_object_size+0x84/0x2c0 (unreliable)
  [   41.884787] [c00150067bd0] [c006aea4] copy_to_user+0x64/0xa0
  [   41.884791] [c00150067c10] [c0042360] 
copy_oldmem_page+0x140/0x1d0
  [   41.884796] [c00150067c60] [c03cd5a8] 
read_from_oldmem.part.0+0x138/0x150
  [   41.884800] [c00150067cd0] [c03cd6fc] read_vmcore+0x13c/0x270
  [   41.884803] [c00150067d40] [c03b8918] proc_reg_read+0x88/0xd0
  [   41.884807] [c00150067d70] [c0318f4c] __vfs_read+0x3c/0x70
  [   41.884811] [c00150067d90] [c031a1ac] vfs_read+0xbc/0x1b0
  [   41.884814] [c00150067de0] [c031bdc8] SyS_read+0x68/0x110
  [   41.884818] [c00150067e30] [c000bd84] system_call+0x38/0xe0
  [   41.884820] Instruction dump:
  [   41.884823] 6000 6042 3c82ff93 3ca2ff9d 38847130 38a5b3f8 3c62ff94 
7fc8f378 
  [   41.884830] 7fe6fb78 38635f20 488142dd 6000 <0fe0> 6042 
2ba30010 409d017c 
  [   41.884838] ---[ end trace c33ccad89db3894a ]---
  [   41.884840] 
  Copying data   : [ 43.7 %] -889527+439 records in
  [   41.805683] kdump-tools[3621]: 889744+1 records out
  [   41.805920] kdump-tools[3621]: 455549276 bytes (456 MB, 434 MiB) copied, 
24.5065 s, 18.6 MB/s
  [   42.263162] kdump-tools[3621]:  * kdump-tools: saved vmcore in 
ubuntu@9.114.15.240:/home/ubuntu/9.114.15.239-201701090710
  [   42.264882] kdump-tools[3621]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /tmp/dmesg.201701090710
  [   42.268482] kdump-tools[3621]: The kernel version is not supported.
  [   42.268810] kdump-tools[3621]: The makedumpfile operation may be 
incomplete.
  [   42.269050] kdump-tools[3621]: The dmesg log is saved to 

[Kernel-packages] [Bug 1664217] fozzie (i386) - tests ran: 1, failed: 0

2017-02-15 Thread Brad Figg
tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-8.10-generic/fozzie__4.10.0-8.10__2017-02-15_17-31-00/results-index.html

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

Title:
  linux: 4.10.0-8.10 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Fix Released
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:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: 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-development-workflow/+bug/1664217/+subscriptions

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


[Kernel-packages] [Bug 1555786] Re: [Hyper-V] VM with ubuntu 32bit with linux-next does not boot

2017-02-15 Thread Brad Figg
** Tags added: kernel-hyper-v

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

Title:
  [Hyper-V] VM with ubuntu 32bit with linux-next does not boot

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Yakkety:
  Incomplete
Status in linux source package in Zesty:
  Incomplete

Bug description:
  We identified that at least ubuntu (let's take 15.10) does not boot if
  installed in the 32bit architecture, and using the linux-next upstream
  kernel 4.5 on it. This has been seen on other distributions as well.

  We took both the official linux-next branch from kernel.org and the one from 
kernel.ubuntu.com v4.5-rc7.
  For the compilation process we went either with the 4.2 kernel config file 
from the installed running kernel, and also built the config separately. 
  No errors have been encountered during the build or install process of the 
4.5 kernel, however at boot, the VM will just hang.
  There are no call traces or messages at boot to show any pottential issue.

  Have you seen this on your end when testing the 32bit build?
  Attaching the full serial log for reference, however I don't see any errors 
in the kernel boot process.

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

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


[Kernel-packages] [Bug 1664217] gonzo (i386) - tests ran: 1, failed: 0

2017-02-15 Thread Brad Figg
tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-8.10-generic/gonzo__4.10.0-8.10__2017-02-15_17-33-00/results-index.html

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

Title:
  linux: 4.10.0-8.10 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Fix Released
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:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: 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-development-workflow/+bug/1664217/+subscriptions

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


[Kernel-packages] [Bug 1664217] kernel03 (s390x.zVM) - tests ran: 19, failed: 1

2017-02-15 Thread Brad Figg
tests ran:  19, failed: 1;
  
http://kernel.ubuntu.com/testing/4.10.0-8.10-generic/kernel03__4.10.0-8.10__2017-02-15_16-38-00/results-index.html

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

Title:
  linux: 4.10.0-8.10 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Fix Released
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:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: 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-development-workflow/+bug/1664217/+subscriptions

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


[Kernel-packages] [Bug 1660704] modoc (ppc64el) - tests ran: 64, failed: 0

2017-02-15 Thread Brad Figg
tests ran:  64, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-63.84-generic/modoc__4.4.0-63.84__2017-02-15_16-53-00/results-index.html

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

Title:
  linux: 4.4.0-63.84 -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-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
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 Xenial:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: 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/1660704/+subscriptions

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


[Kernel-packages] [Bug 1660704] rumford (amd64) - tests ran: 2, failed: 0

2017-02-15 Thread Brad Figg
tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-63.84-generic/rumford__4.4.0-63.84__2017-02-15_17-02-00/results-index.html

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

Title:
  linux: 4.4.0-63.84 -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-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
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 Xenial:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: 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/1660704/+subscriptions

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


[Kernel-packages] [Bug 1664217] gonzo (amd64) - tests ran: 1, failed: 0

2017-02-15 Thread Brad Figg
tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-8.10-generic/gonzo__4.10.0-8.10__2017-02-15_17-04-00/results-index.html

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

Title:
  linux: 4.10.0-8.10 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Fix Released
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:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: 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-development-workflow/+bug/1664217/+subscriptions

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


[Kernel-packages] [Bug 1664217] fozzie (amd64) - tests ran: 1, failed: 0

2017-02-15 Thread Brad Figg
tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-8.10-generic/fozzie__4.10.0-8.10__2017-02-15_17-04-00/results-index.html

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

Title:
  linux: 4.10.0-8.10 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Fix Released
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:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: 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-development-workflow/+bug/1664217/+subscriptions

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


[Kernel-packages] [Bug 1665016] Re: [4.10.0-8] ATK0110 ATK0110:00: hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info().

2017-02-15 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  [4.10.0-8] ATK0110 ATK0110:00: hwmon_device_register() is deprecated.
  Please convert the driver to use hwmon_device_register_with_info().

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Get that error logged:
   kernel: ATK0110 ATK0110:00: hwmon_device_register() is deprecated. Please 
convert the driver to use hwmon_device_register_with_info().

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-8-generic 4.10.0-8.10
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem2956 F pulseaudio
   /dev/snd/controlC0:  oem2956 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Feb 15 17:04:18 2017
  HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16
  IwConfig:
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-8-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-8-generic N/A
   linux-backports-modules-4.10.0-8-generic  N/A
   linux-firmware1.163
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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


[Kernel-packages] [Bug 1664217] kernel03 (s390x.zVM) - tests ran: 1, failed: 0

2017-02-15 Thread Brad Figg
tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-8.10-generic/kernel03__4.10.0-8.10__2017-02-15_16-37-00/results-index.html

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

Title:
  linux: 4.10.0-8.10 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Fix Released
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:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: 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-development-workflow/+bug/1664217/+subscriptions

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


[Kernel-packages] [Bug 1664217] Re: linux: 4.10.0-8.10 -proposed tracker

2017-02-15 Thread Brad Figg
** Changed in: kernel-development-workflow/automated-testing
   Status: New => Confirmed

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

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

** Changed in: kernel-development-workflow/automated-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug is for tracking the 4.10.0-8.10 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Uploaded
+ kernel-phase-changed:Wednesday, 15. February 2017 16:33 UTC
+ kernel-phase:Promoted to proposed

** Description changed:

  This bug is for tracking the 4.10.0-8.10 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
- phase: Uploaded
- kernel-phase-changed:Wednesday, 15. February 2017 16:33 UTC
- kernel-phase:Promoted to proposed
+ 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/1664217

Title:
  linux: 4.10.0-8.10 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Fix Released
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:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: 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-development-workflow/+bug/1664217/+subscriptions

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


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

2017-02-15 Thread Brad Figg
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/1665016

Title:
  [4.10.0-8] ATK0110 ATK0110:00: hwmon_device_register() is deprecated.
  Please convert the driver to use hwmon_device_register_with_info().

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Get that error logged:
   kernel: ATK0110 ATK0110:00: hwmon_device_register() is deprecated. Please 
convert the driver to use hwmon_device_register_with_info().

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-8-generic 4.10.0-8.10
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem2956 F pulseaudio
   /dev/snd/controlC0:  oem2956 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Feb 15 17:04:18 2017
  HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16
  IwConfig:
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-8-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-8-generic N/A
   linux-backports-modules-4.10.0-8-generic  N/A
   linux-firmware1.163
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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


[Kernel-packages] [Bug 1660704] rumford (amd64) - tests ran: 64, failed: 0

2017-02-15 Thread Brad Figg
tests ran:  64, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-63.84-generic/rumford__4.4.0-63.84__2017-02-15_15-56-00/results-index.html

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

Title:
  linux: 4.4.0-63.84 -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-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
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 Xenial:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: 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/1660704/+subscriptions

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


[Kernel-packages] [Bug 1660704] modoc (ppc64el) - tests ran: 2, failed: 0

2017-02-15 Thread Brad Figg
tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-63.84-generic/modoc__4.4.0-63.84__2017-02-15_16-16-00/results-index.html

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

Title:
  linux: 4.4.0-63.84 -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-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
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 Xenial:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: 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/1660704/+subscriptions

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


[Kernel-packages] [Bug 1663876] Re: [zesty] dkms nvidia error with linux-headers-4.10.0-7

2017-02-15 Thread dino99
Feedback

zesty 64 bit with kernel 4.10.0-8 + nvidia-378.13

kernel installation was good, and next cold boot was normal: journalctl
is clean (mostly)

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

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

Title:
  [zesty] dkms nvidia error with linux-headers-4.10.0-7

Status in dkms package in Ubuntu:
  Incomplete

Bug description:
  On Zesty, x64, I can't install the nvidia-378 driver with the new
  kernel 4.10.0-7 due to a dkms error.

  ...
  ERROR (dkms apport): kernel package linux-headers-4.10.0-7-generic is not 
supported
  Error! Bad return status for module build on kernel: 4.10.0-7-generic (x86_64)
  Consult /var/lib/dkms/nvidia-378/378.09/build/make.log for more information.
  ...

  And make.log as attachement

  Regards

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

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


[Kernel-packages] [Bug 1665016] [NEW] [4.10.0-8] ATK0110 ATK0110:00: hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info().

2017-02-15 Thread dino99
Public bug reported:

Get that error logged:
 kernel: ATK0110 ATK0110:00: hwmon_device_register() is deprecated. Please 
convert the driver to use hwmon_device_register_with_info().

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-8-generic 4.10.0-8.10
ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
Uname: Linux 4.10.0-8-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  oem2956 F pulseaudio
 /dev/snd/controlC0:  oem2956 F pulseaudio
CurrentDesktop: GNOME
Date: Wed Feb 15 17:04:18 2017
HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16
IwConfig:
 eth1  no wireless extensions.
 
 eth0  no wireless extensions.
 
 lono wireless extensions.
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-8-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-8-generic N/A
 linux-backports-modules-4.10.0-8-generic  N/A
 linux-firmware1.163
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3002
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5W DH Deluxe
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5W DH Deluxe
dmi.product.version: System Version
dmi.sys.vendor: ASUSTEK COMPUTER INC

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


** Tags: amd64 apport-bug package-from-proposed third-party-packages zesty

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

Title:
  [4.10.0-8] ATK0110 ATK0110:00: hwmon_device_register() is deprecated.
  Please convert the driver to use hwmon_device_register_with_info().

Status in linux package in Ubuntu:
  New

Bug description:
  Get that error logged:
   kernel: ATK0110 ATK0110:00: hwmon_device_register() is deprecated. Please 
convert the driver to use hwmon_device_register_with_info().

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-8-generic 4.10.0-8.10
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem2956 F pulseaudio
   /dev/snd/controlC0:  oem2956 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Feb 15 17:04:18 2017
  HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16
  IwConfig:
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-8-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-8-generic N/A
   linux-backports-modules-4.10.0-8-generic  N/A
   linux-firmware1.163
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

[Kernel-packages] [Bug 1579917] Re: Skylake processor never reaches low power states on X1 Carbon gen 4 with NVMe drive

2017-02-15 Thread Dave Chiluk
@djao, sorry for the slow response.  I hit pc8 briefly, but that's with
most everything tuned, and running nothing.  Lots of applications seem
to be pretty power hungry for me.  That's going to have to get tackled
by each upstream project before we integrate solutions into the distro.

@fthx.  Welcome to the club.  Did you try updating the IMEI firmware?

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

Title:
  Skylake processor never reaches low power states on X1 Carbon gen 4
  with NVMe drive

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Reproducer
  1. Find a skylake machine. - in my case Lenovo x1 carbon gen 4. In my case 
with an NVME drive.
  2. run powertop, and switch to idle stats tab
  3. do nothing. *(as in let the machine idle till the cores regularly reach 
low power states.
  4. Watch the watts fly.  On my  machine the package never gets into any power 
state other than PC2.

  Expected results: PC3-PC10 power states should all show some usage.

  I also tried the mainline build of 4.6-rc7 with no benefits.

  Public conversations about the issue
  https://mjg59.dreamwidth.org/42156.html
  https://mjg59.dreamwidth.org/41713.html

  As far as I can tell having the nvme drive is part of the overall
  problem here.  Please keep this case to skylake + nvme.  Skylake +
  sata appears to have a number of fixes in the 4.6 and newer kernels
  that enable some of the higher sleep states, but I have not tested
  with a sata drive.  Those fixes as of testing 4.6-rc7 do not resolve
  this issue with users who have nvme drives.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.39
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chiluk 3139 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon May  9 15:55:03 2016
  HibernationDevice: RESUME=UUID=4f4ea88e-642e-4be5-bdf0-bbc7f47f5628
  InstallationDate: Installed on 2016-04-25 (14 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b531 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FBCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=249f91bb-7789-41cc-9cc0-8ba25d7f55bb ro quiet splash pcie_aspm=force 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/15/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET37W (1.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FBCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET37W(1.11):bd03/15/2016:svnLENOVO:pn20FBCTO1WW:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FBCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FBCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 4th
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1664579] Re: package linux-image-4.4.0-62-generic 4.4.0-62.83 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

2017-02-15 Thread Susanne Jensen
I did send this in as private but if its been changed to public as long
as i can get an answer to what might be causing the repeated issue I
would be greatful either way at this point ...

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

Title:
  package linux-image-4.4.0-62-generic 4.4.0-62.83 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  its been crashing system for awhile each time 
  first i thought it was a bad superblock but it won't let me fix it
  says-in the initramfs to run fsck manually-  when i try to do the fsck code 
error i got
  was /dev/mapper/ubuntu --vg-root contains a file system with errors check 
forced 
  inodes have a part of a corrupted orphan linked list found 
  the fsck fails exited with status code 4 /dev/mapper/ubuntu --vg-root

  so i start the sudo fsck code but it says there is no sudo and locks
  me out of everthing

  changed partitioning i had to something completely different  and then it 
crashed again yesterday
  after i logged out two other times it was while using gimp or my paint
  and i spent hours over normal it wouldnt delete 2GiB of data on the wiping 
  of drive through PartedMagic 
  but I finally thought last night i got ubuntu back up yet today
  it says there was a error in it when i created the OS back
  hope you can help with this bug report 
  i am at a lost to why?
  not sure if its security issue or not but reporting that it is
  because i didn't think that should happen
  i have checked the actual hdd and it says its passed and fine in PartedMagic 
  if its to crash again 
  reporting this cause i just don't know what else to do

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-62-generic 4.4.0-62.83
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sjart  1590 F pulseaudio
  Date: Tue Feb 14 01:21:08 2017
  DuplicateSignature:
   package:linux-image-4.4.0-62-generic:4.4.0-62.83
   Setting up linux-image-4.4.0-62-generic (4.4.0-62.83) ...
   Internal Error: Could not find image (/boot/vmlinuz-4.4.0-62-generic)
   dpkg: error processing package linux-image-4.4.0-62-generic (--configure):
subprocess installed post-installation script returned error exit status 2
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  HibernationDevice: RESUME=UUID=3bf1824d-1236-4bdc-9206-d19b22854661
  InstallationDate: Installed on 2017-02-14 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 1545
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.7
  SourcePackage: linux
  Title: package linux-image-4.4.0-62-generic 4.4.0-62.83 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/25/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0G848F
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd02/25/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1545
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1660704] modoc (ppc64el) - tests ran: 141, failed: 0

2017-02-15 Thread Brad Figg
tests ran: 141, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-63.84-generic/modoc__4.4.0-63.84__2017-02-15_15-06-00/results-index.html

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

Title:
  linux: 4.4.0-63.84 -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-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
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 Xenial:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: 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/1660704/+subscriptions

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


[Kernel-packages] [Bug 1651981] Re: shaking screen

2017-02-15 Thread Adrian
Christopher, I have tested and confirm that cherry pick of commit
8a08403bcb39f5d0e733bcf59a8a74f16b538f6e from the upstream kernel to
Ubuntu-4.8.0-37.39 tag fixes the issue.

** Changed in: linux (Ubuntu)
   Status: Triaged => 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/1651981

Title:
  shaking screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After login into Ubuntu the screen starts to shake permanently.
  The login screen is still fine, problem start after log in.
  The problem is caused by last kernel update: running Ubuntu with the older 
kernel 4.8.0-30-generic fixes the issue.

  Upstream patch submission:
  https://lists.freedesktop.org/archives/dri-devel/2016-December/128331.html

  WORKAROUND: Revert:
  # first bad commit: [9cc4fd5b9fbb0d74e77c81521da1e2fe712f6787] 
drm/radeon/si_dpm: workaround for SI kickers

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-32-generic 4.8.0-32.34
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  afiergol   7797 F pulseaudio
   /dev/snd/controlC1:  afiergol   7797 F pulseaudio
   /dev/snd/seq:timidity   6155 F timidity
  Date: Thu Dec 22 10:02:30 2016
  HibernationDevice: RESUME=UUID=7ca97ca1-ca2d-43f6-9b4c-cd61421c0831
  InstallationDate: Installed on 2015-04-02 (629 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Hewlett-Packard HP ZBook 15 G2
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-32-generic 
root=/dev/mapper/ubuntu--vg-root ro radeon.dpm=1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-32-generic N/A
   linux-backports-modules-4.8.0-32-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-16 (66 days ago)
  dmi.bios.date: 04/25/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M70 Ver. 01.15
  dmi.board.name: 2253
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 03.12
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM70Ver.01.15:bd04/25/2016:svnHewlett-Packard:pnHPZBook15G2:pvrA3008CD10003:rvnHewlett-Packard:rn2253:rvrKBCVersion03.12:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ZBook 15 G2
  dmi.product.version: A3008CD10003
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1650336] Re: NFS client : kernel 4.4.0-57 crash with nfsv4 enries in /etc/fstab

2017-02-15 Thread Seth Forshee
Sorry for the delay. Please test the kernel below to see if it fixes the
problem. It also includes the submount permission fix from the other
bug.

http://people.canonical.com/~sforshee/lp1650336/linux-4.4.0-63.84+lp1650336v201702150737/

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

Title:
  NFS client : kernel 4.4.0-57 crash with nfsv4 enries in /etc/fstab

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

Bug description:
  On (K)ubuntu 16.04.01 (Xenial) Upgrading to kernel 4.4.0-57 the kernel
  crash on boot when in /etc/fstab a nfsv4 entry is active

  When comment the line or set to noauto the kernel boot with no error
  and mounting the nfs shares (after uncomment ) is also possible
  without error

  4.4.0-54 boots without this problem.

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

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


[Kernel-packages] [Bug 1663265] Re: hibernation does not work probably due to ata subsystem failure (16.10 server)

2017-02-15 Thread Przemyslaw Czarnowski
Reproduced on latest 4.10 rc8

** Tags added: kernel-bug-exists-upstream

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

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

Title:
  hibernation does not work probably due to ata subsystem failure (16.10
  server)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Details:
  * Ubuntu 16.10 Server
  * System right after installation
  * only serial console logging has been enabled
  * used pm-hibernate to initiate S4 transition from root account

  Logs according to https://wiki.ubuntu.com/DebuggingKernelHibernate has
  been collected and attached.

  The same configuration on 16.04 server works perfectly.

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

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


[Kernel-packages] [Bug 1664170] Re: Resume from S4 - reboot after disabling CPUs procedure (15.10 server)

2017-02-15 Thread Przemyslaw Czarnowski
Reproduced on the latest 4.10 rc8

** Tags added: kernel-bug-exists-upstream

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

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

Title:
  Resume from S4 - reboot after disabling CPUs procedure (15.10 server)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Details:
  * Ubuntu 15.10 Server
  * System right after installation (no upgrades)
  * only serial console logging has been enabled
  * used pm-hibernate to initiate S4 transition from root account

  Logs according to https://wiki.ubuntu.com/DebuggingKernelHibernate has been 
collected and attached.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.2.0-42-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=681be7f0-8ce9-4ee6-8c23-cb77a6516503
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
   
   enp23s0   no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 14dd:0002 Raritan Computer, Inc. 
   Bus 001 Device 002: ID 0409:005a NEC Corp. HighSpeed Hub
   Bus 001 Device 003: ID 058f:6387 Alcor Micro Corp. Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Intel Corporation PURLEY
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-42-generic.efi.signed 
root=UUID=6448ab2b-f1bb-4ff5-9b21-5adaa56116eb ro console=tty0 
console=ttyS0,115200n8 no_console_suspend
  ProcVersionSignature: Ubuntu 4.2.0-42.49-generic 4.2.8-ckt12
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-42-generic N/A
   linux-backports-modules-4.2.0-42-generic  N/A
   linux-firmware1.149.3
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: PLYDCRB1.86B.0119.R05.1701181843
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: PURLEY
  dmi.board.vendor: Intel Corporation
  dmi.board.version: E63448-400
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 23
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrPLYDCRB1.86B.0119.R05.1701181843:bd01/18/2017:svnIntelCorporation:pnPURLEY:pvrE63448-400:rvnIntelCorporation:rnPURLEY:rvrE63448-400:cvnIntelCorporation:ct23:cvr0.1:
  dmi.product.name: PURLEY
  dmi.product.version: E63448-400
  dmi.sys.vendor: Intel Corporation

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

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


[Kernel-packages] [Bug 1660704] modoc (ppc64el) - tests ran: 16, failed: 2

2017-02-15 Thread Brad Figg
tests ran:  16, failed: 2;
  
http://kernel.ubuntu.com/testing/4.4.0-63.84-generic/modoc__4.4.0-63.84__2017-02-15_14-08-00/results-index.html

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

Title:
  linux: 4.4.0-63.84 -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-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
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 Xenial:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: 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/1660704/+subscriptions

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


[Kernel-packages] [Bug 1664708] Re: LTPstress :- genload: page allocation stalls on Ubuntu 17.04 , Power NV system

2017-02-15 Thread Manoj Iyer
How long does it take for you to reproduce this issue? I ran the same
test on AMD64 for over 12hrs and was not able to reproduce the failure.
The 17.04 kernel I have is 4.9.0-15-generic #16-Ubuntu SMP Fri Jan 20.

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

Title:
  LTPstress :- genload: page allocation stalls on Ubuntu 17.04 , Power
  NV system

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Shriya R. Kulkarni  - 2017-02-10 
06:24:36 ==
  Problem Description :
  ==
  Executed ./ltpstress.sh from ltp testsuite on Bare metal and suddenly system 
hangs up for few minutes. I see call traces in dmesg as genload : page 
allocation stalls.

  Test : 
  -
  Execution of ltpstress (LTP version : ltp-full-20170116)

  System :
  -- 
  Ubuntu 17.04, Power NV(Habanero and POwerKVM5)

  uname -a  : 
  ---
  4.9.0-15-generic

  Steps :
  --
  1. Download ltp testsuite
  2. Untar
  3. ./configure, make , make install
  4. cd /opt/ltp/testscripts/
  5. ./ltpstress.sh

  
  Call trace :
  

  [ 5443.865352] genload: 
  [ 5443.865352] genload: page allocation stalls for 37764ms, order:0, 
mode:0x24200ca(GFP_HIGHUSER_MOVABLE)
  [ 5443.865360] page allocation stalls for 51524ms, order:0
  [ 5443.865362] , mode:0x24200ca(GFP_HIGHUSER_MOVABLE)
  [ 5443.865365] CPU: 68 PID: 33142 Comm: genload Not tainted 4.9.0-15-generic 
#16-Ubuntu
  [ 5443.865366] Call Trace:
  [ 5443.865372] [c03bf10d3940] [c0b2b720] dump_stack+0xb0/0xf0 
(unreliable)
  [ 5443.865377] [c03bf10d3980] [c0259560] warn_alloc+0x130/0x160
  [ 5443.865382] [c03bf10d3a10] [c025a1b0] 
__alloc_pages_nodemask+0xb80/0xff0
  [ 5443.865386] [c03bf10d3c30] [c02d2794] 
alloc_pages_vma+0x104/0x350
  [ 5443.865390] [c03bf10d3cc0] [c029e948] 
handle_mm_fault+0x1058/0x1510
  [ 5443.865393] [c03bf10d3d80] [c0054d10] do_page_fault+0x350/0x7d0
  [ 5443.865398] [c03bf10d3e30] [c000b148] 
handle_page_fault+0x10/0x30
  [ 5443.865400] Mem-Info:
  [ 5443.865403] CPU: 22 PID: 33414 Comm: genload Not tainted 4.9.0-15-generic 
#16-Ubuntu
  [ 5443.865404] Call Trace:
  [ 5443.865407] [c03b565e7940] [c0b2b720] dump_stack+0xb0/0xf0
  [ 5443.865414] active_anon:3975704 inactive_anon:84983 isolated_anon:12968
  active_file:233 inactive_file:186 isolated_file:0
  unevictable:69 dirty:4 writeback:5409 unstable:0
  slab_reclaimable:5089 slab_unreclaimable:25129
  mapped:107 shmem:3 pagetables:1631 bounce:0
  free:2544 free_pcp:0 free_cma:214
  [ 5443.865416]  (unreliable)
  [ 5443.865420] [c03b565e7980] [c0259560] warn_alloc+0x130/0x160
  [ 5443.865424] [c03b565e7a10] [c025a1b0] 
__alloc_pages_nodemask+0xb80/0xff0
  [ 5443.865428] [c03b565e7c30] [c02d2794] 
alloc_pages_vma+0x104/0x350
  [ 5443.865438] [c03b565e7cc0] [c029e948] 
handle_mm_fault+0x1058/0x1510
  [ 5443.865438] Node 0 active_anon:254445056kB inactive_anon:5438912kB 
active_file:14912kB inactive_file:11904kB unevictable:4416kB 
isolated(anon):829952kB isolated(file):0kB mapped:6848kB dirty:256kB 
writeback:346176kB shmem:0kB shmem_thp: 0kB shmem_pmdmapped: 217022464kB 
anon_thp: 192kB writeback_tmp:0kB unstable:0kB pages_scanned:0 
all_unreclaimable? no
  [ 5443.865443] [c03b565e7d80] [c0054d10] do_page_fault+0x350/0x7d0
  [ 5443.865443] Node 0 DMA free:162816kB min:180224kB low:443776kB 
high:707328kB active_anon:254445056kB inactive_anon:5436096kB 
active_file:10816kB inactive_file:15232kB unevictable:4416kB 
writepending:341504kB present:268435456kB managed:263658752kB mlocked:4416kB 
slab_reclaimable:325696kB slab_unreclaimable:1608256kB kernel_stack:21776kB 
pagetables:104384kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:13696kB
  [ 5443.865453] lowmem_reserve[]:
  [ 5443.865457] [c03b565e7e30] [c000b148] 
handle_page_fault+0x10/0x30
  [ 5443.865458]  0
  [ 5443.865460]  0
  [ 5443.865461]  0 0
  [ 5443.865464] Mem-Info:
  [ 5443.865466] Node 0 DMA: 433*64kB (UMEC) 135*128kB 
  [ 5443.865476] active_anon:3975704 inactive_anon:84983 isolated_anon:12968
  active_file:233 inactive_file:186 isolated_file:0
  unevictable:69 dirty:4 writeback:5409 unstable:0
  slab_reclaimable:5089 slab_unreclaimable:25129
  mapped:107 shmem:3 pagetables:1631 bounce:0
  free:2544 free_pcp:0 free_cma:214
  [ 5443.865477] (UMEC) 35*256kB (UME) 10*512kB (UMEC) 32*1024kB (UME) 9*2048kB 
(UME) 3*4096kB (UM) 6*8192kB (MC) 0*16384kB = 171712kB
  [ 5443.865493] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 
hugepages_size=1024kB

  == Comment: #4 - Shriya R. Kulkarni 

[Kernel-packages] [Bug 1384955] Re: support compressed kernels on arm64

2017-02-15 Thread Launchpad Bug Tracker
This bug was fixed in the package debian-installer -
20101020ubuntu451.10

---
debian-installer (20101020ubuntu451.10) xenial; urgency=medium

  [ dann frazier ]
  * arm64/xgene-uboot: Set the correct compression flag when generating
a uImage of a gzip'd kernel. LP: #1384955.
  * Tell GRUB to load the gzio module on arm64 now that we're booting
a compressed kernel. LP: #1632473.

  [ Adam Conrad ]
  * Add HWE variants for all architectures except powerpc (LP: #1662712)
  * Move master kernels to 4.4.0-62.
  * Rebuild to pick up new components (LP: #1572620, #1558271)

 -- Adam Conrad   Tue, 07 Feb 2017 07:13:40 -0700

** Changed in: debian-installer (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  support compressed kernels on arm64

Status in debian-installer package in Ubuntu:
  Fix Released
Status in flash-kernel package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-edge package in Ubuntu:
  New
Status in debian-installer source package in Xenial:
  Fix Released
Status in flash-kernel source package in Xenial:
  Fix Released
Status in linux-hwe-edge source package in Xenial:
  New
Status in flash-kernel package in Debian:
  New

Bug description:
  [Impact]
  Ubuntu kernels >= hwe-y (4.8) will no longer boot on xgene/uboot systems. The 
image size appears to have outgrown the defined firmware region, and u-boot 
will error out with a checksum mismatch error. A solution for this is to start 
shipping a compressed kernel (Image.gz target). flash-kernel needs updating to 
detect a compressed kernel and set the appropriate uImage compression flag. 
Similarly, d-i needs updating because it does it's own uImage generation.

  [Test Case]
  Boot an hwe-y kernel on an xgene/uboot system (APM Mustang, HP ProLiant m400).

  [Regression Risk]
  The necessary code is in place and in-use for yakkety, and no issues have 
been discovered there. The SRU involves clean cherry-picks of that code for d-i 
& f-k. The kernel side needs to be modified to pull in the correct version of 
flash-kernel for xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1384955/+subscriptions

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


  1   2   >