From: Badari Pulavarty <pbadari@us.ibm.com>
To: Balbir Singh <balbir@in.ibm.com>
Cc: linux-mm <linux-mm@kvack.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: 2.6.28-rc3 mem_cgroup panic
Date: Fri, 07 Nov 2008 14:29:00 -0800 [thread overview]
Message-ID: <1226096940.8805.4.camel@badari-desktop> (raw)
Hi Balbir,
I was running memory remove/add tests in a continuous loop.
I get following panic in mem_cgroup migration code.
Is this a known issue ?
Thanks,
Badari
Unable to handle kernel paging request for data at address 0x027d7d80
Faulting instruction address: 0xc000000000105334
Oops: Kernel access of bad area, sig: 11 [#1]
SMP NR_CPUS=32 NUMA pSeries
Modules linked in:
NIP: c000000000105334 LR: c000000000105314 CTR: c0000000000bf6d0
REGS: c0000000e446b410 TRAP: 0300 Not tainted (2.6.28-rc3)
MSR: 8000000000009032 <EE,ME,IR,DR> CR: 24000448 XER: 00000020
DAR: 00000000027d7d80, DSISR: 0000000040000000
TASK = c0000000e4526cc0[4823] 'drmgr' THREAD: c0000000e4468000 CPU: 0
GPR00: 0000000000000001 c0000000e446b690 c000000000b33f10 00000000027d7d80
GPR04: c000000000105314 c0000000000bf6d0 c0000000eafded40 0000000000000000
GPR08: c000000000bd7fc0 0000000000000008 00000000027d7d80 c000000000bd7000
GPR12: 0000000000004000 c000000000b58300 00000000200957bc 0000000000000000
GPR16: 0000000000000000 c0000000e446b8f8 0000000000000000 c000000000adba20
GPR20: 0000000000000000 0000000000000000 c0000000e4937cb8 00000000000ff000
GPR24: 0000000000000000 00000000000000f2 fffffffffffffff4 c0000000ea10d748
GPR28: c0000000e4937c80 c0000000e4937c80 c000000000aa9bc0 c0000000e446b690
NIP [c000000000105334] .mem_cgroup_prepare_migration+0x70/0x160
LR [c000000000105314] .mem_cgroup_prepare_migration+0x50/0x160
Call Trace:
[c0000000e446b690] [c000000000105314] .mem_cgroup_prepare_migration+0x50/0x160 (unreliable)
[c0000000e446b730] [c000000000102770] .migrate_pages+0x12c/0x62c
[c0000000e446b880] [c000000000100558] .offline_pages+0x398/0x5ac
[c0000000e446b990] [c0000000001007b0] .remove_memory+0x44/0x60
[c0000000e446ba20] [c0000000003fdb90] .memory_block_change_state+0x198/0x230
[c0000000e446bad0] [c0000000003fe2b0] .store_mem_state+0xcc/0x144
[c0000000e446bb70] [c0000000003f0eb8] .sysdev_store+0x74/0xa4
[c0000000e446bc10] [c000000000172d54] .sysfs_write_file+0x128/0x1a4
[c0000000e446bcd0] [c000000000109330] .vfs_write+0xf0/0x1c4
[c0000000e446bd80] [c000000000109ccc] .sys_write+0x6c/0xb8
[c0000000e446be30] [c00000000000852c] syscall_exit+0x0/0x40
Instruction dump:
2f800000 409e00f0 7f83e378 48000871 60000000 48000018 7c210b78 7c421378
e8030000 780907e1 4082fff0 38000001 <7d6018a8> 7d690378 7d2019ad 40a2fff4
---[ end trace 719565d8677c8ae0 ]---
Unable to handle kernel paging request for data at address 0x027d7dd0
Faulting instruction address: 0xc0000000001040f0
Oops: Kernel access of bad area, sig: 11 [#2]
SMP NR_CPUS=32 NUMA pSeries
Modules linked in:
NIP: c0000000001040f0 LR: c0000000001040e4 CTR: c0000000000bf6d0
REGS: c0000000e446aa10 TRAP: 0300 Tainted: G D (2.6.28-rc3)
MSR: 8000000000009032 <EE,ME,IR,DR> CR: 48000428 XER: 00000006
DAR: 00000000027d7dd0, DSISR: 0000000040000000
TASK = c0000000e4526cc0[4823] 'drmgr' THREAD: c0000000e4468000 CPU: 0
GPR00: c0000000001040e4 c0000000e446ac90 c000000000b33f10 00000000027d7dd0
GPR04: c0000000001040e4 c0000000000bf6d0 0000001fdfe40797 0000000000000000
GPR08: c000000000bd7fc0 0000000000000008 00000000027d7dd0 c000000000bd7000
GPR12: c0000000e446ace0 c000000000b58300 c0000000e4382800 00000000100d0000
GPR16: 00000000100d0000 fffffffffffffffb 0000000000000000 00000000100d0000
GPR20: 000000000035eee6 c0000000e7c67b88 c000000000bf2f68 0000000000000000
GPR24: 0000001fdfe40797 c0000000e42ab400 000000001002f000 0000000000000001
GPR28: c0000000e4937cf0 00000000027d7dd0 c000000000aa9bc0 c0000000e446ac90
NIP [c0000000001040f0] .__mem_cgroup_uncharge_common+0x60/0x20c
LR [c0000000001040e4] .__mem_cgroup_uncharge_common+0x54/0x20c
Call Trace:
[c0000000e446ac90] [c0000000001040e4] .__mem_cgroup_uncharge_common+0x54/0x20c (unreliable)
[c0000000e446ad30] [c0000000001045a0] .mem_cgroup_uncharge_page+0x50/0x68
[c0000000e446adc0] [c0000000000e50f0] .page_remove_rmap+0x190/0x1d4
[c0000000e446ae50] [c0000000000da8c8] .unmap_vmas+0x528/0x8f4
[c0000000e446af90] [c0000000000e0890] .exit_mmap+0xf0/0x1cc
[c0000000e446b040] [c0000000000640b0] .mmput+0x78/0x164
[c0000000e446b0e0] [c00000000006983c] .exit_mm+0x1a8/0x1d0
[c0000000e446b190] [c00000000006b6c8] .do_exit+0x22c/0x880
[c0000000e446b260] [c0000000000294d0] .die+0x1d0/0x1d4
[c0000000e446b310] [c0000000000312d8] .bad_page_fault+0xc8/0xe8
[c0000000e446b3a0] [c000000000005198] handle_page_fault+0x3c/0x5c
--- Exception: 300 at .mem_cgroup_prepare_migration+0x70/0x160
LR = .mem_cgroup_prepare_migration+0x50/0x160
[c0000000e446b730] [c000000000102770] .migrate_pages+0x12c/0x62c
[c0000000e446b880] [c000000000100558] .offline_pages+0x398/0x5ac
[c0000000e446b990] [c0000000001007b0] .remove_memory+0x44/0x60
[c0000000e446ba20] [c0000000003fdb90] .memory_block_change_state+0x198/0x230
[c0000000e446bad0] [c0000000003fe2b0] .store_mem_state+0xcc/0x144
[c0000000e446bb70] [c0000000003f0eb8] .sysdev_store+0x74/0xa4
[c0000000e446bc10] [c000000000172d54] .sysfs_write_file+0x128/0x1a4
[c0000000e446bcd0] [c000000000109330] .vfs_write+0xf0/0x1c4
[c0000000e446bd80] [c000000000109ccc] .sys_write+0x6c/0xb8
[c0000000e446be30] [c00000000000852c] syscall_exit+0x0/0x40
Instruction dump:
7c9b2378 4bf04d99 60000000 e93e8018 80090060 2f800000 409e019c 7f83e378
48001aa1 60000000 7c7d1b79 41820188 <e81d0000> 7809f7e3 40a2001c 48000178
---[ end trace 719565d8677c8ae0 ]---
Fixing recursive fault but reboot is needed!
WARNING: multiple messages have this Message-ID (diff)
From: Badari Pulavarty <pbadari@us.ibm.com>
To: Balbir Singh <balbir@in.ibm.com>
Cc: linux-mm <linux-mm@kvack.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: 2.6.28-rc3 mem_cgroup panic
Date: Fri, 07 Nov 2008 14:29:00 -0800 [thread overview]
Message-ID: <1226096940.8805.4.camel@badari-desktop> (raw)
Hi Balbir,
I was running memory remove/add tests in a continuous loop.
I get following panic in mem_cgroup migration code.
Is this a known issue ?
Thanks,
Badari
Unable to handle kernel paging request for data at address 0x027d7d80
Faulting instruction address: 0xc000000000105334
Oops: Kernel access of bad area, sig: 11 [#1]
SMP NR_CPUS=32 NUMA pSeries
Modules linked in:
NIP: c000000000105334 LR: c000000000105314 CTR: c0000000000bf6d0
REGS: c0000000e446b410 TRAP: 0300 Not tainted (2.6.28-rc3)
MSR: 8000000000009032 <EE,ME,IR,DR> CR: 24000448 XER: 00000020
DAR: 00000000027d7d80, DSISR: 0000000040000000
TASK = c0000000e4526cc0[4823] 'drmgr' THREAD: c0000000e4468000 CPU: 0
GPR00: 0000000000000001 c0000000e446b690 c000000000b33f10 00000000027d7d80
GPR04: c000000000105314 c0000000000bf6d0 c0000000eafded40 0000000000000000
GPR08: c000000000bd7fc0 0000000000000008 00000000027d7d80 c000000000bd7000
GPR12: 0000000000004000 c000000000b58300 00000000200957bc 0000000000000000
GPR16: 0000000000000000 c0000000e446b8f8 0000000000000000 c000000000adba20
GPR20: 0000000000000000 0000000000000000 c0000000e4937cb8 00000000000ff000
GPR24: 0000000000000000 00000000000000f2 fffffffffffffff4 c0000000ea10d748
GPR28: c0000000e4937c80 c0000000e4937c80 c000000000aa9bc0 c0000000e446b690
NIP [c000000000105334] .mem_cgroup_prepare_migration+0x70/0x160
LR [c000000000105314] .mem_cgroup_prepare_migration+0x50/0x160
Call Trace:
[c0000000e446b690] [c000000000105314] .mem_cgroup_prepare_migration+0x50/0x160 (unreliable)
[c0000000e446b730] [c000000000102770] .migrate_pages+0x12c/0x62c
[c0000000e446b880] [c000000000100558] .offline_pages+0x398/0x5ac
[c0000000e446b990] [c0000000001007b0] .remove_memory+0x44/0x60
[c0000000e446ba20] [c0000000003fdb90] .memory_block_change_state+0x198/0x230
[c0000000e446bad0] [c0000000003fe2b0] .store_mem_state+0xcc/0x144
[c0000000e446bb70] [c0000000003f0eb8] .sysdev_store+0x74/0xa4
[c0000000e446bc10] [c000000000172d54] .sysfs_write_file+0x128/0x1a4
[c0000000e446bcd0] [c000000000109330] .vfs_write+0xf0/0x1c4
[c0000000e446bd80] [c000000000109ccc] .sys_write+0x6c/0xb8
[c0000000e446be30] [c00000000000852c] syscall_exit+0x0/0x40
Instruction dump:
2f800000 409e00f0 7f83e378 48000871 60000000 48000018 7c210b78 7c421378
e8030000 780907e1 4082fff0 38000001 <7d6018a8> 7d690378 7d2019ad 40a2fff4
---[ end trace 719565d8677c8ae0 ]---
Unable to handle kernel paging request for data at address 0x027d7dd0
Faulting instruction address: 0xc0000000001040f0
Oops: Kernel access of bad area, sig: 11 [#2]
SMP NR_CPUS=32 NUMA pSeries
Modules linked in:
NIP: c0000000001040f0 LR: c0000000001040e4 CTR: c0000000000bf6d0
REGS: c0000000e446aa10 TRAP: 0300 Tainted: G D (2.6.28-rc3)
MSR: 8000000000009032 <EE,ME,IR,DR> CR: 48000428 XER: 00000006
DAR: 00000000027d7dd0, DSISR: 0000000040000000
TASK = c0000000e4526cc0[4823] 'drmgr' THREAD: c0000000e4468000 CPU: 0
GPR00: c0000000001040e4 c0000000e446ac90 c000000000b33f10 00000000027d7dd0
GPR04: c0000000001040e4 c0000000000bf6d0 0000001fdfe40797 0000000000000000
GPR08: c000000000bd7fc0 0000000000000008 00000000027d7dd0 c000000000bd7000
GPR12: c0000000e446ace0 c000000000b58300 c0000000e4382800 00000000100d0000
GPR16: 00000000100d0000 fffffffffffffffb 0000000000000000 00000000100d0000
GPR20: 000000000035eee6 c0000000e7c67b88 c000000000bf2f68 0000000000000000
GPR24: 0000001fdfe40797 c0000000e42ab400 000000001002f000 0000000000000001
GPR28: c0000000e4937cf0 00000000027d7dd0 c000000000aa9bc0 c0000000e446ac90
NIP [c0000000001040f0] .__mem_cgroup_uncharge_common+0x60/0x20c
LR [c0000000001040e4] .__mem_cgroup_uncharge_common+0x54/0x20c
Call Trace:
[c0000000e446ac90] [c0000000001040e4] .__mem_cgroup_uncharge_common+0x54/0x20c (unreliable)
[c0000000e446ad30] [c0000000001045a0] .mem_cgroup_uncharge_page+0x50/0x68
[c0000000e446adc0] [c0000000000e50f0] .page_remove_rmap+0x190/0x1d4
[c0000000e446ae50] [c0000000000da8c8] .unmap_vmas+0x528/0x8f4
[c0000000e446af90] [c0000000000e0890] .exit_mmap+0xf0/0x1cc
[c0000000e446b040] [c0000000000640b0] .mmput+0x78/0x164
[c0000000e446b0e0] [c00000000006983c] .exit_mm+0x1a8/0x1d0
[c0000000e446b190] [c00000000006b6c8] .do_exit+0x22c/0x880
[c0000000e446b260] [c0000000000294d0] .die+0x1d0/0x1d4
[c0000000e446b310] [c0000000000312d8] .bad_page_fault+0xc8/0xe8
[c0000000e446b3a0] [c000000000005198] handle_page_fault+0x3c/0x5c
--- Exception: 300 at .mem_cgroup_prepare_migration+0x70/0x160
LR = .mem_cgroup_prepare_migration+0x50/0x160
[c0000000e446b730] [c000000000102770] .migrate_pages+0x12c/0x62c
[c0000000e446b880] [c000000000100558] .offline_pages+0x398/0x5ac
[c0000000e446b990] [c0000000001007b0] .remove_memory+0x44/0x60
[c0000000e446ba20] [c0000000003fdb90] .memory_block_change_state+0x198/0x230
[c0000000e446bad0] [c0000000003fe2b0] .store_mem_state+0xcc/0x144
[c0000000e446bb70] [c0000000003f0eb8] .sysdev_store+0x74/0xa4
[c0000000e446bc10] [c000000000172d54] .sysfs_write_file+0x128/0x1a4
[c0000000e446bcd0] [c000000000109330] .vfs_write+0xf0/0x1c4
[c0000000e446bd80] [c000000000109ccc] .sys_write+0x6c/0xb8
[c0000000e446be30] [c00000000000852c] syscall_exit+0x0/0x40
Instruction dump:
7c9b2378 4bf04d99 60000000 e93e8018 80090060 2f800000 409e019c 7f83e378
48001aa1 60000000 7c7d1b79 41820188 <e81d0000> 7809f7e3 40a2001c 48000178
---[ end trace 719565d8677c8ae0 ]---
Fixing recursive fault but reboot is needed!
--
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:[~2008-11-07 22:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-07 22:29 Badari Pulavarty [this message]
2008-11-07 22:29 ` 2.6.28-rc3 mem_cgroup panic Badari Pulavarty
2008-11-08 2:24 ` KAMEZAWA Hiroyuki
2008-11-08 2:24 ` KAMEZAWA Hiroyuki
2008-11-08 2:46 ` KAMEZAWA Hiroyuki
2008-11-08 2:46 ` KAMEZAWA Hiroyuki
2008-11-08 5:00 ` Badari Pulavarty
2008-11-08 5:00 ` Badari Pulavarty
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=1226096940.8805.4.camel@badari-desktop \
--to=pbadari@us.ibm.com \
--cc=balbir@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.