public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mingming Cao <cmm@us.ibm.com>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.70-mm2
Date: Fri, 30 May 2003 15:36:38 -0700	[thread overview]
Message-ID: <3ED7DCF6.20206@us.ibm.com> (raw)
In-Reply-To: 20030530133015.4f305808.akpm@digeo.com

Andrew Morton wrote:
>>
>>Any hint on when -mm3 will be out,
> 
> 
> About ten hours hence, probably.
> 
> Welll ext3 has been a bit bumpy of course.  It's getting better, but I
> haven't yet been able to give it a 12-hour bash on the 4-way.  Last time I
> tried a circuit breaker conked; it lasted three hours but even ext3 needs
> electricity.  But three hours is very positive - it was hard testing.
> 
I run many fsx tests on mm2 on 8 way yesterday for a overnight run, 
before I saw your previous post.  Of course the tests failed with lots 
of error messages, but the good news is the system did not hang. Looking 
forward to mm3 out.



  parent reply	other threads:[~2003-05-30 22:23 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-29  8:29 2.5.70-mm2 Andrew Morton
2003-05-29  8:49 ` 2.5.70-mm2 Andrew Morton
2003-05-29 11:23 ` 2.5.70-mm2 Andrew Morton
2003-05-30 20:05   ` 2.5.70-mm2 John Stoffel
2003-05-30 20:30     ` 2.5.70-mm2 Andrew Morton
2003-05-30 20:56       ` 2.5.70-mm2 John Stoffel
2003-05-30 22:36       ` Mingming Cao [this message]
2003-05-29 12:55 ` 2.5.70-mm2 still dies with RAID-1 Helge Hafting
2003-05-29 19:40 ` [patch] 2.5.70-mm2: aha1740.c doesn't compile Adrian Bunk
2003-05-29 20:57 ` 2.5.70-mm2: NCR_D700.c " Adrian Bunk
2003-05-29 21:01   ` James Bottomley
2003-05-29 21:17 ` 2.5.70-mm2: NCR53C9x.c " Adrian Bunk
2003-05-29 21:52 ` 2.5.70-mm2 Badari Pulavarty
2003-05-30 11:17   ` 2.5.70-mm2 Andrew Morton
2003-05-29 22:15 ` 2.5.70-mm2: g_NCR5380 link errors Adrian Bunk
2003-05-30  8:05 ` [patch] 2.5.70-mm2: `__raw_{read,write}ll' undefinded references Adrian Bunk
  -- strict thread matches above, loose matches on Subject: below --
2003-05-29 16:48 2.5.70-mm2 Downing, Thomas
2003-05-29 17:36 ` 2.5.70-mm2 Andrew Morton
2003-05-29 18:45   ` 2.5.70-mm2 Felipe Alfaro Solana
2003-05-29 21:22   ` 2.5.70-mm2 John Stoffel
2003-05-29 21:35     ` 2.5.70-mm2 Andrew Morton
2003-05-29 20:08 ` 2.5.70-mm2 Paul Larson
2003-05-29 19:08 2.5.70-mm2 Downing, Thomas
2003-05-30  7:43 2.5.70-mm2 Boszormenyi Zoltan
2003-05-30  8:27 ` 2.5.70-mm2 Andrew Morton
2003-05-30  8:44   ` 2.5.70-mm2 Christoph Hellwig
2003-05-30  8:59     ` 2.5.70-mm2 Boszormenyi Zoltan
2003-05-30  9:48   ` 2.5.70-mm2 Boszormenyi Zoltan
2003-05-30 10:12     ` 2.5.70-mm2 Boszormenyi Zoltan
2003-05-30 10:33       ` 2.5.70-mm2 Boszormenyi Zoltan

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=3ED7DCF6.20206@us.ibm.com \
    --to=cmm@us.ibm.com \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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