From: Brett <generica@email.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.5 kernel hangs system
Date: Wed, 23 Apr 2003 12:17:40 +1000 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44.0304231215340.798-100000@bad-sports.com> (raw)
In-Reply-To: <20030423023128.GJ1249@Master.Bellsouth.net>
On Tue, 22 Apr 2003, Murray J. Root wrote:
> 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 :)
>
>
I agree with > >
I'd say he's getting the same thing as me
<http://marc.theaimsgroup.com/?l=linux-kernel&m=105099066618652&w=2>
the 'hex codes' are the last line of grub loading the kernel
so where to from here ??
/ Brett
prev parent reply other threads:[~2003-04-23 2:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-22 20:19 2.5 kernel hangs system Dave Mehler
2003-04-22 20:55 ` Michael Buesch
2003-04-22 21:00 ` Richard B. Johnson
2003-04-22 23:11 ` Felipe Alfaro Solana
2003-04-23 1:29 ` Murray J. Root
2003-04-23 1:55 ` Randy.Dunlap
2003-04-23 2:31 ` Murray J. Root
2003-04-23 2:17 ` Brett [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.44.0304231215340.798-100000@bad-sports.com \
--to=generica@email.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).