From owner-freebsd-hackers Wed Jun 7 08:21:05 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA22595 for hackers-outgoing; Wed, 7 Jun 1995 08:21:05 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA22588 for ; Wed, 7 Jun 1995 08:20:56 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id BAA22660; Thu, 8 Jun 1995 01:19:21 +1000 Date: Thu, 8 Jun 1995 01:19:21 +1000 From: Bruce Evans Message-Id: <199506071519.BAA22660@godzilla.zeta.org.au> To: freebsd-hackers@freefall.cdrom.com, jleppek@suw2k.ess.harris.com Subject: Re: silo overflows Sender: hackers-owner@FreeBSD.org Precedence: bulk >The only bus hogging DMA I could think of is the 1542CF but it is >at the default settings which I thought were safe. My root, usr, I think so too. There have been reports about silo overflows under X in normal operations, but I don't know the cause. Overflows are normal, at least in old versions of XFree, when interrupts are disabled while fiddling with the clocks. >and home partitions are on IDE disks(VLB controller). Is there a "cleaner" way >to adjust the fifo trigger levels than making another constant like >FIFO_TRIGGER_10? perhaps a sysctl or stty option? Not yet. There will be some ioctl for comcontrol to use. >Oh, the sio man page still describes the automatic adjusting as enabled >is that going to be put back in or was it decided that it was not a >good idea? It will probably go away. Bruce