Skip to contentSkip to conversation

2.2.18pre, usb mouse messages

DISCUSSION f5ibh 3 participants 3 messages Nov 23, 2000 – Nov 24, 2000 USB

lore
Share & tools
lore

f5ibh

author
#0 lore raw

Hi,

I use an USB mouse, it works perfectly both with 'gpm' and with X-window but time to time, I've this kind of message stream :

[root@debian-f5ibh] ~ # usb-uhci.c: interrupt, status 3, frame# 20 usb-uhci.c: interrupt, status 3, frame# 44
usb-uhci.c: interrupt, status 3, frame# 68
usb-uhci.c: interrupt, status 3, frame# 92
usb-uhci.c: interrupt, status 3, frame# 116
usb-uhci.c: interrupt, status 3, frame# 140
usb-uhci.c: interrupt, status 3, frame# 164
usb-uhci.c: interrupt, status 3, frame# 188
usb-uhci.c: interrupt, status 3, frame# 212
hub.c: already running port 2 disabled by hub (EMI?), re-enabling...

This message appears with most (all ?) of the 2.2.18pre releases, the actual one is 2.2.18pre23.

Computer is pentium 200MMX, 64Mb SDRAM.

Relevant CONFIG bits :
----------------------
# USB support
#
CONFIG_USB=m
# CONFIG_USB_DEBUG is not set

# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
CONFIG_HOTPLUG=y
# CONFIG_USB_BANDWIDTH is not set

#
# USB Controllers
#
CONFIG_USB_UHCI=m
# CONFIG_USB_UHCI_ALT is not set
# CONFIG_USB_OHCI is not set

#
# USB Devices
#
# CONFIG_USB_PRINTER is not set
# CONFIG_USB_SCANNER is not set
# CONFIG_USB_AUDIO is not set
# CONFIG_USB_ACM is not set
# CONFIG_USB_SERIAL is not set
# CONFIG_USB_IBMCAM is not set
# CONFIG_USB_OV511 is not set
# CONFIG_USB_DC2XX is not set
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_STORAGE is not set
# CONFIG_USB_DABUSB is not set
# CONFIG_USB_PLUSB is not set
# CONFIG_USB_PEGASUS is not set
#
# USB HID
#
CONFIG_USB_HID=m
# CONFIG_USB_KBD is not set
# CONFIG_USB_MOUSE is not set
# CONFIG_USB_WACOM is not set
# CONFIG_USB_WMFORCE is not set
# CONFIG_INPUT_KEYBDEV is not set
CONFIG_INPUT_MOUSEDEV=m
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_EVDEV is not set

boot messages :
---------------
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb.c: registered new driver hid
usb-uhci.c: $Revision: 1.237 $ time 23:53:07 Nov 23 2000 usb-uhci.c: High bandwidth mode enabled
usb-uhci.c: USB UHCI at I/O 0x6100, IRQ 11
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
usb.c: USB new device connect, assigned device number 1 hub.c: USB hub found
hub.c: 2 ports detected
mice: PS/2 mouse device common for all mice
usb.c: USB new device connect, assigned device number 2
mouse0: PS/2 mouse device for input0
input0: USB HID v1.00 Mouse [Cypress Sem. Cypress USB Mouse] on usb1:2.0 hub.c: already running port 2 disabled by hub (EMI?), re-enabling... usb.c: USB disconnect on device 2
usb.c: USB new device connect, assigned device number 2
mouse0: PS/2 mouse device for input0
input0: USB HID v1.00 Mouse [Cypress Sem. Cypress USB Mouse] on usb1:2.0

----
Regards

Jean-Luc
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/

#1 lore raw
Quoted 16 lines · On Thu, Nov 23, 2000 at 10:32:01PM +0100, f5ibh wrote:

Hi,

I use an USB mouse, it works perfectly both with 'gpm' and with X-window but time to time, I've this kind of message stream :

[root@debian-f5ibh] ~ # usb-uhci.c: interrupt, status 3, frame# 20 usb-uhci.c: interrupt, status 3, frame# 44
usb-uhci.c: interrupt, status 3, frame# 68
usb-uhci.c: interrupt, status 3, frame# 92
usb-uhci.c: interrupt, status 3, frame# 116
usb-uhci.c: interrupt, status 3, frame# 140
usb-uhci.c: interrupt, status 3, frame# 164
usb-uhci.c: interrupt, status 3, frame# 188
usb-uhci.c: interrupt, status 3, frame# 212
hub.c: already running port 2 disabled by hub (EMI?), re-enabling...

Quoted 2 lines

This message appears with most (all ?) of the 2.2.18pre releases, the actual one is 2.2.18pre23.

The messages are harmless debug messages. Anyone want to whip up a patch to turn them off (like was recently done for 2.4.0-test)? If no one else does, I can do it later this weekend...

greg k-h

Signature · 6 lines
greg@(kroah|wirex).com
http://immunix.org/~greg
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
#2 lore raw
In reply to f5ibh
Quoted 3 lines
Quoted 3 lines

usb-uhci.c: interrupt, status 3, frame# 212
hub.c: already running port 2 disabled by hub (EMI?), re-enabling...

[Greg KH]

Quoted 2 lines

The messages are harmless debug messages. Anyone want to whip up a patch to turn them off (like was recently done for 2.4.0-test)?

Is this what you mean?

Peter

drivers/usb/hub.c renamed from drivers/usb/hub.c.bak +1 -4
diff -urk.bak 2.2.18-19/drivers/usb/hub.c.bak 2.2.18-19/drivers/usb/hub.c
@@ -530,11 +530,8 @@
 				// be shutdown by the hub, this hack enables them again.
 				// Works at least with mouse driver. 
 				if (!(portstatus & USB_PORT_STAT_ENABLE) && 
-				    (portstatus & USB_PORT_STAT_CONNECTION) && (dev->children[i])) {
-					err("already running port %i disabled by hub (EMI?), re-enabling...",
-						i + 1);
+				    (portstatus & USB_PORT_STAT_CONNECTION) && (dev->children[i]))
 					usb_hub_port_connect_change(dev, i);
-				}
 			}
 
 			if (portstatus & USB_PORT_STAT_SUSPEND) {
drivers/usb/usb-uhci.c renamed from drivers/usb/usb-uhci.c.bak +3 -9
diff -urk.bak 2.2.18-19/drivers/usb/usb-uhci.c.bak 2.2.18-19/drivers/usb/usb-uhci.c
@@ -2538,16 +2538,10 @@
 
 	dbg("interrupt");
 
-	if (status != 1) {
-		warn("interrupt, status %x, frame# %i", status, 
-		     UHCI_GET_CURRENT_FRAME(s));
+	// remove host controller halted state
+	if ((status&0x20) && (s->running))
+		outw (USBCMD_RS | inw(io_addr + USBCMD), io_addr + USBCMD);
 
-		// remove host controller halted state
-		if ((status&0x20) && (s->running)) {
-			outw (USBCMD_RS | inw(io_addr + USBCMD), io_addr + USBCMD);
-		}
-		//uhci_show_status (s);
-	}
 	/*
 	 * traverse the list in *reverse* direction, because new entries
 	 * may be added at the end.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/