linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Badari Pulavarty <pbadari@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm <linux-mm@kvack.org>, Andy Whitcroft <apw@shadowen.org>,
	Christoph Lameter <clameter@sgi.com>
Subject: Re: 2.6.21-rc7-mm1 on test.kernel.org
Date: Tue, 24 Apr 2007 16:59:29 -0700	[thread overview]
Message-ID: <1177459170.1281.5.camel@dyn9047017100.beaverton.ibm.com> (raw)
In-Reply-To: <20070424130601.4ab89d54.akpm@linux-foundation.org>

On Tue, 2007-04-24 at 13:06 -0700, Andrew Morton wrote:
> An amd64 machine is crashing badly.
> 
> http://test.kernel.org/abat/84767/debug/console.log
> 
> VFS: Mounted root (ext3 filesystem) readonly.
> Freeing unused kernel memory: 308k freed
> INIT: version 2.86 booting
> Bad page state in process 'init'
> page:ffff81007e492628 flags:0x0100000000000000 mapping:0000000000000000 mapcount:0 count:1
> Trying to fix it up, but a reboot is needed
> Backtrace:
> 
> Call Trace:
>  [<ffffffff80250d3c>] bad_page+0x74/0x10d
>  [<ffffffff80253090>] free_hot_cold_page+0x8d/0x172
...
> 
> So free_pgd_range() is freeing a refcount=1 page.  Can anyone see what
> might be causing this?  The quicklist code impacts this area more than
> anything else..
> 

Yep. quicklist patches are causing these.

making CONFIG_QUICKLIST=n didn't solve the problem. I had
to back out all quicklist patches to make my machine boot.

Thanks,
Badari


--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2007-04-24 23:59 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-24 20:06 Andrew Morton
2007-04-24 20:21 ` Christoph Lameter
2007-04-24 20:27   ` Andrew Morton
2007-04-24 20:32     ` Christoph Lameter
2007-04-24 20:43       ` Andrew Morton
2007-04-24 20:52         ` Christoph Lameter
2007-04-24 21:12           ` Andy Whitcroft
2007-04-24 21:18           ` Andrew Morton
2007-04-24 21:30             ` Christoph Lameter
2007-04-24 21:36               ` Andrew Morton
2007-04-24 21:46                 ` Andy Whitcroft
2007-04-25  0:16                   ` Andy Whitcroft
2007-04-25  0:34                     ` Badari Pulavarty
2007-04-25  0:44                       ` Andy Whitcroft
2007-04-25  1:03                         ` Badari Pulavarty
2007-04-25  6:39                       ` Christoph Lameter
2007-04-25  8:21                         ` Andy Whitcroft
2007-04-25  8:40                           ` Andrew Morton
2007-04-25 15:15                             ` Christoph Lameter
2007-04-24 21:53                 ` Christoph Lameter
2007-04-24 22:27 ` Badari Pulavarty
2007-04-24 22:51   ` Andrew Morton
2007-04-24 23:32     ` Andy Whitcroft
2007-04-25  0:07       ` Andy Whitcroft
2007-04-25  0:51     ` Badari Pulavarty
2007-04-25  1:22       ` Andrew Morton
2007-04-25  6:23         ` Christoph Lameter
2007-04-25  6:38           ` Andrew Morton
2007-04-25  6:58         ` Christoph Lameter
2007-04-25  6:21       ` Christoph Lameter
2007-04-24 23:59 ` Badari Pulavarty [this message]
2007-04-25  1:26   ` Andrew Morton

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=1177459170.1281.5.camel@dyn9047017100.beaverton.ibm.com \
    --to=pbadari@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=apw@shadowen.org \
    --cc=clameter@sgi.com \
    --cc=linux-mm@kvack.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