From: Vince Weaver <[EMAIL PROTECTED]>
Date: Fri, 26 Jan 2007 14:44:44 -0500 (EST)
>
> > Vince, I think I figured out what the bug is, can you test the
> > following patch? If we set %g5 with the fault address here, we have
> > to set %g4 too. This allows to correctly handle a DTLB-PROT trap fo
Vince, I think I figured out what the bug is, can you test the
following patch? If we set %g5 with the fault address here, we have
to set %g4 too. This allows to correctly handle a DTLB-PROT trap for
a window spill during trap entry for another top-level fault. The
non-Niagara DTLB-PROT code
Vince, I think I figured out what the bug is, can you test the
following patch? If we set %g5 with the fault address here, we have
to set %g4 too. This allows to correctly handle a DTLB-PROT trap for
a window spill during trap entry for another top-level fault. The
non-Niagara DTLB-PROT code do
From: Vince Weaver <[EMAIL PROTECTED]>
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
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
From: David Miller <[EMAIL PROTECTED]>
Date: Thu, 25 Jan 2007 15:26:21 -0800 (PST)
> 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 :)
-
To unsubscribe from this list: send the line "unsubscri
From: Vince Weaver <[EMAIL PROTECTED]>
Date: Wed, 24 Jan 2007 22:00:12 -0500 (EST)
> I've reproduced it, here are the results (the bug is still at line 413,
> my debug code pushed it down a bit):
>
> [ 263.773194] VMW: fault_code=4 address=ff0cc000 regs->tpc=70131660
>
I have a theory about w
From: Vince Weaver <[EMAIL PROTECTED]>
Date: Wed, 24 Jan 2007 22:00:12 -0500 (EST)
> I've reproduced it, here are the results (the bug is still at line 413,
> my debug code pushed it down a bit):
>
>
> [ 263.773194] VMW: fault_code=4 address=ff0cc000 regs->tpc=70131660
Thanks for the info Vin
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.
I am running Ubuntu Feisty. (probably a bit too new, I was having
problems getting
From: Vince Weaver <[EMAIL PROTECTED]>
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 ver
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:
[ 1020.332688] kernel BUG at arch/sparc64/mm/fault.c:413!
[ 1020.332710] \|/ \|/
[ 1020.332716
11 matches
Mail list logo