Tomasz Chmielewski schrieb:
Tomasz Chmielewski schrieb:
Sorry, both machines run Debian Lenny and 2.6.26 kernel.
The only difference is that machine which crashes (with MTU=100) or
locks up (with MTU=1500) runs a "2.6.26-1-686" kernel and the one
which doesn't lock up runs "2.6.26-1-486" kernel (both are Debian's
kernels).
Some more tries and I got this one. Serial console died, but SSH is
still working.
Note the "S" tainted flag.
According to Documentation/oops-tracing.txt, it means:
3: 'S' if the oops occurred on an SMP kernel running on hardware that
hasn't been certified as safe to run multiprocessor.
Currently this occurs only on various Athlons that are not
SMP capable.
And this is a difference between "2.6.26-1-686" and "2.6.26-1-486" kernels.
# grep -i smp /boot/config-2.6.26-1-686
CONFIG_X86_SMP=y
CONFIG_X86_32_SMP=y
CONFIG_SMP=y
# grep -i smp /boot/config-2.6.26-1-486
CONFIG_BROKEN_ON_SMP=y
# CONFIG_SMP is not set
BTW, it was the machine with /boot/config-2.6.26-1-486 kernel (non-SMP)
which got slow for me today.
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
