From: Linus Torvalds <torvalds@linux-foundation.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Arjan van de Ven <arjan@linux.intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
NetDev <netdev@vger.kernel.org>, Dmitry Torokhov <dtor@mail.ru>
Subject: Re: Oops/Warning report for the week of March 28th 2008
Date: Fri, 28 Mar 2008 15:01:24 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.00.0803281500100.14670@woody.linux-foundation.org> (raw)
In-Reply-To: <1206740581.22530.83.camel@johannes.berg>
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
next prev parent reply other threads:[~2008-03-28 22:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 18:55 Arjan van de Ven
2008-03-28 20:21 ` Linus Torvalds
2008-03-28 20:51 ` Linus Torvalds
2008-03-28 21:01 ` Johannes Berg
2008-03-28 21:24 ` Linus Torvalds
2008-03-28 21:43 ` Johannes Berg
2008-03-28 22:01 ` Linus Torvalds [this message]
2008-03-28 22:14 ` Jiri Kosina
2008-03-28 22:14 ` Johannes Berg
2008-03-28 21:16 ` Dmitry Torokhov
2008-03-29 12:20 ` Björn Steinbrink
2008-03-28 20:57 ` Björn Steinbrink
2008-03-28 22:33 ` Arjan van de Ven
2008-03-28 22:58 ` Arjan van de Ven
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=alpine.LFD.1.00.0803281500100.14670@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=dtor@mail.ru \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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
all inboxes | Powered by JetHome®