Found a bug? Report here
Cheers. I only have one machine currently using a dedicated L2, so will keep an eye on it and flush the cache periodically until the bug is zapped.
If I understand correctly, this problem appears only when using L2 as read cache, it is not a issue witch write only L2?
Bug doesn't seem to affect me if I have writes enabled too on the L2 cache, maybe the reason the bug doesn't affect L1 cache?