From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-iy0-f177.google.com ([209.85.210.177]) by merlin.infradead.org with esmtps (Exim 4.76 #1 (Red Hat Linux)) id 1Rnmi1-0002F4-Rb for kexec@lists.infradead.org; Thu, 19 Jan 2012 07:46:58 +0000 Received: by iagw33 with SMTP id w33so1996008iag.36 for ; Wed, 18 Jan 2012 23:46:56 -0800 (PST) Message-ID: <4F17CA71.6040405@gmail.com> Date: Wed, 18 Jan 2012 23:46:57 -0800 From: Jay Lan MIME-Version: 1.0 Subject: kdump kernel tried to load modules not included in the kdump initrd? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: kexec-bounces@lists.infradead.org Errors-To: kexec-bounces+dwmw2=infradead.org@lists.infradead.org To: "kexec@lists.infradead.org" Hi, I have a 2.6.32-131.6.1.el6 kernel, and kexec-tools-2.0.0-145.el6.x86_64 rpm on a cent6 machine. When i forced a kdump by 'echo c > /proc/sysrq-trigger', the kdump kernel panicked during the boot. Surprisingly, it tried to load lustre modules that should not be part of the initrd and panicked! The syslog showed the --initrd specified a kdump.img when kdump was started. I dumped out the kdump.img (with zcat) and verified that no lustre module was included in the initrd image. So, how did this have happened? Thanks, Jay _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec