Re: Pointer to info on decoding oops messages

["Randy.Dunlap" <rddunlap@osdl.org>]

On Thu, 27 Nov 2003 09:36:16 +0800 (WST) Ian Kent <raven@themaw.net> wrote:

| On Wed, 26 Nov 2003, Randy.Dunlap wrote:
| 
| > On Wed, 26 Nov 2003 21:41:18 +0800 (WST) Ian Kent <raven@themaw.net> wrote:
| >
| > |
| > | The subject says it all.
| > |
| > | Any suggestions please.
| >
| > Unless the instruction pointer register is scrogged, you get
| > some registers, some stack data, the code bytes at the next
| > instruction pointer, and some backtrace symbols.
| > These are mostly self-explanatory.
| 
| Umm .. yes but ....
| 
| >
| > However, I'm guessing that you want help with the _cause_ of
| > an oops, not just with decoding the oops messages.
| 
| Well yes.
| 
| What I really need is a way to determine if my poorly coded changes are
| causing the problem or if I am dealing with a bug in other code.

Have you posted any of your oopsen?  You can try that.
Sometimes that will get you some good feedback, sometimes not....

| >
| > Anyway, here's where I pointed out some basic info recently:
| > http://marc.theaimsgroup.com/?l=linux-kernel&m=106433590230743&w=2
| > and
| > http://marc.theaimsgroup.com/?l=linux-kernel&m=106434159306658&w=2
| 
| Thanks. Will look it up.

--
~Randy