From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rik van Riel Subject: Re: BUG: x86-64 VT crash backtrace Date: Tue, 25 Jul 2006 13:09:05 -0400 Message-ID: <44C65031.4090203@redhat.com> References: <44C6408E.4070700@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: 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: Keir Fraser Cc: xen-devel@lists.xensource.com, jun.nakajima@intel.com List-Id: xen-devel@lists.xenproject.org Keir Fraser wrote: > > On 25 Jul 2006, at 17:02, Rik van Riel wrote: > >> Hi Jun, >> >> here is the x86-64 VT crash backtrace, as promised. I can trigger it >> within minutes by simply starting up a 64 bit VT domain on a 64 bit >> system. > > The hideously long (but apparently valid) call sequence has overflowed > the 4kB Xen stack. Given that stacks are only per-cpu on x86 Xen, I > should probably just make them bigger (perhaps 8kB on debug builds, 16kB > on non-debug builds). 64-bit non-debug builds already have (almost) 8kB > stacks, so shouldn't see this crash. These crashes are on a 64 bit system. So yes, even with 8kB stacks it crashes. -- "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian W. Kernighan