From: "Martin J. Bligh" <mbligh@google.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: linux-mm <linux-mm@kvack.org>, Andy Whitcroft <apw@shadowen.org>,
Linus Torvalds <torvalds@osdl.org>
Subject: Slab panic on 2.6.19-rc3-git5 (-git4 was OK)
Date: Sat, 28 Oct 2006 22:57:48 -0700 [thread overview]
Message-ID: <454442DC.9050703@google.com> (raw)
-git4 was fine. -git5 is broken (on PPC64 blade)
As -rc2-mm2 seemed fine on this box, I'm guessing it's something
that didn't go via Andrew ;-( Looks like it might be something
JFS or slab specific. Bigger PPC64 box with different config
was OK though.
Full log is here: http://test.kernel.org/abat/59046/debug/console.log
Good -git4 run: http://test.kernel.org/abat/58997/debug/console.log
kernel BUG in cache_grow at mm/slab.c:2705!
cpu 0x1: Vector: 700 (Program Check) at [c0000000fffb7710]
pc: c0000000000c8ad4: .cache_grow+0x64/0x4f0
lr: c0000000000c91a8: .cache_alloc_refill+0x248/0x2cc
sp: c0000000fffb7990
msr: 8000000000021032
current = 0xc0000000fffab800
paca = 0xc00000000047e780
pid = 1, comm = swapper
kernel BUG in cache_grow at mm/slab.c:2705!
enter ? for help
[c0000000fffb7a60] c0000000000c91a8 .cache_alloc_refill+0x248/0x2cc
[c0000000fffb7b20] c0000000000c9708 .kmem_cache_alloc_node+0xd0/0x10c
[c0000000fffb7bc0] c0000000000b69cc .__get_vm_area_node+0xcc/0x230
[c0000000fffb7c70] c0000000000b7640 .__vmalloc_node+0x60/0xc0
[c0000000fffb7d10] c0000000001ad4c8 .txInit+0x2a0/0x3a8
[c0000000fffb7e20] c00000000044c1ec .init_jfs_fs+0x78/0x27c
[c0000000fffb7ec0] c0000000000094c0 .init+0x1f4/0x3e4
[c0000000fffb7f90] c000000000027270 .kernel_thread+0x4c/0x68
WARNING: multiple messages have this Message-ID (diff)
From: "Martin J. Bligh" <mbligh@google.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: linux-mm <linux-mm@kvack.org>, Andy Whitcroft <apw@shadowen.org>,
Linus Torvalds <torvalds@osdl.org>
Subject: Slab panic on 2.6.19-rc3-git5 (-git4 was OK)
Date: Sat, 28 Oct 2006 22:57:48 -0700 [thread overview]
Message-ID: <454442DC.9050703@google.com> (raw)
-git4 was fine. -git5 is broken (on PPC64 blade)
As -rc2-mm2 seemed fine on this box, I'm guessing it's something
that didn't go via Andrew ;-( Looks like it might be something
JFS or slab specific. Bigger PPC64 box with different config
was OK though.
Full log is here: http://test.kernel.org/abat/59046/debug/console.log
Good -git4 run: http://test.kernel.org/abat/58997/debug/console.log
kernel BUG in cache_grow at mm/slab.c:2705!
cpu 0x1: Vector: 700 (Program Check) at [c0000000fffb7710]
pc: c0000000000c8ad4: .cache_grow+0x64/0x4f0
lr: c0000000000c91a8: .cache_alloc_refill+0x248/0x2cc
sp: c0000000fffb7990
msr: 8000000000021032
current = 0xc0000000fffab800
paca = 0xc00000000047e780
pid = 1, comm = swapper
kernel BUG in cache_grow at mm/slab.c:2705!
enter ? for help
[c0000000fffb7a60] c0000000000c91a8 .cache_alloc_refill+0x248/0x2cc
[c0000000fffb7b20] c0000000000c9708 .kmem_cache_alloc_node+0xd0/0x10c
[c0000000fffb7bc0] c0000000000b69cc .__get_vm_area_node+0xcc/0x230
[c0000000fffb7c70] c0000000000b7640 .__vmalloc_node+0x60/0xc0
[c0000000fffb7d10] c0000000001ad4c8 .txInit+0x2a0/0x3a8
[c0000000fffb7e20] c00000000044c1ec .init_jfs_fs+0x78/0x27c
[c0000000fffb7ec0] c0000000000094c0 .init+0x1f4/0x3e4
[c0000000fffb7f90] c000000000027270 .kernel_thread+0x4c/0x68
--
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>
next reply other threads:[~2006-10-29 5:58 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-29 5:57 Martin J. Bligh [this message]
2006-10-29 5:57 ` Slab panic on 2.6.19-rc3-git5 (-git4 was OK) Martin J. Bligh
2006-10-29 6:58 ` Pekka Enberg
2006-10-29 6:58 ` Pekka Enberg
2006-10-29 12:46 ` Giridhar Pemmasani
2006-10-29 12:46 ` Giridhar Pemmasani
2006-10-29 15:21 ` Martin J. Bligh
2006-10-29 15:21 ` Martin J. Bligh
2006-10-29 15:53 ` Giridhar Pemmasani
2006-10-29 15:53 ` Giridhar Pemmasani
2006-10-29 7:05 ` Andrew Morton
2006-10-29 7:05 ` Andrew Morton
2006-10-29 9:17 ` Nick Piggin
2006-10-29 9:17 ` Nick Piggin
2006-10-29 20:53 ` Giridhar Pemmasani
2006-10-29 20:53 ` Giridhar Pemmasani
2006-10-29 17:47 ` Andy Whitcroft
2006-10-29 17:47 ` Andy Whitcroft
2006-10-29 22:59 ` Martin J. Bligh
2006-10-29 22:59 ` Martin J. Bligh
2006-10-30 1:19 ` Linus Torvalds
2006-10-30 1:19 ` Linus Torvalds
2006-10-30 9:53 ` Andy Whitcroft
2006-10-30 9:53 ` Andy Whitcroft
2006-10-30 15:35 ` Andy Whitcroft
2006-10-30 15:35 ` Andy Whitcroft
2006-10-30 15:47 ` Pekka Enberg
2006-10-30 15:47 ` Pekka Enberg
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=454442DC.9050703@google.com \
--to=mbligh@google.com \
--cc=apw@shadowen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.