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

[Guennadi Liakhovetski <g.liakhovetski@gmx.de>]

On Mon, 24 Nov 2003, Linus Torvalds wrote:

> On Mon, 24 Nov 2003, Guennadi Liakhovetski wrote:
> >
> > 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.
>
> I'd love to have more info - I actually looked at your original report,
> and it's one of those "impossible" things as far as I can tell. The low
> bit of the work "pending" flag should acts as a lock on workqueues, and
> serialize access to one workqueue totally - so having it show up with a
> pending timer is "strange" to say the least. The only two ways to clear
> the "pending" timer is by running the work-queue - either for the timer to
> have gone off (for the delayed case) _or_ the timer not to have evern been
> set in the first place (for the immediate case).
>
> So more information would be wonderful.

I've got that Oops while testing my fix of the tmscsim driver for 2.6. It
was test7. The driver worked, except in that only configuration, where
I've got the reported Oops. I just tried a working configuration (with
preempt enabled) and enabled DEBUG_PAGEALLOC - it still worked... So,
unless it REALLY was an impossible bug, that somehow impossibly
disappeared again (the only thing I can say - I couldn't have written that
Oops by hand just out of my head...:-)) - it should really be a
combination of all those parameters. I am currently recompiling test10
with that configuration, will try test7 again, if this one doesn't
reproduce the bug, will report results tomorrow. If I get the Oops again -
will attach the complete .config.

Thanks
Guennadi
---
Guennadi Liakhovetski