>> An MCA brings down our system immediately, so console output won't help >> much. Our MCA analyzer is complaining about accessing a memory hole >> consistently at the same address. I am going to try adding some trace >> code. > > Hm. On PowerPC we detect machine checks caused by stray I/O cycles, and > we recover from them. Can't we do that kind of thing on IA64 too? This (presumably) isn't a stray cycle. The cpu has dereferenced a bogus pointer to an unpopulated memory address. How can we recover from that? It would be nicer if Linux reported this in a more user-friendly way (with the invalid address and a stack trace) ... but the MCA handler is a pretty software hostile environment in which to do this. -Tony -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
