What drivers. There is no reason for the problem you are seeing being a
CPU specific bug - its most likely a driver flaw. What drivers do you
use and does 2.0.x SMP work for your box
> Personally I would like to get rid of about half these tests and just go
> with the fractionally slower code with no configuration tests. I don't
> mind having arch/i386/kernel/smp.c linked in or not depending on __SMP__,
> but I don't like seeing __SMP__ in the middle of low-level include files.
> Besides the code cleanup benefit, it would eliminate the distinction
> between SMP and non-SMP modules.
The difference on intel for non SMP with things like FPU heavy tasks can
be over 100% gain. Its worth having SMP seperate.
Alan