From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable, stacktrace with >4096M of dom0_mem Date: Wed, 09 Sep 2009 15:35:44 -0700 Message-ID: <4AA82DC0.9090305@goop.org> References: <20090908184927.GJ31123@reaktio.net> <41057.67598.qm@web56102.mail.re3.yahoo.com> <20090908192246.GK31123@reaktio.net> <20090908193433.GA6944@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20090908193433.GA6944@phenom.dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Konrad Rzeszutek Wilk Cc: Boris Derzhavets , xen-devel@lists.xensource.com, fedora-xen@redhat.com List-Id: xen-devel@lists.xenproject.org On 09/08/09 12:34, Konrad Rzeszutek Wilk wrote: > On Tue, Sep 08, 2009 at 10:22:46PM +0300, Pasi K=E4rkk=E4inen wrote: > =20 >> On Tue, Sep 08, 2009 at 12:14:54PM -0700, Boris Derzhavets wrote: >> =20 >>> Console drops into the same stack trace in both cases. >>> >>> =20 >> Jeremy: Any ideas could some recent change in pv_ops dom0 kernel cause >> usb stuff to stop working with >4096M of dom0 memory?=20 >> =20 > The last set of changes in Jeremy's kernel are a set of patches I sent, > so the problem is most likely caused by my work. > =20 Yes, I suspect so. Last time around, USB was good for highlighting problems in the swiotlb code. If there's a problem at 4G then generally its some physical address being accidentally truncated by an implicit cast in the middle of an expression. Or something else. (Why, yes, I am helpful today.) J > A dmesg from both Xen and Linux kernel would be most helpfull. Also > a lspci -vvv would be nice. > > And as Pasi suggested, booting the same kernel without Xen would > be most helpful. > > > =20 >> dom0_mem=3D4096M works >> dom0_mem=3D4097M fails with stacktrace >> >> Boris: What was the last kernel that worked without backtraces?=20 >> Also, does that same kernel work as baremetal (without Xen) ? >> =20 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > > =20