Hello,
On 7/20/20 8:04 AM, Agrain Patrick wrote:
> Hello all,
>
> I've upgraded my Centos 8 VM to the latest kernel
> (4.18.0-193.6.3.el8_2.x86_64).
> I have then installed the kernel-debug packages (and dependencies), as
> suggested below.
>
> Now, I have following kernels in /boot:
> -
> > > > > > > > > 2ed6e490 2ed6e850 2ed6ec10
> > > > > > > > > 2ed6efd0
> > > > > > > > > 2ed6f390 2ed6f750 2ed6fb10
> >
2ed72090 2ed72450 00002ed72810
> > > > > > > 2ed72bd0
> > > > > > > 2ed72f90 2ed73350 2ed73710
> > > > > > > 2ed73ad0
> > > > > > > 2ed73e90 0
t; > > - Original Message -
> > > > > On Mon, Jan 27, 2020 at 09:56:53AM -0500, Dave Anderson wrote:
> > > > > >
> > > > > >
> > > > > > - Original Message -
> > > > > > > From: M
On Mon, Jan 27, 2020 at 10:17:51AM -0500, Dave Anderson wrote:
>
>
> - Original Message -
> > On Mon, Jan 27, 2020 at 09:56:53AM -0500, Dave Anderson wrote:
> > >
> > >
> > > - Original Message -
> > > > From: Masayoshi Mi
On Mon, Jan 27, 2020 at 10:06:57AM -0500, Masayoshi Mizuma wrote:
> On Mon, Jan 27, 2020 at 09:56:53AM -0500, Dave Anderson wrote:
> >
> >
> > - Original Message -
> > > From: Masayoshi Mizuma
> > >
> > > Fix for aarch64 with Linux v
On Mon, Jan 27, 2020 at 09:56:53AM -0500, Dave Anderson wrote:
>
>
> - Original Message -
> > From: Masayoshi Mizuma
> >
> > Fix for aarch64 with Linux v5.0 and later kernels that
> > contains commit 91fc957c9b1d ("arm64/bpf: don't allocate
From: Masayoshi Mizuma
Fix for aarch64 with Linux v5.0 and later kernels that
contains commit 91fc957c9b1d ("arm64/bpf: don't allocate
BPF JIT programs in module memory") and the memory dump
is captured by virsh dump.
Without the patch, crash cannot find kimage_voffset so it
fails to
From: Masayoshi Mizuma
Fix for aarch64 with Linux v5.0 and later kernels that
contains commit 91fc957c9b1d ("arm64/bpf: don't allocate
BPF JIT programs in module memory") and the memory dump
is captured by virsh dump.
Note: Another two issues remain for the memory dump captured by
e following patch? That's the incremental patch for
>> commit 9937878 ("Fix for the "kmem -n" option on Linux-5.4-rc1...").
>
> Thanks Masa, this additional patch tests OK. Note that I removed a couple
> unused
> variables, and adjusted the display just
lowing patch? That's the incremental patch for
commit 9937878 ("Fix for the "kmem -n" option on Linux-5.4-rc1...").
From: Masayoshi Mizuma
Date: Fri, 18 Oct 2019 17:45:04 -0400
Subject: [PATCH] Additional fix for "kmem -n" option on Linux 5.4-rc1
commit 9937878 ("Fix
From: Masayoshi Mizuma
Fix for Linux 5.4-rc1 and later kernels that contain commit
b6c88d3b9d38 ("drivers/base/memory.c: don't store end_section_nr
in memory blocks"). Without this patch, kmem -n stops as the following:
crash> kmem -n
...
kmem: invalid structure
From: Masayoshi Mizuma
On 4.19 and newer kernel, gcore command fails as following:
===
gcore: invalid structure size: pid_link
FILE: libgcore/gcore_coredump_table.c LINE: 423 FUNCTION:
pid_alive()
[./crash] error
On Mon, Jan 07, 2019 at 02:02:24PM -0500, Dave Anderson wrote:
> - Original Message -
> Hi Masa,
>
> I appreciate the quick response to my offlist request. I also added a line
Thanks you for adding the line to the help page.
> to the "dev" help page, and queued the patch for
the number of I/Os issued to disk driver. So this patch
gets DRV column removed if in_flight member in struct request_queue
isn't valid.
Without the patch, the command fails with the error message
"dev: -d option not supported or applicable on this architecture
or kernel".
Signed-off-
On Fri, Oct 05, 2018 at 11:16:28AM -0400, Dave Anderson wrote:
>
>
> - Original Message -
> > ...
> >
> > > It is nice macro! The macro returns machdep->pageshift and
> > > it is stored at crash initialization in all arch, right?
> > > So, does the following make sense?
> >
> > Yeah,
.
It is nice macro! The macro returns machdep->pageshift and
it is stored at crash initialization in all arch, right?
So, does the following make sense?
---
diff --git a/memory.c b/memory.c
index 9657c28..de93af0 100644
--- a/memory.c
+++ b/memory.c
@@ -17312,7 +17312,7 @@ fill_memory_block_state(ulong
<< PAGE_SHIFT;
+ return pfn * sysconf(_SC_PAGESIZE);
}
static void
---
Thanks,
Masa
>
> Thanks,
> Dave
>
>
>
> >
> > >
> > > Signed-off-by: Masayoshi Mizuma
> > > ---
> > > defs.h| 9 ++
> > > memory.c | 2
From: Masayoshi Mizuma
Update for the "kmem -n" option to also dump memory block.
Currently, "kmem -n" shows the memory section only. This
patch gets available the memory block as well if 'memory_block'
structure and 'memory_subsys' symbol exist.
The memory block i
On Wed, Oct 03, 2018 at 08:52:00AM -0400, Dave Anderson wrote:
>
>
> - Original Message -
> >
> ... [ cut ] ...
> >
> > How about the following layout? The following shows the sections
> > which belong to the memory block.
> >
> > crash> kmem -n
> > ...
> > NR SECTION
Hi Dave,
Thank you for your comment.
On Tue, Oct 02, 2018 at 12:02:35PM -0400, Dave Anderson wrote:
>
>
> - Original Message -
> > From: Masayoshi Mizuma
> >
> > Update for the "kmem -n" option to also dump memory block.
> > Current
From: Masayoshi Mizuma
Update for the "kmem -n" option to also dump memory block.
Currently, "kmem -n" shows the memory section only. This
patch gets available the memory block as well if 'memory_block'
structure and 'memory_subsys' symbol exist.
The memory block i
et_table entries to the end of the structure so
> that previously-compiled extension modules using OFFSET() will not break.
Thanks!
- Masa
>
> Thanks,
> Dave
>
>
> - Original Message -
> > From: Masayoshi Mizuma
> >
> > dev -p supports to
From: Masayoshi Mizuma
dev -p supports to show the PCI information, however, it works
in old kernel only. This patch gets it available in recently kernel.
And also it will show the PCI BUS information. The BUS information
may be useful for investigation of PCI hotplug issue to track the
PCI
;.
Thank you for the additional changes!
- Masayoshi Mizuma
Queued for crash-7.1.6:
https://github.com/crash-utility/crash/commit/df08978f31ba39e94b3096804f4e0776373c8b53
Thanks,
Dave
- Original Message -
Improvement -d option of dev command to display I/O statics
for the
calculation for the
disk. It judges as the device driver uses blk-mq if the
request_queue.mq_ops is not NULL.
"DRV" field is displayed as "N/A(MQ)" because the value for in-flight
in the device driver is not exists for blk-mq...
Signed-off-by: Masayoshi Mizuma <m.miz...@jp.f
Hi Alex,
When I searched struct journal_head by readStructNext(), the
number of journal_head was over _MAXEL (== 1) and the
searching was stopped.
It is good to add a parameter to change the limit.
Signed-off-by: Masayoshi Mizuma <m.miz...@jp.fujitsu.com>
---
pykdump/wrapcrash.py
27 matches
Mail list logo
