USB devices causing G5 meltdown

A friend purchased a used G5 Dual 2.5GHz running a fresh install of 10.4.x. The machine runs fine when no USB devices are attached, but consistently crashes when a USB device is connected. Both the Maxtor external HDD and Pro Tools external audio Interface (Mbox2) result in the same behavior. The computer attempts to go to sleep and never wakes up, with the fans humming at full strength. Without the USB devices attached the machine can go to sleep without problems.
This occurs with both the front USB ports and the rear (Althoug I assume these are connected to the same controller?) The keyboard and mouse can remain connected without issues. It would appear that the USB hardware is the original.
Thoughts, next troubleshooting steps?
Much appreciated,
Jon

Ah, the good ol' cinema display. We may have Yahtzee.
That would most likely be your problem. The hubs built into those monitors are prone to failure. It is especially bad if you chain a mouse of the keyboard ports.
Try leaving the hub connections from the monitor disconnected and plug the mouse and keyboard each into its own USB port on the Mac and try that. If it works and you still need a hub try a standalone powered USB hub.

Similar Messages

USB devices cause a crash at Lion login screen

Since I have installed MacOS X Lion I am experiencing regular crashes at the login screen at startup.
These crashes occur virtually always when
+ a USB device that was connected at the previous shutdown is missing at next launch
+ a USB device that was not connected at previous shutdown is connected at next launch
The type of the device does not make a difference.
I have had this with USB sticks, but also with my Wacom graphics tablet and a regular USB hard disk (connected via two USB ports).
This is extremely annoying and I had hoped this would be fixed with the latest Lion upgrade, but it is not.
Anyone out there has an idea for an easy fix?

Guys -
am I really the only person who sees this?
This is a serious issue and I also see it happening upon connecting certain USB devices (e.g. today a Garmin nüvi 1250) while running Lion. Non of the OS updates since I posted this helped.
I feel like I am running Windows here...

USB Devices Cause Kernal Panic

Hi Everyone,
Ok, So on my White MacBook 2.2Ghz Core 2 Duo when I plug a device into either of the USB ports the computer goes into a kernal panic. It has the screen that says press the power button to turn off your computer. The funny thing, is that it only seems to be certain types of devices: Printers, and Jumpdrives. The mouse and keyboard don't do that, and neither does the iPhone. Any ideas?
Thanks!

Tue Mar 3 12:14:29 2009
panic(cpu 1 caller 0x003EB97C): "IOUSBDevice::_RESERVEDIOUSBDevice8 called\n"@/SourceCache/xnu/xnu-1228.9.59/libkern/c++/OSMetaClass.cpp:816
Backtrace (CPU 1), Frame : Return Address (4 potential args on stack)
0x3bfb7a68 : 0x12b4f3 (0x45b13c 0x3bfb7a9c 0x1335e4 0x0)
0x3bfb7ab8 : 0x3eb97c (0x49c500 0x678280 0x678280 0x8)
0x3bfb7ad8 : 0x6694d4 (0x680118 0x8 0x3bfb7b08 0x3ece8f)
0x3bfb7af8 : 0x34696b66 (0xbafbe00 0x3bfb7b1c 0x3bfb7b28 0x3f0459)
0x3bfb7b28 : 0x346979ce (0xbeb0e00 0x3469cad4 0x3ebfe60 0x0)
0x3bfb7b78 : 0x412976 (0xbeb0e00 0xbaf6000 0x1 0x3ecd96)
0x3bfb7bd8 : 0x414219 (0xbaf6000 0xbeb0e00 0xbc6a6c0 0xbc72280)
0x3bfb7c58 : 0x413a7d (0xbaf6000 0x45e4d80 0x0 0x1)
0x3bfb7ca8 : 0x414786 (0xbaf6000 0x2 0x0 0x0)
0x3bfb7ce8 : 0x40e528 (0xbaf6000 0x2 0x0 0xbaf6000)
0x3bfb7d28 : 0x667c75 (0xbaf6000 0x2 0x4 0x0)
0x3bfb7da8 : 0x94ee3c (0xbafbe00 0xbae6500 0x1 0x1)
0x3bfb7dc8 : 0x94e886 (0xbae6500 0x1 0x1 0x0)
0x3bfb7e18 : 0x94e3f5 (0xbae6500 0x680118 0x3e91d80 0x10001)
0x3bfb7e48 : 0x412976 (0xbae6500 0xbafbe00 0x1 0x3ecd96)
0x3bfb7ea8 : 0x414219 (0xbafbe00 0xbae6500 0xbb2b1e0 0xbb2b180)
Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOUSBMassStorageClass(2.0.4)@0x34695000->0x3469efff
dependency: com.apple.iokit.IOSCSIArchitectureModelFamily(2.0.5)@0x628000
dependency: com.apple.iokit.IOUSBFamily(3.1.5)@0x659000
dependency: com.apple.iokit.IOStorageFamily(1.5.5)@0x83f000
com.apple.driver.AppleUSBComposite(3.0.0)@0x94d000->0x950fff
dependency: com.apple.iokit.IOUSBFamily(3.1.5)@0x659000
com.apple.iokit.IOUSBFamily(3.1.5)@0x659000->0x680fff
BSD process name corresponding to current thread: kernel_task
Mac OS version:
9G55
Kernel version:
Darwin Kernel Version 9.6.0: Mon Nov 24 17:37:00 PST 2008; root:xnu-1228.9.59~1/RELEASE_I386
System model name: MacBook3,1 (Mac-F22788C8)

Death of a USB device... natural causes or foul play?

I've had a little usb flash drive mp3 player for years. The last time that I mounted it (mount -o umask=0 ...) to replace some songs, the songs were correctly copied but umount hung when I tried to dismount it.
After about 5 minutes I killed umount and checked that the device was unmounted, which it was. After removing the device, I turned it on to check it but it wouldn't proceed past the initial logo screen.
I can no longer mount the device. Here's the dmesg output from multiple attempts:
[ 101.066671] usb 6-2: new full speed USB device number 2 using uhci_hcd
[ 101.515930] usbcore: registered new interface driver uas
[ 101.520972] Initializing USB Mass Storage driver...
[ 101.521079] scsi10 : usb-storage 6-2:1.0
[ 101.521176] usbcore: registered new interface driver usb-storage
[ 101.521182] USB Mass Storage support registered.
[ 102.903338] usb 6-2: reset full speed USB device number 2 using uhci_hcd
[ 103.020004] usb 6-2: device descriptor read/64, error -71
[ 103.240002] usb 6-2: device descriptor read/64, error -71
[ 103.450003] usb 6-2: reset full speed USB device number 2 using uhci_hcd
[ 103.620002] usb 6-2: device descriptor read/64, error -71
[ 103.840000] usb 6-2: device descriptor read/64, error -71
[ 104.050005] usb 6-2: reset full speed USB device number 2 using uhci_hcd
[ 104.463350] usb 6-2: device not accepting address 2, error -71
[ 104.570003] usb 6-2: reset full speed USB device number 2 using uhci_hcd
[ 104.983340] usb 6-2: device not accepting address 2, error -71
[ 104.983365] usb 6-2: USB disconnect, device number 2
[ 105.090003] usb 6-2: new full speed USB device number 3 using uhci_hcd
[ 105.260002] usb 6-2: device descriptor read/64, error -71
[ 105.480006] usb 6-2: device descriptor read/64, error -71
[ 105.690003] usb 6-2: new full speed USB device number 4 using uhci_hcd
[ 105.806673] usb 6-2: device descriptor read/64, error -71
[ 106.080003] usb 6-2: device descriptor read/64, error -71
[ 106.290002] usb 6-2: new full speed USB device number 5 using uhci_hcd
[ 106.703342] usb 6-2: device not accepting address 5, error -71
[ 106.810006] usb 6-2: new full speed USB device number 6 using uhci_hcd
[ 107.223340] usb 6-2: device not accepting address 6, error -71
[ 107.223350] hub 6-0:1.0: unable to enumerate USB device on port 2
[ 847.596593] usb 6-2: new full speed USB device number 7 using uhci_hcd
[ 847.781385] scsi11 : usb-storage 6-2:1.0
[ 869.493259] usb 6-2: reset full speed USB device number 7 using uhci_hcd
[ 879.739928] usb 6-2: reset full speed USB device number 7 using uhci_hcd
[ 895.993259] usb 6-2: reset full speed USB device number 7 using uhci_hcd
[ 896.243260] usb 6-2: reset full speed USB device number 7 using uhci_hcd
[ 906.489922] usb 6-2: reset full speed USB device number 7 using uhci_hcd
[ 906.636310] scsi 11:0:0:0: Device offlined - not ready after error recovery
[ 1240.346582] usb 6-2: USB disconnect, device number 7
[ 1242.973223] usb 6-1: new full speed USB device number 8 using uhci_hcd
[ 1243.141696] scsi12 : usb-storage 6-1:1.0
[ 1265.439888] usb 6-1: reset full speed USB device number 8 using uhci_hcd
[ 1275.693217] usb 6-1: reset full speed USB device number 8 using uhci_hcd
[ 1291.943223] usb 6-1: reset full speed USB device number 8 using uhci_hcd
[ 1292.193219] usb 6-1: reset full speed USB device number 8 using uhci_hcd
[ 1302.439883] usb 6-1: reset full speed USB device number 8 using uhci_hcd
[ 1302.586484] scsi 12:0:0:0: Device offlined - not ready after error recovery
I get the same messages on a different system.
I've tried removing the ehci-hcd module as recommended in the Linux USB FAQ and in several threads concerning similar issues. I've even taken the device apart to see if anything was broken, fried or disconnected, but I didn't notice anything.
Before I give up and accept that it's an irreparable hardware failure, is there anything that I should try?
I should also mention that I swapped some songs recently, so if this was caused by recent kernel changes, then they were probably introduced in 2.6.39.3. I've found the following in the kernel changelog, which may be relevant:
commit b8680d130d565da6eb07567bd6ff20b73f747498
Author: Alan Stern <[email protected]>
Date: Wed Jul 6 17:03:45 2011 -0400
USB: additional regression fix for device removal
commit ca5c485f55d326d9a23e4badd05890148aa53f74 upstream.
Commit e534c5b831c8b8e9f5edee5c8a37753c808b80dc (USB: fix regression
occurring during device removal) didn't go far enough. It failed to
take into account that when a driver claims multiple interfaces, it may
release them all at the same time. As a result, some interfaces can
get released before they are unregistered, and we deadlock trying to
acquire the bandwidth_mutex that we already own.
This patch (asl478) handles this case by setting the "unregistering"
flag on all the interfaces before removing any of them.
Signed-off-by: Alan Stern <[email protected]>
Tested-by: Éric Piel <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
commit 042fe1a2805b175b318db0fa10cf8c9df192fa7c
Author: Alan Stern <[email protected]>
Date: Fri Jul 1 16:43:02 2011 -0400
USB: fix regression occurring during device removal
commit e534c5b831c8b8e9f5edee5c8a37753c808b80dc upstream.
This patch (as1476) fixes a regression introduced by
fccf4e86200b8f5edd9a65da26f150e32ba79808 (USB: Free bandwidth when
usb_disable_device is called). usb_disconnect() grabs the
bandwidth_mutex before calling usb_disable_device(), which calls down
indirectly to usb_set_interface(), which tries to acquire the
bandwidth_mutex.
The fix causes usb_set_interface() to return early when it is called
for an interface that has already been unregistered, which is what
happens in usb_disable_device().
Signed-off-by: Alan Stern <[email protected]>
Tested-by: Sarah Sharp <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
commit 8c603fc5c6608bac3e3df537f8f4a70a24e4edd0
Author: Alan Stern <[email protected]>
Date: Wed Jun 15 16:29:16 2011 -0400
USB: don't let the hub driver prevent system sleep
commit cbb330045e5df8f665ac60227ff898421fc8fb92 upstream.
This patch (as1465) continues implementation of the policy that errors
during suspend or hibernation should not prevent the system from going
to sleep.
In this case, failure to turn on the Suspend feature for a hub port
shouldn't be reported as an error. There are situations where this
does actually occur (such as when the device plugged into that port
was disconnected in the recent past), and it turns out to be harmless.
There's no reason for it to prevent a system sleep.
Also, don't allow the hub driver to fail a system suspend if the
downstream ports aren't all suspended. This is also harmless (and
should never happen, given the change mentioned above); printing a
warning message in the kernel log is all we really need to do.
Signed-off-by: Alan Stern <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
commit c4c3048b2bda6562bcdf5507bb9c6c248a87f675
Author: Alan Stern <[email protected]>
Date: Wed Jun 15 16:27:43 2011 -0400
USB: don't let errors prevent system sleep
commit 0af212ba8f123c2eba151af7726c34a50b127962 upstream.
This patch (as1464) implements the recommended policy that most errors
during suspend or hibernation should not prevent the system from going
to sleep. In particular, failure to suspend a USB driver or a USB
device should not prevent the sleep from succeeding:
Failure to suspend a device won't matter, because the device will
automatically go into suspend mode when the USB bus stops carrying
packets. (This might be less true for USB-3.0 devices, but let's not
worry about them now.)
Failure of a driver to suspend might lead to trouble later on when the
system wakes up, but it isn't sufficient reason to prevent the system
from going to sleep.
Signed-off-by: Alan Stern <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
commit a96e5158f0cab04b29e9236f04214c056efe3a04
Author: Sarah Sharp <[email protected]>
Date: Sun Jun 5 23:22:22 2011 -0700
USB: Free bandwidth when usb_disable_device is called.
commit fccf4e86200b8f5edd9a65da26f150e32ba79808 upstream.
Tanya ran into an issue when trying to switch a UAS device from the BOT
configuration to the UAS configuration via the bConfigurationValue sysfs
file. Before installing the UAS configuration, set_bConfigurationValue()
calls usb_disable_device(). That function is supposed to remove all host
controller resources associated with that device, but it leaves some state
in the xHCI host controller.
Commit 0791971ba8fbc44e4f476079f856335ed45e6324
usb: allow drivers to use allocated bandwidth until unbound
added a call to usb_disable_device() in usb_set_configuration(), before
the xHCI bandwidth functions were invoked. That commit fixed a bug, but
also introduced a bug that is triggered when a configured device is
switched to a new configuration.
usb_disable_device() goes through all the motions of unbinding the drivers
attached to active interfaces and removing the USB core structures
associated with those interfaces, but it doesn't actually remove the
endpoints from the internal xHCI host controller bandwidth structures.
When usb_disable_device() calls usb_disable_endpoint() with reset_hardware
set to true, the entries in udev->ep_out and udev->ep_in will be set to
NULL. Usually, when the USB core installs a new configuration,
usb_hcd_alloc_bandwidth() will drop all non-NULL endpoints in udev->ep_out
and udev->ep_in before adding any new endpoints. However, when the new
UAS configuration was added, all those entries were null, so none of the
old endpoints in the BOT configuration were dropped.
The xHCI driver blindly added the UAS configuration endpoints, and some of
the endpoint addresses overlapped with the old BOT configuration
endpoints. This caused the xHCI host to reject the Configure Endpoint
command. Now that the xHCI driver code is cleaned up to reject a
double-add of active endpoints, we need to fix the USB core to properly
drop old endpoints in usb_disable_device().
If the host controller driver needs bandwidth checking support, make
usb_disable_device() call usb_disable_endpoint() with
reset_hardware set to false, drop the endpoints from the xHCI host
controller, and then call usb_disable_endpoint() again with
reset_hardware set to true.
The first call to usb_disable_endpoint() will cancel any pending URBs and
wait on them to be freed in usb_hcd_disable_endpoint(), but will keep the
pointers in udev->ep_out and udev->ep in intact. Then
usb_hcd_alloc_bandwidth() will use those pointers to know which endpoints
to drop.
The final call to usb_disable_endpoint() will do two things:
1. It will call usb_hcd_disable_endpoint() again, which should be harmless
since the ep->urb_list should be empty after the first call to
usb_disable_endpoint() returns.
2. It will set the entries in udev->ep_out and udev->ep in to NULL, and call
usb_hcd_disable_endpoint(). That call will have no effect, since the xHCI
driver doesn't set the endpoint_disable function pointer.
Note that usb_disable_device() will now need to be called with
hcd->bandwidth_mutex held.
This should be backported to kernels as old as 2.6.32.
Signed-off-by: Sarah Sharp <[email protected]>
Reported-by: Tanya Brokhman <[email protected]>
Cc: [email protected]
Cc: Alan Stern <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Does anyone know if any of those changes could kill a USB flash drive?
Linux fun fact #3487: if you remove the uhci-hcd module, your usb keyboard and mouse stop working (luckily I still have an old non-usb keyboard)
Last edited by Xyne (2011-07-22 11:49:37)

I had a while ago similar problem with USB memory stick. At the end, I don't know why, just formatting it using WinXP helped me.
S-
Last edited by StenM (2011-07-22 17:56:32)

IPhone causes problems on other USB devices?

Is anyone having problems with external USB hard drives or any other USB peripheral when his iPhone is connected to a Windows PC or sometime after that?
I'm having some problems with external USB hard drives when the Windows system is continuously hammering them for more than a half-hour. The problem is not easily reproducable, and I don't know the cause.
It probably has nothing to do with the iPhone. But one possibility I have to consider is that the iPhone draws enough current (or something else I haven't thought of) that interefers with the USB communications.

What I meant in my previous post was that the USB wouldn't allow the iPhone to draw more current than the USB can safely provide, unless it was defective. I have an external hardrive, a wireless mouse, my printer and my iPhone connected directly to my laptop's USB ports and have not seen any problems with any of them. In several years of using USB devices, I've not seen any problems that I could assign to the USB ports/controllers... they just seem to work all the time. Will be interested as to your findings.

Connecting Nano to PC causes other USB devices to unconnect

Connecting Nano to PC causes other USB devices to unconnect from USB2 ports. USB2 are on a pci card. Is there anything I can do to stop this from happening?
Thanks,
RON C

Hi
I have Satellite M70-159 and I didnt notice any strange problem with USB ports. I use a few of them like printer, webcam, USB memory stick, optical mouse and external HDD. The devices are recognized properly and I remove them always without safe remove option.
Now I have Vista preinstalled and till now there is no problem. If I understood you right USB ports are working well but there is problem with USB modem only. Am I right?
Try also to contact modem producer support. Maybe is issue like this known and hopefully they have some logical explanation.

[SOLVED] Intel NUC using second dvb-t device causes usb lockup

I have an intel NUC D54250WYK running latest non-testing arch.
linux minikat 3.17.3-1-ARCH #1 SMP PREEMPT Fri Nov 14 23:13:48 CET 2014 x86_64 GNU/Linux
I have two PCTV 290e cards.
Bus 001 Device 002: ID 8087:8000 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 009: ID 2013:024f PCTV Systems nanoStick T2 290e
Bus 002 Device 008: ID 2013:024f PCTV Systems nanoStick T2 290e
Bus 002 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 002 Device 007: ID 0461:4d15 Primax Electronics, Ltd Dell Optical Mouse
Bus 002 Device 010: ID 413c:2003 Dell Computer Corp. Keyboard
Bus 002 Device 006: ID 0557:7000 ATEN International Co., Ltd Hub
Bus 002 Device 005: ID 9e88:9e8f
Bus 002 Device 004: ID 1e4e:0110 Cubeternet
Bus 002 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Both of these work fine running alone (ie using just /dev/dvb/adapter0 or adapter1). However, when I run both together all my usb devices seem to disappear. Using the power button I can shut the system down. In the logs I see this
Nov 17 22:42:44 minikat kernel: tda18271: performing RF tracking filter calibration
Nov 17 22:42:46 minikat kernel: tda18271: RF tracking filter calibration complete
Nov 17 22:42:51 minikat kernel: xhci_hcd 0000:00:14.0: xHCI host not responding to stop endpoint command.
Nov 17 22:42:51 minikat kernel: xhci_hcd 0000:00:14.0: Assuming host is dying, halting host.
Nov 17 22:42:51 minikat kernel: xhci_hcd 0000:00:14.0: HC died; cleaning up
Nov 17 22:42:51 minikat kernel: usb 1-3: USB disconnect, device number 2
Nov 17 22:42:51 minikat kernel: usb 1-3.1: USB disconnect, device number 4
Nov 17 22:42:51 minikat kernel: em28174 #1: writing to i2c device at 0xd8 failed (error=-5)
Nov 17 22:42:51 minikat kernel: i2c i2c-11: cxd2820r: i2c rd failed=-5 reg=db len=1
Nov 17 22:42:51 minikat kernel: em28174 #1: writing to i2c device at 0xc0 failed (error=-19)
Nov 17 22:42:51 minikat kernel: em28174 #1: writing to i2c device at 0xd8 failed (error=-19)
Nov 17 22:42:51 minikat kernel: i2c i2c-11: cxd2820r: i2c rd failed=-19 reg=db len=1
Nov 17 22:42:51 minikat kernel: __tda18271_write_regs: [11-0060|M] ERROR: idx = 0x5, len = 1, i2c_transfer returned: -19
Nov 17 22:42:51 minikat kernel: tda18271_set_params: [11-0060|M] error -19 on line 985
Nov 17 22:42:51 minikat kernel: em28174 #1: writing to i2c device at 0xd8 failed (error=-19)
searching reveals a similar problem here https://bugs.launchpad.net/ubuntu/+sour … ug/1306712.
It doesn't seem to matter which device is used second or which application is using them; ie 2 x vlc or vlc + tzap etc etc all seem to cause the problem.
I used the same devices on my old acer revo 3610 and they work fine together there.
I would like to report this to Intel if I can get the right information together. Is there something I can do to clarify the problem?
Edit: added relevant device stuff from the same boot
Nov 17 22:40:35 minikat kernel: em28xx: New device PCTV Systems PCTV 290e @ 480 Mbps (2013:024f, interface 0, class 0)
Nov 17 22:40:35 minikat kernel: em28xx: DVB interface 0 found: isoc
Nov 17 22:40:35 minikat kernel: em28xx: chip ID is em28174
Nov 17 22:40:36 minikat kernel: em28174 #0: EEPROM ID = 26 00 01 00, EEPROM hash = 0x924125c8
Nov 17 22:40:36 minikat kernel: em28174 #0: EEPROM info:
Nov 17 22:40:36 minikat kernel: em28174 #0: microcode start address = 0x0004, boot configuration = 0x01
Nov 17 22:40:36 minikat kernel: em28174 #0: No audio on board.
Nov 17 22:40:36 minikat kernel: em28174 #0: 500mA max power
Nov 17 22:40:36 minikat kernel: em28174 #0: Table at offset 0x39, strings=0x1aa0, 0x14ba, 0x1ace
Nov 17 22:40:36 minikat kernel: em28174 #0: Identified as PCTV nanoStick T2 290e (card=78)
Nov 17 22:40:36 minikat kernel: em28174 #0: dvb set to isoc mode.
Nov 17 22:40:36 minikat kernel: em28xx: New device PCTV Systems PCTV 290e @ 480 Mbps (2013:024f, interface 0, class 0)
Nov 17 22:40:36 minikat kernel: em28xx: DVB interface 0 found: isoc
Nov 17 22:40:36 minikat kernel: em28xx: chip ID is em28174
Nov 17 22:40:36 minikat kernel: em28174 #1: EEPROM ID = 26 00 01 00, EEPROM hash = 0x9de637c6
Nov 17 22:40:36 minikat kernel: em28174 #1: EEPROM info:
Nov 17 22:40:36 minikat kernel: em28174 #1: microcode start address = 0x0004, boot configuration = 0x01
Nov 17 22:40:36 minikat kernel: em28174 #1: No audio on board.
Nov 17 22:40:36 minikat kernel: em28174 #1: 500mA max power
Nov 17 22:40:36 minikat kernel: em28174 #1: Table at offset 0x39, strings=0x1aa0, 0x14ba, 0x1ace
Nov 17 22:40:36 minikat kernel: em28174 #1: Identified as PCTV nanoStick T2 290e (card=78)
Nov 17 22:40:36 minikat kernel: em28174 #1: dvb set to isoc mode.
Nov 17 22:40:36 minikat kernel: usbcore: registered new interface driver em28xx
Nov 17 22:40:36 minikat kernel: em28174 #0: Binding DVB extension
Nov 17 22:40:36 minikat kernel: DVB: registering new adapter (em28174 #0)
Nov 17 22:40:36 minikat kernel: em28174 #0: DVB extension successfully initialized
Nov 17 22:40:36 minikat kernel: em28174 #1: Binding DVB extension
Nov 17 22:40:36 minikat kernel: DVB: registering new adapter (em28174 #1)
Nov 17 22:40:36 minikat kernel: em28174 #1: DVB extension successfully initialized
Nov 17 22:40:36 minikat kernel: em28xx: Registered (Em28xx dvb Extension) extension
Nov 17 22:40:36 minikat kernel: em28174 #0: Registering input extension
Nov 17 22:40:36 minikat kernel: input: em28xx IR (em28174 #0) as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.1/rc/rc1/input14
Nov 17 22:40:36 minikat kernel: rc1: em28xx IR (em28174 #0) as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.1/rc/rc1
Nov 17 22:40:36 minikat kernel: em28174 #0: Input extension successfully initalized
Nov 17 22:40:36 minikat kernel: em28174 #1: Registering input extension
Nov 17 22:40:36 minikat kernel: input: em28xx IR (em28174 #1) as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.2/rc/rc2/input15
Nov 17 22:40:36 minikat kernel: rc2: em28xx IR (em28174 #1) as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.2/rc/rc2
Nov 17 22:40:36 minikat kernel: em28174 #1: Input extension successfully initalized
Nov 17 22:40:36 minikat kernel: em28xx: Registered (Em28xx Input Extension) extension
I think the above indicates the devices are separately recognized.
Last edited by replabrobin (2015-01-25 19:12:37)

I'm having a similar problem with the WinTV HVR 950Q on my i7 laptop. Any time something (tvtime, ffplay, etc) tries to read from the device, USB dies with the same "Assuming host is dying" message in dmesg. Fortunately my laptop keyboard & touchpad aren't connected via usb, so I'm not forced to power cycle, but I'ld like to figure out the problem so I can use the device.
Currently I'm thinking there is a problem with the xhci driver module, but I'm still working on tracking it down. Let me know if you figure this out.
Update:
Just confirmed that at least in my case this is an issue with xhci. I compiled a kernel with no xhci support and booted to it (since blacklisting xhci_hcd doesn't seem to work), now the capture device seems to work properly. Unfortunately this means I can have USB3, or the capture device, but not both (for now).
There is a "quirks" parameter that can be passed to the xhci_hcd module. It seems to be a bitmask AFAICT, but I haven't been able to find any documentation as to what it does yet. Maybe there's something in there that can help here.
Last edited by mcgrew (2014-11-18 20:43:48)

Does Mac format cause USB device not recongized ?

Hi, I have beengiven a 2nd hand Ipod.
When i try to connect to any windows PC I get "USB device not recongized ".
When I look at the setting, there is nothing to say it is windows formatted, S/n and Mdel are the last things displayed.
If its MAC formatted would that cause my error message.
If so how to I reformatto windows files systems if I don't have a MAC and my PCs don't recognize the Ipod ?
I've trie placing the ipod in 'disk mode' but the PC don't recongze it either ( I'm using the same USB port as my windows formatted Ipod nano and the same cable. Is the Ipod toast ?

Well, you need to check if iTunes recognizes the iPod. If it does then great. You just need to click the restore button, and then just sync it to your computer. This will format it so you can use it on Windows.
If not, there might be some problem with the iPod. Go to your nearest Apple Store and get them to check it for you, or the Apple Technical Support Hotline (1-800-APL-CARE)
Hope I helped,
Danny

USB Device Not Recognized - Caused by iTunes Update???

I have been reviewing the posts associated with USB Device Not Recognized and many persons have had this problem, but most are within the past 10-12 days. My problem started after installing an iTunes update.
Can Apple please advise if the latest iTunes update interacts with Windows to cause this problem (which remains even after iTunes is uninstalled).

Check if any of the tips in this thread can help you.
http://talk.sonymobile.com/message/328564#328564
- Community Manager Sony Xperia Support Forum
If you're new to our forums make sure that you have read our Discussion guidelines.
If you want to get in touch with the local support team for your country please visit our contact page.

Ejecting iPod causes other USB devices to be ejected at the same time.

When ejecting an iPod Nano 4g from iTunes under Windows Vista, all other USB devices attached to the computer are also ejected at the same time (external hard drives, thumb drives, scanners, etc.). Is there a way to prevent this from happening?

Express is slow ethernet.. 10/100 only. The max speed of any connection to a USB hard disk is limited severely by the 100mbit..
USB is always slow btw.. This is actually a poor way to share a drive. A cheap NAS.. ie ethernet to Sata directly is far far superior and a single disk NAS can be had cheaply.. you will never get close with USB in network situations.
If you use a hub though, you can plug multiple disks into an Extreme.. I guess the network speed is at least no worse than the USB hub -- ethernet devices which are lousy as a whole.
Never forget you have the fastest ethernet adapters and fastest possible connectors already on computers on the network.. people are so utterly mesmerized by NAS they forget.. a FW800 or better USB3 if you have a newer computer shared to the network from a computer has much higher throughput and is much cheaper than even the very low end network stand alone boxes.

The USB device Apple Internal Keyboard / Trackpad

Hello,
in the console of my rMBP 13 mid 2014 I have a lot of messages of this type:
The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (1)
can please somebody give me some information what this message mean?
Thanks

There are 3 checks that can be performed initially:
- perform a NVRAM reset : About NVRAM and PRAM
- perform a SMC reset: Intel-based Macs: Resetting the System Management Controller (SMC)
- perform a Safe Boot : OS X: What is Safe Boot, Safe Mode?
- then reboot to normal
If the issue persists: run Diagnostics. Using Apple Diagnostics
and check if any codes come up : Apple Diagnostics: Reference codes
Cheers

I have pluged a portable battery to the USB and my macbook pro stopped working after that, right before it shut down there was a message on the screen that said something like " USB device is withdrawing so much power, please disconnect and connect again?

I have plugged a portable battery to the USB and my macbook pro stopped working after that, right before it shut down there was a message on the screen that said something like " USB device is withdrawing so much power, please disconnect and connect again?
if the device I connected have caused this, shouldn't the macbook itself have some type of protection that should prevent this from happening.
because when I took it to an apple certified maintenance shop, the guy said that now it could only run while connected to the power. it won't run on batteries. and that I have to change the motherboard.
can I just replace the damaged part only, would apple consider this as a design issue and they could pay for it, or should I just buy a new motherboard for 800$.
Help.

BB1B2,
The problem is in finding a tech shop that will/can do board level repairs on Macs. They are few. And I certainly wouldn't spend $800 on a new logic board - I would replace the computer if I had to pay that much!
You could call around to a few repair shops and see if they feel competent to isolate the problem and do a board level repair - but I'm afraid, in the end, that your search will be futile.
Sorry,
Clinton

I have a 3rd generation ipod that will not connect. I keep getting an error message that says "USB Device Not Recognized". I have tried 3 seperate cables and none of them are working. Please help!

It keeps telling me that one of the USB devices for this computer has malfunctioned and windows does not recognize it. I have tried all of the ports and still am not having any luck. I have purchased 3 brand new cables and none of them are working. I have tried to update the driver but it says I am using the most up to date. I have tried to reset the Ipod by holding the center button and menu button until the apple appears. I am not sure what else to try. Any help would be greatly appreciated. My computer is Windows Vista!

Hello butterflygirlie,
Have you tried uninstalling the driver for your iPod from within Device Manager? After uninstalling it, go ahead and unplug your iPod and plug it back in. Doing so should cause your system to locate the proper driver for it.
B-rock

USB device keeps disconnecting/connecting after upgrading to Windows 8.1

I have a device(Pedal for Sim Racing) connected via USB, everything is working fine in Windows 7 and 8 but after upgrading my machine to Windows 8.1 the device keeps disconnecting and connecting for like every 2 seconds. But after I open the Property Sheet
in Game Controllers panel the disconnection issue was gone, if I reconnect the device the issue persist. Other people who have similar device also encounters the same issue after upgrading to windows 8.1. The issue persist with or without the device driver
installed.
Any idea, what might cause this?
Best regards
mark

I'v got this exact same problem with my Win 7 desktop. I've also got pedals and wheel but don't see it as different than all the other USB devices. I'm using a bunch of USB, but no hubs, including 3 external storage hard drives. But the momentary
disconnect appears in all devices as best as i can see..even my long time trouble free head phones..keyboard..and all. Sometimes the sound goes away and if I unplug and replug them the sound comes back, and other times I have to exit and re enter the
game. I also get video crashes ..maybe not related.IDK..and have to restart all, because I've got three black screens in Eyefinity. For years my system was trouble free and its just slowly started getting worse. I've thought it had to do with system "sleep"
etc but long ago went to never sleep max performance etc..Makes no difference. Keep thinking its my hardware or my house wiring etc..But can't seem to solve it. I replaced my Mobo/chip/ram maybe 6 months ago and that appears to have not helped. It seems
to be getting worse. I hate to start replacing parts piece by piece..cost a lot of money and sometimes doesn't help.
When I'm playing a game I can often hear "faint" sound of USB connect disconnect happening with regularity..that little bing/boink sound etc..So it must just be constantly happening...Seems weird. Didn't have anything like this happening years
ago with pretty much the same hardware and same Win7 with the continuing updates etc.
What can be causing this common problem?

USB Device Not Recognized issues

I have a Qosmio X505-Q860 and I've been getting the 'USB Device Not Recognized' error constantly for several months. I've never plugged anything into any of my USBs and the error is now causing a nice Blue Screen (which happened about 4 times yesterday within 1 hour). I've tried uninstalling the problem USB hub but it keeps telling me that it failed to uninstall (I'm on my administrator account when doing this). How in the world do I get rid of this so my computer stops crashing and driving me crazy!?
Edit: I should also mention that everything is up to date (I check often and checked just now).
"A stopped clock is still right twice a day."

I suggest trying another USB cable. If you are positive that your cable is not the issue then try resetting the iPod and booting into disk mode (Hold menu+select down until Apple logo appears. Then hold menu+play/pause down and the iPod will go into disk mode, see if the computer recognizes it then. If that works then their is either a software issue on the computer or a firmware issue. Worth trying to restore but backup all your iPod's files first!

USB devices causing G5 meltdown

Similar Messages

Maybe you are looking for