From: Nick Warne <nick@linicks.net>
To: linux-kernel@vger.kernel.org
Subject: Re: kswapd0 oops -> debug information
Date: Sat, 27 Nov 2004 17:21:21 +0000 [thread overview]
Message-ID: <200411271721.21847.nick@linicks.net> (raw)
In-Reply-To: <41A8B2EF.5090608@osdl.org>
On Saturday 27 November 2004 17:01, Randy.Dunlap wrote:
> kernel version?
Heh. My great debug attempt, eh?
kernel 2.6.9
> .config file?
> full oops message, with stack backtrace?
> The stack backtrace could tell us who a bad caller is.
> It can just be a caller's problem, not a bug in (this)
> one isolated function.
http://linicks.net/kdebug/
> Did you read/check linux/REPORTING-BUGS ?
Yes, but wanted to try and learn myself on what was going on, rather than push
the onus onto other people.
The book I have re the make /dir/file.s states that it will produce assembler
with _line_ numbers to corresponding C code. That is where I got lost, as it
doesn't.
Thanks,
Nick.
--
"When you're chewing on life's gristle,
Don't grumble, Give a whistle..."
next prev parent reply other threads:[~2004-11-27 17:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-27 13:11 kswapd0 oops -> debug information Nick Warne
2004-11-27 17:01 ` Randy.Dunlap
2004-11-27 17:21 ` Nick Warne [this message]
2005-01-02 7:41 ` Herbert Poetzl
2005-01-02 11:01 ` Nick Warne
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=200411271721.21847.nick@linicks.net \
--to=nick@linicks.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.