On Mon, Nov 15, 2010 at 12:44:13PM -0500, Konrad Rzeszutek Wilk wrote:
> On Mon, Nov 15, 2010 at 05:23:09PM +0000, Mark Adams wrote:
> > On Mon, Nov 15, 2010 at 12:15:44PM -0500, Konrad Rzeszutek Wilk wrote:
> > > On Sun, Nov 14, 2010 at 05:15:02PM +0000, Mark Adams wrote:
> > > >
> > > > On 12 Nov 2010, at 22:22, Konrad Rzeszutek Wilk
> > > > <konrad.wilk@xxxxxxxxxx> wrote:
> > > >
> > > > > 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
> > >
> > > Looking briefly at the code it means that somebody enabled the MSI
> > > already on the device and did not disable them. But I wonder how
> > > you got those in the first place. Did you use xen-pciback.hide (for PVOPS
> > > kernels)
> > > or pciback.hide (for older kernels) to "hide" the devices away from the
> > > Linux Dom0 kernel?
> >
> > using xen-pciback.hide as its a pvops kernel (debian squeeze
> > 2.6.32-5-27)
>
> Ok. Then it might be worth looking in when this happens. I think
> there is an argument on the Xen hyperisor line to include the time-stamp, but
> I don't remember it :-(
>
http://wiki.xen.org/xenwiki/XenHypervisorBootOptions
So I think it's "console_timestamps"
-- Pasi
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home