On 8/10/23 16:50, Kees Cook wrote:
> Can you share the .config you're building with? And what are you using
> to trigger an Oops? I will see if I can reproduce this...
Config: https://paste.ubuntu.com/p/Vrcsf8Ry9g/
Just ran plain "sudo reboot" and inspected /var/lib/systemd/pstore/dmesg-ramoops-0 after reboot.
Thanks,
Vijay
On Thu, Aug 10, 2023 at 05:48:17PM -0700, Vijay Balakrishna wrote:
> On 8/10/23 16:50, Kees Cook wrote:
> > Can you share the .config you're building with? And what are you using
> > to trigger an Oops? I will see if I can reproduce this...
>
> Config: https://paste.ubuntu.com/p/Vrcsf8Ry9g/
Thanks! I'll see how close I can get to this for my local testing...
>
> Just ran plain "sudo reboot" and inspected /var/lib/systemd/pstore/dmesg-ramoops-0 after reboot.
If you have a "dmesg-ramoops-0" there, something Oopsed. On a clean
shutdown, only "console-ramoops-0" will be recorded. Can you double
check by deleting everything in /var/lib/systemd/pstore/ and rebooting?
If you still get a dmesg-ramoops-0 file, can you upload that somewhere
so I can look at it?
Also, can you send the contents of /proc/iomem ?
--
Kees Cook
On Thu, Aug 10, 2023 at 05:48:17PM -0700, Vijay Balakrishna wrote:
> On 8/10/23 16:50, Kees Cook wrote:
> > Can you share the .config you're building with? And what are you using
> > to trigger an Oops? I will see if I can reproduce this...
>
>
> Config: https://paste.ubuntu.com/p/Vrcsf8Ry9g/
>
> Just ran plain "sudo reboot" and inspected /var/lib/systemd/pstore/dmesg-ramoops-0 after reboot.
Ah-ha! I have reproduced by reconfiguring my system to use your exact
memory sizes. And I get the unexpected "dmesg-ramoops-0" file too! I
will continue digging...
--
Kees Cook