Date: Sun, 2 Oct 2005 16:50:35 -0700 From: David Kirchner <dpk@dpk.net> To: Jakob Breivik Grimstveit <jakob@grimstveit.no> Cc: FreeBSD Questions <questions@freebsd.org>, freebsd-questions-local@be-well.ilk.org Subject: Re: Complete hangs while extracting source Message-ID: <35c231bf0510021650o5fdb6e50ob0e0d78704f0ef04@mail.gmail.com> In-Reply-To: <20051003010551.6021404a@corona.grimstveit.no> References: <20050930112833.4fc7ae78@corona.grimstveit.no> <44psqpfmcz.fsf@be-well.ilk.org> <20051003010551.6021404a@corona.grimstveit.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/2/05, Jakob Breivik Grimstveit <jakob@grimstveit.no> wrote: > How can I tell? I doubt this to be the problem, since I experience same > problem on two other machines as well. Only thing they share (except same > lousy administrator :-) is that they all run on AMD CPUs (1700+, 1800+ an= d > 3500+). dmesg will show you irqs, but you can also find it using systat's "vmstat" mode. It'll also allow you to monitor interrupt activity. It's best used from the console of the machine. I would guess you'd want to watch for two drivers, sharing an interrupt, and both incrementing at the same rate. (I've seen that before, and it was associated with severe performance problems, but unfortunately I do not recall how it was fixed.)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?35c231bf0510021650o5fdb6e50ob0e0d78704f0ef04>