[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.1804231528130.2077@nanos.tec.linutronix.de>
Date: Mon, 23 Apr 2018 15:35:26 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: "Wan, Kaike" <kaike.wan@...el.com>
cc: "Marciniszyn, Mike" <mike.marciniszyn@...el.com>,
"Dalessandro, Dennis" <dennis.dalessandro@...el.com>,
"Weiny, Ira" <ira.weiny@...el.com>,
"Fleck, John" <john.fleck@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>
Subject: RE: hrtimer (rdmavt RNR timer) was lost
On Mon, 23 Apr 2018, Wan, Kaike wrote:
> > Can you apply the following debug patch and enable the hrtimer_start trace
> > point and send me the full trace or upload it somewhere?
>
> The original trace was about 29GB and I filtered it with
> "0000000066dda1ea" (the offending base) to generate a 1.4GB file that I
> could open and investigate. I am not sure how I can send them to you. Do
> you have somewhere I can upload to?
>
> I can try your debug patch and again I am anticipating a big trace file.
Well, you can find the spot where the fail happens and then extract the
full thing from 2s before that point to 1s after. That should be reasonably
small and good enough. Let me know when you have it and how big it is
(compressed) and we'll figure something out how to transport it.
Thanks,
tglx
Powered by blists - more mailing lists