[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] Errors when build 2.6.31-rc8
- To: M A Young <m.a.young@xxxxxxxxxxxx>
- From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
- Date: Sat, 5 Sep 2009 05:45:39 -0700 (PDT)
- Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
- Delivery-date: Sat, 05 Sep 2009 05:46:13 -0700
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=H+7HFP2jBnh+IuExqzMcSZQWwlWYyABwTecs+6PH2yxi1nJZGKXatu3XObnRzsSBhlKwll37E0gd9ShtLxzlmMgKoNGPWhL/f2V49cm8ph3h7f2ERyo+3gfXlurx4agPW2qcvZ1YiXGffw7mk4MEgwyL0hHUJTXEDkg3VWKBxaQ=;
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
After this change:-
-*- /dev/agpgart (AGP Support) --->
< > Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)
i was able to build 2.6.31-rc8 (with Xen Dom0 support).
However, attempt to load 2.6.31-rc8 either under Xen 3.5 or Xen 3.4.1 causes console to drop into stack trace and hangs.
Thank you.
Boris.
--- On Sat, 9/5/09, M A Young <m.a.young@xxxxxxxxxxxx> wrote:
From: M A Young <m.a.young@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Errors when build 2.6.31-rc8
To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
Cc: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>, "Xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Date: Saturday, September 5, 2009, 7:31 AM
On Sat, 5 Sep 2009, Boris Derzhavets wrote:
> After fresh git clone, git checkout tune "make menuconfig" the same way as
> for RC6
>
> When build :-
>
> In file included from /usr/src/linux-2.6-xen/arch/x86/include/asm/agp.h:5,
> from drivers/gpu/drm/ttm/ttm_agp_backend.c:40:
> include/linux/swiotlb.h:48: warning: ?enum dma_data_direction? declared inside
> parameter list
I think there is a conflict between the newer drm code and swiotlb. I have
seen this for a while on my Fedora builds as Fedora Rawhide seems to get the new drm code before it makes it into the official kernel. You can work around it by disabling a small number of drm related kernel options, though you probably lose some functionality by doing so.
Michael Young
-----Inline Attachment Follows-----
|
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
