[Kernel-packages] [Bug 1691045] Comment bridged from LTC Bugzilla
--- Comment From kumar.ankit...@in.ibm.com 2017-05-19 09:43 EDT--- (In reply to comment #13) > 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? Tested. Working well. ~Ankit --- Comment From kumar.ankit...@in.ibm.com 2017-06-01 05:27 EDT--- (In reply to comment #17) > 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? Tested. Working well. ~Ankit -- 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 KumarDate: 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] Comment bridged from LTC Bugzilla
--- Comment From pavra...@in.ibm.com 2017-05-26 05:50 EDT--- Issue is observed even on Ubuntu 16.04.03. root@ltc-firep2:/sys/fs/pstore# ls -lrt total 0 -r--r--r-- 1 root root 3909 May 5 04:21 dmesg-nvram-1 -r--r--r-- 1 root root 4080 May 26 02:59 powerpc-opal-nvram-8 -r--r--r-- 1 root root 65520 May 26 02:59 powerpc-common-nvram-6 root@ltc-firep2:/sys/fs/pstore# ls -lrt total 0 -r--r--r-- 1 root root 3909 May 5 04:21 dmesg-nvram-1 -r--r--r-- 1 root root 4080 May 26 02:59 powerpc-opal-nvram-8 -r--r--r-- 1 root root 65520 May 26 02:59 powerpc-common-nvram-6 root@ltc-firep2:/sys/fs/pstore# tail dmesg-nvram-1 <4>[ 351.724539] LR [c05dd79c] write_sysrq_trigger+0x10c/0x230 <4>[ 351.724583] Call Trace: <4>[ 351.724603] [c00fd79b7cf0] [c05dd77c] write_sysrq_trigger+0xec/0x230 (unreliable) <4>[ 351.724677] [c00fd79b7d90] [c03dabd4] proc_reg_write+0x84/0x120 <4>[ 351.724733] [c00fd79b7dd0] [c0327520] SyS_write+0x150/0x400 <4>[ 351.724789] [c00fd79b7e30] [c000a17c] system_call+0x38/0xb4 <4>[ 351.724843] Instruction dump: <4>[ 351.724870] 409effb8 7fc3f378 4bfff381 4bac 3c4c00c1 384205c0 3d42fff2 394ac530 <4>[ 351.724963] 3921 912a 7c0004ac 3940 <992a> 4e800020 6000 6042 <4>[ 351.725055] ---[ end trace 9de875846d84dfcd ]--- root@ltc-firep2:/sys/fs/pstore# ls -lrt total 0 -r--r--r-- 1 root root 3909 May 5 04:21 dmesg-nvram-1 -r--r--r-- 1 root root 4080 May 26 05:31 powerpc-opal-nvram-8 -r--r--r-- 1 root root 65520 May 26 05:31 powerpc-common-nvram-6 root@ltc-firep2:/sys/fs/pstore# tail dmesg-nvram-1 <4>[ 351.724539] LR [c05dd79c] write_sysrq_trigger+0x10c/0x230 <4>[ 351.724583] Call Trace: <4>[ 351.724603] [c00fd79b7cf0] [c05dd77c] write_sysrq_trigger+0xec/0x230 (unreliable) <4>[ 351.724677] [c00fd79b7d90] [c03dabd4] proc_reg_write+0x84/0x120 <4>[ 351.724733] [c00fd79b7dd0] [c0327520] SyS_write+0x150/0x400 <4>[ 351.724789] [c00fd79b7e30] [c000a17c] system_call+0x38/0xb4 <4>[ 351.724843] Instruction dump: <4>[ 351.724870] 409effb8 7fc3f378 4bfff381 4bac 3c4c00c1 384205c0 3d42fff2 394ac530 <4>[ 351.724963] 3921 912a 7c0004ac 3940 <992a> 4e800020 6000 6042 <4>[ 351.725055] ---[ end trace 9de875846d84dfcd ]--- root@ltc-firep2:/sys/fs/pstore# Thanks, Pavithra --- Comment From hegdevas...@in.ibm.com 2017-05-26 07:55 EDT--- ... based on previous comment .. can you please backport patch to 16.04.03 as well? -Vasant -- 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 KumarDate: 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 :
[Kernel-packages] [Bug 1691045] Comment bridged from LTC Bugzilla
--- Comment From vipar...@in.ibm.com 2017-05-16 07:07 EDT--- Commit c950fd6f20 ("pstore: Split pstore fragile flags") is available in kernel 4.9 and above, while commit 041939c1ec ("pstore: Fix flags to enable dumps on powerpc") would get into 4.12, so need to be pulled into kernel version 4.9 and above. -- 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 KumarDate: 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