From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Slow boot with 2.6.37-rc4 Date: Fri, 3 Dec 2010 18:11:51 -0500 Message-ID: <20101203231151.GA12689@dumpdata.com> References: <20101201151737.GA2066@dumpdata.com> <20101203200626.GA4161@dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: M A Young Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Fri, Dec 03, 2010 at 10:20:55PM +0000, M A Young wrote: > On Fri, 3 Dec 2010, Konrad Rzeszutek Wilk wrote: > > >Can you pass in pci=nomsi on the Linux kernel line just to see if it is > >indeed MSI (or vector) related. > > I still see the delay with pci=nomsi. The dmseg output from that > boot is attached. It still looks to be using MSIs.. Maybe the command line parameter is wrong? > > >And also under the Xen hypervisor serial line print out the PCI MSI irq and IRQ vectors > >values? Don't remember the debug keys - but the point is to see if for your AHCI controller: > >0000:00:1f.2 and 0000:00:1f.1, there is an MSI vector allocated for it. > > I tried various xm debug-keys (M,Q,i and z) on a boot without > pci=nomsi. The output of xm dmesg afterwards is attached. Try it also on Xen line, thought I am not sure what the arguments for disabling MSI in the hypervisor are.