All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: sparclinux@vger.kernel.org
Subject: Re: kernel BUG at arch/sparc64/mm/fault.c:413!
Date: Fri, 26 Jan 2007 08:39:53 +0000	[thread overview]
Message-ID: <20070126.003953.08324074.davem@davemloft.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0701181328230.8124@pianoman.cluster.toy>

From: Vince Weaver <vince@deater.net>
Date: Thu, 25 Jan 2007 22:21:00 -0500 (EST)

> 
> >> Note, this patch is pretty straight forward, but I've only compile
> >> tested it.  I'm about to test boot it myself right now.
> >
> > FWIW, it works fine for me :)
> 
> Unfortunately it didn't seem to fix things.  It ran a lot longer this 
> time, but eventually stopped with
> 
> [  597.730241] VMW: fault_code=4 addressÿ564000 regs->tpcp179660
> [  597.730266] kernel BUG at arch/sparc64/mm/fault.c:417!

That eliminates one theory.

I'll think about this some more, but could you do me a favor
and test something?  Revert my patch, and change your debugging
printk to print out not just fault_code and address, but also
get_thread_fault_code() and current_thread_info()->fault_address.

I want to see if they are changing after being read for some
reason.

Thanks!

  parent reply	other threads:[~2007-01-26  8:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-18 18:33 kernel BUG at arch/sparc64/mm/fault.c:413! Vince Weaver
2007-01-24  5:25 ` David Miller
2007-01-25  3:00 ` Vince Weaver
2007-01-25 22:02 ` David Miller
2007-01-25 23:26 ` David Miller
2007-01-25 23:48 ` David Miller
2007-01-26  3:21 ` Vince Weaver
2007-01-26  8:39 ` David Miller [this message]
2007-01-26 11:01 ` David Miller
2007-01-26 19:44 ` Vince Weaver
2007-01-26 21:05 ` David Miller

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=20070126.003953.08324074.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=sparclinux@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.