From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: dom0 / hypervisor hang on dom0 boot Date: Wed, 15 May 2013 10:42:17 +0100 Message-ID: <5193749902000078000D6569@nat28.tlf.novell.com> References: <3374329.VOz1gdFjBv@amur.mch.fsc.net> <4214469.ll1CnAiDMX@amur.mch.fsc.net> <5193650202000078000D6514@nat28.tlf.novell.com> <1801825.vc7PjyMSRn@amur.mch.fsc.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1801825.vc7PjyMSRn@amur.mch.fsc.net> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Dietmar Hahn Cc: Andrew Cooper , Konrad Rzeszutek Wilk , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org >>> On 15.05.13 at 11:12, Dietmar Hahn wrote: > Am Mittwoch 15 Mai 2013, 09:35:46 schrieb Jan Beulich: >> >>> On 15.05.13 at 08:53, Dietmar Hahn wrote: >> > I tried iommu=debug and I can't see any faulting messages but Iam not >> > familiar with this code. >> > I attached the logging, maybe anyone can have a look on this. >> >> Indeed, there are no faults being logged. >> >> Following the comment yesterday - any chance you could try a >> recent master branch kernel? > > Sure I can do this, send me a link and I'll try this one. http://download.opensuse.org/repositories/Kernel:/HEAD/standard/x86_64/ > The other thing is that the hypervisor doesn't respond to key pressing on > the > serial line. This should always be working, shouldn't it? As long as it's alive, it should. > So I need some ideas how I can persuade the hypervisor to print a stack > trace > in this situation. Perhaps only (if at all) by instrumenting the hypervisor. The question of course is how easily/quickly you can narrow down the code region that it might be dying in. And whether it's a hypervisor action at all that causes the hang (as opposed to something the DRM code in Dom0 does). Jan