With attached config, boot failed on my core i3 machine. Bisection log is also attached (bisectlog). Probably, the patchset from [email protected] (https://lkml.org/lkml/2011/5/26/433) breaks things up.
It seems the following commit is responsible:
commit f144a6b4d1688675d88990e29567b2335b48205e
Author: Andy Lutomirski <[email protected]>
Date: Mon May 23 09:31:30 2011 -0400
On Sat, May 28, 2011 at 6:46 AM, Rakib Mullick <[email protected]> wrote:
> With attached config, boot failed on my core i3 machine. Bisection log is also attached (bisectlog). Probably, the patchset from [email protected] (https://lkml.org/lkml/2011/5/26/433) breaks things up.
> It seems the following commit is responsible:
>
> ?commit f144a6b4d1688675d88990e29567b2335b48205e
> ?Author: Andy Lutomirski <[email protected]>
> ?Date: ? Mon May 23 09:31:30 2011 -0400
>
I would bet it's one of the other commits in the series, not that one.
Can you try this:
http://git.kernel.org/?p=linux/kernel/git/rostedt/linux-2.6-trace.git;a=commit;h=89e1be50c68eb5e58b873dce87bbac627ee18d1f
If that doesn't fix it, what was the failure? Attempted to kill init
is most likely, but whatever showed up on the screen would be helpful.
--Andy
>
>
>
>
On Sat, May 28, 2011 at 5:16 PM, Andrew Lutomirski <[email protected]> wrote:
> On Sat, May 28, 2011 at 6:46 AM, Rakib Mullick <[email protected]> wrote:
>> With attached config, boot failed on my core i3 machine. Bisection log is also attached (bisectlog). Probably, the patchset from [email protected] (https://lkml.org/lkml/2011/5/26/433) breaks things up.
>> It seems the following commit is responsible:
>>
>> ?commit f144a6b4d1688675d88990e29567b2335b48205e
>> ?Author: Andy Lutomirski <[email protected]>
>> ?Date: ? Mon May 23 09:31:30 2011 -0400
>>
>
> I would bet it's one of the other commits in the series, not that one.
>
> Can you try this:
>
> http://git.kernel.org/?p=linux/kernel/git/rostedt/linux-2.6-trace.git;a=commit;h=89e1be50c68eb5e58b873dce87bbac627ee18d1f
>
> If that doesn't fix it, what was the failure? ?Attempted to kill init
> is most likely, but whatever showed up on the screen would be helpful.
>
Yes, thanks. It does fix the failure.
Thanks,
Rakib
> --Andy
>
>>
>>
>>
>>
>