[Kernel-packages] [Bug 1691045] Re: PowerPC: Pstore dump for powerpc is broken

2017-07-17 Thread Joseph Salisbury 
** Changed in: ubuntu-power-systems
   Status: New => Fix Released

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

Title:
  PowerPC: Pstore dump for powerpc is broken

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

Bug description:
  ---Problem Description---
  Pstore write is broken for PowerPC. On panic, kernel doesn't write mesg to 
/fs/pstore/dmesg*
  (Entry doesn't gets created at all)
   
  Contact Information = Ankit Kumar/kumar.ankit...@in.ibm.com 
   
  ---uname output---
  Linux seedlp2 4.10.0-15-generic #17-Ubuntu SMP Fri Mar 24 17:50:37 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = lpar 
   
  Write to nvram failed
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  1. Checked kdump kernel is loaded.
  2. Triggered system crash
  # echo c > /proc/sysrq-trigger

  3. /sys/fs/pstore/dmesg* doesn't gets created

  This issue can be reproduced after commit c950fd6f201

  c950fd6f201 - pstore: Split pstore fragile flags

  It introduces  PSTORE_FLAGS_DMESG, which is not set for PowerPC.

  
  Please include below commit 041939c1ec5 as this fixes this issue.

  commit 041939c1ec54208b42f5cd819209173d52a29d34
  Author: Ankit Kumar 
  Date:   Thu Apr 27 17:03:13 2017 +0530

  pstore: Fix flags to enable dumps on powerpc
  
  After commit c950fd6f201a kernel registers pstore write based on flag set.
  Pstore write for powerpc is broken as flags(PSTORE_FLAGS_DMESG) is not 
set for
  powerpc architecture. On panic, kernel doesn't write message to
  /fs/pstore/dmesg*(Entry doesn't gets created at all).
  
  This patch enables pstore write for powerpc architecture by setting
  PSTORE_FLAGS_DMESG flag.
  
  Fixes: c950fd6f201a ("pstore: Split pstore fragile flags")
  Cc: sta...@vger.kernel.org # v4.9+
  Signed-off-by: Ankit Kumar 
  Signed-off-by: Kees Cook 

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

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

[Kernel-packages] [Bug 1691045] Re: PowerPC: Pstore dump for powerpc is broken

2017-06-30 Thread Launchpad Bug Tracker 
This bug was fixed in the package linux - 4.10.0-26.30

---
linux (4.10.0-26.30) zesty; urgency=low

  * linux: 4.10.0-26.30 -proposed tracker (LP: #1700528)

  * CVE-2017-1000364
- Revert "UBUNTU: SAUCE: mm: Only expand stack if guard area is hit"
- Revert "mm: do not collapse stack gap into THP"
- Revert "mm: enlarge stack guard gap"
- mm: larger stack guard gap, between vmas
- mm: fix new crash in unmapped_area_topdown()
- Allow stack to grow up to address space limit

linux (4.10.0-25.29) zesty; urgency=low

  * linux: 4.10.0-25.29 -proposed tracker (LP: #1699028)

  * CVE-2017-1000364
- SAUCE: mm: Only expand stack if guard area is hit

  * CVE-2017-9074
- ipv6: Prevent overrun when parsing v6 header options
- ipv6: Check ip6_find_1stfragopt() return value properly.

  * [Zesty] QDF2400 ARM64 server - NMI watchdog: BUG: soft lockup - CPU#8 stuck
for 22s!  (LP: #1680549)
- iommu/dma: Stop getting dma_32bit_pfn wrong
- iommu/dma: Implement PCI allocation optimisation
- iommu/dma: Convert to address-based allocation
- iommu/dma: Clean up MSI IOVA allocation
- iommu/dma: Plumb in the per-CPU IOVA caches
- iommu/iova: Fix underflow bug in __alloc_and_insert_iova_range

  * Zesty update to 4.10.17 stable release (LP: #1692898)
- xen: adjust early dom0 p2m handling to xen hypervisor behavior
- target: Fix compare_and_write_callback handling for non GOOD status
- target/fileio: Fix zero-length READ and WRITE handling
- iscsi-target: Set session_fall_back_to_erl0 when forcing reinstatement
- usb: xhci: bInterval quirk for TI TUSB73x0
- usb: host: xhci: print correct command ring address
- USB: serial: ftdi_sio: add device ID for Microsemi/Arrow SF2PLUS Dev Kit
- USB: Proper handling of Race Condition when two USB class drivers try to
  call init_usb_class simultaneously
- USB: Revert "cdc-wdm: fix "out-of-sync" due to missing notifications"
- staging: vt6656: use off stack for in buffer USB transfers.
- staging: vt6656: use off stack for out buffer USB transfers.
- staging: gdm724x: gdm_mux: fix use-after-free on module unload
- staging: wilc1000: Fix problem with wrong vif index
- staging: comedi: jr3_pci: fix possible null pointer dereference
- staging: comedi: jr3_pci: cope with jiffies wraparound
- usb: misc: add missing continue in switch
- usb: gadget: legacy gadgets are optional
- usb: Make sure usb/phy/of gets built-in
- usb: hub: Fix error loop seen after hub communication errors
- usb: hub: Do not attempt to autosuspend disconnected devices
- x86/boot: Fix BSS corruption/overwrite bug in early x86 kernel startup
- selftests/x86/ldt_gdt_32: Work around a glibc sigaction() bug
- x86, pmem: Fix cache flushing for iovec write < 8 bytes
- um: Fix PTRACE_POKEUSER on x86_64
- perf/x86: Fix Broadwell-EP DRAM RAPL events
- KVM: x86: fix user triggerable warning in kvm_apic_accept_events()
- KVM: arm/arm64: fix races in kvm_psci_vcpu_on
- arm64: KVM: Fix decoding of Rt/Rt2 when trapping AArch32 CP accesses
- block: fix blk_integrity_register to use template's interval_exp if not 0
- crypto: s5p-sss - Close possible race for completed requests
- crypto: algif_aead - Require setkey before accept(2)
- crypto: ccp - Use only the relevant interrupt bits
- crypto: ccp - Disable interrupts early on unload
- crypto: ccp - Change ISR handler method for a v3 CCP
- crypto: ccp - Change ISR handler method for a v5 CCP
- dm crypt: rewrite (wipe) key in crypto layer using random data
- dm era: save spacemap metadata root after the pre-commit
- dm rq: check blk_mq_register_dev() return value in
  dm_mq_init_request_queue()
- dm thin: fix a memory leak when passing discard bio down
- vfio/type1: Remove locked page accounting workqueue
- iov_iter: don't revert iov buffer if csum error
- IB/core: Fix sysfs registration error flow
- IB/core: For multicast functions, verify that LIDs are multicast LIDs
- IB/IPoIB: ibX: failed to create mcg debug file
- IB/mlx4: Fix ib device initialization error flow
- IB/mlx4: Reduce SRIOV multicast cleanup warning message to debug level
- IB/hfi1: Prevent kernel QP post send hard lockups
- perf auxtrace: Fix no_size logic in addr_filter__resolve_kernel_syms()
- perf annotate s390: Fix perf annotate error -95 (4.10 regression)
- perf annotate s390: Implement jump types for perf annotate
- jbd2: fix dbench4 performance regression for 'nobarrier' mounts
- ext4: evict inline data when writing to memory map
- orangefs: fix bounds check for listxattr
- orangefs: clean up oversize xattr validation
- orangefs: do not set getattr_time on orangefs_lookup
- orangefs: do not check possibly stale size on truncate
- fs/xattr.c: zero out memory copied to userspace in getxattr
- ceph: fix memory

[Kernel-packages] [Bug 1691045] Re: PowerPC: Pstore dump for powerpc is broken

2017-06-29 Thread Launchpad Bug Tracker 
This bug was fixed in the package linux - 4.10.0-26.30

---
linux (4.10.0-26.30) zesty; urgency=low

  * linux: 4.10.0-26.30 -proposed tracker (LP: #1700528)

  * CVE-2017-1000364
- Revert "UBUNTU: SAUCE: mm: Only expand stack if guard area is hit"
- Revert "mm: do not collapse stack gap into THP"
- Revert "mm: enlarge stack guard gap"
- mm: larger stack guard gap, between vmas
- mm: fix new crash in unmapped_area_topdown()
- Allow stack to grow up to address space limit

linux (4.10.0-25.29) zesty; urgency=low

  * linux: 4.10.0-25.29 -proposed tracker (LP: #1699028)

  * CVE-2017-1000364
- SAUCE: mm: Only expand stack if guard area is hit

  * CVE-2017-9074
- ipv6: Prevent overrun when parsing v6 header options
- ipv6: Check ip6_find_1stfragopt() return value properly.

  * [Zesty] QDF2400 ARM64 server - NMI watchdog: BUG: soft lockup - CPU#8 stuck
for 22s!  (LP: #1680549)
- iommu/dma: Stop getting dma_32bit_pfn wrong
- iommu/dma: Implement PCI allocation optimisation
- iommu/dma: Convert to address-based allocation
- iommu/dma: Clean up MSI IOVA allocation
- iommu/dma: Plumb in the per-CPU IOVA caches
- iommu/iova: Fix underflow bug in __alloc_and_insert_iova_range

  * Zesty update to 4.10.17 stable release (LP: #1692898)
- xen: adjust early dom0 p2m handling to xen hypervisor behavior
- target: Fix compare_and_write_callback handling for non GOOD status
- target/fileio: Fix zero-length READ and WRITE handling
- iscsi-target: Set session_fall_back_to_erl0 when forcing reinstatement
- usb: xhci: bInterval quirk for TI TUSB73x0
- usb: host: xhci: print correct command ring address
- USB: serial: ftdi_sio: add device ID for Microsemi/Arrow SF2PLUS Dev Kit
- USB: Proper handling of Race Condition when two USB class drivers try to
  call init_usb_class simultaneously
- USB: Revert "cdc-wdm: fix "out-of-sync" due to missing notifications"
- staging: vt6656: use off stack for in buffer USB transfers.
- staging: vt6656: use off stack for out buffer USB transfers.
- staging: gdm724x: gdm_mux: fix use-after-free on module unload
- staging: wilc1000: Fix problem with wrong vif index
- staging: comedi: jr3_pci: fix possible null pointer dereference
- staging: comedi: jr3_pci: cope with jiffies wraparound
- usb: misc: add missing continue in switch
- usb: gadget: legacy gadgets are optional
- usb: Make sure usb/phy/of gets built-in
- usb: hub: Fix error loop seen after hub communication errors
- usb: hub: Do not attempt to autosuspend disconnected devices
- x86/boot: Fix BSS corruption/overwrite bug in early x86 kernel startup
- selftests/x86/ldt_gdt_32: Work around a glibc sigaction() bug
- x86, pmem: Fix cache flushing for iovec write < 8 bytes
- um: Fix PTRACE_POKEUSER on x86_64
- perf/x86: Fix Broadwell-EP DRAM RAPL events
- KVM: x86: fix user triggerable warning in kvm_apic_accept_events()
- KVM: arm/arm64: fix races in kvm_psci_vcpu_on
- arm64: KVM: Fix decoding of Rt/Rt2 when trapping AArch32 CP accesses
- block: fix blk_integrity_register to use template's interval_exp if not 0
- crypto: s5p-sss - Close possible race for completed requests
- crypto: algif_aead - Require setkey before accept(2)
- crypto: ccp - Use only the relevant interrupt bits
- crypto: ccp - Disable interrupts early on unload
- crypto: ccp - Change ISR handler method for a v3 CCP
- crypto: ccp - Change ISR handler method for a v5 CCP
- dm crypt: rewrite (wipe) key in crypto layer using random data
- dm era: save spacemap metadata root after the pre-commit
- dm rq: check blk_mq_register_dev() return value in
  dm_mq_init_request_queue()
- dm thin: fix a memory leak when passing discard bio down
- vfio/type1: Remove locked page accounting workqueue
- iov_iter: don't revert iov buffer if csum error
- IB/core: Fix sysfs registration error flow
- IB/core: For multicast functions, verify that LIDs are multicast LIDs
- IB/IPoIB: ibX: failed to create mcg debug file
- IB/mlx4: Fix ib device initialization error flow
- IB/mlx4: Reduce SRIOV multicast cleanup warning message to debug level
- IB/hfi1: Prevent kernel QP post send hard lockups
- perf auxtrace: Fix no_size logic in addr_filter__resolve_kernel_syms()
- perf annotate s390: Fix perf annotate error -95 (4.10 regression)
- perf annotate s390: Implement jump types for perf annotate
- jbd2: fix dbench4 performance regression for 'nobarrier' mounts
- ext4: evict inline data when writing to memory map
- orangefs: fix bounds check for listxattr
- orangefs: clean up oversize xattr validation
- orangefs: do not set getattr_time on orangefs_lookup
- orangefs: do not check possibly stale size on truncate
- fs/xattr.c: zero out memory copied to userspace in getxattr
- ceph: fix memory

[Kernel-packages] [Bug 1691045] Re: PowerPC: Pstore dump for powerpc is broken

2017-06-15 Thread bugproxy 
--- Comment From kumar.ankit...@in.ibm.com 2017-06-15 04:13 EDT---
Above patch is present as part of :
1. Ubuntu-17.04 as well as
2. Ubuntu 16.04.2 LTS

Verified its working.
It's working as expected.

Hence moving status from verification-needed-zesty to verification-done-
zesty

.
~Ankit

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

Title:
  PowerPC: Pstore dump for powerpc is broken

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

Bug description:
  ---Problem Description---
  Pstore write is broken for PowerPC. On panic, kernel doesn't write mesg to 
/fs/pstore/dmesg*
  (Entry doesn't gets created at all)
   
  Contact Information = Ankit Kumar/kumar.ankit...@in.ibm.com 
   
  ---uname output---
  Linux seedlp2 4.10.0-15-generic #17-Ubuntu SMP Fri Mar 24 17:50:37 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = lpar 
   
  Write to nvram failed
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  1. Checked kdump kernel is loaded.
  2. Triggered system crash
  # echo c > /proc/sysrq-trigger

  3. /sys/fs/pstore/dmesg* doesn't gets created

  This issue can be reproduced after commit c950fd6f201

  c950fd6f201 - pstore: Split pstore fragile flags

  It introduces  PSTORE_FLAGS_DMESG, which is not set for PowerPC.

  
  Please include below commit 041939c1ec5 as this fixes this issue.

  commit 041939c1ec54208b42f5cd819209173d52a29d34
  Author: Ankit Kumar 
  Date:   Thu Apr 27 17:03:13 2017 +0530

  pstore: Fix flags to enable dumps on powerpc
  
  After commit c950fd6f201a kernel registers pstore write based on flag set.
  Pstore write for powerpc is broken as flags(PSTORE_FLAGS_DMESG) is not 
set for
  powerpc architecture. On panic, kernel doesn't write message to
  /fs/pstore/dmesg*(Entry doesn't gets created at all).
  
  This patch enables pstore write for powerpc architecture by setting
  PSTORE_FLAGS_DMESG flag.
  
  Fixes: c950fd6f201a ("pstore: Split pstore fragile flags")
  Cc: sta...@vger.kernel.org # v4.9+
  Signed-off-by: Ankit Kumar 
  Signed-off-by: Kees Cook 

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

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

[Kernel-packages] [Bug 1691045] Re: PowerPC: Pstore dump for powerpc is broken

2017-06-14 Thread Kleber Sacilotto de Souza 
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1691045

Title:
  PowerPC: Pstore dump for powerpc is broken

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

Bug description:
  ---Problem Description---
  Pstore write is broken for PowerPC. On panic, kernel doesn't write mesg to 
/fs/pstore/dmesg*
  (Entry doesn't gets created at all)
   
  Contact Information = Ankit Kumar/kumar.ankit...@in.ibm.com 
   
  ---uname output---
  Linux seedlp2 4.10.0-15-generic #17-Ubuntu SMP Fri Mar 24 17:50:37 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = lpar 
   
  Write to nvram failed
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  1. Checked kdump kernel is loaded.
  2. Triggered system crash
  # echo c > /proc/sysrq-trigger

  3. /sys/fs/pstore/dmesg* doesn't gets created

  This issue can be reproduced after commit c950fd6f201

  c950fd6f201 - pstore: Split pstore fragile flags

  It introduces  PSTORE_FLAGS_DMESG, which is not set for PowerPC.

  
  Please include below commit 041939c1ec5 as this fixes this issue.

  commit 041939c1ec54208b42f5cd819209173d52a29d34
  Author: Ankit Kumar 
  Date:   Thu Apr 27 17:03:13 2017 +0530

  pstore: Fix flags to enable dumps on powerpc
  
  After commit c950fd6f201a kernel registers pstore write based on flag set.
  Pstore write for powerpc is broken as flags(PSTORE_FLAGS_DMESG) is not 
set for
  powerpc architecture. On panic, kernel doesn't write message to
  /fs/pstore/dmesg*(Entry doesn't gets created at all).
  
  This patch enables pstore write for powerpc architecture by setting
  PSTORE_FLAGS_DMESG flag.
  
  Fixes: c950fd6f201a ("pstore: Split pstore fragile flags")
  Cc: sta...@vger.kernel.org # v4.9+
  Signed-off-by: Ankit Kumar 
  Signed-off-by: Kees Cook 

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

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

[Kernel-packages] [Bug 1691045] Re: PowerPC: Pstore dump for powerpc is broken

2017-06-06 Thread Kleber Sacilotto de Souza 
** 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/1691045

Title:
  PowerPC: Pstore dump for powerpc is broken

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

Bug description:
  ---Problem Description---
  Pstore write is broken for PowerPC. On panic, kernel doesn't write mesg to 
/fs/pstore/dmesg*
  (Entry doesn't gets created at all)
   
  Contact Information = Ankit Kumar/kumar.ankit...@in.ibm.com 
   
  ---uname output---
  Linux seedlp2 4.10.0-15-generic #17-Ubuntu SMP Fri Mar 24 17:50:37 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = lpar 
   
  Write to nvram failed
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  1. Checked kdump kernel is loaded.
  2. Triggered system crash
  # echo c > /proc/sysrq-trigger

  3. /sys/fs/pstore/dmesg* doesn't gets created

  This issue can be reproduced after commit c950fd6f201

  c950fd6f201 - pstore: Split pstore fragile flags

  It introduces  PSTORE_FLAGS_DMESG, which is not set for PowerPC.

  
  Please include below commit 041939c1ec5 as this fixes this issue.

  commit 041939c1ec54208b42f5cd819209173d52a29d34
  Author: Ankit Kumar 
  Date:   Thu Apr 27 17:03:13 2017 +0530

  pstore: Fix flags to enable dumps on powerpc
  
  After commit c950fd6f201a kernel registers pstore write based on flag set.
  Pstore write for powerpc is broken as flags(PSTORE_FLAGS_DMESG) is not 
set for
  powerpc architecture. On panic, kernel doesn't write message to
  /fs/pstore/dmesg*(Entry doesn't gets created at all).
  
  This patch enables pstore write for powerpc architecture by setting
  PSTORE_FLAGS_DMESG flag.
  
  Fixes: c950fd6f201a ("pstore: Split pstore fragile flags")
  Cc: sta...@vger.kernel.org # v4.9+
  Signed-off-by: Ankit Kumar 
  Signed-off-by: Kees Cook 

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

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

[Kernel-packages] [Bug 1691045] Re: PowerPC: Pstore dump for powerpc is broken

2017-06-02 Thread Joseph Salisbury 
** Also affects: linux (Ubuntu Artful)
   Importance: Medium
 Assignee: Joseph Salisbury (jsalisbury)
   Status: In Progress

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

Title:
  PowerPC: Pstore dump for powerpc is broken

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

Bug description:
  ---Problem Description---
  Pstore write is broken for PowerPC. On panic, kernel doesn't write mesg to 
/fs/pstore/dmesg*
  (Entry doesn't gets created at all)
   
  Contact Information = Ankit Kumar/kumar.ankit...@in.ibm.com 
   
  ---uname output---
  Linux seedlp2 4.10.0-15-generic #17-Ubuntu SMP Fri Mar 24 17:50:37 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = lpar 
   
  Write to nvram failed
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  1. Checked kdump kernel is loaded.
  2. Triggered system crash
  # echo c > /proc/sysrq-trigger

  3. /sys/fs/pstore/dmesg* doesn't gets created

  This issue can be reproduced after commit c950fd6f201

  c950fd6f201 - pstore: Split pstore fragile flags

  It introduces  PSTORE_FLAGS_DMESG, which is not set for PowerPC.

  
  Please include below commit 041939c1ec5 as this fixes this issue.

  commit 041939c1ec54208b42f5cd819209173d52a29d34
  Author: Ankit Kumar 
  Date:   Thu Apr 27 17:03:13 2017 +0530

  pstore: Fix flags to enable dumps on powerpc
  
  After commit c950fd6f201a kernel registers pstore write based on flag set.
  Pstore write for powerpc is broken as flags(PSTORE_FLAGS_DMESG) is not 
set for
  powerpc architecture. On panic, kernel doesn't write message to
  /fs/pstore/dmesg*(Entry doesn't gets created at all).
  
  This patch enables pstore write for powerpc architecture by setting
  PSTORE_FLAGS_DMESG flag.
  
  Fixes: c950fd6f201a ("pstore: Split pstore fragile flags")
  Cc: sta...@vger.kernel.org # v4.9+
  Signed-off-by: Ankit Kumar 
  Signed-off-by: Kees Cook 

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

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

[Kernel-packages] [Bug 1691045] Re: PowerPC: Pstore dump for powerpc is broken

2017-06-01 Thread Manoj Iyer 
** Tags added: ubuntu-17.04

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

Title:
  PowerPC: Pstore dump for powerpc is broken

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

Bug description:
  ---Problem Description---
  Pstore write is broken for PowerPC. On panic, kernel doesn't write mesg to 
/fs/pstore/dmesg*
  (Entry doesn't gets created at all)
   
  Contact Information = Ankit Kumar/kumar.ankit...@in.ibm.com 
   
  ---uname output---
  Linux seedlp2 4.10.0-15-generic #17-Ubuntu SMP Fri Mar 24 17:50:37 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = lpar 
   
  Write to nvram failed
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  1. Checked kdump kernel is loaded.
  2. Triggered system crash
  # echo c > /proc/sysrq-trigger

  3. /sys/fs/pstore/dmesg* doesn't gets created

  This issue can be reproduced after commit c950fd6f201

  c950fd6f201 - pstore: Split pstore fragile flags

  It introduces  PSTORE_FLAGS_DMESG, which is not set for PowerPC.

  
  Please include below commit 041939c1ec5 as this fixes this issue.

  commit 041939c1ec54208b42f5cd819209173d52a29d34
  Author: Ankit Kumar 
  Date:   Thu Apr 27 17:03:13 2017 +0530

  pstore: Fix flags to enable dumps on powerpc
  
  After commit c950fd6f201a kernel registers pstore write based on flag set.
  Pstore write for powerpc is broken as flags(PSTORE_FLAGS_DMESG) is not 
set for
  powerpc architecture. On panic, kernel doesn't write message to
  /fs/pstore/dmesg*(Entry doesn't gets created at all).
  
  This patch enables pstore write for powerpc architecture by setting
  PSTORE_FLAGS_DMESG flag.
  
  Fixes: c950fd6f201a ("pstore: Split pstore fragile flags")
  Cc: sta...@vger.kernel.org # v4.9+
  Signed-off-by: Ankit Kumar 
  Signed-off-by: Kees Cook 

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

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

[Kernel-packages] [Bug 1691045] Re: PowerPC: Pstore dump for powerpc is broken

2017-05-26 Thread Joseph Salisbury 
Yes, the 16.04.03 kernel is based off the 4.10 Zesty kernel, so it will
get the patch.  Did you happen to have a chance to test the kernel
posted in comment #2?

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

Title:
  PowerPC: Pstore dump for powerpc is broken

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

Bug description:
  ---Problem Description---
  Pstore write is broken for PowerPC. On panic, kernel doesn't write mesg to 
/fs/pstore/dmesg*
  (Entry doesn't gets created at all)
   
  Contact Information = Ankit Kumar/kumar.ankit...@in.ibm.com 
   
  ---uname output---
  Linux seedlp2 4.10.0-15-generic #17-Ubuntu SMP Fri Mar 24 17:50:37 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = lpar 
   
  Write to nvram failed
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  1. Checked kdump kernel is loaded.
  2. Triggered system crash
  # echo c > /proc/sysrq-trigger

  3. /sys/fs/pstore/dmesg* doesn't gets created

  This issue can be reproduced after commit c950fd6f201

  c950fd6f201 - pstore: Split pstore fragile flags

  It introduces  PSTORE_FLAGS_DMESG, which is not set for PowerPC.

  
  Please include below commit 041939c1ec5 as this fixes this issue.

  commit 041939c1ec54208b42f5cd819209173d52a29d34
  Author: Ankit Kumar 
  Date:   Thu Apr 27 17:03:13 2017 +0530

  pstore: Fix flags to enable dumps on powerpc
  
  After commit c950fd6f201a kernel registers pstore write based on flag set.
  Pstore write for powerpc is broken as flags(PSTORE_FLAGS_DMESG) is not 
set for
  powerpc architecture. On panic, kernel doesn't write message to
  /fs/pstore/dmesg*(Entry doesn't gets created at all).
  
  This patch enables pstore write for powerpc architecture by setting
  PSTORE_FLAGS_DMESG flag.
  
  Fixes: c950fd6f201a ("pstore: Split pstore fragile flags")
  Cc: sta...@vger.kernel.org # v4.9+
  Signed-off-by: Ankit Kumar 
  Signed-off-by: Kees Cook 

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

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

[Kernel-packages] [Bug 1691045] Re: PowerPC: Pstore dump for powerpc is broken

2017-05-17 Thread Joseph Salisbury 
I built a Zesty test kernel with a cherry pick of commit 041939c1ec54.
The test kernel can be downloaded from:

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

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

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

Title:
  PowerPC: Pstore dump for powerpc is broken

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

Bug description:
  ---Problem Description---
  Pstore write is broken for PowerPC. On panic, kernel doesn't write mesg to 
/fs/pstore/dmesg*
  (Entry doesn't gets created at all)
   
  Contact Information = Ankit Kumar/kumar.ankit...@in.ibm.com 
   
  ---uname output---
  Linux seedlp2 4.10.0-15-generic #17-Ubuntu SMP Fri Mar 24 17:50:37 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = lpar 
   
  Write to nvram failed
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  1. Checked kdump kernel is loaded.
  2. Triggered system crash
  # echo c > /proc/sysrq-trigger

  3. /sys/fs/pstore/dmesg* doesn't gets created

  This issue can be reproduced after commit c950fd6f201

  c950fd6f201 - pstore: Split pstore fragile flags

  It introduces  PSTORE_FLAGS_DMESG, which is not set for PowerPC.

  
  Please include below commit 041939c1ec5 as this fixes this issue.

  commit 041939c1ec54208b42f5cd819209173d52a29d34
  Author: Ankit Kumar 
  Date:   Thu Apr 27 17:03:13 2017 +0530

  pstore: Fix flags to enable dumps on powerpc
  
  After commit c950fd6f201a kernel registers pstore write based on flag set.
  Pstore write for powerpc is broken as flags(PSTORE_FLAGS_DMESG) is not 
set for
  powerpc architecture. On panic, kernel doesn't write message to
  /fs/pstore/dmesg*(Entry doesn't gets created at all).
  
  This patch enables pstore write for powerpc architecture by setting
  PSTORE_FLAGS_DMESG flag.
  
  Fixes: c950fd6f201a ("pstore: Split pstore fragile flags")
  Cc: sta...@vger.kernel.org # v4.9+
  Signed-off-by: Ankit Kumar 
  Signed-off-by: Kees Cook 

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

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

[Kernel-packages] [Bug 1691045] Re: PowerPC: Pstore dump for powerpc is broken

2017-05-17 Thread Joseph Salisbury 
** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

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

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

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

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

** Changed in: linux (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
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/1691045

Title:
  PowerPC: Pstore dump for powerpc is broken

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

Bug description:
  ---Problem Description---
  Pstore write is broken for PowerPC. On panic, kernel doesn't write mesg to 
/fs/pstore/dmesg*
  (Entry doesn't gets created at all)
   
  Contact Information = Ankit Kumar/kumar.ankit...@in.ibm.com 
   
  ---uname output---
  Linux seedlp2 4.10.0-15-generic #17-Ubuntu SMP Fri Mar 24 17:50:37 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = lpar 
   
  Write to nvram failed
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  1. Checked kdump kernel is loaded.
  2. Triggered system crash
  # echo c > /proc/sysrq-trigger

  3. /sys/fs/pstore/dmesg* doesn't gets created

  This issue can be reproduced after commit c950fd6f201

  c950fd6f201 - pstore: Split pstore fragile flags

  It introduces  PSTORE_FLAGS_DMESG, which is not set for PowerPC.

  
  Please include below commit 041939c1ec5 as this fixes this issue.

  commit 041939c1ec54208b42f5cd819209173d52a29d34
  Author: Ankit Kumar 
  Date:   Thu Apr 27 17:03:13 2017 +0530

  pstore: Fix flags to enable dumps on powerpc
  
  After commit c950fd6f201a kernel registers pstore write based on flag set.
  Pstore write for powerpc is broken as flags(PSTORE_FLAGS_DMESG) is not 
set for
  powerpc architecture. On panic, kernel doesn't write message to
  /fs/pstore/dmesg*(Entry doesn't gets created at all).
  
  This patch enables pstore write for powerpc architecture by setting
  PSTORE_FLAGS_DMESG flag.
  
  Fixes: c950fd6f201a ("pstore: Split pstore fragile flags")
  Cc: sta...@vger.kernel.org # v4.9+
  Signed-off-by: Ankit Kumar 
  Signed-off-by: Kees Cook 

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

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

[Kernel-packages] [Bug 1691045] Re: PowerPC: Pstore dump for powerpc is broken

2017-05-17 Thread Joseph Salisbury 
** 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/1691045

Title:
  PowerPC: Pstore dump for powerpc is broken

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

Bug description:
  ---Problem Description---
  Pstore write is broken for PowerPC. On panic, kernel doesn't write mesg to 
/fs/pstore/dmesg*
  (Entry doesn't gets created at all)
   
  Contact Information = Ankit Kumar/kumar.ankit...@in.ibm.com 
   
  ---uname output---
  Linux seedlp2 4.10.0-15-generic #17-Ubuntu SMP Fri Mar 24 17:50:37 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = lpar 
   
  Write to nvram failed
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  1. Checked kdump kernel is loaded.
  2. Triggered system crash
  # echo c > /proc/sysrq-trigger

  3. /sys/fs/pstore/dmesg* doesn't gets created

  This issue can be reproduced after commit c950fd6f201

  c950fd6f201 - pstore: Split pstore fragile flags

  It introduces  PSTORE_FLAGS_DMESG, which is not set for PowerPC.

  
  Please include below commit 041939c1ec5 as this fixes this issue.

  commit 041939c1ec54208b42f5cd819209173d52a29d34
  Author: Ankit Kumar 
  Date:   Thu Apr 27 17:03:13 2017 +0530

  pstore: Fix flags to enable dumps on powerpc
  
  After commit c950fd6f201a kernel registers pstore write based on flag set.
  Pstore write for powerpc is broken as flags(PSTORE_FLAGS_DMESG) is not 
set for
  powerpc architecture. On panic, kernel doesn't write message to
  /fs/pstore/dmesg*(Entry doesn't gets created at all).
  
  This patch enables pstore write for powerpc architecture by setting
  PSTORE_FLAGS_DMESG flag.
  
  Fixes: c950fd6f201a ("pstore: Split pstore fragile flags")
  Cc: sta...@vger.kernel.org # v4.9+
  Signed-off-by: Ankit Kumar 
  Signed-off-by: Kees Cook 

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

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

[Kernel-packages] [Bug 1691045] Re: PowerPC: Pstore dump for powerpc is broken

2017-05-16 Thread Frank Heimes 
** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

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

Title:
  PowerPC: Pstore dump for powerpc is broken

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

Bug description:
  ---Problem Description---
  Pstore write is broken for PowerPC. On panic, kernel doesn't write mesg to 
/fs/pstore/dmesg*
  (Entry doesn't gets created at all)
   
  Contact Information = Ankit Kumar/kumar.ankit...@in.ibm.com 
   
  ---uname output---
  Linux seedlp2 4.10.0-15-generic #17-Ubuntu SMP Fri Mar 24 17:50:37 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = lpar 
   
  Write to nvram failed
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  1. Checked kdump kernel is loaded.
  2. Triggered system crash
  # echo c > /proc/sysrq-trigger

  3. /sys/fs/pstore/dmesg* doesn't gets created

  This issue can be reproduced after commit c950fd6f201

  c950fd6f201 - pstore: Split pstore fragile flags

  It introduces  PSTORE_FLAGS_DMESG, which is not set for PowerPC.

  
  Please include below commit 041939c1ec5 as this fixes this issue.

  commit 041939c1ec54208b42f5cd819209173d52a29d34
  Author: Ankit Kumar 
  Date:   Thu Apr 27 17:03:13 2017 +0530

  pstore: Fix flags to enable dumps on powerpc
  
  After commit c950fd6f201a kernel registers pstore write based on flag set.
  Pstore write for powerpc is broken as flags(PSTORE_FLAGS_DMESG) is not 
set for
  powerpc architecture. On panic, kernel doesn't write message to
  /fs/pstore/dmesg*(Entry doesn't gets created at all).
  
  This patch enables pstore write for powerpc architecture by setting
  PSTORE_FLAGS_DMESG flag.
  
  Fixes: c950fd6f201a ("pstore: Split pstore fragile flags")
  Cc: sta...@vger.kernel.org # v4.9+
  Signed-off-by: Ankit Kumar 
  Signed-off-by: Kees Cook 

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

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