From: Linus Torvalds <torvalds@osdl.org>
To: Bradley Chapman <kakadu_croc@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: What exactly are the issues with 2.6.0-test10 preempt?
Date: Mon, 24 Nov 2003 14:32:31 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.58.0311241429330.15101@home.osdl.org> (raw)
In-Reply-To: <20031124222652.16351.qmail@web40910.mail.yahoo.com>
On Mon, 24 Nov 2003, Bradley Chapman wrote:
>
> What sort of information would you like me to provide, sir? The bug you're
> discussing here isn't affecting me; CONFIG_PREEMPT has been solid on 2.6.0-test10.
> This is on a Gateway 600S laptop with a P4-M 2Ghz processor and an i845 Brookdale
> chipset.
Basically, there's something strange going on, which _seems_ to be memory
corruption, and seems to correlate reasonable well (but not 100%) with
CONFIG_PREEMPT.
It's actually unlikely to be preemption itself that is broken: it's much
more likely that some driver or other subsystem is broken, and preempt is
just better at triggering it by making some race conditions much easier to
see due to bigger windows for them to happen.
The problem is finding enough of a pattern to the reports to make sense of
what seems to be the common thread. A lot of people use preemption without
any trouble.
Linus
next prev parent reply other threads:[~2003-11-24 22:32 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 [this message]
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
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.58.0311241429330.15101@home.osdl.org \
--to=torvalds@osdl.org \
--cc=kakadu_croc@yahoo.com \
--cc=linux-kernel@vger.kernel.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).