public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug gcov-profile/94394] New: [GCOV]It will cause random kernel panic during collecting kernel code coverage
@ 2020-03-30 3:53 ammy.yi at intel dot com
2020-03-30 5:49 ` [Bug gcov-profile/94394] " pinskia at gcc dot gnu.org
` (4 more replies)
0 siblings, 5 replies; 6+ messages in thread
From: ammy.yi at intel dot com @ 2020-03-30 3:53 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94394
Bug ID: 94394
Summary: [GCOV]It will cause random kernel panic during
collecting kernel code coverage
Product: gcc
Version: 9.3.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: gcov-profile
Assignee: unassigned at gcc dot gnu.org
Reporter: ammy.yi at intel dot com
CC: marxin at gcc dot gnu.org
Target Milestone: ---
It will cause random kernel panic during collecting kernel code coverage .
gcc version 9.3.1 20200319 releases
[ 222.538244] #PF: supervisor instruction fetch in kernel mode
[ 222.543945] #PF: error_code(0x0010) - not-present page
[ 222.549133] PGD 0 P4D 0
[ 222.551719] Oops: 0010 [#1] SMP NOPTI
[ 222.577223] RIP: 0010:0x0
[ 222.579901] Code: Bad RIP value.
[ 222.583184] RSP: 0018:ffffae3140f13f58 EFLAGS: 00010082
[ 222.588448] RAX: ffffffff94217940 RBX: 0000000000000000 RCX:
0000000000000000
[ 222.595618] RDX: 0000000080004000 RSI: ffff89203c624440 RDI:
ffffffff94217940
[ 222.602781] RBP: 0000000000000000 R08: ffffffff94203da0 R09:
0000000000000000
[ 222.609942] R10: 0000000000000000 R11: 000000000002c502 R12:
0000000000000000
[ 222.617114] R13: 0000000000000000 R14: 0000000000000000 R15:
0000000000000000
[ 222.624283] FS: 00007fc8e2c1a740(0000) GS:ffff89205fc00000(0000)
knlGS:0000000000000000
[ 222.632404] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 222.638190] CR2: ffffffffffffffd6 CR3: 0000000497278005 CR4:
0000000000fe0ef0
[ 222.645354] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
0000000000000000
[ 222.652523] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7:
0000000000000400
[ 222.659697] PKRU: 55555554
[ 222.662441] Call Trace:
[ 222.664924] WARNING: kernel stack frame pointer at 00000000fc81ab36 in
load_unload_mod:4080 has bad value 000000008657b9bc
[ 222.664926] unwind stack type:0 next_sp:000000008657b9bc mask:0x2
graph_idx:0
[ 222.664927] 00000000fc81ab36: 0000000000000000 ...
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug gcov-profile/94394] [GCOV]It will cause random kernel panic during collecting kernel code coverage
2020-03-30 3:53 [Bug gcov-profile/94394] New: [GCOV]It will cause random kernel panic during collecting kernel code coverage ammy.yi at intel dot com
@ 2020-03-30 5:49 ` pinskia at gcc dot gnu.org
2020-03-30 6:39 ` marxin at gcc dot gnu.org
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: pinskia at gcc dot gnu.org @ 2020-03-30 5:49 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94394
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Last reconfirmed| |2020-03-30
Status|UNCONFIRMED |WAITING
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
There is not information here to say if this is a kernel issue or a compiler
issue.
See https://gcc.gnu.org/bugs.html on what information we need.
Also I don't think the gcov code is used directly inside the kernel.
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug gcov-profile/94394] [GCOV]It will cause random kernel panic during collecting kernel code coverage
2020-03-30 3:53 [Bug gcov-profile/94394] New: [GCOV]It will cause random kernel panic during collecting kernel code coverage ammy.yi at intel dot com
2020-03-30 5:49 ` [Bug gcov-profile/94394] " pinskia at gcc dot gnu.org
@ 2020-03-30 6:39 ` marxin at gcc dot gnu.org
2020-03-30 8:04 ` ammy.yi at intel dot com
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: marxin at gcc dot gnu.org @ 2020-03-30 6:39 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94394
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
If I remember correctly kernel implements its own "runtime library" libgcov, so
I would expect a crash somewhere in it. Anyway, a reasonable reproducer would
be needed.
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug gcov-profile/94394] [GCOV]It will cause random kernel panic during collecting kernel code coverage
2020-03-30 3:53 [Bug gcov-profile/94394] New: [GCOV]It will cause random kernel panic during collecting kernel code coverage ammy.yi at intel dot com
2020-03-30 5:49 ` [Bug gcov-profile/94394] " pinskia at gcc dot gnu.org
2020-03-30 6:39 ` marxin at gcc dot gnu.org
@ 2020-03-30 8:04 ` ammy.yi at intel dot com
2020-03-30 8:51 ` marxin at gcc dot gnu.org
2020-03-31 5:42 ` ammy.yi at intel dot com
4 siblings, 0 replies; 6+ messages in thread
From: ammy.yi at intel dot com @ 2020-03-30 8:04 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94394
--- Comment #3 from ammy.yi <ammy.yi at intel dot com> ---
Actually, there is some random kernel panic here.
The following steps may reproduce this issue:
1. Enable gcov in kconfig
2. build kernel and boot to system
3. Do following load/unload modules steps
modprobe stm_p_basic
modprobe intel_th_pci
modprobe intel_th_sth
modprobe intel_th_msu
modprobe stm_console
modprobe -r stm_p_basic
modprobe -r intel_th_pci
modprobe -r intel_th_sth
modprobe -r intel_th_msu
modprobe -r stm_console
Hi martin,
If it is libgcov issue, do you know where to file issue for it?
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug gcov-profile/94394] [GCOV]It will cause random kernel panic during collecting kernel code coverage
2020-03-30 3:53 [Bug gcov-profile/94394] New: [GCOV]It will cause random kernel panic during collecting kernel code coverage ammy.yi at intel dot com
` (2 preceding siblings ...)
2020-03-30 8:04 ` ammy.yi at intel dot com
@ 2020-03-30 8:51 ` marxin at gcc dot gnu.org
2020-03-31 5:42 ` ammy.yi at intel dot com
4 siblings, 0 replies; 6+ messages in thread
From: marxin at gcc dot gnu.org @ 2020-03-30 8:51 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94394
--- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to ammy.yi from comment #3)
> Actually, there is some random kernel panic here.
>
> The following steps may reproduce this issue:
>
> 1. Enable gcov in kconfig
> 2. build kernel and boot to system
> 3. Do following load/unload modules steps
>
> modprobe stm_p_basic
> modprobe intel_th_pci
> modprobe intel_th_sth
> modprobe intel_th_msu
> modprobe stm_console
>
> modprobe -r stm_p_basic
> modprobe -r intel_th_pci
> modprobe -r intel_th_sth
> modprobe -r intel_th_msu
> modprobe -r stm_console
Would it be possible to provide a stack-traces where it usually causes a kernel
panic?
>
> Hi martin,
>
> If it is libgcov issue, do you know where to file issue for it?
I would create a normal linux kernel bug. The pseudo-runtime is implemented in
kernel/gcov subfolder.
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug gcov-profile/94394] [GCOV]It will cause random kernel panic during collecting kernel code coverage
2020-03-30 3:53 [Bug gcov-profile/94394] New: [GCOV]It will cause random kernel panic during collecting kernel code coverage ammy.yi at intel dot com
` (3 preceding siblings ...)
2020-03-30 8:51 ` marxin at gcc dot gnu.org
@ 2020-03-31 5:42 ` ammy.yi at intel dot com
4 siblings, 0 replies; 6+ messages in thread
From: ammy.yi at intel dot com @ 2020-03-31 5:42 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94394
--- Comment #5 from ammy.yi <ammy.yi at intel dot com> ---
(In reply to Martin Liška from comment #4)
> (In reply to ammy.yi from comment #3)
> > Actually, there is some random kernel panic here.
> >
> > The following steps may reproduce this issue:
> >
> > 1. Enable gcov in kconfig
> > 2. build kernel and boot to system
> > 3. Do following load/unload modules steps
> >
> > modprobe stm_p_basic
> > modprobe intel_th_pci
> > modprobe intel_th_sth
> > modprobe intel_th_msu
> > modprobe stm_console
> >
> > modprobe -r stm_p_basic
> > modprobe -r intel_th_pci
> > modprobe -r intel_th_sth
> > modprobe -r intel_th_msu
> > modprobe -r stm_console
>
> Would it be possible to provide a stack-traces where it usually causes a
> kernel panic?
>
> >
> > Hi martin,
> >
> > If it is libgcov issue, do you know where to file issue for it?
>
> I would create a normal linux kernel bug. The pseudo-runtime is implemented
> in kernel/gcov subfolder.
Hi Martin,
Actually, there is no detailed call trace. The whole call trace I got is added
in my first comments
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2020-03-31 5:42 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-03-30 3:53 [Bug gcov-profile/94394] New: [GCOV]It will cause random kernel panic during collecting kernel code coverage ammy.yi at intel dot com
2020-03-30 5:49 ` [Bug gcov-profile/94394] " pinskia at gcc dot gnu.org
2020-03-30 6:39 ` marxin at gcc dot gnu.org
2020-03-30 8:04 ` ammy.yi at intel dot com
2020-03-30 8:51 ` marxin at gcc dot gnu.org
2020-03-31 5:42 ` ammy.yi at intel dot com
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).