From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Tvrtko A. =?iso-8859-2?q?Ur=B9ulin?=" Subject: Re: Kernel panic while compiling kernel Date: Wed, 11 Feb 2004 13:20:32 +0100 Sender: xen-devel-admin@lists.sourceforge.net Message-ID: <200402111320.32071.tvrtko@croadria.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Content-Disposition: inline Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: xen-devel@lists.sourceforge.net Cc: Keir Fraser List-Id: xen-devel@lists.xenproject.org On Wednesday 11 February 2004 12:22, Keir Fraser wrote: > Hmmm... well we know there are bugs in Xen v1.3, but v1.2 has been > stable for a while now (it passes our regression tests). > > If you can, turn on debugging in Xen (edit arch/i386/Rules.mk and > remove -DNDEBUG from CFLAGS), re-compile, and send us the full serial > output for a Xen/Xenolinxu session which includes this crash. Something is really bad, after sending you the report of working tg3 witd Xen DEBUG I planned to put some load on the DOM0 to see if I can reproduce the problem from this thread. While I was trying to ssh to DOM0 I got the same kernel panic. Fortunately I had an minicom session active :) The complete log is the same as one I have sent you in tg3 thread. Just append this: DOM0: Kernel panic: Failed mmu update: c015bf80, 4 Domain 0 killed: rebooting machine! ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn