Bug#295657: Interesting article
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jeroen van Disseldorp <jdizzl@xs4all.nl> writes:
>Looks like this could explain the problem:
>http://lwn.net/Articles/150583/
>What do you think?
Well, from a quick read it looks like they have problems when
CONFIG_4KSTACKS are set. As far as I can see, and I may be wrong,
CONFIG_4KSTACKS is not set in the Debian kernel packages we're having
problems with.
\EF
- --
Erik Forsberg http://www.lysator.liu.se/~forsberg/
GPG/PGP Key: 1024D/0BAC89D9
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
iD8DBQFDJyVXrJurFAusidkRAmujAJ9tUhqIkZC6TxCnSaLeh4gPuvP/6gCgt0Gv
7SToArglX3kaf7W0u5kenU8=
=6Aij
-----END PGP SIGNATURE-----
Reply to: