Bug#464962: 18.104.22.168 doesn't quite fix it -- hoping not to have to build my own
Based on the changes reported when the new package was released on
April 6th or 7th, I upgraded on April 7th, but no joy.
Same symptoms as previous version. My CPU is a Via C3, i.e. does not
support the long noop as shown by output of the long noop test program
To get 2.6.24 rather than stay with 2.6.22, I had to downgrade to the
-486 version of 2.6.24. How much impact is this likely to have? (I've
noted nothing egregious in the past hour since switching to 2.6.24-1-486.)
Will there be a respin of the -686 with CONFIG_X86_GENERIC set, per
Tim Phipps note?
I'd rather not go back to spending time rolling my own custom kernels.
I'm sure it has gotten better since 1994 and BSD kernels, but it's
still time and effort consuming.
lrwxrwxrwx 1 root root 25 2008-04-07 10:05 /vmlinuz.old -> boot/vmlinuz-2.6.24-1-686
ii linux-image-2.6.22-3-686 2.6.22-6.lenny1 Linux 2.6.22 image on PPro/Celeron/PII/PIII/
ii linux-image-2.6.24-1-486 2.6.24-5 Linux 2.6.24 image on x86
ii linux-image-2.6.24-1-686 2.6.24-5 Linux 2.6.24 image on PPro/Celeron/PII/PIII/