Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 10 Mar 2003 00:18:01 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 10 Mar 2003 00:18:01 -0500 Received: from fmr05.intel.com ([134.134.136.6]:56826 "EHLO hermes.jf.intel.com") by vger.kernel.org with ESMTP id ; Mon, 10 Mar 2003 00:18:00 -0500 Subject: Re: Available watchdog test cases From: Rusty Lynch To: Paul Rolland Cc: "'Paul Larson'" , "'lkml'" In-Reply-To: <008501c2e61f$fdd0a800$2101a8c0@witbe> References: <008501c2e61f$fdd0a800$2101a8c0@witbe> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Date: 09 Mar 2003 21:23:08 -0800 Message-Id: <1047273790.6399.13.camel@vmhack> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 714 Lines: 21 On Sun, 2003-03-09 at 01:40, Paul Rolland wrote: > Just a quick question : is there an easy to force the kernel to Oops, > to make sure that the watchdog will even be working under such > conditions ? > > I know people are all trying to avoid Oops... but I think the testplan > should include that too... > > Regards, > Paul You can write a kernel module that when loaded will disable all interrupts and sit and spin, or even easier just call panic(). --rustyl - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/