On Fri, Nov 21, 2014 at 07:37:42AM +0100, Ingo Molnar wrote:
> It might make sense to disable the softlockup detector altogether
> and just see whether trinity finishes/wedges, whether a login
> over the console is still possible - etc.
I can give that a try later.
> The softlockup messages in themselves are only analytical, unless
> CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE=1 is used.
Hm, I don't recall why I had that set. That should make things easier
to debug if the machine stays alive a little longer rather than
panicing. At least it might make sure that I get the full traces
over usb-serial.
Additionally, it might make ftrace an option.
The last thing I tested was 3.17 plus the perf fixes Frederic pointed
out yesterday. It's survived 20 hours of runtime, so I'm back to
believing that this is a recent (ie, post 3.17 bug).
Running into the weekend though, so I'm not going to get to bisecting
until Monday probably. So maybe I'll try your idea at the top of this
mail in my over-the-weekend run.
Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
