Re: [Xen-devel] Problem: Pattern with vertical colored lines on the dom0
On Tue, Sep 21, 2010 at 09:19:51AM +0200, Dietmar Hahn wrote:
> Am 20.09.2010 schrieb Konrad Rzeszutek Wilk:
> > On Fri, Sep 17, 2010 at 03:20:11PM +0200, Dietmar Hahn wrote:
> > > Hi list,
> > >
> > > I have a problem with a new laptop (reproducable on other machines too)
> > > and the
> > > xen hypervisor.
> > > When the hypervisor gets booted with VESA mode 800x600 I see some
> > > messages and
> > > then the screen contents is switched into a pattern of vertical colored
> > > lines
> > > and never comes back.
> > > In text mode all works well, but later the pattern appears when the X
> > > servers
> > > starts.
> > > I disabled VTd in the bios and now all went fine.
> > So no VT-d and the you have no trouble even with VESA 800x600?
And if you have VT-d enabled and you don't include the "vga=mode-0x314" then
it works fine too?
Just curious, but why did you try the 'vga=mode' option?
> > Are there any
> > errors reported by Xen when you use VT-d?
> In the original mail I sent the full hypervisor log from the error case (VT-d
> switched on). I couldn't spot an error message.
> > Can you ping the machine even
> > if the screen is showing vertical lines?
> Yes the machine runs well. I can work remotely. Only the console is affected.
> > > I saw this first with SLES11 SP1 but could reproduce it with the
> > > xen-unstable
> > > hypervisor.
> > What about the Linux kernel? Is this happening when you use the PVOPS
> > kernel?
> I didn't try this out because at the end I could reproduce this behaviour
> booting the hypervisor and before dom0 starts.
> Another thing is when starting the X server I see kernel messages in a loop:
> [ 1193.549808] [drm:i915_hangcheck_elapsed] ERROR Hangcheck timer elapsed...
> GPU hung
> [ 1193.572464] render error detected, EIR: 0x00000000
> [ 1193.586720] i915: Waking up sleeping processes
> [ 1193.600679] [drm:i915_do_wait_request] ERROR i915_do_wait_request returns
> -5 (awaiting 1 at 0)
Ugh, that looks nasty.
> dom0 kernel is from SLES11 SP1 18.104.22.168-0.7-xen.
> As in the orignal mail mentioned I would assume it's a problem with the bios
> and maybe some access stuff due to the iommu. But I'am not familiar enough
> So I hoped anybody on the list could give me a hint while reading the logs in
> my original mail ;-)
> Company details: http://ts.fujitsu.com/imprint.html
> Xen-devel mailing list
Xen-devel mailing list