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
User-Agent: KMail/1.7
References: <200411271311.25997.nick@linicks.net> <41A8B2EF.5090608@osdl.org>
In-Reply-To: <41A8B2EF.5090608@osdl.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200411271721.21847.nick@linicks.net>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1012
Lines: 37

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..."
-
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/