From: Phil Oester <kernel@linuxace.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.12-rc4 random oopses
Date: Sat, 21 May 2005 07:57:11 -0700 [thread overview]
Message-ID: <20050521145711.GA28132@linuxace.com> (raw)
In-Reply-To: <E1DZOFT-0001JJ-00@gondolin.me.apana.org.au>
On Sat, May 21, 2005 at 05:18:15PM +1000, Herbert Xu wrote:
> How long can your machine stay up under 2.6.11/2.6.12-rc4? Is 2.6.10
> still stable if rebuild it?
Machine stays up 'forever' on 2.6.10, dies within ~4 hours on 2.6.11+.
Yes, I have rebuilt 2.6.10 with some backported patches, and it still
works fine.
> If 2.6.10 is still proving to be stable, then please do a bisection
> search on the releases between 2.6.10/2.6.11. That may be the only
> way we can track this problem down.
Unfortunately the box is the firewall for my employer's west coast office
so I can only get away with one unexplained natural phenomenon per
day. May take awhile...
Phil
next prev parent reply other threads:[~2005-05-21 14:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 15:33 2.6.12-rc4 random oopses Phil Oester
2005-05-21 7:18 ` Herbert Xu
2005-05-21 14:57 ` Phil Oester [this message]
2005-05-22 7:52 ` Herbert Xu
2005-05-23 8:30 ` Maneesh Soni
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=20050521145711.GA28132@linuxace.com \
--to=kernel@linuxace.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.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