date:20170227

--- Comment From sthou...@in.ibm.com 2017-02-28 00:57 EDT---
(In reply to comment #24)
> The patch attached to comment #2 does not appear to be a fix for the issue
> reported in this bug. Could you pls point me to an upstream fix you might
> have identified that addresses this issue? I can make a best effort in
> merging that patch in Ubuntu.

patch file for crash and makedumpfile attached above fixes this issue
and been fixed with the following Ubuntu

https://launchpad.net/ubuntu/+source/crash/7.1.4-1ubuntu4.1
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.5.9-5ubuntu0.4

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

Title:
  Ubuntu 16.04.02: crash tool fails with error "cannot find
  'cpu_possible_map', 'cpu_present_map', 'cpu_online_map' or
  'cpu_active_map' symbols".

Status in crash package in Ubuntu:
  New
Status in makedumpfile package in Ubuntu:
  New

Bug description:
  ---Problem Description---

  Ubuntu 16.04.02: crash tool fails with error "cannot find
  'cpu_possible_map', 'cpu_present_map', 'cpu_online_map' or
  'cpu_active_map' symbols".

  ---Steps to Reproduce---

  1. Install 16.04.02 [ 4.8.0-32-generic ].
  2. Configure kdump.
  3. Install debug package. 
  4. trigger crash.
  5. run crash tool on dump captured.

  sudo tee /etc/apt/sources.list.d/ddebs.list << EOF
  deb http://ddebs.ubuntu.com/ $(lsb_release -cs) main restricted universe 
multiverse
  deb http://ddebs.ubuntu.com/ $(lsb_release -cs)-security main restricted 
universe multiverse
  deb http://ddebs.ubuntu.com/ $(lsb_release -cs)-updates main restricted 
universe multiverse
  deb http://ddebs.ubuntu.com/ $(lsb_release -cs)-proposed main restricted 
universe multiverse
  EOF 

  sudo apt-get update
  sudo apt-get install linux-image-$(uname -r)-dbgsym  


  
  path: /var/crash/201612190432

  Logs
  ===

  root@ltc-haba2:/var/crash/201612190432# crash
  /usr/lib/debug/boot/vmlinux-4.8.0-32-generic dump.201612190432

  crash 7.1.4
  Copyright (C) 2002-2015  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.
   
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  
  crash: PPC64: cannot find 'cpu_possible_map', 'cpu_present_map', 
'cpu_online_map' or 'cpu_active_map' symbols

  
  It appears problem is with System.map-4.8.0-32-generic file 

  (gdb) symbol-file System.map-4.8.0-32-generic -readshow
  `/boot/System.map-4.8.0-32-generic': can't read symbols: File format not 
recognized.
  (gdb) 

  crash System.map-4.8.0-32-generic
  /usr/lib/debug/boot/vmlinux-4.8.0-32-generic
  /var/crash/201612260004/dump.201612260004

  crash 7.1.4
  Copyright (C) 2002-2015  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.
   
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

 
  crash: PPC64: cannot find 'cpu_possible_map', 'cpu_present_map', 
'cpu_online_map' or 'cpu_active_map' symbols

To

[Kernel-packages] [Bug 1667066] gonzo (i386) - tests ran: 64, failed: 64

tests ran:  64, failed: 64;
  
http://kernel.ubuntu.com/testing/4.8.0-40.43-generic/gonzo__4.8.0-40.43__2017-02-28_02-46-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/1667066

Title:
  linux: 4.8.0-40.43 -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:
  Confirmed
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 Yakkety:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  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/1667066/+subscriptions

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

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

--- Comment From vajai...@in.ibm.com 2017-02-28 00:41 EDT---
(In reply to comment #34)
> Setting CONFIG_PCIEPORTBUS=n has already been applied to our 4.10 kernel in
> response to bug #1665404. If pcieportdrv is to blame I believe this should
> take care of the problem. Can you confirm? Thanks!

PCIE port bus driver simply exposed this issue with pnv-php module and
since its not needed on ppc64 we requested it to be disabled. Since the
core issue lies with pnv-phb hence ideally we would like above patches
to be applied so that the issue doesnt get reproduced in any other way.

~ Vaibhav

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

Title:
  CAPI:Ubuntu: Kernel panic while rebooting

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  default desc

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

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

[Kernel-packages] [Bug 1668135] Re: Bluetooth is not working pls help~

dell@dell-Vostro-1320:~$ sudo lsusb |grep Bluetooth
Bus 008 Device 003: ID 413c:8126 Dell Computer Corp. Wireless 355 Bluetooth
Bus 008 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of 
BCM2046 Bluetooth)
dell@dell-Vostro-1320:~$

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

Title:
  Bluetooth is not working pls help~

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  dell@dell-Vostro-1320:~$ sudo cat /sys/kernel/debug/usb/devices

  T:  Bus=08 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12   MxCh= 2
  B:  Alloc=  4/900 us ( 0%), #Int=  3, #Iso=  0
  D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
  P:  Vendor=1d6b ProdID=0001 Rev= 4.04
  S:  Manufacturer=Linux 4.4.0-62-generic uhci_hcd
  S:  Product=UHCI Host Controller
  S:  SerialNumber=:00:1d.2
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   2 Ivl=255ms

  T:  Bus=08 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=12   MxCh= 3
  D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
  P:  Vendor=0a5c ProdID=4500 Rev= 1.00
  S:  Manufacturer=Broadcom
  S:  Product=BCM2045B2
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   1 Ivl=255ms

  T:  Bus=08 Lev=02 Prnt=02 Port=01 Cnt=01 Dev#=  3 Spd=12   MxCh= 0
  D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
  P:  Vendor=0a5c ProdID=4502 Rev= 1.00
  S:  Manufacturer=Broadcom Corp
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=01 Driver=usbhid
  E:  Ad=81(I) Atr=03(Int.) MxPS=   8 Ivl=10ms

  T:  Bus=08 Lev=02 Prnt=02 Port=02 Cnt=02 Dev#=  4 Spd=12   MxCh= 0
  D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
  P:  Vendor=0a5c ProdID=4503 Rev= 1.00
  S:  Manufacturer=Broadcom Corp
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=02 Driver=usbhid
  E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=10ms

  T:  Bus=07 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12   MxCh= 2
  B:  Alloc=  0/900 us ( 0%), #Int=  0, #Iso=  0
  D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
  P:  Vendor=1d6b ProdID=0001 Rev= 4.04
  S:  Manufacturer=Linux 4.4.0-62-generic uhci_hcd
  S:  Product=UHCI Host Controller
  S:  SerialNumber=:00:1d.1
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   2 Ivl=255ms

  T:  Bus=06 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12   MxCh= 2
  B:  Alloc= 11/900 us ( 1%), #Int=  1, #Iso=  0
  D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
  P:  Vendor=1d6b ProdID=0001 Rev= 4.04
  S:  Manufacturer=Linux 4.4.0-62-generic uhci_hcd
  S:  Product=UHCI Host Controller
  S:  SerialNumber=:00:1d.0
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   2 Ivl=255ms

  T:  Bus=06 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=1.5  MxCh= 0
  D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
  P:  Vendor=413c ProdID=3200 Rev= 1.10
  S:  Manufacturer=Dell
  S:  Product=Dell USB Mouse
  C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=02 Driver=usbhid
  E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=10ms

  T:  Bus=05 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12   MxCh= 2
  B:  Alloc=  0/900 us ( 0%), #Int=  0, #Iso=  0
  D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
  P:  Vendor=1d6b ProdID=0001 Rev= 4.04
  S:  Manufacturer=Linux 4.4.0-62-generic uhci_hcd
  S:  Product=UHCI Host Controller
  S:  SerialNumber=:00:1a.2
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   2 Ivl=255ms

  T:  Bus=04 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12   MxCh= 2
  B:  Alloc=  0/900 us ( 0%), #Int=  0, #Iso=  0
  D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
  P:  Vendor=1d6b ProdID=0001 Rev= 4.04
  S:  Manufacturer=Linux 4.4.0-62-generic uhci_hcd
  S:  Product=UHCI Host Controller
  S:  SerialNumber=:00:1a.1
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   2 Ivl=255ms

  T:  Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12   MxCh= 2
  B:  Alloc=  0/900 us ( 0%), #Int=  0, #Iso=  0
  D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
  P:  Vendor=1d6b ProdID=0001 Rev= 4.04
  S:  Manufacturer=Linux 4.4.0-62-generic uhci_hcd
  S:  Product=UHCI Host Controller
  S:  SerialNumber=:00:1a.0
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub

[Kernel-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

2017-02-27 Thread Rolf Leggewie

I'm happy to report that with the latest kernel from
http://kernel.ubuntu.com/~jsalisbury/lp1619918/ the original issue with
lsattr is fixed and there are no regressions with "btrfs fi show" or
"btrfs sub snapshot".

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

Title:
  lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

Status in linux:
  Unknown
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:
  I run an amd64 kernel on trusty.  The e2fsprogs package was still the
  32 bit i386 variety.  This lead to the following situation (for
  essentially all files on a btrfs partition).

  $ lsattr 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko
  lsattr: Inappropriate ioctl for device While reading flags on 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko

  The problem was resolved by installing e2fsprogs:amd64.

  https://patchwork.kernel.org/patch/7517361/ might be related.

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

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

[Kernel-packages] [Bug 1668135] Re: Bluetooth is not working pls help~

dell@dell-Vostro-1320:~$ sudo lsusb |grep Bluetooth
Bus 008 Device 003: ID 413c:8126 Dell Computer Corp. Wireless 355 Bluetooth
Bus 008 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of 
BCM2046 Bluetooth)
dell@dell-Vostro-1320:~$

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

Title:
  Bluetooth is not working pls help~

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  dell@dell-Vostro-1320:~$ sudo cat /sys/kernel/debug/usb/devices

  T:  Bus=08 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12   MxCh= 2
  B:  Alloc=  4/900 us ( 0%), #Int=  3, #Iso=  0
  D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
  P:  Vendor=1d6b ProdID=0001 Rev= 4.04
  S:  Manufacturer=Linux 4.4.0-62-generic uhci_hcd
  S:  Product=UHCI Host Controller
  S:  SerialNumber=:00:1d.2
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   2 Ivl=255ms

  T:  Bus=08 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=12   MxCh= 3
  D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
  P:  Vendor=0a5c ProdID=4500 Rev= 1.00
  S:  Manufacturer=Broadcom
  S:  Product=BCM2045B2
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   1 Ivl=255ms

  T:  Bus=08 Lev=02 Prnt=02 Port=01 Cnt=01 Dev#=  3 Spd=12   MxCh= 0
  D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
  P:  Vendor=0a5c ProdID=4502 Rev= 1.00
  S:  Manufacturer=Broadcom Corp
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=01 Driver=usbhid
  E:  Ad=81(I) Atr=03(Int.) MxPS=   8 Ivl=10ms

  T:  Bus=08 Lev=02 Prnt=02 Port=02 Cnt=02 Dev#=  4 Spd=12   MxCh= 0
  D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
  P:  Vendor=0a5c ProdID=4503 Rev= 1.00
  S:  Manufacturer=Broadcom Corp
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=02 Driver=usbhid
  E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=10ms

  T:  Bus=07 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12   MxCh= 2
  B:  Alloc=  0/900 us ( 0%), #Int=  0, #Iso=  0
  D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
  P:  Vendor=1d6b ProdID=0001 Rev= 4.04
  S:  Manufacturer=Linux 4.4.0-62-generic uhci_hcd
  S:  Product=UHCI Host Controller
  S:  SerialNumber=:00:1d.1
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   2 Ivl=255ms

  T:  Bus=06 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12   MxCh= 2
  B:  Alloc= 11/900 us ( 1%), #Int=  1, #Iso=  0
  D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
  P:  Vendor=1d6b ProdID=0001 Rev= 4.04
  S:  Manufacturer=Linux 4.4.0-62-generic uhci_hcd
  S:  Product=UHCI Host Controller
  S:  SerialNumber=:00:1d.0
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   2 Ivl=255ms

  T:  Bus=06 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=1.5  MxCh= 0
  D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
  P:  Vendor=413c ProdID=3200 Rev= 1.10
  S:  Manufacturer=Dell
  S:  Product=Dell USB Mouse
  C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=02 Driver=usbhid
  E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=10ms

  T:  Bus=05 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12   MxCh= 2
  B:  Alloc=  0/900 us ( 0%), #Int=  0, #Iso=  0
  D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
  P:  Vendor=1d6b ProdID=0001 Rev= 4.04
  S:  Manufacturer=Linux 4.4.0-62-generic uhci_hcd
  S:  Product=UHCI Host Controller
  S:  SerialNumber=:00:1a.2
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   2 Ivl=255ms

  T:  Bus=04 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12   MxCh= 2
  B:  Alloc=  0/900 us ( 0%), #Int=  0, #Iso=  0
  D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
  P:  Vendor=1d6b ProdID=0001 Rev= 4.04
  S:  Manufacturer=Linux 4.4.0-62-generic uhci_hcd
  S:  Product=UHCI Host Controller
  S:  SerialNumber=:00:1a.1
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   2 Ivl=255ms

  T:  Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12   MxCh= 2
  B:  Alloc=  0/900 us ( 0%), #Int=  0, #Iso=  0
  D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
  P:  Vendor=1d6b ProdID=0001 Rev= 4.04
  S:  Manufacturer=Linux 4.4.0-62-generic uhci_hcd
  S:  Product=UHCI Host Controller
  S:  SerialNumber=:00:1a.0
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub

[Kernel-packages] [Bug 1668135] Re: Bluetooth is not working pls help~

dell@dell-Vostro-1320:~$ uname -r
4.4.0-62-generic
dell@dell-Vostro-1320:~$ dmesg | grep -i blue
[   89.965243] Bluetooth: Core ver 2.21
[   89.965339] Bluetooth: HCI device and connection manager initialized
[   89.965344] Bluetooth: HCI socket layer initialized
[   89.965348] Bluetooth: L2CAP socket layer initialized
[   89.965356] Bluetooth: SCO socket layer initialized
[   91.310220] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   91.310225] Bluetooth: BNEP filters: protocol multicast
[   91.310232] Bluetooth: BNEP socket layer initialized
[   91.434070] Bluetooth: RFCOMM TTY layer initialized
[   91.434078] Bluetooth: RFCOMM socket layer initialized
[   91.434086] Bluetooth: RFCOMM ver 1.11
dell@dell-Vostro-1320:~$

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

Title:
  Bluetooth is not working pls help~

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  dell@dell-Vostro-1320:~$ sudo cat /sys/kernel/debug/usb/devices

  T:  Bus=08 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12   MxCh= 2
  B:  Alloc=  4/900 us ( 0%), #Int=  3, #Iso=  0
  D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
  P:  Vendor=1d6b ProdID=0001 Rev= 4.04
  S:  Manufacturer=Linux 4.4.0-62-generic uhci_hcd
  S:  Product=UHCI Host Controller
  S:  SerialNumber=:00:1d.2
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   2 Ivl=255ms

  T:  Bus=08 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=12   MxCh= 3
  D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
  P:  Vendor=0a5c ProdID=4500 Rev= 1.00
  S:  Manufacturer=Broadcom
  S:  Product=BCM2045B2
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   1 Ivl=255ms

  T:  Bus=08 Lev=02 Prnt=02 Port=01 Cnt=01 Dev#=  3 Spd=12   MxCh= 0
  D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
  P:  Vendor=0a5c ProdID=4502 Rev= 1.00
  S:  Manufacturer=Broadcom Corp
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=01 Driver=usbhid
  E:  Ad=81(I) Atr=03(Int.) MxPS=   8 Ivl=10ms

  T:  Bus=08 Lev=02 Prnt=02 Port=02 Cnt=02 Dev#=  4 Spd=12   MxCh= 0
  D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
  P:  Vendor=0a5c ProdID=4503 Rev= 1.00
  S:  Manufacturer=Broadcom Corp
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=02 Driver=usbhid
  E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=10ms

  T:  Bus=07 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12   MxCh= 2
  B:  Alloc=  0/900 us ( 0%), #Int=  0, #Iso=  0
  D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
  P:  Vendor=1d6b ProdID=0001 Rev= 4.04
  S:  Manufacturer=Linux 4.4.0-62-generic uhci_hcd
  S:  Product=UHCI Host Controller
  S:  SerialNumber=:00:1d.1
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   2 Ivl=255ms

  T:  Bus=06 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12   MxCh= 2
  B:  Alloc= 11/900 us ( 1%), #Int=  1, #Iso=  0
  D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
  P:  Vendor=1d6b ProdID=0001 Rev= 4.04
  S:  Manufacturer=Linux 4.4.0-62-generic uhci_hcd
  S:  Product=UHCI Host Controller
  S:  SerialNumber=:00:1d.0
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   2 Ivl=255ms

  T:  Bus=06 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=1.5  MxCh= 0
  D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
  P:  Vendor=413c ProdID=3200 Rev= 1.10
  S:  Manufacturer=Dell
  S:  Product=Dell USB Mouse
  C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=02 Driver=usbhid
  E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=10ms

  T:  Bus=05 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12   MxCh= 2
  B:  Alloc=  0/900 us ( 0%), #Int=  0, #Iso=  0
  D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
  P:  Vendor=1d6b ProdID=0001 Rev= 4.04
  S:  Manufacturer=Linux 4.4.0-62-generic uhci_hcd
  S:  Product=UHCI Host Controller
  S:  SerialNumber=:00:1a.2
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   2 Ivl=255ms

  T:  Bus=04 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12   MxCh= 2
  B:  Alloc=  0/900 us ( 0%), #Int=  0, #Iso=  0
  D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
  P:  Vendor=1d6b ProdID=0001 Rev= 4.04
  S:  Manufacturer=Linux 4.4.0-62-generic uhci_hcd
  S:  Product=UHCI Host Controller
  S:  SerialNumber=:00:1a.1
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00

[Kernel-packages] [Bug 1668006] Re: Keyboard unresponsive after suspend Ubuntu 16.04 with touchscreen

2017-02-27 Thread nacenteno

Hi Joseph,


I appreciate your help with this issue.

I got the laptop late on 2015 new and installed 16.04 removing the
original OS (Win10).

The issue has been there since the very first start on Ubuntu 16.04 but
Windows 10 never had issues.

As for the upstream kernel, I see several Kernels 4.10 and 4.10.1, sorry
but your instruction is vague. I am not going to guess and install
without a very specific target.

Is there other specific log of settings you need to see before trying
any install?

Let me know.

Thanks.

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

Title:
  Keyboard unresponsive after suspend Ubuntu 16.04 with touchscreen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 16.04 64 bit
  Toshiba Satellite P55W-C with touchscreen
  CPU: Intel® Core™ i7-5500U CPU @ 2.40GHz × 4 
  Video Card: Intel® HD Graphics 5500 (Broadwell GT2) 
  Display: 15.6” diagonal widescreen TruBrite ® TFT LCD display at 1920 x 1080
  native resolution (FHD)

  After suspend, several times the keyboard is unresponsive.

  Touchscreen remain responsive all the time so I had to suspend again
  using the touchscreen and try again until keyboard is finally
  responsive.

  Already tried with an edit to /etc/default/grub
  Changed the line
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
  to
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash atkbd.reset"

  Then run update-grub, and reboot.

  That did not fix the issue.

  I have attached the output of  ubuntu-bug linux, what other
  information is needed to fix the issue?

  What do you suggest to solve the issue?

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-64-generic 4.4.0-64.85
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arturo 2047 F pulseaudio
   /dev/snd/pcmC1D0p:   arturo 2047 F...m pulseaudio
   /dev/snd/controlC1:  arturo 2047 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Feb 25 23:23:09 2017
  HibernationDevice: RESUME=UUID=16283a3e-099e-4e71-9bb9-60cae60bfc06
  InstallationDate: Installed on 2016-05-31 (271 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: TOSHIBA Satellite P55W-C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic 
root=UUID=13ab440b-6f1e-465c-969e-b434431dce7d ro quiet splash atkbd.reset 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-64-generic N/A
   linux-backports-modules-4.4.0-64-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 5.00
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: 0692
  dmi.board.vendor: FF40
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr5.00:bd07/01/2015:svnTOSHIBA:pnSatelliteP55W-C:pvrPSPVJU-00V016:rvnFF40:rn0692:rvr2.0:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite P55W-C
  dmi.product.version: PSPVJU-00V016
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1668135] Re: Bluetooth is not working pls help~

kernel-fixed-upstream

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

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

Title:
  Bluetooth is not working pls help~

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  dell@dell-Vostro-1320:~$ sudo cat /sys/kernel/debug/usb/devices

  T:  Bus=08 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12   MxCh= 2
  B:  Alloc=  4/900 us ( 0%), #Int=  3, #Iso=  0
  D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
  P:  Vendor=1d6b ProdID=0001 Rev= 4.04
  S:  Manufacturer=Linux 4.4.0-62-generic uhci_hcd
  S:  Product=UHCI Host Controller
  S:  SerialNumber=:00:1d.2
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   2 Ivl=255ms

  T:  Bus=08 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=12   MxCh= 3
  D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
  P:  Vendor=0a5c ProdID=4500 Rev= 1.00
  S:  Manufacturer=Broadcom
  S:  Product=BCM2045B2
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   1 Ivl=255ms

  T:  Bus=08 Lev=02 Prnt=02 Port=01 Cnt=01 Dev#=  3 Spd=12   MxCh= 0
  D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
  P:  Vendor=0a5c ProdID=4502 Rev= 1.00
  S:  Manufacturer=Broadcom Corp
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=01 Driver=usbhid
  E:  Ad=81(I) Atr=03(Int.) MxPS=   8 Ivl=10ms

  T:  Bus=08 Lev=02 Prnt=02 Port=02 Cnt=02 Dev#=  4 Spd=12   MxCh= 0
  D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
  P:  Vendor=0a5c ProdID=4503 Rev= 1.00
  S:  Manufacturer=Broadcom Corp
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=02 Driver=usbhid
  E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=10ms

  T:  Bus=07 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12   MxCh= 2
  B:  Alloc=  0/900 us ( 0%), #Int=  0, #Iso=  0
  D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
  P:  Vendor=1d6b ProdID=0001 Rev= 4.04
  S:  Manufacturer=Linux 4.4.0-62-generic uhci_hcd
  S:  Product=UHCI Host Controller
  S:  SerialNumber=:00:1d.1
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   2 Ivl=255ms

  T:  Bus=06 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12   MxCh= 2
  B:  Alloc= 11/900 us ( 1%), #Int=  1, #Iso=  0
  D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
  P:  Vendor=1d6b ProdID=0001 Rev= 4.04
  S:  Manufacturer=Linux 4.4.0-62-generic uhci_hcd
  S:  Product=UHCI Host Controller
  S:  SerialNumber=:00:1d.0
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   2 Ivl=255ms

  T:  Bus=06 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=1.5  MxCh= 0
  D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
  P:  Vendor=413c ProdID=3200 Rev= 1.10
  S:  Manufacturer=Dell
  S:  Product=Dell USB Mouse
  C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=02 Driver=usbhid
  E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=10ms

  T:  Bus=05 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12   MxCh= 2
  B:  Alloc=  0/900 us ( 0%), #Int=  0, #Iso=  0
  D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
  P:  Vendor=1d6b ProdID=0001 Rev= 4.04
  S:  Manufacturer=Linux 4.4.0-62-generic uhci_hcd
  S:  Product=UHCI Host Controller
  S:  SerialNumber=:00:1a.2
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   2 Ivl=255ms

  T:  Bus=04 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12   MxCh= 2
  B:  Alloc=  0/900 us ( 0%), #Int=  0, #Iso=  0
  D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
  P:  Vendor=1d6b ProdID=0001 Rev= 4.04
  S:  Manufacturer=Linux 4.4.0-62-generic uhci_hcd
  S:  Product=UHCI Host Controller
  S:  SerialNumber=:00:1a.1
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   2 Ivl=255ms

  T:  Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12   MxCh= 2
  B:  Alloc=  0/900 us ( 0%), #Int=  0, #Iso=  0
  D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
  P:  Vendor=1d6b ProdID=0001 Rev= 4.04
  S:  Manufacturer=Linux 4.4.0-62-generic uhci_hcd
  S:  Product=UHCI Host Controller
  S:  SerialNumber=:00:1a.0
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   2 Ivl=255ms

  T:  Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480  MxCh= 6
  B:

[Kernel-packages] [Bug 1666742] Re: Ath10k to read different board data file if specify in SMBIOS

2017-02-27 Thread Anthony Wong

** Also affects: hwe-next
   Importance: Undecided
   Status: New

** Changed in: hwe-next
 Assignee: (unassigned) => AceLan Kao (acelankao)

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

** Changed in: hwe-next
   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/1666742

Title:
  Ath10k to read different board data file if specify in SMBIOS

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

Bug description:
  Board Data File (BDF) is loaded upon driver boot-up procedure. The right
  board data file is identified, among others, by device and sybsystem ids.

  The problem, however, can occur when the (default) board data file cannot
  fulfill with the vendor requirements and it is necessary to use a different
  board data file.

  To solve the issue QCA uses SMBIOS type 0xF8 to store Board Data File Name
  Extension to specify the extension/variant name. The driver will take the
  extension suffix into consideration and will load the right (non-default)
  board data file if necessary.

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

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

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

tests ran:  64, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-40.43-generic/gonzo__4.8.0-40.43__2017-02-28_01-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/1667066

Title:
  linux: 4.8.0-40.43 -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:
  Confirmed
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 Yakkety:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  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/1667066/+subscriptions

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

[Kernel-packages] [Bug 1550270] Re: Touchpad stops working randomly

2017-02-27 Thread Petras

This problem comes from debian

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

Title:
  Touchpad stops working randomly

Status in linux package in Ubuntu:
  Expired

Bug description:
  Touchpad stops working randomly, sometimes only scroll function stops
  working but mostly entire mouse freezes. Unable to move around the
  desktop. Cant find anything in dmesg-, xorg- or syslog- logs that
  seems to cause it. A reboot solves the problem temporarily but occures
  soon again so something is borked.

  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  BootLog:

  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Feb 26 11:31:46 2016
  DistUpgraded: 2016-02-23 12:13:20,341 DEBUG enabling apt cron job
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:3978]
  InstallationDate: Installed on 2016-02-19 (6 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20344
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-6-generic 
root=UUID=56fd75d9-c132-48f8-8cd4-e69995ecae91 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to xenial on 2016-02-23 (2 days ago)
  dmi.bios.date: 10/16/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 96CN29WW(V1.15)
  dmi.board.asset.tag: 31900058WIN
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: 31900058WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213:
  dmi.product.name: 20344
  dmi.product.version: Lenovo Yoga 2 13
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160209-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1
  xserver.bootTime: Fri Feb 26 10:42:31 2016
  xserver.configfile: default
  xserver.errors: systemd-logind: failed to get session: PID 805 does not 
belong to any known session
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id8237
   vendor AUO
  xserver.version: 2:1.17.3-2ubuntu4

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

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

[Kernel-packages] [Bug 1667531] Re: [Hyper-V] Include bondvf in /usr/sbin for SR-IOV interface bonding

The test kernel in comment #7 will crash the kernel.

Please apply the patches mentioned in this bug to below test kernel which is 
verified as pass:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667527
http://kernel.ubuntu.com/~jsalisbury/lp1667527/Commit4a9b0933bdfOnBug1667007Tree/

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

Title:
  [Hyper-V] Include bondvf in /usr/sbin for SR-IOV interface bonding

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

Bug description:
  Please include bondvf.sh from kernel git tools/hv/ in /usr/sbin

  commit fd7aabb062fa1a8331a786d617744de220eaf002
  Author: Haiyang Zhang 
  Date:   Fri Dec 2 15:55:38 2016 -0800

  tools: hv: Enable network manager for bonding scripts on RHEL

  We found network manager is necessary on RHEL to make the synthetic
  NIC, VF NIC bonding operations handled automatically. So, enabling
  network manager here.

  Signed-off-by: Haiyang Zhang 
  Reviewed-by: K. Y. Srinivasan 
  Signed-off-by: David S. Miller 

  commit 178cd55f086629cf0bad9c66c793a7e2bcc3abb6
  Author: Haiyang Zhang 
  Date:   Mon Jul 11 17:06:42 2016 -0700

  tools: hv: Add a script to help bonding synthetic and VF NICs

  This script helps to create bonding network devices based on synthetic NIC
  (the virtual network adapter usually provided by Hyper-V) and the matching
  VF NIC (SRIOV virtual function). So the synthetic NIC and VF NIC can
  function as one network device, and fail over to the synthetic NIC if VF 
is
  down.

  Mayjor distros (RHEL, Ubuntu, SLES) supported by Hyper-V are supported by
  this script.

  Signed-off-by: Haiyang Zhang 
  Reviewed-by: K. Y. Srinivasan 
  Signed-off-by: David S. Miller 

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

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

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

tests ran:   2, failed: 2;
  
http://kernel.ubuntu.com/testing/4.8.0-40.43-generic/gonzo__4.8.0-40.43__2017-02-28_01-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/1667066

Title:
  linux: 4.8.0-40.43 -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:
  Confirmed
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 Yakkety:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  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/1667066/+subscriptions

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

[Kernel-packages] [Bug 1667052] Re: linux: 4.4.0-65.86 -proposed tracker

2017-02-27 Thread Steve Beattie

** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => 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/1667052

Title:
  linux: 4.4.0-65.86 -proposed tracker

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

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

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

  backports: 1667054
  derivatives: 1667056,1667058,1667061
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1667527] Re: [Hyper-V] pci-hyperv: Use device serial number as PCI domain

Thanks. This test kernel works.

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

Title:
  [Hyper-V] pci-hyperv: Use device serial number as PCI domain

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

Bug description:
  This allows PCI domain numbers starts with 1, and also unique
  on the same VM. So names, such as VF NIC names, that include
  domain number as part of the name, can be shorter than that
  based on part of bus UUID previously. The new names will also
  stay same for VMs created with copied VHD and same number of
  devices.

  This is needed for SR-IOV in Azure.

  This is Bjorn's tree for 4.11 here:
  https://git.kernel.org/cgit/linux/kernel/git/helgaas/pci.git/commit/?h=pci
  /host-hv=4a9b0933bdfcd85da840284bf5a0eb17b654b9c2

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

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

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

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-40.43-generic/gonzo__4.8.0-40.43__2017-02-28_00-46-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/1667066

Title:
  linux: 4.8.0-40.43 -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:
  Confirmed
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 Yakkety:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  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/1667066/+subscriptions

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

[Kernel-packages] [Bug 1661695] Re: screen flickering raedon

2017-02-27 Thread louiedog

I think a fix for this was committed a few days ago. Possibly
http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-
firmware.git/commit/?id=e8fe3bfd306d376c035c754e6c7d36826a0e3f78

I copied all the new firmware from radeon and amdgpu over to
/lib/firmware and rebuilt the latest 4.10 kernel and the issue is gone!

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

Title:
  screen flickering raedon

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  4.4.0-53 WORKS FINE

  4.4.0-62 DOES NOT WORK (screen flickers)

  It seems there is a problem with powersafe:

  With auto:
  echo auto > /sys/class/drm/card0/device/power_dpm_force_performance_level

  you will see heavy screen flickering on higher display resolutions

  With low or high:
  echo low > /sys/class/drm/card0/device/power_dpm_force_performance_level or
  echo high > /sys/class/drm/card0/device/power_dpm_force_performance_level

  there is no screen flickering

  And having performance level set to HIGH at all times is not a
  workaround because it wears out the card. :(

  details:

  Linux CINNAMON 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC
  2017 x86_64 x86_64 x86_64 GNU/Linux

  ```
  Vendor: X.Org (0x1002)
  Device: AMD PITCAIRN (DRM 2.43.0 / 4.4.0-62-generic, LLVM 5.0.0) (0x6811)
  Version: 17.1.0
  Accelerated: yes
  Video memory: 2048MB
  Unified memory: no
  Preferred profile: core (0x1)
  Max core profile version: 4.2
  Max compat profile version: 3.0
  Max GLES1 profile version: 1.1
  Max GLES[23] profile version: 3.0
  OpenGL vendor string: X.Org
  OpenGL renderer string: Gallium 0.4 on AMD PITCAIRN (DRM 2.43.0 / 
4.4.0-62-generic, LLVM 5.0.0)
  OpenGL core profile version string: 4.2 (Core Profile) Mesa 17.1.0-devel - 
padoka PPA
  OpenGL core profile shading language version string: 4.20
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile

  ```
  ---
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  atomi  3734 F pulseaudio
   /dev/snd/controlC0:  atomi  3734 F pulseaudio
   /dev/snd/controlC1:  atomi  3734 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.1
  HibernationDevice: RESUME=UUID=30254b0c-14d7-4c0e-9168-a8d492fa027b
  InstallationDate: Installed on 2016-12-27 (37 days ago)
  InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=41cc7dce-52e8-4b29-9347-60afc0a7d0ed 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.6
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  Tags:  serena
  Uname: Linux 4.4.0-53-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/23/2013
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FA
  dmi.board.name: GA-78LMT-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

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

tests ran: 141, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-40.43-generic/gonzo__4.8.0-40.43__2017-02-27_23-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/1667066

Title:
  linux: 4.8.0-40.43 -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:
  Confirmed
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 Yakkety:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  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/1667066/+subscriptions

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

[Kernel-packages] [Bug 1668129] Re: Amazon I3 Instance Buffer I/O error on dev nvme0n1

2017-02-27 Thread Ricky Ramirez

@ddstreet I can replicate the issue in us-west-2. All i3.2xls using ext4
as the filesystem I'm testing on.

ami-4e98182e (precise) - doesn't recognize device
ami-17ac2c77 (trusty) - no error
ami-edf6758d (xenial) - I/O errors
ami-a49b1bc4 (yakkety) - I/O errors

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

Title:
  Amazon I3 Instance Buffer I/O error on dev nvme0n1

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

Bug description:
  On the AWS i3 instance class - when putting the new NVME storage disks
  under high IO load - seeing data corruption and errors in dmesg

  
  [  662.884390] blk_update_request: I/O error, dev nvme0n1, sector 120063912
  [  662.887824] Buffer I/O error on dev nvme0n1, logical block 14971093, lost 
async page write
  [  662.891254] Buffer I/O error on dev nvme0n1, logical block 14971094, lost 
async page write
  [  662.895591] Buffer I/O error on dev nvme0n1, logical block 14971095, lost 
async page write
  [  662.899873] Buffer I/O error on dev nvme0n1, logical block 14971096, lost 
async page write
  [  662.904179] Buffer I/O error on dev nvme0n1, logical block 14971097, lost 
async page write
  [  662.908458] Buffer I/O error on dev nvme0n1, logical block 14971098, lost 
async page write
  [  662.912287] Buffer I/O error on dev nvme0n1, logical block 14971099, lost 
async page write
  [  662.916047] Buffer I/O error on dev nvme0n1, logical block 14971100, lost 
async page write
  [  662.920285] Buffer I/O error on dev nvme0n1, logical block 14971101, lost 
async page write
  [  662.924565] Buffer I/O error on dev nvme0n1, logical block 14971102, lost 
async page write
  [  663.645530] blk_update_request: I/O error, dev nvme0n1, sector 120756912
  
  [ 1012.752265] blk_update_request: I/O error, dev nvme0n1, sector 3744
  [ 1012.755396] buffer_io_error: 194552 callbacks suppressed
  [ 1012.755398] Buffer I/O error on dev nvme0n1, logical block 20, lost async 
page write
  [ 1012.759248] Buffer I/O error on dev nvme0n1, logical block 21, lost async 
page write
  [ 1012.763368] Buffer I/O error on dev nvme0n1, logical block 22, lost async 
page write
  [ 1012.767271] Buffer I/O error on dev nvme0n1, logical block 23, lost async 
page write
  [ 1012.771314] Buffer I/O error on dev nvme0n1, logical block 24, lost async 
page write

  Able to replicate this with a bonnie++ stress test.

  bonnie++ -d /mnt/test/ -r 1000

  Linux i-0d76e144d85f487cf 4.4.0-64-generic #85-Ubuntu SMP Mon Feb 20 11:50:30 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 27 02:12 seq
   crw-rw 1 root audio 116, 33 Feb 27 02:12 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  Ec2AMI: ami-bc62b2aa
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1d
  Ec2InstanceType: i3.2xlarge
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic 
root=UUID=cfda0544-9803-41e7-badb-43563085ff3a ro console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-64-generic N/A
   linux-backports-modules-4.4.0-64-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial ec2-images
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 12/12/2016
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd12/12/2016:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1667920] Re: login screen freeze

2017-02-27 Thread Alexandru Chirvasitu

Done!

The issue seems to be resolved in 4.4.52-040452-generic (boots fine, no
freeze, on it now).

** Tags added: kernel-fixed-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/1667920

Title:
  login screen freeze

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running an up-to-date (as of Feb 25 2017) 16.04 / Unity on an old MSI
  U160 netbook.

  After a recent update to kernel 4.4.0-63 I have started getting frozen
  login screens. The touchpad and keyboard are completely dead (before I
  ever get to enter my password), and my only way out is to force
  shutdown.

  I can start GRUB on boot and go for an earlier version instead, but
  everything past 4.4.0-62 freezes in the same fashion (that's what I'm
  currently running as a temporary fix); a newer update to 4.4.0-64 has
  not fixed the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-64-generic 4.4.0-64.85
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chirvasitua   1841 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Feb 25 03:42:57 2017
  HibernationDevice: RESUME=UUID=5e60245a-50f2-4f9c-97b2-d68560e38218
  InstallationDate: Installed on 2015-10-18 (495 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-N051
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=250be7ea-5182-43d2-b638-5c4a933b4942 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-62-generic N/A
   linux-backports-modules-4.4.0-62-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: EN051IMS.100
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-N051
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrEN051IMS.100:bd02/06/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-N051:pvrTobefilledbyO.E.M.:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-N051:rvrTobefilledbyO.E.M.:cvnMICRO-STARINTERNATIONALCO.,LTD:ct9:cvrToBeFilledByO.E.M.:
  dmi.product.name: MS-N051
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD

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

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

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

tests ran: 141, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-40.43-generic/gonzo__4.8.0-40.43__2017-02-27_22-24-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/1667066

Title:
  linux: 4.8.0-40.43 -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:
  Confirmed
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 Yakkety:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  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/1667066/+subscriptions

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

[Kernel-packages] [Bug 1667527] Re: [Hyper-V] pci-hyperv: Use device serial number as PCI domain

I built a test kernel using the source tree from bug 1667007.  However,
I applied commit 4a9b0933bdfcd85 on top of that tree.  The test kernel
can be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1667527/Commit4a9b0933bdfOnBug1667007Tree/

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

Title:
  [Hyper-V] pci-hyperv: Use device serial number as PCI domain

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

Bug description:
  This allows PCI domain numbers starts with 1, and also unique
  on the same VM. So names, such as VF NIC names, that include
  domain number as part of the name, can be shorter than that
  based on part of bus UUID previously. The new names will also
  stay same for VMs created with copied VHD and same number of
  devices.

  This is needed for SR-IOV in Azure.

  This is Bjorn's tree for 4.11 here:
  https://git.kernel.org/cgit/linux/kernel/git/helgaas/pci.git/commit/?h=pci
  /host-hv=4a9b0933bdfcd85da840284bf5a0eb17b654b9c2

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

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

[Kernel-packages] [Bug 1668042] Re: [Xenial - 16.04 ]Bonding driver - stack corruption when trying to copy 20 bytes to a sockaddr

I built a Xenial test kernel with a pick of commit
1533e77315220dc1d5ec3bd6d9fe32e2aa0a74c0.  The test kernel can be
downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1668042/

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

Title:
  [Xenial - 16.04 ]Bonding driver - stack corruption when trying to copy
  20 bytes to a sockaddr

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

Bug description:
  
  In Ubuntu Xenial with kernel 4.4.0-65, we get kernel Panic after scenario [1].

  patch [2] should fix the issue

  When using an IPoIB bond currently only active-backup mode is a valid
  use case and this commit strengthens it.

  Since commit 2ab82852a270 ("net/bonding: Enable bonding to enslave
  netdevices not supporting set_mac_address()") was introduced till
  4.7-rc1, IPoIB didn't support the set_mac_address ndo, and hence the
  fail over mac policy always applied to IPoIB bonds.

  With the introduction of commit 492a7e67ff83 ("IB/IPoIB: Allow setting
  the device address"), that doesn't hold and practically IPoIB bonds are
  broken as of that. To fix it, lets go to fail over mac if the device
  doesn't support the ndo OR this is IPoIB device.

  As a by-product, this commit also prevents a stack corruption which
  occurred when trying to copy 20 bytes (IPoIB) device address
  to a sockaddr struct that has only 16 bytes of storage.


  [1]
  Get panic after create bond with down/updelay and restart NIC driver
  Configure bond with down/updelay

  cat /etc/network/interfaces
  auto bond1
  iface bond1 inet static
  address 31.136.42.17
  netmask 255.255.0.0
  bond-slaves ib0 ib1
  bond-miimon 100
  bond-updelay 5000
  bond-mode active-backup
  bond-primary ib1
  bond-downdelay 5000

  auto ib0
  iface ib0 inet manual
  bond-master bond1

  auto ib1
  iface ib1 inet manual
  bond-master bond1

  modprobe -r 

  
  [2]
  1533e77315220dc1d5ec3bd6d9fe32e2aa0a74c0
  net/bonding: Enforce active-backup policy for IPoIB bonds

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

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

[Kernel-packages] [Bug 1668129] Re: Amazon I3 Instance Buffer I/O error on dev nvme0n1

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

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

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

Title:
  Amazon I3 Instance Buffer I/O error on dev nvme0n1

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

Bug description:
  On the AWS i3 instance class - when putting the new NVME storage disks
  under high IO load - seeing data corruption and errors in dmesg

  
  [  662.884390] blk_update_request: I/O error, dev nvme0n1, sector 120063912
  [  662.887824] Buffer I/O error on dev nvme0n1, logical block 14971093, lost 
async page write
  [  662.891254] Buffer I/O error on dev nvme0n1, logical block 14971094, lost 
async page write
  [  662.895591] Buffer I/O error on dev nvme0n1, logical block 14971095, lost 
async page write
  [  662.899873] Buffer I/O error on dev nvme0n1, logical block 14971096, lost 
async page write
  [  662.904179] Buffer I/O error on dev nvme0n1, logical block 14971097, lost 
async page write
  [  662.908458] Buffer I/O error on dev nvme0n1, logical block 14971098, lost 
async page write
  [  662.912287] Buffer I/O error on dev nvme0n1, logical block 14971099, lost 
async page write
  [  662.916047] Buffer I/O error on dev nvme0n1, logical block 14971100, lost 
async page write
  [  662.920285] Buffer I/O error on dev nvme0n1, logical block 14971101, lost 
async page write
  [  662.924565] Buffer I/O error on dev nvme0n1, logical block 14971102, lost 
async page write
  [  663.645530] blk_update_request: I/O error, dev nvme0n1, sector 120756912
  
  [ 1012.752265] blk_update_request: I/O error, dev nvme0n1, sector 3744
  [ 1012.755396] buffer_io_error: 194552 callbacks suppressed
  [ 1012.755398] Buffer I/O error on dev nvme0n1, logical block 20, lost async 
page write
  [ 1012.759248] Buffer I/O error on dev nvme0n1, logical block 21, lost async 
page write
  [ 1012.763368] Buffer I/O error on dev nvme0n1, logical block 22, lost async 
page write
  [ 1012.767271] Buffer I/O error on dev nvme0n1, logical block 23, lost async 
page write
  [ 1012.771314] Buffer I/O error on dev nvme0n1, logical block 24, lost async 
page write

  Able to replicate this with a bonnie++ stress test.

  bonnie++ -d /mnt/test/ -r 1000

  Linux i-0d76e144d85f487cf 4.4.0-64-generic #85-Ubuntu SMP Mon Feb 20 11:50:30 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 27 02:12 seq
   crw-rw 1 root audio 116, 33 Feb 27 02:12 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  Ec2AMI: ami-bc62b2aa
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1d
  Ec2InstanceType: i3.2xlarge
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic 
root=UUID=cfda0544-9803-41e7-badb-43563085ff3a ro console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-64-generic N/A
   linux-backports-modules-4.4.0-64-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial ec2-images
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 12/12/2016
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd12/12/2016:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

-- 
Mailing list:

[Kernel-packages] [Bug 1667920] Re: login screen freeze

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

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

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

If you are unable to test the mainline kernel, for example it will not boot, 
please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as 
"Confirmed".


Thanks in advance.

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

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

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

** Tags added: kernel-da-key

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

Title:
  login screen freeze

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Running an up-to-date (as of Feb 25 2017) 16.04 / Unity on an old MSI
  U160 netbook.

  After a recent update to kernel 4.4.0-63 I have started getting frozen
  login screens. The touchpad and keyboard are completely dead (before I
  ever get to enter my password), and my only way out is to force
  shutdown.

  I can start GRUB on boot and go for an earlier version instead, but
  everything past 4.4.0-62 freezes in the same fashion (that's what I'm
  currently running as a temporary fix); a newer update to 4.4.0-64 has
  not fixed the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-64-generic 4.4.0-64.85
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chirvasitua   1841 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Feb 25 03:42:57 2017
  HibernationDevice: RESUME=UUID=5e60245a-50f2-4f9c-97b2-d68560e38218
  InstallationDate: Installed on 2015-10-18 (495 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-N051
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=250be7ea-5182-43d2-b638-5c4a933b4942 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-62-generic N/A
   linux-backports-modules-4.4.0-62-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: EN051IMS.100
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-N051
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrEN051IMS.100:bd02/06/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-N051:pvrTobefilledbyO.E.M.:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-N051:rvrTobefilledbyO.E.M.:cvnMICRO-STARINTERNATIONALCO.,LTD:ct9:cvrToBeFilledByO.E.M.:
  dmi.product.name: MS-N051
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD

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

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

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

--- Comment From ha...@us.ibm.com 2017-02-27 17:37 EDT---
The system where we had seen most of these hangs is now running kernel 4.4.0-62 
(and corresponding aufs.ko module still based on 4.x-rcN-20160111).

NVIDIA driver has been updated to 361.119.

The system's been running the new code levels since beginning of
February, and has been running the same workload (build GPU-related
projects in docker containers) as earlier.

We have not seen any of these hangs during the last month.

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

Title:
  rcu_sched detected stalls with kernel 3.19.0-58, NVIDIA driver, and
  docker

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ---Problem Description---
  Seeing occasional rcu_sched detected stalls on 14.04 LTS with kernel 
3.19.0-58. The system is running docker containers, and has the NVIDIA GPU 
driver loaded. We've seen about 4 stalls in the last month, all with the 
3.19.0-58 kernel, and with the NVIDIA 352.93 and 361.49 drivers.

  ---uname output---
  Linux dldev1 3.19.0-58-generic #64~14.04.1-Ubuntu SMP Fri Mar 18 19:05:01 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  2 x NVIDIA K80 GPU adapter:
  $ lspci | grep NV
  0002:03:00.0 3D controller: NVIDIA Corporation GK210GL [Tesla K80] (rev a1)
  0002:04:00.0 3D controller: NVIDIA Corporation GK210GL [Tesla K80] (rev a1)
  0006:03:00.0 3D controller: NVIDIA Corporation GK210GL [Tesla K80] (rev a1)
  0006:04:00.0 3D controller: NVIDIA Corporation GK210GL [Tesla K80] (rev a1) 

   
  Machine Type = 8247-42L 
   
  ---System Hang---
   Usual symptom is that the system is unresponsive except maybe for ping and 
writing the stall-detection messages to the console. Login/getty isn't 
available either via ssh nor on the console. System must be power cycled to 
recover.
   
  Attached is the kernel log from a stall detection on May 18th. The detection 
first occurs at: May 18 15:17:55.

  The system is later rebooted and those messages indicate the kernel
  (3.19.0-58) and NVIDIA driver version (352.93) that were active at the
  time.

  We've suffered 3 or 4 stalls since, all with the same kernel, but some
  with a newer NVIDIA driver (361.49).

  Unfortunately, information about the newer stalls wasn't preserved in
  the various log files (and we're not capturing the console
  constantly), so we don't have detailed data for those.

  We'd welcome any suggestions for how to collect additional data for
  these occurrences.

  I can't say for sure that we haven't seen the stalls on other systems,
  but they're occuring fairly frequently on this system, and it's
  unusual in that it's running both Docker and NVIDIA GPU driver. So
  maybe aufs or the NVIDIA driver are somehow involved.

  From the kern.log,

  The Call trace points to some kind of deadlock in aufs -

  May 18 15:17:55 dldev1 kernel: [713670.798624] Task dump for CPU 3:
  May 18 15:17:55 dldev1 kernel: [713670.798628] cc1 R  running 
task0 99183  99173 0x00040004
  May 18 15:17:55 dldev1 kernel: [713670.798633] Call Trace:
  May 18 15:17:55 dldev1 kernel: [713670.798643] [c00fa64673a0] 
[c00cf004] wake_up_worker+0x44/0x60 (unreliable)
  May 18 15:17:55 dldev1 kernel: [713670.798671] [c00fa6467570] 
[c00fa64675d0] 0xc00fa64675d0
  May 18 15:17:55 dldev1 kernel: [713670.798676] [c00fa64675d0] 
[c0a1b050] __schedule+0x370/0x900
  May 18 15:17:55 dldev1 kernel: [713670.798679] [c00fa64677f0] 
[c00fa6467850] 0xc00fa6467850
  May 18 15:17:55 dldev1 kernel: [713670.798682] Task dump for CPU 75:
  May 18 15:17:55 dldev1 kernel: [713670.798684] cc1 D 
105d9410 0 99427  99405 0x00040004
  May 18 15:17:55 dldev1 kernel: [713670.798688] Call Trace:
  May 18 15:17:55 dldev1 kernel: [713670.798691] [c017efdd3460] 
[c017efdd34a0] 0xc017efdd34a0 (unreliable)
  May 18 15:17:55 dldev1 kernel: [713670.798695] [c017efdd3630] 
[c017efdd3690] 0xc017efdd3690
  May 18 15:17:55 dldev1 kernel: [713670.798698] [c017efdd3690] 
[c0a1b050] __schedule+0x370/0x900
  May 18 15:17:55 dldev1 kernel: [713670.798702] [c017efdd38b0] 
[c0a1f128] rwsem_down_write_failed+0x288/0x400
  May 18 15:17:55 dldev1 kernel: [713670.798706] [c017efdd3940] 
[c0a1e538] down_write+0x88/0x90
  May 18 15:17:55 dldev1 kernel: [713670.798716] [c017efdd3970] 
[d0001ead562c] do_ii_write_lock+0x8c/0xd0 [aufs]
  May 18 15:17:55 dldev1 kernel: [713670.798724] [c017efdd39a0] 
[d0001eac0e98] aufs_read_lock+0xb8/0xd0 [aufs]
  May 18 15:17:55 dldev1 kernel: [713670.798733] [c017efdd39e0] 
[d0001ead8208] aufs_d_revalidate+0x98/0x7a0 [aufs]
  May 18 15:17:55 dldev1 kernel: [713670.798737] [c017efdd3aa0] 
[c02c88f8] lookup_fast+0x368/0x3b0
  May 18 15:17:55

[Kernel-packages] [Bug 1668006] Re: Keyboard unresponsive after suspend Ubuntu 16.04 with touchscreen

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

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

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

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

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


Thanks in advance.

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

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

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

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

Title:
  Keyboard unresponsive after suspend Ubuntu 16.04 with touchscreen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 16.04 64 bit
  Toshiba Satellite P55W-C with touchscreen
  CPU: Intel® Core™ i7-5500U CPU @ 2.40GHz × 4 
  Video Card: Intel® HD Graphics 5500 (Broadwell GT2) 
  Display: 15.6” diagonal widescreen TruBrite ® TFT LCD display at 1920 x 1080
  native resolution (FHD)

  After suspend, several times the keyboard is unresponsive.

  Touchscreen remain responsive all the time so I had to suspend again
  using the touchscreen and try again until keyboard is finally
  responsive.

  Already tried with an edit to /etc/default/grub
  Changed the line
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
  to
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash atkbd.reset"

  Then run update-grub, and reboot.

  That did not fix the issue.

  I have attached the output of  ubuntu-bug linux, what other
  information is needed to fix the issue?

  What do you suggest to solve the issue?

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-64-generic 4.4.0-64.85
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arturo 2047 F pulseaudio
   /dev/snd/pcmC1D0p:   arturo 2047 F...m pulseaudio
   /dev/snd/controlC1:  arturo 2047 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Feb 25 23:23:09 2017
  HibernationDevice: RESUME=UUID=16283a3e-099e-4e71-9bb9-60cae60bfc06
  InstallationDate: Installed on 2016-05-31 (271 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: TOSHIBA Satellite P55W-C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic 
root=UUID=13ab440b-6f1e-465c-969e-b434431dce7d ro quiet splash atkbd.reset 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-64-generic N/A
   linux-backports-modules-4.4.0-64-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 5.00
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: 0692
  dmi.board.vendor: FF40
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr5.00:bd07/01/2015:svnTOSHIBA:pnSatelliteP55W-C:pvrPSPVJU-00V016:rvnFF40:rn0692:rvr2.0:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite P55W-C
  dmi.product.version: PSPVJU-00V016
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1668019] Re: [UBUNTU Zesty] mlx5 - Improve OVS offload driver

Can you submit this request to the kernel team mailing list:
kernel-t...@lists.ubuntu.com

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

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

** Also affects: linux (Ubuntu Zesty)
   Importance: Medium
   Status: Triaged

** Tags added: kernel-da-key

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

Title:
  [UBUNTU Zesty] mlx5 - Improve OVS offload driver

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

Bug description:
  The patches in this series should improve the OVS offloading driver and some 
fixes mlx5 driver, by adding reflect HW offload status for querying whether a 
filter is offloaded to HW or not.
  This patches is already accepted upstream net-next (4.11).
  The following patches should improve the OVS offload driver:

  PICK: 5cecb6c net/sched: cls_bpf: Reflect HW offload status
  PICK: 24d3dc6 net/sched: cls_u32: Reflect HW offload status
  PICK: c7d2b2f net/sched: cls_matchall: Reflect HW offloading status
  PICK: 5559396 net/sched: cls_flower: Reflect HW offload status
  PICK: e696028 net/sched: Reflect HW offload status
  PICK: 7a335ad net/sched: cls_matchall: Dump the classifier flags
  PICK: 749e672 net/sched: cls_flower: Properly handle classifier flags 
dumping
  PICK: a61d5ce net/mlx5: Fix static checker warnings
  PICK: 264d7bf net/mlx5: E-Switch, Enlarge the FDB size for the switchdev 
mode
  PICK: ce99f6b net/mlx5e: Support SRIOV TC encapsulation offloads for IPv6 
tunnels
  PICK: 9a94111 net/mlx5e: Maximize ip tunnel key usage on the TC 
offloading path
  PICK: 76f7444 net/mlx5e: Use the full tunnel key info for encapsulation 
offload house-keeping
  PICK: 75c33da net/mlx5e: TC ipv4 tunnel encap offload cosmetic changes
  PICK: 19f4440 net/mlx5e: Add TC offloads matching on IPv6 encapsulation 
headers
  PICK: 073ff3c net/mlx5: Use exact encap header size for the FW input 
buffer
  PICK: 7898489 IB/mlx5: Enable Eth VFs to query their min-inline value for 
user-space
  PICK: 8c7245a6 net/mlx5: Push min-inline mode resolution helper into the 
core
  PICK: a3308d8 net/sched: cls_flower: Disallow duplicate internal elements

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

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

[Kernel-packages] [Bug 1668031] Re: Network adapter keeps on hanging up

Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?

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

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

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

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

Thanks in advance.

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

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

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

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

Title:
Network adapter keeps on hanging up

Status in linux package in Ubuntu:
Incomplete

Bug description:
Every hour or so, I'm unable to access the internet through this
laptop. dmesg usually reports errors related to the network adapter,
but not always. Disconnecting from the current Wifi network and
connecting to another, usually works. Immediately connecting to the
original network after that does not cause the problem to reoccur. At
least, not for another hour or so.

I'm not sure how to better describe this bug.

The network also provides a nfs drive that is mounted on the laptop,
if that is significant.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-39-generic 4.8.0-39.42
ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17
Uname: Linux 4.8.0-39-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ruud 2810 F pulseaudio
CurrentDesktop: Unity
Date: Sun Feb 26 02:13:55 2017
HibernationDevice: RESUME=UUID=2f2d2c45-4fef-49ec-932a-8314b15c2f6b
InstallationDate: Installed on 2016-11-08 (109 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: Dell Inc. XPS 13 9360
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-39-generic.efi.signed
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.8.0-39-generic N/A
linux-backports-modules-4.8.0-39-generic N/A
linux-firmware1.162
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/18/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.2
dmi.board.name: 0T3FTF
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9360
dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1667527] Re: [Hyper-V] pci-hyperv: Use device serial number as PCI domain

Same kernel crash issue found on the v2 kernel (Comment #5).

This is the known good kernel: 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667007
Could you please apply the patch of this bug to that 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/1667527

Title:
  [Hyper-V] pci-hyperv: Use device serial number as PCI domain

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

Bug description:
  This allows PCI domain numbers starts with 1, and also unique
  on the same VM. So names, such as VF NIC names, that include
  domain number as part of the name, can be shorter than that
  based on part of bus UUID previously. The new names will also
  stay same for VMs created with copied VHD and same number of
  devices.

  This is needed for SR-IOV in Azure.

  This is Bjorn's tree for 4.11 here:
  https://git.kernel.org/cgit/linux/kernel/git/helgaas/pci.git/commit/?h=pci
  /host-hv=4a9b0933bdfcd85da840284bf5a0eb17b654b9c2

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

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

[Kernel-packages] [Bug 1668129] Re: Amazon I3 Instance Buffer I/O error on dev nvme0n1

2017-02-27 Thread Anne-Marie

(This was in eu-west-1, with ami-405f7226)

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

Title:
  Amazon I3 Instance Buffer I/O error on dev nvme0n1

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

Bug description:
  On the AWS i3 instance class - when putting the new NVME storage disks
  under high IO load - seeing data corruption and errors in dmesg

  
  [  662.884390] blk_update_request: I/O error, dev nvme0n1, sector 120063912
  [  662.887824] Buffer I/O error on dev nvme0n1, logical block 14971093, lost 
async page write
  [  662.891254] Buffer I/O error on dev nvme0n1, logical block 14971094, lost 
async page write
  [  662.895591] Buffer I/O error on dev nvme0n1, logical block 14971095, lost 
async page write
  [  662.899873] Buffer I/O error on dev nvme0n1, logical block 14971096, lost 
async page write
  [  662.904179] Buffer I/O error on dev nvme0n1, logical block 14971097, lost 
async page write
  [  662.908458] Buffer I/O error on dev nvme0n1, logical block 14971098, lost 
async page write
  [  662.912287] Buffer I/O error on dev nvme0n1, logical block 14971099, lost 
async page write
  [  662.916047] Buffer I/O error on dev nvme0n1, logical block 14971100, lost 
async page write
  [  662.920285] Buffer I/O error on dev nvme0n1, logical block 14971101, lost 
async page write
  [  662.924565] Buffer I/O error on dev nvme0n1, logical block 14971102, lost 
async page write
  [  663.645530] blk_update_request: I/O error, dev nvme0n1, sector 120756912
  
  [ 1012.752265] blk_update_request: I/O error, dev nvme0n1, sector 3744
  [ 1012.755396] buffer_io_error: 194552 callbacks suppressed
  [ 1012.755398] Buffer I/O error on dev nvme0n1, logical block 20, lost async 
page write
  [ 1012.759248] Buffer I/O error on dev nvme0n1, logical block 21, lost async 
page write
  [ 1012.763368] Buffer I/O error on dev nvme0n1, logical block 22, lost async 
page write
  [ 1012.767271] Buffer I/O error on dev nvme0n1, logical block 23, lost async 
page write
  [ 1012.771314] Buffer I/O error on dev nvme0n1, logical block 24, lost async 
page write

  Able to replicate this with a bonnie++ stress test.

  bonnie++ -d /mnt/test/ -r 1000

  Linux i-0d76e144d85f487cf 4.4.0-64-generic #85-Ubuntu SMP Mon Feb 20 11:50:30 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 27 02:12 seq
   crw-rw 1 root audio 116, 33 Feb 27 02:12 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  Ec2AMI: ami-bc62b2aa
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1d
  Ec2InstanceType: i3.2xlarge
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic 
root=UUID=cfda0544-9803-41e7-badb-43563085ff3a ro console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-64-generic N/A
   linux-backports-modules-4.4.0-64-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial ec2-images
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 12/12/2016
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd12/12/2016:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

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

[Kernel-packages] [Bug 1668042] Re: [Xenial - 16.04 ]Bonding driver - stack corruption when trying to copy 20 bytes to a sockaddr

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

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

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

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

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

Title:
  [Xenial - 16.04 ]Bonding driver - stack corruption when trying to copy
  20 bytes to a sockaddr

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

Bug description:
  
  In Ubuntu Xenial with kernel 4.4.0-65, we get kernel Panic after scenario [1].

  patch [2] should fix the issue

  When using an IPoIB bond currently only active-backup mode is a valid
  use case and this commit strengthens it.

  Since commit 2ab82852a270 ("net/bonding: Enable bonding to enslave
  netdevices not supporting set_mac_address()") was introduced till
  4.7-rc1, IPoIB didn't support the set_mac_address ndo, and hence the
  fail over mac policy always applied to IPoIB bonds.

  With the introduction of commit 492a7e67ff83 ("IB/IPoIB: Allow setting
  the device address"), that doesn't hold and practically IPoIB bonds are
  broken as of that. To fix it, lets go to fail over mac if the device
  doesn't support the ndo OR this is IPoIB device.

  As a by-product, this commit also prevents a stack corruption which
  occurred when trying to copy 20 bytes (IPoIB) device address
  to a sockaddr struct that has only 16 bytes of storage.


  [1]
  Get panic after create bond with down/updelay and restart NIC driver
  Configure bond with down/updelay

  cat /etc/network/interfaces
  auto bond1
  iface bond1 inet static
  address 31.136.42.17
  netmask 255.255.0.0
  bond-slaves ib0 ib1
  bond-miimon 100
  bond-updelay 5000
  bond-mode active-backup
  bond-primary ib1
  bond-downdelay 5000

  auto ib0
  iface ib0 inet manual
  bond-master bond1

  auto ib1
  iface ib1 inet manual
  bond-master bond1

  modprobe -r 

  
  [2]
  1533e77315220dc1d5ec3bd6d9fe32e2aa0a74c0
  net/bonding: Enforce active-backup policy for IPoIB bonds

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

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

[Kernel-packages] [Bug 1668129] Re: Amazon I3 Instance Buffer I/O error on dev nvme0n1

2017-02-27 Thread Anne-Marie

I find it is easy to reproduce by using "dd if=/dev/zero of=big bs=4096"
-- I generally get errors within a few minutes.

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

Title:
  Amazon I3 Instance Buffer I/O error on dev nvme0n1

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

Bug description:
  On the AWS i3 instance class - when putting the new NVME storage disks
  under high IO load - seeing data corruption and errors in dmesg

  
  [  662.884390] blk_update_request: I/O error, dev nvme0n1, sector 120063912
  [  662.887824] Buffer I/O error on dev nvme0n1, logical block 14971093, lost 
async page write
  [  662.891254] Buffer I/O error on dev nvme0n1, logical block 14971094, lost 
async page write
  [  662.895591] Buffer I/O error on dev nvme0n1, logical block 14971095, lost 
async page write
  [  662.899873] Buffer I/O error on dev nvme0n1, logical block 14971096, lost 
async page write
  [  662.904179] Buffer I/O error on dev nvme0n1, logical block 14971097, lost 
async page write
  [  662.908458] Buffer I/O error on dev nvme0n1, logical block 14971098, lost 
async page write
  [  662.912287] Buffer I/O error on dev nvme0n1, logical block 14971099, lost 
async page write
  [  662.916047] Buffer I/O error on dev nvme0n1, logical block 14971100, lost 
async page write
  [  662.920285] Buffer I/O error on dev nvme0n1, logical block 14971101, lost 
async page write
  [  662.924565] Buffer I/O error on dev nvme0n1, logical block 14971102, lost 
async page write
  [  663.645530] blk_update_request: I/O error, dev nvme0n1, sector 120756912
  
  [ 1012.752265] blk_update_request: I/O error, dev nvme0n1, sector 3744
  [ 1012.755396] buffer_io_error: 194552 callbacks suppressed
  [ 1012.755398] Buffer I/O error on dev nvme0n1, logical block 20, lost async 
page write
  [ 1012.759248] Buffer I/O error on dev nvme0n1, logical block 21, lost async 
page write
  [ 1012.763368] Buffer I/O error on dev nvme0n1, logical block 22, lost async 
page write
  [ 1012.767271] Buffer I/O error on dev nvme0n1, logical block 23, lost async 
page write
  [ 1012.771314] Buffer I/O error on dev nvme0n1, logical block 24, lost async 
page write

  Able to replicate this with a bonnie++ stress test.

  bonnie++ -d /mnt/test/ -r 1000

  Linux i-0d76e144d85f487cf 4.4.0-64-generic #85-Ubuntu SMP Mon Feb 20 11:50:30 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 27 02:12 seq
   crw-rw 1 root audio 116, 33 Feb 27 02:12 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  Ec2AMI: ami-bc62b2aa
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1d
  Ec2InstanceType: i3.2xlarge
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic 
root=UUID=cfda0544-9803-41e7-badb-43563085ff3a ro console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-64-generic N/A
   linux-backports-modules-4.4.0-64-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial ec2-images
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 12/12/2016
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd12/12/2016:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

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

[Kernel-packages] [Bug 1668097] Re: On func nf_log_proc_dostring issue.

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

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

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

Title:
  On func nf_log_proc_dostring issue.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Removing suppress errors message from my kernel.
  Run make
  Bellow is errors :
CC  net/netfilter/nf_log.o
  net/netfilter/nf_log.c: In function ‘nf_log_proc_dostring’:
  net/netfilter/nf_log.c:406:36: error: dereferencing pointer to incomplete 
type ‘struct nsproxy’
struct net *net = current->nsproxy->net_ns;
  ^
  scripts/Makefile.build:291: recipe for target 'net/netfilter/nf_log.o' failed
  make[2]: *** [net/netfilter/nf_log.o] Error 1
  scripts/Makefile.build:440: recipe for target 'net/netfilter' failed
  make[1]: *** [net/netfilter] Error 2
  Makefile:963: recipe for target 'net' failed
  make: *** [net] Error 2

  ProblemType: Bug
  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/controlC0:  asu2795 F mate-settings-d
asu2865 F mate-volume-con
  CurrentDesktop: MATE
  Date: Sun Feb 26 22:11:33 2017
  InstallationDate: Installed on 2016-04-29 (303 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
   
   enp2s4no wireless extensions.
  MachineType: Olidata S.p.A. ALABAMA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-62-generic 
root=/dev/mapper/192--168--0--108--vg-root ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-62-generic N/A
   linux-backports-modules-4.4.0-62-generic  N/A
   linux-firmware1.157.8
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/08/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: S0101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrS0101:bd07/08/2008:svnOlidataS.p.A.:pnALABAMA:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: ALABAMA
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: Olidata S.p.A.

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

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

[Kernel-packages] [Bug 1668105] Re: xhci_kcd module turns off usb host controller on boot

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

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

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

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


Thanks in advance.

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

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

** Tags added: kernel-da-key

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

Title:
  xhci_kcd module turns off usb host controller on boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  So we know this xhci_kcd was always shit in that it turns off the
  console usb keyboard for long running computers and that it on abrupt
  termination of Linux puts usb in a 12x slower mode. It is buggy, it
  was always buggy, and its getting worse.

  With Linux 4.8.0-37, this crappy software decides to halt the host
  controller on boot, ie. turn off the console keyboard preventing any
  boot. I cannot think of any situation where anyone would want their
  host controller halted.

  This is MacBook Pro 2015. So, it's already broken in UEFI-grub as it
  always was, ie. every key press takes 8 seconds, but you only need
  two, so you can boot in 16 s.

  I tried to disable the xhci_kcd crap by using kernel parameter
  noxhci_port_switch or modprobe.blacklist=xhci_hcd neither which works.

  Because it has crap in UEFI, the computer will not boot any external
  hard drive or usb fob. The only thing that works is Apple rescue that
  gets rid of the xhci garbage, and the boot os x immediately after
  that.

  So the log output
  xhci_hcd :00:14.0: Timeout while waiting for setup device command
  xhci_hcd :00:14.0: xHCI host not responding to stop endpoint command.
  - and a bit later:
  xhci_hcd :00:14.0: Assuming host is dying, halting host.
  xhci_hcd :00:14.0: HC died; cleaning up

  This clown programming of Linux has to stop. Why would anyone ever
  want their host controller halted?

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

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

[Kernel-packages] [Bug 1668042] Re: [Xenial - 16.04 ]Bonding driver - stack corruption when trying to copy 20 bytes to a sockaddr

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

** Tags added: kernel-da-key

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

Title:
  [Xenial - 16.04 ]Bonding driver - stack corruption when trying to copy
  20 bytes to a sockaddr

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  In Ubuntu Xenial with kernel 4.4.0-65, we get kernel Panic after scenario [1].

  patch [2] should fix the issue

  When using an IPoIB bond currently only active-backup mode is a valid
  use case and this commit strengthens it.

  Since commit 2ab82852a270 ("net/bonding: Enable bonding to enslave
  netdevices not supporting set_mac_address()") was introduced till
  4.7-rc1, IPoIB didn't support the set_mac_address ndo, and hence the
  fail over mac policy always applied to IPoIB bonds.

  With the introduction of commit 492a7e67ff83 ("IB/IPoIB: Allow setting
  the device address"), that doesn't hold and practically IPoIB bonds are
  broken as of that. To fix it, lets go to fail over mac if the device
  doesn't support the ndo OR this is IPoIB device.

  As a by-product, this commit also prevents a stack corruption which
  occurred when trying to copy 20 bytes (IPoIB) device address
  to a sockaddr struct that has only 16 bytes of storage.


  [1]
  Get panic after create bond with down/updelay and restart NIC driver
  Configure bond with down/updelay

  cat /etc/network/interfaces
  auto bond1
  iface bond1 inet static
  address 31.136.42.17
  netmask 255.255.0.0
  bond-slaves ib0 ib1
  bond-miimon 100
  bond-updelay 5000
  bond-mode active-backup
  bond-primary ib1
  bond-downdelay 5000

  auto ib0
  iface ib0 inet manual
  bond-master bond1

  auto ib1
  iface ib1 inet manual
  bond-master bond1

  modprobe -r 

  
  [2]
  1533e77315220dc1d5ec3bd6d9fe32e2aa0a74c0
  net/bonding: Enforce active-backup policy for IPoIB bonds

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

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

[Kernel-packages] [Bug 1668129] Re: Amazon I3 Instance Buffer I/O error on dev nvme0n1

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

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

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

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

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

** Tags added: kernel-key

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

Title:
  Amazon I3 Instance Buffer I/O error on dev nvme0n1

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

Bug description:
  On the AWS i3 instance class - when putting the new NVME storage disks
  under high IO load - seeing data corruption and errors in dmesg

  
  [  662.884390] blk_update_request: I/O error, dev nvme0n1, sector 120063912
  [  662.887824] Buffer I/O error on dev nvme0n1, logical block 14971093, lost 
async page write
  [  662.891254] Buffer I/O error on dev nvme0n1, logical block 14971094, lost 
async page write
  [  662.895591] Buffer I/O error on dev nvme0n1, logical block 14971095, lost 
async page write
  [  662.899873] Buffer I/O error on dev nvme0n1, logical block 14971096, lost 
async page write
  [  662.904179] Buffer I/O error on dev nvme0n1, logical block 14971097, lost 
async page write
  [  662.908458] Buffer I/O error on dev nvme0n1, logical block 14971098, lost 
async page write
  [  662.912287] Buffer I/O error on dev nvme0n1, logical block 14971099, lost 
async page write
  [  662.916047] Buffer I/O error on dev nvme0n1, logical block 14971100, lost 
async page write
  [  662.920285] Buffer I/O error on dev nvme0n1, logical block 14971101, lost 
async page write
  [  662.924565] Buffer I/O error on dev nvme0n1, logical block 14971102, lost 
async page write
  [  663.645530] blk_update_request: I/O error, dev nvme0n1, sector 120756912
  
  [ 1012.752265] blk_update_request: I/O error, dev nvme0n1, sector 3744
  [ 1012.755396] buffer_io_error: 194552 callbacks suppressed
  [ 1012.755398] Buffer I/O error on dev nvme0n1, logical block 20, lost async 
page write
  [ 1012.759248] Buffer I/O error on dev nvme0n1, logical block 21, lost async 
page write
  [ 1012.763368] Buffer I/O error on dev nvme0n1, logical block 22, lost async 
page write
  [ 1012.767271] Buffer I/O error on dev nvme0n1, logical block 23, lost async 
page write
  [ 1012.771314] Buffer I/O error on dev nvme0n1, logical block 24, lost async 
page write

  Able to replicate this with a bonnie++ stress test.

  bonnie++ -d /mnt/test/ -r 1000

  Linux i-0d76e144d85f487cf 4.4.0-64-generic #85-Ubuntu SMP Mon Feb 20 11:50:30 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 27 02:12 seq
   crw-rw 1 root audio 116, 33 Feb 27 02:12 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  Ec2AMI: ami-bc62b2aa
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1d
  Ec2InstanceType: i3.2xlarge
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic 
root=UUID=cfda0544-9803-41e7-badb-43563085ff3a ro console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-64-generic N/A
   linux-backports-modules-4.4.0-64-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial ec2-images
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 12/12/2016
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd12/12/2016:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:

[Kernel-packages] [Bug 1668230] Re: CIFS module =>2.06 shipped with Xenial cannot stat files.

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

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

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

If you are unable to test the mainline kernel, for example it will not boot, 
please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as 
"Confirmed".


Thanks in advance.

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

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

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

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

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

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

Title:
  CIFS module =>2.06 shipped with Xenial cannot stat files.

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

Bug description:
  This seems to be a kernel bug affecting cifs modules => 2.06.

  This might be fixed by the upstream kernel provider but I need it
  fixed in the specific kernel version that Ubuntu ships.

  root@miguel-test2:~/cifs-bug-xenial# mount -t cifs //157.249.168.181/storeB 
/mnt/ -o ro,guest
  root@miguel-test2:~/cifs-bug-xenial# ls -l 
/mnt/immutable/short-term-archive/DNMI_VARSLER/2017/02/22/vn/
  ls: 
'/mnt/immutable/short-term-archive/DNMI_VARSLER/2017/02/22/vn/VN_minQNH_ZONE_BCD-2017-02-22-06:00:00-EN.txt':
 No such file or directory
  ls: 
'/mnt/immutable/short-term-archive/DNMI_VARSLER/2017/02/22/vn/NRKMIDNATT_V-2017-02-22-23:00:00-NB.txt':
 No such file or directory
  ls: 
'/mnt/immutable/short-term-archive/DNMI_VARSLER/2017/02/22/vn/VVkyst0-1-2017-02-22-12:00:00-EN.txt':
 No such file or directory
  ls: 
'/mnt/immutable/short-term-archive/DNMI_VARSLER/2017/02/22/vn/ENHF-ENBJ-2017-02-23-00:00:00-EN.txt':
 No such file or directory
  ls: 
'/mnt/immutable/short-term-archive/DNMI_VARSLER/2017/02/22/vn/VNkyst0-1-2017-02-22-12:00:00-NB.txt':
 No such file or directory
  ls: 
'/mnt/immutable/short-term-archive/DNMI_VARSLER/2017/02/22/vn/VNkystobs-2017-02-22-12:00:00-NB.txt':
 No such file or directory
  ls: 
'/mnt/immutable/short-term-archive/DNMI_VARSLER/2017/02/22/vn/VNfisk-2017-02-22-12:00:00-NB.txt':
 No such file or directory
  ls: 
'/mnt/immutable/short-term-archive/DNMI_VARSLER/2017/02/22/vn/VN_Obsvarsel_kansellering-2017-02-22-07:27:04-NB.txt':
 No such file or directory
  ls: 
'/mnt/immutable/short-term-archive/DNMI_VARSLER/2017/02/22/vn/VNkystobs-2017-02-22-18:00:00-NB.txt':
 No such file or directory
  ls: 
'/mnt/immutable/short-term-archive/DNMI_VARSLER/2017/02/22/vn/VNhav-2017-02-22-10:00:00-NB.txt':
 No such file or directory
  ls: 
'/mnt/immutable/short-term-archive/DNMI_VARSLER/2017/02/22/vn/METoversikt0-2017-02-22-12:00:00-NB.txt':
 No such file or directory
  ls: 
'/mnt/immutable/short-term-archive/DNMI_VARSLER/2017/02/22/vn/VNhav-2017-02-22-22:00:00-NB.txt':
 No such file or directory
  ls: 
'/mnt/immutable/short-term-archive/DNMI_VARSLER/2017/02/22/vn/VNkyst0-2017-02-22-09:00:00-NB.txt':
 No such file or directory
  ls: 
'/mnt/immutable/short-term-archive/DNMI_VARSLER/2017/02/22/vn/VNfisk-2017-02-22-22:00:00-NB.txt':
 No such file or directory
  ls: 
'/mnt/immutable/short-term-archive/DNMI_VARSLER/2017/02/22/vn/VNiga-2017-02-22-06:00:00-EN.txt':
 No such file or directory
  ls: 
'/mnt/immutable/short-term-archive/DNMI_VARSLER/2017/02/22/vn/VNhoydevind_ENNA-2017-02-22-04:00:00-EN.txt':
 No such file or directory
  ls: 
'/mnt/immutable/short-term-archive/DNMI_VARSLER/2017/02/22/vn/ENHF-ENBJ-2017-02-22-12:00:00-EN.txt':
 No such file or directory
  ls: 
'/mnt/immutable/short-term-archive/DNMI_VARSLER/2017/02/22/vn/VVkyst0-1-2017-02-22-18:00:00-NB.txt':
 No such file or directory
  ls: 
'/mnt/immutable/short-term-archive/DNMI_VARSLER/2017/02/22/vn/VNiga-2017-02-22-13:00:00-EN.txt':
 No such file or directory
  ls: 
'/mnt/immutable/short-term-archive/DNMI_VARSLER/2017/02/22/vn/VVkyst0-1-2017-02-22-18:00:00-EN.txt':
 No such file or directory
  ls: 
'/mnt/immutable/short-term-archive/DNMI_VARSLER/2017/02/22/vn/METoversikt1-2017-02-22-18:00:00-NB.txt':
 No such file or directory
  ls: 
'/mnt/immutable/short-term-archive/DNMI_VARSLER/2017/02/22/vn/Sigmet_E-2017-02-22-03:45:40-EN.txt':
 No such file or directory
  ls: 
'/mnt/immutable/short-term-archive/DNMI_VARSLER/2017/02/22/vn/METoversikt0-2017-02-23-00:00:00-NB.txt':
 No such file or directory
  ls:

[Kernel-packages] [Bug 1652499] Re: Cannot hibernate properly ; systemd-sleep hangs

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

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

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

If you are unable to test the mainline kernel, for example it will not boot,
please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".

Thanks in advance.

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

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

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

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

Title:
Cannot hibernate properly ; systemd-sleep hangs

Status in linux package in Ubuntu:
Incomplete

Bug description:
Hello,
on recent kernels including 4.4.0-57-generic, I observe more often than not
the following behaviour after clicking the Hibernate button in XFCE4 interface :

1. Screen becomes black
2. No hard drive activity, which is suspicious
3. Moving the mouse shows the "locked screen" lightdm prompt
4. Unlocking the session, I get back to it ; things seems to work as usual
except the ethernet connection is down
5. ps aux | grep hib shows that there is a /lib/systemd/systemd-sleep
hibernate running
6. if I kill this process, the computer finally hibernates
7. booting the computer again resumes the session (with networking enabled)
but with persistent graphical glitches on some parts of the interface, most
visibly
a. in my terminal, all occurrences of the letter b are scrambled
b. in all windows, the maximise/minimise/close buttons are scrambled.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: systemd 229-4ubuntu13
ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
Uname: Linux 4.4.0-57-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun Dec 25 10:36:33 2016
InstallationDate: Installed on 2016-09-07 (108 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
MachineType: Dell Inc. Precision Tower 3620
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic.efi.signed
root=UUID=6ebb7e70-29f5-4ddf-a1a1-8cc58113961a ro
SourcePackage: systemd
SystemdDelta:
[EXTENDED] /lib/systemd/system/rc-local.service →
/lib/systemd/system/rc-local.service.d/debian.conf
[EXTENDED] /lib/systemd/system/systemd-timesyncd.service →
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf

2 overridden configuration files found.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/26/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.6
dmi.board.name: 09WH54
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.3.6:bd05/26/2016:svnDellInc.:pnPrecisionTower3620:pvr:rvnDellInc.:rn09WH54:rvrA00:cvnDellInc.:ct6:cvr:
dmi.product.name: Precision Tower 3620
dmi.sys.vendor: Dell Inc.

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

[Kernel-packages] [Bug 1668135] Re: Bluetooth is not working pls help~

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

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

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

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

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


Thanks in advance.

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

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

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

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

Title:
  Bluetooth is not working pls help~

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  dell@dell-Vostro-1320:~$ sudo cat /sys/kernel/debug/usb/devices

  T:  Bus=08 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12   MxCh= 2
  B:  Alloc=  4/900 us ( 0%), #Int=  3, #Iso=  0
  D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
  P:  Vendor=1d6b ProdID=0001 Rev= 4.04
  S:  Manufacturer=Linux 4.4.0-62-generic uhci_hcd
  S:  Product=UHCI Host Controller
  S:  SerialNumber=:00:1d.2
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   2 Ivl=255ms

  T:  Bus=08 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=12   MxCh= 3
  D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
  P:  Vendor=0a5c ProdID=4500 Rev= 1.00
  S:  Manufacturer=Broadcom
  S:  Product=BCM2045B2
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   1 Ivl=255ms

  T:  Bus=08 Lev=02 Prnt=02 Port=01 Cnt=01 Dev#=  3 Spd=12   MxCh= 0
  D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
  P:  Vendor=0a5c ProdID=4502 Rev= 1.00
  S:  Manufacturer=Broadcom Corp
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=01 Driver=usbhid
  E:  Ad=81(I) Atr=03(Int.) MxPS=   8 Ivl=10ms

  T:  Bus=08 Lev=02 Prnt=02 Port=02 Cnt=02 Dev#=  4 Spd=12   MxCh= 0
  D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
  P:  Vendor=0a5c ProdID=4503 Rev= 1.00
  S:  Manufacturer=Broadcom Corp
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=02 Driver=usbhid
  E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=10ms

  T:  Bus=07 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12   MxCh= 2
  B:  Alloc=  0/900 us ( 0%), #Int=  0, #Iso=  0
  D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
  P:  Vendor=1d6b ProdID=0001 Rev= 4.04
  S:  Manufacturer=Linux 4.4.0-62-generic uhci_hcd
  S:  Product=UHCI Host Controller
  S:  SerialNumber=:00:1d.1
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   2 Ivl=255ms

  T:  Bus=06 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12   MxCh= 2
  B:  Alloc= 11/900 us ( 1%), #Int=  1, #Iso=  0
  D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
  P:  Vendor=1d6b ProdID=0001 Rev= 4.04
  S:  Manufacturer=Linux 4.4.0-62-generic uhci_hcd
  S:  Product=UHCI Host Controller
  S:  SerialNumber=:00:1d.0
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   2 Ivl=255ms

  T:  Bus=06 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=1.5  MxCh= 0
  D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
  P:  Vendor=413c ProdID=3200 Rev= 1.10
  S:  Manufacturer=Dell
  S:  Product=Dell USB Mouse
  C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=02 Driver=usbhid
  E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=10ms

  T:  Bus=05 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12   MxCh= 2
  B:  Alloc=  0/900 us ( 0%), #Int=  0, #Iso=  0
  D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
  P:  Vendor=1d6b ProdID=0001 Rev= 4.04
  S:  Manufacturer=Linux 4.4.0-62-generic uhci_hcd
  S:  Product=UHCI Host Controller
  S:  SerialNumber=:00:1a.2
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   2 Ivl=255ms

  T:  Bus=04 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12   MxCh= 2
  B:  Alloc=  0/900 us ( 0%), #Int=  0, #Iso=  0
  D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
  P:  Vendor=1d6b ProdID=0001 Rev= 4.04
  S:  Manufacturer=Linux 4.4.0-62-generic uhci_hcd
  S:  Product=UHCI Host Controller
  S:  SerialNumber=:00:1a.1
  C:* #Ifs= 1 Cfg#= 1 Atr=e0

[Kernel-packages] [Bug 1668117] Re: package linux-image-4.4.0-64-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

You may need to run the following from a terminal:

sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

Then re-install the package or updates.

If that does not resolve your issue, please mark the bug as "Confirmed"

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

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

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

Title:
  package linux-image-4.4.0-64-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 1

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  problem during new installation on to acer laptop 1680

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-64-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  Date: Mon Feb 27 00:37:08 2017
  DuplicateSignature:
   package:linux-image-4.4.0-64-generic:(not installed)
   Preparing to unpack .../linux-image-4.4.0-64-generic_4.4.0-64.85_i386.deb ...
   This kernel does not support a non-PAE CPU.
   dpkg: error processing archive 
/var/cache/apt/archives/linux-image-4.4.0-64-generic_4.4.0-64.85_i386.deb 
(--unpack):
subprocess new pre-installation script returned error exit status 1
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  InstallationDate: Installed on 2017-02-27 (0 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 002: ID 09da:0006 A4Tech Co., Ltd. Optical Mouse WOP-35 / 
Trust 450L Optical 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
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=59a28bc6-2c9c-42d6-9a25-ff532e490f14 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: linux
  Title: package linux-image-4.4.0-64-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.board.name: Aspire 1680
  dmi.product.name: Aspire 1680
  dmi.product.version: Rev 1

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

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

[Kernel-packages] [Bug 1566302] Re: Ubuntu 16.04: Suspend freezes the system after upgrade to linux image 4.4.0-16

2017-02-27 Thread Manuel

Solved by disabling the xCHI usb 3.0 on the bios. adding parameters to
Grub didn´t.

Now Freezes does not happen after suspend, hibernate, close the lip or
turning off.

It takes a decent amount of time to turn off and the screen flash in
different shades of black when booting though. would be nice to see this
solved.

Hope it helps and that this is the proper place to share this.

I had the same problem here on Acer Aspire E15.

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

Title:
  Ubuntu 16.04: Suspend freezes the system after upgrade to linux image
  4.4.0-16

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  I'm using ubuntu 16.04 on a XPS 15 9550.

  Suspend/resume worked flawlessly with linux image 4.4.0-15, and after
  standard upgrade yesterday (5/04/2016) which installed image 4.4.0-16,
  the system freezes when attempting a suspend. I get  no response from
  the system (nor keyboard, nor screen, nor touchpad), but it gets very
  hot, so that it must be running something.

  Booting with 4.4.0-15 makes the suspend to work perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-16-generic 4.4.0-16.32
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  macias 1770 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Tue Apr  5 14:56:17 2016
  HibernationDevice: RESUME=UUID=4180adfa-3852-4a96-86b4-f3696448c743
  InstallationDate: Installed on 2016-03-07 (28 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. 
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcEnviron:
   LANGUAGE=es_ES
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed 
root=UUID=673f4658-75f8-4c01-bcd8-0af860269699 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.01.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.01.19:bd01/25/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/1566302/+subscriptions

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

[Kernel-packages] [Bug 1668356] Re: Hard lockup after 4 hours uptime

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

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

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

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


Thanks in advance.

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

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

Title:
  Hard lockup after 4 hours uptime

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

Bug description:
  We have recently deployed intel NUC6i5 devices in store for POS
  display and are encountering strange inexplicable freezes on several
  devices.

  What is very strange is that all devices are freezing exactly 4h after
  boot.

  We have had this exact same issue on more than 20 devices (over 100),
  with parts from different batches, and all did freeze exactly 4h after
  boot (but it's not reproducible, it won't freeze every day). Some
  devices are playing MPV videos, while other run chromium. They are
  running non-stop, but are all rebooting daily at 05h05.

  Looks like it might be related to https://lkml.org/lkml/2015/6/11/787

  That seem to have been fixed and backported already
  https://lkml.org/lkml/2015/10/17/259

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-64-generic 4.4.0-64.85
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Mon Feb 27 21:06:44 2017
  InstallationDate: Installed on 2016-06-08 (264 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 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=1f60f9c9-bbf1-45df-bdc3-9b4da883839e ro quiet splash net.ifnames=0 
vt.handoff=7
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.board.name: NUC6i5SYB

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

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

[Kernel-packages] [Bug 1668356] Re: Hard lockup after 4 hours uptime

The lkml tread you referenced in the bug description was for commit
37b12910dd11d9ab969f2c310dc9160b7f3e3405.  That commit landed upstream
in v4.3.rc1, so it is already in the 4.4 based Xenial kernel.

Did this issue start happening after a recent upgrade, or after applying
updates?

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

Title:
  Hard lockup after 4 hours uptime

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

Bug description:
  We have recently deployed intel NUC6i5 devices in store for POS
  display and are encountering strange inexplicable freezes on several
  devices.

  What is very strange is that all devices are freezing exactly 4h after
  boot.

  We have had this exact same issue on more than 20 devices (over 100),
  with parts from different batches, and all did freeze exactly 4h after
  boot (but it's not reproducible, it won't freeze every day). Some
  devices are playing MPV videos, while other run chromium. They are
  running non-stop, but are all rebooting daily at 05h05.

  Looks like it might be related to https://lkml.org/lkml/2015/6/11/787

  That seem to have been fixed and backported already
  https://lkml.org/lkml/2015/10/17/259

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-64-generic 4.4.0-64.85
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Mon Feb 27 21:06:44 2017
  InstallationDate: Installed on 2016-06-08 (264 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 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=1f60f9c9-bbf1-45df-bdc3-9b4da883839e ro quiet splash net.ifnames=0 
vt.handoff=7
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.board.name: NUC6i5SYB

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

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

[Kernel-packages] [Bug 1668356] Re: Hard lockup after 4 hours uptime

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

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

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

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

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

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

** Tags added: kernel-da-key

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

Title:
  Hard lockup after 4 hours uptime

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

Bug description:
  We have recently deployed intel NUC6i5 devices in store for POS
  display and are encountering strange inexplicable freezes on several
  devices.

  What is very strange is that all devices are freezing exactly 4h after
  boot.

  We have had this exact same issue on more than 20 devices (over 100),
  with parts from different batches, and all did freeze exactly 4h after
  boot (but it's not reproducible, it won't freeze every day). Some
  devices are playing MPV videos, while other run chromium. They are
  running non-stop, but are all rebooting daily at 05h05.

  Looks like it might be related to https://lkml.org/lkml/2015/6/11/787

  That seem to have been fixed and backported already
  https://lkml.org/lkml/2015/10/17/259

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-64-generic 4.4.0-64.85
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Mon Feb 27 21:06:44 2017
  InstallationDate: Installed on 2016-06-08 (264 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 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=1f60f9c9-bbf1-45df-bdc3-9b4da883839e ro quiet splash net.ifnames=0 
vt.handoff=7
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.board.name: NUC6i5SYB

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

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

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

tests ran:   6, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-40.43-generic/gonzo__4.8.0-40.43__2017-02-27_21-11-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/1667066

Title:
  linux: 4.8.0-40.43 -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:
  Confirmed
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 Yakkety:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  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/1667066/+subscriptions

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

[Kernel-packages] [Bug 1668129] Re: Amazon I3 Instance Buffer I/O error on dev nvme0n1

2017-02-27 Thread Matt Billenstein

I don't know that I do -- I'm finding these errors when rsync'ing a
larger database from another machine.

I'm using ubuntu/images/hvm-ssd/ubuntu-
xenial-16.04-amd64-server-20170221 (ami-a58d0dc5)

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

Title:
  Amazon I3 Instance Buffer I/O error on dev nvme0n1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On the AWS i3 instance class - when putting the new NVME storage disks
  under high IO load - seeing data corruption and errors in dmesg

  
  [  662.884390] blk_update_request: I/O error, dev nvme0n1, sector 120063912
  [  662.887824] Buffer I/O error on dev nvme0n1, logical block 14971093, lost 
async page write
  [  662.891254] Buffer I/O error on dev nvme0n1, logical block 14971094, lost 
async page write
  [  662.895591] Buffer I/O error on dev nvme0n1, logical block 14971095, lost 
async page write
  [  662.899873] Buffer I/O error on dev nvme0n1, logical block 14971096, lost 
async page write
  [  662.904179] Buffer I/O error on dev nvme0n1, logical block 14971097, lost 
async page write
  [  662.908458] Buffer I/O error on dev nvme0n1, logical block 14971098, lost 
async page write
  [  662.912287] Buffer I/O error on dev nvme0n1, logical block 14971099, lost 
async page write
  [  662.916047] Buffer I/O error on dev nvme0n1, logical block 14971100, lost 
async page write
  [  662.920285] Buffer I/O error on dev nvme0n1, logical block 14971101, lost 
async page write
  [  662.924565] Buffer I/O error on dev nvme0n1, logical block 14971102, lost 
async page write
  [  663.645530] blk_update_request: I/O error, dev nvme0n1, sector 120756912
  
  [ 1012.752265] blk_update_request: I/O error, dev nvme0n1, sector 3744
  [ 1012.755396] buffer_io_error: 194552 callbacks suppressed
  [ 1012.755398] Buffer I/O error on dev nvme0n1, logical block 20, lost async 
page write
  [ 1012.759248] Buffer I/O error on dev nvme0n1, logical block 21, lost async 
page write
  [ 1012.763368] Buffer I/O error on dev nvme0n1, logical block 22, lost async 
page write
  [ 1012.767271] Buffer I/O error on dev nvme0n1, logical block 23, lost async 
page write
  [ 1012.771314] Buffer I/O error on dev nvme0n1, logical block 24, lost async 
page write

  Able to replicate this with a bonnie++ stress test.

  bonnie++ -d /mnt/test/ -r 1000

  Linux i-0d76e144d85f487cf 4.4.0-64-generic #85-Ubuntu SMP Mon Feb 20 11:50:30 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 27 02:12 seq
   crw-rw 1 root audio 116, 33 Feb 27 02:12 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  Ec2AMI: ami-bc62b2aa
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1d
  Ec2InstanceType: i3.2xlarge
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic 
root=UUID=cfda0544-9803-41e7-badb-43563085ff3a ro console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-64-generic N/A
   linux-backports-modules-4.4.0-64-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial ec2-images
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 12/12/2016
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd12/12/2016:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

-- 
Mailing list:

[Kernel-packages] [Bug 1530405] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

2017-02-27 Thread Roberto Longobardi

Just wanted to report that I no longer have this issue since I installed
the Solus distribution: https://solus-project.com/

I was also affected by the fan bug just cited in the previous comment,
which also seems to have been solved with Solus:
https://bugzilla.kernel.org/show_bug.cgi?id=153281

I had tried the latest Fedora 25 just before Solus, but couldn't even
complete the installation wizard: it hanged with "soft lockup - CPU#0
stuck for 22s!".

I've been running the Solus distribution for some days now and didn't
get fans or NMI watchdog issues anymore. Also no boot options have been
required.

My machine is an Asus K550V laptop, Intel Core i7-6700HQ with NVidia
Geforce GTX 950M.

Hope this helps.

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will
  randomly freeze up, sometimes before the login screen, sometimes while
  I'm in the middle of using a program. This sometimes happens on the
  Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel
  4.2.0-22.

  Important part of log:

  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112129] NMI watchdog: BUG: soft 
lockup - CPU#0 stuck for 22s! [kerneloops:814]
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112134] Modules linked in: rfcomm 
bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul 
sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae 
glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic 
snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core 
joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi 
serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device 
snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore 
edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp 
parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid 
amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes 
video
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112183] CPU: 0 PID: 814 Comm: 
kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112184] Hardware name: ASUSTeK 
COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 
07/09/2015
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112186] task: 88031146d400 
ti: 88030e838000 task.ti: 88030e838000
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112188] RIP: 
0010:[]  [] __do_softirq+0x76/0x250
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112194] RSP: 
0018:88031fc03f30  EFLAGS: 0202
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112196] RAX: 88030e83c000 
RBX:  RCX: 40400040
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112197] RDX:  
RSI: 613e RDI: 0380
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112198] RBP: 88031fc03f80 
R08: 0029f8fa1411 R09: 88031fc169f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112199] R10: 0020 
R11: 0004 R12: 88031fc169c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112201] R13: 88030df8e200 
R14:  R15: 0001
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112202] FS:  
7f6c266ac880() GS:88031fc0() knlGS:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112203] CS:  0010 DS:  ES: 
 CR0: 80050033
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112205] CR2: 7ffef000bff8 
CR3: 00030f368000 CR4: 000406f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112206] Stack:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112207]  404000401fc03f78 
88030e83c000 0121 8803000a
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112209]  00021fc0d640 
 88031fc169c0 88030df8e200
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112211]   
0001 88031fc03f90 81081d23
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112213] Call Trace:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112215]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112219]  [] 
irq_exit+0xa3/0xb0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.11]  [] 
smp_apic_timer_interrupt+0x42/0x50
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112225]  [] 
apic_timer_interrupt+0x82/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112226]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112230]  [] ? 
finish_task_switch+0x67/0x1c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112232]  [] 
__schedule+0x36c/0x980

[Kernel-packages] [Bug 1623750] Re: Request to backport cxlflash patches to Xenial SRU stream

For yakkety:

https://lists.ubuntu.com/archives/kernel-team/2017-February/082724.html

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

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

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

** Changed in: linux (Ubuntu Yakkety)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

Title:
  Request to backport cxlflash patches to Xenial SRU stream

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  Problem Description
  ==
  There are a few patches in cxlflash that are in the process of getting 
upstream. We would like to have them pulled into Xenial SRU.

  Patches are,
  cxlflash: Scan host only after the port is ready for I/O
  cxlflash: Remove the device cleanly in the system shutdown path
  cxlflash: Fix to avoid EEH and host reset collisions
  cxlflash: Improve EEH recovery time

  These patches are applied to mkp's 4.9/scsi-queue. Commit ids from
  that queue,

  05dab43230fdc0d14ca885b473a2740fe017ecb1 scsi: cxlflash: Improve EEH recovery 
time
  1d3324c382b1a617eb567e3650dcb51f22dfec9a scsi: cxlflash: Fix to avoid EEH and 
host reset collisions
  babf985d1e1b0677cb264acd01319d2b9c8f4327 scsi: cxlflash: Remove the device 
cleanly in the system shutdown path
  bbbfae962b7c221237c0f92547ee0c83f7204747 scsi: cxlflash: Scan host only after 
the port is ready for I/O

  I tried applying them on local copy of xenial/master-next tree and it
  applied cleanly. Please let me know if you want me to attach the
  patches instead.

  Please include the above commits to Xenial SRU.

  Thank you.

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

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

[Kernel-packages] [Bug 1667531] Re: [Hyper-V] Include bondvf in /usr/sbin for SR-IOV interface bonding

I built a test kernel with the patch from this bug(Commit fd7aabb) , the
patch from bug 1667527 (Commit 4a9b0933) and the patch posted in comment
#5.

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1667531/SR-IOV/

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

Title:
  [Hyper-V] Include bondvf in /usr/sbin for SR-IOV interface bonding

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

Bug description:
  Please include bondvf.sh from kernel git tools/hv/ in /usr/sbin

  commit fd7aabb062fa1a8331a786d617744de220eaf002
  Author: Haiyang Zhang 
  Date:   Fri Dec 2 15:55:38 2016 -0800

  tools: hv: Enable network manager for bonding scripts on RHEL

  We found network manager is necessary on RHEL to make the synthetic
  NIC, VF NIC bonding operations handled automatically. So, enabling
  network manager here.

  Signed-off-by: Haiyang Zhang 
  Reviewed-by: K. Y. Srinivasan 
  Signed-off-by: David S. Miller 

  commit 178cd55f086629cf0bad9c66c793a7e2bcc3abb6
  Author: Haiyang Zhang 
  Date:   Mon Jul 11 17:06:42 2016 -0700

  tools: hv: Add a script to help bonding synthetic and VF NICs

  This script helps to create bonding network devices based on synthetic NIC
  (the virtual network adapter usually provided by Hyper-V) and the matching
  VF NIC (SRIOV virtual function). So the synthetic NIC and VF NIC can
  function as one network device, and fail over to the synthetic NIC if VF 
is
  down.

  Mayjor distros (RHEL, Ubuntu, SLES) supported by Hyper-V are supported by
  this script.

  Signed-off-by: Haiyang Zhang 
  Reviewed-by: K. Y. Srinivasan 
  Signed-off-by: David S. Miller 

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

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

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

--- Comment From dougm...@us.ibm.com 2017-02-27 16:29 EDT---
Verified, kernel 4.8.0-40-generic fixes this 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/1662673

Title:
  systemd-udevd hung in blk_mq_freeze_queue_wait testing unpartitioned
  NVMe drive

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

Bug description:
  For reference, here is the stack of systemd-udevd seen in the hang:

  [ 1558.214013] INFO: task systemd-udevd:1778 blocked for more than 120 
seconds.
  [ 1558.214318] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 1558.214556] systemd-udevd   D 3fff8dbdf7a0 0  1778  1 
0x0004
  [ 1558.214637] Call Trace:
  [ 1558.214673] [c4ad3790] [c07aac20] 
schedule_timeout+0x180/0x2f0 (unreliable)
  [ 1558.214779] [c4ad3960] [c00158d0] __switch_to+0x200/0x350
  [ 1558.214870] [c4ad39c0] [c07adbb4] __schedule+0x414/0x9e0
  [ 1558.214961] [c4ad3a90] [c03b4e54] 
blk_mq_freeze_queue_wait+0x64/0xd0
  [ 1558.215107] [c4ad3af0] [d00034011964] 
nvme_revalidate_disk+0xd4/0x3a0 [nvme]
  [ 1558.215386] [c4ad3b90] [c03c2398] 
rescan_partitions+0x98/0x390
  [ 1558.215508] [c4ad3c60] [c03bb7ac] 
__blkdev_reread_part+0x9c/0xd0
  [ 1558.215599] [c4ad3c90] [c03bb818] 
blkdev_reread_part+0x38/0x70
  [ 1558.215935] [c4ad3cc0] [c03bc334] blkdev_ioctl+0x3b4/0xb80
  [ 1558.216016] [c4ad3d20] [c02cbcd0] block_ioctl+0x70/0x90
  [ 1558.216114] [c4ad3d40] [c0296b38] do_vfs_ioctl+0x458/0x740
  [ 1558.216192] [c4ad3dd0] [c0296ee4] SyS_ioctl+0xc4/0xe0
  [ 1558.216275] [c4ad3e30] [c000a17c] system_call+0x38/0xb4

  It appears that systemd-udevd is triggering every time HTX writes to
  the boot sector (partition table) of the raw drive, and this is
  causing the revalidate calls which expose the issue with the block
  driver mq freeze. With a partition table on each drive, HTX will no
  longer be writing the partition table and no longer triggering systemd
  to re-read the partition table and try to freeze I/O.

  The fix for this is provided by the following upstream commit:

  966d2b0 percpu-refcount: fix reference leak during percpu-atomic
  transition

  which needs to be pulled into 16.04 (as well as newer releases).

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

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

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

--- Comment From dougm...@us.ibm.com 2017-02-27 16:29 EDT---
Verified, kernel 4.8.0-40-generic fixes this 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/1662666

Title:
  ISST-LTE:pNV: ppc64_cpu command is hung w HDs, SSDs and NVMe

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:
  -- Problem Description --
  The following upstream patches are needed for Ubuntu to fix a hang situation 
reported when executing ppc64_cpu --smt=on that occurs with various disk types. 
We need whichever ones have not yet been pulled into the base.

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=e57690fe009b2ab0cee8a57f53be634540e49c9d
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=0e87e58bf60edb6bb28e493c7a143f41b091a5e5
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=135e8c9250dd5c8c9aae5984fde6f230d0cbfeaf
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=c02ebfdddbafa9a6a0f52fbd715e6bfa229af9d3
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d1b1cea1e58477dad88ff769f54c0d2dfa56d923
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=36e1f3d107867b25c616c2fd294f5a1c9d4e5d09
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=71f79fb3179e69b0c1448a2101a866d871c66e7f

  The hang problem can be reproduced with the following shell script
  using an NVMe device executed on kernel versions 4.4.0-45 and 4.4.0-59
  within 30 minutes. It was also reproduced on a 4.8.0-32-generic
  kernel, although it took over 3 hours to manifest.

  #!/bin/bash

  if [[ ${#} -eq 0 ]]; then
  ${0} breaker &
  while true; do
  dd if=/dev/nvme0n1 bs=1024k of=/dev/null
  done
  elif [[ ${1} == "breaker" ]]; then
  while true; do
  ppc64_cpu --smt=off
  sleep 5
  ppc64_cpu --smt=on
  sleep 5
  done
  fi

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

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

[Kernel-packages] [Bug 1632458] Re: [Ubuntu 16.10] - System crashes and gives out call traces when libhugetlbfs test suite is run.

*** This bug is a duplicate of bug 1628976 ***
https://bugs.launchpad.net/bugs/1628976

Comment #4 says that this is a duplicate of LP #1628976, and that
appears to be true. The fix identified here was applied for that bug and
was released several months ago.

Closing this bug as a duplicate of that one.

** This bug has been marked a duplicate of bug 1628976
   Ubuntu 16.10: Oops panic in move_page_tables/page_remove_rmap after running 
memory_stress_ng.

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

Title:
  [Ubuntu 16.10] - System crashes and gives out call traces when
  libhugetlbfs test suite is run.

Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - Santhosh G  - 2016-09-27 01:55:00 ==
  Issue:
  Kernel unable to handle page request when heapshrink test case is run from 
libhugetlbfs suite.

  Environment:
  arch - ppc64le
  ubuntu kvm guest

  Host related Info:
  Kernel:
  -
  uname -a
  Linux ltc-haba1 4.8.0-17-generic #19-Ubuntu SMP Sun Sep 25 06:35:40 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  Memory:
  
  oot@ltc-haba1:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   255G 65G187G 22M1.9G
188G
  Swap:  225G  0B225G

  Hugepages configured:
  
  root@ltc-haba1:~# cat /proc/meminfo | grep -i Huge
  AnonHugePages: 81920 kB
  ShmemHugePages:0 kB
  HugePages_Total:4096
  HugePages_Free: 3584
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:  16384 kB

  
  Guest Related Info:
  --
  -
  Kernel:
  -
  root@ubuntu:~/libhugetlbfs# uname -a
  Linux ubuntu 4.8.0-17-generic #19-Ubuntu SMP Sun Sep 25 06:35:40 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  Memory:
  -
  root@ubuntu:~/libhugetlbfs# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   8.0G133M7.7G 15M132M
7.5G
  Swap:  3.3G  0B3.3G

  Hugepages configured:
  ---
  root@ubuntu:~/libhugetlbfs# cat /proc/meminfo | grep -i Huge
  AnonHugePages: 0 kB
  ShmemHugePages:0 kB
  HugePages_Total: 256
  HugePages_Free:  256
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:  16384 kB

  
  Steps to reproduce:
  1- Install a ubuntu kvm guest with hugepages memory Backing.
  2 - git clone the latest libhugetlbfs from 
https://github.com/libhugetlbfs/libhugetlbfs.git
  3 - configure huge[pages in guest and run make check.

  xmon is configured in the system .
  The system gets call traces and enters xmon console:

  HUGETLB_VERBOSE=1 HUGETLB_MORECORE=yes heap-overflow (16M: 64):   [  
281.735713] Unable to handle kernel paging request for data at address 
0x42328e38
  [  281.735804] Faulting instruction address: 0xc027b410
  cpu 0x1: Vector: 300 (Data Access) at [c001fa8c3730]
  pc: c027b410: shrink_active_list+0x300/0x4d0
  lr: c027b3f4: shrink_active_list+0x2e4/0x4d0
  sp: c001fa8c39b0
 msr: 80010280b033
 dar: 42328e38
   dsisr: 4200
current = 0xc001fa8adc00
paca= 0xcfb80900 softe: 0irq_happened: 0x01
  pid   = 50, comm = kswapd0
  Linux version 4.8.0-17-generic (buildd@bos01-ppc64el-025) (gcc version 6.2.0 
20160914 (Ubuntu 6.2.0-3ubuntu15) ) #19-Ubuntu SMP Sun Sep 25 06:35:40 UTC 2016 
(Ubuntu 4.8.0-17.19-generic 4.8.0-rc7)
  enter ? for help
  [c001fa8c3aa0] c027bbdc shrink_node_memcg+0x5fc/0x800
  [c001fa8c3bc0] c027bf0c shrink_node+0x12c/0x3f0
  [c001fa8c3c80] c027d500 kswapd+0x460/0x990
  [c001fa8c3d80] c00fd120 kthread+0x110/0x130
  [c001fa8c3e30] c00098f0 ret_from_kernel_thread+0x5c/0x6c

  xmon logs:

  1:mon> e
  cpu 0x1: Vector: 300 (Data Access) at [c001fa8e7730]
  pc: c027b410: shrink_active_list+0x300/0x4d0
  lr: c027b3f4: shrink_active_list+0x2e4/0x4d0
  sp: c001fa8e79b0
 msr: 80010280b033
 dar: 420c58d0
   dsisr: 4200
current = 0xc001fa8a
paca= 0xcfb80900 softe: 0irq_happened: 0x01
  pid   = 50, comm = kswapd0
  Linux version 4.8.0-17-generic (buildd@bos01-ppc64el-025) (gcc version 6.2.0 
20160914 (Ubuntu 6.2.0-3ubuntu15) ) #19-Ubuntu SMP Sun Sep 25 06:35:40 UTC 2016 
(Ubuntu 4.8.0-17.19-generic 4.8.0-rc7)

  1:mon> r
  R00 = c027b3f4   R16 = c001fffcfe00
  R01 = c001fa8e79b0   R17 =

[Kernel-packages] [Bug 1623750] Re: Request to backport cxlflash patches to Xenial SRU stream

** Tags removed: bugnameltc-146336 severity-high

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

Title:
  Request to backport cxlflash patches to Xenial SRU stream

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

Bug description:
  Problem Description
  ==
  There are a few patches in cxlflash that are in the process of getting 
upstream. We would like to have them pulled into Xenial SRU.

  Patches are,
  cxlflash: Scan host only after the port is ready for I/O
  cxlflash: Remove the device cleanly in the system shutdown path
  cxlflash: Fix to avoid EEH and host reset collisions
  cxlflash: Improve EEH recovery time

  These patches are applied to mkp's 4.9/scsi-queue. Commit ids from
  that queue,

  05dab43230fdc0d14ca885b473a2740fe017ecb1 scsi: cxlflash: Improve EEH recovery 
time
  1d3324c382b1a617eb567e3650dcb51f22dfec9a scsi: cxlflash: Fix to avoid EEH and 
host reset collisions
  babf985d1e1b0677cb264acd01319d2b9c8f4327 scsi: cxlflash: Remove the device 
cleanly in the system shutdown path
  bbbfae962b7c221237c0f92547ee0c83f7204747 scsi: cxlflash: Scan host only after 
the port is ready for I/O

  I tried applying them on local copy of xenial/master-next tree and it
  applied cleanly. Please let me know if you want me to attach the
  patches instead.

  Please include the above commits to Xenial SRU.

  Thank you.

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

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

[Kernel-packages] [Bug 1668129] Re: Amazon I3 Instance Buffer I/O error on dev nvme0n1

2017-02-27 Thread Dan Streetman

@matt-e do you have a quicker reproducer I can use?  I've been trying
bonnie++ from the description, but that doesn't repro at all in west-2
for me, and only once in east-1 so far.  Also what AMI are you using in
west-2 that shows 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/1668129

Title:
  Amazon I3 Instance Buffer I/O error on dev nvme0n1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On the AWS i3 instance class - when putting the new NVME storage disks
  under high IO load - seeing data corruption and errors in dmesg

  
  [  662.884390] blk_update_request: I/O error, dev nvme0n1, sector 120063912
  [  662.887824] Buffer I/O error on dev nvme0n1, logical block 14971093, lost 
async page write
  [  662.891254] Buffer I/O error on dev nvme0n1, logical block 14971094, lost 
async page write
  [  662.895591] Buffer I/O error on dev nvme0n1, logical block 14971095, lost 
async page write
  [  662.899873] Buffer I/O error on dev nvme0n1, logical block 14971096, lost 
async page write
  [  662.904179] Buffer I/O error on dev nvme0n1, logical block 14971097, lost 
async page write
  [  662.908458] Buffer I/O error on dev nvme0n1, logical block 14971098, lost 
async page write
  [  662.912287] Buffer I/O error on dev nvme0n1, logical block 14971099, lost 
async page write
  [  662.916047] Buffer I/O error on dev nvme0n1, logical block 14971100, lost 
async page write
  [  662.920285] Buffer I/O error on dev nvme0n1, logical block 14971101, lost 
async page write
  [  662.924565] Buffer I/O error on dev nvme0n1, logical block 14971102, lost 
async page write
  [  663.645530] blk_update_request: I/O error, dev nvme0n1, sector 120756912
  
  [ 1012.752265] blk_update_request: I/O error, dev nvme0n1, sector 3744
  [ 1012.755396] buffer_io_error: 194552 callbacks suppressed
  [ 1012.755398] Buffer I/O error on dev nvme0n1, logical block 20, lost async 
page write
  [ 1012.759248] Buffer I/O error on dev nvme0n1, logical block 21, lost async 
page write
  [ 1012.763368] Buffer I/O error on dev nvme0n1, logical block 22, lost async 
page write
  [ 1012.767271] Buffer I/O error on dev nvme0n1, logical block 23, lost async 
page write
  [ 1012.771314] Buffer I/O error on dev nvme0n1, logical block 24, lost async 
page write

  Able to replicate this with a bonnie++ stress test.

  bonnie++ -d /mnt/test/ -r 1000

  Linux i-0d76e144d85f487cf 4.4.0-64-generic #85-Ubuntu SMP Mon Feb 20 11:50:30 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 27 02:12 seq
   crw-rw 1 root audio 116, 33 Feb 27 02:12 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  Ec2AMI: ami-bc62b2aa
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1d
  Ec2InstanceType: i3.2xlarge
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic 
root=UUID=cfda0544-9803-41e7-badb-43563085ff3a ro console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-64-generic N/A
   linux-backports-modules-4.4.0-64-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial ec2-images
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 12/12/2016
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd12/12/2016:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1623750] Re: Request to backport cxlflash patches to Xenial SRU stream

https://lists.ubuntu.com/archives/kernel-team/2017-February/082719.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/1623750

Title:
  Request to backport cxlflash patches to Xenial SRU stream

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

Bug description:
  Problem Description
  ==
  There are a few patches in cxlflash that are in the process of getting 
upstream. We would like to have them pulled into Xenial SRU.

  Patches are,
  cxlflash: Scan host only after the port is ready for I/O
  cxlflash: Remove the device cleanly in the system shutdown path
  cxlflash: Fix to avoid EEH and host reset collisions
  cxlflash: Improve EEH recovery time

  These patches are applied to mkp's 4.9/scsi-queue. Commit ids from
  that queue,

  05dab43230fdc0d14ca885b473a2740fe017ecb1 scsi: cxlflash: Improve EEH recovery 
time
  1d3324c382b1a617eb567e3650dcb51f22dfec9a scsi: cxlflash: Fix to avoid EEH and 
host reset collisions
  babf985d1e1b0677cb264acd01319d2b9c8f4327 scsi: cxlflash: Remove the device 
cleanly in the system shutdown path
  bbbfae962b7c221237c0f92547ee0c83f7204747 scsi: cxlflash: Scan host only after 
the port is ready for I/O

  I tried applying them on local copy of xenial/master-next tree and it
  applied cleanly. Please let me know if you want me to attach the
  patches instead.

  Please include the above commits to Xenial SRU.

  Thank you.

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

-- 
Mailing list: https://launchpad.net/~kernel-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-27 Thread Adrian

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

-- 
You 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
Status in linux source package in Yakkety:
  Fix Committed

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 1667531] Re: [Hyper-V] Include bondvf in /usr/sbin for SR-IOV interface bonding

Could you please build the test kernel based on this one:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667527
http://kernel.ubuntu.com/~jsalisbury/lp1667527/xenial/

Thus, we will have a test kernel with all the patches and it would be
the test kernel for the full SR-IOV tests.

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

Title:
  [Hyper-V] Include bondvf in /usr/sbin for SR-IOV interface bonding

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

Bug description:
  Please include bondvf.sh from kernel git tools/hv/ in /usr/sbin

  commit fd7aabb062fa1a8331a786d617744de220eaf002
  Author: Haiyang Zhang 
  Date:   Fri Dec 2 15:55:38 2016 -0800

  tools: hv: Enable network manager for bonding scripts on RHEL

  We found network manager is necessary on RHEL to make the synthetic
  NIC, VF NIC bonding operations handled automatically. So, enabling
  network manager here.

  Signed-off-by: Haiyang Zhang 
  Reviewed-by: K. Y. Srinivasan 
  Signed-off-by: David S. Miller 

  commit 178cd55f086629cf0bad9c66c793a7e2bcc3abb6
  Author: Haiyang Zhang 
  Date:   Mon Jul 11 17:06:42 2016 -0700

  tools: hv: Add a script to help bonding synthetic and VF NICs

  This script helps to create bonding network devices based on synthetic NIC
  (the virtual network adapter usually provided by Hyper-V) and the matching
  VF NIC (SRIOV virtual function). So the synthetic NIC and VF NIC can
  function as one network device, and fail over to the synthetic NIC if VF 
is
  down.

  Mayjor distros (RHEL, Ubuntu, SLES) supported by Hyper-V are supported by
  this script.

  Signed-off-by: Haiyang Zhang 
  Reviewed-by: K. Y. Srinivasan 
  Signed-off-by: David S. Miller 

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

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

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

tests ran:  19, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-40.43-generic/gonzo__4.8.0-40.43__2017-02-27_19-49-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/1667066

Title:
  linux: 4.8.0-40.43 -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:
  Confirmed
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 Yakkety:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  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/1667066/+subscriptions

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

[Kernel-packages] [Bug 1668129] Re: Amazon I3 Instance Buffer I/O error on dev nvme0n1

2017-02-27 Thread Matt Billenstein

I've had this issue on 4 different instances in us-west-2 -- two I still
have running -- can I help?

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

Title:
  Amazon I3 Instance Buffer I/O error on dev nvme0n1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On the AWS i3 instance class - when putting the new NVME storage disks
  under high IO load - seeing data corruption and errors in dmesg

  
  [  662.884390] blk_update_request: I/O error, dev nvme0n1, sector 120063912
  [  662.887824] Buffer I/O error on dev nvme0n1, logical block 14971093, lost 
async page write
  [  662.891254] Buffer I/O error on dev nvme0n1, logical block 14971094, lost 
async page write
  [  662.895591] Buffer I/O error on dev nvme0n1, logical block 14971095, lost 
async page write
  [  662.899873] Buffer I/O error on dev nvme0n1, logical block 14971096, lost 
async page write
  [  662.904179] Buffer I/O error on dev nvme0n1, logical block 14971097, lost 
async page write
  [  662.908458] Buffer I/O error on dev nvme0n1, logical block 14971098, lost 
async page write
  [  662.912287] Buffer I/O error on dev nvme0n1, logical block 14971099, lost 
async page write
  [  662.916047] Buffer I/O error on dev nvme0n1, logical block 14971100, lost 
async page write
  [  662.920285] Buffer I/O error on dev nvme0n1, logical block 14971101, lost 
async page write
  [  662.924565] Buffer I/O error on dev nvme0n1, logical block 14971102, lost 
async page write
  [  663.645530] blk_update_request: I/O error, dev nvme0n1, sector 120756912
  
  [ 1012.752265] blk_update_request: I/O error, dev nvme0n1, sector 3744
  [ 1012.755396] buffer_io_error: 194552 callbacks suppressed
  [ 1012.755398] Buffer I/O error on dev nvme0n1, logical block 20, lost async 
page write
  [ 1012.759248] Buffer I/O error on dev nvme0n1, logical block 21, lost async 
page write
  [ 1012.763368] Buffer I/O error on dev nvme0n1, logical block 22, lost async 
page write
  [ 1012.767271] Buffer I/O error on dev nvme0n1, logical block 23, lost async 
page write
  [ 1012.771314] Buffer I/O error on dev nvme0n1, logical block 24, lost async 
page write

  Able to replicate this with a bonnie++ stress test.

  bonnie++ -d /mnt/test/ -r 1000

  Linux i-0d76e144d85f487cf 4.4.0-64-generic #85-Ubuntu SMP Mon Feb 20 11:50:30 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 27 02:12 seq
   crw-rw 1 root audio 116, 33 Feb 27 02:12 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  Ec2AMI: ami-bc62b2aa
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1d
  Ec2InstanceType: i3.2xlarge
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic 
root=UUID=cfda0544-9803-41e7-badb-43563085ff3a ro console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-64-generic N/A
   linux-backports-modules-4.4.0-64-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial ec2-images
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 12/12/2016
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd12/12/2016:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

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

[Kernel-packages] [Bug 1623750] Re: Request to backport cxlflash patches to Xenial SRU stream

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

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

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

Title:
  Request to backport cxlflash patches to Xenial SRU stream

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

Bug description:
  Problem Description
  ==
  There are a few patches in cxlflash that are in the process of getting 
upstream. We would like to have them pulled into Xenial SRU.

  Patches are,
  cxlflash: Scan host only after the port is ready for I/O
  cxlflash: Remove the device cleanly in the system shutdown path
  cxlflash: Fix to avoid EEH and host reset collisions
  cxlflash: Improve EEH recovery time

  These patches are applied to mkp's 4.9/scsi-queue. Commit ids from
  that queue,

  05dab43230fdc0d14ca885b473a2740fe017ecb1 scsi: cxlflash: Improve EEH recovery 
time
  1d3324c382b1a617eb567e3650dcb51f22dfec9a scsi: cxlflash: Fix to avoid EEH and 
host reset collisions
  babf985d1e1b0677cb264acd01319d2b9c8f4327 scsi: cxlflash: Remove the device 
cleanly in the system shutdown path
  bbbfae962b7c221237c0f92547ee0c83f7204747 scsi: cxlflash: Scan host only after 
the port is ready for I/O

  I tried applying them on local copy of xenial/master-next tree and it
  applied cleanly. Please let me know if you want me to attach the
  patches instead.

  Please include the above commits to Xenial SRU.

  Thank you.

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

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

[Kernel-packages] [Bug 1668129] Re: Amazon I3 Instance Buffer I/O error on dev nvme0n1

2017-02-27 Thread Dan Streetman

@rram can you try to reproduce with us-west-2?  I'm able to repro in
east-1 but not in west-2.

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

Title:
  Amazon I3 Instance Buffer I/O error on dev nvme0n1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On the AWS i3 instance class - when putting the new NVME storage disks
  under high IO load - seeing data corruption and errors in dmesg

  
  [  662.884390] blk_update_request: I/O error, dev nvme0n1, sector 120063912
  [  662.887824] Buffer I/O error on dev nvme0n1, logical block 14971093, lost 
async page write
  [  662.891254] Buffer I/O error on dev nvme0n1, logical block 14971094, lost 
async page write
  [  662.895591] Buffer I/O error on dev nvme0n1, logical block 14971095, lost 
async page write
  [  662.899873] Buffer I/O error on dev nvme0n1, logical block 14971096, lost 
async page write
  [  662.904179] Buffer I/O error on dev nvme0n1, logical block 14971097, lost 
async page write
  [  662.908458] Buffer I/O error on dev nvme0n1, logical block 14971098, lost 
async page write
  [  662.912287] Buffer I/O error on dev nvme0n1, logical block 14971099, lost 
async page write
  [  662.916047] Buffer I/O error on dev nvme0n1, logical block 14971100, lost 
async page write
  [  662.920285] Buffer I/O error on dev nvme0n1, logical block 14971101, lost 
async page write
  [  662.924565] Buffer I/O error on dev nvme0n1, logical block 14971102, lost 
async page write
  [  663.645530] blk_update_request: I/O error, dev nvme0n1, sector 120756912
  
  [ 1012.752265] blk_update_request: I/O error, dev nvme0n1, sector 3744
  [ 1012.755396] buffer_io_error: 194552 callbacks suppressed
  [ 1012.755398] Buffer I/O error on dev nvme0n1, logical block 20, lost async 
page write
  [ 1012.759248] Buffer I/O error on dev nvme0n1, logical block 21, lost async 
page write
  [ 1012.763368] Buffer I/O error on dev nvme0n1, logical block 22, lost async 
page write
  [ 1012.767271] Buffer I/O error on dev nvme0n1, logical block 23, lost async 
page write
  [ 1012.771314] Buffer I/O error on dev nvme0n1, logical block 24, lost async 
page write

  Able to replicate this with a bonnie++ stress test.

  bonnie++ -d /mnt/test/ -r 1000

  Linux i-0d76e144d85f487cf 4.4.0-64-generic #85-Ubuntu SMP Mon Feb 20 11:50:30 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 27 02:12 seq
   crw-rw 1 root audio 116, 33 Feb 27 02:12 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  Ec2AMI: ami-bc62b2aa
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1d
  Ec2InstanceType: i3.2xlarge
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic 
root=UUID=cfda0544-9803-41e7-badb-43563085ff3a ro console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-64-generic N/A
   linux-backports-modules-4.4.0-64-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial ec2-images
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 12/12/2016
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd12/12/2016:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

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

[Kernel-packages] [Bug 1668129] Re: Amazon I3 Instance Buffer I/O error on dev nvme0n1

2017-02-27 Thread Ricky Ramirez

@ddstreet us-east-1

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

Title:
  Amazon I3 Instance Buffer I/O error on dev nvme0n1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On the AWS i3 instance class - when putting the new NVME storage disks
  under high IO load - seeing data corruption and errors in dmesg

  
  [  662.884390] blk_update_request: I/O error, dev nvme0n1, sector 120063912
  [  662.887824] Buffer I/O error on dev nvme0n1, logical block 14971093, lost 
async page write
  [  662.891254] Buffer I/O error on dev nvme0n1, logical block 14971094, lost 
async page write
  [  662.895591] Buffer I/O error on dev nvme0n1, logical block 14971095, lost 
async page write
  [  662.899873] Buffer I/O error on dev nvme0n1, logical block 14971096, lost 
async page write
  [  662.904179] Buffer I/O error on dev nvme0n1, logical block 14971097, lost 
async page write
  [  662.908458] Buffer I/O error on dev nvme0n1, logical block 14971098, lost 
async page write
  [  662.912287] Buffer I/O error on dev nvme0n1, logical block 14971099, lost 
async page write
  [  662.916047] Buffer I/O error on dev nvme0n1, logical block 14971100, lost 
async page write
  [  662.920285] Buffer I/O error on dev nvme0n1, logical block 14971101, lost 
async page write
  [  662.924565] Buffer I/O error on dev nvme0n1, logical block 14971102, lost 
async page write
  [  663.645530] blk_update_request: I/O error, dev nvme0n1, sector 120756912
  
  [ 1012.752265] blk_update_request: I/O error, dev nvme0n1, sector 3744
  [ 1012.755396] buffer_io_error: 194552 callbacks suppressed
  [ 1012.755398] Buffer I/O error on dev nvme0n1, logical block 20, lost async 
page write
  [ 1012.759248] Buffer I/O error on dev nvme0n1, logical block 21, lost async 
page write
  [ 1012.763368] Buffer I/O error on dev nvme0n1, logical block 22, lost async 
page write
  [ 1012.767271] Buffer I/O error on dev nvme0n1, logical block 23, lost async 
page write
  [ 1012.771314] Buffer I/O error on dev nvme0n1, logical block 24, lost async 
page write

  Able to replicate this with a bonnie++ stress test.

  bonnie++ -d /mnt/test/ -r 1000

  Linux i-0d76e144d85f487cf 4.4.0-64-generic #85-Ubuntu SMP Mon Feb 20 11:50:30 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 27 02:12 seq
   crw-rw 1 root audio 116, 33 Feb 27 02:12 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  Ec2AMI: ami-bc62b2aa
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1d
  Ec2InstanceType: i3.2xlarge
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic 
root=UUID=cfda0544-9803-41e7-badb-43563085ff3a ro console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-64-generic N/A
   linux-backports-modules-4.4.0-64-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial ec2-images
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 12/12/2016
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd12/12/2016:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

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

[Kernel-packages] [Bug 1668129] Re: Amazon I3 Instance Buffer I/O error on dev nvme0n1

2017-02-27 Thread Dan Streetman

@rram what region are you using?

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

Title:
  Amazon I3 Instance Buffer I/O error on dev nvme0n1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On the AWS i3 instance class - when putting the new NVME storage disks
  under high IO load - seeing data corruption and errors in dmesg

  
  [  662.884390] blk_update_request: I/O error, dev nvme0n1, sector 120063912
  [  662.887824] Buffer I/O error on dev nvme0n1, logical block 14971093, lost 
async page write
  [  662.891254] Buffer I/O error on dev nvme0n1, logical block 14971094, lost 
async page write
  [  662.895591] Buffer I/O error on dev nvme0n1, logical block 14971095, lost 
async page write
  [  662.899873] Buffer I/O error on dev nvme0n1, logical block 14971096, lost 
async page write
  [  662.904179] Buffer I/O error on dev nvme0n1, logical block 14971097, lost 
async page write
  [  662.908458] Buffer I/O error on dev nvme0n1, logical block 14971098, lost 
async page write
  [  662.912287] Buffer I/O error on dev nvme0n1, logical block 14971099, lost 
async page write
  [  662.916047] Buffer I/O error on dev nvme0n1, logical block 14971100, lost 
async page write
  [  662.920285] Buffer I/O error on dev nvme0n1, logical block 14971101, lost 
async page write
  [  662.924565] Buffer I/O error on dev nvme0n1, logical block 14971102, lost 
async page write
  [  663.645530] blk_update_request: I/O error, dev nvme0n1, sector 120756912
  
  [ 1012.752265] blk_update_request: I/O error, dev nvme0n1, sector 3744
  [ 1012.755396] buffer_io_error: 194552 callbacks suppressed
  [ 1012.755398] Buffer I/O error on dev nvme0n1, logical block 20, lost async 
page write
  [ 1012.759248] Buffer I/O error on dev nvme0n1, logical block 21, lost async 
page write
  [ 1012.763368] Buffer I/O error on dev nvme0n1, logical block 22, lost async 
page write
  [ 1012.767271] Buffer I/O error on dev nvme0n1, logical block 23, lost async 
page write
  [ 1012.771314] Buffer I/O error on dev nvme0n1, logical block 24, lost async 
page write

  Able to replicate this with a bonnie++ stress test.

  bonnie++ -d /mnt/test/ -r 1000

  Linux i-0d76e144d85f487cf 4.4.0-64-generic #85-Ubuntu SMP Mon Feb 20 11:50:30 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 27 02:12 seq
   crw-rw 1 root audio 116, 33 Feb 27 02:12 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  Ec2AMI: ami-bc62b2aa
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1d
  Ec2InstanceType: i3.2xlarge
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic 
root=UUID=cfda0544-9803-41e7-badb-43563085ff3a ro console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-64-generic N/A
   linux-backports-modules-4.4.0-64-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial ec2-images
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 12/12/2016
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd12/12/2016:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668129/+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 1668382] [NEW] Ubuntu (Zesty): When we miss LSI/INTx interrupts on slot, message is too imprecise

Public bug reported:

-- Problem Description --
Some Power machines has limitations regarding INTx/Level-signaled interrupts in 
some slots. The kernel will present currently the following message in dmesg:

"pci 0003:70:00.0: of_irq_parse_pci() failed with rc=-22"

This is an imprecise, and kind of "misleading" message. The following
patch improved the way this information is showed to user:

f1aa54840657 ("of/irq: improve error report on irq discovery process failure")
[https://git.kernel.org/torvalds/c/f1aa5484]

With the patch, messages will show like:

"pci 0003:70:00.0: no interrupt-map found, INTx interrupts not available"
"pci 0003:70:00.0: possibly some PCI slots don't have level triggered 
interrupts capability" (<= this one shows only once, regardless the number of 
slot without LSI)
--

So, we want to request Canonical to include the above patch on kernel 4.10, to 
Ubuntu 17.04 (Zesty), if possible.
Thanks in advance,


Guilherme

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


** Tags: architecture-ppc64le bugnameltc-144695 severity-high 
targetmilestone-inin1704

** Tags added: architecture-ppc64le bugnameltc-144695 severity-high
targetmilestone-inin1704

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

Title:
  Ubuntu (Zesty): When we miss LSI/INTx interrupts on slot, message is
  too imprecise

Status in linux package in Ubuntu:
  New

Bug description:
  -- Problem Description --
  Some Power machines has limitations regarding INTx/Level-signaled interrupts 
in some slots. The kernel will present currently the following message in dmesg:

  "pci 0003:70:00.0: of_irq_parse_pci() failed with rc=-22"

  This is an imprecise, and kind of "misleading" message. The following
  patch improved the way this information is showed to user:

  f1aa54840657 ("of/irq: improve error report on irq discovery process failure")
  [https://git.kernel.org/torvalds/c/f1aa5484]

  With the patch, messages will show like:

  "pci 0003:70:00.0: no interrupt-map found, INTx interrupts not available"
  "pci 0003:70:00.0: possibly some PCI slots don't have level triggered 
interrupts capability" (<= this one shows only once, regardless the number of 
slot without LSI)
  --

  So, we want to request Canonical to include the above patch on kernel 4.10, 
to Ubuntu 17.04 (Zesty), if possible.
  Thanks in advance,

  
  Guilherme

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

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

[Kernel-packages] [Bug 1668129] Re: Amazon I3 Instance Buffer I/O error on dev nvme0n1

2017-02-27 Thread Ricky Ramirez

I tested this on a few i3.2xlarge instances using bonnie++ and an ext4
mounted filesystem

ami-cc10c1da (precise) - does not recognize the ephemeral device
ami-822bfa94 (trusty) - does NOT appear to be affected
ami-1ac0120c (xenial) - is affected
ami-e600d1f0 (yakkety) - is affected

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

Title:
  Amazon I3 Instance Buffer I/O error on dev nvme0n1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On the AWS i3 instance class - when putting the new NVME storage disks
  under high IO load - seeing data corruption and errors in dmesg

  
  [  662.884390] blk_update_request: I/O error, dev nvme0n1, sector 120063912
  [  662.887824] Buffer I/O error on dev nvme0n1, logical block 14971093, lost 
async page write
  [  662.891254] Buffer I/O error on dev nvme0n1, logical block 14971094, lost 
async page write
  [  662.895591] Buffer I/O error on dev nvme0n1, logical block 14971095, lost 
async page write
  [  662.899873] Buffer I/O error on dev nvme0n1, logical block 14971096, lost 
async page write
  [  662.904179] Buffer I/O error on dev nvme0n1, logical block 14971097, lost 
async page write
  [  662.908458] Buffer I/O error on dev nvme0n1, logical block 14971098, lost 
async page write
  [  662.912287] Buffer I/O error on dev nvme0n1, logical block 14971099, lost 
async page write
  [  662.916047] Buffer I/O error on dev nvme0n1, logical block 14971100, lost 
async page write
  [  662.920285] Buffer I/O error on dev nvme0n1, logical block 14971101, lost 
async page write
  [  662.924565] Buffer I/O error on dev nvme0n1, logical block 14971102, lost 
async page write
  [  663.645530] blk_update_request: I/O error, dev nvme0n1, sector 120756912
  
  [ 1012.752265] blk_update_request: I/O error, dev nvme0n1, sector 3744
  [ 1012.755396] buffer_io_error: 194552 callbacks suppressed
  [ 1012.755398] Buffer I/O error on dev nvme0n1, logical block 20, lost async 
page write
  [ 1012.759248] Buffer I/O error on dev nvme0n1, logical block 21, lost async 
page write
  [ 1012.763368] Buffer I/O error on dev nvme0n1, logical block 22, lost async 
page write
  [ 1012.767271] Buffer I/O error on dev nvme0n1, logical block 23, lost async 
page write
  [ 1012.771314] Buffer I/O error on dev nvme0n1, logical block 24, lost async 
page write

  Able to replicate this with a bonnie++ stress test.

  bonnie++ -d /mnt/test/ -r 1000

  Linux i-0d76e144d85f487cf 4.4.0-64-generic #85-Ubuntu SMP Mon Feb 20 11:50:30 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 27 02:12 seq
   crw-rw 1 root audio 116, 33 Feb 27 02:12 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  Ec2AMI: ami-bc62b2aa
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1d
  Ec2InstanceType: i3.2xlarge
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic 
root=UUID=cfda0544-9803-41e7-badb-43563085ff3a ro console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-64-generic N/A
   linux-backports-modules-4.4.0-64-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial ec2-images
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 12/12/2016
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd12/12/2016:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1668382] [NEW] Ubuntu (Zesty): When we miss LSI/INTx interrupts on slot, message is too imprecise

2017-02-27 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

-- Problem Description --
Some Power machines has limitations regarding INTx/Level-signaled interrupts in 
some slots. The kernel will present currently the following message in dmesg:

"pci 0003:70:00.0: of_irq_parse_pci() failed with rc=-22"

This is an imprecise, and kind of "misleading" message. The following
patch improved the way this information is showed to user:

f1aa54840657 ("of/irq: improve error report on irq discovery process failure")
[https://git.kernel.org/torvalds/c/f1aa5484]

With the patch, messages will show like:

"pci 0003:70:00.0: no interrupt-map found, INTx interrupts not available"
"pci 0003:70:00.0: possibly some PCI slots don't have level triggered 
interrupts capability" (<= this one shows only once, regardless the number of 
slot without LSI)
--

So, we want to request Canonical to include the above patch on kernel 4.10, to 
Ubuntu 17.04 (Zesty), if possible.
Thanks in advance,


Guilherme

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


** Tags: architecture-ppc64le bugnameltc-144695 severity-high 
targetmilestone-inin1704
-- 
Ubuntu (Zesty): When we miss LSI/INTx interrupts on slot, message is too 
imprecise
https://bugs.launchpad.net/bugs/1668382
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

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

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-40.43-generic/gonzo__4.8.0-40.43__2017-02-27_19-24-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/1667066

Title:
  linux: 4.8.0-40.43 -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:
  Confirmed
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 Yakkety:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  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/1667066/+subscriptions

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

[Kernel-packages] [Bug 1658219] Re: flock not mediated by 'k'

4.4.0-65.86-generic fixes this issue on xenial.

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

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

Title:
  flock not mediated by 'k'

Status in AppArmor:
  In Progress
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

Bug description:
  $ cat ./apparmor.profile 
  #include 

  profile test {
#include 

/bin/bash ixr,
/dev/pts/* rw,
/usr/bin/flock ixr,
# Not blocked:
# aa-exec -p test -- flock -w 1 /tmp/test.lock -c true
/tmp/test.lock rw,

  }

  $ sudo apparmor_parser -r ./apparmor.profile

  $ aa-exec -p test -- flock -w 1 /tmp/test.lock -c true && echo yes
  yes

  $ ls -l /tmp/test.lock 
  -rw-rw-r-- 1 jamie jamie 0 Jan 20 15:57 /tmp/test.lock

  The flock command uses flock(LOCK_EX) and I expected it to be blocked
  due to the lack of 'k'.

  apparmor userspace 2.10.95-0ubuntu2.5 (xenial) and 4.9.0-12.13-generic
  kernel on amd64.

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

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

[Kernel-packages] [Bug 1658219] Re: flock not mediated by 'k'

4.8.0-40.43-generic fixes this issue on yakkety.

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

Title:
  flock not mediated by 'k'

Status in AppArmor:
  In Progress
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

Bug description:
  $ cat ./apparmor.profile 
  #include 

  profile test {
#include 

/bin/bash ixr,
/dev/pts/* rw,
/usr/bin/flock ixr,
# Not blocked:
# aa-exec -p test -- flock -w 1 /tmp/test.lock -c true
/tmp/test.lock rw,

  }

  $ sudo apparmor_parser -r ./apparmor.profile

  $ aa-exec -p test -- flock -w 1 /tmp/test.lock -c true && echo yes
  yes

  $ ls -l /tmp/test.lock 
  -rw-rw-r-- 1 jamie jamie 0 Jan 20 15:57 /tmp/test.lock

  The flock command uses flock(LOCK_EX) and I expected it to be blocked
  due to the lack of 'k'.

  apparmor userspace 2.10.95-0ubuntu2.5 (xenial) and 4.9.0-12.13-generic
  kernel on amd64.

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

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

[Kernel-packages] [Bug 1658219] Re: flock not mediated by 'k'

4.10.0-8.10-generic has the fix for this bug so marking the zesty task
as released.

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

** Changed in: apparmor
   Status: Triaged => In Progress

** Changed in: apparmor
 Assignee: (unassigned) => John Johansen (jjohansen)

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

Title:
  flock not mediated by 'k'

Status in AppArmor:
  In Progress
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

Bug description:
  $ cat ./apparmor.profile 
  #include 

  profile test {
#include 

/bin/bash ixr,
/dev/pts/* rw,
/usr/bin/flock ixr,
# Not blocked:
# aa-exec -p test -- flock -w 1 /tmp/test.lock -c true
/tmp/test.lock rw,

  }

  $ sudo apparmor_parser -r ./apparmor.profile

  $ aa-exec -p test -- flock -w 1 /tmp/test.lock -c true && echo yes
  yes

  $ ls -l /tmp/test.lock 
  -rw-rw-r-- 1 jamie jamie 0 Jan 20 15:57 /tmp/test.lock

  The flock command uses flock(LOCK_EX) and I expected it to be blocked
  due to the lack of 'k'.

  apparmor userspace 2.10.95-0ubuntu2.5 (xenial) and 4.9.0-12.13-generic
  kernel on amd64.

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

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

[Kernel-packages] [Bug 1648903] Re: Permission denied and inconsistent behavior in complain mode with 'ip netns list' command

FYI, this issue was hitting snapcrafters on Raspberry Pi3
(https://lists.ubuntu.com/archives/snapcraft/2017-February/003366.html).
Please also update the other reference kernels and snaps. Thanks!

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

Title:
  Permission denied and inconsistent behavior in complain mode with 'ip
  netns list' command

Status in AppArmor:
  In Progress
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

Bug description:
  On 16.04 with Ubuntu 4.4.0-53.74-generic 4.4.30

  With this profile:

  #include 

  profile test (attach_disconnected,complain) {
  #include 

  /{,usr/}{,s}bin/ip ixr,  # COMMENT OUT THIS RULE TO SEE WEIRDNESS

  capability sys_admin,
  capability net_admin,
  capability sys_ptrace,

  network netlink raw,

  ptrace (trace),

  / r,
  /run/netns/ rw,
  /run/netns/* rw,

  mount options=(rw, rshared) -> /run/netns/,
  mount options=(rw, bind) /run/netns/ -> /run/netns/,
  mount options=(rw, bind) / -> /run/netns/*,
  mount options=(rw, rslave) /,
  mount options=(rw, rslave), # LP: #1648245
  umount /sys/,
  umount /,

  
  /bin/dash ixr,
  }

  Everything is fine when I do:
  $ sudo apparmor_parser -r /home/jamie/apparmor.profile && sudo aa-exec -p 
test -- sh -c 'ip netns list'
  $

  and there are no ALLOWED entries in syslog.

  
  However, if I comment out the '/{,usr/}{,s}bin/ip ixr,' rule, I get a 
permission denied and a bunch of ALLOWED entries:

  $ sudo apparmor_parser -r /home/jamie/apparmor.profile && sudo aa-exec -p 
test -- sh -c 'ip netns list'
  open("/proc/self/ns/net"): Permission denied
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.862629] audit: type=1400 
audit(1481324889.782:469): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="test" pid=4314 comm="apparmor_parser"
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870339] audit: type=1400 
audit(1481324889.790:470): apparmor="ALLOWED" operation="exec" profile="test" 
name="/bin/ip" pid=4317 comm="sh" requested_mask="x" denied_mask="x" fsuid=0 
ouid=0 target="test//null-/bin/ip"
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870559] audit: type=1400 
audit(1481324889.790:471): apparmor="ALLOWED" operation="open" 
profile="test//null-/bin/ip" name="/etc/ld.so.cache" pid=4317 comm="ip" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870628] audit: type=1400 
audit(1481324889.790:472): apparmor="ALLOWED" operation="open" 
profile="test//null-/bin/ip" name="/lib/x86_64-linux-gnu/libdl-2.23.so" 
pid=4317 comm="ip" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870703] audit: type=1400 
audit(1481324889.790:473): apparmor="ALLOWED" operation="open" 
profile="test//null-/bin/ip" name="/lib/x86_64-linux-gnu/libc-2.23.so" pid=4317 
comm="ip" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870861] audit: type=1400 
audit(1481324889.790:474): apparmor="ALLOWED" operation="file_mprotect" 
profile="test//null-/bin/ip" name="/bin/ip" pid=4317 comm="ip" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870913] audit: type=1400 
audit(1481324889.790:475): apparmor="ALLOWED" operation="file_mprotect" 
profile="test//null-/bin/ip" name="/lib/x86_64-linux-gnu/ld-2.23.so" pid=4317 
comm="ip" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.871019] audit: type=1400 
audit(1481324889.790:476): apparmor="ALLOWED" operation="create" 
profile="test//null-/bin/ip" pid=4317 comm="ip" family="netlink" 
sock_type="raw" protocol=0 requested_mask="create" denied_mask="create"
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.871066] audit: type=1400 
audit(1481324889.790:477): apparmor="ALLOWED" operation="setsockopt" 
profile="test//null-/bin/ip" pid=4317 comm="ip" family="netlink" 
sock_type="raw" protocol=0 requested_mask="setopt" denied_mask="setopt"
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.871099] audit: type=1400 
audit(1481324889.790:478): apparmor="ALLOWED" operation="setsockopt" 
profile="test//null-/bin/ip" pid=4317 comm="ip" family="netlink" 
sock_type="raw" protocol=0 requested_mask="setopt" denied_mask="setopt"
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.871128] audit: type=1400 
audit(1481324889.790:479): apparmor="ALLOWED" operation="bind" 
profile="test//null-/bin/ip" pid=4317 comm="ip" family="netlink" 
sock_type="raw" protocol=0 requested_mask="bind" denied_mask="bind"
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.871672] audit: type=1400 
audit(1481324889.794:480): apparmor="ALLOWED" operation="getsockname" 
profile="test//null-/bin/ip" pid=4317 comm="ip"

[Kernel-packages] [Bug 1668373] [NEW] Kernel versions 4.4.0-21 to 4.4.0-64 don't work with nvidia discrete graphics adapter

2017-02-27 Thread Isaak Babaev

Public bug reported:

Switching from ubuntu 14.04 to ubuntu 16.04 I am having trouble using
nvidia discrete graphics adapter when trying to switch b/w intel GPU and
Nvidia GPU. When I switched back from ubuntu 16.04 to 14.04 and tried to
upgrade the kernel from 3.19.0-80 to kernel versions 4.4.0-21 until
4.4.0-64 the graphics driver starts to malfunction and can't switch b/w
the GPUs, while it works fine with kernel versions 3.19.0-x.  Please
look into the problem, and thanks in advance for your help.

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

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

Title:
  Kernel versions 4.4.0-21 to 4.4.0-64 don't work with nvidia discrete
  graphics adapter

Status in linux-lts-vivid package in Ubuntu:
  New

Bug description:
  Switching from ubuntu 14.04 to ubuntu 16.04 I am having trouble using
  nvidia discrete graphics adapter when trying to switch b/w intel GPU
  and Nvidia GPU. When I switched back from ubuntu 16.04 to 14.04 and
  tried to upgrade the kernel from 3.19.0-80 to kernel versions 4.4.0-21
  until 4.4.0-64 the graphics driver starts to malfunction and can't
  switch b/w the GPUs, while it works fine with kernel versions
  3.19.0-x.  Please look into the problem, and thanks in advance for
  your help.

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

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

[Kernel-packages] [Bug 1648903] Re: Permission denied and inconsistent behavior in complain mode with 'ip netns list' command

Confirmed this bug is fixed with 4.8.0-40.43-generic on yakkety.

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

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

Title:
  Permission denied and inconsistent behavior in complain mode with 'ip
  netns list' command

Status in AppArmor:
  In Progress
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

Bug description:
  On 16.04 with Ubuntu 4.4.0-53.74-generic 4.4.30

  With this profile:

  #include 

  profile test (attach_disconnected,complain) {
  #include 

  /{,usr/}{,s}bin/ip ixr,  # COMMENT OUT THIS RULE TO SEE WEIRDNESS

  capability sys_admin,
  capability net_admin,
  capability sys_ptrace,

  network netlink raw,

  ptrace (trace),

  / r,
  /run/netns/ rw,
  /run/netns/* rw,

  mount options=(rw, rshared) -> /run/netns/,
  mount options=(rw, bind) /run/netns/ -> /run/netns/,
  mount options=(rw, bind) / -> /run/netns/*,
  mount options=(rw, rslave) /,
  mount options=(rw, rslave), # LP: #1648245
  umount /sys/,
  umount /,

  
  /bin/dash ixr,
  }

  Everything is fine when I do:
  $ sudo apparmor_parser -r /home/jamie/apparmor.profile && sudo aa-exec -p 
test -- sh -c 'ip netns list'
  $

  and there are no ALLOWED entries in syslog.

  
  However, if I comment out the '/{,usr/}{,s}bin/ip ixr,' rule, I get a 
permission denied and a bunch of ALLOWED entries:

  $ sudo apparmor_parser -r /home/jamie/apparmor.profile && sudo aa-exec -p 
test -- sh -c 'ip netns list'
  open("/proc/self/ns/net"): Permission denied
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.862629] audit: type=1400 
audit(1481324889.782:469): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="test" pid=4314 comm="apparmor_parser"
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870339] audit: type=1400 
audit(1481324889.790:470): apparmor="ALLOWED" operation="exec" profile="test" 
name="/bin/ip" pid=4317 comm="sh" requested_mask="x" denied_mask="x" fsuid=0 
ouid=0 target="test//null-/bin/ip"
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870559] audit: type=1400 
audit(1481324889.790:471): apparmor="ALLOWED" operation="open" 
profile="test//null-/bin/ip" name="/etc/ld.so.cache" pid=4317 comm="ip" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870628] audit: type=1400 
audit(1481324889.790:472): apparmor="ALLOWED" operation="open" 
profile="test//null-/bin/ip" name="/lib/x86_64-linux-gnu/libdl-2.23.so" 
pid=4317 comm="ip" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870703] audit: type=1400 
audit(1481324889.790:473): apparmor="ALLOWED" operation="open" 
profile="test//null-/bin/ip" name="/lib/x86_64-linux-gnu/libc-2.23.so" pid=4317 
comm="ip" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870861] audit: type=1400 
audit(1481324889.790:474): apparmor="ALLOWED" operation="file_mprotect" 
profile="test//null-/bin/ip" name="/bin/ip" pid=4317 comm="ip" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870913] audit: type=1400 
audit(1481324889.790:475): apparmor="ALLOWED" operation="file_mprotect" 
profile="test//null-/bin/ip" name="/lib/x86_64-linux-gnu/ld-2.23.so" pid=4317 
comm="ip" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.871019] audit: type=1400 
audit(1481324889.790:476): apparmor="ALLOWED" operation="create" 
profile="test//null-/bin/ip" pid=4317 comm="ip" family="netlink" 
sock_type="raw" protocol=0 requested_mask="create" denied_mask="create"
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.871066] audit: type=1400 
audit(1481324889.790:477): apparmor="ALLOWED" operation="setsockopt" 
profile="test//null-/bin/ip" pid=4317 comm="ip" family="netlink" 
sock_type="raw" protocol=0 requested_mask="setopt" denied_mask="setopt"
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.871099] audit: type=1400 
audit(1481324889.790:478): apparmor="ALLOWED" operation="setsockopt" 
profile="test//null-/bin/ip" pid=4317 comm="ip" family="netlink" 
sock_type="raw" protocol=0 requested_mask="setopt" denied_mask="setopt"
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.871128] audit: type=1400 
audit(1481324889.790:479): apparmor="ALLOWED" operation="bind" 
profile="test//null-/bin/ip" pid=4317 comm="ip" family="netlink" 
sock_type="raw" protocol=0 requested_mask="bind" denied_mask="bind"
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.871672] audit: type=1400 
audit(1481324889.794:480): apparmor="ALLOWED" operation="getsockname" 
profile="test//null-/bin/ip" pid=4317 comm="ip" family="netlink" 
sock_type="raw" protocol=0

[Kernel-packages] [Bug 1648903] Re: Permission denied and inconsistent behavior in complain mode with 'ip netns list' command

Confirmed this bug is fixed with 4.4.0-65.86-generic on xenial.

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

** Changed in: apparmor
   Status: New => In Progress

** Changed in: apparmor
 Assignee: (unassigned) => John Johansen (jjohansen)

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

Title:
  Permission denied and inconsistent behavior in complain mode with 'ip
  netns list' command

Status in AppArmor:
  In Progress
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

Bug description:
  On 16.04 with Ubuntu 4.4.0-53.74-generic 4.4.30

  With this profile:

  #include 

  profile test (attach_disconnected,complain) {
  #include 

  /{,usr/}{,s}bin/ip ixr,  # COMMENT OUT THIS RULE TO SEE WEIRDNESS

  capability sys_admin,
  capability net_admin,
  capability sys_ptrace,

  network netlink raw,

  ptrace (trace),

  / r,
  /run/netns/ rw,
  /run/netns/* rw,

  mount options=(rw, rshared) -> /run/netns/,
  mount options=(rw, bind) /run/netns/ -> /run/netns/,
  mount options=(rw, bind) / -> /run/netns/*,
  mount options=(rw, rslave) /,
  mount options=(rw, rslave), # LP: #1648245
  umount /sys/,
  umount /,

  
  /bin/dash ixr,
  }

  Everything is fine when I do:
  $ sudo apparmor_parser -r /home/jamie/apparmor.profile && sudo aa-exec -p 
test -- sh -c 'ip netns list'
  $

  and there are no ALLOWED entries in syslog.

  
  However, if I comment out the '/{,usr/}{,s}bin/ip ixr,' rule, I get a 
permission denied and a bunch of ALLOWED entries:

  $ sudo apparmor_parser -r /home/jamie/apparmor.profile && sudo aa-exec -p 
test -- sh -c 'ip netns list'
  open("/proc/self/ns/net"): Permission denied
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.862629] audit: type=1400 
audit(1481324889.782:469): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="test" pid=4314 comm="apparmor_parser"
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870339] audit: type=1400 
audit(1481324889.790:470): apparmor="ALLOWED" operation="exec" profile="test" 
name="/bin/ip" pid=4317 comm="sh" requested_mask="x" denied_mask="x" fsuid=0 
ouid=0 target="test//null-/bin/ip"
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870559] audit: type=1400 
audit(1481324889.790:471): apparmor="ALLOWED" operation="open" 
profile="test//null-/bin/ip" name="/etc/ld.so.cache" pid=4317 comm="ip" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870628] audit: type=1400 
audit(1481324889.790:472): apparmor="ALLOWED" operation="open" 
profile="test//null-/bin/ip" name="/lib/x86_64-linux-gnu/libdl-2.23.so" 
pid=4317 comm="ip" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870703] audit: type=1400 
audit(1481324889.790:473): apparmor="ALLOWED" operation="open" 
profile="test//null-/bin/ip" name="/lib/x86_64-linux-gnu/libc-2.23.so" pid=4317 
comm="ip" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870861] audit: type=1400 
audit(1481324889.790:474): apparmor="ALLOWED" operation="file_mprotect" 
profile="test//null-/bin/ip" name="/bin/ip" pid=4317 comm="ip" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870913] audit: type=1400 
audit(1481324889.790:475): apparmor="ALLOWED" operation="file_mprotect" 
profile="test//null-/bin/ip" name="/lib/x86_64-linux-gnu/ld-2.23.so" pid=4317 
comm="ip" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.871019] audit: type=1400 
audit(1481324889.790:476): apparmor="ALLOWED" operation="create" 
profile="test//null-/bin/ip" pid=4317 comm="ip" family="netlink" 
sock_type="raw" protocol=0 requested_mask="create" denied_mask="create"
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.871066] audit: type=1400 
audit(1481324889.790:477): apparmor="ALLOWED" operation="setsockopt" 
profile="test//null-/bin/ip" pid=4317 comm="ip" family="netlink" 
sock_type="raw" protocol=0 requested_mask="setopt" denied_mask="setopt"
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.871099] audit: type=1400 
audit(1481324889.790:478): apparmor="ALLOWED" operation="setsockopt" 
profile="test//null-/bin/ip" pid=4317 comm="ip" family="netlink" 
sock_type="raw" protocol=0 requested_mask="setopt" denied_mask="setopt"
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.871128] audit: type=1400 
audit(1481324889.790:479): apparmor="ALLOWED" operation="bind" 
profile="test//null-/bin/ip" pid=4317 comm="ip" family="netlink" 
sock_type="raw" protocol=0 requested_mask="bind" denied_mask="bind"
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.871672] audit: type=1400 
audit(1481324889.794:480):

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

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-40.43-generic/gonzo__4.8.0-40.43__2017-02-27_18-57-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/1667066

Title:
  linux: 4.8.0-40.43 -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:
  Confirmed
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 Yakkety:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  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/1667066/+subscriptions

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

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

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

Title:
  Hard lockup after 4 hours uptime

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We have recently deployed intel NUC6i5 devices in store for POS
  display and are encountering strange inexplicable freezes on several
  devices.

  What is very strange is that all devices are freezing exactly 4h after
  boot.

  We have had this exact same issue on more than 20 devices (over 100),
  with parts from different batches, and all did freeze exactly 4h after
  boot (but it's not reproducible, it won't freeze every day). Some
  devices are playing MPV videos, while other run chromium. They are
  running non-stop, but are all rebooting daily at 05h05.

  Looks like it might be related to https://lkml.org/lkml/2015/6/11/787

  That seem to have been fixed and backported already
  https://lkml.org/lkml/2015/10/17/259

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-64-generic 4.4.0-64.85
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Mon Feb 27 21:06:44 2017
  InstallationDate: Installed on 2016-06-08 (264 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 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=1f60f9c9-bbf1-45df-bdc3-9b4da883839e ro quiet splash net.ifnames=0 
vt.handoff=7
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.board.name: NUC6i5SYB

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

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

[Kernel-packages] [Bug 1648903] Re: Permission denied and inconsistent behavior in complain mode with 'ip netns list' command

This is fixed with 4.10.0-8.10-generic. Marking zesty task as fixed.

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

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

Title:
  Permission denied and inconsistent behavior in complain mode with 'ip
  netns list' command

Status in AppArmor:
  New
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

Bug description:
  On 16.04 with Ubuntu 4.4.0-53.74-generic 4.4.30

  With this profile:

  #include 

  profile test (attach_disconnected,complain) {
  #include 

  /{,usr/}{,s}bin/ip ixr,  # COMMENT OUT THIS RULE TO SEE WEIRDNESS

  capability sys_admin,
  capability net_admin,
  capability sys_ptrace,

  network netlink raw,

  ptrace (trace),

  / r,
  /run/netns/ rw,
  /run/netns/* rw,

  mount options=(rw, rshared) -> /run/netns/,
  mount options=(rw, bind) /run/netns/ -> /run/netns/,
  mount options=(rw, bind) / -> /run/netns/*,
  mount options=(rw, rslave) /,
  mount options=(rw, rslave), # LP: #1648245
  umount /sys/,
  umount /,

  
  /bin/dash ixr,
  }

  Everything is fine when I do:
  $ sudo apparmor_parser -r /home/jamie/apparmor.profile && sudo aa-exec -p 
test -- sh -c 'ip netns list'
  $

  and there are no ALLOWED entries in syslog.

  
  However, if I comment out the '/{,usr/}{,s}bin/ip ixr,' rule, I get a 
permission denied and a bunch of ALLOWED entries:

  $ sudo apparmor_parser -r /home/jamie/apparmor.profile && sudo aa-exec -p 
test -- sh -c 'ip netns list'
  open("/proc/self/ns/net"): Permission denied
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.862629] audit: type=1400 
audit(1481324889.782:469): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="test" pid=4314 comm="apparmor_parser"
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870339] audit: type=1400 
audit(1481324889.790:470): apparmor="ALLOWED" operation="exec" profile="test" 
name="/bin/ip" pid=4317 comm="sh" requested_mask="x" denied_mask="x" fsuid=0 
ouid=0 target="test//null-/bin/ip"
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870559] audit: type=1400 
audit(1481324889.790:471): apparmor="ALLOWED" operation="open" 
profile="test//null-/bin/ip" name="/etc/ld.so.cache" pid=4317 comm="ip" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870628] audit: type=1400 
audit(1481324889.790:472): apparmor="ALLOWED" operation="open" 
profile="test//null-/bin/ip" name="/lib/x86_64-linux-gnu/libdl-2.23.so" 
pid=4317 comm="ip" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870703] audit: type=1400 
audit(1481324889.790:473): apparmor="ALLOWED" operation="open" 
profile="test//null-/bin/ip" name="/lib/x86_64-linux-gnu/libc-2.23.so" pid=4317 
comm="ip" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870861] audit: type=1400 
audit(1481324889.790:474): apparmor="ALLOWED" operation="file_mprotect" 
profile="test//null-/bin/ip" name="/bin/ip" pid=4317 comm="ip" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870913] audit: type=1400 
audit(1481324889.790:475): apparmor="ALLOWED" operation="file_mprotect" 
profile="test//null-/bin/ip" name="/lib/x86_64-linux-gnu/ld-2.23.so" pid=4317 
comm="ip" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.871019] audit: type=1400 
audit(1481324889.790:476): apparmor="ALLOWED" operation="create" 
profile="test//null-/bin/ip" pid=4317 comm="ip" family="netlink" 
sock_type="raw" protocol=0 requested_mask="create" denied_mask="create"
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.871066] audit: type=1400 
audit(1481324889.790:477): apparmor="ALLOWED" operation="setsockopt" 
profile="test//null-/bin/ip" pid=4317 comm="ip" family="netlink" 
sock_type="raw" protocol=0 requested_mask="setopt" denied_mask="setopt"
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.871099] audit: type=1400 
audit(1481324889.790:478): apparmor="ALLOWED" operation="setsockopt" 
profile="test//null-/bin/ip" pid=4317 comm="ip" family="netlink" 
sock_type="raw" protocol=0 requested_mask="setopt" denied_mask="setopt"
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.871128] audit: type=1400 
audit(1481324889.790:479): apparmor="ALLOWED" operation="bind" 
profile="test//null-/bin/ip" pid=4317 comm="ip" family="netlink" 
sock_type="raw" protocol=0 requested_mask="bind" denied_mask="bind"
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.871672] audit: type=1400 
audit(1481324889.794:480): apparmor="ALLOWED" operation="getsockname" 
profile="test//null-/bin/ip" pid=4317 comm="ip" family="netlink" 
sock_type="raw" protocol=0 requested_mask="getattr"

[Kernel-packages] [Bug 1667531] Re: [Hyper-V] Include bondvf in /usr/sbin for SR-IOV interface bonding

2017-02-27 Thread Haiyang Zhang

Please include this pending patch:
http://patchwork.ozlabs.org/patch/73/

[net-next] tools: hv: Add clean up function for Ubuntu config
This patch adds a function to clean up duplicate config info
on Ubuntu.

Signed-off-by: Haiyang Zhang 
---
 tools/hv/bondvf.sh |   18 ++
 1 files changed, 18 insertions(+), 0 deletions(-)

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

Title:
  [Hyper-V] Include bondvf in /usr/sbin for SR-IOV interface bonding

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

Bug description:
  Please include bondvf.sh from kernel git tools/hv/ in /usr/sbin

  commit fd7aabb062fa1a8331a786d617744de220eaf002
  Author: Haiyang Zhang 
  Date:   Fri Dec 2 15:55:38 2016 -0800

  tools: hv: Enable network manager for bonding scripts on RHEL

  We found network manager is necessary on RHEL to make the synthetic
  NIC, VF NIC bonding operations handled automatically. So, enabling
  network manager here.

  Signed-off-by: Haiyang Zhang 
  Reviewed-by: K. Y. Srinivasan 
  Signed-off-by: David S. Miller 

  commit 178cd55f086629cf0bad9c66c793a7e2bcc3abb6
  Author: Haiyang Zhang 
  Date:   Mon Jul 11 17:06:42 2016 -0700

  tools: hv: Add a script to help bonding synthetic and VF NICs

  This script helps to create bonding network devices based on synthetic NIC
  (the virtual network adapter usually provided by Hyper-V) and the matching
  VF NIC (SRIOV virtual function). So the synthetic NIC and VF NIC can
  function as one network device, and fail over to the synthetic NIC if VF 
is
  down.

  Mayjor distros (RHEL, Ubuntu, SLES) supported by Hyper-V are supported by
  this script.

  Signed-off-by: Haiyang Zhang 
  Reviewed-by: K. Y. Srinivasan 
  Signed-off-by: David S. Miller 

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

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

[Kernel-packages] [Bug 1632458] Re: [Ubuntu 16.10] - System crashes and gives out call traces when libhugetlbfs test suite is run.

2017-02-27 Thread Leann Ogasawara

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

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

** Changed in: linux (Ubuntu)
 Assignee: Taco Screen team (taco-screen-team) => Canonical Kernel Team 
(canonical-kernel-team)

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

Title:
  [Ubuntu 16.10] - System crashes and gives out call traces when
  libhugetlbfs test suite is run.

Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - Santhosh G  - 2016-09-27 01:55:00 ==
  Issue:
  Kernel unable to handle page request when heapshrink test case is run from 
libhugetlbfs suite.

  Environment:
  arch - ppc64le
  ubuntu kvm guest

  Host related Info:
  Kernel:
  -
  uname -a
  Linux ltc-haba1 4.8.0-17-generic #19-Ubuntu SMP Sun Sep 25 06:35:40 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  Memory:
  
  oot@ltc-haba1:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   255G 65G187G 22M1.9G
188G
  Swap:  225G  0B225G

  Hugepages configured:
  
  root@ltc-haba1:~# cat /proc/meminfo | grep -i Huge
  AnonHugePages: 81920 kB
  ShmemHugePages:0 kB
  HugePages_Total:4096
  HugePages_Free: 3584
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:  16384 kB

  
  Guest Related Info:
  --
  -
  Kernel:
  -
  root@ubuntu:~/libhugetlbfs# uname -a
  Linux ubuntu 4.8.0-17-generic #19-Ubuntu SMP Sun Sep 25 06:35:40 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  Memory:
  -
  root@ubuntu:~/libhugetlbfs# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   8.0G133M7.7G 15M132M
7.5G
  Swap:  3.3G  0B3.3G

  Hugepages configured:
  ---
  root@ubuntu:~/libhugetlbfs# cat /proc/meminfo | grep -i Huge
  AnonHugePages: 0 kB
  ShmemHugePages:0 kB
  HugePages_Total: 256
  HugePages_Free:  256
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:  16384 kB

  
  Steps to reproduce:
  1- Install a ubuntu kvm guest with hugepages memory Backing.
  2 - git clone the latest libhugetlbfs from 
https://github.com/libhugetlbfs/libhugetlbfs.git
  3 - configure huge[pages in guest and run make check.

  xmon is configured in the system .
  The system gets call traces and enters xmon console:

  HUGETLB_VERBOSE=1 HUGETLB_MORECORE=yes heap-overflow (16M: 64):   [  
281.735713] Unable to handle kernel paging request for data at address 
0x42328e38
  [  281.735804] Faulting instruction address: 0xc027b410
  cpu 0x1: Vector: 300 (Data Access) at [c001fa8c3730]
  pc: c027b410: shrink_active_list+0x300/0x4d0
  lr: c027b3f4: shrink_active_list+0x2e4/0x4d0
  sp: c001fa8c39b0
 msr: 80010280b033
 dar: 42328e38
   dsisr: 4200
current = 0xc001fa8adc00
paca= 0xcfb80900 softe: 0irq_happened: 0x01
  pid   = 50, comm = kswapd0
  Linux version 4.8.0-17-generic (buildd@bos01-ppc64el-025) (gcc version 6.2.0 
20160914 (Ubuntu 6.2.0-3ubuntu15) ) #19-Ubuntu SMP Sun Sep 25 06:35:40 UTC 2016 
(Ubuntu 4.8.0-17.19-generic 4.8.0-rc7)
  enter ? for help
  [c001fa8c3aa0] c027bbdc shrink_node_memcg+0x5fc/0x800
  [c001fa8c3bc0] c027bf0c shrink_node+0x12c/0x3f0
  [c001fa8c3c80] c027d500 kswapd+0x460/0x990
  [c001fa8c3d80] c00fd120 kthread+0x110/0x130
  [c001fa8c3e30] c00098f0 ret_from_kernel_thread+0x5c/0x6c

  xmon logs:

  1:mon> e
  cpu 0x1: Vector: 300 (Data Access) at [c001fa8e7730]
  pc: c027b410: shrink_active_list+0x300/0x4d0
  lr: c027b3f4: shrink_active_list+0x2e4/0x4d0
  sp: c001fa8e79b0
 msr: 80010280b033
 dar: 420c58d0
   dsisr: 4200
current = 0xc001fa8a
paca= 0xcfb80900 softe: 0irq_happened: 0x01
  pid   = 50, comm = kswapd0
  Linux version 4.8.0-17-generic (buildd@bos01-ppc64el-025) (gcc version 6.2.0 
20160914 (Ubuntu 6.2.0-3ubuntu15) ) #19-Ubuntu SMP Sun Sep 25 06:35:40 UTC 2016 
(Ubuntu 4.8.0-17.19-generic 4.8.0-rc7)

  1:mon> r
  R00 = c027b3f4   R16 = c001fffcfe00
  R01 = c001fa8e79b0   R17 = 010a
  R02 = c14e5e00   R18 = 420cbdd0
  R03 = 0001   R19 = c001fffc6300
  R04 = 0005   R20 = c001fa8e79e0
  R05 =    R21 =

[Kernel-packages] [Bug 1661030] Re: regession tests failing after stackprofile test is run

2017-02-27 Thread Colin Ian King

tested and verified it is fixed on Ubuntu Xenial with -proposed kernel
4.4.0-64 #86

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

Title:
  regession tests failing after stackprofile test is run

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

Bug description:
  from source, I'm running the tests and the makefile fails at the end
  with:

  running stackprofile
  Makefile:303: recipe for target 'tests' failed
  make: *** [tests] Error 1

  No idea why that is happening. It's breaking on our kernel team
  regression tests runs, so can this be investigated?  The source was
  fetched using "apt-get source apparmor".

  A full run is below:

  king@ubuntu:~/apparmor-2.10.95/tests/regression/apparmor$ sudo make
  USE_SYSTEM=1 tests

  running aa_exec

  running access
  xfail: ACCESS file rx (r)
  xfail: ACCESS file rwx (r)
  xfail: ACCESS file r (wx)
  xfail: ACCESS file rx (wx)
  xfail: ACCESS file rwx (wx)
  xfail: ACCESS dir rwx (r)
  xfail: ACCESS dir r (wx)
  xfail: ACCESS dir rx (wx)
  xfail: ACCESS dir rwx (wx)

  running at_secure

  running introspect

  running capabilities
  (ptrace)
  (sethostname)
  (setdomainname)
  (setpriority)
  (setscheduler)
  (reboot)
  (chroot)
  (mlockall)
  (net_raw)
  (ioperm)
  (iopl)

  running changeprofile

  running onexec

  running changehat

  running changehat_fork

  running changehat_misc

  *** A 'Killed' message from bash is expected for the following test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12503 Killed  $testexec "$@" > $outfile 2>&1

  *** A 'Killed' message from bash is expected for the following test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12537 Killed  $testexec "$@" > $outfile 2>&1

  running chdir

  running clone

  running coredump
  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12803 Segmentation fault  (core dumped) $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12833 Segmentation fault  $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12869 Segmentation fault  $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12905 Segmentation fault  $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12941 Segmentation fault  $testexec "$@" > $outfile 2>&1
  XFAIL: Error: corefile present when not expected -- COREDUMP (ix confinement)

  running deleted

  running environ
  Fatal Error (environ): Unable to run test sub-executable

  running exec

  running exec_qual

  running fchdir

  running fd_inheritance

  running fork

  running i18n

  running link

  running link_subset

  running mkdir

  running mmap

  running mount
  using mount rules ...

  running mult_mount

  running named_pipe

  running namespaces

  running net_raw

  running open

  running openat

  running pipe

  running pivot_root

  running ptrace
 using ptrace v6 tests ...

  running pwrite

  running query_label
  Alert: query_label passed. Test 'QUERY file (all base perms #1)' was marked 
as expected pass but known problem (xpass)
  xpass: QUERY file (all base perms #1)
  Alert: query_label passed. Test 'QUERY file (all base perms #2)' was marked 
as expected pass but known problem (xpass)
  xpass: QUERY file (all base perms #2)

  running regex

  running rename

  running readdir

  running rw

  running socketpair

  running swap
  mkswap: /tmp/sdtest.21272-20356-eRXvtR/swapfile: insecure permissions 0644, 
0600 suggested.
  swapon: /tmp/sdtest.21272-20356-eRXvtR/swapfile: insecure permissions 0644, 
0600 suggested.

  running sd_flags

  running setattr

[Kernel-packages] [Bug 1628988] Re: ISST-LTE:Ubuntu1610: UbuntuKVM 16.10 guest crashed after 30 hours of stress testing

2017-02-27 Thread Michael Hohnbaum

** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/1628988

Title:
  ISST-LTE:Ubuntu1610: UbuntuKVM 16.10 guest crashed after 30 hours of
  stress testing

Status in linux package in Ubuntu:
  Invalid

Bug description:
  After running Stress tests for 30 hours, Ubuntu16.10 KVM guest crashed
  and entered xmon.

  Guest Build:
  --
  4.8.0-16-generic

  Tests started on guest:
  --
  BASE: LTP Base tests.. 
  IO: admndisk, aio, fstest tests (on btrfs file system over 6 partitions of 2 
disks).
  TCP: TCP commands: telnet, ssh, rlogin, ping etc..

  XMON traces:
  --
  4:mon> t
  [c0017ffcf800] c024385c end_page_writeback+0x7c/0x120
  [c0017ffcf830] d22d8298 ext4_finish_bio+0x1f0/0x2e0 [ext4]
  [c0017ffcf910] d22d8928 ext4_end_bio+0x70/0x170 [ext4]
  [c0017ffcf9a0] c04c96cc bio_endio+0xfc/0x120
  [c0017ffcf9d0] c04d5f50 blk_update_request+0xf0/0x4d0
  [c0017ffcfa60] c06df2dc scsi_end_request+0x6c/0x260
  [c0017ffcfad0] c06e32a4 scsi_io_completion+0x2d4/0x740
  [c0017ffcfba0] c06d6714 scsi_finish_command+0x144/0x200
  [c0017ffcfc20] c06e25a8 scsi_softirq_done+0x198/0x200
  [c0017ffcfca0] c04e2e98 __blk_mq_complete_request_remote+0x38/0x50
  [c0017ffcfcd0] c0183e80 flush_smp_call_function_queue+0xd0/0x220
  [c0017ffcfd50] c0047aac smp_ipi_demux+0xac/0x110
  [c0017ffcfd90] c00738e4 icp_hv_ipi_action+0x64/0xd0
  [c0017ffcfe00] c01466d0 __handle_irq_event_percpu+0x90/0x340
  [c0017ffcfec0] c01469bc handle_irq_event_percpu+0x3c/0x90
  [c0017ffcff00] c014ced4 handle_percpu_irq+0x84/0xd0
  [c0017ffcff30] c0145664 generic_handle_irq+0x54/0x80
  [c0017ffcff60] c0015b20 __do_irq+0x80/0x230
  [c0017ffcff90] c002a2e0 call_do_irq+0x14/0x24
  [c0013073b210] c0015d68 do_IRQ+0x98/0x140
  [c0013073b260] c00026d8 hardware_interrupt_common+0x158/0x180
  --- Exception: 501 (Hardware Interrupt) at c008fe4c 
plpar_hcall_norets+0x1c/0x28
  [link register   ] c006c094 __spin_yield+0xa4/0xb0
  [c0013073b550] c0017fe28b00 (unreliable)
  [c0013073b5c0] c0949758 _raw_spin_lock_irqsave+0x128/0x130
  [c0013073b600] d17222cc ibmvscsi_queuecommand+0x54/0x4b0 
[ibmvscsi]
  [c0013073b6b0] c06dfc80 scsi_dispatch_cmd+0x140/0x370
  [c0013073b730] c06e1ad0 scsi_queue_rq+0x770/0x920
  [c0013073b800] c04e62f4 __blk_mq_run_hw_queue+0x2e4/0x570
  [c0013073b910] c04e5fc8 blk_mq_run_hw_queue+0xf8/0x140
  [c0013073b940] c04e8f90 blk_mq_flush_plug_list+0x160/0x1b0
  [c0013073b9c0] c04d7fbc blk_flush_plug_list+0xfc/0x2b0
  [c0013073ba30] c04d8708 blk_finish_plug+0x58/0x80
  [c0013073ba60] d22d270c ext4_writepages+0x6c4/0xe60 [ext4]
  [c0013073bbf0] c025ae80 do_writepages+0x60/0xc0
  [c0013073bc20] c0246c18 __filemap_fdatawrite_range+0x108/0x190
  [c0013073bcc0] c0246f20 filemap_write_and_wait_range+0x70/0xf0
  [c0013073bd00] d22c5944 ext4_sync_file+0x24c/0x5a0 [ext4]
  [c0013073bd60] c0365a28 vfs_fsync_range+0x78/0x130
  [c0013073bdb0] c0365b90 do_fsync+0x60/0xb0
  [c0013073be00] c0366000 SyS_fsync+0x30/0x50
  [c0013073be30] c00095e0 system_call+0x38/0x108
  --- Exception: c00 (System Call) at 3fff7b26cc98
  SP (3fffc42b5280) is in userspace
  4:mon> e
  cpu 0x4: Vector: 300 (Data Access) at [c0017ffcf520]
  pc: c025b4ec: test_clear_page_writeback+0x1ec/0x300
  lr: c025b4c0: test_clear_page_writeback+0x1c0/0x300
  sp: c0017ffcf7a0
 msr: 80009033
 dar: 2d0
   dsisr: 4000
current = 0xc00036f59880
paca= 0xc7b82400   softe: 0irq_happened: 0x09
  pid   = 1102, comm = create_datafile
  Linux version 4.8.0-16-generic (buildd@bos01-ppc64el-007) (gcc version 6.2.0 
20160914 (Ubuntu 6.2.0-3ubuntu15) ) #17-Ubuntu SMP Thu Sep 22 22:45:44 UTC 2016 
(Ubuntu 4.8.0-16.17-generic 4.8.0-rc7)
  4:mon>
  4:mon>
  4:mon> r
  R00 = c025b4c0   R16 = 0550
  R01 = c0017ffcf7a0   R17 = 7fff
  R02 = c10af400   R18 = 
  R03 =    R19 = c00172e35b00
  R04 =    R20 = c00035f831b0
  R05 = ffe0   R21 = 0001
  R06 = fffe   R22 = 0002
  R07 = f800   R23 = 0400
  R08 = 00017f18   R24 = 
  R09 =    R25 = c10f00c4
  R10 = 00017f18   R26 = 
  R11 = 0230

Re: [Kernel-packages] [Bug 1632458] Comment bridged from LTC Bugzilla

2017-02-27 Thread Michael Hohnbaum

Leann,

This one is now ready for the Kernel Team to evaluate.

 Michael


On 02/27/2017 10:19 AM, bugproxy wrote:
> --- Comment From laurent.duf...@fr.ibm.com 2017-02-27 13:11 EDT---
> (In reply to comment #33)
>> Question to IBM: have you made any progress towards identifying a patch to
>> address this issue?
> Yep fixed by https://patchwork.kernel.org/patch/9364805/
>

-- 
Michael Hohnbaum
OIL Program Manager
Power (ppc64el) Development Project Manager
Canonical, Ltd.

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

Title:
  [Ubuntu 16.10] - System crashes and gives out call traces when
  libhugetlbfs test suite is run.

Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - Santhosh G  - 2016-09-27 01:55:00 ==
  Issue:
  Kernel unable to handle page request when heapshrink test case is run from 
libhugetlbfs suite.

  Environment:
  arch - ppc64le
  ubuntu kvm guest

  Host related Info:
  Kernel:
  -
  uname -a
  Linux ltc-haba1 4.8.0-17-generic #19-Ubuntu SMP Sun Sep 25 06:35:40 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  Memory:
  
  oot@ltc-haba1:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   255G 65G187G 22M1.9G
188G
  Swap:  225G  0B225G

  Hugepages configured:
  
  root@ltc-haba1:~# cat /proc/meminfo | grep -i Huge
  AnonHugePages: 81920 kB
  ShmemHugePages:0 kB
  HugePages_Total:4096
  HugePages_Free: 3584
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:  16384 kB

  
  Guest Related Info:
  --
  -
  Kernel:
  -
  root@ubuntu:~/libhugetlbfs# uname -a
  Linux ubuntu 4.8.0-17-generic #19-Ubuntu SMP Sun Sep 25 06:35:40 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  Memory:
  -
  root@ubuntu:~/libhugetlbfs# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   8.0G133M7.7G 15M132M
7.5G
  Swap:  3.3G  0B3.3G

  Hugepages configured:
  ---
  root@ubuntu:~/libhugetlbfs# cat /proc/meminfo | grep -i Huge
  AnonHugePages: 0 kB
  ShmemHugePages:0 kB
  HugePages_Total: 256
  HugePages_Free:  256
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:  16384 kB

  
  Steps to reproduce:
  1- Install a ubuntu kvm guest with hugepages memory Backing.
  2 - git clone the latest libhugetlbfs from 
https://github.com/libhugetlbfs/libhugetlbfs.git
  3 - configure huge[pages in guest and run make check.

  xmon is configured in the system .
  The system gets call traces and enters xmon console:

  HUGETLB_VERBOSE=1 HUGETLB_MORECORE=yes heap-overflow (16M: 64):   [  
281.735713] Unable to handle kernel paging request for data at address 
0x42328e38
  [  281.735804] Faulting instruction address: 0xc027b410
  cpu 0x1: Vector: 300 (Data Access) at [c001fa8c3730]
  pc: c027b410: shrink_active_list+0x300/0x4d0
  lr: c027b3f4: shrink_active_list+0x2e4/0x4d0
  sp: c001fa8c39b0
 msr: 80010280b033
 dar: 42328e38
   dsisr: 4200
current = 0xc001fa8adc00
paca= 0xcfb80900 softe: 0irq_happened: 0x01
  pid   = 50, comm = kswapd0
  Linux version 4.8.0-17-generic (buildd@bos01-ppc64el-025) (gcc version 6.2.0 
20160914 (Ubuntu 6.2.0-3ubuntu15) ) #19-Ubuntu SMP Sun Sep 25 06:35:40 UTC 2016 
(Ubuntu 4.8.0-17.19-generic 4.8.0-rc7)
  enter ? for help
  [c001fa8c3aa0] c027bbdc shrink_node_memcg+0x5fc/0x800
  [c001fa8c3bc0] c027bf0c shrink_node+0x12c/0x3f0
  [c001fa8c3c80] c027d500 kswapd+0x460/0x990
  [c001fa8c3d80] c00fd120 kthread+0x110/0x130
  [c001fa8c3e30] c00098f0 ret_from_kernel_thread+0x5c/0x6c

  xmon logs:

  1:mon> e
  cpu 0x1: Vector: 300 (Data Access) at [c001fa8e7730]
  pc: c027b410: shrink_active_list+0x300/0x4d0
  lr: c027b3f4: shrink_active_list+0x2e4/0x4d0
  sp: c001fa8e79b0
 msr: 80010280b033
 dar: 420c58d0
   dsisr: 4200
current = 0xc001fa8a
paca= 0xcfb80900 softe: 0irq_happened: 0x01
  pid   = 50, comm = kswapd0
  Linux version 4.8.0-17-generic (buildd@bos01-ppc64el-025) (gcc version 6.2.0 
20160914 (Ubuntu 6.2.0-3ubuntu15) ) #19-Ubuntu SMP Sun Sep 25 06:35:40 UTC 2016 
(Ubuntu 4.8.0-17.19-generic 4.8.0-rc7)

  1:mon> r
  R00 = c027b3f4   R16 = c001fffcfe00

[Kernel-packages] [Bug 1652595] Re: Ubuntu 16.04.02: crash tool fails with error "cannot find 'cpu_possible_map', 'cpu_present_map', 'cpu_online_map' or 'cpu_active_map' symbols".

2017-02-27 Thread Manoj Iyer

The patch attached to comment #2 does not appear to be a fix for the
issue reported in this bug. Could you pls point me to an upstream fix
you might have identified that addresses this issue? I can make a best
effort in merging that patch in Ubuntu.

** Package changed: basemap (Ubuntu) => crash (Ubuntu)

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

** Changed in: crash (Ubuntu)
 Assignee: Taco Screen team (taco-screen-team) => Manoj Iyer (manjo)

** Changed in: makedumpfile (Ubuntu)
 Assignee: (unassigned) => Manoj Iyer (manjo)

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

Title:
  Ubuntu 16.04.02: crash tool fails with error "cannot find
  'cpu_possible_map', 'cpu_present_map', 'cpu_online_map' or
  'cpu_active_map' symbols".

Status in crash package in Ubuntu:
  New
Status in makedumpfile package in Ubuntu:
  New

Bug description:
  ---Problem Description---

  Ubuntu 16.04.02: crash tool fails with error "cannot find
  'cpu_possible_map', 'cpu_present_map', 'cpu_online_map' or
  'cpu_active_map' symbols".

  ---Steps to Reproduce---

  1. Install 16.04.02 [ 4.8.0-32-generic ].
  2. Configure kdump.
  3. Install debug package. 
  4. trigger crash.
  5. run crash tool on dump captured.

  sudo tee /etc/apt/sources.list.d/ddebs.list << EOF
  deb http://ddebs.ubuntu.com/ $(lsb_release -cs) main restricted universe 
multiverse
  deb http://ddebs.ubuntu.com/ $(lsb_release -cs)-security main restricted 
universe multiverse
  deb http://ddebs.ubuntu.com/ $(lsb_release -cs)-updates main restricted 
universe multiverse
  deb http://ddebs.ubuntu.com/ $(lsb_release -cs)-proposed main restricted 
universe multiverse
  EOF 

  sudo apt-get update
  sudo apt-get install linux-image-$(uname -r)-dbgsym  


  
  path: /var/crash/201612190432

  Logs
  ===

  root@ltc-haba2:/var/crash/201612190432# crash
  /usr/lib/debug/boot/vmlinux-4.8.0-32-generic dump.201612190432

  crash 7.1.4
  Copyright (C) 2002-2015  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.
   
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  
  crash: PPC64: cannot find 'cpu_possible_map', 'cpu_present_map', 
'cpu_online_map' or 'cpu_active_map' symbols

  
  It appears problem is with System.map-4.8.0-32-generic file 

  (gdb) symbol-file System.map-4.8.0-32-generic -readshow
  `/boot/System.map-4.8.0-32-generic': can't read symbols: File format not 
recognized.
  (gdb) 

  crash System.map-4.8.0-32-generic
  /usr/lib/debug/boot/vmlinux-4.8.0-32-generic
  /var/crash/201612260004/dump.201612260004

  crash 7.1.4
  Copyright (C) 2002-2015  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.
   
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

 
  crash: PPC64: cannot find 'cpu_possible_map', 'cpu_present_map', 
'cpu_online_map' or 'cpu_active_map' symbols

To manage

[Kernel-packages] [Bug 1509929] Re: kernel panic after booting up 4 hours

2017-02-27 Thread Olivier Louvignes

Looks like I'm encountering the exact same issue, in my case it's not
every single day, but happen quite often ~10% of our devices daily. I
opened a new bug report:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668356

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

Title:
  kernel panic after booting up 4 hours

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

Bug description:
  After upgrading to Wily from Vivid, I always meet kernal panic after
  booting up 4 hours;

  I use wireless, the Ethernet cable is not connected.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-16-generic 4.2.0-16.19
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alfred 5470 F pulseaudio
   /dev/snd/controlC0:  alfred 5470 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Oct 26 12:57:59 2015
  HibernationDevice: RESUME=UUID=a9831098-f784-41f9-b1f4-7f39b1040838
  InstallationDate: Installed on 2015-01-23 (275 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: LENOVO 20ANS01N00
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed 
root=UUID=cf490836-5dbd-4c19-8796-52575400a1f9 ro nomdmonddf nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.149
  SourcePackage: linux
  UpgradeStatus: Upgraded to wily on 2015-10-23 (2 days ago)
  dmi.bios.date: 06/23/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET79WW (2.33 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ANS01N00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0A46860 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET79WW(2.33):bd06/23/2015:svnLENOVO:pn20ANS01N00:pvrThinkPadT440p:rvnLENOVO:rn20ANS01N00:rvrSDK0A46860WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20ANS01N00
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1623750] Re: Request to backport cxlflash patches to Xenial SRU stream

2017-02-27 Thread Leann Ogasawara

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

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

** Changed in: linux (Ubuntu)
 Assignee: Taco Screen team (taco-screen-team) => Canonical Kernel Team 
(canonical-kernel-team)

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

Title:
  Request to backport cxlflash patches to Xenial SRU stream

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Problem Description
  ==
  There are a few patches in cxlflash that are in the process of getting 
upstream. We would like to have them pulled into Xenial SRU.

  Patches are,
  cxlflash: Scan host only after the port is ready for I/O
  cxlflash: Remove the device cleanly in the system shutdown path
  cxlflash: Fix to avoid EEH and host reset collisions
  cxlflash: Improve EEH recovery time

  These patches are applied to mkp's 4.9/scsi-queue. Commit ids from
  that queue,

  05dab43230fdc0d14ca885b473a2740fe017ecb1 scsi: cxlflash: Improve EEH recovery 
time
  1d3324c382b1a617eb567e3650dcb51f22dfec9a scsi: cxlflash: Fix to avoid EEH and 
host reset collisions
  babf985d1e1b0677cb264acd01319d2b9c8f4327 scsi: cxlflash: Remove the device 
cleanly in the system shutdown path
  bbbfae962b7c221237c0f92547ee0c83f7204747 scsi: cxlflash: Scan host only after 
the port is ready for I/O

  I tried applying them on local copy of xenial/master-next tree and it
  applied cleanly. Please let me know if you want me to attach the
  patches instead.

  Please include the above commits to Xenial SRU.

  Thank you.

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

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

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

--- Comment From laurent.duf...@fr.ibm.com 2017-02-27 13:11 EDT---
(In reply to comment #33)
> Question to IBM: have you made any progress towards identifying a patch to
> address this issue?

Yep fixed by https://patchwork.kernel.org/patch/9364805/

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

Title:
  [Ubuntu 16.10] - System crashes and gives out call traces when
  libhugetlbfs test suite is run.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  == Comment: #0 - Santhosh G  - 2016-09-27 01:55:00 ==
  Issue:
  Kernel unable to handle page request when heapshrink test case is run from 
libhugetlbfs suite.

  Environment:
  arch - ppc64le
  ubuntu kvm guest

  Host related Info:
  Kernel:
  -
  uname -a
  Linux ltc-haba1 4.8.0-17-generic #19-Ubuntu SMP Sun Sep 25 06:35:40 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  Memory:
  
  oot@ltc-haba1:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   255G 65G187G 22M1.9G
188G
  Swap:  225G  0B225G

  Hugepages configured:
  
  root@ltc-haba1:~# cat /proc/meminfo | grep -i Huge
  AnonHugePages: 81920 kB
  ShmemHugePages:0 kB
  HugePages_Total:4096
  HugePages_Free: 3584
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:  16384 kB

  
  Guest Related Info:
  --
  -
  Kernel:
  -
  root@ubuntu:~/libhugetlbfs# uname -a
  Linux ubuntu 4.8.0-17-generic #19-Ubuntu SMP Sun Sep 25 06:35:40 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  Memory:
  -
  root@ubuntu:~/libhugetlbfs# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   8.0G133M7.7G 15M132M
7.5G
  Swap:  3.3G  0B3.3G

  Hugepages configured:
  ---
  root@ubuntu:~/libhugetlbfs# cat /proc/meminfo | grep -i Huge
  AnonHugePages: 0 kB
  ShmemHugePages:0 kB
  HugePages_Total: 256
  HugePages_Free:  256
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:  16384 kB

  
  Steps to reproduce:
  1- Install a ubuntu kvm guest with hugepages memory Backing.
  2 - git clone the latest libhugetlbfs from 
https://github.com/libhugetlbfs/libhugetlbfs.git
  3 - configure huge[pages in guest and run make check.

  xmon is configured in the system .
  The system gets call traces and enters xmon console:

  HUGETLB_VERBOSE=1 HUGETLB_MORECORE=yes heap-overflow (16M: 64):   [  
281.735713] Unable to handle kernel paging request for data at address 
0x42328e38
  [  281.735804] Faulting instruction address: 0xc027b410
  cpu 0x1: Vector: 300 (Data Access) at [c001fa8c3730]
  pc: c027b410: shrink_active_list+0x300/0x4d0
  lr: c027b3f4: shrink_active_list+0x2e4/0x4d0
  sp: c001fa8c39b0
 msr: 80010280b033
 dar: 42328e38
   dsisr: 4200
current = 0xc001fa8adc00
paca= 0xcfb80900 softe: 0irq_happened: 0x01
  pid   = 50, comm = kswapd0
  Linux version 4.8.0-17-generic (buildd@bos01-ppc64el-025) (gcc version 6.2.0 
20160914 (Ubuntu 6.2.0-3ubuntu15) ) #19-Ubuntu SMP Sun Sep 25 06:35:40 UTC 2016 
(Ubuntu 4.8.0-17.19-generic 4.8.0-rc7)
  enter ? for help
  [c001fa8c3aa0] c027bbdc shrink_node_memcg+0x5fc/0x800
  [c001fa8c3bc0] c027bf0c shrink_node+0x12c/0x3f0
  [c001fa8c3c80] c027d500 kswapd+0x460/0x990
  [c001fa8c3d80] c00fd120 kthread+0x110/0x130
  [c001fa8c3e30] c00098f0 ret_from_kernel_thread+0x5c/0x6c

  xmon logs:

  1:mon> e
  cpu 0x1: Vector: 300 (Data Access) at [c001fa8e7730]
  pc: c027b410: shrink_active_list+0x300/0x4d0
  lr: c027b3f4: shrink_active_list+0x2e4/0x4d0
  sp: c001fa8e79b0
 msr: 80010280b033
 dar: 420c58d0
   dsisr: 4200
current = 0xc001fa8a
paca= 0xcfb80900 softe: 0irq_happened: 0x01
  pid   = 50, comm = kswapd0
  Linux version 4.8.0-17-generic (buildd@bos01-ppc64el-025) (gcc version 6.2.0 
20160914 (Ubuntu 6.2.0-3ubuntu15) ) #19-Ubuntu SMP Sun Sep 25 06:35:40 UTC 2016 
(Ubuntu 4.8.0-17.19-generic 4.8.0-rc7)

  1:mon> r
  R00 = c027b3f4   R16 = c001fffcfe00
  R01 = c001fa8e79b0   R17 = 010a
  R02 = c14e5e00   R18 = 420cbdd0
  R03 = 0001   R19 = c001fffc6300
  R04 = 0005   R20 = c001fa8e79e0
  R05 =    R21 =

[Kernel-packages] [Bug 1550704] Re: Type Cover (3) touchpad not working on Surface Pro 3

2017-02-27 Thread BitBurners.com

>  Fedora has out-of-the-box support as well, since v24.

It does not have Touchpad multi touch patch included. F25 was quite
unstable on my SP3, for whatever reason.

> How is that helpful??

Since the support on Ubuntu is not going anywhere. This is a year old
bug, and unofficial patched kernels have been around for ages. Since we
are here at stand still, but someone may actually want to use the
device, it is worth pointing out that there are alternatives.

Since Ubuntu/Canonical is so friendly with Microsoft, I wonder why there
is no interest in improving support for partners hardware.

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

Title:
  Type Cover (3) touchpad not working on Surface Pro 3

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Type Cover (3) touchpad is not working on the Surface Pro 3.

  The keyboard works out of the box.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-generic 4.4.0.7.8
  ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2
  Uname: Linux 4.4.0-7-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xubuntu3087 F pulseaudio
   /dev/snd/controlC1:  xubuntu3087 F pulseaudio
  CasperVersion: 1.367
  Date: Sat Feb 27 13:33:53 2016
  LiveMediaBuild: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224)
  MachineType: Microsoft Corporation Surface Pro 3
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed boot=casper quiet splash --- 
cdrom-detect/try-usb=true noprompt persistent
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-7-generic N/A
   linux-backports-modules-4.4.0-7-generic  N/A
   linux-firmware   1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.11.0950
  dmi.board.asset.tag: 0
  dmi.board.name: Surface Pro 3
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 1
  dmi.chassis.asset.tag: 0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.11.0950:bd06/05/2015:svnMicrosoftCorporation:pnSurfacePro3:pvr1:rvnMicrosoftCorporation:rnSurfacePro3:rvr1:cvnMicrosoftCorporation:ct9:cvr1:
  dmi.product.name: Surface Pro 3
  dmi.product.version: 1
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1661030] Re: regession tests failing after stackprofile test is run

2017-02-27 Thread Colin Ian King

tested and verified it is fixed on Ubuntu Yakkety with -proposed kernel
4.8.0-39-generic #42

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

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

Title:
  regession tests failing after stackprofile test is run

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

Bug description:
  from source, I'm running the tests and the makefile fails at the end
  with:

  running stackprofile
  Makefile:303: recipe for target 'tests' failed
  make: *** [tests] Error 1

  No idea why that is happening. It's breaking on our kernel team
  regression tests runs, so can this be investigated?  The source was
  fetched using "apt-get source apparmor".

  A full run is below:

  king@ubuntu:~/apparmor-2.10.95/tests/regression/apparmor$ sudo make
  USE_SYSTEM=1 tests

  running aa_exec

  running access
  xfail: ACCESS file rx (r)
  xfail: ACCESS file rwx (r)
  xfail: ACCESS file r (wx)
  xfail: ACCESS file rx (wx)
  xfail: ACCESS file rwx (wx)
  xfail: ACCESS dir rwx (r)
  xfail: ACCESS dir r (wx)
  xfail: ACCESS dir rx (wx)
  xfail: ACCESS dir rwx (wx)

  running at_secure

  running introspect

  running capabilities
  (ptrace)
  (sethostname)
  (setdomainname)
  (setpriority)
  (setscheduler)
  (reboot)
  (chroot)
  (mlockall)
  (net_raw)
  (ioperm)
  (iopl)

  running changeprofile

  running onexec

  running changehat

  running changehat_fork

  running changehat_misc

  *** A 'Killed' message from bash is expected for the following test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12503 Killed  $testexec "$@" > $outfile 2>&1

  *** A 'Killed' message from bash is expected for the following test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12537 Killed  $testexec "$@" > $outfile 2>&1

  running chdir

  running clone

  running coredump
  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12803 Segmentation fault  (core dumped) $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12833 Segmentation fault  $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12869 Segmentation fault  $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12905 Segmentation fault  $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12941 Segmentation fault  $testexec "$@" > $outfile 2>&1
  XFAIL: Error: corefile present when not expected -- COREDUMP (ix confinement)

  running deleted

  running environ
  Fatal Error (environ): Unable to run test sub-executable

  running exec

  running exec_qual

  running fchdir

  running fd_inheritance

  running fork

  running i18n

  running link

  running link_subset

  running mkdir

  running mmap

  running mount
  using mount rules ...

  running mult_mount

  running named_pipe

  running namespaces

  running net_raw

  running open

  running openat

  running pipe

  running pivot_root

  running ptrace
 using ptrace v6 tests ...

  running pwrite

  running query_label
  Alert: query_label passed. Test 'QUERY file (all base perms #1)' was marked 
as expected pass but known problem (xpass)
  xpass: QUERY file (all base perms #1)
  Alert: query_label passed. Test 'QUERY file (all base perms #2)' was marked 
as expected pass but known problem (xpass)
  xpass: QUERY file (all base perms #2)

  running regex

  running rename

  running readdir

  running rw

  running socketpair

  running swap
  mkswap: /tmp/sdtest.21272-20356-eRXvtR/swapfile: insecure permissions 0644, 
0600 suggested.
  swapon: /tmp/sdtest.21272-20356-eRXvtR/swapfile: insecure permissions 0644, 
0600 suggested.

  running sd_flags

  running

[Kernel-packages] [Bug 1668356] [NEW] Hard lockup after 4 hours uptime

2017-02-27 Thread Olivier Louvignes

Public bug reported:

We have recently deployed intel NUC6i5 devices in store for POS display
and are encountering strange inexplicable freezes on several devices.

What is very strange is that all devices are freezing exactly 4h after
boot.

We have had this exact same issue on more than 20 devices (over 100),
with parts from different batches, and all did freeze exactly 4h after
boot (but it's not reproducible, it won't freeze every day). Some
devices are playing MPV videos, while other run chromium. They are
running non-stop, but are all rebooting daily at 05h05.

Looks like it might be related to https://lkml.org/lkml/2015/6/11/787

That seem to have been fixed and backported already
https://lkml.org/lkml/2015/10/17/259

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-64-generic 4.4.0-64.85
ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
Uname: Linux 4.4.0-64-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
Date: Mon Feb 27 21:06:44 2017
InstallationDate: Installed on 2016-06-08 (264 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 8087:0a2b Intel Corp. 
 Bus 001 Device 002: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=1f60f9c9-bbf1-45df-bdc3-9b4da883839e ro quiet splash net.ifnames=0 
vt.handoff=7
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.board.name: NUC6i5SYB

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


** Tags: amd64 apport-bug xenial

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

Title:
  Hard lockup after 4 hours uptime

Status in linux package in Ubuntu:
  New

Bug description:
  We have recently deployed intel NUC6i5 devices in store for POS
  display and are encountering strange inexplicable freezes on several
  devices.

  What is very strange is that all devices are freezing exactly 4h after
  boot.

  We have had this exact same issue on more than 20 devices (over 100),
  with parts from different batches, and all did freeze exactly 4h after
  boot (but it's not reproducible, it won't freeze every day). Some
  devices are playing MPV videos, while other run chromium. They are
  running non-stop, but are all rebooting daily at 05h05.

  Looks like it might be related to https://lkml.org/lkml/2015/6/11/787

  That seem to have been fixed and backported already
  https://lkml.org/lkml/2015/10/17/259

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-64-generic 4.4.0-64.85
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Mon Feb 27 21:06:44 2017
  InstallationDate: Installed on 2016-06-08 (264 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 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=1f60f9c9-bbf1-45df-bdc3-9b4da883839e ro quiet splash net.ifnames=0 
vt.handoff=7
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.board.name: NUC6i5SYB

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

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

[Kernel-packages] [Bug 1668356] Re: Hard lockup after 4 hours uptime

2017-02-27 Thread Olivier Louvignes

DHCPREQUEST of 10.34.242.77 on eth0 to 10.32.65.65 port 67 (xid=0x30fdf923)
BUG: unable to handle kernel NULL pointer dereference at   (null)
IP: [] timecounter_read+0x13/0x60
PGD 0 
Oops:  [#1] SMP 
Modules linked in: rfcomm ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_multiport 
xfrm_user xfrm_algo iptable_nat nf_nat_ipv4 br_netfilter bridge stp llc aufs 
pl2303 usbserial bnep arc4 snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc 
snd_hda_ext_core snd_soc_sst_ipc snd_hda_codec_realtek snd_soc_sst_dsp 
snd_hda_codec_generic nls_iso8859_1 snd_soc_core snd_compress ac97_bus 
snd_pcm_dmaengine dw_dmac_core snd_hda_intel iwlmvm snd_hda_codec snd_hda_core 
intel_rapl 8250_dw snd_hwdep mac80211 x86_pkg_temp_thermal intel_powerclamp 
coretemp snd_pcm kvm_intel kvm snd_seq_midi snd_seq_midi_event irqbypass 
crct10dif_pclmul crc32_pclmul iwlwifi ghash_clmulni_intel snd_rawmidi 
aesni_intel snd_seq aes_x86_64 lrw gf128mul glue_helper cfg80211 snd_seq_device 
ablk_helper cryptd snd_timer snd soundcore idma64
 virt_dma shpchp ir_lirc_codec ir_xmp_decoder lirc_dev ir_mce_kbd_decoder 
ir_sharp_decoder intel_lpss_pci ir_sanyo_decoder btusb ir_sony_decoder hci_uart 
btrtl ir_jvc_decoder ir_rc6_decoder btbcm btqca ir_rc5_decoder btintel 
ir_nec_decoder bluetooth mei_me rc_rc6_mce ite_cir rc_core intel_lpss_acpi 
intel_lpss mei acpi_pad mac_hid acpi_als kfifo_buf industrialio ip6t_REJECT 
nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 
ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp 
xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ip6table_filter 
ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat 
nf_conntrack_ftp nf_conntrack iptable_filter ip_tables x_tables parport_pc 
ppdev sunrpc lp parport autofs4 i915_bpo intel_ips
 i2c_algo_bit drm_kms_helper syscopyarea e1000e sysfillrect sysimgblt 
fb_sys_fops ptp sdhci_pci ahci drm pps_core sdhci libahci video 
pinctrl_sunrisepoint i2c_hid pinctrl_intel hid fjes
CPU: 3 PID: 15471 Comm: kworker/3:0 Not tainted 4.4.0-64-generic #85-Ubuntu
Hardware name:  /NUC6i5SYB, BIOS 
SYSKLi35.86A.0051.2016.0804.1114 08/04/2016
Workqueue: events e1000e_systim_overflow_work [e1000e]
task: 880031f32d00 ti: 8800350e8000 task.ti: 8800350e8000
RIP: 0010:[]  [] timecounter_read+0x13/0x60
RSP: 0018:8800350ebdb0  EFLAGS: 00010046
RAX:  RBX: 8800353ab7a0 RCX: 0001
RDX: 0001 RSI: 8800350ebdf8 RDI: 
RBP: 8800350ebdb8 R08: 88016ed965c0 R09: 
R10: 00010035 R11: 0001 R12: 8800353ab780
R13: 8800350ebdf8 R14: 0246 R15: 8800353ab6d0
FS:  () GS:88016ed8() knlGS:
CS:  0010 DS:  ES:  CR0: 80050033
CR2:  CR3: 02e0a000 CR4: 003406e0
Stack:
 8800353ab7d0 8800350ebde8 c014d36e 8800353ab6d0
 88016ed965c0 88016ed9af00 00c0 8800350ebe18
 c014d521 81837e26 88016ed9af00 a91221c0
Call Trace:
 [] e1000e_phc_gettime+0x2e/0x60 [e1000e]
 [] e1000e_systim_overflow_work+0x31/0xa0 [e1000e]
 [] ? __schedule+0x3b6/0xa30
 [] process_one_work+0x165/0x480
 [] worker_thread+0x4b/0x4c0
 [] ? process_one_work+0x480/0x480
 [] ? process_one_work+0x480/0x480
 [] kthread+0xd8/0xf0
 [] ? kthread_create_on_node+0x1e0/0x1e0
 [] ret_from_fork+0x3f/0x70
 [] ? kthread_create_on_node+0x1e0/0x1e0
Code: 00 48 d3 e0 48 83 e8 01 48 89 43 18 5b 41 5c 41 5d 5d c3 0f 1f 44 00 00 
0f 1f 44 00 00 55 48 89 e5 53 48 8b 07 48 89 fb 48 89 c7  10 48 8b 33 48 89 
c2 48 2b 53 08 8b 4e 10 48 23 56 08 48 0f 
RIP  [] timecounter_read+0x13/0x60
 RSP 
CR2: 
---[ end trace 7d024538180dff79 ]---
BUG: unable to handle kernel paging request at ffd8
IP: [] kthread_data+0x10/0x20
PGD 2e0d067 PUD 2e0f067 PMD 0 
Oops:  [#2] SMP 
Modules linked in: rfcomm ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_multiport 
xfrm_user xfrm_algo iptable_nat nf_nat_ipv4 br_netfilter bridge stp llc aufs 
pl2303 usbserial bnep arc4 snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc 
snd_hda_ext_core snd_soc_sst_ipc snd_hda_codec_realtek snd_soc_sst_dsp 
snd_hda_codec_generic nls_iso8859_1 snd_soc_core snd_compress ac97_bus 
snd_pcm_dmaengine dw_dmac_core snd_hda_intel iwlmvm snd_hda_codec snd_hda_core 
intel_rapl 8250_dw snd_hwdep mac80211 x86_pkg_temp_thermal intel_powerclamp 
coretemp snd_pcm kvm_intel kvm snd_seq_midi snd_seq_midi_event irqbypass 
crct10dif_pclmul crc32_pclmul iwlwifi ghash_clmulni_intel snd_rawmidi 
aesni_intel snd_seq aes_x86_64 lrw gf128mul glue_helper cfg80211 snd_seq_device 
ablk_helper cryptd snd_timer snd soundcore idma64
 virt_dma shpchp ir_lirc_codec ir_xmp_decoder lirc_dev ir_mce_kbd_decoder 
ir_sharp_decoder intel_lpss_pci ir_sanyo_decoder btusb ir_sony_decoder hci_uart 
btrtl ir_jvc_decoder ir_rc6_decoder btbcm btqca

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

Closed as a duplicate of LP1628976

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

Title:
  [Ubuntu 16.10] - System crashes and gives out call traces when
  libhugetlbfs test suite is run.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  == Comment: #0 - Santhosh G  - 2016-09-27 01:55:00 ==
  Issue:
  Kernel unable to handle page request when heapshrink test case is run from 
libhugetlbfs suite.

  Environment:
  arch - ppc64le
  ubuntu kvm guest

  Host related Info:
  Kernel:
  -
  uname -a
  Linux ltc-haba1 4.8.0-17-generic #19-Ubuntu SMP Sun Sep 25 06:35:40 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  Memory:
  
  oot@ltc-haba1:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   255G 65G187G 22M1.9G
188G
  Swap:  225G  0B225G

  Hugepages configured:
  
  root@ltc-haba1:~# cat /proc/meminfo | grep -i Huge
  AnonHugePages: 81920 kB
  ShmemHugePages:0 kB
  HugePages_Total:4096
  HugePages_Free: 3584
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:  16384 kB

  
  Guest Related Info:
  --
  -
  Kernel:
  -
  root@ubuntu:~/libhugetlbfs# uname -a
  Linux ubuntu 4.8.0-17-generic #19-Ubuntu SMP Sun Sep 25 06:35:40 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  Memory:
  -
  root@ubuntu:~/libhugetlbfs# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   8.0G133M7.7G 15M132M
7.5G
  Swap:  3.3G  0B3.3G

  Hugepages configured:
  ---
  root@ubuntu:~/libhugetlbfs# cat /proc/meminfo | grep -i Huge
  AnonHugePages: 0 kB
  ShmemHugePages:0 kB
  HugePages_Total: 256
  HugePages_Free:  256
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:  16384 kB

  
  Steps to reproduce:
  1- Install a ubuntu kvm guest with hugepages memory Backing.
  2 - git clone the latest libhugetlbfs from 
https://github.com/libhugetlbfs/libhugetlbfs.git
  3 - configure huge[pages in guest and run make check.

  xmon is configured in the system .
  The system gets call traces and enters xmon console:

  HUGETLB_VERBOSE=1 HUGETLB_MORECORE=yes heap-overflow (16M: 64):   [  
281.735713] Unable to handle kernel paging request for data at address 
0x42328e38
  [  281.735804] Faulting instruction address: 0xc027b410
  cpu 0x1: Vector: 300 (Data Access) at [c001fa8c3730]
  pc: c027b410: shrink_active_list+0x300/0x4d0
  lr: c027b3f4: shrink_active_list+0x2e4/0x4d0
  sp: c001fa8c39b0
 msr: 80010280b033
 dar: 42328e38
   dsisr: 4200
current = 0xc001fa8adc00
paca= 0xcfb80900 softe: 0irq_happened: 0x01
  pid   = 50, comm = kswapd0
  Linux version 4.8.0-17-generic (buildd@bos01-ppc64el-025) (gcc version 6.2.0 
20160914 (Ubuntu 6.2.0-3ubuntu15) ) #19-Ubuntu SMP Sun Sep 25 06:35:40 UTC 2016 
(Ubuntu 4.8.0-17.19-generic 4.8.0-rc7)
  enter ? for help
  [c001fa8c3aa0] c027bbdc shrink_node_memcg+0x5fc/0x800
  [c001fa8c3bc0] c027bf0c shrink_node+0x12c/0x3f0
  [c001fa8c3c80] c027d500 kswapd+0x460/0x990
  [c001fa8c3d80] c00fd120 kthread+0x110/0x130
  [c001fa8c3e30] c00098f0 ret_from_kernel_thread+0x5c/0x6c

  xmon logs:

  1:mon> e
  cpu 0x1: Vector: 300 (Data Access) at [c001fa8e7730]
  pc: c027b410: shrink_active_list+0x300/0x4d0
  lr: c027b3f4: shrink_active_list+0x2e4/0x4d0
  sp: c001fa8e79b0
 msr: 80010280b033
 dar: 420c58d0
   dsisr: 4200
current = 0xc001fa8a
paca= 0xcfb80900 softe: 0irq_happened: 0x01
  pid   = 50, comm = kswapd0
  Linux version 4.8.0-17-generic (buildd@bos01-ppc64el-025) (gcc version 6.2.0 
20160914 (Ubuntu 6.2.0-3ubuntu15) ) #19-Ubuntu SMP Sun Sep 25 06:35:40 UTC 2016 
(Ubuntu 4.8.0-17.19-generic 4.8.0-rc7)

  1:mon> r
  R00 = c027b3f4   R16 = c001fffcfe00
  R01 = c001fa8e79b0   R17 = 010a
  R02 = c14e5e00   R18 = 420cbdd0
  R03 = 0001   R19 = c001fffc6300
  R04 = 0005   R20 = c001fa8e79e0
  R05 =    R21 = c001fe144800
  R06 = f03bc9a0   R22 = 0001
  R07 = 0001fee3   R23 = 0005
  R08 = 002a   R24 = 207d
  R09 =    R25 = 0100
  R10 =

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