public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: Natanael Copa <mlists@tanael.org>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] lockups with hardened kernel
Date: Fri, 13 Jan 2006 10:50:14 +0100	[thread overview]
Message-ID: <1137145814.27064.171.camel@nc> (raw)
In-Reply-To: <Pine.LNX.4.44.0601091717471.29241-100000@lnx.bridge.intra>

On man, 2006-01-09 at 17:20 +0100, Peter S. Mazinger wrote:
> On Sat, 7 Jan 2006, Mike Frysinger wrote:
> 
> > On Saturday 07 January 2006 02:30, Natanael Copa wrote:
> > > On lør, 2006-01-07 at 00:44 -0500, Mike Frysinger wrote:
> > > > On Wednesday 04 January 2006 03:52, Natanael Copa wrote:
> > > > > I got a report from someone who experienced lockups when using
> > > > > gentoo-embedded built system (2.6.14-hardened-r1)

> > > When I disabled "Configure standard kernel features (for small
> > > systems)" (gcc -Os) the problem magically went away.
> > 
> > the kernel can be pretty sensitive to optimizations
> 
> if kernel is built w/ gcc-3.4.4 and -Os (at least I had that for 2.4.x 
> kernels) it "optimizes away" memcmp and the kernels have gotten a patch 
> to overcome this, the same problem does not occur w/ gcc-3.3.x.
> 
> > > So I think its a bug in gcc version 3.4.4 (Gentoo Hardened 3.4.4-r1,
> > > ssp-3.4.4-1.0, pie-8.7.8)
> > >
> > > Makes me nervous because I have built everything with -Os.
> 
> I have built everything w/ -Os and do not have trouble w/ it

I have researched this and found out that it is not the -Os itself that
causes this, but it is something else under "Configure standard kernel
features (for small systems)". I'm not sure of exactly what but I know
at least that it is not "Optimize for size". I have turned all options
under "Configure standard kernel features (for small systems)" except
"Load all symbols for debugging/kksymoops" (including optimize for size
(-Os)) and done the netload test all night. This morning the computer
was still up.  When I have an unstable kernel it hangs after an hour or
two.

I have tried to flip the "futex support" and that did not make any
difference (anyone who know how this affects uclibc based apps btw? Do I
need futex support?)

I think I have narrowed down the problem to one of those:
* BUG() support
* Enable full-sized data structures for core
* Enable eventpoll support

But exactly what, I dont know. If anyone here have had any problems with
disabling one of those, I'm very interested to hear.

Lots of bla bla here, I just thought it could be good for you guys to
know that turning off of those might make your kernel unstable, while
-Os should be ok with current gcc.


-- 
Natanael Copa

-- 
gentoo-embedded@gentoo.org mailing list



  parent reply	other threads:[~2006-01-13  9:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-04  8:52 [gentoo-embedded] lockups with hardened kernel Natanael Copa
2006-01-07  5:44 ` Mike Frysinger
2006-01-07  7:30   ` Natanael Copa
2006-01-07  7:35     ` Mike Frysinger
2006-01-09 16:20       ` Peter S. Mazinger
2006-01-09 19:49         ` Douglas Campos
2006-01-13  9:50         ` Natanael Copa [this message]
2006-01-13 11:00           ` Douglas Campos
2006-01-14  4:37             ` Dan C
2006-01-14 10:13               ` Dan C
2006-01-16  6:16             ` Dan C
2006-01-16 14:19               ` Douglas Campos

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=1137145814.27064.171.camel@nc \
    --to=mlists@tanael.org \
    --cc=gentoo-embedded@lists.gentoo.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