Unsuccessful transactions during usb enumeration

Unsuccessful transactions during usb enumeration

[Ranjith T. C.]

Hi,

I am using a device with Marvel USB controller in device mode.
During the enumeration, I am getting so many unsuccessful transactions in my USB packet sniffer.
A screenshot of the issue is attached herewith.
Can anyone please tell me the possible reason  for this?

Any help in this regard is much appreciated.
Please copy me in the further communications.

Regards,
Ranjith
________________________________

Confidentiality Statement / Disclaimer : This message and any attachments is intended for the sole use of the intended recipient. It may contain confidential information. Any unauthorized use, dissemination or modification is strictly prohibited. If you are not the intended recipient, please notify the sender immediately then delete it from all your systems, and do not copy, use or print. Internet communications are not secure and it is the responsibility of the recipient to make sure that it is virus/malicious code exempt.

The company/sender cannot be responsible for any unauthorized alterations or modifications made to the contents. If you require any form of confirmation of the contents, please contact the company/sender. The company/sender is not liable for any errors or omissions in the content of this message.

________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140617/8631c24e/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: usb_transaction.jpg
Type: image/jpeg
Size: 381471 bytes
Desc: usb_transaction.jpg
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140617/8631c24e/attachment-0001.jpg 

Unsuccessful transactions during usb enumeration

[Ranjith T. C.]

Hi,

I am using a device with Marvel USB controller in device mode with Linux 2.6.22 running on it.
During the enumeration, I am getting so many unsuccessful  transactions in my USB packet sniffer.
Can anyone please tell me the possible reason  for this?

Any help in this regard is much appreciated.
Please copy me in the further communications.

Regards,
Ranjith
________________________________

Confidentiality Statement / Disclaimer : This message and any attachments is intended for the sole use of the intended recipient. It may contain confidential information. Any unauthorized use, dissemination or modification is strictly prohibited. If you are not the intended recipient, please notify the sender immediately then delete it from all your systems, and do not copy, use or print. Internet communications are not secure and it is the responsibility of the recipient to make sure that it is virus/malicious code exempt.

The company/sender cannot be responsible for any unauthorized alterations or modifications made to the contents. If you require any form of confirmation of the contents, please contact the company/sender. The company/sender is not liable for any errors or omissions in the content of this message.

________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140618/72e988e6/attachment.html 

Unsuccessful transactions during usb enumeration

[Greg KH]

On Wed, Jun 18, 2014 at 05:27:35AM +0000, Ranjith T. C. wrote:
> Hi,
> 
>  
> 
> I am using a device with Marvel USB controller in device mode with Linux 2.6.22
> running on it.

You do realize just how old and obsolete that kernel version is, right?
You are pretty much on your own here, unless you can get support for the
company that is forcing you to stay on that kernel version.

> During the enumeration, I am getting so many unsuccessful  transactions in my
> USB packet sniffer.

What exactly do you mean by this?

> Can anyone please tell me the possible reason  for this?

Your device is broken?  :)

Unsuccessful transactions during usb enumeration

[Ranjith T. C.]

Thanks for the reply.

> What exactly do you mean by this?

What I meant is whether it could be could be an of the USB controller driver or the hardware?

I am attaching a screen shot of the sniffer.


Regards,
Ranjith

-----Original Message-----
From: Greg KH [mailto:greg at kroah.com]
Sent: Wednesday, June 18, 2014 11:10 AM
To: Ranjith T. C.
Cc: kernelnewbies at kernelnewbies.org
Subject: Re: Unsuccessful transactions during usb enumeration

On Wed, Jun 18, 2014 at 05:27:35AM +0000, Ranjith T. C. wrote:
> Hi,
>
>
>
> I am using a device with Marvel USB controller in device mode with Linux 2.6.22
> running on it.

You do realize just how old and obsolete that kernel version is, right?
You are pretty much on your own here, unless you can get support for the
company that is forcing you to stay on that kernel version.

> During the enumeration, I am getting so many unsuccessful  transactions in my
> USB packet sniffer.

What exactly do you mean by this?

> Can anyone please tell me the possible reason  for this?

Your device is broken?  :)

________________________________

Confidentiality Statement / Disclaimer : This message and any attachments is intended for the sole use of the intended recipient. It may contain confidential information. Any unauthorized use, dissemination or modification is strictly prohibited. If you are not the intended recipient, please notify the sender immediately then delete it from all your systems, and do not copy, use or print. Internet communications are not secure and it is the responsibility of the recipient to make sure that it is virus/malicious code exempt.

The company/sender cannot be responsible for any unauthorized alterations or modifications made to the contents. If you require any form of confirmation of the contents, please contact the company/sender. The company/sender is not liable for any errors or omissions in the content of this message.

________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: usb.jpg
Type: image/jpeg
Size: 214993 bytes
Desc: usb.jpg
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140618/533cabbb/attachment-0001.jpg 

Unsuccessful transactions during usb enumeration

[Greg KH]

On Wed, Jun 18, 2014 at 06:26:23AM +0000, Ranjith T. C. wrote:
> Thanks for the reply.
> 
> > What exactly do you mean by this?
> 
> What I meant is whether it could be could be an of the USB controller driver or the hardware?

It could be both.  Or a bad cable, or bad connection.

Try putting some debugging code in the Linux device side and see what
that is telling you is happening.

Try plugging the device into different operating systems with different
types of host controller hardware to see if it is a timing issue.

Good luck,

greg k-h

Unsuccessful transactions during usb enumeration

[sanjeev sharma]

Hi Greg,

In one of my imx6 based Board when I connect USB Disk first time everything
work's ok and I can read/write content from USB Flash Driver but when I do
eject and connect again I could see below continuous messages from dmesg
and disk never mounted.

 218.431346] FAT-fs (sda): Directory bread(block 480) failed

<3>[  218.431362] FAT-fs (sda): Directory bread(block 481) failed

<3>[  218.431374] FAT-fs (sda): Directory bread(block 482) failed

<3>[  218.431386] FAT-fs (sda): Directory bread(block 483) failed

<3>[  218.431398] FAT-fs (sda): Directory bread(block 484) failed

<3>[  218.431420] FAT-fs (sda): Directory bread(block 485) failed

<3>[  218.431432] FAT-fs (sda): Directory bread(block 486) failed

<3>[  218.431444] FAT-fs (sda): Directory bread(block 487) failed

<3>[  218.431466] FAT-fs (sda): Directory bread(block 488) failed

<3>[  218.431478] FAT-fs (sda): Directory bread(block 489) failed

<3>[  218.431499] FAT-fs (sda): Directory bread(block 490) failed

<3>[  218.431515] FAT-fs (sda): Directory bread(block 491) failed

<3>[  218.431528] FAT-fs (sda): Directory bread(block 492) failed

<3>[  218.431540] FAT-fs (sda): Directory bread(block 493) failed

<3>[  218.431551] FAT-fs (sda): Directory bread(block 494) failed

<3>[  218.431563] FAT-fs (sda): Directory bread(block 495) failed

<3>[  218.431592] FAT-fs (sda): Directory bread(block 496) failed

<3>[  218.431604] FAT-fs (sda): Directory bread(block 497) failed

<3>[  218.431616] FAT-fs (sda): Directory bread(block 498) failed

<3>[  218.431627] FAT-fs (sda): Directory bread(block 499)

is this probably issue in driver where It is failing to properly re-init
the USB device 2nd time ?

Regards
Sanjeev Sharma


On Wed, Jun 18, 2014 at 12:09 PM, Greg KH <greg@kroah.com> wrote:

> On Wed, Jun 18, 2014 at 06:26:23AM +0000, Ranjith T. C. wrote:
> > Thanks for the reply.
> >
> > > What exactly do you mean by this?
> >
> > What I meant is whether it could be could be an of the USB controller
> driver or the hardware?
>
> It could be both.  Or a bad cable, or bad connection.
>
> Try putting some debugging code in the Linux device side and see what
> that is telling you is happening.
>
> Try plugging the device into different operating systems with different
> types of host controller hardware to see if it is a timing issue.
>
> Good luck,
>
> greg k-h
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140618/e23c3979/attachment.html 

Unsuccessful transactions during usb enumeration

[Greg KH]

On Wed, Jun 18, 2014 at 12:22:33PM +0530, sanjeev sharma wrote:
> Hi Greg,
> 
> In one of my imx6 based Board when I connect USB Disk first time everything
> work's ok and I can read/write content from USB Flash Driver but when I do
> eject and connect again I could see below continuous messages from dmesg
> and disk never mounted.
> 
>  218.431346] FAT-fs (sda): Directory bread(block 480) failed
> 
> <3>[  218.431362] FAT-fs (sda): Directory bread(block 481) failed
> 
> <3>[  218.431374] FAT-fs (sda): Directory bread(block 482) failed
> 
> <3>[  218.431386] FAT-fs (sda): Directory bread(block 483) failed
> 
> <3>[  218.431398] FAT-fs (sda): Directory bread(block 484) failed
> 
> <3>[  218.431420] FAT-fs (sda): Directory bread(block 485) failed
> 
> <3>[  218.431432] FAT-fs (sda): Directory bread(block 486) failed
> 
> <3>[  218.431444] FAT-fs (sda): Directory bread(block 487) failed
> 
> <3>[  218.431466] FAT-fs (sda): Directory bread(block 488) failed
> 
> <3>[  218.431478] FAT-fs (sda): Directory bread(block 489) failed
> 
> <3>[  218.431499] FAT-fs (sda): Directory bread(block 490) failed
> 
> <3>[  218.431515] FAT-fs (sda): Directory bread(block 491) failed
> 
> <3>[  218.431528] FAT-fs (sda): Directory bread(block 492) failed
> 
> <3>[  218.431540] FAT-fs (sda): Directory bread(block 493) failed
> 
> <3>[  218.431551] FAT-fs (sda): Directory bread(block 494) failed
> 
> <3>[  218.431563] FAT-fs (sda): Directory bread(block 495) failed
> 
> <3>[  218.431592] FAT-fs (sda): Directory bread(block 496) failed
> 
> <3>[  218.431604] FAT-fs (sda): Directory bread(block 497) failed
> 
> <3>[  218.431616] FAT-fs (sda): Directory bread(block 498) failed
> 
> <3>[  218.431627] FAT-fs (sda): Directory bread(block 499)
> 
> is this probably issue in driver where It is failing to properly re-init
> the USB device 2nd time ?

I have no idea, something is trying to read those blocks and failing,
perhaps a program doesn't realize the disk is no longer there anymore?

greg k-h

Unsuccessful transactions during usb enumeration

[sanjeev sharma]

OK ! So USB Driver is trying to read but physically disk is not enumerated
but USB Subsystem did recognize the disk as per Logs.

 usb 2-1.1: new high speed USB device number 6 using fsl-ehci

<6>[  216.990681] scsi1 : usb-storage 2-1.1:1.0

<5>[  217.983182] scsi 1:0:0:0: Direct-Access     USB2.0    Flash Disk
0.00 PQ: 0 ANSI: 2

<5>[  217.986978] sd 1:0:0:0: [sdb] 3904512 512-byte logical blocks: (1.99
GB/1.86 GiB)

<5>[  217.987461] sd 1:0:0:0: [sdb] Write Protect is off

<7>[  217.987473] sd 1:0:0:0: [sdb] Mode Sense: 00 00 00 00

<3>[  217.987958] sd 1:0:0:0: [sdb] Asking for cache data failed

<3>[  217.987968] sd 1:0:0:0: [sdb] Assuming drive cache: write through

<3>[  217.991715] sd 1:0:0:0: [sdb] Asking for cache data failed

<3>[  217.991726] sd 1:0:0:0: [sdb] Assuming drive cache: write through

<6>[  218.215499]  sdb:

<3>[  218.221482] sd 1:0:0:0: [sdb] Asking for cache data failed

<3>[  218.221513] sd 1:0:0:0: [sdb] Assuming drive cache: write through

<5>[  218.221529] sd 1:0:0:0: [sdb] Attached SCSI removable disk

<3>[  218.431346] FAT-fs (sda): Directory bread(block 480) failed

<3>[  218.431362] FAT-fs (sda): Directory bread(block 481) failed

<3>[  218.431374] FAT-fs (sda): Directory bread(block 482) failed

<3>[  218.431386] FAT-fs (sda): Directory bread(block 483) failed

Regards
Sanjeev Sharma



On Wed, Jun 18, 2014 at 12:37 PM, Greg KH <greg@kroah.com> wrote:

> On Wed, Jun 18, 2014 at 12:22:33PM +0530, sanjeev sharma wrote:
> > Hi Greg,
> >
> > In one of my imx6 based Board when I connect USB Disk first time
> everything
> > work's ok and I can read/write content from USB Flash Driver but when I
> do
> > eject and connect again I could see below continuous messages from dmesg
> > and disk never mounted.
> >
> >  218.431346] FAT-fs (sda): Directory bread(block 480) failed
> >
> > <3>[  218.431362] FAT-fs (sda): Directory bread(block 481) failed
> >
> > <3>[  218.431374] FAT-fs (sda): Directory bread(block 482) failed
> >
> > <3>[  218.431386] FAT-fs (sda): Directory bread(block 483) failed
> >
> > <3>[  218.431398] FAT-fs (sda): Directory bread(block 484) failed
> >
> > <3>[  218.431420] FAT-fs (sda): Directory bread(block 485) failed
> >
> > <3>[  218.431432] FAT-fs (sda): Directory bread(block 486) failed
> >
> > <3>[  218.431444] FAT-fs (sda): Directory bread(block 487) failed
> >
> > <3>[  218.431466] FAT-fs (sda): Directory bread(block 488) failed
> >
> > <3>[  218.431478] FAT-fs (sda): Directory bread(block 489) failed
> >
> > <3>[  218.431499] FAT-fs (sda): Directory bread(block 490) failed
> >
> > <3>[  218.431515] FAT-fs (sda): Directory bread(block 491) failed
> >
> > <3>[  218.431528] FAT-fs (sda): Directory bread(block 492) failed
> >
> > <3>[  218.431540] FAT-fs (sda): Directory bread(block 493) failed
> >
> > <3>[  218.431551] FAT-fs (sda): Directory bread(block 494) failed
> >
> > <3>[  218.431563] FAT-fs (sda): Directory bread(block 495) failed
> >
> > <3>[  218.431592] FAT-fs (sda): Directory bread(block 496) failed
> >
> > <3>[  218.431604] FAT-fs (sda): Directory bread(block 497) failed
> >
> > <3>[  218.431616] FAT-fs (sda): Directory bread(block 498) failed
> >
> > <3>[  218.431627] FAT-fs (sda): Directory bread(block 499)
> >
> > is this probably issue in driver where It is failing to properly re-init
> > the USB device 2nd time ?
>
> I have no idea, something is trying to read those blocks and failing,
> perhaps a program doesn't realize the disk is no longer there anymore?
>
> greg k-h
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140618/28e5ef32/attachment.html