Date: Thu, 19 Mar 1998 11:26:46 -0500 (EST) From: "Alok K. Dhir" <adhir@worldbank.org> To: mark@grondar.za Cc: dyson@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: A reminder of toxic -current Message-ID: <Pine.BSF.3.96.980319112406.4988A-100000@shadow.worldbank.org> In-Reply-To: <98A8C50807D608D8852565CC00240560.002337FE852565CC@worldbank.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980319112406.4988A-100000>