All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stephen P. Becker" <geoman@gentoo.org>
To: Martin Michlmayr <tbm@cyrius.com>
Cc: "'Linux/MIPS Development'" <linux-mips@linux-mips.org>
Subject: Re: Has anyone seen O2 crashes?
Date: Mon, 06 Feb 2006 11:03:39 -0500	[thread overview]
Message-ID: <43E7735B.4050307@gentoo.org> (raw)
In-Reply-To: <20060206151754.GA22181@deprecation.cyrius.com>

Martin Michlmayr wrote:
> I got a report that Debian's experimental 2.6.15 mips patches
> (2.6.15.2 plus linux-mips git from a few weeks ago plus random
> patches) sometimes crashes, posibly under high load - there's
> nothing on the serial console.
> 
> I was just wondering if anyone else (in particular the Gentoo folks)
> has seem something similar, or is O2 rock solid for you?

I don't know how Debian is patching things up for O2 (ths care to 
comment?), but ip32 has been absolutely rock solid for me the past 
several releases.  The only modifications I make to the source tree are 
a small gbefb patch and a minor Makefile patch (however, this is 
probably different from other Gentoo folks...I hate using our kernel 
source ebuilds which apply a number of patches for other platforms and 
issues).

I had over 60 days of uptime recently with some variant of 2.6.15 (-rc5 
I think), and the machine was hammered fairly hard during that time with 
plenty of compiling, including significant portions of KDE.  I have run 
both the 2.6.15 tag from lmo git, and now I'm on 2.6.16-rc1.  It still 
seems solid as ever.

-Steve

  reply	other threads:[~2006-02-06 15:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-06 15:17 Has anyone seen O2 crashes? Martin Michlmayr
2006-02-06 16:03 ` Stephen P. Becker [this message]
2006-02-06 18:11   ` Martin Michlmayr

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=43E7735B.4050307@gentoo.org \
    --to=geoman@gentoo.org \
    --cc=linux-mips@linux-mips.org \
    --cc=tbm@cyrius.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 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.