ANTS Report

For what ever it's worth, this failure was the 'invalidate_ktlb' kernel variety, not the user space 'invalidate_tlb_x' type of tlbflush.

Just an idea (maybe a bad one)...

I'm wondering if this shield_all test script should be changed to not fail if it sees just one invalidate_ktlb occur during a 10 second shield trace on a given cpu.... maybe this would be only for 32bit systems with HIGHMEM.

Feel free to ignore this suggestion.

It's just that we'll (I'll) have to look at manufacturing systems everytime this test fails, and say whether or not this is a user or kernel failure and whether to ignore it.