On Fri, Sep 18, 2026 at 04:39:57AM +0200, Christian Zigotzky wrote: > On 17/09/26 16:15, Shrikanth Hegde wrote: > > > > Hi Michal, > > > > > > > > > > Give it a try. > > > > > > > > I am suspecting both lockup, stack corruptions are secondary > > > > symptoms here. > > > > While recreate, I have different type of traces. > > > > > > Yes, it does work for the crash I see. > > > > Thanks. Give me sometime to see further on that. Didn't get any time > > today. > > > > > However, we hijacked the report > > > of KVM locking up on FSL Cyrus+, and that is likely a different problem > > > still not addressed. > > > > > > > Ah, that's what you meant. Yes, i still don't know where FSL Cyrus+ is > > stuck. > > > > I would need help from FSL Cyrus+ to get some logs or is there a way we > > can spin of > > a QEMU guest of it? We should have the log to start somewhere. > > > > > It's difficult to get a log because it freezes and can't write any error > messages to the log files. This bug is very old. We had this issue some > years ago but we was able to disable PREEMPT because we don't need it.
I would expect serial console and sysrq could give something, depending on how much of the kernel is frozen. Thanks Michal
