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

[Boris Derzhavets <bderzhavets@xxxxxxxxx>]

>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@xxxxxxxxxx> wrote:

From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
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@xxxxxxxxx>
Cc: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, fedora-xen@xxxxxxxxxx
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@xxxxxxxxx> wrote:
>
> From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
> Subject: Re: [Xen-devel] Re: Xorg on JF 2.6.31-rc8 with xen 3.5 unstable, stacktrace with >4096M of dom0_mem
> To: "Pasi Kärkkäinen" <pasik@xxxxxx>, "Konrad Rzeszutek Wilk" <konrad.wilk@xxxxxxxxxx>
> Cc: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, fedora-xen@xxxxxxxxxx
> 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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

Attachment: dmesg.log.gz
Description: GNU Zip compressed data

Attachment: dmesg.1.gz
Description: GNU Zip compressed data

Attachment: lspci.vvv.gz
Description: GNU Zip compressed data

--
Fedora-xen mailing list
Fedora-xen@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-xen