On Mon, Jan 30, 2017 at 12:39 AM, Sagi Grimberg <sagi@xxxxxxxxxxx> wrote: >> The first output (without the dates) is from dmesg, the second output >> is from journal. > > > Hey Robert, > > I'm still having a hard time understanding the traces. > How about you reproduce the error and attach a full dmesg > output? I suggest to reproduce once with debug_level=2 (to > cleanup some noise) and once with debug_level=4 and hopefully > we can understand what is getting lost. > > Also, please wait for the hang timeout watchdog traces, they > can give us confirmation that we are stuck waiting for a final > reference on some command. I left the capture of dmesg run for ~20 minutes after iSER failed. 2017-01-30_11:37:28_dmesg.log is level 2 and 2017-01-30_12:04:47_dmesg.log is level 4. The log files can be found at [1]. [1] http://mirrors.betterservers.com/trace/dmesg_logs.txz ---------------- Robert LeBlanc PGP Fingerprint 79A2 9CA4 6CC4 45DD A904 C70E E654 3BB2 FA62 B9F1 -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
