[fedora-arm] Trimslice SSD issues

Jon Masters jcm at redhat.com
Thu Sep 15 01:24:26 UTC 2011


Hi again Konstantin,

A number of folks in the Fedora ARM community are experiencing problems
with the Trimslice internal SSD dropping off the USB bus following a
forced bus reset (we are unclear why this happens under load). This
sometimes results in the SSD going readonly, or disappearing entirely.
Either way, it means that we can't use the SSD for e.g. building gcc.

Can you take a look at the example logs attached? To reproduce, using an
F15 hardfp rootfs running from an SD card, mount the SSD and build a
package such as gcc (recommended) from there. This avoids the entire
system falling over when the SSD drops, but allows for a reproducer.

Since this only happens under load, I'm hoping you will tell us there is
a software fix, or that it is heat related, or otherwise addressable.
Either way, we would like to know. Especially if it's a known issue.

Thanks!

Jon.

--- begin forward---
[19536.272955] usb 3-1: USB disconnect, device number 2
[19536.284124] sd 0:0:0:0: [sda] Unhandled error code
[19536.288907] sd 0:0:0:0: [sda]  Result: hostbyte=DID_NO_CONNECT 
driverbyte=DRIVER_OK
[19536.296568] sd 0:0:0:0: [sda] CDB: Write(10): 2a 00 01 28 1e e8 00
00 
f0 00
[19536.303591] end_request: I/O error, dev sda, sector 19406568
[19536.309241] Buffer I/O error on device sda1, logical block 2425817
[19536.315416] lost page write due to I/O error on sda1
[19536.320372] Buffer I/O error on device sda1, logical block 2425818
[19536.326546] lost page write due to I/O error on sda1
[19536.331509] Buffer I/O error on device sda1, logical block 2425819
[19536.337675] lost page write due to I/O error on sda1
[19536.342636] Buffer I/O error on device sda1, logical block 2425820
[19536.348802] lost page write due to I/O error on sda1
[19536.353764] Buffer I/O error on device sda1, logical block 2425821
[19536.359930] lost page write due to I/O error on sda1
[19536.364892] Buffer I/O error on device sda1, logical block 2425822
[19536.371065] lost page write due to I/O error on sda1
[19536.376020] Buffer I/O error on device sda1, logical block 2425823
[19536.382194] lost page write due to I/O error on sda1
[19536.387149] Buffer I/O error on device sda1, logical block 2425824
[19536.393322] lost page write due to I/O error on sda1
[19536.398277] Buffer I/O error on device sda1, logical block 2425825
[19536.404450] lost page write due to I/O error on sda1
[19536.409404] Buffer I/O error on device sda1, logical block 2425826
[19536.415577] lost page write due to I/O error on sda1
[19536.420640] EXT3-fs: ext3_journal_dirty_data: aborting transaction: 
IO failure in ext3_journal_dirty_data
[19536.422997] sd 0:0:0:0: [sda] Unhandled error code
[19536.423006] sd 0:0:0:0: [sda]  Result: hostbyte=DID_NO_CONNECT 
driverbyte=DRIVER_OK
[19536.423017] sd 0:0:0:0: [sda] CDB: Write(10): 2a 00 01 28 1f d8 00
00 
20 00
[19536.423037] end_request: I/O error, dev sda, sector 19406808
[19536.455307] EXT3-fs (sda1): error in ext3_orphan_add: Readonly
filesystem
[19536.456507] EXT3-fs error (device sda1): ext3_get_inode_loc: unable 
to read inode block - inode=1748744, block=7077890
[19536.470674] EXT3-fs (sda1): I/O error while writing superblock
[19536.500682] EXT3-fs (sda1): I/O error while writing superblock
[19536.506521] EXT3-fs (sda1): error in ext3_ordered_write_end: IO
failure
[19536.520753] EXT3-fs (sda1): I/O error while writing superblock
[19536.526675] JBD: Detected IO errors while flushing file data on sda1
[19536.534108] Aborting journal on device sda1.
[19536.538769] JBD: I/O error detected when updating journal superblock 
for sda1.
[19536.550614] EXT3-fs (sda1): error: ext3_journal_start_sb: Detected 
aborted journal
[19536.558174] EXT3-fs (sda1): error: remounting filesystem read-only
[19536.564521] EXT3-fs error (device sda1): ext3_get_inode_loc: unable 
to read inode block - inode=1748744, block=7077890
[19536.565359] JBD: Detected IO errors while flushing file data on sda1
[19536.565437] journal commit I/O error
[19537.630856] Kernel panic - not syncing: Attempted to kill init!
[19537.636831] [<c005edb4>] (unwind_backtrace+0x0/0x134) from 
[<c049bc08>] (panic+0x78/0x1a4)
[19537.645211] [<c049bc08>] (panic+0x78/0x1a4) from [<c008a598>] 
(do_exit+0xc0/0x714)
[19537.652805] [<c008a598>] (do_exit+0xc0/0x714) from [<c008ac84>] 
(do_group_exit+0x98/0xc8)
[19537.661036] [<c008ac84>] (do_group_exit+0x98/0xc8) from [<c009b39c>] 
(get_signal_to_deliver+0x3e0/0x434)
[19537.670564] [<c009b39c>] (get_signal_to_deliver+0x3e0/0x434) from 
[<c0059f10>] (do_signal+0xb8/0x594)
[19537.679781] [<c0059f10>] (do_signal+0xb8/0x594) from [<c005a40c>] 
(do_notify_resume+0x20/0x5c)
[19537.688452] [<c005a40c>] (do_notify_resume+0x20/0x5c) from 
[<c00570f8>] (work_pending+0x24/0x28)
[19537.697263] CPU0: stopping
[19537.699991] [<c005edb4>] (unwind_backtrace+0x0/0x134) from 
[<c00512b0>] (do_IPI+0xc4/0x130)
[19537.708336] [<c00512b0>] (do_IPI+0xc4/0x130) from [<c049f72c>] 
(__irq_svc+0x4c/0xe4)
[19537.716064] Exception stack(0xee121c58 to 0xee121ca0)
[19537.721103] 1c40: 
    00000000 e735f780
[19537.729268] 1c60: 00260021 00200000 ee120000 e735f780 c08f4260 
e735f780 ed89d4e4 0000000c
[19537.737432] 1c80: c06422d4 ee121d30 00000000 ee121ca0 c020ae7c 
c027d9ac 60000013 ffffffff
[19537.745612] [<c049f72c>] (__irq_svc+0x4c/0xe4) from [<c027d9ac>] 
(_test_and_set_bit+0x3c/0x48)




More information about the arm mailing list