From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dietmar Hahn Subject: Re: dom0 / hypervisor hang on dom0 boot Date: Fri, 17 May 2013 09:10:52 +0200 Message-ID: <3605548.xZS9Ex6Icv@amur.mch.fsc.net> References: <3374329.VOz1gdFjBv@amur.mch.fsc.net> <2903155.vZYnOgsWoo@amur.mch.fsc.net> <5194FEFC02000078000D6C35@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <5194FEFC02000078000D6C35@nat28.tlf.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: xen-devel@lists.xen.org Cc: Andrew Cooper , Donald D Dugger , Jan Beulich , Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org Am Donnerstag 16 Mai 2013, 14:45:00 schrieb Jan Beulich: > >>> On 16.05.13 at 15:16, Dietmar Hahn wrote: > > Am Donnerstag 16 Mai 2013, 13:10:27 schrieb Jan Beulich: > >> 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. > > I took this for given. But I'd expect the 12.2 kernel on the 12.3 > hypervisor would work too (though worth a try to be certain), i.e. > I rather expect the kernel side (AGP/DRM) changes to have > introduced this (which doesn't imply the hypothetical fix necessarily > to be to the kernel - that obviously depends on understanding what > the problem is). I tried openSuSE-12.2 kernel-xen-3.4.45-1.1.gba139d5.x86_64.rpm successfully. So you are right it seems to be the kernel side. Dietmar. -- Company details: http://ts.fujitsu.com/imprint.html