From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: [Xen-devel] linux-next: Tree for Jun 26 (xen/x86) Date: Wed, 26 Jun 2013 17:25:09 -0400 Message-ID: <20130626212509.GB2810@phenom.dumpdata.com> References: <20130626180653.57aee1721b4b5096ddc8f82d@canb.auug.org.au> <51CB379A.7010606@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <51CB379A.7010606@infradead.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: virtualization-bounces@lists.linux-foundation.org Errors-To: virtualization-bounces@lists.linux-foundation.org To: Randy Dunlap Cc: Stephen Rothwell , Jeremy Fitzhardinge , xen-devel@lists.xensource.com, linux-kernel@vger.kernel.org, virtualization@lists.linux-foundation.org, linux-next@vger.kernel.org List-Id: linux-next.vger.kernel.org On Wed, Jun 26, 2013 at 11:48:58AM -0700, Randy Dunlap wrote: > On 06/26/13 01:06, Stephen Rothwell wrote: > > Hi all, > > > > Changes since 20130625: > > > > CONFIG_SMP is not set > CONFIG_X86_UP_APIC is not set That is new. Any thoughts of which patch might be the culprit? What are the other config options? What XEN options are set? > > on i386: > > drivers/built-in.o: In function `xen_callback_vector': > (.text+0x1dc3cb): undefined reference to `first_system_vector' > drivers/built-in.o: In function `xen_callback_vector': > (.text+0x1dc3f5): undefined reference to `first_system_vector' > > > -- > ~Randy > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel >