| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <8bd0f97a0705251055n12dab89apbb246a0c82b56ef6@mail.gmail.com> Date: Fri, 25 May 2007 13:55:31 -0400 From: "Mike Frysinger" <vapier.adi@...il.com> To: "Daniel Newby" <daniel.a.newby@...il.com> Cc: "Linux Kernel Mailing List" <linux-kernel@...r.kernel.org> Subject: Re: how to allow board writers to customize driver behavior (watchdog here) On 5/25/07, Daniel Newby <daniel.a.newby@...il.com> wrote: > On 5/24/07, Paul Mundt <lethal@...ux-sh.org> wrote: > > So far the only example anyone has provided outside of periodic timers or > > hardware reset has been dumping the stack when something gets stuck. > > Softlockup does this already today, using a timer. > > Many watchdogs can be hooked up to a non-maskable interrupt (NMI) that > cannot be disabled or preempted. You get a stack dump even for drastic > bugs: ISR lock up, timer misconfiguration, level-sensitive interrupt > line stuck asserted, and so forth. Getting that information by other > means can be painful and/or expensive. > > The Blackfin chip in the original message appears to support watchdog > NMI. it does ... it has four modes: - reset (drivers/char/watchdog/bfin_wdt.c) - interrupt (i'll prob write a clockevents driver for this) - NMI (no plans to do anything for this as NMI is unused in Blackfin) - nothing (have yet to find a use case for this) -mike - 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