public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Ian Jackson <ijackson@chiark.greenend.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux 2.2.18pre17 + VM-global -7 = `Negative d_count' oops
Date: Fri, 27 Oct 2000 01:05:39 +0200	[thread overview]
Message-ID: <20001027010539.B1282@athlon.random> (raw)
In-Reply-To: <39F4AB91.72F2C300@transmeta.com> <20001025050631.A6817@athlon.random> <14840.27617.448792.438567@chiark.greenend.org.uk>
In-Reply-To: <14840.27617.448792.438567@chiark.greenend.org.uk>; from ijackson@chiark.greenend.org.uk on Thu, Oct 26, 2000 at 06:37:37PM +0100

On Thu, Oct 26, 2000 at 06:37:37PM +0100, Ian Jackson wrote:
>  Negative d_count (-805538369) for [binary garbage]/<NULL>
> 
> followed by an oops.  Kernel logfile extract below, uuencoded.

Thanks for the feedback.

The oops is forced by the kernel after it sees then wrong negative d_count.

I'd say it's memory corruption, but it doesn't look like a memory bitflip.

I'm almost certain that it's not caused by the VM-global patch.

Which device driver and compiler are you using?

Andrea
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-10-26 23:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <39F4AB91.72F2C300@transmeta.com>
     [not found] ` <20001025050631.A6817@athlon.random>
2000-10-26 17:37   ` linux 2.2.18pre17 + VM-global -7 = `Negative d_count' oops Ian Jackson
2000-10-26 23:05     ` Andrea Arcangeli [this message]
2000-10-27 11:14       ` Ian Jackson
2000-10-27 15:42         ` Andrea Arcangeli

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=20001027010539.B1282@athlon.random \
    --to=andrea@suse.de \
    --cc=ijackson@chiark.greenend.org.uk \
    --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