public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: David Liontooth <liontooth@cogweb.net>
Cc: Randy Dunlap <randy.dunlap@oracle.com>, linux-kernel@vger.kernel.org
Subject: Re: Eeek! page_mapcount(page) went negative! (-1)
Date: Mon, 5 Feb 2007 08:57:37 -0500	[thread overview]
Message-ID: <20070205135737.GB4121@redhat.com> (raw)
In-Reply-To: <45C6CA72.6020206@cogweb.net>

On Sun, Feb 04, 2007 at 10:10:58PM -0800, David Liontooth wrote:

 > > Two things:
 > > a.  Can you try a recent/current kernel to see if this happens?
 > > b.  The "Tainted: GF" means that a module was forcibly loaded.
 > > What module was this?  and is it compatible with a 2.6.16.38 kernel?
 > > Can you reproduce this problem without having that module loaded?
 > >   
 > Randy, thanks for responding. I discovered that the files the script was
 > operating on were corrupt, so let me see if it recurs with healthy files.
 > 
 > It's the lirc module that generates the GF flag --
 > 
 >     lirc_serial: no version for "lirc_unregister_plugin" found: kernel
 > tainted.
 > 
 > So it's not actually forced. I'll remove it if this problem recurs.
 > 
 > I've tried 2.6.18 and 2.6.19 on this box, and they are moderately stable
 > if I use acpi_use_timer_override. It's a production machine, so I can't
 > experiment much.

Which will make it awkward for my suggestion..   The box I was seeing
this on turned out to have hardware problems.  A run of memtest86 may
show up something.  Then again, maybe it won't.  The failing box
I had ran memtest86 for days without incident, despite that the
capacitors on the motherboard were oozing out their goo.

		Dave

-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2007-02-05 13:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-05  2:39 Eeek! page_mapcount(page) went negative! (-1) David Liontooth
2007-02-05  4:48 ` David Liontooth
2007-02-05  5:17   ` Randy Dunlap
2007-02-05  6:10     ` David Liontooth
2007-02-05 13:57       ` Dave Jones [this message]
2007-02-05 16:30       ` Randy Dunlap
  -- strict thread matches above, loose matches on Subject: below --
2006-07-01 17:06 Daniel Drake
2006-07-01 17:07 ` Arjan van de Ven
2006-07-01 17:44   ` Lee Revell
2006-07-01 17:45     ` Arjan van de Ven
2006-07-01 18:11       ` Lee Revell
2006-07-01 21:29         ` Daniel Drake
2006-07-01 17:30 ` Nick Piggin
2006-07-01 18:09   ` Dave Jones
2006-07-01 20:13     ` Alistair John Strachan

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=20070205135737.GB4121@redhat.com \
    --to=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liontooth@cogweb.net \
    --cc=randy.dunlap@oracle.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