Re: xhci_hcd Warn: Stalled Endpoint with USB 3.0 to esata connection

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Please don't top-post.

On Mon, 27 Jun 2011, M. Steven Ginn wrote:

> the tower can hold 5 drives but at present I only have 4 installed.  

Okay, that explains part of the problem.  The system should realize 
there are only four drives, but for some reason it doesn't.

> At the end of the log.txt file I sent, it shows the drives being
> properly discovered and remounted after I plugged the esata cable
> back into the esata port.
> 
> do you want me to follow the instructions in usbmon.txt and post the
> file to the list?

Yes, please.

>  Should I just plug in the Addonics adapter without
> the drives connected or with the raid tower connected as before?

With the read tower connected as before.

Alan Stern

> 
> thanks,
> 
> Steve
> sginn@xxxxxxx
> 
> 
> 
> 
> On Jun 27, 2011, at 9:56 AM, Alan Stern wrote:
> 
> > On Fri, 24 Jun 2011, M. Steven Ginn wrote:
> > 
> >> ok I rebooted and here is an excerpt of my syslog showing the system trying to setup my four drives via the USB 3.0 to esata device:
> > 
> > Skipping a lot of stuff...
> > 
> >> Jun 24 10:53:20 xbmcS64 kernel: [42038.326010] scsi 7:0:0:0: Direct-Access     WDC WD20 EARS-00MVWB0          PQ: 0 ANSI: 2 CCS
> >> Jun 24 10:53:20 xbmcS64 kernel: [42038.326365] scsi 7:0:0:1: Direct-Access     ST315003 41AS                  PQ: 0 ANSI: 2 CCS
> >> Jun 24 10:53:20 xbmcS64 kernel: [42038.326764] scsi 7:0:0:2: Direct-Access     ST315003 41AS                  PQ: 0 ANSI: 2 CCS
> >> Jun 24 10:53:20 xbmcS64 kernel: [42038.327091] scsi 7:0:0:3: Direct-Access     Hitachi  HDS5C3020ALA632       PQ: 0 ANSI: 2 CCS
> >> Jun 24 10:53:20 xbmcS64 kernel: [42038.327401] scsi 7:0:0:4: Direct-Access     0  As    R   > n '(8\S0        PQ: 0 ANSI: 2 CCS
> > 
> > This certainly looks suspicious.  It appears that the drive has four 
> > internal disks but for some reason the computer thinks it has five.
> > 
> >> Jun 24 10:53:20 xbmcS64 kernel: [42038.328361] sd 7:0:0:0: [sdg] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
> >> Jun 24 10:53:20 xbmcS64 kernel: [42038.330817] sd 7:0:0:1: [sdh] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)
> >> Jun 24 10:53:20 xbmcS64 kernel: [42038.334959] sd 7:0:0:2: [sdi] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)
> >> Jun 24 10:53:20 xbmcS64 kernel: [42038.335308] sd 7:0:0:4: [sdk] Very big device. Trying to use READ CAPACITY(16).
> >> Jun 24 10:53:20 xbmcS64 kernel: [42038.335487] sd 7:0:0:3: [sdj] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
> >> Jun 24 10:53:20 xbmcS64 kernel: [42038.337206] sd 7:0:0:4: [sdk] 281474976710656 512-byte logical blocks: (144 PB/128 PiB)
> > 
> > The last one (sdk) obviously is garbage.  No wonder it doesn't work 
> > right.
> > 
> > Instead of working on xhci-hcd debugging, I suggest using usbmon.  See 
> > the instructions in the kernel source file 
> > Documentation/usb/usbmon.txt.
> > 
> > Alan Stern
> > 

--
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


[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux