From: Bodo Eggert <7eggert@gmx.de>
To: linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>
Subject: [BUG] No PS/2 mouse in 2.6.16 - bisect result
Date: Thu, 6 Apr 2006 12:21:59 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.58.0604061145230.2262@be1.lrz> (raw)
As decribed in the thread
http://groups.google.com/groups?selm=5V6m7-81J-11@gated-at.bofh.it ,
my mouse does not work in 2.6.16.
Copying the drivers/input/mouse directory from 2.6.15 helped, but
bisecting gave the below result. Reverting this patch did help,
so it must be some kind of conflict with an input patch, but I can't find
a way to make git tell me all commits between foo and bar affecting baz.
I don't intend to do it manually.
---------------------------
8ba7b0a14b2ec19583bedbcdbea7f1c5008fc922 is first bad commit
diff-tree 8ba7b0a14b2ec19583bedbcdbea7f1c5008fc922 (from
91c0bce29e4050a59ee5fdc1192b60bbf8693a6d)
Author: Linus Torvalds <torvalds@g5.osdl.org>
Date: Mon Mar 6 17:38:49 2006 -0800
Add early-boot-safety check to cond_resched()
Just to be safe, we should not trigger a conditional reschedule during
the early boot sequence. We've historically done some questionable
early on, and the safety warnings in __might_sleep() are generally
turned off during that period, so there might be problems lurking.
This affects CONFIG_PREEMPT_VOLUNTARY, which takes over might_sleep()
to
cause a voluntary conditional reschedule.
Acked-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
:040000 040000 397bb2be72349a868d25f8668ee4a7dd86e53c3e
459acaeb07f5d1b1f993a38b084af4c71d76e354 M kernel
--------------------------
# CONFIG_PREEMPT_NONE is not set
CONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not set
--------------------------
--
Never be afraid to try something new. Remember, amateurs built the
ark; professionals built the Titanic. -- Anonymous
next reply other threads:[~2006-04-06 10:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-06 10:21 Bodo Eggert [this message]
2006-04-06 10:31 ` Andrew Morton
2006-04-06 16:40 ` Bodo Eggert
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.0604061145230.2262@be1.lrz \
--to=7eggert@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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®