From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Christopher S. Aker" Subject: Re: BUG at domain.c:144 Date: Thu, 7 Apr 2005 18:19:39 -0500 Message-ID: <001b01c53bc8$480bfb90$0201a8c0@hawk> References: <002e01c53a7e$a25cd3d0$0201a8c0@hawk><81f8f6c8aca9491c3f6a5b78da0ade37@cl.cam.ac.uk> <000901c53ba3$1c87ff70$0201a8c0@hawk> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com Cc: Ian Pratt List-Id: xen-devel@lists.xenproject.org Under the -testing tree: (retrieved with bk clone -r bk://xen.bkbits.net/xen-2.0-testing.bk) 1.1774 - boots correctly (creates a 2.6.10-xen0) 1.1784 - refuses to boot (creates a 2.6.11-xen0) Anything past 1.1784 that I've tried also BUGs. It seems like any 2.6.11-dom0 kernel fails on this machine. Incidentally, I am able to run 2.6.11-domUs using the -stable 2.6.10-dom0. All of the changesets between 1.1774 and 1.1784 are the 2.6.11 merge. I haven't bother to try changesets in between those, since they look to me like they all need each other. If anyone wants me to try those changesets, let me know. How can I get more information from the stack trace that Xen puts out to further narrow this down? Thanks, -Chris