From owner-freebsd-current Thu Mar 19 08:27:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16767 for freebsd-current-outgoing; Thu, 19 Mar 1998 08:27:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shadow.worldbank.org (shadow.worldbank.org [138.220.104.78]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA16761; Thu, 19 Mar 1998 08:27:54 -0800 (PST) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.8.8/8.8.8) with SMTP id LAA05005; Thu, 19 Mar 1998 11:26:46 -0500 (EST) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Thu, 19 Mar 1998 11:26:46 -0500 (EST) From: "Alok K. Dhir" To: mark@grondar.za cc: dyson@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: A reminder of toxic -current In-Reply-To: <98A8C50807D608D8852565CC00240560.002337FE852565CC@worldbank.org> 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 On Thu, 19 Mar 1998 mark@grondar.za wrote: > "John S. Dyson" wrote: > > Yes. It is an extremely elusive problem. Are you using SMP or UP? Also, > > any info about your system config might be useful (so I can see how you > > are using your system.) It has been difficult for me to reproduce the > > problems since my latest commits, but they still do happen. > > I am using CURRENT on an SMP box. SCB's are hosed (I have an ahc), > so I disabled them; and the vx (ethernet) driver has a problem > where it suddenly starts r u n n i n g v e r y s l o w l y, But > I have no FS problems, and I reboot and FSCK after doing anything > vaguely large. In case it matters, I am also running a very current -current (March 17 kernel, 2:30 pm) on an SMP box, and so far (*knock knock) haven't had any problems with filesystem corruption, etc. Just another datapoint... Al To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message