From: Eduardo Gallofin <egallofin@yahoo.com>
To: balrogg@gmail.com
Cc: linux-omap-open-source@linux.omap.com
Subject: init (busybox) problem on OSK5912
Date: Thu, 4 May 2006 17:10:47 -0700 (PDT) [thread overview]
Message-ID: <20060505001047.52257.qmail@web52309.mail.yahoo.com> (raw)
In-Reply-To: <fb249edb0605040943k8a85615w76b5231436d5aec@mail.gmail.com>
Hi Andrzej,
Thanks for your response. However, we already have
swap support enabled all the time, but still the
problem persists. And it does not seem random at all,
our applications always fail with a segfault when
connecting or binding to a socket....
I'm using the tool chain available at the
linux.omap website (3.3.2).... I've tried 3.4.1 but I
still have the same problem... do you have a link to
the newest toolchain (binaries please). It might be
worth a try...
Thank you very much!
- Ed -
--- andrzej zaborowski <balrog@zabor.org> wrote:
> Hi Eduardo,
>
> From your description it sounds like a similar bug
> to what we've been
> facing on some PDAs based on OMAP311. If it is the
> same thing, then it
> doesn't matter what version of busybox or other
> applications you are
> running or whether it's compiled statically. All
> programs seem to be
> affected by the bug in the way that they hang or
> segfault in random
> places. Statically compiled programs do that with
> lower probability
> but they still do. Some versions are more affected
> and others less,
> but changing a single line in the busybox code
> changes that
> probability randomly.
>
> We haven't found a definitive solution yet but we
> found a nasty
> workaround (credits go to nasty Marex): compile the
> kernel with swap
> support ("Paging of anonymous memory" in the config,
> I think) -- you
> don't need to add swap partitions, just compile the
> kernel with this
> option enabled. This should lower the probability of
> breakage to near
> acceptable level. It would be interesting to see if
> this works for you
> and if it's really the same problem. So far I was
> only seeing it on
> OMAP311. It might just as well be something totally
> different, in this
> case just ignore me.
>
> With this option enabled we're able to run whole
> dynamically-linked
> Linux distributions including X, Gnome, KDE, gdb and
> strace. The
> problem persists but is a whole order of magnitude
> less annoying.
>
> BTW: programs compilled statically against uclibc
> are not huge at all,
> sometime smaller than dynamically-linked against
> glibc.
> >
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Tired of spam? Yahoo! Mail has the best spam
> protection around
> > http://mail.yahoo.com
> > _______________________________________________
> > Linux-omap-open-source mailing list
> > Linux-omap-open-source@linux.omap.com
> >
>
http://linux.omap.com/mailman/listinfo/linux-omap-open-source
> >
> Good luck!
>
> Regards,
> Andrzej
> --
> balrog 2oo6
>
> Dear Outlook users: Please remove me from your
> address books
>
http://www.newsforge.com/article.pl?sid=03/08/21/143258
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
next prev parent reply other threads:[~2006-05-05 0:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060503194919.7EDC38062D@linux.omap.com>
2006-05-04 6:47 ` init (busybox) problem on OSK5912 Eduardo Gallofin
2006-05-04 16:43 ` andrzej zaborowski
2006-05-05 0:10 ` Eduardo Gallofin [this message]
2006-05-05 2:39 ` Eduardo Gallofin
2006-05-10 7:38 Chetan Kapoor
-- strict thread matches above, loose matches on Subject: below --
2006-05-10 7:21 chetan.kapoor
2006-05-10 7:08 Chetan Kapoor
2006-05-04 7:19 Fw: " Chetan Kapoor
2006-05-04 7:59 ` Eduardo Gallofin
[not found] <20060501170002.24B3A8062B@linux.omap.com>
2006-05-02 7:09 ` Eduardo Gallofin
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=20060505001047.52257.qmail@web52309.mail.yahoo.com \
--to=egallofin@yahoo.com \
--cc=balrogg@gmail.com \
--cc=linux-omap-open-source@linux.omap.com \
/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