[Kernel-packages] [Bug 1632578] [NEW] Add support for KabeLake i219-LOM chips

[Phidias]

Public bug reported:

There's a commit add device ids to support new i219 Lan-on-motherboard:

commit deaa1d226af725d4e3a56527cdb506c3c30f9fd0
e1000e: Initial support for KabeLake

[Impact]

Add support for devices [8086:15e3], [8086:15d7], [8086:15d6],
[8086:15d8]. This patch only add device ids so no further regressions
are expected.

[Test]

Though the commit log says it's "Initial support", but it's been
successfully tested on multiple platforms and no further issues are
spotted, so at the moment no further patches are needed.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Phidias (phidias-chiang)
 Status: New


** Tags: 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/1632578

Title:
  Add support for KabeLake i219-LOM chips

Status in linux package in Ubuntu:
  New

Bug description:
  There's a commit add device ids to support new i219 Lan-on-
  motherboard:

  commit deaa1d226af725d4e3a56527cdb506c3c30f9fd0
  e1000e: Initial support for KabeLake

  [Impact]

  Add support for devices [8086:15e3], [8086:15d7], [8086:15d6],
  [8086:15d8]. This patch only add device ids so no further regressions
  are expected.

  [Test]

  Though the commit log says it's "Initial support", but it's been
  successfully tested on multiple platforms and no further issues are
  spotted, so at the moment no further patches are needed.

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

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

[Kernel-packages] [Bug 1625932] Re: Backlight does not change when adjust it higher than 50% after S3

[AceLan Kao]

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

** Changed in: hwe-next
   Status: Fix Committed => Fix Released

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

Title:
  Backlight does not change when adjust it higher than 50% after S3

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  Backlight does not change when adjust it higher than 50% after S3

  Steps:
  1. Install ubuntu 16.04 and boot into OS
  2. suspend system
  3. resume system from S3
  4. Try to adjust brightness level

  Expected results: Backlight should be changed when adjust it

  Actual results: Backlight does not change when adjust it higher than
  50% after S3

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

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

[Kernel-packages] [Bug 1632484] Re: linux: 4.8.0-23.25 -proposed tracker

[Brad Figg]

** Changed in: kernel-development-workflow/prepare-package-meta
   Status: Confirmed => Fix Released

** Changed in: kernel-development-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee 
(sforshee)

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

** Description changed:

  This bug is for tracking the 4.8.0-23.25 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 --
  derivative-trackers-created: true
  phase: Uploaded
+ kernel-phase-changed:Wednesday, 12. October 2016 06:17 UTC
+ kernel-phase:Uploaded

** Description changed:

  This bug is for tracking the 4.8.0-23.25 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
+ boot-testing-requested: true
  derivative-trackers-created: true
  phase: Uploaded
- kernel-phase-changed:Wednesday, 12. October 2016 06:17 UTC
- kernel-phase:Uploaded

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

Title:
  linux: 4.8.0-23.25 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Uploaded

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

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

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

[bugproxy]

--- Comment From pt...@cn.ibm.com 2016-10-12 01:45 EDT---
We can reproduce this bug with 4.8.0-22-generic. When the patch will be 
applied, please?

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

Title:
  Ubuntu 16.10: Oops panic in move_page_tables/page_remove_rmap after
  running memory_stress_ng.

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

Bug description:
  FYI Canonical:

  We have been seeing various page handling issues during memory stress
  in the 4.8 kernels.  The following is the most recent issue resulting
  in system panics on this host after the 4.8.0-17 update:

  == Comment: #17 - PAVITHRA R. PRAKASH - 2016-09-28 06:26:21 ==
  Hi,

  Tried running on 4.8.0-17-generic kernel. Getting below call trace and
  system crashes. Attaching logs.

  [ 2959.364333] Unable to handle kernel paging request for data at address 
0xf2fe4020
  [ 2959.364345] Faulting instruction address: 0xc02bb2a0
  [ 2959.364356] Oops: Kernel access of bad area, sig: 11 [#1]
  [ 2959.364364] SMP NR_CPUS=2048 NUMA pSeries
  [ 2959.364377] Modules linked in: rpadlpar_io rpaphp dccp_diag dccp tcp_diag 
udp_diag inet_diag unix_diag af_packet_diag netlink_diag bnx2x mdio libcrc32c 
pseries_rng vmx_crypto binfmt_misc ip_tables x_tables autofs4 ibmvscsi 
crc32c_vpmsum
  [ 2959.364441] CPU: 13 PID: 108 Comm: oom_reaper Not tainted 4.8.0-17-generic 
#19-Ubuntu
  [ 2959.364452] task: c004fbdf9c00 task.stack: c004fbe0
  [ 2959.364461] NIP: c02bb2a0 LR: c0300618 CTR: 
c009ca40
  [ 2959.364471] REGS: c004fbe036e0 TRAP: 0300   Not tainted  
(4.8.0-17-generic)
  [ 2959.364481] MSR: 80010280b033   
CR: 24028844  XER: 200c
  [ 2959.364526] CFAR: c0300614 DAR: f2fe4020 DSISR: 4000 
SOFTE: 1 
 GPR00: c0300618 c004fbe03960 c14e5e00 
f2fe4000 
 GPR04: 0001 0800  
c1665e00 
 GPR08: f900a196 0001 02fe4000 
 
 GPR12: 8800 c1b37500 0008 
c1ffe7ff 
 GPR16: c004f62a55f0 3fff9a00 3fff9900 
 
 GPR20: c004fbe03b80 c004e0713800 8e017c3302c0 
0001 
 GPR24: c000fb3614c8 c000fce9d990 c000fce9d6e4 
96a100f90b40 
 GPR28: f2fe4000 c000fb3614c8 0001 
f2fe4000 
  [ 2959.364673] NIP [c02bb2a0] page_remove_rmap+0x30/0x4b0
  [ 2959.364685] LR [c0300618] zap_huge_pmd+0xf8/0x480
  [ 2959.364692] Call Trace:
  [ 2959.364699] [c004fbe03960] [c004fbe039a0] 0xc004fbe039a0 
(unreliable)
  [ 2959.364714] [c004fbe039a0] [c0300618] zap_huge_pmd+0xf8/0x480
  [ 2959.364726] [c004fbe039f0] [c02a68d8] 
unmap_page_range+0xd08/0xee0
  [ 2959.364740] [c004fbe03b20] [c025c474] 
__oom_reap_task+0x204/0x2c0
  [ 2959.364752] [c004fbe03c80] [c025cda8] oom_reaper+0x1e8/0x300
  [ 2959.364765] [c004fbe03d80] [c00fd120] kthread+0x110/0x130
  [ 2959.364778] [c004fbe03e30] [c00098f0] 
ret_from_kernel_thread+0x5c/0x6c
  [ 2959.364788] Instruction dump:
  [ 2959.364796] 3c4c0123 3842ab90 7c0802a6 fba1ffe8 fbc1fff0 fbe1fff8 f8010010 
f821ffc1 
  [ 2959.364821] 7c7f1b78 7c9e2378 6000 6000  71480001 
392a 40820008 
  [ 2959.364871] ---[ end trace 178b14c6911b70dc ]---
  [ 2959.372762] 
  [ 2959.372798] Sending IPI to other CPUs
  [ 2959.373834] IPI complete

  Thanks,
  Pavithra

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

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

[Kernel-packages] [Bug 1632484] Re: linux: 4.8.0-23.25 -proposed tracker

[Brad Figg]

** Changed in: kernel-development-workflow/prepare-package
   Status: Confirmed => Fix Released

** Changed in: kernel-development-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => 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/1632484

Title:
  linux: 4.8.0-23.25 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.8.0-23.25 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 --
  derivative-trackers-created: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1598571] Re: Audio-out on Asus X555 dont work

[Rodolpho Pivetta Sabino]

Problem still present on Ubuntu 16.10 Yakkety with 4.8.0-21-generic
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/1598571

Title:
  Audio-out on Asus X555 dont work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Have problem with headphone/microphone port in my laptop. When plug-in 
headphones, sound resume play on speackers... In Win10 i dont have this 
problem. Physicaly port work good.
  Card: HDA Intel PCH
  Chip: Realtek ALC256

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-30-generic 4.4.0-30.49
  ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13
  Uname: Linux 4.4.0-30-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mnaz   1727 F pulseaudio
    mnaz   9456 F alsamixer
  CurrentDesktop: Unity
  Date: Sun Jul  3 15:17:26 2016
  HibernationDevice: RESUME=UUID=773628e6-2536-424b-9a24-4e8c8f0a1892
  InstallationDate: Installed on 2016-06-25 (8 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 004: ID 0bda:57de Realtek Semiconductor Corp.
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:0520 Microdia MaxTrack Wireless Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X555UB
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-30-generic.efi.signed 
root=UUID=f9ab2085-6070-4e16-969a-8769d6bd87e3 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-30-generic N/A
   linux-backports-modules-4.4.0-30-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555UB.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555UB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555UB.204:bd10/18/2015:svnASUSTeKCOMPUTERINC.:pnX555UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X555UB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1632484] Re: linux: 4.8.0-23.25 -proposed tracker

[Brad Figg]

** Changed in: kernel-development-workflow/prepare-package-signed
   Status: Confirmed => Fix Released

** Changed in: kernel-development-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee 
(sforshee)

** Description changed:

  This bug is for tracking the 4.8.0-23.25 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
- kernel-phase-changed:Tuesday, 11. October 2016 21:45 UTC
- kernel-phase:Packaging
- 
  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging
+ kernel-phase-changed:Wednesday, 12. October 2016 04:16 UTC
+ kernel-phase:Uploaded

** Description changed:

  This bug is for tracking the 4.8.0-23.25 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 --
  derivative-trackers-created: true
- phase: Packaging
- kernel-phase-changed:Wednesday, 12. October 2016 04:16 UTC
- kernel-phase:Uploaded
+ phase: Uploaded

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

Title:
  linux: 4.8.0-23.25 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.8.0-23.25 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 --
  derivative-trackers-created: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1628835] Re: msg='apparmor="DENIED" operation="dbus_method_call"

[Tyler Hicks]

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

Not quite. The root cause of these denials is the switch over to
systemd-resolved for name resolution. This is being tracked in bug
#1598759. The kernel is not at fault so I'm marking the linux task as
invalid.

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

** This bug has been marked a duplicate of bug 1598759
   AppArmor nameservice abstraction doesn't allow communication with 
systemd-resolved

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

Title:
  msg='apparmor="DENIED" operation="dbus_method_call"

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Get some apparmor 'DENIED' messages logged when booting with 4.8.0-17
  kernel; this was not happening with some previous versions (at least
  4.8.0-12) and no other upgrades can explain such apparmor messages, so
  blaming the kernel.

   oem@u64:~$ journalctl | grep  DENIED

  Sep 29 08:11:52 u64 audit[840]: USER_AVC pid=840 uid=101
  auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/resolve1"
  interface="org.freedesktop.resolve1.Manager" member="ResolveHostname"
  mask="send" name="org.freedesktop.resolve1" pid=1287
  label="/usr/sbin/ntpd" peer_pid=1024 peer_label="unconfined"

  Sep 29 08:11:52 u64 kernel: audit: type=1107 audit(1475129512.681:27):
  pid=840 uid=101 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/resolve1"
  interface="org.freedesktop.resolve1.Manager" member="ResolveHostname"
  mask="send" name="org.freedesktop.resolve1" pid=1287
  label="/usr/sbin/ntpd" peer_pid=1024 peer_label="unconfined"

  Sep 29 08:11:53 u64 audit[840]: USER_AVC pid=840 uid=101
  auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/resolve1"
  interface="org.freedesktop.resolve1.Manager" member="ResolveHostname"
  mask="send" name="org.freedesktop.resolve1" pid=1287
  label="/usr/sbin/ntpd" peer_pid=1024 peer_label="unconfined"

  Sep 29 08:11:53 u64 kernel: audit: type=1107 audit(1475129513.581:28):
  pid=840 uid=101 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/resolve1"
  interface="org.freedesktop.resolve1.Manager" member="ResolveHostname"
  mask="send" name="org.freedesktop.resolve1" pid=1287
  label="/usr/sbin/ntpd" peer_pid=1024 peer_label="unconfined"

  Sep 29 08:11:54 u64 audit[840]: USER_AVC pid=840 uid=101
  auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/resolve1"
  interface="org.freedesktop.resolve1.Manager" member="ResolveHostname"
  mask="send" name="org.freedesktop.resolve1" pid=1287
  label="/usr/sbin/ntpd" peer_pid=1024 peer_label="unconfined"

  Sep 29 08:11:54 u64 kernel: audit: type=1107 audit(1475129514.585:29):
  pid=840 uid=101 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/resolve1"
  interface="org.freedesktop.resolve1.Manager" member="ResolveHostname"
  mask="send" name="org.freedesktop.resolve1" pid=1287
  label="/usr/sbin/ntpd" peer_pid=1024 peer_label="unconfined"

  Sep 29 08:11:55 u64 audit[840]: USER_AVC pid=840 uid=101
  auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/resolve1"
  interface="org.freedesktop.resolve1.Manager" member="ResolveHostname"
  mask="send" name="org.freedesktop.resolve1" pid=1287
  label="/usr/sbin/ntpd" peer_pid=1024 peer_label="unconfined"

  Sep 29 08:11:55 u64 kernel: audit: type=1107 audit(1475129515.124:30):
  pid=840 uid=101 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/resolve1"
  interface="org.freedesktop.resolve1.Manager" member="ResolveHostname"
  mask="send" name="org.freedesktop.resolve1" pid=1287
  label="/usr/sbin/ntpd" peer_pid=1024 peer_label="unconfined"

  
  Note: i wonder if there is a relationship with the previous logged line 
before that error appear:
  ntpd[1282]: Soliciting pool server .

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-17-generic 4.8.0-17.19
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem2213 F pulseaudio
   /dev/snd/pcmC0D0p:   oem2213 F...m pulseaudio
   /dev/snd/controlC0:  oem2213 F pulseaudio
  Current

[Kernel-packages] [Bug 1628835] Re: msg='apparmor="DENIED" operation="dbus_method_call"

[dino99]

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

The root cause seems related to the apparmor tcpdump profile  Bug
#1632399

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

Title:
  msg='apparmor="DENIED" operation="dbus_method_call"

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Get some apparmor 'DENIED' messages logged when booting with 4.8.0-17
  kernel; this was not happening with some previous versions (at least
  4.8.0-12) and no other upgrades can explain such apparmor messages, so
  blaming the kernel.

   oem@u64:~$ journalctl | grep  DENIED

  Sep 29 08:11:52 u64 audit[840]: USER_AVC pid=840 uid=101
  auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/resolve1"
  interface="org.freedesktop.resolve1.Manager" member="ResolveHostname"
  mask="send" name="org.freedesktop.resolve1" pid=1287
  label="/usr/sbin/ntpd" peer_pid=1024 peer_label="unconfined"

  Sep 29 08:11:52 u64 kernel: audit: type=1107 audit(1475129512.681:27):
  pid=840 uid=101 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/resolve1"
  interface="org.freedesktop.resolve1.Manager" member="ResolveHostname"
  mask="send" name="org.freedesktop.resolve1" pid=1287
  label="/usr/sbin/ntpd" peer_pid=1024 peer_label="unconfined"

  Sep 29 08:11:53 u64 audit[840]: USER_AVC pid=840 uid=101
  auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/resolve1"
  interface="org.freedesktop.resolve1.Manager" member="ResolveHostname"
  mask="send" name="org.freedesktop.resolve1" pid=1287
  label="/usr/sbin/ntpd" peer_pid=1024 peer_label="unconfined"

  Sep 29 08:11:53 u64 kernel: audit: type=1107 audit(1475129513.581:28):
  pid=840 uid=101 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/resolve1"
  interface="org.freedesktop.resolve1.Manager" member="ResolveHostname"
  mask="send" name="org.freedesktop.resolve1" pid=1287
  label="/usr/sbin/ntpd" peer_pid=1024 peer_label="unconfined"

  Sep 29 08:11:54 u64 audit[840]: USER_AVC pid=840 uid=101
  auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/resolve1"
  interface="org.freedesktop.resolve1.Manager" member="ResolveHostname"
  mask="send" name="org.freedesktop.resolve1" pid=1287
  label="/usr/sbin/ntpd" peer_pid=1024 peer_label="unconfined"

  Sep 29 08:11:54 u64 kernel: audit: type=1107 audit(1475129514.585:29):
  pid=840 uid=101 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/resolve1"
  interface="org.freedesktop.resolve1.Manager" member="ResolveHostname"
  mask="send" name="org.freedesktop.resolve1" pid=1287
  label="/usr/sbin/ntpd" peer_pid=1024 peer_label="unconfined"

  Sep 29 08:11:55 u64 audit[840]: USER_AVC pid=840 uid=101
  auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/resolve1"
  interface="org.freedesktop.resolve1.Manager" member="ResolveHostname"
  mask="send" name="org.freedesktop.resolve1" pid=1287
  label="/usr/sbin/ntpd" peer_pid=1024 peer_label="unconfined"

  Sep 29 08:11:55 u64 kernel: audit: type=1107 audit(1475129515.124:30):
  pid=840 uid=101 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/resolve1"
  interface="org.freedesktop.resolve1.Manager" member="ResolveHostname"
  mask="send" name="org.freedesktop.resolve1" pid=1287
  label="/usr/sbin/ntpd" peer_pid=1024 peer_label="unconfined"

  
  Note: i wonder if there is a relationship with the previous logged line 
before that error appear:
  ntpd[1282]: Soliciting pool server .

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-17-generic 4.8.0-17.19
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem2213 F pulseaudio
   /dev/snd/pcmC0D0p:   oem2213 F...m pulseaudio
   /dev/snd/controlC0:  oem2213 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Sep 29 10:58:44 2016
  HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16
  IwConfig:
   lono wireless extensions.

   eth1  no wireless extensions.

   eth0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 04

[Kernel-packages] [Bug 1575437] Re: Asus ZenBook UX501VW frequently hangs during boot under Ubuntu 16.04

[chris]

More info,
Fixed boot problem, you need to go to recovery and go to software and 
updates/use nvidia video and intel cpu driver. Basically similar vein to 
noveaumodset=0. I have also removed the archlinux sound codes because I had 
worse audio whitenoise at regular bootup and when I did try to listen to 
something it didn't work. Hopes this helps someone. Cheers

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

Title:
  Asus ZenBook UX501VW frequently hangs during boot under Ubuntu 16.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  A fresh install of Ubuntu Gnome 16.04 on an Asus ZenBook UX501VW hangs
  during boot, approximately 80% to 90% of the time... occasionally it
  manages to complete the startup for no discrenable reason, at which
  point the fan will run at full speed nonstop (very loud) until the
  machine is powered down. Due to the information from
  , I installed the wily 4.3.5 kernel (replacing 4.4.0)
  from ,
  which appears to work perfectly... no bootup hangs or odd fan
  behaviour

  The hang occurs shortly after providing the disk decryption key (I
  opted for full-disk encryption during installation). The issue occurs
  frequently when booting Ubuntu Gnome from a flash drive using "try
  before installation" mode, however, so I'm confident that it's not
  actually encryption related.

  I am *not* using any proprietary drivers (no nvidia, etc.).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: 
boot/vmlinuz-4.4.0-21-generic]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  adric  1574 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Apr 26 19:19:26 2016
  HibernationDevice: RESUME=UUID=74c52e77-74c8-49d1-843b-23584516bd07
  InstallationDate: Installed on 2016-04-26 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: ASUSTeK COMPUTER INC. N501VW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/03/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501VW.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501VW.206:bd02/03/2016:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501VW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1575437] Re: Asus ZenBook UX501VW frequently hangs during boot under Ubuntu 16.04

[chris]

noveau modset and apci=! didn't work, and my trackpad didn't work at regular 
boots (the 10% of the time I got it). recovery mode I have full use.
It may also be because I have two boot devices after boot-repair, ubuntu and 
windows, but I am not sure right now.

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

Title:
  Asus ZenBook UX501VW frequently hangs during boot under Ubuntu 16.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  A fresh install of Ubuntu Gnome 16.04 on an Asus ZenBook UX501VW hangs
  during boot, approximately 80% to 90% of the time... occasionally it
  manages to complete the startup for no discrenable reason, at which
  point the fan will run at full speed nonstop (very loud) until the
  machine is powered down. Due to the information from
  , I installed the wily 4.3.5 kernel (replacing 4.4.0)
  from ,
  which appears to work perfectly... no bootup hangs or odd fan
  behaviour

  The hang occurs shortly after providing the disk decryption key (I
  opted for full-disk encryption during installation). The issue occurs
  frequently when booting Ubuntu Gnome from a flash drive using "try
  before installation" mode, however, so I'm confident that it's not
  actually encryption related.

  I am *not* using any proprietary drivers (no nvidia, etc.).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: 
boot/vmlinuz-4.4.0-21-generic]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  adric  1574 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Apr 26 19:19:26 2016
  HibernationDevice: RESUME=UUID=74c52e77-74c8-49d1-843b-23584516bd07
  InstallationDate: Installed on 2016-04-26 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: ASUSTeK COMPUTER INC. N501VW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/03/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501VW.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501VW.206:bd02/03/2016:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501VW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1575437] Re: Asus ZenBook UX501VW frequently hangs during boot under Ubuntu 16.04

[chris]

Hello all,
I have been working on this for two days now, and it seems that i slowly have 
made things worse as time has gone on. I had all of the problems stated (boot 
hang, blaring fan, white noise), but have found solutions to a few of them, and 
have information that could help pinpoint the others.

1. go to advance boot
2. linux 4.4 recovery works and does not have blaring fan.
2.5 linux 4.4 regular and upstart do not work
3. I have followed the instructions for archlinux which has solved the problem 
of the white noise in the earphones.
https://wiki.archlinux.org/index.php/ASUS_Zenbook_Pro_UX501

boot/fan:
After trying everything from reinstalling to boot-repair to fsck and all of the 
bios options (except flashing the bios, which I am possibly going to do a 
reinstall and flash the bios).

anyone have any more information, would be greatly obliged!

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

Title:
  Asus ZenBook UX501VW frequently hangs during boot under Ubuntu 16.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  A fresh install of Ubuntu Gnome 16.04 on an Asus ZenBook UX501VW hangs
  during boot, approximately 80% to 90% of the time... occasionally it
  manages to complete the startup for no discrenable reason, at which
  point the fan will run at full speed nonstop (very loud) until the
  machine is powered down. Due to the information from
  , I installed the wily 4.3.5 kernel (replacing 4.4.0)
  from ,
  which appears to work perfectly... no bootup hangs or odd fan
  behaviour

  The hang occurs shortly after providing the disk decryption key (I
  opted for full-disk encryption during installation). The issue occurs
  frequently when booting Ubuntu Gnome from a flash drive using "try
  before installation" mode, however, so I'm confident that it's not
  actually encryption related.

  I am *not* using any proprietary drivers (no nvidia, etc.).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: 
boot/vmlinuz-4.4.0-21-generic]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  adric  1574 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Apr 26 19:19:26 2016
  HibernationDevice: RESUME=UUID=74c52e77-74c8-49d1-843b-23584516bd07
  InstallationDate: Installed on 2016-04-26 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: ASUSTeK COMPUTER INC. N501VW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/03/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501VW.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501VW.206:bd02/03/2016:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501VW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1632527] Re: [Dell][XPS]Touchscreen fails to function after resume from s3 by Lid close/open

[AceLan Kao]

>From Mika Westerberg

To backport to kernel 4.4, we need some extra work besides that commit.
   1. 6cee382 ("gpio/pinctrl: sunxi: stop poking around in private vars")
   2. 
diff --git a/drivers/gpio/gpiolib.c b/drivers/gpio/gpiolib.c
index db007a3e2af7..6240dd40e8be 100644
--- a/drivers/gpio/gpiolib.c
+++ b/drivers/gpio/gpiolib.c
@@ -1524,7 +1524,7 @@ bool gpiochip_line_is_irq(struct gpio_chip *chip, 
unsigned int offset)
if (offset >= chip->ngpio)
return false;

-   return test_bit(FLAG_USED_AS_IRQ, &chip->gpiodev->descs[offset].flags);
+   return test_bit(FLAG_USED_AS_IRQ, &chip->desc[offset].flags);
 }
 EXPORT_SYMBOL_GPL(gpiochip_line_is_irq);

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

Title:
  [Dell][XPS]Touchscreen fails to function after resume from s3 by Lid
  close/open

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

Bug description:
  Touchscreen fails to function after resume from s3 by Lid close/open

  Suspend from power menu/ power button cannot reproduce this issue

  Steps:
  1. Install ubuntu 16.04 and boot to OS
  2. suspend the system by Lid close action
  3. resume the session by Lid open
  4. check if touchscreen function works

  Expected results: Touchscreen should still works after Lid open

  Actual results: Touchscreen fails to work after lid open

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

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

[Kernel-packages] [Bug 1630857] Re: Dell Precision Trackpoint not working after suspend

[AceLan Kao]

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

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

Title:
   Dell Precision Trackpoint not working after suspend

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Steps:
  1) Install Ubuntu 16.04
  2) Enter Desktop.
  3) Suspend system.
  4) Using the trackpoint.
  5) Click the left button with DualPoint stick.
  6) Click the right button with DualPoint stick.
  7) Click the middle button with DualPoint stick.
  8) Double-click the left button with DualPoint stick.

  Expected results: Trackpoint and DualPoint stick can work after
  suspend.

  Actual results: Trackpoing and DualPoint stick not working after
  suspend.

  Manufacturer: Dell Inc.

  ProductName: Precision 7500

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

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

[Kernel-packages] [Bug 1632527] Re: [Dell][XPS]Touchscreen fails to function after resume from s3 by Lid close/open

[AceLan Kao]

There is a patch for this issue here
https://marc.info/?l=linux-gpio&m=147610677825233&w=2
but the patch is based on some commits in 4.6, so it can't be used on ubuntu 
xenial 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/1632527

Title:
  [Dell][XPS]Touchscreen fails to function after resume from s3 by Lid
  close/open

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

Bug description:
  Touchscreen fails to function after resume from s3 by Lid close/open

  Suspend from power menu/ power button cannot reproduce this issue

  Steps:
  1. Install ubuntu 16.04 and boot to OS
  2. suspend the system by Lid close action
  3. resume the session by Lid open
  4. check if touchscreen function works

  Expected results: Touchscreen should still works after Lid open

  Actual results: Touchscreen fails to work after lid open

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

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

[Kernel-packages] [Bug 1626222] Re: STC860:alpine-pdq:alpdq5p03: kernel panic when adding vnic

[bugproxy]

** Tags removed: bugnameltc-142343 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/1626222

Title:
  STC860:alpine-pdq:alpdq5p03: kernel panic when adding vnic

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 Released

Bug description:
  Description:Ubuntu 16.04 LTS
  Linux alpdq5p03 4.4.0-22-generic #40-Ubuntu SMP Thu May 12 22:03:35 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  Problem Description :

  When I created a vNIC on alpdq5p03 using U78C7.001.KIC1906-P1-C12-T1
  via alpdq5p08 and U78C7.001.KIC1906-P1-C12-T2 via alpdq5p09 as the
  backing devices I got a kernel panic.

  [  129.977324] ibmvnic 3004: Virtual Adapter failed (rc=8)
  [  129.977346] Unable to handle kernel paging request for data at address 
0x00f1
  [  129.977351] Faulting instruction address: 0xd00010882434
  [  129.977355] Oops: Kernel access of bad area, sig: 11 [#1]
  [  129.977359] SMP NR_CPUS=2048 NUMA pSeries
  [  129.977364] Modules linked in: ibmvnic rpadlpar_io rpaphp nfsv3 nfs_acl 
rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache dccp_diag dccp 
tcp_diag udp_diag inet_diag unix_diag af_packet_diag netlink_diag rtc_generic 
pseries_rng binfmt_misc sunrpc autofs4 ibmvscsi ibmveth
  [  129.977392] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.4.0-22-generic 
#40-Ubuntu
  [  129.977397] task: c15566b0 ti: c01d8000 task.ti: 
c15b
  [  129.977401] NIP: d00010882434 LR: d00010882420 CTR: 
c02b25f0
  [  129.977406] REGS: c01db9c0 TRAP: 0300   Not tainted  
(4.4.0-22-generic)
  [  129.977410] MSR: 80009033   CR: 48048224  
XER: 2010
  [  129.977422] CFAR: c0008468 DAR: 00f1 DSISR: 4000 
SOFTE: 0 
  GPR00: d00010882420 c01dbc40 d00010894240  
  GPR04: c01ff4039ee0  001ffdd8 2082 
  GPR08: c0f9fda8 c0f9fda8 001ffdd8 d000108896e8 
  GPR12: c02b25f0 ce7e c15eef18 c0f9d678 
  GPR16: 0001  c01fd3960e18 c01fd3960db0 
  GPR20: c15b c01fd3960d98 c01fd3960e08 c01fd3960900 
  GPR24: c01fd3960d88 c01fd39bf000 c01fd39bf048  
  GPR28: 0100 0200 00f0 c01fd3960900 
  [  129.977482] NIP [d00010882434] ibmvnic_free_inflight+0x104/0x330 
[ibmvnic]
  [  129.977488] LR [d00010882420] ibmvnic_free_inflight+0xf0/0x330 
[ibmvnic]
  [  129.977492] Call Trace:
  [  129.977496] [c01dbc40] [d00010882420] 
ibmvnic_free_inflight+0xf0/0x330 [ibmvnic] (unreliable)
  [  129.977503] [c01dbce0] [d00010887188] 
ibmvnic_handle_crq+0x3a8/0x2010 [ibmvnic]
  [  129.977509] [c01dbda0] [d00010888ea8] 
ibmvnic_interrupt+0xb8/0x198 [ibmvnic]
  [  129.977517] [c01dbe10] [c0130660] 
handle_irq_event_percpu+0xa0/0x320
  [  129.977523] [c01dbed0] [c0130948] 
handle_irq_event+0x68/0xc0
  [  129.977528] [c01dbf00] [c0135c2c] 
handle_fasteoi_irq+0xec/0x2b0
  [  129.977534] [c01dbf30] [c012f844] 
generic_handle_irq+0x54/0x80
  [  129.977539] [c01dbf60] [c0011320] __do_irq+0x80/0x1d0
  [  129.977545] [c01dbf90] [c0024800] call_do_irq+0x14/0x24
  [  129.977550] [c15b39a0] [c0011508] do_IRQ+0x98/0x140
  [  129.977555] [c15b39f0] [c0002594] 
hardware_interrupt_common+0x114/0x180
  [  129.977563] --- interrupt: 501 at plpar_hcall_norets+0x1c/0x28
  [  129.977563] LR = check_and_cede_processor+0x34/0x50
  [  129.977570] [c15b3ce0] [c090d9f0] 
check_and_cede_processor+0x20/0x50 (unreliable)
  [  129.977576] [c15b3d40] [c090da94] 
dedicated_cede_loop+0x74/0x190
  [  129.977582] [c15b3d80] [c090ac20] 
cpuidle_enter_state+0x160/0x410
  [  129.977588] [c15b3de0] [c0119a88] call_cpuidle+0x78/0xd0
  [  129.977593] [c15b3e20] [c0119e5c] 
cpu_startup_entry+0x37c/0x480
  [  129.977599] [c15b3ee0] [c000bdcc] rest_init+0xac/0xc0
  [  129.977605] [c15b3f00] [c0ea3f5c] start_kernel+0x53c/0x558
  [  129.977610] [c15b3f90] [c0008c6c] 
start_here_common+0x20/0xa8
  [  129.977615] Instruction dump:
  [  129.977617] e95e0010 7fc3f378 f92a0008 f949 fb9e0010 fbbe0018 480072cd 
e8410018 
  [  129.977626] ebde0010 7fb6f040 3bdefff0 419e00f4 <893e0001> 2f890009 
409effb4 7ea3ab78 
  [  129.977636] ---[ end trace 79d415687d3074f2 ]---
  [  129.979495] 
  [  131.979529] Kernel panic - not syncing: Fatal exception in interrupt
  [  131.985480] ---[ end Kernel panic - not syncing: Fatal exception in 
interrupt

  Th

[Kernel-packages] [Bug 1626222] Re: STC860:alpine-pdq:alpdq5p03: kernel panic when adding vnic

[Tim Gardner]

I cannot tell what kernel version caused this stack dump, but
Ubuntu-4.4.0-42.62 has yet to be uploaded.

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

Title:
  STC860:alpine-pdq:alpdq5p03: kernel panic when adding vnic

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 Released

Bug description:
  Description:Ubuntu 16.04 LTS
  Linux alpdq5p03 4.4.0-22-generic #40-Ubuntu SMP Thu May 12 22:03:35 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  Problem Description :

  When I created a vNIC on alpdq5p03 using U78C7.001.KIC1906-P1-C12-T1
  via alpdq5p08 and U78C7.001.KIC1906-P1-C12-T2 via alpdq5p09 as the
  backing devices I got a kernel panic.

  [  129.977324] ibmvnic 3004: Virtual Adapter failed (rc=8)
  [  129.977346] Unable to handle kernel paging request for data at address 
0x00f1
  [  129.977351] Faulting instruction address: 0xd00010882434
  [  129.977355] Oops: Kernel access of bad area, sig: 11 [#1]
  [  129.977359] SMP NR_CPUS=2048 NUMA pSeries
  [  129.977364] Modules linked in: ibmvnic rpadlpar_io rpaphp nfsv3 nfs_acl 
rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache dccp_diag dccp 
tcp_diag udp_diag inet_diag unix_diag af_packet_diag netlink_diag rtc_generic 
pseries_rng binfmt_misc sunrpc autofs4 ibmvscsi ibmveth
  [  129.977392] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.4.0-22-generic 
#40-Ubuntu
  [  129.977397] task: c15566b0 ti: c01d8000 task.ti: 
c15b
  [  129.977401] NIP: d00010882434 LR: d00010882420 CTR: 
c02b25f0
  [  129.977406] REGS: c01db9c0 TRAP: 0300   Not tainted  
(4.4.0-22-generic)
  [  129.977410] MSR: 80009033   CR: 48048224  
XER: 2010
  [  129.977422] CFAR: c0008468 DAR: 00f1 DSISR: 4000 
SOFTE: 0 
  GPR00: d00010882420 c01dbc40 d00010894240  
  GPR04: c01ff4039ee0  001ffdd8 2082 
  GPR08: c0f9fda8 c0f9fda8 001ffdd8 d000108896e8 
  GPR12: c02b25f0 ce7e c15eef18 c0f9d678 
  GPR16: 0001  c01fd3960e18 c01fd3960db0 
  GPR20: c15b c01fd3960d98 c01fd3960e08 c01fd3960900 
  GPR24: c01fd3960d88 c01fd39bf000 c01fd39bf048  
  GPR28: 0100 0200 00f0 c01fd3960900 
  [  129.977482] NIP [d00010882434] ibmvnic_free_inflight+0x104/0x330 
[ibmvnic]
  [  129.977488] LR [d00010882420] ibmvnic_free_inflight+0xf0/0x330 
[ibmvnic]
  [  129.977492] Call Trace:
  [  129.977496] [c01dbc40] [d00010882420] 
ibmvnic_free_inflight+0xf0/0x330 [ibmvnic] (unreliable)
  [  129.977503] [c01dbce0] [d00010887188] 
ibmvnic_handle_crq+0x3a8/0x2010 [ibmvnic]
  [  129.977509] [c01dbda0] [d00010888ea8] 
ibmvnic_interrupt+0xb8/0x198 [ibmvnic]
  [  129.977517] [c01dbe10] [c0130660] 
handle_irq_event_percpu+0xa0/0x320
  [  129.977523] [c01dbed0] [c0130948] 
handle_irq_event+0x68/0xc0
  [  129.977528] [c01dbf00] [c0135c2c] 
handle_fasteoi_irq+0xec/0x2b0
  [  129.977534] [c01dbf30] [c012f844] 
generic_handle_irq+0x54/0x80
  [  129.977539] [c01dbf60] [c0011320] __do_irq+0x80/0x1d0
  [  129.977545] [c01dbf90] [c0024800] call_do_irq+0x14/0x24
  [  129.977550] [c15b39a0] [c0011508] do_IRQ+0x98/0x140
  [  129.977555] [c15b39f0] [c0002594] 
hardware_interrupt_common+0x114/0x180
  [  129.977563] --- interrupt: 501 at plpar_hcall_norets+0x1c/0x28
  [  129.977563] LR = check_and_cede_processor+0x34/0x50
  [  129.977570] [c15b3ce0] [c090d9f0] 
check_and_cede_processor+0x20/0x50 (unreliable)
  [  129.977576] [c15b3d40] [c090da94] 
dedicated_cede_loop+0x74/0x190
  [  129.977582] [c15b3d80] [c090ac20] 
cpuidle_enter_state+0x160/0x410
  [  129.977588] [c15b3de0] [c0119a88] call_cpuidle+0x78/0xd0
  [  129.977593] [c15b3e20] [c0119e5c] 
cpu_startup_entry+0x37c/0x480
  [  129.977599] [c15b3ee0] [c000bdcc] rest_init+0xac/0xc0
  [  129.977605] [c15b3f00] [c0ea3f5c] start_kernel+0x53c/0x558
  [  129.977610] [c15b3f90] [c0008c6c] 
start_here_common+0x20/0xa8
  [  129.977615] Instruction dump:
  [  129.977617] e95e0010 7fc3f378 f92a0008 f949 fb9e0010 fbbe0018 480072cd 
e8410018 
  [  129.977626] ebde0010 7fb6f040 3bdefff0 419e00f4 <893e0001> 2f890009 
409effb4 7ea3ab78 
  [  129.977636] ---[ end trace 79d415687d3074f2 ]---
  [  129.979495] 
  [  131.979529] Kernel panic - not syncing: Fatal exception in interrupt
  [  131.985480] ---[ end Kernel 

[Kernel-packages] [Bug 1632527] Re: [Dell][XPS]Touchscreen fails to function after resume from s3 by Lid close/open

[AceLan Kao]

upstream bug is here
https://bugzilla.kernel.org/show_bug.cgi?id=176361

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

Title:
  [Dell][XPS]Touchscreen fails to function after resume from s3 by Lid
  close/open

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

Bug description:
  Touchscreen fails to function after resume from s3 by Lid close/open

  Suspend from power menu/ power button cannot reproduce this issue

  Steps:
  1. Install ubuntu 16.04 and boot to OS
  2. suspend the system by Lid close action
  3. resume the session by Lid open
  4. check if touchscreen function works

  Expected results: Touchscreen should still works after Lid open

  Actual results: Touchscreen fails to work after lid open

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

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

[Kernel-packages] [Bug 1632527] [NEW] [Dell][XPS]Touchscreen fails to function after resume from s3 by Lid close/open

[AceLan Kao]

Public bug reported:

Touchscreen fails to function after resume from s3 by Lid close/open

Suspend from power menu/ power button cannot reproduce this issue

Steps:
1. Install ubuntu 16.04 and boot to OS
2. suspend the system by Lid close action
3. resume the session by Lid open
4. check if touchscreen function works

Expected results: Touchscreen should still works after Lid open

Actual results: Touchscreen fails to work after lid open

** Affects: hwe-next
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: AceLan Kao (acelankao)
 Status: In Progress


** Tags: originate-from-1607594 somerville

** Tags added: originate-from-1607594 somerville

** Bug watch added: Linux Kernel Bug Tracker #176361
   http://bugzilla.kernel.org/show_bug.cgi?id=176361

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

Title:
  [Dell][XPS]Touchscreen fails to function after resume from s3 by Lid
  close/open

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

Bug description:
  Touchscreen fails to function after resume from s3 by Lid close/open

  Suspend from power menu/ power button cannot reproduce this issue

  Steps:
  1. Install ubuntu 16.04 and boot to OS
  2. suspend the system by Lid close action
  3. resume the session by Lid open
  4. check if touchscreen function works

  Expected results: Touchscreen should still works after Lid open

  Actual results: Touchscreen fails to work after lid open

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

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

[Kernel-packages] [Bug 1628976] Re: Ubuntu 16.10: Oops panic in move_page_tables/page_remove_rmap after running memory_stress_ng.

[Seth Forshee]

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

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

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

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

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

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

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

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

Title:
  Ubuntu 16.10: Oops panic in move_page_tables/page_remove_rmap after
  running memory_stress_ng.

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

Bug description:
  FYI Canonical:

  We have been seeing various page handling issues during memory stress
  in the 4.8 kernels.  The following is the most recent issue resulting
  in system panics on this host after the 4.8.0-17 update:

  == Comment: #17 - PAVITHRA R. PRAKASH - 2016-09-28 06:26:21 ==
  Hi,

  Tried running on 4.8.0-17-generic kernel. Getting below call trace and
  system crashes. Attaching logs.

  [ 2959.364333] Unable to handle kernel paging request for data at address 
0xf2fe4020
  [ 2959.364345] Faulting instruction address: 0xc02bb2a0
  [ 2959.364356] Oops: Kernel access of bad area, sig: 11 [#1]
  [ 2959.364364] SMP NR_CPUS=2048 NUMA pSeries
  [ 2959.364377] Modules linked in: rpadlpar_io rpaphp dccp_diag dccp tcp_diag 
udp_diag inet_diag unix_diag af_packet_diag netlink_diag bnx2x mdio libcrc32c 
pseries_rng vmx_crypto binfmt_misc ip_tables x_tables autofs4 ibmvscsi 
crc32c_vpmsum
  [ 2959.364441] CPU: 13 PID: 108 Comm: oom_reaper Not tainted 4.8.0-17-generic 
#19-Ubuntu
  [ 2959.364452] task: c004fbdf9c00 task.stack: c004fbe0
  [ 2959.364461] NIP: c02bb2a0 LR: c0300618 CTR: 
c009ca40
  [ 2959.364471] REGS: c004fbe036e0 TRAP: 0300   Not tainted  
(4.8.0-17-generic)
  [ 2959.364481] MSR: 80010280b033   
CR: 24028844  XER: 200c
  [ 2959.364526] CFAR: c0300614 DAR: f2fe4020 DSISR: 4000 
SOFTE: 1 
 GPR00: c0300618 c004fbe03960 c14e5e00 
f2fe4000 
 GPR04: 0001 0800  
c1665e00 
 GPR08: f900a196 0001 02fe4000 
 
 GPR12: 8800 c1b37500 0008 
c1ffe7ff 
 GPR16: c004f62a55f0 3fff9a00 3fff9900 
 
 GPR20: c004fbe03b80 c004e0713800 8e017c3302c0 
0001 
 GPR24: c000fb3614c8 c000fce9d990 c000fce9d6e4 
96a100f90b40 
 GPR28: f2fe4000 c000fb3614c8 0001 
f2fe4000 
  [ 2959.364673] NIP [c02bb2a0] page_remove_rmap+0x30/0x4b0
  [ 2959.364685] LR [c0300618] zap_huge_pmd+0xf8/0x480
  [ 2959.364692] Call Trace:
  [ 2959.364699] [c004fbe03960] [c004fbe039a0] 0xc004fbe039a0 
(unreliable)
  [ 2959.364714] [c004fbe039a0] [c0300618] zap_huge_pmd+0xf8/0x480
  [ 2959.364726] [c004fbe039f0] [c02a68d8] 
unmap_page_range+0xd08/0xee0
  [ 2959.364740] [c004fbe03b20] [c025c474] 
__oom_reap_task+0x204/0x2c0
  [ 2959.364752] [c004fbe03c80] [c025cda8] oom_reaper+0x1e8/0x300
  [ 2959.364765] [c004fbe03d80] [c00fd120] kthread+0x110/0x130
  [ 2959.364778] [c004fbe03e30] [c00098f0] 
ret_from_kernel_thread+0x5c/0x6c
  [ 2959.364788] Instruction dump:
  [ 2959.364796] 3c4c0123 3842ab90 7c0802a6 fba1ffe8 fbc1fff0 fbe1fff8 f8010010 
f821ffc1 
  [ 2959.364821] 7c7f1b78 7c9e2378 6000 6000  71480001 
392a 40820008 
  [ 2959.364871] ---[ end trace 178b14c6911b70dc ]---
  [ 2959.372762] 
  [ 2959.372798] Sending IPI to other CPUs
  [ 2959.373834] IPI complete

  Thanks,
  Pavithra

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

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

[Kernel-packages] [Bug 1632462] Re: [Trusty->Yakkety] powerpc/64: Fix incorrect return value from __copy_tofrom_user

[Seth Forshee]

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

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

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

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

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

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

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

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

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

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

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

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

Title:
  [Trusty->Yakkety] powerpc/64: Fix incorrect return value from
  __copy_tofrom_user

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

Bug description:
  == SRU Justification ==
  Impacts all releases from Trusty through Yakkety

  http://paste.ubuntu.com/23309548/

  From ca47910e3b549501b6a3ff786174d2f0d4748ccf Mon Sep 17 00:00:00 2001
  From: Paul Mackerras 
  Date: Tue, 11 Oct 2016 22:18:58 +1100
  Subject: [PATCH] powerpc/64: Fix incorrect return value from__copy_tofrom_user

  Debugging a data corruption issue with virtio-net/vhost-net led to
  the observation that __copy_tofrom_user was occasionally returning
  a value 16 larger than it should.  Since the return value from
  __copy_tofrom_user is the number of bytes not copied, this means
  that __copy_tofrom_user can occasionally return a value larger
  than the number of bytes it was asked to copy.  In turn this can
  cause higher-level copy functions such as copy_page_to_iter_iovec
  to corrupt memory by copying data into the wrong memory locations.

  It turns out that the failing case involves a fault on the store
  at label 79, and at that point the first unmodified byte of the
  destination is at R3 + 16.  Consequently the exception handler
  for that store needs to add 16 to R3 before using it to work out
  how many bytes were not copied, but in this one case it was not
  adding the offset to R3.  To fix it, this moves the label 179 to
  the point where we add 16 to R3.  I have checked manually all the
  exception handlers for the loads and stores in this code and the
  rest of them are correct (it would be excellent to have an
  automated test of all the exception cases).

  Signed-off-by: Paul Mackerras 
  ---
   arch/powerpc/lib/copyuser_64.S | 2 +-
   1 file changed, 1 insertion(+), 1 deletion(-)

  diff --git a/arch/powerpc/lib/copyuser_64.S b/arch/powerpc/lib/copyuser_64.S
  index f09899e..7b22624 100644
  --- a/arch/powerpc/lib/copyuser_64.S
  +++ b/arch/powerpc/lib/copyuser_64.S
  @@ -359,6 +359,7 @@ END_FTR_SECTION_IFCLR(CPU_FTR_UNALIGNED_LD_STD)
addir3,r3,8
   171:
   177:
  +179:
addir3,r3,8
   370:
   372:
  @@ -373,7 +374,6 @@ END_FTR_SECTION_IFCLR(CPU_FTR_UNALIGNED_LD_STD)
   173:
   174:
   175:
  -179:
   181:
   184:
   186:
  -- 
  2.7.4

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

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

[Kernel-packages] [Bug 1632116] Re: Paths not failed properly when unmapping virtual FC ports in VIOS (using ibmvfc)

[Seth Forshee]

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

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

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

Title:
  Paths not failed properly when unmapping virtual FC ports in VIOS
  (using ibmvfc)

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

Bug description:
  ---Problem Description---
  vios vfc unmap (vfcmap -vadapter vfchost0 -fcp) can result in no i/o being 
retried nor device offline.

  ---uname output---
  Linux ubuntu16 4.4.0-9136-generic #55-Ubuntu SMP Fri Aug 26 05:56:24 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = Power8 LPAR 
   
  ---Steps to Reproduce---
   Ubuntu 16.10 lpar with two vfc adapters mapped to SAN Storage and configured 
with mulitpath.
  In vios do:  vfcmap -vadapter vfchost0 -fcp (where vfchost0 maps to test 
lpar).  multipath -ll and lvm commands hang in linux lpar.  tail 
/var/log/message hangs sometimes. multipath doesn't see failing devices and 
doesn't mark paths down.

  
  Fyi ...
   the following patch fixes the problem, which is now upstream accepted in 
the scsi tree as
  
http://git.kernel.org/cgit/linux/kernel/git/mkp/scsi.git/commit/?h=for-next&id=07d0e9a847401ffd2f09bd450d41644cd090e81d
  ("scsi: ibmvfc: Fix I/O hang when port is not mapped")

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

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

[Kernel-packages] [Bug 1630311] Re: arm64: SPCR console not autodetected

[Seth Forshee]

** Also affects: linux (Ubuntu Yakkety)
   Importance: High
 Assignee: dann frazier (dannf)
   Status: In Progress

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

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

Title:
  arm64: SPCR console not autodetected

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  ARM servers that boot in ACPI mode will not autodetect their console 
settings. The SBSA (Server Base System Architecture) spec requires that these 
settings be specified using the ACPI SPCR table. Support for parsing this table 
just landed upstream in the 4.9 merge window.

  [Test Case]
  Boot an ARM system in ACPI mode(I used a Cavium ThunderX CRB1S w/ 
acpi=force). You'll have no console unless you know and explicitly specify the 
correct console= parameter on the cmdline.

  [Regression Risk]
  The changes cleanly cherry-pick from upstream, so we'll have upstream support 
for any regressions. Though the patches do touch code in arch-indep 
directories, that code is limited by config options that restrict the 
functionality to either ARM or OpenFirmware systems:

  of/serial: move earlycon early_param handling to serial
   - Cleanup of OF-specific code.

  ACPI: parse SPCR and enable matching console
   - Adds parse_spcr() for all archs, but this function is only called from
 arch/arm64 code (next patch).
   - Adds an arch-generic call to a stub function only if the OF-specific
 earlycon parameter is specified. Further, that stub function just returns
 -ENODEV on non-OF systems.

  ARM64: ACPI: enable ACPI_SPCR_TABLE
   - ARM64-specific code, only built if CONFIG_ACPI=y

  serial: pl011: add console matching function
   - Driver for ARM AMBA-type serial port - code is only activated if a
 console=pl011,* parameter is specified on the cmdline.

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

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

[Kernel-packages] [Bug 1630990] Re: include/linux/security.h header syntax error with !CONFIG_SECURITYFS

[Seth Forshee]

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

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

Title:
  include/linux/security.h header syntax error with !CONFIG_SECURITYFS

Status in linux package in Ubuntu:
  Fix Committed
Status in zfcpdump-kernel package in Ubuntu:
  Fix Released
Status in linux source package in Yakkety:
  Fix Committed
Status in zfcpdump-kernel source package in Yakkety:
  Fix Released

Bug description:
CC  init/main.o
  In file included from init/main.c:34:0:
  ./include/linux/security.h: In function ‘__securityfs_setup_d_inode’:
  ./include/linux/security.h:1638:42: error: expected declaration specifiers 
before ‘)’ token
const struct inode_operations *iops))
^
  ./include/linux/security.h:1648:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or 
‘__attribute__’ before ‘{’ token

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

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

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

[Brad Figg]

This change was made by a bot.

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

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

Title:
  Bluetooth: hci0 command 0x200f tx timeout

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [   10.730856] Bluetooth: hci0 command 0x2001 tx timeout
  [   10.730892] Bluetooth: hci0 sending frame failed (-19)

  [...]

  [   12.746738] Bluetooth: hci0 command 0x2007 tx timeout
  [   12.746762] Bluetooth: hci0 sending frame failed (-19)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-22-generic 4.8.0-22.24
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   2141 F...m pulseaudio
   /dev/snd/controlC0:  caravena   2141 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Oct 11 18:28:59 2016
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (443 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-22-generic N/A
   linux-backports-modules-4.8.0-22-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1632484] Re: linux: 4.8.0-23.25 -proposed tracker

[Brad Figg]

** Changed in: kernel-development-workflow/prepare-package
   Status: New => Confirmed

** Changed in: kernel-development-workflow/prepare-package-meta
   Status: New => Confirmed

** Changed in: kernel-development-workflow/prepare-package-signed
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 4.8.0-23.25 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+ 
+ kernel-phase-changed:Tuesday, 11. October 2016 21:45 UTC
+ kernel-phase:Packaging

** Description changed:

  This bug is for tracking the 4.8.0-23.25 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  kernel-phase-changed:Tuesday, 11. October 2016 21:45 UTC
  kernel-phase:Packaging
+ 
+ -- swm properties --
+ derivative-trackers-created: true
+ phase: Packaging

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

Title:
  linux: 4.8.0-23.25 -proposed tracker

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

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

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

  kernel-phase-changed:Tuesday, 11. October 2016 21:45 UTC
  kernel-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

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

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

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

[bugproxy]

--- Comment From cdead...@us.ibm.com 2016-10-11 17:38 EDT---
transferred to ppclinux_nonconfidential_BZilla using CMVC. updates not visible 
in BQ. State: Open by: avkuttan on 26 July 2016 04:49:05 

Transfer this defect to Linux team for further analysis. State: Open
by: panico on 25 July 2016 18:02:09 

There is also another defect opened (SW360179) on a glacier park logging
a miscompare on another ubuntu 16.04 guest, but on a ubuntu 16.04 KVM
host. State: Assigned by: cde00 on 11 October 2016 16:02:54 

== Comment: #1 - Application Cdeadmin  - 2016-07-26
11:20:22 == State: Open by: avkuttan on 26 July 2016 04:49:05 

There is also another defect opened (SW360179) on a glacier park logging
a miscompare on another ubuntu 16.04 guest, but on a ubuntu 16.04 KVM
host. State: Assigned by: cde00 on 11 October 2016 16:24:06 

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

Title:
  STC860:Tuleta-L:KVM:iap03:HTX logs miscompares on multiple adapters on
  ubuntu 16.04 guest.

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Application Cdeadmin  -
  2016-07-26 11:20:20 ==

  
  == Comment: #1 - Application Cdeadmin  - 2016-07-26 
11:20:22 ==
   State: Open by: panico on 25 July 2016 18:02:09 

  Contact Information:
  
  Defect Originator:  Michael Panico
  Defect Originator   pan...@us.ibm.com

  Backup: Deepti Umarani
  Backup ST ID: Deepti S Umarani/India/IBM

  System Info:
  
  Machine Type:8284-22A
  Card Type:...FSP2_P8LE
  Current Boot Side:...T
  Next Boot Side:..T
  PT_Swap:.1
  Current Side Driver:.fips860/b0713a_1630.860 

  Ubuntu KVM Host:
  root@iaos1:/tmp# uname -a
  Linux iaos1 4.4.0-30-generic #49-Ubuntu SMP Fri Jul 1 10:00:36 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
  root@iaos1:/tmp# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10
  Codename: yakkety

  Ubuntu Guest:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m uname -a
  Linux iap03 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  Codename: xenial

  HTX level on ubuntu 16.04 guest:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m dpkg -l | grep htxubuntu
  ii  htxubuntu  402 ppc64el

  Problem Description:
  
  Running networks (via bridging) on three different guests (other linux, 
ubuntu 16.10 and ubuntu 16.04) the ubuntu 16.04 guest logged a miscompare on 
the austin adapter and the shinerT adapter.  The shinerT ran for 24 hours and 
the austin for 72 hours before logging miscompares.

  From /tmp/htxerr:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m cat /tmp/htxerr

  /dev/enp0s6   Jul 23 14:29:00 2016 err=00e3 sev=4 hxecom
  R(102.1.2.20.50854) connected to W(102.1.1.20.39073)
  Miscompare with packet 0, data size = 51062. miscompare_count=0 pakLen = 
51082 
  Miscompare at displacement (decimal) = 23876 
  wbuf = 
  rbuf = 

  For stanza 0, TCP connection, bufmin=3, bufmax=65000, bufinc=10531
  Consecutive prior good reads= 70739865,  good bytes read= 2868570843930

  /dev/enp0s6   Jul 23 14:29:00 2016 err=00d8 sev=4 hxecom
  Shutting down testing due to error flag - 1
  R(102.1.2.20.50854) connected to W(102.1.1.20.39073)
  For stanza 0, TCP connection, bufmin=3, bufmax=65000, bufinc=10531
  Consecutive prior good reads=0,  good bytes read= 0

  /dev/enp0s7   Jul 23 14:29:00 2016 err=00fb0068 sev=1 hxecom
  W(102.1.1.20.39073) connected to R(102.1.2.20.50854)
  Wrote 878 characters, expected 963
  Write failed - Connection reset by peer.
  For stanza 1, TCP connection,  bufmin=3, bufmax=2869, bufinc=94
  Consecutive prior good writes= 25459432,  good bytes written=   
35283290616

  htx_messages  Jul 23 14:29:01 2016 err= sev=1 hxssup
  hxecom HE program for enp0s6 terminated by exit(0) call.

  htx_messages  Jul 23 16:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 7206 seconds.

  htx_messages  Jul 23 18:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 14406 seconds.

  htx_messages  Jul 23 20:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (s

[Kernel-packages] [Bug 1632484] [NEW] linux: 4.8.0-23.25 -proposed tracker

[Seth Forshee]

Public bug reported:

This bug is for tracking the 4.8.0-23.25 upload package. This bug will
contain status and testing results related to that upload.

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

kernel-phase-changed:Tuesday, 11. October 2016 21:45 UTC
kernel-phase:Packaging

-- swm properties --
derivative-trackers-created: true
phase: Packaging

** Affects: kernel-development-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-development-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-development-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-development-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-development-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

** Affects: kernel-development-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: linux (Ubuntu Yakkety)
 Importance: Medium
 Status: Confirmed


** Tags: block-proposed kernel-release-tracking-bug yakkety

** Tags added: kernel-release-tracking-bug

** Tags added: block-proposed

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

** Tags added: yakkety

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

** Also affects: kernel-development-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/promote-to-release
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/regression-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-development-workflow
   Status: New => In Progress

** Changed in: kernel-development-workflow
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package-signed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/promote-to-proposed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/promote-to-release
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

** Changed in: kernel-development-workflow/regression-testing
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/regression-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

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

[Kernel-packages] [Bug 1435040] Re: Ubuntu Phone does not connect to car-bluetooth

[Marco A. Harrendorf]

With OTA13 it is still not working together with my Garmin Navigon navigation 
system.
I can pair my phone and the navigation system. The navigation system can also 
download the addressbook and initiate calls, but during a call no audio is 
routed between the phone and the navigation system.

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

Title:
  Ubuntu Phone does not connect to car-bluetooth

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  With my FORD Focus Car, pairing does not work. The bluetooth system in
  the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition"
  and then prompts me to connect with a 4-digit pin code, but the Ubuntu
  phone doesn't react at all and after a while the car system says that
  it failed to connect.

  image: 20150310-3201c0a
  KRILIN01A-S15A_BQ_L100EN_2020_150312
  OS Build 20

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+subscriptions

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

[Kernel-packages] [Bug 1632481] [NEW] Bluetooth: hci0 command 0x200f tx timeout

[Cristian Aravena Romero]

Public bug reported:

[   10.730856] Bluetooth: hci0 command 0x2001 tx timeout
[   10.730892] Bluetooth: hci0 sending frame failed (-19)

[...]

[   12.746738] Bluetooth: hci0 command 0x2007 tx timeout
[   12.746762] Bluetooth: hci0 sending frame failed (-19)

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-22-generic 4.8.0-22.24
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   caravena   2141 F...m pulseaudio
 /dev/snd/controlC0:  caravena   2141 F pulseaudio
CurrentDesktop: GNOME
Date: Tue Oct 11 18:28:59 2016
HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
InstallationDate: Installed on 2015-07-26 (443 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-22-generic N/A
 linux-backports-modules-4.8.0-22-generic  N/A
 linux-firmware1.161
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P14AAJ
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SAMSUNG_NP1234567890
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 530U3C/530U4C
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


** Tags: amd64 apport-bug 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/1632481

Title:
  Bluetooth: hci0 command 0x200f tx timeout

Status in linux package in Ubuntu:
  New

Bug description:
  [   10.730856] Bluetooth: hci0 command 0x2001 tx timeout
  [   10.730892] Bluetooth: hci0 sending frame failed (-19)

  [...]

  [   12.746738] Bluetooth: hci0 command 0x2007 tx timeout
  [   12.746762] Bluetooth: hci0 sending frame failed (-19)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-22-generic 4.8.0-22.24
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   2141 F...m pulseaudio
   /dev/snd/controlC0:  caravena   2141 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Oct 11 18:28:59 2016
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (443 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-22-generic N/A
   linux-backports-modules-4.8.0-22-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

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

[bugproxy]

--- Comment From cha...@us.ibm.com 2016-10-11 17:05 EDT---
*** Bug 147358 has been marked as a duplicate of 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/1632466

Title:
  STC860:Tuleta-L:KVM:iap03:HTX logs miscompares on multiple adapters on
  ubuntu 16.04 guest.

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Application Cdeadmin  -
  2016-07-26 11:20:20 ==

  
  == Comment: #1 - Application Cdeadmin  - 2016-07-26 
11:20:22 ==
   State: Open by: panico on 25 July 2016 18:02:09 

  Contact Information:
  
  Defect Originator:  Michael Panico
  Defect Originator   pan...@us.ibm.com

  Backup: Deepti Umarani
  Backup ST ID: Deepti S Umarani/India/IBM

  System Info:
  
  Machine Type:8284-22A
  Card Type:...FSP2_P8LE
  Current Boot Side:...T
  Next Boot Side:..T
  PT_Swap:.1
  Current Side Driver:.fips860/b0713a_1630.860 

  Ubuntu KVM Host:
  root@iaos1:/tmp# uname -a
  Linux iaos1 4.4.0-30-generic #49-Ubuntu SMP Fri Jul 1 10:00:36 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
  root@iaos1:/tmp# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10
  Codename: yakkety

  Ubuntu Guest:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m uname -a
  Linux iap03 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  Codename: xenial

  HTX level on ubuntu 16.04 guest:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m dpkg -l | grep htxubuntu
  ii  htxubuntu  402 ppc64el

  Problem Description:
  
  Running networks (via bridging) on three different guests (other linux, 
ubuntu 16.10 and ubuntu 16.04) the ubuntu 16.04 guest logged a miscompare on 
the austin adapter and the shinerT adapter.  The shinerT ran for 24 hours and 
the austin for 72 hours before logging miscompares.

  From /tmp/htxerr:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m cat /tmp/htxerr

  /dev/enp0s6   Jul 23 14:29:00 2016 err=00e3 sev=4 hxecom
  R(102.1.2.20.50854) connected to W(102.1.1.20.39073)
  Miscompare with packet 0, data size = 51062. miscompare_count=0 pakLen = 
51082 
  Miscompare at displacement (decimal) = 23876 
  wbuf = 
  rbuf = 

  For stanza 0, TCP connection, bufmin=3, bufmax=65000, bufinc=10531
  Consecutive prior good reads= 70739865,  good bytes read= 2868570843930

  /dev/enp0s6   Jul 23 14:29:00 2016 err=00d8 sev=4 hxecom
  Shutting down testing due to error flag - 1
  R(102.1.2.20.50854) connected to W(102.1.1.20.39073)
  For stanza 0, TCP connection, bufmin=3, bufmax=65000, bufinc=10531
  Consecutive prior good reads=0,  good bytes read= 0

  /dev/enp0s7   Jul 23 14:29:00 2016 err=00fb0068 sev=1 hxecom
  W(102.1.1.20.39073) connected to R(102.1.2.20.50854)
  Wrote 878 characters, expected 963
  Write failed - Connection reset by peer.
  For stanza 1, TCP connection,  bufmin=3, bufmax=2869, bufinc=94
  Consecutive prior good writes= 25459432,  good bytes written=   
35283290616

  htx_messages  Jul 23 14:29:01 2016 err= sev=1 hxssup
  hxecom HE program for enp0s6 terminated by exit(0) call.

  htx_messages  Jul 23 16:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 7206 seconds.

  htx_messages  Jul 23 18:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 14406 seconds.

  htx_messages  Jul 23 20:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 21606 seconds.

  htx_messages  Jul 23 22:29:08 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 28807 seconds.

  htx_messages  Jul 24 00:29:08 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 36007 seconds.

  /dev/enp0s4   Jul 25 04:56:13 2016 err=00e3 sev=4 hxecom
  R(103.1.2.20.36665) connected to W(103.1.1.20.40459)
  Miscompare with packet 0, data size = 3. miscompare_count=0 pakLen = 
30020 
  Miscompare at displacement (decimal) = 17508 
  wbuf = ff

[Kernel-packages] [Bug 1632471] console 's log file

[bugproxy]

Default Comment by Bridge

** Attachment added: "console 's log file"
   
https://bugs.launchpad.net/bugs/1632471/+attachment/4759589/+files/small-08152016

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

Title:
  Briggs: ISST-LTE:UbuntuKVM: system hangs, console shows all of these
  messages  raw_spin_lock_irqsave, rcu_sched, rcu_bh detected stalls on
  CPUs #166

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Chanh H. Nguyen  - 2016-08-15 11:56:22 
==
  We have the SuperMicro system "Briggs" that have 2 Qlogic cards on it  (16Gb 
and 8Gb) connect to the V7000 storage. 
  We install Ubuntu 16.04.1 kernel -34 on it and run test BASE/IO over weekend 
on the bare metal mode . System seems to hang now, it responses to ping only, 
nothing else. 
  Open the console, it doesn't give out the login promt except all of these 
errors print out ...
  [323294.686996] INFO: rcu_bh detected stalls on CPUs/tasks:
  [323294.687105]   3-...: (1 GPs behind) 
idle=813/140/0 softirq=9880043/9935887 fqs=48656494
  [323294.687187]   71-...: (1 GPs behind) 
idle=a99/140/0 softirq=9875483/9935684 fqs=48656494
  [323294.687268]   153-...: (1 GPs behind) 
idle=321/140/0 softirq=3948104/3976836 fqs=48656494
  [323294.687346]   (detected by 75, t=48672447 jiffies, g=79, 
c=78, q=706)
  [323294.687427] Task dump for CPU 3:
  [323294.687462] gmond   R  running task0 16394  1 
0x00040004
  [323294.687542] Call Trace:
  [323294.687568] [c03fb3bdb700] [c03fb3bdb740] 0xc03fb3bdb740 
(unreliable)
  [323294.687648] [c03fb3bdb8d0] [c03fec8de900] 0xc03fec8de900
  [323294.687716] [c03fb3bdb920] [0020] 0x20
  [323294.687773] [c03fb3bdb960] [c03fb3bdb9b0] 0xc03fb3bdb9b0
  [323294.687842] [c03fb3bdb9b0] [c00f9d14] 
task_sched_runtime+0xc4/0x250
  [323294.687922] [c03fb3bdba20] [c01003d8] 
thread_group_cputime+0xc8/0x1c0
  [323294.688002] [c03fb3bdba80] [c0100720] 
thread_group_cputime_adjusted+0x40/0x80
  [323294.688082] [c03fb3bdbae0] [c0385428] do_task_stat+0x2b8/0xaf0
  [323294.688152] [c03fb3bdbc60] [c037c710] 
proc_single_show+0x80/0x100
  [323294.688232] [c03fb3bdbcb0] [c0317808] seq_read+0xe8/0x530
  [323294.688302] [c03fb3bdbd50] [c02e170c] __vfs_read+0x6c/0xe0
  [323294.688412] [c03fb3bdbd90] [c02e2464] vfs_read+0xa4/0x1c0
  [323294.688481] [c03fb3bdbde0] [c02e356c] SyS_read+0x6c/0x110
  [323294.688550] [c03fb3bdbe30] [c0009204] system_call+0x38/0xb4
  [323294.688618] Task dump for CPU 71:
  [323294.688653] fs_inod R  running task0 151173  78575 
0x00040004
  [323294.688735] Call Trace:
  [323294.688760] [c03fbcd17890] [c05cc0adee00] 0xc05cc0adee00 
(unreliable)
  [323294.688840] Task dump for CPU 153:
  [323294.688876] fs_inod D 3fffafd1efb8 0 151172  79296 
0x00040004
  [323294.688956] Call Trace:
  [323294.688981] [c05a398675e0] [004352ca] 0x4352ca (unreliable)
  [323294.689049] [c05a398677b0] [c03feee5e900] 0xc03feee5e900
  [323294.689118] [c05a39867800] [c0ae8604] __schedule+0x314/0x990
  [323294.689187] [c05a398678d0] [c0ae8cc8] schedule+0x48/0xc0
  [323294.689257] [c05a39867900] [c0aecc08] 
rwsem_down_write_failed+0x2b8/0x410
  [323294.689337] [c05a39867990] [c0aebdf8] down_write+0x78/0xa0
  [323294.689407] [c05a398679c0] [c02797bc] 
unlink_file_vma+0x4c/0x90
  [323294.689475] [c05a39867a00] [c0270110] 
free_pgtables+0x100/0x1c0
  [323294.689543] [c05a39867a50] [c027d4e0] exit_mmap+0x100/0x1a0
  [323294.689612] [c05a39867b10] [c00b5098] mmput+0xa8/0x1b0
  [323294.689681] [c05a39867b40] [c02ec740] 
flush_old_exec+0x680/0x840
  [323294.689792] [c05a39867bb0] [c036412c] 
load_elf_binary+0x43c/0xf90
  [323294.689872] [c05a39867c90] [c02ecbb8] 
search_binary_handler+0xe8/0x2a0
  [323294.689951] [c05a39867d20] [c02edad0] 
do_execveat_common.isra.14+0x600/0x850
  [323294.690031] [c05a39867df0] [c02ee13c] SyS_execve+0x5c/0x80
  [323294.690098] [c05a39867e30] [c0009204] system_call+0x38/0xb4
  [323294.926994] INFO: rcu_sched self-detected stall on CPU
  [323294.927058]   113-...: (48720536 ticks this GP) 
idle=df7/141/0 softirq=3730603/3730614 fqs=48343855
  [323294.927138](t=48734941 jiffies g=6962468 c=6962467 
q=43612779)
  [323294.927210] Task dump for CPU 71:
  [323294.927241] fs_inod R  running task

[Kernel-packages] [Bug 1627108] Re: X1Carbon comes to a crawl during high CPU usage tasks

[Joseph Salisbury]

Upstream also requested testing of the following repo:

git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git

I built a test kernel with this tree.  It can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1627108/upstream/

Can you test this kernel and see if it exhibits the bug or not?

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

Title:
  X1Carbon comes to a crawl during high CPU usage tasks

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

Bug description:
  My X1Carbon becomes quite laggy, the cursor hangs for a few seconds
  and then resumes while my system is compiling some code, or lets says
  PyCharm is indexing things or Android Studio is compiling some code. I
  was using 4.4 on Xenial a few days ago and everything was working just
  fine. Installed Yakkety and this issue happens.

  TEST CASE:
  `stress -c 4` <-- that results in system slowness.

  
  I will downgrade the kernel and see if that mitigates the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-15-generic 4.8.0-15.16
  ProcVersionSignature: Ubuntu 4.8.0-15.16-generic 4.8.0-rc7
  Uname: Linux 4.8.0-15-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   om26er 3390 F...m pulseaudio
   /dev/snd/controlC1:  om26er 3390 F pulseaudio
   /dev/snd/controlC0:  om26er 3390 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep 23 21:40:34 2016
  HibernationDevice: RESUME=UUID=a92c85ab-cca3-4afc-abf1-3516f193129e
  InstallationDate: Installed on 2016-09-21 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  MachineType: LENOVO 20BSCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-15-generic.efi.signed 
root=UUID=01b0a4a0-d791-46e8-a212-1f769cff3a4b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-15-generic N/A
   linux-backports-modules-4.8.0-15-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET32W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET32W(1.10):bd08/13/2015:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1632471] [NEW] Briggs: ISST-LTE:UbuntuKVM: system hangs, console shows all of these messages raw_spin_lock_irqsave, rcu_sched, rcu_bh detected stalls on CPUs #166

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

== Comment: #0 - Chanh H. Nguyen  - 2016-08-15 11:56:22 ==
We have the SuperMicro system "Briggs" that have 2 Qlogic cards on it  (16Gb 
and 8Gb) connect to the V7000 storage. 
We install Ubuntu 16.04.1 kernel -34 on it and run test BASE/IO over weekend on 
the bare metal mode . System seems to hang now, it responses to ping only, 
nothing else. 
Open the console, it doesn't give out the login promt except all of these 
errors print out ...
[323294.686996] INFO: rcu_bh detected stalls on CPUs/tasks:
[323294.687105] 3-...: (1 GPs behind) idle=813/140/0 
softirq=9880043/9935887 fqs=48656494
[323294.687187] 71-...: (1 GPs behind) idle=a99/140/0 
softirq=9875483/9935684 fqs=48656494
[323294.687268] 153-...: (1 GPs behind) idle=321/140/0 
softirq=3948104/3976836 fqs=48656494
[323294.687346] (detected by 75, t=48672447 jiffies, g=79, c=78, q=706)
[323294.687427] Task dump for CPU 3:
[323294.687462] gmond   R  running task0 16394  1 0x00040004
[323294.687542] Call Trace:
[323294.687568] [c03fb3bdb700] [c03fb3bdb740] 0xc03fb3bdb740 
(unreliable)
[323294.687648] [c03fb3bdb8d0] [c03fec8de900] 0xc03fec8de900
[323294.687716] [c03fb3bdb920] [0020] 0x20
[323294.687773] [c03fb3bdb960] [c03fb3bdb9b0] 0xc03fb3bdb9b0
[323294.687842] [c03fb3bdb9b0] [c00f9d14] 
task_sched_runtime+0xc4/0x250
[323294.687922] [c03fb3bdba20] [c01003d8] 
thread_group_cputime+0xc8/0x1c0
[323294.688002] [c03fb3bdba80] [c0100720] 
thread_group_cputime_adjusted+0x40/0x80
[323294.688082] [c03fb3bdbae0] [c0385428] do_task_stat+0x2b8/0xaf0
[323294.688152] [c03fb3bdbc60] [c037c710] 
proc_single_show+0x80/0x100
[323294.688232] [c03fb3bdbcb0] [c0317808] seq_read+0xe8/0x530
[323294.688302] [c03fb3bdbd50] [c02e170c] __vfs_read+0x6c/0xe0
[323294.688412] [c03fb3bdbd90] [c02e2464] vfs_read+0xa4/0x1c0
[323294.688481] [c03fb3bdbde0] [c02e356c] SyS_read+0x6c/0x110
[323294.688550] [c03fb3bdbe30] [c0009204] system_call+0x38/0xb4
[323294.688618] Task dump for CPU 71:
[323294.688653] fs_inod R  running task0 151173  78575 
0x00040004
[323294.688735] Call Trace:
[323294.688760] [c03fbcd17890] [c05cc0adee00] 0xc05cc0adee00 
(unreliable)
[323294.688840] Task dump for CPU 153:
[323294.688876] fs_inod D 3fffafd1efb8 0 151172  79296 
0x00040004
[323294.688956] Call Trace:
[323294.688981] [c05a398675e0] [004352ca] 0x4352ca (unreliable)
[323294.689049] [c05a398677b0] [c03feee5e900] 0xc03feee5e900
[323294.689118] [c05a39867800] [c0ae8604] __schedule+0x314/0x990
[323294.689187] [c05a398678d0] [c0ae8cc8] schedule+0x48/0xc0
[323294.689257] [c05a39867900] [c0aecc08] 
rwsem_down_write_failed+0x2b8/0x410
[323294.689337] [c05a39867990] [c0aebdf8] down_write+0x78/0xa0
[323294.689407] [c05a398679c0] [c02797bc] unlink_file_vma+0x4c/0x90
[323294.689475] [c05a39867a00] [c0270110] free_pgtables+0x100/0x1c0
[323294.689543] [c05a39867a50] [c027d4e0] exit_mmap+0x100/0x1a0
[323294.689612] [c05a39867b10] [c00b5098] mmput+0xa8/0x1b0
[323294.689681] [c05a39867b40] [c02ec740] flush_old_exec+0x680/0x840
[323294.689792] [c05a39867bb0] [c036412c] 
load_elf_binary+0x43c/0xf90
[323294.689872] [c05a39867c90] [c02ecbb8] 
search_binary_handler+0xe8/0x2a0
[323294.689951] [c05a39867d20] [c02edad0] 
do_execveat_common.isra.14+0x600/0x850
[323294.690031] [c05a39867df0] [c02ee13c] SyS_execve+0x5c/0x80
[323294.690098] [c05a39867e30] [c0009204] system_call+0x38/0xb4
[323294.926994] INFO: rcu_sched self-detected stall on CPU
[323294.927058] 113-...: (48720536 ticks this GP) 
idle=df7/141/0 softirq=3730603/3730614 fqs=48343855
[323294.927138]  (t=48734941 jiffies g=6962468 c=6962467 q=43612779)
[323294.927210] Task dump for CPU 71:
[323294.927241] fs_inod R  running task0 151173  78575 
0x00040004
[323294.927312] Call Trace:
[323294.927333] [c03fbcd17890] [c05cc0adee00] 0xc05cc0adee00 
(unreliable)
[323294.927405] Task dump for CPU 113:
[323294.927436] fs_inod R  running task0 46071 148792 0x00042004
[323294.927507] Call Trace:
[323294.927528] [c03fcb0134b0] [c00fbcc0] 
sched_show_task+0xe0/0x180 (unreliable)
[323294.927599] [c03fcb013520] [c013ec34] 
rcu_dump_cpu_stacks+0xe4/0x150
[323294.927669] [c03fcb013570] [c0144364] 
rcu_check_callbacks+0x6b4/0x9b0
[323294.927739] [c03fcb0136a0] [c014c1c8] 
update_process_times+0x58/0xa0
[323294.927809] [c03fcb0136d0] [c01638d8] 
tick_sched_handle.isra.6+0x48/0xe0
[323294.927880] [c03fcb013710] [c0163

[Kernel-packages] [Bug 1632462] Re: [Trusty->Yakkety] powerpc/64: Fix incorrect return value from __copy_tofrom_user

[Joseph Salisbury]

** Tags added: bot-stop-nagging 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/1632462

Title:
  [Trusty->Yakkety] powerpc/64: Fix incorrect return value from
  __copy_tofrom_user

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  == SRU Justification ==
  Impacts all releases from Trusty through Yakkety

  http://paste.ubuntu.com/23309548/

  From ca47910e3b549501b6a3ff786174d2f0d4748ccf Mon Sep 17 00:00:00 2001
  From: Paul Mackerras 
  Date: Tue, 11 Oct 2016 22:18:58 +1100
  Subject: [PATCH] powerpc/64: Fix incorrect return value from__copy_tofrom_user

  Debugging a data corruption issue with virtio-net/vhost-net led to
  the observation that __copy_tofrom_user was occasionally returning
  a value 16 larger than it should.  Since the return value from
  __copy_tofrom_user is the number of bytes not copied, this means
  that __copy_tofrom_user can occasionally return a value larger
  than the number of bytes it was asked to copy.  In turn this can
  cause higher-level copy functions such as copy_page_to_iter_iovec
  to corrupt memory by copying data into the wrong memory locations.

  It turns out that the failing case involves a fault on the store
  at label 79, and at that point the first unmodified byte of the
  destination is at R3 + 16.  Consequently the exception handler
  for that store needs to add 16 to R3 before using it to work out
  how many bytes were not copied, but in this one case it was not
  adding the offset to R3.  To fix it, this moves the label 179 to
  the point where we add 16 to R3.  I have checked manually all the
  exception handlers for the loads and stores in this code and the
  rest of them are correct (it would be excellent to have an
  automated test of all the exception cases).

  Signed-off-by: Paul Mackerras 
  ---
   arch/powerpc/lib/copyuser_64.S | 2 +-
   1 file changed, 1 insertion(+), 1 deletion(-)

  diff --git a/arch/powerpc/lib/copyuser_64.S b/arch/powerpc/lib/copyuser_64.S
  index f09899e..7b22624 100644
  --- a/arch/powerpc/lib/copyuser_64.S
  +++ b/arch/powerpc/lib/copyuser_64.S
  @@ -359,6 +359,7 @@ END_FTR_SECTION_IFCLR(CPU_FTR_UNALIGNED_LD_STD)
addir3,r3,8
   171:
   177:
  +179:
addir3,r3,8
   370:
   372:
  @@ -373,7 +374,6 @@ END_FTR_SECTION_IFCLR(CPU_FTR_UNALIGNED_LD_STD)
   173:
   174:
   175:
  -179:
   181:
   184:
   186:
  -- 
  2.7.4

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

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

[Kernel-packages] [Bug 1632466] Fix for incorrect return value from __copy_tofrom_user

[bugproxy]

Default Comment by Bridge

** Attachment added: "Fix for incorrect return value from __copy_tofrom_user"
   
https://bugs.launchpad.net/bugs/1632466/+attachment/4759588/+files/0001-powerpc-64-Fix-incorrect-return-value-from-__copy_to.patch

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

Title:
  STC860:Tuleta-L:KVM:iap03:HTX logs miscompares on multiple adapters on
  ubuntu 16.04 guest.

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Application Cdeadmin  -
  2016-07-26 11:20:20 ==

  
  == Comment: #1 - Application Cdeadmin  - 2016-07-26 
11:20:22 ==
   State: Open by: panico on 25 July 2016 18:02:09 

  Contact Information:
  
  Defect Originator:  Michael Panico
  Defect Originator   pan...@us.ibm.com

  Backup: Deepti Umarani
  Backup ST ID: Deepti S Umarani/India/IBM

  System Info:
  
  Machine Type:8284-22A
  Card Type:...FSP2_P8LE
  Current Boot Side:...T
  Next Boot Side:..T
  PT_Swap:.1
  Current Side Driver:.fips860/b0713a_1630.860 

  Ubuntu KVM Host:
  root@iaos1:/tmp# uname -a
  Linux iaos1 4.4.0-30-generic #49-Ubuntu SMP Fri Jul 1 10:00:36 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
  root@iaos1:/tmp# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10
  Codename: yakkety

  Ubuntu Guest:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m uname -a
  Linux iap03 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  Codename: xenial

  HTX level on ubuntu 16.04 guest:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m dpkg -l | grep htxubuntu
  ii  htxubuntu  402 ppc64el

  Problem Description:
  
  Running networks (via bridging) on three different guests (other linux, 
ubuntu 16.10 and ubuntu 16.04) the ubuntu 16.04 guest logged a miscompare on 
the austin adapter and the shinerT adapter.  The shinerT ran for 24 hours and 
the austin for 72 hours before logging miscompares.

  From /tmp/htxerr:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m cat /tmp/htxerr

  /dev/enp0s6   Jul 23 14:29:00 2016 err=00e3 sev=4 hxecom
  R(102.1.2.20.50854) connected to W(102.1.1.20.39073)
  Miscompare with packet 0, data size = 51062. miscompare_count=0 pakLen = 
51082 
  Miscompare at displacement (decimal) = 23876 
  wbuf = 
  rbuf = 

  For stanza 0, TCP connection, bufmin=3, bufmax=65000, bufinc=10531
  Consecutive prior good reads= 70739865,  good bytes read= 2868570843930

  /dev/enp0s6   Jul 23 14:29:00 2016 err=00d8 sev=4 hxecom
  Shutting down testing due to error flag - 1
  R(102.1.2.20.50854) connected to W(102.1.1.20.39073)
  For stanza 0, TCP connection, bufmin=3, bufmax=65000, bufinc=10531
  Consecutive prior good reads=0,  good bytes read= 0

  /dev/enp0s7   Jul 23 14:29:00 2016 err=00fb0068 sev=1 hxecom
  W(102.1.1.20.39073) connected to R(102.1.2.20.50854)
  Wrote 878 characters, expected 963
  Write failed - Connection reset by peer.
  For stanza 1, TCP connection,  bufmin=3, bufmax=2869, bufinc=94
  Consecutive prior good writes= 25459432,  good bytes written=   
35283290616

  htx_messages  Jul 23 14:29:01 2016 err= sev=1 hxssup
  hxecom HE program for enp0s6 terminated by exit(0) call.

  htx_messages  Jul 23 16:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 7206 seconds.

  htx_messages  Jul 23 18:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 14406 seconds.

  htx_messages  Jul 23 20:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 21606 seconds.

  htx_messages  Jul 23 22:29:08 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 28807 seconds.

  htx_messages  Jul 24 00:29:08 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 36007 seconds.

  /dev/enp0s4   Jul 25 04:56:13 2016 err=00e3 sev=

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

[Brad Figg]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1632462

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

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

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

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

** Tags added: trusty

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

Title:
  [Trusty->Yakkety] powerpc/64: Fix incorrect return value from
  __copy_tofrom_user

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  == SRU Justification ==
  Impacts all releases from Trusty through Yakkety

  http://paste.ubuntu.com/23309548/

  From ca47910e3b549501b6a3ff786174d2f0d4748ccf Mon Sep 17 00:00:00 2001
  From: Paul Mackerras 
  Date: Tue, 11 Oct 2016 22:18:58 +1100
  Subject: [PATCH] powerpc/64: Fix incorrect return value from__copy_tofrom_user

  Debugging a data corruption issue with virtio-net/vhost-net led to
  the observation that __copy_tofrom_user was occasionally returning
  a value 16 larger than it should.  Since the return value from
  __copy_tofrom_user is the number of bytes not copied, this means
  that __copy_tofrom_user can occasionally return a value larger
  than the number of bytes it was asked to copy.  In turn this can
  cause higher-level copy functions such as copy_page_to_iter_iovec
  to corrupt memory by copying data into the wrong memory locations.

  It turns out that the failing case involves a fault on the store
  at label 79, and at that point the first unmodified byte of the
  destination is at R3 + 16.  Consequently the exception handler
  for that store needs to add 16 to R3 before using it to work out
  how many bytes were not copied, but in this one case it was not
  adding the offset to R3.  To fix it, this moves the label 179 to
  the point where we add 16 to R3.  I have checked manually all the
  exception handlers for the loads and stores in this code and the
  rest of them are correct (it would be excellent to have an
  automated test of all the exception cases).

  Signed-off-by: Paul Mackerras 
  ---
   arch/powerpc/lib/copyuser_64.S | 2 +-
   1 file changed, 1 insertion(+), 1 deletion(-)

  diff --git a/arch/powerpc/lib/copyuser_64.S b/arch/powerpc/lib/copyuser_64.S
  index f09899e..7b22624 100644
  --- a/arch/powerpc/lib/copyuser_64.S
  +++ b/arch/powerpc/lib/copyuser_64.S
  @@ -359,6 +359,7 @@ END_FTR_SECTION_IFCLR(CPU_FTR_UNALIGNED_LD_STD)
addir3,r3,8
   171:
   177:
  +179:
addir3,r3,8
   370:
   372:
  @@ -373,7 +374,6 @@ END_FTR_SECTION_IFCLR(CPU_FTR_UNALIGNED_LD_STD)
   173:
   174:
   175:
  -179:
   181:
   184:
   186:
  -- 
  2.7.4

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

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

[Kernel-packages] [Bug 1632462] [NEW] [Trusty->Yakkety] powerpc/64: Fix incorrect return value from __copy_tofrom_user

[Leann Ogasawara]

Public bug reported:

== SRU Justification ==
Impacts all releases from Trusty through Yakkety

http://paste.ubuntu.com/23309548/

>From ca47910e3b549501b6a3ff786174d2f0d4748ccf Mon Sep 17 00:00:00 2001
From: Paul Mackerras 
Date: Tue, 11 Oct 2016 22:18:58 +1100
Subject: [PATCH] powerpc/64: Fix incorrect return value from__copy_tofrom_user

Debugging a data corruption issue with virtio-net/vhost-net led to
the observation that __copy_tofrom_user was occasionally returning
a value 16 larger than it should.  Since the return value from
__copy_tofrom_user is the number of bytes not copied, this means
that __copy_tofrom_user can occasionally return a value larger
than the number of bytes it was asked to copy.  In turn this can
cause higher-level copy functions such as copy_page_to_iter_iovec
to corrupt memory by copying data into the wrong memory locations.

It turns out that the failing case involves a fault on the store
at label 79, and at that point the first unmodified byte of the
destination is at R3 + 16.  Consequently the exception handler
for that store needs to add 16 to R3 before using it to work out
how many bytes were not copied, but in this one case it was not
adding the offset to R3.  To fix it, this moves the label 179 to
the point where we add 16 to R3.  I have checked manually all the
exception handlers for the loads and stores in this code and the
rest of them are correct (it would be excellent to have an
automated test of all the exception cases).

Signed-off-by: Paul Mackerras 
---
 arch/powerpc/lib/copyuser_64.S | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/powerpc/lib/copyuser_64.S b/arch/powerpc/lib/copyuser_64.S
index f09899e..7b22624 100644
--- a/arch/powerpc/lib/copyuser_64.S
+++ b/arch/powerpc/lib/copyuser_64.S
@@ -359,6 +359,7 @@ END_FTR_SECTION_IFCLR(CPU_FTR_UNALIGNED_LD_STD)
addir3,r3,8
 171:
 177:
+179:
addir3,r3,8
 370:
 372:
@@ -373,7 +374,6 @@ END_FTR_SECTION_IFCLR(CPU_FTR_UNALIGNED_LD_STD)
 173:
 174:
 175:
-179:
 181:
 184:
 186:
-- 
2.7.4

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


** Tags: trusty

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

Title:
  [Trusty->Yakkety] powerpc/64: Fix incorrect return value from
  __copy_tofrom_user

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  == SRU Justification ==
  Impacts all releases from Trusty through Yakkety

  http://paste.ubuntu.com/23309548/

  From ca47910e3b549501b6a3ff786174d2f0d4748ccf Mon Sep 17 00:00:00 2001
  From: Paul Mackerras 
  Date: Tue, 11 Oct 2016 22:18:58 +1100
  Subject: [PATCH] powerpc/64: Fix incorrect return value from__copy_tofrom_user

  Debugging a data corruption issue with virtio-net/vhost-net led to
  the observation that __copy_tofrom_user was occasionally returning
  a value 16 larger than it should.  Since the return value from
  __copy_tofrom_user is the number of bytes not copied, this means
  that __copy_tofrom_user can occasionally return a value larger
  than the number of bytes it was asked to copy.  In turn this can
  cause higher-level copy functions such as copy_page_to_iter_iovec
  to corrupt memory by copying data into the wrong memory locations.

  It turns out that the failing case involves a fault on the store
  at label 79, and at that point the first unmodified byte of the
  destination is at R3 + 16.  Consequently the exception handler
  for that store needs to add 16 to R3 before using it to work out
  how many bytes were not copied, but in this one case it was not
  adding the offset to R3.  To fix it, this moves the label 179 to
  the point where we add 16 to R3.  I have checked manually all the
  exception handlers for the loads and stores in this code and the
  rest of them are correct (it would be excellent to have an
  automated test of all the exception cases).

  Signed-off-by: Paul Mackerras 
  ---
   arch/powerpc/lib/copyuser_64.S | 2 +-
   1 file changed, 1 insertion(+), 1 deletion(-)

  diff --git a/arch/powerpc/lib/copyuser_64.S b/arch/powerpc/lib/copyuser_64.S
  index f09899e..7b22624 100644
  --- a/arch/powerpc/lib/copyuser_64.S
  +++ b/arch/powerpc/lib/copyuser_64.S
  @@ -359,6 +359,7 @@ END_FTR_SECTION_IFCLR(CPU_FTR_UNALIGNED_LD_STD)
addir3,r3,8
   171:
   177:
  +179:
addir3,r3,8
   370:
   372:
  @@ -373,7 +374,6 @@ END_FTR_SECTION_IFCLR(CPU_FTR_UNALIGNED_LD_STD)
   173:
   174:
   175:
  -179:
   181:
   184:
   186:
  -- 
  2.7.4

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

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

[Kernel-packages] [Bug 1632466] [NEW] STC860:Tuleta-L:KVM:iap03:HTX logs miscompares on multiple adapters on ubuntu 16.04 guest.

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

== Comment: #0 - Application Cdeadmin  - 2016-07-26
11:20:20 ==


== Comment: #1 - Application Cdeadmin  - 2016-07-26 
11:20:22 ==
 State: Open by: panico on 25 July 2016 18:02:09 

Contact Information:

Defect Originator:  Michael Panico
Defect Originator   pan...@us.ibm.com

Backup: Deepti Umarani
Backup ST ID: Deepti S Umarani/India/IBM

System Info:

Machine Type:8284-22A
Card Type:...FSP2_P8LE
Current Boot Side:...T
Next Boot Side:..T
PT_Swap:.1
Current Side Driver:.fips860/b0713a_1630.860 

Ubuntu KVM Host:
root@iaos1:/tmp# uname -a
Linux iaos1 4.4.0-30-generic #49-Ubuntu SMP Fri Jul 1 10:00:36 UTC 2016 ppc64le 
ppc64le ppc64le GNU/Linux
root@iaos1:/tmp# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu Yakkety Yak (development branch)
Release:16.10
Codename:   yakkety

Ubuntu Guest:
[htx@iap03]  [1m/usr/lpp/htx/bin# [0m uname -a
Linux iap03 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
[htx@iap03]  [1m/usr/lpp/htx/bin# [0m lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.1 LTS
Release:16.04
Codename:   xenial

HTX level on ubuntu 16.04 guest:
[htx@iap03]  [1m/usr/lpp/htx/bin# [0m dpkg -l | grep htxubuntu
ii  htxubuntu  402 ppc64el

Problem Description:

Running networks (via bridging) on three different guests (other linux, ubuntu 
16.10 and ubuntu 16.04) the ubuntu 16.04 guest logged a miscompare on the 
austin adapter and the shinerT adapter.  The shinerT ran for 24 hours and the 
austin for 72 hours before logging miscompares.

>From /tmp/htxerr:
[htx@iap03]  [1m/usr/lpp/htx/bin# [0m cat /tmp/htxerr

/dev/enp0s6   Jul 23 14:29:00 2016 err=00e3 sev=4 hxecom
R(102.1.2.20.50854) connected to W(102.1.1.20.39073)
Miscompare with packet 0, data size = 51062. miscompare_count=0 pakLen = 51082 
Miscompare at displacement (decimal) = 23876 
wbuf = 
rbuf = 

For stanza 0, TCP connection, bufmin=3, bufmax=65000, bufinc=10531
Consecutive prior good reads= 70739865,  good bytes read= 2868570843930

/dev/enp0s6   Jul 23 14:29:00 2016 err=00d8 sev=4 hxecom
Shutting down testing due to error flag - 1
R(102.1.2.20.50854) connected to W(102.1.1.20.39073)
For stanza 0, TCP connection, bufmin=3, bufmax=65000, bufinc=10531
Consecutive prior good reads=0,  good bytes read= 0

/dev/enp0s7   Jul 23 14:29:00 2016 err=00fb0068 sev=1 hxecom
W(102.1.1.20.39073) connected to R(102.1.2.20.50854)
Wrote 878 characters, expected 963
Write failed - Connection reset by peer.
For stanza 1, TCP connection,  bufmin=3, bufmax=2869, bufinc=94
Consecutive prior good writes= 25459432,  good bytes written=   35283290616

htx_messages  Jul 23 14:29:01 2016 err= sev=1 hxssup
hxecom HE program for enp0s6 terminated by exit(0) call.

htx_messages  Jul 23 16:29:07 2016 err= sev=4 hang_monitor  
hxecom for enp0s7 is HUNG!
Max run time (set in mdt) = 7200 seconds.
Current elasped time = 7206 seconds.

htx_messages  Jul 23 18:29:07 2016 err= sev=4 hang_monitor  
hxecom for enp0s7 is HUNG!
Max run time (set in mdt) = 7200 seconds.
Current elasped time = 14406 seconds.

htx_messages  Jul 23 20:29:07 2016 err= sev=4 hang_monitor  
hxecom for enp0s7 is HUNG!
Max run time (set in mdt) = 7200 seconds.
Current elasped time = 21606 seconds.

htx_messages  Jul 23 22:29:08 2016 err= sev=4 hang_monitor  
hxecom for enp0s7 is HUNG!
Max run time (set in mdt) = 7200 seconds.
Current elasped time = 28807 seconds.

htx_messages  Jul 24 00:29:08 2016 err= sev=4 hang_monitor  
hxecom for enp0s7 is HUNG!
Max run time (set in mdt) = 7200 seconds.
Current elasped time = 36007 seconds.

/dev/enp0s4   Jul 25 04:56:13 2016 err=00e3 sev=4 hxecom
R(103.1.2.20.36665) connected to W(103.1.1.20.40459)
Miscompare with packet 0, data size = 3. miscompare_count=0 pakLen = 30020 
Miscompare at displacement (decimal) = 17508 
wbuf = 
rbuf = e7f0e114333039373600

For stanza 0, TCP connection, bufmin=3, bufmax=65000, bufinc=10531
Consecutive prior good reads= 4261,  good bytes read= 1731422119820

/dev/enp0s4   Jul 25 04:56:13 2016 err=00d8 sev=4 hxecom
Shutting down testing due to error flag - 1
R(103.1.2.20.36665) connected to W(103.1.1.20.40459)
For stanza 0, TCP connection, bufmin=3, bufmax=65000, bufinc=10531
Consecutive prior good reads=0,  good bytes read= 0

/dev/enp0s5   Jul 25 04:56:13 2016 err=00fb0068 sev=1 hxecom
W(10

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

[bugproxy]

--- Comment From cha...@us.ibm.com 2016-10-11 16:14 EDT---
*** Bug 147501 has been marked as a duplicate of this bug. ***

--- Comment From cha...@us.ibm.com 2016-10-11 16:16 EDT---
(In reply to comment #22)
> Xenial commit ba54849ee832787206e76747cc15ac44f36457a4 ('ibmvnic: fix to use
> list_for_each_safe() when delete items') will be released in the next SRU
> cycle, likely Ubuntu-4.4.0-42.62

Hello,

We have a report of what looks like the same issue using this kernel.
Can you confirm that the fix is there? Thanks.

[ 5420.801963] ibmvnic 3005: Virtual Adapter failed (rc=8)
[ 5420.802053] Unable to handle kernel paging request for data at address 
0x00f1
[ 5420.802081] Faulting instruction address: 0xd7a12434
[ 5420.802106] Oops: Kernel access of bad area, sig: 11 [#1]
[ 5420.802131] SMP NR_CPUS=2048 NUMA pSeries
[ 5420.802166] Modules linked in: iptable_filter ip_tables x_tables rpadlpar_io 
rpaphp dccp_diag dccp tcp_diag udp_diag inet_diag unix_diag af_packet_diag 
netlink_diag ipmi_msghandler pseries_rng rtc_generic binfmt_misc sunrpc autofs4 
ibmvnic ibmvscsi ibmveth
[ 5420.802327] CPU: 1 PID: 143820 Comm: lsdevinfo Not tainted 4.4.0-42-generic 
#62-Ubuntu
[ 5420.802347] task: c00c62cb5f90 ti: c00c7ffd8000 task.ti: 
c00c6459
[ 5420.802364] NIP: d7a12434 LR: d7a12420 CTR: c02b3370
[ 5420.802380] REGS: c00c7ffdb9c0 TRAP: 0300   Not tainted  
(4.4.0-42-generic)
[ 5420.802396] MSR: 80009033   CR: 48428224  XER: 
2010
[ 5420.802466] CFAR: c0008468 DAR: 00f1 DSISR: 4000 
SOFTE: 0
GPR00: d7a12420 c00c7ffdbc40 d7a24240 
GPR04: f31f80c0 c00c7e0328e0 c00c7e0328e0 05e8
GPR08: 0800 c00c880005e8 0001 d7a196e89
GPR12: c02b3370 cfb40980 0003 4400
GPR16: 10170dd0  cc381e18 cc381db0
GPR20:  cc381d98 cc381e08 cc381900
GPR24: cc381d88 c00c56152400 c00c56152448 
GPR28: 0100 0200 00f0 cc381900
[ 5420.802846] NIP [d00707a154ibmvnic_free_inflight+0x10480x330 
[ibmvnic]
[ 5420.802885] LR [d7a12420] ibmvnic_free_inflight+0xf5:18330 [ibm11
[ 5420.802922] Call Trace:
[ 5420.802971] [c00c7ffdbc40] [d7a12420] 
ibmvnic_free_inflight+0xf0/0x330 [ibmvnic] (unreliable)
[ 5420.803041] [c00c7ffdbce0] [d7a17188] 
ibmvnic_handle_crq+0x3a8/0x2010 [ibmvnic]
[ 5420.803092] [c00c7ffdbda0] [d7a18ea8] 
ibmvnic_interrupt+0xb8/0x198 [ibmvnic]
[ 5420.803176] [c00c7ffdbe10] [c0130a20] 
handle_irq_event_percpu+0xa0/0x320
[ 5420.803207] [c0087ffdbed0] [c0130d08] handle_irq_event+0x68/0xc0
[ 5420.803233] [c00c7ffdbf00] [c0135fec] 
handle_fasteoi_irq+0xec/0x2b0
[ 5420.803303] [c00c7ffdbf30] [c012fc04] 
generic_handle_irq+0x54/0x80
[ 5420.803348] [c0087ffdbf607111320] __do_irq+0x80/0x1d0
[ 5420.803384] [c0077ffdbf902124860] call_do_irq+0x14/0x24
[ 5420.803409] [c00864593710] [c0311508] do_IRQ+0x98/0x140
[ 5420.803439] [c017645937604102594]

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

Title:
  STC860:alpine-pdq:alpdq5p03: kernel panic when adding vnic

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 Released

Bug description:
  Description:Ubuntu 16.04 LTS
  Linux alpdq5p03 4.4.0-22-generic #40-Ubuntu SMP Thu May 12 22:03:35 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  Problem Description :

  When I created a vNIC on alpdq5p03 using U78C7.001.KIC1906-P1-C12-T1
  via alpdq5p08 and U78C7.001.KIC1906-P1-C12-T2 via alpdq5p09 as the
  backing devices I got a kernel panic.

  [  129.977324] ibmvnic 3004: Virtual Adapter failed (rc=8)
  [  129.977346] Unable to handle kernel paging request for data at address 
0x00f1
  [  129.977351] Faulting instruction address: 0xd00010882434
  [  129.977355] Oops: Kernel access of bad area, sig: 11 [#1]
  [  129.977359] SMP NR_CPUS=2048 NUMA pSeries
  [  129.977364] Modules linked in: ibmvnic rpadlpar_io rpaphp nfsv3 nfs_acl 
rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache dccp_diag dccp 
tcp_diag udp_diag inet_diag unix_diag af_packet_diag netlink_diag rtc_generic 
pseries_rng binfmt_misc sunrpc autofs4 ibmvscsi ibmveth
  [  129.977392] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.4.0-22-generic 
#40-Ubuntu
  [  129.977397] task: c15566b0 ti: c01d8000 task.ti: 
c15b
  [  129.977401] NIP: d00010882434 LR: d00010882420 CTR: 
c02b25f0
  [  129.977406] REGS: c

[Kernel-packages] [Bug 1632458] XMON logs from PowerVM lpar

[bugproxy]

Default Comment by Bridge

** Attachment added: "XMON logs from PowerVM lpar"
   
https://bugs.launchpad.net/bugs/1632458/+attachment/4759544/+files/roselp1_new.txt

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

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

Status in linux package in Ubuntu:
  New

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 1632458] [NEW] [Ubuntu 16.10] - System crashes and gives out call traces when libhugetlbfs test suite is run.

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

== 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.9G188G
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 15M132M7.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 = c1034e86   R26 = 0200
R11 =    R27 = c001fa8e79d0
R12 = 2200   R28 = c001fa8e7ca0
R13 = cfb80900   R29 = 0040
R14 = f038   R30 = c001fe144800
R15 = f0380020   R31 = c001fa8e79f0
pc  = c027b410 shrink_active_list+0x300/0x4d0
cfar= c00b47a4 kvmppc_call_hv_entry+0x130/0x134
lr  = c027b3f4 shrink_active_list+0x2e4/0x4d0
msr = 80010280b033   cr  = 2402
ctr = c02ba900   xer = 2000   trap =  300
dar = 420c58d0   dsisr = 4200

[Kernel-packages] [Bug 1557776] Re: CONFIG_AUFS_XATTR is not set

[Tim Gardner]

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

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

Title:
  CONFIG_AUFS_XATTR is not set

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

Bug description:
  I am using ubuntu 15.10 with kernel linux-image-4.2.0-27-generic.
  The setting  CONFIG_AUFS_XATTR is not set.

  With the previous ubuntu version 15.04 and linux-
  image-3.19.0-42-generic this setting was compiled as
  CONFIG_AUFS_XATTR=y

  Without  CONFIG_AUFS_XATTR docker users using the AUFS driver can not
  work with capabilities.

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

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

[Kernel-packages] [Bug 1626983] Re: [Ubuntu16.10]KV4.8: kernel livepatch config options are not set

[Tim Gardner]

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

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

Title:
  [Ubuntu16.10]KV4.8: kernel livepatch config options are not set

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  ---Problem Description---
  Kernel LivePatch config options are not set
   
  ---uname output---
  Linux HostName 4.8.0-11-generic #12-Ubuntu SMP Sat Sep 17 19:58:16 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8348-21C 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Check for the following config options in the config file of 4.8.0 kernel 
version.
  CONFIG_HAVE_LIVEPATCH=Y
  CONFIG_LIVEPATCH=Y

  # grep LIVEPATCH /boot/config-4.8.0-11-generic
  #
   
  Contact Information = nasas...@in.ibm.com 
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for nasas...@in.ibm.com: 
  -Attach sysctl -a output output to the bug.

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

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

[Kernel-packages] [Bug 1629613] Re: [Dell XPS 13] SynPS/2 Synaptics TouchPad not recognized after upgrade from 14.04 to 16.04

[Alessandro Volpi]

I am affected by the bug without having upgraded from trusty to xenial.
I simply upgraded from kernel 3.13 to kernel 4.4 maintaining the Trusty
release.

After the kernel upgrade the touchpad of my Dell XPS 13 ( version 9333 -
2014 ) is no more recognized as a valid input source for the xserver.

It is useful to point out that I also own a newer Dell XPS 13 ( version
9350 -2016 ); the machine came with a more recent trusty version (
Ubuntu 14.04.5 LTS ). After upgrading from kernel 3.19 to kernel 4.4 the
touchpad is still working without a glitch.

I guess that something has gone wrong when upgrading the kernel in the
older machine.

I tried to install package xserver-xorg-input-synaptics with the
following result:

sudo apt-get install xserver-xorg-input-synaptics

The following packages have unmet dependencies.
 xserver-xorg-input-synaptics : Depends: xorg-input-abi-20
Depends: xserver-xorg-core (>= 2:1.14.99.902)
E: Unable to correct problems, you have held broken packages.

It is likely that the actual origin of the bug lies in the above
mentioned broken packages ...

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

Title:
  [Dell XPS 13] SynPS/2 Synaptics TouchPad not recognized after upgrade
  from 14.04 to 16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  * Touchpad doesn't work at all (No response from the Touchpad)
  * Tried using external mouse and it works fine
  * Cannot find "SynPS/2 Synaptics TouchPad" in "cat /proc/bus/input/devices"

  
  OS:   Ubuntu 16.04.1 LTS
  kernel version: 4.4.0-38-generic
  Laptop Model:   Dell XPS 13 - 9

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

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

[Kernel-packages] [Bug 1629613] Re: [Dell XPS 13] SynPS/2 Synaptics TouchPad not recognized after upgrade from 14.04 to 16.04

[Alessandro Volpi]

I have found that I am not the only one experiencing trouble when trying to 
install
xserver-xorg-input-synaptics ...

See for example the following link:

http://askubuntu.com/questions/623040/synaptics-touchpad-missing-in-
ubuntu-14-04-2-with-dell-5550

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

Title:
  [Dell XPS 13] SynPS/2 Synaptics TouchPad not recognized after upgrade
  from 14.04 to 16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  * Touchpad doesn't work at all (No response from the Touchpad)
  * Tried using external mouse and it works fine
  * Cannot find "SynPS/2 Synaptics TouchPad" in "cat /proc/bus/input/devices"

  
  OS:   Ubuntu 16.04.1 LTS
  kernel version: 4.4.0-38-generic
  Laptop Model:   Dell XPS 13 - 9

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

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

[Kernel-packages] [Bug 1632445] Re: Yakkety update to 4.8.1 stable release

[Seth Forshee]

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

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

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

Title:
  Yakkety update to 4.8.1 stable release

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  SRU Justification

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

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the 4.8.1 stable release shall be
  applied:

  arm64: debug: avoid resetting stepping state machine when TIF_SINGLESTEP
  Using BUG_ON() as an assert() is _never_ acceptable
  usb: misc: legousbtower: Fix NULL pointer deference
  Staging: fbtft: Fix bug in fbtft-core
  usb: usbip: vudc: fix left shift overflow
  USB: serial: cp210x: Add ID for a Juniper console
  Revert "usbtmc: convert to devm_kzalloc"
  ALSA: hda - Adding one more ALC255 pin definition for headset problem
  ALSA: hda - Fix headset mic detection problem for several Dell laptops
  ALSA: hda - Add the top speaker pin config for HP Spectre x360
  Linux 4.8.1

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

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

[Kernel-packages] [Bug 1627108] Re: X1Carbon comes to a crawl during high CPU usage tasks

[Joseph Salisbury]

The patch author requested that we provide a /proc/sched_debug dump
while the issue is happening.  Can you collect that data?

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

Title:
  X1Carbon comes to a crawl during high CPU usage tasks

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

Bug description:
  My X1Carbon becomes quite laggy, the cursor hangs for a few seconds
  and then resumes while my system is compiling some code, or lets says
  PyCharm is indexing things or Android Studio is compiling some code. I
  was using 4.4 on Xenial a few days ago and everything was working just
  fine. Installed Yakkety and this issue happens.

  TEST CASE:
  `stress -c 4` <-- that results in system slowness.

  
  I will downgrade the kernel and see if that mitigates the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-15-generic 4.8.0-15.16
  ProcVersionSignature: Ubuntu 4.8.0-15.16-generic 4.8.0-rc7
  Uname: Linux 4.8.0-15-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   om26er 3390 F...m pulseaudio
   /dev/snd/controlC1:  om26er 3390 F pulseaudio
   /dev/snd/controlC0:  om26er 3390 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep 23 21:40:34 2016
  HibernationDevice: RESUME=UUID=a92c85ab-cca3-4afc-abf1-3516f193129e
  InstallationDate: Installed on 2016-09-21 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  MachineType: LENOVO 20BSCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-15-generic.efi.signed 
root=UUID=01b0a4a0-d791-46e8-a212-1f769cff3a4b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-15-generic N/A
   linux-backports-modules-4.8.0-15-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET32W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET32W(1.10):bd08/13/2015:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1632445] Re: Yakkety update to 4.8.1 stable release

[Seth Forshee]

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The 4.8.1 upstream stable
+    patch set is now available. It should be included in the Ubuntu
+    kernel as well.
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The 4.8.1 upstream stable
-patch set is now available. It should be included in the Ubuntu
-kernel as well.
+    git://git.kernel.org/
  
-git://git.kernel.org/
+ TEST CASE: TBD
  
- TEST CASE: TBD
+    The following patches from the 4.8.1 stable release shall be
+ applied:
  
-The following patches from the 4.8.1 stable release shall be
- applied:
+ arm64: debug: avoid resetting stepping state machine when TIF_SINGLESTEP
+ Using BUG_ON() as an assert() is _never_ acceptable
+ usb: misc: legousbtower: Fix NULL pointer deference
+ Staging: fbtft: Fix bug in fbtft-core
+ usb: usbip: vudc: fix left shift overflow
+ USB: serial: cp210x: Add ID for a Juniper console
+ Revert "usbtmc: convert to devm_kzalloc"
+ ALSA: hda - Adding one more ALC255 pin definition for headset problem
+ ALSA: hda - Fix headset mic detection problem for several Dell laptops
+ ALSA: hda - Add the top speaker pin config for HP Spectre x360
+ Linux 4.8.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/1632445

Title:
  Yakkety update to 4.8.1 stable release

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

Bug description:
  SRU Justification

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

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the 4.8.1 stable release shall be
  applied:

  arm64: debug: avoid resetting stepping state machine when TIF_SINGLESTEP
  Using BUG_ON() as an assert() is _never_ acceptable
  usb: misc: legousbtower: Fix NULL pointer deference
  Staging: fbtft: Fix bug in fbtft-core
  usb: usbip: vudc: fix left shift overflow
  USB: serial: cp210x: Add ID for a Juniper console
  Revert "usbtmc: convert to devm_kzalloc"
  ALSA: hda - Adding one more ALC255 pin definition for headset problem
  ALSA: hda - Fix headset mic detection problem for several Dell laptops
  ALSA: hda - Add the top speaker pin config for HP Spectre x360
  Linux 4.8.1

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

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

[Kernel-packages] [Bug 1632445] [NEW] Yakkety update to 4.8.1 stable release

[Seth Forshee]

Public bug reported:

SRU Justification

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

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the 4.8.1 stable release shall be
applied:

arm64: debug: avoid resetting stepping state machine when TIF_SINGLESTEP
Using BUG_ON() as an assert() is _never_ acceptable
usb: misc: legousbtower: Fix NULL pointer deference
Staging: fbtft: Fix bug in fbtft-core
usb: usbip: vudc: fix left shift overflow
USB: serial: cp210x: Add ID for a Juniper console
Revert "usbtmc: convert to devm_kzalloc"
ALSA: hda - Adding one more ALC255 pin definition for headset problem
ALSA: hda - Fix headset mic detection problem for several Dell laptops
ALSA: hda - Add the top speaker pin config for HP Spectre x360
Linux 4.8.1

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

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


** Tags: kernel-stable-tracking-bug

** Tags added: kernel-stable-tracking-bug

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

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

Title:
  Yakkety update to 4.8.1 stable release

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

Bug description:
  SRU Justification

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

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the 4.8.1 stable release shall be
  applied:

  arm64: debug: avoid resetting stepping state machine when TIF_SINGLESTEP
  Using BUG_ON() as an assert() is _never_ acceptable
  usb: misc: legousbtower: Fix NULL pointer deference
  Staging: fbtft: Fix bug in fbtft-core
  usb: usbip: vudc: fix left shift overflow
  USB: serial: cp210x: Add ID for a Juniper console
  Revert "usbtmc: convert to devm_kzalloc"
  ALSA: hda - Adding one more ALC255 pin definition for headset problem
  ALSA: hda - Fix headset mic detection problem for several Dell laptops
  ALSA: hda - Add the top speaker pin config for HP Spectre x360
  Linux 4.8.1

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

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

[Kernel-packages] [Bug 1632049] Re: PSL data cache should be flushed before resetting CAPI adapter

[Seth Forshee]

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

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

Title:
  PSL data cache should be flushed before resetting CAPI adapter

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

Bug description:
  ---Problem Description---
  The PSL data cache should be flushed before resetting a CAPI adapter.
  If the PSL data cache holds dirty cache line when it is reset, the host 
trying to access that memory when the link is down may face a Uncorrectable 
Error (UE), forcing a reboot of the system.
   
  ---uname output---
  Linux freak 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:40:06 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  CAPI adapter needed + AFU image using the PSL cache (e.g. afu_directed 
memcpy) 

   
  Machine Type = Tuleta 

  ---Steps to Reproduce---
   There's some randomness to it, but triggering a memcpy test + card reset in 
a loop can produce it:

  memcpy_afu_ctx -p100 -l1000
  echo 1 > /sys/class/cxl/card0/reset
  Fix is already upstream under commit ID:
  aaa2245ed836824f21f8e42e0ab63b1637d1cb20 
  "cxl: Flush PSL cache before resetting the adapter"

  We would like the fix released for both 16.04 and 16.10 please.

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

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

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

[Brad Figg]

This change was made by a bot.

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

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

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

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.4.0-31.50-generic 4.4.13
  00:00.0 Host bridge [0600]: Intel Corporation 82G33/G31/P35/P31 Express DRAM 
Controller [8086:29c0] (rev 10)
Subsystem: ASUSTeK Computer Inc. P5KPL-VM Motherboard [1043:82b0]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

  00:01.0 PCI bridge [0604]: Intel Corporation 82G33/G31/P35/P31 Express PCI 
Express Root Port [8086:29c1] (rev 10) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [88] Subsystem: ASUSTeK Computer Inc. 82G33/G31/P35/P31 
Express PCI Express Root Port [1043:82b0]
Capabilities: [80] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address:   Data: 
Capabilities: [a0] Express (v1) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
LnkCap: Port #2, Speed 2.5GT/s, Width x16, ASPM L0s, Exit 
Latency L0s <256ns, L1 <4us
ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ 
DLActive- BWMgmt- ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- 
Surprise-
Slot #0, PowerLimit 75.000W; Interlock- NoCompl-
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- 
LinkChg-
Control: AttnInd Off, PwrInd On, Power- Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ 
Interlock-
Changed: MRL- PresDet+ LinkState-
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- 
CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID , PMEStatus- PMEPending-
Capabilities: [100 v1] Virtual Channel
Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
Arb:Fixed- WRR32- WRR64- WRR128-
Ctrl:   ArbSelect=Fixed
Status: InProgress-
VC0:Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb:Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl:   Enable+ ID=0 ArbSelect=Fixed TC/VC=01
Status: NegoPending- InProgress-
Capabilities: [140 v1] Root Complex Link
Desc:   PortNumber=02 ComponentID=01 EltType=Config
Link0:  Desc:   TargetPort=00 TargetComponent=01 AssocRCRB- 
LinkType=MemMapped LinkValid+
Addr:   fed19000
Kernel driver in use: pcieport
Kernel modules: shpchp

  00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family High 
Definition Audio Controller [8086:27d8] (rev 01)
Subsystem: ASUSTeK Computer Inc. P5KPL-VM Motherboard [1043:8290]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Express (v1) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-

[Kernel-packages] [Bug 1628976] Re: Ubuntu 16.10: Oops panic in move_page_tables/page_remove_rmap after running memory_stress_ng.

[Tim Gardner]

https://lists.ubuntu.com/archives/kernel-team/2016-October/080310.html

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

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

** Changed in: linux (Ubuntu Yakkety)
 Assignee: Taco Screen team (taco-screen-team) => Tim Gardner (timg-tpi)

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

Title:
  Ubuntu 16.10: Oops panic in move_page_tables/page_remove_rmap after
  running memory_stress_ng.

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:
  FYI Canonical:

  We have been seeing various page handling issues during memory stress
  in the 4.8 kernels.  The following is the most recent issue resulting
  in system panics on this host after the 4.8.0-17 update:

  == Comment: #17 - PAVITHRA R. PRAKASH - 2016-09-28 06:26:21 ==
  Hi,

  Tried running on 4.8.0-17-generic kernel. Getting below call trace and
  system crashes. Attaching logs.

  [ 2959.364333] Unable to handle kernel paging request for data at address 
0xf2fe4020
  [ 2959.364345] Faulting instruction address: 0xc02bb2a0
  [ 2959.364356] Oops: Kernel access of bad area, sig: 11 [#1]
  [ 2959.364364] SMP NR_CPUS=2048 NUMA pSeries
  [ 2959.364377] Modules linked in: rpadlpar_io rpaphp dccp_diag dccp tcp_diag 
udp_diag inet_diag unix_diag af_packet_diag netlink_diag bnx2x mdio libcrc32c 
pseries_rng vmx_crypto binfmt_misc ip_tables x_tables autofs4 ibmvscsi 
crc32c_vpmsum
  [ 2959.364441] CPU: 13 PID: 108 Comm: oom_reaper Not tainted 4.8.0-17-generic 
#19-Ubuntu
  [ 2959.364452] task: c004fbdf9c00 task.stack: c004fbe0
  [ 2959.364461] NIP: c02bb2a0 LR: c0300618 CTR: 
c009ca40
  [ 2959.364471] REGS: c004fbe036e0 TRAP: 0300   Not tainted  
(4.8.0-17-generic)
  [ 2959.364481] MSR: 80010280b033   
CR: 24028844  XER: 200c
  [ 2959.364526] CFAR: c0300614 DAR: f2fe4020 DSISR: 4000 
SOFTE: 1 
 GPR00: c0300618 c004fbe03960 c14e5e00 
f2fe4000 
 GPR04: 0001 0800  
c1665e00 
 GPR08: f900a196 0001 02fe4000 
 
 GPR12: 8800 c1b37500 0008 
c1ffe7ff 
 GPR16: c004f62a55f0 3fff9a00 3fff9900 
 
 GPR20: c004fbe03b80 c004e0713800 8e017c3302c0 
0001 
 GPR24: c000fb3614c8 c000fce9d990 c000fce9d6e4 
96a100f90b40 
 GPR28: f2fe4000 c000fb3614c8 0001 
f2fe4000 
  [ 2959.364673] NIP [c02bb2a0] page_remove_rmap+0x30/0x4b0
  [ 2959.364685] LR [c0300618] zap_huge_pmd+0xf8/0x480
  [ 2959.364692] Call Trace:
  [ 2959.364699] [c004fbe03960] [c004fbe039a0] 0xc004fbe039a0 
(unreliable)
  [ 2959.364714] [c004fbe039a0] [c0300618] zap_huge_pmd+0xf8/0x480
  [ 2959.364726] [c004fbe039f0] [c02a68d8] 
unmap_page_range+0xd08/0xee0
  [ 2959.364740] [c004fbe03b20] [c025c474] 
__oom_reap_task+0x204/0x2c0
  [ 2959.364752] [c004fbe03c80] [c025cda8] oom_reaper+0x1e8/0x300
  [ 2959.364765] [c004fbe03d80] [c00fd120] kthread+0x110/0x130
  [ 2959.364778] [c004fbe03e30] [c00098f0] 
ret_from_kernel_thread+0x5c/0x6c
  [ 2959.364788] Instruction dump:
  [ 2959.364796] 3c4c0123 3842ab90 7c0802a6 fba1ffe8 fbc1fff0 fbe1fff8 f8010010 
f821ffc1 
  [ 2959.364821] 7c7f1b78 7c9e2378 6000 6000  71480001 
392a 40820008 
  [ 2959.364871] ---[ end trace 178b14c6911b70dc ]---
  [ 2959.372762] 
  [ 2959.372798] Sending IPI to other CPUs
  [ 2959.373834] IPI complete

  Thanks,
  Pavithra

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

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

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

[Apport retracing service]

** Tags removed: need-duplicate-check

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

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

Status in linux package in Ubuntu:
  New

Bug description:
  Ubuntu 4.4.0-31.50-generic 4.4.13
  00:00.0 Host bridge [0600]: Intel Corporation 82G33/G31/P35/P31 Express DRAM 
Controller [8086:29c0] (rev 10)
Subsystem: ASUSTeK Computer Inc. P5KPL-VM Motherboard [1043:82b0]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

  00:01.0 PCI bridge [0604]: Intel Corporation 82G33/G31/P35/P31 Express PCI 
Express Root Port [8086:29c1] (rev 10) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [88] Subsystem: ASUSTeK Computer Inc. 82G33/G31/P35/P31 
Express PCI Express Root Port [1043:82b0]
Capabilities: [80] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address:   Data: 
Capabilities: [a0] Express (v1) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
LnkCap: Port #2, Speed 2.5GT/s, Width x16, ASPM L0s, Exit 
Latency L0s <256ns, L1 <4us
ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ 
DLActive- BWMgmt- ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- 
Surprise-
Slot #0, PowerLimit 75.000W; Interlock- NoCompl-
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- 
LinkChg-
Control: AttnInd Off, PwrInd On, Power- Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ 
Interlock-
Changed: MRL- PresDet+ LinkState-
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- 
CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID , PMEStatus- PMEPending-
Capabilities: [100 v1] Virtual Channel
Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
Arb:Fixed- WRR32- WRR64- WRR128-
Ctrl:   ArbSelect=Fixed
Status: InProgress-
VC0:Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb:Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl:   Enable+ ID=0 ArbSelect=Fixed TC/VC=01
Status: NegoPending- InProgress-
Capabilities: [140 v1] Root Complex Link
Desc:   PortNumber=02 ComponentID=01 EltType=Config
Link0:  Desc:   TargetPort=00 TargetComponent=01 AssocRCRB- 
LinkType=MemMapped LinkValid+
Addr:   fed19000
Kernel driver in use: pcieport
Kernel modules: shpchp

  00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family High 
Definition Audio Controller [8086:27d8] (rev 01)
Subsystem: ASUSTeK Computer Inc. P5KPL-VM Motherboard [1043:8290]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Express (v1) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
   

[Kernel-packages] [Bug 1632434] [NEW] package linux-image-4.4.0-42-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 2

[natsihit]

Public bug reported:

Ubuntu 4.4.0-31.50-generic 4.4.13
00:00.0 Host bridge [0600]: Intel Corporation 82G33/G31/P35/P31 Express DRAM 
Controller [8086:29c0] (rev 10)
Subsystem: ASUSTeK Computer Inc. P5KPL-VM Motherboard [1043:82b0]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:01.0 PCI bridge [0604]: Intel Corporation 82G33/G31/P35/P31 Express PCI 
Express Root Port [8086:29c1] (rev 10) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [88] Subsystem: ASUSTeK Computer Inc. 82G33/G31/P35/P31 
Express PCI Express Root Port [1043:82b0]
Capabilities: [80] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address:   Data: 
Capabilities: [a0] Express (v1) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
LnkCap: Port #2, Speed 2.5GT/s, Width x16, ASPM L0s, Exit 
Latency L0s <256ns, L1 <4us
ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ 
DLActive- BWMgmt- ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- 
Surprise-
Slot #0, PowerLimit 75.000W; Interlock- NoCompl-
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- 
LinkChg-
Control: AttnInd Off, PwrInd On, Power- Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ 
Interlock-
Changed: MRL- PresDet+ LinkState-
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- 
CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID , PMEStatus- PMEPending-
Capabilities: [100 v1] Virtual Channel
Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
Arb:Fixed- WRR32- WRR64- WRR128-
Ctrl:   ArbSelect=Fixed
Status: InProgress-
VC0:Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb:Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl:   Enable+ ID=0 ArbSelect=Fixed TC/VC=01
Status: NegoPending- InProgress-
Capabilities: [140 v1] Root Complex Link
Desc:   PortNumber=02 ComponentID=01 EltType=Config
Link0:  Desc:   TargetPort=00 TargetComponent=01 AssocRCRB- 
LinkType=MemMapped LinkValid+
Addr:   fed19000
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family High Definition 
Audio Controller [8086:27d8] (rev 01)
Subsystem: ASUSTeK Computer Inc. P5KPL-VM Motherboard [1043:8290]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Express (v1) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ 
TransPend-
LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit 
Latency L0s <1us, L1 <4us
ClockPM- Surprise- LLActRep+ BwNot- ASPMOptComp-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta:

[Kernel-packages] [Bug 1628976] Re: Ubuntu 16.10: Oops panic in move_page_tables/page_remove_rmap after running memory_stress_ng.

[Breno Leitão]

The fix could be found at 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/1628976

Title:
  Ubuntu 16.10: Oops panic in move_page_tables/page_remove_rmap after
  running memory_stress_ng.

Status in linux package in Ubuntu:
  New

Bug description:
  FYI Canonical:

  We have been seeing various page handling issues during memory stress
  in the 4.8 kernels.  The following is the most recent issue resulting
  in system panics on this host after the 4.8.0-17 update:

  == Comment: #17 - PAVITHRA R. PRAKASH - 2016-09-28 06:26:21 ==
  Hi,

  Tried running on 4.8.0-17-generic kernel. Getting below call trace and
  system crashes. Attaching logs.

  [ 2959.364333] Unable to handle kernel paging request for data at address 
0xf2fe4020
  [ 2959.364345] Faulting instruction address: 0xc02bb2a0
  [ 2959.364356] Oops: Kernel access of bad area, sig: 11 [#1]
  [ 2959.364364] SMP NR_CPUS=2048 NUMA pSeries
  [ 2959.364377] Modules linked in: rpadlpar_io rpaphp dccp_diag dccp tcp_diag 
udp_diag inet_diag unix_diag af_packet_diag netlink_diag bnx2x mdio libcrc32c 
pseries_rng vmx_crypto binfmt_misc ip_tables x_tables autofs4 ibmvscsi 
crc32c_vpmsum
  [ 2959.364441] CPU: 13 PID: 108 Comm: oom_reaper Not tainted 4.8.0-17-generic 
#19-Ubuntu
  [ 2959.364452] task: c004fbdf9c00 task.stack: c004fbe0
  [ 2959.364461] NIP: c02bb2a0 LR: c0300618 CTR: 
c009ca40
  [ 2959.364471] REGS: c004fbe036e0 TRAP: 0300   Not tainted  
(4.8.0-17-generic)
  [ 2959.364481] MSR: 80010280b033   
CR: 24028844  XER: 200c
  [ 2959.364526] CFAR: c0300614 DAR: f2fe4020 DSISR: 4000 
SOFTE: 1 
 GPR00: c0300618 c004fbe03960 c14e5e00 
f2fe4000 
 GPR04: 0001 0800  
c1665e00 
 GPR08: f900a196 0001 02fe4000 
 
 GPR12: 8800 c1b37500 0008 
c1ffe7ff 
 GPR16: c004f62a55f0 3fff9a00 3fff9900 
 
 GPR20: c004fbe03b80 c004e0713800 8e017c3302c0 
0001 
 GPR24: c000fb3614c8 c000fce9d990 c000fce9d6e4 
96a100f90b40 
 GPR28: f2fe4000 c000fb3614c8 0001 
f2fe4000 
  [ 2959.364673] NIP [c02bb2a0] page_remove_rmap+0x30/0x4b0
  [ 2959.364685] LR [c0300618] zap_huge_pmd+0xf8/0x480
  [ 2959.364692] Call Trace:
  [ 2959.364699] [c004fbe03960] [c004fbe039a0] 0xc004fbe039a0 
(unreliable)
  [ 2959.364714] [c004fbe039a0] [c0300618] zap_huge_pmd+0xf8/0x480
  [ 2959.364726] [c004fbe039f0] [c02a68d8] 
unmap_page_range+0xd08/0xee0
  [ 2959.364740] [c004fbe03b20] [c025c474] 
__oom_reap_task+0x204/0x2c0
  [ 2959.364752] [c004fbe03c80] [c025cda8] oom_reaper+0x1e8/0x300
  [ 2959.364765] [c004fbe03d80] [c00fd120] kthread+0x110/0x130
  [ 2959.364778] [c004fbe03e30] [c00098f0] 
ret_from_kernel_thread+0x5c/0x6c
  [ 2959.364788] Instruction dump:
  [ 2959.364796] 3c4c0123 3842ab90 7c0802a6 fba1ffe8 fbc1fff0 fbe1fff8 f8010010 
f821ffc1 
  [ 2959.364821] 7c7f1b78 7c9e2378 6000 6000  71480001 
392a 40820008 
  [ 2959.364871] ---[ end trace 178b14c6911b70dc ]---
  [ 2959.372762] 
  [ 2959.372798] Sending IPI to other CPUs
  [ 2959.373834] IPI complete

  Thanks,
  Pavithra

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

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

[Kernel-packages] [Bug 1613270] Re: Cannot power down system

[Brian Knutsson]

Well something was fixed. I have had this laptop for 6 months, and it
NEVER worked, so someone did something.

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

Title:
  Cannot power down system

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I cannot do a shutdown of the system. It never turns off my computer.

  If I track the shutdown process, it ends with:
  System: Power down

  And then nothing happends except for the internal fans normally speeds
  up, but it does not turn off the PC.

  I can do a reboot without problems.

  I tried the dev kernel version 4.8.0 (amd64) but it did not solve the
  issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bfk5288 F pulseaudio
   /dev/snd/controlC1:  bfk5288 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Aug 15 14:22:07 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=1d553aaa-5506-4fdd-b6e4-2da0c11fb7f8
  InstallationDate: Installed on 2016-03-10 (157 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  MachineType: Apple Inc. MacBookPro11,5
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=980d5758-068c-4c32-8f18-ac0d9c15855b ro quiet splash acpi=force 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP114.88Z.0172.B06.1509021656
  dmi.board.name: Mac-06F11F11946D27C5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,5
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-06F11F11946D27C5
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B06.1509021656:bd09/02/2015:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5:
  dmi.product.name: MacBookPro11,5
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1630906] Re: QML segfault on arm64 due to builder kernel change

[Łukasz Zemczak]

As per the agreement, the xenial-based builders seem to be now running a
newer custom kernel (4.4.0-42-generic) that seems to no longer segfault
on QML code for arm64.

I suppose we can set the kernel task as Fix Released? Since I suppose
CONFIG_ARM64_VA_BITS=48 is the right way to go, with Qt just needing to
support it properly. This way at least we won't need to think about
SRUing it to xenial to get things unblocked. Also, our touch arm64
xenial devices are unaffected as they're still using the old kernel, so
no blockers here.

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

Title:
  QML segfault on arm64 due to builder kernel change

Status in linux package in Ubuntu:
  Confirmed
Status in online-accounts-api package in Ubuntu:
  New
Status in qmenumodel package in Ubuntu:
  New
Status in qtdeclarative-opensource-src package in Ubuntu:
  New
Status in ubuntu-push-qml package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Builders were changed from wily to xenial (4.4) kernel for arm64, and
  likely due to this the following kind of errors started happening:

  https://launchpadlibrarian.net/288487533/buildlog_ubuntu-yakkety-arm64
  .ubuntu-push-qml_0.1+15.10.20150826.1-0ubuntu2_BUILDING.txt.gz

  They happen when executing QML code.

  I've ruled out that reverting to previous qtbase and qtdeclarative
  versions don't affect this, so it's not coming from a Qt change. I've
  also verified there's no problem eg on our Bq tablet running the same
  tests on xenial+overlay. There are currently no found changes at least
  in Qt upstream to backport arm64 related fixes.

  Cause is unknown. But the same problem is there on vivid, xenial and yakkety 
builds:
  
https://launchpadlibrarian.net/288516465/buildlog_ubuntu-yakkety-arm64.online-accounts-api_0.1+16.10.20161006.1-0ubuntu1_BUILDING.txt.gz
  
https://launchpadlibrarian.net/288515705/buildlog_ubuntu-xenial-arm64.online-accounts-api_0.1+16.04.20161006.1-0ubuntu1_BUILDING.txt.gz
  
https://launchpadlibrarian.net/288515510/buildlog_ubuntu-vivid-arm64.online-accounts-api_0.1+15.04.20161006.1-0ubuntu1_BUILDING.txt.gz

  This means it does not matter if it's Qt 5.4 or 5.6, GCC 4.9, 5 or 6,
  or glibc 2.21, 2.23 or 2.24.

  More logs from affected packages:
  
https://launchpadlibrarian.net/288493058/buildlog_ubuntu-yakkety-arm64.qtdeclarative-opensource-src_5.6.1-7ubuntu3~1_BUILDING.txt.gz
  
https://launchpadlibrarian.net/288347391/buildlog_ubuntu-xenial-arm64.webbrowser-app_0.23+16.04.20161005.1-0ubuntu1_BUILDING.txt.gz
  
https://launchpadlibrarian.net/288385063/buildlog_ubuntu-vivid-arm64.qmenumodel_0.2.10+15.04.20161005.1-0ubuntu1_BUILDING.txt.gz

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

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

[Kernel-packages] [Bug 1403152] Re: unregister_netdevice: waiting for lo to become free. Usage count

[Alexandre]

Apparently the fix is in:

https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.22

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

Title:
  unregister_netdevice: waiting for lo to become free. Usage count

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Confirmed
Status in linux-lts-xenial package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Fix Released
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-lts-xenial source package in Trusty:
  Confirmed
Status in linux source package in Vivid:
  Fix Released

Bug description:
  SRU Justification:

  [Impact]

  Users of kernels that utilize NFS may see the following messages when
  shutting down and starting containers:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  Setup multiple containers in parallel to mount and NFS share, create
  some traffic and shutdown. Eventually you will see the kernel message.

  Dave's script here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1403152/comments/24

  [Fix]
  commit de84d89030fa4efa44c02c96c8b4a8176042c4ff upstream

  --

  I currently running trusty latest patches and i get on these hardware
  and software:

  Ubuntu 3.13.0-43.72-generic 3.13.11.11

  processor : 7
  vendor_id : GenuineIntel
  cpu family: 6
  model : 77
  model name: Intel(R) Atom(TM) CPU  C2758  @ 2.40GHz
  stepping  : 8
  microcode : 0x11d
  cpu MHz   : 2400.000
  cache size: 1024 KB
  physical id   : 0
  siblings  : 8
  core id   : 7
  cpu cores : 8
  apicid: 14
  initial apicid: 14
  fpu   : yes
  fpu_exception : yes
  cpuid level   : 11
  wp: yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm 
constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc 
aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm 
sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch 
arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms
  bogomips  : 4799.48
  clflush size  : 64
  cache_alignment   : 64
  address sizes : 36 bits physical, 48 bits virtual
  power management:

  somehow reproducable the subjected error, and lxc is working still but
  not more managable until a reboot.

  managable means every command hangs.

  I saw there are alot of bugs but they seams to relate to older version
  and are closed, so i decided to file a new one?

  I run alot of machine with trusty an lxc containers but only these kind of 
machines produces these errors, all
  other don't show these odd behavior.

  thx in advance

  meno

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

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

[Kernel-packages] [Bug 1584479] Re: [MSI GP72 6QE Leopard Pro] acpi=off required to boot

[jiapei100]

I'm using a MSI GT72-6QE, and my OS is Ubuntu 16.04.1 LTS. My touchpad doesn 
NOT work as well. And I'm pretty sure I've already did "acpi=off".

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=off
intel_idle.max_cstate=0"

is enabled in my /etc/default/grub .

So, is there a standard solution for now?

Cheers

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

Title:
  [MSI GP72 6QE Leopard Pro] acpi=off required to boot

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hi,
  I just install Ubuntu 16.04 on my new MSI laptop G72 6QE.
  My touchpad doesn't work and recognize at all.

  I try :
  - Fn+F3 to activate my touchpad
  - xinput list and is not listed
  - xev and nothing append (no signal)
  - cat /proc/bus/input/devices ddoesn't display touchpad (only HDMI, mic, 
headphone, external mouse and keyboard)
  - I don't know if there is a link, but some buttons of my keyboard don't work 
(like Fn+arrows to manage sound and luminosity) :
  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input0
  U: Uniq=
  H: Handlers=sysrq kbd event0 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=60070290 8380207af040d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  
  Thanks
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1305 F pulseaudio
moi1668 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=9649bbed-2d32-42cd-a446-43abaa9ab1f3
  InstallationDate: Installed on 2016-05-20 (2 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: Micro-Star International Co., Ltd. GP72 6QE
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-22-generic 
root=UUID=80432220-0bdf-49f0-a145-0c015ad36c2a ro rootflags=subvol=@ acpi=off 
acpi_osi=! acpi_backlight=native i8042.nopnp quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  Tags:  xenial
  Uname: Linux 4.4.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1795IMS.10C
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-1795
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.A
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1795IMS.10C:bd12/10/2015:svnMicro-StarInternationalCo.,Ltd.:pnGP726QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1795:rvrREV0.A:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:
  dmi.product.name: GP72 6QE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Kernel-packages] [Bug 1629386] Re: Xenial update to v4.4.23 stable release

[Seth Forshee]

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

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

Title:
  Xenial update to v4.4.23 stable release

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

Bug description:
  SRU Justification

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

     git://git.kernel.org/

  TEST CASE: TBD

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

  include/linux/kernel.h: change abs() macro so it uses consistent return type
  Fix build warning in kernel/cpuset.c
  reiserfs: fix "new_insert_key may be used uninitialized ..."
  ipv4: panic in leaf_walk_rcu due to stale node pointer
  ipv6: release dst in ping_v6_sendmsg
  tcp: cwnd does not increase in TCP YeAH
  tcp: properly scale window in tcp_v[46]_reqsk_send_ack()
  crypto: arm64/aes-ctr - fix NULL dereference in tail processing
  crypto: arm/aes-ctr - fix NULL dereference in tail processing
  crypto: skcipher - Fix blkcipher walk OOM crash
  crypto: echainiv - Replace chaining with multiplication
  ocfs2/dlm: fix race between convert and migration
  ocfs2: fix start offset to ocfs2_zero_range_for_truncate()
  kbuild: Do not run modules_install and install in paralel
  Makefile: revert "Makefile: Document ability to make file.lst and file.S" 
partially
  tools: Support relative directory path for 'O='
  kbuild: forbid kernel directory to contain spaces and colons
  Kbuild: disable 'maybe-uninitialized' warning for CONFIG_PROFILE_ALL_BRANCHES
  gcov: disable -Wmaybe-uninitialized warning
  Disable "maybe-uninitialized" warning globally
  Disable "frame-address" warning
  Makefile: Mute warning for __builtin_return_address(>0) for tracing only
  net: caif: fix misleading indentation
  Add braces to avoid "ambiguous ‘else’" compiler warnings
  am437x-vfpe: fix typo in vpfe_get_app_input_index
  ath9k: fix misleading indentation
  iwlegacy: avoid warning about missing braces
  Staging: iio: adc: fix indent on break statement
  nouveau: fix nv40_perfctr_next() cleanup regression
  bonding: Fix bonding crash
  Revert "af_unix: Fix splice-bind deadlock"
  af_unix: split 'u->readlock' into two: 'iolock' and 'bindlock'
  vti: flush x-netns xfrm cache when vti interface is removed
  net/irda: handle iriap_register_lsap() allocation failure
  tipc: fix NULL pointer dereference in shutdown()
  net/mlx5: Added missing check of msg length in verifying its signature
  net: dsa: bcm_sf2: Fix race condition while unmasking interrupts
  Revert "phy: IRQ cannot be shared"
  net: smc91x: fix SMC accesses
  bridge: re-introduce 'fix parsing of MLDv2 reports'
  autofs races
  autofs: use dentry flags to block walks during expire
  xfs: prevent dropping ioend completions during buftarg wait
  fsnotify: add a way to stop queueing events on group shutdown
  fanotify: fix list corruption in fanotify_get_response()
  fix fault_in_multipages_...() on architectures with no-op access_ok()
  mtd: maps: sa1100-flash: potential NULL dereference
  mtd: pmcmsp-flash: Allocating too much in init_msp_flash()
  power: reset: hisi-reboot: Unmap region obtained by of_iomap
  fix memory leaks in tracing_buffers_splice_read()
  tracing: Move mutex to protect against resetting of seq data
  mm: delete unnecessary and unsafe init_tlb_ubc()
  can: flexcan: fix resume function
  nl80211: validate number of probe response CSA counters
  btrfs: ensure that file descriptor used with subvol ioctls is a dir
  i2c-eg20t: fix race between i2c init and interrupt enable
  i2c: qup: skip qup_i2c_suspend if the device is already runtime suspended
  MIPS: Fix pre-r6 emulation FPU initialisation
  MIPS: SMP: Fix possibility of deadlock when bringing CPUs online
  MIPS: vDSO: Fix Malta EVA mapping to vDSO page structs
  MIPS: Remove compact branch policy Kconfig entries
  MIPS: Avoid a BUG warning during prctl(PR_SET_FP_MODE, ...)
  MIPS: Add a missing ".set pop" in an early commit
  MIPS: paravirt: Fix undefined reference to smp_bootstrap
  PM / hibernate: Restore processor state before using per-CPU variables
  PM / hibernate: Fix rtree_next_node() to avoid walking off list ends
  power_supply: tps65217-charger: fix missing platform_set_drvdata()
  power: supply: max17042_battery: fix model download bug.
  qxl: check for kmap failures
  hostfs: Freeing an ERR_PTR in hostfs_fill_sb_common()
  Linux 4.4.23

To manage notification

[Kernel-packages] [Bug 1631468] Re: Xenial update to v4.4.24 stable release

[Seth Forshee]

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

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

Title:
  Xenial update to v4.4.24 stable release

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

Bug description:
  SRU Justification

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

     git://git.kernel.org/

  TEST CASE: TBD

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

  cpuset: handle race between CPU hotplug and cpuset_hotplug_work
  mtd: nand: davinci: Reinitialize the HW ECC engine in 4bit hwctl
  mm,ksm: fix endless looping in allocating memory when ksm enable
  can: dev: fix deadlock reported after bus-off
  x86/init: Fix cr4_init_shadow() on CR4-less machines
  x86/boot: Initialize FPU and X86_FEATURE_ALWAYS even if we don't have CPUID
  drm/nouveau/fifo/nv04: avoid ramht race against cookie insertion
  drm/radeon/si/dpm: add workaround for for Jet parts
  ARM: 8616/1: dt: Respect property size when parsing CPUs
  ARM: 8617/1: dma: fix dma_max_pfn()
  usb: musb: Fix DMA desired mode for Mentor DMA engine
  usb: musb: fix DMA for host mode
  iwlwifi: mvm: fix a few firmware capability checks
  perf/core: Fix pmu::filter_match for SW-led groups
  i40e: avoid null pointer dereference
  pinctrl: uniphier: fix .pin_dbg_show() callback
  pinctrl: Flag strict is a field in struct pinmux_ops
  drivers/perf: arm_pmu: Fix leak in error path
  mmc: pxamci: fix potential oops
  tools/vm/slabinfo: fix an unintentional printf
  ipvs: fix bind to link-local mcast IPv6 address in backup
  nvmem: Declare nvmem_cell_read() consistently
  hwmon: (adt7411) set bit 3 in CFG1 register
  spi: sh-msiof: Avoid invalid clock generator parameters
  iwlwifi: pcie: fix access to scratch buffer
  iwlwifi: mvm: don't use ret when not initialised
  ceph: fix race during filling readdir cache
  usb: gadget: fsl_qe_udc: signedness bug in qe_get_frame()
  gpio: sa1100: fix irq probing for ucb1x00
  irqchip/gicv3: Silence noisy DEBUG_PER_CPU_MAPS warning
  ARM: 8618/1: decompressor: reset ttbcr fields to use TTBR0 on ARMv7
  arm64: debug: avoid resetting stepping state machine when TIF_SINGLESTEP
  MIPS: uprobes: remove incorrect set_orig_insn
  MIPS: fix uretprobe implementation
  MIPS: Malta: Fix IOCU disable switch read for MIPS64
  MIPS: uprobes: fix use of uninitialised variable
  printk: fix parsing of "brl=" option
  tpm: fix byte-order for the value read by tpm2_get_tpm_pt
  regulator: qcom_spmi: Add support for S4 supply on pm8941
  regulator: qcom_spmi: Add support for get_mode/set_mode on switches
  regulator: qcom_spmi: Update mvs1/mvs2 switches on pm8941
  regulator: qcom_smd: Fix voltage ranges for pm8x41
  ARM: sun5i: Fix typo in trip point temperature
  ARM: sa1100: register clocks early
  ARM: sa1100: fix 3.6864MHz clock
  ARM: sa1100: clear reset status prior to reboot
  ARM: shmobile: fix regulator quirk for Gen2
  ARM: sa: fix pcmcia suspend/resume
  hwrng: omap - Fix assumption that runtime_get_sync will always succeed
  blk-mq: actually hook up defer list when running requests
  pstore: drop file opened reference count
  tile: Define AT_VECTOR_SIZE_ARCH for ARCH_DLINFO
  iwlmvm: mvm: set correct state in smart-fifo configuration
  NFC: fdp: Detect errors from fdp_nci_create_conn()
  em28xx-i2c: rt_mutex_trylock() returns zero on failure
  gspca: avoid unused variable warnings
  ath9k: Fix programming of minCCA power threshold
  avr32: off by one in at32_init_pio()
  fnic: pci_dma_mapping_error() doesn't return an error code
  dmaengine: at_xdmac: fix debug string
  svc: Avoid garbage replies when pc_func() returns rpc_drop_reply
  NFS: Don't drop CB requests with invalid principals
  pNFS/files: Fix layoutcommit after a commit to DS
  pNFS/flexfiles: Fix layoutcommit after a commit to DS
  ASoC: Intel: Skylake: Fix error return code in skl_probe()
  brcmfmac: Fix glob_skb leak in brcmf_sdiod_recv_chain
  brcmsmac: Free packet if dma_mapping_error() fails in dma_rxfill
  brcmsmac: Initialize power in brcms_c_stf_ss_algo_channel_get()
  powerpc/prom: Fix sub-processor option passed to ibm, 
client-architecture-support
  sysctl: handle error writing UINT_MAX to u32 fields
  ASoC: omap-mcpdm: Fix irq resource handling
  kernel/fork: fix CLONE_CHILD_CLEARTID regression in nscd
  dmaengine: at_xdmac: fix to pass correct device identity to free_irq()
  KVM

[Kernel-packages] [Bug 1630857] Re: Dell Precision Trackpoint not working after suspend

[Seth Forshee]

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

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => AceLan Kao (acelankao)

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

Title:
   Dell Precision Trackpoint not working after suspend

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Steps:
  1) Install Ubuntu 16.04
  2) Enter Desktop.
  3) Suspend system.
  4) Using the trackpoint.
  5) Click the left button with DualPoint stick.
  6) Click the right button with DualPoint stick.
  7) Click the middle button with DualPoint stick.
  8) Double-click the left button with DualPoint stick.

  Expected results: Trackpoint and DualPoint stick can work after
  suspend.

  Actual results: Trackpoing and DualPoint stick not working after
  suspend.

  Manufacturer: Dell Inc.

  ProductName: Precision 7500

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

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

[Kernel-packages] [Bug 1632049] Re: PSL data cache should be flushed before resetting CAPI adapter

[Seth Forshee]

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

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

Title:
  PSL data cache should be flushed before resetting CAPI adapter

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

Bug description:
  ---Problem Description---
  The PSL data cache should be flushed before resetting a CAPI adapter.
  If the PSL data cache holds dirty cache line when it is reset, the host 
trying to access that memory when the link is down may face a Uncorrectable 
Error (UE), forcing a reboot of the system.
   
  ---uname output---
  Linux freak 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:40:06 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  CAPI adapter needed + AFU image using the PSL cache (e.g. afu_directed 
memcpy) 

   
  Machine Type = Tuleta 

  ---Steps to Reproduce---
   There's some randomness to it, but triggering a memcpy test + card reset in 
a loop can produce it:

  memcpy_afu_ctx -p100 -l1000
  echo 1 > /sys/class/cxl/card0/reset
  Fix is already upstream under commit ID:
  aaa2245ed836824f21f8e42e0ab63b1637d1cb20 
  "cxl: Flush PSL cache before resetting the adapter"

  We would like the fix released for both 16.04 and 16.10 please.

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

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

[Kernel-packages] [Bug 1630038] Re: thunder nic: avoid link delays due to RX_PACKET_DIS

[Seth Forshee]

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

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

Title:
  thunder nic: avoid link delays due to RX_PACKET_DIS

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

Bug description:
  [Impact]
  Link establishment is delayed during initialization, possibly resulting in 
remote fault conditions that may cause the interface to fail to come up.

  [Test Case]
  Put the system in a reboot loop and watch for a remote fault condition, or a 
failure to bring up the link that can only be resolved by reloading the module.

  [Regression Risk]
  Patch is to a specific driver that is only used on Cavium ThunderX systems. 
The patch is upstream, so will have upstream support for regressions.

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

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

[Andrzej Mazur]

the same problem for me:

When I start fresh system, the suspend to RAM and resume works properly. 
But after certain amount of time when OS works, suspending and resuming ends 
with no response (blank screen). 

Ubuntu 16.04 64bit, Toshiba A200-1N8, 4.4.0-38-generic, Intel(R)
Core(TM)2 Duo CPU T7250

-- 
You 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 1602577] Re: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel

[Joseph Salisbury]

** Tags removed: kernel-key
** 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/1602577

Title:
  [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel

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

Bug description:
  Hi,

  In order to investigate bug LP#1531768, we upgraded some arm64 compute
  nodes (swirlices) to a 4.4 kernel. I think it made the VMs work
  better, but the hosts became extremely unstable.

  After some time, getting a shell on them would be impossible.
  Connecting on the VSP, you'd get a prompt, and once you typed your
  username and password, you'd see the motd but the shell would never
  spawn.

  Because of these instability issues, all the arm64 compute nodes are
  now back on 4.2. However, we managed to capture "perf record" data
  when a host was failing. I'll attach it to the bug. Perhaps it will
  give you hints as to what we can do to help you troubleshoot this bug
  further.

  Once we have your instructions, we'll happily reboot one (or a few)
  nodes to 4.4 to continue troubleshooting.

  Thanks !
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 12 12:54 seq
   crw-rw 1 root audio 116, 33 Jul 12 12:54 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: arm64
  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: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l
  ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-41-generic N/A
   linux-backports-modules-4.2.0-41-generic  N/A
   linux-firmware1.127.22
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 4.2.0-41-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1632237] Re: I have no expertise on progamming please

[Paul White]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).

You don't even tell us which version/release of Ubuntu you are using.

Please also change the bug title to something that better describes your
issue.

Thanks!

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

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

Title:
  I have no expertise on progamming please

Status in bcmwl package in Ubuntu:
  Incomplete

Bug description:
  Installation of upgrades failed

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

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

[Kernel-packages] [Bug 1632375] Re: linux: 4.4.0-43.63 -proposed tracker

[Brad Figg]

Derivative packages from packages here can be worked on, the following tracking 
bugs were opened for them:
linux-raspi2 - bug 1632378
linux-snapdragon - bug 1632379

Backport packages from packages here can be worked on, the following tracking 
bugs were opened for them:
linux-lts-xenial (14.04.1) - bug 1632380

** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 4.4.0-43.63 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+ 
+ kernel-stable-phase:Packaging
+ kernel-stable-phase-changed:Tuesday, 11. October 2016 15:45 UTC

** Description changed:

  This bug is for tracking the 4.4.0-43.63 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  kernel-stable-phase:Packaging
  kernel-stable-phase-changed:Tuesday, 11. October 2016 15:45 UTC
+ 
+ -- swm properties --
+ derivative-trackers-created: true
+ phase: Packaging

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

Title:
  linux: 4.4.0-43.63 -proposed tracker

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

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

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

  kernel-stable-phase:Packaging
  kernel-stable-phase-changed:Tuesday, 11. October 2016 15:45 UTC

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

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

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

[Kernel-packages] [Bug 1632375] [NEW] linux: 4.4.0-43.63 -proposed tracker

[Seth Forshee]

Public bug reported:

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

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

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Status: Invalid

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: linux (Ubuntu Xenial)
 Importance: Medium
 Status: Confirmed


** Tags: block-proposed block-proposed-xenial kernel-release-tracking-bug xenial

** Tags added: kernel-release-tracking-bug

** Tags added: block-proposed

** Tags added: block-proposed-xenial

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

** Tags added: xenial

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

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (cano

[Kernel-packages] [Bug 1628124] Re: Yakkety - Enable the arm64 arch on Raspberry Pi

[Andy Whitcroft]

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

** Also affects: linux-meta-raspi2 (Ubuntu)
   Importance: Undecided
   Status: New

** Package changed: linux (Ubuntu Yakkety) => linux-raspi2 (Ubuntu
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/1628124

Title:
  Yakkety - Enable the arm64 arch on Raspberry Pi

Status in linux-meta-raspi2 package in Ubuntu:
  New
Status in linux-raspi2 package in Ubuntu:
  Fix Committed
Status in linux-meta-raspi2 source package in Yakkety:
  New
Status in linux-raspi2 source package in Yakkety:
  Fix Committed

Bug description:
  Enable arm64 on the raspi2 branch of Yakkety. No functional change to
  armhf.

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

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

[Kernel-packages] [Bug 1632116] Re: Paths not failed properly when unmapping virtual FC ports in VIOS (using ibmvfc)

[Tim Gardner]

https://lists.ubuntu.com/archives/kernel-team/2016-October/080309.html

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

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

** Changed in: linux (Ubuntu Yakkety)
 Assignee: Taco Screen team (taco-screen-team) => Tim Gardner (timg-tpi)

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

Title:
  Paths not failed properly when unmapping virtual FC ports in VIOS
  (using ibmvfc)

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:
  ---Problem Description---
  vios vfc unmap (vfcmap -vadapter vfchost0 -fcp) can result in no i/o being 
retried nor device offline.

  ---uname output---
  Linux ubuntu16 4.4.0-9136-generic #55-Ubuntu SMP Fri Aug 26 05:56:24 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = Power8 LPAR 
   
  ---Steps to Reproduce---
   Ubuntu 16.10 lpar with two vfc adapters mapped to SAN Storage and configured 
with mulitpath.
  In vios do:  vfcmap -vadapter vfchost0 -fcp (where vfchost0 maps to test 
lpar).  multipath -ll and lvm commands hang in linux lpar.  tail 
/var/log/message hangs sometimes. multipath doesn't see failing devices and 
doesn't mark paths down.

  
  Fyi ...
   the following patch fixes the problem, which is now upstream accepted in 
the scsi tree as
  
http://git.kernel.org/cgit/linux/kernel/git/mkp/scsi.git/commit/?h=for-next&id=07d0e9a847401ffd2f09bd450d41644cd090e81d
  ("scsi: ibmvfc: Fix I/O hang when port is not mapped")

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

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

[Kernel-packages] [Bug 1632369] Re: linux-lts-vivid: 3.19.0-72.80~14.04.1 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 3.19.0-72.80~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1632368
+ kernel-stable-phase:Packaging
+ kernel-stable-phase-changed:Tuesday, 11. October 2016 15:30 UTC

** Description changed:

  This bug is for tracking the 3.19.0-72.80~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
+ derivative-trackers-created: true
  kernel-stable-master-bug: 1632368
- kernel-stable-phase:Packaging
- kernel-stable-phase-changed:Tuesday, 11. October 2016 15:30 UTC
+ phase: Packaging

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

Title:
  linux-lts-vivid: 3.19.0-72.80~14.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1632368
  phase: Packaging

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

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

[Kernel-packages] [Bug 1572801] Re: Ubuntu 16.04 Unity desktop uses much more ram than Ubuntu 15.10

[Khurshid Alam]

Now I can confirm It's definitely the kernel. Here are my test result:

Kernel RAM usage after boot
---
4.4.0-18:  600MB
4.4.0-22:  600MB

4.4.0-31:  900MB
4.4-0-38:  900MB
4.4-0-42:  1000MB

4.8-0-22:  900MB (Yakkety)


Can anyone confirm ?

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

Title:
  Ubuntu 16.04 Unity desktop uses much more ram than Ubuntu 15.10

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

Bug description:
  Ubuntu 16.04 64bit ISO number 20160420.1
  unity version 7.4.0+16.04.20160415-0ubuntu1
  Ubuntu 16.04 64bit ram usage has increase dramatically over Ubuntu 15.10
  Ubuntu 16.04 ram roughly 1 GB Ubuntu15.10 can be tuned to 420, 450 MB
  Ubuntu 16.04 with unity uses 1GB whereas Kubuntu 16.04 is using 420MB live usb

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.376
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Apr 21 01:44:22 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  GsettingsChanges:
   b'org.compiz.core' b'outputs' b"['1920x1080+0+0']"
   b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 
'place', 'regex', 'resize', 'session', 'snap', 'vpswitch', 'wall', 'animation', 
'commands', 'compiztoolbox', 'copytex', 'fade', 'grid', 'imgpng', 'mousepoll', 
'move', 'scale', 'unitymtgrabhandles', 'workarounds', 'expo', 'ezoom', 
'unityshell']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  MachineType: ASUS All Series
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --- 
cdrom-detect/try-usb=true noprompt
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/03/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2004
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2004:bd06/03/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PLUS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Apr 21 01:37:17 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Kernel-packages] [Bug 1632045] Re: Host OS slowly runs out of available memory after running UbuntuKVM Guest Create/Destroy loop #59

[Brian Murray]

** Package changed: kernel-package (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/1632045

Title:
  Host OS slowly runs out of available memory after running UbuntuKVM
  Guest Create/Destroy loop #59

Status in linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  https://github.com/open-power/supermicro-openpower/issues/59

  SW/HW Configuration

  PNOR image version: 5/3/2016
  BMC image version: 0.25
  CPLD Version: B2.81.01
  Host OS version: Ubuntu 16.04 LTS
  UbuntuKVM Guest OS version: Ubuntu 14.04.4 LTS
  HTX version: 394
  Processor: 00UL865 * 2
  Memory: SK hynix 16GB 2Rx4 PC4-2133P * 16
  Summary of Issue

  Two UbuntuKVM guests are each configured with 8 processors, 64 GB of
  memory, 1 disk of 128 GB, 1 network interface, and 1 GPU (pass-
  through'd from the Host OS's K80).

  The two guests are each put into a Create/Destroy loop, with HTX
  running on each of the guests (NOT HOST) in between its creation and
  destruction. The mdt.bu profile is used, and the processors, memory,
  and the GPU are put under load. The HTX session lasts 9 minutes.

  While this is running, the amount of available memory (free memory) in
  the Host OS will slowly decrease, and this can continue until the
  point wherein there's no more free memory for the Host OS to do
  anything, including creating the two VM guests. It seems to be that
  after every cycle, a small portion of the memory that was allocated to
  the VM guest does not get released back to the Host OS, and
  eventually, this can and will add up to take up all the available
  memory in the Host OS.

  At some point, the VM guest(s) might get disconnected and will display
  the following error:

  error: Disconnected from qemu:///system due to I/O error

  error: One or more references were leaked after disconnect from
  the hypervisor

  Then, when the Host OS tries to start the VM guest again, the
  following error shows up:

  error: Failed to create domain from guest2_trusty.xml
  error: internal error: early end of file from monitor, possible problem: 
Unexpected error in spapr_alloc_htab() at 
/build/qemu-c3ZrbA/qemu-2.5+dfsg/hw/ppc/spapr.c:1030:
  2016-05-23T16:18:16.871549Z qemu-system-ppc64: Failed to allocate HTAB of 
requested size, try with smaller maxmem

  The Host OS syslog, as seen HERE, also contains quite some errors.
  To just list a few:

  May 13 20:27:44 191-136 kernel: [36827.151228] alloc_contig_range: 
[3fb800, 3fd8f8) PFNs busy
  May 13 20:27:44 191-136 kernel: [36827.151291] alloc_contig_range: 
[3fb800, 3fd8fc) PFNs busy
  May 13 20:27:44 191-136 libvirtd[19263]: *** Error in 
`/usr/sbin/libvirtd': realloc(): invalid next size: 0x01000a780400 ***
  May 13 20:27:44 191-136 libvirtd[19263]: === Backtrace: =
  May 13 20:27:44 191-136 libvirtd[19263]: 
/lib/powerpc64le-linux-gnu/libc.so.6(+0x8720c)[0x3fffaf6a720c]
  May 13 20:27:44 191-136 libvirtd[19263]: 
/lib/powerpc64le-linux-gnu/libc.so.6(+0x96f70)[0x3fffaf6b6f70]
  May 13 20:27:44 191-136 libvirtd[19263]: 
/lib/powerpc64le-linux-gnu/libc.so.6(realloc+0x16c)[0x3fffaf6b87fc]
  May 13 20:27:44 191-136 libvirtd[19263]: 
/usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virReallocN+0x68)[0x3fffaf90ccc8]
  May 13 20:27:44 191-136 libvirtd[19263]: 
/usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so(+0x8ef6c)[0x3fff9346ef6c]
  May 13 20:27:44 191-136 libvirtd[19263]: 
/usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so(+0xa826c)[0x3fff9348826c]
  May 13 20:27:44 191-136 libvirtd[19263]: 
/usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virEventPollRunOnce+0x8b4)[0x3fffaf9332b4]
  May 13 20:27:44 191-136 libvirtd[19263]: 
/usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virEventRunDefaultImpl+0x54)[0x3fffaf931334]
  May 13 20:27:44 191-136 libvirtd[19263]: 
/usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virNetDaemonRun+0x1f0)[0x3fffafad2f70]
  May 13 20:27:44 191-136 libvirtd[19263]: 
/usr/sbin/libvirtd(+0x15d74)[0x52e45d74]
  May 13 20:27:44 191-136 libvirtd[19263]: 
/lib/powerpc64le-linux-gnu/libc.so.6(+0x2319c)[0x3fffaf64319c]
  May 13 20:27:44 191-136 libvirtd[19263]: 
/lib/powerpc64le-linux-gnu/libc.so.6(__libc_start_main+0xb8)[0x3fffaf6433b8]
  May 13 20:27:44 191-136 libvirtd[19263]: === Memory map: 
  May 13 20:27:44 191-136 libvirtd[19263]: 52e3-52eb r-xp  
08:02 65540510 /usr/sbin/libvirtd
  May 13 20:27:44 191-136 libvirtd[19263]: 52ec-52ed r--p 0008 
08:02 65540510 /usr/sbin/libvirtd
  May 13 20:27:44 191-136 libvirtd[19263]: 52ed-52ee rw-p 0009 
08:02 65540510 /usr/sbin/libvirtd
  May 13 20:27:44 191-136 libvirtd[19263]: 1000a73-1000a83 rw-p 
 00:00 0 [heap]
  May 13 20:27:44 191-136 libvirtd[19263]: 3fff6000-3fff6003

[Kernel-packages] [Bug 1632368] Packages available

[Brad Figg]

Backport packages from packages here can be worked on, the following tracking 
bugs were opened for them:
linux-lts-vivid (14.04.1) - bug 1632369

** Description changed:

  This bug is for tracking the 3.19.0-72.80 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+ 
+ kernel-stable-phase:Packaging
+ kernel-stable-phase-changed:Tuesday, 11. October 2016 15:15 UTC

** Description changed:

  This bug is for tracking the 3.19.0-72.80 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  kernel-stable-phase:Packaging
  kernel-stable-phase-changed:Tuesday, 11. October 2016 15:15 UTC
+ 
+ -- swm properties --
+ derivative-trackers-created: true
+ phase: Packaging

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

Title:
  linux: 3.19.0-72.80 -proposed tracker

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

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

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

  kernel-stable-phase:Packaging
  kernel-stable-phase-changed:Tuesday, 11. October 2016 15:15 UTC

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

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

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

[Kernel-packages] [Bug 1632368] Re: linux: 3.19.0-72.80 -proposed tracker

[Seth Forshee]

** Changed in: kernel-sru-workflow/regression-testing
   Importance: Undecided => Medium

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

** Changed in: kernel-sru-workflow/security-signoff
   Importance: Undecided => Medium

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

** Changed in: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/upload-to-ppa
   Status: New => Invalid

** Changed in: kernel-sru-workflow/verification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/verification-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

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

Title:
  linux: 3.19.0-72.80 -proposed tracker

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

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

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

  kernel-stable-phase:Packaging
  kernel-stable-phase-changed:Tuesday, 11. October 2016 15:15 UTC

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

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

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

[Kernel-packages] [Bug 1632369] [NEW] linux-lts-vivid: 3.19.0-72.80~14.04.1 -proposed tracker

[Brad Figg]

Public bug reported:

This bug is for tracking the 3.19.0-72.80~14.04.1 upload package. This
bug will contain status and testing results related to that upload.

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-stable-master-bug: 1632368

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-lts-vivid (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux-lts-vivid (Ubuntu Trusty)
 Importance: Medium
 Status: Confirmed


** Tags: block-proposed-trusty kernel-release-tracking-bug trusty

** Tags added: kernel-release-tracking-bug

** Tags added: block-proposed-trusty

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

** Tags added: trusty

** Changed in: linux-lts-vivid (Ubuntu Trusty)
   Status: New => Confirmed

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kern

[Kernel-packages] [Bug 1561474] Re: Bluetooth will be disable after resume from suspend on Xenial

[mosquito]

same bug here on Lenovo S20-30, i filld a bug report and marked it as
duplicated #1632360

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

Title:
  Bluetooth will be disable after resume from suspend on Xenial

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  CID: 201208-11536 Dell Latitude 6430u

  The Bluetooth will be disabled after resume from suspend.
  You will need to use "hciconfig hci0 reset" to enable it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-15-generic 4.4.0-15.31
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1202 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Mar 24 19:14:07 2016
  HibernationDevice: RESUME=UUID=25c03762-079c-4c6d-aedb-ec768318a6bf
  InstallationDate: Installed on 2016-03-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
  MachineType: Dell Inc. Latitude 6430U
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic 
root=UUID=18cfda3e-4f3d-40cf-8e7e-a83030819487 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: 11/15/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.asset.tag: 1234567
  dmi.board.name: 0MN74V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X01
  dmi.chassis.asset.tag: 1234567
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd11/15/2012:svnDellInc.:pnLatitude6430U:pvr01:rvnDellInc.:rn0MN74V:rvrX01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 6430U
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1632368] Re: linux: 3.19.0-72.80 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/prepare-package-signed
   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/1632368

Title:
  linux: 3.19.0-72.80 -proposed tracker

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

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

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

  kernel-stable-phase:Packaging
  kernel-stable-phase-changed:Tuesday, 11. October 2016 15:15 UTC

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

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

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

[Kernel-packages] [Bug 1632360] Re: bluetooth stop working after resume from sleep/suspend

[mosquito]

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

** This bug has been marked a duplicate of bug 1561474
   Bluetooth will be disable after resume from suspend on 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/1632360

Title:
  bluetooth stop working after resume from sleep/suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend/sleep bluetooth seems to stop working.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-42-generic 4.4.0-42.62
  ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
  Uname: Linux 4.4.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jemand 1434 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Oct 11 16:56:46 2016
  HibernationDevice: RESUME=UUID=ec4eb0b5-dad4-42e7-b5d0-c575bfe8781a
  InstallationDate: Installed on 2016-10-11 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO INVALID
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-42-generic.efi.signed 
root=UUID=f1eaf3e6-0728-453a-abeb-46cdc4cc1626 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-42-generic N/A
   linux-backports-modules-4.4.0-42-generic  N/A
   linux-firmware1.157.4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/08/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: ACCN19WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: IdeaPad S20-30
  dmi.board.vendor: LENOVO
  dmi.board.version: 12345678WIN8 PRO
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S20-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrACCN19WW:bd10/08/2014:svnLENOVO:pnINVALID:pvrLenovoIdeaPadS20-30:rvnLENOVO:rnIdeaPadS20-30:rvr12345678WIN8PRO:cvnLENOVO:ct10:cvrLenovoIdeaPadS20-30:
  dmi.product.name: INVALID
  dmi.product.version: Lenovo IdeaPad S20-30
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1632368] [NEW] linux: 3.19.0-72.80 -proposed tracker

[Seth Forshee]

Public bug reported:

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

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

kernel-stable-phase:Packaging
kernel-stable-phase-changed:Tuesday, 11. October 2016 15:15 UTC

-- swm properties --
derivative-trackers-created: true
phase: Packaging

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Status: Invalid

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: linux (Ubuntu Vivid)
 Importance: Medium
 Status: Confirmed


** Tags: block-proposed-vivid kernel-release-tracking-bug vivid

** Tags added: kernel-release-tracking-bug

** Tags added: block-proposed-vivid

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

** Tags added: vivid

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

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

[Kernel-packages] [Bug 1632045] [NEW] Host OS slowly runs out of available memory after running UbuntuKVM Guest Create/Destroy loop #59

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

---Problem Description---
https://github.com/open-power/supermicro-openpower/issues/59

SW/HW Configuration

PNOR image version: 5/3/2016
BMC image version: 0.25
CPLD Version: B2.81.01
Host OS version: Ubuntu 16.04 LTS
UbuntuKVM Guest OS version: Ubuntu 14.04.4 LTS
HTX version: 394
Processor: 00UL865 * 2
Memory: SK hynix 16GB 2Rx4 PC4-2133P * 16
Summary of Issue

Two UbuntuKVM guests are each configured with 8 processors, 64 GB of
memory, 1 disk of 128 GB, 1 network interface, and 1 GPU (pass-through'd
from the Host OS's K80).

The two guests are each put into a Create/Destroy loop, with HTX running
on each of the guests (NOT HOST) in between its creation and
destruction. The mdt.bu profile is used, and the processors, memory, and
the GPU are put under load. The HTX session lasts 9 minutes.

While this is running, the amount of available memory (free memory) in
the Host OS will slowly decrease, and this can continue until the point
wherein there's no more free memory for the Host OS to do anything,
including creating the two VM guests. It seems to be that after every
cycle, a small portion of the memory that was allocated to the VM guest
does not get released back to the Host OS, and eventually, this can and
will add up to take up all the available memory in the Host OS.

At some point, the VM guest(s) might get disconnected and will display
the following error:

error: Disconnected from qemu:///system due to I/O error

error: One or more references were leaked after disconnect from the
hypervisor

Then, when the Host OS tries to start the VM guest again, the following
error shows up:

error: Failed to create domain from guest2_trusty.xml
error: internal error: early end of file from monitor, possible problem: 
Unexpected error in spapr_alloc_htab() at 
/build/qemu-c3ZrbA/qemu-2.5+dfsg/hw/ppc/spapr.c:1030:
2016-05-23T16:18:16.871549Z qemu-system-ppc64: Failed to allocate HTAB of 
requested size, try with smaller maxmem

The Host OS syslog, as seen HERE, also contains quite some errors.
To just list a few:

May 13 20:27:44 191-136 kernel: [36827.151228] alloc_contig_range: [3fb800, 
3fd8f8) PFNs busy
May 13 20:27:44 191-136 kernel: [36827.151291] alloc_contig_range: [3fb800, 
3fd8fc) PFNs busy
May 13 20:27:44 191-136 libvirtd[19263]: *** Error in `/usr/sbin/libvirtd': 
realloc(): invalid next size: 0x01000a780400 ***
May 13 20:27:44 191-136 libvirtd[19263]: === Backtrace: =
May 13 20:27:44 191-136 libvirtd[19263]: 
/lib/powerpc64le-linux-gnu/libc.so.6(+0x8720c)[0x3fffaf6a720c]
May 13 20:27:44 191-136 libvirtd[19263]: 
/lib/powerpc64le-linux-gnu/libc.so.6(+0x96f70)[0x3fffaf6b6f70]
May 13 20:27:44 191-136 libvirtd[19263]: 
/lib/powerpc64le-linux-gnu/libc.so.6(realloc+0x16c)[0x3fffaf6b87fc]
May 13 20:27:44 191-136 libvirtd[19263]: 
/usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virReallocN+0x68)[0x3fffaf90ccc8]
May 13 20:27:44 191-136 libvirtd[19263]: 
/usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so(+0x8ef6c)[0x3fff9346ef6c]
May 13 20:27:44 191-136 libvirtd[19263]: 
/usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so(+0xa826c)[0x3fff9348826c]
May 13 20:27:44 191-136 libvirtd[19263]: 
/usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virEventPollRunOnce+0x8b4)[0x3fffaf9332b4]
May 13 20:27:44 191-136 libvirtd[19263]: 
/usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virEventRunDefaultImpl+0x54)[0x3fffaf931334]
May 13 20:27:44 191-136 libvirtd[19263]: 
/usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virNetDaemonRun+0x1f0)[0x3fffafad2f70]
May 13 20:27:44 191-136 libvirtd[19263]: 
/usr/sbin/libvirtd(+0x15d74)[0x52e45d74]
May 13 20:27:44 191-136 libvirtd[19263]: 
/lib/powerpc64le-linux-gnu/libc.so.6(+0x2319c)[0x3fffaf64319c]
May 13 20:27:44 191-136 libvirtd[19263]: 
/lib/powerpc64le-linux-gnu/libc.so.6(__libc_start_main+0xb8)[0x3fffaf6433b8]
May 13 20:27:44 191-136 libvirtd[19263]: === Memory map: 
May 13 20:27:44 191-136 libvirtd[19263]: 52e3-52eb r-xp  
08:02 65540510 /usr/sbin/libvirtd
May 13 20:27:44 191-136 libvirtd[19263]: 52ec-52ed r--p 0008 
08:02 65540510 /usr/sbin/libvirtd
May 13 20:27:44 191-136 libvirtd[19263]: 52ed-52ee rw-p 0009 
08:02 65540510 /usr/sbin/libvirtd
May 13 20:27:44 191-136 libvirtd[19263]: 1000a73-1000a83 rw-p 
 00:00 0 [heap]
May 13 20:27:44 191-136 libvirtd[19263]: 3fff6000-3fff6003 rw-p 
 00:00 0
May 13 20:27:44 191-136 libvirtd[19263]: 3fff6003-3fff6400 ---p 
 00:00 0
May 13 20:50:33 191-136 kernel: [38196.502926] audit: type=1400 
audit(1463197833.497:4025): apparmor="DENIED" operation="open" 
profile="libvirt-d3ade785-c1c1-4519-b123-9d28704c2ad4" 
name="/sys/devices/pci0003:00/0003:00:00.0/0003:01:00.0/0003:02:08.0/0003:03:00.0/devspec"
 pid=24887 comm="qemu-system-ppc" requested_mask="r" denied_mask="r" fsuid=110 

[Kernel-packages] [Bug 1632360] [NEW] bluetooth stop working after resume from sleep/suspend

[mosquito]

Public bug reported:

After resume from suspend/sleep bluetooth seems to stop working.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-42-generic 4.4.0-42.62
ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
Uname: Linux 4.4.0-42-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jemand 1434 F pulseaudio
CurrentDesktop: Unity
Date: Tue Oct 11 16:56:46 2016
HibernationDevice: RESUME=UUID=ec4eb0b5-dad4-42e7-b5d0-c575bfe8781a
InstallationDate: Installed on 2016-10-11 (0 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO INVALID
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-42-generic.efi.signed 
root=UUID=f1eaf3e6-0728-453a-abeb-46cdc4cc1626 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-42-generic N/A
 linux-backports-modules-4.4.0-42-generic  N/A
 linux-firmware1.157.4
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/08/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: ACCN19WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: IdeaPad S20-30
dmi.board.vendor: LENOVO
dmi.board.version: 12345678WIN8 PRO
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad S20-30
dmi.modalias: 
dmi:bvnLENOVO:bvrACCN19WW:bd10/08/2014:svnLENOVO:pnINVALID:pvrLenovoIdeaPadS20-30:rvnLENOVO:rnIdeaPadS20-30:rvr12345678WIN8PRO:cvnLENOVO:ct10:cvrLenovoIdeaPadS20-30:
dmi.product.name: INVALID
dmi.product.version: Lenovo IdeaPad S20-30
dmi.sys.vendor: LENOVO

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


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

Title:
  bluetooth stop working after resume from sleep/suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend/sleep bluetooth seems to stop working.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-42-generic 4.4.0-42.62
  ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
  Uname: Linux 4.4.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jemand 1434 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Oct 11 16:56:46 2016
  HibernationDevice: RESUME=UUID=ec4eb0b5-dad4-42e7-b5d0-c575bfe8781a
  InstallationDate: Installed on 2016-10-11 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO INVALID
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-42-generic.efi.signed 
root=UUID=f1eaf3e6-0728-453a-abeb-46cdc4cc1626 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-42-generic N/A
   linux-backports-modules-4.4.0-42-generic  N/A
   linux-firmware1.157.4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/08/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: ACCN19WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: IdeaPad S20-30
  dmi.board.vendor: LENOVO
  dmi.board.version: 12345678WIN8 PRO
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S20-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrACCN19WW:bd10/08/2014:svnLENOVO:pnINVALID:pvrLenovoIdeaPadS20-30:rvnLENOVO:rnIdeaPadS20-30:rvr12345678WIN8PRO:cvnLENOVO:ct10:cvrLenovoIdeaPadS20-30:
  dmi.product.name: INVALID
  dmi.product.version: Lenovo IdeaPad S20-30
  dmi.sys.vendor: LENOVO

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

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

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

[Brad Figg]

This change was made by a bot.

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

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

Title:
  bluetooth stop working after resume from sleep/suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend/sleep bluetooth seems to stop working.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-42-generic 4.4.0-42.62
  ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
  Uname: Linux 4.4.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jemand 1434 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Oct 11 16:56:46 2016
  HibernationDevice: RESUME=UUID=ec4eb0b5-dad4-42e7-b5d0-c575bfe8781a
  InstallationDate: Installed on 2016-10-11 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO INVALID
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-42-generic.efi.signed 
root=UUID=f1eaf3e6-0728-453a-abeb-46cdc4cc1626 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-42-generic N/A
   linux-backports-modules-4.4.0-42-generic  N/A
   linux-firmware1.157.4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/08/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: ACCN19WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: IdeaPad S20-30
  dmi.board.vendor: LENOVO
  dmi.board.version: 12345678WIN8 PRO
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S20-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrACCN19WW:bd10/08/2014:svnLENOVO:pnINVALID:pvrLenovoIdeaPadS20-30:rvnLENOVO:rnIdeaPadS20-30:rvr12345678WIN8PRO:cvnLENOVO:ct10:cvrLenovoIdeaPadS20-30:
  dmi.product.name: INVALID
  dmi.product.version: Lenovo IdeaPad S20-30
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1618782] Re: wifi stops functioning briefly after connecting to network

[Kgorbi]

After upgrading the BIOS firmware on Lenovo W530 to version 2.66
(newest):

# Testing Ubuntu Kernel-4.4.0
After system start:
 - rarely works
 - often re-connecting to WiFi suffices
 - less oftne WLAN PM must be disabled
After wake-up:
 - rarely works
 - often re-connecting to WiFi suffices
 - less oftne WLAN PM must be disabled

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

Title:
  wifi stops functioning briefly after connecting to network

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Lenovo W530, after upgrade from 14.04 to 16.04:
  Although wifi card is still connected to the wifi-router (network manager 
states so), no user traffic is passing through after a few seconds from 
authentication.

  Workaround: 'iwconfig wlan0 power off' executed after the connection
  becomes unusable brings it back to operation.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-36-generic 4.4.0-36.55
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kgar   4992 F pulseaudio
   /dev/snd/controlC0:  kgar   4992 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Aug 31 10:48:01 2016
  HibernationDevice: RESUME=UUID=eeaac5ff-7cb9-4674-963c-2641065f84b6
  InstallationDate: Installed on 2014-01-17 (956 days ago)
  InstallationMedia: It
  MachineType: LENOVO 244759G
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=20cbb6d9-2c69-427b-a27f-09a0787436b9 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-08-13 (18 days ago)
  dmi.bios.date: 02/27/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ET92WW (2.52 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 244759G
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 Pro DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5ET92WW(2.52):bd02/27/2013:svnLENOVO:pn244759G:pvrThinkPadW530:rvnLENOVO:rn244759G:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 244759G
  dmi.product.version: ThinkPad W530
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1614987] Re: cannot connect BT speaker to laptop running unity8

[Dave Morley]

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

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

Title:
  cannot connect BT speaker to laptop running unity8

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Laptop running unity8::

  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Codename:   yakkety

  HW: Toshiba portege Z30-A12T | Intel i5+intel graphics | SSD hd

  BT speaker: Avrha Strauss P/N:11BQALT01

  Steps to reproduce:

  1º On your laptop running unity8, go to System settings>Bluetooth and turn it 
on
  2º Turn on your BT speaker as well(on this model just press the BT button a 
few seconds for being discoverable)
  3º After a few seconds BT speaker should be found by the laptop, but it 
doesn't

  Current result: Laptop can discover and pair with Utouch and android
  devices, but is not seeing the BT speaker

  Expected result: Laptop should discover and be able to pair BT
  speakers

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

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

Re: [Kernel-packages] [Bug 1629204] Re: Autofs parameter substitution broken in kernel 4.4.0-38 and 4.4.0-40

[Seth Forshee]

On Tue, Oct 11, 2016 at 01:14:53PM -, Robert Euhus wrote:
> I am very disappointed that another broken "stable" kernel (4.4.0-42.62)
> was just released for xenial, even though this problem and the fix have
> been known for about a week!
> 
> Why?
> 
> What can I do to speed up the progress?
> 
> I really need a working kernel on xenial! Or do I have to build it
> myself and roll it out to our systems?

There will be a new kernel in -proposed in the next day or two which
will include the fix.

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

Title:
  Autofs parameter substitution broken in kernel 4.4.0-38 and 4.4.0-40

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 Released

Bug description:
  SRU Justification

  Impact: ca6fe3344554 "fs: Call d_automount with the filesystems creds"
  causes a regression in the requester uid and gid passed to userspace
  during automount, as the current credentials during automount are
  those of root and not the user who requested the mount.

  Fix: Use current->real_cred instead of current->cred for getting the
  requester's uid and gid.

  Regression Potential: Minimal. current->cred and current->real_cred
  are the same except when credentials are overridden, thus
  current->real_cred contains the same credentials that autofs had been
  using prior to the change which overrides the credentials during
  automount.

  ---

  Hello,

  I have run into a bug relating autofs's parameter substitution (e.g.
  UID, GID, etc) with kernel versions 4.4.0-38 and proposed 4.4.0-40.
  Kernel version 4.4.0-28 does things correctly but testing intermediate
  kernel versions is hard due to earlier bugs related with fs's.
  Incorrect parameter substitution makes CIFS mounting with variable
  credentials impossible.

  Wat was expected:
  $UID in autofs map are substituted by the uid of the user that starts the 
auto-mounting process.

  What actually happens:
  Root's uid (0) is substituted instead.

  This ill parameter substitution likely caused by recent fixes
  resolving permissions problems for nfs/cifs mounts and dfs referrals
  (#1626112 and #1612135). And possibly the fix 'fs: Call d_automount
  with the filesystems creds' but that is a wild guess.

  Furthermore; playing with the force_standard_program_map_env settings
  in autofs.conf and prefixing variables with 'AUTOFS_' does not solve
  anything.

  Yours kindly,

  Chris

   Additional info 

    lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04
  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  run1   3015 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=f2a2c5c4-2f41-482a-80b4-968a87131214
  InstallationDate: Installed on 2016-09-19 (10 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp0s8no wireless extensions.

   enp0s3no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-40-generic root=/dev/sda1 
ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-40.60-generic 4.4.21
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-40-generic N/A
   linux-backports-modules-4.4.0-40-generic  N/A
   linux-firmware1.157.3
  RfKill:

  Tags:  xenial
  Uname: Linux 4.4.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1628976] Re: Ubuntu 16.10: Oops panic in move_page_tables/page_remove_rmap after running memory_stress_ng.

[bugproxy]

** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin1610

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

Title:
  Ubuntu 16.10: Oops panic in move_page_tables/page_remove_rmap after
  running memory_stress_ng.

Status in linux package in Ubuntu:
  New

Bug description:
  FYI Canonical:

  We have been seeing various page handling issues during memory stress
  in the 4.8 kernels.  The following is the most recent issue resulting
  in system panics on this host after the 4.8.0-17 update:

  == Comment: #17 - PAVITHRA R. PRAKASH - 2016-09-28 06:26:21 ==
  Hi,

  Tried running on 4.8.0-17-generic kernel. Getting below call trace and
  system crashes. Attaching logs.

  [ 2959.364333] Unable to handle kernel paging request for data at address 
0xf2fe4020
  [ 2959.364345] Faulting instruction address: 0xc02bb2a0
  [ 2959.364356] Oops: Kernel access of bad area, sig: 11 [#1]
  [ 2959.364364] SMP NR_CPUS=2048 NUMA pSeries
  [ 2959.364377] Modules linked in: rpadlpar_io rpaphp dccp_diag dccp tcp_diag 
udp_diag inet_diag unix_diag af_packet_diag netlink_diag bnx2x mdio libcrc32c 
pseries_rng vmx_crypto binfmt_misc ip_tables x_tables autofs4 ibmvscsi 
crc32c_vpmsum
  [ 2959.364441] CPU: 13 PID: 108 Comm: oom_reaper Not tainted 4.8.0-17-generic 
#19-Ubuntu
  [ 2959.364452] task: c004fbdf9c00 task.stack: c004fbe0
  [ 2959.364461] NIP: c02bb2a0 LR: c0300618 CTR: 
c009ca40
  [ 2959.364471] REGS: c004fbe036e0 TRAP: 0300   Not tainted  
(4.8.0-17-generic)
  [ 2959.364481] MSR: 80010280b033   
CR: 24028844  XER: 200c
  [ 2959.364526] CFAR: c0300614 DAR: f2fe4020 DSISR: 4000 
SOFTE: 1 
 GPR00: c0300618 c004fbe03960 c14e5e00 
f2fe4000 
 GPR04: 0001 0800  
c1665e00 
 GPR08: f900a196 0001 02fe4000 
 
 GPR12: 8800 c1b37500 0008 
c1ffe7ff 
 GPR16: c004f62a55f0 3fff9a00 3fff9900 
 
 GPR20: c004fbe03b80 c004e0713800 8e017c3302c0 
0001 
 GPR24: c000fb3614c8 c000fce9d990 c000fce9d6e4 
96a100f90b40 
 GPR28: f2fe4000 c000fb3614c8 0001 
f2fe4000 
  [ 2959.364673] NIP [c02bb2a0] page_remove_rmap+0x30/0x4b0
  [ 2959.364685] LR [c0300618] zap_huge_pmd+0xf8/0x480
  [ 2959.364692] Call Trace:
  [ 2959.364699] [c004fbe03960] [c004fbe039a0] 0xc004fbe039a0 
(unreliable)
  [ 2959.364714] [c004fbe039a0] [c0300618] zap_huge_pmd+0xf8/0x480
  [ 2959.364726] [c004fbe039f0] [c02a68d8] 
unmap_page_range+0xd08/0xee0
  [ 2959.364740] [c004fbe03b20] [c025c474] 
__oom_reap_task+0x204/0x2c0
  [ 2959.364752] [c004fbe03c80] [c025cda8] oom_reaper+0x1e8/0x300
  [ 2959.364765] [c004fbe03d80] [c00fd120] kthread+0x110/0x130
  [ 2959.364778] [c004fbe03e30] [c00098f0] 
ret_from_kernel_thread+0x5c/0x6c
  [ 2959.364788] Instruction dump:
  [ 2959.364796] 3c4c0123 3842ab90 7c0802a6 fba1ffe8 fbc1fff0 fbe1fff8 f8010010 
f821ffc1 
  [ 2959.364821] 7c7f1b78 7c9e2378 6000 6000  71480001 
392a 40820008 
  [ 2959.364871] ---[ end trace 178b14c6911b70dc ]---
  [ 2959.372762] 
  [ 2959.372798] Sending IPI to other CPUs
  [ 2959.373834] IPI complete

  Thanks,
  Pavithra

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

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

[Kernel-packages] [Bug 1406014] Re: Bluetooth: can't load firmware, may not work correctly

[Yota]

I've been affected by this exact bug for over a year and have not been able to 
use bluetooth. 
dmesg:

[3.353578] Bluetooth: Core ver 2.21
[3.353593] Bluetooth: HCI device and connection manager initialized
[3.353596] Bluetooth: HCI socket layer initialized
[3.353598] Bluetooth: L2CAP socket layer initialized
[3.353605] Bluetooth: SCO socket layer initialized
[3.363019] Bluetooth: hci0: BCM: chip id 63
[3.379130] Bluetooth: hci0: BCM20702A
[3.380049] Bluetooth: hci0: BCM20702A1 (001.002.014) build 
[3.386656] bluetooth hci0: Direct firmware load for 
brcm/BCM20702A1-0a5c-216f.hcd failed with error -2
[3.386659] Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0a5c-216f.hcd not 
found
[4.637831] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[4.637834] Bluetooth: BNEP filters: protocol multicast
[4.637839] Bluetooth: BNEP socket layer initialized

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

Title:
  Bluetooth: can't load firmware, may not work correctly

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Bluetooth does not work. The tray icon appears, but none of the functionality 
is available. Probable cause:
  The firmware for Bus 001 Device 003: ID 0a5c:21e6 Broadcom Corp. BCM20702 
Bluetooth 4.0 [ThinkPad] does not load. The message in dmesg is "Bluetooth: 
can't load firmware, may not work correctly". The problem appeared after 
upgrading from the previous LTS version (12.04?).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-44-generic 3.13.0-44.73
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  weber  2408 F pulseaudio
    weber  2744 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat Dec 27 22:58:37 2014
  HibernationDevice: RESUME=UUID=4dd72213-9a42-4532-aa22-2ccc72d46062
  InstallationDate: Installed on 2012-07-21 (889 days ago)
  InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120423)
  MachineType: LENOVO 2320CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic 
root=UUID=a58cd4c1-52b5-4b88-b5a8-3bf530c20c4a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-44-generic N/A
   linux-backports-modules-3.13.0-44-generic  N/A
   linux-firmware 1.127.11
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-12-26 (1 days ago)
  dmi.bios.date: 05/24/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET31WW (1.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2320CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET31WW(1.11):bd05/24/2012:svnLENOVO:pn2320CTO:pvrThinkPadX230:rvnLENOVO:rn2320CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2320CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1614987] Re: cannot connect BT speaker to laptop running unity8

[Victor gonzalez]

Right now, after installing latest Yakkety ISO 20161008, discover BT
devices is not working at all.

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

Title:
  cannot connect BT speaker to laptop running unity8

Status in bluez package in Ubuntu:
  New

Bug description:
  Laptop running unity8::

  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Codename:   yakkety

  HW: Toshiba portege Z30-A12T | Intel i5+intel graphics | SSD hd

  BT speaker: Avrha Strauss P/N:11BQALT01

  Steps to reproduce:

  1º On your laptop running unity8, go to System settings>Bluetooth and turn it 
on
  2º Turn on your BT speaker as well(on this model just press the BT button a 
few seconds for being discoverable)
  3º After a few seconds BT speaker should be found by the laptop, but it 
doesn't

  Current result: Laptop can discover and pair with Utouch and android
  devices, but is not seeing the BT speaker

  Expected result: Laptop should discover and be able to pair BT
  speakers

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

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

[Kernel-packages] [Bug 1604995] Re: NVMe stress test fails after 12 hours on Ubuntu 16.04

[Tim Gardner]

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

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

Title:
  NVMe stress test fails after 12 hours on Ubuntu 16.04

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 Released

Bug description:
   State: Open by: mdate on 21 June 2016 10:22:28 

  Stress testing for perfromance is being done in preparation for the the 
Tencent PoC Sort Competition using the attached per scripts.  The system either 
hangs, or the NVMe goes offline after 12 hours or so.
  The nvme drives are set up in a RAID 0 config.  The script is run like this:

  ./perf_nvme_fio2.sh nvme_jobfile_raid0_huawei

  mdate (md...@pezman.austin.ibm.com) added native attachment 
/opt/IBM/WebSphere/AppServer/profiles/cqweb/temp/ausratsrv5Node01/server1/TeamEAR/cqweb.war/perf_nvme_fio2.sh
 on 2016-06-21 10:22:28
  mdate (md...@pezman.austin.ibm.com) added native attachment 
/opt/IBM/WebSphere/AppServer/profiles/cqweb/temp/ausratsrv5Node01/server1/TeamEAR/cqweb.war/nvme_jobfile_raid0_huawei
 on 2016-06-21 10:22:28

  == Comment: #48 - Gabriel Krisman Bertazi  - 2016-07-18 12:33:13 ==
  Hi, 

  We need to apply the following patch to the Ubuntu kernel to prevent
  wrongly identification of ATARI partitions, as mentioned in the commit
  log.

  It still didn't make to Linus tree, but Jens Axboe already approved it
  on linux-block.

  https://git.kernel.org/cgit/linux/kernel/git/axboe/linux-
  block.git/commit/?h=for-4.8/core

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

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

[Kernel-packages] [Bug 1626269] Sosreport after reboot

[bugproxy]

Default Comment by Bridge

** Attachment added: "Sosreport after reboot"
   
https://bugs.launchpad.net/bugs/1626269/+attachment/4759337/+files/sosreport-ubuntu-20160921004751.tar.xz

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

Title:
  Ubuntu 16.10: kdump is not working in 4.8 kernel.

Status in makedumpfile package in Ubuntu:
  Confirmed
Status in makedumpfile source package in Trusty:
  New
Status in makedumpfile source package in Xenial:
  New
Status in makedumpfile source package in Yakkety:
  Confirmed

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH - 2016-09-21 00:50:22 ==
  ---Problem Description---

  Ubuntu 16.10: kdump is not working in 4.8 kernel.

  ---Steps to Reproduce---

  1) apt-get install linux-crashdump
  2) increase crashdump size:
  sudo vim /etc/default/grub.d/kexec-tools.cfg

  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel
  =2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M"

  3) sudo update-grub ; reboot the machine
  4) sudo sed -i 's/USE_KDUMP=0/USE_KDUMP=1/g' /etc/default/kdump-tools
  5) kdump-config show
  6) echo "c" > /proc/sysrq-trigger

  Logs
  

  root@ubuntu:/home/ubuntu# uname -a
  Linux ubuntu 4.8.0-11-generic #12-Ubuntu SMP Sat Sep 17 19:58:16 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

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

  kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.8.0-11-generic 
root=UUID=7ea3831b-f4c3-4f69-8f77-79aefcda70e3 ro splash quiet irqpoll 
nr_cpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  root@ubuntu:/home/ubuntu# cd
  root@ubuntu:~# echo "c" > /proc/sysrq-trigger
  [   50.733424] sysrq: SysRq : Trigger a crash
  [   50.733437] Unable to handle kernel paging request for data at address 
0x
  [   50.733441] Faulting instruction address: 0xc05af3f4
  [   50.733444] Oops: Kernel access of bad area, sig: 11 [#1]
  [   50.733446] SMP NR_CPUS=2048 NUMA pSeries
  [   50.733450] Modules linked in: rpadlpar_io rpaphp dccp_diag dccp tcp_diag 
udp_diag inet_diag unix_diag af_packet_diag netlink_diag pseries_rng sg 
rng_core binfmt_misc ghash_generic gf128mul vmx_crypto ip_tables x_tables 
autofs4 ext4 crc16 jbd2 fscrypto mbcache sr_mod cdrom sd_mod bnx2x ibmvscsi 
ibmveth scsi_transport_srp ptp pps_core mdio libcrc32c crc32c_generic 
crc32c_vpmsum
  [   50.733477] CPU: 2 PID: 1517 Comm: bash Not tainted 4.8.0-11-generic 
#12-Ubuntu
  [   50.733480] task: c004f7906880 task.stack: c004f7898000
  [   50.733482] NIP: c05af3f4 LR: c05b04d8 CTR: 
c05af3c0
  [   50.733485] REGS: c004f789b990 TRAP: 0300   Not tainted  
(4.8.0-11-generic)
  [   50.733488] MSR: 80009033   CR: 28242422  
XER: 0001
  [   50.733496] CFAR: c00087d0 DAR:  DSISR: 4200 
SOFTE: 1 
  GPR00: c05b04d8 c004f789bc10 c0f46700 0063 
  GPR04: c005ef78a9b8 c005ef79f7d8 c0063fe82300 5970 
  GPR08: 0007 0001  0001 
  GPR12: c05af3c0 c7b31200  2200 
  GPR16: 10170dc8 0100111c0538 10140f58 100c7570 
  GPR20:  1017dd58 10153618 1017b608 
  GPR24: 310b9624 0001 c0e9fd40 0004 
  GPR28: c0ea0100 0063 c0e528e8  
  [   50.733536] NIP [c05af3f4] sysrq_handle_crash+0x34/0x50
  [   50.733539] LR [c05b04d8] __handle_sysrq+0xe8/0x280
  [   50.733541] Call Trace:
  [   50.733544] [c004f789bc10] [c09ff9e8] 0xc09ff9e8 
(unreliable)
  [   50.733548] [c004f789bc30] [c05b04d8] __handle_sysrq+0xe8/0x280
  [   50.733552] [c004f789bcd0] [c05b0c88] 
write_sysrq_trigger+0x78/0xa0
  [   50.733556] [c004f789bd00] [c03a9a90] proc_reg_write+0xb0/0x110
  [   50.733560] [c004f789bd50] [c030c27c] __vfs_write+0x6c/0xe0
  [   50.733564] [c004f789bd90] [c030d784] vfs_write+0xd4/0x240
  [   50.733567] [c004f789bde0] [c030f49c] SyS_write+0x6c/0x110
  [   50.733571] [c004f789be30] [c00095e0] system_call+0x38/0x108
  [   50.733574] Instruction dump:
  [   50.733576] 38427340 7c0802a6 f8010010 f821ffe1 6000 6000 3d220019 
3949cde0 
  [   50.733582] 3921 912a 7c0004ac 3940 <992a000

[Kernel-packages] [Bug 1629204] Re: Autofs parameter substitution broken in kernel 4.4.0-38 and 4.4.0-40

[Robert Euhus]

I am very disappointed that another broken "stable" kernel (4.4.0-42.62)
was just released for xenial, even though this problem and the fix have
been known for about a week!

Why?

What can I do to speed up the progress?

I really need a working kernel on xenial! Or do I have to build it
myself and roll it out to our systems?

Thanks,
Robert.

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

Title:
  Autofs parameter substitution broken in kernel 4.4.0-38 and 4.4.0-40

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 Released

Bug description:
  SRU Justification

  Impact: ca6fe3344554 "fs: Call d_automount with the filesystems creds"
  causes a regression in the requester uid and gid passed to userspace
  during automount, as the current credentials during automount are
  those of root and not the user who requested the mount.

  Fix: Use current->real_cred instead of current->cred for getting the
  requester's uid and gid.

  Regression Potential: Minimal. current->cred and current->real_cred
  are the same except when credentials are overridden, thus
  current->real_cred contains the same credentials that autofs had been
  using prior to the change which overrides the credentials during
  automount.

  ---

  Hello,

  I have run into a bug relating autofs's parameter substitution (e.g.
  UID, GID, etc) with kernel versions 4.4.0-38 and proposed 4.4.0-40.
  Kernel version 4.4.0-28 does things correctly but testing intermediate
  kernel versions is hard due to earlier bugs related with fs's.
  Incorrect parameter substitution makes CIFS mounting with variable
  credentials impossible.

  Wat was expected:
  $UID in autofs map are substituted by the uid of the user that starts the 
auto-mounting process.

  What actually happens:
  Root's uid (0) is substituted instead.

  This ill parameter substitution likely caused by recent fixes
  resolving permissions problems for nfs/cifs mounts and dfs referrals
  (#1626112 and #1612135). And possibly the fix 'fs: Call d_automount
  with the filesystems creds' but that is a wild guess.

  Furthermore; playing with the force_standard_program_map_env settings
  in autofs.conf and prefixing variables with 'AUTOFS_' does not solve
  anything.

  Yours kindly,

  Chris

   Additional info 

    lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04
  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  run1   3015 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=f2a2c5c4-2f41-482a-80b4-968a87131214
  InstallationDate: Installed on 2016-09-19 (10 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp0s8no wireless extensions.

   enp0s3no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-40-generic root=/dev/sda1 
ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-40.60-generic 4.4.21
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-40-generic N/A
   linux-backports-modules-4.4.0-40-generic  N/A
   linux-firmware1.157.3
  RfKill:

  Tags:  xenial
  Uname: Linux 4.4.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1602737] Re: PCI RoCE Interface could not be renamed from default name with link file

[Frank Heimes]

** Changed in: ubuntu-z-systems
   Status: Fix Committed => Fix Released

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

Title:
  PCI RoCE Interface could not be renamed from default name with link
  file

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  New
Status in linux source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  New
Status in linux source package in Yakkety:
  Fix Released
Status in systemd source package in Yakkety:
  New

Bug description:
  == Comment: #0 - Helmut Grauer  - 2016-07-13 
09:05:27 ==
  Try to rename PCI Roce Interface with .link file

  root@s35lp02:/etc/systemd/network# cat 10-net.link
  [Match]
  Path=pci-:00:00.0*
  MACAddress=82:01:14:07:85:70

  [Link]
  Name=hug0
  root@s35lp02:/etc/systemd/network#

  do  a reboot and journalctl show old interface name for RoCE PCI
  Interface

  Jul 13 14:39:40 s35lp02 kernel: mlx4_en 0001:00:00.0: Activating port:1
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: Using 32 TX 
rings
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: Using 4 RX 
rings
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1:   frag:0 - 
size:1522 prefix:0 stride:1536
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: Initializing 
port
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en 0001:00:00.0: Activating port:2
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: Using 32 TX 
rings
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: Using 4 RX 
rings
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2:   frag:0 - 
size:1522 prefix:0 stride:1536
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: Initializing 
port
  Jul 13 14:39:40 s35lp02 kernel: mlx4_core :00:00.0 enp0s0: renamed from 
eth0
  Jul 13 14:39:40 s35lp02 kernel: mlx4_core :00:00.0 enp0s0d1: renamed from 
eth1
  Jul 13 14:39:40 s35lp02 kernel: mlx4_core 0001:00:00.0 enP1p0s0d1: renamed 
from eth3
  Jul 13 14:39:40 s35lp02 kernel: mlx4_core 0001:00:00.0 enP1p0s0: renamed from 
eth2
  Jul 13 14:39:40 s35lp02 kernel: EXT4-fs (dasda1): mounting ext3 file system 
using the ext4 subsystem
  Jul 13 14:39:40 s35lp02 kernel: EXT4-fs (dasda1): mounted filesystem with 
ordered data mode. Opts: (null)

  udevadm test show the following output

  oot@s35lp02:/etc/systemd/network# udevadm test /class/net/enp0s0
  calling: test
  version 229
  This program is for debugging only, it does not run any program
  specified by a RUN key. It may show incorrect results, because
  some values may be different, or not available at a simulation run.

  === trie on-disk ===
  tool version:  229
  file size: 6841701 bytes
  header size 80 bytes
  strings1755245 bytes
  nodes  5086376 bytes
  Load module index
  timestamp of '/etc/systemd/network' changed
  Skipping overridden file: /usr/lib/systemd/network/99-default.link.
  Skipping overridden file: /usr/lib/systemd/network/10-net.link.
  Skipping overridden file: /lib/systemd/network/99-default.link.
  Skipping overridden file: /lib/systemd/network/10-net.link.
  Parsed configuration file /etc/systemd/network/99-default.link
  Parsed configuration file /lib/systemd/network/90-mac-for-usb.link
  Parsed configuration file /etc/systemd/network/11-net.link
  Parsed configuration file /etc/systemd/network/10-net.link
  Created link configuration context.
  timestamp of '/etc/udev/rules.d' changed
  Reading rules file: /lib/udev/rules.d/40-vm-hotadd.rules
  Reading rules file: /lib/udev/rules.d/40-z90crypt.rules
  Reading rules file: /etc/udev/rules.d/41-cio-ignore.rules
  Reading rules file: /etc/udev/rules.d/41-dasd-eckd-0.0.af06.rules
  Reading rules file: /etc/udev/rules.d/41-dasd-eckd-0.0.af07.rules
  Reading rules file: /etc/udev/rules.d/41-generic-ccw-0.0.0009.rules
  Reading rules file: /etc/udev/rules.d/41-qeth-0.0.b100.rules
  Reading rules file: /etc/udev/rules.d/41-qeth-0.0.f500.rules
  Reading rules file: /lib/udev/rules.d/50-firmware.rules
  Reading rules file: /lib/udev/rules.d/50-udev-default.rules
  Reading rules file: /lib/udev/rules.d/55-dm.rules
  Reading rules file: /lib/udev/rules.d/55-scsi-sg3_id.rules
  Reading rules file: /lib/udev/rules.d/56-dm-mpath-lvm.rules
  Reading rules file: /lib/udev/rules.d/56-lvm.rules
  Reading rules file: /lib/udev/rules.d/58-scsi-sg3_symlink.rules
  Reading rules file: /lib/udev/rules.d/59-dasd.rules
  Reading rules file: /lib/udev/rules.d/60-block.rules
  Reading rules file: /lib/udev/rules.d/60-cdrom_id.rules
  Reading rules file: /lib/udev/rules.d/60-crda.rules
  Reading rules file: /lib/udev/rules.d/60-drm.rules
  Reading rules file: /lib/udev/rules.d/60-evdev.rules
  Reading rules file: /lib/udev/rules.d/60-gnup

[Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM

[Grief]

I have exactly the same issue with kernel 4.8.1 taken from here:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8.1/

Isn't this bug supposed to be fixed already?

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

Title:
  4.8.0 kernels do not complete boot process on VM

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux-raspi2 package in Ubuntu:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in linux-raspi2 source package in Yakkety:
  Fix Released

Bug description:
  On my native amd64 box, 4.8.0-15 works just fine, but on my VMWare
  Fusion 8.5 system, none of the 4.8.0 kernels complete the boot
  process.  I tried 4.8.0-15 from yakkety and 4.8.0-16 from yakkety-
  proposed.

  Currently  I am seeing the last message in my console at boot up as:

  [ OK ] Started Bluetooth service

  and then... it just sits there.

  Through the use of snapshots, restores, and package bisects, I've
  definitively narrowed it to linux-generic linux-image-generic and
  linux-headers-generic.

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

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

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

[bugproxy]

--- Comment From helmut.gra...@de.ibm.com 2016-10-11 06:20 EDT---
Hi,
retest done with Kernel 4.4.0-38-generic
apt-get install linux-image-extra-4.4.0-38-generic

Linux s35lp02 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:47:15 UTC
2016 s390x s390x s390x GNU/Linux

Renaming of PCI devices with

root@s35lp02:/etc/udev/rules.d# cat 70-persistent-net.rules
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="mlx4_core", ATTR{dev_id}=="0x0", 
KERNELS==":00:00.0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

works fine
root@s35lp02:/etc/udev/rules.d# cat /etc/network/interfaces

allow-hotplug eth0
iface eth0 inet static
address 10.100.60.18
netmask 255.255.0.0

toot@s35lp02:/etc/udev/rules.d# ifconfig eth0
eth0  Link encap:Ethernet  HWaddr 82:01:14:07:85:70
inet addr:10.100.60.18  Bcast:10.100.255.255  Mask:255.255.0.0
inet6 addr: fe80::8001:14ff:fe07:8570/64 Scope:Link
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:742 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:66596 (66.5 KB)  TX bytes:964 (964.0 B)

Renaming works OK
Greetings Helmut

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

Title:
  PCI RoCE Interface could not be renamed from default name with link
  file

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  New
Status in linux source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  New
Status in linux source package in Yakkety:
  Fix Released
Status in systemd source package in Yakkety:
  New

Bug description:
  == Comment: #0 - Helmut Grauer  - 2016-07-13 
09:05:27 ==
  Try to rename PCI Roce Interface with .link file

  root@s35lp02:/etc/systemd/network# cat 10-net.link
  [Match]
  Path=pci-:00:00.0*
  MACAddress=82:01:14:07:85:70

  [Link]
  Name=hug0
  root@s35lp02:/etc/systemd/network#

  do  a reboot and journalctl show old interface name for RoCE PCI
  Interface

  Jul 13 14:39:40 s35lp02 kernel: mlx4_en 0001:00:00.0: Activating port:1
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: Using 32 TX 
rings
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: Using 4 RX 
rings
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1:   frag:0 - 
size:1522 prefix:0 stride:1536
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: Initializing 
port
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en 0001:00:00.0: Activating port:2
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: Using 32 TX 
rings
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: Using 4 RX 
rings
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2:   frag:0 - 
size:1522 prefix:0 stride:1536
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: Initializing 
port
  Jul 13 14:39:40 s35lp02 kernel: mlx4_core :00:00.0 enp0s0: renamed from 
eth0
  Jul 13 14:39:40 s35lp02 kernel: mlx4_core :00:00.0 enp0s0d1: renamed from 
eth1
  Jul 13 14:39:40 s35lp02 kernel: mlx4_core 0001:00:00.0 enP1p0s0d1: renamed 
from eth3
  Jul 13 14:39:40 s35lp02 kernel: mlx4_core 0001:00:00.0 enP1p0s0: renamed from 
eth2
  Jul 13 14:39:40 s35lp02 kernel: EXT4-fs (dasda1): mounting ext3 file system 
using the ext4 subsystem
  Jul 13 14:39:40 s35lp02 kernel: EXT4-fs (dasda1): mounted filesystem with 
ordered data mode. Opts: (null)

  udevadm test show the following output

  oot@s35lp02:/etc/systemd/network# udevadm test /class/net/enp0s0
  calling: test
  version 229
  This program is for debugging only, it does not run any program
  specified by a RUN key. It may show incorrect results, because
  some values may be different, or not available at a simulation run.

  === trie on-disk ===
  tool version:  229
  file size: 6841701 bytes
  header size 80 bytes
  strings1755245 bytes
  nodes  5086376 bytes
  Load module index
  timestamp of '/etc/systemd/network' changed
  Skipping overridden file: /usr/lib/systemd/network/99-default.link.
  Skipping overridden file: /usr/lib/systemd/network/10-net.link.
  Skipping overridden file: /lib/systemd/network/99-default.link.
  Skipping overridden file: /lib/systemd/network/10-net.link.
  Parsed configuration file /etc/systemd/network/99-default.link
  Parsed configuration file /lib/systemd/network/90-mac-for-usb.link
  Parsed configuration file /etc/systemd/network/11-net.link
  Parsed configuration file /etc/systemd/network/10-net.link
  Created link configuration context.
  timestamp of '/etc/udev/rules.d' changed
  Reading rules file: /lib/udev/rules.d/40-vm-hotadd.rules
  Reading rules file: /lib/udev/rules.d/40-z90crypt.rules
  Reading rules file: /etc/udev/rules.d/41-cio-ignore.rules
  Reading rules file: /etc/udev/rules.d/4

[Kernel-packages] [Bug 1623804] Re: headset microphone is not recognized in headset-jack

[brandon211]

This behaviour persists with kernel 4.8.1

** Tags added: kernel-bug-exists-upstream

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

Title:
  headset microphone is not recognized in headset-jack

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 16.04 on a Lenovo ThinkPad T450s. This notebook has a
  combined headphones/mic "headset"-jack as used by pretty much every
  smartphone nowadays.

  I have a Plantronics-Headset HW251/A - SupraPlus Monaural and a 4-pin
  3,5mm jack cable, made for use with PCs.

  When connecting the headset to the notebook, I get audio but the mic
  is not recognized.

  In contrast, when I boot Windows 7 on the same machine, the headset 
(including mic) works fine.
  Moreover, the headset works fine connected to an Apple MacBook Air.

  In contrast, I also have an Apple Earphones-Headset which came with an
  iPhone, this also works with the ThinkPad under Ubuntu.

  By saying "not recognized", I mean that in the audio settings of Ubuntu, when 
plugging in the Plantronics headset, no audio input "microphone" comes up and 
the internal mic of the notebook is still used. 
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  buerger2021 F pulseaudio
   /dev/snd/controlC1:  buerger2021 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=21eeaf61-c437-45dc-80e3-e581eb6f795c
  InstallationDate: Installed on 2015-09-15 (366 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20BX000XGE
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=93fc15f9-4090-40ff-a3ac-a642833f1da2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-36-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (146 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 05/25/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET60WW (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BX000XGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET60WW(1.24):bd05/25/2016:svnLENOVO:pn20BX000XGE:pvrThinkPadT450s:rvnLENOVO:rn20BX000XGE:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BX000XGE
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1592442] Re: Ubuntu 16.04 Xenial hard crashing on ACER E3-11-P0D8

[Christopher M. Penalver]

Saif Taifur Anwar, could you please capture the crash following
https://wiki.ubuntu.com/DebuggingSystemCrash ?

Also, is there a crash file in /var/crash?

** Tags removed: bios-outdated-1.16
** Tags added: latest-bios-1.16

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

Title:
  Ubuntu 16.04 Xenial hard crashing on ACER E3-11-P0D8

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  About a month ago I installed the latest Ubuntu 16.04 Xenial on my
  ACER E3-11-P0D8 laptop. Since then, it randomly freeze up while I
  work. It generally takes 10-20 mins to do that.

  Out of frustration, I started to change the kernel. It seems that
  every >4.0 kernel is freezing up my system. Now i am stable at 3.19.8
  from here: http://kernel.ubuntu.com/~kernel-ppa/mainline/

  Please note: When using old kernel ( 3.19.8 ) i have no crash. But
  when i use the latest one, it freeze up and i can not use anything (
  no kernel panic, no terminal, nothing, keyboard mouse doesn't work ).

  The freeze happens very randomly. It can take 5 mins or hours after
  working. And it takes me to switch off the laptop and start it again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-24-generic 4.4.0-24.43
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  saif   1431 F pulseaudio
  Date: Tue Jun 14 20:39:57 2016
  HibernationDevice: RESUME=UUID=f2e69a50-3159-4db7-be6b-10bc5072fc65
  InstallationDate: Installed on 2016-05-14 (31 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b48a Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire E3-112
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed 
root=UUID=665e2c47-366b-4bc0-9142-8ae6796d1b72 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-24-generic N/A
   linux-backports-modules-4.4.0-24-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: R2
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd08/20/2014:svnAcer:pnAspireE3-112:pvrV1.10:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E3-112
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1604313] Re: Ubuntu 16.04: system freezes instead of suspend after undocking

[brandon211]

With the latest mainline kernel, 4.8.1, the problem is not present.

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

Title:
  Ubuntu 16.04: system freezes instead of suspend after undocking

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using a Lenovo ThinkPad T450s. When the system was docked and then 
undocked, suspend won't work. Instead, the screen goes black, the system 
freezes and the fan runs on high speed.
  This problem persists with the (as of today) most recent kernel 
4.4.0-31-generic #50.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  buerger3534 F pulseaudio
   /dev/snd/pcmC1D0p:   buerger3534 F...m pulseaudio
   /dev/snd/controlC1:  buerger3534 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jul 19 11:13:41 2016
  HibernationDevice: RESUME=UUID=21eeaf61-c437-45dc-80e3-e581eb6f795c
  InstallationDate: Installed on 2015-09-15 (307 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20BX000XGE
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=93fc15f9-4090-40ff-a3ac-a642833f1da2 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (87 days ago)
  dmi.bios.date: 03/23/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET57WW (1.22 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BX000XGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET57WW(1.22):bd03/23/2016:svnLENOVO:pn20BX000XGE:pvrThinkPadT450s:rvnLENOVO:rn20BX000XGE:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BX000XGE
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

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

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