public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockrwd@gmail.com>
To: "Rogério Brito" <rbrito@ime.usp.br>
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [2.6.30-rc2] usb reset during big file transfer and ext3 error
Date: Tue, 21 Apr 2009 18:34:22 -0600	[thread overview]
Message-ID: <49EE660E.7040907@gmail.com> (raw)
In-Reply-To: <20090421111015.GA30260@ime.usp.br>

(ccing linux-usb)

Rogério Brito wrote:
> Hi there.
> 
> I have an amd64 system running Debian's sid distribution and I installed
> Linux 2.6.30-rc2 on it, as a way to get improvements for the i915
> subsystem.
> 
> Unfortunately, when I was transferring the contents of 2 DVDs from the
> main IDE HD to a USB external HD, I got errors from the USB host, the
> writes on the external HD become failures and the ext3 filesystem there
> enters into error mode, going read-only.
> 
> I eventually lose the access to the device (i.e., the /dev/sd??? device
> isn't there anymore) and I then have to re-run fsck on the given
> filesystem.
> 
> This has already happened 2 or 3 times already and I observed that it
> only occurs when there is high traffic---if I am, say, compiling the
> kernel on that external HD, I don't see any problems.
> 
> Attached is part of the dmesg log that shows the problem. I put the
> whole dmesg at <http://rb.doesntexist.org/linux/>.
> 
> As always, if any further information is needed, please let me know.

You're seeing these:

[103051.265045] ehci_hcd 0000:00:1d.7: detected XactErr len 1536/4096 
retry 1
[103051.265156] ehci_hcd 0000:00:1d.7: detected XactErr len 1536/4096 
retry 2
[103051.265281] ehci_hcd 0000:00:1d.7: detected XactErr len 1536/4096 
retry 3
[103051.265406] ehci_hcd 0000:00:1d.7: detected XactErr len 1536/4096 
retry 4

According to the EHCI spec, XactErr is "Set to a one by the Host 
Controller during status update in the case where the host did not 
receive a valid response from the device (Timeout, CRC, Bad PID, etc.)"

Quite likely this is some kind of hardware problem - maybe the USB port 
doesn't quite provide enough power for the drive, etc. A lot of these 
USB enclosure devices are also rather poor quality in general..

  reply	other threads:[~2009-04-22  0:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-21 11:10 [2.6.30-rc2] usb reset during big file transfer and ext3 error Rogério Brito
2009-04-22  0:34 ` Robert Hancock [this message]
2009-04-22 22:06   ` Rogério Brito
2009-04-23  2:53     ` Alan Stern
2009-05-01  9:15       ` Rogério Brito
2009-05-01 19:16         ` Alan Stern
2009-05-24  7:16           ` Rogério Brito
2009-05-24 14:40             ` Alan Stern
2009-05-24 15:32               ` ioctl_internal_command messages (was: Re: [2.6.30-rc2] usb reset during big file transfer and ext3 error) Rogério Brito
2009-05-24 16:11               ` [2.6.30-rc2] usb reset during big file transfer and ext3 error Rogério Brito
2009-05-25  2:34                 ` Alan Stern
2009-05-25 15:13                   ` [PATCH] usb-storage: include USB drive in unusual_devs list Rogério Brito
2009-05-25 21:03                     ` Alan Stern
2009-05-25 21:41                       ` Rogério Brito
2009-08-01 18:30                         ` Rogério Brito

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49EE660E.7040907@gmail.com \
    --to=hancockrwd@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=rbrito@ime.usp.br \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox