uas problem in linux kernel 3.15
Jos.v.W.
Status: Contributor
Joined: 25 Jan 2011
Posts: 57
Reply Quote
After upgrading linux to 3.15 I have problems with my Seagate expansion hard drive.
While mounting it or writing to it, my whole system sometimes freezes and needs a hard reset.

It seems to be a known UAS (USB Attached SCSI) issue and there is a workaround, see
bbs.archlinux.or/viewtopic.php?id=183190
The mentioned workaround fixes the issue.
Back to top
Re: uas problem in linux kernel 3.15
Jos.v.W.
Status: Contributor
Joined: 25 Jan 2011
Posts: 57
Reply Quote
:: Jos.v.W. wrote ::
there is a workaround, see
bbs.archlinux.or/viewtopic.php?id=183190

The url should be
bbs.archlinux.org/viewtopic.php?id=183190
The workaround fixes the issue by telling the USB-UAS module to ignore the device.
Back to top
damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 1122
Reply Quote
Hmm, so there doesn't appear to be a patch in site, the developers on linux-usb are still discussing it.

Thanks for pointing this out. Although we can't solve it, someone else will see this post and find the workaround.
Back to top
USB-UAS problem in linux kernel 3.16
Jos.v.W.
Status: Contributor
Joined: 25 Jan 2011
Posts: 57
Reply Quote
kernel 3.16-1 still has the same USB-UAS issue.
See:
Enabling UAS makes Seagate Expansion Desk unavailable (with workaround)
bugzilla.kernel.org/show_bug.cgi?id=79511
Back to top
uas issue in linux kernel
Jos.v.W.
Status: Contributor
Joined: 25 Jan 2011
Posts: 57
Reply Quote
This issue has been 'fixed' in kernel 3.16-2:
www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.16.2
:: Quote ::
For now this at least makes uas capable disk enclosures work again by forcing fallback to the usb-storage driver.

Back to top
UAS kernel module issue fixed in kernel 3.17.1
Jos.v.W.
Status: Contributor
Joined: 25 Jan 2011
Posts: 57
Reply Quote
I got a message from UAS kernel module developer hdegoede@redhat.com about a patch which I have tested.
'Has this patch already been merged into kernel 3.17.0?'
:: Quote ::
No, the patches were to late for 3.17.0, they have been queued up for 3.17.1, so once 3.17.1 is out, things should work out of the box.

Back to top
Display posts from previous:   

All times are GMT - 8 Hours