From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756230AbXJaIPf (ORCPT ); Wed, 31 Oct 2007 04:15:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752964AbXJaIPU (ORCPT ); Wed, 31 Oct 2007 04:15:20 -0400 Received: from pentafluge.infradead.org ([213.146.154.40]:33037 "EHLO pentafluge.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751958AbXJaIPS (ORCPT ); Wed, 31 Oct 2007 04:15:18 -0400 Date: Wed, 31 Oct 2007 08:15:13 +0000 From: Christoph Hellwig To: Andi Kleen Cc: Steven Rostedt , LKML , Linus Torvalds , Andrew Morton , Ingo Molnar , Christoph Hellwig , Daniel Walker Subject: Re: [PATCH] dump_stack on panic Message-ID: <20071031081513.GB3810@infradead.org> References: <1193788979.5623.43.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-SRS-Rewrite: SMTP reverse-path rewritten from by pentafluge.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Oct 31, 2007 at 01:14:04AM +0100, Andi Kleen wrote: > One (mostly psychological, but still serious) problem is that stack > dumps make panics always look like kernel bugs. But there are panics > which are definitely not kernel bugs: like the popular cannot mount > root or machine checks or a couple of others. But that one really shouldn't be a panic anyway. The panic alone is psycologically bad enough for users. I think it would be best to have a simple scanf loop asking for another root device..