From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Re: xen-swiotlb Date: Fri, 27 Aug 2010 10:19:55 -0400 Message-ID: <20100827141954.GA32011@phenom.dumpdata.com> References: <1045449371.20100815232839@eikelenboom.it> <20100816144353.GB29351@phenom.dumpdata.com> <1077869382.20100816213227@eikelenboom.it> <20100826214321.GA17372@phenom.dumpdata.com> <20100827064637.GY2804@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: <20100827064637.GY2804@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Cc: Sander Eikelenboom , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On Fri, Aug 27, 2010 at 09:46:37AM +0300, Pasi K=E4rkk=E4inen wrote: > On Thu, Aug 26, 2010 at 05:43:21PM -0400, Konrad Rzeszutek Wilk wrote: > >=20 > > >=20 > > > Apart from fixing the xhci in the end, is there a way to prevent xe= n from freezing altogether without leaving a trace ? > >=20 > > I am still puzzled as why Xen hypervisor would freeze. It _should_ wo= rk > > just fine. > >=20 >=20 > There has been multiple reports about these freezes..=20 > for one user 'acpi=3Dht' fixes the freezes. >=20 > Or another way: libata.noacpi=3D1 fixes it aswell for that user. Weren't those bootup options thought? As in, without those the user was not able to boot? Not as something where two days in the machine suddenly stops working?