Hello Borislav, On 11/19/2013 11:15 AM, Borislav Petkov wrote: > On Tue, Nov 19, 2013 at 11:01:14AM +0100, Francis Moreau wrote: >> I think the easiest way to do it is to install a minimal system on a >> USB stick and try to reproduce first in order to preserve my system. > > Yep, sounds simple enough. > >> Then I'll try to see if this issue exists in a previous kernel version >> and if so, I'll do a git-bisect session. >> >> I can't find a quicker way to do that although using git-bisect (which >> implies several kernel builds) is a PITA. > > You can start with a coarse bisect by testing the major kernel versions > first, i.e. 3.11, 3.10, 3.9 ... and once you find good and bad, then you > can do the git-bisect thing. >
Unfortunately the bisect session didn't give any positive results: I couldn't be sure if a specific revision was good or bad because the bug wasn't reproductible every time. But I got a different kernel oops on my stripped system that may give us a clue: http://imgur.com/zdCknbY Does this help ? Thanks. -- 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/