From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Bradley Chapman <kakadu_croc@yahoo.com>, <linux-kernel@vger.kernel.org>
Subject: Re: What exactly are the issues with 2.6.0-test10 preempt?
Date: Tue, 25 Nov 2003 08:17:21 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.44.0311250815200.2874-100000@poirot.grange> (raw)
In-Reply-To: <Pine.LNX.4.58.0311241356420.1473@home.osdl.org>
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.
SORRY. Please, inore this report. It IS 100% reproducable - if you load
wrong (compiled without debugging) modules... Maybe you should only accept
bug-reports either without modules or with CONFIG_MODVERSIONS...
Really sorry for taking your time.
Regards
Guennadi
---
Guennadi Liakhovetski
next prev parent reply other threads:[~2003-11-25 7:19 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-24 19:14 What exactly are the issues with 2.6.0-test10 preempt? Bradley Chapman
2003-11-24 21:08 ` Guennadi Liakhovetski
2003-11-24 21:29 ` Bradley Chapman
2003-11-24 21:47 ` Guennadi Liakhovetski
2003-11-24 21:55 ` Bradley Chapman
2003-11-24 21:59 ` Linus Torvalds
2003-11-24 22:26 ` Bradley Chapman
2003-11-24 22:32 ` Linus Torvalds
2003-11-24 22:45 ` Bradley Chapman
2003-11-24 23:00 ` Linus Torvalds
2003-11-24 23:45 ` Linus Torvalds
2003-11-25 7:55 ` Jos Hulzink
2003-11-24 22:41 ` Måns Rullgård
2003-11-24 22:51 ` Mike Fedyk
2003-11-25 1:37 ` Måns Rullgård
2003-11-25 17:22 ` bill davidsen
2003-11-24 22:57 ` Guennadi Liakhovetski
2003-11-25 7:17 ` Guennadi Liakhovetski [this message]
2003-11-25 16:20 ` Linus Torvalds
2003-11-30 9:09 ` Matthias Urlichs
[not found] <20031124224514.56242.qmail@web40908.mail.yahoo.com.suse.lists.linux.kernel>
[not found] ` <Pine.LNX.4.58.0311241452550.15101@home.osdl.org.suse.lists.linux.kernel>
2003-11-24 23:50 ` Andi Kleen
2003-11-25 0:00 ` Mike Fedyk
2003-11-25 0:05 ` Andi Kleen
2003-11-25 0:16 ` Chris Mason
2003-11-25 18:13 kernel
2003-11-25 18:14 root
2003-11-25 18:31 kernel
2003-11-26 9:30 ` Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.44.0311250815200.2874-100000@poirot.grange \
--to=g.liakhovetski@gmx.de \
--cc=kakadu_croc@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).