linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Tilman Schmidt <tilman@imap.cc>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Nick Piggin <nickpiggin@yahoo.com.au>,
	Hugh Dickins <hugh@veritas.com>,
	Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: 2.6.21-rc7-mm2 crash: Eeek! page_mapcount(page) went negative! (-1)
Date: Mon, 30 Apr 2007 19:17:02 +0200	[thread overview]
Message-ID: <4636248E.7030309@imap.cc> (raw)
In-Reply-To: <20070428141024.887342bd.akpm@linux-foundation.org>

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

>> With kernel 2.6.21-rc7-mm2, my Dell Optiplex GX110 (P3/933) regularly
>> crashes during the SuSE 10.1 startup sequence. When booting to RL5,
>> it panicblinks shortly after the graphical login screen appears.
>> Booting to RL3, it hangs after the startup message:

I have now bisected this down to the section in the series file between
#GREGKH-DRIVER-START and #GREGKH-DRIVER-END, and therefore added GregKH
to the CC list. I'll try bisecting further inside that section (unless
you tell me not to), but it may take some time.

The exact point during the startup sequence when the crash occurred and
the amount of BUG messages produced varied somewhat during these tests.
The common denominator, and my criterion for the good/bad decisions
during the bisect, was the crash (panic blink) just before completion
of the system startup.
Sometimes there weren't any BUG messages in the log (or perhaps they
just didn't make it to the disk.) Sometimes I just had a couple of the
"sleeping function called from invalid context at mm/slab.c:3054"
ones but no "Eeek! page_mapcount(page) went negative!" one before them.
However, whenever the "Eeek!" did appear it announced "getcfg-interfac"
as the current process and was followed by a few of the "mm/slab.c:3054"
ones.

HTH
Tilman

-- 
In the long run, we'll all be dead.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 253 bytes --]

  parent reply	other threads:[~2007-04-30 17:17 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070425225716.8e9b28ca.akpm@linux-foundation.org>
     [not found] ` <46338AEB.2070109@imap.cc>
2007-04-28 21:10   ` Andrew Morton
2007-04-28 22:06     ` Hugh Dickins
2007-04-30 17:17     ` Tilman Schmidt [this message]
2007-04-30 18:21       ` Andrew Morton
2007-04-30 19:28         ` Tilman Schmidt
2007-04-30 19:46           ` Andrew Morton
2007-04-30 21:32             ` Tilman Schmidt
2007-05-01 11:26             ` Tilman Schmidt
2007-05-02  3:10               ` Greg KH
2007-05-02  7:01             ` Tilman Schmidt
2007-05-02  7:02               ` Greg KH
2007-05-02  7:10               ` Andrew Morton
2007-05-02  7:28                 ` Greg KH
2007-05-02  7:43                 ` Greg KH
2007-05-02  9:41                   ` Tilman Schmidt
2007-05-02 22:06                     ` Greg KH
2007-05-02 12:14                   ` Kay Sievers
2007-05-02  7:52                 ` Greg KH
2007-05-02 17:36                   ` Tilman Schmidt
2007-05-02 20:07                     ` Andrew Morton
2007-05-02 21:22                       ` Tilman Schmidt
2007-05-02  7:10               ` 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=4636248E.7030309@imap.cc \
    --to=tilman@imap.cc \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@suse.de \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=nickpiggin@yahoo.com.au \
    /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