WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Problem: Pattern with vertical colored lines on the dom0

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-devel] Problem: Pattern with vertical colored lines on the dom0 screen
From: Dietmar Hahn <dietmar.hahn@xxxxxxxxxxxxxx>
Date: Thu, 23 Sep 2010 13:53:34 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Jan Beulich <JBeulich@xxxxxxxxxx>
Delivery-date: Thu, 23 Sep 2010 05:51:41 -0700
Dkim-signature: v=1; a=rsa-sha256; c=simple/simple; d=ts.fujitsu.com; i=dietmar.hahn@xxxxxxxxxxxxxx; q=dns/txt; s=s1536b; t=1285242832; x=1316778832; h=from:to:subject:date:cc:references:in-reply-to: mime-version:content-transfer-encoding:message-id; z=From:=20Dietmar=20Hahn=20<dietmar.hahn@xxxxxxxxxxxxxx> |To:=20Konrad=20Rzeszutek=20Wilk=20<konrad.wilk@xxxxxxxxx m>|Subject:=20Re:=20[Xen-devel]=20Problem:=20Pattern=20wi th=20vertical=20colored=20lines=20on=20the=20dom0=20scree n|Date:=20Thu,=2023=20Sep=202010=2013:53:34=20+0200|Cc: =20xen-devel@xxxxxxxxxxxxxxxxxxx,=0D=0A=20Jan=20Beulich =20<JBeulich@xxxxxxxxxx>|References:=20<201009171520.1190 3.dietmar.hahn@xxxxxxxxxxxxxx>=20<201009221506.14610.diet mar.hahn@xxxxxxxxxxxxxx>=20<20100922135659.GB2734@dumpdat a.com>|In-Reply-To:=20<20100922135659.GB2734@xxxxxxxxxxxx >|MIME-Version:=201.0|Content-Transfer-Encoding:=207bit |Message-Id:=20<201009231353.34913.dietmar.hahn@xxxxxxxxx u.com>; bh=zEPug+K9PMoPrvDWCsQW58bRVury1ITx9wQLNoPCArQ=; b=S7MYBBmr6d4TqIZJjtp7FzTVFDoFCid9rHVBhGHTOKrgNc+0wWr64QpP qAuunz44AiZr4eBGFqPQV88nCLbz7bqRQajYZmEcWCJ9SZ+gwyJ6TewJY N6DsUl8VcThEsSK1yc31+uL1GiWGj/ywof3HCcsVryl3ZDML2hp4XmPrS XCN7Y9zfE0RAQ5ZoRkjRSJ2HJtc1bMHSrK13wRDAPtTYQi/tLX877SGZx A8HYwVjpduRQiOAS6sDE9LSYtMAwx;
Domainkey-signature: s=s1536a; d=ts.fujitsu.com; c=nofws; q=dns; h=X-SBRSScore:X-IronPort-AV:Received:X-IronPort-AV: Received:Received:From:To:Subject:Date:User-Agent:Cc: References:In-Reply-To:MIME-Version:Content-Type: Content-Transfer-Encoding:Message-Id; b=ssEnuG7+XxhBz5+PUJumvhA5B+Jhb5/BbVpiNNiiWHNlPGL9agm15wjk 5WhoefIh7/eyKO0zh+td9iA2p/ZahoxNrn/nWy7FG6/lQRFywM31AK2/5 ZOLLN90kkbhRiUmoCwHcV8soTiWpIIcrGXcIu5IAKQoE3Rya3nO3/SAQO 16015l3YoN/kVj3ei72KPbRQaZ6SoVjmmUQ/k13JynNZRujHYN1sU1jkh SzJk9NK4bFxaiGa8OwluXLic+dy49;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100922135659.GB2734@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <201009171520.11903.dietmar.hahn@xxxxxxxxxxxxxx> <201009221506.14610.dietmar.hahn@xxxxxxxxxxxxxx> <20100922135659.GB2734@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.13.5 (Linux/2.6.34.7-0.2-xen; KDE/4.4.4; x86_64; ; )
Hi Konrad,

first thanks for trying to help, but it seems I didn't explain the problem not
clear enough.

Am 22.09.2010 schrieb Konrad Rzeszutek Wilk:

> I don't know much about the SLES11 kernel, but I know that I fixed a lot of 
> KMS/DRM
> issues with the PVOPS kernel. It might be that some of those fixes didn't 
> make it
> in the SLES11 kernel.
> 
> The details are on http://wiki.xensource.com/xenwiki/XenPVOPSDRM
> 
> but you have an i915 and there weren't much of changes in the area.
> The big one for the PVOPS was that you had to have CONFIG_DMAR enabled
> so that the code for programming the GART would use the PCI API.

I will have a look on this to understand the behavior ;-)

> 
> My recommendation is to check the .config to see if CONFIG_DMAR
> was enabled for your kernel. After that, take a whirl with the
> PVOPS kernel: http://wiki.xensource.com/xenwiki/XenParavirtOps
> 
> Lastly, did a baremetal kernel work on this machine with X? That is
> a kernel without the Xen hypervisor running alongside?

Yes the SLES11 SP1 linux kernel with X11 works flawless.

In my original mail I wrote at the end:

> With staring at the console I could see that the switch to the screen pattern 
> is
> around the following messages (but no guarantee):
> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = ff:0.0
> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = ff:0.1
> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = ff:2.0
> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = ff:2.1
> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = ff:2.2
> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = ff:2.3

What I wanted to say is, I don't need a linux kernel to reproduce the problem!
With the argument vga=mode-0x314 on the Xen command line the screen gets
patterned while booting only the hypervisor.
As I have the test machine back again I will try to isolate the excat location
in the hypervisor where this effect gets triggered.
Thanks.

Dietmar.

-- 
Company details: http://ts.fujitsu.com/imprint.html

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>