sysrq dump fails looping in ODM module load
Article ID: 100033738
Updated On:
Description
Error Message
insmod: page allocation failure. order:0, mode:0xd2
Pid: 405, comm: insmod Tainted: P --------------- 2.6.32-431.1.2.el6.x86_64 #1
Call Trace:
[] ? __alloc_pages_nodemask+0x757/0x8d0
[] ? thread_return+0x4e/0x76e
[] ? _spin_unlock_irqrestore+0x17/0x20
[] ? alloc_pages_current+0xaa/0x110
[] ? __vmalloc_area_node+0xe6/0x190
[] ? odm_alloc+0x168/0x180 [vxodm]
[] ? __vmalloc_node+0xad/0x120
[] ? odm_alloc+0x168/0x180 [vxodm]
[] ? vmalloc+0x2c/0x30
[] ? odm_alloc+0x168/0x180 [vxodm]
[] ? odm_zalloc+0x1e/0x50 [vxodm]
[] ? odm_io_init+0xed/0x150 [vxodm]
[] ? odminit+0x0/0x1b1 [vxodm]
[] ? odm_kioctl_init+0x95/0xa0 [vxodm]
[] ? odminit+0x90/0x1b1 [vxodm]
[] ? odminit+0x0/0x1b1 [vxodm]
[] ? do_one_initcall+0x3c/0x1d0
[] ? sys_init_module+0xe1/0x250
[] ? system_call_fastpath+0x16/0x1b
Cause
The initrd image has been built to incorrectly load the ODM module. This can be due to a simple rebuild of the kernel or after installing a kernel patch, subsequent to the install of Storage Foundation.
Resolution
The solution is to prevent the ODM module from being installed in the initrd by including it in the blacklist section of the /etc/kdump.conf file. Reference the RedHat documentation for more information on kdump and the /etc/kdump.conf file format. For a configuration example, see the chapter on kdump in the RedHat Enterprise Linux Deployment Guide. The other modules that should be included in the exclude directive are:
vxodm, vxspec, vxio, vxdump, vxportal, fdd, vxfs, vxodm, vxglm, vxfen, gab, llt
Add the line below to the /etc/kdump.conf file:
blacklist vxodm vxspec vxio vxdump vxportal fdd vxfs vxodm vxglm vxfen gab llt
Applies To
Applies to Linux only. First reported on RedHat Enterprise Linux 6.5.
Issue/Introduction
When forcing a crash-dump with sysrq or attempting to save a system core after a panic, the attempt to build a core file fails due to looping in insmod attempting to load modules that should not be included in a crash dump image. In this specific case, the ODM module is involved.
Was this article helpful?
Yes
No
Powered by
