From owner-freebsd-questions@FreeBSD.ORG Tue Nov 27 08:55:37 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E16B516A418; Tue, 27 Nov 2007 08:55:37 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (pointyhat.freebsd.org [IPv6:2001:4f8:fff6::2b]) by mx1.freebsd.org (Postfix) with ESMTP id CB15913C4EA; Tue, 27 Nov 2007 08:55:36 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <474BDB92.7090708@FreeBSD.org> Date: Tue, 27 Nov 2007 09:55:46 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: Kris Kennaway References: <000701c82f89$fb9b40a0$0200a8c0@satellite> <4749FDE0.9030902@netscape.net> <474A9DCD.6020500@FreeBSD.org> <3aaaa3a0711260734tb0a46a3kac3b423bfd89582b@mail.gmail.com> <474B4610.5020702@FreeBSD.org> In-Reply-To: <474B4610.5020702@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Chris , Tore Lund , freebsd-questions@freebsd.org Subject: Re: stability of FreeBSD 7 Beta 3? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Nov 2007 08:55:38 -0000 Kris Kennaway wrote: > Chris wrote: >> On 26/11/2007, Kris Kennaway wrote: >>> Tore Lund wrote: >>>> Ivan Voras wrote: >>>>> Dave wrote: >>>>>> Hello, >>>>>> How stable is FreeBSD 7 Beta 3? Is it near production are their >>>>>> any >>>>>> outstanding issues? >>>>> Probably no major bugs will be fixed between now and 7.0 so you >>>>> might as >>>>> well start using it now. >>>>> >>>>> It's "stable enough" like all .0 releases, meaning you should >>>>> throughly >>>>> test it for your own workload before using it in production. >>>> Just curious, what is the "official" forum for pre-release discussions? >>>> I notice there are some threads on the "current" list, but it seems to >>>> me that this is really "questions" stuff, since it is an upcoming >>>> release. >>> freebsd-stable is probably best. >>> >>>> In any case, I tried the boot-only CD, and I was not able to install >>>> any >>>> packages during the install process. Sysinstall aborted with Signal 11 >>>> when trying to read INDEX from the ftp site. Pkg_add from the command >>>> line seems to work, however, so it looks like I may get online from >>>> 7.0-BETA3 tomorrow. >>> That is expected, packages are not available until later in the release >>> cycle. >>> >>>> Moreover, wasn't there supposed to be a new install program? I have >>>> read some promising remarks about it, but it's certainly not part of >>>> 7.0-BETA3. Personally, I would much rather type a long list of >>>> commands >>>> than use the old, rickety sysinstall. >>> One is in early development, but not even complete let alone ready to >>> replace sysinstall. >>> >>> Kris >>> _______________________________________________ >>> freebsd-questions@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >>> To unsubscribe, send any mail to >>> "freebsd-questions-unsubscribe@freebsd.org" >>> >> >> Kris can I ask what sort of importance bugs that cause crashes (page >> faults) are? >> I reported 2 bugs before BETA1 both these bugs involved 7.0 getting a >> page fault and of course then stop responding requiring a reboot yet >> both PRs have had no response and both bugs are still present in BETA3 >> I see minor issues been worked on such as responsiveness in desktop >> use whilst issues that cause system crashes are left unattended. Is >> FreeBSD primarily a desktop os now and thats the new path? > > Of course not :P What are the PR references? > >> Try this. >> >> Login to twice on ssh. >> If not root su both to root. >> using the 2nd tty do a watch -W on the first tty. >> on the first tty type 'killall watch' >> you have now crashed freebsd 7 and most probably a auto reboot timer >> is counting down. > > I can confirm this. Try this patch from kib@ diff --git a/sys/dev/snp/snp.c b/sys/dev/snp/snp.c index a84e90c..b8f3d63 100644 --- a/sys/dev/snp/snp.c +++ b/sys/dev/snp/snp.c @@ -491,7 +491,7 @@ snpioctl(struct cdev *dev, u_long cmd, caddr_t data, int flags, struct thread *td) { struct snoop *snp; - struct tty *tp, *tpo; + struct tty *tp; struct cdev *tdev; struct file *fp; int s; @@ -502,6 +502,9 @@ snpioctl(struct cdev *dev, u_long cmd, caddr_t data, int flags, s = *(int *)data; if (s < 0) return (snp_down(snp)); + if (snp->snp_tty != NULL) + return (EBUSY); + if (fget(td, s, &fp) != 0) return (EINVAL); if (fp->f_type != DTYPE_VNODE || @@ -520,13 +523,6 @@ snpioctl(struct cdev *dev, u_long cmd, caddr_t data, int flags, return (EBUSY); s = spltty(); - - if (snp->snp_target == NULL) { - tpo = snp->snp_tty; - if (tpo) - tpo->t_state &= ~TS_SNOOP; - } - tp->t_state |= TS_SNOOP; snp->snp_olddisc = tp->t_line; tp->t_line = snooplinedisc;