[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#375845: marked as done (linux-source-2.6.17: Pre-emptive features not enabled in Debian kernel builds)



Your message dated Sun, 29 Jul 2007 21:06:38 +0200
with message-id <20070729190638.GI4504@stro.at>
and subject line linux-source-2.6.17: Pre-emptive features not enabled in Debian kernel builds
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: linux-source-2.6.17
Severity: wishlist


Per a recent thread on the Debian-KDE mailing list questioning why the
system seems to stall under heavy processing, it was pointed out that
the Debian kernel builds do not enable the CONFIG_PREEMPT options.  Per
my config file in /boot for 2.6.16-1-686, the following options are 
configured:

CONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT is not set

On my other machine which has a 2.6.17 K7 kernel there are a couple more
options.

Would it be possible to create desktop kernel image packages with the
CONFIG-PREEMPT options enabled?

For reference, here is the thread:

http://lists.debian.org/debian-kde/2006/06/msg00229.html

- Nate >>

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-1-686
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)


--- End Message ---
--- Begin Message ---
in the past preemptive managed to trigger a *lot* of bugs
and was thus highly unstable, nowadays as most distros switch
to it we might reconsider at a later base.

this is a duplicate bug report, there are other on this topic
thus closing in this linux-2.6 bug cleanup round.

regards

-- 
maks

--- End Message ---

Reply to: