From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: Konrad Rzeszutek Wilk <konrad@darnok.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: question about i915 driver in dom0
Date: Fri, 6 Jan 2012 09:37:19 -0500 [thread overview]
Message-ID: <20120106143719.GA5078@phenom.dumpdata.com> (raw)
In-Reply-To: <AADFC41AFE54684AB9EE6CBC0274A5D102DDA2@SHSMSX102.ccr.corp.intel.com>
> > > I hadn't seen it... but then my main desktop box where I run intensive
> > > tests (ie, games) is radeon and nvidia so hadn't really tried seen this.
> > > The box that has i915 just does some simple framebuffer manipulation and
> > > that looks OK.
> >
> > yes, framebuffer console works well in my side too.
Good.
> > > Do you see the same symptoms - checkboard screen?
> >
> > Not exactly. The screen becomes white, and then the system becomes
> > unstable and hang several minutes later. It's possible that mine is a
> > different issue than listed on the wiki page, since many reasons may
> > finally reach the same symptom - GPU hang... :/
>
> well, there happens once with a checkboard screen, with the rest all
> white screens.
>
> >
> > >
> > > The LKML had some fixes for this from Keith Packard. Something about
> > > using i915.semaphores=0 I think. And I thought I saw some fixes for
> > > 3.2-rc7 for this but not sure..
> >
> > I'll have a try on latest Linux on this. But I suspect that this may be a
> > virtualization specific bug (e.g. similar gfn/mfn issue as nvidia case),
> > because same dom0 image could run glxgear smoothly on bare metal.
> >
>
> I used latest 3.2 release, no difference.
What is the motherboard you have? I just bought an "DQ67SW" which perhaps
has the same video card?
But more interestingly - are you building your kernel from scratch? There
was some requirements in having CONFIG_IOMMU_DMAR in the kernels - otherwise
the intel-gtt.c would use the 'virt_to_phys' code instead of the DMA API.
And that caused an endless amount of pain.
>
> i915.semaphores=0 has no effect.
>
> But I observed below warnings in the boot process:
> [ 8.872430] [drm] MTRR allocation failed. Graphics performance may suffer.
> [ 18.384552] microcode: CPU0 update to revision 0x1b failed
>
> Not sure whether above two issues may have impact on the said problem.
> I know microcode update is still missing in upstream, but not sure about any
Right, microcode is ... pending hpa's coming back from paternity leave.
> MTRR specific pending patches.
The MTRR are not in, but the graphics code should still work.
next prev parent reply other threads:[~2012-01-06 14:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-27 6:47 question about i915 driver in dom0 Tian, Kevin
2012-01-03 16:59 ` Konrad Rzeszutek Wilk
2012-01-06 0:57 ` Tian, Kevin
2012-01-06 5:37 ` Tian, Kevin
2012-01-06 14:37 ` Konrad Rzeszutek Wilk [this message]
2012-01-09 5:09 ` Tian, Kevin
2012-01-09 15:04 ` Konrad Rzeszutek Wilk
2012-01-10 5:47 ` Tian, Kevin
2012-01-10 14:38 ` Konrad Rzeszutek Wilk
2012-01-12 2:27 ` Tian, Kevin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120106143719.GA5078@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=kevin.tian@intel.com \
--cc=konrad@darnok.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.