From: divya <dipraksh@linux.vnet.ibm.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: libhugetlbfs causes kernel panic on system x machine
Date: Tue, 24 Aug 2010 12:19:16 +0530 [thread overview]
Message-ID: <4C736B6C.5000900@linux.vnet.ibm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1328 bytes --]
Hi,
With 4G memory available on the system x machine
Memory: 3975224k/4980736k available (3764k kernel code, 787208k absent, 218304k reserved, 5318k data, 1272k init)
and by using the attached config file on the kernel versions 2.6.36-rc1 and 2.6.36-rc2
- getting the following panic call trace while running libhugetlbfs autotest
mls21b login: -- 0:conmux-control -- time-stamp -- Aug/21/10 19:52:48 --
-- 0:conmux-control -- time-stamp -- Aug/21/10 20:01:24 --
Kernel panic - not syncing: Out of memory and no killable processes...
Pid: 24576, comm: mmap-cow Not tainted 2.6.36-rc1-git4-autotest #1
Call Trace:
[<ffffffff813a1906>] panic+0x8c/0x196
[<ffffffff810da058>] out_of_memory+0x2e8/0x375
[<ffffffff810de1e6>] __alloc_pages_nodemask+0x556/0x6ac
[<ffffffff81107717>] alloc_page_vma+0x16d/0x18c
[<ffffffff810ef661>] do_wp_page+0x384/0x745
[<ffffffff810ef051>] ? __do_fault+0x412/0x449
[<ffffffff810f1604>] handle_mm_fault+0x959/0x9c2
[<ffffffff813a7379>] do_page_fault+0x38e/0x3b2
[<ffffffff810f7138>] ? do_mmap_pgoff+0x290/0x2f3
[<ffffffff810f72af>] ? sys_mmap_pgoff+0x114/0x126
[<ffffffff813a46df>] page_fault+0x1f/0x30
-- 0:conmux-control -- time-stamp -- Aug/21/10 20:03:24 --
-- 0:conmux-control -- time-stamp -- Aug/21/10 20:11:57 --
(bot:conmon-payload) disconnected
Thanks
Divya
[-- Attachment #2: config_sparsemem_vmemmap --]
[-- Type: text/plain, Size: 3165 bytes --]
CONFIG_FLATMEM=n
CONFIG_DISCONTIGMEM=n
CONFIG_SPARSEMEM=n
CONFIG_SPARSEMEM_EXTREME=n
CONFIG_SPARSEMEM_VMEMMAP=y
CONFIG_USB_STORAGE_CYPRESS_ATACB=n
CONFIG_LOCALVERSION_AUTO=n
CONFIG_LOCALVERSION=""
CONFIG_GROUP_SCHED=y
CONFIG_FAIR_GROUP_SCHED=y
CONFIG_CGROUP_SCHED=y
CONFIG_CGROUPS=y
CONFIG_CGROUP_NS=y
CONFIG_CGROUP_FREEZER=y
CONFIG_CGROUP_DEVICE=y
CONFIG_CPUSETS=y
CONFIG_PROC_PID_CPUSET=y
CONFIG_CGROUP_CPUACCT=y
CONFIG_RESOURCE_COUNTERS=y
CONFIG_CGROUP_MEM_RES_CTLR=y
CONFIG_CGROUP_MEM_RES_CTLR_SWAP=y
CONFIG_MM_OWNER=y
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
CONFIG_USER_NS=y
CONFIG_PID_NS=y
CONFIG_NET_NS=y
CONFIG_LOCALVERSION_AUTO=n
CONFIG_LOCALVERSION=""
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
CONFIG_HOTPLUG=y
CONFIG_KEXEC=y
CONFIG_PM=y
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_EXT4_FS=y
CONFIG_EXT4DEV_COMPAT=y
CONFIG_EXT4_FS_XATTR=y
CONFIG_EXT4_FS_POSIX_ACL=y
CONFIG_EXT4_FS_SECURITY=y
CONFIG_JBD=y
CONFIG_JBD2=y
CONFIG_REISERFS_FS=y
CONFIG_REISERFS_PROC_INFO=y
CONFIG_REISERFS_FS_XATTR=y
CONFIG_REISERFS_FS_POSIX_ACL=y
CONFIG_REISERFS_FS_SECURITY=y
CONFIG_JFS_FS=m
CONFIG_JFS_POSIX_ACL=y
CONFIG_JFS_SECURITY=y
CONFIG_XFS_FS=m
CONFIG_XFS_QUOTA=y
CONFIG_XFS_POSIX_ACL=y
CONFIG_XFS_RT=y
CONFIG_BTRFS_FS=m
CONFIG_BTRFS_FS_POSIX_ACL=y
CONFIG_HUGETLBFS=y
CONFIG_HUGETLB_PAGE=y
CONFIG_PROC_VMCORE=y
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=y
CONFIG_NFS_SWAP=y
CONFIG_NFSD=m
CONFIG_NFSD_V2_ACL=y
CONFIG_NFSD_V3=y
CONFIG_NFSD_V3_ACL=y
CONFIG_NFSD_V4=y
CONFIG_LOCKD=m
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=m
CONFIG_NFS_ACL_SUPPORT=m
CONFIG_NFS_COMMON=y
CONFIG_TASKSTATS=y
CONFIG_TASK_DELAY_ACCT=y
CONFIG_TASK_XACCT=y
CONFIG_TASK_IO_ACCOUNTING=y
CONFIG_TREE_RCU=y
CONFIG_RCU_FANOUT=64
ONFIG_SLAB_ALLOCATOR=y
CONFIG_SLAB=y
CONFIG_DETECT_SOFTLOCKUP=y
CONFIG_DEBUG_SLAB=y
CONFIG_RCU_CPU_STALL_DETECTOR=y
CONFIG_HAVE_DYNAMIC_FTRACE=y
CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y
CONFIG_HAVE_FTRACE_SYSCALLS=y
CONFIG_FTRACE=y
CONFIG_HAVE_KVM=y
CONFIG_HAVE_KVM_IRQCHIP=y
CONFIG_VIRTUALIZATION=y
CONFIG_KVM=y
CONFIG_KVM_AMD=m
CONFIG_KVM_INTEL=m
CONFIG_VIRTIO=y
CONFIG_VIRTIO_RING=y
CONFIG_VIRTIO_PCI=y
CONFIG_VIRTIO_BALLOON=y
CONFIG_VIRTIO_BLK=y
CONFIG_VIRTIO_NET=y
CONFIG_DEVPTS_MULTIPLE_INSTANCES=y
CONFIG_IMA=y
CONFIG_IMA_MEASURE_PCR_IDX=10
CONFIG_IMA_AUDIT=y
CONFIG_IMA_LSM_RULES=y
CONFIG_X86_SUPPORTS_MEMORY_FAILURE=y
CONFIG_ARCH_SUPPORTS_MEMORY_FAILURE=y
CONFIG_MEMORY_FAILURE=y
CONFIG_HWPOISON_INJECT=y
CONFIG_RCU_TORTURE_TEST=y
CONFIG_RCU_TORTURE_TEST_RUNNABLE=y
CONFIG_RCU_CPU_STALL_DETECTOR=y
CONFIG_PERF_EVENTS=y
CONFIG_EVENT_PROFILE=y
CONFIG_PERF_COUNTERS=y
CONFIG_IOSCHED_CFQ=y
CONFIG_GROUP_IOSCHED=y
CONFIG_MEMORY_HOTREMOVE=y
CONFIG_PAGE_MIGRATION=y
CONFIG_KSM=y
CONFIG_KEXEC=y
CONFIG_CRASH_DUMP=y
CONFIG_PHYSICAL_START=0x200000
CONFIG_RELOCATABLE=y
CONFIG_HOTPLUG_CPU=y
CONFIG_PM=y
CONFIG_SUSPEND=y
CONFIG_HIBERNATION=y
CONFIG_PM_RUNTIME=y
CONFIG_ACPI=y
CONFIG_ACPI_PROCFS_POWER=y
CONFIG_ACPI_POWER_METER=m
CONFIG_SYSFS_DEPRECATED_V2=y
CONFIG_IXGBE_DCB=y
CONFIG_DCB=y
reply other threads:[~2010-08-24 6:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4C736B6C.5000900@linux.vnet.ibm.com \
--to=dipraksh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.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.