On 10/10/2013 10:59 AM, Peter Robinson wrote:
On Wed, Oct 9, 2013 at 9:49 PM, Jeffrey Bastian <jbastian@xxxxxxxxxx> wrote:
I just got a Trimslice Pro (a friend wasn't using it), and I booted the
Fedora-Minimal-armhfp-20-Beta-TC2-sda image from an SD card and started
copying it to the internal SSD, and started getting errors on the serial
console:
[ 864.153171] hub 1-0:1.0: cannot reset port 1 (err = -110)
[ 864.382165] hub 1-0:1.0: cannot reset port 1 (err = -110)
[ 864.611136] hub 1-0:1.0: cannot reset port 1 (err = -110)
[ 864.616551] hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
...
[ 923.473666] hub 1-0:1.0: cannot reset port 1 (err = -110)
[ 923.702667] hub 1-0:1.0: cannot reset port 1 (err = -110)
[ 923.931671] hub 1-0:1.0: cannot reset port 1 (err = -110)
[ 924.574479] end_request: I/O error, dev sda, sector 240082
[ 924.579969] Buffer I/O error on device sda1, logical block 119017
[ 924.586047] Buffer I/O error on device sda1, logical block 119018
[ 924.592124] Buffer I/O error on device sda1, logical block 119019
...
[ 1422.769804] Buffer I/O error on device sda1, logical block 135410
[ 1422.977894] EXT4-fs error (device sda1) in ext4_writepages:2540: IO
failure
[ 1423.163072] EXT4-fs error (device sda1): ext4_journal_check_start:56:
Detected aborted journal
[ 1423.171705] EXT4-fs (sda1): Remounting filesystem read-only
[ 1423.880858] EXT4-fs (sda1): ext4_writepages: jbd2_start: 1024 pages,
ino 31; err -30
[ 1433.542568] hub 1-0:1.0: cannot reset port 1 (err = -110)
This is using the 3.11.3-301.fc20.armv7hl kernel.
Searching the list archives, I see this has come up before, but there
doesn't seem to be a resolution:
https://lists.fedoraproject.org/pipermail/arm/2013-January/005114.html
Is this a kernel bug? Or is the SSD starting to fail?
I suspect neither is actually the answer. We've had a quite regular
issue with timeouts of the SSD on the trimslice pros that we've never
managed to nail down well. It could be a problem with the SSD, the USB
HW, or the kernel drivers for the tegra USB controller. The issue
seems to come and go. The way I use my TS pro is to use the SSD as
/home and have root on a SD card but that's primarily as it allows me
to swap out the SD card for different releases and easy testing. In
that config the SSD seems pretty stable but the few times I tried to
install the OS onto the SSD it had time out issues but that's back in
ther 3.4 - 3.6 kernel days so not recently.
Maybe I'm not quite comparing like-for-like here, but I suspect it's
more to do with the SATA controller than the Tegra USB controller. I am
using a heavily modified Toshiba AC100 (Tegra2 based, same as TrimSlice)
with a SuperTalent RC8 USB SSD (internally containing USB->SATA adapter,
and a Sandforce controller) and have never seen any disk dropout issues.
I am also NOT using a vanilla kernel.
Gordan
_______________________________________________
arm mailing list
arm@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/arm
