[Fedora-xen] 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 at yahoo.com
Wed Sep 9 07:19:20 UTC 2009
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 <bderzhavets at yahoo.com> wrote:
From: Boris Derzhavets <bderzhavets at 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 at iki.fi>, "Konrad Rzeszutek Wilk" <konrad.wilk at oracle.com>
Cc: "Jeremy Fitzhardinge" <jeremy at goop.org>, xen-devel at lists.xensource.com, fedora-xen at redhat.com
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 <konrad.wilk at oracle.com> wrote:
From: Konrad Rzeszutek Wilk <konrad.wilk at oracle.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 at iki.fi>
Cc: "Boris Derzhavets" <bderzhavets at yahoo.com>, xen-devel at lists.xensource.com, "Jeremy Fitzhardinge" <jeremy at goop.org>, fedora-xen at redhat.com
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
Xen-devel at lists.xensource.com
http://lists.xensource.com/xen-devel
-----Inline Attachment Follows-----
--
Fedora-xen mailing list
Fedora-xen at redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/fedora-xen/attachments/20090909/ec573ef1/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dmesg.1.gz
Type: application/x-gzip
Size: 15354 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/fedora-xen/attachments/20090909/ec573ef1/attachment.bin>
More information about the Fedora-xen
mailing list