On Nov 29, 2022, at 7:06 AM, Steven Rostedt <rostedt@xxxxxxxxxxx> wrote: > On Tue, 29 Nov 2022 04:25:38 +0000 > Nadav Amit <namit@xxxxxxxxxx> wrote: > > >> I will need to further debug it, but this issue does not occur every time. >> >> The kernel didn’t crash exactly - it’s more of a deadlock. I have lockdep >> enabled, so it is not a deadlock that lockdep knows. Could it be that >> somehow things just slowed down due to IPIs and mostly-disabled IRQs? I have >> no idea. I would need to recreate the scenario. > > You have lockdep enabled and you are running function tracing with stack > trace on? So you are doing a stack trace on *every* function that is traced? > > I don't think you hit a deadlock, I think you hit a live lock. You could > possibly slow the system down so much that when an interrupt finishes it's > time for it to be triggered again, and you never make forward progress. It might be the issue. Perhaps I have a bug, because my code was supposed to either enable stack-tracing with selected functions or create a trace all function but *without* stack-tracing. Thanks for the pointer and sorry for the noise. Regards, Nadav
