From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lukas Hejtmanek Subject: Re: [ofa-general] MTHCA driver for Linux Date: Fri, 18 Jan 2008 21:48:34 +0100 Message-ID: <20080118204834.GI4136@ics.muni.cz> References: <20080118170117.GH4136@ics.muni.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Roland Dreier Cc: xen-devel@lists.xensource.com, general@lists.openfabrics.org List-Id: xen-devel@lists.xenproject.org On Fri, Jan 18, 2008 at 12:36:00PM -0800, Roland Dreier wrote: > I would like to understand the underlying problem before blindly > setting the .shutdown method of the ib_mthca PCI driver section. The > mthca driver should be able to handle the hardware being in an > arbitrary state when it is reloaded -- that is why it resets the > adapter very early during initialization. Do you have any idea what > is going wrong in the case where the machine resets? The pcifront-end of xen is wrong. It touches somehow the device when the = DomU is starting. At that point, it resets the box hardly, if DomU has been st= arted already with IB driver since the box start up. If the IB device is properly shut down (rmmod ib_mthca), pcifront-end dri= ver=20 does not reset the box at DomU start up. --=20 Luk=E1=B9 Hejtm=E1nek