From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030234AbWHQUHL (ORCPT ); Thu, 17 Aug 2006 16:07:11 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030240AbWHQUHK (ORCPT ); Thu, 17 Aug 2006 16:07:10 -0400 Received: from liaag2aa.mx.compuserve.com ([149.174.40.154]:25510 "EHLO liaag2aa.mx.compuserve.com") by vger.kernel.org with ESMTP id S1030234AbWHQUHJ (ORCPT ); Thu, 17 Aug 2006 16:07:09 -0400 Date: Thu, 17 Aug 2006 16:03:23 -0400 From: Chuck Ebbert <76306.1226@compuserve.com> Subject: Re: 2.6.18-rc3-g3b445eea BUG: warning at /usr/src/linux-git/kernel/cpu.c:51 To: Jan Beulich Cc: linux-kernel , Andi Kleen , Andrew Morton , Michal Piotrowski , Linus Torvalds , Dave Jones Message-ID: <200608171605_MC3-1-C870-818F@compuserve.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org In-Reply-To: <44E1D8CD.76E4.0078.0@novell.com> On Tue, 15 Aug 2006 14:23:09 +0200, Jan Beulich wrote: > Again, if "unwinder stuck" messages appear, I'll need a raw > stack dump to accompany the stack trace. So people who want to help debug the stuck unwinder should be booting with "kstack=2048" on i386 in order to get the full stack dump. -- Chuck