From: Sid Boyce <sboyce@blueyonder.co.uk>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
Zoltan Boszormenyi <zboszor@freemail.hu>
Subject: Re: USB mice do not work on 2.6.12-rc5-git9, -rc5-mm1, -rc5-mm2
Date: Sun, 05 Jun 2005 15:18:28 +0100 [thread overview]
Message-ID: <42A309B4.9060808@blueyonder.co.uk> (raw)
In-Reply-To: <200506050227.25378.dtor_core@ameritech.net>
Dmitry Torokhov wrote:
> On Sunday 05 June 2005 02:10, Andrew Morton wrote:
>
>>Zoltan Boszormenyi <zboszor@freemail.hu> wrote:
>>
>>>Zoltan Boszormenyi írta:
>>>
>>>>Hi,
>>>>
>>>>$SUBJECT says almost all, system is MSI K8TNeo FIS2R,
>>>>Athlon64 3200+, running FC3/x86-64. I use the multiconsole
>>>>extension from linuxconsole.sf.net, the patch does not touch
>>>>anything relevant under drivers/input or drivers/usb.
>>>>
>>>>The mice are detected just fine but the mouse pointers
>>>>do not move on either of my two screens. The same patch
>>>>(not counting the trivial reject fixes) do work on the
>>>>2.6.11-1.14_FC3 errata kernel. Both PS2 keyboard on the
>>>>keyboard and aux ports work correctly.
>>>
>>>The same patch also works on 2.6.12-rc4-mm2, with working mice.
>>>It seems the bug is mainstream.
>>>
>>
>>Please test an unpatched kernel.
>
>
> I think it is the same problem as Sid is seeing on his box.
>
>
>>I attached dmesg and the contents of /proc/interrupts.
>>The interrupt count on USB does not increase if I move either
>>mouse.
>>
>
>
> Sid, if you move mouse on your box, do you see interrupts reported
> in /proc/interrupts? Do you also have x86-64?
>
2.6.12-rc5-git9 on both x86 and x86_64. On the x86 I have as follows:-
177: 178576 IO-APIC-level ohci_hcd:usb3, eth0
185: 64 IO-APIC-level eth1
193: 5 IO-APIC-level ehci_hcd:usb1, ohci1394
201: 961 IO-APIC-level ohci_hcd:usb2, NVidia nForce2
The interrupts are increasing, but they come from eth0 only, usb3 and
eth0 share the same interrupt.
On the x86_64, all joystick controls and buttons are functional
193: 107220 IO-APIC-level ehci_hcd:usb1, uhci_hcd:usb2,
uhci_hcd:usb3, uhci_hcd:usb4
201: 20940 IO-APIC-level eth0
Possible problem with interrupt routing on the x86 box?. I shall try
"pci=routeirq" next boot.
Regards
Sid.
--
Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot
Retired IBM Mainframes and Sun Servers Tech Support Specialist
Microsoft Windows Free Zone - Linux used for all Computing Tasks
next prev parent reply other threads:[~2005-06-05 14:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-05 6:50 USB mice do not work on 2.6.12-rc5-git9, -rc5-mm1, -rc5-mm2 Zoltan Boszormenyi
2005-06-05 7:14 ` Zoltan Boszormenyi
2005-06-05 7:10 ` Andrew Morton
2005-06-05 7:27 ` Dmitry Torokhov
2005-06-05 14:18 ` Sid Boyce [this message]
2005-06-05 14:33 ` Sid Boyce
2005-06-05 8:48 ` Zoltan Boszormenyi
2005-06-05 10:08 ` Zoltan Boszormenyi
2005-06-05 10:29 ` Zoltan Boszormenyi
2005-06-05 15:17 ` Zoltan Boszormenyi
2005-06-06 20:33 ` Zoltan Boszormenyi
2005-06-06 22:04 ` Mousedev or hiddev problem, was: " Zoltan Boszormenyi
2005-06-07 5:39 ` Vojtech Pavlik
2005-06-08 4:55 ` Zoltan Boszormenyi
2005-06-08 5:17 ` Vojtech Pavlik
2005-06-05 9:09 ` Gene Heskett
2005-06-05 9:10 ` Gene Heskett
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=42A309B4.9060808@blueyonder.co.uk \
--to=sboyce@blueyonder.co.uk \
--cc=akpm@osdl.org \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=zboszor@freemail.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.