Third-party USB hubs may incorrectly disconnect after wake from sleep, causing system instability
Some third-party USB hubs and devices connected though them may disconnect unexpectedly after the computer is woken from sleep. This may cause unexpected behaviors such as general system instability within open applications, or data loss if a connected device was being used to store data from an open document. If a printer was connected through the third-party USB hub, it may not be recognized.
Hi Experts,
I am facing one problem here which is one process always stuck in running state which causes the other similar process to sleep state . This causes my system in hanged state.
On doing cat /proc/<pid>wchan showing the "__init_begin" in the output.
Can you please help me here... (6 Replies)
Hi Experts,
I am facing one problem here which is one process always stuck in running state which causes the other similar process to sleep state . This causes my system in hanged state.
On doing cat /proc/<pid>wchan showing the "__init_begin" in the output.
Can you please help me here... (1 Reply)
Hi Experts,
I am facing one problem here which is one process always stuck in running state which causes the other similar process to sleep state . This causes my system in hanged state.
On doing cat /proc/<pid>wchan showing the "__init_begin" in the output.
Can you please help me here... (0 Replies)
Hi guys,
I am creating two posix threads. I have some queries, hopefully you will help me out with them
1) How can I put a thread to indefinite sleep, for indefinite time period. I am familiar with this
sleep(5);
for 5 second, how can I make it indefinite??
2) How can one thread wake another... (11 Replies)
Hi,
Is someone knows how or maybe the caused why my USB 3G dongle doesn't work when plug-in after boot the /dev/ttyUSB*
I wonder how this /dev/ttyUSB1-4 works, i had a 3G USB dongle for my internet connection before i used lucyd lynx this the same USB dongle works fine when i plug-in after... (2 Replies)
Hello,
I have a Toshiba Satellite A505-S6965. My hardware is as attached via the Hardinfo report in pdf format.
Here is the most recent kernel error. It never says it is shutting down. It just "dies" even after saying the temp/speed is normal.
Jun 16 19:28:00 localhost kernel: CPU0:... (4 Replies)
hubd(7D)hubd(7D)NAME
hubd - USB hub driver
SYNOPSIS
hub@unit-address
The hubd is a USBA (Solaris USB Architecture) compliant client driver that supports USB hubs conforming to the Universal Serial Bus Speci-
fication 2.0. The hubd driver supports bus-powered and self-powered hubs. The driver supports hubs with individual port power, ganged power
and no power switching.
When a device is attached to a hub port, the hubd driver enumerates the device by determining its type and assigning an address to it. For
multi-configuration devices, hubd sets the preferred configuration (refer to cfgadm_usb(1M) to select a configuration). The hubd driver
attaches a driver to the device if one is available for the default or selected configuration. When the device is disconnected from the hub
port, the hubd driver offlines any driver instance attached to the device.
/kernel/drv/hubd
32- bit ELF kernel module
/kernel/drv/amd64/hubd
64- bit ELF kernel module
/kernel/drv/sparcv9/hubd
64-bit SPARC ELF kernel module
See attributes(5) for a description of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Architecture |SPARC, , PCI-based systems |
+-----------------------------+-----------------------------+
|Availability |SUNWusb |
+-----------------------------+-----------------------------+
cfgadm_usb(1M), attributes(5), usba(7D)
Writing Device Drivers
Universal Serial Bus Specification 2.0
System Administration Guide: Basic Administration
http://www.sun.com/io
In addition to being logged, the following messages may also appear on the system console. Messages are formatted in the following manner:
WARNING: <device path> <hubd<instance number>): Message...
where <instance number> is the instance number of hubd and <device path> is the physical path to the device in /devices directory. Messages
from the root hub are displayed with a usb<instance number> prefix instead of hub<instance number> as the root hub is an integrated part of
the host controller.
Connecting device on port <number> failed.
The driver failed to enumerate the device connected on port <number> of hub. If enumeration fails, disconnect and re-connect.
Use of a USB 1.0 hub behind a high speed port may cause unexpected failures.
Devices connected to a USB 1.0 hub which are in turn connected to an external USB 2.0 hub, may misbehave unexpectedly or suddenly go
offline. This is due to a documented incompatibility between USB 1.0 hubs and USB 2.0 hub Transaction Translators. Please use only USB
2.0 or USB 1.1 hubs behind high-speed ports.
Connecting a high speed device to a non-high speed hub (port x) will result in a loss of performance. Please connect the device to a high
speed port to get the maximum performance.
USB 2.0 devices connected to USB 1.0 or 1.1 hubs cannot run at their highest speed, even when the hub is in turn connected to a high-
speed port. For best performance, reconnect without going through a USB 1.0 or 1.1 hub.
Cannot access <device>. Please reconnect.
This hub has been disconnected because a device other than the original one has been inserted. The driver informs you of this fact by
displaying the name of the original device.
Devices not identical to the previous one on this port. Please disconnect and reconnect.
Same condition as described above; however in this case, the driver is unable to identify the original device with a name string.
Hub driver supports max of <n> ports on hub. Hence, using the first <number of physical ports> of <n> ports available.
The current hub driver supports hubs that have <n> ports or less. A hub with more than <n> ports has been plugged in. Only the first
<n> out of the total <number of physical ports> ports are usable.
The following messages may be logged into the system log. They are formatted in the following manner:
<device path> <hubd<instance number>): message...
Global over current condition, please disconnect hub.
The driver detected an over current condition. This means that the aggregate current being drawn by the devices on the downstream port
exceeds a preset value. Refer to section 7.2.1.2 and 11.13 of the Universal Serial Bus Specification 2.0. You must remove and insert
this hub to render it and its downstream devices functional again. If this message continues to display for a particular hub, you may
need to remove downstream devices to eliminate the problem.
Local power has been lost, please disconnect hub.
A USB self-powered hub has lost external power. All USB devices connected down-stream from this hub will cease to function. Disconnect
the hub, plug in the external power-supply and then plug in the hub again.
Local power has been lost, the hub could draw <x> mA power from the USB bus.
A USB self/bus-powered hub has lost external power. Some USB devices connected down-stream from this hub may cease to func-
tion. Disconnect the external power-supply and then plug in the hub again.
20 June 2005 hubd(7D)
