From: Mikulas Patocka <mpatocka@xxxxxxxxxx> Date: Wed, 21 Oct 2009 14:24:59 -0400 (EDT) > The fault_code variable that triggered is in l2, it's 0xfe, the fault > address is in l3. Do you have any idea how this could (or couldn't) > happen? The fault_code on sparc64 is a bitmask which should contain only the following bit values (some of which are exclusive): #define FAULT_CODE_WRITE 0x01 /* Write access, implies D-TLB */ #define FAULT_CODE_DTLB 0x02 /* Miss happened in D-TLB */ #define FAULT_CODE_ITLB 0x04 /* Miss happened in I-TLB */ #define FAULT_CODE_WINFIXUP 0x08 /* Miss happened during spill/fill */ #define FAULT_CODE_BLKCOMMIT 0x10 /* Use blk-commit ASI in copy_page */ 0xfe is an illegal value. I suspect that once you hit this IDE bug, the IDE controller is spamming garbage via DMA all over memory corrupting things. -- 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
