On Wednesday, January 23, 2013 11:57:33 am Ian Lepore wrote:
> On Wed, 2013-01-23 at 08:47 -0800, Matthew Jacob wrote:
> > On 1/23/2013 7:25 AM, John Baldwin wrote:
> > > On Tuesday, January 22, 2013 5:40:55 pm Sushanth Rai wrote:
> > >> Hi,
> > >>
> > >> Does freebsd have some functionality simila
On 23 January 2013 11:57, Ian Lepore wrote:
>
> But adding a real hardware watchdog that fires on a slightly longer
> timeout than the NMI watchdog gives you the best of everything: you get
> information if it's possible to produce it, and you get a real hardware
> reset shortly thereafter if prod
On Wed, 2013-01-23 at 08:47 -0800, Matthew Jacob wrote:
> On 1/23/2013 7:25 AM, John Baldwin wrote:
> > On Tuesday, January 22, 2013 5:40:55 pm Sushanth Rai wrote:
> >> Hi,
> >>
> >> Does freebsd have some functionality similar to Linux's NMI watchdog ? I'm
> > aware of ichwd driver, but that depe
On 1/23/2013 7:25 AM, John Baldwin wrote:
On Tuesday, January 22, 2013 5:40:55 pm Sushanth Rai wrote:
Hi,
Does freebsd have some functionality similar to Linux's NMI watchdog ? I'm
aware of ichwd driver, but that depends to WDT to be available in the
hardware. Even when it is available, BIOS
On Tuesday, January 22, 2013 5:40:55 pm Sushanth Rai wrote:
> Hi,
>
> Does freebsd have some functionality similar to Linux's NMI watchdog ? I'm
aware of ichwd driver, but that depends to WDT to be available in the
hardware. Even when it is available, BIOS needs to support a mechanism to
trigg
Hi,
Does freebsd have some functionality similar to Linux's NMI watchdog ? I'm
aware of ichwd driver, but that depends to WDT to be available in the hardware.
Even when it is available, BIOS needs to support a mechanism to trigger a OS
level recovery to get any useful information when system i
6 matches
Mail list logo
