linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Helge Hafting <helgehaf@aitel.hist.no>
To: William Lee Irwin III <wli@holomorphy.com>,
	Helge Hafting <helgehaf@aitel.hist.no>,
	"David S. Miller" <davem@redhat.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org, akpm@digeo.com
Subject: Re: 2.5.69-mm2 Kernel panic, possibly network related
Date: Thu, 8 May 2003 08:54:40 +0200	[thread overview]
Message-ID: <20030508065440.GA1890@hh.idb.hist.no> (raw)
In-Reply-To: <20030508013854.GW8931@holomorphy.com>

On Wed, May 07, 2003 at 06:38:54PM -0700, William Lee Irwin III wrote:
[...] 
> Can you try one kernel with the netfilter cset backed out, and another
> with the re-slabification patch backed out? (But not with both backed
> out simultaneously).

I'm compiling without reslabify now.
I got 
patching file arch/i386/mm/pageattr.c
Hunk #1 succeeded at 67 (offset 9 lines).
when backing it out - is this the effect of
some other patch touching the same file or could
my source be wrong somehow?

Which patch is the netfilter cset?  None of
the patches in mm2 looked obvious to me.  Or
is it part of the linus patch? Note that mm1
works for me, so anything found there too
isn't as likely to be the problem.

Helge Hafting

  reply	other threads:[~2003-05-08  6:39 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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
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 [this message]
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 13:39                           ` Helge Hafting
2003-05-08 13:37                             ` Jens Axboe
2003-05-10  7:03                               ` William Lee Irwin III
2003-05-10  7:30                                 ` Jens Axboe
2003-05-08 17:39                             ` William Lee Irwin III
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-09 17:42       ` Helge Hafting
2003-05-07 12:06   ` William Lee Irwin III
2003-05-09 18:56 J. Hidding
     [not found] <fa.f4fihqc.4kq986@ifi.uio.no>
     [not found] ` <fa.clherio.l2of82@ifi.uio.no>
2003-05-10 12:18   ` Ed Tomlinson

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=20030508065440.GA1890@hh.idb.hist.no \
    --to=helgehaf@aitel.hist.no \
    --cc=akpm@digeo.com \
    --cc=davem@redhat.com \
    --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;
as well as URLs for NNTP newsgroup(s).