date:20180226

** Package changed: kernel-package (Ubuntu) => linux (Ubuntu)

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-power-systems
   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/1752002

Title:
  [P9,POwer NV][WSP][DD2.1][Ubuntu 1804][Perf fuzzer] : Call trace is
  seen while running perf fuzzer (perf:)

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

Bug description:
  == Comment: #0 - Shriya R. Kulkarni  - 2018-02-02 
01:21:36 ==
  Problem Description :
  =

  Warn on message is seen while running perf fuzzer tests.

  Machine details :
  ==
  Hardware : Witherspoon (wsp12) + DD2.1
  OS : Ubuntu 1804
  uname -a : 4.13.0-32-generic #35~lp1746225 ( Kernel from the bug : 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=164107#c7 )

  
  Steps to reproduce :
  
  Build Kernel :
  
  To avoid the kernel crash due to Perf fuzzer , use the kernel mentioned in 
the link : https://bugzilla.linux.ibm.com/show_bug.cgi?id=164107#c7

  #! /bin/bash
  set -x
  git clone https://github.com/deater/perf_event_tests.git
  cd perf_event_tests/include
  mkdir asm
  cd asm
  wget http://9.114.13.132/repo/shriya/perf_regs.h
  cd ../../lib
  make
  sleep 10
  cd ../fuzzer
  make
  sleep 10

  echo 0 > /proc/sys/kernel/nmi_watchdog
  echo 2 > /proc/sys/kernel/perf_event_paranoid
  echo 10 > /proc/sys/kernel/perf_event_max_sample_rate
  ./perf_fuzzer -r 1492143527

  
  Call trace :
  ===
  [  329.228031] [ cut here ]
  [  329.228039] WARNING: CPU: 43 PID: 9088 at 
/home/jsalisbury/bugs/lp1746225/ubuntu-artful/kernel/events/core.c:3038 
perf_pmu_sched_task+0x170/0x180
  [  329.228040] Modules linked in: ofpart at24 uio_pdrv_genirq uio cmdlinepart 
powernv_flash mtd ipmi_powernv vmx_crypto ipmi_devintf ipmi_msghandler 
ibmpowernv opal_prd crct10dif_vpmsum sch_fq_codel ip_tables x_tables autofs4 
crc32c_vpmsum lpfc ast i2c_algo_bit drm_kms_helper syscopyarea sysfillrect 
sysimgblt mlx5_core fb_sys_fops ttm tg3 nvmet_fc drm ahci nvmet nvme_fc libahci 
nvme_fabrics mlxfw nvme_core devlink scsi_transport_fc
  [  329.228068] CPU: 43 PID: 9088 Comm: perf_fuzzer Not tainted 
4.13.0-32-generic #35~lp1746225
  [  329.228070] task: c03f776ac900 task.stack: c03f77728000
  [  329.228071] NIP: c0299b70 LR: c02a4534 CTR: 
c029bb80
  [  329.228073] REGS: c03f7772b760 TRAP: 0700   Not tainted  
(4.13.0-32-generic)
  [  329.228073] MSR: 9282b033 
  [  329.228079]   CR: 24008822  XER: 
  [  329.228080] CFAR: c0299a70 SOFTE: 0 
 GPR00: c02a4534 c03f7772b9e0 c1606200 
c03fef858908 
 GPR04: c03f776ac900 0001  
003fee73 
 GPR08:   c11220d8 
0002 
 GPR12: c029bb80 c7a3d900  
 
 GPR16:    
 
 GPR20:   c03f776ad090 
c0c71354 
 GPR24: c03fef716780 003fee73 c03fe69d4200 
c03f776ad330 
 GPR28: c11220d8 0001 c14c6108 
c03fef858900 
  [  329.228098] NIP [c0299b70] perf_pmu_sched_task+0x170/0x180
  [  329.228100] LR [c02a4534] __perf_event_task_sched_in+0xc4/0x230
  [  329.228101] Call Trace:
  [  329.228102] [c03f7772b9e0] [c02a0678] 
perf_iterate_sb+0x158/0x2a0 (unreliable)
  [  329.228105] [c03f7772ba30] [c02a4534] 
__perf_event_task_sched_in+0xc4/0x230
  [  329.228107] [c03f7772bab0] [c01396dc] 
finish_task_switch+0x21c/0x310
  [  329.228109] [c03f7772bb60] [c0c71354] __schedule+0x304/0xb80
  [  329.228111] [c03f7772bc40] [c0c71c10] schedule+0x40/0xc0
  [  329.228113] [c03f7772bc60] [c01033f4] do_wait+0x254/0x2e0
  [  329.228115] [c03f7772bcd0] [c0104ac0] kernel_wait4+0xa0/0x1a0
  [  329.228117] [c03f7772bd70] [c0104c24] SyS_wait4+0x64/0xc0
  [  329.228121] [c03f7772be30] [c000b184] system_call+0x58/0x6c
  [  329.228121] Instruction dump:
  [  329.228123] 3beafea0 7faa4800 409eff18 e8010060 eb610028 ebc10040 7c0803a6 
38210050 
  [  329.228127] eb81ffe0 eba1ffe8 ebe1fff8 4e800020 <0fe0> 4bbc 
6000 6042 
  [  329.228131] ---[ end trace 8c46856d314c1811 ]---
  [  375.755943] hrtimer: interrupt took 31601 ns

  == Comment: #4 - SEETEENA THOUFEEK  - 2018-02-05
  06:34:09 ==

  
  == Comment: #5 - SEETEENA THOUFEEK

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

** Tags added: kernel-key

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1752002] [NEW] [P9, POwer NV][WSP][DD2.1][Ubuntu 1804][Perf fuzzer] : Call trace is seen while running perf fuzzer (perf:)

You have been subscribed to a public bug:

== Comment: #0 - Shriya R. Kulkarni  - 2018-02-02 01:21:36 
==
Problem Description :
=

Warn on message is seen while running perf fuzzer tests.

Machine details :
==
Hardware : Witherspoon (wsp12) + DD2.1
OS : Ubuntu 1804
uname -a : 4.13.0-32-generic #35~lp1746225 ( Kernel from the bug : 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=164107#c7 )


Steps to reproduce :

Build Kernel :

To avoid the kernel crash due to Perf fuzzer , use the kernel mentioned in the 
link : https://bugzilla.linux.ibm.com/show_bug.cgi?id=164107#c7

#! /bin/bash
set -x
git clone https://github.com/deater/perf_event_tests.git
cd perf_event_tests/include
mkdir asm
cd asm
wget http://9.114.13.132/repo/shriya/perf_regs.h
cd ../../lib
make
sleep 10
cd ../fuzzer
make
sleep 10

echo 0 > /proc/sys/kernel/nmi_watchdog
echo 2 > /proc/sys/kernel/perf_event_paranoid
echo 10 > /proc/sys/kernel/perf_event_max_sample_rate
./perf_fuzzer -r 1492143527


Call trace :
===
[  329.228031] [ cut here ]
[  329.228039] WARNING: CPU: 43 PID: 9088 at 
/home/jsalisbury/bugs/lp1746225/ubuntu-artful/kernel/events/core.c:3038 
perf_pmu_sched_task+0x170/0x180
[  329.228040] Modules linked in: ofpart at24 uio_pdrv_genirq uio cmdlinepart 
powernv_flash mtd ipmi_powernv vmx_crypto ipmi_devintf ipmi_msghandler 
ibmpowernv opal_prd crct10dif_vpmsum sch_fq_codel ip_tables x_tables autofs4 
crc32c_vpmsum lpfc ast i2c_algo_bit drm_kms_helper syscopyarea sysfillrect 
sysimgblt mlx5_core fb_sys_fops ttm tg3 nvmet_fc drm ahci nvmet nvme_fc libahci 
nvme_fabrics mlxfw nvme_core devlink scsi_transport_fc
[  329.228068] CPU: 43 PID: 9088 Comm: perf_fuzzer Not tainted 
4.13.0-32-generic #35~lp1746225
[  329.228070] task: c03f776ac900 task.stack: c03f77728000
[  329.228071] NIP: c0299b70 LR: c02a4534 CTR: c029bb80
[  329.228073] REGS: c03f7772b760 TRAP: 0700   Not tainted  
(4.13.0-32-generic)
[  329.228073] MSR: 9282b033 
[  329.228079]   CR: 24008822  XER: 
[  329.228080] CFAR: c0299a70 SOFTE: 0 
   GPR00: c02a4534 c03f7772b9e0 c1606200 
c03fef858908 
   GPR04: c03f776ac900 0001  
003fee73 
   GPR08:   c11220d8 
0002 
   GPR12: c029bb80 c7a3d900  
 
   GPR16:    
 
   GPR20:   c03f776ad090 
c0c71354 
   GPR24: c03fef716780 003fee73 c03fe69d4200 
c03f776ad330 
   GPR28: c11220d8 0001 c14c6108 
c03fef858900 
[  329.228098] NIP [c0299b70] perf_pmu_sched_task+0x170/0x180
[  329.228100] LR [c02a4534] __perf_event_task_sched_in+0xc4/0x230
[  329.228101] Call Trace:
[  329.228102] [c03f7772b9e0] [c02a0678] 
perf_iterate_sb+0x158/0x2a0 (unreliable)
[  329.228105] [c03f7772ba30] [c02a4534] 
__perf_event_task_sched_in+0xc4/0x230
[  329.228107] [c03f7772bab0] [c01396dc] 
finish_task_switch+0x21c/0x310
[  329.228109] [c03f7772bb60] [c0c71354] __schedule+0x304/0xb80
[  329.228111] [c03f7772bc40] [c0c71c10] schedule+0x40/0xc0
[  329.228113] [c03f7772bc60] [c01033f4] do_wait+0x254/0x2e0
[  329.228115] [c03f7772bcd0] [c0104ac0] kernel_wait4+0xa0/0x1a0
[  329.228117] [c03f7772bd70] [c0104c24] SyS_wait4+0x64/0xc0
[  329.228121] [c03f7772be30] [c000b184] system_call+0x58/0x6c
[  329.228121] Instruction dump:
[  329.228123] 3beafea0 7faa4800 409eff18 e8010060 eb610028 ebc10040 7c0803a6 
38210050 
[  329.228127] eb81ffe0 eba1ffe8 ebe1fff8 4e800020 <0fe0> 4bbc 6000 
6042 
[  329.228131] ---[ end trace 8c46856d314c1811 ]---
[  375.755943] hrtimer: interrupt took 31601 ns

== Comment: #4 - SEETEENA THOUFEEK  - 2018-02-05
06:34:09 ==


== Comment: #5 - SEETEENA THOUFEEK  - 2018-02-05 06:36:12 
==
We have similar issue reported on different distro where Anju Provided the 
patch. Patch attached above. 
. 
Will check with her if that patch got accepted upstream

== Comment: #14 - SEETEENA THOUFEEK  - 2018-02-23
01:52:50 ==

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-ppc64le bugnameltc-164198 severity-high 
targetmilestone-inin1804
-- 
[P9,POwer NV][WSP][DD2.1][Ubuntu 1804][Perf fuzzer] : Call trace is seen while 
running perf fuzzer (perf:)
https://bugs.launchpad.net/bugs/1752002
You received this bug notification

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

** Changed in: ubuntu-power-systems
   Status: New => 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/1751834

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1751994] Re: ppc64el: Support firmware disable of RFI flush

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-power-systems
   Importance: Undecided => Medium

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

** Tags added: triage-g

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

Title:
  ppc64el: Support firmware disable of RFI flush

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

Bug description:
  == Comment: #0 - Breno Leitao  - 2018-02-26 13:59:55 ==
  Hi Canonical,

  We still need some changes regarding spectre and meltdown. We need to
  backport the following commit to all supported kernel.

  I undertand that the backport for kernel 4.XX should be trivial. Not
  sure about kernel 3.13 yet.

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=582605a429e20ae68fd0b041b2e840af296edd08
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb0a2d2620ae431c543963c8c7f08f597366fc60

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

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

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

--- Comment From bssrika...@in.ibm.com 2018-02-27 01:52 EDT---
Ubuntu,

we need this patch to be in bionic kernel asap. Without which we are
having hardlock issues with KVM on DD 2.2.

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

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

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1747639] Re: [18.04 FEAT] Automatically detect layer2 setting in the qeth device driver

** Tags added: kernel-da-key severity-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/1747639

Title:
  [18.04 FEAT] Automatically detect layer2 setting in the qeth device
  driver

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

Bug description:
  Follow-on of  
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1541544
  Now we have an enhancement as part of kernel 4.16.

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

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

[Kernel-packages] [Bug 1750813] Re: qeth: fix L3 next-hop im xmit qeth hdr

** Changed in: ubuntu-z-systems
   Status: Triaged => In Progress

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

Title:
  qeth: fix L3 next-hop im xmit qeth hdr

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

Bug description:
  Description:  qeth: fix L3 next-hop im xmit qeth hdr

  Symptom:  wrong destination address in qdio header

  Problem:  The current code accesses rtable->rt_gateway without checking
that rtable is a valid address. The accidental access to a
lowcore area results in a random next-hop address in the
qeth_hdr.
rtable (or more precisely, skb_dst(skb)) can be NULL in rare
cases (for instance together with AF_PACKET sockets).

  Solution: Add the missing NULL-ptr checks.
  Reproduction: AF_PACKET program sending raw data

  
  Upstream Commit:
  ec2c6726322f0d270bab477e4904bf9496f70ee5
  kernel 4.13

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

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

[Kernel-packages] [Bug 1751994] [NEW] ppc64el: Support firmware disable of RFI flush

Public bug reported:

== Comment: #0 - Breno Leitao  - 2018-02-26 13:59:55 ==
Hi Canonical,

We still need some changes regarding spectre and meltdown. We need to
backport the following commit to all supported kernel.

I undertand that the backport for kernel 4.XX should be trivial. Not
sure about kernel 3.13 yet.

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=582605a429e20ae68fd0b041b2e840af296edd08
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb0a2d2620ae431c543963c8c7f08f597366fc60

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-ppc64le bugnameltc-165181 severity-medium 
targetmilestone-inin---

** Tags added: architecture-ppc64le bugnameltc-165181 severity-medium
targetmilestone-inin---

** Changed in: ubuntu
 Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage 
(ubuntu-power-triage)

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

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

Title:
  ppc64el: Support firmware disable of RFI flush

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Breno Leitao  - 2018-02-26 13:59:55 ==
  Hi Canonical,

  We still need some changes regarding spectre and meltdown. We need to
  backport the following commit to all supported kernel.

  I undertand that the backport for kernel 4.XX should be trivial. Not
  sure about kernel 3.13 yet.

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=582605a429e20ae68fd0b041b2e840af296edd08
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb0a2d2620ae431c543963c8c7f08f597366fc60

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

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

[Kernel-packages] [Bug 1751994] [NEW] ppc64el: Support firmware disable of RFI flush

You have been subscribed to a public bug:

== Comment: #0 - Breno Leitao  - 2018-02-26 13:59:55 ==
Hi Canonical,

We still need some changes regarding spectre and meltdown. We need to
backport the following commit to all supported kernel.

I undertand that the backport for kernel 4.XX should be trivial. Not
sure about kernel 3.13 yet.

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=582605a429e20ae68fd0b041b2e840af296edd08
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb0a2d2620ae431c543963c8c7f08f597366fc60

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-ppc64le bugnameltc-165181 severity-medium 
targetmilestone-inin---
-- 
ppc64el: Support firmware disable of RFI flush
https://bugs.launchpad.net/bugs/1751994
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

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

--- Comment From shriy...@in.ibm.com 2018-02-27 00:25 EDT---
Hi ,
Unable to hit the above call trace , hence the issue is resolved.

Verified on kernel :

root@ltc-wcwsp1:~/shriya/kernel# uname -a
Linux ltc-wcwsp1 4.15.0-10-generic #11 SMP Fri Feb 23 01:59:38 EST 2018 ppc64le 
ppc64le ppc64le GNU/Linux

Perf fuzzer :
===
+ ./perf_fuzzer -r 1492143527
Using user-specified random seed of 1492143527

*** perf_fuzzer 0.32-rc0 *** by Vince Weaver

Linux version 4.15.0-10-generic ppc64le
Processor: ppc64le UNKNOWN

Watchdog enabled with timeout 60s
Will auto-exit if signal storm detected
Seeding RNG with supplied seed 1492143527

To reproduce, try:
echo 0 > /proc/sys/kernel/nmi_watchdog
echo 2 > /proc/sys/kernel/perf_event_paranoid
echo 10 > /proc/sys/kernel/perf_event_max_sample_rate
./perf_fuzzer -r 1492143527

Fuzzing the following syscalls: mmap perf_event_open close read write ioctl 
fork prctl poll
Also attempting the following: signal-handler-on-overflow busy-instruction-loop 
accessing-perf-proc-and-sys-files trashing-the-mmap-page

Pid=4506, sleeping 1s

==
Starting fuzzing at 2018-02-26 21:36:45
==
Cannot open /sys/kernel/tracing/kprobe_events
Iteration 1, 98728 syscalls in 5.32 s (18.554 k syscalls/s)
Open attempts: 90726  Successful: 917  Currently open: 54
ENOENT : 446
E2BIG : 7816
EBADF : 8522
EINVAL : 72718
ENOSPC : 81
EOVERFLOW : 2
EOPNOTSUPP : 224
Trinity Type (Normal 345/22780)(Sampling 28/22630)(Global 488/22586)(Random 
56/22730)
Type (Hardware 246/12690)(software 362/11897)(tracepoint 58/11874)(Cache 
55/11258)(cpu 136/11638)(breakpoint 33/11690)(nest_capp0_imc 
1/357)(nest_capp1_imc 1/365)(core_imc 0/460)(nest_mba0_imc 1/378)(nest_mba1_imc 
0/352)(nest_mba2_imc 0/362)(nest_mba3_imc 1/371)(nest_mba4_imc 
1/357)(nest_mba5_imc 0/320)(nest_mba6_imc 1/358)(nest_mba7_imc 
0/439)(nest_mcs01_imc 0/359)(nest_mcs23_imc 2/361)(nest_nvlink0_imc 19/14840)
Close:  863/863 Successful
Read:   824/912 Successful
Write:  0/855 Successful
Ioctl:  371/924 Successful: (ENABLE 91/91)(DISABLE 81/81)(REFRESH 9/78)(RESET 
84/84)(PERIOD 2/75)(SET_OUTPUT 8/80)(SET_FILTER 0/92)(ID 87/87)(SET_BPF 
0/91)(PAUSE_OUTPUT 9/79)(#10 0/0)(#11 0/0)(#12 0/0)(#13 0/0)(#14 0/0)(>14 0/86)
Mmap:   662/1060 Successful: (MMAP 662/1060)(TRASH 144/156)(READ 133/143)(UNMAP 
653/988)(AUX 0/169)(AUX_READ 0/0)
Prctl:  929/929 Successful
Fork:   471/471 Successful
Poll:   895/921 Successful
Access: 0/0 Successful
Overflows: 0  Recursive: 0
SIGIOs due to RT signal queue full: 0
Memset of mmap#18 at (nil) caused segfault!
MAP_SHARED MAP_DENYWRITE MAP_FIXED MAP_NONBLOCK MAP_STACK PROT_READ PROT_WRITE 
size 27661 fd 47
event: cpu=4 pid=-1 group_fd=-1 flags=9
memset([47],0,sizeof(struct perf_event_attr));
pe[47].type=PERF_TYPE_SOFTWARE;
pe[47].size=64;
pe[47].config=PERF_COUNT_SW_PAGE_FAULTS;
pe[47].sample_type=0; /* 0 */
pe[47].read_format=PERF_FORMAT_TOTAL_TIME_RUNNING|PERF_FORMAT_GROUP; /* a */
pe[47].disabled=1;
pe[47].inherit=1;
pe[47].pinned=1;
pe[47].precise_ip=0; /* arbitrary skid */
pe[47].wakeup_events=0;
pe[47].bp_type=HW_BREAKPOINT_EMPTY;

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

Title:
  [P9,Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when
  grouping different pmu events using perf fuzzer . (perf:)

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification ==
  Due to this bug, perf fuzzer resulted in crash and system goes for a reboot
  and results in a call trace shown in the bug.  It is due to grouping of 
  different PMU events, which is fixed by mainline commit 
5aa04b3eb6fca63d2e9827be656dcadc26d54e1

  Commit 5aa04b3eb6fca63d2e9827be656dcadc26d54e11 is in mailine as of
  v4.15-rc5.

  
  == Fix ==
  commit 5aa04b3eb6fca63d2e9827be656dcadc26d54e11
  Author: Ravi Bangoria 
  Date:   Thu Nov 30 14:03:22 2017 +0530

  powerpc/perf: Fix oops when grouping different pmu events

  
  == Regression Potential ==
  Low.  This fix is specific to powerpc.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

  
  ==Original Bug Description==
  == Comment: #0 - Shriya R. Kulkarni  - 2018-01-30 
03:24:47 ==
  Problem Description :
  ==
  Perf fuzzer resulted in crash and system goes for reboot and the call trace 
is shown below . It is due to grouping of different PMU events.

  Machine details :
  ==
  OS : Ubuntu 1804
  uname -r : 4.13.0-25-generic
  system : Witherspoon + DD2.1
  perf -v : perf

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

--- Comment From bssrika...@in.ibm.com 2018-02-27 00:21 EDT---
(In reply to comment #5)
> When you say "Power9 DD 2.2 needs HMI fixup backport of..." in the original
> bug description. Is this patchset required to boot P9 DD2.2?

We need this patch for KVM guest testing on DD 2.2 revision. Good
explanation on why this is required is in commit pointed.

==_
Hypervisor maintenance interrupts (HMIs) are generated by various
causes, signalled by bits in the hypervisor maintenance exception
register (HMER).  In most cases calling OPAL to handle the interrupt
is the correct thing to do, but the "debug trigger" HMIs signalled by
PPC bit 17 (bit 46) of HMER are used to invoke software workarounds
for hardware bugs, and OPAL does not have any code to handle this
cause.  The debug trigger HMI is used in POWER9 DD2.0 and DD2.1 chips
to work around a hardware bug in executing vector load instructions to
cache inhibited memory.  In POWER9 DD2.2 chips, it is generated when
conditions are detected relating to threads being in TM (transactional
memory) suspended mode when the core SMT configuration needs to be
reconfigured.

The kernel currently has code to detect the vector CI load condition,
but only when the HMI occurs in the host, not when it occurs in a
guest.  If a HMI occurs in the guest, it is always passed to OPAL, and
then we always re-sync the timebase, because the HMI cause might have
been a timebase error, for which OPAL would re-sync the timebase, thus
removing the timebase offset which KVM applied for the guest.  Since
we don't know what OPAL did, we don't know whether to subtract the
timebase offset from the timebase, so instead we re-sync the timebase.

This adds code to determine explicitly what the cause of a debug
trigger HMI will be.  This is based on a new device-tree property
under the CPU nodes called ibm,hmi-special-triggers, if it is
present, or otherwise based on the PVR (processor version register).
The handling of debug trigger HMIs is pulled out into a separate
function which can be called from the KVM guest exit code.  If this
function handles and clears the HMI, and no other HMI causes remain,
then we skip calling OPAL and we proceed to subtract the guest
timebase offset from the timebase.

The overall handling for HMIs that occur in the host (i.e. not in a
KVM guest) is largely unchanged, except that we now don't set the flag
for the vector CI load workaround on DD2.2 processors.

This also removes a BUG_ON in the KVM code.  BUG_ON is generally not
useful in KVM guest entry/exit code since it is difficult to handle
the resulting trap gracefully.
==_

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

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

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1749040] Re: KPTI support for arm64 systems

2018-02-26 Thread dann frazier

** Summary changed:

- KPTI-enabled kernel fails to boot on Cavium ThunderX CRB
+ KPTI support for arm64 systems

** Attachment added: "config used to build 4.16-rc3 kernel"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+attachment/5064177/+files/.config

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

Title:
  KPTI support for arm64 systems

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

Bug description:
  While regression testing the current linux-hwe proposed kernel
  (4.13.0-33.36~16.04.1), I found that it fails to boot on a Cavium
  ThunderX CRB. I've rebooted twice since upgrading from the current
  -updates kernel, and it's failed to boot both times, with different
  failure modes.

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

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

[Kernel-packages] [Bug 1749040] Re: KPTI-enabled kernel fails to boot on Cavium ThunderX CRB

2018-02-26 Thread dann frazier

** Attachment added: "4.16-rc3+ guest boot log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+attachment/5064176/+files/guest-boot.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/1749040

Title:
  KPTI support for arm64 systems

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

Bug description:
  While regression testing the current linux-hwe proposed kernel
  (4.13.0-33.36~16.04.1), I found that it fails to boot on a Cavium
  ThunderX CRB. I've rebooted twice since upgrading from the current
  -updates kernel, and it's failed to boot both times, with different
  failure modes.

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

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

[Kernel-packages] [Bug 1749040] Re: KPTI-enabled kernel fails to boot on Cavium ThunderX CRB

2018-02-26 Thread dann frazier

I'm able to reproduce the failure with an upstream kernel (4.16-rc3+ @
6f70eb2b00eb4), running on both the host and guest.

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

Title:
  KPTI support for arm64 systems

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

Bug description:
  While regression testing the current linux-hwe proposed kernel
  (4.13.0-33.36~16.04.1), I found that it fails to boot on a Cavium
  ThunderX CRB. I've rebooted twice since upgrading from the current
  -updates kernel, and it's failed to boot both times, with different
  failure modes.

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

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

[Kernel-packages] [Bug 1664602] Re: Using an NVMe drive causes huge power drain

2018-02-26 Thread Anthony Wong

** Tags added: originate-from-1659177 somerville

** Changed in: hwe-next
   Status: New => 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/1664602

Title:
  Using an NVMe drive causes huge power drain

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

Bug description:
  PCIe NVMe drives are very common in new laptops. The Zesty's kernels 
(including latest 4.10 rc8 from CKT PPA) does not support APST (autonomous 
power state transitions). A patch does exist :
  http://lists.infradead.org/pipermail/linux-nvme/2017-February/008051.html
  https://github.com/damige/linux-nvme

  It seems that we cannot expect this before kernel 4.11.

  Additionally my laptop CPU does never go under PC3 power saving state, 
powertop says. I don't know if it's related.
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ft 1900 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=a04b55bf-b1b6-464c-88ce-44b6adbbbc10
  InstallationDate: Installed on 2016-12-12 (63 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20161211)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 7510
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 nouveaufb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-8-generic 
root=UUID=0d1f213e-73a9-4097-ae64-9cd963cfba23 ro quiet
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-8-generic N/A
   linux-backports-modules-4.10.0-8-generic  N/A
   linux-firmware1.163
  Tags:  zesty
  Uname: Linux 4.10.0-8-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/22/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.5
  dmi.board.name: 0YH43H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.5:bd12/22/2016:svnDellInc.:pnPrecision7510:pvr:rvnDellInc.:rn0YH43H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 7510
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1744754] Re: qemu-efi-aarch64 in >= artful can't boot xenial cloud images

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  qemu-efi-aarch64 in >= artful can't boot xenial cloud images

Status in cloud-images:
  New
Status in edk2 package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in edk2 source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  In Progress

Bug description:
  [Impact]
  After upgrading an Ubuntu/arm64 KVM host past xenial, your xenial-based 
guests will fail to boot.

  [Test Case]
  Boot a xenial cloud image with qemu-efi-aarch64 from artful/bionic.

  [Regression Risk]
  I've tested booting a xenial cloud image in bionic (ACPI mode), and 
regression tested w/ xenial's qemu-efi (DTB mode). I've regression tested on a 
Cavium ThunderX CRB1S, Caviumt ThunderX CRB2S and an APM X-Gene 2 Merlin board.

  Patches 1-5 change only code in the GICv3 driver. The xenial GA kernel
  only supported 2 GICv3 systems - the 1 socket and 2 socket variants of
  the Cavium ThunderX CRB - and I've regression tested on those systems.

  Patch 6 only adds new macro definitions.

  Patch 7 is restricted to devicetree code, except for a change to
  earlycon.c:param_setup_earlycon(). In the case that 'earlycon' is
  passed on the cmdline (vs. earlycon=something), this function used to
  return 0 - but now it will return -ENODEV on non-devicetree systems,
  which is a subtle API change. However, according to kernel-
  parameters.txt (and the code itself), 'earlycon' by itself is only
  valid on devicetree systems. Just to be sure, I booted an x86 system
  up w/ 'earlycon' with and without this series, and observed no
  difference.

  Patch 8 adds the SPCR table parser, but no caller to it yet. It also
  modifies the same earlycon code as Patch 7 - here it avoids earlycon
  init in the case that the devicetree-specific 'earlycon' was passed.
  As mentioned in my analysis Patch 7, this codepath is only supported
  for devicetree systems, and has been regression tested on x86.

  Patch 9 turns on CONFIG_ACPI_SPCR_TABLE - however, this driver will
  only be built for arm64. TBH, I'm not 100% sure how Kconfig knows not
  to build this for other archs - but I checked the logs, and there's no
  spcr.o built on other archs. (Not that that should be a problem - they
  would just grow a bit of unused code).

  Patch 10 only touches arm64-specific code, adding the call to
  parse_spcr(), so risk is limited to arm64.

  Patch 11 adds a new match method to the ARM-specific pl011 console
  driver, so regression risk to other architectures is negligible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1744754/+subscriptions

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

[Kernel-packages] [Bug 1751718] Re: Unable to create Xenial KVM with uvtool on Cavium ThunderX ARM64 system

2018-02-26 Thread Po-Hsu Lin

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

** This bug has been marked a duplicate of bug 1744754
   qemu-efi-aarch64 in >= artful can't boot xenial cloud images

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

Title:
  Unable to create Xenial KVM with uvtool on Cavium ThunderX ARM64
  system

Status in uvtool:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With a Cavium ThunderX system deployed with Bionic, if you try to create a 
Xenial KVM, this tool will failed with:
uvt-kvm: error: timed out waiting for dnsmasq lease for 52:54:00:32:a2:f7

  Steps:
sudo uvt-simplestreams-libvirt sync release=xenial arch=arm64
sudo uvt-kvm create kvm-test release=xenial arch=arm64
sudo uvt-kvm wait bjf-test --insecure

  Note that it works with release=artful.

  
  With a Cavium ThunderX system deployed with Artful, the behaviour is 
different, this tool will failed with the KVM creation no matter if you're 
trying with Xenial or Artful:
uvt-kvm: error: libvirt: unsupported configuration: ACPI requires UEFI on 
this architecture

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: User Name 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 26 03:32 seq
   crw-rw 1 root audio 116, 33 Feb 26 03:32 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   
  Date: Mon Feb 26 06:20:28 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Cavium ThunderX CRB
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 EFI VGA
   1 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=ddcb8b36-6267-4392-a1f9-74d9203b742e ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.171
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 0
  dmi.chassis.vendor: Cavium
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd12/12/2012:svnCavium:pnThunderXCRB:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnCavium:ct0:cvrTobefilledbyO.E.M.:
  dmi.product.family: Default string
  dmi.product.name: ThunderX CRB
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Cavium

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

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

[Kernel-packages] [Bug 1751512] Re: Kernel 4.13.0-32 goes dark after boot with two monitors

2018-02-26 Thread Alan Bland

There were some other problems with the install. Gvim would not work.
It turned into a terminal rather than an editor. I decided to do a
clean install. The third time. The first time it installed with two
montors attached and the network was connected. That is when I first
saw the video go blank at startup.

The second time it installed with a single monitor and without the
network and no third party software. It booted and ran with two
monitors. Then I updated the level 1, 2 and 3 updates. Then the level
4 updates saving the kernel for last. After that the video would blank
with two monitors until I switched back to the 4.10 kernel.

After a third clean install the 4.13.0-36 kernel is booting up with two
monitors and they are staying lit.
Gvim is working like is should. Something in the install went wrong or when I
installed the updates one at a time i did so in the wrong order.

It is up a running I will continue configuring it.

Please close this bug report.

FM.

Please close this bug report.

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

Title:
Kernel 4.13.0-32 goes dark after boot with two monitors

Status in linux package in Ubuntu:
Confirmed

Bug description:
I did a new install today of Mint 18.3 on my laptop. Dell latitude E6410
Installed without connecting to the internet.
After install finished I booted a few times before connecting an external
monitor. It still booted ok.
Then I ran the software update and got a bunch of level 1 and level 2
updates. No problems.
There were four level 3 updates
systemd 229-4ubuntu21.1
linix-firmware 1.157.16
linux-libc-dev 4.4.0-116.140
linuxkernel 4.13.0-36.40-16.041

I installed them one at a time and restarted the laptop after each one.
After the kernel update the laptop would boot and show the square mint icon
for a brief time them the screen goes dark. Once I disconected the external
monitor the laptop rebooted correctly.

I tested the external montior with VGA and HDMI to DVI cable. The
same response. I reverted to the 4.10.0-38 kernel that came with the
installer ISO. Am back up and running.

There is a problem with the new kernel.
---
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: alan 1777 F pulseaudio
CurrentDesktop: MATE
DistroRelease: Linux 18.3
HibernationDevice: RESUME=UUID=d536e87b-7a3c-48dc-9e30-ed32fc32e74a
InstallationDate: Installed on 2018-02-24 (1 days ago)
InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
Lsusb:
Bus 002 Device 004: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications
Processor
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Latitude E6410
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic
root=UUID=b2b6da50-3200-491a-95d1-eeab4794941c ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
RelatedPackageVersions:
linux-restricted-modules-4.13.0-36-generic N/A
linux-backports-modules-4.13.0-36-generic N/A
linux-firmware 1.157.16
Tags: sylvia
Uname: Linux 4.13.0-36-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/30/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0667CC
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA11:bd11/30/2011:svnDellInc.:pnLatitudeE6410:pvr0001:rvnDellInc.:rn0667CC:rvrA01:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6410
dmi.product.version: 0001
dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1748871] Re: GDM horizontal scanline corruption with an ultra wide monitor

Yes when the problem was first reported we had kernel 4.13, but now it
is 4.15 which might have fixed it.

Since you are the original reporter we can declare this bug fixed.
Anyone else who still has issues after updating to kernel 4.15 should
file a new bug.

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

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

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

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

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

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

Title:
  GDM horizontal scanline corruption with an ultra wide monitor

Status in gdm3 package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Invalid

Bug description:
  Using a ultra wide monitor with ubuntu 18.04 daily it's a bad ideea.
  Because the loging screen it's out of focus and has orizontal radio
  screen lines

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.26.2.1-2ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 12 13:28:04 2018
  InstallationDate: Installed on 2018-02-12 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180212)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1749975] Re: Flickering screen with ultra-wide monitor in Wayland mode

Krister,

Other people are saying that kernel 4.15 has fixed the problem. Can you
please try testing it by booting this?

  http://cdimages.ubuntu.com/daily-live/current/


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

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

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

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

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

Title:
  Flickering screen with ultra-wide monitor in Wayland mode

Status in gdm3 package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  1. leave computer until gnome-shell blanks the screen (monitor goes to sleep)
  2. clear GDM screen by swiping up.

  There is a video flicker now when I interact with computer.
  Usually small, but can cover many different UI elements.

  This does not happen if I use the X backend instead of wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 16 16:07:12 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['workspace-g...@mathematical.coffee.gmail.com', 
'alt-tab-worksp...@kwalo.net', 'system-moni...@paradoxxx.zero.gmail.com', 
'user-th...@gnome-shell-extensions.gcampax.github.com', 
'ubuntu-d...@ubuntu.com', 'ubuntu-appindicat...@ubuntu.com']"
   b'org.gnome.shell' b'enable-hot-corners' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['googleinbox.desktop', 
'googlecalendar.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 11'"
  InstallationDate: Installed on 2018-01-05 (42 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2018-01-05 (42 days ago)

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

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

[Kernel-packages] [Bug 1750379] Re: Distortion Realtek ALC887

If you experience the same sounding glitching in Win 10 then yes this
sounds like a hardware problem. But you also said that "Amplification
worked well for years before recent PulseAudio update", so I wonder if
you can find any older Ubuntu release where it works still? Try live
booting some of these:

  http://cdimages.ubuntu.com/releases/

Otherwise, try replacing your 3.5mm audio splitter and related cables. I
was stunned in the past to discover that cheap/broken audio cables can
severely distort sound, so it's probably worth trying other cables and
connectors.

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

Title:
  Distortion Realtek ALC887

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Sounds can distort even when not amplified. Amplification worked well
  for years before recent PulseAudio update. The audio is Realtek ALC887
  under an IntelG41 Chipset with GA-G41M-Combo main board;

  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  I am seeking to engage upstream for April LTS release. Windows have
  abandoned this esoteric hardware! Please Ubuntu! Keep a C2D user
  going!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu6
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fleamour   1049 F pulseaudio
   /dev/snd/controlC2:  fleamour   1049 F pulseaudio
   /dev/snd/controlC0:  fleamour   1049 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 19 13:54:33 2018
  InstallationDate: Installed on 2018-02-19 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FB
  dmi.board.name: G41M-Combo
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFB:bd10/25/2012:svnGigabyteTechnologyCo.,Ltd.:pnG41M-Combo:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-Combo:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: G41M-Combo
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1700256] Re: package bluez 5.37-0ubuntu5 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package bluez 5.37-0ubuntu5 failed to install/upgrade [bluez depends
  on udev (> = 170-1); but: Package udev is not configured yet.]

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  
  This bug is already displayed when I start up. Updates are not possible, 
there are further error messages ...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  Uname: Linux 4.4.0-81-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Tue Jun 20 21:06:57 2017
  ErrorMessage: Abhängigkeitsprobleme - verbleibt unkonfiguriert
  InstallationDate: Installed on 2016-06-20 (369 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  InterestingModules: bluetooth
  MachineType: LENOVO 2491.A3G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-81-generic 
root=UUID=5c7ae55f-369b-45ae-bb99-457d973001cb ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: bluez
  Title: package bluez 5.37-0ubuntu5 failed to install/upgrade: 
Abhängigkeitsprobleme - verbleibt unkonfiguriert
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/10/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9HKT58AUS
  dmi.board.vendor: LENOVO
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvr9HKT58AUS:bd06/10/2014:svnLENOVO:pn2491.A3G:pvrThinkCentreM91:rvnLENOVO:rn:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: 2491.A3G
  dmi.product.version: ThinkCentre M91
  dmi.sys.vendor: LENOVO
  hciconfig:
   
  rfkill:
   
  syslog: Jun 24 16:43:19 ted-M91 NetworkManager[1108]:   
[1498315399.6618] Loaded device plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)

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

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

[Kernel-packages] [Bug 1700256] Re: package bluez 5.37-0ubuntu5 failed to install/upgrade [bluez depends on udev (> = 170-1); but: Package udev is not configured yet.]

** Summary changed:

- package bluez 5.37-0ubuntu5 failed to install/upgrade: Abhängigkeitsprobleme 
- verbleibt unkonfiguriert
+ package bluez 5.37-0ubuntu5 failed to install/upgrade [bluez depends on udev 
(> = 170-1); but: Package udev is not configured yet.]

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

Title:
  package bluez 5.37-0ubuntu5 failed to install/upgrade [bluez depends
  on udev (> = 170-1); but: Package udev is not configured yet.]

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  
  This bug is already displayed when I start up. Updates are not possible, 
there are further error messages ...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  Uname: Linux 4.4.0-81-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Tue Jun 20 21:06:57 2017
  ErrorMessage: Abhängigkeitsprobleme - verbleibt unkonfiguriert
  InstallationDate: Installed on 2016-06-20 (369 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  InterestingModules: bluetooth
  MachineType: LENOVO 2491.A3G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-81-generic 
root=UUID=5c7ae55f-369b-45ae-bb99-457d973001cb ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: bluez
  Title: package bluez 5.37-0ubuntu5 failed to install/upgrade: 
Abhängigkeitsprobleme - verbleibt unkonfiguriert
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/10/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9HKT58AUS
  dmi.board.vendor: LENOVO
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvr9HKT58AUS:bd06/10/2014:svnLENOVO:pn2491.A3G:pvrThinkCentreM91:rvnLENOVO:rn:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: 2491.A3G
  dmi.product.version: ThinkCentre M91
  dmi.sys.vendor: LENOVO
  hciconfig:
   
  rfkill:
   
  syslog: Jun 24 16:43:19 ted-M91 NetworkManager[1108]:   
[1498315399.6618] Loaded device plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)

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

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

[Kernel-packages] [Bug 1730562] Re: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным

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

** This bug is no longer a duplicate of bug 1718974
   package bluez 5.37-0ubuntu5.1 failed to install/upgrade: проблемы 
зависимостей — оставляем не настроенным
** This bug has been marked a duplicate of bug 1700256
   package bluez 5.37-0ubuntu5 failed to install/upgrade: Abhängigkeitsprobleme 
- verbleibt unkonfiguriert

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

Title:
  package bluez 5.37-0ubuntu5.1 failed to install/upgrade: проблемы
  зависимостей — оставляем не настроенным

Status in bluez package in Ubuntu:
  New

Bug description:
  package bluez 5.37-0ubuntu5.1 failed to install/upgrade: проблемы
  зависимостей — оставляем не настроенным

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5.1
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sat Nov  4 06:15:49 2017
  ErrorMessage: проблемы зависимостей — оставляем не настроенным
  InstallationDate: Installed on 2017-10-31 (6 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  InterestingModules: bluetooth
  MachineType: Gigabyte Technology Co., Ltd. H61M-S2-B3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=2b78b13f-3349-4562-b722-70033e013f0b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: bluez
  Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: проблемы 
зависимостей — оставляем не настроенным
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/27/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F1
  dmi.board.name: H61M-S2-B3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd05/27/2011:svnGigabyteTechnologyCo.,Ltd.:pnH61M-S2-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-S2-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: H61M-S2-B3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  hciconfig:
   
  rfkill:
   
  syslog: ноя 03 11:04:20 viktor NetworkManager[768]:   [1509696260.1830] 
Loaded device plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)

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

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

[Kernel-packages] [Bug 1718974] Re: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1700256, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1700256
   package bluez 5.37-0ubuntu5 failed to install/upgrade: Abhängigkeitsprobleme 
- verbleibt unkonfiguriert

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

Title:
  package bluez 5.37-0ubuntu5.1 failed to install/upgrade: проблемы
  зависимостей — оставляем не настроенным

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  When updating

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5.1
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Sep 22 22:25:17 2017
  ErrorMessage: проблемы зависимостей — оставляем не настроенным
  InstallationDate: Installed on 2017-07-29 (55 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  InterestingModules: bluetooth
  MachineType: Gigabyte Technology Co., Ltd. P35-S3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=UUID=68eb309e-4d7d-4735-b7ec-c972ec4839d6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: bluez
  Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: проблемы 
зависимостей — оставляем не настроенным
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F8
  dmi.board.name: P35-S3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd06/19/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-S3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-S3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P35-S3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  hciconfig:
   
  rfkill:
   
  syslog:
   Сен 22 22:23:03 leonid-P35-S3 NetworkManager[776]:   [1506108183.9686] 
Loaded device plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
   Сен 22 22:23:57 leonid-P35-S3 ureadahead[249]: 
ureadahead:unity-control-center_bluetooth.png: Относительный путь пропущен

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

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

[Kernel-packages] [Bug 1751893] Re: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: problèmes de dépendances - laissé non configuré

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1718974, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1718974
   package bluez 5.37-0ubuntu5.1 failed to install/upgrade: проблемы 
зависимостей — оставляем не настроенным

** This bug is no longer a duplicate of bug 1718974
   package bluez 5.37-0ubuntu5.1 failed to install/upgrade: проблемы 
зависимостей — оставляем не настроенным
** This bug has been marked a duplicate of bug 1700256
   package bluez 5.37-0ubuntu5 failed to install/upgrade: Abhängigkeitsprobleme 
- verbleibt unkonfiguriert

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

Title:
  package bluez 5.37-0ubuntu5.1 failed to install/upgrade: problèmes de
  dépendances - laissé non configuré

Status in bluez package in Ubuntu:
  New

Bug description:
  Dear Community manager,

  I am not a system specialist and I cannot say more about this problem

  Thanks for your help

  Claude

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5.1
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Jan  5 14:52:19 2018
  ErrorMessage: problèmes de dépendances - laissé non configuré
  InstallationDate: Installed on 2016-07-30 (576 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  InterestingModules: bluetooth
  MachineType: Dell Inc. Precision M6500
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic 
root=UUID=80b71b49-579d-4c19-b1ed-b0f1cee9626e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: bluez
  Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: problèmes de 
dépendances - laissé non configuré
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/04/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0R1203
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd06/04/2013:svnDellInc.:pnPrecisionM6500:pvr:rvnDellInc.:rn0R1203:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Precision M6500
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   
  syslog: févr. 26 21:16:01 groix NetworkManager[888]:   
[1519676161.1202] Loaded device plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)

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

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

[Kernel-packages] [Bug 1717224] Re: virsh start of virtual guest domain fails with internal error due to low default aio-max-nr sysctl value

2018-02-26 Thread Joseph Salisbury

Commit 2a8a98673c13 has been in Xenial and Artful for some time now.
Can you confirm this bug is now resolved with the latest updates.

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

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

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

Title:
  virsh start of virtual guest domain fails with internal error due to
  low default aio-max-nr sysctl value

Status in Ubuntu on IBM z Systems:
  In Progress
Status in kvm package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Fix Released
Status in procps package in Ubuntu:
  New
Status in linux source package in Xenial:
  Fix Released
Status in procps source package in Xenial:
  New
Status in linux source package in Artful:
  Fix Released
Status in procps source package in Artful:
  New

Bug description:
  Starting virtual guests via on Ubuntu 16.04.2 LTS installed with its
  KVM hypervisor on an IBM Z14 system LPAR fails on the 18th guest with
  the following error:

  root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70038
  error: Failed to start domain zs93kag70038
  error: internal error: process exited while connecting to monitor: 
2017-07-26T01:48:26.352534Z qemu-kvm: -drive 
file=/guestimages/data1/zs93kag70038.qcow2,format=qcow2,if=none,id=drive-virtio-disk0,cache=none,aio=native:
 Could not open backing file: Could not set AIO state: Inappropriate ioctl for 
device

  The previous 17 guests started fine:

  root@zm93k8# virsh start zs93kag70020
  Domain zs93kag70020 started

  root@zm93k8# virsh start zs93kag70021
  Domain zs93kag70021 started

  .
  .

  root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70036
  Domain zs93kag70036 started

  
  We ended up fixing the issue by adding the following line to /etc/sysctl.conf 
: 

  fs.aio-max-nr = 4194304

  ... then, reload the sysctl config file:

  root@zm93k8:/etc# sysctl -p /etc/sysctl.conf
  fs.aio-max-nr = 4194304

  
  Now, we're able to start more guests...

  root@zm93k8:/etc# virsh start zs93kag70036
  Domain zs93kag70036 started

  
  The default value was originally set to 65535: 

  root@zm93k8:/rawimages/ubu1604qcow2# cat /proc/sys/fs/aio-max-nr
  65536

  
  Note, we chose the 4194304 value, because this is what our KVM on System Z 
hypervisor ships as its default value.  Eg.  on our zKVM system: 

  [root@zs93ka ~]# cat /proc/sys/fs/aio-max-nr
  4194304

  ubuntu@zm93k8:/etc$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  Codename:   xenial
  ubuntu@zm93k8:/etc$

  ubuntu@zm93k8:/etc$ dpkg -s qemu-kvm |grep Version
  Version: 1:2.5+dfsg-5ubuntu10.8

  Is something already documented for Ubuntu KVM users warning them about the 
low default value, and some guidance as to
  how to select an appropriate value?   Also, would you consider increasing the 
default aio-max-nr value to something much
  higher, to accommodate significantly more virtual guests?  

  Thanks!

  ---uname output---
  ubuntu@zm93k8:/etc$ uname -a Linux zm93k8 4.4.0-62-generic #83-Ubuntu SMP Wed 
Jan 18 14:12:54 UTC 2017 s390x s390x s390x GNU/Linux
   
  Machine Type = z14 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   See Problem Description.

  The problem was happening a week ago, so this may not reflect that
  activity.

  This file was collected on Aug 7, one week after we were hitting the
  problem.  If I need to reproduce the problem and get fresh data,
  please let me know.

  /var/log/messages doesn't exist on this system, so I provided syslog
  output instead.

  All data have been collected too late after the problem was observed
  over a week ago.  If you need me to reproduce the problem and get new
  data, please let me know.  That's not a problem.

  Also, we would have to make special arrangements for login access to
  these systems.  I'm happy to run traces and data collection for you as
  needed.  If that's not sufficient, then we'll explore log in access
  for you.

  Thanks...   - Scott G.

  
  I was able to successfully recreate the problem and captured / attached new 
debug docs. 

  Recreate procedure:

  #  Started out with no virtual guests running.

  ubuntu@zm93k8:/home/scottg$ virsh list
   IdName   State
  

  
  # Set fs.aio-max-nr back to original Ubuntu "out of the box" value in 
/etc/sysctl.conf

  ubuntu@zm93k8:~$ tail -1 /etc/sysctl.conf
  fs.aio-max-nr = 65536

  
  ## sysctl -a shows: 

  fs.aio-max-nr = 4194304

  
  ##  Reload sysctl.

  ubuntu@zm93k8:~$ sudo sysctl -p /etc/sysctl.conf
  fs.aio-max-nr = 65536
  ubuntu@zm93k8:~$

  ubuntu@zm93k8:~$ sudo sysctl -a |grep fs.aio-max-nr
  fs.aio-max-nr = 65536

  ubuntu@zm93k8:~$  cat

[Kernel-packages] [Bug 1717224] Re: virsh start of virtual guest domain fails with internal error due to low default aio-max-nr sysctl value

2018-02-26 Thread Joseph Salisbury

** No longer affects: linux (Ubuntu Zesty)

** No longer affects: procps (Ubuntu Zesty)

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

Title:
  virsh start of virtual guest domain fails with internal error due to
  low default aio-max-nr sysctl value

Status in Ubuntu on IBM z Systems:
  In Progress
Status in kvm package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Fix Released
Status in procps package in Ubuntu:
  New
Status in linux source package in Xenial:
  In Progress
Status in procps source package in Xenial:
  New
Status in linux source package in Artful:
  In Progress
Status in procps source package in Artful:
  New

Bug description:
  Starting virtual guests via on Ubuntu 16.04.2 LTS installed with its
  KVM hypervisor on an IBM Z14 system LPAR fails on the 18th guest with
  the following error:

  root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70038
  error: Failed to start domain zs93kag70038
  error: internal error: process exited while connecting to monitor: 
2017-07-26T01:48:26.352534Z qemu-kvm: -drive 
file=/guestimages/data1/zs93kag70038.qcow2,format=qcow2,if=none,id=drive-virtio-disk0,cache=none,aio=native:
 Could not open backing file: Could not set AIO state: Inappropriate ioctl for 
device

  The previous 17 guests started fine:

  root@zm93k8# virsh start zs93kag70020
  Domain zs93kag70020 started

  root@zm93k8# virsh start zs93kag70021
  Domain zs93kag70021 started

  .
  .

  root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70036
  Domain zs93kag70036 started

  
  We ended up fixing the issue by adding the following line to /etc/sysctl.conf 
: 

  fs.aio-max-nr = 4194304

  ... then, reload the sysctl config file:

  root@zm93k8:/etc# sysctl -p /etc/sysctl.conf
  fs.aio-max-nr = 4194304

  
  Now, we're able to start more guests...

  root@zm93k8:/etc# virsh start zs93kag70036
  Domain zs93kag70036 started

  
  The default value was originally set to 65535: 

  root@zm93k8:/rawimages/ubu1604qcow2# cat /proc/sys/fs/aio-max-nr
  65536

  
  Note, we chose the 4194304 value, because this is what our KVM on System Z 
hypervisor ships as its default value.  Eg.  on our zKVM system: 

  [root@zs93ka ~]# cat /proc/sys/fs/aio-max-nr
  4194304

  ubuntu@zm93k8:/etc$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  Codename:   xenial
  ubuntu@zm93k8:/etc$

  ubuntu@zm93k8:/etc$ dpkg -s qemu-kvm |grep Version
  Version: 1:2.5+dfsg-5ubuntu10.8

  Is something already documented for Ubuntu KVM users warning them about the 
low default value, and some guidance as to
  how to select an appropriate value?   Also, would you consider increasing the 
default aio-max-nr value to something much
  higher, to accommodate significantly more virtual guests?  

  Thanks!

  ---uname output---
  ubuntu@zm93k8:/etc$ uname -a Linux zm93k8 4.4.0-62-generic #83-Ubuntu SMP Wed 
Jan 18 14:12:54 UTC 2017 s390x s390x s390x GNU/Linux
   
  Machine Type = z14 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   See Problem Description.

  The problem was happening a week ago, so this may not reflect that
  activity.

  This file was collected on Aug 7, one week after we were hitting the
  problem.  If I need to reproduce the problem and get fresh data,
  please let me know.

  /var/log/messages doesn't exist on this system, so I provided syslog
  output instead.

  All data have been collected too late after the problem was observed
  over a week ago.  If you need me to reproduce the problem and get new
  data, please let me know.  That's not a problem.

  Also, we would have to make special arrangements for login access to
  these systems.  I'm happy to run traces and data collection for you as
  needed.  If that's not sufficient, then we'll explore log in access
  for you.

  Thanks...   - Scott G.

  
  I was able to successfully recreate the problem and captured / attached new 
debug docs. 

  Recreate procedure:

  #  Started out with no virtual guests running.

  ubuntu@zm93k8:/home/scottg$ virsh list
   IdName   State
  

  
  # Set fs.aio-max-nr back to original Ubuntu "out of the box" value in 
/etc/sysctl.conf

  ubuntu@zm93k8:~$ tail -1 /etc/sysctl.conf
  fs.aio-max-nr = 65536

  
  ## sysctl -a shows: 

  fs.aio-max-nr = 4194304

  
  ##  Reload sysctl.

  ubuntu@zm93k8:~$ sudo sysctl -p /etc/sysctl.conf
  fs.aio-max-nr = 65536
  ubuntu@zm93k8:~$

  ubuntu@zm93k8:~$ sudo sysctl -a |grep fs.aio-max-nr
  fs.aio-max-nr = 65536

  ubuntu@zm93k8:~$  cat /proc/sys/fs/aio-max-nr
  65536


  # Attempt to start more than 17 qcow2 virtual guests on the Ubuntu
  host.  Fails on the 18th XML.

  Script used to start guests..

  
  ubuntu@zm93k8:/home/scottg$

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

2018-02-26 Thread henczati

As mentioned in #47, same problem on trusty + xenial HWE stack
(14.04.5).

Additionally, had a gcc version mismatch, don't know where that came
from.

Meta package gcc was 4:4.8.2-1ubuntu6, but /usr/bin/gcc (and corresponding 
package gcc-4.8) was 4.8.5-1ubuntu1~14.04 .
I also had installed just gcc-4.9-base (without even gcc-4.9) due to some 
dependencies.

Went back to -112 kernel.

Tried #57 (@cjjefcoat) steps, but did not trigger a driver rebuild.

I had a lot of PPA-s and manual file-wrapped deb lines in 
/etc/apt/sources.list.d/.
I had ubuntu-toolchain-r/ppa, not ubuntu-toolchain-r/test, but IIRC purging 
failed somehow (cant remember, couple of days ago), probably due to same 
mismatch.

So just deleted all entries from /etc/apt/sources.list.d/, manually
cleaned /etc/apt/sources.list, updated repo cache.

Then tried to force-install (downgrade) gcc-4.8 and gcc-4.8-base to 
4.8.4-2ubuntu1~14.04.4, to make it in sync with the gcc package again.
After force-picking all the needed dependencies, I ended up with
sudo apt-get install gcc-4.8 gcc-4.8-base:i386=4.8.4-2ubuntu1~14.04.4 
gcc-4.8-base:amd64=4.8.4-2ubuntu1~14.04.4 g++-4.8=4.8.4-2ubuntu1~14.04.4 
libstdc++-4.8-dev=4.8.4-2ubuntu1~14.04.4 libgcc-4.8-dev=4.8.4-2ubuntu1~14.04.4 
cpp-4.8=4.8.4-2ubuntu1~14.04.4 libgl1-mesa-dri 
libgfortran3=4.8.4-2ubuntu1~14.04.4 libstdc++6=4.8.4-2ubuntu1~14.04.4 
libquadmath0=4.8.4-2ubuntu1~14.04.4 libgomp1=4.8.4-2ubuntu1~14.04.4 
libitm1=4.8.4-2ubuntu1~14.04.4 libatomic1=4.8.4-2ubuntu1~14.04.4 
libasan0=4.8.4-2ubuntu1~14.04.4 libtsan0=4.8.4-2ubuntu1~14.04.4

Somewhere in the process (do not remember when) the nvidia driver, dkms, the 
HWE stack (kernel + xorg) and some other stuff got uninstalled (due to missing 
dependencies).
Probably I could have avoided that and was just too strict on removing 
potentially screwed up stuff.
I think I totally removed gcc-4.8 or even all of gcc before reinstalling with 
the (assumed) correct version.

So after "aligning" gcc, I installed back the xenial kernel (a'la ubuntu wiki 
HWE page, for multiarch):
sudo apt-get install --install-recommends linux-generic-lts-xenial 
xserver-xorg-core-lts-xenial xserver-xorg-lts-xenial 
xserver-xorg-video-all-lts-xenial xserver-xorg-input-all-lts-xenial 
libwayland-egl1-mesa-lts-xenial libgl1-mesa-glx-lts-xenial 
libgl1-mesa-glx-lts-xenial:i386 libglapi-mesa-lts-xenial:i386

There the amd64 and i386 versions of libgl1-mesa-dri-lts-xenial had a 
/etc/drirc conflict.
Apt was useless, just returned a dpkg fail (with or without -f).
Overwriting /etc/drirc with /etc/drirc.dpkg-new was not enough, had to remove 
/etc/drirc alltogether.
THEN on `sudo apt-get install -f` apt asked me to resolve /etc/drirc conflict 
using apt-s command line query.
One said Unigine Heaven 3.0 this and that setting, the other said "Unigine 
Heaven 3.0 and older contain too many bugs and can't be supported [...]".
Went with the second, seemingly newer one.

Then came the nvidia driver (with forcing the dependencies previously removed 
by apt):
sudo apt-get -f install nvidia-340 dkms acpid lib32gcc1 libc6-i386 nvidia-prime 
nvidia-opencl-icd-340

This compiled the driver and
modinfo nvidia-340 -k 4.4.0-116-generic | grep vermagic
said retpoline.

Reboot, works.

Just like that. :)

I guess the system is ripe for reinstall. :)

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

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04)

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

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

  Rebooted into 4.4.0-112 kernel and all was well.

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

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

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename:

[Kernel-packages] [Bug 1509839] Re: segfault on start of live session in kactivitymanager / libqt5sql

2018-02-26 Thread Christopher M. Penalver

private_lock, your release has been EOL since July 28, 2016 as per
https://wiki.ubuntu.com/Releases . Could you please advise if this is
reproducible in a supported release?

** Tags removed: hard kactivitymanager libqt5sql lockup segfault
** Tags added: latest-bios-520

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

Title:
  segfault on start of live session in kactivitymanager / libqt5sql

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've installed 15.10 Wily Werewolf to my USB stick via usb-creator and 
restart the laptop
  on boot, I'm asked for the language and if I want to install or try a live 
session
  I select try life session, the dialog disappears and the machine is frozen

  Next try:
  boot to selection dialog
  switch to console crtl+alt+F1 (takes a moment)
  issue alt+syreq+1 and alt+sysreq+t ... both answer "operation is disabled"
  switch back to X ctrl+alt+F7 & click try live session
  immediately switch back to console ctrl+alt+F1
  watchdog detects hard lockup a few seconds later
  see attached screenshot

  reproduced also in beta1 of wily werewolf ... a month ago I imagine
  the beta was still starting, as for bug #1492840. But I've reformated
  the stick meanwhile and cannot really guarantee, that I didn't confuse
  the multiple ISO's I tried in short time.

  version information:
  kernel 4.2.0-16-generic #19-Ubuntu (4.1.0-3-generic #3-Ubuntu)
  libqt5sql.so 5.4.2 (both)
  currently running Kubuntu 15.04 on the same hardware
  --- 
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kubuntu3331 F pulseaudio
   /dev/snd/controlC0:  kubuntu3331 F pulseaudio
  CasperVersion: 1.365
  DistroRelease: Ubuntu 15.10
  LiveMediaBuild: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Micro-Star International Co., Ltd. GE70 2OC\2OD\2OE
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.149
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/06/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1757IMS.520
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1757
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.B
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1757IMS.520:bd11/06/2014:svnMicro-StarInternationalCo.,Ltd.:pnGE702OC\2OD\2OE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1757:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.name: GE70 2OC\2OD\2OE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

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

2018-02-26 Thread George Hunter

** Description changed:

  It is ON and VISIBLE in the control panel.  My iPhone can see two other
  devices but it can't see the computer, and the computer  can't see
  anything, even if left searching for tens of minutes.
  
  The previous answers listed below suggest the following diagnostics
  
  Bluetooth not working after update
  How can I make my bluetooth works on Ubuntu 16.04?
  Ubuntu 16.04 bluetooth not working (Dell XPS13)
  Bluetooth (Atheros AR3012) not working on Ubuntu 16.04
  Bluetooth not working on Ubuntu 16.04 LTS
  Bluetooth cannot find any devices
  Stuck on a bluetooth problem
  
  The service seems to be running
  
  /home >sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
-Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
-Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
-  Docs: man:bluetoothd(8)
-  Main PID: 790 (bluetoothd)
-Status: "Running"
-CGroup: /system.slice/bluetooth.service
-└─790 /usr/lib/bluetooth/bluetoothd
+    Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
+    Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
+  Docs: man:bluetoothd(8)
+  Main PID: 790 (bluetoothd)
+    Status: "Running"
+    CGroup: /system.slice/bluetooth.service
+    └─790 /usr/lib/bluetooth/bluetoothd
  
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
- Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
+ Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
- Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
+ Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  
  and not blocked
  
  /home >rfkill list
  0: hci0: Bluetooth
-   Soft blocked: no
-   Hard blocked: no
+  Soft blocked: no
+  Hard blocked: no
  1: phy0: Wireless LAN
-   Soft blocked: no
-   Hard blocked: no
+  Soft blocked: no
+  Hard blocked: no
  
  I have edited /etc/bluetooth/main.conf to include
  
  AutoEnable=true
  
  but I noted that the entire file was commented out.
  
  The kernel seems reasonably up to date
  
-  >uname -a
+  >uname -a
  Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 
22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  
  I wonder if I need a device driver, but I have no idea how to find out.
  The following diagnostics may help some of you knowledgeable people find
  out.
  
-  >hcitool dev
+  >hcitool dev
  Devices:
-   hci024:0A:64:F5:EE:86
+  hci0 24:0A:64:F5:EE:86
  
  and the output of dmsg is
  
  >dmesg | grep Blue
- [2.030855] usb 1-1.4: Product: Bluetooth Radio 
+ [2.030855] usb 1-1.4: Product: Bluetooth Radio
  [   13.806355] Bluetooth: Core ver 2.22
  [   13.806369] Bluetooth: HCI device and connection manager initialized
  [   13.806372] Bluetooth: HCI socket layer initialized
  [   13.806373] Bluetooth: L2CAP socket layer initialized
  [   13.806377] Bluetooth: SCO socket layer initialized
  [   13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a 
lmp_ver=06 lmp_subver=8821
  [   13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
  [   13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin
  [   13.877382] Bluetooth: hci0: rom_version status=0 version=1
  [   13.877387] Bluetooth: cfg_sz 0, total size 17428
  [   16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   16.550281] Bluetooth: BNEP filters: protocol multicast
  [   16.550284] Bluetooth: BNEP socket layer initialized
  [   27.868345] Bluetooth: RFCOMM TTY layer initialized
  [   27.868350] Bluetooth: RFCOMM socket layer initialized
  [   27.868354] Bluetooth: RFCOMM ver 1.11
  
  and of lsusb is
  
  >lsusb
  Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
- Bus 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd 
+ Bus 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0

[Kernel-packages] [Bug 1747639] Re: [18.04 FEAT] Automatically detect layer2 setting in the qeth device driver