public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: David Jander <david.jander@protonic•nl>
To: linuxppc-embedded@ozlabs•org
Subject: Re: frequent sig 11 with malloc() on mpc8xx
Date: Thu, 4 May 2006 17:46:31 +0200	[thread overview]
Message-ID: <200605041746.31645.david.jander@protonic.nl> (raw)
In-Reply-To: <20060504144605.B18B3353BE7@atlas.denx.de>

On Thursday 04 May 2006 16:46, Wolfgang Denk wrote:
> Ummm... I have yet to see a single case where moving to 2.6  improved
> the stability for a MPC8xx system :-(

Our case.

Jffs2's gc thread stopped crashing. This might have more to do with mtd/jffs2 
than with the rest of the kernel, but it sure works better now.

Nevertheless I am very interested in hearing about (potential) stability 
problems with with 2.6.14, 15 and 16 (besides not booting just because 
Marcelo couldn't resist screwing up on the last minute; problem which is 
being worked on ;-).

Greetings,

-- 
David Jander

  reply	other threads:[~2006-05-04 15:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-04  7:48 frequent sig 11 with malloc() on mpc8xx Gautam Borad
2006-05-04 14:46 ` Wolfgang Denk
2006-05-04 15:46   ` David Jander [this message]
2006-05-05  8:43   ` Gautam Borad
2006-05-05  9:40     ` Wolfgang Denk
2006-05-05 14:00       ` Gautam Borad
2006-05-05 14:17         ` Mark Chambers

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=200605041746.31645.david.jander@protonic.nl \
    --to=david.jander@protonic$(echo .)nl \
    --cc=linuxppc-embedded@ozlabs$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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