On 5/13/21 4:49 AM, Rich wrote:
> I'm mostly curious about whether anyone knows why the Call Trace might
> be empty - I see the message about corrupted stack end above it, but
> from what I can see online, plenty of people get that message and a
> call trace printout below it (...on other architectures, at least).
> https://lists.debian.org/debian-sparc/2016/09/msg00002.html is even an
> example of someone on this very list.

If the stack is corrupted the backtrace may or may not be affected.

> Does anyone have any insights? Or am I going to have to resort to
> printks in random parts of the thread the panic notes and hope I find
> the problem?

Why not bisect the kernel to find the actual bug?


 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Reply via email to