On Wed, Jun 26, 2013 at 09:18:53PM +0200, Oleg Nesterov wrote:
> On 06/25, Dave Jones wrote:
> >
> > Took a lot longer to trigger this time. (13 hours of runtime).
>
> And _perhaps_ this means that 3.10-rc7 without 8aac6270 needs more
> time to hit the same bug ;)
>
> Dave, I am not going to "deny the problem". We should investigate it
> anyway. And yes, 8aac6270 is not as trivial as it looks.
>
> But so far it is absolutely unclear how it can trigger such a problem,
> and none of the traces _look_ as if it should be blamed.
>
> Probably I should try to reproduce too...
I've tried so many different kernels this last week that I've forgotten
just how long I left the build without 8aac6270 running, but I'm pretty
sure it included an overnight run last weekend. Given I have two identical
machines that can reproduce it, I'll leave one running for a few days
with that reverted just to see if it turns up.
(Though, I seem to be walking into other issues [like the perf overflow bug
I reported last night] before seeing the lockups reproduce, so I'll keep an
eye on it).
Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
