Date: Thu, 7 Jul 2005 10:21:56 +0930 From: "Wilkinson, Alex" <alex.wilkinson@dsto.defence.gov.au> To: Scott Long <scottl@samsco.org> Cc: freebsd-current@freebsd.org, Mike Tancsa <mike@sentex.net> Subject: Re: 6.0-CURRENT SNAP004 hangs on amr (long) Message-ID: <20050707005155.GC7289@squash.dsto.defence.gov.au> In-Reply-To: <42CC1085.6090504@samsco.org> References: <42C6DA5F.9070303@gneto.com> <6.2.1.2.0.20050703212843.07889088@64.7.153.2> <20050705011650.R80892@lexi.siliconlandmark.com> <70e8236f050706002655cd9a0c@mail.gmail.com> <42CBE7F4.9040106@samsco.org> <83fb4207210a3f028b8ee2d2289573c4@xcllnt.net> <42CBFC36.1040406@samsco.org> <6.2.1.2.0.20050706115146.07a59d08@64.7.153.2> <6.2.1.2.0.20050706115824.07a58588@64.7.153.2> <42CC1085.6090504@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
0n Wed, Jul 06, 2005 at 11:10:29AM -0600, Scott Long wrote:
>I wonder if the AMR interrupt is getting routed to the ata interrupt
>pins. With the ata driver enabled, the OS gets stuck in an infinite
>loop of trying to service what it thinks in an ata interrupt. With
>the ata driver disabled, the ata interrupt lines stay disabled and the
>OS sees nothing. Would it be possible to send an NMI to the machine
>while it's hung with the ata driver enabled? If not, we can probably
>drop some simple printf into the ata interrupt handler.
Curious, how does one send a Non-Maskable-Interupt in FreeBSD ?
-aW
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050707005155.GC7289>