Date: Fri, 5 Jan 1996 14:52:31 -0700 From: kelly@fsl.noaa.gov (Sean Kelly) To: craigs@venus.os.com Cc: wollman@lcs.mit.edu, questions@freebsd.org Subject: Re: Finding interrupts Message-ID: <9601052152.AA07718@emu.fsl.noaa.gov> In-Reply-To: <Pine.BSF.3.91.960105161029.1052A-100000@venus.os.com> (message from Craig Shrimpton on Fri, 5 Jan 1996 16:14:48 -0500 (EST))
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> "Craig" == Craig Shrimpton <craigs@venus.os.com> writes:
Craig> On Fri, 5 Jan 1996, Garrett A. Wollman wrote:
Craig> cat /proc/interrupts on a Linux box I'll get the following:
Craig> [ ... ]
Craig> This tells me what devices are on which interrupts and how
Craig> many interrupts have occured since the last re-boot. cat
Craig> /proc/ioports returns a similar output but IO location info
Craig> instead of interrupts.
Craig> My question is: does a similar facility exist in FreeBSD?
Well, dmesg is a good start. It prints the system message buffer,
part of which includes the boot-up messages, part of which are the
device probes. That'll give you IRQ, ioport, etc.
As for number of interrupts, try vmstat -i.
--
Sean Kelly
NOAA Forecast Systems Laboratory, Boulder Colorado USA
I put contact lenses in my dog's eyes. They had little pictures of
cats on them. Then I took one out and he ran around in circles.
-- Steven Wright
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9601052152.AA07718>