From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: dmidecode doesn't work under xen 4.1.1 on certain hardware Date: Mon, 10 Oct 2011 12:18:41 -0400 Message-ID: <20111010161841.GE28646@phenom.oracle.com> References: <20110926193732.GA10007@phenom.oracle.com> <4E82E429.2080600@overnetdata.com> <20110928132815.GE10270@phenom.oracle.com> <4E83462B.9080002@overnetdata.com> <4E835324.30902@citrix.com> <4E8AF9BA.3000906@overnetdata.com> <20111005151601.GA5223@phenom.oracle.com> <4E8DA4D1.2040904@overnetdata.com> <20111006160717.GA31310@phenom.oracle.com> <4E930E71.7000306@overnetdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <4E930E71.7000306@overnetdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Anthony Wright Cc: "xen-devel@lists.xensource.com" , David Vrabel List-Id: xen-devel@lists.xenproject.org On Mon, Oct 10, 2011 at 04:25:37PM +0100, Anthony Wright wrote: > On 06/10/2011 17:07, Konrad Rzeszutek Wilk wrote: > >>> If you feel adventours you could use the oss.oracle.com/git/kwilk/xen.git > >>> tree. Mainly the #linux-next or #testing branch. They both have David's new > >>> e820 code. > >>> > >>> The way to get it is: > >>> > >>> git clone oss.oracle.com/git/kwilk/xen.git > >>> cd xen > >>> git checkout origin/linux-next > >>> make -j90 > >> Sorry it panicked :-( > >> I've attached two photos of the two flavours of panic & a copy of the > >> config. > > No serial console? Did it panic when you booted as baremetal? > Sorry - no serial console - I hadn't really intended to become part > kernel hacker!! We're looking for leads to see if we can set it up, but > I'm going to have to look through the attic into some old dusty boxes... I just realized that you can run netconsole - so no need for serial console. But.. I am really baffled by this. None of the patches in #linux-next do anything there. Please do try to run v3.1-rc8 (or v3.1-rc9) and see if that fails? If it does then we can try to play a bit of bisection game and figure out what caused this mayhem. Is your motherboard easily bought online?