From: Linus Torvalds <torvalds@osdl.org>
To: Christian Kujau <evil@g-house.de>
Cc: Matt Domsch <Matt_Domsch@dell.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
Pekka Enberg <penberg@gmail.com>, Greg KH <greg@kroah.com>
Subject: Re: Oops in 2.6.10-rc1 (almost solved)
Date: Thu, 11 Nov 2004 16:49:59 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.58.0411111645110.2301@ppc970.osdl.org> (raw)
In-Reply-To: <41940384.1000409@g-house.de>
On Fri, 12 Nov 2004, Christian Kujau wrote:
>
> nevermind then. as nobody else seem to be bothered by this i am happy with
> the workarund (CONFIG_EDD=n) and since the lkml-archives exist we could
> get back to it when it's bothering more people (n>1)
The problem with that approach is that very few people are willing to
spend the time and effort to really try to figure out where the problem
triggers for them. Thanks again for testing lots of kernels, and different
configurations.
Basically, if it's a problem that only happens for a smallish percentage
of people, and an even smaller percentage of those is willing to dig down
and find it, it's not a problem we can afford to ignore. Ignoring it just
means that there will be "a few" error reports that we will either waste
time on, or (even worse) we'll dismiss as "known problems" and then
possibly miss _another_ bug.
This is why I take random unexplained (but pinpointed) problems so
seriously. If it wasn't as apparently random, we could file it under
"known problem" and decide to try to fix it later. As it is, it's filed
under "known cause", but since we don't know _why_, it might cause totally
different problems on another machine, and that just makes it too painful
for words.
So the changeset is reverted for now in the current -bk tree, and I'll
make a -rc2 this weekend and hope that we can stabilize for 2.6.10.
Linus
next prev parent reply other threads:[~2004-11-12 0:56 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-28 13:12 Oops in 2.6.10-rc1 Christian
2004-10-28 13:29 ` [Alsa-devel] " Jaroslav Kysela
2004-10-28 14:09 ` Christian
2004-11-04 15:16 ` Christian Kujau
2004-11-05 2:35 ` Christian Kujau
2004-11-05 11:40 ` holborn
2004-11-07 1:24 ` Christian Kujau
2004-11-07 7:02 ` Linus Torvalds
2004-11-07 13:10 ` Christian Kujau
2004-11-07 16:02 ` Christian Kujau
2004-11-07 16:57 ` Linus Torvalds
2004-11-07 18:31 ` Christian Kujau
2004-11-07 18:44 ` Linus Torvalds
2004-11-07 23:45 ` Christian Kujau
2004-11-07 23:45 ` Christian Kujau
2004-11-08 1:16 ` Linus Torvalds
2004-11-08 1:16 ` Linus Torvalds
2004-11-08 13:01 ` Christian Kujau
2004-11-08 13:01 ` Christian Kujau
2004-11-08 18:13 ` Linus Torvalds
2004-11-08 18:13 ` Linus Torvalds
2004-11-08 20:59 ` Christian Kujau
2004-11-08 20:59 ` Christian Kujau
2004-11-08 23:49 ` Christian Kujau
2004-11-09 1:05 ` Linus Torvalds
2004-11-09 1:41 ` Christian Kujau
2004-11-09 1:31 ` Christian Kujau
2004-11-09 7:40 ` Pekka Enberg
2004-11-09 12:33 ` Christian Kujau
2004-11-09 17:26 ` Oops in 2.6.10-rc1 (almost solved) Christian Kujau
2004-11-09 18:53 ` Linus Torvalds
2004-11-09 19:04 ` [PATCH] kobject: fix double kobject_put() in error path of kobject_add() Greg KH
2004-11-09 19:08 ` Greg KH
2004-11-09 20:19 ` Pekka Enberg
2004-11-09 21:21 ` Christian Kujau
2004-11-09 21:31 ` Christian Kujau
2004-11-09 19:09 ` Linus Torvalds
2004-11-09 22:06 ` Christian Kujau
2004-11-09 23:30 ` Oops in 2.6.10-rc1 (almost solved) Christian Kujau
2004-11-09 23:40 ` Matt Domsch
2004-11-10 0:21 ` Christian Kujau
2004-11-10 1:01 ` Linus Torvalds
2004-11-11 22:43 ` Matt Domsch
2004-11-11 22:53 ` Linus Torvalds
2004-11-11 22:55 ` Matt Domsch
2004-11-12 0:27 ` Christian Kujau
2004-11-12 0:49 ` Linus Torvalds [this message]
2004-11-12 1:27 ` Christian Kujau
2004-11-10 0:12 ` Oops in 2.6.10-rc1 Christian Kujau
2004-11-10 0:23 ` Linus Torvalds
2004-11-08 18:44 ` Pekka Enberg
2004-11-08 18:44 ` Pekka Enberg
2004-11-08 19:00 ` Greg KH
2004-11-08 19:00 ` Greg KH
2004-11-08 19:18 ` Pekka Enberg
2004-11-08 19:18 ` Pekka Enberg
2004-11-08 19:30 ` Pekka Enberg
2004-11-08 19:30 ` Pekka Enberg
2004-11-08 20:31 ` Christian Kujau
2004-11-08 20:31 ` Christian Kujau
2004-11-07 13:05 ` Pekka Enberg
2004-11-07 13:43 ` Christian Kujau
2004-11-13 3:45 Oops in 2.6.10-rc1 (almost solved) Chuck Ebbert
2004-11-13 14:28 ` Matt Domsch
2004-11-13 18:55 ` Matt Domsch
2004-11-14 2:58 ` Matt Domsch
2004-11-14 4:43 ` Linus Torvalds
2004-11-14 11:45 ` Christian
2004-11-14 20:02 ` Christian Kujau
2004-11-14 21:55 ` Matt Domsch
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.0411111645110.2301@ppc970.osdl.org \
--to=torvalds@osdl.org \
--cc=Matt_Domsch@dell.com \
--cc=evil@g-house.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.