date:20170823

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1712724

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

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

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

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

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

Title:
  s390 zKVM complains about "illegal operation" to s390/mm/pgalloc.c

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [  543.516708] kernel BUG at 
/build/linux-a7axPg/linux-4.12.0/arch/s390/mm/pgalloc.c:84!
  [  543.516783] illegal operation: 0001 ilc:1 [#1] SMP 
  [  543.516785] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat xt_tcpudp bridge stp llc iptable_filter 
openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack binfmt_misc zfs(PO) zunicode(PO) 
zavl(PO) zcommon(PO) znvpair(PO) spl(O) vfio_ccw vfio_mdev mdev 
vfio_iommu_type1 vfio ib_iser rdma_cm iw_cm ib_cm ib_core nfsd iscsi_tcp 
auth_rpcgss nfs_acl lockd grace libiscsi_tcp libiscsi sunrpc 
scsi_transport_iscsi ip_tables x_tables btrfs zlib_deflate raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 linear ghash_s390 prng aes_s390 des_s390 des_generic 
sha512_s390 sha256_s390 virtio_net sha1_s390 sha_common virtio_blk virtio_scsi
  [  543.516828] CPU: 0 PID: 10024 Comm: task-size-overr Tainted: P   O 
   4.12.0-12-generic #13-Ubuntu
  [  543.516829] Hardware name: IBM 2964 N63 400 (KVM/Linux)
  [  543.516830] task: 0cdb9e00 task.stack: 099e8000
  [  543.516831] Krnl PSW : 0704d0018000 001274ec 
(crst_table_upgrade+0x124/0x130)
  [  543.516841]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 PM:0 
RI:0 EA:3
  [  543.516842] Krnl GPRS: 0001 0400 243d7800 
0020
  [  543.516843]1000  0032 

  [  543.516844]8000 0020  
1000
  [  543.516845]0020 243d7800 001239f6 
099ebbe0
  [  543.516853] Krnl Code: 001274de: c0e5002446c1  brasl   
%r14,5b0260
  [  543.516853]001274e4: a7f4ffb8  brc 
15,127454
  [  543.516853]   #001274e8: a7f40001  brc 
15,1274ea
  [  543.516853]   >001274ec: a728fff4  lhi %r2,-12
  [  543.516853]001274f0: a7f4ffee  brc 
15,1274cc
  [  543.516853]001274f4: 0707  bcr 0,%r7
  [  543.516853]001274f6: 0707  bcr 0,%r7
  [  543.516853]001274f8: c004  brcl0,1274f8
  [  543.516862] Call Trace:
  [  543.516864] ([<085d8578>] 0x85d8578)
  [  543.516868]  [<002f529a>] get_unmapped_area+0x72/0x120 
  [  543.516870]  [<002f931a>] do_mmap+0xfa/0x3e0 
  [  543.516873]  [<002d6292>] vm_mmap_pgoff+0xca/0x120 
  [  543.516874]  [<002f6962>] SyS_mmap_pgoff+0x10a/0x2a0 
  [  543.516875]  [<002f6b72>] SyS_old_mmap+0x7a/0xa8 
  [  543.516880]  [<00864c1c>] system_call+0xc4/0x27c 
  [  543.516881] Last Breaking-Event-Address:
  [  543.516882]  [<001274e8>] crst_table_upgrade+0x120/0x130
  [  543.516883]  
  [  543.516883] ---[ end trace 036f94bf79a83905 ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.12.0-12-generic 4.12.0-12.13
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic s390x
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Thu Aug 24 05:01:08 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  ProcFB: Error:

[Kernel-packages] [Bug 1712724] [NEW] s390 zKVM complains about "illegal operation" to s390/mm/pgalloc.c

2017-08-23 Thread Po-Hsu Lin

Public bug reported:

[  543.516708] kernel BUG at 
/build/linux-a7axPg/linux-4.12.0/arch/s390/mm/pgalloc.c:84!
[  543.516783] illegal operation: 0001 ilc:1 [#1] SMP 
[  543.516785] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat xt_tcpudp bridge stp llc iptable_filter 
openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack binfmt_misc zfs(PO) zunicode(PO) 
zavl(PO) zcommon(PO) znvpair(PO) spl(O) vfio_ccw vfio_mdev mdev 
vfio_iommu_type1 vfio ib_iser rdma_cm iw_cm ib_cm ib_core nfsd iscsi_tcp 
auth_rpcgss nfs_acl lockd grace libiscsi_tcp libiscsi sunrpc 
scsi_transport_iscsi ip_tables x_tables btrfs zlib_deflate raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 linear ghash_s390 prng aes_s390 des_s390 des_generic 
sha512_s390 sha256_s390 virtio_net sha1_s390 sha_common virtio_blk virtio_scsi
[  543.516828] CPU: 0 PID: 10024 Comm: task-size-overr Tainted: P   O   
 4.12.0-12-generic #13-Ubuntu
[  543.516829] Hardware name: IBM 2964 N63 400 (KVM/Linux)
[  543.516830] task: 0cdb9e00 task.stack: 099e8000
[  543.516831] Krnl PSW : 0704d0018000 001274ec 
(crst_table_upgrade+0x124/0x130)
[  543.516841]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 PM:0 
RI:0 EA:3
[  543.516842] Krnl GPRS: 0001 0400 243d7800 
0020
[  543.516843]1000  0032 

[  543.516844]8000 0020  
1000
[  543.516845]0020 243d7800 001239f6 
099ebbe0
[  543.516853] Krnl Code: 001274de: c0e5002446c1brasl   
%r14,5b0260
[  543.516853]001274e4: a7f4ffb8brc 
15,127454
[  543.516853]   #001274e8: a7f40001brc 
15,1274ea
[  543.516853]   >001274ec: a728fff4lhi %r2,-12
[  543.516853]001274f0: a7f4ffeebrc 
15,1274cc
[  543.516853]001274f4: 0707bcr 0,%r7
[  543.516853]001274f6: 0707bcr 0,%r7
[  543.516853]001274f8: c004brcl0,1274f8
[  543.516862] Call Trace:
[  543.516864] ([<085d8578>] 0x85d8578)
[  543.516868]  [<002f529a>] get_unmapped_area+0x72/0x120 
[  543.516870]  [<002f931a>] do_mmap+0xfa/0x3e0 
[  543.516873]  [<002d6292>] vm_mmap_pgoff+0xca/0x120 
[  543.516874]  [<002f6962>] SyS_mmap_pgoff+0x10a/0x2a0 
[  543.516875]  [<002f6b72>] SyS_old_mmap+0x7a/0xa8 
[  543.516880]  [<00864c1c>] system_call+0xc4/0x27c 
[  543.516881] Last Breaking-Event-Address:
[  543.516882]  [<001274e8>] crst_table_upgrade+0x120/0x130
[  543.516883]  
[  543.516883] ---[ end trace 036f94bf79a83905 ]---

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.12.0-12-generic 4.12.0-12.13
ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
Uname: Linux 4.12.0-12-generic s390x
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: 
ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.6-0ubuntu6
Architecture: s390x
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not 
found.
Date: Thu Aug 24 05:01:08 2017
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lspci:
 
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:
 
ProcEnviron:
 TERM=vt220
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C
 SHELL=/bin/bash
ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
ProcKernelCmdLine: root=UUID=d86dc8de-6ac8-4e4b-aba8-92872a209a8c 
crashkernel=196M
RelatedPackageVersions:
 linux-restricted-modules-4.12.0-12-generic N/A
 linux-backports-modules-4.12.0-12-generic  N/A
 linux-firmware 1.167
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug artful package-from-proposed s390x

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

Title:
  s390 zKVM complains about "illegal operation" to s390/mm/pgalloc.c

Status in linux package in Ubuntu:
  New

Bug description:
  [  543.516708] kernel BUG at 
/build/linux-a7axPg/linux-4.12.0/arch/s390/mm/pgalloc.c:84!
  [  543.516783]

[Kernel-packages] [Bug 1709303] Re: linux: 4.10.0-33.37 -proposed tracker

2017-08-23 Thread Gavin Lin

Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-testing/zesty/4.10.0-33.37
/zesty-proposed-published.html

** Tags added: certification-testing-passed

** Changed in: kernel-sru-workflow/certification-testing
   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/1709303

Title:
  linux: 4.10.0-33.37 -proposed tracker

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

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

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

  backports: 1709304
  derivatives: 1709305
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1712481] Re: HID: multitouch: Support ALPS PTP Stick and Touchpad devices

** Description changed:

[Impact]
Support to ALPS PTP Stick and Touchpad devices found on latest Dell Latitude
systems.

[Fix]
This fix in two parts:
- 1. Requires backport/cherry-pick of patch submitted by ALPS in upstream
kernel 4.13.
- (The backport is only for Xenial due to the differences in context)
+ 1. Requires cherry-pick of patch submitted by ALPS in upstream kernel 4.13
See:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v4.13-rc6=504c932c7c47a6b4c572302a13873f7d83af1ff3

2. Additional sauce patch adds the device-id of the new PTP stick. This
patch is already submitted to linux-input and is pending review.
See: http://marc.info/?l=linux-input=150235885218076=2

[Test Case]
Verified on the systems affected with this issue and confirmed that this
solution works.

[Regression Potential]
The patch adds new device ids to hid multi-touch driver. With strict
conditional filtering based on these device-ids, regression potential is
minimal.

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

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

Title:
HID: multitouch: Support ALPS PTP Stick and Touchpad devices

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

Bug description:
[Impact]
Support to ALPS PTP Stick and Touchpad devices found on latest Dell Latitude
systems.

[Fix]
This fix in two parts:
1. Requires cherry-pick of patch submitted by ALPS in upstream kernel 4.13
See:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v4.13-rc6=504c932c7c47a6b4c572302a13873f7d83af1ff3

2. Additional sauce patch adds the device-id of the new PTP stick. This
patch is already submitted to linux-input and is pending review.
See: http://marc.info/?l=linux-input=150235885218076=2

[Test Case]
Verified on the systems affected with this issue and confirmed that this
solution works.

[Regression Potential]
The patch adds new device ids to hid multi-touch driver. With strict
conditional filtering based on these device-ids, regression potential is
minimal.

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

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

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

[Kernel-packages] [Bug 1644056] Re: kernel BUG at /build/linux-lts-xenial-gUF4JR/linux-lts-xenial-4.4.0/mm/huge_memory.c:1931!

2017-08-23 Thread asm64

Ubuntu Server

# cat /etc/os-release | grep "VERSION="
VERSION="16.04.3 LTS (Xenial Xerus)"
# uname -r
4.4.0-91-generic

Kernel log in attachment. Patch released in april
https://lkml.org/lkml/2017/4/10/152


** Attachment added: "kps-KERNEL.BUG2.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1644056/+attachment/4937786/+files/kps-KERNEL.BUG2.txt

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

Title:
  kernel BUG at /build/linux-lts-xenial-gUF4JR/linux-lts-
  xenial-4.4.0/mm/huge_memory.c:1931!

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  While running IO on the following kernel/Ubuntu version:

  $ lsb_release -rd
  Description:Ubuntu 14.04.5 LTS
  Release:14.04

  $ uname -a
  Linux 4.4.0-31-generic #50~14.04.1-Ubuntu SMP Wed Jul 13 01:07:32 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

  $ cat /etc/issue
  Ubuntu 14.04.5 LTS \n \l

  [1133672.985186] 
/build/linux-lts-xenial-gUF4JR/linux-lts-xenial-4.4.0/mm/pgtable-generic.c:33: 
bad pmd 881fd6790240(80004b8008e7)
  [1135572.440941] huge_memory: mapcount 0 page_mapcount 1
  [1135572.441607] [ cut here ]
  [1135572.442059] kernel BUG at 
/build/linux-lts-xenial-gUF4JR/linux-lts-xenial-4.4.0/mm/huge_memory.c:1931!
  [1135572.442571] invalid opcode:  [#1] SMP
  [1135572.443028] Modules linked in: intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm joydev input_leds sb_edac irqbypass 
crct10dif_pclmul crc32_pclmul aesni_intel edac_core aes_x86_64 lrw gf128mul 
glue_helper ablk_helper cryptd dm_multipath lpc_ich ipmi_ssif ipmi_devintf 
shpchp 8250_fintek mac_hid acpi_power_meter ipmi_si ipmi_msghandler iTCO_wdt 
iTCO_vendor_support raid10 raid456 async_raid6_recov async_memcpy async_pq 
async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear ses enclosure 
raid1 ast ttm ixgbe hid_generic igb vxlan drm_kms_helper syscopyarea 
ip6_udp_tunnel usbhid dca sysfillrect udp_tunnel sysimgblt hid mxm_wmi 
fb_sys_fops mpt3sas ptp drm ahci raid_class pps_core libahci i2c_algo_bit mdio 
scsi_transport_sas fjes wmi
  [1135572.448909] CPU: 15 PID: 2018 Comm: sh Not tainted 4.4.0-31-generic 
#50~14.04.1-Ubuntu
  [1135572.450082] Hardware name: Quanta Computer Inc. 
X-100.Column.01/S2PC-MB(Dual 1G LOM), BIOS S2P_3B04.HGT02 09/21/2016
  [1135572.451346] task: 8814923ae040 ti: 882eba658000 task.ti: 
882eba658000
  [1135572.452494] RIP: 0010:[]  [] 
__split_huge_page+0x691/0x6d0
  [1135572.453580] RSP: 0018:882eba65b7e0  EFLAGS: 00010292
  [1135572.454589] RAX: 0027 RBX: ea00012e RCX: 

  [1135572.455742] RDX: 0001 RSI: 883fff3cdc78 RDI: 
883fff3cdc78
  [1135572.457040] RBP: 882eba65b860 R08:  R09: 
881fe93eaf00
  [1135572.458271] R10: 03ff R11: 0ac1 R12: 

  [1135572.459539] R13: 882eba65ba10 R14: ea00012e R15: 
ea00012e
  [1135572.460746] FS:  7fcf6b305740() GS:883fff3c() 
knlGS:
  [1135572.461972] CS:  0010 DS:  ES:  CR0: 80050033
  [1135572.463237] CR2: 558db9da0bb8 CR3: 0021667eb000 CR4: 
003406e0
  [1135572.464515] DR0:  DR1:  DR2: 

  [1135572.465831] DR3:  DR6: fffe0ff0 DR7: 
0400
  [1135572.467177] Stack:
  [1135572.468502]   882eba65b840 811bdfe9 
883fed2e51d0
  [1135572.469769]  811c67c8 883fee9bb760 0007f43c9000 
882eba65ba10
  [1135572.471040]  7b6d 81c72fa0 883ff17340f4 
ea00012e
  [1135572.472277] Call Trace:
  [1135572.473574]  [] ? rmap_walk+0x239/0x2d0
  [1135572.475079]  [] split_huge_page_to_list+0x67/0xd0
  [1135572.476473]  [] add_to_swap+0x57/0x70
  [1135572.477852]  [] shrink_page_list+0x62c/0x770
  [1135572.479246]  [] shrink_inactive_list+0x1e9/0x500
  [1135572.480688]  [] shrink_lruvec+0x58e/0x730
  [1135572.482077]  [] ? __queue_work+0x130/0x350
  [1135572.483615]  [] ? __queue_work+0x130/0x350
  [1135572.485078]  [] shrink_zone+0xdc/0x2c0
  [1135572.486661]  [] do_try_to_free_pages+0x164/0x440
  [1135572.488354]  [] ? throttle_direct_reclaim+0x8d/0x230
  [1135572.490068]  [] try_to_free_pages+0xb5/0x170
  [1135572.491535]  [] __alloc_pages_nodemask+0x597/0xac0
  [1135572.493287]  [] alloc_kmem_pages_node+0x4d/0xd0
  [1135572.495083]  [] copy_process+0x185/0x1c70
  [1135572.496792]  [] ? from_kgid_munged+0x12/0x20
  [1135572.498404]  [] ? cp_new_stat+0x13d/0x160
  [1135572.500116]  [] _do_fork+0x8a/0x310
  [1135572.501866]  [] SyS_clone+0x19/0x20
  [1135572.503672]  [] entry_SYSCALL_64_fastpath+0x16/0x75
  [1135572.505395] Code: 16 d0 fe ff e9 37 fa ff ff 0f 0b 0f 0b 0f 0b 0f 0b 0f 
0b 41 8b 57 18 8b 75 a4 48 c7 c7 48 f0 ac 81 31 c0

[Kernel-packages] [Bug 1696102] Re: xfs/073 test fails with Metadata corruption detected on xfs file system (xfsprogs)

** Changed in: ubuntu-power-systems
   Status: Confirmed => Fix Released

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Canonical Foundations Team 
(canonical-foundations)

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

Title:
  xfs/073 test fails with Metadata corruption detected on xfs file
  system (xfsprogs)

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in xfsprogs package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in xfsprogs source package in Xenial:
  Triaged
Status in linux source package in Zesty:
  Invalid
Status in xfsprogs source package in Zesty:
  Triaged

Bug description:
  Problem Description
  
  xfs/073 test fails with Metadata corruption detected on xfs file system. Test 
fails with _check_xfs_filesystem: filesystem on /mnt/test/84004.image2 is 
inconsistent.

  # diff -u tests/xfs/073.out /root/xfstests-dev/results//xfs/073.out.bad
  --- tests/xfs/073.out 2017-03-23 12:13:05.288877197 +0530
  +++ /root/xfstests-dev/results//xfs/073.out.bad   2017-03-27 
11:11:43.023059702 +0530
  @@ -59,8 +59,7 @@
   comparing new image geometry to old
   unmounting and removing new image
   checking new image
  -mounting new image on loopback
  -comparing new image files to old
  -comparing new image directories to old
  -comparing new image geometry to old
  -unmounting and removing new image
  +_check_xfs_filesystem: filesystem on /mnt/test/15413.image2 is inconsistent 
(c)
  +(see /root/xfstests-dev/results//xfs/073.full for details)
  +_check_xfs_filesystem: filesystem on /mnt/test/15413.image2 is inconsistent 
(r)
  +(see /root/xfstests-dev/results//xfs/073.full for details)

  Metadata corruption detected at xfs_agf block 0x1/0x200

  # uname -a
  Linux ltc-tuleta12 4.10.0-21-generic #23~16.04.1-Ubuntu SMP Tue May 2 
12:54:57 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Steps to reproduce:
  
  1. Create a loop device with xfs filesystem
  2. git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git; cd 
xfstests-dev
  3. make
  4. Create a local.conf for running with created loop device
  5.. Run xfstests-dev test  : ./check tests/xfs/073

  Full log is attached.

  == Comment: #2 - Harish Sriram  - 2017-05-31 01:22:11 ==
  (In reply to comment #1)
  > Hi Harish,
  > Can you share the steps used in creating the loop device with xfs filesystem
  > ?
  > 
  > Thank you.

  Create loop device:
  # mkdir /mnt/loop-device /mnt/test /mnt/scratch

  # for i in $(seq 0 1); do fallocate -o 0 -l 5GiB 
/mnt/loop-device/file-$i.img; done
  # for i in $(seq 0 1); do losetup /dev/loop$i /mnt/loop-device/file-$i.img; 
done

  Create File system:
  # for i in $(seq 0 1); do mkfs.ext4 -F /dev/loop$i; done

  # cat local.config
  export TEST_DEV=/dev/loop0
  export TEST_DIR=/mnt/test
  export SCRATCH_DEV=/dev/loop1
  export SCRATCH_MNT=/mnt/scratch

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

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

[Kernel-packages] [Bug 1704730] Re: xfstest fails with corrupt file /mnt/scratch/1 - non-zero size but no extents ( ext4 )

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

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

Title:
  xfstest fails with corrupt file /mnt/scratch/1 - non-zero size but no
  extents ( ext4 )

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

Bug description:
  xfstests fails non-zero size but no extents on ext4 filesystem

  Environment
  --
  Kernel Build:  4.12.1-041201-generic

  Model  : 8247-22L
  Platform:  PowerNV ( P8 )

  Uname output
  ---
  # uname -a
  Linux ltc-test-ci2 4.12.1-041201-generic #201707121132 SMP Wed Jul 12 
17:03:25 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Steps to reproduce:
  
  1. Create a loop device with ext4 filesystem
  2. git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git; cd 
xfstests-dev
  3. make
  4. Create a local.config for running with created loop device
  5. Run xfstests-dev test  : ./check tests/generic/044

  The test 044 fails with following
  generic/044 - output mismatch (see 
/root/harish/xfstests-dev/results//generic/044.out.bad)
  --- tests/generic/044.out 2017-07-13 06:04:36.208323135 -0400
  +++ /root/harish/xfstests-dev/results//generic/044.out.bad
2017-07-14 06:24:08.153731112 -0400
  @@ -1 +1,1000 @@
   QA output created by 044
  +corrupt file /mnt/scratch/1 - non-zero size but no extents
  +corrupt file /mnt/scratch/2 - non-zero size but no extents
  +corrupt file /mnt/scratch/3 - non-zero size but no extents
  +corrupt file /mnt/scratch/4 - non-zero size but no extents
  +corrupt file /mnt/scratch/5 - non-zero size but no extents
  +corrupt file /mnt/scratch/6 - non-zero size but no extents
  ...
  (Run 'diff -u tests/generic/044.out 
/root/harish/xfstests-dev/results//generic/044.out.bad'  to see the entire diff)
  Ran: generic/044
  Failures: generic/044
  Failed 1 of 1 tests

  
  Dmesg:
  --
  [17244.878673] EXT4-fs (loop0): mounted filesystem with ordered data mode. 
Opts: (null)
  [17245.517227] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17245.697100] EXT4-fs (loop0): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17245.710634] run fstests generic/044 at 2017-07-14 06:23:49
  [17246.534410] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17246.535534] EXT4-fs (loop2): shut down requested (1)
  [17246.535625] Aborting journal on device loop2-8.
  [17247.278467] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17259.888304] EXT4-fs (loop2): shut down requested (2)
  [17259.995751] Aborting journal on device loop2-8.
  [17260.113582] EXT4-fs (loop2): recovery complete
  [17260.113902] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17260.190076] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17264.821978] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr


  == Comment: #2 - SEETEENA THOUFEEK  - 2017-07-17 
02:10:52 ==
  Issue does not happen when running the same test with xfs file system. (ie, 
creating loop device with xfs file system).

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

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

[Kernel-packages] [Bug 1706531] Re: ath10k doesn't report full RSSI information

2017-08-23 Thread AceLan Kao

** Tags removed: verification-needed-xenial verification-needed-zesty
** Tags added: verification-done-xenial verification-done-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/1706531

Title:
  ath10k doesn't report full RSSI information

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

Bug description:
  [Impact]
  ASA (Active Steering Antenna) requires per chain RSSI info. Intel WLAN driver 
has full support for per-chain RSSI information, but ath10k doesn't.

  [Fix]
  The fix is pretty simple just fills up RSSI value to the structure.

  [Test Case]
  RSSI information can be polled from userspace using NL80211 wireless stack.

  [Regression Potential]
  No any regression concern.

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

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

[Kernel-packages] [Bug 1290110] Re: Fan stops after resume from suspend leading to overheating; requires reboot to fix [HP Probook 4710s and many others]

2017-08-23 Thread derWalter

Happens regularly but not every time on ubuntu 16.04 on a thinkpad x201.

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

Title:
  Fan stops after resume from suspend leading to overheating; requires
  reboot to fix [HP Probook 4710s and many others]

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

Bug description:
  After resume from suspend, the fan (there is only one) first speeds up to 
about a normal speed and then slows down in a couple of seconds to a complete 
stop. It doesn't spin up again even if the temperatures shoot way up 
(monitoring using indicator-sensors or lm-sensors, both use acpitz info).
  There are 2 ways to get the fan spinning again:
  - reboot the system
  - echo 1 > /sys/class/thermal/cooling_device[4|12...don't remember 
which]/curr_state

  This is happening on a clean install of Trusty from daily build that also has 
the updates-proposed source enabled. Previously the laptop ran 13.10 and 
suspend and resume worked fine.
  Only thing is, I also updated the BIOS during formatting for Trusty, which 
could cause this issue but I'm leaning more towards an ACPI issue (the latest 
BIOS is from 2010 and someone would have probably noticed a problem with the 
fan?)

  Attached is the output from cd /sys/class/thermal && grep . */*
  2&>/dev/null after first boot and after resume suspend; as can be
  seen, after resume all fan states are 0 whereas on boot some are also
  1.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-16-generic 3.13.0-16.36 [modified: 
boot/vmlinuz-3.13.0-16-generic]
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jernej 2582 F pulseaudio
   /dev/snd/controlC0:  jernej 2582 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg:
   [   78.199783] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
   [  104.824460] audit_printk_skb: 147 callbacks suppressed
   [  104.824464] type=1400 audit(1394393526.590:61): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="/usr/lib/cups/backend/cups-pdf" pid=1986 comm="apparmor_parser"
   [  104.824472] type=1400 audit(1394393526.590:62): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" 
pid=1986 comm="apparmor_parser"
   [  104.824884] type=1400 audit(1394393526.590:63): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" 
pid=1986 comm="apparmor_parser"
  Date: Sun Mar  9 20:46:48 2014
  HibernationDevice: RESUME=UUID=79b35f90-100a-4582-9b65-a84fbedf5bf7
  InstallationDate: Installed on 2014-03-08 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140308)
  MachineType: Hewlett-Packard HP ProBook 4710s
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-16-generic 
root=UUID=9561bd56-ffa3-4f61-91cf-019c359ed8e8 ro quiet splash radeon.dpm=1 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-16-generic N/A
   linux-backports-modules-3.13.0-16-generic  N/A
   linux-firmware 1.126
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PZI Ver. F.18
  dmi.board.name: 3074
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 24.0F
  dmi.chassis.asset.tag: CNU9465LRD
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PZIVer.F.18:bd12/02/2010:svnHewlett-Packard:pnHPProBook4710s:pvrF.18:rvnHewlett-Packard:rn3074:rvrKBCVersion24.0F:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4710s
  dmi.product.version: F.18
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 344878] Re: file name too long when creating new file (ecryptfs_lookup: lookup_one_len() returned [-36] on lower_dentry)

2017-08-23 Thread mhalcrow

Hi, original designer/author of eCryptfs chiming in. Sorry for the mess
with file name lengths, but because of technical constraints in the
kernel file system stack and security concerns, I went with the design I
did.

Good news is, I fixed this issue for file-based encryption by designing
it (sort of) right in file system native encryption. That's currently
available in ext4 for kernels 4.1 and later. We're working to switch
from eCryptfs to ext4 encryption for Ubuntu 17.10.

https://github.com/google/fscrypt/issues/24

We've released a really great user space utility to help you do pretty
much everything you can do with eCryptfs today:

https://github.com/google/fscrypt

https://launchpad.net/~ubuntu-security/+archive/ubuntu/ubuntu-security-
staging/+build/13255257

Prior to Ubuntu 17.10, you'll be in "early adopter" territory with ext4
encryption on Ubuntu.

Note that I did make a security tradeoff with the current version of
file name encryption in ext4 for the sake of giving you (1) the full 255
characters and (2) decent performance. If the plaintext prefixes for two
file names in the same directory collide, then the ciphertext prefixes
will also collide. I asked Alex Cope and Eric Biggers to try to fix that
by implementing a new encryption mode that they proposed upstream, but
getting new encryption modes upstream isn't necessarily a trivial
prospect. No real crypto review/comments so far.

https://www.spinics.net/lists/linux-crypto/msg22416.html

Note that Android is carrying the HEH patches and is using that mode for
file name encryption. Hopefully we'll be able to get that upstream at
some point.

** Bug watch added: github.com/google/fscrypt/issues #24
   https://github.com/google/fscrypt/issues/24

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

Title:
  file name too long when creating new file (ecryptfs_lookup:
  lookup_one_len() returned [-36] on lower_dentry)

Status in eCryptfs:
  Fix Released
Status in ecryptfs-utils package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in ecryptfs-utils source package in Natty:
  Won't Fix
Status in linux source package in Natty:
  Won't Fix
Status in ecryptfs-utils source package in Oneiric:
  Won't Fix
Status in linux source package in Oneiric:
  Won't Fix
Status in ecryptfs-utils source package in Precise:
  Invalid
Status in linux source package in Precise:
  Fix Released

Bug description:
  ===
  IMPORTANT: eCryptfs can only store filenames of up to 143 characters when 
filename encryption is enabled. The remaining 112 characters are used for 
storing metadata such as the encrypted filename prefix, the signature of the 
filename encryption key, and an identifier for the cipher used, as well as 
random bytes to make /foo/file and /bar/file encrypt to different ciphertext 
and padding bytes to achieve proper cipher block size alignment.

  This bug is considered 'fixed' by the upstream maintainers. The
  eCryptfs kernel error message has been reduced to a debug level log
  message and eCryptfs now correctly reports its maximum supported
  filename length through the statfs() syscall. This is all that can be
  done without implementing a completely new encrypted filename design.
  A design that allows 255 character filenames without introducing other
  design limitations has not been identified and no one is currently
  working to come up with such a design.

  Please do not add comments or create new bugs saying that mv reports
  'File name too long' or that you can't create a long filename in your
  eCryptfs mounts. It is an unfortunate design limitation that cannot be
  avoided at this time.

  Please do create new bugs when an application generates filenames that are 
too long to be stored in an eCryptfs mount. The application may be able to use 
the statfs() syscall to check the filename length limits of eCryptfs. Note that 
this does not include something like a torrent or ftp client trying to download 
a file with a long filename. The application is not generating the filename in 
those cases, it is just downloading the file that the user told it to download.
  ===

  When trying to create a new file with a relatively long filename (f. ex. 
dfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqb.txt)
  I get an error: file name to long, when in fact the file name is not to long, 
but the encrypted name created for this file is to long, so, the file was not 
created.

  this is no problem when I try to create a file, but when I'm copying a
  lot of files to my home folder I get some: filename to long error's
  and it's hard to fix (first locate the file, create shorter name, move
  again)

  so, maybe you could create a check for to long filenames?

  I'm using ext4

Re: [Kernel-packages] [Bug 1596205] Re: BCM43142 can't work with 16.04

2017-08-23 Thread Alpha

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

Title:
  BCM43142 can't work with 16.04

Status in bcmwl package in Ubuntu:
  Expired

Bug description:
  simon@simon-X455LJ:~$ lshw -C network
  WARNING: you should run this program as super-user.
*-network   
 description: Ethernet interface
 product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0
 bus info: pci@:02:00.0
 logical name: enp2s0
 version: 10
 serial: 9c:5c:8e:32:c8:a6
 size: 100Mbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: bus_master cap_list ethernet physical tp mii 10bt 
10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=full firmware=rtl8168g-3_0.0.1 04/23/13 
ip=192.168.1.101 latency=0 link=yes multicast=yes port=MII speed=100Mbit/s
 resources: irq:48 ioport:e000(size=256) memory:f7204000-f7204fff 
memory:f720-f7203fff
*-network UNCLAIMED
 description: Network controller
 product: BCM43142 802.11b/g/n
 vendor: Broadcom Corporation
 physical id: 0
 bus info: pci@:03:00.0
 version: 01
 width: 64 bits
 clock: 33MHz
 capabilities: bus_master cap_list
 configuration: latency=0
 resources: memory:f710-f7107fff
  WARNING: output may be incomplete or inaccurate, you should run this program 
as super-user.

  
  simon@simon-X455LJ:~$ sudo lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  simon@simon-X455LJ:~$ uname -a
  Linux simon-X455LJ 4.4.0-24-generic #43-Ubuntu SMP Wed Jun 8 19:27:37 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux

  simon@simon-X455LJ:~$ sudo apt-cache policy bcmwl-kernel-source
  bcmwl-kernel-source:
Installed: 6.30.223.248+bdcom-0ubuntu8
Candidate: 6.30.223.248+bdcom-0ubuntu8
Version table:
   *** 6.30.223.248+bdcom-0ubuntu8 500
  500 http://cn.archive.ubuntu.com/ubuntu xenial/restricted amd64 
Packages
  100 /var/lib/dpkg/status

  simon@simon-X455LJ:~$ apt-cache policy broadcom-sta-source
  broadcom-sta-source:
Installed: (none)
Candidate: 6.30.223.271-2
Version table:
   6.30.223.271-2 500
  500 http://cn.archive.ubuntu.com/ubuntu xenial/multiverse amd64 
Packages
  500 http://cn.archive.ubuntu.com/ubuntu xenial/multiverse i386 
Packages
   6.30.223.248-3 500
  500 http://httpredir.debian.org/debian jessie/non-free amd64 Packages
  500 http://httpredir.debian.org/debian jessie/non-free i386 Packages

  simon@simon-X455LJ:~$ lspci -vvnn | grep -A 9 Network
  03:00.0 Network controller [0280]: Broadcom Corporation BCM43142 802.11b/g/n 
[14e4:4365] (rev 01)
Subsystem: Lite-On Communications Inc BCM43142 802.11b/g/n [11ad:6675]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel modules: bcma, wl

  simon@simon-X455LJ:~$ sudo dmidecode -s bios-version
  X455LJ.205

  simon@simon-X455LJ:~$ sudo dmidecode -s bios-release-date
  08/03/2015

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: broadcom-sta-source (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jun 26 00:31:13 2016
  InstallationDate: Installed on 2016-06-21 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: broadcom-sta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1708409] Re: kdump service does not start after configure/reboot

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Canonical Foundations Team 
(canonical-foundations)

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

Title:
  kdump service does not start after configure/reboot

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

Bug description:
  == Comment: #0 - Harish Sriram  - 2017-08-02 01:45:01 ==
  kdump service does not start after configure/reboot

  --Problem Description---
  kdump service does not start after configure/reboot. It has to be 
started/loaded manually, everytime after reboot.

  # kdump-config status
  current state   : Not ready to kdump

  
  ---uname output---
  Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux 
   
  Machine Type/Model = Power 8/8247-22L 

  Additional Info-
  # cat /proc/cmdline
  root=UUID=974df602-c0e4-4e67-8853-78ad15884c59 ro console=tty0 
console=ttyS0,115200 quiet splash cgroup_enable=memory swapaccount=1 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
   
  ---Steps to Reproduce---
  1. installed linux-crashdump
  2. edited the kdump-tools.cfg crashkernel cmdline to above
  3. update-grub
  4. reboot

  Expected:
  kdump-config to be loaded by default after reboot

  # kdump-config status
  current state   : Not ready to kdump

  # service kdump-tools status
  * kdump-tools.service - Kernel crash dump capture service
 Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
pres
 Active: inactive (dead)

  ...
  https://github.com/systemd/systemd/issues/6334

  systemd in artful is not properly picking up the unit files in 
  /etc/systemd/system/default.target.wants

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

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

[Kernel-packages] [Bug 1708096] Re: Ubuntu16.04.3 Installation fails for JFS file system

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

Title:
  Ubuntu16.04.3 Installation fails for JFS file system

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

Bug description:
  ---Problem Description---

  Ubuntu16.04.3 installation fails for JFS file system.

  
  ---Environment---
  Garrison Power8

  
  ---Steps to reproduce---
   Install Ubuntu 16.04.3 with 
   - prepboot
  - /root [JFS filesystem]
  - swap space

  
  ---Fails in below step---

   ?? [!!] Install the GRUB boot loader on a hard disk ??
? ?
?  ?Unable to install GRUB in /dev/sdi1 ? ?
?  ? Executing 'grub-install /dev/sdi1' failed. ? ?
?  ?? ?
? Running "? This is a fatal error. ? ?
?  ?? ?
 ? ?
   ??
   ??



  
   moves;  selects;  activates buttons



  
   ? [!!] Install the GRUB boot loader on a hard disk ??
   ?   ?
   ? Installation step failed  ?
   ? An installation step failed. You can try to run the failing item  ?
   ? again from the menu, or skip it and choose something else. The?
   ? failing step is: Install the GRUB boot loader on a hard disk  ?
   ?   ?
   ? ?
   ?   ?
   ?



  
   moves;  selects;  activates buttons

  
  Comment 3 2017-07-20 04:31:05 CDT

  Based on your error, may be you deleted partition 1 (8MB the PReP boot
  partition) which is required for installing the boot loader in IBM
  power systems.  Or maybe you changed the use type to JFS from PReP
  boot.

  Partition 1 (PReP boot) does NOT contain a filesystem and is not
  mounted.Grub is written to it raw and the firmware loads the contents
  of the partition into ram and executes it raw.

  Can you try one more time,
  Pick the default guided partitioning, then change the root 
partition(partition 2) from ext4(or  filesystem) to JFS.Do not delete and 
create any partitions from the default guided setup. Paste the results.

  Comment 4  2017-07-20 09:22:22 CDT

  (In reply to comment #3)
  > Based on your error, may be you deleted partition 1 (8MB the PReP boot
  > partition) which is required for installing the boot loader in IBM power
  > systems.  Or maybe you changed the use type to JFS from PReP boot. 
  > 
  > Partition 1 (PReP boot) does NOT contain a filesystem and is not
  > mounted.Grub is written to it raw and the firmware loads the contents of the
  > partition into ram and executes it raw.
  > 
  > Can you try one more time,
  > Pick the default guided partitioning, then change the root
  > partition(partition 2) from ext4(or  filesystem) to JFS.Do not delete
  > and create any partitions from the default guided setup. Paste the results.

  No, I have not deleted partition and I have not changed the use type
  to JFS from PReP boot.

  Any ways I tried again and it still fails.

  ?? [!!] Partition disks ???
? ?
? This is an overview of your currently configured partitions and mount   ?
? points. Select a partition to modify its settings (file system, mount   ?
? point, etc.), a free space to create partitions, or a device to ?
? initialize its partition table. ?
? ?
?  SCSI4 (0,0,0) (sdi) - 1.0 TB ATA ST1000NX0313  ?
?  >1.0 MBFREE SPACE  ?   ?
?  > #1 7.3 MB K  ?   ?
?  > #2   959.7 GB F  ext4  / ?   ?
?  > #340.5 GB f  swap  swap  ?
?  >  728.6 kBFREE SPACE  ?   ?
?  SCSI5 (0,0,0) (sdj) - 1.0 TB ATA

[Kernel-packages] [Bug 1333294] Re: 32-bit kernel HDD slow write speed

2017-08-23 Thread Norbert

Got this bug on Ubuntu 16.04 LTS server with 32-bit 
linux-image-4.4.0-92-generic.
My system has 32GB of RAM.

With USB 3.0 SanDisk Extreme Flash I got:
$ dd if=/dev/zero of=1G bs=1M count=1024
1024+0 records in
1024+0 records out
1073741824 bytes (1,1 GB, 1,0 GiB) copied, 171,214 s, 6,3 MB/s

It's terrible slow!

Note: `sudo -w vm.highmem_is_dirtyable=1` helps on 32 bit system.

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

Title:
  32-bit kernel HDD slow write speed

Status in linux package in Ubuntu:
  Confirmed
Status in linux-meta-lts-trusty package in Ubuntu:
  Confirmed

Bug description:
  Summary

  After upgrading my Ubuntu 32-bit from 12.04 to 14.04 the write
  performance is painfully slow (less than 4.6MB/s) of both my SSD
  drives. The read speed is still fine. I've tested with the latest
  version of System Rescue CD (4.2.0 at this time) to see if was a
  hardware problem. However the performance of my drives was even better
  better than using Ubuntu 12.04.

  I've also tried to make a fresh installation of Ubuntu 14.04 on a
  spare SSD drive of mine to see if its because I upgraded from 12.04.
  But after waiting 4 hours for it to install, I finally lost patience,
  and stopped the installation.

  I'm using the deadline scheduler, but it doesn't matter which one I
  use. I'm also using the lowlatency kernel, but using the generic
  kernel doesn't have any effect.

  I've tested with mechanical hard drives, and the problem also occurs
  there.

  I've also tried to update to the proposed updates, and updated to
  kernel 3.13.0-30.54, but problem still exists there.

  The only think that helps is telling the kernel only to address 8GB
  RAM using the "mem=8GB" kernel option, but that is obviously not a
  solution when I need to utilize all the 32GB RAM that I have .

  The reason that I use a 32-bit OS  is because most of the applications
  I use on my laptop are propriety software that only exists in 32-bit
  versions.


  Details

  Kernel version
  root@ubuntu:~# uname -a
  Linux fk20563 3.13.0-29-lowlatency #53-Ubuntu SMP PREEMPT Wed Jun 4 21:20:42 
UTC 2014 i686 i686 i686 GNU/Linux

  List hardware
  lshw > lshw.txt

  Timings of devices (which is also 4x slower than normal)
  root@ubuntu:~# hdparm -t /dev/sda && hdparm -t /dev/sda && hdparm -t /dev/sda
  /dev/sda:
   Timing buffered disk reads: 470 MB in  3.01 seconds = 156.33 MB/sec

  /dev/sda:
   Timing buffered disk reads: 530 MB in  3.03 seconds = 174.86 MB/sec

  /dev/sda:
   Timing buffered disk reads: 500 MB in  3.01 seconds = 166.36 MB/sec

  root@ubuntu:~# hdparm -t /dev/sdb && hdparm -t /dev/sdb && hdparm -t /dev/sdb
  /dev/sdb:
   Timing buffered disk reads: 500 MB in  3.32 seconds = 150.61 MB/sec

  /dev/sdb:
   Timing buffered disk reads: 508 MB in  3.03 seconds = 167.49 MB/sec

  /dev/sdb:
   Timing buffered disk reads: 500 MB in  3.21 seconds = 155.81 MB/sec

  SSD partition alignment check
  root@ubuntu:~# fdisk -l

  Disk /dev/sda: 256.1 GB, 256060514304 bytes
  255 heads, 63 sectors/track, 31130 cylinders, total 500118192 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disk identifier: 0xd162fc6d

  Device Boot Start End Blocks Id System
  /dev/sda1 2048 483332095 241665024 83 Linux
  /dev/sda2 483332096 500117503 8392704 5 Extended
  /dev/sda5 483334144 500117503 8391680 82 Linux swap / Solaris

  Disk /dev/sdb: 480.1 GB, 480103981056 bytes
  255 heads, 63 sectors/track, 58369 cylinders, total 937703088 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disk identifier: 0x

  Device Boot Start End Blocks Id System
  /dev/sdb1 2048 937703087 468850520 83 Linux
  root@ubuntu:~# parted 
  GNU Parted 2.3
  Using /dev/sda
  Welcome to GNU Parted! Type 'help' to view a list of commands.
  (parted) select /dev/sda
  Using /dev/sda
  (parted) align-check opt 1 
  1 aligned
  (parted) select /dev/sdb
  Using /dev/sdb
  (parted) align-check opt 1 
  1 aligned
  (parted) quit 

  Scheduler:
  root@ubuntu:~# cat /sys/block/sd{a,b}/queue/scheduler
  noop [deadline] cfq 
  noop [deadline] cfq 

  Mount options:
  root@fk20563:~# mount | grep sda
  /dev/sda1 on / type ext4 (rw,noatime,nodiratime,errors=remount-ro,discard)
  root@fk20563:~# mount | grep sdb
  /dev/sdb1 on /media/vmware type xfs 
(rw,noatime,nodiratime,logbsize=256k,discard)

  FS read/write check of /dev/sda1 on Ubuntu
  root@fk20563:~# dd if=/dev/zero of=/test.raw bs=1M count=1000
  1000+0 records in
  1000+0 records out
  1048576000 bytes (1.0 GB) copied, 229.091 s, 4.6 MB/s
  root@fk20563:~# dd of=/dev/null if=/test.raw
  2048000+0 records in
  2048000+0 records out
  1048576000 bytes (1.0 GB) copied, 2.58461 s, 406 MB/s

[Kernel-packages] [Bug 1596205] Re: BCM43142 can't work with 16.04

2017-08-23 Thread Christopher M. Penalver

Dmitry Danilson (patchranger), given you have a different problem, different 
hardware subsystem, and likely different WiFi environment, as per the article 
please file a new report via a terminal:
ubuntu-bug bcmwl-kernel-source

Please feel free to subscribe me to it.

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

Title:
  BCM43142 can't work with 16.04

Status in bcmwl package in Ubuntu:
  Expired

Bug description:
  simon@simon-X455LJ:~$ lshw -C network
  WARNING: you should run this program as super-user.
*-network   
 description: Ethernet interface
 product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0
 bus info: pci@:02:00.0
 logical name: enp2s0
 version: 10
 serial: 9c:5c:8e:32:c8:a6
 size: 100Mbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: bus_master cap_list ethernet physical tp mii 10bt 
10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=full firmware=rtl8168g-3_0.0.1 04/23/13 
ip=192.168.1.101 latency=0 link=yes multicast=yes port=MII speed=100Mbit/s
 resources: irq:48 ioport:e000(size=256) memory:f7204000-f7204fff 
memory:f720-f7203fff
*-network UNCLAIMED
 description: Network controller
 product: BCM43142 802.11b/g/n
 vendor: Broadcom Corporation
 physical id: 0
 bus info: pci@:03:00.0
 version: 01
 width: 64 bits
 clock: 33MHz
 capabilities: bus_master cap_list
 configuration: latency=0
 resources: memory:f710-f7107fff
  WARNING: output may be incomplete or inaccurate, you should run this program 
as super-user.

  
  simon@simon-X455LJ:~$ sudo lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  simon@simon-X455LJ:~$ uname -a
  Linux simon-X455LJ 4.4.0-24-generic #43-Ubuntu SMP Wed Jun 8 19:27:37 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux

  simon@simon-X455LJ:~$ sudo apt-cache policy bcmwl-kernel-source
  bcmwl-kernel-source:
Installed: 6.30.223.248+bdcom-0ubuntu8
Candidate: 6.30.223.248+bdcom-0ubuntu8
Version table:
   *** 6.30.223.248+bdcom-0ubuntu8 500
  500 http://cn.archive.ubuntu.com/ubuntu xenial/restricted amd64 
Packages
  100 /var/lib/dpkg/status

  simon@simon-X455LJ:~$ apt-cache policy broadcom-sta-source
  broadcom-sta-source:
Installed: (none)
Candidate: 6.30.223.271-2
Version table:
   6.30.223.271-2 500
  500 http://cn.archive.ubuntu.com/ubuntu xenial/multiverse amd64 
Packages
  500 http://cn.archive.ubuntu.com/ubuntu xenial/multiverse i386 
Packages
   6.30.223.248-3 500
  500 http://httpredir.debian.org/debian jessie/non-free amd64 Packages
  500 http://httpredir.debian.org/debian jessie/non-free i386 Packages

  simon@simon-X455LJ:~$ lspci -vvnn | grep -A 9 Network
  03:00.0 Network controller [0280]: Broadcom Corporation BCM43142 802.11b/g/n 
[14e4:4365] (rev 01)
Subsystem: Lite-On Communications Inc BCM43142 802.11b/g/n [11ad:6675]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel modules: bcma, wl

  simon@simon-X455LJ:~$ sudo dmidecode -s bios-version
  X455LJ.205

  simon@simon-X455LJ:~$ sudo dmidecode -s bios-release-date
  08/03/2015

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: broadcom-sta-source (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jun 26 00:31:13 2016
  InstallationDate: Installed on 2016-06-21 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: broadcom-sta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1712626] Re: Cannot launch virtual instance on nova host after upgrading to kernel 4.4.0.92- works with 4.4.0.83

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

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

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

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

Thanks in advance.

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


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

** Tags added: kernel-da-key

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

Title:
  Cannot launch virtual instance on nova host after upgrading to kernel
  4.4.0.92- works with 4.4.0.83

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Host -- IBM Power 8  822L
  OS- Ubuntu 14.04 ppc64el
  previous kernel 3.19.0.68
  Nova Compute host using kvm - Openstack Liberty

  HWE was out of date so needed to update

  Steps:

  sudo apt-get install linux-generic-lts-xenial linux-image-generic-lts-xenial
  sudo init 6
  sudo apt update
  sudo apt upgrade
  sudo init 6

  afterwards - system seemed ok - kernel 4.4.0.92 installed

  However, launching a Ubuntu VM failed

  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246360] Facility 'TM' unavailable, 
exception at 0xd000189f85a0, MSR=90009033
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246374] Oops: Unexpected facility 
unavailable exception, sig: 6 [#1]
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246379] SMP NR_CPUS=2048 NUMA PowerNV
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246385] Modules linked in: vhost_net 
vhost macvtap macvlan xt_REDIRECT nf_nat_redirect xt_mark xt_nat ip6table_raw 
nf_conntrack_ipv6
   xt_CT xt_mac xt_comment xt_physdev br_netfilter iptable_raw veth xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 
nf_nat nf_conntrac
  k_ipv4 nf_defrag_ipv4 xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables 
x_tables vport_gre ip_gre 
  ip_tunnel gre nbd kvm_hv kvm ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core 
ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi openvswitch 
nf_defrag_ipv6 nf_conn
  track dm_crypt bridge stp llc dm_multipath uio_pdrv_genirq ipmi_powernv 
ipmi_msghandler uio ibmpowernv powernv_rng vmx_crypto leds_powernv ses 
enclosure bnx2x vxlan ip6_udp_
  tunnel udp_tunnel mdio libcrc32c ipr
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246500] CPU: 96 PID: 52779 Comm: 
qemu-system-ppc Not tainted 4.4.0-92-generic #115~14.04.1-Ubuntu
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246506] task: c01e228dcf60 ti: 
c01e229f4000 task.ti: c01e229f4000
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246511] NIP: d000189f85a0 LR: 
d000188a2584 CTR: d000189f84f0
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246516] REGS: c01e229f7840 TRAP: 
0f60   Not tainted  (4.4.0-92-generic)
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246519] MSR: 90009033 
  CR: 28022448  XER: 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] CFAR: d000189f8534 
SOFTE: 1 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR00: d000188a2584 
c01e229f7ac0 d00018a0c7f8 c01c4c68 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR04: c01c5308 
c01e229f7bc0  0004 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR08: 0001 
c01e228dcf60  d000188a7518 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR12: d000189f84f0 
cfb79000 3fff7d74ed40 3fff7d74f3d0 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR16: 3fff7cf5 
 0003 3fff7d750010 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR20: 100c0570 
01000f6ebba0 0080 3fff85644330 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR24:  
3fff7cf30028 d4f6d401 0010 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR28:  
c01c4c68 c01c4c68 c01c5308 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246594] NIP [d000189f85a0] 
kvmppc_vcpu_run_hv+0xb0/0x610 [kvm_hv]
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246606] LR [d000188a2584] 
kvmppc_vcpu_run+0x44/0x60 [kvm]
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246610] Call Trace:
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246617] [c01e229f7ac0] 
[c00ca294] recalc_sigpending+0x24/0x90 (unreliable)
  Aug 23 11:38:25 rcsnode03 kernel: [

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

This change was made by a bot.

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

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

Title:
  The computer don't recognize my cellphone device.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I connect my cellphone to the USB port, my cellphone recognize it
  and show me options of connection, but the computer don't show me
  anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-121-generic 3.13.0-121.170
  ProcVersionSignature: Ubuntu 3.13.0-121.170-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-121-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vinicius   2282 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Aug 23 18:01:35 2017
  GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
  HibernationDevice: RESUME=UUID=d02a4916-1c22-45b2-bfb1-c8761de14e8e
  HotplugNewDevices:
   
  HotplugNewMounts:
   
  InstallationDate: Installed on 2014-02-20 (1280 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  MachineType: Dell Inc. Inspiron N4050
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-121-generic 
root=UUID=252638a5-b37d-45ae-8a1f-02a56ee91c75 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-121-generic N/A
   linux-backports-modules-3.13.0-121-generic  N/A
   linux-firmware  1.127.23
  SourcePackage: linux
  Symptom: storage
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   18:02:09.163: The udisks-daemon is running (name-owner :1.80).
  UpgradeStatus: Upgraded to trusty on 2015-03-18 (889 days ago)
  dmi.bios.date: 11/14/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0X0DC1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A06
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd11/14/2011:svnDellInc.:pnInspironN4050:pvrNotSpecified:rvnDellInc.:rn0X0DC1:rvrA06:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron N4050
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1712688] [NEW] The computer don't recognize my cellphone device.

2017-08-23 Thread Sofia Jardim Carvalho

Public bug reported:

When I connect my cellphone to the USB port, my cellphone recognize it
and show me options of connection, but the computer don't show me
anything.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-121-generic 3.13.0-121.170
ProcVersionSignature: Ubuntu 3.13.0-121.170-generic 3.13.11-ckt39
Uname: Linux 3.13.0-121-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.24
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  vinicius   2282 F pulseaudio
CurrentDesktop: Unity
Date: Wed Aug 23 18:01:35 2017
GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
HibernationDevice: RESUME=UUID=d02a4916-1c22-45b2-bfb1-c8761de14e8e
HotplugNewDevices:
 
HotplugNewMounts:
 
InstallationDate: Installed on 2014-02-20 (1280 days ago)
InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
MachineType: Dell Inc. Inspiron N4050
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-121-generic 
root=UUID=252638a5-b37d-45ae-8a1f-02a56ee91c75 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-121-generic N/A
 linux-backports-modules-3.13.0-121-generic  N/A
 linux-firmware  1.127.23
SourcePackage: linux
Symptom: storage
UdisksMonitorLog:
 Monitoring the udisks daemon. Press Ctrl+C to exit.
 18:02:09.163: The udisks-daemon is running (name-owner :1.80).
UpgradeStatus: Upgraded to trusty on 2015-03-18 (889 days ago)
dmi.bios.date: 11/14/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0X0DC1
dmi.board.vendor: Dell Inc.
dmi.board.version: A06
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd11/14/2011:svnDellInc.:pnInspironN4050:pvrNotSpecified:rvnDellInc.:rn0X0DC1:rvrA06:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron N4050
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug trusty

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

Title:
  The computer don't recognize my cellphone device.

Status in linux package in Ubuntu:
  New

Bug description:
  When I connect my cellphone to the USB port, my cellphone recognize it
  and show me options of connection, but the computer don't show me
  anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-121-generic 3.13.0-121.170
  ProcVersionSignature: Ubuntu 3.13.0-121.170-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-121-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vinicius   2282 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Aug 23 18:01:35 2017
  GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
  HibernationDevice: RESUME=UUID=d02a4916-1c22-45b2-bfb1-c8761de14e8e
  HotplugNewDevices:
   
  HotplugNewMounts:
   
  InstallationDate: Installed on 2014-02-20 (1280 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  MachineType: Dell Inc. Inspiron N4050
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-121-generic 
root=UUID=252638a5-b37d-45ae-8a1f-02a56ee91c75 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-121-generic N/A
   linux-backports-modules-3.13.0-121-generic  N/A
   linux-firmware  1.127.23
  SourcePackage: linux
  Symptom: storage
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   18:02:09.163: The udisks-daemon is running (name-owner :1.80).
  UpgradeStatus: Upgraded to trusty on 2015-03-18 (889 days ago)
  dmi.bios.date: 11/14/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0X0DC1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A06
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd11/14/2011:svnDellInc.:pnInspironN4050:pvrNotSpecified:rvnDellInc.:rn0X0DC1:rvrA06:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron N4050
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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

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

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

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1712626

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

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

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

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

** Tags added: xenial

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

Title:
  Cannot launch virtual instance on nova host after upgrading to kernel
  4.4.0.92- works with 4.4.0.83

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Host -- IBM Power 8  822L
  OS- Ubuntu 14.04 ppc64el
  previous kernel 3.19.0.68
  Nova Compute host using kvm - Openstack Liberty

  HWE was out of date so needed to update

  Steps:

  sudo apt-get install linux-generic-lts-xenial linux-image-generic-lts-xenial
  sudo init 6
  sudo apt update
  sudo apt upgrade
  sudo init 6

  afterwards - system seemed ok - kernel 4.4.0.92 installed

  However, launching a Ubuntu VM failed

  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246360] Facility 'TM' unavailable, 
exception at 0xd000189f85a0, MSR=90009033
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246374] Oops: Unexpected facility 
unavailable exception, sig: 6 [#1]
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246379] SMP NR_CPUS=2048 NUMA PowerNV
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246385] Modules linked in: vhost_net 
vhost macvtap macvlan xt_REDIRECT nf_nat_redirect xt_mark xt_nat ip6table_raw 
nf_conntrack_ipv6
   xt_CT xt_mac xt_comment xt_physdev br_netfilter iptable_raw veth xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 
nf_nat nf_conntrac
  k_ipv4 nf_defrag_ipv4 xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables 
x_tables vport_gre ip_gre 
  ip_tunnel gre nbd kvm_hv kvm ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core 
ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi openvswitch 
nf_defrag_ipv6 nf_conn
  track dm_crypt bridge stp llc dm_multipath uio_pdrv_genirq ipmi_powernv 
ipmi_msghandler uio ibmpowernv powernv_rng vmx_crypto leds_powernv ses 
enclosure bnx2x vxlan ip6_udp_
  tunnel udp_tunnel mdio libcrc32c ipr
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246500] CPU: 96 PID: 52779 Comm: 
qemu-system-ppc Not tainted 4.4.0-92-generic #115~14.04.1-Ubuntu
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246506] task: c01e228dcf60 ti: 
c01e229f4000 task.ti: c01e229f4000
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246511] NIP: d000189f85a0 LR: 
d000188a2584 CTR: d000189f84f0
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246516] REGS: c01e229f7840 TRAP: 
0f60   Not tainted  (4.4.0-92-generic)
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246519] MSR: 90009033 
  CR: 28022448  XER: 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] CFAR: d000189f8534 
SOFTE: 1 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR00: d000188a2584 
c01e229f7ac0 d00018a0c7f8 c01c4c68 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR04: c01c5308 
c01e229f7bc0  0004 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR08: 0001 
c01e228dcf60  d000188a7518 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR12: d000189f84f0 
cfb79000 3fff7d74ed40 3fff7d74f3d0 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR16: 3fff7cf5 
 0003 3fff7d750010 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR20: 100c0570 
01000f6ebba0 0080 3fff85644330 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR24:  
3fff7cf30028 d4f6d401 0010 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR28:  
c01c4c68 c01c4c68 c01c5308 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246594] NIP [d000189f85a0] 
kvmppc_vcpu_run_hv+0xb0/0x610 [kvm_hv]
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246606] LR [d000188a2584] 
kvmppc_vcpu_run+0x44/0x60 [kvm]
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246610] Call Trace:
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246617] [c01e229f7ac0] 
[c00ca294] recalc_sigpending+0x24/0x90 (unreliable)
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246630] [c01e229f7b70] 
[d000188a2584] kvmppc_vcpu_run+0x44/0x60 [kvm]
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246642]

[Kernel-packages] [Bug 1712508] Re: Disappearing screen and flickering after upgrade to 16.04

2017-08-23 Thread udippel

Sorry, but I run into another bug:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1439784

Therefore, I get the notorious
ERROR: Could not import module, is a package upgrade in progress?  Error: No 
module named PyQt5.QtCore

I add the dmesg, thinking it will help further

** Attachment added: "dmesg_nogood"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1712508/+attachment/4937696/+files/dmesg_nogood

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

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

Title:
  Disappearing screen and flickering after upgrade to 16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have two Lenovo T410s that I upgraded from 14.04 to 16.04.
  Since then, one is working fine while the other shows mainly an ever 
disappearing screen and flickering.

  I have asked here: 
https://askubuntu.com/questions/947233/i-upgraded-from-kubuntu-14-04-lts-to-16-04-lts-and-now-my-screen-shows-up-and-di?noredirect=1#comment1506995_947233
  I also found I am not the only one: 
https://askubuntu.com/questions/927407/flickering-screen-with-intel-graphics-on-ubuntu-17-04?noredirect=1#comment1507937_927407
  The latter has tried pretty much that could be tried already, to no avail.

  I think that I can help with this problem, since my two T410s are
  identical in hard- and software, including BIOS, except that one is a
  type 2924 (with NVIDIA-card, though disabled in the BIOS), and the
  other one is a 2904 (without NVIDIA card).

  I have checked for differences at boot time and found DMAR as major 
difference:
  T410s, 2924: [ 0.335616] DMAR: Disabling batched IOTLB flush on Ironlake
  T410s, 2904: [ 0.355681] DMAR: BIOS has allocated no shadow GTT; disabling 
IOMMU for graphics 

  Should this be initially at the root of the problem, I'd consider the
  kernel package as responsible, therefore I marked it as above.

  The outputs of lspci -k | grep -EA3 'VGA|3D|Display' are identical to
  the point.

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

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

[Kernel-packages] [Bug 1709784] Re: KVM on 16.04.3 throws an error

There is commit 17d381054b1d6f4adc3db623b2066fff41b4dc1a ("KVM: PPC: Book3S HV: 
Reload HTM registers explicitly") from
v4.4.80 series that is in Xenial master-next.  I built a master-next test 
kernel, which can be downloaded from:

Xenial: http://kernel.ubuntu.com/~jsalisbury/lp1709784/xenial/

Can you test these kernels and see if they resolve this bug?

Thanks in advance!

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

Title:
  KVM on 16.04.3 throws an error

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in qemu package in Ubuntu:
  Won't Fix
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  Invalid

Bug description:
  Problem Description
  
  KVM on Ubuntu 16.04.3 throws an error when used
   
  ---uname output---
  Linux bastion-1 4.4.0-89-generic #112-Ubuntu SMP Mon Jul 31 19:37:08 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type =  8348-21C Habanero 
   
  ---Steps to Reproduce---
   Install 16.04.3

  install KVM like:

  apt-get install libvirt-bin qemu qemu-slof qemu-system qemu-utils

  then exit and log back in so virsh will work without sudo

  then run my spawn script

  $ cat spawn.sh
  #!/bin/bash

  img=$1
  qemu-system-ppc64 \
  -machine pseries,accel=kvm,usb=off -cpu host -m 512 \
  -display none -nographic \
  -net nic -net user \
  -drive "file=$img"

  with a freshly downloaded ubuntu cloud image

  sudo ./spawn.sh xenial-server-cloudimg-ppc64el-disk1.img

  And I get nothing on the output.

  and errors in dmesg

  
  ubuntu@bastion-1:~$ [  340.180295] Facility 'TM' unavailable, exception at 
0xd000148b7f10, MSR=90009033
  [  340.180399] Oops: Unexpected facility unavailable exception, sig: 6 [#1]
  [  340.180513] SMP NR_CPUS=2048 NUMA PowerNV
  [  340.180547] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables 
iptable_filter ip_tables x_tables kvm_hv kvm binfmt_misc joydev input_leds 
mac_hid opal_prd ofpart cmdlinepart powernv_flash ipmi_powernv ipmi_msghandler 
mtd at24 uio_pdrv_genirq uio ibmpowernv powernv_rng vmx_crypto ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath 
linear mlx4_en hid_generic usbhid hid uas usb_storage ast i2c_algo_bit bnx2x 
ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops mlx4_core drm 
ahci vxlan libahci ip6_udp_tunnel udp_tunnel mdio libcrc32c
  [  340.181331] CPU: 46 PID: 5252 Comm: qemu-system-ppc Not tainted 
4.4.0-89-generic #112-Ubuntu
  [  340.181382] task: c01e34c30b50 ti: c01e34ce4000 task.ti: 
c01e34ce4000
  [  340.181432] NIP: d000148b7f10 LR: d00014822a14 CTR: 
d000148b7e40
  [  340.181475] REGS: c01e34ce77b0 TRAP: 0f60   Not tainted  
(4.4.0-89-generic)
  [  340.181519] MSR: 90009033   CR: 22024848  
XER: 
  [  340.181629] CFAR: d000148b7ea4 SOFTE: 1 
  GPR00: d00014822a14 c01e34ce7a30 d000148cc018 c01e37bc 
  GPR04: c01db9ac c01e34ce7bc0   
  GPR08: 0001 c01e34c30b50 0001 d000148278f8 
  GPR12: d000148b7e40 cfb5b500  001f 
  GPR16: 3fff91c3 0080 3fffa8e34390 3fff9242f200 
  GPR20: 3fff92430010 01001de5c030 3fff9242eb60 100c1ff0 
  GPR24: 3fffc91fe990 3fff91c10028  c01e37bc 
  GPR28:  c01db9ac c01e37bc c01db9ac 
  [  340.182315] NIP [d000148b7f10] kvmppc_vcpu_run_hv+0xd0/0xff0 [kvm_hv]
  [  340.182357] LR [d00014822a14] kvmppc_vcpu_run+0x44/0x60 [kvm]
  [  340.182394] Call Trace:
  [  340.182413] [c01e34ce7a30] [c01e34ce7ab0] 0xc01e34ce7ab0 
(unreliable)
  [  340.182468] [c01e34ce7b70] [d00014822a14] 
kvmppc_vcpu_run+0x44/0x60 [kvm]
  [  340.182522] [c01e34ce7ba0] [d0001481f674] 
kvm_arch_vcpu_ioctl_run+0x64/0x170 [kvm]
  [  340.182581] [c01e34ce7be0] [d00014813918] 
kvm_vcpu_ioctl+0x528/0x7b0 [kvm]
  [  340.182634] [c01e34ce7d40] [c02fffa0] do_vfs_ioctl+0x480/0x7d0
  [  340.182678] [c01e34ce7de0] [c03003c4] SyS_ioctl+0xd4/0xf0
  [  340.182723] [c01e34ce7e30] [c0009204] system_call+0x38/0xb4
  [  340.182766] Instruction dump:
  [  340.182788] e92d02a0 e9290a50 e9290108 792a07e3 41820058 e92d02a0 e9290a50 
e9290108 
  [  340.182863] 7927e8a4

[Kernel-packages] [Bug 1712626] Re: Cannot launch virtual instance on nova host after upgrading to kernel 4.4.0.92- works with 4.4.0.83

2017-08-23 Thread Brian Murray

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

Title:
  Cannot launch virtual instance on nova host after upgrading to kernel
  4.4.0.92- works with 4.4.0.83

Status in linux package in Ubuntu:
  New

Bug description:
  Host -- IBM Power 8  822L
  OS- Ubuntu 14.04 ppc64el
  previous kernel 3.19.0.68
  Nova Compute host using kvm - Openstack Liberty

  HWE was out of date so needed to update

  Steps:

  sudo apt-get install linux-generic-lts-xenial linux-image-generic-lts-xenial
  sudo init 6
  sudo apt update
  sudo apt upgrade
  sudo init 6

  afterwards - system seemed ok - kernel 4.4.0.92 installed

  However, launching a Ubuntu VM failed

  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246360] Facility 'TM' unavailable, 
exception at 0xd000189f85a0, MSR=90009033
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246374] Oops: Unexpected facility 
unavailable exception, sig: 6 [#1]
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246379] SMP NR_CPUS=2048 NUMA PowerNV
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246385] Modules linked in: vhost_net 
vhost macvtap macvlan xt_REDIRECT nf_nat_redirect xt_mark xt_nat ip6table_raw 
nf_conntrack_ipv6
   xt_CT xt_mac xt_comment xt_physdev br_netfilter iptable_raw veth xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 
nf_nat nf_conntrac
  k_ipv4 nf_defrag_ipv4 xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables 
x_tables vport_gre ip_gre 
  ip_tunnel gre nbd kvm_hv kvm ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core 
ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi openvswitch 
nf_defrag_ipv6 nf_conn
  track dm_crypt bridge stp llc dm_multipath uio_pdrv_genirq ipmi_powernv 
ipmi_msghandler uio ibmpowernv powernv_rng vmx_crypto leds_powernv ses 
enclosure bnx2x vxlan ip6_udp_
  tunnel udp_tunnel mdio libcrc32c ipr
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246500] CPU: 96 PID: 52779 Comm: 
qemu-system-ppc Not tainted 4.4.0-92-generic #115~14.04.1-Ubuntu
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246506] task: c01e228dcf60 ti: 
c01e229f4000 task.ti: c01e229f4000
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246511] NIP: d000189f85a0 LR: 
d000188a2584 CTR: d000189f84f0
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246516] REGS: c01e229f7840 TRAP: 
0f60   Not tainted  (4.4.0-92-generic)
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246519] MSR: 90009033 
  CR: 28022448  XER: 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] CFAR: d000189f8534 
SOFTE: 1 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR00: d000188a2584 
c01e229f7ac0 d00018a0c7f8 c01c4c68 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR04: c01c5308 
c01e229f7bc0  0004 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR08: 0001 
c01e228dcf60  d000188a7518 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR12: d000189f84f0 
cfb79000 3fff7d74ed40 3fff7d74f3d0 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR16: 3fff7cf5 
 0003 3fff7d750010 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR20: 100c0570 
01000f6ebba0 0080 3fff85644330 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR24:  
3fff7cf30028 d4f6d401 0010 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR28:  
c01c4c68 c01c4c68 c01c5308 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246594] NIP [d000189f85a0] 
kvmppc_vcpu_run_hv+0xb0/0x610 [kvm_hv]
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246606] LR [d000188a2584] 
kvmppc_vcpu_run+0x44/0x60 [kvm]
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246610] Call Trace:
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246617] [c01e229f7ac0] 
[c00ca294] recalc_sigpending+0x24/0x90 (unreliable)
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246630] [c01e229f7b70] 
[d000188a2584] kvmppc_vcpu_run+0x44/0x60 [kvm]
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246642] [c01e229f7ba0] 
[d0001889f274] kvm_arch_vcpu_ioctl_run+0x64/0x180 [kvm]
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246653] [c01e229f7be0] 
[d00018893898] kvm_vcpu_ioctl+0x5e8/0x7c0 [kvm]
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246661] [c01e229f7d40] 
[c02ef7d0] do_vfs_ioctl+0x4d0/0x7e0
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246667] [c01e229f7de0] 
[c02efbb4] SyS_ioctl+0xd4/0xf0
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246673] [c01e229f7e30] 
[c0009204] system_call+0x38/0xb4
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246677]

[Kernel-packages] [Bug 1712626] [NEW] Cannot launch virtual instance on nova host after upgrading to kernel 4.4.0.92- works with 4.4.0.83

2017-08-23 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

Host -- IBM Power 8  822L
OS- Ubuntu 14.04 ppc64el
previous kernel 3.19.0.68
Nova Compute host using kvm - Openstack Liberty

HWE was out of date so needed to update

Steps:

sudo apt-get install linux-generic-lts-xenial linux-image-generic-lts-xenial
sudo init 6
sudo apt update
sudo apt upgrade
sudo init 6

afterwards - system seemed ok - kernel 4.4.0.92 installed

However, launching a Ubuntu VM failed

Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246360] Facility 'TM' unavailable, 
exception at 0xd000189f85a0, MSR=90009033
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246374] Oops: Unexpected facility 
unavailable exception, sig: 6 [#1]
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246379] SMP NR_CPUS=2048 NUMA PowerNV
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246385] Modules linked in: vhost_net 
vhost macvtap macvlan xt_REDIRECT nf_nat_redirect xt_mark xt_nat ip6table_raw 
nf_conntrack_ipv6
 xt_CT xt_mac xt_comment xt_physdev br_netfilter iptable_raw veth xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 
nf_nat nf_conntrac
k_ipv4 nf_defrag_ipv4 xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables 
x_tables vport_gre ip_gre 
ip_tunnel gre nbd kvm_hv kvm ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core 
ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi openvswitch 
nf_defrag_ipv6 nf_conn
track dm_crypt bridge stp llc dm_multipath uio_pdrv_genirq ipmi_powernv 
ipmi_msghandler uio ibmpowernv powernv_rng vmx_crypto leds_powernv ses 
enclosure bnx2x vxlan ip6_udp_
tunnel udp_tunnel mdio libcrc32c ipr
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246500] CPU: 96 PID: 52779 Comm: 
qemu-system-ppc Not tainted 4.4.0-92-generic #115~14.04.1-Ubuntu
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246506] task: c01e228dcf60 ti: 
c01e229f4000 task.ti: c01e229f4000
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246511] NIP: d000189f85a0 LR: 
d000188a2584 CTR: d000189f84f0
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246516] REGS: c01e229f7840 TRAP: 
0f60   Not tainted  (4.4.0-92-generic)
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246519] MSR: 90009033 
  CR: 28022448  XER: 
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] CFAR: d000189f8534 SOFTE: 
1 
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR00: d000188a2584 
c01e229f7ac0 d00018a0c7f8 c01c4c68 
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR04: c01c5308 
c01e229f7bc0  0004 
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR08: 0001 
c01e228dcf60  d000188a7518 
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR12: d000189f84f0 
cfb79000 3fff7d74ed40 3fff7d74f3d0 
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR16: 3fff7cf5 
 0003 3fff7d750010 
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR20: 100c0570 
01000f6ebba0 0080 3fff85644330 
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR24:  
3fff7cf30028 d4f6d401 0010 
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR28:  
c01c4c68 c01c4c68 c01c5308 
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246594] NIP [d000189f85a0] 
kvmppc_vcpu_run_hv+0xb0/0x610 [kvm_hv]
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246606] LR [d000188a2584] 
kvmppc_vcpu_run+0x44/0x60 [kvm]
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246610] Call Trace:
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246617] [c01e229f7ac0] 
[c00ca294] recalc_sigpending+0x24/0x90 (unreliable)
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246630] [c01e229f7b70] 
[d000188a2584] kvmppc_vcpu_run+0x44/0x60 [kvm]
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246642] [c01e229f7ba0] 
[d0001889f274] kvm_arch_vcpu_ioctl_run+0x64/0x180 [kvm]
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246653] [c01e229f7be0] 
[d00018893898] kvm_vcpu_ioctl+0x5e8/0x7c0 [kvm]
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246661] [c01e229f7d40] 
[c02ef7d0] do_vfs_ioctl+0x4d0/0x7e0
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246667] [c01e229f7de0] 
[c02efbb4] SyS_ioctl+0xd4/0xf0
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246673] [c01e229f7e30] 
[c0009204] system_call+0x38/0xb4
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246677] Instruction dump:
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246681] e92d02a0 e9290a50 e9290108 
792807e3 41820058 e92d02a0 e9290a50 e9290108 
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246690] 792ae8a4 794a1f87 40820508 
e92d02a0 <7d4022a6> f9490ee8 e92d02a0 7d4122a6 
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246705] ---[ end trace 
df289857e3c4915a ]---

Installing kernel 4.4.0.83 and booting off it resolved issue.

Problem seems to be

[Kernel-packages] [Bug 1692538] Re: Ubuntu 16.04.02: ibmveth: Support to enable LSO/CSO for Trunk VEA

There is now a Xenial test kernel, which has a backport of commit
66aa0678efc2. The test kernels can be downloaded from:

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

Can you test these kernels and see if they resolve this bug?

Thanks in advance!

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

Title:
  Ubuntu 16.04.02: ibmveth: Support to enable LSO/CSO for Trunk VEA

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Fix Released

Bug description:
  == Comment: #0 - BRYANT G. LY  - 2017-05-22 08:40:16 ==
  ---Problem Description---

   - Issue 1: ibmveth doesn't support largesend and checksum offload features
 when configured as "Trunk". Driver has explicit checks to prevent
 enabling these offloads.

   - Issue 2: SYN packet drops seen at destination VM. When the packet
 originates, it has CHECKSUM_PARTIAL flag set and as it gets delivered to
 IO server's inbound Trunk ibmveth, on validating "checksum good" bits
 in ibmveth receive routine, SKB's ip_summed field is set with
 CHECKSUM_UNNECESSARY flag. This packet is then bridged by OVS (or Linux
 Bridge) and delivered to outbound Trunk ibmveth. At this point the
 outbound ibmveth transmit routine will not set "no checksum" and
 "checksum good" bits in transmit buffer descriptor, as it does so only
 when the ip_summed field is CHECKSUM_PARTIAL. When this packet gets
 delivered to destination VM, TCP layer receives the packet with checksum
 value of 0 and with no checksum related flags in ip_summed field. This
 leads to packet drops. So, TCP connections never goes through fine.

   - Issue 3: First packet of a TCP connection will be dropped, if there is
 no OVS flow cached in datapath. OVS while trying to identify the flow,
 computes the checksum. The computed checksum will be invalid at the
 receiving end, as ibmveth transmit routine zeroes out the pseudo
 checksum value in the packet. This leads to packet drop.

   - Issue 4: ibmveth driver doesn't have support for SKB's with frag_list.
 When Physical NIC has GRO enabled and when OVS bridges these packets,
 OVS vport send code will end up calling dev_queue_xmit, which in turn
 calls validate_xmit_skb.
 In validate_xmit_skb routine, the larger packets will get segmented into
 MSS sized segments, if SKB has a frag_list and if the driver to which
 they are delivered to doesn't support NETIF_F_FRAGLIST feature.
   
  Contact Information = Bryant G. Ly/b...@us.ibm.com 
   
  ---uname output---
  4.8.0-51.54
   
  Machine Type = p8 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Increases performance greatly

  The patch has been accepted upstream: 
  https://patchwork.ozlabs.org/patch/764533/

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

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

[Kernel-packages] [Bug 1701222] Re: [Hyper-V] LIS daemons fail to start after disable/re-enable VM integration services

I started a kernel bisect between Ubuntu 4.4.0-2 and Ubuntu 4.4.0-3. The
kernel bisect will require testing of about 7-10 test kernels.

I built the first test kernel, up to the following commit:
ef754413085f5ab7688989585f9223fec0ed7870

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

Can you test that kernel and report back if it has the bug or not?  I
will build the next test kernel based on your test results.

Thanks in advance

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

Title:
  [Hyper-V] LIS daemons fail to start after disable/re-enable VM
  integration services

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

Bug description:
  Issue description: Hyper-V daemons fail to start after disable/re-
  enable VM integration services.

  Platform: host independent
  Affected daemons - KVP, FCOPY and VSS.

  Distribution name and release: Ubuntu 16.04, Ubuntu 17.04
  Kernel version: 4.11.0-rc7-next-20170421 (for Ubuntu 16.04), 
4.10.0-19-generic (for Ubuntu 17.04)

  Repro rate: 100%

  Steps to reproduce:
  1.Start VM with Guest Services enabled (FCopy daemon starts automatically)
  2.Go to File > Settings > Integration Services, uncheck Guest Services 
and apply (FCopy daemon will stop at this point)
  3.Re-enable Guest Services from VM Settings (Fcopy daemon is not running).
  This is the issue. systemd monitors for the service and if we have the hook 
for the Guest Service, it tries to start the daemon again.
  systemd attempt to start any of the LIS daemons will fail, but manually 
executing the daemon binary, it will start the daemon.

  Additional Info:
  - the steps above can be repro'd with KVP / Data Exchange integration service 
as well.
  - Manually starting hv_fcopy_daemon works fine.
  - other distros (RHEL) does not have this behavior, the LIS daemons are 
started automatically by systemd once we re-enable the integration service.

  On the upstream kernel and the upstream hv daemons, these messages are 
recorded in syslog, once we re-enable the Guest service:
  HV_FCOPY: pread failed: Bad file descriptor
  systemd[1]: hv-fcopy-daemon.service: Main process exited, code=exited, 
status=1/FAILURE
  systemd[1]: hv-fcopy-daemon.service: Unit entered failed state.
  systemd[1]: hv-fcopy-daemon.service: Failed with result 'exit-code'.

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

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

[Kernel-packages] [Bug 1711951] Re: CPU fan goes full throttle triggered by waking up from suspend on Lenovo X1 Carbon (4th Gen., 2016)

I built a Zesty test kernel with commits 662591461 and 9c40f956.  The kernel 
can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1711951/

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

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

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

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

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

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

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

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

Title:
  CPU fan goes full throttle triggered by waking up from suspend on
  Lenovo X1 Carbon (4th Gen., 2016)

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

Bug description:
  This is a copy of a very similar bug report which is currently marked
  as triaged and where my comment is ignored maybe because of that.

  Please see my additional remarks at the end of this report.

  ---
  Thinkpad X1 Carbon 5th generation ultrabook with i7 Kabylake CPU running 
Ubuntu 17.04 has its fan go full steam if the laptop is woken up from 
sleep/suspend. Without any sleep/suspend the laptop's fan is basically "off" or 
silent, even for hours.

  The bug has been fixed upstream, see

  6625914 ACPI / EC: Drop EC noirq hooks to fix a regression
  9c40f95 Revert "ACPI / EC: Enable event freeze mode..." to fix a regression

  and/or https://bugzilla.kernel.org/show_bug.cgi?id=196129
  (with duplicate https://bugzilla.kernel.org/show_bug.cgi?id=191181)

  and I hope this fix will make its way into a near-future kernel update
  to ubuntu :)

  Many thanks!
  ---

  Source: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709616

  Additional remarks:

  - Like mentioned in https://bugzilla.kernel.org/show_bug.cgi?id=191181, the 
bug happens in other Lenovo models as well. It's not limited to the X1 Carbon 
5th Gen.
  - The bug was fixed in kernel 4.13 but not in 4.10. This means that users who 
run the HWE kernel on Ubuntu 16.04 LTS will have this problem too!

  I can reproduce it on my local system which has "linux-image-generic-
  hwe-16.04" installed (4.10.0.32.34).

  Reading through the comments, it's not exactly clear to me which of
  the commits has fixed this problem, but I guess that the following two
  changes have made the difference:

  https://patchwork.kernel.org/patch/9835823/
  https://patchwork.kernel.org/patch/9835825/

  I am reporting this as a new issue because the fixes from 4.13 need to
  be backported to 4.10 for users of the Ubuntu 16.04 HWE kernel.

  Many thanks!

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

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

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

--- Comment From rosat...@br.ibm.com 2017-08-23 14:07 EDT---
The patch was applied to zesty/master-next -> 
http://kernel.ubuntu.com/git/ubuntu/ubuntu-zesty.git/commit/?h=master-next=e899988c4387b827897d7214493856b2b853baa9

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

Title:
  Avoid spurious PMU interrupts after idle

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  Hello Canonical,

  For POWER9 enablement, we need to backport the following commit ID up
  to Zesty.

  101dd590a7fa ("powerpc/perf: Avoid spurious PMU interrupts after
  idle")

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

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

[Kernel-packages] [Bug 1709179] Re: Drop GPL from of_node_to_nid() export to match other arches

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

** Changed in: linux (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
Canonical Kernel Team (canonical-kernel-team)

** Tags added: triage-a

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

Title:
  Drop GPL from of_node_to_nid() export to match other arches

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

Bug description:
  == Comment: #0 - Reza A. Arbab  - 2017-08-07 15:34:04 ==
  We need to backport mainline commit be9ba9ff93cc ("Drop GPL from 
of_node_to_nid() export to match other arches") to the Ubuntu 4.10 kernel.

  This exposes functionality needed by the Nvidia device driver on
  POWER9.

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

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

[Kernel-packages] [Bug 1709179] Re: Drop GPL from of_node_to_nid() export to match other arches

2017-08-23 Thread Andrew Cloke

Apologies for the delay. This bug somehow missed our initial handling
process. I've now assigned to the kernel team.

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

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

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

Title:
  Drop GPL from of_node_to_nid() export to match other arches

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

Bug description:
  == Comment: #0 - Reza A. Arbab  - 2017-08-07 15:34:04 ==
  We need to backport mainline commit be9ba9ff93cc ("Drop GPL from 
of_node_to_nid() export to match other arches") to the Ubuntu 4.10 kernel.

  This exposes functionality needed by the Nvidia device driver on
  POWER9.

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

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

[Kernel-packages] [Bug 1701222] Re: [Hyper-V] LIS daemons fail to start after disable/re-enable VM integration services

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

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

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

Title:
  [Hyper-V] LIS daemons fail to start after disable/re-enable VM
  integration services

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

Bug description:
  Issue description: Hyper-V daemons fail to start after disable/re-
  enable VM integration services.

  Platform: host independent
  Affected daemons - KVP, FCOPY and VSS.

  Distribution name and release: Ubuntu 16.04, Ubuntu 17.04
  Kernel version: 4.11.0-rc7-next-20170421 (for Ubuntu 16.04), 
4.10.0-19-generic (for Ubuntu 17.04)

  Repro rate: 100%

  Steps to reproduce:
  1.Start VM with Guest Services enabled (FCopy daemon starts automatically)
  2.Go to File > Settings > Integration Services, uncheck Guest Services 
and apply (FCopy daemon will stop at this point)
  3.Re-enable Guest Services from VM Settings (Fcopy daemon is not running).
  This is the issue. systemd monitors for the service and if we have the hook 
for the Guest Service, it tries to start the daemon again.
  systemd attempt to start any of the LIS daemons will fail, but manually 
executing the daemon binary, it will start the daemon.

  Additional Info:
  - the steps above can be repro'd with KVP / Data Exchange integration service 
as well.
  - Manually starting hv_fcopy_daemon works fine.
  - other distros (RHEL) does not have this behavior, the LIS daemons are 
started automatically by systemd once we re-enable the integration service.

  On the upstream kernel and the upstream hv daemons, these messages are 
recorded in syslog, once we re-enable the Guest service:
  HV_FCOPY: pread failed: Bad file descriptor
  systemd[1]: hv-fcopy-daemon.service: Main process exited, code=exited, 
status=1/FAILURE
  systemd[1]: hv-fcopy-daemon.service: Unit entered failed state.
  systemd[1]: hv-fcopy-daemon.service: Failed with result 'exit-code'.

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

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

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

--- Comment From ar...@us.ibm.com 2017-08-23 13:03 EDT---
Ping! Could someone have a look at this?

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

Title:
  Drop GPL from of_node_to_nid() export to match other arches

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Reza A. Arbab  - 2017-08-07 15:34:04 ==
  We need to backport mainline commit be9ba9ff93cc ("Drop GPL from 
of_node_to_nid() export to match other arches") to the Ubuntu 4.10 kernel.

  This exposes functionality needed by the Nvidia device driver on
  POWER9.

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

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

[Kernel-packages] [Bug 1690174] Re: [Hyper-V] hv_netvsc: Exclude non-TCP port numbers from vRSS hashing

2017-08-23 Thread Marcelo Cerri

** Tags removed: verification-needed-xenial verification-needed-zesty
** Tags added: verification-done-xenial verification-done-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/1690174

Title:
  [Hyper-V] hv_netvsc: Exclude non-TCP port numbers from vRSS hashing

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux-azure source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Won't Fix
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Fix Released

Bug description:
  Azure hosts are not supporting non-TCP port numbers in vRSS hashing for
  now. For example, UDP packet loss rate will be high if port numbers are
  also included in vRSS hash.

  So, we created this patch to use only IP numbers for hashing in non-TCP
  traffic.

  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/?id=f72860afa2e32cdc674cbdd7f354f8fb62e908a6

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

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

[Kernel-packages] [Bug 1709300] Re: linux-aws: 4.4.0-1032.41 -proposed tracker

2017-08-23 Thread Steve Beattie

** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

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

Title:
  linux-aws: 4.4.0-1032.41 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1709296
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

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

--- Comment From dougm...@us.ibm.com 2017-08-23 12:13 EDT---
By the way, I would not classify this behavior I'm seeing as a performance 
issue. There are hundreds of I/Os per second on each disk, and most of them are 
being submitted right away. But a subset of those I/Os are getting delayed for 
10 minutes - if not over an hour - which is a huge disparity. The effect this 
can have on applications could be significant, if not critical. Some of the 
I/Os are taking at least 3 orders of magnitude longer than the rest. And since 
no timeouts are in place at this stage, I wonder if any other test frameworks 
even notice it. You could be hitting this in your test cases but are not aware. 
Consider what would happen in a database server if the rollback segment I/Os 
were getting delayed like this.

Some things to think about.

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

Title:
  Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to
  adapter for a very long time.

Status in Linux:
  Unknown
Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  ---Problem Description---
  When running stress test, sometimes seeing IO hung in dmesg or seeing "Host 
adapter abort request" error.

  ---Steps to Reproduce---
   There are two ways to re-create the issues:
  (1)running HTX, you will see IO timeout backtrace in dmesg in several hours
  (2)running some IO test, then reboot system, repeat this two steps, it takes 
long time to re-create the issue.
   
  ---uname output---
  4.10.0-11-generic

  The bulk of the effort for this issue is currently being worked in
  MicroSemi's JIRA https://jira.pmcs.com/browse/ESDIBMOP-133.

  Ran an interesting test: Ran HTX until I started getting the "stall"
  messages on the console, then shutdown HTX and examined the I/O
  counters for the tested disks in sysfs:

  root@bostonp15:~# for i in 
/sys/devices/pci0003:00/0003:00:00.0/0003:01:00.0/host0/target0:2:[2345]/0:2:[2345]:0;
 do echo ${i##*/} $(<${i}/iorequest_cnt) $(<${i}/iodone_cnt); done
  0:2:2:0 0x5eba3d 0x5eba3d
  0:2:3:0 0x773cc9 0x773cc9
  0:2:4:0 0x782c61 0x782c61
  0:2:5:0 0x5ca134 0x5ca134
  root@bostonp15:~#

  So, none of the disks showed any evidence of having lost an I/O. I
  then restarted HTX and aside from having to manually restart one of
  the disks, see no problems with the testing. It appears that what was
  "hung" was purely in userland.

  This does not absolve the kernel or aacraid driver from blame, but it
  shows that the OS "believes" that it completed the I/O and thus
  removed it from the queue. What we don't know is whether the OS truly
  notified HTX about the completion, or if HTX (or userland libraries)
  just failed to process the notification.

  Tests are running again, will see what happens next.

  Update from JIRA:

  I have run some more experiments. Not sure what it tells us, but
  here's what I've seen.

  First test, ran until I got kernel messages about stalled tasks, then
  shutdown HTX. After HTX was down, I checked the above mentioned
  counters and found that on each disk iorequest_cnt matched iodone_cnt.
  The disks were usable and I could restart HTX. This suggests that the
  problem is not in the PM8069 firmware, and makes the case for the
  aacraid driver having a bug somewhat weaker. However, this merely says
  that the driver "completed" the I/O as far as the kernel is concerned,
  not that a completion rippled back to the application.

  I restarted HTX and have run until errors. This time, I am leaving HTX
  running and observing. Two of the disks reached the HTX error
  threshold and the testers stopped (those 2 disks are now idle).
  Another disks saw errors but then stopped and appears to be running
  fine now. The last disk has not seen any errors (yet). On the two idle
  (errored-out) disks I see  iorequest_cnt matches iodone_cnt. I am able
  to "terminate and restart" the two idle disks and HTX appears to be
  testing them again "normally". Note that no reboot was required,
  further supporting the evidence that, as far as the kernel is
  concerned, there is nothing wrong with the disks and their I/O paths.

  So, I don't believe this completely eliminates aacraid from the
  picture, especially given we don't see this behavior on other
  systems/drivers. But, it probably moves the focus of the investigation
  away form the adapter firmware.

  Tried build upstream 4.11 kernel on Ubuntu. This still gets the hangs.
  Both Ubuntu 4.10 and upstream 4.11 have aacraid driver
  1.2.1[50792]-custom.

  Good new/bad news... While doing an initial evaluation of the LSI-3008
  SAS HBA on Boston and Ubuntu 17.04, I am hitting this same problem.
  So, it appears to have nothing specific to do with the PM8069 or

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

--- Comment From jhop...@us.ibm.com 2017-08-23 12:05 EDT---
(In reply to comment #4)
> I built a Zesty test kernel with a revert of commit 809ecb9bca.  The test
> kernel can be downloaded from:
>
> http://kernel.ubuntu.com/~jsalisbury/lp1711251
>
> Can you test this kernel and see if it resolves this bug?
>
> Thanks in advance!

Thanks! I ran multiple rounds of VMtoVM network stress tests using this
host kernel and found no issues, it resolves the network drop issue.

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

Title:
  vhost guest network randomly drops under stress (kvm)

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress

Bug description:
  ---Problem Description---
  A vhost performance patch was introduced in the 4.10 kernel upstream, and is 
currently included in the Zesty 4.10 kernel:

  commit 809ecb9bca6a9424ccd392d67e368160f8b76c92
  Author: Jason Wang 
  Date:   Mon Dec 12 14:46:49 2016 +0800

  vhost: cache used event for better performance

  --

  However I recently hit a functional issue linked to this patch which
  would cause random guests to lose their network connection under
  stress.  This is not architecture specific and more likely to be hit
  with high network stress (i.e. lots of uperf instances).

  The patch author has now reverted this patch upstream:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/vhost?id=8d65843c44269c21e95c98090d9bb4848d473853

  which reads:
  " 
  Revert "vhost: cache used event for better performance"
  This reverts commit 809ecb9bca6a9424ccd392d67e368160f8b76c92. Since it
  was reported to break vhost_net. We want to cache used event and use
  it to check for notification. The assumption was that guest won't move
  the event idx back, but this could happen in fact when 16 bit index
  wraps around after 64K entries.

  Signed-off-by: Jason Wang 
  Acked-by: Michael S. Tsirkin 
  Signed-off-by: David S. Miller 
  "

  I am requesting this patch to revert the problematic one be pulled into 
Ubuntu Zesty (anything 4.10+).
   
  ---uname output---
  Linux p82qvirt 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:19 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8247-22L 
   
  ---Steps to Reproduce---
   I can recreate the scenario with the following setup:
   - on a 20core host, start 20 1core VMs
   - I have a single linux bridge assigned to all guests using virtio
   - start a uperf benchmark between each guest pair (10 total) using a high 
number of uperf nprocs (32)

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

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

[Kernel-packages] [Bug 1709749] Re: Docker hangs with xfs using aufs storage driver

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

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

Title:
  Docker hangs with xfs using aufs storage driver

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

Bug description:
  SRU Justification

  Impact: Running the yum command in a Centos/RHEL container causes the
  process to hang enter uninterruptible sleep mode if /var/lib/docker is
  hosted on an XFS filesystem while the AUFS storage driver is used.

  Fix: Commit e34c81ff96415c64ca827ec30e7935454d26c1d3 from upstream
  aufs-standalone. Requires prerequisite commit
  b4d3dcc92a13d53952fe6e9a640201ef87475302.

  Test Case: Test scenario described above. Kernel with fixes applied
  has been confirmed by reporter to fix the issue.

  Regression Potential: Both patches have been in upstream aufs-
  standalone for a while now and included in the artful kernel as well
  as currently being included in the upstream branch for 4.10. Therefore
  they are well tested and unlikely to cause regressions.

  ---

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Ubuntu 16.04 and 17.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  kernel 4.10.0-28-generic

  3) What you expected to happen

  Docker with AUFS on XFS works.

  4) What happened instead

  It hangs up

  ---

  As reported in https://github.com/moby/moby/issues/34361 , AUFS on XFS
  needs this fix for kernel 4.10:
  
https://github.com/sfjro/aufs4-standalone/commit/e34c81ff96415c64ca827ec30e7935454d26c1d3

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

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

[Kernel-packages] [Bug 1711182] Re: ACPI ID for Hip07/08 I2C controller has typo

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

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

Title:
  ACPI ID for Hip07/08 I2C controller has typo

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

Bug description:
  [Impact]
  Due to a typo in the upstream fix for LP: #1708293, the i2c driver still does 
not recognize the ACPI IDs for the i2c devices on the Hip07/08 platforms, 
making these devices unusable.

  [Test Case]
ls -l /sys/class/i2c-dev/*/device/firmware_node | grep HISI

  [Regression Risk]
  This adds an ID/config for previously unsupported ACPI IDs.

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

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

[Kernel-packages] [Bug 1709352] Re: Avoid spurious PMU interrupts after idle

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

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

Title:
  Avoid spurious PMU interrupts after idle

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  Hello Canonical,

  For POWER9 enablement, we need to backport the following commit ID up
  to Zesty.

  101dd590a7fa ("powerpc/perf: Avoid spurious PMU interrupts after
  idle")

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

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

[Kernel-packages] [Bug 1709073] Re: [SRU][ZESTY]kernel BUG at /build/linux-H5UzH8/linux-4.10.0/drivers/nvme/host/pci.c:567!

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

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

Title:
  [SRU][ZESTY]kernel BUG at /build/linux-
  H5UzH8/linux-4.10.0/drivers/nvme/host/pci.c:567!

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  SRU Justification:

  Impact: reliably reproducible kernel BUG_ON leading to complete system hang
  Fix: cherry-pick upstream followup commit
  Testcase: mkfs.btrfs on Samsung SM/PM961 no longer triggers the BUG_ON

  Detailed description:

  the fix for http://bugs.launchpad.net/bugs/1657539 which cherry-picked

  729204ef49ec00b788ce23deb9eb922a5769f55d block: relax check on sg gap

  is missing a follow-up fix commit

  5a8d75a1b8c99bdc926ba69b7b7dbe4fae81a5af block: fix bio_will_gap() for
  first bvec with offset

  without, the following BUG_ON is triggered using a mkfs.btrfs
  /dev/nvme0n1 on a Samsung SM961/PM961 M.2 device:

  Aug 07 09:19:09 ubuntu kernel: kernel BUG at 
/build/linux-H5UzH8/linux-4.10.0/drivers/nvme/host/pci.c:567!
  Aug 07 09:19:09 ubuntu kernel: invalid opcode:  [#1] SMP
  Aug 07 09:19:09 ubuntu kernel: Modules linked in: nls_iso8859_1 ppdev 
snd_hda_intel snd_hda_codec snd_hda_core joydev snd_hwdep snd_pcm snd_ti
  Aug 07 09:19:09 ubuntu kernel: CPU: 0 PID: 2071 Comm: mkfs.btrfs Not tainted 
4.10.0-30-generic #34-Ubuntu
  Aug 07 09:19:09 ubuntu kernel: Hardware name: QEMU Standard PC (Q35 + ICH9, 
2009), BIOS 0.0.0 02/06/2015
  Aug 07 09:19:09 ubuntu kernel: task: 8e537417bfc0 task.stack: 
b580c1698000
  Aug 07 09:19:09 ubuntu kernel: RIP: 0010:nvme_queue_rq+0x746/0x8e0 [nvme]
  Aug 07 09:19:09 ubuntu kernel: RSP: 0018:b580c169b950 EFLAGS: 00010286
  Aug 07 09:19:09 ubuntu kernel: RAX: 0078 RBX: fa00 
RCX: 1000
  Aug 07 09:19:09 ubuntu kernel: RDX: 0010 RSI: 0200 
RDI: 0246
  Aug 07 09:19:09 ubuntu kernel: RBP: b580c169ba28 R08: 8e53733cb000 
R09: fa00
  Aug 07 09:19:09 ubuntu kernel: R10: 1000 R11: 8e53733d 
R12: 000273a8a000
  Aug 07 09:19:09 ubuntu kernel: R13: 0002fc00 R14: 8e53733cb000 
R15: 0200
  Aug 07 09:19:09 ubuntu kernel: FS:  7f92511ba080() 
GS:8e537fc0() knlGS:
  Aug 07 09:19:09 ubuntu kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Aug 07 09:19:09 ubuntu kernel: CR2: 7ffeecdc9000 CR3: 000274323000 
CR4: 06f0
  Aug 07 09:19:09 ubuntu kernel: DR0:  DR1:  
DR2: 
  Aug 07 09:19:09 ubuntu kernel: DR3:  DR6: fffe0ff0 
DR7: 0400
  Aug 07 09:19:09 ubuntu kernel: Call Trace:
  Aug 07 09:19:09 ubuntu kernel:  blk_mq_try_issue_directly+0x7e/0x100
  Aug 07 09:19:09 ubuntu kernel:  blk_mq_make_request+0x3cf/0x4e0
  Aug 07 09:19:09 ubuntu kernel:  generic_make_request+0x110/0x2d0
  Aug 07 09:19:09 ubuntu kernel:  submit_bio+0x73/0x150
  Aug 07 09:19:09 ubuntu kernel:  ? __percpu_counter_add+0x4f/0x60
  Aug 07 09:19:09 ubuntu kernel:  submit_bh_wbc+0x152/0x180
  Aug 07 09:19:09 ubuntu kernel:  __block_write_full_page+0x176/0x360
  Aug 07 09:19:09 ubuntu kernel:  ? I_BDEV+0x20/0x20
  Aug 07 09:19:09 ubuntu kernel:  ? I_BDEV+0x20/0x20
  Aug 07 09:19:09 ubuntu kernel:  block_write_full_page+0x13b/0x160
  Aug 07 09:19:09 ubuntu kernel:  blkdev_writepage+0x18/0x20
  Aug 07 09:19:09 ubuntu kernel:  __writepage+0x13/0x30
  Aug 07 09:19:09 ubuntu kernel:  write_cache_pages+0x205/0x530
  Aug 07 09:19:09 ubuntu kernel:  ? wb_position_ratio+0x1f0/0x1f0
  Aug 07 09:19:09 ubuntu kernel:  generic_writepages+0x56/0x90
  Aug 07 09:19:09 ubuntu kernel:  blkdev_writepages+0x2f/0x40
  Aug 07 09:19:09 ubuntu kernel:  do_writepages+0x1e/0x30
  Aug 07 09:19:09 ubuntu kernel:  __filemap_fdatawrite_range+0xc6/0x100
  Aug 07 09:19:09 ubuntu kernel:  SyS_fadvise64+0x25e/0x290
  Aug 07 09:19:09 ubuntu kernel:  entry_SYSCALL_64_fastpath+0x1e/0xad
  Aug 07 09:19:09 ubuntu kernel: RIP: 0033:0x7f925066debd
  Aug 07 09:19:09 ubuntu kernel: RSP: 002b:7ffeecd46a38 EFLAGS: 0246 
ORIG_RAX: 00dd
  Aug 07 09:19:09 ubuntu kernel: RAX: ffda RBX: 7ffeecd45a30 
RCX: 7f925066debd
  Aug 07 09:19:09 ubuntu kernel: RDX:  RSI:  
RDI: 0004
  Aug 07 09:19:09 ubuntu kernel: RBP:  R08:  
R09: 1001
  Aug 07 09:19:09 ubuntu kernel: R10: 0004 R11: 0246 
R12: 0010
  Aug 07 09:19:09 ubuntu kernel: R13: 7ffeecd45a40 R14: 0004 
R15: 
  Aug 07 09:19:09 ubuntu kernel: Code: f1 61 26 d5 8b 95 48 ff ff ff 48 89 85 
60 ff ff ff 4c 8b 50 10 44 8b 48 18 8b 8d 50 ff ff ff 44 8b 9d 58
  Aug 07

[Kernel-packages] [Bug 1709073] Re: [SRU][ZESTY]kernel BUG at /build/linux-H5UzH8/linux-4.10.0/drivers/nvme/host/pci.c:567!

2017-08-23 Thread Seth Forshee

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

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

Title:
  [SRU][ZESTY]kernel BUG at /build/linux-
  H5UzH8/linux-4.10.0/drivers/nvme/host/pci.c:567!

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  SRU Justification:

  Impact: reliably reproducible kernel BUG_ON leading to complete system hang
  Fix: cherry-pick upstream followup commit
  Testcase: mkfs.btrfs on Samsung SM/PM961 no longer triggers the BUG_ON

  Detailed description:

  the fix for http://bugs.launchpad.net/bugs/1657539 which cherry-picked

  729204ef49ec00b788ce23deb9eb922a5769f55d block: relax check on sg gap

  is missing a follow-up fix commit

  5a8d75a1b8c99bdc926ba69b7b7dbe4fae81a5af block: fix bio_will_gap() for
  first bvec with offset

  without, the following BUG_ON is triggered using a mkfs.btrfs
  /dev/nvme0n1 on a Samsung SM961/PM961 M.2 device:

  Aug 07 09:19:09 ubuntu kernel: kernel BUG at 
/build/linux-H5UzH8/linux-4.10.0/drivers/nvme/host/pci.c:567!
  Aug 07 09:19:09 ubuntu kernel: invalid opcode:  [#1] SMP
  Aug 07 09:19:09 ubuntu kernel: Modules linked in: nls_iso8859_1 ppdev 
snd_hda_intel snd_hda_codec snd_hda_core joydev snd_hwdep snd_pcm snd_ti
  Aug 07 09:19:09 ubuntu kernel: CPU: 0 PID: 2071 Comm: mkfs.btrfs Not tainted 
4.10.0-30-generic #34-Ubuntu
  Aug 07 09:19:09 ubuntu kernel: Hardware name: QEMU Standard PC (Q35 + ICH9, 
2009), BIOS 0.0.0 02/06/2015
  Aug 07 09:19:09 ubuntu kernel: task: 8e537417bfc0 task.stack: 
b580c1698000
  Aug 07 09:19:09 ubuntu kernel: RIP: 0010:nvme_queue_rq+0x746/0x8e0 [nvme]
  Aug 07 09:19:09 ubuntu kernel: RSP: 0018:b580c169b950 EFLAGS: 00010286
  Aug 07 09:19:09 ubuntu kernel: RAX: 0078 RBX: fa00 
RCX: 1000
  Aug 07 09:19:09 ubuntu kernel: RDX: 0010 RSI: 0200 
RDI: 0246
  Aug 07 09:19:09 ubuntu kernel: RBP: b580c169ba28 R08: 8e53733cb000 
R09: fa00
  Aug 07 09:19:09 ubuntu kernel: R10: 1000 R11: 8e53733d 
R12: 000273a8a000
  Aug 07 09:19:09 ubuntu kernel: R13: 0002fc00 R14: 8e53733cb000 
R15: 0200
  Aug 07 09:19:09 ubuntu kernel: FS:  7f92511ba080() 
GS:8e537fc0() knlGS:
  Aug 07 09:19:09 ubuntu kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Aug 07 09:19:09 ubuntu kernel: CR2: 7ffeecdc9000 CR3: 000274323000 
CR4: 06f0
  Aug 07 09:19:09 ubuntu kernel: DR0:  DR1:  
DR2: 
  Aug 07 09:19:09 ubuntu kernel: DR3:  DR6: fffe0ff0 
DR7: 0400
  Aug 07 09:19:09 ubuntu kernel: Call Trace:
  Aug 07 09:19:09 ubuntu kernel:  blk_mq_try_issue_directly+0x7e/0x100
  Aug 07 09:19:09 ubuntu kernel:  blk_mq_make_request+0x3cf/0x4e0
  Aug 07 09:19:09 ubuntu kernel:  generic_make_request+0x110/0x2d0
  Aug 07 09:19:09 ubuntu kernel:  submit_bio+0x73/0x150
  Aug 07 09:19:09 ubuntu kernel:  ? __percpu_counter_add+0x4f/0x60
  Aug 07 09:19:09 ubuntu kernel:  submit_bh_wbc+0x152/0x180
  Aug 07 09:19:09 ubuntu kernel:  __block_write_full_page+0x176/0x360
  Aug 07 09:19:09 ubuntu kernel:  ? I_BDEV+0x20/0x20
  Aug 07 09:19:09 ubuntu kernel:  ? I_BDEV+0x20/0x20
  Aug 07 09:19:09 ubuntu kernel:  block_write_full_page+0x13b/0x160
  Aug 07 09:19:09 ubuntu kernel:  blkdev_writepage+0x18/0x20
  Aug 07 09:19:09 ubuntu kernel:  __writepage+0x13/0x30
  Aug 07 09:19:09 ubuntu kernel:  write_cache_pages+0x205/0x530
  Aug 07 09:19:09 ubuntu kernel:  ? wb_position_ratio+0x1f0/0x1f0
  Aug 07 09:19:09 ubuntu kernel:  generic_writepages+0x56/0x90
  Aug 07 09:19:09 ubuntu kernel:  blkdev_writepages+0x2f/0x40
  Aug 07 09:19:09 ubuntu kernel:  do_writepages+0x1e/0x30
  Aug 07 09:19:09 ubuntu kernel:  __filemap_fdatawrite_range+0xc6/0x100
  Aug 07 09:19:09 ubuntu kernel:  SyS_fadvise64+0x25e/0x290
  Aug 07 09:19:09 ubuntu kernel:  entry_SYSCALL_64_fastpath+0x1e/0xad
  Aug 07 09:19:09 ubuntu kernel: RIP: 0033:0x7f925066debd
  Aug 07 09:19:09 ubuntu kernel: RSP: 002b:7ffeecd46a38 EFLAGS: 0246 
ORIG_RAX: 00dd
  Aug 07 09:19:09 ubuntu kernel: RAX: ffda RBX: 7ffeecd45a30 
RCX: 7f925066debd
  Aug 07 09:19:09 ubuntu kernel: RDX:  RSI:  
RDI: 0004
  Aug 07 09:19:09 ubuntu kernel: RBP:  R08:  
R09: 1001
  Aug 07 09:19:09 ubuntu kernel: R10: 0004 R11: 0246 
R12: 0010
  Aug 07 09:19:09 ubuntu kernel: R13: 7ffeecd45a40 R14: 0004 
R15: 
  Aug 07 09:19:09 ubuntu kernel: Code: f1 61 26 d5 8b 95 48 ff ff ff 48 89 85 
60 ff ff ff 4c 8b 50 10 44 8b 48 18 8b 8d 50 ff ff ff 44 8b 9d

[Kernel-packages] [Bug 1680513] Re: Migrating KSM page causes the VM lock up as the KSM page merging list is too large

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

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

Title:
  Migrating KSM page causes the VM lock up as the KSM page merging list
  is too large

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

Bug description:
  [Impact]
  After numad is enabled and there are several VMs running on the same
  host machine(host kernel version: 4.4.0-72-generic #93), the
  softlockup messages can be observed inside the VMs' dmesg.

  First, the crashdump was captured when the symptom was observed. At
  the first glance, it looks like an IPI lost issue. The numad process
  initiates a migration of memory, and as part of this, needs to flush
  the TLB cache of another CPU. When the crash dump was taken, that
  other CPU has the TLB flush pending, but not executed. 

  The numad kernel task is holding a semaphore lock mmap_sem(for the
  VM's memory) to do the migration, and the tasks that actually end up
  being blocked are other virtual CPUs for the same VM. These tasks need
  to access or make changes to the memory map for the VM because of the
  VM page fault, but cannot acquire the semaphore lock.

  However, the original thoughts on the root cause (unhandled IPI or csd
  lock issue) are incorrect.

  We originally suspected an issue with a lost IPI (inter processor
  interrupt) that performs remote CPU cache flushes during page
  migration, or a known issue with the "csd" lock used to synchronize
  the remote CPU cache flush.  A lost IPI would be a function of the
  system firmware or chipset (it is not a CPU issue), but the known csd
  issue is hardware independent. 

  Gavin created the hotfix kernel with changes in the csd_lock_wait
  function that would time out if the unlock never happens (the end
  result of either cause), and print messages to the console when that
  timeout occurred. The messages look like: 

  csd_lock_wait called %d times

  csd: Detected non-responsive CSD lock (#%d) on CPU#%02d, waiting
  %Ld.%03Ld secs for CPU#%02d

  However, the VMs are still experiencing the hangs, but the
  csd_lock_wait timeout is not happening. This suggests that the csd
  lock / lost IPI is not the actual cause.

  In the crash dump, the numad task has induced a migration, and the
  stack is as follows: 

  #1 [885f8fb4fb78] smp_call_function_many 
  #2 [885f8fb4fbc0] native_flush_tlb_others 
  #3 [885f8fb4fc08] flush_tlb_page 
  #4 [885f8fb4fc30] ptep_clear_flush 
  #5 [885f8fb4fc60] try_to_unmap_one 
  #6 [885f8fb4fcd0] rmap_walk_ksm 
  #7 [885f8fb4fd28] rmap_walk 
  #8 [885f8fb4fd80] try_to_unmap 
  #9 [885f8fb4fdc8] migrate_pages 
  #10 [885f8fb4fe80] do_migrate_pages 

  
  The frame #1 is actually in the csd_lock_wait function mentioned
  above, but the compiler has optimized that call and it does not appear
  in the stack. 

  What happens here is that do_migrate_pages (frame #10) acquires the
  semaphore that everything else is waiting for (and that eventually
  produce the hang warnings), and it holds that semaphore for the
  duration of the page migration.  This strongly suggests that this
  single do_migrate_pages call is taking in excess of 10 seconds, and if
  the csd lock is not stuck, then something else within its call path is
  not functioning correctly. 

  We originally suspected that the lost IPI/csd lock hang was
  responsible for the hung task timeouts, but in the absence of the csd
  warning messages, the cause presumably lies elsewhere. 

  A KSM function appears in frame #6; this is the function that will
  search out the merged pages to handle them for the migration. 

  Gavin have tried to disassemble the code and finally find the 
  stable_node->hlist is as long as 2306920 entries:

  rmap_item list(stable_node->hlist): 
  stable_node: 0x881f836ba000 stable_node->hlist->first = 
0x883f3e5746b0 

  struct hlist_head { 
  [0] struct hlist_node *first; 
  } 
  struct hlist_node { 
  [0] struct hlist_node *next; 
  [8] struct hlist_node **pprev; 
  } 

  crash> list hlist_node.next 0x883f3e5746b0 > rmap_item.lst

  $ wc -l rmap_item.lst 
  2306920 rmap_item.lst

  This is roughly 9 GB of pages. The theory is that KSM has merged a
  very large number of pages that are empty (the value of all locations
  in the page are zero).

  The bug can be observed by the perf flame graph[1]:

  [1]. http://kernel.ubuntu.com/~gavinguo/sf00131845/numa-131845.svg

  [Fix]
  Andrea Arcangeli already sent out the patch[2] in the 2015/11/10.
  Andrew Morton also said he will apply the patch. However, the patch
  finally disappears from the mmtom tree in April 2016. Andrea suggested
  apply the 3 patches[3].

  [2]. [PATCH 1/1] ksm: introduce ksm_max_page_sharing

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

--- Comment From pac...@us.ibm.com 2017-08-23 10:15 EDT---
(In reply to comment #7)
> Any chance we could pull in this patch as well:
>
> https://lists.ozlabs.org/pipermail/linuxppc-dev/2017-August/161412.html
>
> It's recent enough that it has not made it to mainline, but it's
> ppc64le-specific.

ping.  Can we pull the above patch in as well, or shall I open a new
request?

The commit is now in the linux "tip" tree:
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/tools/perf/scripts/python/Perf-Trace-Util/lib/Perf/Trace/Util.py?id=6fae8663c9940bcaa9edd8e21a9ae0f562789a3d

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

Title:
  include support for Python bindings in "perf"

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

Bug description:
  == Comment: #0 - Paul A. Clarke  - 2017-07-26 09:59:57 ==
  ---Problem Description---
  Request to build python bindings support with perf.

  ---Steps to Reproduce---
   Ubuntu-17.04# perf script -g python
  Python scripting not supported.  Install libpython and rebuild perf to enable 
it.
  For example:
# apt-get install python-dev (ubuntu)
# yum install python-devel (Fedora)
etc.
   
  Userspace tool common name: perf 
   
  Userspace rpm: linux-tools-common 

  Userspace tool obtained from project website:  na

  == Comment: #2 - MAMATHA INAMDAR  - 2017-08-01 05:02:34 
==
  After installing libpython, downloaded ubuntu 17.04 linux source code and 
compiled perf tool then it works fine.

  # ./perf script  -g python 
  generated Python script: perf-script.py

  but when I run perf tool without rebuilding after installing libpython
  it shows an error

  # perf script  -g python 
  Python scripting not supported.  Install libpython and rebuild perf to enable 
it.
  For example:
# apt-get install python-dev (ubuntu)
# yum install python-devel (Fedora)
etc.
  root@p8wookie:/home/Mamatha/ubuntu/ubuntu-zesty/tools/perf# perf --version
  perf version 4.10.17

  == Comment: #3 - MAMATHA INAMDAR  - 2017-08-01 05:03:44 
==
  Request to build python bindings support with perf.

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

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

[Kernel-packages] [Bug 1709889] Re: Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to adapter for a very long time.

2017-08-23 Thread Colin Ian King

Thanks for also testing with the latest upstream kernel and reporting it
to the upstream developers. I've added the link to the bug so we pull in
bug updates automatically from the bugzilla.

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

Title:
  Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to
  adapter for a very long time.

Status in Linux:
  Unknown
Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  ---Problem Description---
  When running stress test, sometimes seeing IO hung in dmesg or seeing "Host 
adapter abort request" error.

  ---Steps to Reproduce---
   There are two ways to re-create the issues:
  (1)running HTX, you will see IO timeout backtrace in dmesg in several hours
  (2)running some IO test, then reboot system, repeat this two steps, it takes 
long time to re-create the issue.
   
  ---uname output---
  4.10.0-11-generic

  The bulk of the effort for this issue is currently being worked in
  MicroSemi's JIRA https://jira.pmcs.com/browse/ESDIBMOP-133.

  Ran an interesting test: Ran HTX until I started getting the "stall"
  messages on the console, then shutdown HTX and examined the I/O
  counters for the tested disks in sysfs:

  root@bostonp15:~# for i in 
/sys/devices/pci0003:00/0003:00:00.0/0003:01:00.0/host0/target0:2:[2345]/0:2:[2345]:0;
 do echo ${i##*/} $(<${i}/iorequest_cnt) $(<${i}/iodone_cnt); done
  0:2:2:0 0x5eba3d 0x5eba3d
  0:2:3:0 0x773cc9 0x773cc9
  0:2:4:0 0x782c61 0x782c61
  0:2:5:0 0x5ca134 0x5ca134
  root@bostonp15:~#

  So, none of the disks showed any evidence of having lost an I/O. I
  then restarted HTX and aside from having to manually restart one of
  the disks, see no problems with the testing. It appears that what was
  "hung" was purely in userland.

  This does not absolve the kernel or aacraid driver from blame, but it
  shows that the OS "believes" that it completed the I/O and thus
  removed it from the queue. What we don't know is whether the OS truly
  notified HTX about the completion, or if HTX (or userland libraries)
  just failed to process the notification.

  Tests are running again, will see what happens next.

  Update from JIRA:

  I have run some more experiments. Not sure what it tells us, but
  here's what I've seen.

  First test, ran until I got kernel messages about stalled tasks, then
  shutdown HTX. After HTX was down, I checked the above mentioned
  counters and found that on each disk iorequest_cnt matched iodone_cnt.
  The disks were usable and I could restart HTX. This suggests that the
  problem is not in the PM8069 firmware, and makes the case for the
  aacraid driver having a bug somewhat weaker. However, this merely says
  that the driver "completed" the I/O as far as the kernel is concerned,
  not that a completion rippled back to the application.

  I restarted HTX and have run until errors. This time, I am leaving HTX
  running and observing. Two of the disks reached the HTX error
  threshold and the testers stopped (those 2 disks are now idle).
  Another disks saw errors but then stopped and appears to be running
  fine now. The last disk has not seen any errors (yet). On the two idle
  (errored-out) disks I see  iorequest_cnt matches iodone_cnt. I am able
  to "terminate and restart" the two idle disks and HTX appears to be
  testing them again "normally". Note that no reboot was required,
  further supporting the evidence that, as far as the kernel is
  concerned, there is nothing wrong with the disks and their I/O paths.

  So, I don't believe this completely eliminates aacraid from the
  picture, especially given we don't see this behavior on other
  systems/drivers. But, it probably moves the focus of the investigation
  away form the adapter firmware.

  Tried build upstream 4.11 kernel on Ubuntu. This still gets the hangs.
  Both Ubuntu 4.10 and upstream 4.11 have aacraid driver
  1.2.1[50792]-custom.

  Good new/bad news... While doing an initial evaluation of the LSI-3008
  SAS HBA on Boston and Ubuntu 17.04, I am hitting this same problem.
  So, it appears to have nothing specific to do with the PM8069 or
  aacraid driver.

  Some notes on reproduce this. I have been using the github release of
  HTX, built using the following steps:

  1. apt install make gcc g++ git libncurses5-dev libcxl-dev libdapl-dev 
(others may be required)
  2. git clone https://github.com/open-power/HTX
  3. cd HTX
  4. make
  5. make deb

  Then install the resulting "htxubuntu.deb" package.

  Note, HTX will not test disks that have a filesystem or OS installed,
  so there must be at least two disks made available to HTX by clearing
  any previous data. A partition table is optional, in my testing I have
  none.

  Also, it may be desirable to run HTX somewhere other

[Kernel-packages] [Bug 1635597] Re: Ubuntu16.10:talclp1: Kdump failed with multipath disk

Kernel team,

makedumpfile is marked fix-released in this bug, but the series are
marked as confirmed. Could you please take a look at this bug and make
sure we have makedumpfile fix is applied to those series as well ?

** Changed in: makedumpfile (Ubuntu Trusty)
 Assignee: David Britton (davidpbritton) => Canonical Kernel Team 
(canonical-kernel-team)

** Changed in: makedumpfile (Ubuntu Xenial)
 Assignee: David Britton (davidpbritton) => Canonical Kernel Team 
(canonical-kernel-team)

** Changed in: makedumpfile (Ubuntu Zesty)
 Assignee: David Britton (davidpbritton) => Canonical Kernel Team 
(canonical-kernel-team)

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

Title:
  Ubuntu16.10:talclp1: Kdump failed with multipath disk

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  New
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  New
Status in makedumpfile source package in Trusty:
  Confirmed
Status in linux source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  Confirmed
Status in linux source package in Zesty:
  New
Status in makedumpfile source package in Zesty:
  Confirmed

Bug description:
  Problem  Description
  ==
  On talclp1, I enabled kdump. But kdump failed and it drop to BusyBox.

  root@talclp1:~# echo c> /proc/sysrq-trigger
  [  132.643690] sysrq: SysRq : Trigger a crash
  [  132.643739] Unable to handle kernel paging request for data at address 
0x
  [  132.643745] Faulting instruction address: 0xc05c28f4
  [  132.643749] Oops: Kernel access of bad area, sig: 11 [#1]
  [  132.643753] SMP NR_CPUS=2048 NUMA pSeries
  [  132.643758] Modules linked in: fuse ufs qnx4 hfsplus hfs minix ntfs msdos 
jfs rpadlpar_io rpaphp rpcsec_gss_krb5 nfsv4 dccp_diag cifs nfs dns_resolver 
dccp tcp_diag fscache udp_diag inet_diag unix_diag af_packet_diag netlink_diag 
binfmt_misc xfs libcrc32c pseries_rng rng_core ghash_generic gf128mul 
vmx_crypto sg nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables 
autofs4 ext4 crc16 jbd2 fscrypto mbcache crc32c_generic btrfs xor raid6_pq 
dm_round_robin sr_mod sd_mod cdrom ses enclosure scsi_transport_sas ibmveth 
crc32c_vpmsum ipr scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath dm_mod
  [  132.643819] CPU: 49 PID: 10174 Comm: bash Not tainted 4.8.0-15-generic 
#16-Ubuntu
  [  132.643824] task: c00111767080 task.stack: c000d82e
  [  132.643828] NIP: c05c28f4 LR: c05c39d8 CTR: 
c05c28c0
  [  132.643832] REGS: c000d82e3990 TRAP: 0300   Not tainted  
(4.8.0-15-generic)
  [  132.643836] MSR: 80009033   CR: 28242422  
XER: 0001
  [  132.643848] CFAR: c00087d0 DAR:  DSISR: 4200 
SOFTE: 1
  GPR00: c05c39d8 c000d82e3c10 c0f67b00 0063
  GPR04: c0011d04a9b8 c0011d05f7e0 c0047fb0 00015998
  GPR08: 0007 0001  0001
  GPR12: c05c28c0 c7b4b900  2200
  GPR16: 10170dc8 01002b566368 10140f58 100c7570
  GPR20:  1017dd58 10153618 1017b608
  GPR24: 3e87a294 0001 c0ebff60 0004
  GPR28: c0ec0320 0063 c0e72a90 
  [  132.643906] NIP [c05c28f4] sysrq_handle_crash+0x34/0x50
  [  132.643911] LR [c05c39d8] __handle_sysrq+0xe8/0x280
  [  132.643914] Call Trace:
  [  132.643917] [c000d82e3c10] [c0a245e8] 0xc0a245e8 
(unreliable)
  [  132.643923] [c000d82e3c30] [c05c39d8] __handle_sysrq+0xe8/0x280
  [  132.643928] [c000d82e3cd0] [c05c4188] 
write_sysrq_trigger+0x78/0xa0
  [  132.643935] [c000d82e3d00] [c03ad770] proc_reg_write+0xb0/0x110
  [  132.643941] [c000d82e3d50] [c030fc3c] __vfs_write+0x6c/0xe0
  [  132.643946] [c000d82e3d90] [c0311144] vfs_write+0xd4/0x240
  [  132.643950] [c000d82e3de0] [c0312e5c] SyS_write+0x6c/0x110
  [  132.643957] [c000d82e3e30] [c00095e0] system_call+0x38/0x108
  [  132.643961] Instruction dump:
  [  132.643963] 38425240 7c0802a6 f8010010 f821ffe1 6000 6000 3d220019 
3949ba60
  [  132.643972] 3921 912a 7c0004ac 3940 <992a> 38210020 
e8010010 7c0803a6
  [  132.643981] ---[ end trace eed6bbcd2c3bdfdf ]---
  [  132.646105]
  [  132.646176] Sending IPI to other CPUs
  [  132.647490] IPI complete
  I'm in purgatory
   -> smp_release_cpus()
  spinning_secondaries = 104
   <- smp_release_cpus()
  [2.011346] alg: hash: Test 1 failed for crc32c-vpmsum
  [2.729254] sd 0:2:0:0: [sda] Assuming drive cache: write through
  [

[Kernel-packages] [Bug 1709889] Re: Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to adapter for a very long time.

2017-08-23 Thread Colin Ian King

Doug,

"Can we get some answers as to why CFQ is the default scheduler? It
seems like the expedient fix is to change the default to "deadline"."

Sure. We went back to CFQ as it was showing to be a good general purpose
I/O scheduler for a lot of wide ranging and general purpose I/O demands.
Unfortunately you seem to have uncovered some cases where clearly it
does not behave well for your use case where deadline would be more
appropriate.  Like all schedulers, it's hard to chose one that is going
to meet every use case and every scenario perfectly, especially for a
wide range of devices, device configurations, system memory size and
file system choices.

We do try to systematically check the performance and latencies of
various synthetic test scenarios across a range of file systems on each
kernel to try and spot issues:  http://kernel.ubuntu.com/~cking/fs-
tests/jun-2017/

CFQ has several tunables that may help your issue, I'd refer you to:

https://www.kernel.org/doc/Documentation/block/cfq-iosched.txt

it may be worth reviewing this document and then seeing if the CFQ can
be tuned to improve the issues you are seeing.



** Also affects: linux via
   https://bugzilla.kernel.org/show_bug.cgi?id=196737
   Importance: Unknown
   Status: Unknown

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

Title:
  Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to
  adapter for a very long time.

Status in Linux:
  Unknown
Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  ---Problem Description---
  When running stress test, sometimes seeing IO hung in dmesg or seeing "Host 
adapter abort request" error.

  ---Steps to Reproduce---
   There are two ways to re-create the issues:
  (1)running HTX, you will see IO timeout backtrace in dmesg in several hours
  (2)running some IO test, then reboot system, repeat this two steps, it takes 
long time to re-create the issue.
   
  ---uname output---
  4.10.0-11-generic

  The bulk of the effort for this issue is currently being worked in
  MicroSemi's JIRA https://jira.pmcs.com/browse/ESDIBMOP-133.

  Ran an interesting test: Ran HTX until I started getting the "stall"
  messages on the console, then shutdown HTX and examined the I/O
  counters for the tested disks in sysfs:

  root@bostonp15:~# for i in 
/sys/devices/pci0003:00/0003:00:00.0/0003:01:00.0/host0/target0:2:[2345]/0:2:[2345]:0;
 do echo ${i##*/} $(<${i}/iorequest_cnt) $(<${i}/iodone_cnt); done
  0:2:2:0 0x5eba3d 0x5eba3d
  0:2:3:0 0x773cc9 0x773cc9
  0:2:4:0 0x782c61 0x782c61
  0:2:5:0 0x5ca134 0x5ca134
  root@bostonp15:~#

  So, none of the disks showed any evidence of having lost an I/O. I
  then restarted HTX and aside from having to manually restart one of
  the disks, see no problems with the testing. It appears that what was
  "hung" was purely in userland.

  This does not absolve the kernel or aacraid driver from blame, but it
  shows that the OS "believes" that it completed the I/O and thus
  removed it from the queue. What we don't know is whether the OS truly
  notified HTX about the completion, or if HTX (or userland libraries)
  just failed to process the notification.

  Tests are running again, will see what happens next.

  Update from JIRA:

  I have run some more experiments. Not sure what it tells us, but
  here's what I've seen.

  First test, ran until I got kernel messages about stalled tasks, then
  shutdown HTX. After HTX was down, I checked the above mentioned
  counters and found that on each disk iorequest_cnt matched iodone_cnt.
  The disks were usable and I could restart HTX. This suggests that the
  problem is not in the PM8069 firmware, and makes the case for the
  aacraid driver having a bug somewhat weaker. However, this merely says
  that the driver "completed" the I/O as far as the kernel is concerned,
  not that a completion rippled back to the application.

  I restarted HTX and have run until errors. This time, I am leaving HTX
  running and observing. Two of the disks reached the HTX error
  threshold and the testers stopped (those 2 disks are now idle).
  Another disks saw errors but then stopped and appears to be running
  fine now. The last disk has not seen any errors (yet). On the two idle
  (errored-out) disks I see  iorequest_cnt matches iodone_cnt. I am able
  to "terminate and restart" the two idle disks and HTX appears to be
  testing them again "normally". Note that no reboot was required,
  further supporting the evidence that, as far as the kernel is
  concerned, there is nothing wrong with the disks and their I/O paths.

  So, I don't believe this completely eliminates aacraid from the
  picture, especially given we don't see this behavior on other
  systems/drivers. But, it probably moves the

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

--- Comment From hbath...@in.ibm.com 2017-08-23 09:29 EDT---
(In reply to comment #28)
> Retested kdump today (23rd Aug 2017) on Ubuntu1610 and kdump hangs still:
> -
> root@thymelp3:~# echo c> /proc/sysrq-trigger
> [ 1314.534126] sysrq: SysRq : Trigger a crash
> [ 1314.534139] Unable to handle kernel paging request for data at address
> 0x
> [ 1314.534143] Faulting instruction address: 0xc06a2428
> [ 1314.534147] Oops: Kernel access of bad area, sig: 11 [#1]
> [ 1314.534150] SMP NR_CPUS=2048 NUMA pSeries
> [ 1314.534154] Modules linked in: nfsv3 nfs_acl rpcsec_gss_krb5 auth_rpcgss
> nfsv4 nfs lockd grace fscache binfmt_misc pseries_rng vmx_crypto sunrpc
> ip_tables x_tables autofs4 dm_round_robin btrfs xor raid6_pq lpfc
> crc32c_vpmsum be2net scsi_transport_fc scsi_dh_emc scsi_dh_rdac scsi_dh_alua
> dm_multipath
> [ 1314.534177] CPU: 9 PID: 3421 Comm: bash Not tainted 4.8.0-59-generic
> #64-Ubuntu
> [ 1314.534181] task: c003efc25200 task.stack: c000fb97
> [ 1314.534184] NIP: c06a2428 LR: c06a3478 CTR:
> c06a2400
> [ 1314.534187] REGS: c000fb9739f0 TRAP: 0300   Not tainted
> (4.8.0-59-generic)
> [ 1314.534190] MSR: 80009033   CR: 2822
> XER: 0001
> [ 1314.534198] CFAR: c0008750 DAR:  DSISR: 4200
> SOFTE: 1
> GPR00: c06a3478 c000fb973c70 c1467500 0063
> GPR04: c003ff64aca0 c003ff65fb40 c003ff38 80a0
> GPR08: 0007 0001  0001
> GPR12: c06a2400 c7b35100  2200
> GPR16: 10170dc8 01000bbf0258 10140528 100c6f60
> GPR20:  1017dd58 10152bf0 1017b608
> GPR24: 3fffd72098a4 3fffd72098a0 c137e6e0 0004
> GPR28: c137eaa0 0063 c1332590 
> [ 1314.534242] NIP [c06a2428] sysrq_handle_crash+0x28/0x30
> [ 1314.534246] LR [c06a3478] __handle_sysrq+0xe8/0x280
> [ 1314.534248] Call Trace:
> [ 1314.534250] [c000fb973c70] [c06a3458]
> __handle_sysrq+0xc8/0x280 (unreliable)
> [ 1314.534255] [c000fb973d10] [c06a3bcc]
> write_sysrq_trigger+0x6c/0x90
> [ 1314.534260] [c000fb973d40] [c03adb48] proc_reg_write+0x88/0xd0
> [ 1314.534265] [c000fb973d70] [c03105ac] __vfs_write+0x3c/0x70
> [ 1314.534268] [c000fb973d90] [c0311814] vfs_write+0xd4/0x240
> [ 1314.534272] [c000fb973de0] [c0313368] SyS_write+0x68/0x110
> [ 1314.534276] [c000fb973e30] [c0009584] system_call+0x38/0xec
> [ 1314.534279] Instruction dump:
> [ 1314.534281] 6000 6000 3c4c00dc 38425100 7c0802a6 6000
> 3d22001a 3949bc60
> [ 1314.534288] 3921 912a 7c0004ac 3940 <992a> 4e800020
> 3c4c00dc 384250d0
> [ 1314.534296] ---[ end trace efc32115f1d43c62 ]---
> [ 1314.537099]
> [ 1314.537123] Sending IPI to other CPUs
> [ 1314.538149] IPI complete
> I'm in purgatory
>  -> smp_release_cpus()
> spinning_secondaries = 8
>  <- smp_release_cpus()
> [0.172393] pci 001b:50:00.0: of_irq_parse_pci() failed with rc=-22
> [0.425077] Kernel panic - not syncing: Out of memory and no killable
> processes...
> [0.425077]
> [0.425100] CPU: 2 PID: 1 Comm: swapper/1 Not tainted 4.8.0-59-generic
> #64-Ubuntu
> [0.425102] Call Trace:
> [0.425105] [cd10b220] [c8b0fe4c] dump_stack+0xb0/0xf0
> (unreliable)
> [0.425110] [cd10b260] [c8b0bf58] panic+0x144/0x308
> [0.425114] [cd10b2f0] [c8249c2c]
> out_of_memory+0x48c/0x570
> [0.425117] [cd10b3a0] [c8250ad8]
> __alloc_pages_nodemask+0xdf8/0xe20
> [0.425122] [cd10b560] [c82c6da8]
> alloc_page_interleave+0x58/0xc0
> [0.425126] [cd10b5a0] [c82c7678]
> alloc_pages_current+0x168/0x1d0
> [0.425130] [cd10b600] [c82435e8]
> __page_cache_alloc+0x118/0x160
> [0.425134] [cd10b640] [c82437b4]
> pagecache_get_page+0x184/0x3c0
> [0.425138] [cd10b6b0] [c8243a34]
> grab_cache_page_write_begin+0x44/0x70
> [0.425142] [cd10b6e0] [c834bf6c]
> simple_write_begin+0x4c/0x1b0
> [0.425146] [cd10b730] [c8243264]
> generic_perform_write+0x104/0x280
> [0.425150] [cd10b7d0] [c8245540]
> __generic_file_write_iter+0x1e0/0x230
> [0.425154] [cd10b830] [c824567c]
> generic_file_write_iter+0xec/0x250
> [0.425158] [cd10b870] [c831050c]
> new_sync_write+0xec/0x150
> [0.425162] [cd10b900] [c8311814] vfs_write+0xd4/0x240
> [0.425165] [cd10b950] [c8313368] SyS_write+0x68/0x110
> [0.425169] [cd10b9a0] [c8ea5d0c] xwrite+0x4c/0xb0
> [0.425173] [cd10b9e0]

[Kernel-packages] [Bug 1675624] Kernel debian package with fix (17.04)

Default Comment by Bridge

** Attachment added: "Kernel debian package with fix (17.04)"
   
https://bugs.launchpad.net/bugs/1675624/+attachment/4937481/+files/linux-image-4.10.0-13-generic_4.10.0-13.15_ppc64el.deb

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

Title:
  ubuntu 17.04: hw-breakpoint in kernel-sapce not working

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

Bug description:
  How to reproduce:

  $ sudo cat /proc/kallsyms  | grep pid_max
c1308794 D pid_max

  $ sudo perf record -a --event=mem:0xc1308794 sleep 10

  $ dmesg
[   99.095475] Unable to handle hardware breakpoint. Breakpoint at 
0xc1308794 will be disabled.
[   99.095478] [ cut here ]
[   99.095480] WARNING: CPU: 27 PID: 3306 at 
/build/linux-VtwHOM/linux-4.10.0/arch/powerpc/kernel/hw_breakpoint.c:277 
hw_breakpoint_handler+0x120/0x230
...

  System detail:

  $ uname -a
  Linux tul163-u1704-qemu 4.10.0-13-generic #15-Ubuntu SMP Thu Mar 9 20:27:28 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  $ cat /etc/*release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=17.04
DISTRIB_CODENAME=zesty
DISTRIB_DESCRIPTION="Ubuntu Zesty Zapus (development branch)"

  == Comment: #1 - Ravikumar B. Bangoria  - 
2017-03-22 04:29:24 ==
  https://patchwork.ozlabs.org/patch/727837/ will solve this issue.

  == Comment: #2 - SEETEENA THOUFEEK  - 2017-03-23 
01:14:58 ==
  Patch is accepted upstream. 

  
  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=e148bd17f48bd17fca2f4f089ec879

  
  I had build kernel package with the patch included and tested and it is 
working perfect. 

  link to the backport kernel debian package is uploaded in box note

  https://ibm.ent.box.com/folder/22186913949  under the folder name
  152781

  == Comment: #3 - SEETEENA THOUFEEK  - 2017-03-23
  01:17:02 ==

  
  == Comment: #4 - SEETEENA THOUFEEK  - 2017-03-23 
02:17:04 ==
  Backported patch and kernel debian package with patch provided.

  == Comment: #5 - SEETEENA THOUFEEK  - 2017-03-23 
02:17:52 ==
  debian package is tested locally and verified.

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

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

[Kernel-packages] [Bug 1709889] Re: Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to adapter for a very long time.

--- Comment From dougm...@us.ibm.com 2017-08-23 09:19 EDT---
Opened kernel.org bugzilla https://bugzilla.kernel.org/show_bug.cgi?id=196737

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

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

Title:
  Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to
  adapter for a very long time.

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  ---Problem Description---
  When running stress test, sometimes seeing IO hung in dmesg or seeing "Host 
adapter abort request" error.

  ---Steps to Reproduce---
   There are two ways to re-create the issues:
  (1)running HTX, you will see IO timeout backtrace in dmesg in several hours
  (2)running some IO test, then reboot system, repeat this two steps, it takes 
long time to re-create the issue.
   
  ---uname output---
  4.10.0-11-generic

  The bulk of the effort for this issue is currently being worked in
  MicroSemi's JIRA https://jira.pmcs.com/browse/ESDIBMOP-133.

  Ran an interesting test: Ran HTX until I started getting the "stall"
  messages on the console, then shutdown HTX and examined the I/O
  counters for the tested disks in sysfs:

  root@bostonp15:~# for i in 
/sys/devices/pci0003:00/0003:00:00.0/0003:01:00.0/host0/target0:2:[2345]/0:2:[2345]:0;
 do echo ${i##*/} $(<${i}/iorequest_cnt) $(<${i}/iodone_cnt); done
  0:2:2:0 0x5eba3d 0x5eba3d
  0:2:3:0 0x773cc9 0x773cc9
  0:2:4:0 0x782c61 0x782c61
  0:2:5:0 0x5ca134 0x5ca134
  root@bostonp15:~#

  So, none of the disks showed any evidence of having lost an I/O. I
  then restarted HTX and aside from having to manually restart one of
  the disks, see no problems with the testing. It appears that what was
  "hung" was purely in userland.

  This does not absolve the kernel or aacraid driver from blame, but it
  shows that the OS "believes" that it completed the I/O and thus
  removed it from the queue. What we don't know is whether the OS truly
  notified HTX about the completion, or if HTX (or userland libraries)
  just failed to process the notification.

  Tests are running again, will see what happens next.

  Update from JIRA:

  I have run some more experiments. Not sure what it tells us, but
  here's what I've seen.

  First test, ran until I got kernel messages about stalled tasks, then
  shutdown HTX. After HTX was down, I checked the above mentioned
  counters and found that on each disk iorequest_cnt matched iodone_cnt.
  The disks were usable and I could restart HTX. This suggests that the
  problem is not in the PM8069 firmware, and makes the case for the
  aacraid driver having a bug somewhat weaker. However, this merely says
  that the driver "completed" the I/O as far as the kernel is concerned,
  not that a completion rippled back to the application.

  I restarted HTX and have run until errors. This time, I am leaving HTX
  running and observing. Two of the disks reached the HTX error
  threshold and the testers stopped (those 2 disks are now idle).
  Another disks saw errors but then stopped and appears to be running
  fine now. The last disk has not seen any errors (yet). On the two idle
  (errored-out) disks I see  iorequest_cnt matches iodone_cnt. I am able
  to "terminate and restart" the two idle disks and HTX appears to be
  testing them again "normally". Note that no reboot was required,
  further supporting the evidence that, as far as the kernel is
  concerned, there is nothing wrong with the disks and their I/O paths.

  So, I don't believe this completely eliminates aacraid from the
  picture, especially given we don't see this behavior on other
  systems/drivers. But, it probably moves the focus of the investigation
  away form the adapter firmware.

  Tried build upstream 4.11 kernel on Ubuntu. This still gets the hangs.
  Both Ubuntu 4.10 and upstream 4.11 have aacraid driver
  1.2.1[50792]-custom.

  Good new/bad news... While doing an initial evaluation of the LSI-3008
  SAS HBA on Boston and Ubuntu 17.04, I am hitting this same problem.
  So, it appears to have nothing specific to do with the PM8069 or
  aacraid driver.

  Some notes on reproduce this. I have been using the github release of
  HTX, built using the following steps:

  1. apt install make gcc g++ git libncurses5-dev libcxl-dev libdapl-dev 
(others may be required)
  2. git clone https://github.com/open-power/HTX
  3. cd HTX
  4. make
  5. make deb

  Then install the resulting "htxubuntu.deb" package.

  Note, HTX will not test disks that have a filesystem or OS installed,
  so there must be at least two disks made available to HTX by clearing
  any previous data. A partition table is optional, in my testing I have
  none.

  Also, it may be

[Kernel-packages] [Bug 1665783] Re: Include Broadcom GPL modules in Xenial Kernel

2017-08-23 Thread Thadeu Lima de Souza Cascardo

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

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

Title:
  Include Broadcom GPL modules in Xenial Kernel

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Invalid

Bug description:
  Please include the OpenNSL GPL modules with the Kernel.
  These modules are located at https://github.com/Broadcom-Switch/OpenNSL.
  The latest SDK version is 6.5.6. 
  We would like to have the kernel modules included with the LTS Xenial kernel 
so that we can provide these modules to network vendors so that they don't have 
to compile them and taint our working kernel. 
  We would want to manage these modules so that we can perform updates and 
security fixes to the kernel and even use kernel-livepatch with these devices. 
  Currently, Network vendors compile and build these against older kernel's and 
then they cannot be patched or updated leaving network devices vulnerable to 
security threats that normally would be patched by our systems. By having us 
manage these modules, we can maintain security and compatibility with the 
kernel and the network vendors can use our native kernel with their software.

  The three modules that get built are linux-kernel-bde.ko, linux-user-
  bde,ko and linux-bcm-knet.ko.

  If you have any other questions, please don't hesitate to contact me.

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

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

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

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1712580

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

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

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

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

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

Title:
  [SRU][Zesty]PCI: Add pci_mmap_resource_range() and use it for ARM64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  uio device binding inside VM would fail with errors
  EAL: Detected 3 lcore(s)
  EAL: Probing VFIO support...
  EAL: PCI device :00:01.0 on NUMA socket -1
  EAL: probe driver: 1af4:1000 net_virtio
  EAL: Cannot open /sys/bus/pci/devices/:00:01.0/resource1: No such file or 
directory
  EAL: Cannot open /sys/bus/pci/devices/:00:01.0/resource0: No such file or 
directory
  EAL: Error - exiting with code: 1
Cause: Requested device :00:01.0 cannot be used

  [Fix]
  Fixed in linus kernel by patch 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch/arm64/include/asm/pci.h?h=v4.13-rc4=f719582435afe9c7985206e42d804ea6aa315d33

  [Test]

  [Regression Potential]

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

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

[Kernel-packages] [Bug 1712580] [NEW] [SRU][Zesty]PCI: Add pci_mmap_resource_range() and use it for ARM64

Public bug reported:

[Impact]
uio device binding inside VM would fail with errors
EAL: Detected 3 lcore(s)
EAL: Probing VFIO support...
EAL: PCI device :00:01.0 on NUMA socket -1
EAL: probe driver: 1af4:1000 net_virtio
EAL: Cannot open /sys/bus/pci/devices/:00:01.0/resource1: No such file or 
directory
EAL: Cannot open /sys/bus/pci/devices/:00:01.0/resource0: No such file or 
directory
EAL: Error - exiting with code: 1
  Cause: Requested device :00:01.0 cannot be used

[Fix]
Fixed in linus kernel by patch 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch/arm64/include/asm/pci.h?h=v4.13-rc4=f719582435afe9c7985206e42d804ea6aa315d33

[Test]

[Regression Potential]

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Manoj Iyer (manjo)
 Status: Incomplete


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

Title:
  [SRU][Zesty]PCI: Add pci_mmap_resource_range() and use it for ARM64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  uio device binding inside VM would fail with errors
  EAL: Detected 3 lcore(s)
  EAL: Probing VFIO support...
  EAL: PCI device :00:01.0 on NUMA socket -1
  EAL: probe driver: 1af4:1000 net_virtio
  EAL: Cannot open /sys/bus/pci/devices/:00:01.0/resource1: No such file or 
directory
  EAL: Cannot open /sys/bus/pci/devices/:00:01.0/resource0: No such file or 
directory
  EAL: Error - exiting with code: 1
Cause: Requested device :00:01.0 cannot be used

  [Fix]
  Fixed in linus kernel by patch 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch/arm64/include/asm/pci.h?h=v4.13-rc4=f719582435afe9c7985206e42d804ea6aa315d33

  [Test]

  [Regression Potential]

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

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

[Kernel-packages] [Bug 1709626] Re: Kernel Oops - unable to handle kernel paging request; RIP is at free_pipe_info+0x57/0x90

We should be able to perform a kernel bisect to identify the commit that
introduced this regression.  You say this bug did not exist in 4.4.0-71,
but it does exist in 4.4.0-87.  To perform a bisect, we need to identify
the last kernel version that did not have the bug and the first that
did.  Can you test the following kernel:

4.4.0-85: https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/ppa/+build/12845707

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

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

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

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

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

** Tags added: performing-bisect

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

Title:
  Kernel Oops - unable to handle kernel paging request; RIP is at
  free_pipe_info+0x57/0x90

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

Bug description:
  Hi,

  I'm running a Docker swarm with 5 Nodes. Each node is getting this
  kernel oops pretty frequently, i would say once a day. I'm not able to
  reproduce it effectively but it seem's to happen in case a docker
  stack consisting of approx. 40 containers gets deployed.

  Thanks in advance!

  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-87-generic 4.4.0-87.110
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Uname: Linux 4.4.0-87-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug  9 10:23 seq
   crw-rw 1 root audio 116, 33 Aug  9 10:23 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  Date: Wed Aug  9 15:31:53 2017
  HibernationDevice: RESUME=/dev/mapper/vg00-lv_swap
  InstallationDate: Installed on 2016-06-01 (434 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-87-generic 
root=/dev/mapper/vg00-lv_root ro cgroup_enable=memory swapaccount=1
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-87-generic N/A
   linux-backports-modules-4.4.0-87-generic  N/A
   linux-firmware1.157.11
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/21/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

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

--- Comment From manju...@in.ibm.com 2017-08-23 08:54 EDT---
Retested kdump today (23rd Aug 2017) on Ubuntu1610 and kdump hangs still:
-
root@thymelp3:~# echo c> /proc/sysrq-trigger
[ 1314.534126] sysrq: SysRq : Trigger a crash
[ 1314.534139] Unable to handle kernel paging request for data at address 
0x
[ 1314.534143] Faulting instruction address: 0xc06a2428
[ 1314.534147] Oops: Kernel access of bad area, sig: 11 [#1]
[ 1314.534150] SMP NR_CPUS=2048 NUMA pSeries
[ 1314.534154] Modules linked in: nfsv3 nfs_acl rpcsec_gss_krb5 auth_rpcgss 
nfsv4 nfs lockd grace fscache binfmt_misc pseries_rng vmx_crypto sunrpc 
ip_tables x_tables autofs4 dm_round_robin btrfs xor raid6_pq lpfc crc32c_vpmsum 
be2net scsi_transport_fc scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath
[ 1314.534177] CPU: 9 PID: 3421 Comm: bash Not tainted 4.8.0-59-generic 
#64-Ubuntu
[ 1314.534181] task: c003efc25200 task.stack: c000fb97
[ 1314.534184] NIP: c06a2428 LR: c06a3478 CTR: c06a2400
[ 1314.534187] REGS: c000fb9739f0 TRAP: 0300   Not tainted  
(4.8.0-59-generic)
[ 1314.534190] MSR: 80009033   CR: 2822  XER: 
0001
[ 1314.534198] CFAR: c0008750 DAR:  DSISR: 4200 
SOFTE: 1
GPR00: c06a3478 c000fb973c70 c1467500 0063
GPR04: c003ff64aca0 c003ff65fb40 c003ff38 80a0
GPR08: 0007 0001  0001
GPR12: c06a2400 c7b35100  2200
GPR16: 10170dc8 01000bbf0258 10140528 100c6f60
GPR20:  1017dd58 10152bf0 1017b608
GPR24: 3fffd72098a4 3fffd72098a0 c137e6e0 0004
GPR28: c137eaa0 0063 c1332590 
[ 1314.534242] NIP [c06a2428] sysrq_handle_crash+0x28/0x30
[ 1314.534246] LR [c06a3478] __handle_sysrq+0xe8/0x280
[ 1314.534248] Call Trace:
[ 1314.534250] [c000fb973c70] [c06a3458] __handle_sysrq+0xc8/0x280 
(unreliable)
[ 1314.534255] [c000fb973d10] [c06a3bcc] 
write_sysrq_trigger+0x6c/0x90
[ 1314.534260] [c000fb973d40] [c03adb48] proc_reg_write+0x88/0xd0
[ 1314.534265] [c000fb973d70] [c03105ac] __vfs_write+0x3c/0x70
[ 1314.534268] [c000fb973d90] [c0311814] vfs_write+0xd4/0x240
[ 1314.534272] [c000fb973de0] [c0313368] SyS_write+0x68/0x110
[ 1314.534276] [c000fb973e30] [c0009584] system_call+0x38/0xec
[ 1314.534279] Instruction dump:
[ 1314.534281] 6000 6000 3c4c00dc 38425100 7c0802a6 6000 3d22001a 
3949bc60
[ 1314.534288] 3921 912a 7c0004ac 3940 <992a> 4e800020 3c4c00dc 
384250d0
[ 1314.534296] ---[ end trace efc32115f1d43c62 ]---
[ 1314.537099]
[ 1314.537123] Sending IPI to other CPUs
[ 1314.538149] IPI complete
I'm in purgatory
-> smp_release_cpus()
spinning_secondaries = 8
<- smp_release_cpus()
[0.172393] pci 001b:50:00.0: of_irq_parse_pci() failed with rc=-22
[0.425077] Kernel panic - not syncing: Out of memory and no killable 
processes...
[0.425077]
[0.425100] CPU: 2 PID: 1 Comm: swapper/1 Not tainted 4.8.0-59-generic 
#64-Ubuntu
[0.425102] Call Trace:
[0.425105] [cd10b220] [c8b0fe4c] dump_stack+0xb0/0xf0 
(unreliable)
[0.425110] [cd10b260] [c8b0bf58] panic+0x144/0x308
[0.425114] [cd10b2f0] [c8249c2c] out_of_memory+0x48c/0x570
[0.425117] [cd10b3a0] [c8250ad8] 
__alloc_pages_nodemask+0xdf8/0xe20
[0.425122] [cd10b560] [c82c6da8] 
alloc_page_interleave+0x58/0xc0
[0.425126] [cd10b5a0] [c82c7678] 
alloc_pages_current+0x168/0x1d0
[0.425130] [cd10b600] [c82435e8] 
__page_cache_alloc+0x118/0x160
[0.425134] [cd10b640] [c82437b4] 
pagecache_get_page+0x184/0x3c0
[0.425138] [cd10b6b0] [c8243a34] 
grab_cache_page_write_begin+0x44/0x70
[0.425142] [cd10b6e0] [c834bf6c] 
simple_write_begin+0x4c/0x1b0
[0.425146] [cd10b730] [c8243264] 
generic_perform_write+0x104/0x280
[0.425150] [cd10b7d0] [c8245540] 
__generic_file_write_iter+0x1e0/0x230
[0.425154] [cd10b830] [c824567c] 
generic_file_write_iter+0xec/0x250
[0.425158] [cd10b870] [c831050c] new_sync_write+0xec/0x150
[0.425162] [cd10b900] [c8311814] vfs_write+0xd4/0x240
[0.425165] [cd10b950] [c8313368] SyS_write+0x68/0x110
[0.425169] [cd10b9a0] [c8ea5d0c] xwrite+0x4c/0xb0
[0.425173] [cd10b9e0] [c8ea5e60] do_copy+0xf0/0x170
[0.425176] [cd10ba10] [c8ea59c4] write_buffer+0x5c/0x88
[0.425180] [cd10ba40] [c8ea5a50] flush_buffer+0x60/0xec
[0.425183]

[Kernel-packages] [Bug 1709294] Re: linux: 3.19.0-92.100 -proposed tracker

2017-08-23 Thread Brad Figg

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

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

Title:
  linux: 3.19.0-92.100 -proposed tracker

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

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

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

  backports: 1709295
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

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

--- Comment From dougm...@us.ibm.com 2017-08-23 08:45 EDT---
I tried running 4.13-rc6 with "cfq" set as default scheduler. The problem is 
even worse. I/O delays show up almost immediately. Many exceed the HTX 
10-minute limit. It seems that CFQ is even more broken on the latest kernels.

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

Title:
  Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to
  adapter for a very long time.

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  ---Problem Description---
  When running stress test, sometimes seeing IO hung in dmesg or seeing "Host 
adapter abort request" error.

  ---Steps to Reproduce---
   There are two ways to re-create the issues:
  (1)running HTX, you will see IO timeout backtrace in dmesg in several hours
  (2)running some IO test, then reboot system, repeat this two steps, it takes 
long time to re-create the issue.
   
  ---uname output---
  4.10.0-11-generic

  The bulk of the effort for this issue is currently being worked in
  MicroSemi's JIRA https://jira.pmcs.com/browse/ESDIBMOP-133.

  Ran an interesting test: Ran HTX until I started getting the "stall"
  messages on the console, then shutdown HTX and examined the I/O
  counters for the tested disks in sysfs:

  root@bostonp15:~# for i in 
/sys/devices/pci0003:00/0003:00:00.0/0003:01:00.0/host0/target0:2:[2345]/0:2:[2345]:0;
 do echo ${i##*/} $(<${i}/iorequest_cnt) $(<${i}/iodone_cnt); done
  0:2:2:0 0x5eba3d 0x5eba3d
  0:2:3:0 0x773cc9 0x773cc9
  0:2:4:0 0x782c61 0x782c61
  0:2:5:0 0x5ca134 0x5ca134
  root@bostonp15:~#

  So, none of the disks showed any evidence of having lost an I/O. I
  then restarted HTX and aside from having to manually restart one of
  the disks, see no problems with the testing. It appears that what was
  "hung" was purely in userland.

  This does not absolve the kernel or aacraid driver from blame, but it
  shows that the OS "believes" that it completed the I/O and thus
  removed it from the queue. What we don't know is whether the OS truly
  notified HTX about the completion, or if HTX (or userland libraries)
  just failed to process the notification.

  Tests are running again, will see what happens next.

  Update from JIRA:

  I have run some more experiments. Not sure what it tells us, but
  here's what I've seen.

  First test, ran until I got kernel messages about stalled tasks, then
  shutdown HTX. After HTX was down, I checked the above mentioned
  counters and found that on each disk iorequest_cnt matched iodone_cnt.
  The disks were usable and I could restart HTX. This suggests that the
  problem is not in the PM8069 firmware, and makes the case for the
  aacraid driver having a bug somewhat weaker. However, this merely says
  that the driver "completed" the I/O as far as the kernel is concerned,
  not that a completion rippled back to the application.

  I restarted HTX and have run until errors. This time, I am leaving HTX
  running and observing. Two of the disks reached the HTX error
  threshold and the testers stopped (those 2 disks are now idle).
  Another disks saw errors but then stopped and appears to be running
  fine now. The last disk has not seen any errors (yet). On the two idle
  (errored-out) disks I see  iorequest_cnt matches iodone_cnt. I am able
  to "terminate and restart" the two idle disks and HTX appears to be
  testing them again "normally". Note that no reboot was required,
  further supporting the evidence that, as far as the kernel is
  concerned, there is nothing wrong with the disks and their I/O paths.

  So, I don't believe this completely eliminates aacraid from the
  picture, especially given we don't see this behavior on other
  systems/drivers. But, it probably moves the focus of the investigation
  away form the adapter firmware.

  Tried build upstream 4.11 kernel on Ubuntu. This still gets the hangs.
  Both Ubuntu 4.10 and upstream 4.11 have aacraid driver
  1.2.1[50792]-custom.

  Good new/bad news... While doing an initial evaluation of the LSI-3008
  SAS HBA on Boston and Ubuntu 17.04, I am hitting this same problem.
  So, it appears to have nothing specific to do with the PM8069 or
  aacraid driver.

  Some notes on reproduce this. I have been using the github release of
  HTX, built using the following steps:

  1. apt install make gcc g++ git libncurses5-dev libcxl-dev libdapl-dev 
(others may be required)
  2. git clone https://github.com/open-power/HTX
  3. cd HTX
  4. make
  5. make deb

  Then install the resulting "htxubuntu.deb" package.

  Note, HTX will not test disks that have a filesystem or OS installed,
  so there must be at least two disks made available to HTX by clearing
  any previous data. A partition table is optional, in my

[Kernel-packages] [Bug 1635597] Re: Ubuntu16.10:talclp1: Kdump failed with multipath disk

** Changed in: makedumpfile (Ubuntu)
 Assignee: David Britton (davidpbritton) => Canonical Kernel Team 
(canonical-kernel-team)

** Changed in: linux (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
Canonical Kernel Team (canonical-kernel-team)

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

Title:
  Ubuntu16.10:talclp1: Kdump failed with multipath disk

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  New
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  New
Status in makedumpfile source package in Trusty:
  Confirmed
Status in linux source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  Confirmed
Status in linux source package in Zesty:
  New
Status in makedumpfile source package in Zesty:
  Confirmed

Bug description:
  Problem  Description
  ==
  On talclp1, I enabled kdump. But kdump failed and it drop to BusyBox.

  root@talclp1:~# echo c> /proc/sysrq-trigger
  [  132.643690] sysrq: SysRq : Trigger a crash
  [  132.643739] Unable to handle kernel paging request for data at address 
0x
  [  132.643745] Faulting instruction address: 0xc05c28f4
  [  132.643749] Oops: Kernel access of bad area, sig: 11 [#1]
  [  132.643753] SMP NR_CPUS=2048 NUMA pSeries
  [  132.643758] Modules linked in: fuse ufs qnx4 hfsplus hfs minix ntfs msdos 
jfs rpadlpar_io rpaphp rpcsec_gss_krb5 nfsv4 dccp_diag cifs nfs dns_resolver 
dccp tcp_diag fscache udp_diag inet_diag unix_diag af_packet_diag netlink_diag 
binfmt_misc xfs libcrc32c pseries_rng rng_core ghash_generic gf128mul 
vmx_crypto sg nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables 
autofs4 ext4 crc16 jbd2 fscrypto mbcache crc32c_generic btrfs xor raid6_pq 
dm_round_robin sr_mod sd_mod cdrom ses enclosure scsi_transport_sas ibmveth 
crc32c_vpmsum ipr scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath dm_mod
  [  132.643819] CPU: 49 PID: 10174 Comm: bash Not tainted 4.8.0-15-generic 
#16-Ubuntu
  [  132.643824] task: c00111767080 task.stack: c000d82e
  [  132.643828] NIP: c05c28f4 LR: c05c39d8 CTR: 
c05c28c0
  [  132.643832] REGS: c000d82e3990 TRAP: 0300   Not tainted  
(4.8.0-15-generic)
  [  132.643836] MSR: 80009033   CR: 28242422  
XER: 0001
  [  132.643848] CFAR: c00087d0 DAR:  DSISR: 4200 
SOFTE: 1
  GPR00: c05c39d8 c000d82e3c10 c0f67b00 0063
  GPR04: c0011d04a9b8 c0011d05f7e0 c0047fb0 00015998
  GPR08: 0007 0001  0001
  GPR12: c05c28c0 c7b4b900  2200
  GPR16: 10170dc8 01002b566368 10140f58 100c7570
  GPR20:  1017dd58 10153618 1017b608
  GPR24: 3e87a294 0001 c0ebff60 0004
  GPR28: c0ec0320 0063 c0e72a90 
  [  132.643906] NIP [c05c28f4] sysrq_handle_crash+0x34/0x50
  [  132.643911] LR [c05c39d8] __handle_sysrq+0xe8/0x280
  [  132.643914] Call Trace:
  [  132.643917] [c000d82e3c10] [c0a245e8] 0xc0a245e8 
(unreliable)
  [  132.643923] [c000d82e3c30] [c05c39d8] __handle_sysrq+0xe8/0x280
  [  132.643928] [c000d82e3cd0] [c05c4188] 
write_sysrq_trigger+0x78/0xa0
  [  132.643935] [c000d82e3d00] [c03ad770] proc_reg_write+0xb0/0x110
  [  132.643941] [c000d82e3d50] [c030fc3c] __vfs_write+0x6c/0xe0
  [  132.643946] [c000d82e3d90] [c0311144] vfs_write+0xd4/0x240
  [  132.643950] [c000d82e3de0] [c0312e5c] SyS_write+0x6c/0x110
  [  132.643957] [c000d82e3e30] [c00095e0] system_call+0x38/0x108
  [  132.643961] Instruction dump:
  [  132.643963] 38425240 7c0802a6 f8010010 f821ffe1 6000 6000 3d220019 
3949ba60
  [  132.643972] 3921 912a 7c0004ac 3940 <992a> 38210020 
e8010010 7c0803a6
  [  132.643981] ---[ end trace eed6bbcd2c3bdfdf ]---
  [  132.646105]
  [  132.646176] Sending IPI to other CPUs
  [  132.647490] IPI complete
  I'm in purgatory
   -> smp_release_cpus()
  spinning_secondaries = 104
   <- smp_release_cpus()
  [2.011346] alg: hash: Test 1 failed for crc32c-vpmsum
  [2.729254] sd 0:2:0:0: [sda] Assuming drive cache: write through
  [2.731554] sd 1:2:5:0: [sdn] Assuming drive cache: write through
  [2.739087] sd 1:2:4:0: [sdm] Assuming drive cache: write through
  [2.739089] sd 1:2:6:0: [sdo] Assuming drive cache: write through
  [2.739110] sd 1:2:7:0: [sdp] Assuming drive cache: write through
  [2.739115] sd 1:2:0:0: [sdi] Assuming drive cache: write through

[Kernel-packages] [Bug 1609750] Re: Audio not working on Acer Chromebook R11

2017-08-23 Thread Timo Jyrinki

A fix might be coming in some months' time to the upstream kernel.

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Invalid

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

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

Title:
  Audio not working on Acer Chromebook R11

Status in linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Audio is not working at all on Acer Chromebook R11 (codename CYAN).
  It's a Intel Braswell platform. snd_hda_intel messages seem normal,
  but Pulseaudio does not detect sound hardware.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: pulseaudio 1:9.0-1.1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: Unity
  Date: Thu Aug  4 14:12:03 2016
  InstallationDate: Installed on 2016-07-22 (13 days ago)
  InstallationMedia:
   
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE
  --- 
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=53fe7902-c347-4ff8-945d-a3e3de773a08
  InstallationDate: Installed on 2016-07-22 (13 days ago)
  InstallationMedia:
   
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Cyan
  Package: linux-image-4.4.0-33-generic 4.4.0-33.52
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic 
root=UUID=742e4082-264a-4459-93df-9ec07b41d5e8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-33-generic N/A
   linux-backports-modules-4.4.0-33-generic  N/A
   linux-firmware1.159
  Tags:  yakkety
  Uname: Linux 4.4.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/20/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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

[Kernel-packages] [Bug 1706132] Re: xfs slab objects (memory) leak when xfs shutdown is called

2017-08-23 Thread Rafael David Tinoco

Okay,

First I have failed the path without propagating transport layer error
and xfs stayed up (nmi watchdog would eventually detect a lockup if
pagecache was ever attempted to be flushed), i returned the path and
failed it again, now with error propagation. The error was detected and
all SCSI CDBs were failed, SCSI sensed errors and XFS called shutdown:

http://pastebin.ubuntu.com/25376025/

Aug 23 11:34:47 xfshang kernel: [ 1871.328044] blk_update_request: I/O error, 
dev sdb, sector 20481104
Aug 23 11:34:47 xfshang kernel: [ 1871.328051] XFS (sdb1): metadata I/O error: 
block 0x1387c50 ("xlog_iodone") error 5 numblks 64
Aug 23 11:34:47 xfshang kernel: [ 1871.328053] XFS (sdb1): 
xfs_do_force_shutdown(0x2) called from line 1197 of file 
/build/linux-lts-xenial-AsqcmJ/linux-lts-xenial-4.4.0/fs/xfs/xfs_log.c.  Return 
address = 0xc025f698
Aug 23 11:34:47 xfshang kernel: [ 1871.328066] XFS (sdb1): Log I/O Error 
Detected.  Shutting down filesystem
Aug 23 11:34:47 xfshang kernel: [ 1871.328067] XFS (sdb1): Please umount the 
filesystem and rectify the problem(s)
Aug 23 11:34:47 xfshang kernel: [ 1873.966241] buffer_io_error: 173396 
callbacks suppressed

Aug 23 11:34:47 xfshang kernel: [ 1873.966244] Buffer I/O error on dev sdb1, 
logical block 102421, lost async page write
Aug 23 11:34:47 xfshang kernel: [ 1873.967411] Buffer I/O error on dev sdb1, 
logical block 102422, lost async page write
Aug 23 11:34:47 xfshang kernel: [ 1873.968599] Buffer I/O error on dev sdb1, 
logical block 102423, lost async page write
...
Aug 23 11:34:56 xfshang dhclient: DHCPREQUEST of 192.168.50.95 on internal to 
192.168.48.1 port 67 (xid=0x87b4739)
Aug 23 11:34:56 xfshang dhclient: DHCPACK of 192.168.50.95 from 192.168.48.1
Aug 23 11:34:56 xfshang dhclient: bound to 192.168.50.95 -- renewal in 15 
seconds.
Aug 23 11:35:01 xfshang kernel: [ 1887.284525] XFS (sdb1): xfs_log_force: error 
-5 returned.
Aug 23 11:35:01 xfshang kernel: [ 1887.548087] XFS (sdb1): Unmounting Filesystem
Aug 23 11:35:01 xfshang kernel: [ 1887.548100] XFS (sdb1): xfs_log_force: error 
-5 returned.
Aug 23 11:35:01 xfshang kernel: [ 1887.548145] XFS (sdb1): xfs_log_force: error 
-5 returned.
Aug 23 11:35:01 xfshang kernel: [ 1887.548438] sd 5:0:0:1: rejecting I/O to 
offline device
Aug 23 11:35:01 xfshang kernel: [ 1887.549424] blk_update_request: I/O error, 
dev sdb, sector 0

Then I removed xfs module and no leak was found. I consider this
verified and good to go.

Thank you!

-Rafael

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

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

Title:
  xfs slab objects (memory) leak when xfs shutdown is called

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

Bug description:
  [Impact]

   * xfs kernel memory leak in case of xfs shutdown due to i/o errors
   * if xfs on iscsi, iscsi disconnection and module unload will case mem leak

  [Test Case]

   * configure tgtd with 1 lun and make it available through tcp/ip
   * configure open-iscsi to map this lun
   * make sure node.session.timeo.replacement_timeout = 0 in iscsid.conf
   * mount a xfs volume using the lun from tgtd host, run bonnie -d /xfsdir
   * in tgtd server, drop iscsi packets and watch client to have i/o errors
   * after sometime (depending on timeout) xfs will call shutdown
   * make sure the i/o errors led to xfs shutdown (comment #3)
   * after shutdown you try to remove xfs module and it will leak

  [Regression Potential]

   * based on upstream fix
   * tested in the same environment
   * potential damage to xfs

  [Other Info]

  Original Description:

     This scenario is testing [iscsi <-> scsi <-> disk <-> xfs]

  [  551.125604] sd 2:0:0:1: rejecting I/O to offline device
  [  551.125615] sd 2:0:0:1: rejecting I/O to offline device
  [  551.125627] sd 2:0:0:1: rejecting I/O to offline device
  [  551.125639] sd 2:0:0:1: rejecting I/O to offline device

  [  551.135216] XFS (sda1): metadata I/O error: block 0xeffe01 
("xfs_trans_read_buf_map") error 5 numblks 1
  [  551.135274] XFS (sda1): page discard on page ea0002a89cc0, inode 0x83, 
offset 6442385408.

  # when XFS shuts down because of an error (or offline disk, example):

  [  551.850498] XFS (sda1): xfs_do_force_shutdown(0x2) called from line 1197 
of file /build/linux-lts-xenial-roXrYH/linux-lts-xenial-4.4.0/fs/xfs/xfs_log.c. 
 Return address = 0xc0300388
  [  551.850568] XFS (sda1): Log I/O Error Detected.  Shutting down filesystem

  [  551.850618] XFS (sda1): xfs_log_force: error -5 returned.

  [  551.850630] XFS (sda1): Failing async write on buffer block 0x77ff08. 
Retrying async write.
  [  551.850634] XFS (sda1): Failing async write on buffer block 0x77ff10. 
Retrying async write.
  [  551.850638] XFS (sda1): Failing async write on buffer block

[Kernel-packages] [Bug 1333294] Re: 32-bit kernel HDD slow write speed

** Package changed: linux-meta (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/1333294

Title:
  32-bit kernel HDD slow write speed

Status in linux package in Ubuntu:
  Confirmed
Status in linux-meta-lts-trusty package in Ubuntu:
  Confirmed

Bug description:
  Summary

  After upgrading my Ubuntu 32-bit from 12.04 to 14.04 the write
  performance is painfully slow (less than 4.6MB/s) of both my SSD
  drives. The read speed is still fine. I've tested with the latest
  version of System Rescue CD (4.2.0 at this time) to see if was a
  hardware problem. However the performance of my drives was even better
  better than using Ubuntu 12.04.

  I've also tried to make a fresh installation of Ubuntu 14.04 on a
  spare SSD drive of mine to see if its because I upgraded from 12.04.
  But after waiting 4 hours for it to install, I finally lost patience,
  and stopped the installation.

  I'm using the deadline scheduler, but it doesn't matter which one I
  use. I'm also using the lowlatency kernel, but using the generic
  kernel doesn't have any effect.

  I've tested with mechanical hard drives, and the problem also occurs
  there.

  I've also tried to update to the proposed updates, and updated to
  kernel 3.13.0-30.54, but problem still exists there.

  The only think that helps is telling the kernel only to address 8GB
  RAM using the "mem=8GB" kernel option, but that is obviously not a
  solution when I need to utilize all the 32GB RAM that I have .

  The reason that I use a 32-bit OS  is because most of the applications
  I use on my laptop are propriety software that only exists in 32-bit
  versions.


  Details

  Kernel version
  root@ubuntu:~# uname -a
  Linux fk20563 3.13.0-29-lowlatency #53-Ubuntu SMP PREEMPT Wed Jun 4 21:20:42 
UTC 2014 i686 i686 i686 GNU/Linux

  List hardware
  lshw > lshw.txt

  Timings of devices (which is also 4x slower than normal)
  root@ubuntu:~# hdparm -t /dev/sda && hdparm -t /dev/sda && hdparm -t /dev/sda
  /dev/sda:
   Timing buffered disk reads: 470 MB in  3.01 seconds = 156.33 MB/sec

  /dev/sda:
   Timing buffered disk reads: 530 MB in  3.03 seconds = 174.86 MB/sec

  /dev/sda:
   Timing buffered disk reads: 500 MB in  3.01 seconds = 166.36 MB/sec

  root@ubuntu:~# hdparm -t /dev/sdb && hdparm -t /dev/sdb && hdparm -t /dev/sdb
  /dev/sdb:
   Timing buffered disk reads: 500 MB in  3.32 seconds = 150.61 MB/sec

  /dev/sdb:
   Timing buffered disk reads: 508 MB in  3.03 seconds = 167.49 MB/sec

  /dev/sdb:
   Timing buffered disk reads: 500 MB in  3.21 seconds = 155.81 MB/sec

  SSD partition alignment check
  root@ubuntu:~# fdisk -l

  Disk /dev/sda: 256.1 GB, 256060514304 bytes
  255 heads, 63 sectors/track, 31130 cylinders, total 500118192 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disk identifier: 0xd162fc6d

  Device Boot Start End Blocks Id System
  /dev/sda1 2048 483332095 241665024 83 Linux
  /dev/sda2 483332096 500117503 8392704 5 Extended
  /dev/sda5 483334144 500117503 8391680 82 Linux swap / Solaris

  Disk /dev/sdb: 480.1 GB, 480103981056 bytes
  255 heads, 63 sectors/track, 58369 cylinders, total 937703088 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disk identifier: 0x

  Device Boot Start End Blocks Id System
  /dev/sdb1 2048 937703087 468850520 83 Linux
  root@ubuntu:~# parted 
  GNU Parted 2.3
  Using /dev/sda
  Welcome to GNU Parted! Type 'help' to view a list of commands.
  (parted) select /dev/sda
  Using /dev/sda
  (parted) align-check opt 1 
  1 aligned
  (parted) select /dev/sdb
  Using /dev/sdb
  (parted) align-check opt 1 
  1 aligned
  (parted) quit 

  Scheduler:
  root@ubuntu:~# cat /sys/block/sd{a,b}/queue/scheduler
  noop [deadline] cfq 
  noop [deadline] cfq 

  Mount options:
  root@fk20563:~# mount | grep sda
  /dev/sda1 on / type ext4 (rw,noatime,nodiratime,errors=remount-ro,discard)
  root@fk20563:~# mount | grep sdb
  /dev/sdb1 on /media/vmware type xfs 
(rw,noatime,nodiratime,logbsize=256k,discard)

  FS read/write check of /dev/sda1 on Ubuntu
  root@fk20563:~# dd if=/dev/zero of=/test.raw bs=1M count=1000
  1000+0 records in
  1000+0 records out
  1048576000 bytes (1.0 GB) copied, 229.091 s, 4.6 MB/s
  root@fk20563:~# dd of=/dev/null if=/test.raw
  2048000+0 records in
  2048000+0 records out
  1048576000 bytes (1.0 GB) copied, 2.58461 s, 406 MB/s

  FS read/write check of /dev/sdb1 on Ubuntu
  root@fk20563:~# dd if=/dev/zero of=/media/vmware/test.raw bs=1M count=1000
  1000+0 records in
  1000+0 records out
  1048576000 bytes (1.0 GB) copied, 229.395 s, 4.6 MB/s
  root@fk20563:~# dd of=/dev/null if=/media/vmware/test.raw
  2048000+0 records in
  2048000+0 records

[Kernel-packages] [Bug 1333294] Re: 32-bit kernel HDD slow write speed

2017-08-23 Thread Launchpad Bug Tracker

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

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

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

Title:
  32-bit kernel HDD slow write speed

Status in linux package in Ubuntu:
  Confirmed
Status in linux-meta-lts-trusty package in Ubuntu:
  Confirmed

Bug description:
  Summary

  After upgrading my Ubuntu 32-bit from 12.04 to 14.04 the write
  performance is painfully slow (less than 4.6MB/s) of both my SSD
  drives. The read speed is still fine. I've tested with the latest
  version of System Rescue CD (4.2.0 at this time) to see if was a
  hardware problem. However the performance of my drives was even better
  better than using Ubuntu 12.04.

  I've also tried to make a fresh installation of Ubuntu 14.04 on a
  spare SSD drive of mine to see if its because I upgraded from 12.04.
  But after waiting 4 hours for it to install, I finally lost patience,
  and stopped the installation.

  I'm using the deadline scheduler, but it doesn't matter which one I
  use. I'm also using the lowlatency kernel, but using the generic
  kernel doesn't have any effect.

  I've tested with mechanical hard drives, and the problem also occurs
  there.

  I've also tried to update to the proposed updates, and updated to
  kernel 3.13.0-30.54, but problem still exists there.

  The only think that helps is telling the kernel only to address 8GB
  RAM using the "mem=8GB" kernel option, but that is obviously not a
  solution when I need to utilize all the 32GB RAM that I have .

  The reason that I use a 32-bit OS  is because most of the applications
  I use on my laptop are propriety software that only exists in 32-bit
  versions.


  Details

  Kernel version
  root@ubuntu:~# uname -a
  Linux fk20563 3.13.0-29-lowlatency #53-Ubuntu SMP PREEMPT Wed Jun 4 21:20:42 
UTC 2014 i686 i686 i686 GNU/Linux

  List hardware
  lshw > lshw.txt

  Timings of devices (which is also 4x slower than normal)
  root@ubuntu:~# hdparm -t /dev/sda && hdparm -t /dev/sda && hdparm -t /dev/sda
  /dev/sda:
   Timing buffered disk reads: 470 MB in  3.01 seconds = 156.33 MB/sec

  /dev/sda:
   Timing buffered disk reads: 530 MB in  3.03 seconds = 174.86 MB/sec

  /dev/sda:
   Timing buffered disk reads: 500 MB in  3.01 seconds = 166.36 MB/sec

  root@ubuntu:~# hdparm -t /dev/sdb && hdparm -t /dev/sdb && hdparm -t /dev/sdb
  /dev/sdb:
   Timing buffered disk reads: 500 MB in  3.32 seconds = 150.61 MB/sec

  /dev/sdb:
   Timing buffered disk reads: 508 MB in  3.03 seconds = 167.49 MB/sec

  /dev/sdb:
   Timing buffered disk reads: 500 MB in  3.21 seconds = 155.81 MB/sec

  SSD partition alignment check
  root@ubuntu:~# fdisk -l

  Disk /dev/sda: 256.1 GB, 256060514304 bytes
  255 heads, 63 sectors/track, 31130 cylinders, total 500118192 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disk identifier: 0xd162fc6d

  Device Boot Start End Blocks Id System
  /dev/sda1 2048 483332095 241665024 83 Linux
  /dev/sda2 483332096 500117503 8392704 5 Extended
  /dev/sda5 483334144 500117503 8391680 82 Linux swap / Solaris

  Disk /dev/sdb: 480.1 GB, 480103981056 bytes
  255 heads, 63 sectors/track, 58369 cylinders, total 937703088 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disk identifier: 0x

  Device Boot Start End Blocks Id System
  /dev/sdb1 2048 937703087 468850520 83 Linux
  root@ubuntu:~# parted 
  GNU Parted 2.3
  Using /dev/sda
  Welcome to GNU Parted! Type 'help' to view a list of commands.
  (parted) select /dev/sda
  Using /dev/sda
  (parted) align-check opt 1 
  1 aligned
  (parted) select /dev/sdb
  Using /dev/sdb
  (parted) align-check opt 1 
  1 aligned
  (parted) quit 

  Scheduler:
  root@ubuntu:~# cat /sys/block/sd{a,b}/queue/scheduler
  noop [deadline] cfq 
  noop [deadline] cfq 

  Mount options:
  root@fk20563:~# mount | grep sda
  /dev/sda1 on / type ext4 (rw,noatime,nodiratime,errors=remount-ro,discard)
  root@fk20563:~# mount | grep sdb
  /dev/sdb1 on /media/vmware type xfs 
(rw,noatime,nodiratime,logbsize=256k,discard)

  FS read/write check of /dev/sda1 on Ubuntu
  root@fk20563:~# dd if=/dev/zero of=/test.raw bs=1M count=1000
  1000+0 records in
  1000+0 records out
  1048576000 bytes (1.0 GB) copied, 229.091 s, 4.6 MB/s
  root@fk20563:~# dd of=/dev/null if=/test.raw
  2048000+0 records in
  2048000+0 records out
  1048576000 bytes (1.0 GB) copied, 2.58461 s, 406 MB/s

  FS read/write check of /dev/sdb1 on Ubuntu
  root@fk20563:~# dd if=/dev/zero of=/media/vmware/test.raw bs=1M count=1000
  1000+0 records in
  1000+0 records out
  1048576000 bytes (1.0 GB) copied, 229.395 s, 4.6 MB/s
  root@fk20563:~#

[Kernel-packages] [Bug 1709303] Re: linux: 4.10.0-33.37 -proposed tracker

2017-08-23 Thread Brad Figg

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

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

Title:
  linux: 4.10.0-33.37 -proposed tracker

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

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

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

  backports: 1709304
  derivatives: 1709305
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1333294] Re: 32-bit kernel HDD slow write speed

2017-08-23 Thread Norbert

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

** Tags added: trusty xenial

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

Title:
  32-bit kernel HDD slow write speed

Status in linux-meta package in Ubuntu:
  Confirmed
Status in linux-meta-lts-trusty package in Ubuntu:
  Confirmed

Bug description:
  Summary

  After upgrading my Ubuntu 32-bit from 12.04 to 14.04 the write
  performance is painfully slow (less than 4.6MB/s) of both my SSD
  drives. The read speed is still fine. I've tested with the latest
  version of System Rescue CD (4.2.0 at this time) to see if was a
  hardware problem. However the performance of my drives was even better
  better than using Ubuntu 12.04.

  I've also tried to make a fresh installation of Ubuntu 14.04 on a
  spare SSD drive of mine to see if its because I upgraded from 12.04.
  But after waiting 4 hours for it to install, I finally lost patience,
  and stopped the installation.

  I'm using the deadline scheduler, but it doesn't matter which one I
  use. I'm also using the lowlatency kernel, but using the generic
  kernel doesn't have any effect.

  I've tested with mechanical hard drives, and the problem also occurs
  there.

  I've also tried to update to the proposed updates, and updated to
  kernel 3.13.0-30.54, but problem still exists there.

  The only think that helps is telling the kernel only to address 8GB
  RAM using the "mem=8GB" kernel option, but that is obviously not a
  solution when I need to utilize all the 32GB RAM that I have .

  The reason that I use a 32-bit OS  is because most of the applications
  I use on my laptop are propriety software that only exists in 32-bit
  versions.


  Details

  Kernel version
  root@ubuntu:~# uname -a
  Linux fk20563 3.13.0-29-lowlatency #53-Ubuntu SMP PREEMPT Wed Jun 4 21:20:42 
UTC 2014 i686 i686 i686 GNU/Linux

  List hardware
  lshw > lshw.txt

  Timings of devices (which is also 4x slower than normal)
  root@ubuntu:~# hdparm -t /dev/sda && hdparm -t /dev/sda && hdparm -t /dev/sda
  /dev/sda:
   Timing buffered disk reads: 470 MB in  3.01 seconds = 156.33 MB/sec

  /dev/sda:
   Timing buffered disk reads: 530 MB in  3.03 seconds = 174.86 MB/sec

  /dev/sda:
   Timing buffered disk reads: 500 MB in  3.01 seconds = 166.36 MB/sec

  root@ubuntu:~# hdparm -t /dev/sdb && hdparm -t /dev/sdb && hdparm -t /dev/sdb
  /dev/sdb:
   Timing buffered disk reads: 500 MB in  3.32 seconds = 150.61 MB/sec

  /dev/sdb:
   Timing buffered disk reads: 508 MB in  3.03 seconds = 167.49 MB/sec

  /dev/sdb:
   Timing buffered disk reads: 500 MB in  3.21 seconds = 155.81 MB/sec

  SSD partition alignment check
  root@ubuntu:~# fdisk -l

  Disk /dev/sda: 256.1 GB, 256060514304 bytes
  255 heads, 63 sectors/track, 31130 cylinders, total 500118192 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disk identifier: 0xd162fc6d

  Device Boot Start End Blocks Id System
  /dev/sda1 2048 483332095 241665024 83 Linux
  /dev/sda2 483332096 500117503 8392704 5 Extended
  /dev/sda5 483334144 500117503 8391680 82 Linux swap / Solaris

  Disk /dev/sdb: 480.1 GB, 480103981056 bytes
  255 heads, 63 sectors/track, 58369 cylinders, total 937703088 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disk identifier: 0x

  Device Boot Start End Blocks Id System
  /dev/sdb1 2048 937703087 468850520 83 Linux
  root@ubuntu:~# parted 
  GNU Parted 2.3
  Using /dev/sda
  Welcome to GNU Parted! Type 'help' to view a list of commands.
  (parted) select /dev/sda
  Using /dev/sda
  (parted) align-check opt 1 
  1 aligned
  (parted) select /dev/sdb
  Using /dev/sdb
  (parted) align-check opt 1 
  1 aligned
  (parted) quit 

  Scheduler:
  root@ubuntu:~# cat /sys/block/sd{a,b}/queue/scheduler
  noop [deadline] cfq 
  noop [deadline] cfq 

  Mount options:
  root@fk20563:~# mount | grep sda
  /dev/sda1 on / type ext4 (rw,noatime,nodiratime,errors=remount-ro,discard)
  root@fk20563:~# mount | grep sdb
  /dev/sdb1 on /media/vmware type xfs 
(rw,noatime,nodiratime,logbsize=256k,discard)

  FS read/write check of /dev/sda1 on Ubuntu
  root@fk20563:~# dd if=/dev/zero of=/test.raw bs=1M count=1000
  1000+0 records in
  1000+0 records out
  1048576000 bytes (1.0 GB) copied, 229.091 s, 4.6 MB/s
  root@fk20563:~# dd of=/dev/null if=/test.raw
  2048000+0 records in
  2048000+0 records out
  1048576000 bytes (1.0 GB) copied, 2.58461 s, 406 MB/s

  FS read/write check of /dev/sdb1 on Ubuntu
  root@fk20563:~# dd if=/dev/zero of=/media/vmware/test.raw bs=1M count=1000
  1000+0 records in
  1000+0 records out
  1048576000 bytes (1.0 GB) copied, 229.395 s, 4.6 MB/s
  root@fk20563:~# dd of=/dev/null

[Kernel-packages] [Bug 1706132] Re: xfs slab objects (memory) leak when xfs shutdown is called

2017-08-23 Thread Rafael David Tinoco

Working on verification right now.

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

Title:
  xfs slab objects (memory) leak when xfs shutdown is called

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

Bug description:
  [Impact]

   * xfs kernel memory leak in case of xfs shutdown due to i/o errors
   * if xfs on iscsi, iscsi disconnection and module unload will case mem leak

  [Test Case]

   * configure tgtd with 1 lun and make it available through tcp/ip
   * configure open-iscsi to map this lun
   * make sure node.session.timeo.replacement_timeout = 0 in iscsid.conf
   * mount a xfs volume using the lun from tgtd host, run bonnie -d /xfsdir
   * in tgtd server, drop iscsi packets and watch client to have i/o errors
   * after sometime (depending on timeout) xfs will call shutdown
   * make sure the i/o errors led to xfs shutdown (comment #3)
   * after shutdown you try to remove xfs module and it will leak

  [Regression Potential]

   * based on upstream fix
   * tested in the same environment
   * potential damage to xfs

  [Other Info]

  Original Description:

     This scenario is testing [iscsi <-> scsi <-> disk <-> xfs]

  [  551.125604] sd 2:0:0:1: rejecting I/O to offline device
  [  551.125615] sd 2:0:0:1: rejecting I/O to offline device
  [  551.125627] sd 2:0:0:1: rejecting I/O to offline device
  [  551.125639] sd 2:0:0:1: rejecting I/O to offline device

  [  551.135216] XFS (sda1): metadata I/O error: block 0xeffe01 
("xfs_trans_read_buf_map") error 5 numblks 1
  [  551.135274] XFS (sda1): page discard on page ea0002a89cc0, inode 0x83, 
offset 6442385408.

  # when XFS shuts down because of an error (or offline disk, example):

  [  551.850498] XFS (sda1): xfs_do_force_shutdown(0x2) called from line 1197 
of file /build/linux-lts-xenial-roXrYH/linux-lts-xenial-4.4.0/fs/xfs/xfs_log.c. 
 Return address = 0xc0300388
  [  551.850568] XFS (sda1): Log I/O Error Detected.  Shutting down filesystem

  [  551.850618] XFS (sda1): xfs_log_force: error -5 returned.

  [  551.850630] XFS (sda1): Failing async write on buffer block 0x77ff08. 
Retrying async write.
  [  551.850634] XFS (sda1): Failing async write on buffer block 0x77ff10. 
Retrying async write.
  [  551.850638] XFS (sda1): Failing async write on buffer block 0x77ff01. 
Retrying async write.
  [  551.853171] XFS (sda1): Please umount the filesystem and rectify the 
problem(s)

  [  551.874131] XFS (sda1): metadata I/O error: block 0x1dffc49 
("xlog_iodone") error 5 numblks 64
  [  551.877993] XFS (sda1): xfs_do_force_shutdown(0x2) called from line 1197 
of file /build/linux-lts-xenial-roXrYH/linux-lts-xenial-4.4.0/fs/xfs/xfs_log.c. 
 Return address = 0xc0300388

  [  551.899036] XFS (sda1): xfs_log_force: error -5 returned.
  [  569.323074] XFS (sda1): xfs_log_force: error -5 returned.
  [  599.403085] XFS (sda1): xfs_log_force: error -5 returned.
  [  629.483111] XFS (sda1): xfs_log_force: error -5 returned.
  [  659.563115] XFS (sda1): xfs_log_force: error -5 returned.
  [  689.643014] XFS (sda1): xfs_log_force: error -5 returned.

  # when I execute:

  # sudo umount /dev/sda1:

  [81634.923043] XFS (sda1): xfs_log_force: error -5 returned.
  [81640.739097] XFS (sda1): xfs_log_force: error -5 returned.
  [81640.739137] XFS (sda1): Unmounting Filesystem
  [81640.739463] XFS (sda1): xfs_log_force: error -5 returned.
  [81640.739508] XFS (sda1): xfs_log_force: error -5 returned.
  [81640.742741] sd 2:0:0:1: rejecting I/O to offline device
  [81640.745576] blk_update_request: 25 callbacks suppressed
  [81640.745601] blk_update_request: I/O error, dev sda, sector 0

  # i was able to umount and then to remove iscsi disk.

  # but if i try to unload the xfs module:

  inaddy@(trustyiscsicli):~$ sudo rmmod xfs
  [82211.059301] 
=
  [82211.063764] BUG xfs_log_ticket (Tainted: G   OE  ): Objects 
remaining in xfs_log_ticket on kmem_cache_close()
  [82211.067450] 
-
  [82211.067450]
  [82211.070580] INFO: Slab 0xea0002eb7640 objects=22 used=1 
fp=0x8800badd9f18 flags=0xc00080
  [82211.074430] INFO: Object 0x8800badd9228 @offset=552
  [82211.076133] kmem_cache_destroy xfs_log_ticket: Slab cache still has objects

  AND

  [82211.059301] 
=
  [82211.063764] BUG xfs_log_ticket (Tainted: G   OE  ): Objects 
remaining in xfs_log_ticket on kmem_cache_close()
  [82211.067450] 
-
  [82211.067450]
  [82211.070570] Disabling lock debugging due to kernel taint
  [82211.070580] INFO: Slab 0xea0002eb7640 objects=22

[Kernel-packages] [Bug 1680904] Re: zesty unable to handle kernel NULL pointer dereference

2017-08-23 Thread Sam Stenvall

Enable proposed updates from the "Software updater" application, install
whatever updates you get, then disable proposed updates again.

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

Title:
  zesty unable to handle kernel NULL pointer dereference

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Fix Committed
Status in linux-hwe source package in Zesty:
  Confirmed

Bug description:
  Upgraded to zesty about a week ago. Ran into this on latest kernel.
  (during high load, nothing in particular seems to cause it to happen).

  Did not happen with previous (4.10.0.14.16) kernel. Only after update
  to 4.10.0.15.17, has happened about 3 times since then (or other
  crashes), this is the one I could capture.

  kern.log entries below. Let me know if you need anything else from me.

  Thanks!

  Apr  7 11:20:28 doe kernel: [26003.796278] BUG: unable to handle kernel NULL 
pointer dereference at 0018
  Apr  7 11:20:28 doe kernel: [26003.796375] IP: 
gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
  Apr  7 11:20:28 doe kernel: [26003.796404] PGD 0
  Apr  7 11:20:28 doe kernel: [26003.796405]
  Apr  7 11:20:28 doe kernel: [26003.796427] Oops: 0002 [#1] SMP
  Apr  7 11:20:28 doe kernel: [26003.796441] Modules linked in: xt_REDIRECT 
nf_nat_redirect xt_hl scsi_transport_iscsi binfmt_misc veth ip6table_nat 
nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter ip6_tables 
ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_CHECKSUM xt_comment xt_tcpudp 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack 
libcrc32c iptable_mangle iptable_filter ccm rfcomm bridge stp llc cmac bnep 
zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) nls_iso8859_1 
hid_multitouch joydev i2c_designware_platform i2c_designware_core 
snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp 
snd_hda_codec_realtek snd_hda_ext_core snd_soc_sst_match snd_hda_codec_generic 
snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel 
snd_hda_codec snd_hda_core asus_nb_wmi
  Apr  7 11:20:28 doe kernel: [26003.796722]  snd_hwdep asus_wmi sparse_keymap 
snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device 
iwlmvm snd_timer mac80211 intel_rapl x86_pkg_temp_thermal snd intel_powerclamp 
uvcvideo coretemp kvm_intel iwlwifi videobuf2_vmalloc kvm videobuf2_memops 
irqbypass videobuf2_v4l2 intel_cstate videobuf2_core intel_rapl_perf cfg80211 
videodev input_leds serio_raw media shpchp soundcore btusb btrtl hci_uart btbcm 
elan_i2c btqca btintel acpi_als int3403_thermal bluetooth kfifo_buf 
industrialio mac_hid idma64 mei_me virt_dma intel_pch_thermal acpi_pad 
int3400_thermal intel_lpss_pci int3402_thermal mei intel_lpss_acpi 
acpi_thermal_rel processor_thermal_device intel_lpss tpm_crb 
int340x_thermal_zone int3406_thermal intel_soc_dts_iosf asus_wireless 
parport_pc ppdev lp parport ip_tables
  Apr  7 11:20:28 doe kernel: [26003.797026]  x_tables autofs4 algif_skcipher 
af_alg dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 
aesni_intel aes_x86_64 crypto_simd glue_helper cryptd i2c_algo_bit 
drm_kms_helper syscopyarea sysfillrect ahci sysimgblt libahci fb_sys_fops drm 
wmi i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel fjes
  Apr  7 11:20:28 doe kernel: [26003.797142] CPU: 0 PID: 8418 Comm: 
chromium-browse Tainted: P   O4.10.0-15-generic #17-Ubuntu
  Apr  7 11:20:28 doe kernel: [26003.797175] Hardware name: ASUSTeK COMPUTER 
INC. UX305CA/UX305CA, BIOS UX305CA.201 09/11/2015
  Apr  7 11:20:28 doe kernel: [26003.797206] task: 9bbaa201dc00 task.stack: 
c25b5ea8c000
  Apr  7 11:20:28 doe kernel: [26003.797250] RIP: 
0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
  Apr  7 11:20:28 doe kernel: [26003.797279] RSP: 0018:c25b5ea8f880 EFLAGS: 
00010246
  Apr  7 11:20:28 doe kernel: [26003.797299] RAX: 9bba689be580 RBX: 
0003 RCX: 0003
  Apr  7 11:20:28 doe kernel: [26003.797325] RDX:  RSI: 
9bbae7c0a000 RDI: 9bbba0418000
  Apr  7 11:20:28 doe kernel: [26003.797351] RBP: c25b5ea8f8d8 R08: 
 R09: 
  Apr  7 11:20:28 doe kernel: [26003.797378] R10:  R11: 
0041 R12: 9bbb5f00a000
  Apr  7 11:20:28 doe kernel: [26003.797405] R13: 9bbba932bb10 R14: 
fff97000 R15: 8000
  Apr  7 11:20:28 doe kernel: [26003.797440] FS:  7f70bd1df6c0() 
GS:93c0() knlGS:
  Apr  7 11:20:28 doe kernel: [26003.797470] CS:  0010 DS:  ES:  CR0: 
80050033
  Apr  7 11:20:28 doe kernel: [26003.797497] CR2: 0018 CR3: 
00016942 CR4: 003406f0
  Apr  7

[Kernel-packages] [Bug 1706991] Re: ubuntu/rsi driver downlink wifi throughput drops to 5-6 Mbps when BT keyboard is connected

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

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

Title:
  ubuntu/rsi driver downlink wifi throughput drops to 5-6 Mbps when BT
  keyboard is connected

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

Bug description:
  SRU Justification
  =

  [Impact]
  wifi throughput numbers are good when device is running in WLAN only mode.

  In STA+BT+BLE mode, we get expected wifi throughput numbers when BT
  device is not connected. However downlink throughput drops to 5-6 Mbps
  from 35+Mbps as soon as bluetooth keyboard is connected.

  [Fix]
  Enable UAPSD mode with some optimized parameters, so that wifi station can 
get Rx packets buffered by AP efficiently even if radio is shared with bluetooth

  [Test Case]
  Conducted throughput tests and confirmed throughput gets dropped by 60% to 
65% as expected(not more than that) when bluetooth keyboard connected.

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

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

[Kernel-packages] [Bug 1680904] Re: zesty unable to handle kernel NULL pointer dereference

2017-08-23 Thread Ahmad Amr

This bug affects me too.

@Sam Stenvall: How can I install the Xenial kernel from -proposed?

Aug 23 12:31:46 U571T kernel: [40284.307406] BUG: unable to handle kernel NULL 
pointer dereference at 0018
Aug 23 12:31:46 U571T kernel: [40284.307480] IP: 
gen8_ppgtt_alloc_page_directories.isra.38+0x124/0x270 [i915]
Aug 23 12:31:46 U571T kernel: [40284.307518] PGD 0 
Aug 23 12:31:46 U571T kernel: [40284.307518] 
Aug 23 12:31:46 U571T kernel: [40284.307542] Oops: 0002 [#1] SMP
Aug 23 12:31:46 U571T kernel: [40284.307558] Modules linked in: uas usb_storage 
snd_usb_audio snd_usbmidi_lib cdc_ether usbnet r8152 mii hid_generic ccm 
ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user 
xfrm_algo iptable_nat nf_nat_ipv4 br_netfilter bridge stp llc aufs rfcomm 
pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep binfmt_misc 
arc4 iwlmvm snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_codec_generic 
mac80211 intel_rapl x86_pkg_temp_thermal snd_hda_intel intel_powerclamp 
snd_hda_codec coretemp kvm_intel snd_hda_core snd_hwdep kvm iwlwifi snd_pcm 
irqbypass intel_cstate intel_rapl_perf snd_seq_midi snd_seq_midi_event btusb 
cfg80211 btrtl btbcm btintel bluetooth thinkpad_acpi snd_rawmidi input_leds 
joydev serio_raw nvram intel_pch_thermal lpc_ich snd_seq snd_seq_device 
snd_timer
Aug 23 12:31:46 U571T kernel: [40284.307755]  snd mei_me mac_hid mei shpchp 
soundcore ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt 
nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 
nf_log_common xt_LOG xt_multiport xt_limit xt_tcpudp xt_addrtype 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables 
nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat libcrc32c 
nf_conntrack_ftp nf_conntrack iptable_filter ip_tables parport_pc x_tables 
ppdev lp parport autofs4 algif_skcipher af_alg dm_crypt hid_logitech_hidpp 
hid_logitech_dj usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd i2c_algo_bit 
drm_kms_helper psmouse syscopyarea sysfillrect e1000e sysimgblt ahci 
fb_sys_fops libahci drm ptp pps_core wmi fjes
Aug 23 12:31:46 U571T kernel: [40284.307948]  video
Aug 23 12:31:46 U571T kernel: [40284.307957] CPU: 1 PID: 19032 Comm: chrome 
Tainted: G   OE   4.10.0-32-generic #36~16.04.1-Ubuntu
Aug 23 12:31:46 U571T kernel: [40284.307981] Hardware name: LENOVO 
20BS0052AD/20BS0052AD, BIOS N14ET24W (1.02 ) 10/27/2014
Aug 23 12:31:46 U571T kernel: [40284.308003] task: 9868ed62ad00 task.stack: 
b32449664000
Aug 23 12:31:46 U571T kernel: [40284.308037] RIP: 
0010:gen8_ppgtt_alloc_page_directories.isra.38+0x124/0x270 [i915]
Aug 23 12:31:46 U571T kernel: [40284.308058] RSP: 0018:b32449667878 EFLAGS: 
00010246
Aug 23 12:31:46 U571T kernel: [40284.308073] RAX: 98679cbd4a40 RBX: 
0003 RCX: 0003
Aug 23 12:31:46 U571T kernel: [40284.308092] RDX:  RSI: 
9868899c1000 RDI: 98691b7d
Aug 23 12:31:46 U571T kernel: [40284.308111] RBP: b324496678d8 R08: 
0018 R09: 
Aug 23 12:31:46 U571T kernel: [40284.308130] R10:  R11: 
d35144a5ac20 R12: 9868cb05
Aug 23 12:31:46 U571T kernel: [40284.308149] R13: 98679734ef90 R14: 
fffed000 R15: 8000
Aug 23 12:31:46 U571T kernel: [40284.308169] FS:  7f70e7521a80() 
GS:98692dc4() knlGS:
Aug 23 12:31:46 U571T kernel: [40284.308198] CS:  0010 DS:  ES:  CR0: 
80050033
Aug 23 12:31:46 U571T kernel: [40284.308214] CR2: 0018 CR3: 
0001fcb7f000 CR4: 003426e0
Aug 23 12:31:46 U571T kernel: [40284.308234] Call Trace:
Aug 23 12:31:46 U571T kernel: [40284.308258]  
gen8_alloc_va_range_3lvl+0xf3/0x9b0 [i915]
Aug 23 12:31:46 U571T kernel: [40284.308288]  gen8_alloc_va_range+0x23e/0x490 
[i915]
Aug 23 12:31:46 U571T kernel: [40284.308317]  i915_vma_bind+0x6a/0x170 [i915]
Aug 23 12:31:46 U571T kernel: [40284.308349]  __i915_vma_do_pin+0x2a5/0x450 
[i915]
Aug 23 12:31:46 U571T kernel: [40284.308380]  
i915_gem_execbuffer_reserve_vma.isra.31+0x144/0x1b0 [i915]
Aug 23 12:31:46 U571T kernel: [40284.308418]  
i915_gem_execbuffer_reserve.isra.32+0x388/0x3b0 [i915]
Aug 23 12:31:46 U571T kernel: [40284.308453]  
i915_gem_do_execbuffer.isra.38+0x4f7/0x1570 [i915]
Aug 23 12:31:46 U571T kernel: [40284.308475]  ? ___slab_alloc+0x207/0x4b0
Aug 23 12:31:46 U571T kernel: [40284.308492]  ? radix_tree_lookup_slot+0x22/0x50
Aug 23 12:31:46 U571T kernel: [40284.308510]  ? find_get_entry+0x20/0x110
Aug 23 12:31:46 U571T kernel: [40284.308537]  ? 
drm_malloc_gfp.constprop.39+0x3c/0x70 [i915]
Aug 23 12:31:46 U571T kernel: [40284.308569]  i915_gem_execbuffer2+0xa2/0x1e0 
[i915]
Aug 23 12:31:46 U571T kernel: [40284.308593]  drm_ioctl+0x21b/0x4d0 [drm]
Aug 23 12:31:46 U571T kernel: [40284.308621]  ? i915_gem_execbuffer+0x310/0x310 
[i915]
Aug 23 12:31:46

[Kernel-packages] [Bug 1701222] Re: [Hyper-V] LIS daemons fail to start after disable/re-enable VM integration services

2017-08-23 Thread Ionut Lenghel

I have checked back to 4.2.0-16. It seems that 4.4.0-2 is the last
kernel where the daemons remain running even if integration services are
being disabled. Starting with 4.4.0-3 the daemons stop if the
integration services are disabled, but do not automatically start if the
integrations services are being enabled again.

I have also checked the content of linux-cloud-tools-common package for
the above mentioned kernels, and it seems there is no difference between
the two packages (as shown by the md5sum file).

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

Title:
  [Hyper-V] LIS daemons fail to start after disable/re-enable VM
  integration services

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

Bug description:
  Issue description: Hyper-V daemons fail to start after disable/re-
  enable VM integration services.

  Platform: host independent
  Affected daemons - KVP, FCOPY and VSS.

  Distribution name and release: Ubuntu 16.04, Ubuntu 17.04
  Kernel version: 4.11.0-rc7-next-20170421 (for Ubuntu 16.04), 
4.10.0-19-generic (for Ubuntu 17.04)

  Repro rate: 100%

  Steps to reproduce:
  1.Start VM with Guest Services enabled (FCopy daemon starts automatically)
  2.Go to File > Settings > Integration Services, uncheck Guest Services 
and apply (FCopy daemon will stop at this point)
  3.Re-enable Guest Services from VM Settings (Fcopy daemon is not running).
  This is the issue. systemd monitors for the service and if we have the hook 
for the Guest Service, it tries to start the daemon again.
  systemd attempt to start any of the LIS daemons will fail, but manually 
executing the daemon binary, it will start the daemon.

  Additional Info:
  - the steps above can be repro'd with KVP / Data Exchange integration service 
as well.
  - Manually starting hv_fcopy_daemon works fine.
  - other distros (RHEL) does not have this behavior, the LIS daemons are 
started automatically by systemd once we re-enable the integration service.

  On the upstream kernel and the upstream hv daemons, these messages are 
recorded in syslog, once we re-enable the Guest service:
  HV_FCOPY: pread failed: Bad file descriptor
  systemd[1]: hv-fcopy-daemon.service: Main process exited, code=exited, 
status=1/FAILURE
  systemd[1]: hv-fcopy-daemon.service: Unit entered failed state.
  systemd[1]: hv-fcopy-daemon.service: Failed with result 'exit-code'.

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

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

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

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1712508

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

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

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

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

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

Title:
  Disappearing screen and flickering after upgrade to 16.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have two Lenovo T410s that I upgraded from 14.04 to 16.04.
  Since then, one is working fine while the other shows mainly an ever 
disappearing screen and flickering.

  I have asked here: 
https://askubuntu.com/questions/947233/i-upgraded-from-kubuntu-14-04-lts-to-16-04-lts-and-now-my-screen-shows-up-and-di?noredirect=1#comment1506995_947233
  I also found I am not the only one: 
https://askubuntu.com/questions/927407/flickering-screen-with-intel-graphics-on-ubuntu-17-04?noredirect=1#comment1507937_927407
  The latter has tried pretty much that could be tried already, to no avail.

  I think that I can help with this problem, since my two T410s are
  identical in hard- and software, including BIOS, except that one is a
  type 2924 (with NVIDIA-card, though disabled in the BIOS), and the
  other one is a 2904 (without NVIDIA card).

  I have checked for differences at boot time and found DMAR as major 
difference:
  T410s, 2924: [ 0.335616] DMAR: Disabling batched IOTLB flush on Ironlake
  T410s, 2904: [ 0.355681] DMAR: BIOS has allocated no shadow GTT; disabling 
IOMMU for graphics 

  Should this be initially at the root of the problem, I'd consider the
  kernel package as responsible, therefore I marked it as above.

  The outputs of lspci -k | grep -EA3 'VGA|3D|Display' are identical to
  the point.

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

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

[Kernel-packages] [Bug 1712508] [NEW] Disappearing screen and flickering after upgrade to 16.04

2017-08-23 Thread udippel

Public bug reported:

I have two Lenovo T410s that I upgraded from 14.04 to 16.04.
Since then, one is working fine while the other shows mainly an ever 
disappearing screen and flickering.

I have asked here: 
https://askubuntu.com/questions/947233/i-upgraded-from-kubuntu-14-04-lts-to-16-04-lts-and-now-my-screen-shows-up-and-di?noredirect=1#comment1506995_947233
I also found I am not the only one: 
https://askubuntu.com/questions/927407/flickering-screen-with-intel-graphics-on-ubuntu-17-04?noredirect=1#comment1507937_927407
The latter has tried pretty much that could be tried already, to no avail.

I think that I can help with this problem, since my two T410s are
identical in hard- and software, including BIOS, except that one is a
type 2924 (with NVIDIA-card, though disabled in the BIOS), and the other
one is a 2904 (without NVIDIA card).

I have checked for differences at boot time and found DMAR as major difference:
T410s, 2924: [ 0.335616] DMAR: Disabling batched IOTLB flush on Ironlake
T410s, 2904: [ 0.355681] DMAR: BIOS has allocated no shadow GTT; disabling 
IOMMU for graphics 

Should this be initially at the root of the problem, I'd consider the
kernel package as responsible, therefore I marked it as above.

The outputs of lspci -k | grep -EA3 'VGA|3D|Display' are identical to
the point.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: 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/1712508

Title:
  Disappearing screen and flickering after upgrade to 16.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have two Lenovo T410s that I upgraded from 14.04 to 16.04.
  Since then, one is working fine while the other shows mainly an ever 
disappearing screen and flickering.

  I have asked here: 
https://askubuntu.com/questions/947233/i-upgraded-from-kubuntu-14-04-lts-to-16-04-lts-and-now-my-screen-shows-up-and-di?noredirect=1#comment1506995_947233
  I also found I am not the only one: 
https://askubuntu.com/questions/927407/flickering-screen-with-intel-graphics-on-ubuntu-17-04?noredirect=1#comment1507937_927407
  The latter has tried pretty much that could be tried already, to no avail.

  I think that I can help with this problem, since my two T410s are
  identical in hard- and software, including BIOS, except that one is a
  type 2924 (with NVIDIA-card, though disabled in the BIOS), and the
  other one is a 2904 (without NVIDIA card).

  I have checked for differences at boot time and found DMAR as major 
difference:
  T410s, 2924: [ 0.335616] DMAR: Disabling batched IOTLB flush on Ironlake
  T410s, 2904: [ 0.355681] DMAR: BIOS has allocated no shadow GTT; disabling 
IOMMU for graphics 

  Should this be initially at the root of the problem, I'd consider the
  kernel package as responsible, therefore I marked it as above.

  The outputs of lspci -k | grep -EA3 'VGA|3D|Display' are identical to
  the point.

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

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

[Kernel-packages] [Bug 1704363] Re: Add firmware for Redpine 9113 chipset

** Tags added: verification-done-xenial

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

Title:
  Add firmware for Redpine 9113 chipset

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Xenial:
  Fix Committed

Bug description:
  SRU Justification

  Impact: The redpine driver in xenial has been updated, and a
  corresponding firmware update is also required.

  Fix: Add new firmware files.

  Test case: Test with affected hw and with a kernel which has the
  driver update.

  Regression potential: These are new files used by a single driver, so
  no regressions are possible outside of that driver.

  ---

  Latest firmware images provided by Redpine in 1.2 production release
  are updated to ubuntu's linux-firmware.git

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

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

[Kernel-packages] [Bug 1709300] Re: linux-aws: 4.4.0-1032.41 -proposed tracker

2017-08-23 Thread Brad Figg

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

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

Title:
  linux-aws: 4.4.0-1032.41 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1709296
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1712495] Re: Please sponsor bluez 5.46-0ubuntu2 to artful

2017-08-23 Thread Daniel van Vugt

** Patch added: "bluez_5.46-0ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1712495/+attachment/4937338/+files/bluez_5.46-0ubuntu2.debdiff

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

Title:
  Please sponsor bluez 5.46-0ubuntu2 to artful

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  Please sponsor bluez 5.46-0ubuntu2 to artful

  This fixes a crash of zyga's that's been discussed a lot in the past
  but never opened as an official bug report. It has however already
  been fixed upstream and will be included in 5.47.

  It's not yet clear exactly which existing LP bug/error reports this
  will resolve. We'll find out later by tracking errors.ubuntu.com (I
  suspect it might resolve a couple).

  If you need a proper bug report then please ask
  zygmunt.kryni...@canonical.com

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

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

[Kernel-packages] [Bug 1712495] [NEW] Please sponsor bluez 5.46-0ubuntu2 to artful

2017-08-23 Thread Daniel van Vugt

Public bug reported:

Please sponsor bluez 5.46-0ubuntu2 to artful

This fixes a crash of zyga's that's been discussed a lot in the past but
never opened as an official bug report. It has however already been
fixed upstream and will be included in 5.47.

It's not yet clear exactly which existing LP bug/error reports this will
resolve. We'll find out later by tracking errors.ubuntu.com (I suspect
it might resolve a couple).

If you need a proper bug report then please ask
zygmunt.kryni...@canonical.com

** Affects: bluez (Ubuntu)
Importance: High
Assignee: Daniel van Vugt (vanvugt)
Status: In Progress

** Tags: artful

** Attachment added: "bluez_5.46-0ubuntu2.debdiff"

https://bugs.launchpad.net/bugs/1712495/+attachment/4937330/+files/bluez_5.46-0ubuntu2.debdiff

** Tags added: artful

** Description changed:

Please sponsor bluez 5.46-0ubuntu2 to artful

This fixes a crash of zyga's that's been discussed a lot in the past but
- never opened as an official bug report.
+ never opened as an official bug report. It has however already been
+ fixed upstream and will be included in 5.47.

It's not yet clear exactly which existing bug/error reports this will
resolve. We'll find out later by tracking errors.ubuntu.com (I suspect
it might resolve a couple).

If you need a proper bug report then please ask
zygmunt.kryni...@canonical.com

** Description changed:

Please sponsor bluez 5.46-0ubuntu2 to artful

This fixes a crash of zyga's that's been discussed a lot in the past but
never opened as an official bug report. It has however already been
fixed upstream and will be included in 5.47.

- It's not yet clear exactly which existing bug/error reports this will
+ It's not yet clear exactly which existing LP bug/error reports this will
resolve. We'll find out later by tracking errors.ubuntu.com (I suspect
it might resolve a couple).

If you need a proper bug report then please ask
zygmunt.kryni...@canonical.com

** Attachment removed: "bluez_5.46-0ubuntu2.debdiff"

https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1712495/+attachment/4937330/+files/bluez_5.46-0ubuntu2.debdiff

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

Title:
Please sponsor bluez 5.46-0ubuntu2 to artful

Status in bluez package in Ubuntu:
In Progress

Bug description:
Please sponsor bluez 5.46-0ubuntu2 to artful

This fixes a crash of zyga's that's been discussed a lot in the past
but never opened as an official bug report. It has however already
been fixed upstream and will be included in 5.47.

It's not yet clear exactly which existing LP bug/error reports this
will resolve. We'll find out later by tracking errors.ubuntu.com (I
suspect it might resolve a couple).

If you need a proper bug report then please ask
zygmunt.kryni...@canonical.com

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

[Kernel-packages] [Bug 1712481] Re: HID: multitouch: Support ALPS PTP Stick and Touchpad devices