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
