Bug 9097 - rndis_host claiming PocketPC and not releasing it
Summary: rndis_host claiming PocketPC and not releasing it
Status: REJECTED INVALID
Alias: None
Product: Drivers
Classification: Unclassified
Component: USB (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Greg Kroah-Hartman
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-28 10:45 UTC by Paul Lemmons
Modified: 2008-04-11 01:08 UTC (History)
0 users

See Also:
Kernel Version: 2.6.22.7-85.fc7
Subsystem:
Regression: ---
Bisected commit-id:


Attachments

Description Paul Lemmons 2007-09-28 10:45:22 UTC
Most recent kernel where this bug did not occur: 2.6.22.7-85
Distribution: Fedora 7, Gentoo and probably others
Hardware Environment: Intel
Software Environment: KDE
Problem Description:

I use VMware v5 and active sync under a virtual Windows session. Prior to 2.6.21 kernel there was never a problem. Now, It occasionally works but most of the time it fails. 

When I connect my PDA (Dell Axim) I see the following in dmesg:

usb 4-1: new full speed USB device using uhci_hcd and address 2
usb 4-1: configuration #1 chosen from 1 choice
usbcore: registered new interface driver cdc_ether
eth2: register 'rndis_host' at usb-0000:00:1d.3-1, RNDIS device, 80:00:60:0f:e8:00
usbcore: registered new interface driver rndis_host
usb 4-1: USB disconnect, address 2

on my VMWare session I get a dialog that says:

The specified device appears to be claimed by another driver (rndis_host) on the host operating system which means that the device may be in use. To continue, the device will first be disconnected from its current driver.

Pressing OK does not have a positive effect.

I have read bug: 8094 and it may or may not apply. I am not getting the oops. 

A post on the VMWare forum has more detailed information form others experiencing the same problem. 

http://communities.vmware.com/message/759604


Steps to reproduce:

1) Connect PDA (PocketPC/Windows Mobile 5)
2) See message appear on VMWare session
Comment 1 Greg Kroah-Hartman 2007-09-28 11:03:44 UTC
This is not a Linux kernel issue, vmware knows how to properly disconnect a device from a driver, they just need to do it in the correct manner.

I suggest you take this up with them.
Comment 2 Stephen J. Gowdy 2008-04-11 01:08:30 UTC
Could this be due to a different structure in /sys/bus/usb/devices/? Did it previously use <bus>-<device> and now it is <bus>-<port>.<port>, or was it always the later?

Note You need to log in before you can comment on or make changes to this bug.