linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andre Noll <maan@systemlinux.org>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, andrea@suse.de,
	riel@redhat.com
Subject: Re: 2.6.18: Kernel BUG at mm/rmap.c:522
Date: Wed, 4 Oct 2006 17:42:27 +0200	[thread overview]
Message-ID: <20061004154227.GD22487@skl-net.de> (raw)
In-Reply-To: <4523BE45.5050205@yahoo.com.au>

[-- Attachment #1: Type: text/plain, Size: 985 bytes --]

On 23:59, Nick Piggin wrote:

> Ah, this old thing. I hope it is repeatable?

Well, it happened on both of the new machines we got last week. One
of these is still up BTW and I'm able to ssh into it.

> What we really want is the bit before this, the "Eeek! page_mapcount went
> negative" part.

There's no such message in the log. The preceeding lines are just normal
startup messages:

	Adding 16779852k swap on /dev/sda1.  Priority:42 extents:1 across:16779852k
	Adding 16779852k swap on /dev/sdb1.  Priority:42 extents:1 across:16779852k
	process `syslogd' is using obsolete setsockopt SO_BSDCOMPAT

> It is also nice if we can work out where the page actually came from. The
> following attached patch should help out a bit with that, if you could
> run with it?

Okay. I'll reboot with your patch and let you know if it crashes again.

Thanks for the quick response.
Andre
-- 
The only person who always got his work done by Friday was Robinson Crusoe

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-10-04 15:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-04 10:40 Andre Noll
2006-10-04 13:59 ` Nick Piggin
2006-10-04 15:42   ` Andre Noll [this message]
2006-10-04 15:49     ` Peter Zijlstra
2006-10-04 16:12       ` Andre Noll
2006-10-04 20:39       ` Dave Jones
2006-10-05  6:28         ` Nick Piggin

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=20061004154227.GD22487@skl-net.de \
    --to=maan@systemlinux.org \
    --cc=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=riel@redhat.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