Third-party USB hubs may incorrectly disconnect after wake from sleep, causing system instability

 
Thread Tools Search this Thread
Operating Systems OS X (Apple) OS X Support RSS Third-party USB hubs may incorrectly disconnect after wake from sleep, causing system instability
# 1  
Old 03-09-2011
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.

More from Apple OS X Support ...
Login or Register to Ask a Question

Previous Thread | Next Thread

6 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Process remians in Running state causing other similar process to sleep and results to system hang

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)
Discussion started by: naveeng
6 Replies

2. UNIX for Advanced & Expert Users

Process remians in Running state causing other similar process to sleep and results to system hang

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)
Discussion started by: naveeng
1 Replies

3. BSD

Process remians in Running state causing other similar process to sleep and results to system hang

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)
Discussion started by: naveeng
0 Replies

4. Programming

How to sleep and wake a thread???

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)
Discussion started by: gabam
11 Replies

5. Ubuntu

Does /dev/ttyUSB* causing my usb 3G Dongle doesn't work when plug-in

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)
Discussion started by: jao_madn
2 Replies

6. Hardware

Overheating causing system shutdowns

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)
Discussion started by: Narnie
4 Replies
Login or Register to Ask a Question
USB_MAKE_PATH(9)					  Host-Side Data Types and Macro					  USB_MAKE_PATH(9)

NAME
usb_make_path - returns stable device path in the usb tree SYNOPSIS
int usb_make_path(struct usb_device * dev, char * buf, size_t size); ARGUMENTS
dev the device whose path is being constructed buf where to put the string size how big is "buf"? DESCRIPTION
Returns length of the string (> 0) or negative if size was too small. This identifier is intended to be "stable", reflecting physical paths in hardware such as physical bus addresses for host controllers or ports on USB hubs. That makes it stay the same until systems are physically reconfigured, by re-cabling a tree of USB devices or by moving USB host controllers. Adding and removing devices, including virtual root hubs in host controller driver modules, does not change these path identifers; neither does rebooting or re-enumerating. These are more useful identifiers than changeable ("unstable") ones like bus numbers or device addresses. With a partial exception for devices connected to USB 2.0 root hubs, these identifiers are also predictable. So long as the device tree isn't changed, plugging any USB device into a given hub port always gives it the same path. Because of the use of "companion" controllers, devices connected to ports on USB 2.0 root hubs (EHCI host controllers) will get one path ID if they are high speed, and a different one if they are full or low speed. COPYRIGHT
Kernel Hackers Manual 2.6. July 2010 USB_MAKE_PATH(9)