From owner-freebsd-hackers Sun Dec 12 13: 5:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id C292314E96 for ; Sun, 12 Dec 1999 13:05:45 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id NAA90073; Sun, 12 Dec 1999 13:05:30 -0800 (PST) Date: Sun, 12 Dec 1999 13:05:29 -0800 (PST) From: Julian Elischer To: Egervary Gergely Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: silo overflows In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG what kind of disk to you have? and the chipset? (this may seem irrelevant but misconfigured DMA devices can block the cpu for long enough to cause this sort of thing in some cases). ALSO check systat -vmstat while this is happenning and check that you don't have a source of spurious interrupts. Julian On Sun, 12 Dec 1999, Egervary Gergely wrote: > hy, > > i still can't get rid of silo overflows :( > > 3.3-STABLE, a simple pentium2 system w/ external 33.6 rockwell modem > attached to sio0. i see nothing special. and the overflows just still come > :( > > what should i check/ look after? > > --mauzi > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message