From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Shuklin Subject: Re: linux crash behavior Date: Wed, 17 Aug 2011 15:46:39 +0400 Message-ID: <1313581599.2116.18.camel@mabase> References: <1313579697.2116.14.camel@mabase> <4E4BA436.1020203@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Return-path: In-Reply-To: <4E4BA436.1020203@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Andrew Cooper Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org В Срд, 17/08/2011 в 12:21 +0100, Andrew Cooper пишет: > On 17/08/11 12:14, George Shuklin wrote: > > Good day. > > > > I found that xen_panic_event (in arch/x86/xen/enlighten.c) ignore sysctl > > settings for kernel.panic, which declare delay between crash and crash > > consequences. > > Is this dom0 or domU, and which Xen and Linux version? I think this apply to domU and dom0. I saw this in source of vanilla 3.0/3.1rc2, and I saw this behaivor in 2.6.34-xen (suse kernel), and even it 2.6.18-xen (rhel5.5 kernel). http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=blob_plain;f=arch/x86/xen/enlighten.c;hb=HEAD static void xen_crash_shutdown(struct pt_regs *regs) { xen_reboot(SHUTDOWN_crash); } static int xen_panic_event(struct notifier_block *this, unsigned long event, void *ptr) { xen_reboot(SHUTDOWN_crash); return NOTIFY_DONE; }