From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: [Xen-users] Re: pci-passthrough in pvops causing offline raid Date: Fri, 12 Nov 2010 17:22:15 -0500 Message-ID: <20101112222215.GC26189@dumpdata.com> References: <20101111102416.GA32457@campbell-lange.net> <20101111165340.GB30006@dumpdata.com> <20101111173850.GA8756@campbell-lange.net> <20101111175809.GA30825@dumpdata.com> <20101111181329.GA9058@campbell-lange.net> <20101111184723.GA10054@campbell-lange.net> <20101111190658.GC15530@dumpdata.com> <20101112171058.GA29875@campbell-lange.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20101112171058.GA29875@campbell-lange.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: Mark Adams Cc: xen-devel@lists.xensource.com, xen-users@lists.xensource.com, JBeulich@novell.com List-Id: xen-devel@lists.xenproject.org On Fri, Nov 12, 2010 at 05:10:58PM +0000, Mark Adams wrote: > On Thu, Nov 11, 2010 at 02:06:58PM -0500, Konrad Rzeszutek Wilk wrote: > > > I've just noticed this at the end of xm dmesg > > > > > > (XEN) msi.c:715: MSI is already in use on device 02:00.0 > > > (XEN) msi.c:715: MSI is already in use on device 02:00.0 > > > (XEN) msi.c:715: MSI is already in use on device 02:00.0 > > > > > > Something else trying to use the device being exported? (the nics are > > > 02:00.0 and 03:00.0) > > > > Hmm, looks like it, but it should not have happend. Can you attach > > the output of 'xm dmesg' and also do the 'xm debug-keys ..' that I > > asked for in the previous e-mail? > > > > Jan, the fixes for the MSI you did, they weren't for 4.0.1 right? Just > > for unstable? > > > > Any further idea's on this? Is it a xen bug if the hidden device is being > accessed in dom0? or is there an overlap somewhere? (not sure how this > would work).. I was going to look in the source today to get an idea but never got to it... You might, as I mentioned in earlier emails, try to setup a serial console or netconsole and log the Linux kernel output when it hangs/fails.