[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AE4F746F2AECFC4DA4AADD66A1DFEF01A551D3@otce2k301.adaptec.com>
Date: Wed, 30 May 2007 17:49:01 -0400
From: "Salyzyn, Mark" <mark_salyzyn@...ptec.com>
To: "Yinghai Lu" <yhlu.kernel@...il.com>
Cc: "Andrew Morton" <akpm@...ux-foundation.org>,
"Vivek Goyal" <vgoyal@...ibm.com>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
<linux-scsi@...r.kernel.org>,
"Michal Piotrowski" <michal.k.k.piotrowski@...il.com>
Subject: RE: kexec and aacraid broken
Yinghai Lu [mailto:yhlu.kernel@...il.com] writes:
> aacraid_commit_reset.patch is in the mainline already.
But aacraid_commit_reset.patch is not in 2.6.22-rc3 (to which you report
the issue). Does the aacraid_commit_reset.patch work to resolve this
issue all by itself in the kexec'd kernel? Or alternatively did you try
aacraid.startup_timeout=540 as one of the kernel parameters passed to
the kexec'd kernel?
The '[PATCH] aacraid: fix shutdown handler to also disable interrupts'
patch (you refer to this as patch 4) is not to be in the picture because
it will hide the root cause. I believe I have you correct in stating
that this patch (4) resolves the problem... but I expect the problem to
remain with kdump.
Sincerely -- Mark Salyzyn
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists