From: Itai Nahshon <nahshon@actcom.co.il>
To: Alan Cox <alan@redhat.com>, linux-kernel@vger.kernel.org
Cc: Pete Zaitcev <zaitcev@redhat.com>
Subject: Re: Linux 2.4.20-pre4-ac2
Date: Tue, 27 Aug 2002 02:01:53 +0300 [thread overview]
Message-ID: <200208270201.53750.nahshon@actcom.co.il> (raw)
In-Reply-To: <200208261035.g7QAZ4G19985@devserv.devel.redhat.com>
On Monday 26 August 2002 13:35 pm, Alan Cox wrote:
> o Error handling clean ups for USB storage (Pete Zaitcev)
While USB-storage error handling is looked at...
--- linux-2.4.20-pre4-ac2-i2/drivers/usb/storage/transport.c.orig Mon Aug 26
23:24:09 2002
+++ linux-2.4.20-pre4-ac2-i2/drivers/usb/storage/transport.c Mon Aug 26
23:24:53 2002
@@ -1164,6 +1164,10 @@
ret = USB_STOR_TRANSPORT_ABORTED;
goto out;
}
+ if (result == US_BULK_TRANSFER_FAILED) {
+ ret = USB_STOR_TRANSPORT_FAILED;
+ goto out;
+ }
}
}
There's a check for US_BULK_TRANSFER_FAILED after
a call to usb_stor_transfer everywhere except here... Is it for
a reason?
Backround:
A long time ago (linux-2.4.19-pre4-ac2) I got a USB disk
related hang (all processes accessing it stuck in state D).
It happened while reading from a USB-storage device
(disk attached to a USB-IDE bridge).
The system log has just these two errors:
usb-uhci.c: interrupt, status 3, frame# 1660
usb_control/bulk_msg: timeout
That problem happened only once. I had to reboot in order
to continue use the device.
Is it possible that the missing check is the cause for that
hang?
-- Itai
next prev parent reply other threads:[~2002-08-26 22:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-26 10:35 Alan Cox
2002-08-26 11:54 ` Christoph Hellwig
2002-08-26 15:15 ` Benjamin Herrenschmidt
2002-08-26 16:23 ` Daniel Egger
2002-08-26 20:06 ` Benjamin Herrenschmidt
2002-08-26 19:06 ` Alan Cox
2002-08-26 20:37 ` Benjamin Herrenschmidt
2002-08-26 23:01 ` Itai Nahshon [this message]
2002-09-04 17:45 ` Pete Zaitcev
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=200208270201.53750.nahshon@actcom.co.il \
--to=nahshon@actcom.co.il \
--cc=alan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zaitcev@redhat.com \
/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
all inboxes | Powered by JetHome®