PS: still crash on 2.6.0-test9
devel envirronment;
gcc 3.2, binutils 2.14.90.0.6-3
lspci:
00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
00:02.1 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
00:02.2 USB Controller: nVidia Corporation nForce2 USB C
here it is in diff -u old new format
On Mon, 10 Nov 2003 14:51:30 -0800
"David Brownell" <[EMAIL PROTECTED]> wrote:
> diff -u old new--- usb-uhci.c.orig Mon Nov 10 23:37:44 2003
+++ usb-uhci.c Mon Nov 10 16:28:50 2003
@@ -795,7 +795,7 @@
list_add (&qh->desc_list, &urb_priv->desc_li
> Has anyone looked at why the reset failed? I assume that would clear the
> sense.
How could anyone attempt to find out why the reset failed?
Just some ideas:
a) not supported - AFAIK many storage devices don't seem to support the
bulk-reset, as the 'Other Popular OS' doesn't seem to issue them.
Here a patch sloving the probleme.
On Sat, 8 Nov 2003 19:53:06 +0100
"fee mail" <[EMAIL PROTECTED]> wrote:
>
>
> this happen with eci adsul usermode driver.
> pppd crash with this oops on console.
>
> The field dev may be reseted so the the line 321 of usb.c
> ("dev->bus->bandwidth_allocate
Can someone verify my decoding? (This matches what Dmitri sent earlier
that did not make it to the list, execept it looks like it starts with an
INQUIRY VPD page 0 - get a list of supported VPD pages).
No, that is not a SCSI command.
> TransferBuffer: 0x0012 (18) length
>
On Tue, Nov 04, 2003 at 05:53:44PM +0100, Till Harbaum wrote:
>
> i am just equipping one of my devices with a serial USB port to use this as a
> simple debug console to be displayed on my linux box.
>
> The driver lists a device with vendor/product id 05f9/ as the generic
> serial device.
On Sun, Nov 09, 2003 at 07:45:46PM +1100, Dmitri Katchalov wrote:
> [My previous msg didn't make it to the list, resending]
>
> Attached here for your perusal is USB log for this device on win98.
Thanks.
Can someone verify my decoding? (This matches what Dmitri sent earlier
that did not make it
On Mon, 10 Nov 2003, Patrick Mansfield wrote:
> On Mon, Nov 10, 2003 at 01:46:44PM -0500, Alan Stern wrote:
> > On Mon, 10 Nov 2003, Patrick Mansfield wrote:
>
> > How could anyone attempt to find out why the reset failed? The only
> > externally visible state is the device's response to incomi
On Mon, Nov 10, 2003 at 01:46:44PM -0500, Alan Stern wrote:
> On Mon, 10 Nov 2003, Patrick Mansfield wrote:
> How could anyone attempt to find out why the reset failed? The only
> externally visible state is the device's response to incoming USB
> requests. IIRC, it simply didn't respond to th
On Mon, 10 Nov 2003, Patrick Mansfield wrote:
> On Sat, Nov 08, 2003 at 10:47:26PM -0500, Alan Stern wrote:
> >
> > For CB and CBI devices, babble causes a DID_ERROR return. For Bulk-only
> > it causes a Check-Condition status to be returned along with Invalid
> > Command sense data. Like I s
On Sat, Nov 08, 2003 at 10:47:26PM -0500, Alan Stern wrote:
> On Sat, 8 Nov 2003, Patrick Mansfield wrote:
>
> > On Sat, Nov 08, 2003 at 11:28:37AM -0500, Alan Stern wrote:
> > A DID_ERROR causes scsi core to retry the command - it will not even check
> > the sense data. A DID_ABORT might be bett
11 matches
Mail list logo
