From mboxrd@z Thu Jan 1 00:00:00 1970 From: Linus Torvalds Subject: Re: Oops/Warning report for the week of March 28th 2008 Date: Fri, 28 Mar 2008 15:01:24 -0700 (PDT) Message-ID: References: <47ED3F1A.1090101@linux.intel.com> (sfid-20080328_205203_254278_BF9EB41F) <1206738071.22530.80.camel@johannes.berg> <1206740581.22530.83.camel@johannes.berg> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Arjan van de Ven , Linux Kernel Mailing List , NetDev , Dmitry Torokhov To: Johannes Berg Return-path: In-Reply-To: <1206740581.22530.83.camel@johannes.berg> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Fri, 28 Mar 2008, Johannes Berg wrote: > > I tend to think it's actually a regression, I've done exactly what I > described there dozens of times before on older kernels and it doesn't > seem to be a race condition, X always locks the input device and I never > had trouble with that before. Ahh. So it's easily repeatable for you.. Do you think you could bisect it? At least a few runs? Even a partial bisection will give a nice (== much smaller) range of commits to be blamed, and might tell us why it started happening.. Linus