Comment # 5 on bug 1185113 from Yvan-Marie Grosjean

Recently (in January AND now in April) VirtualBox caused similar problems. Here
is a workout.
THESE ARE THE STEPS TO CLEAN UP ALL THOSE UNWANTED ���������PREEMPTS���������:
In Yast, you first UNINSTALL virtualbox-kmp-preempt AND kernel-preempt AND
kernel-preempt-devel (with this last one, you choose the third alternative:
���������keep kernel-syms with broken capacities���������)
THEN YOU REBOOT
Then, in Yast again, you put a TABU option (with right mouse) on these three: 
virtualbox-kmp-preempt AND kernel-preempt AND kernel-preempt-devel  ; that way
these three won't bother you anymore, never: they're "tabu" now.
THEN YOU REBOOT AGAIN
Then, in Yast again, you UPDATE kernel-syms (with this, you choose the third
alternative option: ���������keep kernel-syms with broken capacities���������)   Don't bother
about those ���������broken capacities���������: they refer to the unwanted preempts.
THEN YOU REBOOT AGAIN
And now your computer works fine, your kernel-default updates will not prompt
you anymore to install those damned ���������preempts���������, and your VirtualBox (or what it
was that pulled in those ���������preempts���������) works like a charm.
The first reboot is needed so that you can put the ���������tabu��������� option on the three
���������preempts���������;
the second reboot is needed so that the three tabus are fixed and so that you
can update your kernel-syms with the right version;
the third reboot is needed to finalize all the steps you've taken and to clean
up your computer for good.
Have a nice day!