From: David Miller <davem@davemloft.net>
To: sparclinux@vger.kernel.org
Subject: Re: kernel BUG at arch/sparc64/mm/fault.c:413!
Date: Wed, 24 Jan 2007 05:25:03 +0000 [thread overview]
Message-ID: <20070123.212503.55506485.davem@davemloft.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0701181328230.8124@pianoman.cluster.toy>
From: Vince Weaver <vince@deater.net>
Date: Thu, 18 Jan 2007 13:33:15 -0500 (EST)
>
> I am running Linux 2.6.20-rc5 on an UltraSparc T1 (Niagara) with 24
> threads.
>
> When trying to compile gcc-4.2-20070117 gcc snapshot from scratch, the
> following BUG() happens:
What distribution and version are you running? I tried to dump
the code at address 0x1a368 of the /bin/sh binary running on
Ubuntu Dapper and it didn't show a code location which could
trigger this code path.
> The relevant code is:
>
> 409 /* If we took a ITLB miss on a non-executable page, catch
> 410 * that here.
> 411 */
> 412 if ((fault_code & FAULT_CODE_ITLB) && !(vma->vm_flags & VM_EXEC)) {
> 413 BUG_ON(address != regs->tpc);
> 414 BUG_ON(regs->tstate & TSTATE_PRIV);
> 415 goto bad_area;
> 416 }
>
> What's the next step in tracking down what's going on?
Try to print out the "fault_code", "address", and regs->tpc value
when this triggers.
I think the thread struct is being corrupted by some parallel access
and this corrupts the fault state, in particular "fault_code" is
garbage.
But I can only confirm that theory with the information I've
requested above.
next prev parent reply other threads:[~2007-01-24 5:25 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 [this message]
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
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=20070123.212503.55506485.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.