All of lore.kernel.org
 help / color / mirror / Atom feed
From: matthias@kaehlcke.net (Matthias Kaehlcke)
To: linux-arm-kernel@lists.infradead.org
Subject: Problem in USB on the Sheevaplug, 2.6.31
Date: Wed, 23 Sep 2009 11:35:43 +0200	[thread overview]
Message-ID: <20090923093543.GJ2558@darwin> (raw)
In-Reply-To: <45219fb00909230143h38db71e7l7c16b4a59ec1b152@mail.gmail.com>

hi lluis,

El Wed, Sep 23, 2009 at 10:43:56AM +0200 Llu?s Batlle ha dit:

> after using a USB storage device (a Kingston DataTraveler 8GB flash
> stick) in the sheevaplug for some hours, at one point the device
> stopped working until I replugged it in.
> 
> The system kept stable, while all this happened.
> 
> Here comes the 'dmesg' part:
> 
> EXT3 FS on sda1, internal journal
> EXT3-fs: mounted filesystem with writeback data mode.
> #------------ some hours passed ----------
> usb 1-1: reset high speed USB device using orion-ehci and address 2
> ------------[ cut here ]------------
> WARNING: at arch/arm/kernel/process.c:171 cpu_idle+0x74/0xbc()
> Modules linked in: sg
> [<c002f85c>] (unwind_backtrace+0x0/0xdc) from [<c003ecb0>]
> (warn_slowpath_common+0x4c/0x80)
> [<c003ecb0>] (warn_slowpath_common+0x4c/0x80) from [<c002b974>]
> (cpu_idle+0x74/0xbc)
> [<c002b974>] (cpu_idle+0x74/0xbc) from [<c0008b04>] (start_kernel+0x270/0x2d4)
> [<c0008b04>] (start_kernel+0x270/0x2d4) from [<00008034>] (0x8034)
> ---[ end trace 81d90711559dbd0e ]---
> usb 1-1: reset high speed USB device using orion-ehci and address 2
> usb 1-1: device descriptor read/64, error -110
> usb 1-1: device descriptor read/64, error -32
> usb 1-1: reset high speed USB device using orion-ehci and address 2
> usb 1-1: device descriptor read/64, error -32
> usb 1-1: device descriptor read/64, error -32
> usb 1-1: reset high speed USB device using orion-ehci and address 2
> usb 1-1: device not accepting address 2, error -32
> usb 1-1: reset high speed USB device using orion-ehci and address 2
> usb 1-1: device not accepting address 2, error -32
> sd 0:0:0:0: [sda] Unhandled error code
> sd 0:0:0:0: [sda] Result: hostbyte=0x07 driverbyte=0x00
> end_request: I/O error, dev sda, sector 15466566
> usb 1-1: USB disconnect, address 2
> EXT3-fs error (device sda1): read_inode_bitmap: Cannot read inode
> bitmap - block_group = 59, inode_bitmap = 1933313
> EXT3-fs error (device sda1) in ext3_new_inode: IO failure
> ------------[ cut here ]------------
> WARNING: at fs/buffer.c:1152 mark_buffer_dirty+0x34/0xe8()
> Modules linked in: sg
> [<c002f85c>] (unwind_backtrace+0x0/0xdc) from [<c003ecb0>]
> (warn_slowpath_common+0x4c/0x80)
> [<c003ecb0>] (warn_slowpath_common+0x4c/0x80) from [<c00d67d4>]
> (mark_buffer_dirty+0x34/0xe8)
> [<c00d67d4>] (mark_buffer_dirty+0x34/0xe8) from [<c010b3ac>]
> (ext3_commit_super+0x4c/0x70)
> [<c010b3ac>] (ext3_commit_super+0x4c/0x70) from [<c010c5a0>]
> (ext3_handle_error+0x98/0xc4)
> [<c010c5a0>] (ext3_handle_error+0x98/0xc4) from [<c010c634>]
> (__ext3_std_error+0x68/0x74)
> [<c010c634>] (__ext3_std_error+0x68/0x74) from [<c0102e60>]
> (ext3_new_inode+0x898/0x91c)
> [<c0102e60>] (ext3_new_inode+0x898/0x91c) from [<c0109898>]
> (ext3_mkdir+0x8c/0x2cc)
> [<c0109898>] (ext3_mkdir+0x8c/0x2cc) from [<c00bc5ac>] (vfs_mkdir+0x6c/0xc0)
> [<c00bc5ac>] (vfs_mkdir+0x6c/0xc0) from [<c00be928>] (sys_mkdirat+0x84/0xd0)
> [<c00be928>] (sys_mkdirat+0x84/0xd0) from [<c002a9c0>]
> (ret_fast_syscall+0x0/0x2c)
> ---[ end trace 81d90711559dbd0f ]---
> Aborting journal on device sda1.
> journal commit I/O error
> ext3_abort called.
> EXT3-fs error (device sda1): ext3_journal_start_sb: Detected aborted journal
> Remounting filesystem read-only
> 
> It's a vanilla kernel built with gcc 4.3.4 . If you need more
> information, I can compile special versions of that kernel to get some
> additional information.

the USB FAQ suggests it might be a problem of signal quality, try if it
works when removing ehci-hcd:
http://www.linux-usb.org/FAQ.html#ts6

is the file system subject to a lot of write accesses? in this case it
is likely you will encounter problems of corrupt sectors due to flash
wear out. be sure not to mount locations like /var (especially
/var/log) on the flash device. you also should mount the device with
the options noatime and nodiratime if you aren't doing it yet

<ca>per cert: que tal el sheeva plug? porto temps pensant de
comprar-ne un</ca>

salutacions

-- 
Matthias Kaehlcke
Embedded Linux Engineer
Barcelona

     Nationalism is an infantile disease. It is the measles of mankind
                         (Albert Einstein)
                                                                 .''`.
    using free software / Debian GNU/Linux | http://debian.org  : :'  :
                                                                `. `'`
gpg --keyserver pgp.mit.edu --recv-keys 47D8E5D4                  `-

  reply	other threads:[~2009-09-23  9:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-23  8:43 Problem in USB on the Sheevaplug, 2.6.31 Lluís Batlle
2009-09-23  9:35 ` Matthias Kaehlcke [this message]
2009-09-23  9:47   ` Lluís Batlle
2009-09-23 10:12     ` Matthias Kaehlcke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090923093543.GJ2558@darwin \
    --to=matthias@kaehlcke.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.