abe3 Sandisk Sansa clip - umass0: BBB reset failed, IOERRO - The FreeBSD Forums
The FreeBSD Forums  

Go Back   The FreeBSD Forums > Base System > Peripheral Hardware

Peripheral Hardware Stuff that plugs in via USB, FireWire, eSATA, PS/2, etc.

Reply
 
Thread Tools Display Modes
  #1  
Old March 11th, 2009, 07:03
octix octix is offline
Junior Member
 
Join Date: Feb 2009
Posts: 31
Thanks: 3
Thanked 1 Time in 1 Post
Default Sandisk Sansa clip - umass0: BBB reset failed, IOERRO

Hello.

I'm having some issues with my mp3 player. Basically I can mount it only once, I can write/read, but if I try second time I cannot mount it anymore. I need to reboot system to be able to use it again...

dmesg gives:
umass0: <SanDisk SanDisk Sansa Clip, class 0/0, rev 2.00/a6.ec, addr 2> on uhub2
da0 at umass-sim0 bus 0 target 0 lun 0
da0: <SanDisk Sansa Clip 4GB v02.> Removable Direct Access SCSI-0 device
da0: 40.000MB/s transfers
da0: 3889MB (7965696 512 byte sectors: 255H 63S/T 495C)
GEOM_LABEL: Label for provider da0 is msdosfs/SANSA CLIP.
GEOM_LABEL: Label msdosfs/SANSA CLIP removed.
GEOM_LABEL: Label for provider da0 is msdosfs/SANSA CLIP.

looks fine.

I mount it using this cmd: mount_msdosfs /mnt/sansa
And when I'm done just unmount /mnt/sansa

and then it starts with this kind of messages:
umass0: BBB reset failed, IOERROR
umass0: BBB bulk-in clear stall failed, IOERROR
umass0: BBB bulk-out clear stall failed, IOERROR
...

I'm getting the constantly/in a loop, I mean every time I call dmesg, there are more of them each time...


Any thoughts? Apparently it's not unmounted correctly.

Thank you in advance.
Reply With Quote
  #2  
Old March 17th, 2009, 19:16
Lexx Lexx is offline
Junior Member
 
Join Date: Mar 2009
Posts: 6
Thanks: 0
Thanked 0 Times in 0 Posts
Default Same here

I'm getting the exact same error on a Corsair Voyager mini 4GB. I've asked around on other forums about it, but so far nobody seems to know how to fix it. It was working fine with a PQI 2GB, mounted properly with:

mount -t msdosfs /dev/da0s1 /media/drive

I unmounted it, and tried to mount the Corsair. When that didn't work, I tried the PQI drive again and started getting the same problem. I tried a different USB port and it seemed to work, but the first USB port is now hosed. It probably won't fix itself without a reboot.
Reply With Quote
  #3  
Old March 18th, 2009, 02:02
toxc toxc is offline
Junior Member
 
Join Date: Feb 2009
Posts: 6
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Same problem as I found, I guess Freebsd can't support hot plug so good as some linux disto yet when I search on the internet. But it may not be a big problem for an expert,.
Reply With Quote
  #4  
Old March 18th, 2009, 03:01
jb_fvwm2 jb_fvwm2 is online now
Senior Member
 
Join Date: Nov 2008
Posts: 1,387
Thanks: 60
Thanked 145 Times in 130 Posts
Default

no one has mentioned the
#camcontrol rescan all
maybe it would fix it?
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
ACPI autoload failed? ufonpu Installing & Upgrading 1 February 9th, 2009 18:38
Reset Screen Resolution - Bad Result thomas GNOME 0 January 24th, 2009 15:21
make bulid failed ! jackie Installing & Upgrading 15 December 9th, 2008 07:06
xorg build failed francach Installation and Maintenance of FreeBSD Ports or Packages 6 November 28th, 2008 10:59
portupgrade glib-2\* failed John Installation and Maintenance of FreeBSD Ports or Packages 0 November 17th, 2008 06:04


All times are GMT +1. The time now is 13:17.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2013, vBulletin Solutions, Inc.
The mark FreeBSD is a registered trademark of The FreeBSD Foundation and is used by The FreeBSD Project with the permission of The FreeBSD Foundation.
Web protection and acceleration provided by CloudFlare
0