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.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home