Modify

Opened 8 years ago

Closed 6 years ago

#7404 closed defect (fixed)

ohci_hcd ssb0:1: fatal error - USB 2.0 storage failure

Reported by: ldolse <ldolse@…> Owned by: hauke
Priority: response-needed Milestone: Backfire 10.03.1
Component: packages Version: Trunk
Keywords: usb storage ohci ehci Cc:

Description

Building backfire from trunk, svn revision is 21620. Router model is Asus WL500gpV2.

USB storage is working when you first plug a disk in, but fails after a short while. The drive is initially discovered as /dev/sda1 and connected using USB 2. After failing the drive is rediscovered as /dev/sdb1 and is connected using USB 1.1 according to dmesg. After remounting the drive at it's new mount point it runs stably.

dmesg output is attached. Build was compiled with symbols enabled, but no stack trace seems to occur along with the failure. Let me know what else I can gather to debug.

A thread where another user is seeing nearly identical behavior on the same hardware:
https://forum.openwrt.org/viewtopic.php?id=24843

Attachments (1)

USB_Failure-dmesg-linked-modules.txt (11.7 KB) - added by ldolse <ldolse@…> 8 years ago.
dmesg output and linked modules

Download all attachments as: .zip

Change History (4)

Changed 8 years ago by ldolse <ldolse@…>

dmesg output and linked modules

comment:1 Changed 8 years ago by anonymous

I rebuilt from trunk with USB2/ehci disabled. Without USB 2.0 support the problem does not re-occur, so it definitely appears to be a problem in that module.

comment:2 Changed 7 years ago by jow

  • Owner changed from developers to hauke
  • Priority changed from high to response-needed
  • Status changed from new to assigned

Is this still the case with RC5 ?

comment:3 Changed 6 years ago by nbd

  • Resolution set to fixed
  • Status changed from assigned to closed

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.