On Thu, 2020-08-27 at 15:11 +0200, bigeasy@xxxxxxxxxxxxx wrote: > On 2020-08-27 14:52:58 [+0200], To Roosen Henri wrote: > > On 2020-08-26 09:56:16 [+0000], Roosen Henri wrote: > > > Please let me know if there you find any unregularities in my > > > config or > > > suggestions on any usefull debugging-/forensic-config-options. > > > > I have no suggestions. Well besides memory debugging, lockdep and > > these > > kind of things. > > You never sent a backtrace, did you? I remember you posted a link a > pastebin which contain only the "middle" of the trace, not where it > started. Correct, please see https://lore.kernel.org/linux-rt-users/25412beffb96ab8c2b8f869bdac5a66c49faa5ca.camel@xxxxxxxxxxxxx/ Unfortunately the only v5.4 backtrace I currently have, the kernel was continuously dumping backtraces, therefore only the "middle" of the trace is available (https://paste.ubuntu.com/p/wZPCQv8KjX/). Currently testing 2 systems with v5.4.58-rt35 for 2 weeks now. Might take another 6 weeks or more before backtraces become available. The pastebins of the v4.14 kernels from the first post in this thread don't work anymore, I re-posted them here: 4.14.71-rt44 -> https://paste.ubuntu.com/p/rgSNr97w6k/ 4.14.106-rt56 -> https://paste.ubuntu.com/p/csVvJcYGrt/ 4.14.146-rt67 -> https://paste.ubuntu.com/p/crybp6F6Hb/ The v4.14 logs have a more complete backtrace. Seems the v4.14 log are all showing backtraces of SyS_read/SyS_write syscalls on unix-stream- sockets, but that might be just a red-herring. Thanks! Henri
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
