Re: [linux-usb-devel] USB-kbd+mouse spontaneously disconnects

2005-11-08 Thread Alan Stern 
On Tue, 8 Nov 2005, Christian Iversen wrote:

 On Saturday 05 November 2005 17:47, Christian Iversen wrote:
 
 Does nobody have a single idea what's wrong here? 
 
  I'm having an El Cheapo usb keyboard+mouse usb device, and an Logitech
  MX700 usb mouse connected to a computer.
 
  Bus 003 Device 001: ID :
  Bus 002 Device 001: ID :
  Bus 001 Device 005: ID 060b:5811 Solid Year ACK-571U Wireless Keyboard
  Bus 001 Device 003: ID 046d:c506 Logitech, Inc. MX-700 Cordless Mouse
  Receiver Bus 001 Device 001: ID :
 
  The MX700 has no problems, I'm just including it here for completeness.
 
  The keyboardmouse (km) is the problem. It sometimes disconnects for no
  good reason. If the km has disconnected, it can easily be reconnected by
  physically reconnecting the device, but that's wrong on so many levels..
  :-)
 
  Now, I finally managed to get a debug-enabled dmesg output at the time
  something like this happened. I have to be completely honest when I say I
  can't remember if this is at the first or second disconnect. It seems to be
  the second one, though.
 
  Can somebody take a look at the atteched dmesg? It's with usb full-debug
  mode on, and goes all the way back to the start of the machine. It should
  be easy to read, and complete.
 
  I can't really figure out what's going on, so I hope someone here can :-)

Your log shows the keyboardmouse failed to respond to a 1-byte control-OUT
message.  Then there was a disconnection (can't tell if the device did
that by itself or if you unplugged it by hand) and a reconnection.  Then
it looks like you did rmmod usbhid followed by modprobe usbhid, which
was not entirely successful because the keyboardmouse again seems to have 
stopped responding.

There's nothing to indicate what caused the original problem or how it can 
be fixed, although replacing the keyboardmouse might be a good start.

Alan Stern



---
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42 plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
___
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Re: [linux-usb-devel] USB-kbd+mouse spontaneously disconnects

2005-11-07 Thread Christian Iversen 
On Saturday 05 November 2005 17:47, Christian Iversen wrote:

Does nobody have a single idea what's wrong here? 

 I'm having an El Cheapo usb keyboard+mouse usb device, and an Logitech
 MX700 usb mouse connected to a computer.

 Bus 003 Device 001: ID :
 Bus 002 Device 001: ID :
 Bus 001 Device 005: ID 060b:5811 Solid Year ACK-571U Wireless Keyboard
 Bus 001 Device 003: ID 046d:c506 Logitech, Inc. MX-700 Cordless Mouse
 Receiver Bus 001 Device 001: ID :

 The MX700 has no problems, I'm just including it here for completeness.

 The keyboardmouse (km) is the problem. It sometimes disconnects for no
 good reason. If the km has disconnected, it can easily be reconnected by
 physically reconnecting the device, but that's wrong on so many levels..
 :-)

 Now, I finally managed to get a debug-enabled dmesg output at the time
 something like this happened. I have to be completely honest when I say I
 can't remember if this is at the first or second disconnect. It seems to be
 the second one, though.

 Can somebody take a look at the atteched dmesg? It's with usb full-debug
 mode on, and goes all the way back to the start of the machine. It should
 be easy to read, and complete.

 I can't really figure out what's going on, so I hope someone here can :-)

-- 
Regards,
Christian Iversen


---
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42 plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
___
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

[linux-usb-devel] USB-kbd+mouse spontaneously disconnects

2005-11-05 Thread Christian Iversen 

I'm having an El Cheapo usb keyboard+mouse usb device, and an Logitech MX700 
usb mouse connected to a computer. 

Bus 003 Device 001: ID :
Bus 002 Device 001: ID :
Bus 001 Device 005: ID 060b:5811 Solid Year ACK-571U Wireless Keyboard
Bus 001 Device 003: ID 046d:c506 Logitech, Inc. MX-700 Cordless Mouse Receiver
Bus 001 Device 001: ID :

The MX700 has no problems, I'm just including it here for completeness. 

The keyboardmouse (km) is the problem. It sometimes disconnects for no 
good reason. If the km has disconnected, it can easily be reconnected by 
physically reconnecting the device, but that's wrong on so many levels.. :-)

Now, I finally managed to get a debug-enabled dmesg output at the time 
something like this happened. I have to be completely honest when I say I 
can't remember if this is at the first or second disconnect. It seems to be 
the second one, though.

Can somebody take a look at the atteched dmesg? It's with usb full-debug mode 
on, and goes all the way back to the start of the machine. It should be easy 
to read, and complete.

I can't really figure out what's going on, so I hope someone here can :-)

-- 
Regards,
Christian Iversen
Linux version 2.6.13-venus ([EMAIL PROTECTED]) (gcc version 3.3.5 (Debian 
1:3.3.5-13)) #1 SMP Thu Oct 20 12:09:56 CEST 2005
BIOS-provided physical RAM map:
 BIOS-e820:  - 0009fc00 (usable)
 BIOS-e820: 0009fc00 - 000a (reserved)
 BIOS-e820: 000f - 0010 (reserved)
 BIOS-e820: 0010 - 1ffec000 (usable)
 BIOS-e820: 1ffec000 - 1ffef000 (ACPI data)
 BIOS-e820: 1ffef000 - 1000 (reserved)
 BIOS-e820: 1000 - 2000 (ACPI NVS)
 BIOS-e820:  - 0001 (reserved)
511MB LOWMEM available.
On node 0 totalpages: 131052
  DMA zone: 4096 pages, LIFO batch:1
  Normal zone: 126956 pages, LIFO batch:31
  HighMem zone: 0 pages, LIFO batch:1
DMI 2.3 present.
ACPI: RSDP (v000 ASUS  ) @ 0x000f6e20
ACPI: RSDT (v001 ASUS   A7V266-E 0x30303031 MSFT 0x31313031) @ 0x1ffec000
ACPI: FADT (v001 ASUS   A7V266-E 0x30303031 MSFT 0x31313031) @ 0x1ffec080
ACPI: BOOT (v001 ASUS   A7V266-E 0x30303031 MSFT 0x31313031) @ 0x1ffec040
ACPI: DSDT (v001   ASUS A7V266-E 0x1000 MSFT 0x010b) @ 0x
ACPI: PM-Timer IO Port: 0xe408
Allocating PCI resources starting at 2000 (gap: 2000:dfff)
Built 1 zonelists
Kernel command line: root=/dev/hda1
Local APIC disabled by BIOS -- you can enable it with lapic
mapped APIC to d000 (01413000)
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 32768 bytes)
Detected 1343.234 MHz processor.
Using pmtmr for high-res timesource
Console: colour VGA+ 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 513056k/524208k available (3699k kernel code, 10688k reserved, 1440k 
data, 276k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 2688.08 BogoMIPS (lpj=1344040)
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 0383f9ff c1cbf9ff    
 
CPU: After vendor identify, caps: 0383f9ff c1cbf9ff    
 
CPU: CLK_CTL MSR was 6003d22f. Reprogramming to 2003d22f
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
CPU: After all inits, caps: 0383f9ff c1cbf9ff  0020  
 
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
mtrr: v2.0 (20020519)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
ACPI: setting ELCR to 0200 (from 0c20)
CPU0: AMD Athlon(TM) XP1500+ stepping 01
SMP motherboard not detected.
Local APIC not detected. Using dummy APIC emulation.
Brought up 1 CPUs
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xf0ed0, last bus=1
PCI: Using configuration type 1
ACPI: Subsystem revision 20050408
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)
ACPI: PCI Root Bridge [PCI0] (:00)
PCI: Probing PCI hardware (bus 00)
ACPI: Assume root bridge [\_SB_.PCI0] segment is 0
ACPI: Assume root bridge [\_SB_.PCI0] bus is 0
Boot video device is :01:00.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT]
Linux Plug and Play Support v0.97 (c) Adam