Bug 96120 - [ums] [request] USB mouse not always detected
Summary: [ums] [request] USB mouse not always detected
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: usb (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-usb (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-20 22:40 UTC by Walter C. Pelissero
Modified: 2018-05-28 19:46 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Walter C. Pelissero 2006-04-20 22:40:12 UTC
	The mouse port of a MCT PS/2-USB adapter is not always
	detected.  Replugging the adapter would fix the problem but
	unfortunately at the moment this triggers usb/95348.

	Dmesg on my system, when the mouse doesn't work, shows:

	[...]
	ukbd0: MCT Corp. PS/2 - USB Interface Adaptor, rev 1.10/1.00, addr 2, iclass 3/1
	kbd1 at ukbd0
	uhid0: MCT Corp. PS/2 - USB Interface Adaptor, rev 1.10/1.00, addr 2, iclass 3/1
	[...]

	Replugging the adapter:

	ukbd0: at uhub0 port 1 (addr 2) disconnected
	ukbd0: detached
	uhid0: at uhub0 port 1 (addr 2) disconnected
	uhid0: detached
	ukbd0: MCT Corp. PS/2 - USB Interface Adaptor, rev 1.10/1.00, addr 2, iclass 3/1
	kbd1 at ukbd0
	ums0: MCT Corp. PS/2 - USB Interface Adaptor, rev 1.10/1.00, addr 2, iclass 3/1
	ums0: 3 buttons and Z dir.

Fix: 

No one known.
	Replugging the adapter is a workaround.
How-To-Repeat: 	Boot with an MCT PS/2 adaptor connected to the USB port.  Move
	the mouse; the pointer should stay still.  If the pointer
	moves, it was a lucky start: reboot.
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2008-01-29 09:46:45 UTC
State Changed
From-To: open->suspended

Mark suspended awaiting patches.
Comment 2 Eitan Adler freebsd_committer freebsd_triage 2018-05-28 19:46:30 UTC
batch change:

For bugs that match the following
-  Status Is In progress 
AND
- Untouched since 2018-01-01.
AND
- Affects Base System OR Documentation

DO:

Reset to open status.


Note:
I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.