> Eh? r22 is 0020fd0e... although it's easier to spot by looking at IOR > > > IIR: 0ed5d240 ISR: 00000847 IOR: 0020fd0e Obviously, I can't count... > Although, I don't think we're supposed to ever be taking a P. Id trap on > a userspace process as the kernel... Ok, should P and/or D be on? Assuming the protection id isn't wrong, then the WD bit must be on. A problem with the WD bit might explain Helge's comment. As a start, dumping CR 8, 9, 12 and 13 might help debug the problem. There might be a problem restoring access IDs after a cache purge or TLB insertion. Dave -- J. David Anglin dave.anglin@xxxxxxxxxxxxxx National Research Council of Canada (613) 990-0752 (FAX: 952-6602) -- To unsubscribe from this list: send the line "unsubscribe linux-parisc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
