On Wed, Sep 09, 2009 at 07:55:34AM -0700, Boris Derzhavets wrote:
> >I am not sure if I understand you correctly. Are you saying that 2.6.31-rc8
> >boots without the stack-trace failure? Can you attach the dmesg please
> >and also 'lspci -vvv' output?
>
> If i built rc8 on F11 ( dual booting) with F12 and install kernel and modules via
**************************************************************************
This in done on F12
# mount
/dev/mapper/serverfedora11-lv_root /mnt
#cd /mnt/usr/src/linux-2.6-xen
F11's folder /mnt/usr/src/linux-2.6-xen contains prepared kernel and
modules compiled on F11.
Here we copy from F11's folder fo F12 FS
# make modules_install install
( mount was done on F12 ), i get a stable kernel rc8 on F12.
View dmesg.log . It's clean
*************************************************************************
You contradict yourself latter where you say that the 2.6.31-rc8 built
on F12 and installed on F12 has a stack-trace. Or am I misreading it?
>
> If i compile and and install on F12 kernel has stack trace and is pretty unstable at
> runtime.
Is the kernel you build on F11 (that being called ServerXen35), with
and without Xen producing the same dmesg? That being a dmesg that
did not have a stack trace.
>
>
Now i am sending two dmesg reports :-
> 1. Kernel 2.6.31-rc8 been built on F11 and installed on F12
> dmesg.log.gz (clean)
> 2. Kernel 2.6.31-rc8 been built on F12 and installed on F12
> dmesg.1.gz ( stack trace here)
> "lspci -vvv" report has been also sent to you per your request, but i will repeat. This one is for C2D E8400 box.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxhttp://lists.xensource.com/xen-devel
Home