[Kernel-packages] [Bug 1655745] Re: linux: 3.19.0-80.88 -proposed tracker

[Brad Figg]

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

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

** Changed in: kernel-sru-workflow/promote-to-updates
   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/1655745

Title:
  linux: 3.19.0-80.88 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Confirmed
Status in Kernel SRU Workflow promote-to-updates series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
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-80.88 upload package. This bug
  will contain status and testing results related to that upload.

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

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

[bugproxy]

--- Comment From hbath...@in.ibm.com 2017-01-24 01:54 EDT---
(In reply to comment #25)
> Hello bugproxy, or anyone else affected,
>
> Accepted crash into xenial-proposed. The package will build now and be
> available at https://launchpad.net/ubuntu/+source/crash/7.1.4-1ubuntu4.1 in
> a few hours, and then in the -proposed repository.
>
> Please help us by testing this new package.  See
> https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
> enable and use -proposed.  Your feedback will aid us getting this update out
> to other Ubuntu users.
>
> If this package fixes the bug for you, please add a comment to this bug,
> mentioning the version of the package you tested, and change the tag from
> verification-needed to verification-done. If it does not fix the bug for
> you, please add a comment stating that, and change the tag to
> verification-failed.  In either case, details of your testing will help us
> make a better decision.
>
> Further information regarding the verification process can be found at
> https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
> advance!
>
> @louis -- if you could add the SRU template with some appropriate tests for
> old and new kernels.  Ta.

Is makedumpfile tool also updated with the missing patches?

Thanks
Hari

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

Title:
  ISST-LTE:pVM:roselp4:ubuntu 16.04.2: vmcore cannot be analysed by
  crash

Status in crash package in Ubuntu:
  Confirmed
Status in makedumpfile package in Ubuntu:
  Confirmed
Status in crash source package in Xenial:
  Fix Committed
Status in makedumpfile source package in Xenial:
  Confirmed

Bug description:
  [SRU justification]
  This fix is required to make the crash tool usable. It does also improve 
makedumpfile filtering of pages.

  [Impact]
  Kernel crashes cannot be analysed with the crash tool.

  [Fix]
  Cherry-pick upstream commits fixing those issues.

  [Test Case]
  Running crash tool on a kernel crash file will display something like :

  # crash -s usr/lib/debug/boot/vmlinux-4.8.0-34-generic
  crash: read error: kernel virtual address: 81e29ff0  type: 
"pv_init_ops"
  crash: this kernel may be configured with CONFIG_STRICT_DEVMEM, which
 renders /dev/mem unusable as a live memory source.
  crash: trying /proc/kcore as an alternative to /dev/mem

  crash: seek error: kernel virtual address: 81e29ff0  type: 
"pv_init_ops"
  crash: seek error: kernel virtual address: 82166130  type: 
"shadow_timekeeper xtime_sec"
  crash: seek error: kernel virtual address: 81e0d304  type: 
"init_uts_ns"
  crash: usr/lib/debug/boot/vmlinux-4.8.0-34-generic and 
/var/crash/201701191308/dump.201701191308 do not match!

  With the fix, the crash command will work as expected

  [Regression]
  None expected as those modifications are part of the Zesty and upstream 
version.

  [Original description of the problem]
  vmcore captured by kdump cannot be opened with crash:

  % sudo crash -d1 /usr/lib/debug/boot/vmlinux-4.8.0-34-generic 
/var/crash/201612282137/dump.201612282137
  ... ...
  base kernel version: 0.8.0
  linux_banner:
  
  crash: /usr/lib/debug/boot/vmlinux-4 and 
/var/crash/201612282137/dump.201612282137 do not match!

  Usage:

    crash [OPTION]... NAMELIST MEMORY-IMAGE[@ADDRESS] (dumpfile form)
    crash [OPTION]... [NAMELIST]  (live system form)

  Enter "crash -h" for details.

  Looks like the 'linux_banner' cannot be understood by crash.

  And when the vmcore was dumping, this message being showed:

  [  729.609196] kdump-tools[5192]: The kernel version is not supported.
  [  729.609447] kdump-tools[5192]: The makedumpfile operation may be 
incomplete.
  ---uname output---
  Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = lpar

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   1. config kdump
  2. trigger kdump
  3. analyse vmcore with crash

  Userspace tool common name: crash/makedumpfile

  The userspace tool has the following bit modes: 64-bit

  Userspace rpm: makedumpfile 1.5.9-5ubuntu0.3/crash 7.1.4-1ubuntu4

  Userspace tool obtained from project website:  na

  *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com:
  -Post a private note with access information to the machine that the bug is 
occuring on.
  -Attach ltrace and strace of userspace application.

  xtime timespec.tv_sec: 586481e8: Wed Dec 28 21:24:24 2016
  utsname:
   sysname: Linux
  nodename: boblp1
   release: 4.8.0-32-generic
   version: #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 2016
   machine: ppc64le
    domainname: (none)
  base kernel version: 4.8.0
  verify_namelist:
  dumpfile /proc/version:
  Linux version 4.8.0-32-generic 

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

[bugproxy]

--- Comment From hbath...@in.ibm.com 2017-01-24 01:38 EDT---
(In reply to comment #7)
> Leann, could you please get someone to pull in commit referenced in this bug
> to fix the oops ?

The commit I mentioned fixes Oops for /proc/kcore read but the issue
still remains for /proc/vmcore read. Will try and post a fix soon..

Thanks
Hari

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

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

Status in makedumpfile package in Ubuntu:
  New

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

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

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

  # kdump-config propagate

  # kdump-config load

  # kdump-config show

  2. Trigger crash

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

[Kernel-packages] [Bug 1655625] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: vmcore cannot be analysed by crash

[bugproxy]

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

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

Title:
  ISST-LTE:pVM:roselp4:ubuntu 16.04.2: vmcore cannot be analysed by
  crash

Status in crash package in Ubuntu:
  Confirmed
Status in makedumpfile package in Ubuntu:
  Confirmed
Status in crash source package in Xenial:
  Fix Committed
Status in makedumpfile source package in Xenial:
  Confirmed

Bug description:
  [SRU justification]
  This fix is required to make the crash tool usable. It does also improve 
makedumpfile filtering of pages.

  [Impact]
  Kernel crashes cannot be analysed with the crash tool.

  [Fix]
  Cherry-pick upstream commits fixing those issues.

  [Test Case]
  Running crash tool on a kernel crash file will display something like :

  # crash -s usr/lib/debug/boot/vmlinux-4.8.0-34-generic
  crash: read error: kernel virtual address: 81e29ff0  type: 
"pv_init_ops"
  crash: this kernel may be configured with CONFIG_STRICT_DEVMEM, which
 renders /dev/mem unusable as a live memory source.
  crash: trying /proc/kcore as an alternative to /dev/mem

  crash: seek error: kernel virtual address: 81e29ff0  type: 
"pv_init_ops"
  crash: seek error: kernel virtual address: 82166130  type: 
"shadow_timekeeper xtime_sec"
  crash: seek error: kernel virtual address: 81e0d304  type: 
"init_uts_ns"
  crash: usr/lib/debug/boot/vmlinux-4.8.0-34-generic and 
/var/crash/201701191308/dump.201701191308 do not match!

  With the fix, the crash command will work as expected

  [Regression]
  None expected as those modifications are part of the Zesty and upstream 
version.

  [Original description of the problem]
  vmcore captured by kdump cannot be opened with crash:

  % sudo crash -d1 /usr/lib/debug/boot/vmlinux-4.8.0-34-generic 
/var/crash/201612282137/dump.201612282137
  ... ...
  base kernel version: 0.8.0
  linux_banner:
  
  crash: /usr/lib/debug/boot/vmlinux-4 and 
/var/crash/201612282137/dump.201612282137 do not match!

  Usage:

    crash [OPTION]... NAMELIST MEMORY-IMAGE[@ADDRESS] (dumpfile form)
    crash [OPTION]... [NAMELIST]  (live system form)

  Enter "crash -h" for details.

  Looks like the 'linux_banner' cannot be understood by crash.

  And when the vmcore was dumping, this message being showed:

  [  729.609196] kdump-tools[5192]: The kernel version is not supported.
  [  729.609447] kdump-tools[5192]: The makedumpfile operation may be 
incomplete.
  ---uname output---
  Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = lpar

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   1. config kdump
  2. trigger kdump
  3. analyse vmcore with crash

  Userspace tool common name: crash/makedumpfile

  The userspace tool has the following bit modes: 64-bit

  Userspace rpm: makedumpfile 1.5.9-5ubuntu0.3/crash 7.1.4-1ubuntu4

  Userspace tool obtained from project website:  na

  *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com:
  -Post a private note with access information to the machine that the bug is 
occuring on.
  -Attach ltrace and strace of userspace application.

  xtime timespec.tv_sec: 586481e8: Wed Dec 28 21:24:24 2016
  utsname:
   sysname: Linux
  nodename: boblp1
   release: 4.8.0-32-generic
   version: #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 2016
   machine: ppc64le
    domainname: (none)
  base kernel version: 4.8.0
  verify_namelist:
  dumpfile /proc/version:
  Linux version 4.8.0-32-generic (buildd@bos01-ppc64el-001) (gcc version 5.4.0 
20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #34~16.04.1-Ubuntu SMP Tue Dec 
13 17:01:57 UTC 2016 (Ubuntu 4.8.0-32.34~16.04.1-generic 4.8.11)
  /usr/lib/debug/boot/vmlinux-4.8.0-32-generic:
  Linux version 4.8.0-32-generic (buildd@bos01-ppc64el-001) (gcc version 5.4.0 
20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #34~16.04.1-Ubuntu SMP Tue Dec 
13 17:01:57 UTC 2016 (Ubuntu 4.8.0-32.34~16.04.1-generic 4.8.11)

  hypervisor: (undetermined)
  crash: per_cpu_symbol_search(per_cpu__tvec_bases): NULL
  ppc64_vmemmap_init: vmemmap base: f000

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

  root@boblp1:/usr/lib/debug/boot# uname -a
  Linux boblp1 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
  root@boblp1:/usr/lib/debug/boot#

  1. Missing v4.8 support related patches in crash tool

     commit 098cdab16dfa6a85e9dad2cad604dee14ee15f66
     Author: Dave Anderson 
     Date:   Fri Feb 12 14:32:53 2016 -0500

  Fix for the changes made to the kernel module structure introduced by
  this kernel commit for Linux 4.5 and 

[Kernel-packages] [Bug 1655625] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: vmcore cannot be analysed by crash

[bugproxy]

** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin16042

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

Title:
  ISST-LTE:pVM:roselp4:ubuntu 16.04.2: vmcore cannot be analysed by
  crash

Status in crash package in Ubuntu:
  Confirmed
Status in makedumpfile package in Ubuntu:
  Confirmed
Status in crash source package in Xenial:
  Fix Committed
Status in makedumpfile source package in Xenial:
  Confirmed

Bug description:
  [SRU justification]
  This fix is required to make the crash tool usable. It does also improve 
makedumpfile filtering of pages.

  [Impact]
  Kernel crashes cannot be analysed with the crash tool.

  [Fix]
  Cherry-pick upstream commits fixing those issues.

  [Test Case]
  Running crash tool on a kernel crash file will display something like :

  # crash -s usr/lib/debug/boot/vmlinux-4.8.0-34-generic
  crash: read error: kernel virtual address: 81e29ff0  type: 
"pv_init_ops"
  crash: this kernel may be configured with CONFIG_STRICT_DEVMEM, which
 renders /dev/mem unusable as a live memory source.
  crash: trying /proc/kcore as an alternative to /dev/mem

  crash: seek error: kernel virtual address: 81e29ff0  type: 
"pv_init_ops"
  crash: seek error: kernel virtual address: 82166130  type: 
"shadow_timekeeper xtime_sec"
  crash: seek error: kernel virtual address: 81e0d304  type: 
"init_uts_ns"
  crash: usr/lib/debug/boot/vmlinux-4.8.0-34-generic and 
/var/crash/201701191308/dump.201701191308 do not match!

  With the fix, the crash command will work as expected

  [Regression]
  None expected as those modifications are part of the Zesty and upstream 
version.

  [Original description of the problem]
  vmcore captured by kdump cannot be opened with crash:

  % sudo crash -d1 /usr/lib/debug/boot/vmlinux-4.8.0-34-generic 
/var/crash/201612282137/dump.201612282137
  ... ...
  base kernel version: 0.8.0
  linux_banner:
  
  crash: /usr/lib/debug/boot/vmlinux-4 and 
/var/crash/201612282137/dump.201612282137 do not match!

  Usage:

    crash [OPTION]... NAMELIST MEMORY-IMAGE[@ADDRESS] (dumpfile form)
    crash [OPTION]... [NAMELIST]  (live system form)

  Enter "crash -h" for details.

  Looks like the 'linux_banner' cannot be understood by crash.

  And when the vmcore was dumping, this message being showed:

  [  729.609196] kdump-tools[5192]: The kernel version is not supported.
  [  729.609447] kdump-tools[5192]: The makedumpfile operation may be 
incomplete.
  ---uname output---
  Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = lpar

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   1. config kdump
  2. trigger kdump
  3. analyse vmcore with crash

  Userspace tool common name: crash/makedumpfile

  The userspace tool has the following bit modes: 64-bit

  Userspace rpm: makedumpfile 1.5.9-5ubuntu0.3/crash 7.1.4-1ubuntu4

  Userspace tool obtained from project website:  na

  *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com:
  -Post a private note with access information to the machine that the bug is 
occuring on.
  -Attach ltrace and strace of userspace application.

  xtime timespec.tv_sec: 586481e8: Wed Dec 28 21:24:24 2016
  utsname:
   sysname: Linux
  nodename: boblp1
   release: 4.8.0-32-generic
   version: #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 2016
   machine: ppc64le
    domainname: (none)
  base kernel version: 4.8.0
  verify_namelist:
  dumpfile /proc/version:
  Linux version 4.8.0-32-generic (buildd@bos01-ppc64el-001) (gcc version 5.4.0 
20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #34~16.04.1-Ubuntu SMP Tue Dec 
13 17:01:57 UTC 2016 (Ubuntu 4.8.0-32.34~16.04.1-generic 4.8.11)
  /usr/lib/debug/boot/vmlinux-4.8.0-32-generic:
  Linux version 4.8.0-32-generic (buildd@bos01-ppc64el-001) (gcc version 5.4.0 
20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #34~16.04.1-Ubuntu SMP Tue Dec 
13 17:01:57 UTC 2016 (Ubuntu 4.8.0-32.34~16.04.1-generic 4.8.11)

  hypervisor: (undetermined)
  crash: per_cpu_symbol_search(per_cpu__tvec_bases): NULL
  ppc64_vmemmap_init: vmemmap base: f000

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

  root@boblp1:/usr/lib/debug/boot# uname -a
  Linux boblp1 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
  root@boblp1:/usr/lib/debug/boot#

  1. Missing v4.8 support related patches in crash tool

     commit 098cdab16dfa6a85e9dad2cad604dee14ee15f66
     Author: Dave Anderson 
     Date:   Fri Feb 12 14:32:53 2016 -0500

  Fix for the changes made to the kernel module structure introduced by
  this kernel commit for Linux 

[Kernel-packages] [Bug 1251065] Re: HP Mini 1000 fails to resume from suspend

[Bug Watch Updater]

** Changed in: linux
   Status: Incomplete => Fix Released

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

Title:
  HP Mini 1000 fails to resume from suspend

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Booting various kernels including the mainline 3.12 kernel, HP Mini
  1000 does not resume from suspend. Problem seems to have begun
  following update to 13.10, including kernels 3.9, 3.10, 3.11.

  Ran steps on DebuggingKernelSuspend wiki page at
  https://wiki.ubuntu.com/DebugginKernelSuspend#A.22resume-
  trace.22_debugging_procedure_for_finding_buggy_drivers.

  Attached: dmesg.txt
  --- 
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  DistroRelease: Ubuntu 13.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-11-12 (1 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  MarkForUpload: True
  NonfreeKernelModules: wl
  Package: linux (not installed)
  Tags:  saucy
  Uname: Linux 3.12.0-031200-generic i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Kernel-packages] [Bug 1657112] kernel02 (s390x.zVM) - tests ran: 64, failed: 0

[Brad Figg]

tests ran:  64, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/kernel02__4.8.0-36.38__2017-01-24_04-31-00/results-index.html

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

Title:
  linux: 4.8.0-36.38 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1657112] kernel02 (s390x.zVM) - tests ran: 141, failed: 28

[Brad Figg]

tests ran: 141, failed: 28;
  
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/kernel02__4.8.0-36.38__2017-01-24_04-01-00/results-index.html

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

Title:
  linux: 4.8.0-36.38 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59

[Mike Williams]

Cascardo: we've tried your test kernel, and it looks good - we've seen
no OOM problems.

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

Title:
  "Out of memory" errors after upgrade to 4.4.0-59

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

Bug description:
  I recently replaced some Xenial servers, and started experiencing "Out
  of memory" problems with the default kernel.

  We bake Amazon AMIs based on an official Ubuntu-provided image (ami-
  e6b58e85, in ap-southeast-2, from https://cloud-
  images.ubuntu.com/locator/ec2/).  Previous versions of our AMI
  included "4.4.0-57-generic", but the latest version picked up
  "4.4.0-59-generic" as part of a "dist-upgrade".

  Instances booted using the new AMI have been using more memory, and
  experiencing OOM issues - sometimes during boot, and sometimes a while
  afterwards.  An example from the system log is:

  [  130.113411] cloud-init[1560]: Cloud-init v. 0.7.8 running 'modules:final' 
at Wed, 11 Jan 2017 22:07:53 +. Up 29.28 seconds.
  [  130.124219] cloud-init[1560]: Cloud-init v. 0.7.8 finished at Wed, 11 Jan 
2017 22:09:35 +. Datasource DataSourceEc2.  Up 130.09 seconds
  [29871.137128] Out of memory: Kill process 2920 (ruby) score 107 or sacrifice 
child
  [29871.140816] Killed process 2920 (ruby) total-vm:675048kB, 
anon-rss:51184kB, file-rss:2164kB
  [29871.449209] Out of memory: Kill process 3257 (splunkd) score 97 or 
sacrifice child
  [29871.453282] Killed process 3258 (splunkd) total-vm:66272kB, 
anon-rss:6676kB, file-rss:0kB
  [29871.677910] Out of memory: Kill process 2647 (fluentd) score 51 or 
sacrifice child
  [29871.681872] Killed process 2647 (fluentd) total-vm:117944kB, 
anon-rss:23956kB, file-rss:1356kB

  I have a hunch that this may be related to the fix for
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647400,
  introduced in linux (4.4.0-58.79).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: User Name 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 06:29 seq
   crw-rw 1 root audio 116, 33 Jan 12 06:29 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jan 12 06:38:45 2017
  Ec2AMI: ami-0f93966c
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-southeast-2a
  Ec2InstanceType: t2.nano
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=fb0fef08-f3c5-40bf-9776-f7ba00fe72be ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2016
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd12/09/2016:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

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

[Kernel-packages] [Bug 1399064] Re: bridges cannot have a mtu > 1500 by themselves

[Ken Sharp]

LXC displays similar behavious in Xenial. The "solution" was to set the
MTUs for all the slave interfaces, and all the interfaces within the
guests, then finally set the bridge MTU, otherwise it will simply
refuse. Worked fine.

Haven't yet looked into the configs to see if I can do this permanently.

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

Title:
  bridges cannot have a mtu > 1500 by themselves

Status in linux package in Ubuntu:
  Triaged

Bug description:
  A linux bridge always adopts the smallest MTU of the enslaved devices.
  When no device are enslaved, it defaults to a MTU of 1500 and refuses
  to use a larger one. This is problematic when using bridges enslaving
  only virtual NICs (vnetX) like it's common with KVM guests.

  Steps to reproduce the problem

  1) sudo ip link add br-test0 type bridge # create an empty bridge
  2) sudo ip link set br-test0 mtu 9000# attempt to set MTU > 1500
  3) ip link show dev br-test0 # confirm MTU

  Here, 2) returns "RTNETLINK answers: Invalid argument". One
  (cumbersome) way around this is:

  4) sudo modprobe dummy
  5) sudo ip link set dummy0 mtu 9000 master br-test0

  Then the bridge's MTU can be changed from anywhere to 9000.

  This bug is especially annoying for the virtualization case because
  the KVM's tap driver will by default adopt the bridge's MTU on startup
  making it impossible (without the workaround) to use a large MTU on
  the guest VMs.

  Additional information:

  $ lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  $ apt-cache policy linux-image-3.13.0-41-generic iproute2
  linux-image-3.13.0-41-generic:
    Installed: 3.13.0-41.70
    Candidate: 3.13.0-41.70
    Version table:
   *** 3.13.0-41.70 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
  iproute2:
    Installed: 3.12.0-2
    Candidate: 3.12.0-2
    Version table:
   *** 3.12.0-2 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-41-generic 3.13.0-41.70
  ProcVersionSignature: Ubuntu 3.13.0-41.70-generic 3.13.11.11
  Uname: Linux 3.13.0-41-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  simon  4594 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg: dmesg: klogctl failed: Operation not permitted
  Date: Wed Dec  3 23:02:25 2014
  HibernationDevice: RESUME=UUID=8e7a3220-158f-413b-81b2-55b236bb1f3f
  InstallationDate: Installed on 2014-01-26 (311 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124)
  MachineType: LENOVO 2516CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-41-generic 
root=/dev/mapper/crypt-root ro quiet splash 
cryptopts=target=crypt,source=/dev/sda1,lvm=crypt-root possible_cpus=4 
nmi_watchdog=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-41-generic N/A
   linux-backports-modules-3.13.0-41-generic  N/A
   linux-firmware 1.127.10
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET85WW (1.45 )
  dmi.board.name: 2516CTO
  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:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2516CTO
  dmi.product.version: ThinkPad T410
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1399064] Re: bridges cannot have a mtu > 1500 by themselves

[Ken Sharp]

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

Title:
  bridges cannot have a mtu > 1500 by themselves

Status in linux package in Ubuntu:
  Triaged

Bug description:
  A linux bridge always adopts the smallest MTU of the enslaved devices.
  When no device are enslaved, it defaults to a MTU of 1500 and refuses
  to use a larger one. This is problematic when using bridges enslaving
  only virtual NICs (vnetX) like it's common with KVM guests.

  Steps to reproduce the problem

  1) sudo ip link add br-test0 type bridge # create an empty bridge
  2) sudo ip link set br-test0 mtu 9000# attempt to set MTU > 1500
  3) ip link show dev br-test0 # confirm MTU

  Here, 2) returns "RTNETLINK answers: Invalid argument". One
  (cumbersome) way around this is:

  4) sudo modprobe dummy
  5) sudo ip link set dummy0 mtu 9000 master br-test0

  Then the bridge's MTU can be changed from anywhere to 9000.

  This bug is especially annoying for the virtualization case because
  the KVM's tap driver will by default adopt the bridge's MTU on startup
  making it impossible (without the workaround) to use a large MTU on
  the guest VMs.

  Additional information:

  $ lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  $ apt-cache policy linux-image-3.13.0-41-generic iproute2
  linux-image-3.13.0-41-generic:
    Installed: 3.13.0-41.70
    Candidate: 3.13.0-41.70
    Version table:
   *** 3.13.0-41.70 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
  iproute2:
    Installed: 3.12.0-2
    Candidate: 3.12.0-2
    Version table:
   *** 3.12.0-2 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-41-generic 3.13.0-41.70
  ProcVersionSignature: Ubuntu 3.13.0-41.70-generic 3.13.11.11
  Uname: Linux 3.13.0-41-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  simon  4594 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg: dmesg: klogctl failed: Operation not permitted
  Date: Wed Dec  3 23:02:25 2014
  HibernationDevice: RESUME=UUID=8e7a3220-158f-413b-81b2-55b236bb1f3f
  InstallationDate: Installed on 2014-01-26 (311 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124)
  MachineType: LENOVO 2516CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-41-generic 
root=/dev/mapper/crypt-root ro quiet splash 
cryptopts=target=crypt,source=/dev/sda1,lvm=crypt-root possible_cpus=4 
nmi_watchdog=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-41-generic N/A
   linux-backports-modules-3.13.0-41-generic  N/A
   linux-firmware 1.127.10
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET85WW (1.45 )
  dmi.board.name: 2516CTO
  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:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2516CTO
  dmi.product.version: ThinkPad T410
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1658491] Re: VLAN SR-IOV regression for IXGBE driver

[Dan Streetman]

The commit that fixes this, f60439bc21e3337429838e477903214f5bd8277f, is
already in yakkety and later; this is needed only for Xenial.

Additionally, since the problem commit that this fixes was not included
in 4.4 - it was backported into the Xenial kernel via bug 1536473 - the
commit that fixes this won't come into Xenial via the normal stable
process; it needs to be applied directly.

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

Title:
  VLAN SR-IOV regression for IXGBE driver

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

Bug description:
  
  IXGBE driver, for SR-IOV setups, is misbehaving with VLANs.

  Description from affected user:

  - Create 2 networks (sriov 100 and 102 vlan)

  # neutron net-create --provider:physical_network=PHY0 
--provider:network_type=vlan --provider:segmentation_id=100 PHY0_vlan_100
  # neutron net-create --provider:physical_network=PHY0 
--provider:network_type=vlan --provider:segmentation_id=102 PHY0_vlan_102

  - Create the subnets:

  # neutron subnet-create PHY0_vlan_100 192.168.50.0/24
  # neutron subnet-create PHY0_vlan_102 192.168.60.0/24

  - Create the neutron ports:

  # neutron port-create e450757f-fec6-466e-bb21-a42a2019fe6b --name 
vlan_100_port1 --vnic-type direct
  # neutron port-create 32c468ed-7e1e-4267-bbbf-ec72d33e4454 --name 
vlan_102_port1 --vnic-type direct

  - Boot 2 VMs on 2 different hosts (add only 1 port to each of them +
  ovs dhcp network):

  # nova boot --flavor 789 --image ubuntu --nic 
net-id=1cf2a512-8963-413d-a745-99e758789c2b --nic 
port-id=92cf2867-cc0a-4e0d-aa87-14a345cdd708 102_port1_compute6 --key-name mkey 
--config-drive true --availability-zone nova:compute-0-6.domain.tld --poll
  # nova boot --flavor 789 --image ubutnu --nic 
net-id=1cf2a512-8963-413d-a745-99e758789c2b --nic 
port-id=baec6fd6-933d-4c58-94b6-44c50405d409 100_port1_compute5 --key-name mkey 
--config-drive true --availability-zone nova:compute-0-5.domain.tld --poll

  - After the VMs booted, configure the VFs:

  root@102-port1-compute6:~# ifconfig eth1 192.168.34.6 up
  root@100-port1-compute5:~# ifconfig eth1 192.168.34.5 up

  If I ping each other it works but it shouldn't work because in this
  case both of the VMs's interface (host VF) are in different vlans:

  - Pinging shouldn't work because the VMs interface (host VF) are in
  different VLANs.

  root@compute-0-5:~# ip link show eth6
  8: eth6:  mtu 2140 qdisc mq state UP mode 
DEFAULT group default qlen 1000
  link/ether a0:36:9f:3f:1a:64 brd ff:ff:ff:ff:ff:ff
  vf 5 MAC fa:16:3e:f0:2c:e2, vlan 100, spoof checking on, link-state auto

  root@compute-0-6:~# ip link show eth5
  8: eth5:  mtu 2140 qdisc mq state UP mode 
DEFAULT group default qlen 1000
  link/ether a0:36:9f:3f:20:88 brd ff:ff:ff:ff:ff:ff
  vf 7 MAC fa:16:3e:ce:69:41, vlan 101, spoof checking on, link-state auto 

  But user can ping both VMs.

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

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

[Kernel-packages] [Bug 1658491] Re: VLAN SR-IOV regression for IXGBE driver

[Dan Streetman]

> This issue may be fixed by this upstream commit:
> commit f60439bc21e3337429838e477903214f5bd8277f

I verified it is fixed by that commit, thanks Jay.

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

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

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

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

** Changed in: linux (Ubuntu Zesty)
 Assignee: Dan Streetman (ddstreet) => (unassigned)

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

Title:
  VLAN SR-IOV regression for IXGBE driver

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

Bug description:
  
  IXGBE driver, for SR-IOV setups, is misbehaving with VLANs.

  Description from affected user:

  - Create 2 networks (sriov 100 and 102 vlan)

  # neutron net-create --provider:physical_network=PHY0 
--provider:network_type=vlan --provider:segmentation_id=100 PHY0_vlan_100
  # neutron net-create --provider:physical_network=PHY0 
--provider:network_type=vlan --provider:segmentation_id=102 PHY0_vlan_102

  - Create the subnets:

  # neutron subnet-create PHY0_vlan_100 192.168.50.0/24
  # neutron subnet-create PHY0_vlan_102 192.168.60.0/24

  - Create the neutron ports:

  # neutron port-create e450757f-fec6-466e-bb21-a42a2019fe6b --name 
vlan_100_port1 --vnic-type direct
  # neutron port-create 32c468ed-7e1e-4267-bbbf-ec72d33e4454 --name 
vlan_102_port1 --vnic-type direct

  - Boot 2 VMs on 2 different hosts (add only 1 port to each of them +
  ovs dhcp network):

  # nova boot --flavor 789 --image ubuntu --nic 
net-id=1cf2a512-8963-413d-a745-99e758789c2b --nic 
port-id=92cf2867-cc0a-4e0d-aa87-14a345cdd708 102_port1_compute6 --key-name mkey 
--config-drive true --availability-zone nova:compute-0-6.domain.tld --poll
  # nova boot --flavor 789 --image ubutnu --nic 
net-id=1cf2a512-8963-413d-a745-99e758789c2b --nic 
port-id=baec6fd6-933d-4c58-94b6-44c50405d409 100_port1_compute5 --key-name mkey 
--config-drive true --availability-zone nova:compute-0-5.domain.tld --poll

  - After the VMs booted, configure the VFs:

  root@102-port1-compute6:~# ifconfig eth1 192.168.34.6 up
  root@100-port1-compute5:~# ifconfig eth1 192.168.34.5 up

  If I ping each other it works but it shouldn't work because in this
  case both of the VMs's interface (host VF) are in different vlans:

  - Pinging shouldn't work because the VMs interface (host VF) are in
  different VLANs.

  root@compute-0-5:~# ip link show eth6
  8: eth6:  mtu 2140 qdisc mq state UP mode 
DEFAULT group default qlen 1000
  link/ether a0:36:9f:3f:1a:64 brd ff:ff:ff:ff:ff:ff
  vf 5 MAC fa:16:3e:f0:2c:e2, vlan 100, spoof checking on, link-state auto

  root@compute-0-6:~# ip link show eth5
  8: eth5:  mtu 2140 qdisc mq state UP mode 
DEFAULT group default qlen 1000
  link/ether a0:36:9f:3f:20:88 brd ff:ff:ff:ff:ff:ff
  vf 7 MAC fa:16:3e:ce:69:41, vlan 101, spoof checking on, link-state auto 

  But user can ping both VMs.

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

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

[Kernel-packages] [Bug 1646277] Re: Xenial server 16.04.x will have a black screen after PXE installation

[Leo-Chen]

OS installer via PXE and then update to 4.4-59 kernel ,that still would stop at 
tty7 and I haven't looked into why it doesn't switch straight to a tty1 though 
 update command as:
 sudo apt-get update
 sudo apt-get dist-upgrade

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

Title:
  Xenial server 16.04.x will have a black screen after PXE installation

Status in debian-installer package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed
Status in debian-installer source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  The display will keep black screen after install 16.04.x via PXE(need
  use "Ctrl+Alt+F1" to change to terminal 1, then can see text mode
  screen)

  Quanta team is installing Xenial server using PXE boot.   After the
  installation, the console will show a black screen.   Hitting ctl-
  alt-f1 displays the text mode screen OK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1646277/+subscriptions

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

[Kernel-packages] [Bug 1656618] Re: Any key pressed opens shutdown dialog (Asus X205TA)

[harry]

I found the patch that causes the keyboard to malfunction !:
https://www.spinics.net/lists/linux-gpio/msg18340.html

reverse patching this patch 'solves' the issue (specifically reverse
patching pinctrl-baytrail, reverse patching pinctrl-intel is not really
necessary)

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

Title:
  Any key pressed opens shutdown dialog (Asus X205TA)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After a fresh install of 16.10 on my Asus X205TA, any key pressed on
  the built-in keyboard brings up the shutdown dialog. The system works
  fine with a USB keyboard.

  The installed kernel was 4.8.0-34-generic. Booting with
  4.8.0-22-generic, the keyboard works fine.

  Other users have confirmed the bug in Fedora and Tails 
(https://ubuntuforums.org/showthread.php?t=2254322=13594241#post13594241) and 
in 16.10 MATE 
(https://ubuntuforums.org/showthread.php?t=2254322=13594617#post13594617).
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  EcryptfsInUse: Yes
  Lsusb:
   Bus 001 Device 004: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 003: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 8087:07e6 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X205TA
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=05a20fbf-3084-4535-bae3-bed719df662c ro quiet splash 
intel_max.idle_cstate=1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-22-generic N/A
   linux-backports-modules-4.8.0-22-generic  N/A
   linux-firmware1.161.1
  Tags:  yakkety
  Uname: Linux 4.8.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X205TA.212
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X205TA
  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.:bvrX205TA.212:bd09/04/2015:svnASUSTeKCOMPUTERINC.:pnX205TA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX205TA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X205TA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=94efdbb7-8cb5-442c-8a16-5fbe6fbf4959
  InstallationDate: Installed on 2017-01-16 (0 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb:
   Bus 001 Device 005: ID 413c:2101 Dell Computer Corp. SmartCard Reader 
Keyboard
   Bus 001 Device 004: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 003: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 8087:07e6 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X205TA
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic.efi.signed 
root=/dev/mmcblk1p2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-34-generic N/A
   linux-backports-modules-4.8.0-34-generic  N/A
   linux-firmware1.161.1
  Tags:  yakkety
  Uname: Linux 4.8.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X205TA.212
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X205TA
  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: 

[Kernel-packages] [Bug 1646277] Re: Xenial server 16.04.x will have a black screen after PXE installation

[Leo-Chen]

OS installer via PXE and then update to 4.4-59 kernel ,that still would stop at 
tty7 and doesn't auto changed to tty1
update command as: 
sudo apt-get update
sudo apt-get dist-upgrade

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

Title:
  Xenial server 16.04.x will have a black screen after PXE installation

Status in debian-installer package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed
Status in debian-installer source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  The display will keep black screen after install 16.04.x via PXE(need
  use "Ctrl+Alt+F1" to change to terminal 1, then can see text mode
  screen)

  Quanta team is installing Xenial server using PXE boot.   After the
  installation, the console will show a black screen.   Hitting ctl-
  alt-f1 displays the text mode screen OK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1646277/+subscriptions

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

[Kernel-packages] [Bug 1658345] Re: Touchpad not recognized on Lenovo Ideapad Flex 4 running Ubuntu 16.10

[Keary Parinis]

I tested my laptop with the upstream kernel 4.10 and it does not
recognize my touchpad. Please see attached screen shot I captured during
the install. It indicates an error with the Elantech ps mouse / touchpad
device.

** Attachment added: "dkms_elantech_error.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1658345/+attachment/4808300/+files/dkms_elantech_error.png

** Tags added: kernel-bug-exists-upstream

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

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

Title:
  Touchpad not recognized on Lenovo Ideapad Flex 4 running Ubuntu 16.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 16.10 on my Lenovo Ideapad Flex 4 laptop. Ubuntu does not 
recognize the touchpad (it does recognize the touch screen nicely though). When 
I run xinput -list, I do not see the touchpad. I dual boot with Windows 10, 
which recognizes the touchpad from Elantech. I searched online for days and I 
found Elantech drivers for Ubuntu 14.04, however, I was unable to load older 
versions of Ubuntu on my laptop. Do you expect to support the Elantech touchpad 
in future updates? I attached a screen shot of my xinput -list output. Please 
let me know if you require any additional information. Thank you.
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  keary  2345 F pulseaudio
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=dbfec3b4-a8be-406e-9f39-5258c004c656
  InstallationDate: Installed on 2017-01-18 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:57fc Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0cf3:e500 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80U3
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic.efi.signed 
root=UUID=5be7438e-36fd-4960-a4cd-2371715adfa2 ro quiet splash i8042.kbdreset=1 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-34-generic N/A
   linux-backports-modules-4.8.0-34-generic  N/A
   linux-firmware1.161.1
  Tags:  yakkety
  Uname: Linux 4.8.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 2MCN24WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Sofia-F
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J91204WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad FLEX 4-1130
  dmi.modalias: 
dmi:bvnLENOVO:bvr2MCN24WW:bd11/01/2016:svnLENOVO:pn80U3:pvrLenovoideapadFLEX4-1130:rvnLENOVO:rnSofia-F:rvrSDK0J91204WIN:cvnLENOVO:ct10:cvrLenovoideapadFLEX4-1130:
  dmi.product.name: 80U3
  dmi.product.version: Lenovo ideapad FLEX 4-1130
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1658491] Re: VLAN SR-IOV regression for IXGBE driver

[Jay Vosburgh]

This issue may be fixed by this upstream commit:

commit f60439bc21e3337429838e477903214f5bd8277f
Author: Alexander Duyck 
Date:   Thu Aug 11 14:51:56 2016 -0700

ixgbe: Force VLNCTRL.VFE to be set in all VMDq paths

When I was adding the code for enabling VLAN promiscuous mode with SR-IOV
enabled I had inadvertently left the VLNCTRL.VFE bit unchanged as I has
assumed there was code in another path that was setting it when we enabled
SR-IOV.  This wasn't the case and as a result we were just disabling VLAN
filtering for all the VFs apparently.

Also the previous patches were always clearing CFIEN which was always set
to 0 by the hardware anyway so I am dropping the redundant bit clearing.

Fixes: 16369564915a ("ixgbe: Add support for VLAN promiscuous with SR-IOV")
Signed-off-by: Alexander Duyck 
Tested-by: Andrew Bowers 
Signed-off-by: Jeff Kirsher 

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

Title:
  VLAN SR-IOV regression for IXGBE driver

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

Bug description:
  
  IXGBE driver, for SR-IOV setups, is misbehaving with VLANs.

  Description from affected user:

  - Create 2 networks (sriov 100 and 102 vlan)

  # neutron net-create --provider:physical_network=PHY0 
--provider:network_type=vlan --provider:segmentation_id=100 PHY0_vlan_100
  # neutron net-create --provider:physical_network=PHY0 
--provider:network_type=vlan --provider:segmentation_id=102 PHY0_vlan_102

  - Create the subnets:

  # neutron subnet-create PHY0_vlan_100 192.168.50.0/24
  # neutron subnet-create PHY0_vlan_102 192.168.60.0/24

  - Create the neutron ports:

  # neutron port-create e450757f-fec6-466e-bb21-a42a2019fe6b --name 
vlan_100_port1 --vnic-type direct
  # neutron port-create 32c468ed-7e1e-4267-bbbf-ec72d33e4454 --name 
vlan_102_port1 --vnic-type direct

  - Boot 2 VMs on 2 different hosts (add only 1 port to each of them +
  ovs dhcp network):

  # nova boot --flavor 789 --image ubuntu --nic 
net-id=1cf2a512-8963-413d-a745-99e758789c2b --nic 
port-id=92cf2867-cc0a-4e0d-aa87-14a345cdd708 102_port1_compute6 --key-name mkey 
--config-drive true --availability-zone nova:compute-0-6.domain.tld --poll
  # nova boot --flavor 789 --image ubutnu --nic 
net-id=1cf2a512-8963-413d-a745-99e758789c2b --nic 
port-id=baec6fd6-933d-4c58-94b6-44c50405d409 100_port1_compute5 --key-name mkey 
--config-drive true --availability-zone nova:compute-0-5.domain.tld --poll

  - After the VMs booted, configure the VFs:

  root@102-port1-compute6:~# ifconfig eth1 192.168.34.6 up
  root@100-port1-compute5:~# ifconfig eth1 192.168.34.5 up

  If I ping each other it works but it shouldn't work because in this
  case both of the VMs's interface (host VF) are in different vlans:

  - Pinging shouldn't work because the VMs interface (host VF) are in
  different VLANs.

  root@compute-0-5:~# ip link show eth6
  8: eth6:  mtu 2140 qdisc mq state UP mode 
DEFAULT group default qlen 1000
  link/ether a0:36:9f:3f:1a:64 brd ff:ff:ff:ff:ff:ff
  vf 5 MAC fa:16:3e:f0:2c:e2, vlan 100, spoof checking on, link-state auto

  root@compute-0-6:~# ip link show eth5
  8: eth5:  mtu 2140 qdisc mq state UP mode 
DEFAULT group default qlen 1000
  link/ether a0:36:9f:3f:20:88 brd ff:ff:ff:ff:ff:ff
  vf 7 MAC fa:16:3e:ce:69:41, vlan 101, spoof checking on, link-state auto 

  But user can ping both VMs.

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

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

[Kernel-packages] [Bug 1658839] Re: package linux-firmware 1.127.23 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-firmware 1.127.23 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  The error occurred during the automated software update.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-firmware 1.127.23
  ProcVersionSignature: Ubuntu 4.4.0-42.62~14.04.1-generic 4.4.21
  Uname: Linux 4.4.0-42-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Mon Jan 23 18:05:15 2017
  Dependencies:
   
  DuplicateSignature: package:linux-firmware:1.127.23:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-02-27 (696 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: linux-firmware
  Title: package linux-firmware 1.127.23 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1658839] [NEW] package linux-firmware 1.127.23 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Scott Larson]

Public bug reported:

The error occurred during the automated software update.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-firmware 1.127.23
ProcVersionSignature: Ubuntu 4.4.0-42.62~14.04.1-generic 4.4.21
Uname: Linux 4.4.0-42-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.23
Architecture: amd64
Date: Mon Jan 23 18:05:15 2017
Dependencies:
 
DuplicateSignature: package:linux-firmware:1.127.23:subprocess installed 
post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2015-02-27 (696 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.17
SourcePackage: linux-firmware
Title: package linux-firmware 1.127.23 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package trusty

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

Title:
  package linux-firmware 1.127.23 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  The error occurred during the automated software update.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-firmware 1.127.23
  ProcVersionSignature: Ubuntu 4.4.0-42.62~14.04.1-generic 4.4.21
  Uname: Linux 4.4.0-42-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Mon Jan 23 18:05:15 2017
  Dependencies:
   
  DuplicateSignature: package:linux-firmware:1.127.23:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-02-27 (696 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: linux-firmware
  Title: package linux-firmware 1.127.23 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1658491] Re: VLAN SR-IOV regression for IXGBE driver

[Dan Streetman]

Actually, the commit that introduces the problem is the one before
ad740b71fba84e3d17bc0507d2cb696935cd944b.  The actual offending commit
is:

6c39aa938110688cbbd9ad8628f2dc388926e384 ("ixgbe: Add support for VLAN
promiscuous with SR-IOV")

which is cherry-picked from upstream commit
16369564915a9777217244678ee6160f8f1acac7.

I've built a PPA with both commits reverted:
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1658491

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

Title:
  VLAN SR-IOV regression for IXGBE driver

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

Bug description:
  
  IXGBE driver, for SR-IOV setups, is misbehaving with VLANs.

  Description from affected user:

  - Create 2 networks (sriov 100 and 102 vlan)

  # neutron net-create --provider:physical_network=PHY0 
--provider:network_type=vlan --provider:segmentation_id=100 PHY0_vlan_100
  # neutron net-create --provider:physical_network=PHY0 
--provider:network_type=vlan --provider:segmentation_id=102 PHY0_vlan_102

  - Create the subnets:

  # neutron subnet-create PHY0_vlan_100 192.168.50.0/24
  # neutron subnet-create PHY0_vlan_102 192.168.60.0/24

  - Create the neutron ports:

  # neutron port-create e450757f-fec6-466e-bb21-a42a2019fe6b --name 
vlan_100_port1 --vnic-type direct
  # neutron port-create 32c468ed-7e1e-4267-bbbf-ec72d33e4454 --name 
vlan_102_port1 --vnic-type direct

  - Boot 2 VMs on 2 different hosts (add only 1 port to each of them +
  ovs dhcp network):

  # nova boot --flavor 789 --image ubuntu --nic 
net-id=1cf2a512-8963-413d-a745-99e758789c2b --nic 
port-id=92cf2867-cc0a-4e0d-aa87-14a345cdd708 102_port1_compute6 --key-name mkey 
--config-drive true --availability-zone nova:compute-0-6.domain.tld --poll
  # nova boot --flavor 789 --image ubutnu --nic 
net-id=1cf2a512-8963-413d-a745-99e758789c2b --nic 
port-id=baec6fd6-933d-4c58-94b6-44c50405d409 100_port1_compute5 --key-name mkey 
--config-drive true --availability-zone nova:compute-0-5.domain.tld --poll

  - After the VMs booted, configure the VFs:

  root@102-port1-compute6:~# ifconfig eth1 192.168.34.6 up
  root@100-port1-compute5:~# ifconfig eth1 192.168.34.5 up

  If I ping each other it works but it shouldn't work because in this
  case both of the VMs's interface (host VF) are in different vlans:

  - Pinging shouldn't work because the VMs interface (host VF) are in
  different VLANs.

  root@compute-0-5:~# ip link show eth6
  8: eth6:  mtu 2140 qdisc mq state UP mode 
DEFAULT group default qlen 1000
  link/ether a0:36:9f:3f:1a:64 brd ff:ff:ff:ff:ff:ff
  vf 5 MAC fa:16:3e:f0:2c:e2, vlan 100, spoof checking on, link-state auto

  root@compute-0-6:~# ip link show eth5
  8: eth5:  mtu 2140 qdisc mq state UP mode 
DEFAULT group default qlen 1000
  link/ether a0:36:9f:3f:20:88 brd ff:ff:ff:ff:ff:ff
  vf 7 MAC fa:16:3e:ce:69:41, vlan 101, spoof checking on, link-state auto 

  But user can ping both VMs.

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

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

[Kernel-packages] [Bug 1655280] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: cp: error reading '/proc/vmcore': Bad address when trying to dump vmcore

[Steve Langasek]

** Changed in: linux (Ubuntu)
 Assignee: Steve Langasek (vorlon) => Canonical Kernel Team 
(canonical-kernel-team)

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

Title:
  ISST-LTE:pVM:roselp4:ubuntu 16.04.2: cp: error reading '/proc/vmcore':
  Bad address when trying to dump vmcore

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Ping Tian Han  - 2017-01-09 02:51:00 ==
  ---Problem Description---
  Vmcore cannot be saved when triggering bug 150353 on roselp4:

  Copying data   : [  2.0 %] \/usr/sbin/kdump-config: line 
591:  5502 Bus error   makedumpfile $MAKEDUMP_ARGS $vmcore_file 
$KDUMP_CORETEMP
  [  512.833872] kdump-tools[5450]:  * kdump-tools: makedumpfile failed, 
falling back to 'cp'
  [  573.595449] kdump-tools[5450]: cp: error reading '/proc/vmcore': Bad 
address
  [  573.605717] kdump-tools[5450]:  * kdump-tools: failed to save vmcore in 
/var/crash/201701090223
  [  573.765417] kdump-tools[5450]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/201701090223/dmesg.201701090223
  [  574.285506] kdump-tools[5450]: The kernel version is not supported.
  [  574.285672] kdump-tools[5450]: The makedumpfile operation may be 
incomplete.
  [  574.285767] kdump-tools[5450]: The dmesg log is saved to 
/var/crash/201701090223/dmesg.201701090223.
  [  574.305422] kdump-tools[5450]: makedumpfile Completed.
  [  574.315363] kdump-tools[5450]:  * kdump-tools: saved dmesg content in 
/var/crash/201701090223
  [  574.615688] kdump-tools[5450]: Mon, 09 Jan 2017 02:24:26 -0600
  [  574.705384] kdump-tools[5450]: Rebooting.
   Stopping ifup for ib0...
  [  OK  ] Stopped ifup for ib0.
  [ 1008.579897] reboot: Restarting system
   
  Contact Information = Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com 
   
  ---uname output---
  Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = lpar 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. config kdump on roselp4
  2. try to trigger bug 150353

   
  *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.

  == Comment: #3 - Brahadambal Srinivasan  -
  2017-01-10 02:42:25 ==

  root@roselp4:~# cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinux-4.8.0-34-generic 
root=UUID=0bcf3431-df8b-499c-9a13-33070f242e0c ro splash quiet 
crashkernel=384M-:512M

  root@roselp4:~# dmesg | grep Reser
  [0.00] Reserving 512MB of memory at 128MB for crashkernel (System 
RAM: 21760MB)

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

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

[Kernel-packages] [Bug 1558553] 0001-KEYS-Insert-incompressible-bytes-to-vmlinux-to-reser.patch

[bugproxy]

Default Comment by Bridge

** Attachment added: 
"0001-KEYS-Insert-incompressible-bytes-to-vmlinux-to-reser.patch"
   
https://bugs.launchpad.net/bugs/1558553/+attachment/4808270/+files/0001-KEYS-Insert-incompressible-bytes-to-vmlinux-to-reser.patch

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

Title:
  IMA-appraisal is unusable in Ubuntu 16.04

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

Bug description:
  At some point, the IMA keyring changed from _ima to a trusted .ima
  keyring.   At that point, we couldn't add keys to the IMA keyring.
  Other distros import UEFI keys onto the system keyring.  Another
  method of loading keys on the system keyring is needed, which doesn't
  require the UEFI keys or rebuilding the kernel.

  To resolve this problem, the kernel should be built so that
  certificate memory is reserved and randomized.   Two patches are being
  upstreamed in this open window (linux-4.6):

  8e16789 KEYS: Use the symbol value for list size, updated by 
scripts/insert-sys-cert
  c4c3610 KEYS: Reserve an extra certificate symbol for inserting without 
recompiling

  We need to include these Kconfig options to reserve the memory:

  CONFIG_SYSTEM_EXTRA_CERTIFICATE=y
  CONFIG_SYSTEM_EXTRA_CERTIFICATE_SIZE=4096

  An additional patch, which will be upstreamed, is needed to fill the
  reserved memory with random data before it is compressed.  (The patch
  is attached.)  After compiling the kernel with the reserved memory,
  the following build step is required:

  scripts/insert-sys-cert -b vmlinux -c /dev/null

  If you want to add a cert, the following command will unpack a
  bzImage, install the cert (DER format) in the vmlinuz, and repack the
  bzImage.

  scripts/insert-sys-cert -s  -z  -c 

  Contact Information = George Wilson  / Mimi Zohar
  

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

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

[Kernel-packages] [Bug 1558553] 0002-KEYS-Print-insert-sys-cert-information-to-stout-inst.patch

[bugproxy]

Default Comment by Bridge

** Attachment added: 
"0002-KEYS-Print-insert-sys-cert-information-to-stout-inst.patch"
   
https://bugs.launchpad.net/bugs/1558553/+attachment/4808271/+files/0002-KEYS-Print-insert-sys-cert-information-to-stout-inst.patch

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

Title:
  IMA-appraisal is unusable in Ubuntu 16.04

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

Bug description:
  At some point, the IMA keyring changed from _ima to a trusted .ima
  keyring.   At that point, we couldn't add keys to the IMA keyring.
  Other distros import UEFI keys onto the system keyring.  Another
  method of loading keys on the system keyring is needed, which doesn't
  require the UEFI keys or rebuilding the kernel.

  To resolve this problem, the kernel should be built so that
  certificate memory is reserved and randomized.   Two patches are being
  upstreamed in this open window (linux-4.6):

  8e16789 KEYS: Use the symbol value for list size, updated by 
scripts/insert-sys-cert
  c4c3610 KEYS: Reserve an extra certificate symbol for inserting without 
recompiling

  We need to include these Kconfig options to reserve the memory:

  CONFIG_SYSTEM_EXTRA_CERTIFICATE=y
  CONFIG_SYSTEM_EXTRA_CERTIFICATE_SIZE=4096

  An additional patch, which will be upstreamed, is needed to fill the
  reserved memory with random data before it is compressed.  (The patch
  is attached.)  After compiling the kernel with the reserved memory,
  the following build step is required:

  scripts/insert-sys-cert -b vmlinux -c /dev/null

  If you want to add a cert, the following command will unpack a
  bzImage, install the cert (DER format) in the vmlinuz, and repack the
  bzImage.

  scripts/insert-sys-cert -s  -z  -c 

  Contact Information = George Wilson  / Mimi Zohar
  

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

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

[Kernel-packages] [Bug 1558553] The patch updates scripts/insert-sys-cert.c

[bugproxy]

Default Comment by Bridge

** Attachment added: "The patch updates scripts/insert-sys-cert.c"
   
https://bugs.launchpad.net/bugs/1558553/+attachment/4808269/+files/0001-KEYS-Support-for-inserting-a-certificate-into-x86-bz.patch

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

Title:
  IMA-appraisal is unusable in Ubuntu 16.04

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

Bug description:
  At some point, the IMA keyring changed from _ima to a trusted .ima
  keyring.   At that point, we couldn't add keys to the IMA keyring.
  Other distros import UEFI keys onto the system keyring.  Another
  method of loading keys on the system keyring is needed, which doesn't
  require the UEFI keys or rebuilding the kernel.

  To resolve this problem, the kernel should be built so that
  certificate memory is reserved and randomized.   Two patches are being
  upstreamed in this open window (linux-4.6):

  8e16789 KEYS: Use the symbol value for list size, updated by 
scripts/insert-sys-cert
  c4c3610 KEYS: Reserve an extra certificate symbol for inserting without 
recompiling

  We need to include these Kconfig options to reserve the memory:

  CONFIG_SYSTEM_EXTRA_CERTIFICATE=y
  CONFIG_SYSTEM_EXTRA_CERTIFICATE_SIZE=4096

  An additional patch, which will be upstreamed, is needed to fill the
  reserved memory with random data before it is compressed.  (The patch
  is attached.)  After compiling the kernel with the reserved memory,
  the following build step is required:

  scripts/insert-sys-cert -b vmlinux -c /dev/null

  If you want to add a cert, the following command will unpack a
  bzImage, install the cert (DER format) in the vmlinuz, and repack the
  bzImage.

  scripts/insert-sys-cert -s  -z  -c 

  Contact Information = George Wilson  / Mimi Zohar
  

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

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

[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)

[Rod Smith]

Joseph,

I think there was a typo in your URL, since it was the same as from the
previous test. Since you noted a different commit number, I adjusted and
pulled the kernel from:

http://kernel.ubuntu.com/~jsalisbury/lp1649326/59ed4b6/

This kernel fails to boot, with the "failed to get file info size/failed
to alloc highmem for files" message as noted in post #20 of this bug
report, rather than VirtualBox crashing, as described in my original bug
report description.

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

Title:
  EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13
  series)

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

Bug description:
  The EFI stub loader produces consistent boot errors when booting
  Trusty starting with version 3.13.0-101-generic. This bug can be
  reproduced in many ways (using efibootmgr, an EFI shell, rEFInd,
  etc.). One approach is:

  1) Install an EFI shell on the computer and set it as the default boot
 option using efibootmgr.
  2) Copy the kernel and initrd files from /boot to /boot/efi.
  3) Rename the kernel file to use a .efi filename extension.
  4) Reboot into the EFI shell.
  5) Try to launch the kernel with a command like:
 fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 
initrd=\initrd.img-3.13.0-104-generic

  The result will be a hung or crashed system. (In VirtualBox, in which
  I've tested this, the VM produces a "guru meditation" and the session
  terminates.)

  I myself have tested only with the 3.13.0-104 kernel; however, reports
  from others indicate that the problem began with the 3.13.0-101
  kernel. See this Kubuntu forum thread for details:

  https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest-
  kernels

  Note that early on, this thread focuses on rEFInd; however, the bug
  can be reproduced with other boot managers, including the EFI shell,
  as described in the preceding procedure, so I do not believe this is a
  rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux
  kernel, and I believe it's this component that's failing. The problem
  does NOT occur when using GRUB to launch the kernel. (GRUB does not
  rely on the EFI stub loader.)

  I have NOT encountered the problem with Xenial and its 4.4.0-series kernels 
(last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last 
tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from 
series beyond 3.13.0.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rodsmith   1675 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc
  InstallationDate: Installed on 2014-04-27 (960 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no 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)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic 
root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-106-generic N/A
   linux-backports-modules-3.13.0-106-generic  N/A
   linux-firmware  1.127.22
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-106-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _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/1649326/+subscriptions

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

[Kernel-packages] [Bug 1656908] Re: In Ubuntu 17.04 : after reboot getting message in console like Unable to open file: /etc/keys/x509_ima.der (-2)

[Steve Langasek]

This bug is not fixed by packaging the IMA tools, which would still not
be configured/enabled by default.  The bug here is that an error message
is presented on the console, by default, about an optional feature that
has not been enabled.  That's a kernel bug.

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

** Changed in: linux (Ubuntu)
 Assignee: Steve Langasek (vorlon) => Canonical Kernel Team 
(canonical-kernel-team)

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

Title:
  In Ubuntu 17.04 : after reboot getting message in console like Unable
  to open file: /etc/keys/x509_ima.der (-2)

Status in linux package in Ubuntu:
  New

Bug description:
  Installed Ubuntu17.04 as PowerVM/KVM or NV , after installation every
  reboot getting message in console

  Unable to open file: /etc/keys/x509_ima.der (-2)

  
  LOG:

  Booting Linux via __start() @ 0x0a6c ...
   -> smp_release_cpus()
  spinning_secondaries = 7
   <- smp_release_cpus()
  [0.663066] Unable to open file: /etc/keys/x509_ima.der (-2)[0.663129] 
Unable to open file: /etc/keys/x509_evm.der (-2)
  [0.792300] sd 0:0:1:0: [sda] Assuming drive cache: write through

  Ubuntu Zesty Zapus (development branch) ubuntu  hvc0

  ubuntu  login:

  Maybe this was introduced by
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643652 ? Will
  mirror this over to Launchpad for Canonical to review...

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

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

[Kernel-packages] [Bug 1658101] Re: linux: 4.9.0-15.16 -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) => Tim Gardner 
(timg-tpi)

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

** Description changed:

  This bug is for tracking the 4.9.0-15.16 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:Monday, 23. January 2017 21:46 UTC
+ kernel-phase:Uploaded

** Description changed:

  This bug is for tracking the 4.9.0-15.16 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:Monday, 23. January 2017 21:46 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/1658101

Title:
  linux: 4.9.0-15.16 -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 Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.9.0-15.16 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/1658101/+subscriptions

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

[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)

[Joseph Salisbury]

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

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1649326/74bdcac

Can you test that kernel and report back if it has 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/1649326

Title:
  EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13
  series)

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

Bug description:
  The EFI stub loader produces consistent boot errors when booting
  Trusty starting with version 3.13.0-101-generic. This bug can be
  reproduced in many ways (using efibootmgr, an EFI shell, rEFInd,
  etc.). One approach is:

  1) Install an EFI shell on the computer and set it as the default boot
 option using efibootmgr.
  2) Copy the kernel and initrd files from /boot to /boot/efi.
  3) Rename the kernel file to use a .efi filename extension.
  4) Reboot into the EFI shell.
  5) Try to launch the kernel with a command like:
 fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 
initrd=\initrd.img-3.13.0-104-generic

  The result will be a hung or crashed system. (In VirtualBox, in which
  I've tested this, the VM produces a "guru meditation" and the session
  terminates.)

  I myself have tested only with the 3.13.0-104 kernel; however, reports
  from others indicate that the problem began with the 3.13.0-101
  kernel. See this Kubuntu forum thread for details:

  https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest-
  kernels

  Note that early on, this thread focuses on rEFInd; however, the bug
  can be reproduced with other boot managers, including the EFI shell,
  as described in the preceding procedure, so I do not believe this is a
  rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux
  kernel, and I believe it's this component that's failing. The problem
  does NOT occur when using GRUB to launch the kernel. (GRUB does not
  rely on the EFI stub loader.)

  I have NOT encountered the problem with Xenial and its 4.4.0-series kernels 
(last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last 
tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from 
series beyond 3.13.0.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rodsmith   1675 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc
  InstallationDate: Installed on 2014-04-27 (960 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no 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)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic 
root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-106-generic N/A
   linux-backports-modules-3.13.0-106-generic  N/A
   linux-firmware  1.127.22
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-106-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _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/1649326/+subscriptions

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

[Kernel-packages] [Bug 1658270] Re: Backport Dirty COW patch to prevent wineserver freeze

[Joseph Salisbury]

I built a Trusty test kernel with the V2 version of the patch:
https://patchwork.kernel.org/patch/9499897/

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

Can you test this kernel an see if it resolves this bug?

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

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

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

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

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

Title:
  Backport Dirty COW patch to prevent wineserver freeze

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

Bug description:
  A few kernels updates ago (after kernel 3.13.0-98) on 14.04 (Trusty) a
  backported fix for Dirty COW from kernel 4.8.3 resulted in some Delphi
  apps freezing wineserver and leaving it unkillable:

  https://bugs.winehq.org/show_bug.cgi?id=41637

  I haven't tested for the bug on 16.04 Xenial (kernel 4.4.0-59) but it
  is probably affected.  A patch is available:

  https://lkml.org/lkml/2017/1/5/13
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jhansonxi   2775 F pulseaudio
   /dev/snd/controlC2:  jhansonxi   2775 F pulseaudio
   /dev/snd/controlC0:  jhansonxi   2775 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=6c1d3a04-0529-476c-b193-3e584c0333ca
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic 
root=/dev/mapper/vg0-lv1 ro quiet nosplash
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-59-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: dialout
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1206
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M3A78-EM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1206:bd11/26/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3A78-EM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1658101] Re: linux: 4.9.0-15.16 -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) => 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/1658101

Title:
  linux: 4.9.0-15.16 -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 Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.9.0-15.16 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/1658101/+subscriptions

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

[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)

[Rod Smith]

Joseph, the linux-
image-3.13.0-101-generic_3.13.0-101.148~lp1649326Commit74bdcac_amd64.deb
kernel also boots correctly.

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

Title:
  EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13
  series)

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

Bug description:
  The EFI stub loader produces consistent boot errors when booting
  Trusty starting with version 3.13.0-101-generic. This bug can be
  reproduced in many ways (using efibootmgr, an EFI shell, rEFInd,
  etc.). One approach is:

  1) Install an EFI shell on the computer and set it as the default boot
 option using efibootmgr.
  2) Copy the kernel and initrd files from /boot to /boot/efi.
  3) Rename the kernel file to use a .efi filename extension.
  4) Reboot into the EFI shell.
  5) Try to launch the kernel with a command like:
 fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 
initrd=\initrd.img-3.13.0-104-generic

  The result will be a hung or crashed system. (In VirtualBox, in which
  I've tested this, the VM produces a "guru meditation" and the session
  terminates.)

  I myself have tested only with the 3.13.0-104 kernel; however, reports
  from others indicate that the problem began with the 3.13.0-101
  kernel. See this Kubuntu forum thread for details:

  https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest-
  kernels

  Note that early on, this thread focuses on rEFInd; however, the bug
  can be reproduced with other boot managers, including the EFI shell,
  as described in the preceding procedure, so I do not believe this is a
  rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux
  kernel, and I believe it's this component that's failing. The problem
  does NOT occur when using GRUB to launch the kernel. (GRUB does not
  rely on the EFI stub loader.)

  I have NOT encountered the problem with Xenial and its 4.4.0-series kernels 
(last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last 
tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from 
series beyond 3.13.0.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rodsmith   1675 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc
  InstallationDate: Installed on 2014-04-27 (960 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no 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)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic 
root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-106-generic N/A
   linux-backports-modules-3.13.0-106-generic  N/A
   linux-firmware  1.127.22
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-106-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _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/1649326/+subscriptions

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

[Kernel-packages] [Bug 1654067] Re: Ubuntu 16.10 KVM: Running out of memory if trying to bringup guest with more than 64VFs.

[bugproxy]

--- Comment From cls...@us.ibm.com 2017-01-23 15:26 EDT---
I tried Ubuntu 17.04 kernel 4.9.0-12-generic and can not recreate the issue.

** Tags added: verification-done

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

Title:
  Ubuntu 16.10 KVM: Running out of memory if trying to bringup guest
  with more than 64VFs.

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

Bug description:
  == Comment: #0 - Carol L. Soto - 2017-01-04 12:03:57 ==
  ---Problem Description---
  If user try to create a guest with more than 64 VFs then the guest will have 
issues to come up but if user keeps trying to bringup this guest over and over 
the system will eventually start seeing out of memory messages. 
  Like this:
  Jan  3 14:33:13 ltc-fire1 kernel: [ 1053.950753] systemd invoked oom-killer: 
gfp_mask=0x26000d0(GFP_TEMPORARY|__GFP_NOTRACK), order=0, oom_score_adj=0
  Jan  3 14:33:16 ltc-fire1 kernel: [ 1053.950757] systemd cpuset=/ 
mems_allowed=0
  Jan  3 14:33:16 ltc-fire1 kernel: [ 1053.950761] CPU: 104 PID: 1 Comm: 
systemd Tainted: G   OE   4.8.0-34-generic #36-Ubuntu
  Jan  3 14:33:16 ltc-fire1 kernel: [ 1053.950763] Call Trace:

   
  ---uname output---
  Linux ltc-fire1 4.8.0-34-generic #36 SMP Tue Jan 3 15:27:22 CST 2017 ppc64le 
ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  we are using Mellanox CX4 card with SRIOV enabled to be able to create a 
guest with more than 64 VFs.  

   
  Machine Type = P8 
   

  ---Steps to Reproduce---
   create a guest with more than 64 VFs and then just try to bring up the guest 
by 
  virsh start --console ltc-fire1-vm3-ubuntu-16.10-69VFs.
  Will attach example guest xml.

  == Comment: #2 - Carol L. Soto - 2017-01-04 12:09:32 ==
  If I build a kernel with these upstream patches, then I do not see the memory 
leaks messages in dmesg:

  From 88f54a3581eb9deaa3bd1aade40aef266d782385 Mon Sep 17 00:00:00 2001
  From: Alexey Kardashevskiy 
  Date: Wed, 30 Nov 2016 17:51:59 +1100
  Subject: powerpc/iommu: Pass mm_struct to init/cleanup helpers

  From d7baee6901b34c4895eb78efdbf13a49079d7404 Mon Sep 17 00:00:00 2001
  From: Alexey Kardashevskiy 
  Date: Wed, 30 Nov 2016 17:52:00 +1100
  Subject: powerpc/iommu: Stop using @current in mm_iommu_xxx

  From 39701e56f5f16ea0cf8fc9e8472e645f8de91d23 Mon Sep 17 00:00:00 2001
  From: Alexey Kardashevskiy 
  Date: Wed, 30 Nov 2016 17:52:01 +1100
  Subject: vfio/spapr: Postpone allocation of userspace version of TCE table

  From 6f01cc692a16405235d5c34056455b182682123c Mon Sep 17 00:00:00 2001
  From: Alexey Kardashevskiy 
  Date: Wed, 30 Nov 2016 17:52:02 +1100
  Subject: vfio/spapr: Add a helper to create default DMA window

  From d9c728949ddc9de5734bf3b12ea906ca8a77f2a0 Mon Sep 17 00:00:00 2001
  From: Alexey Kardashevskiy 
  Date: Wed, 30 Nov 2016 17:52:03 +1100
  Subject: vfio/spapr: Postpone default window creation

  From bc82d122ae4a0e9f971f13403995898fcfa0c09e Mon Sep 17 00:00:00 2001
  From: Alexey Kardashevskiy 
  Date: Wed, 30 Nov 2016 17:52:04 +1100
  Subject: vfio/spapr: Reference mm in tce_container

  From 4b6fad7097f883335b6d9627c883cb7f276d94c9 Mon Sep 17 00:00:00 2001
  From: Alexey Kardashevskiy 
  Date: Wed, 30 Nov 2016 17:52:05 +1100
  Subject: powerpc/mm/iommu, vfio/spapr: Put pages on VFIO container shutdown

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

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

[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)

[Joseph Salisbury]

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

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1649326/74bdcac

Can you test that kernel and report back if it has 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/1649326

Title:
  EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13
  series)

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

Bug description:
  The EFI stub loader produces consistent boot errors when booting
  Trusty starting with version 3.13.0-101-generic. This bug can be
  reproduced in many ways (using efibootmgr, an EFI shell, rEFInd,
  etc.). One approach is:

  1) Install an EFI shell on the computer and set it as the default boot
 option using efibootmgr.
  2) Copy the kernel and initrd files from /boot to /boot/efi.
  3) Rename the kernel file to use a .efi filename extension.
  4) Reboot into the EFI shell.
  5) Try to launch the kernel with a command like:
 fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 
initrd=\initrd.img-3.13.0-104-generic

  The result will be a hung or crashed system. (In VirtualBox, in which
  I've tested this, the VM produces a "guru meditation" and the session
  terminates.)

  I myself have tested only with the 3.13.0-104 kernel; however, reports
  from others indicate that the problem began with the 3.13.0-101
  kernel. See this Kubuntu forum thread for details:

  https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest-
  kernels

  Note that early on, this thread focuses on rEFInd; however, the bug
  can be reproduced with other boot managers, including the EFI shell,
  as described in the preceding procedure, so I do not believe this is a
  rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux
  kernel, and I believe it's this component that's failing. The problem
  does NOT occur when using GRUB to launch the kernel. (GRUB does not
  rely on the EFI stub loader.)

  I have NOT encountered the problem with Xenial and its 4.4.0-series kernels 
(last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last 
tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from 
series beyond 3.13.0.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rodsmith   1675 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc
  InstallationDate: Installed on 2014-04-27 (960 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no 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)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic 
root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-106-generic N/A
   linux-backports-modules-3.13.0-106-generic  N/A
   linux-firmware  1.127.22
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-106-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _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/1649326/+subscriptions

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

[Kernel-packages] [Bug 1658790] Sosreport

[bugproxy]

Default Comment by Bridge

** Attachment added: "Sosreport"
   
https://bugs.launchpad.net/bugs/1658790/+attachment/4808243/+files/sosreport-tuleta4u-lp4-20170111041125.tar.xz

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

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

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

Title:
  Ubuntu 17.04: kdump fails with error "kdump-tools[1532]: /etc/init.d
  /kdump-tools: 26: [: -ne: unexpected operator" when / file system is
  xfs.

Status in makedumpfile package in Ubuntu:
  New

Bug description:
  ---Problem Description---

  Ubuntu 17.04: kdump fails with error "kdump-tools[1532]: /etc/init.d
  /kdump-tools: 26: [: -ne: unexpected operator" when / file system is
  xfs.

  ---Steps to Reproduce---

  1. Install Ubuntu 17.04 with / as xfs.
  2. Configure kdump.
  3. trigger crash.

  Machine hangs after below log. Attaching console log.

   Starting Raise network interfaces...
  [  OK  ] Started Raise network interfaces.
  [  OK  ] Reached target Network.
  [  OK  ] Reached target Network is Online.
   Starting iSCSI initiator daemon (iscsid)...
   Starting Kernel crash dump capture service...
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [   86.119692] kdump-tools[1532]: /etc/init.d/kdump-tools: 26: [: -ne: 
unexpected operator
  [  OK  ] Started Kernel crash dump capture service.
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).

  
  4. After manual reboot  /etc/default/kdump-tools is empty.

  Logs
  ---

  root@tuleta4u-lp4:/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.9.0-11-generic
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.9.0-11-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.9.0-11-generic 
root=UUID=adbca1e4-13ef-4054-a486-402ab1552ca6 ro irqpoll nr_cpus=1 nousb 
systemd.unit=kdump-tools.service ata_piix.prefer_ms_hyperv=0" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  root@tuleta4u-lp4:/home/ubuntu# tail /etc/default/kdump-tools 
  #
  # SSH_KEY=""
  #
  # HOSTTAG="hostname|[ip]"
  # 
  # NFS=""
  #
  # NFS_TIMEO="600"
  #
  # NFS_RETRANS="3"
  root@tuleta4u-lp4:/home/ubuntu# echo "c" > /proc/sysrq-trigger
  [  199.601020] sysrq: SysRq : Trigger a crash
  [  199.601044] Unable to handle kernel paging request for data at address 
0x
  [  199.601053] Faulting instruction address: 0xc06af628
  [  199.601061] Oops: Kernel access of bad area, sig: 11 [#1]
  [  199.601066] SMP NR_CPUS=2048 [  199.601069] NUMA

  
  after crash:

  root@tuleta4u-lp4:/home/ubuntu# cat /etc/default/kdump-tools 
  root@tuleta4u-lp4:/home/ubuntu#

  > > > 
  > > > Hi,
  > > > 
  > > > yeah bug is recreatable.
  > > > 
  > > 
  > > Hi Pavithra/Latha,
  > > 
  > > Any idea why /etc/default/kdumpt-tools file is empty?
  > > Are we getting an empty /etc/default/kdumpt-tools file on installing
  > > kdump-tools?
  > > 
  > > Pavithra, please mention the steps used to recreated this bug..
  > > 
  > > Thanks
  > > Hari
  > 
  > When we install kdump /etc/default/kdumpt-tools will have valid contents and
  > "kdump-config show" shows "ready to kdump" but after crash
  > /etc/default/kdumpt-tools file contents are getting deleted. 
  > 
  > ---Steps to Reproduce---
  > 
  > 1. Install Ubuntu 17.04 with / as xfs.
  > 2. Configure kdump.
  > 3. trigger crash.
  >

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

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

[Kernel-packages] [Bug 1658790] [NEW] Ubuntu 17.04: kdump fails with error "kdump-tools[1532]: /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file system is xfs.

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

---Problem Description---

Ubuntu 17.04: kdump fails with error "kdump-tools[1532]: /etc/init.d
/kdump-tools: 26: [: -ne: unexpected operator" when / file system is
xfs.

---Steps to Reproduce---

1. Install Ubuntu 17.04 with / as xfs.
2. Configure kdump.
3. trigger crash.

Machine hangs after below log. Attaching console log.

 Starting Raise network interfaces...
[  OK  ] Started Raise network interfaces.
[  OK  ] Reached target Network.
[  OK  ] Reached target Network is Online.
 Starting iSCSI initiator daemon (iscsid)...
 Starting Kernel crash dump capture service...
[  OK  ] Started iSCSI initiator daemon (iscsid).
 Starting Login to default iSCSI targets...
[   86.119692] kdump-tools[1532]: /etc/init.d/kdump-tools: 26: [: -ne: 
unexpected operator
[  OK  ] Started Kernel crash dump capture service.
[  OK  ] Started Login to default iSCSI targets.
[  OK  ] Reached target Remote File Systems (Pre).


4. After manual reboot  /etc/default/kdump-tools is empty.

Logs
---

root@tuleta4u-lp4:/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.9.0-11-generic
kdump initrd: 
   /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.9.0-11-generic
current state:ready to kdump

kexec command:
  /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.9.0-11-generic 
root=UUID=adbca1e4-13ef-4054-a486-402ab1552ca6 ro irqpoll nr_cpus=1 nousb 
systemd.unit=kdump-tools.service ata_piix.prefer_ms_hyperv=0" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
root@tuleta4u-lp4:/home/ubuntu# tail /etc/default/kdump-tools 
#
# SSH_KEY=""
#
# HOSTTAG="hostname|[ip]"
# 
# NFS=""
#
# NFS_TIMEO="600"
#
# NFS_RETRANS="3"
root@tuleta4u-lp4:/home/ubuntu# echo "c" > /proc/sysrq-trigger
[  199.601020] sysrq: SysRq : Trigger a crash
[  199.601044] Unable to handle kernel paging request for data at address 
0x
[  199.601053] Faulting instruction address: 0xc06af628
[  199.601061] Oops: Kernel access of bad area, sig: 11 [#1]
[  199.601066] SMP NR_CPUS=2048 [  199.601069] NUMA


after crash:

root@tuleta4u-lp4:/home/ubuntu# cat /etc/default/kdump-tools 
root@tuleta4u-lp4:/home/ubuntu#

> > > 
> > > Hi,
> > > 
> > > yeah bug is recreatable.
> > > 
> > 
> > Hi Pavithra/Latha,
> > 
> > Any idea why /etc/default/kdumpt-tools file is empty?
> > Are we getting an empty /etc/default/kdumpt-tools file on installing
> > kdump-tools?
> > 
> > Pavithra, please mention the steps used to recreated this bug..
> > 
> > Thanks
> > Hari
> 
> When we install kdump /etc/default/kdumpt-tools will have valid contents and
> "kdump-config show" shows "ready to kdump" but after crash
> /etc/default/kdumpt-tools file contents are getting deleted. 
> 
> ---Steps to Reproduce---
> 
> 1. Install Ubuntu 17.04 with / as xfs.
> 2. Configure kdump.
> 3. trigger crash.
>

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


** Tags: architecture-ppc64le bugnameltc-150457 severity-high 
targetmilestone-inin1704
-- 
Ubuntu 17.04: kdump fails with error "kdump-tools[1532]: 
/etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file system is 
xfs.
https://bugs.launchpad.net/bugs/1658790
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to makedumpfile in Ubuntu.

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

[Kernel-packages] [Bug 1581326] syslog

[bugproxy]

Default Comment by Bridge

** Attachment added: "syslog"
   https://bugs.launchpad.net/bugs/1581326/+attachment/4808236/+files/syslog

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

Title:
  Kernel crashed while Creating a second RAID volume on Ubuntu 16.04 OS.

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

Bug description:
  Booted into Ubuntu16.04(4.4.0-21-generic) OS with inbox driver-
  v12.100.00.00,

  Successfully discovered HBA and the devices connected to HBA.
  >>Launched SAS3IRCU utility and created a RAID volume (RAID0/RAID1/RAID10). 
volume successfully created and listed from SAS3IRCU utility.
  >>Tried to create a second RAID volume (RAID0/RAID1/RAID10) from SAS3IRCU 
utility. 
  Kernel crashed here while creating second volume.
  >>tried with all possible combinations of RAID volumes.

  Please find the attached kernel crash logs.

  >>cat /proc/version_signature 
  Ubuntu 4.4.0-21.37-generic 4.4.6 

  HBA used : LSI SAS3(Fury)

  Issue : Kernel gets crashed , when tried creating 2nd RAID volume.
  Expected : One should be able to create MAX 2 RAID volumes at any point of 
time successfully , without any kernel crash.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=7f36ec0c-c34b-4750-bd78-2c394cc513b2
  InstallationDate: Installed on 2016-05-11 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig:
   enp5s0f0  no wireless extensions.
   
   enp5s0f1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Supermicro X9DRH-7TF/7F/iTF/iF
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=8f5b571b-235f-4881-8344-dfaa2bd9ed48 ro
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
   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
  RfKill:
   
  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: 04/28/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.0b
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X9DRH-7TF/7F/iTF/iF
  dmi.board.vendor: Supermicro
  dmi.board.version: 1234567890
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 1234567890
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.0b:bd04/28/2014:svnSupermicro:pnX9DRH-7TF/7F/iTF/iF:pvr1234567890:rvnSupermicro:rnX9DRH-7TF/7F/iTF/iF:rvr1234567890:cvnSupermicro:ct3:cvr1234567890:
  dmi.product.name: X9DRH-7TF/7F/iTF/iF
  dmi.product.version: 1234567890
  dmi.sys.vendor: Supermicro
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=7f36ec0c-c34b-4750-bd78-2c394cc513b2
  InstallationDate: Installed on 2016-05-11 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig:
   enp5s0f0  no wireless extensions.
   
   enp5s0f1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Supermicro X9DRH-7TF/7F/iTF/iF
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=8f5b571b-235f-4881-8344-dfaa2bd9ed48 ro
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
   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
   

[Kernel-packages] [Bug 1581326] 4.4.14- Kernel crash logs.

[bugproxy]

Default Comment by Bridge

** Attachment added: "4.4.14- Kernel crash logs."
   
https://bugs.launchpad.net/bugs/1581326/+attachment/4808240/+files/Ubuntu16.04_4.4.14_kernel_log.txt

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

Title:
  Kernel crashed while Creating a second RAID volume on Ubuntu 16.04 OS.

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

Bug description:
  Booted into Ubuntu16.04(4.4.0-21-generic) OS with inbox driver-
  v12.100.00.00,

  Successfully discovered HBA and the devices connected to HBA.
  >>Launched SAS3IRCU utility and created a RAID volume (RAID0/RAID1/RAID10). 
volume successfully created and listed from SAS3IRCU utility.
  >>Tried to create a second RAID volume (RAID0/RAID1/RAID10) from SAS3IRCU 
utility. 
  Kernel crashed here while creating second volume.
  >>tried with all possible combinations of RAID volumes.

  Please find the attached kernel crash logs.

  >>cat /proc/version_signature 
  Ubuntu 4.4.0-21.37-generic 4.4.6 

  HBA used : LSI SAS3(Fury)

  Issue : Kernel gets crashed , when tried creating 2nd RAID volume.
  Expected : One should be able to create MAX 2 RAID volumes at any point of 
time successfully , without any kernel crash.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=7f36ec0c-c34b-4750-bd78-2c394cc513b2
  InstallationDate: Installed on 2016-05-11 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig:
   enp5s0f0  no wireless extensions.
   
   enp5s0f1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Supermicro X9DRH-7TF/7F/iTF/iF
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=8f5b571b-235f-4881-8344-dfaa2bd9ed48 ro
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
   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
  RfKill:
   
  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: 04/28/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.0b
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X9DRH-7TF/7F/iTF/iF
  dmi.board.vendor: Supermicro
  dmi.board.version: 1234567890
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 1234567890
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.0b:bd04/28/2014:svnSupermicro:pnX9DRH-7TF/7F/iTF/iF:pvr1234567890:rvnSupermicro:rnX9DRH-7TF/7F/iTF/iF:rvr1234567890:cvnSupermicro:ct3:cvr1234567890:
  dmi.product.name: X9DRH-7TF/7F/iTF/iF
  dmi.product.version: 1234567890
  dmi.sys.vendor: Supermicro
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=7f36ec0c-c34b-4750-bd78-2c394cc513b2
  InstallationDate: Installed on 2016-05-11 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig:
   enp5s0f0  no wireless extensions.
   
   enp5s0f1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Supermicro X9DRH-7TF/7F/iTF/iF
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=8f5b571b-235f-4881-8344-dfaa2bd9ed48 ro
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   

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

[bugproxy]

Default Comment by Bridge

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

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

Title:
  Kernel crashed while Creating a second RAID volume on Ubuntu 16.04 OS.

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

Bug description:
  Booted into Ubuntu16.04(4.4.0-21-generic) OS with inbox driver-
  v12.100.00.00,

  Successfully discovered HBA and the devices connected to HBA.
  >>Launched SAS3IRCU utility and created a RAID volume (RAID0/RAID1/RAID10). 
volume successfully created and listed from SAS3IRCU utility.
  >>Tried to create a second RAID volume (RAID0/RAID1/RAID10) from SAS3IRCU 
utility. 
  Kernel crashed here while creating second volume.
  >>tried with all possible combinations of RAID volumes.

  Please find the attached kernel crash logs.

  >>cat /proc/version_signature 
  Ubuntu 4.4.0-21.37-generic 4.4.6 

  HBA used : LSI SAS3(Fury)

  Issue : Kernel gets crashed , when tried creating 2nd RAID volume.
  Expected : One should be able to create MAX 2 RAID volumes at any point of 
time successfully , without any kernel crash.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=7f36ec0c-c34b-4750-bd78-2c394cc513b2
  InstallationDate: Installed on 2016-05-11 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig:
   enp5s0f0  no wireless extensions.
   
   enp5s0f1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Supermicro X9DRH-7TF/7F/iTF/iF
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=8f5b571b-235f-4881-8344-dfaa2bd9ed48 ro
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
   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
  RfKill:
   
  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: 04/28/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.0b
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X9DRH-7TF/7F/iTF/iF
  dmi.board.vendor: Supermicro
  dmi.board.version: 1234567890
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 1234567890
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.0b:bd04/28/2014:svnSupermicro:pnX9DRH-7TF/7F/iTF/iF:pvr1234567890:rvnSupermicro:rnX9DRH-7TF/7F/iTF/iF:rvr1234567890:cvnSupermicro:ct3:cvr1234567890:
  dmi.product.name: X9DRH-7TF/7F/iTF/iF
  dmi.product.version: 1234567890
  dmi.sys.vendor: Supermicro
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=7f36ec0c-c34b-4750-bd78-2c394cc513b2
  InstallationDate: Installed on 2016-05-11 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig:
   enp5s0f0  no wireless extensions.
   
   enp5s0f1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Supermicro X9DRH-7TF/7F/iTF/iF
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=8f5b571b-235f-4881-8344-dfaa2bd9ed48 ro
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
   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 

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

[bugproxy]

Default Comment by Bridge

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

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

Title:
  Kernel crashed while Creating a second RAID volume on Ubuntu 16.04 OS.

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

Bug description:
  Booted into Ubuntu16.04(4.4.0-21-generic) OS with inbox driver-
  v12.100.00.00,

  Successfully discovered HBA and the devices connected to HBA.
  >>Launched SAS3IRCU utility and created a RAID volume (RAID0/RAID1/RAID10). 
volume successfully created and listed from SAS3IRCU utility.
  >>Tried to create a second RAID volume (RAID0/RAID1/RAID10) from SAS3IRCU 
utility. 
  Kernel crashed here while creating second volume.
  >>tried with all possible combinations of RAID volumes.

  Please find the attached kernel crash logs.

  >>cat /proc/version_signature 
  Ubuntu 4.4.0-21.37-generic 4.4.6 

  HBA used : LSI SAS3(Fury)

  Issue : Kernel gets crashed , when tried creating 2nd RAID volume.
  Expected : One should be able to create MAX 2 RAID volumes at any point of 
time successfully , without any kernel crash.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=7f36ec0c-c34b-4750-bd78-2c394cc513b2
  InstallationDate: Installed on 2016-05-11 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig:
   enp5s0f0  no wireless extensions.
   
   enp5s0f1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Supermicro X9DRH-7TF/7F/iTF/iF
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=8f5b571b-235f-4881-8344-dfaa2bd9ed48 ro
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
   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
  RfKill:
   
  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: 04/28/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.0b
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X9DRH-7TF/7F/iTF/iF
  dmi.board.vendor: Supermicro
  dmi.board.version: 1234567890
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 1234567890
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.0b:bd04/28/2014:svnSupermicro:pnX9DRH-7TF/7F/iTF/iF:pvr1234567890:rvnSupermicro:rnX9DRH-7TF/7F/iTF/iF:rvr1234567890:cvnSupermicro:ct3:cvr1234567890:
  dmi.product.name: X9DRH-7TF/7F/iTF/iF
  dmi.product.version: 1234567890
  dmi.sys.vendor: Supermicro
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=7f36ec0c-c34b-4750-bd78-2c394cc513b2
  InstallationDate: Installed on 2016-05-11 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig:
   enp5s0f0  no wireless extensions.
   
   enp5s0f1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Supermicro X9DRH-7TF/7F/iTF/iF
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=8f5b571b-235f-4881-8344-dfaa2bd9ed48 ro
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   

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

[bugproxy]

Default Comment by Bridge

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

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

Title:
  Kernel crashed while Creating a second RAID volume on Ubuntu 16.04 OS.

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

Bug description:
  Booted into Ubuntu16.04(4.4.0-21-generic) OS with inbox driver-
  v12.100.00.00,

  Successfully discovered HBA and the devices connected to HBA.
  >>Launched SAS3IRCU utility and created a RAID volume (RAID0/RAID1/RAID10). 
volume successfully created and listed from SAS3IRCU utility.
  >>Tried to create a second RAID volume (RAID0/RAID1/RAID10) from SAS3IRCU 
utility. 
  Kernel crashed here while creating second volume.
  >>tried with all possible combinations of RAID volumes.

  Please find the attached kernel crash logs.

  >>cat /proc/version_signature 
  Ubuntu 4.4.0-21.37-generic 4.4.6 

  HBA used : LSI SAS3(Fury)

  Issue : Kernel gets crashed , when tried creating 2nd RAID volume.
  Expected : One should be able to create MAX 2 RAID volumes at any point of 
time successfully , without any kernel crash.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=7f36ec0c-c34b-4750-bd78-2c394cc513b2
  InstallationDate: Installed on 2016-05-11 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig:
   enp5s0f0  no wireless extensions.
   
   enp5s0f1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Supermicro X9DRH-7TF/7F/iTF/iF
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=8f5b571b-235f-4881-8344-dfaa2bd9ed48 ro
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
   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
  RfKill:
   
  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: 04/28/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.0b
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X9DRH-7TF/7F/iTF/iF
  dmi.board.vendor: Supermicro
  dmi.board.version: 1234567890
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 1234567890
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.0b:bd04/28/2014:svnSupermicro:pnX9DRH-7TF/7F/iTF/iF:pvr1234567890:rvnSupermicro:rnX9DRH-7TF/7F/iTF/iF:rvr1234567890:cvnSupermicro:ct3:cvr1234567890:
  dmi.product.name: X9DRH-7TF/7F/iTF/iF
  dmi.product.version: 1234567890
  dmi.sys.vendor: Supermicro
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=7f36ec0c-c34b-4750-bd78-2c394cc513b2
  InstallationDate: Installed on 2016-05-11 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig:
   enp5s0f0  no wireless extensions.
   
   enp5s0f1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Supermicro X9DRH-7TF/7F/iTF/iF
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=8f5b571b-235f-4881-8344-dfaa2bd9ed48 ro
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   

[Kernel-packages] [Bug 1581326] kern.log

[bugproxy]

Default Comment by Bridge

** Attachment added: "kern.log"
   https://bugs.launchpad.net/bugs/1581326/+attachment/4808235/+files/kern.log

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

Title:
  Kernel crashed while Creating a second RAID volume on Ubuntu 16.04 OS.

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

Bug description:
  Booted into Ubuntu16.04(4.4.0-21-generic) OS with inbox driver-
  v12.100.00.00,

  Successfully discovered HBA and the devices connected to HBA.
  >>Launched SAS3IRCU utility and created a RAID volume (RAID0/RAID1/RAID10). 
volume successfully created and listed from SAS3IRCU utility.
  >>Tried to create a second RAID volume (RAID0/RAID1/RAID10) from SAS3IRCU 
utility. 
  Kernel crashed here while creating second volume.
  >>tried with all possible combinations of RAID volumes.

  Please find the attached kernel crash logs.

  >>cat /proc/version_signature 
  Ubuntu 4.4.0-21.37-generic 4.4.6 

  HBA used : LSI SAS3(Fury)

  Issue : Kernel gets crashed , when tried creating 2nd RAID volume.
  Expected : One should be able to create MAX 2 RAID volumes at any point of 
time successfully , without any kernel crash.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=7f36ec0c-c34b-4750-bd78-2c394cc513b2
  InstallationDate: Installed on 2016-05-11 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig:
   enp5s0f0  no wireless extensions.
   
   enp5s0f1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Supermicro X9DRH-7TF/7F/iTF/iF
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=8f5b571b-235f-4881-8344-dfaa2bd9ed48 ro
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
   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
  RfKill:
   
  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: 04/28/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.0b
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X9DRH-7TF/7F/iTF/iF
  dmi.board.vendor: Supermicro
  dmi.board.version: 1234567890
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 1234567890
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.0b:bd04/28/2014:svnSupermicro:pnX9DRH-7TF/7F/iTF/iF:pvr1234567890:rvnSupermicro:rnX9DRH-7TF/7F/iTF/iF:rvr1234567890:cvnSupermicro:ct3:cvr1234567890:
  dmi.product.name: X9DRH-7TF/7F/iTF/iF
  dmi.product.version: 1234567890
  dmi.sys.vendor: Supermicro
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=7f36ec0c-c34b-4750-bd78-2c394cc513b2
  InstallationDate: Installed on 2016-05-11 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig:
   enp5s0f0  no wireless extensions.
   
   enp5s0f1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Supermicro X9DRH-7TF/7F/iTF/iF
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=8f5b571b-235f-4881-8344-dfaa2bd9ed48 ro
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
   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  

[Kernel-packages] [Bug 1635447] Re: Upgraded or Live USB 16.10 hangs at boot up blank purple screen

[Joseph Salisbury]

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

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

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

Title:
  Upgraded or Live USB 16.10 hangs at boot up blank purple screen

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

Bug description:
  My HP dm3z-2000 laptop works out of box for everything with Ubuntu
  16.04, but fails to boot up after upgraded to 16.10. The upgrading
  went smooth itself.

  Laptop still can boot up with the latest 4.4 kernel of 16.04 which I
  did a regular update/upgrade before 16.10 release upgrade.

  Then I tried to boot with 16.10 Live USB and got same result.

  It also can boot up with kernel 4.8 if "acpi=off" parameter in place,
  but it takes long time to boot up. Everything seems fine after logged
  in and Unity 8 session works too.

  I couldn't get any log files since the system won't boot up,
  Ctrl+Alt+F1 does nothing. I can only see some messages in text boot
  mode, so I took a screen shot with my phone and attached here.

  Let me know how to get more details.
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  renm   2918 F pulseaudio
   /dev/snd/controlC1:  renm   2918 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=7e8ca036-f81d-43e2-820a-1deadcffc2dc
  InstallationDate: Installed on 2016-10-08 (13 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard HP Pavilion dm3t Notebook PC
  Package: linux (not installed)
  ProcFB:
   0 radeondrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=19005996-db50-4249-9c73-17cf874dc678 ro acpi=off
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-22-generic N/A
   linux-backports-modules-4.8.0-22-generic  N/A
   linux-firmware1.161
  Tags:  yakkety
  Uname: Linux 4.8.0-22-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-15 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/13/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1482
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 76.34
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.15:bd10/13/2010:svnHewlett-Packard:pnHPPaviliondm3tNotebookPC:pvr048620241F0011032:rvnHewlett-Packard:rn1482:rvr76.34:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion dm3t Notebook PC
  dmi.product.version: 048620241F0011032
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1581326] Re: Kernel crashed while Creating a second RAID volume on Ubuntu 16.04 OS.

[Joseph Salisbury]

@Chaitra, do you have an update on the status of this patch upstream?
If not, I can contact the patch author, Sreekanth Reddy, directly.

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

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

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

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

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

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

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

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

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

Title:
  Kernel crashed while Creating a second RAID volume on Ubuntu 16.04 OS.

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

Bug description:
  Booted into Ubuntu16.04(4.4.0-21-generic) OS with inbox driver-
  v12.100.00.00,

  Successfully discovered HBA and the devices connected to HBA.
  >>Launched SAS3IRCU utility and created a RAID volume (RAID0/RAID1/RAID10). 
volume successfully created and listed from SAS3IRCU utility.
  >>Tried to create a second RAID volume (RAID0/RAID1/RAID10) from SAS3IRCU 
utility. 
  Kernel crashed here while creating second volume.
  >>tried with all possible combinations of RAID volumes.

  Please find the attached kernel crash logs.

  >>cat /proc/version_signature 
  Ubuntu 4.4.0-21.37-generic 4.4.6 

  HBA used : LSI SAS3(Fury)

  Issue : Kernel gets crashed , when tried creating 2nd RAID volume.
  Expected : One should be able to create MAX 2 RAID volumes at any point of 
time successfully , without any kernel crash.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=7f36ec0c-c34b-4750-bd78-2c394cc513b2
  InstallationDate: Installed on 2016-05-11 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig:
   enp5s0f0  no wireless extensions.
   
   enp5s0f1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Supermicro X9DRH-7TF/7F/iTF/iF
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=8f5b571b-235f-4881-8344-dfaa2bd9ed48 ro
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
   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
  RfKill:
   
  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: 04/28/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.0b
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X9DRH-7TF/7F/iTF/iF
  dmi.board.vendor: Supermicro
  dmi.board.version: 1234567890
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 1234567890
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.0b:bd04/28/2014:svnSupermicro:pnX9DRH-7TF/7F/iTF/iF:pvr1234567890:rvnSupermicro:rnX9DRH-7TF/7F/iTF/iF:rvr1234567890:cvnSupermicro:ct3:cvr1234567890:
  dmi.product.name: X9DRH-7TF/7F/iTF/iF
  dmi.product.version: 1234567890
  dmi.sys.vendor: Supermicro
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=7f36ec0c-c34b-4750-bd78-2c394cc513b2
  InstallationDate: Installed on 2016-05-11 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig:
   enp5s0f0  no wireless extensions.
   
   enp5s0f1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Supermicro X9DRH-7TF/7F/iTF/iF
  Package: linux (not installed)
  ProcFB: 

[Kernel-packages] [Bug 1646277] Re: Xenial server 16.04.x will have a black screen after PXE installation

[Joseph Salisbury]

Thanks for testing.  The kernel in -updates(4.4.0-59) now has the 4.4.35
updates.  Can you apply the latest updates without using -proposed and
confirm this bug is resolved?

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

Title:
  Xenial server 16.04.x will have a black screen after PXE installation

Status in debian-installer package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed
Status in debian-installer source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  The display will keep black screen after install 16.04.x via PXE(need
  use "Ctrl+Alt+F1" to change to terminal 1, then can see text mode
  screen)

  Quanta team is installing Xenial server using PXE boot.   After the
  installation, the console will show a black screen.   Hitting ctl-
  alt-f1 displays the text mode screen OK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1646277/+subscriptions

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

[Kernel-packages] [Bug 1654073] dev

[bugproxy]

Default Comment by Bridge

** Attachment added: "dev"
   https://bugs.launchpad.net/bugs/1654073/+attachment/4808232/+files/dev

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

Title:
  Ubuntu 17.04: machine crashes with Oops in dccp_v4_ctl_send_reset
  while running stress-ng.

Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH - 2016-12-28 03:39:50 ==
  ---Problem Description---

  Ubuntu 17.04: machine crashes with Oops while running stress-ng.

  ---Steps followed-

  1. Install 17.04 on NV machine.
  2. apt-get install stress-ng
  3. stress-ng -a 0

  Logs
  
  dccp af_alg joydev input_leds mac_hid at24 nvmem_core ofpart cmdlinepart 
powernv_flash mtd opal_prd powernv_rng ipmi_powernv ipmi_msghandler ibmpowernv 
uio_pdrv_genirq uio vmx_crypto ib_iser rdma_cm iw_cm ib_cm ib_core configfs 
iscsi_tcp libiscsi_tcp libiscsi scsi_tran[165938083361,3] OPAL: Trying a CPU 
re-init with flags: 0x1
  [166456504189,3] OPAL: CPU 0x29 not in OPAL !
  [167510150475,3] OPAL: Trying a CPU re-init with flags: 0x2
  [168022446397,3] OPAL: CPU 0x29 not in OPAL !
  sport_iscsi ip_tables x_tables autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath 
linear ses enclosure scsi_transport_sas hid_generic ast i2c_algo_bit ttm 
drm_kms_helper syscopyarea sysfillrect sysimgblt bnx2x fb_sys_fops drm aacraid 
tg3 usbhid uas hid usb_storage mdio ahci libcrc32c libahci crc32c_vpmsum
  [  237.047216] CPU: 33 PID: 34694 Comm: stress-ng-dccp Not tainted 
4.9.0-11-generic #12-Ubuntu
  [  237.047315] task: c03312a69400 task.stack: c03779698000
  [  237.047402] NIP: d0002e7b0a7c LR: d0002e7b21cc CTR: 
c0a0dd00
  [  237.047509] REGS: c03fff68f670 TRAP: 0300   Not tainted  
(4.9.0-11-generic)
  [  237.047613] MSR: 90010280b033 
[  237.049028]   CR: 24002282  XER: 
2000
  [  237.049103] CFAR: c0008a60 DAR: 02f4 DSISR: 4000 
SOFTE: 1 
  GPR00: d0002e7b21cc c03fff68f8f0 d0002e7bb670 0001 
  GPR04: c02b5dbdc400 c03c74c0a460 0474 c03c74c0a474 
  GPR08: c03c74c0a000  c0348cd25200  
  GPR12: 2200 c7b72900 c03fff68c000  
  GPR16:  0040 0001 2713 
  GPR20: cc84 017f 017f c13b2f00 
  GPR24: 0001 0001  0004 
  GPR28: c13b2f00 c03c74c0a474  c02b5dbdc400 
  NIP [d0002e7b0a7c] dccp_v4_ctl_send_reset+0xa4/0x2f0 [dccp_ipv4]
  [  237.051403] LR [d0002e7b21cc] dccp_v4_rcv+0x5d4/0x850 [dccp_ipv4]
  [  237.051486] Call Trace:
  [  237.051529] [c03fff68f8f0] [2713cc84] 0x2713cc84 (unreliable)
  [  237.051649] [c03fff68f970] [d0002e7b21cc] dccp_v4_rcv+0x5d4/0x850 
[dccp_ipv4]
  [  237.051779] [c03fff68fa50] [c0a01e40] 
ip_local_deliver_finish+0x170/0x350
  [  237.051932] [c03fff68faa0] [c0a0276c] 
ip_local_deliver+0x5c/0x130
  [  237.052038] [c03fff68fb10] [c0a02278] ip_rcv_finish+0x258/0x510
  [  237.052151] [c03fff68fba0] [c0a02b44] ip_rcv+0x304/0x420
  [  237.052263] [c03fff68fc30] [c09a28bc] 
__netif_receive_skb_core+0x97c/0xda0
  [  237.052388] [c03fff68fd10] [c09a7ab4] 
process_backlog+0xd4/0x1e0
  [  237.052489] [c03fff68fd80] [c09a6f0c] net_rx_action+0x35c/0x480
  [  237.052603] [c03fff68fe90] [c0b22a6c] __do_softirq+0x18c/0x3fc
  [  237.052726] [c03fff68ff90] [c0029fb0] call_do_softirq+0x14/0x24
  [  237.052848] [c0377969b920] [c001765c] 
do_softirq_own_stack+0x5c/0xa0
  [  237.052992] [c0377969b960] [c00cfd48] 
do_softirq.part.3+0x68/0x90
  [  237.053112] [c0377969b990] [c00cfe44] 
__local_bh_enable_ip+0xd4/0x100
  [  237.053240] [c0377969b9b0] [c0a06724] 
ip_finish_output2+0x244/0x460
  [  237.053372] [c0377969ba50] [c0a0977c] ip_output+0xcc/0x180
  [  237.053485] [c0377969bae0] [c0a08c78] ip_local_out+0x68/0x90
  [  237.053607] [c0377969bb20] [d00021966978] 
dccp_transmit_skb+0x320/0x550 [dccp]
  [  237.053739] [c0377969bb90] [d0002196732c] dccp_connect+0xf4/0x1f0 
[dccp]
  [  237.053890] [c0377969bc10] [d0002e7b0320] 
dccp_v4_connect+0x308/0x400 [dccp_ipv4]
  [  237.054213] [c0377969bc90] [c0a51678] 
__inet_stream_connect+0x158/0x400
  [  237.065276] [c0377969bd20] [c0a51978] 
inet_stream_connect+0x58/0x90
  [  237.074757] [c0377969bd60] [c097eeac] SyS_connect+0x10c/0x130
  [  237.092889] [c0377969be30] [c000bd84] 

[Kernel-packages] [Bug 1654073] rxskb

[bugproxy]

Default Comment by Bridge

** Attachment added: "rxskb"
   
https://bugs.launchpad.net/bugs/1654073/+attachment/4808230/+files/dccp_v4_ctl_send_reset.rxskb

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

Title:
  Ubuntu 17.04: machine crashes with Oops in dccp_v4_ctl_send_reset
  while running stress-ng.

Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH - 2016-12-28 03:39:50 ==
  ---Problem Description---

  Ubuntu 17.04: machine crashes with Oops while running stress-ng.

  ---Steps followed-

  1. Install 17.04 on NV machine.
  2. apt-get install stress-ng
  3. stress-ng -a 0

  Logs
  
  dccp af_alg joydev input_leds mac_hid at24 nvmem_core ofpart cmdlinepart 
powernv_flash mtd opal_prd powernv_rng ipmi_powernv ipmi_msghandler ibmpowernv 
uio_pdrv_genirq uio vmx_crypto ib_iser rdma_cm iw_cm ib_cm ib_core configfs 
iscsi_tcp libiscsi_tcp libiscsi scsi_tran[165938083361,3] OPAL: Trying a CPU 
re-init with flags: 0x1
  [166456504189,3] OPAL: CPU 0x29 not in OPAL !
  [167510150475,3] OPAL: Trying a CPU re-init with flags: 0x2
  [168022446397,3] OPAL: CPU 0x29 not in OPAL !
  sport_iscsi ip_tables x_tables autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath 
linear ses enclosure scsi_transport_sas hid_generic ast i2c_algo_bit ttm 
drm_kms_helper syscopyarea sysfillrect sysimgblt bnx2x fb_sys_fops drm aacraid 
tg3 usbhid uas hid usb_storage mdio ahci libcrc32c libahci crc32c_vpmsum
  [  237.047216] CPU: 33 PID: 34694 Comm: stress-ng-dccp Not tainted 
4.9.0-11-generic #12-Ubuntu
  [  237.047315] task: c03312a69400 task.stack: c03779698000
  [  237.047402] NIP: d0002e7b0a7c LR: d0002e7b21cc CTR: 
c0a0dd00
  [  237.047509] REGS: c03fff68f670 TRAP: 0300   Not tainted  
(4.9.0-11-generic)
  [  237.047613] MSR: 90010280b033 
[  237.049028]   CR: 24002282  XER: 
2000
  [  237.049103] CFAR: c0008a60 DAR: 02f4 DSISR: 4000 
SOFTE: 1 
  GPR00: d0002e7b21cc c03fff68f8f0 d0002e7bb670 0001 
  GPR04: c02b5dbdc400 c03c74c0a460 0474 c03c74c0a474 
  GPR08: c03c74c0a000  c0348cd25200  
  GPR12: 2200 c7b72900 c03fff68c000  
  GPR16:  0040 0001 2713 
  GPR20: cc84 017f 017f c13b2f00 
  GPR24: 0001 0001  0004 
  GPR28: c13b2f00 c03c74c0a474  c02b5dbdc400 
  NIP [d0002e7b0a7c] dccp_v4_ctl_send_reset+0xa4/0x2f0 [dccp_ipv4]
  [  237.051403] LR [d0002e7b21cc] dccp_v4_rcv+0x5d4/0x850 [dccp_ipv4]
  [  237.051486] Call Trace:
  [  237.051529] [c03fff68f8f0] [2713cc84] 0x2713cc84 (unreliable)
  [  237.051649] [c03fff68f970] [d0002e7b21cc] dccp_v4_rcv+0x5d4/0x850 
[dccp_ipv4]
  [  237.051779] [c03fff68fa50] [c0a01e40] 
ip_local_deliver_finish+0x170/0x350
  [  237.051932] [c03fff68faa0] [c0a0276c] 
ip_local_deliver+0x5c/0x130
  [  237.052038] [c03fff68fb10] [c0a02278] ip_rcv_finish+0x258/0x510
  [  237.052151] [c03fff68fba0] [c0a02b44] ip_rcv+0x304/0x420
  [  237.052263] [c03fff68fc30] [c09a28bc] 
__netif_receive_skb_core+0x97c/0xda0
  [  237.052388] [c03fff68fd10] [c09a7ab4] 
process_backlog+0xd4/0x1e0
  [  237.052489] [c03fff68fd80] [c09a6f0c] net_rx_action+0x35c/0x480
  [  237.052603] [c03fff68fe90] [c0b22a6c] __do_softirq+0x18c/0x3fc
  [  237.052726] [c03fff68ff90] [c0029fb0] call_do_softirq+0x14/0x24
  [  237.052848] [c0377969b920] [c001765c] 
do_softirq_own_stack+0x5c/0xa0
  [  237.052992] [c0377969b960] [c00cfd48] 
do_softirq.part.3+0x68/0x90
  [  237.053112] [c0377969b990] [c00cfe44] 
__local_bh_enable_ip+0xd4/0x100
  [  237.053240] [c0377969b9b0] [c0a06724] 
ip_finish_output2+0x244/0x460
  [  237.053372] [c0377969ba50] [c0a0977c] ip_output+0xcc/0x180
  [  237.053485] [c0377969bae0] [c0a08c78] ip_local_out+0x68/0x90
  [  237.053607] [c0377969bb20] [d00021966978] 
dccp_transmit_skb+0x320/0x550 [dccp]
  [  237.053739] [c0377969bb90] [d0002196732c] dccp_connect+0xf4/0x1f0 
[dccp]
  [  237.053890] [c0377969bc10] [d0002e7b0320] 
dccp_v4_connect+0x308/0x400 [dccp_ipv4]
  [  237.054213] [c0377969bc90] [c0a51678] 
__inet_stream_connect+0x158/0x400
  [  237.065276] [c0377969bd20] [c0a51978] 
inet_stream_connect+0x58/0x90
  [  237.074757] [c0377969bd60] [c097eeac] SyS_connect+0x10c/0x130
  [  237.092889] [c0377969be30] 

[Kernel-packages] [Bug 1654073] net

[bugproxy]

Default Comment by Bridge

** Attachment added: "net"
   https://bugs.launchpad.net/bugs/1654073/+attachment/4808231/+files/net

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

Title:
  Ubuntu 17.04: machine crashes with Oops in dccp_v4_ctl_send_reset
  while running stress-ng.

Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH - 2016-12-28 03:39:50 ==
  ---Problem Description---

  Ubuntu 17.04: machine crashes with Oops while running stress-ng.

  ---Steps followed-

  1. Install 17.04 on NV machine.
  2. apt-get install stress-ng
  3. stress-ng -a 0

  Logs
  
  dccp af_alg joydev input_leds mac_hid at24 nvmem_core ofpart cmdlinepart 
powernv_flash mtd opal_prd powernv_rng ipmi_powernv ipmi_msghandler ibmpowernv 
uio_pdrv_genirq uio vmx_crypto ib_iser rdma_cm iw_cm ib_cm ib_core configfs 
iscsi_tcp libiscsi_tcp libiscsi scsi_tran[165938083361,3] OPAL: Trying a CPU 
re-init with flags: 0x1
  [166456504189,3] OPAL: CPU 0x29 not in OPAL !
  [167510150475,3] OPAL: Trying a CPU re-init with flags: 0x2
  [168022446397,3] OPAL: CPU 0x29 not in OPAL !
  sport_iscsi ip_tables x_tables autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath 
linear ses enclosure scsi_transport_sas hid_generic ast i2c_algo_bit ttm 
drm_kms_helper syscopyarea sysfillrect sysimgblt bnx2x fb_sys_fops drm aacraid 
tg3 usbhid uas hid usb_storage mdio ahci libcrc32c libahci crc32c_vpmsum
  [  237.047216] CPU: 33 PID: 34694 Comm: stress-ng-dccp Not tainted 
4.9.0-11-generic #12-Ubuntu
  [  237.047315] task: c03312a69400 task.stack: c03779698000
  [  237.047402] NIP: d0002e7b0a7c LR: d0002e7b21cc CTR: 
c0a0dd00
  [  237.047509] REGS: c03fff68f670 TRAP: 0300   Not tainted  
(4.9.0-11-generic)
  [  237.047613] MSR: 90010280b033 
[  237.049028]   CR: 24002282  XER: 
2000
  [  237.049103] CFAR: c0008a60 DAR: 02f4 DSISR: 4000 
SOFTE: 1 
  GPR00: d0002e7b21cc c03fff68f8f0 d0002e7bb670 0001 
  GPR04: c02b5dbdc400 c03c74c0a460 0474 c03c74c0a474 
  GPR08: c03c74c0a000  c0348cd25200  
  GPR12: 2200 c7b72900 c03fff68c000  
  GPR16:  0040 0001 2713 
  GPR20: cc84 017f 017f c13b2f00 
  GPR24: 0001 0001  0004 
  GPR28: c13b2f00 c03c74c0a474  c02b5dbdc400 
  NIP [d0002e7b0a7c] dccp_v4_ctl_send_reset+0xa4/0x2f0 [dccp_ipv4]
  [  237.051403] LR [d0002e7b21cc] dccp_v4_rcv+0x5d4/0x850 [dccp_ipv4]
  [  237.051486] Call Trace:
  [  237.051529] [c03fff68f8f0] [2713cc84] 0x2713cc84 (unreliable)
  [  237.051649] [c03fff68f970] [d0002e7b21cc] dccp_v4_rcv+0x5d4/0x850 
[dccp_ipv4]
  [  237.051779] [c03fff68fa50] [c0a01e40] 
ip_local_deliver_finish+0x170/0x350
  [  237.051932] [c03fff68faa0] [c0a0276c] 
ip_local_deliver+0x5c/0x130
  [  237.052038] [c03fff68fb10] [c0a02278] ip_rcv_finish+0x258/0x510
  [  237.052151] [c03fff68fba0] [c0a02b44] ip_rcv+0x304/0x420
  [  237.052263] [c03fff68fc30] [c09a28bc] 
__netif_receive_skb_core+0x97c/0xda0
  [  237.052388] [c03fff68fd10] [c09a7ab4] 
process_backlog+0xd4/0x1e0
  [  237.052489] [c03fff68fd80] [c09a6f0c] net_rx_action+0x35c/0x480
  [  237.052603] [c03fff68fe90] [c0b22a6c] __do_softirq+0x18c/0x3fc
  [  237.052726] [c03fff68ff90] [c0029fb0] call_do_softirq+0x14/0x24
  [  237.052848] [c0377969b920] [c001765c] 
do_softirq_own_stack+0x5c/0xa0
  [  237.052992] [c0377969b960] [c00cfd48] 
do_softirq.part.3+0x68/0x90
  [  237.053112] [c0377969b990] [c00cfe44] 
__local_bh_enable_ip+0xd4/0x100
  [  237.053240] [c0377969b9b0] [c0a06724] 
ip_finish_output2+0x244/0x460
  [  237.053372] [c0377969ba50] [c0a0977c] ip_output+0xcc/0x180
  [  237.053485] [c0377969bae0] [c0a08c78] ip_local_out+0x68/0x90
  [  237.053607] [c0377969bb20] [d00021966978] 
dccp_transmit_skb+0x320/0x550 [dccp]
  [  237.053739] [c0377969bb90] [d0002196732c] dccp_connect+0xf4/0x1f0 
[dccp]
  [  237.053890] [c0377969bc10] [d0002e7b0320] 
dccp_v4_connect+0x308/0x400 [dccp_ipv4]
  [  237.054213] [c0377969bc90] [c0a51678] 
__inet_stream_connect+0x158/0x400
  [  237.065276] [c0377969bd20] [c0a51978] 
inet_stream_connect+0x58/0x90
  [  237.074757] [c0377969bd60] [c097eeac] SyS_connect+0x10c/0x130
  [  237.092889] [c0377969be30] [c000bd84] 

[Kernel-packages] [Bug 1654073] sosreport from ltc-haba2

[bugproxy]

Default Comment by Bridge

** Attachment added: "sosreport from ltc-haba2"
   
https://bugs.launchpad.net/bugs/1654073/+attachment/4808229/+files/sosreport-pole1lp2.150073-20161221155014.tar.xz

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

Title:
  Ubuntu 17.04: machine crashes with Oops in dccp_v4_ctl_send_reset
  while running stress-ng.

Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH - 2016-12-28 03:39:50 ==
  ---Problem Description---

  Ubuntu 17.04: machine crashes with Oops while running stress-ng.

  ---Steps followed-

  1. Install 17.04 on NV machine.
  2. apt-get install stress-ng
  3. stress-ng -a 0

  Logs
  
  dccp af_alg joydev input_leds mac_hid at24 nvmem_core ofpart cmdlinepart 
powernv_flash mtd opal_prd powernv_rng ipmi_powernv ipmi_msghandler ibmpowernv 
uio_pdrv_genirq uio vmx_crypto ib_iser rdma_cm iw_cm ib_cm ib_core configfs 
iscsi_tcp libiscsi_tcp libiscsi scsi_tran[165938083361,3] OPAL: Trying a CPU 
re-init with flags: 0x1
  [166456504189,3] OPAL: CPU 0x29 not in OPAL !
  [167510150475,3] OPAL: Trying a CPU re-init with flags: 0x2
  [168022446397,3] OPAL: CPU 0x29 not in OPAL !
  sport_iscsi ip_tables x_tables autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath 
linear ses enclosure scsi_transport_sas hid_generic ast i2c_algo_bit ttm 
drm_kms_helper syscopyarea sysfillrect sysimgblt bnx2x fb_sys_fops drm aacraid 
tg3 usbhid uas hid usb_storage mdio ahci libcrc32c libahci crc32c_vpmsum
  [  237.047216] CPU: 33 PID: 34694 Comm: stress-ng-dccp Not tainted 
4.9.0-11-generic #12-Ubuntu
  [  237.047315] task: c03312a69400 task.stack: c03779698000
  [  237.047402] NIP: d0002e7b0a7c LR: d0002e7b21cc CTR: 
c0a0dd00
  [  237.047509] REGS: c03fff68f670 TRAP: 0300   Not tainted  
(4.9.0-11-generic)
  [  237.047613] MSR: 90010280b033 
[  237.049028]   CR: 24002282  XER: 
2000
  [  237.049103] CFAR: c0008a60 DAR: 02f4 DSISR: 4000 
SOFTE: 1 
  GPR00: d0002e7b21cc c03fff68f8f0 d0002e7bb670 0001 
  GPR04: c02b5dbdc400 c03c74c0a460 0474 c03c74c0a474 
  GPR08: c03c74c0a000  c0348cd25200  
  GPR12: 2200 c7b72900 c03fff68c000  
  GPR16:  0040 0001 2713 
  GPR20: cc84 017f 017f c13b2f00 
  GPR24: 0001 0001  0004 
  GPR28: c13b2f00 c03c74c0a474  c02b5dbdc400 
  NIP [d0002e7b0a7c] dccp_v4_ctl_send_reset+0xa4/0x2f0 [dccp_ipv4]
  [  237.051403] LR [d0002e7b21cc] dccp_v4_rcv+0x5d4/0x850 [dccp_ipv4]
  [  237.051486] Call Trace:
  [  237.051529] [c03fff68f8f0] [2713cc84] 0x2713cc84 (unreliable)
  [  237.051649] [c03fff68f970] [d0002e7b21cc] dccp_v4_rcv+0x5d4/0x850 
[dccp_ipv4]
  [  237.051779] [c03fff68fa50] [c0a01e40] 
ip_local_deliver_finish+0x170/0x350
  [  237.051932] [c03fff68faa0] [c0a0276c] 
ip_local_deliver+0x5c/0x130
  [  237.052038] [c03fff68fb10] [c0a02278] ip_rcv_finish+0x258/0x510
  [  237.052151] [c03fff68fba0] [c0a02b44] ip_rcv+0x304/0x420
  [  237.052263] [c03fff68fc30] [c09a28bc] 
__netif_receive_skb_core+0x97c/0xda0
  [  237.052388] [c03fff68fd10] [c09a7ab4] 
process_backlog+0xd4/0x1e0
  [  237.052489] [c03fff68fd80] [c09a6f0c] net_rx_action+0x35c/0x480
  [  237.052603] [c03fff68fe90] [c0b22a6c] __do_softirq+0x18c/0x3fc
  [  237.052726] [c03fff68ff90] [c0029fb0] call_do_softirq+0x14/0x24
  [  237.052848] [c0377969b920] [c001765c] 
do_softirq_own_stack+0x5c/0xa0
  [  237.052992] [c0377969b960] [c00cfd48] 
do_softirq.part.3+0x68/0x90
  [  237.053112] [c0377969b990] [c00cfe44] 
__local_bh_enable_ip+0xd4/0x100
  [  237.053240] [c0377969b9b0] [c0a06724] 
ip_finish_output2+0x244/0x460
  [  237.053372] [c0377969ba50] [c0a0977c] ip_output+0xcc/0x180
  [  237.053485] [c0377969bae0] [c0a08c78] ip_local_out+0x68/0x90
  [  237.053607] [c0377969bb20] [d00021966978] 
dccp_transmit_skb+0x320/0x550 [dccp]
  [  237.053739] [c0377969bb90] [d0002196732c] dccp_connect+0xf4/0x1f0 
[dccp]
  [  237.053890] [c0377969bc10] [d0002e7b0320] 
dccp_v4_connect+0x308/0x400 [dccp_ipv4]
  [  237.054213] [c0377969bc90] [c0a51678] 
__inet_stream_connect+0x158/0x400
  [  237.065276] [c0377969bd20] [c0a51978] 
inet_stream_connect+0x58/0x90
  [  237.074757] [c0377969bd60] [c097eeac] SyS_connect+0x10c/0x130
  [  

Re: [Kernel-packages] [Bug 1658345] Re: Touchpad not recognized on Lenovo Ideapad Flex 4 running Ubuntu 16.10

[Keary Parinis]

I was never able to get Ubuntu to recognize the touchpad. This is a new
laptop. Last week, I tried the latest upstream version 17.10 with the same
result. Is there a new version this week?

On Monday, January 23, 2017, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:

> Did this issue start happening after an update/upgrade?  Was there a
> prior kernel version where you were not having this particular problem?
>
> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
> v4.10 kernel[0].
>
> If this bug is fixed in the mainline kernel, please add the following
> tag 'kernel-fixed-upstream'.
>
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-bug-exists-upstream'.
>
> Once testing of the upstream kernel is complete, please mark this bug as
> "Confirmed".
>
>
> Thanks in advance.
>
> [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc5
>
> ** Changed in: linux (Ubuntu)
>Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
>Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1658345
>
> Title:
>   Touchpad not recognized on Lenovo Ideapad Flex 4 running Ubuntu 16.10
>
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I installed Ubuntu 16.10 on my Lenovo Ideapad Flex 4 laptop. Ubuntu does
> not recognize the touchpad (it does recognize the touch screen nicely
> though). When I run xinput -list, I do not see the touchpad. I dual boot
> with Windows 10, which recognizes the touchpad from Elantech. I searched
> online for days and I found Elantech drivers for Ubuntu 14.04, however, I
> was unable to load older versions of Ubuntu on my laptop. Do you expect to
> support the Elantech touchpad in future updates? I attached a screen shot
> of my xinput -list output. Please let me know if you require any additional
> information. Thank you.
>   ---
>   ApportVersion: 2.20.3-0ubuntu8.2
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  keary  2345 F pulseaudio
>   DistroRelease: Ubuntu 16.10
>   HibernationDevice: RESUME=UUID=dbfec3b4-a8be-406e-9f39-5258c004c656
>   InstallationDate: Installed on 2017-01-18 (2 days ago)
>   InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64
> (20161012.2)
>   Lsusb:
>Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>Bus 001 Device 003: ID 0bda:57fc Realtek Semiconductor Corp.
>Bus 001 Device 002: ID 0cf3:e500 Atheros Communications, Inc.
>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>   MachineType: LENOVO 80U3
>   Package: linux (not installed)
>   ProcEnviron:
>LANGUAGE=en_US
>TERM=xterm-256color
>PATH=(custom, no user)
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic.efi.signed
> root=UUID=5be7438e-36fd-4960-a4cd-2371715adfa2 ro quiet splash
> i8042.kbdreset=1 vt.handoff=7
>   ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
>   PulseList:
>Error: command ['pacmd', 'list'] failed with exit code 1: Home
> directory not accessible: Permission denied
>No PulseAudio daemon running, or not running as session daemon.
>   RelatedPackageVersions:
>linux-restricted-modules-4.8.0-34-generic N/A
>linux-backports-modules-4.8.0-34-generic  N/A
>linux-firmware1.161.1
>   Tags:  yakkety
>   Uname: Linux 4.8.0-34-generic x86_64
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups:
>
>   _MarkForUpload: True
>   dmi.bios.date: 11/01/2016
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: 2MCN24WW
>   dmi.board.asset.tag: No Asset Tag
>   dmi.board.name: Sofia-F
>   dmi.board.vendor: LENOVO
>   dmi.board.version: SDK0J91204WIN
>   dmi.chassis.asset.tag: No Asset Tag
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: Lenovo ideapad FLEX 4-1130
>   dmi.modalias: dmi:bvnLENOVO:bvr2MCN24WW:bd11/01/2016:svnLENOVO:pn80U3:
> pvrLenovoideapadFLEX4-1130:rvnLENOVO:rnSofia-F:rvrSDK0J91204WIN:cvnLENOVO:
> ct10:cvrLenovoideapadFLEX4-1130:
>   dmi.product.name: 80U3
>   dmi.product.version: Lenovo ideapad FLEX 4-1130
>   dmi.sys.vendor: LENOVO
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1658345/+subscriptions
>

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

Title:
  Touchpad not recognized on Lenovo Ideapad Flex 4 running Ubuntu 16.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I installed Ubuntu 16.10 on my Lenovo Ideapad Flex 4 laptop. Ubuntu does not 
recognize the touchpad (it does 

[Kernel-packages] [Bug 1658606] Re: Alsa-lib 1.1.3-1 puls in python2.7 (Zesty dev)

[Harry]

This bug is solved with the version 1.1.3-2.

** Changed in: alsa-lib (Ubuntu)
   Status: New => Fix Released

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

Title:
  Alsa-lib 1.1.3-1 puls in python2.7 (Zesty dev)

Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-lib package in Debian:
  New

Bug description:
  The newest alsa-lib (package libasound2) in Zesty Zapus (v. 1.1.3-1) puls in 
python2.7.
  Package libasound2 depends on libpython2.7 (>= 2.7).
  Earlier version did not depend on python2.7, so this is a new feature.
  However, the aim was to get rid of puthon2.7 (transition to pyhton3) in the 
official ubuntu content.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1658606/+subscriptions

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

[Kernel-packages] [Bug 1658270] Re: Backport Dirty COW patch to prevent wineserver freeze

[Joseph Salisbury]

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

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

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

Title:
  Backport Dirty COW patch to prevent wineserver freeze

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

Bug description:
  A few kernels updates ago (after kernel 3.13.0-98) on 14.04 (Trusty) a
  backported fix for Dirty COW from kernel 4.8.3 resulted in some Delphi
  apps freezing wineserver and leaving it unkillable:

  https://bugs.winehq.org/show_bug.cgi?id=41637

  I haven't tested for the bug on 16.04 Xenial (kernel 4.4.0-59) but it
  is probably affected.  A patch is available:

  https://lkml.org/lkml/2017/1/5/13
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jhansonxi   2775 F pulseaudio
   /dev/snd/controlC2:  jhansonxi   2775 F pulseaudio
   /dev/snd/controlC0:  jhansonxi   2775 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=6c1d3a04-0529-476c-b193-3e584c0333ca
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic 
root=/dev/mapper/vg0-lv1 ro quiet nosplash
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-59-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: dialout
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1206
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M3A78-EM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1206:bd11/26/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3A78-EM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1657994] Re: Regression: HDMI audio produces no sound (Skylake NUC)

[Joseph Salisbury]

I'd like to perform a bisect to figure out what commit caused this
regression. We need to identify the earliest kernel where the issue
started happening as well as the latest kernel that did not have this
issue.

Can you test the following kernels and report back? We are looking for
the first kernel version that exhibits this bug:

4.5 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-wily/
4.6 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/
4.7 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7/
4.8-rc1:  http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc1/


You don't have to test every kernel, just up until the kernel that first
has this bug.

Thanks in advance!

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

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

Title:
  Regression:  HDMI audio produces no sound (Skylake NUC)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrade from Xenial 16.04 to Yakkety 16.10, playing audio over HDMI no 
longer produces sound.
  * When booting with old kernel from Xenial (4.4.0-59), HDMI audio works fine
  * Audio from headphone jack works fine
  * Userspace seems to be happily playing to HDMI audio device, but no sound 
produced at HDMI sink (Samsung TV)

  Any of a wide range of pre-built mainline kernels fail to produce HDMI
  audio, but with a different failure mode (HDMI audio does not seem to
  be enumerated in the same way as in the Ubuntu kernels.)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-34-generic 4.8.0-34.36
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  israel 1973 F pulseaudio
   /dev/snd/controlC1:  israel 1973 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jan 20 08:58:35 2017
  HibernationDevice: RESUME=UUID=ca27f739-071f-4c25-974e-0d0f0614b21c
  InstallationDate: Installed on 2016-10-03 (108 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic.efi.signed 
root=UUID=90c3e094-e890-4c35-a0d2-0a358f5d2430 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-34-generic N/A
   linux-backports-modules-4.8.0-34-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2017-01-13 (6 days ago)
  dmi.bios.date: 06/03/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: KYSKLi70.86A.0037.2016.0603.1032
  dmi.board.name: NUC6i7KYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H90766-405
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrKYSKLi70.86A.0037.2016.0603.1032:bd06/03/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-405:cvnIntelCorporation:ct3:cvr1.0:

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

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

[Kernel-packages] [Bug 1658355] Re: Problem loading in-kernel X.509 certificate (-74)

[Joseph Salisbury]

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

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

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

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

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


Thanks in advance.

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

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

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1658355

Title:
  Problem loading in-kernel X.509 certificate (-74)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I cant run VirtualBox
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  user   2888 F pulseaudio
   /dev/snd/controlC0:  user   2888 F pulseaudio
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=256288a7-6a40-4af8-8fc3-819b998a0188
  InstallationDate: Installed on 2016-08-07 (167 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20309
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed 
root=UUID=10d4651e-5cae-4aea-85eb-7a4744e5b7d6 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  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-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  Tags:  xenial
  Uname: Linux 4.4.0-59-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/13/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8ACN34WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Strawberry 5D
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058Std
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Ideapad Flex 15
  dmi.modalias: 
dmi:bvnLENOVO:bvr8ACN34WW:bd02/13/2014:svnLENOVO:pn20309:pvrLenovoIdeapadFlex15:rvnLENOVO:rnStrawberry5D:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoIdeapadFlex15:
  dmi.product.name: 20309
  dmi.product.version: Lenovo Ideapad Flex 15
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1658345] Re: Touchpad not recognized on Lenovo Ideapad Flex 4 running Ubuntu 16.10

[Joseph Salisbury]

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

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

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

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

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


Thanks in advance.

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

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

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

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

Title:
  Touchpad not recognized on Lenovo Ideapad Flex 4 running Ubuntu 16.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I installed Ubuntu 16.10 on my Lenovo Ideapad Flex 4 laptop. Ubuntu does not 
recognize the touchpad (it does recognize the touch screen nicely though). When 
I run xinput -list, I do not see the touchpad. I dual boot with Windows 10, 
which recognizes the touchpad from Elantech. I searched online for days and I 
found Elantech drivers for Ubuntu 14.04, however, I was unable to load older 
versions of Ubuntu on my laptop. Do you expect to support the Elantech touchpad 
in future updates? I attached a screen shot of my xinput -list output. Please 
let me know if you require any additional information. Thank you.
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  keary  2345 F pulseaudio
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=dbfec3b4-a8be-406e-9f39-5258c004c656
  InstallationDate: Installed on 2017-01-18 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:57fc Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0cf3:e500 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80U3
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic.efi.signed 
root=UUID=5be7438e-36fd-4960-a4cd-2371715adfa2 ro quiet splash i8042.kbdreset=1 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-34-generic N/A
   linux-backports-modules-4.8.0-34-generic  N/A
   linux-firmware1.161.1
  Tags:  yakkety
  Uname: Linux 4.8.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 2MCN24WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Sofia-F
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J91204WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad FLEX 4-1130
  dmi.modalias: 
dmi:bvnLENOVO:bvr2MCN24WW:bd11/01/2016:svnLENOVO:pn80U3:pvrLenovoideapadFLEX4-1130:rvnLENOVO:rnSofia-F:rvrSDK0J91204WIN:cvnLENOVO:ct10:cvrLenovoideapadFLEX4-1130:
  dmi.product.name: 80U3
  dmi.product.version: Lenovo ideapad FLEX 4-1130
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1626894] Re: nvme drive probe failure

[Gerd Peter]

i does not work with the stock kernel, I work with a patched kernel.
(https://forum.proxmox.com/threads/nvme-storage-issue.31572/page-2#post-159444)

my first results, only Only a few hours old, Are up to now good:
(a skylake Fujitsu D3417-B Mainboard with Intel C236 Chipset)

only one Line in dmesg:
# dmesg | grep -i nvme
[0.893264]  nvme0n1: p1 p2 p3

and up to now no errors

this is the part from lspci -v
...
01:00.0 Non-Volatile memory controller: Silicon Motion, Inc. Device 2260 (rev 
03) (prog-if 02 [NVM Express])
Subsystem: Silicon Motion, Inc. Device 2260
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at f701 (64-bit, non-prefetchable) [size=16K]
Expansion ROM at f700 [disabled] [size=64K]
Capabilities: [40] Power Management version 3
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [b0] MSI-X: Enable+ Count=16 Masked-
Capabilities: [100] Advanced Error Reporting
Capabilities: [158] #19
Capabilities: [178] Latency Tolerance Reporting
Capabilities: [180] L1 PM Substates
Kernel driver in use: nvme

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

Title:
  nvme drive probe failure

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

Bug description:
  After upgrading from linux-image-4.4.0-38-generic to proposed update
  linux-image-4.4.0-39-generic, NVMe drives are no longer working. dmesg
  shows a probe failure.

  On the previous kernel version everything is working as expected.
  ->%-
  [1.005243] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 
R1.12.0.SR.2 for D3417-B1x   04/01/2016
  [1.005349] Workqueue: events nvme_remove_dead_ctrl_work [nvme]
  [1.005484]  0286 b6c91251 880fe6e8bce0 
813f1f83
  [1.005800]  880fe02150f0 c90006a7c000 880fe6e8bd00 
8106bdff
  [1.006117]  880fe02150f0 880fe0215258 880fe6e8bd10 
8106be3c
  [1.006433] Call Trace:
  [1.006509]  [] dump_stack+0x63/0x90
  [1.006589]  [] iounmap.part.1+0x7f/0x90
  [1.006668]  [] iounmap+0x2c/0x30
  [1.006770]  [] nvme_dev_unmap.isra.35+0x1a/0x30 [nvme]
  [1.007048]  [] nvme_remove+0xce/0xe0 [nvme]
  [1.007140]  [] pci_device_remove+0x39/0xc0
  [1.007220]  [] __device_release_driver+0xa1/0x150
  [1.007301]  [] device_release_driver+0x23/0x30
  [1.007382]  [] pci_stop_bus_device+0x8a/0xa0
  [1.007462]  [] 
pci_stop_and_remove_bus_device_locked+0x1a/0x30
  [1.007559]  [] nvme_remove_dead_ctrl_work+0x3c/0x50 
[nvme]
  [1.007642]  [] process_one_work+0x165/0x480
  [1.007722]  [] worker_thread+0x4b/0x4c0
  [1.007801]  [] ? process_one_work+0x480/0x480
  [1.007881]  [] kthread+0xd8/0xf0
  [1.007959]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [1.008041]  [] ret_from_fork+0x3f/0x70
  [1.008120]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [1.008222] Trying to free nonexistent resource 

  [1.008276] genirq: Flags mismatch irq 0. 0080 (nvme1q0) vs. 00015a00 
(timer)
  [1.008281] Trying to free nonexistent resource 

  [1.008282] nvme :02:00.0: Removing after probe failure
  [1.008645] Trying to free nonexistent resource 

  [1.027213] iounmap: bad address c90006ae
  [1.027456] CPU: 2 PID: 86 Comm: kworker/2:1 Not tainted 4.4.0-39-generic 
#59-Ubuntu
  -%<-

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

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

[Kernel-packages] [Bug 1657907] Re: 555-BCOE Killer 1535 802.11ac 2x2 WiFi/Bluetooth: firmware crashes

[Joseph Salisbury]

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

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

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

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

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


Thanks in advance.

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

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

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

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

Title:
  555-BCOE Killer 1535 802.11ac 2x2 WiFi/Bluetooth: firmware crashes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Every not too often, my wifi adapter/driver/firmware seems to crash.

  Here is the most recent one, entry in `dmesg`:

  [20634.804968] ath10k_pci :3a:00.0: firmware crashed! (uuid 
a373e5e5-e4a9-4391-b091-f6c7b58f9f73)
  [20634.804985] ath10k_pci :3a:00.0: qca6174 hw3.2 target 0x0503 
chip_id 0x00340aff sub 1a56:1535
  [20634.804989] ath10k_pci :3a:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [20634.805896] ath10k_pci :3a:00.0: firmware ver 
WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad 
crc32 75dee6c5
  [20634.806401] ath10k_pci :3a:00.0: board_file api 2 bmi_id N/A crc32 
6fc88fe7
  [20634.806415] ath10k_pci :3a:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 cal 
otp max-sta 32 raw 0 hwcrypto 1
  [20634.808476] ath10k_pci :3a:00.0: firmware register dump:
  [20634.808486] ath10k_pci :3a:00.0: [00]: 0x0503 0x15B3 
0x009860FA 0x00955B31
  [20634.808492] ath10k_pci :3a:00.0: [04]: 0x009860FA 0x00060730 
0x0004 0x0040E8A0
  [20634.808497] ath10k_pci :3a:00.0: [08]: 0x00498110 0x00955A00 
0x000B 0x0040
  [20634.808502] ath10k_pci :3a:00.0: [12]: 0x0009 0x 
0x00952CD0 0x00952CE6
  [20634.808507] ath10k_pci :3a:00.0: [16]: 0x00952CC4 0x00910712 
0x 0x0091080D
  [20634.808513] ath10k_pci :3a:00.0: [20]: 0x409860FA 0x0040E7E8 
0x 0x0041E0DC
  [20634.808518] ath10k_pci :3a:00.0: [24]: 0x800B5A1D 0x0040E848 
0x000F 0xC09860FA
  [20634.808523] ath10k_pci :3a:00.0: [28]: 0x809B3230 0x0040E948 
0x0018 0x004313B8
  [20634.808528] ath10k_pci :3a:00.0: [32]: 0x809B2992 0x0040E998 
0x0040E9C0 0x00429548
  [20634.808533] ath10k_pci :3a:00.0: [36]: 0x8091D252 0x0040E9B8 
0x 0x0002
  [20634.808538] ath10k_pci :3a:00.0: [40]: 0x809FF05D 0x0040EA68 
0x0043A380 0x00429C10
  [20634.808543] ath10k_pci :3a:00.0: [44]: 0x809FCFDB 0x0040EA88 
0x0043A380 0x0001
  [20634.808548] ath10k_pci :3a:00.0: [48]: 0x80911210 0x0040EAD8 
0x0010 0x004041D0
  [20634.808553] ath10k_pci :3a:00.0: [52]: 0x80911154 0x0040EB28 
0x0040 0x
  [20634.808558] ath10k_pci :3a:00.0: [56]: 0x8091122D 0x0040EB48 
0x 0x00400600
  [20634.911972] ieee80211 phy0: Hardware restart was requested

  The system does recover, at least partially, but system feels laggy. Might be 
subjective.
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ruud   2685 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=2f2d2c45-4fef-49ec-932a-8314b15c2f6b
  InstallationDate: Installed on 2016-11-08 (74 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. XPS 13 9360
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-34-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-34-generic N/A
   linux-backports-modules-4.8.0-34-generic  N/A
   linux-firmware1.161.1
  Tags:  yakkety
  Uname: Linux 4.8.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 09/13/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.7
  dmi.board.name: 0T3FTF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd09/13/2016:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 

[Kernel-packages] [Bug 1658621] Re: Touchpad is not detected in Acer Aspire One AO756-2626

[Joseph Salisbury]

Does this bug go away if you boot back into the prior kernel version?

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

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

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

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


Thanks in advance.

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


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

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

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

Title:
  Touchpad is not detected in Acer Aspire One AO756-2626

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After most recent update to kernel, my touchpad is not recognised and
  does not appear as an input device in cat /proc/bus/input/devices

  An external USB mouse is working correctly (cursor, buttons and scroll
  wheel)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  josh   1777 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jan 23 09:12:32 2017
  HibernationDevice: RESUME=UUID=9aee6652-765c-4b42-9ffd-9370a0d95ca1
  MachineType: Acer AO756
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=a872dd55-2af1-4efd-b447-ec434bff8dcf ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-08-30 (146 days ago)
  dmi.bios.date: 11/06/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.08
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Mimic
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.08
  dmi.modalias: 
dmi:bvnAcer:bvrV2.08:bd11/06/2012:svnAcer:pnAO756:pvrV2.08:rvnAcer:rnMimic:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.08:
  dmi.product.name: AO756
  dmi.product.version: V2.08
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1644716] Re: cpufreq-set --freq option is not able to set the specific frequency value

[Manoj Iyer]

This package is supported by the community, it would require a community
effort to resolve this issue.

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

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

** No longer affects: 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/1644716

Title:
  cpufreq-set --freq option is not able to set the specific frequency
  value

Status in cpufrequtils package in Ubuntu:
  New

Bug description:
  == Comment: #0 - PAVAMAN SUBRAMANIYAM  - 2016-11-23 
03:27:34 ==
  ---Problem Description---
  cpufreq-set --freq option is not able to set the specific frequency value
   
  Contact Information = pavsu...@in.ibm.com 
   
  ---uname output---
  Linux ltc-garri2 4.8.0-27-generic #29-Ubuntu SMP Thu Oct 20 21:01:16 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = P8 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  Install a P8 Open Power Hardware with Ubuntu 16.10 OS.
  Then we are executing cpufreq-set which is a small tool which allows to 
modify cpufreq settings.

  
  root@ltc-garri2:~# cpufreq-info -c 0
  cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
  Report errors and bugs to cpuf...@vger.kernel.org, please.
  analyzing CPU 0:
driver: powernv-cpufreq
CPUs which run at the same hardware frequency: 0 1 2 3 4 5 6 7
CPUs which need to have their frequency coordinated by software: 0 1 2 3 4 
5 6 7
maximum transition latency: 4294.55 ms.
hardware limits: 2.06 GHz - 4.02 GHz
available frequency steps: 4.02 GHz, 3.99 GHz, 3.96 GHz, 3.92 GHz, 3.89 
GHz, 3.86 GHz, 3.82 GHz, 3.79 GHz, 3.76 GHz, 3.72 GHz, 3.69 GHz, 3.66 GHz, 3.62 
GHz, 3.59 GHz, 3.56 GHz, 3.52 GHz, 3.49 GHz, 3.46 GHz, 3.42 GHz, 3.39 GHz, 3.36 
GHz, 3.33 GHz, 3.29 GHz, 3.26 GHz, 3.23 GHz, 3.19 GHz, 3.16 GHz, 3.13 GHz, 3.09 
GHz, 3.06 GHz, 3.03 GHz, 2.99 GHz, 2.96 GHz, 2.93 GHz, 2.89 GHz, 2.86 GHz, 2.83 
GHz, 2.79 GHz, 2.76 GHz, 2.73 GHz, 2.69 GHz, 2.66 GHz, 2.63 GHz, 2.59 GHz, 2.56 
GHz, 2.53 GHz, 2.49 GHz, 2.46 GHz, 2.43 GHz, 2.39 GHz, 2.36 GHz, 2.33 GHz, 2.29 
GHz, 2.26 GHz, 2.23 GHz, 2.19 GHz, 2.16 GHz, 2.13 GHz, 2.09 GHz, 2.06 GHz
available cpufreq governors: conservative, ondemand, userspace, powersave, 
performance
current policy: frequency should be within 4.02 GHz and 4.02 GHz.
The governor "userspace" may decide which speed to use
within this range.
current CPU frequency is 4.02 GHz (asserted by call to hardware).
cpufreq stats: 4.02 GHz:100.00%, 3.99 GHz:0.00%, 3.96 GHz:0.00%, 3.92 
GHz:0.00%, 3.89 GHz:0.00%, 3.86 GHz:0.00%, 3.82 GHz:0.00%, 3.79 GHz:0.00%, 3.76 
GHz:0.00%, 3.72 GHz:0.00%, 3.69 GHz:0.00%, 3.66 GHz:0.00%, 3.62 GHz:0.00%, 3.59 
GHz:0.00%, 3.56 GHz:0.00%, 3.52 GHz:0.00%, 3.49 GHz:0.00%, 3.46 GHz:0.00%, 3.42 
GHz:0.00%, 3.39 GHz:0.00%, 3.36 GHz:0.00%, 3.33 GHz:0.00%, 3.29 GHz:0.00%, 3.26 
GHz:0.00%, 3.23 GHz:0.00%, 3.19 GHz:0.00%, 3.16 GHz:0.00%, 3.13 GHz:0.00%, 3.09 
GHz:0.00%, 3.06 GHz:0.00%, 3.03 GHz:0.00%, 2.99 GHz:0.00%, 2.96 GHz:0.00%, 2.93 
GHz:0.00%, 2.89 GHz:0.00%, 2.86 GHz:0.00%, 2.83 GHz:0.00%, 2.79 GHz:0.00%, 2.76 
GHz:0.00%, 2.73 GHz:0.00%, 2.69 GHz:0.00%, 2.66 GHz:0.00%, 2.63 GHz:0.00%, 2.59 
GHz:0.00%, 2.56 GHz:0.00%, 2.53 GHz:0.00%, 2.49 GHz:0.00%, 2.46 GHz:0.00%, 2.43 
GHz:0.00%, 2.39 GHz:0.00%, 2.36 GHz:0.00%, 2.33 GHz:0.00%, 2.29 GHz:0.00%, 2.26 
GHz:0.00%, 2.23 GHz:0.00%, 2.19 GHz:0.00%, 2.16 GHz:0.00%, 2.13 GHz:0.00%, 2.09 
GHz:0.00%, 2.06 GHz:0.00%  (12)

  Then try to  set the specific frequency to be set for cpu0.

  root@ltc-garri2:~# cpufreq-set -c 0 --freq 3.92GHz
  root@ltc-garri2:~# echo $?
  0

  root@ltc-garri2:~# cat 
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_nominal_freq
  3258000
  root@ltc-garri2:~# cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq
  2061000
  root@ltc-garri2:~# cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq
  4023000
  root@ltc-garri2:~# cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq
  4023000

  As can be seen the new frequency value is not getting set.
  The /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq value still shows 
4023000 or 4.02GHz but we tried to set 3.92GHz.
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  Userspace tool common name: /usr/bin/cpufreq-set 

  Userspace rpm: cpufrequtils 
   
  The userspace tool has the following bit modes: 64-bit 
   
  System Dump Info:
The system is not configured to capture a system dump.

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for pavsu...@in.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on. 
  -Attach sysctl -a output output to the bug.
  -Attach ltrace and strace of 

[Kernel-packages] [Bug 1658270] Re: Backport Dirty COW patch to prevent wineserver freeze

[Joseph Salisbury]

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

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

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

Title:
  Backport Dirty COW patch to prevent wineserver freeze

Status in linux package in Ubuntu:
  Triaged

Bug description:
  A few kernels updates ago (after kernel 3.13.0-98) on 14.04 (Trusty) a
  backported fix for Dirty COW from kernel 4.8.3 resulted in some Delphi
  apps freezing wineserver and leaving it unkillable:

  https://bugs.winehq.org/show_bug.cgi?id=41637

  I haven't tested for the bug on 16.04 Xenial (kernel 4.4.0-59) but it
  is probably affected.  A patch is available:

  https://lkml.org/lkml/2017/1/5/13
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jhansonxi   2775 F pulseaudio
   /dev/snd/controlC2:  jhansonxi   2775 F pulseaudio
   /dev/snd/controlC0:  jhansonxi   2775 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=6c1d3a04-0529-476c-b193-3e584c0333ca
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic 
root=/dev/mapper/vg0-lv1 ro quiet nosplash
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-59-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: dialout
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1206
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M3A78-EM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1206:bd11/26/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3A78-EM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1657994] Re: Regression: HDMI audio produces no sound (Skylake NUC)

[Joseph Salisbury]

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

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

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

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


Thanks in advance.

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

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

** Tags added: performing-bisect

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

Title:
  Regression:  HDMI audio produces no sound (Skylake NUC)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrade from Xenial 16.04 to Yakkety 16.10, playing audio over HDMI no 
longer produces sound.
  * When booting with old kernel from Xenial (4.4.0-59), HDMI audio works fine
  * Audio from headphone jack works fine
  * Userspace seems to be happily playing to HDMI audio device, but no sound 
produced at HDMI sink (Samsung TV)

  Any of a wide range of pre-built mainline kernels fail to produce HDMI
  audio, but with a different failure mode (HDMI audio does not seem to
  be enumerated in the same way as in the Ubuntu kernels.)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-34-generic 4.8.0-34.36
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  israel 1973 F pulseaudio
   /dev/snd/controlC1:  israel 1973 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jan 20 08:58:35 2017
  HibernationDevice: RESUME=UUID=ca27f739-071f-4c25-974e-0d0f0614b21c
  InstallationDate: Installed on 2016-10-03 (108 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic.efi.signed 
root=UUID=90c3e094-e890-4c35-a0d2-0a358f5d2430 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-34-generic N/A
   linux-backports-modules-4.8.0-34-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2017-01-13 (6 days ago)
  dmi.bios.date: 06/03/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: KYSKLi70.86A.0037.2016.0603.1032
  dmi.board.name: NUC6i7KYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H90766-405
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrKYSKLi70.86A.0037.2016.0603.1032:bd06/03/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-405:cvnIntelCorporation:ct3:cvr1.0:

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

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

[Kernel-packages] [Bug 1658632] Re: [drm:intel_pipe_update_end [i915_bpo]] *ERROR* Atomic update failure on pipe C

[Joseph Salisbury]

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

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

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

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

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


Thanks in advance.

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

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

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

Title:
  [drm:intel_pipe_update_end [i915_bpo]] *ERROR* Atomic update failure
  on pipe C

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Dell XPS 15, Ubuntu 16.04 (Ubuntu 4.4.0-59.80-generic 4.4.35), freshly
  updated. Running BTRFS and nouveau.

  The UI crashes, and put me back to the login screen after 30 seconds.

  This happens when I start softwares based on webkit (stremio, opera,
  chrome, etc). But generally only the first time. After login back and
  starting the program again, it works without crashing.

  The full dmesg error message is:

  [  113.711453] [drm:intel_pipe_update_end [i915_bpo]] *ERROR* Atomic
  update failure on pipe C (start=5158 end=5159) time 130 us, min 1073,
  max 1079, scanline start 1071, end 1080

  Repeated several times.

  I also get a:

  [  762.958586] nouveau :01:00.0: priv: HUB0: 10ecc0 
  (1d40822c)

  And a:

  [13925.500344] brcmf_cfg80211_reg_notifier: not a ISO3166 code

  but don't know if it's relevant.

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

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

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

[Joseph Salisbury]

You may need to run the following from a terminal:

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

Then re-install the package or updates.

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

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

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

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

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The software updater fails when used therefore I can't update the lubuntu 
system.
  Hope this can sorted as ubuntu is a very stable OS.
  Thanks.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-107-generic (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mike   1385 F lxpanel
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Mon Jan 23 14:09:24 2017
  DpkgHistoryLog:
   Start-Date: 2017-01-23  14:09:18
   Commandline: apt-get -f install
   Install: linux-headers-3.13.0-107:i386 (3.13.0-107.154, automatic), 
linux-image-extra-3.13.0-107-generic:i386 (3.13.0-107.154, automatic), 
linux-headers-3.13.0-107-generic:i386 (3.13.0-107.154, automatic), 
linux-image-3.13.0-107-generic:i386 (3.13.0-107.154, automatic), 
linux-image-3.13.0-105-generic:i386 (3.13.0-105.152, automatic)
   Upgrade: linux-generic:i386 (3.13.0.105.113, 3.13.0.107.115), 
linux-image-generic:i386 (3.13.0.105.113, 3.13.0.107.115), 
linux-headers-generic:i386 (3.13.0.105.113, 3.13.0.107.115)
  DpkgTerminalLog:
   Preparing to unpack 
.../linux-image-3.13.0-107-generic_3.13.0-107.154_i386.deb ...
   This kernel does not support a non-PAE CPU.
   dpkg: error processing archive 
/var/cache/apt/archives/linux-image-3.13.0-107-generic_3.13.0-107.154_i386.deb 
(--unpack):
subprocess new pre-installation script returned error exit status 1
  DuplicateSignature: package:linux-image-3.13.0-107-generic:(not 
installed):subprocess new pre-installation script returned error exit status 1
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  HibernationDevice: RESUME=UUID=8ea04b59-9c47-4d88-b7c2-9e999ce1435b
  InstallationDate: Installed on 2016-11-16 (68 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Samsung Electronics Aquila Slim Platform
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=7a8e48cc-a123-4e05-85b6-4187292d7699 ro rootflags=sync quiet splash 
vt.handoff=7
  RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.12
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-3.13.0-107-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 09/17/2003
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 02VE
  dmi.board.name: Aquila Slim Platform
  dmi.board.vendor: Samsung Electronics
  dmi.board.version: Revision 01
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Samsung Electronics
  dmi.chassis.version: revision 1.0
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr02VE:bd09/17/2003:svnSamsungElectronics:pnAquilaSlimPlatform:pvrRevision01:rvnSamsungElectronics:rnAquilaSlimPlatform:rvrRevision01:cvnSamsungElectronics:ct10:cvrrevision1.0:
  dmi.product.name: Aquila Slim Platform
  dmi.product.version: Revision 01
  dmi.sys.vendor: Samsung Electronics

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

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

[Kernel-packages] [Bug 1649513] Re: [Ubuntu 16.10] NMI watchdog and soft lockup while running htx memory tests in kernel 4.8.0-17-generic

[Manoj Iyer]

IBM needs to identify a patch that fixes this issue. We do not have a
good mechanism to reproduce the bug.

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

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

Title:
  [Ubuntu 16.10] NMI watchdog and soft lockup while running htx memory
  tests in kernel 4.8.0-17-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Issue:
  --
  NMI Watchdog Bug and soft lockup occurs when htx memory test is run in ubuntu 
16.10.

  Environment:
  --
  Arch : ppc64le
  Platform : Ubuntu KVM Guest
  Host : ubuntu 16.10 [4.8.0-17 -kernel ]
  Guest : ubuntu 16.10 [4.8.0-17 - Kernel]

  Steps To Reproduce:
  ---

  1 - Install a Ubuntu KVM Guest and install htx package in the guest got from 
the link,
  http://ausgsa.ibm.com/projects/h/htx/public_html/htxonly/htxubuntu-413.deb 

  2 - Run the Htx mdt.mem

  3 - The system Hits soft lockup Issue as below:

  dmesg o/p:
  [60287.590335] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 1141s! 
[hxemem64:23468]
  [60287.590572] Modules linked in: vmx_crypto ip_tables x_tables autofs4 
ibmvscsi crc32c_vpmsum
  [60287.590585] CPU: 3 PID: 23468 Comm: hxemem64 Tainted: G L  
4.8.0-17-generic #19-Ubuntu
  [60287.590587] task: c012a0971e00 task.stack: c012a2d4
  [60287.590589] NIP: c0015004 LR: c0015004 CTR: 
c0165e90
  [60287.590591] REGS: c012a2d439a0 TRAP: 0901   Tainted: G L   
(4.8.0-17-generic)
  [60287.590592] MSR: 80009033   CR: 48004244  
XER: 
  [60287.590603] CFAR: c0165890 SOFTE: 1 
 GPR00: c0165f9c c012a2d43c20 c14e5e00 
0900 
 GPR04:  0008 000100e4d61a 
 
 GPR08:  0006 000100e4d619 
c012bfee3130 
 GPR12: 3fffae6cdc70 3fffae436900 
  [60287.590627] NIP [c0015004] arch_local_irq_restore+0x74/0x90
  [60287.590630] LR [c0015004] arch_local_irq_restore+0x74/0x90
  [60287.590631] Call Trace:
  [60287.590634] [c012a2d43c20] [c012bfeccd80] 0xc012bfeccd80 
(unreliable)
  [60287.590639] [c012a2d43c40] [c0165f9c] 
run_timer_softirq+0x10c/0x230
  [60287.590644] [c012a2d43ce0] [c0b94adc] __do_softirq+0x18c/0x3fc
  [60287.590648] [c012a2d43de0] [c00d5828] irq_exit+0xc8/0x100
  [60287.590653] [c012a2d43e00] [c0024810] timer_interrupt+0xa0/0xe0
  [60287.590657] [c012a2d43e30] [c0002814] 
decrementer_common+0x114/0x180
  [60287.590659] Instruction dump:
  [60287.590662] 994d023a 2fa3 409e0024 e92d0020 61298000 7d210164 38210020 
e8010010 
  [60287.590670] 7c0803a6 4e800020 6042 4bfed259 <6000> 4be4 
6042 e92d0020 
  [63127.581494] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 339s! 
[hxemem64:23467]
  [63127.629682] Modules linked in: vmx_crypto ip_tables x_tables autofs4 
ibmvscsi crc32c_vpmsum
  [63127.629699] CPU: 2 PID: 23467 Comm: hxemem64 Tainted: G L  
4.8.0-17-generic #19-Ubuntu
  [63127.629701] task: c012a0965800 task.stack: c012a2d58000
  [63127.629703] NIP: 10011e60 LR: 1000ec6c CTR: 
00f33196
  [63127.629706] REGS: c012a2d5bea0 TRAP: 0901   Tainted: G L   
(4.8.0-17-generic)
  [63127.629707] MSR: 8001d033   CR: 
42004482  XER: 
  [63127.629719] CFAR: 10011e68 SOFTE: 1 
 GPR00: 1000e854 3fffadc2e540 10047f00 
000d 
 GPR04: 0200 3ff5a800 5a5a5a5a5a5a5a5a 
3ff5b0667348 
 GPR08:  1006c8e0 1006ca04 
f001 
 GPR12: 3fffae6cdc70 3fffadc36900 
  [63127.629740] NIP [10011e60] 0x10011e60
  [63127.629742] LR [1000ec6c] 0x1000ec6c
  [63127.629743] Call Trace:

  == Comment: #3 - Santhosh G  - 2016-09-28 02:17:29 ==
  Memory Info :

  root@ubuntu:~# cat /proc/meminfo 
  MemTotal:   78539776 kB
  MemFree:72219392 kB
  MemAvailable:   77217088 kB
  Buffers:  212544 kB
  Cached:  5249088 kB
  SwapCached:0 kB
  Active:  1440832 kB
  Inactive:4107264 kB
  Active(anon):  93888 kB
  Inactive(anon): 8640 kB
  Active(file):1346944 kB
  Inactive(file):  4098624 kB
  Unevictable:   0 kB
  Mlocked:   0 kB
  SwapTotal:   3443648 kB
  SwapFree:3443648 kB
  Dirty: 0 kB
  Writeback: 0 kB
  AnonPages: 87296 kB
  Mapped:30400 kB
  Shmem: 16128 kB
  Slab: 

[Kernel-packages] [Bug 1658016] Re: Intel AC7260 wireless (iwlwifi) stops working after computer sleep/wakeup

[Joseph Salisbury]

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

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

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

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


Thanks in advance.

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

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

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

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

Title:
  Intel AC7260 wireless (iwlwifi) stops working after computer
  sleep/wakeup

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since about the beginning of 2017 the Intel AC7260 wireless card on my Asus 
UX501 stops working correctly when the computer suspends to RAM and wakes up 
again (laptop lid closed and opened).
  The message is:

  [ 7679.281856] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

  The only way to come around this problem is to re-insert the iwlwifi
  module:

  sudo modprobe -r iwlwifi; sudo modprobe iwlwifi

  To be more precise what it means stops working: The wifi does not see
  the networks correctly. nm-applet reports only one of many networks in
  my area. My network is not there and it does not connect.

  I used to have the problem rarely in the past. However it happened only 
occasionally and I could live with the above workaround. Since about the 
beginning of 2017 it happens __always__. Not sure, which update exactly caused 
it, but you can imagine how annoying it is.
  I would appreciate if it could be fixed. Thanks!

  Here is the relevant dmesg log:

  [ 7679.149644] PM: resume of devices complete after 737.622 msecs
  [ 7679.150241] PM: Finishing wakeup.
  [ 7679.150242] Restarting tasks ... done.
  [ 7679.163190] Bluetooth: hci0: read Intel version: 3707100180012d0d00
  [ 7679.163197] Bluetooth: hci0: Intel Bluetooth firmware file: 
intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq
  [ 7679.188077] bbswitch: disabling discrete graphics
  [ 7679.188089] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
  [ 7679.279490] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [ 7679.280238] asix 3-3:1.0 eth0: link down
  [ 7679.280695] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [ 7679.281856] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [ 7679.281960] iwlwifi :3b:00.0: L1 Disabled - LTR Enabled
  [ 7679.282220] iwlwifi :3b:00.0: L1 Disabled - LTR Enabled
  [ 7679.342219] Bluetooth: hci0: Intel Bluetooth firmware patch completed and 
activated
  [ 7679.467403] iwlwifi :3b:00.0: L1 Disabled - LTR Enabled
  [ 7679.467709] iwlwifi :3b:00.0: L1 Disabled - LTR Enabled
  [ 7679.483163] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [ 7679.549503] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [ 7700.394009] iwlwifi :3b:00.0: L1 Disabled - LTR Enabled
  [ 7700.544809] cfg80211: World regulatory domain updated:
  [ 7700.544812] cfg80211:  DFS Master region: unset
  [ 7700.544812] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp), (dfs_cac_time)
  [ 7700.544814] cfg80211:   (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 
2000 mBm), (N/A)
  [ 7700.544815] cfg80211:   (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 
2000 mBm), (N/A)
  [ 7700.544816] cfg80211:   (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 
2000 mBm), (N/A)
  [ 7700.544817] cfg80211:   (517 KHz - 525 KHz @ 8 KHz, 16 KHz 
AUTO), (N/A, 2000 mBm), (N/A)
  [ 7700.544818] cfg80211:   (525 KHz - 533 KHz @ 8 KHz, 16 KHz 
AUTO), (N/A, 2000 mBm), (0 s)
  [ 7700.544819] cfg80211:   (549 KHz - 573 KHz @ 16 KHz), (N/A, 
2000 mBm), (0 s)
  [ 7700.544820] cfg80211:   (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 
2000 mBm), (N/A)
  [ 7700.544821] cfg80211:   (5724 KHz - 6372 KHz @ 216 KHz), (N/A, 
0 mBm), (N/A)
  [ 7700.545380] Intel(R) Wireless WiFi driver for Linux
  [ 7700.545382] Copyright(c) 2003- 2015 Intel Corporation
  [ 7700.546038] iwlwifi :3b:00.0: loaded firmware version 17.352738.0 
op_mode iwlmvm
  [ 7700.557859] iwlwifi :3b:00.0: Detected Intel(R) Dual Band Wireless AC 
7260, REV=0x144
  [ 7700.557914] iwlwifi :3b:00.0: L1 Disabled - LTR Enabled
  [ 7700.558147] iwlwifi :3b:00.0: L1 Disabled - LTR Enabled
  [ 7700.741439] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
  [ 7700.747514] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [ 7700.747609] iwlwifi :3b:00.0: L1 Disabled - LTR Enabled
  [ 7700.747849] iwlwifi 

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

[Joseph Salisbury]

You may need to run the following from a terminal:

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

Then re-install the package or updates.

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


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

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

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

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ?!

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abuelo 1736 F pulseaudio
  Date: Fri Jan 20 12:56:39 2017
  DuplicateSignature:
   package:linux-image-4.4.0-59-generic:(not installed)
   Preparing to unpack .../linux-image-4.4.0-59-generic_4.4.0-59.80_i386.deb ...
   This kernel does not support a non-PAE CPU.
   dpkg: error processing archive 
/var/cache/apt/archives/linux-image-4.4.0-59-generic_4.4.0-59.80_i386.deb 
(--unpack):
subprocess new pre-installation script returned error exit status 1
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  HibernationDevice: RESUME=UUID=bbc94367-a204-4475-9126-10dd986d2397
  InstallationDate: Installed on 2017-01-20 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Dell Inc. Latitude D505
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=55af8e4f-d2f2-4cd3-9ff1-d0aa66ec55f5 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.6
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.4.0-59-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/03/2004
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0H2049
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd09/03/2004:svnDellInc.:pnLatitudeD505:pvr:rvnDellInc.:rn0H2049:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D505
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1651376] Re: ISST-LTE:pVM:seedlp2:ubuntu 16.04.2: oom occurs when running stress tests

[Manoj Iyer]

Colin, Could you please help resolving this OOM with stress-ng?

** Also affects: stress-ng (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: stress-ng (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

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

Title:
  ISST-LTE:pVM:seedlp2:ubuntu 16.04.2: oom occurs when running stress
  tests

Status in linux package in Ubuntu:
  New
Status in stress-ng package in Ubuntu:
  New

Bug description:
  Problem Description
  
  We run stress tests on seedlp2, after a while a lot of oom messages echoed on 
the console again and again and the system hung up:

  
  [ 8331.537440] Out of memory (oom_kill_allocating_task): Kill process 27466 
(fork12) score 0 or sacrifice child
  [ 8331.537447] Killed process 27466 (fork12) total-vm:3072kB, anon-rss:0kB, 
file-rss:512kB, shmem-rss:0kB
  [ 8331.543871] oom_reaper: reaped process 27466 (fork12), now anon-rss:0kB, 
file-rss:0kB, shmem-rss:0kB
  [ 8331.544167] fork12 invoked oom-killer: 
gfp_mask=0x24200ca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0
  [ 8331.544174] fork12 cpuset=/ mems_allowed=3
  [ 8331.544184] CPU: 19 PID: 20947 Comm: fork12 Tainted: G   OE   
4.8.0-31-generic #33~16.04.1-Ubuntu
  [ 8331.544189] Call Trace:
  [ 8331.544197] [c000b7fdb630] [c0b56554] dump_stack+0xb0/0xf0 
(unreliable)
  [ 8331.544204] [c000b7fdb670] [c0b53db4] dump_header+0x88/0x228
  [ 8331.544211] [c000b7fdb740] [c0258194] 
oom_kill_process+0x464/0x570
  [ 8331.544217] [c000b7fdb800] [c02588a4] out_of_memory+0x574/0x590
  [ 8331.544223] [c000b7fdb8a0] [c025fb18] 
__alloc_pages_nodemask+0xe98/0xee0
  [ 8331.544230] [c000b7fdba60] [c02da458] 
alloc_pages_vma+0x108/0x360
  [ 8331.544235] [c000b7fdbb00] [c02c3958] 
__read_swap_cache_async+0x1b8/0x2c0
  [ 8331.544241] [c000b7fdbb70] [c02c3a8c] 
read_swap_cache_async+0x2c/0x60
  [ 8331.544246] [c000b7fdbbb0] [c02c3cb0] 
swapin_readahead+0x1f0/0x2e0
  [ 8331.544253] [c000b7fdbc50] [c02a0b78] do_swap_page+0x338/0x9a0
  [ 8331.544258] [c000b7fdbcd0] [c02a550c] 
handle_mm_fault+0x98c/0x14c0
  [ 8331.544264] [c000b7fdbd80] [c0b4d2d0] do_page_fault+0x350/0x7d0
  [ 8331.553521] [c000b7fdbe30] [c0008948] 
handle_page_fault+0x10/0x30
  [ 8331.553552] Mem-Info:
  [ 8331.553567] active_anon:121 inactive_anon:6417 isolated_anon:742
  [ 8331.553567]  active_file:167 inactive_file:120 isolated_file:0
  [ 8331.553567]  unevictable:230 dirty:0 writeback:141 unstable:0
  [ 8331.553567]  slab_reclaimable:2483 slab_unreclaimable:24404
  [ 8331.553567]  mapped:122 shmem:0 pagetables:11341 bounce:0
  [ 8331.553567]  free:2812 free_pcp:0 free_cma:0
  [ 8331.553611] Node 0 active_anon:0kB inactive_anon:0kB active_file:0kB 
inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB 
mapped:0kB dirty:0kB writeback:0kB shmem:0kB shmem_thp: 0kB shmem_pmdmapped: 
0kB anon_thp: 0kB writeback_tmp:0kB unstable:0kB pages_scanned:0 
all_unreclaimable? yes
  [ 8331.553642] Node 3 active_anon:7744kB inactive_anon:404544kB 
active_file:10688kB inactive_file:7680kB unevictable:14720kB 
isolated(anon):53632kB isolated(file):0kB mapped:7808kB dirty:0kB 
writeback:9024kB shmem:0kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 0kB 
writeback_tmp:0kB unstable:0kB pages_scanned:78640 all_unreclaimable? yes
  [ 8331.556952] Node 3 DMA free:179968kB min:180224kB low:225280kB 
high:270336kB active_anon:5824kB inactive_anon:419840kB active_file:6720kB 
inactive_file:3776kB unevictable:14720kB writepending:9024kB present:4194304kB 
managed:3624960kB mlocked:14720kB slab_reclaimable:158912kB 
slab_unreclaimable:1561856kB kernel_stack:202992kB pagetables:725824kB 
bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB
  [ 8331.556978] lowmem_reserve[]: 0 0 0 0
  [ 8331.556988] Node 3 DMA: 1124*64kB (UME) 172*128kB (UME) 127*256kB (UM) 
95*512kB (M) 6*1024kB (M) 0*2048kB 0*4096kB 0*8192kB 0*16384kB = 181248kB
  [ 8331.557022] Node 3 hugepages_total=0 hugepages_free=0 hugepages_surp=0 
hugepages_size=16384kB
  [ 8331.557032] Node 3 hugepages_total=0 hugepages_free=0 hugepages_surp=0 
hugepages_size=16777216kB
  [ 8331.557040] 7760 total pagecache pages
  [ 8331.563978] 7356 pages in swap cache
  [ 8331.563985] Swap cache stats: add 1612469, delete 1605113, find 
1293795/2233630
  [ 8331.563992] Free swap  = 9015616kB
  [ 8331.563997] Total swap = 12096448kB
  [ 8331.564003] 65536 pages RAM
  [ 8331.564007] 0 pages HighMem/MovableOnly
  [ 8331.564013] 8896 pages reserved
  [ 8331.564019] 0 pages cma reserved
  [ 8331.564024] 0 pages hwpoisoned

   
  ---uname output---
  4.8.0-31-generic 

[Kernel-packages] [Bug 1650062] Re: Ubuntu16.04.01VM:Docker-Powervm aufs bad file panic while running tests in a docker container

[Manoj Iyer]

** Changed in: linux (Ubuntu)
 Assignee: Taco Screen team (taco-screen-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/1650062

Title:
  Ubuntu16.04.01VM:Docker-Powervm aufs bad file panic while running
  tests in a docker container

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Vinutha GS - 2016-12-13 02:47:35 ==
  When some of the base and io tests were run inside a docker container, the 
par crashed and below are the stack trace and other details.

  Steps to re-create -
  1. Install 16.04.02 on a PowerVM lpar.
  2. Ran setup general.
  3. Ran docker scripts[home grown scripts] which does docker package 
installation and other setups required to run STAF cases inside docker 
container.
  4. We have docker image using which we launch containers and start tests 
inside containers.
  If complete details are required on how to execute scripts, please let me 
know.
  5. STAF Base and IO tests were started inside containers successfully, after 
sometime, I see partition is in XMON.

  Docker info -
  docker info
  Containers: 0
   Running: 0
   Paused: 0
   Stopped: 0
  Images: 0
  Server Version: 1.12.1
  Storage Driver: aufs
   Root Dir: /var/lib/docker/aufs
   Backing Filesystem: extfs
   Dirs: 0
   Dirperm1 Supported: true
  Logging Driver: json-file
  Cgroup Driver: cgroupfs
  Plugins:
   Volume: local
   Network: null host bridge overlay
  Swarm: inactive
  Runtimes: runc
  Default Runtime: runc
  Security Options: apparmor
  Kernel Version: 4.4.0-53-generic
  Operating System: Ubuntu 16.04.1 LTS
  OSType: linux
  Architecture: ppc64le
  CPUs: 24
  Total Memory: 49.89 GiB
  Name: bamlp3
  ID: I7VI:G4RJ:RHTQ:WNGV:52FK:K7AZ:YDJQ:KFUM:P3UA:MZ3I:5XUY:WV3N
  Docker Root Dir: /var/lib/docker
  Debug Mode (client): false
  Debug Mode (server): false
  Registry: https://index.docker.io/v1/
  WARNING: No swap limit support
  Insecure Registries:
   127.0.0.0/8

  docker ps -a
  CONTAINER IDIMAGE   COMMAND  CREATED  
   STATUS  PORTS   NAMES
  61f2b8ab0a8632d545c3ea01"/bin/sh -c ./staf_io"   24 minutes 
ago  Up 24 minutes   bamlp3-io
  151da0322172590e44f15214"/bin/sh -c ./staf_ba"   30 minutes 
ago  Up 30 minutes   bamlp3-base

  
  Stack trace -
  8:mon> t
  [c00a5e147d10] da04ca98 aufs_flush_nondir+0x38/0x50 [aufs]
  [c00a5e147d40] c02e0428 filp_close+0x68/0xe0
  [c00a5e147dc0] c030f71c __close_fd+0xcc/0x150
  [c00a5e147e00] c02e04d4 SyS_close+0x34/0x90
  [c00a5e147e30] c0009204 system_call+0x38/0xb4
  --- Exception: c00 (System Call) at 3fff8bc217d8
  SP (3fffd85203b0) is in userspace
  8:mon> e
  cpu 0x8: Vector: 300 (Data Access) at [c00a5e147a40]
  pc: da04bdd4: au_do_flush+0x44/0x220 [aufs]
  lr: da04ca98: aufs_flush_nondir+0x38/0x50 [aufs]
  sp: c00a5e147cc0
 msr: 80009033
 dar: 28
   dsisr: 4000
current = 0xc00a8b7fc8e0
paca= 0xcfb44c00 softe: 0irq_happened: 0x01
  pid   = 11936, comm = remap_file_page
  8:mon>

  Release details -
  uname -r
  4.4.0-53-generic

   uname -a
  Linux bamlp4 4.4.0-53-generic #74-Ubuntu SMP Fri Dec 2 15:59:36 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  == Comment: #6 - Vinutha GS  - 2016-12-14 03:16:18 ==
  Please find the attached sosreport.
  Also i have followed the steps for k-dump, It is enabled now.
  I'm going to start the tests once again.

  == Comment: #12 - Kevin W. Rudd - 2016-12-14 16:06:46 ==
  The basic reason for the panic is that close was called on a file 
  that was no longer valid.  The f_count value was -8 for some reason,
  so it passed the following check in filep_close():

  if (!file_count(filp)) {
  printk(KERN_ERR "VFS: Close: file count is 0\n");
  return 0;
  }

  It then blew up in au_do_flush() because f_inode was NULL.

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

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

[Kernel-packages] [Bug 1566987] ProcEnviron.txt

[yan]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1566987/+attachment/4808205/+files/ProcEnviron.txt

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

Title:
  No internet connection through WLAN although connected to network

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In a fresh install of Kubuntu 16.04 on a ThinkPad t460s, I can connect
  wireless to the local WLAN, but I don't have an internet connection. A
  ping to the router doesn't work in that case.

  After some minutes, the connection usually (but not always) works.

  A LAN connection through the same router works, too. It seems that the
  problem doesn't occur in every WLAN, but in my home network (using an
  O2 box 6431) it always does.

  The problem is reproducible with a Kubuntu Live CD/USB.

  The following steps did not solve the problem:

  - Reconnect to WLAN
  - Using kernel 4.6 or 4.7
  - Restarting NetworkManager and networking service
  - Disable IPv6
  - Factory reset of the o2 box
  - Restart of the o2 box (sometimes it helps temporarily)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-04 (294 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.7.4-040704-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1566987] Re: No internet connection through WLAN although connected to network

[yan]

apport information

** Tags added: apport-collected xenial

** Description changed:

  In a fresh install of Kubuntu 16.04 on a ThinkPad t460s, I can connect
  wireless to the local WLAN, but I don't have an internet connection. A
  ping to the router doesn't work in that case.
  
  After some minutes, the connection usually (but not always) works.
  
  A LAN connection through the same router works, too. It seems that the
  problem doesn't occur in every WLAN, but in my home network (using an O2
  box 6431) it always does.
  
  The problem is reproducible with a Kubuntu Live CD/USB.
  
  The following steps did not solve the problem:
  
  - Reconnect to WLAN
  - Using kernel 4.6 or 4.7
  - Restarting NetworkManager and networking service
  - Disable IPv6
  - Factory reset of the o2 box
  - Restart of the o2 box (sometimes it helps temporarily)
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.5
+ Architecture: amd64
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 16.04
+ InstallationDate: Installed on 2016-04-04 (294 days ago)
+ InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
+ Package: linux (not installed)
+ Tags:  xenial
+ Uname: Linux 4.7.4-040704-generic x86_64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1566987/+attachment/4808204/+files/JournalErrors.txt

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

Title:
  No internet connection through WLAN although connected to network

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In a fresh install of Kubuntu 16.04 on a ThinkPad t460s, I can connect
  wireless to the local WLAN, but I don't have an internet connection. A
  ping to the router doesn't work in that case.

  After some minutes, the connection usually (but not always) works.

  A LAN connection through the same router works, too. It seems that the
  problem doesn't occur in every WLAN, but in my home network (using an
  O2 box 6431) it always does.

  The problem is reproducible with a Kubuntu Live CD/USB.

  The following steps did not solve the problem:

  - Reconnect to WLAN
  - Using kernel 4.6 or 4.7
  - Restarting NetworkManager and networking service
  - Disable IPv6
  - Factory reset of the o2 box
  - Restart of the o2 box (sometimes it helps temporarily)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-04 (294 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.7.4-040704-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

-- 
Mailing list: https://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 1653162] Re: System won't boot after upgrade to 16.04 with 4.4.0 kernel

[Jon Schewe]

I have not been able to schedule time yet. I hope to test it this week.

Sent from my mobile device

On Jan 23, 2017 11:16 AM, "Joseph Salisbury" 
wrote:

> @Jon Schewe, were you able to test any of the kernels posted in comment
> #19?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1653162
>
> Title:
>   System won't boot after upgrade to 16.04 with 4.4.0 kernel
>
> Status in linux package in Ubuntu:
>   Triaged
> Status in linux source package in Xenial:
>   Triaged
> Status in linux source package in Yakkety:
>   Triaged
>
> Bug description:
>   I have a Dell PowerEdge 1800 with Dell CERC 1.5/6ch RAID controller in
>   it. Everything worked fine under Ubuntu 14.04.1. When I upgraded to
>   16.04.1 the system won't boot. It can't find the root filesystem. I
>   see errors about host adapter dead on the screen many times. This is
>   with kernel 4.4.0-57 and with 4.8.0-32. When I switch back to kernel
>   3.13.0-105 the system boots just fine.
>
>   I have mptbios 5.06.04.
>   The CERC card says bios version 4.1-0 [Build 7403]
>
>   When booting into the ercovery kernel I'm getting error messages about
> host adapter dead.
>   Eventually I get a message:
>   "aacraid: aac_fib_send: first asynchronous command timed out.
>   Usually a result of a PCI interrupt routing problem
>   update moher board BIOS or consider utilizing one of
>   the SAFE mode kernel options (acpi, apic etc)"
>
>
>   Using kernel parameter "intel_iommu=on" doesn't help. This was suggested
> on a post that I saw about these errors.
>
>   Booting with "noapic" didn't help.
>   Booting with "noapic noacpi" didn't help.
>
>
>   I've also tried the dkms modules from Adaptec and that doesn't seem to
> help either.
>
>
>   I can't figure out how to upgrade the firmware or BIOS on the system
> from Ubuntu either.
>
>
>   This may be related to this bug: https://bugs.launchpad.net/
> ubuntu/+source/linux/+bug/1552551?comments=all
>   ---
>   ApportVersion: 2.20.1-0ubuntu2.4
>   Architecture: amd64
>   AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
> '/dev/snd/timer'] failed with exit code 1:
>   DistroRelease: Ubuntu 16.04
>   HibernationDevice: RESUME=UUID=beec17b5-eac8-4e94-ac99-65b63c428b77
>   InstallationDate: Installed on 2014-02-24 (1039 days ago)
>   InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64
> (20130820.1)
>   IwConfig:
>eth1  no wireless extensions.
>
>lono wireless extensions.
>   Lsusb:
>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>   MachineType: Dell Computer Corporation PowerEdge 1800
>   Package: linux (not installed)
>   ProcEnviron:
>TERM=screen
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcFB: 0 radeondrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-105-generic
> root=UUID=83e1b87e-adb9-4798-a6e0-18d401c91a4a ro nosplash noplymouth
>   ProcVersionSignature: Ubuntu 3.13.0-105.152-generic 3.13.11-ckt39
>   PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
> PulseAudio daemon running, or not running as session daemon.
>   RelatedPackageVersions:
>linux-restricted-modules-3.13.0-105-generic N/A
>linux-backports-modules-3.13.0-105-generic  N/A
>linux-firmware  1.157.6
>   RfKill:
>
>   Tags:  xenial
>   Uname: Linux 3.13.0-105-generic x86_64
>   UpgradeStatus: Upgraded to xenial on 2016-12-25 (3 days ago)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>   dmi.bios.date: 09/01/2004
>   dmi.bios.vendor: Dell Computer Corporation
>   dmi.bios.version: A00
>   dmi.board.name: 0X7500
>   dmi.board.vendor: Dell Computer Corporation
>   dmi.board.version: A00
>   dmi.chassis.type: 17
>   dmi.chassis.vendor: Dell Computer Corporation
>   dmi.modalias: dmi:bvnDellComputerCorporation:bvrA00:bd09/01/2004:
> svnDellComputerCorporation:pnPowerEdge1800:pvr:rvnDellComputerCorporation:
> rn0X7500:rvrA00:cvnDellComputerCorporation:ct17:cvr:
>   dmi.product.name: PowerEdge 1800
>   dmi.sys.vendor: Dell Computer Corporation
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1653162/+subscriptions
>
>

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

Title:
  System won't boot after upgrade to 16.04 with 4.4.0 kernel

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

Bug description:
  I have a Dell PowerEdge 

[Kernel-packages] [Bug 1655748] Re: linux-lts-vivid: 3.19.0-80.88~14.04.1 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

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

Title:
  linux-lts-vivid: 3.19.0-80.88~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
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-80.88~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 --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1655745
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1655241] Re: Ubuntu 17.04: "Oops: Exception in kernel mode, sig: 5 [#1]" seen during fadump over ssh on Alpine machine.

[Manoj Iyer]

Leann, could you please get someone to pull in commit referenced in this
bug to fix the oops ?

** Changed in: makedumpfile (Ubuntu)
 Assignee: Taco Screen team (taco-screen-team) => Leann Ogasawara 
(leannogasawara)

** Changed in: makedumpfile (Ubuntu)
   Importance: Undecided => Critical

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

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

Status in makedumpfile package in Ubuntu:
  New

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

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

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

  # kdump-config propagate

  # kdump-config load

  # kdump-config show

  2. Trigger crash

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

[Kernel-packages] [Bug 1655280] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: cp: error reading '/proc/vmcore': Bad address when trying to dump vmcore

[Manoj Iyer]

Steve, could your team please take a look ?

** Changed in: linux (Ubuntu)
 Assignee: Taco Screen team (taco-screen-team) => Steve Langasek (vorlon)

** Changed in: linux (Ubuntu)
   Importance: Undecided => 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/1655280

Title:
  ISST-LTE:pVM:roselp4:ubuntu 16.04.2: cp: error reading '/proc/vmcore':
  Bad address when trying to dump vmcore

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Ping Tian Han  - 2017-01-09 02:51:00 ==
  ---Problem Description---
  Vmcore cannot be saved when triggering bug 150353 on roselp4:

  Copying data   : [  2.0 %] \/usr/sbin/kdump-config: line 
591:  5502 Bus error   makedumpfile $MAKEDUMP_ARGS $vmcore_file 
$KDUMP_CORETEMP
  [  512.833872] kdump-tools[5450]:  * kdump-tools: makedumpfile failed, 
falling back to 'cp'
  [  573.595449] kdump-tools[5450]: cp: error reading '/proc/vmcore': Bad 
address
  [  573.605717] kdump-tools[5450]:  * kdump-tools: failed to save vmcore in 
/var/crash/201701090223
  [  573.765417] kdump-tools[5450]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/201701090223/dmesg.201701090223
  [  574.285506] kdump-tools[5450]: The kernel version is not supported.
  [  574.285672] kdump-tools[5450]: The makedumpfile operation may be 
incomplete.
  [  574.285767] kdump-tools[5450]: The dmesg log is saved to 
/var/crash/201701090223/dmesg.201701090223.
  [  574.305422] kdump-tools[5450]: makedumpfile Completed.
  [  574.315363] kdump-tools[5450]:  * kdump-tools: saved dmesg content in 
/var/crash/201701090223
  [  574.615688] kdump-tools[5450]: Mon, 09 Jan 2017 02:24:26 -0600
  [  574.705384] kdump-tools[5450]: Rebooting.
   Stopping ifup for ib0...
  [  OK  ] Stopped ifup for ib0.
  [ 1008.579897] reboot: Restarting system
   
  Contact Information = Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com 
   
  ---uname output---
  Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = lpar 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. config kdump on roselp4
  2. try to trigger bug 150353

   
  *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.

  == Comment: #3 - Brahadambal Srinivasan  -
  2017-01-10 02:42:25 ==

  root@roselp4:~# cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinux-4.8.0-34-generic 
root=UUID=0bcf3431-df8b-499c-9a13-33070f242e0c ro splash quiet 
crashkernel=384M-:512M

  root@roselp4:~# dmesg | grep Reser
  [0.00] Reserving 512MB of memory at 128MB for crashkernel (System 
RAM: 21760MB)

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

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

[Kernel-packages] [Bug 1658733] host sosreport

[bugproxy]

Default Comment by Bridge

** Attachment added: "host sosreport"
   
https://bugs.launchpad.net/bugs/1658733/+attachment/4808203/+files/sosreport-dotkvm.149956-20161214172157.tar.xz

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

Title:
  Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath
  root device

Status in kexec-tools package in Ubuntu:
  New
Status in makedumpfile package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 ==

  ---Problem Description---

  On a KVM guest installed to a multipath root device, the kdump kernel fails 
to mount the root file system.  This error does not occur in a similar guest 
installed to a single path device.
   
  Full console output of the kdump failure is attached.  These messages from 
the output may be relevant:

  Begin: Loading multipath modules ... Success: loaded module dm-multipath.
  done.
  Begin: Loading multipath hardware handlers ... Failure: failed to load module 
sc
  si_dh_alua.
  Failure: failed to load module scsi_dh_rdac.
  Failure: failed to load module scsi_dh_emc.
  done.
  Begin: Starting multipathd ... done.
   
  ---uname output---
  Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest 
   
   
  ---Steps to Reproduce---
   - Install Ubuntu 16.04.1 to a muiltpath target disk
  - Install kdump-tools package
  - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to 
load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg
  - Run update-grub
  - Reboot
  - Initiate a system crash using "echo c > /proc/sysrq-trigger"

  == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 ==
  Here is the log level 8 kdump console log requested in comment 10.

  == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 ==
  (In reply to comment #19)
  > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I
  > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it
  > uses .img files which I didn't found as disks).
  > 
  > Could you please recreate the guest for further debug? 

  Yes, I recreated the guest with its correct multipath lun
  configuration.  I have also attached the guest XML to this bug.

  > Besides that could you please let us know:
  >  - is the multipath the system's root? I mean / is installed/mounted on the
  > multipath device?

  Yes, the guest has only one disk.  That disk is actually a LUN from a
  fiber channel storage device with two paths on the host side.  I have
  passed through both paths to the guest, so the multipath nature of the
  target disk is known to the guest.

  In other words, the guest sees a multipath device and is using it as a
  multipath device.  The root file system is called /dev/mapper/mpatha-
  part2 on the guest.

  >  - how did you attach the device to the guest?

  Each FC LUN path on the host is mapped to a virtio-scsi controller on
  the guest using LUN passthrough.  (See the guest XML for details on
  this.)

  == Comment: #22 - Mauro Sergio Martins Rodrigues  - 2017-01-11 09:31:38 ==
  I managed to get kdump to mount rootfs and perform its tasks by setting 
KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see 
http://pastebin.hursley.ibm.com/8239

  I'm still investigating to figure out what is the reason behind this
  behavior.

  Thanks,

  --
  maurosr

  == Comment: #23 - Mauricio Faria De Oliveira  - 2017-01-11 11:56:40 ==
  Mauro,

  (In reply to comment #22)
  > I managed to get kdump to mount rootfs and perform its tasks by setting
  > KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see
  > http://pastebin.hursley.ibm.com/8239
  > 
  > I'm still investigating to figure out what is the reason behind this
  > behavior.
  > 
  > Thanks,
  > 
  > --
  > maurosr

  That would smell like an out of memory condition that is alleviated
  with a smaller number of CPUs allowed for the kernel (so the amount of
  memory associated with per-CPU stuff is less in total).

  Per the bug description, the memory reserved for the crashkernel is
  512MB:

  (In reply to comment #23)
  > - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to
  > load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg

  That seems low for Power guests/systems. 
  I think it theory is doesn't seem so, but the reality is that _for some 
reason(s)_ we require just too much memory to load and boot a kernel/initramfs 
(either on boot or kdump).

  When working w/ kdump and Ubuntu, I usually set the crashkernel
  allocated size right away to 4GB to avoid problems.

  Since this is a smaller sized guest, obviously we'd want to use less
  than that, but more than 512 MB given the evidence observed.

  

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

[Seth Forshee]

** Description changed:

+ == SRU Justification ==
+ 
+ Impact: A race in kvm can result in the EOI signal for the rtc irq to be
+ lost. After this happens no more rtc interrupts will be delivered to the
+ guest.
+ 
+ Fix: Three upstream cherry picks which fix the problem.
+ 
+ Regression Potential: These patches have been upstream since 4.6, so
+ they're well-tested at this point. Thus regressions are unlikely.
+ 
+ ---
+ 
  ADT testing for the linux package hangs at the kernel's rtc selftest,
  for example:
  
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-zesty/zesty/amd64/l/linux/20161212_132117_a258d@/log.gz
  
  Running this test manually, I've observed that this will hang in me with
  various kernel versions going back to 4.4 in a VM on my machine which is
  running xenial. The test runs to completion in a VM on a different
  machine running zesty.
  
  This is the section of the test which produces the hang:
  
- /* Turn on update interrupts (one per second) */
- retval = ioctl(fd, RTC_UIE_ON, 0);
- if (retval == -1) {
- if (errno == EINVAL) {
- fprintf(stderr,
- "\n...Update IRQs not supported.\n");
- goto test_READ;
- }
- perror("RTC_UIE_ON ioctl");
- exit(errno);
- }
+ /* Turn on update interrupts (one per second) */
+ retval = ioctl(fd, RTC_UIE_ON, 0);
+ if (retval == -1) {
+ if (errno == EINVAL) {
+ fprintf(stderr,
+ "\n...Update IRQs not supported.\n");
+ goto test_READ;
+ }
+ perror("RTC_UIE_ON ioctl");
+ exit(errno);
+ }
  
- fprintf(stderr, "Counting 5 update (1/sec) interrupts from reading 
%s:",
- rtc);
- fflush(stderr);
- for (i=1; i<6; i++) {
- /* This read will block */
- retval = read(fd, , sizeof(unsigned long));
- if (retval == -1) {
- perror("read");
- exit(errno);
- }
- fprintf(stderr, " %d",i);
- fflush(stderr);
- irqcount++;
- }
+ fprintf(stderr, "Counting 5 update (1/sec) interrupts from reading 
%s:",
+ rtc);
+ fflush(stderr);
+ for (i=1; i<6; i++) {
+ /* This read will block */
+ retval = read(fd, , sizeof(unsigned long));
+ if (retval == -1) {
+ perror("read");
+ exit(errno);
+ }
+ fprintf(stderr, " %d",i);
+ fflush(stderr);
+ irqcount++;
+ }
  
  The read blocks indefinitely most of the time. After boot it might
  return once or twice before it hangs, but running the test subsequently
  always hangs on the first read. I'll attach the full source for the test
  (rtctest.c).

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

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

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

Bug description:
  == SRU Justification ==

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

  Fix: Three upstream cherry picks which fix the problem.

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

  ---

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

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

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

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

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

  fprintf(stderr, "Counting 5 update (1/sec) interrupts 

[Kernel-packages] [Bug 1656908] Re: In Ubuntu 17.04 : after reboot getting message in console like Unable to open file: /etc/keys/x509_ima.der (-2)

[Manoj Iyer]

I would assume that the keys are generated by the emvctl package. This
would require evmctl tools packaged in Ubuntu. Could you please confirm
that this package might be a likely candidate that we might want to
carry in Ubuntu? https://sourceforge.net/p/linux-ima/ima-evm-
utils/ci/v0.9/tree/

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

** Changed in: linux (Ubuntu)
 Assignee: Taco Screen team (taco-screen-team) => Steve Langasek (vorlon)

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

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

Title:
  In Ubuntu 17.04 : after reboot getting message in console like Unable
  to open file: /etc/keys/x509_ima.der (-2)

Status in linux package in Ubuntu:
  New

Bug description:
  Installed Ubuntu17.04 as PowerVM/KVM or NV , after installation every
  reboot getting message in console

  Unable to open file: /etc/keys/x509_ima.der (-2)

  
  LOG:

  Booting Linux via __start() @ 0x0a6c ...
   -> smp_release_cpus()
  spinning_secondaries = 7
   <- smp_release_cpus()
  [0.663066] Unable to open file: /etc/keys/x509_ima.der (-2)[0.663129] 
Unable to open file: /etc/keys/x509_evm.der (-2)
  [0.792300] sd 0:0:1:0: [sda] Assuming drive cache: write through

  Ubuntu Zesty Zapus (development branch) ubuntu  hvc0

  ubuntu  login:

  Maybe this was introduced by
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643652 ? Will
  mirror this over to Launchpad for Canonical to review...

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

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

[Kernel-packages] [Bug 1658635] Re: RTC? test time-out (linux 4.9.0-12.13 ADT test failure with linux 4.9.0-12.13)

[Colin Ian King]

@Seth I'll give it a spin. Thanks!

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

Title:
  RTC? test time-out (linux 4.9.0-12.13 ADT test failure with linux
  4.9.0-12.13)

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/l/linux/20170122_155800_770b2@/log.gz

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

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

[Kernel-packages] [Bug 1658733] Adds "noirqdistrib" parameter to kdump command line

[bugproxy]

--- Comment on attachment From maur...@br.ibm.com 2017-01-23 12:10 
EDT---


This patch fixes the issue. The noirqdistrib is a necessary parameter for ppc64 
platform as stated in kdump docs 
https://www.kernel.org/doc//Documentation/kdump/kdump.txt
With this fix crash kernel uses the correct irq server for the case where only 
one cpu is online.

** Attachment added: "Adds "noirqdistrib" parameter to kdump command line"
   
https://bugs.launchpad.net/bugs/1658733/+attachment/4808196/+files/add_noirqdistrib_param_for_ppc64.diff

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

Title:
  Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath
  root device

Status in kexec-tools package in Ubuntu:
  New
Status in makedumpfile package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 ==

  ---Problem Description---

  On a KVM guest installed to a multipath root device, the kdump kernel fails 
to mount the root file system.  This error does not occur in a similar guest 
installed to a single path device.
   
  Full console output of the kdump failure is attached.  These messages from 
the output may be relevant:

  Begin: Loading multipath modules ... Success: loaded module dm-multipath.
  done.
  Begin: Loading multipath hardware handlers ... Failure: failed to load module 
sc
  si_dh_alua.
  Failure: failed to load module scsi_dh_rdac.
  Failure: failed to load module scsi_dh_emc.
  done.
  Begin: Starting multipathd ... done.
   
  ---uname output---
  Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest 
   
   
  ---Steps to Reproduce---
   - Install Ubuntu 16.04.1 to a muiltpath target disk
  - Install kdump-tools package
  - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to 
load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg
  - Run update-grub
  - Reboot
  - Initiate a system crash using "echo c > /proc/sysrq-trigger"

  == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 ==
  Here is the log level 8 kdump console log requested in comment 10.

  == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 ==
  (In reply to comment #19)
  > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I
  > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it
  > uses .img files which I didn't found as disks).
  > 
  > Could you please recreate the guest for further debug? 

  Yes, I recreated the guest with its correct multipath lun
  configuration.  I have also attached the guest XML to this bug.

  > Besides that could you please let us know:
  >  - is the multipath the system's root? I mean / is installed/mounted on the
  > multipath device?

  Yes, the guest has only one disk.  That disk is actually a LUN from a
  fiber channel storage device with two paths on the host side.  I have
  passed through both paths to the guest, so the multipath nature of the
  target disk is known to the guest.

  In other words, the guest sees a multipath device and is using it as a
  multipath device.  The root file system is called /dev/mapper/mpatha-
  part2 on the guest.

  >  - how did you attach the device to the guest?

  Each FC LUN path on the host is mapped to a virtio-scsi controller on
  the guest using LUN passthrough.  (See the guest XML for details on
  this.)

  == Comment: #22 - Mauro Sergio Martins Rodrigues  - 2017-01-11 09:31:38 ==
  I managed to get kdump to mount rootfs and perform its tasks by setting 
KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see 
http://pastebin.hursley.ibm.com/8239

  I'm still investigating to figure out what is the reason behind this
  behavior.

  Thanks,

  --
  maurosr

  == Comment: #23 - Mauricio Faria De Oliveira  - 2017-01-11 11:56:40 ==
  Mauro,

  (In reply to comment #22)
  > I managed to get kdump to mount rootfs and perform its tasks by setting
  > KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see
  > http://pastebin.hursley.ibm.com/8239
  > 
  > I'm still investigating to figure out what is the reason behind this
  > behavior.
  > 
  > Thanks,
  > 
  > --
  > maurosr

  That would smell like an out of memory condition that is alleviated
  with a smaller number of CPUs allowed for the kernel (so the amount of
  memory associated with per-CPU stuff is less in total).

  Per the bug description, the memory reserved for the crashkernel is
  512MB:

  (In reply to comment #23)
  > - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to
  > load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg

  That seems low for Power guests/systems. 
  I think it theory is doesn't seem so, but the reality is that _for some 

[Kernel-packages] [Bug 1658733] Re: Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath root device

[Mauro S M Rodrigues]

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

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

Title:
  Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath
  root device

Status in kexec-tools package in Ubuntu:
  New
Status in makedumpfile package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 ==

  ---Problem Description---

  On a KVM guest installed to a multipath root device, the kdump kernel fails 
to mount the root file system.  This error does not occur in a similar guest 
installed to a single path device.
   
  Full console output of the kdump failure is attached.  These messages from 
the output may be relevant:

  Begin: Loading multipath modules ... Success: loaded module dm-multipath.
  done.
  Begin: Loading multipath hardware handlers ... Failure: failed to load module 
sc
  si_dh_alua.
  Failure: failed to load module scsi_dh_rdac.
  Failure: failed to load module scsi_dh_emc.
  done.
  Begin: Starting multipathd ... done.
   
  ---uname output---
  Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest 
   
   
  ---Steps to Reproduce---
   - Install Ubuntu 16.04.1 to a muiltpath target disk
  - Install kdump-tools package
  - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to 
load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg
  - Run update-grub
  - Reboot
  - Initiate a system crash using "echo c > /proc/sysrq-trigger"

  == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 ==
  Here is the log level 8 kdump console log requested in comment 10.

  == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 ==
  (In reply to comment #19)
  > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I
  > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it
  > uses .img files which I didn't found as disks).
  > 
  > Could you please recreate the guest for further debug? 

  Yes, I recreated the guest with its correct multipath lun
  configuration.  I have also attached the guest XML to this bug.

  > Besides that could you please let us know:
  >  - is the multipath the system's root? I mean / is installed/mounted on the
  > multipath device?

  Yes, the guest has only one disk.  That disk is actually a LUN from a
  fiber channel storage device with two paths on the host side.  I have
  passed through both paths to the guest, so the multipath nature of the
  target disk is known to the guest.

  In other words, the guest sees a multipath device and is using it as a
  multipath device.  The root file system is called /dev/mapper/mpatha-
  part2 on the guest.

  >  - how did you attach the device to the guest?

  Each FC LUN path on the host is mapped to a virtio-scsi controller on
  the guest using LUN passthrough.  (See the guest XML for details on
  this.)

  == Comment: #22 - Mauro Sergio Martins Rodrigues  - 2017-01-11 09:31:38 ==
  I managed to get kdump to mount rootfs and perform its tasks by setting 
KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see 
http://pastebin.hursley.ibm.com/8239

  I'm still investigating to figure out what is the reason behind this
  behavior.

  Thanks,

  --
  maurosr

  == Comment: #23 - Mauricio Faria De Oliveira  - 2017-01-11 11:56:40 ==
  Mauro,

  (In reply to comment #22)
  > I managed to get kdump to mount rootfs and perform its tasks by setting
  > KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see
  > http://pastebin.hursley.ibm.com/8239
  > 
  > I'm still investigating to figure out what is the reason behind this
  > behavior.
  > 
  > Thanks,
  > 
  > --
  > maurosr

  That would smell like an out of memory condition that is alleviated
  with a smaller number of CPUs allowed for the kernel (so the amount of
  memory associated with per-CPU stuff is less in total).

  Per the bug description, the memory reserved for the crashkernel is
  512MB:

  (In reply to comment #23)
  > - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to
  > load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg

  That seems low for Power guests/systems. 
  I think it theory is doesn't seem so, but the reality is that _for some 
reason(s)_ we require just too much memory to load and boot a kernel/initramfs 
(either on boot or kdump).

  When working w/ kdump and Ubuntu, I usually set the crashkernel
  allocated size right away to 4GB to avoid problems.

  Since this is a smaller sized guest, obviously we'd want to use less
  than that, but more than 512 MB given the evidence observed.

  Hope this helps

  == Comment: #28 - Mauro Sergio Martins Rodrigues - 2017-01-13 10:12:28
  ==

  >I 

[Kernel-packages] [Bug 1658635] Re: RTC? test time-out (linux 4.9.0-12.13 ADT test failure with linux 4.9.0-12.13)

[Seth Forshee]

@cking: I think this is the same problem I looked into before, see bug
#1649718. However I completely dropped the ball on SRU-ing the patches.

tl;dr, the problem is with the host kernel for the VM losing irq acks
from the guest and then failing to trigger any subsequent interrupts. So
it's a problem in xenial and not zesty.

I will get SRU patches sent to the list for the other bug. You'll
probably just want to confirm that this one is the same problem then dup
it to that 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/1658635

Title:
  RTC? test time-out (linux 4.9.0-12.13 ADT test failure with linux
  4.9.0-12.13)

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/l/linux/20170122_155800_770b2@/log.gz

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

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

[Kernel-packages] [Bug 1653162] Re: System won't boot after upgrade to 16.04 with 4.4.0 kernel

[Joseph Salisbury]

@Jon Schewe, were you able to test any of the kernels posted in comment
#19?

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

Title:
  System won't boot after upgrade to 16.04 with 4.4.0 kernel

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

Bug description:
  I have a Dell PowerEdge 1800 with Dell CERC 1.5/6ch RAID controller in
  it. Everything worked fine under Ubuntu 14.04.1. When I upgraded to
  16.04.1 the system won't boot. It can't find the root filesystem. I
  see errors about host adapter dead on the screen many times. This is
  with kernel 4.4.0-57 and with 4.8.0-32. When I switch back to kernel
  3.13.0-105 the system boots just fine.

  I have mptbios 5.06.04.
  The CERC card says bios version 4.1-0 [Build 7403]

  When booting into the ercovery kernel I'm getting error messages about host 
adapter dead.
  Eventually I get a message:
  "aacraid: aac_fib_send: first asynchronous command timed out.
  Usually a result of a PCI interrupt routing problem
  update moher board BIOS or consider utilizing one of
  the SAFE mode kernel options (acpi, apic etc)"

  
  Using kernel parameter "intel_iommu=on" doesn't help. This was suggested on a 
post that I saw about these errors.

  Booting with "noapic" didn't help.
  Booting with "noapic noacpi" didn't help.

  
  I've also tried the dkms modules from Adaptec and that doesn't seem to help 
either.

  
  I can't figure out how to upgrade the firmware or BIOS on the system from 
Ubuntu either.

  
  This may be related to this bug: 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552551?comments=all
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=beec17b5-eac8-4e94-ac99-65b63c428b77
  InstallationDate: Installed on 2014-02-24 (1039 days ago)
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  IwConfig:
   eth1  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Dell Computer Corporation PowerEdge 1800
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-105-generic 
root=UUID=83e1b87e-adb9-4798-a6e0-18d401c91a4a ro nosplash noplymouth
  ProcVersionSignature: Ubuntu 3.13.0-105.152-generic 3.13.11-ckt39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-105-generic N/A
   linux-backports-modules-3.13.0-105-generic  N/A
   linux-firmware  1.157.6
  RfKill:
   
  Tags:  xenial
  Uname: Linux 3.13.0-105-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-12-25 (3 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/01/2004
  dmi.bios.vendor: Dell Computer Corporation
  dmi.bios.version: A00
  dmi.board.name: 0X7500
  dmi.board.vendor: Dell Computer Corporation
  dmi.board.version: A00
  dmi.chassis.type: 17
  dmi.chassis.vendor: Dell Computer Corporation
  dmi.modalias: 
dmi:bvnDellComputerCorporation:bvrA00:bd09/01/2004:svnDellComputerCorporation:pnPowerEdge1800:pvr:rvnDellComputerCorporation:rn0X7500:rvrA00:cvnDellComputerCorporation:ct17:cvr:
  dmi.product.name: PowerEdge 1800
  dmi.sys.vendor: Dell Computer Corporation

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

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

[Kernel-packages] [Bug 1658733] Re: Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath root device

[Manoj Iyer]

** Changed in: kexec-tools (Ubuntu)
 Assignee: Taco Screen team (taco-screen-team) => Louis Bouchard 
(louis-bouchard)

** Changed in: kexec-tools (Ubuntu)
   Importance: Undecided => High

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

Title:
  Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath
  root device

Status in kexec-tools package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 ==

  ---Problem Description---

  On a KVM guest installed to a multipath root device, the kdump kernel fails 
to mount the root file system.  This error does not occur in a similar guest 
installed to a single path device.
   
  Full console output of the kdump failure is attached.  These messages from 
the output may be relevant:

  Begin: Loading multipath modules ... Success: loaded module dm-multipath.
  done.
  Begin: Loading multipath hardware handlers ... Failure: failed to load module 
sc
  si_dh_alua.
  Failure: failed to load module scsi_dh_rdac.
  Failure: failed to load module scsi_dh_emc.
  done.
  Begin: Starting multipathd ... done.
   
  ---uname output---
  Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest 
   
   
  ---Steps to Reproduce---
   - Install Ubuntu 16.04.1 to a muiltpath target disk
  - Install kdump-tools package
  - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to 
load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg
  - Run update-grub
  - Reboot
  - Initiate a system crash using "echo c > /proc/sysrq-trigger"

  == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 ==
  Here is the log level 8 kdump console log requested in comment 10.

  == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 ==
  (In reply to comment #19)
  > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I
  > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it
  > uses .img files which I didn't found as disks).
  > 
  > Could you please recreate the guest for further debug? 

  Yes, I recreated the guest with its correct multipath lun
  configuration.  I have also attached the guest XML to this bug.

  > Besides that could you please let us know:
  >  - is the multipath the system's root? I mean / is installed/mounted on the
  > multipath device?

  Yes, the guest has only one disk.  That disk is actually a LUN from a
  fiber channel storage device with two paths on the host side.  I have
  passed through both paths to the guest, so the multipath nature of the
  target disk is known to the guest.

  In other words, the guest sees a multipath device and is using it as a
  multipath device.  The root file system is called /dev/mapper/mpatha-
  part2 on the guest.

  >  - how did you attach the device to the guest?

  Each FC LUN path on the host is mapped to a virtio-scsi controller on
  the guest using LUN passthrough.  (See the guest XML for details on
  this.)

  == Comment: #22 - Mauro Sergio Martins Rodrigues  - 2017-01-11 09:31:38 ==
  I managed to get kdump to mount rootfs and perform its tasks by setting 
KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see 
http://pastebin.hursley.ibm.com/8239

  I'm still investigating to figure out what is the reason behind this
  behavior.

  Thanks,

  --
  maurosr

  == Comment: #23 - Mauricio Faria De Oliveira  - 2017-01-11 11:56:40 ==
  Mauro,

  (In reply to comment #22)
  > I managed to get kdump to mount rootfs and perform its tasks by setting
  > KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see
  > http://pastebin.hursley.ibm.com/8239
  > 
  > I'm still investigating to figure out what is the reason behind this
  > behavior.
  > 
  > Thanks,
  > 
  > --
  > maurosr

  That would smell like an out of memory condition that is alleviated
  with a smaller number of CPUs allowed for the kernel (so the amount of
  memory associated with per-CPU stuff is less in total).

  Per the bug description, the memory reserved for the crashkernel is
  512MB:

  (In reply to comment #23)
  > - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to
  > load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg

  That seems low for Power guests/systems. 
  I think it theory is doesn't seem so, but the reality is that _for some 
reason(s)_ we require just too much memory to load and boot a kernel/initramfs 
(either on boot or kdump).

  When working w/ kdump and Ubuntu, I usually set the crashkernel
  allocated size right away to 4GB to avoid problems.

  Since this is a smaller sized guest, obviously we'd want to use less
  than that, but more than 512 MB given the evidence observed.

  Hope this helps

  == Comment: #28 - 

[Kernel-packages] [Bug 1655748] onza (i386) - tests ran: 3, failed: 0

[Brad Figg]

tests ran:   3, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-80.88~14.04.1-generic/onza__3.19.0-80.88~14.04.1__2017-01-23_16-21-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-80.88~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
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-80.88~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 --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1655745
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1658733] libvirt XML for multipath guest dotg9

[bugproxy]

Default Comment by Bridge

** Attachment added: "libvirt XML for multipath guest dotg9"
   https://bugs.launchpad.net/bugs/1658733/+attachment/4808167/+files/dotg9.xml

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

** Package changed: ubuntu => kexec-tools (Ubuntu)

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

Title:
  Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath
  root device

Status in kexec-tools package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 ==

  ---Problem Description---

  On a KVM guest installed to a multipath root device, the kdump kernel fails 
to mount the root file system.  This error does not occur in a similar guest 
installed to a single path device.
   
  Full console output of the kdump failure is attached.  These messages from 
the output may be relevant:

  Begin: Loading multipath modules ... Success: loaded module dm-multipath.
  done.
  Begin: Loading multipath hardware handlers ... Failure: failed to load module 
sc
  si_dh_alua.
  Failure: failed to load module scsi_dh_rdac.
  Failure: failed to load module scsi_dh_emc.
  done.
  Begin: Starting multipathd ... done.
   
  ---uname output---
  Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest 
   
   
  ---Steps to Reproduce---
   - Install Ubuntu 16.04.1 to a muiltpath target disk
  - Install kdump-tools package
  - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to 
load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg
  - Run update-grub
  - Reboot
  - Initiate a system crash using "echo c > /proc/sysrq-trigger"

  == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 ==
  Here is the log level 8 kdump console log requested in comment 10.

  == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 ==
  (In reply to comment #19)
  > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I
  > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it
  > uses .img files which I didn't found as disks).
  > 
  > Could you please recreate the guest for further debug? 

  Yes, I recreated the guest with its correct multipath lun
  configuration.  I have also attached the guest XML to this bug.

  > Besides that could you please let us know:
  >  - is the multipath the system's root? I mean / is installed/mounted on the
  > multipath device?

  Yes, the guest has only one disk.  That disk is actually a LUN from a
  fiber channel storage device with two paths on the host side.  I have
  passed through both paths to the guest, so the multipath nature of the
  target disk is known to the guest.

  In other words, the guest sees a multipath device and is using it as a
  multipath device.  The root file system is called /dev/mapper/mpatha-
  part2 on the guest.

  >  - how did you attach the device to the guest?

  Each FC LUN path on the host is mapped to a virtio-scsi controller on
  the guest using LUN passthrough.  (See the guest XML for details on
  this.)

  == Comment: #22 - Mauro Sergio Martins Rodrigues  - 2017-01-11 09:31:38 ==
  I managed to get kdump to mount rootfs and perform its tasks by setting 
KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see 
http://pastebin.hursley.ibm.com/8239

  I'm still investigating to figure out what is the reason behind this
  behavior.

  Thanks,

  --
  maurosr

  == Comment: #23 - Mauricio Faria De Oliveira  - 2017-01-11 11:56:40 ==
  Mauro,

  (In reply to comment #22)
  > I managed to get kdump to mount rootfs and perform its tasks by setting
  > KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see
  > http://pastebin.hursley.ibm.com/8239
  > 
  > I'm still investigating to figure out what is the reason behind this
  > behavior.
  > 
  > Thanks,
  > 
  > --
  > maurosr

  That would smell like an out of memory condition that is alleviated
  with a smaller number of CPUs allowed for the kernel (so the amount of
  memory associated with per-CPU stuff is less in total).

  Per the bug description, the memory reserved for the crashkernel is
  512MB:

  (In reply to comment #23)
  > - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to
  > load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg

  That seems low for Power guests/systems. 
  I think it theory is doesn't seem so, but the reality is that _for some 
reason(s)_ we require just too much memory to load and boot a kernel/initramfs 
(either on boot or kdump).

  When working w/ kdump and Ubuntu, I usually set the crashkernel
  allocated size right away to 4GB to avoid problems.

  Since this is a smaller sized guest, obviously we'd want 

[Kernel-packages] [Bug 1629784] Re: Ubuntu16.04 installation failed on IBM LE server

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

Title:
  Ubuntu16.04 installation failed on IBM LE server

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu OS installation is getting failed on IBM LE server. Please let
  us know whether this is System/OS specific issue.,

  Also please include "christy.rajku...@broadcom.com" in bug_list for
  any further information regarding bug.

  We tried installation with the image("ubuntu-16.04-server-ppc64el") that is 
available 
  under link: http://cdimage.ubuntu.com/releases/16.04.1/release/

  
  Please find the error message below.
   
   
   
   GNU GRUB  version 2.02~beta2-36ubuntu3
   
   
++
   |*Install
|
   | Rescue mode
|
   |
|
   |
|
   |
|
   |
|
   |
|
   |
|
   |
|
   |
|
   |
|
   |
|
   
++
   
Use the ^ and v keys to select which entry is highlighted.
Press enter to boot the selected OS, `e' to edit the commands
before booting or `c' for a command-line.
  '
   
  OF stdout device is: /vdevice/vty@3000
  Preparing to boot Linux version 4.4.0-21-generic (buildd@bos01-ppc64el-017) 
(gcc version 5.3.1 20160413 (Ubuntu/IBM 5.3.1-14ubuntu2) ) #37-Ubuntu SMP Mon 
Apr 18 18:30:22 UTC 2016 (Ubuntu 4.4.0-21.37-generic 4.4.6)
  Detected machine type: 0101
  Max number of cores passed to firmware: 256 (NR_CPUS = 2048)
  Calling ibm,client-architecture-support... done
  command line: BOOT_IMAGE=/install/vmlinux tasks=standard 
pkgsel/language-pack-patterns= pkgsel/install-language-support=false --- quiet
  memory layout at init:
memory_limit :  (16 MB aligned)
alloc_bottom : 0ad4
alloc_top: 1000
alloc_top_hi : 1000
rmo_top  : 1000
ram_top  : 1000
  instantiating rtas at 0x0eb8... done
  prom_hold_cpus: skipped
  copying OF device tree...
  Building dt strings...
  Building dt structure...
  Device tree strings 0x0ad5 -> 0x0ad5197e
  Device tree struct  0x0ad6 -> 0x0adb
   -> smp_release_cpus()
  spinning_secondaries = 191
   <- smp_release_cpus()
   <- setup_system()
  [1.277480] pci 0005:50:00.0: of_irq_parse_pci() failed with rc=-22
  [1.490146] pci 0007:80:00.0: of_irq_parse_pci() failed with rc=-22
  [3.611923] genirq: Flags mismatch irq 16.  (hvc_console) vs. 
 (hvsi)
  [3.611954] hvc_open: request_irq failed with rc -16.
  [3.611981] Warning: unable to open an initial console.
  Starting system log daemon: syslogd, klogd.

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

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

[Kernel-packages] [Bug 1658733] [NEW] Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath root device

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

== Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 ==

---Problem Description---

On a KVM guest installed to a multipath root device, the kdump kernel fails to 
mount the root file system.  This error does not occur in a similar guest 
installed to a single path device.
 
Full console output of the kdump failure is attached.  These messages from the 
output may be relevant:

Begin: Loading multipath modules ... Success: loaded module dm-multipath.
done.
Begin: Loading multipath hardware handlers ... Failure: failed to load module sc
si_dh_alua.
Failure: failed to load module scsi_dh_rdac.
Failure: failed to load module scsi_dh_emc.
done.
Begin: Starting multipathd ... done.
 
---uname output---
Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
 
Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest 
 
 
---Steps to Reproduce---
 - Install Ubuntu 16.04.1 to a muiltpath target disk
- Install kdump-tools package
- Configure kexec-tools to reserve sufficient RAM for the kdump kernel to load 
(I use 512MB) in /etc/default/grub.d/kexec-tools.cfg
- Run update-grub
- Reboot
- Initiate a system crash using "echo c > /proc/sysrq-trigger"

== Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 ==
Here is the log level 8 kdump console log requested in comment 10.

== Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 ==
(In reply to comment #19)
> Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I
> found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it
> uses .img files which I didn't found as disks).
> 
> Could you please recreate the guest for further debug? 

Yes, I recreated the guest with its correct multipath lun configuration.
I have also attached the guest XML to this bug.

> Besides that could you please let us know:
>  - is the multipath the system's root? I mean / is installed/mounted on the
> multipath device?

Yes, the guest has only one disk.  That disk is actually a LUN from a
fiber channel storage device with two paths on the host side.  I have
passed through both paths to the guest, so the multipath nature of the
target disk is known to the guest.

In other words, the guest sees a multipath device and is using it as a
multipath device.  The root file system is called /dev/mapper/mpatha-
part2 on the guest.

>  - how did you attach the device to the guest?

Each FC LUN path on the host is mapped to a virtio-scsi controller on
the guest using LUN passthrough.  (See the guest XML for details on
this.)

== Comment: #22 - Mauro Sergio Martins Rodrigues  - 2017-01-11 09:31:38 ==
I managed to get kdump to mount rootfs and perform its tasks by setting 
KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see 
http://pastebin.hursley.ibm.com/8239

I'm still investigating to figure out what is the reason behind this
behavior.

Thanks,

--
maurosr

== Comment: #23 - Mauricio Faria De Oliveira  - 2017-01-11 11:56:40 ==
Mauro,

(In reply to comment #22)
> I managed to get kdump to mount rootfs and perform its tasks by setting
> KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see
> http://pastebin.hursley.ibm.com/8239
> 
> I'm still investigating to figure out what is the reason behind this
> behavior.
> 
> Thanks,
> 
> --
> maurosr

That would smell like an out of memory condition that is alleviated with
a smaller number of CPUs allowed for the kernel (so the amount of memory
associated with per-CPU stuff is less in total).

Per the bug description, the memory reserved for the crashkernel is
512MB:

(In reply to comment #23)
> - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to
> load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg

That seems low for Power guests/systems. 
I think it theory is doesn't seem so, but the reality is that _for some 
reason(s)_ we require just too much memory to load and boot a kernel/initramfs 
(either on boot or kdump).

When working w/ kdump and Ubuntu, I usually set the crashkernel
allocated size right away to 4GB to avoid problems.

Since this is a smaller sized guest, obviously we'd want to use less
than that, but more than 512 MB given the evidence observed.

Hope this helps

== Comment: #28 - Mauro Sergio Martins Rodrigues - 2017-01-13 10:12:28
==

>I think it theory is doesn't seem so, but the reality is that _for some
reason(s)_ we require just too >much memory to load and boot a
kernel/initramfs (either on boot or kdump).

For the record, as you already know, I've raise memory up to 1024mb and
it didn't help.


>Per yesterday's conversations, this had to do with IRQ distribution and the 
>nr_cpus kernel parameter, >and seemed to affect multipath only by chance, 
>usually failing/hanging the guest at kdump at other >parts / way earlier in 
>boot (at virtio-scsi disk probe phase too).

Yes, that's right. So looks like there are a couple of 

[Kernel-packages] [Bug 1626894] Re: nvme drive probe failure

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

Title:
  nvme drive probe failure

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

Bug description:
  After upgrading from linux-image-4.4.0-38-generic to proposed update
  linux-image-4.4.0-39-generic, NVMe drives are no longer working. dmesg
  shows a probe failure.

  On the previous kernel version everything is working as expected.
  ->%-
  [1.005243] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 
R1.12.0.SR.2 for D3417-B1x   04/01/2016
  [1.005349] Workqueue: events nvme_remove_dead_ctrl_work [nvme]
  [1.005484]  0286 b6c91251 880fe6e8bce0 
813f1f83
  [1.005800]  880fe02150f0 c90006a7c000 880fe6e8bd00 
8106bdff
  [1.006117]  880fe02150f0 880fe0215258 880fe6e8bd10 
8106be3c
  [1.006433] Call Trace:
  [1.006509]  [] dump_stack+0x63/0x90
  [1.006589]  [] iounmap.part.1+0x7f/0x90
  [1.006668]  [] iounmap+0x2c/0x30
  [1.006770]  [] nvme_dev_unmap.isra.35+0x1a/0x30 [nvme]
  [1.007048]  [] nvme_remove+0xce/0xe0 [nvme]
  [1.007140]  [] pci_device_remove+0x39/0xc0
  [1.007220]  [] __device_release_driver+0xa1/0x150
  [1.007301]  [] device_release_driver+0x23/0x30
  [1.007382]  [] pci_stop_bus_device+0x8a/0xa0
  [1.007462]  [] 
pci_stop_and_remove_bus_device_locked+0x1a/0x30
  [1.007559]  [] nvme_remove_dead_ctrl_work+0x3c/0x50 
[nvme]
  [1.007642]  [] process_one_work+0x165/0x480
  [1.007722]  [] worker_thread+0x4b/0x4c0
  [1.007801]  [] ? process_one_work+0x480/0x480
  [1.007881]  [] kthread+0xd8/0xf0
  [1.007959]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [1.008041]  [] ret_from_fork+0x3f/0x70
  [1.008120]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [1.008222] Trying to free nonexistent resource 

  [1.008276] genirq: Flags mismatch irq 0. 0080 (nvme1q0) vs. 00015a00 
(timer)
  [1.008281] Trying to free nonexistent resource 

  [1.008282] nvme :02:00.0: Removing after probe failure
  [1.008645] Trying to free nonexistent resource 

  [1.027213] iounmap: bad address c90006ae
  [1.027456] CPU: 2 PID: 86 Comm: kworker/2:1 Not tainted 4.4.0-39-generic 
#59-Ubuntu
  -%<-

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

-- 
Mailing list: https://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 1532746] Re: SHIFT, ALT and CTRL problem with HP pavilion 15 ab062nl

[Patrick Laurin]

I'm now currently using 4.10-RC4 Linux Mint and no keyboard issue.

On 20 January 2017 at 05:04, Dea1993 
wrote:

> problem still present on Kernel 4.9
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1532746
>
> Title:
>   SHIFT, ALT and CTRL problem with HP pavilion 15 ab062nl
>
> Status in linux package in Ubuntu:
>   Triaged
>
> Bug description:
>   I've a problem with the keyboard of notebook HP Pavilion 15 ab062nl.
>   the problem is with SHIFT ALT and CTRL buttons of the keyboard.
>
>   for example when i use ALT-TAB shortcut, after few seconds, the ALT-TAB
> menu disappear as if i release ALT key, but isn't so.
>   another example is when i navigate on web, when i scroll page with mouse
> wheel, sometimes the page start to resize, as if i'm pressing CTRL command
> while scroll, or if i'm writing a text, sometimes, borwser launch shortcut,
> as if i'm pressing CTRL while i type text, for exaple if i'm typing "b"
> letter, opens bookmarks...
>
>   another example is while i'm typing text, if i press SHIFT key and
>   start typing, begins to write uppercase letters and after a while,
>   writes lowercase like I released shift, but i'm still pressing shift.
>
>   for example if i press SHIFT+s, the result is this:
>   SSs
>   some letters are uppercase, but others are lowercase.
>
>   WORKAROUND: Use kernel parameter:
>   i8042.dumbkbd
>
>   the only way to solve momentarily the problem, is pressing for some
>   seconds the only SHIFT key, after that, the problems disappears
>   indefinitely, or until the next restart.
>
>   This problem occurs with all ubuntu version (x86 and x86_64), now i'm
>   using Ubuntu 15.10, but i've also tried ubuntu 15.04, ubuntu 14.04,
>   ubuntu 12.04, ubuntu 10.04.
>
>   furthermore i've this problem also with other GNU/Linux Distributions
> (i've tried Fedora, OpenSuse, ArchLinux, Antergos, Debian, SteamOS).
>   but isn't and hardware problem, because on Windows 8.1 and Windows 10 i
> haven't these problems.
>
>   i've also tried to plug in an externa USB keyboard, and if i use
>   external USB keybaord i haven't problems.
>
>   i think is a problem of compatibility, with integrated keyboard of
>   this notebook.
>
>   i've tried to monitor these problems using XEV, and the results is
>   that also if i'm not using notebook, sometimes XEV reads an INPUT of
>   one of these 3 key (SHIFT, ALT, CTRL), and while i'm pressing one of
>   these 3 key, XEV see also if i release and immedialty after press
>   again the key.
>
>   this is an example of the input while i press Left_ALT key for a while
>
>   KeyPress event, serial 37, synthetic NO, window 0x3e1,
>   root 0x498, subw 0x0, time 129987, (-142,152), root:(452,476),
>   state 0x10, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
>   XLookupString gives 0 bytes:
>   XmbLookupString gives 0 bytes:
>   XFilterEvent returns: False
>
>   KeyRelease event, serial 37, synthetic NO, window 0x3e1,
>   root 0x498, subw 0x0, time 130147, (-142,152), root:(452,476),
>   state 0x18, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
>   XLookupString gives 0 bytes:
>   XFilterEvent returns: False
>
>   KeyPress event, serial 37, synthetic NO, window 0x3e1,
>   root 0x498, subw 0x0, time 130391, (-142,152), root:(452,476),
>   state 0x10, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
>   XLookupString gives 0 bytes:
>   XmbLookupString gives 0 bytes:
>   XFilterEvent returns: False
>
>   whole log here http://pastebin.com/CPGz40aw
>
>   and this is the output of xev, leaving the notebook on a few hours
>   without using it http://pastebin.com/sYSHAbGy
>
>   this is "xinput" output
>
>   ⎡ Virtual core pointerid=2[master pointer
> (3)]
>   ⎜   ↳ Virtual core XTEST pointer  id=4[slave
> pointer  (2)]
>   ⎜   ↳ Logitech USB Laser Mouseid=11   [slave
> pointer  (2)]
>   ⎜   ↳ SynPS/2 Synaptics TouchPad  id=13   [slave
> pointer  (2)]
>   ⎣ Virtual core keyboard   id=3[master keyboard
> (2)]
>   ↳ Virtual core XTEST keyboard id=5[slave
> keyboard (3)]
>   ↳ Power Buttonid=6[slave
> keyboard (3)]
>   ↳ Video Bus   id=7[slave
> keyboard (3)]
>   ↳ Video Bus   id=8[slave
> keyboard (3)]
>   ↳ Power Buttonid=9[slave
> keyboard (3)]
>   ↳ HP Truevision HDid=10   [slave
> keyboard (3)]
>   ↳ AT Translated Set 2 keyboardid=12   [slave
> keyboard (3)]
>   ↳ HP WMI hotkeys  id=14   [slave
> keyboard (3)]
> 

[Kernel-packages] [Bug 1655748] onza (amd64) - tests ran: 33, failed: 5

[Brad Figg]

tests ran:  33, failed: 5;
  
http://kernel.ubuntu.com/testing/3.19.0-80.88~14.04.1-generic/onza__3.19.0-80.88~14.04.1__2017-01-23_15-18-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-80.88~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
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-80.88~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 --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1655745
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

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

[bugproxy]

--- Comment From cha...@us.ibm.com 2017-01-23 10:48 EDT---
*** Bug 150359 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/1635063

Title:
  Ubuntu 16.10: System hangs after crash on Ubuntu KVM guest.

Status in linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---

  Ubuntu 16.10: System hangs after crash on Ubuntu KVM guest.

  ---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:/var/crash# 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
  root@ubuntu:/var/crash# 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-17-generic
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.8.0-17-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.8.0-17-generic 
root=UUID=70f3c690-fe90-444d-a74c-71c05eef8b0e 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:/var/crash# echo c > /proc/sysrq-trigger
  [  202.677946] sysrq: SysRq : Trigger a crash
  [  202.678018] Unable to handle kernel paging request for data at address 
0x
  [  202.678098] Faulting instruction address: 0xc06de134
  [  202.678169] Oops: Kernel access of bad area, sig: 11 [#1]
  [  202.678222] SMP NR_CPUS=2048 NUMA pSeries
  [  202.678281] Modules linked in: vmx_crypto ip_tables x_tables autofs4 
ibmvscsi crc32c_vpmsum 8139too 8139cp mii
  [  202.678465] CPU: 3 PID: 1992 Comm: bash Not tainted 4.8.0-17-generic 
#19-Ubuntu
  [  202.678547] task: c4c5ce00 task.stack: c428c000
  [  202.678612] NIP: c06de134 LR: c06df218 CTR: 
c06de100
  [  202.678716] REGS: c428f990 TRAP: 0300   Not tainted  
(4.8.0-17-generic)
  [  202.678796] MSR: 80009033   CR: 2824  
XER: 2000
  [  202.678992] CFAR: c0014f84 DAR:  DSISR: 4200 
SOFTE: 1 
  GPR00: c06df218 c428fc10 c14e5e00 0063 
  GPR04: c0007fecaca0 c0007fedfb40 c168d278 4b78 
  GPR08: 0007 0001  0001 
  GPR12: c06de100 c7b81b00  2200 
  GPR16: 10170dc8 010020c60488 10140f58 100c7570 
  GPR20:  1017dd58 10153618 1017b608 
  GPR24: 3fffd5f377c4 0001 c13fe5d0 0004 
  GPR28: c13fe990 0063 c13b2590  
  [  202.680090] NIP [c06de134] sysrq_handle_crash+0x34/0x50
  [  202.680159] LR [c06df218] __handle_sysrq+0xe8/0x280
  [  202.680213] Call Trace:
  [  202.680246] [c428fc10] [c0e79720] 
_fw_tigon_tg3_bin_name+0x2f1a8/0x36f48 (unreliable)
  [  202.680356] [c428fc30] [c06df218] __handle_sysrq+0xe8/0x280
  [  202.680440] [c428fcd0] [c06df9c8] 
write_sysrq_trigger+0x78/0xa0
  [  202.680535] [c428fd00] [c03cf890] proc_reg_write+0xb0/0x110
  [  202.680618] [c428fd50] [c032b5dc] __vfs_write+0x6c/0xe0
  [  202.680702] [c428fd90] [c032cae4] vfs_write+0xd4/0x240
  [  202.680783] [c428fde0] [c032e7fc] SyS_write+0x6c/0x110
  [  202.680867] [c428fe30] [c0009584] system_call+0x38/0xec
  [  202.680948] Instruction dump:
  [  202.680991] 38427d00 7c0802a6 f8010010 f821ffe1 6000 6000 3d22001a 
3949d1e0 
  [  202.681133] 3921 912a 7c0004ac 3940 <992a> 38210020 
e8010010 7c0803a6 
  [  202.681276] ---[ end trace 3e9cbc319000fff4 ]---
  [  202.684658] 
  [  202.684718] Sending IPI to other CPUs
  [  202.686765] IPI complete
  I'm in purgatory
   -> smp_release_cpus()
  spinning_secondaries = 3
   <- smp_release_cpus()
  Linux ppc64le
  #19-Ubuntu SMP S[  242.661649] INFO: task swapper/0:1 blocked for more than 
120 seconds.
  [  242.661708]   Not tainted 4.8.0-17-generic #19-Ubuntu
  [  242.661746] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  363.493648] 

[Kernel-packages] [Bug 1650062] Re: Ubuntu16.04.01VM:Docker-Powervm aufs bad file panic while running tests in a docker container

[Seth Forshee]

I haven't found any obvious source in aufs for the extra fputs which I
suspect are causing this problem. If you could either give me more
information so I can run the same tests myself (I'm guessing the problem
isn't arch-specific) or else reproduce the problem with the kernel
patched with something like the following, perhaps we can catch it in
the act. However we also might just catch legitimate fputs since the
erroneous ones could occur while the refcount is still positive ...

diff --git a/fs/file_table.c b/fs/file_table.c
index df66450fb443..d4911a6e8331 100644
--- a/fs/file_table.c
+++ b/fs/file_table.c
@@ -264,7 +264,9 @@ static DECLARE_DELAYED_WORK(delayed_fput_work, 
delayed_fput);
 
 void fput(struct file *file)
 {
-   if (atomic_long_dec_and_test(>f_count)) {
+   long cnt = atomic_long_dec_return(>f_count);
+   WARN_ON(cnt < 0);
+   if (cnt == 0) {
struct task_struct *task = current;
 
if (likely(!in_interrupt() && !(task->flags & PF_KTHREAD))) {

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

Title:
  Ubuntu16.04.01VM:Docker-Powervm aufs bad file panic while running
  tests in a docker container

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Vinutha GS - 2016-12-13 02:47:35 ==
  When some of the base and io tests were run inside a docker container, the 
par crashed and below are the stack trace and other details.

  Steps to re-create -
  1. Install 16.04.02 on a PowerVM lpar.
  2. Ran setup general.
  3. Ran docker scripts[home grown scripts] which does docker package 
installation and other setups required to run STAF cases inside docker 
container.
  4. We have docker image using which we launch containers and start tests 
inside containers.
  If complete details are required on how to execute scripts, please let me 
know.
  5. STAF Base and IO tests were started inside containers successfully, after 
sometime, I see partition is in XMON.

  Docker info -
  docker info
  Containers: 0
   Running: 0
   Paused: 0
   Stopped: 0
  Images: 0
  Server Version: 1.12.1
  Storage Driver: aufs
   Root Dir: /var/lib/docker/aufs
   Backing Filesystem: extfs
   Dirs: 0
   Dirperm1 Supported: true
  Logging Driver: json-file
  Cgroup Driver: cgroupfs
  Plugins:
   Volume: local
   Network: null host bridge overlay
  Swarm: inactive
  Runtimes: runc
  Default Runtime: runc
  Security Options: apparmor
  Kernel Version: 4.4.0-53-generic
  Operating System: Ubuntu 16.04.1 LTS
  OSType: linux
  Architecture: ppc64le
  CPUs: 24
  Total Memory: 49.89 GiB
  Name: bamlp3
  ID: I7VI:G4RJ:RHTQ:WNGV:52FK:K7AZ:YDJQ:KFUM:P3UA:MZ3I:5XUY:WV3N
  Docker Root Dir: /var/lib/docker
  Debug Mode (client): false
  Debug Mode (server): false
  Registry: https://index.docker.io/v1/
  WARNING: No swap limit support
  Insecure Registries:
   127.0.0.0/8

  docker ps -a
  CONTAINER IDIMAGE   COMMAND  CREATED  
   STATUS  PORTS   NAMES
  61f2b8ab0a8632d545c3ea01"/bin/sh -c ./staf_io"   24 minutes 
ago  Up 24 minutes   bamlp3-io
  151da0322172590e44f15214"/bin/sh -c ./staf_ba"   30 minutes 
ago  Up 30 minutes   bamlp3-base

  
  Stack trace -
  8:mon> t
  [c00a5e147d10] da04ca98 aufs_flush_nondir+0x38/0x50 [aufs]
  [c00a5e147d40] c02e0428 filp_close+0x68/0xe0
  [c00a5e147dc0] c030f71c __close_fd+0xcc/0x150
  [c00a5e147e00] c02e04d4 SyS_close+0x34/0x90
  [c00a5e147e30] c0009204 system_call+0x38/0xb4
  --- Exception: c00 (System Call) at 3fff8bc217d8
  SP (3fffd85203b0) is in userspace
  8:mon> e
  cpu 0x8: Vector: 300 (Data Access) at [c00a5e147a40]
  pc: da04bdd4: au_do_flush+0x44/0x220 [aufs]
  lr: da04ca98: aufs_flush_nondir+0x38/0x50 [aufs]
  sp: c00a5e147cc0
 msr: 80009033
 dar: 28
   dsisr: 4000
current = 0xc00a8b7fc8e0
paca= 0xcfb44c00 softe: 0irq_happened: 0x01
  pid   = 11936, comm = remap_file_page
  8:mon>

  Release details -
  uname -r
  4.4.0-53-generic

   uname -a
  Linux bamlp4 4.4.0-53-generic #74-Ubuntu SMP Fri Dec 2 15:59:36 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  == Comment: #6 - Vinutha GS  - 2016-12-14 03:16:18 ==
  Please find the attached sosreport.
  Also i have followed the steps for k-dump, It is enabled now.
  I'm going to start the tests once again.

  == Comment: #12 - Kevin W. Rudd - 2016-12-14 16:06:46 ==
  The basic reason for the panic is that close was called on a file 
  that was no longer valid.  The f_count value was -8 for some reason,
  so it passed the following check in filep_close():

  if (!file_count(filp)) {
  printk(KERN_ERR "VFS: Close: file count 

[Kernel-packages] [Bug 1658635] Re: RTC? test time-out (linux 4.9.0-12.13 ADT test failure with linux 4.9.0-12.13)

[Colin Ian King]

OK, can you run a few more tests and we can see how variable this is,
e.g, does it trigger every time 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/1658635

Title:
  RTC? test time-out (linux 4.9.0-12.13 ADT test failure with linux
  4.9.0-12.13)

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/l/linux/20170122_155800_770b2@/log.gz

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

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

[Kernel-packages] [Bug 1065400] Re: Support for loading Broadcom bluetooth firmware

[Brinstar]

This may seem like a bizarre fix but I read about someone else trying it
and so having run into the issue with no Bluetooth device appearing, I
gave it a try. TL;DR version, you need to install Windows 7 (or any
other recent version), install the official Dell Bluetooth drivers, the
adapter should switch on and become available in Windows. Once it does,
reboot and install Ubuntu and the device should become available in
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/1065400

Title:
  Support for loading Broadcom bluetooth firmware

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in linux source package in Quantal:
  Fix Released
Status in linux source package in Raring:
  Fix Released
Status in linux source package in Saucy:
  Fix Released
Status in linux source package in Trusty:
  Confirmed

Bug description:
  Broadcom bluetooth chips require a tool called patchram uploader [1]
  to load firmware. This applies to at least BCM20702 and BCM43142.
  Although some of the devices have an OTPROM that contains required
  firmware, but it is found that these devices would not have HFP/HSP
  support unless a upgraded firmware is loaded via patchram uploader.

  This tool requires hci device to do the firmware loading, but this may
  cause some race condition between patchram tool and bluetoothd or
  something that also works on hci interface.

  Also it needs some hooks to make firmware loads after bootup, s3,  s4,
  rfkill, and device hotplug events. Implement this loader in kernel
  module would make things more easier.

  [1] http://marc.info/?l=linux-bluetooth=132039175324993=2

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

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

[Kernel-packages] [Bug 1658633] Re: stress_smoke_test passing and exiting rc=9 (linux 4.9.0-12.13 ADT test failure with linux 4.9.0-12.13)

[Colin Ian King]

Right, I think this occurs when ext4 goes read-only. A simple way to
reproduce this on i386 systems with that kernel is:

sudo stress-ng --sockpair 10 && sudo stress-ng --xattr 10

xattr test causes ext4 to detect xattr issues and the file system gets
remounted r/o, and we no longer can log the stress-ng ADT test log.

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

Title:
  stress_smoke_test passing and exiting rc=9 (linux 4.9.0-12.13 ADT test
  failure with linux 4.9.0-12.13)

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Testing failed on:
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/ppc64el/l/linux/20170122_110123_770b2@/log.gz

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

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

[Kernel-packages] [Bug 1654971] Re: linux 4.4.0-59.80 ADT test failure with linux 4.4.0-59.80

[Colin Ian King]

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

Title:
  linux 4.4.0-59.80 ADT test failure with linux 4.4.0-59.80

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Testing failed on:
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20170109_080549_35691@/log.gz

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

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

[Kernel-packages] [Bug 1658635] Re: RTC? test time-out (linux 4.9.0-12.13 ADT test failure with linux 4.9.0-12.13)

[Andy Whitcroft]

@cking mostly using magic, i can trigger new ones etc if that helps.

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

Title:
  RTC? test time-out (linux 4.9.0-12.13 ADT test failure with linux
  4.9.0-12.13)

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/l/linux/20170122_155800_770b2@/log.gz

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

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

[Kernel-packages] [Bug 1559576] Re: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers

[Giuseppe Pennisi]

Same problem. I think is not acceptable that this bug is still 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/1559576

Title:
  Ubuntu GNOME boots to black screen when using proprietary Nvidia
  drivers

Status in gdm:
  Confirmed
Status in Ubuntu GNOME:
  Triaged
Status in gdm3 package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Invalid
Status in gdm3 source package in Xenial:
  Triaged
Status in linux source package in Xenial:
  Invalid

Bug description:
  Using latest Ubuntu Gnome x64 daily build with all updates installed. 
  Lenovo Z70-80 laptop with Nvidia 840M, BIOS updated to latest version, secure 
boot and other potentially problematic BIOS settings disabled.

  Can only see a black screen instead of a log-in screen after boot completes 
when proprietary Nvidia drivers are installed.
  Regular Ubuntu works absolutely fine on the same machine with the same driver 
version. Attempting to use older drivers on Ubuntu Gnome made no difference.

  Bug is affecting more than just me. We were talking about workarounds
  in ubuntuforums. User fthx claims that switching to lightdm fixes the
  issue
  http://ubuntuforums.org/showthread.php?t=2317628=13457703#post13457703

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-14-generic 4.4.0-14.30
  ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
  Uname: Linux 4.4.0-14-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Sat Mar 19 23:19:21 2016
  HibernationDevice: RESUME=UUID=4f8fb76c-f99d-4c54-8a67-eed0653d8eb6
  InstallationDate: Installed on 2016-03-19 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160318)
  MachineType: LENOVO 80FG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-14-generic.efi.signed 
root=UUID=572a19f6-7324-4269-ad36-7ffc9919f7a2 ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-14-generic N/A
   linux-backports-modules-4.4.0-14-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/22/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: ABCN96WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo Z70-80
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z70-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrABCN96WW:bd09/22/2015:svnLENOVO:pn80FG:pvrLenovoZ70-80:rvnLENOVO:rnLenovoZ70-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoZ70-80:
  dmi.product.name: 80FG
  dmi.product.version: Lenovo Z70-80
  dmi.sys.vendor: LENOVO

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

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

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

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-80.88~14.04.1-generic/onza__3.19.0-80.88~14.04.1__2017-01-23_14-53-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-80.88~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
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-80.88~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 --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1655745
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1658635] Re: RTC? test time-out (linux 4.9.0-12.13 ADT test failure with linux 4.9.0-12.13)

[Colin Ian King]

@apw, how are you invoking these tests on prodstack? I can't reproduce
this issue across the VMs I'm using.

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

Title:
  RTC? test time-out (linux 4.9.0-12.13 ADT test failure with linux
  4.9.0-12.13)

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/l/linux/20170122_155800_770b2@/log.gz

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

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