Apols - Also see plain dmesg attached. This one from updated machine
(4.0.1) still showing the msi issues.
On Thu, Nov 11, 2010 at 07:22:56PM +0000, Mark Adams wrote:
> See attached
>
> 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?
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-users
>
dmesg.txt
Description: Text document
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|