linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Ed Tomlinson <tomlins@cam.org>
To: wli@holomorphy.com, helgehaf@aitel.hist.no,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org, akpm@digeo.com
Subject: Re: 2.5.69-mm2 Kernel panic, possibly network related
Date: Sat, 10 May 2003 08:18:23 -0400	[thread overview]
Message-ID: <20030510121823.7C67EAE6@oscar.casa.dyndns.org> (raw)
In-Reply-To: <fa.clherio.l2of82@ifi.uio.no>

Hi,

I reported one of the bugs.  I now am running mm3 with the rusty fix  
backed out and the two davem fixes applied.  Uptime is over one day.  Looks
to be fixed here.

Thanks
Ed

Jens Axboe wrote:

> On Sat, May 10 2003, William Lee Irwin III wrote:
>> On Thu, May 08 2003, Helge Hafting wrote:
>> >> Much fuzz and two rejects.  Seems there is ongoing netfilter
>> >> work in mm3.
>> 
>> On Thu, May 08, 2003 at 03:37:44PM +0200, Jens Axboe wrote:
>> > akpm applied the patch rusty sent, you'd surely want to back that out
>> > first.
>> > dunno what else is in -mm, the patch reversed without incident on
>> > 2.5-bk as of right now.
>> 
>> It looks like rusty's patch only caught one of two bugs of the same
>> flavor and davem cleaned up the second. It looks like we're in good
>> shape on both fronts from where I'm standing but we should probably
>> wait for all of the original bugreporters to get back to use to
>> declare success on all fronts.
> 
> As I wrote yesterday, bk-current has the fix from Davem that works for
> me.
> 

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

       reply	other threads:[~2003-05-10 12:18 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.f4fihqc.4kq986@ifi.uio.no>
     [not found] ` <fa.clherio.l2of82@ifi.uio.no>
2003-05-10 12:18   ` Ed Tomlinson [this message]
2003-05-07  6:23 2.5.69-mm2 Andrew Morton
2003-05-07 10:10 ` 2.5.69-mm2 Kernel panic, possibly network related Helge Hafting
2003-05-07 10:40   ` David S. Miller
2003-05-07 10:49     ` Helge Hafting
2003-05-07  9:56       ` David S. Miller
2003-05-07 14:41         ` William Lee Irwin III, Helge Hafting
2003-05-07 13:40           ` David S. Miller
2003-05-07 21:54             ` Helge Hafting
2003-05-07 23:24               ` Ed Tomlinson
2003-05-08  1:38               ` William Lee Irwin III
2003-05-08  6:54                 ` Helge Hafting
2003-05-08  7:30                   ` Helge Hafting
2003-05-08  8:01                   ` William Lee Irwin III
2003-05-08 10:07                     ` William Lee Irwin III
2003-05-08 11:04                       ` Helge Hafting
2003-05-11 15:06                         ` William Lee Irwin III
2003-05-08 11:53                       ` Helge Hafting
2003-05-08 12:04                         ` Jens Axboe
2003-05-08 17:21                 ` David S. Miller
2003-05-08 21:34                   ` Ed Tomlinson
2003-05-08 21:53                     ` David S. Miller
2003-05-07 15:20           ` Steven Cole
2003-05-07 15:33             ` William Lee Irwin III
2003-05-09 12:57     ` Bill Davidsen
2003-05-07 12:06   ` William Lee Irwin III

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=20030510121823.7C67EAE6@oscar.casa.dyndns.org \
    --to=tomlins@cam.org \
    --cc=akpm@digeo.com \
    --cc=helgehaf@aitel.hist.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=wli@holomorphy.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox