[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] dom0 / hypervisor hang on dom0 boot

  • To: xen-devel@xxxxxxxxxxxxx
  • From: Dietmar Hahn <dietmar.hahn@xxxxxxxxxxxxxx>
  • Date: Thu, 16 May 2013 15:16:54 +0200
  • Cc: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Donald D Dugger <donald.d.dugger@xxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
  • Delivery-date: Thu, 16 May 2013 13:18:03 +0000
  • 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:Cc:Subject:Date:Message-ID: User-Agent:In-Reply-To:References:MIME-Version: Content-Transfer-Encoding:Content-Type; b=l+cwuxibtkKn+iKCkI0Ayl27xOw60/QykRj/h7Rk9AA870Ma2JVZarRa Kgi8fDS6FzLmH2D4vAfeF0kQ2nbJw3uRInktWKe6tKbNcZbM3jA2GD95W LtV5aypUjsZzFTjQd5gcYXCO1wYUPt4x9Ik8DxI4LKuzqtHT/ly3N4jDW KnT5VFGA0BZr6WE60gl5L1/CDq2w/GMo7fzGk/8jFQanpK2yyMFfYtj9B lMEmdIvgLlXtXDM5ykaKK7xr0Dsjq;
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>

Am Donnerstag 16 Mai 2013, 13:10:27 schrieb Jan Beulich:
> >>> On 16.05.13 at 13:07, Dietmar Hahn <dietmar.hahn@xxxxxxxxxxxxxx> wrote:
> > The function behind the pointer intel_private.driver->write_entry is
> > i965_write_entry(). And the interesting instruction seems to be:
> >   writel(addr | pte_flags, intel_private.gtt + entry);
> > 
> > I added another printk() on start of the function i965_write_entry().
> > And surprisingly  after printing a lot of messages the kernel came up!!!
> > But now I had other problems like losing the audio device (maybe timeouts).
> > So maybe the hang is a timing problem?
> Apparently. As the caller is running this in a loop, did you check
> whether it's the first or always the same entry that it hangs on?

I did a fast check, did the first entry and a printk() and than the loop with
the other entries and the message  after the first entry was printed on the
serial log.

> > What I wanted to check is, what the hypervisor is doing while the system 
> > hangs.
> Probably nothing in this case, as it doesn't get involved in the MMIO
> write being carried out.
> > Has anybody an idea maybe a timer and after 30s printing a dump of the 
> > stack 
> > of all cpus?
> That would be the watchdog, which you said doesn't kick in either.


> I'm afraid this is a problem with the graphics device's processing of
> the written data (locking up the machine at the bus level). Without
> help from someone knowing what the driver is supposed to do here,
> and what therefore might be going wrong, I don't see good chances
> of making progress here. Don - any idea who that could be?

I should mention that with openSuSE 12.2 and older all worked flawless.


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

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.