From owner-freebsd-current Sat Feb 6 16:06:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA09983 for freebsd-current-outgoing; Sat, 6 Feb 1999 16:06:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from locus.dml.com (locus.dml.com [198.49.1.49] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA09912 for ; Sat, 6 Feb 1999 16:06:21 -0800 (PST) (envelope-from rose@dml.com) Received: from localhost (rose@localhost) by locus.dml.com (8.8.5/8.8.5) with ESMTP id QAA18920 for ; Sat, 6 Feb 1999 16:06:17 -0800 (PST) Date: Sat, 6 Feb 1999 16:06:17 -0800 (PST) From: Stephen Rose To: current@FreeBSD.ORG Subject: Silo overflow messages with 3.0 Release Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I didn't get a response from the questions list, so let's try here. I've been getting my server ready to switch from FreeBSD 2.2.2 to 3.0 Release. Everything was going well until I tried to bring my kernel ppp link up to my isp. I get many silo overflow messages when there's any activity on the line. The connection doesn't seem very responsive either. This machine is a dual pentium pro. I've built an smp kernel which seems to work fine otherwise. I've arranged to build the new system on another disk so I can easily switch between the 2.2.2 system and the 3.0 system. Everything works fine with 2.2.2. I've seen many messages in the archive about silo overflows, but there doesn't seem to be a real solution in them. Is this ever likely to work or should I just wait for 3.1? Steve Rose To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message