On Fri, Oct 26, 2012 at 04:06:01PM -0400, covici@xxxxxxxxxxxxxx wrote: > Sarah Sharp <sarah.a.sharp@xxxxxxxxxxxxxxx> wrote: > > > On Fri, Oct 26, 2012 at 06:35:57AM -0400, covici@xxxxxxxxxxxxxx wrote: > > > Sarah Sharp <sarah.a.sharp@xxxxxxxxxxxxxxx> wrote: > > > > git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > > > > > > Well, with that kernel, it didn't repeat the messages indefinitely, so I > > > could save them and I also have the messages from the log when I > > > unplugged the enclosure and replugged. > > > > > > Here is the output: > > > > > > usb 4-2: Device not responding to set address. > > > usb 4-2: Device not responding to set address. > > > usb 4-2: device not accepting address 6, error -71 > > > hub 4-0:1.0: unable to enumerate USB device on port 2 > > > > Ok, so you were having issues with the Set Address command. > > > > > and when I unplugged and plugged back in I got: > > > Oct 26 05:54:34 ccs kernel: usb 4-2: device not accepting address 68, error -62 > > > Oct 26 05:54:34 ccs kernel: xhci_hcd 0000:04:00.0: Error while assigning device slot ID > > > Oct 26 05:54:34 ccs kernel: hub 4-0:1.0: couldn't allocate port 2 usb_device > > > Oct 26 05:54:34 ccs kernel: xhci_hcd 0000:04:00.0: Bad Slot ID 1 > > > Oct 26 05:54:34 ccs kernel: xhci_hcd 0000:04:00.0: Could not allocate xHCI USB device data structures > > > Oct 26 05:54:34 ccs kernel: hub 4-0:1.0: couldn't allocate port 2 usb_device > > > > Those error messages are unexpected. Can you recompile that kernel with > > CONFIG_USB_XHCI_HCD_DEBUGGING turned on, and post the full dmesg from > > when you boot with the device plugged in, and then unplug and replug it? > > I need the full dmesg, not just snippets. > > > > > But if I don't boot with the enclosure plugged in, when the system comes > > > up I can plug in and get a drive. > > > > Well, that's good. Let's try to figure out what's wrong with the case > > of booting with the drive connected. > > OK, I will try to compile the kernel as suggested, however a lot of > other messages are missing from the kernel log -- like all the messages > nornally seen such as > Oct 26 06:01:49 ccs kernel: ACPI: bus type pnp registered > > When I was using the 3.7 kernel, none of those messages were seen, I > wonder if they disabled something? First, do you see those messages if you look in /var/log/kern.log (assuming that file exists on your distro)? If so, you may need to run `sudo dmesg -n 8` in order to see the messages in dmesg. Another thing to check is if the default log level changed. What is CONFIG_DEFAULT_MESSAGE_LOGLEVEL set to? Do you have CONFIG_DEBUG_KERNEL turned on? For xHCI debugging, make sure you also have CONFIG_USB_DEBUG turned on as well as CONFIG_USB_XHCI_HCD_DEBUGGING and CONFIG_DEBUG_KERNEL. Sarah Sharp -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
