On Mon, May 16, 2005 at 04:19:00PM -0500, Troy Benjegerdes wrote: > Then why is CONFIG_PREEMPT disabled in 2.6.11 ? The real problem is > preempt is enabled.
Because it doesn't provide much benefits while letting broken code explode. That doesn't mean you should file such reports against against the kernel package unless that broken code is actually part of the mainline kernel or the debian patches. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
