Date: Sat, 25 Sep 2004 14:53:58 -0600 (MDT) From: Scott Long <scottl@freebsd.org> To: Peter Jeremy <PeterJeremy@optushome.com.au> Cc: cvs-src@freebsd.org Subject: Re: cvs commit: src/sys/net if.c Message-ID: <20040925145211.H39925@pooker.samsco.org> In-Reply-To: <20040925203122.GF83620@cirb503493.alcatel.com.au> References: <200409221253.i8MCrR4K036310@repoman.freebsd.org> <20040924140756.GG959@green.homeunix.org> <20040924145126.GH959@green.homeunix.org> <20040924154708.GI959@green.homeunix.org> <20040924161807.GJ959@green.homeunix.org> <20040925203122.GF83620@cirb503493.alcatel.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 26 Sep 2004, Peter Jeremy wrote: > On Fri, 2004-Sep-24 12:18:07 -0400, Brian Fundakowski Feldman wrote: > >On Fri, Sep 24, 2004 at 09:51:31AM -0600, Scott Long wrote: > >> On Fri, 24 Sep 2004, Brian Fundakowski Feldman wrote: > >> > Every time it "appears" to be fixed, I can't get any kind of stability > >> > with SMP, PREEMPTION, and SCHED_ULE; I'm certainly willing to try it > >> > each time it looks to be fixed. > >> > >> Would you please copy me on the reports that you've sent to Julian so I > >> can track them also? > > > >The only way I can get reports other than "it hung, serial DDB and > >SW_WATCHDOG are no help" is if somehow I gain some kind of real > >hardware watchdog. :( > > If you have an ISA slot handy, you can trivially generate NMI by > shorting a pair of opposite pins (from memory the pair closest to the > rear but I can't quickly verify that). Unfortunately, raising SERR# > on a PCI bus appears to require some logic. > Not all PCI bridges are configured to translate an SERR# signal to an NMI. Some let you configure it in the BIOS, some simply ignore SERR# and continue merrily on. Regardless, since the signal is active-low, I would expect that grounding the pin would be enough. Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040925145211.H39925>