public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: mouse&keyboard with 2.6.10+
Date: Mon, 14 Mar 2005 22:06:37 +0300	[thread overview]
Message-ID: <4235E0BD.5090200@tls.msk.ru> (raw)
In-Reply-To: <20050314164342.GA1735@ucw.cz>

Vojtech Pavlik wrote:
[]
>>In 2.6.9 (it works just fine too, problem happens with 2.6.10 and up
>>only), there's no such parameter in drivers/pci/quirks.c.  Hmm.
> 
> Any chance the order of module loading changed between the two versions?
> I see you have 'psmouse' as a module. If i8042 (and psmouse) are loaded
> after uhci-hcd (or ohci-hcd), the problem will disappear, too.

Yes, the prob disappears if usb controller driver is loaded before the
mouse driver.  Obviously I didn't know USB is "involved" here so I never
looked at the problem from this point of view before.  Now when I looked
at it, I see I have uhci-hcd driver being loaded in my 2.6.9 initrd,
before mouse (I removed it after as it wasn't needed).  I also tried
loading 2.6.9 without uhci-hcd but with USB keyboard/mouse enabled in
BIOS - the mouse is flaky too, similar to 2.6.10 behaviour.

Interesting.  I was looking at the difference in input subsystem
between 2.6.9 and 2.6.10 -- obviously there's nothing relevant here! ;)

>>So is this a bios/mobo problem,
> 
> Yes.

Never had any single problem with this hardware so far.  But.. uh-oh.
Well.. it's only 2.6 kernel that encounters problem with it for now,
so it must be the kernel... ;)

>>or can it be solved in kernel somehow?
> 
> We could have usb-handoff by default.

What's the consequences of this?
If it does not hurt (does it?), why not to enable it?
And if it does not hurt, I can enable it in our default netboot
image as well.. if not to see whenever all our machines will work
ok with this parameter.

Thank you very much - this mysterious problem.. I was trying to
find the solution for quite some time before posting to LKML,
without any success, and the solution was already here! ;)

/mjt

  reply	other threads:[~2005-03-14 19:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-14 10:32 mouse&keyboard with 2.6.10+ Michael Tokarev
2005-03-14 11:52 ` Michael Tokarev
2005-03-14 14:28   ` Vojtech Pavlik
2005-03-14 15:53     ` Michael Tokarev
2005-03-14 16:25       ` Vojtech Pavlik
2005-03-14 16:38         ` Michael Tokarev
2005-03-14 16:43           ` Vojtech Pavlik
2005-03-14 19:06             ` Michael Tokarev [this message]
2005-03-14 19:21               ` Vojtech Pavlik
2005-03-22  1:24             ` Andrew Morton
2005-03-22  7:44               ` Vojtech Pavlik
2005-03-22 13:56                 ` Alan Cox
2005-03-14 16:30       ` Dmitry Torokhov

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=4235E0BD.5090200@tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@suse.cz \
    /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