On Sun, 28 Mar 2021 at 07:18, lijiang wrote:
>
> 在 2021年03月26日 16:51, HAGIO KAZUHITO(萩尾 一仁) 写道:
> > -Original Message-
> >> 在 2021年03月26日 12:33, HAGIO KAZUHITO(萩尾 一仁) 写道:
> >>> The trace.c extension module moved to the separate repository:
> >>> https://github.com/fujitsu/crash-trace
>
Hi Pingfan,
On Thu, 25 Mar 2021 at 08:37, Pingfan Liu wrote:
>
> Renaming, so it is better to reflect the flip layout of kernel VA, which
> is introduced by kernel commit 14c127c957c1 ("arm64: mm: Flip kernel VA
> space")
>
> Signed-off-by: Pingfan Liu
> Cc: HAGIO KAZUHITO
> Cc: Lianbo Jiang
Hi Pingfan,
Thanks for the patch.
Some comments below:
On Thu, 25 Mar 2021 at 09:07, piliu wrote:
>
>
> In case of making mistake due to my limited knowledge on arm64, I also
> CC this patch to some guys from arm team. If any comment, please also
> kindly give them.
>
> Thanks,
> Pingfan
>
>
Hi Vinayak,
On Fri, 26 Mar 2021 at 11:56, vinayak menon wrote:
>
> Hi Bhupesh,
>
> On Thu, Mar 25, 2021 at 11:15 PM Bhupesh Sharma
> wrote:
> >
> > Hi Vinayak,
> >
> > Thanks for the patch.
> > Some queries below:
> >
> > On Thu, 25
Hi Vinayak,
Thanks for the patch.
Some queries below:
On Thu, 25 Mar 2021 at 20:08, Vinayak Menon wrote:
>
> Raw ramdumps without vmcoreinfo does not work currently
> with pointer authentication or memory tagging enabled.
> The arm capability array can be queried but that creates
> a dependency
LK_TCK) value instead of the
hardcoded HZ values depending on kernel versions.
Cc: k-hagio...@nec.com
Cc: liji...@redhat.com
Cc: bhupesh.li...@gmail.com
Signed-off-by: Bhupesh Sharma
---
arm.c| 2 +-
arm64.c | 2 +-
ppc.c| 5 +
ppc64.c | 6 ++
x86.c| 5 +
x86_64.c | 5 +-
SUBDIRS=${PWD} modules
> clean:
> rm -f *.mod.c *.ko *.o Module.*
LGTM, so:
Acked-by: Bhupesh Sharma
Thanks.
--
Crash-utility mailing list
Crash-utility@redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility
On Wed, Oct 28, 2020 at 11:56 PM Alexander Egorenkov
wrote:
>
> Bhupesh Sharma writes:
>
> >
> > ifneq ($(CROSS_COMPILE),)
> > SUBARCH := $(shell echo $(CROSS_COMPILE) | cut -d- -f1 | sed 's:^.*/::g')
> > else
> > SUBARCH := $(shell uname -m)
> >
thought the commit log would be enough..
>
> Do you think we should not merge this as is?
No problem. I only had some nitpicks.
We can go ahead and apply the same for now - maybe later on if someone
finds more time we can clean this up further.
Feel free to add:
Acked-by: Bhupesh Sharma
Th
Hi Alexey,
On Wed, Oct 28, 2020 at 11:31 AM Alexey Makhalov wrote:
>
> Hi all,
>
> I’m thinking to update gdb to recent version.
> Are there any concerns?
> What should I know? Any dependencies which force us to stick to 7.6?
>
> The features I’m aiming are:
> 1) `offset` support in
Hello Alexander,
Thanks for working on this. I did some work earlier on this after
discussion with Dave Anderson, but unfortunately I could never queue
it up for upstream consideration, due to lack of time.
I have some suggestions below:
On Sat, Oct 10, 2020 at 7:42 PM Alexander Egorenkov
tatic struct file_operations crash_fops
> .owner = THIS_MODULE,
> .llseek = crash_llseek,
> .read = crash_read,
> +#ifdef CAN_WRITE_KERNEL
> .write = crash_write,
> +#endif
> .unlocked_ioctl = crash_ioctl,
> .open = crash_open,
&
Hi Lianbo,
Please note that we still need to formulate a way to maintain
crash-extension outside a tarball.
I am preparing a RFC proposal and will share it shortly.
On Fri, Aug 28, 2020 at 9:34 AM Lianbo Jiang wrote:
>
> With kernel commit: <577d5cd7e585> ("x86/ioperm: Move iobitmap data into
>
Hi Kazu,
On Wed, Jul 22, 2020 at 1:02 PM HAGIO KAZUHITO(萩尾 一仁)
wrote:
>
> Hi Bhupesh,
>
> sorry for the late response.
>
> > -Original Message-
> > Update the Makefile comments to note that arm and arm64
> > are also supported build targets.
>
_el1_t1sz
> > vmcoreinfo variable has been changed to TCR_EL1_T1SZ.
> >
> > Make a similar change in crash-utility.
> >
> > Signed-off-by: Bhupesh Sharma
>
> Acked-by: Kazuhito Hagio
>
> Thanks for your effort at those kernel patches!
> Kazu
>
> &g
Although we have trace.c uploaded to crash-extensions github currently,
several users (like RHEL/SUSE rpm packagers), prefer using
crash-trace-*.tar.gz directly for rpm packaging, lets upload the same to
github extensions as well.
Signed-off-by: Bhupesh Sharma
---
crash-trace-command-2.0.tar.gz
Since linux kernel commit bbdbc11804ff ("arm64/crash_core: Export TCR_EL1.T1SZ
in
vmcoreinfo") [available in linux-next now], the name of tcr_el1_t1sz
vmcoreinfo variable has been changed to TCR_EL1_T1SZ.
Make a similar change in crash-utility.
Signed-off-by: Bhupesh Sharma
---
arm
Update the Makefile comments to note that arm and arm64
are also supported build targets.
Signed-off-by: Bhupesh Sharma
---
Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Makefile b/Makefile
index 745541012f43..7062139e68bc 100644
--- a/Makefile
+++ b/Makefile
Hi Vijay,
On Thu, Jul 2, 2020 at 8:33 AM Vijay Balakrishna
wrote:
>
> Hello,
>
> We are seeing crash (7.2.8) failing on ARM64 live kernel. After filing
> https://github.com/crash-utility/crash/issues/54 I learned about crash
> utility discussion list
>
Hello Kazu,
On Mon, Jun 15, 2020 at 8:38 PM HAGIO KAZUHITO(萩尾 一仁)
wrote:
>
> -Original Message-
> > > [root@lxkmg-pag-ale test64]# /usr/bin/crash -d 15
> > > System.map-4.18.0-147.el8.x86_64 vmlinux.debuginfo vmcore
> ...
> > >
> > > read_diskdump: PAGE_EXCLUDED: paddr/pfn:
Hi Patrick,
On Mon, Jun 15, 2020 at 12:51 PM Agrain Patrick
wrote:
> -Message d'origine-
> De : crash-utility-boun...@redhat.com
> [mailto:crash-utility-boun...@redhat.com] De la part de Bhupesh Sharma
> Envoyé : lundi 15 juin 2020 09:13
> À : Discussion list for cras
Hello Patrick,
On Mon, Jun 15, 2020 at 12:28 PM Agrain Patrick
wrote:
>
> Hello,
>
>
>
> I tried to test the crash utility from CentOS 8 with following requirements:
>
> First machine (VMware) on which CentOS 8 is installed and on which I
> performed a fake crash using SysRq. After reboot, The
On Thu, May 7, 2020 at 8:34 PM HAGIO KAZUHITO(萩尾 一仁) wrote:
>
> > > Dave,
> > >
> > > > Initially Kazuhito will primarily be handling upstream github duties,
> > > > while Lianbo and Bhupesh will be handling Fedora, CentOS stream, and
> > > > RHEL maintenance. All three will be involved in the
Hi Vinayak,
On Fri, Apr 17, 2020 at 8:34 PM vinayak menon wrote:
>
> Hi Dave,
>
> Noticed that raw ramdumps of 5.4 kernel aren't working with crash tip.
> With the patches attached, I could get it working. Please take a look.
Can you share some details/message-logs of the issue you are seeing?
Hello Poonam,
I see Dave is already helping you with the issue. I saw a couple of
interesting things and have a suggestion regarding the same (see
in-line):
On Mon, Jan 6, 2020 at 6:45 PM Poonam Aggrwal wrote:
>
> Hello
>
> I am getting the following error when I use crash on arm64 platform
Hi Prabhakar,
On Mon, Dec 30, 2019 at 9:55 AM Prabhakar Kushwaha
wrote:
>
> Dear Bhupesh,
>
> On Tue, Dec 24, 2019 at 9:39 AM Prabhakar Kushwaha
> wrote:
> >
> > On Tue, Dec 24, 2019 at 1:09 AM Bhupesh Sharma wrote:
> > >
> > > On Mon, Dec 23, 20
On Mon, Dec 23, 2019 at 7:49 PM Prabhakar Kushwaha
wrote:
>
> On Mon, Dec 23, 2019 at 7:32 PM Dave Anderson wrote:
> >
> >
> >
> > - Original Message -
> > > __exception_text_start and __exception_text_end is used to group functions
> > > and place according to linker script in such a
for determining the vabits_actual
value.
[0].http://lists.infradead.org/pipermail/kexec/2019-November/023962.html
Cc: Dave Anderson
Cc: AKASHI Takahiro
Cc: Prabhakar Kushwaha
Cc: crash-utility@redhat.com
Signed-off-by: Bhupesh Sharma
---
arm64.c | 13 +++--
1 file changed, 11 insertions(+), 2
Hi Akashi,
On Thu, Oct 3, 2019 at 10:49 AM AKASHI Takahiro
wrote:
>
> Hi Dave,
>
> I tried to use crash v7.2.7 with kernel v5.4-rc1 on arm64.
>
> 1. VA_BITS_ACTUAL is missing in vmcoreinfo.
>Does anyone work on fixing it on kernel side?
>(just adding one or two lines though)
I am
/4.14.0/build/vmlinux.o
>> >find_booted_kernel: found: /lib/modules/4.14.0/build/vmlinux.o
>> >
>> > 5. Now the problem happens due to following check inside
>> >'find_booted_kernel()' function:
>> >
>> > if (mount_point(kernel) ||
>
unt'able, so the check in point 5 fails and we incorrectly
>> accept this as the kernel being boot'ed, even though
>> there was a 'vmlinux' present inside
>> '/lib/modules//build'.
>>
>> 7. Now, later when crash tries to access symbols (like _stext)
>> using this kern
s the kernel file.
After this fix, crash no longer errors out and we can use
full functionality on the crash prompt.
Signed-off-by: Bhupesh Sharma <bhsha...@redhat.com>
---
filesys.c | 14 +-
1 file changed, 13 insertions(+), 1 deletion(-)
diff --git a/filesys.c b/filesys
m, we should be finding the vmlinux at the standard
>> location, otherwise we should do proper error handling.
>>
>> So this patch errors out earlier, if we don't find a valid value for
>> '_stext_vmlinux' and prompts the user to refer to the 'usage'
>> banner.
>&
33 matches
Mail list logo
