[Crash-utility] Re: How to get module symbols working ?

2024-04-05 Thread naveenchaudhary2010
You can find the vmlinux, kdump and module file here : https://drive.google.com/file/d/1j-ZUnkRvLD1KDIxvphQpYlilrlgXMn57/view?usp=sharing -- Crash-utility mailing list -- devel@lists.crash-utility.osci.io To unsubscribe send an email to devel-le...@lists.crash-utility.osci.io

[Crash-utility] Re: How to get module symbols working ?

2024-04-05 Thread Tao Liu
On Fri, Apr 5, 2024 at 12:48 PM wrote: > > One of the original concern is still unanswered. I understood the bakctrace > is expected to have " _MODULE_INIT_TEXT_START_" because compiler re-arranged > code for the init function. However, the sym doesn't point us to the source > file. Is that

[Crash-utility] How to get module symbols working?

2024-04-05 Thread Naveen Chaudhary
I am analyzing the kdump in latest crash utility 8.0.4++. I think I loaded the module symbols correctly : crash> mod MODULE NAME TEXT_BASE SIZE OBJECT FILE 80007a7e2040 npdereference 80007a7e 12288 (not loaded) [CONFIG_KALLSYMS] crash> crash> mod

[Crash-utility] Re: [PATCH v4 ] Adding the zram decompression algorithm "lzo-rle" to support kernel versions >= 5.1

2024-04-05 Thread 萩尾 一仁
On 2024/03/28 17:15, Yulong TANG 汤玉龙 wrote: > In Linux 5.1, the ZRAM block driver has changed its default compressor > from "lzo" to "lzo-rle" to enhance LZO compression support. However, > crash does not support the improved LZO algorithm, resulting in failure > when reading memory. > >