From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263932AbTDWCTd (ORCPT ); Tue, 22 Apr 2003 22:19:33 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263935AbTDWCTd (ORCPT ); Tue, 22 Apr 2003 22:19:33 -0400 Received: from stroke.of.genius.brain.org ([206.80.113.1]:36032 "EHLO stroke.of.genius.brain.org") by vger.kernel.org with ESMTP id S263932AbTDWCTc (ORCPT ); Tue, 22 Apr 2003 22:19:32 -0400 Date: Tue, 22 Apr 2003 22:31:28 -0400 From: "Murray J. Root" To: LKML Subject: Re: 2.5 kernel hangs system Message-ID: <20030423023128.GJ1249@Master.Bellsouth.net> Mail-Followup-To: LKML References: <000501c3090c$71683c60$0200a8c0@satellite> <1051053106.710.4.camel@teapot.felipe-alfaro.com> <20030423012903.GI1249@Master.Bellsouth.net> <1491.4.64.197.106.1051062911.squirrel@fire.osdl.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1491.4.64.197.106.1051062911.squirrel@fire.osdl.org> User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Apr 22, 2003 at 06:55:11PM -0700, Randy.Dunlap wrote: > > On Wed, Apr 23, 2003 at 01:11:46AM +0200, Felipe Alfaro Solana wrote: > >> On Tue, 2003-04-22 at 23:00, Richard B. Johnson wrote: > >> > First, I don't understand how as you say, "suggestions are > >> > desperately needed" on a developmental kernel. These things are > >> > not known to work on all configurations and some information like > >> > "It gives me hex codes..." is worthless. Please write down > >> > these "hex-codes" and, after booting a version the works, run them > >> > through ksymoops. If you don't know what that is: > >> > >> ksymoops? I thought 2.5 kernels didn't need ksymoops anymore and that > >> function names were automatically "guessed" in call stack traces. > >> > > > > IFF you use "include symbols" when building you shouldn't need ksymoops. > > IMO, if you're using 2.5.x you really should include the symbols - chances > > are you'll need em. > > Maybe we are reading this differently, but it sounded to me like the > original system hang never reached the kernel | system log and that > some hex codes were the only clues. In that case, pushing them thru > ksymoops does still make some sense, doesn't it? > How else would you determine where the hang occurred? > I read it that he was getting an oops with just hex values cause he didn't have the symbols included (note the reference to "it just gives hex codes"). I could be wrong, since I'm only looking at the quote of a quote of someone's interpretation. :) With symbols included an oops DOES print the actual call trace in readable form. (I've seen enough oops to be certain of that :) -- Murray J. Root