Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755943AbZJLKSt (ORCPT ); Mon, 12 Oct 2009 06:18:49 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755427AbZJLKSs (ORCPT ); Mon, 12 Oct 2009 06:18:48 -0400 Received: from mx3.mail.elte.hu ([157.181.1.138]:56036 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751474AbZJLKSr (ORCPT ); Mon, 12 Oct 2009 06:18:47 -0400 Date: Mon, 12 Oct 2009 12:17:46 +0200 From: Ingo Molnar To: "Justin P. Mattock" Cc: rostedt@goodmis.org, Jason Baron , Peter Zijlstra , Li Zefan , Frederic Weisbecker , Linux Kernel Mailing List Subject: Re: system gets stuck in a lock during boot Message-ID: <20091012101746.GC15777@elte.hu> References: <1254880921.1696.112.camel@gandalf.stny.rr.com> <4ACC001D.4050105@gmail.com> <1254920429.1696.127.camel@gandalf.stny.rr.com> <4ACCAB54.4010408@gmail.com> <1254928298.1696.166.camel@gandalf.stny.rr.com> <4ACCB934.7070805@gmail.com> <1254931582.1696.171.camel@gandalf.stny.rr.com> <4ACCE1BA.5000307@gmail.com> <1254941730.1696.177.camel@gandalf.stny.rr.com> <4ACCE72B.3010906@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4ACCE72B.3010906@gmail.com> User-Agent: Mutt/1.5.18 (2008-05-17) X-ELTE-SpamScore: -1.5 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.5 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.5 -1.5 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0002] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1271 Lines: 38 * Justin P. Mattock wrote: > Steven Rostedt wrote: >> On Wed, 2009-10-07 at 11:45 -0700, Justin P. Mattock wrote: >> >> >>>> >>>> >>> yep like I said I owe you guys an apology, for >>> my mistake(thanks for taking the time). >>> >> >> Well, thank you for reporting it. If nobody reports any problems, we >> just assume everything is OK, and as people curse us out and look for >> alternatives, we will be sipping our mai-tais in ignorant bliss. >> >> -- Steve >> >> > > agree, my main concern when reporting is to make sure that it's a real > issue, and not a mistake like this one. Well, it can be really hard to filter out whether a problem is somehow self-inflicted or caused by the kernel proper - thus we generally prefer over-reporting over under-reporting. Even if it's self-inflicted it's useful on a meta level: if many people report it then we might end up adding more safety guards to disable a particular common pattern of shoot-foot-self incidents. Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/