Re: frequent lockups in 3.18rc4
From: Martin van Es
Date: Thu Feb 12 2015 - 06:09:28 EST
To follow up on this long standing promise to bisect.
I've made two attempts at bisecting and both landed in limbo. It's
hard to explain but it feels like this bug has quantum properties;
I know for sure it's present in 3.17 and not in 3.16(.7). But once I
start bisecting it gets less pronounced. I know it sound vague, but
the best explanations I get come up with are:
- The out-of-kernel dvb-c driver and hardware are playing funny games
(although being absolutely stable in 3.16?)
- and/or the problem consists of two or more commits that
independently don't express themselves like I see in 3.17?
So, my second bisecting ended at
3be738ad55d8e2b9d949eb0d830de5aa4d4f8e05, which is nonsense because
it's a commit to a staging module that I don't even compile.
Best I can come up with now is try the next mainline that has all the
fixes and ideas in this thread incorporated. Would that be 3.19?
I'm sorry I couldn't be more helpful.
On Sat, Dec 6, 2014 at 10:14 PM, Martin van Es <mrvanes@xxxxxxxxx> wrote:
> On Sat, Dec 6, 2014 at 9:09 PM, Linus Torvalds
> <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote:
>> On Sat, Dec 6, 2014 at 8:22 AM, Martin van Es <mrvanes@xxxxxxxxx> wrote:
>>> Hope this may help in finding the right direction for this bug?
>> If you can reproduce it with your spare J1900 system and could perhaps
>> bisect it there, that would be a huge help.
> I'll give it a shot and see if I can get to freeze it on 3.17.3 as a
> start by playing content from the prd backend, but don't expect fast
> respons times... busy man...
If 'but' was any useful, it would be a logic operator
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/