Re: What exactly are the issues with 2.6.0-test10 preempt?

[Guennadi Liakhovetski]

On Mon, 24 Nov 2003, Bradley Chapman wrote:

> I saw in Linus' 2.6.0-test10 announcement that preempt is suffering from some
> problems and should not be used. However, I am currently running 2.6.0-test10
> with CONFIG_PREEMPT=y and nothing has appeared yet. To see if the problem appeared
> under stress, I started an A/V trailer playback with mplayer and then ran the
> find command on both my home directory and the 2.6.0-test10 kernel source directory,
> with the expected result - mplayer did not skip, neither find invocation broke,
> and there were no nasty errors in dmesg.
>
> So what exactly is the problem?

Well, FWIW, I'm getting 100% reproducible Oopses on __boot__ by enabling
preemption AND (almost) all kernel-hacking CONFIG_DEBUG_* options - see my
post of 21.11.2003 with subject "[OOPS] 2.6.0-test7 + preempt + hacking".
If required, could try to narrow it down to 1 CONFIG option. However, the
Oops itself happens somewhere in NFS code (see backtrace in above email
for details).

Guennadi
---
Guennadi Liakhovetski




-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/