19 Sep
2017
19 Sep
'17
8:13 a.m.
On Tue, Sep 19, 2017 at 9:00 AM, Greg KH gregkh@google.com wrote:
On Tue, Sep 19, 2017 at 12:14:56PM +0530, Naresh Kamboju wrote:
On 18 September 2017 at 22:30, Milosz Wasilewski milosz.wasilewski@linaro.org wrote:
- ./run_fuse_test.sh: line 12: 3330 Bus error ./fuse_test ./mnt/memfd Bug is under investigation - which failed on all Linux versions - Checking pstore console is registered ... FAIL Checking /dev/pmsg0 exists ... FAIL Writing unique string to /dev/pmsg0 ... FAIL Bug reported - This test need extra kernel command line arguments "backend=ramoops ramoops.mem_address=0x30000000 ramoops.mem_size=0x10000"Odd, is this a pstore requirement?
Yes, see Documentation/admin-guide/ramoops.rst
ramoops must be configured in one of three ways:
- On device tree based platforms, with a "/reserved-memory/ramoops/" device node that lists the memory location
- With a platform device created from drivers/platform/chrome/chromeos_pstore.c with platform specific data
- Through the kernel command line on platforms that have neither of the other two.
Arnd