From mboxrd@z Thu Jan 1 00:00:00 1970 From: Goncalo Gomes Subject: Re: crash in is_xen_swiotlb_buffer Date: Tue, 13 Mar 2012 14:26:17 +0000 Message-ID: <20120313142617.GA21587@eire.uk.xensource.com> References: <20120312163221.GA10987@eire.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Konrad Rzeszutek Wilk Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On Tue, 13 Mar 2012, Konrad Rzeszutek Wilk wrote: > > On Mar 12, 2012 12:28 PM, "Goncalo Gomes" > wrote: > > > > I've compiled unstable c/s: 5d20d2f6ffed and linux 3.2.9 but I've been > > Do you get similar issues with Xen 4.1? Can't say I tried it, but I can give it a spin. Any specific tag? > > experiencing a couple of panics since. Two times I was able to > > reproduce the crash by simply running upgrade-grub2 after fiddling > > with linux/xen cmdline options, but I noticed it does also crash on > > other (less known) occasions. No VMs have been setup yet, so it's > > purely a domain 0 setup so far. > > > > Attaching the relevant files, in the hope they may help understanding > > the cause of this. > > > > - xl-dmesg.out > > - dmidecode.out > > - lspci-vvv.out > > - 3.2.9-config > > Also need dmesg of dom0 See attached. Goncalo