I had looked at this. It seems to be doing the opposite of what I want. That 
is, it routes a NMI as an SMI and I need SMI to trigger an NMI. Watchdog timer 
on 3100 chipset had the ability to send either an NMI or SMI when the timer 
fired for the first time. I used NMI to generate kernel panic. With 3400 no 
longer generating NMI on WDT expiry, I'm trying to figure out how I can force 
memory dump on watchdog expiry.

Sushanth
 
--- On Sat, 2/11/12, Andriy Gapon <a...@freebsd.org> wrote:

> From: Andriy Gapon <a...@freebsd.org>
> Subject: Re: Generating NMI due to WDT expiry
> To: "Sushanth Rai" <sushanth_...@yahoo.com>
> Cc: freebsd-hackers@FreeBSD.org
> Date: Saturday, February 11, 2012, 3:06 AM
> on 11/02/2012 00:42 Sushanth Rai said
> the following:
> > Basically I would like to force system panic (and take
> kernel dump) when
> > watchdog time expires. Assuming that timer expired due
> to some OS bug, kernel
> > memory dump would be very useful. I'm running freebsd
> 7.2 on Intel IbexPeak
> > chipset. According to specs, the watchdog timer on
> IbexPeak first generates
> > an SMI and then resets the CPU. Since SMI is handled
> within the BIOS, is
> > there a way to generate NMI from within BIOS SMI
> handler ? I see that kernel
> > has support to either enter the debugger or force panic
> upon receipt of a
> > NMI.
> > 
> > This is not necessarily a FreeBSD question, but would
> like to hear any
> > thoughts/pointers.
> 
> See this:
> http://www.intel.com/content/dam/doc/datasheet/5-chipset-3400-chipset-datasheet.pdf
> Search for NMI2SMI_EN.  Maybe it's what you want.
> 
> 
> -- 
> Andriy Gapon
> _______________________________________________
> freebsd-hackers@freebsd.org
> mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
>
_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"

Reply via email to