linux-arm-kernel.lists.infradead.org archive mirror
 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 12:12:46 +0200	[thread overview]
Message-ID: <20090923101246.GK2558@darwin> (raw)
In-Reply-To: <45219fb00909230247s65883755ia584b2e1e8c2369c@mail.gmail.com>

El Wed, Sep 23, 2009 at 11:47:52AM +0200 Llu?s Batlle ha dit:

> 2009/9/23, Matthias Kaehlcke <matthias@kaehlcke.net>:
> > hi lluis,
> >
> > 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
> I have no cable between the board USB connector and the stick, and the
> Sheevaplug people claim to have good USB 2.0 support... I will see if
> it happens again.

ok

> >  is the file system subject to a lot of write accesses? in this case it
> Yes, I'm using it as /tmp, where I do builds. Kernel builds for
> example.

ouch, i don't think that's a good idea. i'd recommend using a
hard drive for stuff like this

> >  is likely you will encounter problems of corrupt sectors due to flash
> >  wear out. be sure not to mount locations like /var (especially
> I barely used that stick... and I trust Kingston so I think this is
> not the case.

flash sticks aren't designed for usage profiles with very frequent
writes, like kernel builds. i'd bet even a kingston one will have
problems in a near future if you use it in that way. have a look at
http://free-electrons.com/doc/flash-filesystems.pdf P. 29ff for more
information about the issue.

it's also recommended to use ext2 instead of ext3 to reduce wear out
produced by journalling

> >  /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
> I use noatime, but I didn't know of nodiratime.
> >
> >  <ca>per cert: que tal el sheeva plug? porto temps pensant de
> >  comprar-ne un</ca>
> <ca>Doncs n'estic ben content. Pel preu crec que est? molt b?. Hi he
> estat portant el NixOS, i no he fet cap compilaci? creuada, aix? que
> s'ho ha menjat tot el Sheevaplug. Per? fa nom?s un dia que utilitzo
> l'stick USB, abans ho feia tot amb nfsroot.</ca>

<ca>molt be allo del nixos, ets un friki de debo ;) jo encara funciono
amb un nslu2, pero va una mica just de recursos, per aixo m'estic
plantetjant el sheevaplug. per cert: t'havia comentat que el teu task
spooler va ser presentat a la versio impresa del <de>linux
magazin</de>?</ca>

-- 
Matthias Kaehlcke
Embedded Linux Engineer
Barcelona

        They that can give up essential liberty to obtain a little
           temporary safety deserve neither liberty nor safety
                         (Benjamin Franklin)
                                                                 .''`.
    using free software / Debian GNU/Linux | http://debian.org  : :'  :
                                                                `. `'`
gpg --keyserver pgp.mit.edu --recv-keys 47D8E5D4                  `-

      reply	other threads:[~2009-09-23 10:12 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
2009-09-23  9:47   ` Lluís Batlle
2009-09-23 10:12     ` Matthias Kaehlcke [this message]

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=20090923101246.GK2558@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).