Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751122AbVJFP75 (ORCPT ); Thu, 6 Oct 2005 11:59:57 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751123AbVJFP75 (ORCPT ); Thu, 6 Oct 2005 11:59:57 -0400 Received: from xenotime.net ([66.160.160.81]:42129 "HELO xenotime.net") by vger.kernel.org with SMTP id S1751122AbVJFP75 (ORCPT ); Thu, 6 Oct 2005 11:59:57 -0400 Date: Thu, 6 Oct 2005 08:59:52 -0700 (PDT) From: "Randy.Dunlap" X-X-Sender: rddunlap@shark.he.net To: Kalin KOZHUHAROV cc: linux-kernel@vger.kernel.org Subject: Re: [PATCH] Documentation: ksymoops should no longer be used to decode Oops messages In-Reply-To: Message-ID: References: <200510052239.43492.jesper.juhl@gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2064 Lines: 56 On Fri, 7 Oct 2005, Kalin KOZHUHAROV wrote: > Jesper Juhl wrote: > > Document the fact that ksymoops should no longer be used to decode Oops > > messages. > > > > > > Signed-off-by: Jesper Juhl > > --- > > > > Documentation/Changes | 7 +++---- > > 1 files changed, 3 insertions(+), 4 deletions(-) > > > > --- linux-2.6.14-rc3-git5-orig/Documentation/Changes 2005-10-03 21:54:50.000000000 +0200 > > +++ linux-2.6.14-rc3-git5/Documentation/Changes 2005-10-05 22:35:44.000000000 +0200 > > @@ -31,7 +31,7 @@ > > Eine deutsche Version dieser Datei finden Sie unter > > . > > > > -Last updated: October 29th, 2002 > > +Last updated: October 05th, 2005 > > > > Chris Ricker (kaboom@gatech.edu or chris.ricker@genetics.utah.edu). > > > > @@ -139,9 +139,8 @@ > > Ksymoops > > -------- > > > > -If the unthinkable happens and your kernel oopses, you'll need a 2.4 > > -version of ksymoops to decode the report; see REPORTING-BUGS in the > > -root of the Linux source for more information. > > +With a 2.4 kernel you need ksymoops to decode a kernel Oops message. With > > +2.6 kernels ksymoops is no longer needed and should not be used. > > > > Module-Init-Tools > > ----------------- > > OK, but what should I use then with 2.6?? > And since when is ksymoops not usable with it? > I have reported quite a few times here, alaways with 2.6.x and nobody said anything about it... You should just enable CONFIG_KALLSYMS so that the kernel can report (decode) the symbols with the oops message. Yes, ksymoops will still work, but it should only be used if the kernel was not configured with CONFIG_KALLSYMS, and some people say that the kernel oops + symbols are better than the ksymoops output. I haven't compared them so can't say. -- ~Randy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/