Re: Kernel error with todays -unstable.

[Matt Ayres <matta@tektonic.net>]

Keir,

Have you any update on this bug I would label as _CRITICAL_ seeing as 
the same hardware, config file, and 2.6.16.13 worked just fine.  Even 
the newer hypervisor and 2.6.16.13 from previous -unstable tree boots fine.

Thanks,
Matt

Keir Fraser wrote:
> 
> 
> On 21/9/06 19:52, "Keir Fraser" <Keir.Fraser@cl.cam.ac.uk> wrote:
> 
>>> Got this changing from  2.6.16.13 to 2.6.16.29.. running .13 under the
>>> same xen binary works fine.
>> Is the Xen binary built from a recent repository (i.e., which includes
>> 2.6.16.29), or an older Xen version? It shouldn't matter, but if you run
>> 2.6.16.29 okay with latest Xen but not with older Xen then it probably
>> indicates a compatibility issue that we should look into.
> 
> Ok, actually the logs you posted are sufficient to see that the Xen and
> Linux are a 'matched pair'. So... Did you modify the Linux config at all?
> 
>  -- Keir
> 
>