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
# mount /dev/mapper/serverfedora11-lv_root /mnt #cd /mnt/usr/src/linux-2.6-xen # make modules_install install
in F12 env, then i get a stable kernel rc8 on F12.
If i compile and and install on F12 kernel has stack trace and is pretty unstable at runtime.
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.
Boris.
--- On Wed, 9/9/09, Konrad Rzeszutek Wilk konrad.wilk@oracle.com wrote:
From: Konrad Rzeszutek Wilk konrad.wilk@oracle.com Subject: Re: [Xen-devel] Dmesg log for 2.6.31-rc8 kernel been built on F12 (rawhide) vs log for same kernel been built on F11 and installed on F12 To: "Boris Derzhavets" bderzhavets@yahoo.com Cc: "Jeremy Fitzhardinge" jeremy@goop.org, xen-devel@lists.xensource.com, fedora-xen@redhat.com Date: Wednesday, September 9, 2009, 10:10 AM
On Wed, Sep 09, 2009 at 12:19:20AM -0700, Boris Derzhavets wrote:
Previous 2.6.31-rc8 kernel was built on F11 and installed with modules on F12. Current kernel has been built on F12 (2.6.31-0.204.rc9.fc12.x86_64) and installed on F12 before loading under Xen 3.4.1. Dmesg log looks similar to Michael Yuong's 'rc7.git4' kernel for F12.
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?
Boris.
--- On Tue, 9/8/09, Boris Derzhavets bderzhavets@yahoo.com wrote:
From: Boris Derzhavets bderzhavets@yahoo.com Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable, stacktrace with >4096M of dom0_mem To: "Pasi Kärkkäinen" pasik@iki.fi, "Konrad Rzeszutek Wilk" konrad..wilk@oracle.com Cc: "Jeremy Fitzhardinge" jeremy@goop.org, xen-devel@lists.xensource.com, fedora-xen@redhat.com Date: Tuesday, September 8, 2009, 3:45 PM
Dmesg log for rc8 under Xen 3.4.1 on F12 rawhide attached.
I took a look at the dmesg and it looks fine. I did not see a stack trace in it?
Maybe I was looking at the wrong one. This is the identifying timestamp at the beginning: Linux version 2.6.31-rc8 (root@ServerXen35) (gcc version 4.4.1 20090725 (Red Hat 4.4.1-2) (GCC) ) #3 SMP Tue Sep 8 04:24:43 EDT 2009
is that the right dmesg?
*************************************************** Yes , this one is fine. Kernel had been built on F11 and installed on F12 ***************************************************
_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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
# mount /dev/mapper/serverfedora11-lv_root /mnt #cd /mnt/usr/src/linux-2.6-xen # make modules_install install
in F12 env, then i get a stable kernel rc8 on F12.
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 :-
- 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.