public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Craig Schlenter <craig.schlenter@absamail.co.za>
To: linux-kernel@vger.kernel.org
Cc: "Martin J. Bligh" <mbligh@aracnet.com>, CaT <cat@zip.com.au>
Subject: Re: Kernel bug in dcache.h:266; 2.5.64, EIP at sysfs_remove_dir
Date: Sun, 9 Mar 2003 20:28:57 +0200	[thread overview]
Message-ID: <20030309182857.GA11703@codefountain.com> (raw)
In-Reply-To: <20030309180732.GA11612@codefountain.com>

On Sun, Mar 09, 2003 at 08:07:32PM +0200, Craig Schlenter wrote:
> On Sun, Mar 09, 2003 at 09:45:30AM -0800, Martin J. Bligh wrote:
> > Look for akpm's latest -mm tree release notes - the patch is embedded
> > in there.
> 
> [I posted a similar oops in another thread]
> 
> Dang! I glossed over that as the comment mentioned SMP and PREEMPT
> and I'm running on uniprocessor. Thanks for the pointer. Will try
> it out shortly ...

Replying to myself :)

The patch was already part of my tree as I had grabbed the latest
bk stuff from v2.5/testing/cset which means my oops is still unresolved.

I see there is a another oops that looks very much that same that
was posted by CaT <cat@zip.com.au> .. CC'ed in case the above notes
help.

Cheers,

--Craig

      parent reply	other threads:[~2003-03-09 18:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-06 19:20 Kernel bug in dcache.h:266; 2.5.64, EIP at sysfs_remove_dir Tomasz Torcz, BG
2003-03-09 17:45 ` Martin J. Bligh
2003-03-09 18:07   ` Patrick Mochel
2003-03-09 20:31     ` Patrick Mochel
2003-03-09 21:34       ` Jeremy Fitzhardinge
2003-03-09 22:06         ` Patrick Mochel
2003-03-09 23:14           ` Jeremy Fitzhardinge
2003-03-10 18:28             ` Craig Schlenter
2003-03-12 23:40           ` CaT
2003-03-12 22:45             ` Patrick Mochel
     [not found]   ` <20030309180732.GA11612@codefountain.com>
2003-03-09 18:28     ` Craig Schlenter [this message]

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=20030309182857.GA11703@codefountain.com \
    --to=craig.schlenter@absamail.co.za \
    --cc=cat@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.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