I tried the approach from comment #30 and also comment #37 with ami-fa01f193 in us-east. This runs a 2.6.32-312.24 kernel currently in proposed and was running on hw that showed 6M cache in cpuinfo. Both methods did not cause the scheduler bug for me.
I will have a look at the source code and see whether something can be found there. This unfortunately is a bit bulky.
I tried the approach from comment #30 and also comment #37 with ami-fa01f193 in us-east. This runs a 2.6.32-312.24 kernel currently in proposed and was running on hw that showed 6M cache in cpuinfo. Both methods did not cause the scheduler bug for me.
I will have a look at the source code and see whether something can be found there. This unfortunately is a bit bulky.