From: David Miller <davem@xxxxxxxxxxxxx>
Date: Tue, 16 Sep 2014 20:16:51 -0400 (EDT)
> Anyways, we have to figure out why 0x8 is set in the PTE that we try
> to load into ITLB. I haven't found any smoking guns yet.
Looking more closely, the PTE 0x2900000dcc800eeb doesn't even have
the valid bit set.
Non-valid PTEs should not even get into the TSB, and non-valid PTEs
found via page table lookup should vector us to the full fault path.
There used to be a bug where we'd put non-valid TTEs into the TSB
but that was fixed by commit:
commit 18f38132528c3e603c66ea464727b29e9bbcb91b
Author: David S. Miller <davem@xxxxxxxxxxxxx>
Date: Mon Aug 4 16:34:01 2014 -0700
sparc64: Do not insert non-valid PTEs into the TSB hash table.
Do you know if the kernels that triggered those ITLB BADRA errors had
that fix or not?
--
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
