linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: naveen yadav <yad.naveen@gmail.com>
To: linux-arm-kernel@lists.infradead.org,
	linux-mm <linux-mm@kvack.org>,
	linux newbie <linux.newbie79@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Fwd: [ARM]crash on 2.6.35.11
Date: Wed, 4 May 2011 15:46:55 +0530	[thread overview]
Message-ID: <BANLkTi=oZ0Mr33rL=QNmzDuaKLNezoKBXg@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimLd-qY-OeKqnf2EoTfvAHWQZVchw@mail.gmail.com>

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

Attaching test case

Dear all,

We are running linux kernel 2.6.35.11 on Cortex a-8. when I run a
simple program expect to give oom.
 But it crash with following crash log

./DiffSize

BUG: Bad page state in process DiffSize  pfn:50769c
page:c9907380 count:892679477 mapcount:892679478 mapping:35353535
index:0x35353535
page flags: 0x35353535(locked|referenced|dirty|lru|owner_priv_1|reserved|private_2|writeback|swapcache|reclaim|swapbacked|unevictable)
Backtrace:
[<c0023b90>] (dump_backtrace+0x0/0x110) from [<c02de8f0>] (dump_stack+0x18/0x1c)
 r6:c9907380 r5:c040674c r4:c9907380 r3:00000000
[<c02de8d8>] (dump_stack+0x0/0x1c) from [<c007b60c>] (bad_page+0xe0/0x10c)
[<c007b52c>] (bad_page+0x0/0x10c) from [<c007c864>]
(get_page_from_freelist+0x364/0x4bc)
 r5:c03cd21c r4:00000000
[<c007c500>] (get_page_from_freelist+0x0/0x4bc) from [<c007cac8>]
(__alloc_pages_nodemask+0x10c/0x578)
[<c007c9bc>] (__alloc_pages_nodemask+0x0/0x578) from [<c008b3e0>]
(handle_mm_fault+0x218/0xd68)
[<c008b1c8>] (handle_mm_fault+0x0/0xd68) from [<c0026514>]
(do_page_fault+0x10c/0x200)
[<c0026408>] (do_page_fault+0x0/0x200) from [<c001f2bc>]
(do_DataAbort+0x3c/0xa0)
[<c001f280>] (do_DataAbort+0x0/0xa0) from [<c001ff24>]
(ret_from_exception+0x0/0x10)
Exception stack(0xc9281fb0 to 0xc9281ff8)
1fa0:                                     48166008 00000035 50166008 35353535
1fc0: 072be000 35353535 48ea7f88 4001f080 00000000 00000000 be87e880 be87e86c
1fe0: 48ea8008 be87e844 00008514 400b449c 20000010 ffffffff
 r7:4001f080 r6:48ea7f88 r5:35353535 r4:ffffffff
Disabling lock debugging due to kernel taint

regards
Naveen

[-- Attachment #2: DiffAllocs.c --]
[-- Type: text/x-csrc, Size: 367 bytes --]

#include <stdio.h>
#include <malloc.h>
#include <string.h>

#define SIZE 4096
#define START_SIZE 1024
char *ptr[1000];

int main(int argc, char **argv)
{
	int i=0;
	unsigned int alloc_size = START_SIZE;	
	sleep(5);
	while(i<1000)
	{
		
		ptr[i] = (char*) malloc(alloc_size);
		if(ptr[i])
			memset(ptr[i],'5',alloc_size);	
		alloc_size *= 2;

		i++;
		sleep(5);
	}
}

  reply	other threads:[~2011-05-04 10:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-04 10:09 [ARM]crash on 2.6.35.11 naveen yadav
2011-05-04 10:16 ` naveen yadav [this message]
2011-05-11 19:36   ` Fwd: " Russell King - ARM Linux
2011-05-04 10:25 ` Catalin Marinas
2011-05-04 13:18   ` naveen yadav
2011-05-04 14:21     ` Catalin Marinas

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='BANLkTi=oZ0Mr33rL=QNmzDuaKLNezoKBXg@mail.gmail.com' \
    --to=yad.naveen@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux.newbie79@gmail.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;
as well as URLs for NNTP newsgroup(s).