just a word to say that since the bug came up, i tested it with all the
hardware i have around (especially an old Compaq Deskpro with Pentium
OverDrive PODP5V83 which was _not_ concerned by the bug)
After upgrading to kernel 2.0.32, i noticed that the workaround was set up
even though it wasn't necessary since the chip is insensible to the bug
Of course this kernel is still working ok on my machine but is there any
way to incorporate a check in the further f00f path (new) not to include
workaround for specific pentium model
BTW, I am amazed by such a nice work and the great reactivity of the linux
community to solve any kind of problem under this brilliant OS
-- Cyril Chaboisseau mailto: Cyril.Chaboisseau@obs.coe.int