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]

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.

Boris.

--- On Tue, 9/8/09, Boris Derzhavets  wrote:

From: Boris Derzhavets 
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" , "Konrad Rzeszutek Wilk" 
Cc: "Jeremy Fitzhardinge" , [e-mail], [e-mail]
Date: Tuesday, September 8, 2009, 3:45 PM

Dmesg log for rc8 under Xen 3.4.1 on F12 rawhide attached.

Boris.

--- On Tue, 9/8/09, Konrad Rzeszutek Wilk  wrote:

From: Konrad Rzeszutek Wilk 
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" 
Cc: "Boris Derzhavets" , [e-mail], "Jeremy Fitzhardinge" , [e-mail]
Date: Tuesday, September 8, 2009, 3:34 PM

On Tue, Sep 08, 2009 at 10:22:46PM +0300, Pasi Kärkkäinen wrote:
> On Tue, Sep 08, 2009 at 12:14:54PM -0700, Boris

Derzhavets wrote:
> > Console drops into the same stack trace in  both cases.
>
> Jeremy: Any ideas could some recent change in pv_ops dom0 kernel cause
> usb stuff to stop working with >4096M of dom0 memory?

The last set of changes in Jeremy's kernel are a set of patches I sent,
so the problem is most likely caused by my work.

A dmesg from both Xen and Linux kernel would be most helpfull. Also
a lspci -vvv would be nice.

And as Pasi suggested, booting the same kernel without Xen would
be most helpful.
> dom0_mem=4096M works
> dom0_mem=4097M fails with stacktrace
>
> Boris: What was the last kernel that worked without backtraces? 
> Also, does that same kernel work as baremetal (without Xen) ?

_______________________________________________
Xen-devel mailing list
[e-mail]
http://lists.xensource.com/xen-devel

-----Inline Attachment Follows-----

--
Fedora-xen mailing list
[e-mail]
https://www.redhat.com/mailman/listinfo/fedora-xen

[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

[Konrad Rzeszutek Wilk]

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  wrote:
>
> From: Boris Derzhavets 
> 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" , "Konrad Rzeszutek Wilk" 
> Cc: "Jeremy Fitzhardinge" , [e-mail], [e-mail]
> 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?