** Changed in: kunpeng920
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935583
Title:
Kernel panic on Bionic 5.4.0-47-generic
To manage notifications about thi
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935583
T
** Changed in: kunpeng920
Status: In Progress => Incomplete
** Changed in: linux (Ubuntu)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935583
Title:
Hi Merlin,
Thanks for the information. I will look into it.
And can you provide us more information please?
e.g. firmware ver, output of `lspci -vvnn`, what kind of operation you use to
reproduce this issue.
Thanks a lot.
--
You received this bug notification because you are a member of Ubunt
[1516299.566982] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110
[1516299.582325] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110
[1516299.601741] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110
[1516299.606825] Unable to handle kernel paging request at virtual address
There are many ways to corrupt stack or pointers to stack. Since this
issue happens in out-of-tree mlx5 modules, it looks to me that where you
shall look at.
Please let us know if you can reproduce this issue without any out-of-
tree module.
** Changed in: linux (Ubuntu)
Status: Incomplete
I notice there is a traceback about mlx5, however, while I check vmcore,
the STACK_END_MAGIC haven't been overridden (I mean $rd 'stack_address'
print 0x57AC6E9D) how can?
//kernel/sched/core.c
static inline void schedule_debug(struct task_struct *prev)
{
#ifdef CONFIG_SCHED_STACK_END_CHECK
The log shows that you are running non-Ubuntu mlx5 modules, and the
traceback is in those modules. Marking Invalid - you'll need to reach
out to your mlx5 driver provider for support.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: kunpeng920
Stat
