Re: Strange error in domU after dom0 update

[Jeremy Fitzhardinge <jeremy@goop.org>]

On 10/27/09 07:44, Andreas Florath wrote:
> It seams that the root cause for this is a bug in the kernel 2.6.31.4
> pv_ops.  Tried a bisection and ended at version
> d2af313fcf20275d4008725f32f1974bde06ec9e, which is good, i.e. works
> without the described problems and
> 9cf89da8cb207818c029975f261ea672addbb801 which is bad.

Thanks for investigating this.

> There are some other problems in version
> 0148adde28789aa72f6210add9ac34625309535b which does even not boot, so
> it's somewhat tricky to do a bisection when there is more than one
> problem :-(

Unfortunately bisecting on the pvops tree is a bit awkward because
individual topic branches don't necessarily boot on their own.

> If it helps to find the bug, I can just try some other versions in
> between by random.
>
> Note that the merge after the version which works for me
> (3dd81018a392941fcc722ee521de344527481eb8) changed things in the
> network layer.

Yes, that's the netchannel2 merge.  Do you have it enabled in your
config?  If it is not enabled then it definitely shouldn't have any
effect on your system.  If it is enabled then it could be buggy because
it is very new code.

    J