From owner-freebsd-current Sun Feb 18 9:18:41 2001 Delivered-To: freebsd-current@freebsd.org Received: from rly-ip02.mx.aol.com (rly-ip02.mx.aol.com [152.163.225.160]) by hub.freebsd.org (Postfix) with ESMTP id 64CD037B401 for ; Sun, 18 Feb 2001 09:18:39 -0800 (PST) Received: from tot-th.proxy.aol.com (tot-th.proxy.aol.com [152.163.213.1]) by rly-ip02.mx.aol.com (8.8.8/8.8.8/AOL-5.0.0) with ESMTP id MAA00550 for ; Sun, 18 Feb 2001 12:18:16 -0500 (EST) Received: from eVIPlist.com (AC9A24A1.ipt.aol.com [172.154.36.161]) by tot-th.proxy.aol.com (8.10.0/8.10.0) with SMTP id f1IHIFf28142 for ; Sun, 18 Feb 2001 12:18:15 -0500 (EST) Message-Id: <200102181718.f1IHIFf28142@tot-th.proxy.aol.com> From: "eVIPlist" To: Subject: www.eVIPlist.com - Your VIP pass to parties & special events! Join the list. Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Date: Sun, 18 Feb 2001 12:16:19 -0500 Content-Transfer-Encoding: 8bit X-Apparently-From: Eluistaylor@aol.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 18 16: 9:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from sidonie.ods.org (APastourelles-101-1-1-123.abo.wanadoo.fr [193.251.52.123]) by hub.freebsd.org (Postfix) with ESMTP id 4B60037B401 for ; Sun, 18 Feb 2001 16:09:35 -0800 (PST) Received: from aglae (aglae [192.168.100.2]) by sidonie.ods.org (8.11.1/8.11.1) with ESMTP id f1J0VEa00989 for ; Mon, 19 Feb 2001 01:31:15 +0100 (CET) (envelope-from f314116@yahoo.com) Date: Mon, 19 Feb 2001 01:09:34 +0100 (CET) From: Frederic Stark X-Sender: fred@aglae.ods.org Reply-To: Frederic Stark To: freebsd-current@freebsd.org Subject: Make kernel fail in modules after upgrade 4.2 -> 5.0 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 Hi, What I did: cvsup from 4.2-STABLE to 5.0-CURRENT make buildworld make installworld mergemaster --> All this went okay Then updated my kernel config file and compiled the kernel. (I still haven't rebooted the machine) The build fails in: ===> 3dfx ld -r -o 3dfx.kld tdfx_pci.o /usr/libexec/elf/ld: cannot open tdfx_pci.o: No such file or directory *** Error code 1 Stop in /usr/src/sys/modules/3dfx. *** Error code 1 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /usr/src/sys/compile/AGLAE. 3dfx seems to be the first module. If I try to build it by hands: su-2.03# pwd /usr/src/sys/modules/3dfx su-2.03# make clean rm -f setdef0.c setdef1.c setdefs.h setdef0.o setdef1.o 3dfx.ko 3dfx.kld tdfx_pci.o @ machine symb.tmp tmp.o opt_tdfx.h bus_if.h device_if.h pci_if.h su-2.03# make Warning: Object directory not changed from original /usr/src/sys/modules/3dfx @ -> /usr/src/sys machine -> /usr/src/sys/i386/include echo "#define TDFX_LINUX" > opt_tdfx.h perl @/kern/makeobjops.pl -h @/kern/bus_if.m perl @/kern/makeobjops.pl -h @/dev/pci/pci_if.m perl @/kern/makeobjops.pl -h @/kern/device_if.m ld -r -o 3dfx.kld tdfx_pci.o /usr/libexec/elf/ld: cannot open tdfx_pci.o: No such file or directory *** Error code 1 Stop in /usr/src/sys/modules/3dfx. su-2.03# ls @ bus_if.h machine pci_if.h Makefile device_if.h opt_tdfx.h If I try to build any other module, I have the same error. Looks like my makefiles are in bad shape and forget to build the object files. What can I do ? Thanks in advance, --fred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 18 16:22:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail-ob.kamp.net (mail-ob.kamp.net [195.62.97.26]) by hub.freebsd.org (Postfix) with ESMTP id D229837B4EC for ; Sun, 18 Feb 2001 16:22:20 -0800 (PST) Received: from bsdevil.meta.net.ob.kamp.net (port-22.d.kamp.de [195.62.120.214]) by mail-ob.kamp.net (8.10.1/8.10.1) with ESMTP id f1J0MDD03345; Mon, 19 Feb 2001 01:22:15 +0100 Date: Mon, 19 Feb 2001 01:22:13 +0100 Message-Id: <200102190022.f1J0MDD03345@mail-ob.kamp.net> From: Farid Hajji To: stephanb@whacky.net Cc: nnd@mail.nsk.ru, current@FreeBSD.ORG In-reply-to: <20010217172941.A11740@enigma.whacky.net> (message from Stephan van Beerschoten on Sat, 17 Feb 2001 17:29:41 +0100) Subject: Re: HEADS UP: -current world broken since Feb 10 X-Mailer: Emacs-20.7.1/FreeBSD-5.0-CURRENT Reply-To: farid.hajji@ob.kamp.net References: <20010216144805.B880@enigma.whacky.net> <200102161503.f1GF3m273003@wint.itfs.nsk.su> <20010217172941.A11740@enigma.whacky.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I just updated -CURRENT 2001-01-25 to 2001-02-18.0100 CET and the system runs fine for me. Built and installed kernel too. All old binaries that linked to libc.so.5 (including X11) not recompiled; they still run fine. No problems with as(1) either. The only glitch during installworld was: install: /usr/share/examples/BSD_daemon/FreeBSD.pfa: No such file or directory Error Code 71 and other errors in /usr/share/examples/BSD_daemon about missing files. make -k buileworld did the trick just fine. Other errors (besides BSD_daemon) didn't occur during buildworld. > > > FreeBSD .whacky.net 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Fri Feb 16 14:33:37 CET 2001 stephanb@.whacky.net:/mnt/archive/CVS/CURRENT/src/sys/compile/ i386 Here too: FreeBSD bsdevil.meta.net 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Sun Feb 18 22:04:15 CET 2001 root@bsdevil.meta.net:/usr/obj/usr/src/sys/MYTWR i386 > > If you want to discover and reproduce the problem (:-) > > it is sufficient to go to ports/devel/gettext and 'make' this port. > > When make start to make in the 'po' directory it SIGFAULTs in > > __ungetc. > > *sighs* True.. it fails here as well. Damn This works fine here (gettext-0.10.35.tar.gz). No problems whatsoever recompiling... Regards, -Farid. -- Farid Hajji -- Unix Systems and Network Admin | Phone: +49-2131-67-555 Broicherdorfstr. 83, D-41564 Kaarst, Germany | farid.hajji@ob.kamp.net - - - - - - - - - - - - - - - - - - - - - - - + - - - - - - - - - - - - Murphy's Law fails only when you try to demonstrate it, and thus succeeds. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 18 16:50:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from c1030098-a.wtrlo1.ia.home.com (c1030098-a.wtrlo1.ia.home.com [24.11.39.39]) by hub.freebsd.org (Postfix) with ESMTP id C18E937B503; Sun, 18 Feb 2001 16:50:44 -0800 (PST) Received: by c1030098-a.wtrlo1.ia.home.com (Postfix, from userid 1001) id 5BBD214A14; Sun, 18 Feb 2001 18:50:54 -0600 (CST) To: freebsd-current@freebsd.org, freebsd-ports@freebsd.org Subject: can't run gnome's panel From: Michael Harnois Date: 18 Feb 2001 18:50:54 -0600 Message-ID: <86ae7jjy1d.fsf@mharnois.workgroup.net> Lines: 17 User-Agent: Gnus/5.090001 (Oort Gnus v0.01) XEmacs/21.2 (Thalia) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ever since the great libc crisis in -current began, I've been unable to run gnome's panel. It segfaults immediately, and the gdb trace is unenlightening: (gdb) where #0 0x2864ec95 in strncmp () from /usr/lib/libc.so.5 #1 0x0 in ?? () I have cleaned out and recompiled everything it depends on a couple of times. -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mdharnois@home.com aa0bt@aa0bt.ampr.org Be radical, be as radical as you can ... because radicals empower liberals. --John Preston To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 18 18:35:49 2001 Delivered-To: freebsd-current@freebsd.org Received: from ns.altadena.net (ns.altadena.net [206.126.144.2]) by hub.freebsd.org (Postfix) with ESMTP id C6A7337B401 for ; Sun, 18 Feb 2001 18:35:47 -0800 (PST) Received: (from pete@localhost) by ns.altadena.net (8.11.2/8.8.8) id f1J2XpC25216 for current@freebsd.org; Sun, 18 Feb 2001 18:33:51 -0800 (PST) (envelope-from pete) From: Pete Carah Message-Id: <200102190233.f1J2XpC25216@ns.altadena.net> Subject: Re: Make kernel fail in modules after upgrade 4.2 -> 5.0 To: current@freebsd.org Date: Sun, 18 Feb 2001 18:33:51 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=iso8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This may relate to a commit about noon (PST) today fixing a different problem. I'm just waiting it out :-) Welcome to "current" where (especially lately) about half the time things don't 'make'... (I'm trying to recompile my kernel after recovering from the libc circus, trying to prevent some new panics) During the fixing stages of the libc problem, vinum caused panics fairly regularly for me (very early on or during fsck). I'm now seeing panics in ufs write after medium heavy activity (make world, no -j) on SMP, no reg dump comes out. Complains about table inconsistent (don't remember the precise message). Hopefully my hardware is OK; this machine has been stable for several weeks with upgraded RAM. -- Pete To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 18 23:41: 1 2001 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id 6522C37B401 for ; Sun, 18 Feb 2001 23:40:58 -0800 (PST) Received: (from ache@localhost) by nagual.pp.ru (8.11.2/8.11.2) id f1J7etT99040 for current@freebsd.org; Mon, 19 Feb 2001 10:40:56 +0300 (MSK) (envelope-from ache) Date: Mon, 19 Feb 2001 10:40:53 +0300 From: "Andrey A. Chernov" To: current@freebsd.org Subject: kernel modules broken (kmod.mk?) Message-ID: <20010219104052.A99018@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Recent -current, 'make' fails ('make depend' works), I got this for _every_ module: ld -r -o 3dfx.kld tdfx_pci.o /usr/libexec/elf/ld: cannot open tdfx_pci.o: No such file or directory *** Error code 1 Stop in /usr/src/sys/modules/3dfx. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 18 23:52:53 2001 Delivered-To: freebsd-current@freebsd.org Received: from www.evil.2y.net (ip-216-23-53-155.adsl.one.net [216.23.53.155]) by hub.freebsd.org (Postfix) with ESMTP id 2419F37B401 for ; Sun, 18 Feb 2001 23:52:50 -0800 (PST) Received: (from cokane@localhost) by www.evil.2y.net (8.11.2/8.11.1) id f1J867546893; Mon, 19 Feb 2001 03:06:07 -0500 (EST) (envelope-from cokane) Date: Mon, 19 Feb 2001 03:06:07 -0500 From: Coleman Kane To: "Andrey A. Chernov" Cc: freebsd-current@FreeBSD.org Subject: Re: 3dfx -current compile error Message-ID: <20010219030607.A46836@cokane.yi.org> References: <20010219103445.A97960@nagual.pp.ru> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="fdj2RfSjLxBAspz7" X-Mailer: Mutt 1.0.1i In-Reply-To: <20010219103445.A97960@nagual.pp.ru>; from ache@nagual.pp.ru on Mon, Feb 19, 2001 at 02:35:05AM -0500 X-Vim: vim:tw=70:ts=4:sw=4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --fdj2RfSjLxBAspz7 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Yeah, this seems to be broken across all modules. I don't know what's going= on, but it seems like it never bothers to make the *.o targets. The reason mine= =20 pops up with the error is that, alphabetically, it is first on the list. If= you remove it from the ports Makefile, the accf_data module brings up the error= . I noticed a lot of commit traffic for config, src/share/mk, make and the like= , so I figured this to be a 'commit in process' issue. I'm forwarding this to=20 -current mailing list to let them know about the prob. -- Coleman Kane Andrey A. Chernov had the audacity to say: >=20 > pa:/sys/modules/3dfx ttyp0 47_# make > ... > ld -r -o 3dfx.kld tdfx_pci.o > /usr/libexec/elf/ld: cannot open tdfx_pci.o: No such file or directory > *** Error code 1 >=20 > Stop in /usr/src/sys/modules/3dfx. > --=20 > Andrey A. Chernov > http://ache.pp.ru/ >=20 --fdj2RfSjLxBAspz7 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6kNPuERViMObJ880RAmBIAJ0WyJxcMi4H2LXKMe0NKAmFtva9VgCeP9BR taPAyRpiaVMHlFUgQrWedPQ= =KYNY -----END PGP SIGNATURE----- --fdj2RfSjLxBAspz7-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 19 0:18:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from localhost.westmarsh.com (orion.westmarsh.com [193.195.76.57]) by hub.freebsd.org (Postfix) with ESMTP id A92F537B401 for ; Mon, 19 Feb 2001 00:18:27 -0800 (PST) Received: from westmarsh.com (mailgate.westmarsh.com [193.195.76.50]) (authenticated) by localhost.westmarsh.com (8.11.2/8.11.1) with ESMTP id f1J8I5K08679; Mon, 19 Feb 2001 08:18:05 GMT (envelope-from pierre.dampure@westmarsh.com) Message-ID: <3A90D6BD.FD9F6E1@westmarsh.com> Date: Mon, 19 Feb 2001 08:18:05 +0000 From: "Pierre Y. Dampure" X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Andrey A. Chernov" Cc: current@freebsd.org Subject: Re: kernel modules broken (kmod.mk?) References: <20010219104052.A99018@nagual.pp.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Andrey A. Chernov" wrote: > Recent -current, 'make' fails ('make depend' works), I got this for > _every_ module: > > ld -r -o 3dfx.kld tdfx_pci.o > /usr/libexec/elf/ld: cannot open tdfx_pci.o: No such file or directory > *** Error code 1 > > Stop in /usr/src/sys/modules/3dfx. > I think this might be related to Peter Wemm's last commit on src/sys/conf/kmod.mk, which seems to remove the .depend file at the start of the make. If I revert the change, modules compile OK Best Regards, PYD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 19 0:26:35 2001 Delivered-To: freebsd-current@freebsd.org Received: from sidonie.ods.org (APastourelles-101-1-1-123.abo.wanadoo.fr [193.251.52.123]) by hub.freebsd.org (Postfix) with ESMTP id 395B237B4EC for ; Mon, 19 Feb 2001 00:26:31 -0800 (PST) Received: from aglae (aglae [192.168.100.2]) by sidonie.ods.org (8.11.1/8.11.1) with ESMTP id f1J8loB00287; Mon, 19 Feb 2001 09:47:51 +0100 (CET) (envelope-from f314116@yahoo.com) Date: Mon, 19 Feb 2001 09:26:20 +0100 (CET) From: Frederic Stark X-Sender: fred@aglae.ods.org Reply-To: Frederic Stark To: Pete Carah Cc: current@freebsd.org Subject: Re: Make kernel fail in modules after upgrade 4.2 -> 5.0 In-Reply-To: <200102190233.f1J2XpC25216@ns.altadena.net> 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 Sun, 18 Feb 2001, Pete Carah wrote: > This may relate to a commit about noon (PST) today fixing a different > problem. I'm just waiting it out :-) Oh. I'll just wait too. > Welcome to "current" where (especially lately) about half the time things > don't 'make'... (I'm trying to recompile my kernel after recovering > from the libc circus, trying to prevent some new panics) Yeah. I don't know what I smoked yesterday to decide to go 'current' (In fact, it is because mozilla-0.8 doesn't compile/run on 4.2, but reportedly works on 5.0. I bet I just replaced a small set of problems by a larger one...). On the bright side, this will keep me entertained for weeks :-) Thanks for the reply, Cheers, --fred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 19 0:47:41 2001 Delivered-To: freebsd-current@freebsd.org Received: from sidonie.ods.org (APastourelles-101-1-1-123.abo.wanadoo.fr [193.251.52.123]) by hub.freebsd.org (Postfix) with ESMTP id 7E5AD37B67D for ; Mon, 19 Feb 2001 00:47:36 -0800 (PST) Received: from aglae (aglae [192.168.100.2]) by sidonie.ods.org (8.11.1/8.11.1) with ESMTP id f1J98hB00309; Mon, 19 Feb 2001 10:08:48 +0100 (CET) (envelope-from f314116@yahoo.com) Date: Mon, 19 Feb 2001 09:47:13 +0100 (CET) From: Frederic Stark X-Sender: fred@aglae.ods.org Reply-To: Frederic Stark To: "Pierre Y. Dampure" Cc: "Andrey A. Chernov" , current@freebsd.org Subject: Re: kernel modules broken (kmod.mk?) In-Reply-To: <3A90D6BD.FD9F6E1@westmarsh.com> 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 Mon, 19 Feb 2001, Pierre Y. Dampure wrote: > "Andrey A. Chernov" wrote: > > > Recent -current, 'make' fails ('make depend' works), I got this for > > _every_ module: > > > > ld -r -o 3dfx.kld tdfx_pci.o > > /usr/libexec/elf/ld: cannot open tdfx_pci.o: No such file or directory > > *** Error code 1 > > > > Stop in /usr/src/sys/modules/3dfx. > > > > I think this might be related to Peter Wemm's last commit on > src/sys/conf/kmod.mk, which seems to remove the .depend file at the start > of the make. If I revert the change, modules compile OK After I commented out line 161 of 'kmod.mk' ( @rm -f .depend ) and removed the linux module from src/sys/modules/Makefile the compile went OK. Cheers, --fred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 19 1:19:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from web2905.mail.yahoo.com (web2905.mail.yahoo.com [128.11.68.48]) by hub.freebsd.org (Postfix) with SMTP id AD8D937B401 for ; Mon, 19 Feb 2001 01:19:13 -0800 (PST) Received: (qmail 19843 invoked by uid 60001); 19 Feb 2001 09:19:13 -0000 Message-ID: <20010219091913.19842.qmail@web2905.mail.yahoo.com> Received: from [63.204.134.48] by web2905.mail.yahoo.com; Mon, 19 Feb 2001 01:19:13 PST Date: Mon, 19 Feb 2001 01:19:13 -0800 (PST) From: Herman Tan Subject: updating from 12/25/1999 -current? To: current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings everyone: Will I run into any problems doing a make world from a 12/25/1999 version of -CURRENT to the latest -current? I noticed on -RELEASE machines when I went from 3.3-R to 4.1-R, I had problems because the loaded kernel doesn't have the modules and I had to use the Generic kernel in 4.1R and reboot the machine. Any suggestions? Thanks. HT __________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail - only $35 a year! http://personal.mail.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 19 2: 6: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 7E33E37B401; Mon, 19 Feb 2001 02:05:56 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f1JA5uH06662; Mon, 19 Feb 2001 02:05:56 -0800 (PST) Date: Mon, 19 Feb 2001 02:05:56 -0800 From: Alfred Perlstein To: grog@freebsd.org Cc: current@freebsd.org Subject: please test, vinum + devfs Message-ID: <20010219020556.K6641@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-all-your-base: are belong to us. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This gets my vinum config working enough such that I can mount my pre-devfs configuration, if anyone wants to test/comment please try this: (you'll need to recompile src/sbin/vinum as well) Index: vinum.c =================================================================== RCS file: /home/ncvs/src/sys/dev/vinum/vinum.c,v retrieving revision 1.39 diff -u -r1.39 vinum.c --- vinum.c 2000/10/23 08:35:36 1.39 +++ vinum.c 2001/02/19 09:54:39 @@ -35,8 +35,8 @@ * otherwise) arising in any way out of the use of this software, even if * advised of the possibility of such damage. * - * $Id: vinum.c,v 1.28 1999/10/12 09:41:20 grog Exp grog $ - * $FreeBSD: src/sys/dev/vinum/vinum.c,v 1.39 2000/10/23 08:35:36 phk Exp $ + * $Id: vinum.c,v 1.39 2000/10/23 08:35:36 phk Exp $ + * $FreeBSD: src/sys/dev/vinum/vinum.c,v 1.38 2000/02/29 06:07:39 grog Exp $ */ #define STATIC static /* nothing while we're testing XXX */ @@ -53,7 +53,7 @@ #endif #include -STATIC struct cdevsw vinum_cdevsw = +struct cdevsw vinum_cdevsw = { vinumopen, vinumclose, physread, physwrite, vinumioctl, seltrue, nommap, vinumstrategy, @@ -68,6 +68,9 @@ struct _vinum_conf vinum_conf; /* configuration information */ +dev_t vinum_daemon_dev; +dev_t vinum_super_dev; + /* * Called by main() during pseudo-device attachment. All we need * to do is allocate enough space for devices to be configured later, and @@ -88,6 +91,10 @@ dqend = NULL; cdevsw_add(&vinum_cdevsw); /* add the cdevsw entry */ + vinum_daemon_dev = make_dev(&vinum_cdevsw, VINUM_DAEMON_DEV, + UID_ROOT, GID_WHEEL, S_IRUSR|S_IWUSR, VINUM_DAEMON_DEV_NAME); /* daemon device */ + vinum_super_dev = make_dev(&vinum_cdevsw, VINUM_SUPERDEV, + UID_ROOT, GID_WHEEL, S_IRUSR|S_IWUSR, VINUM_SUPERDEV_NAME); /* daemon device */ /* allocate space: drives... */ DRIVE = (struct drive *) Malloc(sizeof(struct drive) * INITIAL_DRIVES); @@ -174,21 +181,33 @@ queue_daemon_request(daemonrq_return, (union daemoninfo) 0); /* stop the daemon */ tsleep(&vinumclose, PUSER, "vstop", 1); /* and wait for it */ } - if (SD != NULL) + if (SD != NULL) { + for (i = 0; i < vinum_conf.subdisks_allocated; i++) { + struct sd *sd = &vinum_conf.sd[i]; + + if (sd->state != sd_unallocated) + free_sd(i); + } Free(SD); + } if (PLEX != NULL) { for (i = 0; i < vinum_conf.plexes_allocated; i++) { struct plex *plex = &vinum_conf.plex[i]; - if (plex->state != plex_unallocated) { /* we have real data there */ - if (plex->sdnos) - Free(plex->sdnos); - } + if (plex->state != plex_unallocated) /* we have real data there */ + free_plex(i); } Free(PLEX); } - if (VOL != NULL) + if (VOL != NULL) { + for (i = 0; i < vinum_conf.volumes_allocated; i++) { + struct volume *volume = &vinum_conf.volume[i]; + + if (volume->state != volume_unallocated) + free_volume(i); + } Free(VOL); + } bzero(&vinum_conf, sizeof(vinum_conf)); } @@ -236,6 +255,8 @@ } } #endif + destroy_dev(vinum_daemon_dev); /* daemon device */ + destroy_dev(vinum_super_dev); cdevsw_remove(&vinum_cdevsw); log(LOG_INFO, "vinum: unloaded\n"); /* tell the world */ return 0; Index: vinumconfig.c =================================================================== RCS file: /home/ncvs/src/sys/dev/vinum/vinumconfig.c,v retrieving revision 1.38 diff -u -r1.38 vinumconfig.c --- vinumconfig.c 2001/02/02 07:14:13 1.38 +++ vinumconfig.c 2001/02/19 10:05:10 @@ -734,6 +734,7 @@ sd->sectors); if (sd->plexno >= 0) PLEX[sd->plexno].subdisks--; /* one less subdisk */ + destroy_dev(sd->dev); bzero(sd, sizeof(struct sd)); /* and clear it out */ sd->state = sd_unallocated; vinum_conf.subdisks_used--; /* one less sd */ @@ -811,6 +812,7 @@ Free(plex->sdnos); if (plex->lock) Free(plex->lock); + destroy_dev(plex->dev); bzero(plex, sizeof(struct plex)); /* and clear it out */ plex->state = plex_unallocated; } @@ -881,6 +883,7 @@ struct volume *vol; vol = &VOL[volno]; + destroy_dev(vol->dev); bzero(vol, sizeof(struct volume)); /* and clear it out */ vol->state = volume_unallocated; } @@ -1220,6 +1223,8 @@ if (sd->sectors < 0) throw_rude_remark(EINVAL, "sd %s has no length spec", sd->name); + sd->dev = make_dev(&vinum_cdevsw, VINUMRMINOR(VINUM_SD_TYPE, sdno), + UID_ROOT, GID_WHEEL, S_IRUSR|S_IWUSR, "vinum/sd/%s", sd->name); if (state != sd_unallocated) /* we had a specific state to set */ sd->state = state; /* do it now */ else if (sd->state == sd_unallocated) /* no, nothing set yet, */ @@ -1377,6 +1382,9 @@ if (plex->organization == plex_disorg) throw_rude_remark(EINVAL, "No plex organization specified"); + plex->dev = make_dev(&vinum_cdevsw, VINUMRMINOR(VINUM_PLEX_TYPE, plexno), + UID_ROOT, GID_WHEEL, S_IRUSR|S_IWUSR, "vinum/plex/%s", plex->name); + if ((plex->volno < 0) /* we don't have a volume */ &&(!detached)) /* and we wouldn't object */ plex->volno = current_volume; @@ -1534,7 +1542,10 @@ /* Find out how big our volume is */ for (i = 0; i < vol->plexes; i++) vol->size = max(vol->size, PLEX[vol->plex[i]].length); + vinum_conf.volumes_used++; /* one more in use */ + vol->dev = make_dev(&vinum_cdevsw, VINUMRMINOR(VINUM_VOLUME_TYPE, volno), + UID_ROOT, GID_WHEEL, S_IRUSR|S_IWUSR, "vinum/vol/%s", vol->name); } /* @@ -1686,23 +1697,29 @@ ||(sd->state == sd_unallocated)) { /* or nothing there */ ioctl_reply->error = EINVAL; strcpy(ioctl_reply->msg, "No such subdisk"); + return; } else if (sd->flags & VF_OPEN) { /* we're open */ ioctl_reply->error = EBUSY; /* no getting around that */ return; } else if (sd->plexno >= 0) { /* we have a plex */ - if (force) { /* do it at any cost */ + if (!force) { /* do it at any cost */ + ioctl_reply->error = EBUSY; /* can't do that */ + return; + } else { struct plex *plex = &PLEX[sd->plexno]; /* point to our plex */ int mysdno; for (mysdno = 0; /* look for ourselves */ mysdno < plex->subdisks && &SD[plex->sdnos[mysdno]] != sd; mysdno++); - if (mysdno == plex->subdisks) /* didn't find it */ + if (mysdno == plex->subdisks) { /* didn't find it */ log(LOG_ERR, "Error removing subdisk %s: not found in plex %s\n", SD[mysdno].name, plex->name); - else { /* remove the subdisk from plex */ + ioctl_reply->error = EINVAL; + return; + } else { /* remove the subdisk from plex */ if (mysdno < (plex->subdisks - 1)) /* not the last subdisk */ bcopy(&plex->sdnos[mysdno + 1], &plex->sdnos[mysdno], @@ -1719,14 +1736,10 @@ */ if (plex->organization != plex_concat) /* not concatenated, */ set_plex_state(plex->plexno, plex_faulty, setstate_force); /* need to reinitialize */ - log(LOG_INFO, "vinum: removing %s\n", sd->name); - free_sd(sdno); - } else - ioctl_reply->error = EBUSY; /* can't do that */ - } else { - log(LOG_INFO, "vinum: removing %s\n", sd->name); - free_sd(sdno); + } } + log(LOG_INFO, "vinum: removing %s\n", sd->name); + free_sd(sdno); } /* remove a plex */ Index: vinumhdr.h =================================================================== RCS file: /home/ncvs/src/sys/dev/vinum/vinumhdr.h,v retrieving revision 1.22 diff -u -r1.22 vinumhdr.h --- vinumhdr.h 2001/01/21 19:25:04 1.22 +++ vinumhdr.h 2001/02/18 23:49:36 @@ -36,8 +36,8 @@ /* Header files used by all modules */ /* - * $Id: vinumhdr.h,v 1.18 2001/01/04 00:14:14 grog Exp grog $ - * $FreeBSD: src/sys/dev/vinum/vinumhdr.h,v 1.22 2001/01/21 19:25:04 jake Exp $ + * $Id: vinumhdr.h,v 1.22 2001/01/21 19:25:04 jake Exp $ + * $FreeBSD: src/sys/dev/vinum/vinumhdr.h,v 1.21 2001/01/10 21:42:06 grog Exp $ */ #include @@ -96,3 +96,4 @@ #define Free(x) free ((x)) /* just the address */ #endif +extern struct cdevsw vinum_cdevsw; Index: vinumvar.h =================================================================== RCS file: /home/ncvs/src/sys/dev/vinum/vinumvar.h,v retrieving revision 1.36 diff -u -r1.36 vinumvar.h --- vinumvar.h 2001/01/14 06:34:57 1.36 +++ vinumvar.h 2001/02/19 09:43:58 @@ -37,8 +37,8 @@ * otherwise) arising in any way out of the use of this software, even if * advised of the possibility of such damage. * - * $Id: vinumvar.h,v 1.24 2000/03/01 02:34:57 grog Exp grog $ - * $FreeBSD: src/sys/dev/vinum/vinumvar.h,v 1.36 2001/01/14 06:34:57 grog Exp $ + * $Id: vinumvar.h,v 1.36 2001/01/14 06:34:57 grog Exp $ + * $FreeBSD$ */ #include @@ -216,7 +216,7 @@ unsigned signbit:1; /* to make 32 bits */ }; -#define VINUM_DIR "/dev/vinum" +#define VINUM_DIR "vinum" /* * These definitions help catch @@ -451,6 +451,7 @@ int init_blocksize; /* init block size (bytes) */ int init_interval; /* and time to wait between transfers */ char name[MAXSDNAME]; /* name of subdisk */ + dev_t dev; }; /*** Plex definitions ***/ @@ -498,6 +499,7 @@ u_int64_t multistripe; /* requests that needed more than one stripe */ int sddowncount; /* number of subdisks down */ char name[MAXPLEXNAME]; /* name of plex */ + dev_t dev; }; /*** Volume definitions ***/ @@ -537,6 +539,7 @@ int plex[MAXPLEX]; /* index of plexes */ char name[MAXVOLNAME]; /* name of volume */ struct disklabel label; /* for DIOCGPART */ + dev_t dev; }; /* -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 19 2: 7: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail-ob.kamp.net (mail-ob.kamp.net [195.62.97.26]) by hub.freebsd.org (Postfix) with ESMTP id 571E037B491 for ; Mon, 19 Feb 2001 02:07:06 -0800 (PST) Received: from bsdevil.meta.net.ob.kamp.net (port-51.d.kamp.de [195.62.120.243]) by mail-ob.kamp.net (8.10.1/8.10.1) with ESMTP id f1JA6xD17073; Mon, 19 Feb 2001 11:07:01 +0100 Date: Mon, 19 Feb 2001 11:07:00 +0100 Message-Id: <200102191007.f1JA6xD17073@mail-ob.kamp.net> From: Farid Hajji To: pete@ns.altadena.net Cc: current@FreeBSD.ORG In-reply-to: <200102190233.f1J2XpC25216@ns.altadena.net> (message from Pete Carah on Sun, 18 Feb 2001 18:33:51 -0800 (PST)) Subject: Re: Make kernel fail in modules after upgrade 4.2 -> 5.0 X-Mailer: Emacs-20.7.1/FreeBSD-5.0-CURRENT Reply-To: farid.hajji@ob.kamp.net References: <200102190233.f1J2XpC25216@ns.altadena.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > During the fixing stages of the libc problem, vinum caused panics fairly > regularly for me (very early on or during fsck). > > I'm now seeing panics in ufs write after medium heavy activity (make world, > no -j) on SMP, no reg dump comes out. Complains about table inconsistent > (don't remember the precise message). Hopefully my hardware is OK; this > machine has been stable for several weeks with upgraded RAM. I've just upgraded from 2001-01-25 to 2001-02-18:0100 CET and everyting seemed to work fine for me... Well, that was not true: The new kernel panics during dump(8), even when running in single user mode. This error is reproducible, though not at exactly the same number of dumped bytes (the dump file is more or less big). Shutting down now frequently leaves unflushed buffers too. I'm just rebuilding with DDB now... Anyone experiencing problems while dumping? Thanks, -Farid. -- Farid Hajji -- Unix Systems and Network Admin | Phone: +49-2131-67-555 Broicherdorfstr. 83, D-41564 Kaarst, Germany | farid.hajji@ob.kamp.net - - - - - - - - - - - - - - - - - - - - - - - + - - - - - - - - - - - - Murphy's Law fails only when you try to demonstrate it, and thus succeeds. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 19 3:18:26 2001 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-165-226-53.dsl.lsan03.pacbell.net [64.165.226.53]) by hub.freebsd.org (Postfix) with ESMTP id 00FF237B491 for ; Mon, 19 Feb 2001 03:18:24 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id CF3DA66E74; Mon, 19 Feb 2001 03:18:23 -0800 (PST) Date: Mon, 19 Feb 2001 03:18:23 -0800 From: Kris Kennaway To: Herman Tan Cc: current@FreeBSD.ORG Subject: Re: updating from 12/25/1999 -current? Message-ID: <20010219031823.A42403@mollari.cthul.hu> References: <20010219091913.19842.qmail@web2905.mail.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="azLHFNyN32YCQGCU" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010219091913.19842.qmail@web2905.mail.yahoo.com>; from mengtrading@rocketmail.com on Mon, Feb 19, 2001 at 01:19:13AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --azLHFNyN32YCQGCU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Feb 19, 2001 at 01:19:13AM -0800, Herman Tan wrote: > Greetings everyone: >=20 > Will I run into any problems doing a make world from a > 12/25/1999 version of -CURRENT to the latest -current? > I noticed on -RELEASE machines when I went from=20 > 3.3-R to 4.1-R, I had problems because the loaded > kernel doesn't have the modules and I had to use the > Generic kernel in 4.1R and reboot the machine. Any > suggestions? Thanks. It can probably be done, perhaps with a bit of hoop-jumping (see /usr/src/UPDATING), but you may find a binary upgrade to be easier. Kris --azLHFNyN32YCQGCU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6kQD/Wry0BWjoQKURAurNAJ9KymO0pHR7ZqcFW4aPBrVM8eECKQCfaXhO ohfJiY3nbV4MulPincY/OfA= =857/ -----END PGP SIGNATURE----- --azLHFNyN32YCQGCU-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 19 3:42:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail-ob.kamp.net (mail-ob.kamp.net [195.62.97.26]) by hub.freebsd.org (Postfix) with ESMTP id 50F6837B4EC for ; Mon, 19 Feb 2001 03:42:18 -0800 (PST) Received: from bsdevil.meta.net.ob.kamp.net (port-48.d.kamp.de [195.62.120.240]) by mail-ob.kamp.net (8.10.1/8.10.1) with ESMTP id f1JBgBD20663 for ; Mon, 19 Feb 2001 12:42:13 +0100 Date: Mon, 19 Feb 2001 12:42:11 +0100 Message-Id: <200102191142.f1JBgBD20663@mail-ob.kamp.net> From: Farid Hajji To: current@freebsd.org Subject: Kernel panic while dumping (even in single user mode). X-Mailer: Emacs-20.7.1/FreeBSD-5.0-CURRENT Reply-To: farid.hajji@ob.kamp.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, the kernel panics while dump(8)ing /usr, even in single user mode. This is what DDB says: Fatal trap 12: page fault while in kernel mode fault virtual address = 0xffffffff fault code = supervisor read, page not present instruction pointer = 0x8:0xffffffff stack pointer = 0x10:0xc86ebcc0 frame pointer = 0x10:0xc86ebd5c code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL=0 current process = 46 (dump) kernel: type 12 trap, code = 0 Stopped at -0x1: Fatal trap 12: page fault while in kernel mode fault virtual address = 0xffffffff fault code = supervisor read, page not present instruction pointer = 0x8:0xc02745ec stack pointer = 0x10:0xc86ebb28 frame pointer = 0x10:0xc86ebb2c code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL=0 current process = 46 (dump) kernel: type 12 trap, code = 0 Stopped at -0x1: This is my kernel config: # MYTWR: Farid's Machine running FreeBSD-5.0 CURRENT # $Id: MYTWR,v 2.5 2001/02/19 09:43:30 root Exp $ machine i386 cpu I586_CPU ident MYTWR maxusers 32 #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols options DDB #Enable kernel debugger. options MAXMEM="(128*1024)" options MAXDSIZ="(256*1024*1024)" # Allow max. 256 MB of Virtual RAM options DFLDSIZ="(128*1024*1024)" # Can be user-changed up to MAXDSIZ # strings -n 3 /kernel | sed -n 's/^___//p' > MYTWR.from.kernel options INCLUDE_CONFIG_FILE #Include this file in kerneLl options INET #InterNETworking options FFS #Berkeley Fast Filesystem options SOFTUPDATES #Enables FFS soft updates support #options MFS #Memory Filesystem #options MD_ROOT #MD is a potential root device options NFS #Network Filesystem #options NFS_ROOT #NFS usable as root device, NFS required # The following are optional (loaded when needed) #options MSDOSFS #MSDOS Filesystem #options CD9660 #ISO 9660 Filesystem #options DEVFS #Device Filesystem #options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=8000 #Delay (in ms) before probing SCSI options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor #options KTRACE #Needed by SvrV4 Emulator (slower) options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options KBD_INSTALL_CDEV # install a CDEV entry in /dev device isa device eisa device pci # Floppy drives device fdc # Floppy Device Controller # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives options ATA_STATIC_ID #Static device numbering #options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices # SCSI Controllers device ahc # AHA2940 and onboard AIC7xxx devices # SCSI peripherals device scbus # SCSI bus (required) device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc 1 # Keyboard and PS/2 mouse device atkbd # The AT-Keyboard. device vga # Video driver. #options VESA # Support for VESA Video Modes # splash screen/screen saver device splash # syscons is the default console driver, resembling an SCO console device sc 1 options MAXCONS=10 # Maximum number of virtual consoles options SC_NORM_ATTR="(FG_GREEN|BG_BLACK)" options SC_NORM_REV_ATTR="(FG_YELLOW|BG_GREEN)" options SC_KERNEL_CONS_ATTR="(FG_RED|BG_BLACK)" options SC_KERNEL_CONS_REV_ATTR="(FG_BLACK|BG_RED)" # Floating point support - do not disable. device npx #Mandatory, don't remove! # Sound-Support with Luigi's code: device sbc # Soundblaster Bridge-Code to pcm device pcm # PnP/PCI Sound Cards #device midi # Midi interfaces #device seq # Sequencer # Serial (COM) ports device sio #Serial Devices # Parallel port device ppc # ISA-Bus parallel port interface device ppbus # Parallel port bus (required) device lpt # Printer device plip # TCP/IP over parallel device ppi # Parallel port interface device #device vpo # Requires scbus and da # ISA Ethernet NICs. device ed # SMC Ultra, settings in /boot/hints # Pseudo devices - the number indicates how many units to allocated. device random # Random Entropy Pool. device loop # Network loopback device ether # Ethernet support device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) #device md # Memory "disks" device bpf # Berkeley packet filter # NOTE: vn is depracated, used md instead. #device vn # VNode driver (turns a file into a device) # ---- options USER_LDT #allow user-level control of i386 ldt options ROOTDEVNAME=\"ufs:da0s1a\" options EXT2FS #Linux ext2 filesystem options ENABLE_VFS_IOOPT #vfs.ioopt=0(noopt),1(normal),2(aggr.) options _KPOSIX_VERSION=199309L # This is only needed for PPPoE (more NETGRAPH_* options in NOTES) #options NETGRAPH #netgraph(4) system #options NETGRAPH_PPP #options NETGRAPH_PPPOE # The following options are _dangerous_ (but work on my hardware) #options AUTO_EOI_1 #options AUTO_EOI_2 # <- This is especially DANGEROUS! #options AHC_ALLOW_MEMIO # aic7xxx memory mapped i/o And this is dmesg output: farid@bsdevil:~> /sbin/dmesg Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Mon Feb 19 11:21:32 CET 2001 root@bsdevil.meta.net:/usr/obj/usr/src/sys/MYTWR Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 199432836 Hz CPU: Pentium/P54C (199.43-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping = 12 Features=0x1bf real memory = 134217728 (131072K bytes) config> di psm0 config> di sn0 config> di lnc0 config> di le0 config> di ie0 config> di fe0 config> di cs0 config> di bt0 config> di aic0 config> di aha0 config> di adv0 config> en ed0 config> po ed0 0x300 config> ir ed0 11 config> iom ed0 0xc8000 config> f ed0 0 config> q avail memory = 126947328 (123972K bytes) Preloaded elf kernel "kernel" at 0xc039e000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc039e09c. Intel Pentium detected, installing workaround for F00F bug WARNING: size of kinfo_proc (648) should be 644!!! npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xe800-0xe80f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 pci0: at 9.0 (no driver attached) ahc0: port 0xe000-0xe0ff mem 0xfa000000-0xfa000fff irq 12 at device 10.0 on pci0 aic7880: Wide Channel A, SCSI Id=7, 16/255 SCBs isa0: unexpected small tag 14 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 ed0 at port 0x300-0x31f iomem 0xc8000-0xcbfff irq 11 drq 0 on isa0 ed0: address 00:00:c0:9b:e1:a8, type SMC8216/SMC8216C (16 bit) fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/15 bytes threshold plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sc0: at flags 0x100 on isa0 sc0: VGA <10 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources sbc0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 pcm1: on sbc0 ata0-master: DMA limited to UDMA33, non-ATA66 compliant cable ad0: 19464MB [39546/16/63] at ata0-master WDMA2 acd0: CDROM at ata0-slave using PIO3 Waiting 8 seconds for SCSI devices to settle Mounting root from ufs:/dev/ad0s1a cd0 at ahc0 bus 0 target 4 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) I'm trying to dump an IDE drive (main drive) on an msdos filesystem written on a SCSI disk (ahc driver). This is the command (in single user mode!) that caused the dump: # cd /msdos/dump/dump.8 # dump -0u -B 10000000 -f usr-fs.l0.dump /usr /usr was not even mounted at this time. I just upgraded from CURRENT 2001-01-25 to 2001-02-18:0100 CET. Everything else _seems_ to work sofar (no libc problems etc...). The panic is new (I've never had a panic in this situation with the old kernel). The error above is reproducible. Another problem is when shutting down: at least one buffer is never flushed => enforcing fsck at next reboot. Something's wrong. What's going on here? Thanks, -Farid. -- Farid Hajji -- Unix Systems and Network Admin | Phone: +49-2131-67-555 Broicherdorfstr. 83, D-41564 Kaarst, Germany | farid.hajji@ob.kamp.net - - - - - - - - - - - - - - - - - - - - - - - + - - - - - - - - - - - - Murphy's Law fails only when you try to demonstrate it, and thus succeeds. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 19 4:12: 3 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id E31FA37B4EC for ; Mon, 19 Feb 2001 04:11:58 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id XAA06666; Mon, 19 Feb 2001 23:11:42 +1100 Date: Mon, 19 Feb 2001 23:11:11 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Coleman Kane Cc: "Andrey A. Chernov" , freebsd-current@FreeBSD.ORG Subject: Re: 3dfx -current compile error In-Reply-To: <20010219030607.A46836@cokane.yi.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 Mon, 19 Feb 2001, Coleman Kane wrote: > Yeah, this seems to be broken across all modules. I don't know what's going on, > but it seems like it never bothers to make the *.o targets. The reason mine > pops up with the error is that, alphabetically, it is first on the list. If you > remove it from the ports Makefile, the accf_data module brings up the error. I > noticed a lot of commit traffic for config, src/share/mk, make and the like, so > I figured this to be a 'commit in process' issue. I'm forwarding this to > -current mailing list to let them know about the prob. This is because there is now an explicit rule for everything in ${OBJS} (and some other wrong things), so the suffix rule doesn't get used, and objects are "built" by removing .depend. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 19 4:29:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from www.evil.2y.net (ip-216-23-53-155.adsl.one.net [216.23.53.155]) by hub.freebsd.org (Postfix) with ESMTP id 85C2C37B401 for ; Mon, 19 Feb 2001 04:29:39 -0800 (PST) Received: (from cokane@localhost) by www.evil.2y.net (8.11.2/8.11.1) id f1JCgqT71759; Mon, 19 Feb 2001 07:42:52 -0500 (EST) (envelope-from cokane) Date: Mon, 19 Feb 2001 07:42:52 -0500 From: Coleman Kane To: Bruce Evans Cc: Coleman Kane , "Andrey A. Chernov" , freebsd-current@FreeBSD.ORG Subject: Re: 3dfx -current compile error Message-ID: <20010219074252.B71200@cokane.yi.org> References: <20010219030607.A46836@cokane.yi.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="HG+GLK89HZ1zG0kk" X-Mailer: Mutt 1.0.1i In-Reply-To: ; from bde@zeta.org.au on Mon, Feb 19, 2001 at 07:11:50AM -0500 X-Vim: vim:tw=70:ts=4:sw=4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --HG+GLK89HZ1zG0kk Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable So, do you need me to do anything or just wait until it gets worked out? Bruce Evans had the audacity to say: >=20 > On Mon, 19 Feb 2001, Coleman Kane wrote: >=20 > > Yeah, this seems to be broken across all modules. I don't know what's g= oing on, > > but it seems like it never bothers to make the *.o targets. The reason = mine=20 > > pops up with the error is that, alphabetically, it is first on the list= . If you > > remove it from the ports Makefile, the accf_data module brings up the e= rror. I > > noticed a lot of commit traffic for config, src/share/mk, make and the = like, so > > I figured this to be a 'commit in process' issue. I'm forwarding this t= o=20 > > -current mailing list to let them know about the prob. >=20 > This is because there is now an explicit rule for everything in ${OBJS} > (and some other wrong things), so the suffix rule doesn't get used, and > objects are "built" by removing .depend. >=20 > Bruce >=20 --HG+GLK89HZ1zG0kk Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6kRTKERViMObJ880RAaSZAJ4rS5gygVkSauMkhukxPGYNEK+ECQCfQu0F xRjgN1yaI0MJ0r+CRiPHKPk= =ZIOU -----END PGP SIGNATURE----- --HG+GLK89HZ1zG0kk-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 19 8: 8: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from dsl.MexComUSA.net (adsl-63-200-120-86.dsl.mtry01.pacbell.net [63.200.120.86]) by hub.freebsd.org (Postfix) with ESMTP id BDD0F37B491 for ; Mon, 19 Feb 2001 08:08:03 -0800 (PST) Received: (from root@localhost) by dsl.MexComUSA.net (8.11.2/8.11.1) id f1JG2pv52343 for freebsd-current@FreeBSD.ORG; Mon, 19 Feb 2001 08:02:51 -0800 (PST) (envelope-from eculp@EnContacto.Net) Received: from 63.205.16.203 ( [63.205.16.203]) as user eculp@EnContacto.Net by Mail.MexComUSA.net with HTTP; Mon, 19 Feb 2001 08:02:48 -0800 Message-ID: <982598568.3a9143a8419de@Mail.MexComUSA.net> Date: Mon, 19 Feb 2001 08:02:48 -0800 From: Edwin Culp To: freebsd-current@FreeBSD.ORG Subject: Re: 3dfx -current compile error References: <20010219030607.A46836@cokane.yi.org> <20010219074252.B71200@cokane.yi.org> In-Reply-To: <20010219074252.B71200@cokane.yi.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 2.3.7-cvs X-Originating-IP: 63.205.16.203 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've got the same problem on my laptop. Quoting Coleman Kane : > So, do you need me to do anything or just wait until it gets worked out? > > Bruce Evans had the audacity to say: > > > > On Mon, 19 Feb 2001, Coleman Kane wrote: > > > > > Yeah, this seems to be broken across all modules. I don't know what's > going on, > > > but it seems like it never bothers to make the *.o targets. The reason > mine > > > pops up with the error is that, alphabetically, it is first on the list. > If you > > > remove it from the ports Makefile, the accf_data module brings up the > error. I > > > noticed a lot of commit traffic for config, src/share/mk, make and the > like, so > > > I figured this to be a 'commit in process' issue. I'm forwarding this to > > > > -current mailing list to let them know about the prob. > > > > This is because there is now an explicit rule for everything in ${OBJS} > > (and some other wrong things), so the suffix rule doesn't get used, and > > objects are "built" by removing .depend. > > > > Bruce > > > -- EnContacto.Net - InternetSalon.Org - CafeMania.Net ------------------------------------------------- EnContacto.Net - CafeMania.Net - InternetSalon.Org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 19 8:22:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14]) by hub.freebsd.org (Postfix) with ESMTP id 26AF437B401 for ; Mon, 19 Feb 2001 08:22:04 -0800 (PST) Received: from beagle (beagle [193.175.132.100]) by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id RAA04392; Mon, 19 Feb 2001 17:21:53 +0100 (MET) Date: Mon, 19 Feb 2001 17:21:53 +0100 (CET) From: Harti Brandt To: Edwin Culp Cc: Subject: Re: 3dfx -current compile error In-Reply-To: <982598568.3a9143a8419de@Mail.MexComUSA.net> 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 Mon, 19 Feb 2001, Edwin Culp wrote: Reverting /usr/src/sys/conf/kmod.mk to rev. 1.90 fixes the problem for the moment. harti EC>I've got the same problem on my laptop. EC> EC> EC>Quoting Coleman Kane : EC> EC>> So, do you need me to do anything or just wait until it gets worked out? EC>> EC>> Bruce Evans had the audacity to say: EC>> > EC>> > On Mon, 19 Feb 2001, Coleman Kane wrote: EC>> > EC>> > > Yeah, this seems to be broken across all modules. I don't know what's EC>> going on, EC>> > > but it seems like it never bothers to make the *.o targets. The reason EC>> mine EC>> > > pops up with the error is that, alphabetically, it is first on the list. EC>> If you EC>> > > remove it from the ports Makefile, the accf_data module brings up the EC>> error. I EC>> > > noticed a lot of commit traffic for config, src/share/mk, make and the EC>> like, so EC>> > > I figured this to be a 'commit in process' issue. I'm forwarding this to EC>> EC>> > > -current mailing list to let them know about the prob. EC>> > EC>> > This is because there is now an explicit rule for everything in ${OBJS} EC>> > (and some other wrong things), so the suffix rule doesn't get used, and EC>> > objects are "built" by removing .depend. EC>> > EC>> > Bruce EC>> > EC>> EC> EC> EC> EC> -- harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private brandt@fokus.gmd.de, harti@begemot.org, lhbrandt@mail.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 19 8:29: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from dsl.MexComUSA.net (adsl-63-200-120-86.dsl.mtry01.pacbell.net [63.200.120.86]) by hub.freebsd.org (Postfix) with ESMTP id 5590D37B4EC for ; Mon, 19 Feb 2001 08:28:59 -0800 (PST) Received: (from root@localhost) by dsl.MexComUSA.net (8.11.2/8.11.1) id f1JGNhK57729; Mon, 19 Feb 2001 08:23:43 -0800 (PST) (envelope-from eculp@EnContacto.Net) Received: from 63.205.16.203 ( [63.205.16.203]) as user eculp@EnContacto.Net by Mail.MexComUSA.net with HTTP; Mon, 19 Feb 2001 08:23:42 -0800 Message-ID: <982599822.3a91488ea753c@Mail.MexComUSA.net> Date: Mon, 19 Feb 2001 08:23:42 -0800 From: Edwin Culp To: Harti Brandt Cc: freebsd-current@FreeBSD.ORG Subject: Re: 3dfx -current compile error References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 2.3.7-cvs X-Originating-IP: 63.205.16.203 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting Harti Brandt : > On Mon, 19 Feb 2001, Edwin Culp wrote: > > Reverting /usr/src/sys/conf/kmod.mk to rev. 1.90 fixes the problem for > the moment. > > harti Thanks, I'll do that right now. ed ------------------------------------------------- EnContacto.Net - CafeMania.Net - InternetSalon.Org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 19 8:54:18 2001 Delivered-To: freebsd-current@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id A801E37B503 for ; Mon, 19 Feb 2001 08:54:12 -0800 (PST) Received: (from uucp@localhost) by ns.internet.dk (8.11.2/8.11.2) id f1JGsA189888 for freebsd-current@FreeBSD.ORG.AVP; Mon, 19 Feb 2001 17:54:10 +0100 (CET) (envelope-from leifn@neland.dk) Received: (from uucp@localhost) by ns.internet.dk (8.11.2/8.11.2) with UUCP id f1JGsAq89882 for freebsd-current@FreeBSD.ORG; Mon, 19 Feb 2001 17:54:10 +0100 (CET) (envelope-from leifn@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.11.1/8.11.0) with SMTP id f1JGrvx71268 for ; Mon, 19 Feb 2001 17:54:03 +0100 (CET) (envelope-from leifn@neland.dk) Message-ID: <00d001c09a94$b280d9c0$0e00a8c0@neland.dk> Reply-To: "Leif Neland" From: "Leif Neland" Cc: References: <20010216025147.A25002@dragon.nuxi.com> <20010216104409.A99749@enigma.whacky.net> <20010216025147.A25002@dragon.nuxi.com> <200102161703.f1GH37E29782@billy-club.village.org> <20010217101500.A10023@enigma.whacky.net> Subject: Do we need a 3. level between stable and cuurent? Date: Mon, 19 Feb 2001 17:54:53 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by ns.internet.dk id f1JGsAq89882 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We all know: -current is bleeding edge, expect it to break at random. Don't run it if you don't know how to fix it. -stable is for production, it works all the time. Do we need a level in between for people who just run current for the fun of it and for testing. So after the hardcore has tested it in -current, they commit it to all the monkeys trying to break it, and we then try it on n^m' combinations of hardware/software. I might not be able to fix a problem, but I can report what happens, and if my -current breaks for a few days, it is no big deal. While -current is not for everybody, I believe people like me helps in quality testing before the stuff hits -stable. Perhaps not a level, just a separate file, which contained the date of the last known version without known major problems. (or "." if no known problems) Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 19 9: 8:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from mls.gtonet.net (mls.gtonet.net [216.112.90.195]) by hub.freebsd.org (Postfix) with ESMTP id E8CE537B491 for ; Mon, 19 Feb 2001 09:08:28 -0800 (PST) Received: from pld (pld.gtonet.net [216.112.90.200]) by mls.gtonet.net (8.11.2/8.11.2) with SMTP id f1JH8Sb50601 for ; Mon, 19 Feb 2001 09:08:29 -0800 (PST) (envelope-from oldfart@gtonet.net) Reply-To: From: "oldfart@gtonet" To: "freebsd-current@FreeBSD. ORG" Subject: RE: Do we need a 3. level between stable and cuurent? Date: Mon, 19 Feb 2001 09:08:27 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal In-Reply-To: <00d001c09a94$b280d9c0$0e00a8c0@neland.dk> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: owner-freebsd-current@FreeBSD.ORG > [mailto:owner-freebsd-current@FreeBSD.ORG]On Behalf Of Leif Neland > Sent: Monday, February 19, 2001 8:55 AM > Cc: freebsd-current@FreeBSD.ORG > Subject: Do we need a 3. level between stable and cuurent? > > > We all know: -current is bleeding edge, expect it to break at > random. Don't run it if you don't know how to fix it. > -stable is for production, it works all the time. > -RELEASE, I thought, is for production. Although, it's true, -STABLE rarely has a stop. > Do we need a level in between for people who just run current for > the fun of it and for testing. > So after the hardcore has tested it in -current, they commit it > to all the monkeys trying to break it, and we then try it on n^m' > combinations of hardware/software. Actually, I've always thought that's what -STABLE is for? > I might not be able to fix a problem, but I can report what > happens, and if my -current breaks for a few days, it is no big deal. > > While -current is not for everybody, I believe people like me > helps in quality testing before the stuff hits -stable. Actually, I've always thought that's what -STABLE is for? Deja-vu :) > Perhaps not a level, just a separate file, which contained the > date of the last known version without known major problems. (or > "." if no known problems) I think the current HEADS UP given on here is sufficient warning to determine if a make world will build or if there are stops. YMMV OF > > Leif > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 19 9:22:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from teebar.directski.com (mauer.directski.com [193.95.161.233]) by hub.freebsd.org (Postfix) with ESMTP id 4625A37B401 for ; Mon, 19 Feb 2001 09:22:53 -0800 (PST) Received: from directski.com (dermot.traveldev.com [192.168.0.50]) by teebar.directski.com (8.11.1/8.11.1) with ESMTP id f1JHMgq99272; Mon, 19 Feb 2001 17:22:43 GMT (envelope-from dermot@directski.com) Message-ID: <3A915663.5348C9F3@directski.com> Date: Mon, 19 Feb 2001 17:22:43 +0000 From: Dermot McNally X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U) X-Accept-Language: de,en MIME-Version: 1.0 To: oldfart@gtonet.net Cc: "freebsd-current@FreeBSD. ORG" Subject: Re: Do we need a 3. level between stable and cuurent? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "oldfart@gtonet" wrote: > -RELEASE, I thought, is for production. Although, it's true, -STABLE rarely > has a stop. Nope, -STABLE is for production, -RELEASE is for installing immediately prior to upgrading it to -STABLE. X.X-STABLE = X.X-RELEASE + fixes + carefully selected stuff that has been well tested in -CURRENT. Dermot -- --------------------------------------------------------------- Dermot McNally, Chief Technical Officer, Directski.com dermot@directski.com http://www.directski.com - ski the web To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 19 9:24:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from mls.gtonet.net (mls.gtonet.net [216.112.90.195]) by hub.freebsd.org (Postfix) with ESMTP id 11B0C37B4EC for ; Mon, 19 Feb 2001 09:24:54 -0800 (PST) Received: from pld (pld.gtonet.net [216.112.90.200]) by mls.gtonet.net (8.11.2/8.11.2) with SMTP id f1JHOrb50690 for ; Mon, 19 Feb 2001 09:24:54 -0800 (PST) (envelope-from oldfart@gtonet.net) Reply-To: From: "oldfart@gtonet" To: "freebsd-current@FreeBSD. ORG" Subject: RE: Do we need a 3. level between stable and cuurent? Date: Mon, 19 Feb 2001 09:24:52 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal In-Reply-To: <3A915663.5348C9F3@directski.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I stand corrected... > -----Original Message----- > From: Dermot McNally [mailto:dermot@directski.com] > Sent: Monday, February 19, 2001 9:23 AM > To: oldfart@gtonet.net > Cc: freebsd-current@FreeBSD. ORG > Subject: Re: Do we need a 3. level between stable and cuurent? > > > "oldfart@gtonet" wrote: > > > -RELEASE, I thought, is for production. Although, it's true, > -STABLE rarely > > has a stop. > > Nope, -STABLE is for production, -RELEASE is for installing immediately > prior to upgrading it to -STABLE. X.X-STABLE = X.X-RELEASE + fixes + > carefully selected stuff that has been well tested in -CURRENT. > > Dermot > > -- > --------------------------------------------------------------- > Dermot McNally, Chief Technical Officer, Directski.com > dermot@directski.com http://www.directski.com - ski the web To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 19 9:41:13 2001 Delivered-To: freebsd-current@freebsd.org Received: from FreeBSD.org (qix.dalai-zebu.org [62.4.22.91]) by hub.freebsd.org (Postfix) with ESMTP id 17C3737B4EC for ; Mon, 19 Feb 2001 09:41:10 -0800 (PST) Received: (from jmz@localhost) by qix.dalai-zebu.org (8.11.0/8.11.0) id f1JHdgT88781; Mon, 19 Feb 2001 18:39:42 +0100 (MET) (envelope-from jmz@FreeBSD.org) From: Jean-Marc Zucconi MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14993.23133.880042.179955@qix.dalai-zebu.org> Date: Mon, 19 Feb 2001 18:39:41 +0100 To: freebsd-current@FreeBSD.org Subject: make world breakage X-Mailer: Emacs 20.7.1 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sources updated yesterday: ===> sbin/mountd cc -O -pipe -DNFS -DMFS -DCD9660 -DMSDOSFS -c /usr/src/sbin/mountd/mountd.c /usr/src/sbin/mountd/mountd.c:164: warning: `struct xucred' declared inside parameter list /usr/src/sbin/mountd/mountd.c:164: warning: its scope is only this definition or declaration, which is probably not what you want. /usr/src/sbin/mountd/mountd.c:166: warning: `struct xucred' declared inside parameter list /usr/src/sbin/mountd/mountd.c:187: warning: `struct xucred' declared inside parameter list /usr/src/sbin/mountd/mountd.c:205: variable `def_anon' has initializer but incomplete type /usr/src/sbin/mountd/mountd.c:206: warning: excess elements in struct initializer /usr/src/sbin/mountd/mountd.c:206: warning: (near initialization for `def_anon') /usr/src/sbin/mountd/mountd.c:207: warning: excess elements in struct initializer /usr/src/sbin/mountd/mountd.c:207: warning: (near initialization for `def_anon') /usr/src/sbin/mountd/mountd.c:208: warning: excess elements in struct initializer /usr/src/sbin/mountd/mountd.c:208: warning: (near initialization for `def_anon') /usr/src/sbin/mountd/mountd.c:209: extra brace group at end of initializer /usr/src/sbin/mountd/mountd.c:209: (near initialization for `def_anon') /usr/src/sbin/mountd/mountd.c:209: warning: excess elements in struct initializer /usr/src/sbin/mountd/mountd.c:209: warning: (near initialization for `def_anon') /usr/src/sbin/mountd/mountd.c:211: warning: excess elements in struct initializer /usr/src/sbin/mountd/mountd.c:211: warning: (near initialization for `def_anon') /usr/src/sbin/mountd/mountd.c: In function `get_exportlist': /usr/src/sbin/mountd/mountd.c:736: storage size of `anon' isn't known /usr/src/sbin/mountd/mountd.c: In function `do_opt': /usr/src/sbin/mountd/mountd.c:1337: argument `cr' doesn't match prototype /usr/src/sbin/mountd/mountd.c:166: prototype declaration /usr/src/sbin/mountd/mountd.c:1376: warning: passing arg 2 of `parsecred' from incompatible pointer type /usr/src/sbin/mountd/mountd.c: In function `do_mount': /usr/src/sbin/mountd/mountd.c:1599: argument `anoncrp' doesn't match prototype /usr/src/sbin/mountd/mountd.c:164: prototype declaration /usr/src/sbin/mountd/mountd.c:1618: dereferencing pointer to incomplete type /usr/src/sbin/mountd/mountd.c: In function `parsecred': /usr/src/sbin/mountd/mountd.c:1847: argument `cr' doesn't match prototype /usr/src/sbin/mountd/mountd.c:187: prototype declaration /usr/src/sbin/mountd/mountd.c:1858: dereferencing pointer to incomplete type /usr/src/sbin/mountd/mountd.c:1859: dereferencing pointer to incomplete type /usr/src/sbin/mountd/mountd.c:1860: dereferencing pointer to incomplete type /usr/src/sbin/mountd/mountd.c:1878: dereferencing pointer to incomplete type /usr/src/sbin/mountd/mountd.c:1885: dereferencing pointer to incomplete type /usr/src/sbin/mountd/mountd.c:1886: dereferencing pointer to incomplete type /usr/src/sbin/mountd/mountd.c:1888: dereferencing pointer to incomplete type /usr/src/sbin/mountd/mountd.c:1896: dereferencing pointer to incomplete type /usr/src/sbin/mountd/mountd.c:1898: dereferencing pointer to incomplete type /usr/src/sbin/mountd/mountd.c:1903: dereferencing pointer to incomplete type /usr/src/sbin/mountd/mountd.c:1904: dereferencing pointer to incomplete type /usr/src/sbin/mountd/mountd.c:1907: dereferencing pointer to incomplete type /usr/src/sbin/mountd/mountd.c:1907: dereferencing pointer to incomplete type /usr/src/sbin/mountd/mountd.c:1913: dereferencing pointer to incomplete type /usr/src/sbin/mountd/mountd.c:1913: dereferencing pointer to incomplete type /usr/src/sbin/mountd/mountd.c:1916: dereferencing pointer to incomplete type *** Error code 1 Stop in /usr/src/sbin/mountd. *** Error code 1 Jean-Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 19 10: 6:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 4B3D237B6A3 for ; Mon, 19 Feb 2001 10:06:54 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA06606; Mon, 19 Feb 2001 10:06:45 -0800 Date: Mon, 19 Feb 2001 10:06:45 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Warner Losh Cc: current@FreeBSD.org Subject: Re: got stuck in the current __sF foo... In-Reply-To: <200102180157.f1I1vKW93062@harmony.village.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 > In message Matthew Jacob writes: > : One system got stuck in the current __sF bork... I'm not stuck with: > > : Any advice? > > Copy a pre Feb 10th libc.so.5 to this box. Alternatively, copy a Feb > 17 or later one. It turns out that no matter what I seem to do, I can't rebuild. I think I'll just do the big bomb approach and take another alpha (the Alpha 4100, of all things!) that managed to make it through unscathed and just clone it's disk. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 19 10:12:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from smtp.wanadoo.nl (smtp.wanadoo.nl [194.134.193.6]) by hub.freebsd.org (Postfix) with ESMTP id 1C21E37B491 for ; Mon, 19 Feb 2001 10:12:30 -0800 (PST) Received: from ams-gw.sohara.org (p659.vcu.wanadoo.nl [194.134.201.187]) by smtp.wanadoo.nl (8.9.3/8.9.3) with SMTP id TAA05290; Mon, 19 Feb 2001 19:12:21 +0100 (MET) Date: Mon, 19 Feb 2001 19:12:20 +0100 From: "Steve O'Hara-Smith" To: Dermot McNally Cc: oldfart@gtonet.net, freebsd-current@FreeBSD.ORG Subject: Re: Do we need a 3. level between stable and cuurent? Message-Id: <20010219191220.65638e71.steveo@eircom.net> In-Reply-To: <3A915663.5348C9F3@directski.com> References: <3A915663.5348C9F3@directski.com> X-Mailer: Sylpheed version 0.4.60 (GTK+ 1.2.8; FreeBSD 4.2-STABLE; i386) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Feb 2001 17:22:43 +0000 Dermot McNally wrote: DM> Nope, -STABLE is for production, -RELEASE is for installing immediately Indeed, in fact there has been at least one release that was *not* tagged for -STABLE (3.0). -- Tell a computer to WIN - you lose! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 19 10:26:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 741D237B401 for ; Mon, 19 Feb 2001 10:26:48 -0800 (PST) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id NAA08745; Mon, 19 Feb 2001 13:26:11 -0500 (EST) Date: Mon, 19 Feb 2001 13:26:11 -0500 (EST) From: Daniel Eischen To: Matthew Jacob Cc: Warner Losh , current@FreeBSD.ORG Subject: Re: got stuck in the current __sF foo... In-Reply-To: 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 Mon, 19 Feb 2001, Matthew Jacob wrote: > > In message Matthew Jacob writes: > > : One system got stuck in the current __sF bork... I'm not stuck with: > > > > : Any advice? > > > > Copy a pre Feb 10th libc.so.5 to this box. Alternatively, copy a Feb > > 17 or later one. > > It turns out that no matter what I seem to do, I can't rebuild. Going back from a library with __stdXXX changes to the compat __sF took 2 installworlds for me. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 19 10:30:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 76A7B37B491 for ; Mon, 19 Feb 2001 10:30:21 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f1JIUHI18068; Mon, 19 Feb 2001 10:30:17 -0800 (PST) Date: Mon, 19 Feb 2001 10:30:17 -0800 From: Alfred Perlstein To: Leif Neland Cc: freebsd-current@FreeBSD.ORG Subject: Re: Do we need a 3. level between stable and cuurent? Message-ID: <20010219103017.M6641@fw.wintelcom.net> References: <20010216025147.A25002@dragon.nuxi.com> <20010216104409.A99749@enigma.whacky.net> <20010216025147.A25002@dragon.nuxi.com> <200102161703.f1GH37E29782@billy-club.village.org> <20010217101500.A10023@enigma.whacky.net> <00d001c09a94$b280d9c0$0e00a8c0@neland.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <00d001c09a94$b280d9c0$0e00a8c0@neland.dk>; from leifn@neland.dk on Mon, Feb 19, 2001 at 05:54:53PM +0100 X-all-your-base: are belong to us. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Leif Neland [010219 08:54] wrote: > We all know: -current is bleeding edge, expect it to break at random. Don't run it if you don't know how to fix it. > -stable is for production, it works all the time. > > Do we need a level in between for people who just run current for the fun of it and for testing. > So after the hardcore has tested it in -current, they commit it to all the monkeys trying to break it, and we then try it on n^m' combinations of hardware/software. > > I might not be able to fix a problem, but I can report what happens, and if my -current breaks for a few days, it is no big deal. > > While -current is not for everybody, I believe people like me helps in quality testing before the stuff hits -stable. > > Perhaps not a level, just a separate file, which contained the date of the last known version without known major problems. (or "." if no known problems) This is a good idea, however it would take someone dedicated to maintaining this as well as doing regression testing. Those regression tests could easily be ported to -stable making for happier -stable as well as -current users. Are you volunteering? :) -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 19 12: 0: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 01DA837B503 for ; Mon, 19 Feb 2001 11:59:59 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA07011 for ; Mon, 19 Feb 2001 11:59:58 -0800 Date: Mon, 19 Feb 2001 11:59:57 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: current@freebsd.org Subject: pooched kernel stuff (linux) 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 looks like the usual drill for alpha, w/o lubricant: @/alpha/linux/linux_syscall.h:126: warning: `LINUX_SYS_linux_mount' redefined @/alpha/linux/linux_syscall.h:25: warning: this is the location of the previous definition In file included from /tstsys/modules/linux/../../compat/linux/linux_file.c:53: machine/../linux/linux_proto.h:346: redefinition of `struct linux_mount_args' machine/../linux/linux_proto.h:602: warning: redundant redeclaration of `linux_mount' in same scope machine/../linux/linux_proto.h:540: warning: previous declaration of `linux_mount' /tstsys/modules/linux/../../compat/linux/linux_file.c: In function `linux_mount': /tstsys/modules/linux/../../compat/linux/linux_file.c:910: structure has no member named `filesystemtype' /tstsys/modules/linux/../../compat/linux/linux_file.c:914: structure has no member named `specialfile' /tstsys/modules/linux/../../compat/linux/linux_file.c:917: structure has no member named `dir' /tstsys/modules/linux/../../compat/linux/linux_file.c:934: structure has no member named `rwflag' /tstsys/modules/linux/../../compat/linux/linux_file.c:945: structure has no member named `rwflag' /tstsys/modules/linux/../../compat/linux/linux_file.c:950: structure has no member named `rwflag' /tstsys/modules/linux/../../compat/linux/linux_file.c:952: structure has no member named `rwflag' /tstsys/modules/linux/../../compat/linux/linux_file.c:954: structure has no member named `rwflag' /tstsys/modules/linux/../../compat/linux/linux_file.c:956: structure has no member named `rwflag' /tstsys/modules/linux/../../compat/linux/linux_file.c:958: structure has no member named `rwflag' *** Error code 1 Stop in /tstsys/modules/linux. *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 19 13:45:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from mobile.hub.org (mobile.acadiau.ca [131.162.137.70]) by hub.freebsd.org (Postfix) with ESMTP id 6906B37B491 for ; Mon, 19 Feb 2001 13:45:27 -0800 (PST) Received: from localhost (scrappy@localhost) by mobile.hub.org (8.11.1/8.11.1) with ESMTP id f1JLjQi04973 for ; Mon, 19 Feb 2001 17:45:26 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: mobile.hub.org: scrappy owned process doing -bs Date: Mon, 19 Feb 2001 17:45:25 -0400 (AST) From: The Hermit Hacker To: Subject: proper kernel config procedure ... 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 it u sed to be that one would do 'config -r ' to config a kernel, so that it removed the old /sys/compile/ directory ... -r was removed, so is it no longer required to remove the old directory before building the new kernel, or ... ? Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 19 14:18:19 2001 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id CF2D737B491 for ; Mon, 19 Feb 2001 14:18:15 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id RAA11504; Mon, 19 Feb 2001 17:18:13 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.2/8.9.1) id f1JMHhe06969; Mon, 19 Feb 2001 17:17:43 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14993.39815.448274.905277@grasshopper.cs.duke.edu> Date: Mon, 19 Feb 2001 17:17:43 -0500 (EST) To: mjacob@feral.com Cc: current@freebsd.org Subject: Re: pooched kernel stuff (linux) In-Reply-To: References: X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Jacob writes: > > looks like the usual drill for alpha, w/o lubricant: > > @/alpha/linux/linux_syscall.h:126: warning: `LINUX_SYS_linux_mount' redefined > @/alpha/linux/linux_syscall.h:25: warning: this is the location of the > previous definition > In file included from > /tstsys/modules/linux/../../compat/linux/linux_file.c:53: > machine/../linux/linux_proto.h:346: redefinition of `struct linux_mount_args' > machine/../linux/linux_proto.h:602: warning: redundant redeclaration of > `linux_mount' in same scope > machine/../linux/linux_proto.h:540: warning: previous declaration of > `linux_mount' > /tstsys/modules/linux/../../compat/linux/linux_file.c: In function > `linux_mount': > /tstsys/modules/linux/../../compat/linux/linux_file.c:910: structure has no Sigh. I'll take a whack at fixing it when I get my -current alpha working again. It got pooched last week during the libc mixup. Speaking of which -- I've got 2 disks on this box. ad0 is -stable and da0 is -current. I'm building the -current world right now with everything mounted under /mnt. When I'm done, is it safe to just install the world with 'make installworld DESTDIR=/mnt' ? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 19 14:26:38 2001 Delivered-To: freebsd-current@freebsd.org Received: from volatile.chemikals.org (ci391991-a.grnvle1.sc.home.com [24.6.40.144]) by hub.freebsd.org (Postfix) with ESMTP id CBA7637B491 for ; Mon, 19 Feb 2001 14:26:32 -0800 (PST) Received: (from morganw@localhost) by volatile.chemikals.org (8.11.2/8.11.1) id f1JMQTl63609; Mon, 19 Feb 2001 17:26:29 -0500 (EST) (envelope-from morganw) Date: Mon, 19 Feb 2001 17:26:29 -0500 (EST) From: Wesley Morgan To: Subject: name resolution problems 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 Since the big shake-up with -current, I find that mozilla and galeon can no longer function (both up to date), but lynx has no problems. Mozilla seems stuck resolving hostnames, yet tcpdump shows no traffic and truss indicates that it is simply looping around a poll(). The biggest difference between lynx and mozilla in terms of name resolution is that mozilla is linked against libc_r... Could there be some problem here? Is anyone else seeing this? -- _ __ ___ ____ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ morganw@chemikals.org _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 19 15: 5:21 2001 Delivered-To: freebsd-current@freebsd.org Received: from sidonie.ods.org (APastourelles-101-1-4-125.abo.wanadoo.fr [193.253.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9055D37B401 for ; Mon, 19 Feb 2001 15:05:18 -0800 (PST) Received: from aglae (aglae [192.168.100.2]) by sidonie.ods.org (8.11.1/8.11.1) with ESMTP id f1JNQrB00986; Tue, 20 Feb 2001 00:26:55 +0100 (CET) (envelope-from f314116@yahoo.com) Date: Tue, 20 Feb 2001 00:05:04 +0100 (CET) From: Frederic Stark X-Sender: fred@aglae.ods.org Reply-To: Frederic Stark To: Wesley Morgan Cc: current@freebsd.org Subject: Re: name resolution problems In-Reply-To: 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 Mon, 19 Feb 2001, Wesley Morgan wrote: > Since the big shake-up with -current, I find that mozilla and galeon can > no longer function (both up to date), but lynx has no problems. Mozilla > seems stuck resolving hostnames, yet tcpdump shows no traffic and truss > indicates that it is simply looping around a poll(). The biggest > difference between lynx and mozilla in terms of name resolution is that > mozilla is linked against libc_r... Could there be some problem here? > Is anyone else seeing this? I see that too. I removed ~/.mozilla, and it works well, but only once. At next launch it get stuck in name resolution again, until I remove ~/.mozilla. Weird. Cheers, --fred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 19 15: 7:42 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 5241237B4EC for ; Mon, 19 Feb 2001 15:07:39 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id PAA07715; Mon, 19 Feb 2001 15:07:37 -0800 Date: Mon, 19 Feb 2001 15:07:37 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Andrew Gallatin Cc: current@FreeBSD.ORG Subject: Re: pooched kernel stuff (linux) In-Reply-To: <14993.39815.448274.905277@grasshopper.cs.duke.edu> 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 > > Speaking of which -- I've got 2 disks on this box. ad0 is -stable and > da0 is -current. I'm building the -current world right now with > everything mounted under /mnt. When I'm done, is it safe to just > install the world with 'make installworld DESTDIR=/mnt' ? Uh... don't know that one... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 19 15:54:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-165-226-53.dsl.lsan03.pacbell.net [64.165.226.53]) by hub.freebsd.org (Postfix) with ESMTP id D7A5A37B401 for ; Mon, 19 Feb 2001 15:54:24 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 442F066D46; Mon, 19 Feb 2001 15:54:24 -0800 (PST) Date: Mon, 19 Feb 2001 15:54:24 -0800 From: Kris Kennaway To: The Hermit Hacker Cc: freebsd-current@freebsd.org Subject: Re: proper kernel config procedure ... Message-ID: <20010219155424.A55214@mollari.cthul.hu> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="WIyZ46R2i8wDzkSu" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from scrappy@hub.org on Mon, Feb 19, 2001 at 05:45:25PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --WIyZ46R2i8wDzkSu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Feb 19, 2001 at 05:45:25PM -0400, The Hermit Hacker wrote: >=20 > it u sed to be that one would do 'config -r ' to config a kernel, so > that it removed the old /sys/compile/ directory ... -r was removed, > so is it no longer required to remove the old directory before building > the new kernel, or ... ? Yes. The dependency stuff all just works, you can 'make clean' if you really want to do a complete rebuild. Kris --WIyZ46R2i8wDzkSu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6kbIvWry0BWjoQKURAjUWAKDRvGlFoyGFGnB9/n1KmIFJ/9YYkwCg9KVv h+rPCZRa1Sjp4LGtvnGL3QE= =Mtxa -----END PGP SIGNATURE----- --WIyZ46R2i8wDzkSu-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 19 16: 6:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id E339C37B503 for ; Mon, 19 Feb 2001 16:06:38 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id QAA07972; Mon, 19 Feb 2001 16:06:23 -0800 Date: Mon, 19 Feb 2001 16:06:23 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Kris Kennaway Cc: The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: proper kernel config procedure ... In-Reply-To: <20010219155424.A55214@mollari.cthul.hu> 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 > > it u sed to be that one would do 'config -r ' to config a kernel, so > > that it removed the old /sys/compile/ directory ... -r was removed, > > so is it no longer required to remove the old directory before building > > the new kernel, or ... ? > > Yes. The dependency stuff all just works, you can 'make clean' if you > really want to do a complete rebuild. This doesn't work 100%. In particular if you have a sys that's not part of /usr/src/sys it doesn't always work. I've told Peter, but I think he thinks this is a real edge case. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 19 16:11:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-165-226-53.dsl.lsan03.pacbell.net [64.165.226.53]) by hub.freebsd.org (Postfix) with ESMTP id 6815837B401 for ; Mon, 19 Feb 2001 16:11:25 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 2F34C66C11; Mon, 19 Feb 2001 16:11:25 -0800 (PST) Date: Mon, 19 Feb 2001 16:11:25 -0800 From: Kris Kennaway To: Matthew Jacob Cc: Kris Kennaway , The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: proper kernel config procedure ... Message-ID: <20010219161124.A55759@mollari.cthul.hu> References: <20010219155424.A55214@mollari.cthul.hu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="17pEHd4RhPHOinZp" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from mjacob@feral.com on Mon, Feb 19, 2001 at 04:06:23PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --17pEHd4RhPHOinZp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Feb 19, 2001 at 04:06:23PM -0800, Matthew Jacob wrote: > > > it u sed to be that one would do 'config -r ' to config a kerne= l, so > > > that it removed the old /sys/compile/ directory ... -r was remo= ved, > > > so is it no longer required to remove the old directory before buildi= ng > > > the new kernel, or ... ? > >=20 > > Yes. The dependency stuff all just works, you can 'make clean' if you > > really want to do a complete rebuild. >=20 > This doesn't work 100%. In particular if you have a sys that's not part of > /usr/src/sys it doesn't always work. I've told Peter, but I think he thin= ks > this is a real edge case. Well, there's always rm -rf CONFIGDIR Kris --17pEHd4RhPHOinZp Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6kbYsWry0BWjoQKURAv6hAJ9R0RTg0zPZIhiyghadfwR19yNzXgCfecFp SotYtVtuvPdOlVoz8AjNq9c= =/G8p -----END PGP SIGNATURE----- --17pEHd4RhPHOinZp-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 19 16:13:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id CDBAC37B4EC for ; Mon, 19 Feb 2001 16:13:17 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id QAA08043; Mon, 19 Feb 2001 16:13:13 -0800 Date: Mon, 19 Feb 2001 16:13:13 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Kris Kennaway Cc: The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: proper kernel config procedure ... In-Reply-To: <20010219161124.A55759@mollari.cthul.hu> 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 > > /usr/src/sys it doesn't always work. I've told Peter, but I think he thinks > > this is a real edge case. > > Well, there's always rm -rf CONFIGDIR So I have concluded. Forward into the past! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 19 20: 3: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from wint.itfs.nsk.su (wint.itfs.nsk.su [212.20.32.43]) by hub.freebsd.org (Postfix) with ESMTP id C1FE037B491 for ; Mon, 19 Feb 2001 20:02:59 -0800 (PST) Received: (from nnd@localhost) by wint.itfs.nsk.su (8.11.2/8.11.1) id f1K42vr25483; Tue, 20 Feb 2001 10:02:57 +0600 (NOVT) (envelope-from nnd) Date: Tue, 20 Feb 2001 10:02:57 +0600 (NOVT) Message-Id: <200102200402.f1K42vr25483@wint.itfs.nsk.su> From: nnd@mail.nsk.ru To: current@FreeBSD.ORG Subject: Re: cvs commit: src/share/mk sys.mk In-Reply-To: <200102192333.f1JNXEd10589@freefall.freebsd.org> X-Newsgroups: itfs.freebsd.cvs.all User-Agent: tin/1.5.8-20010204 ("Paradise Regained") (UNIX) (FreeBSD/5.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > > Modified files: > share/mk sys.mk > Log: > Remove bogus setting of MACHINE_CPU here. There is no need for it. But there MUST be at least one setting for MACHINE_CPU for 'make buildworld' to succeed before new 'make' with this variable is in place. I can 'make installworld' after defining 'MACHINE_CPU= i686' in '/etc/make.conf'. Is it deservs some kind of HEADS UP ? N.Dudorov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 19 23:20: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id D152C37B491 for ; Mon, 19 Feb 2001 23:19:57 -0800 (PST) (envelope-from vallo@myhakas.matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id 79CC22CE93 for ; Tue, 20 Feb 2001 09:19:52 +0200 (EET) Received: (from vallo@localhost) by myhakas.matti.ee (8.11.2/8.11.2) id f1K7Jun69112 for freebsd-current@freebsd.org; Tue, 20 Feb 2001 09:19:56 +0200 (EET) (envelope-from vallo) Date: Tue, 20 Feb 2001 09:19:56 +0200 From: Vallo Kallaste To: freebsd-current@freebsd.org Subject: occasional filesystem corruption Message-ID: <20010220091956.A68889@myhakas.matti.ee> Reply-To: vallo@matti.ee Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.14i-ja0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I have experienced two filesystem corruption cases recently. Both took place in /usr filesystem, the first was file with very big negative size, other one was in mozilla port work tree where six files were lost in deep subdirectory and prevented make clean to clean up. Fsck did usual job and cleaned that up. /usr filesystem resides on SCSI disk and there are no problems with either disk or SCSI controller. Incidentally I haven't had any such problems before and these appeared after installing and using smbfs-1.3.5 port. I've built correct smbfs.ko module, defined SMP by hand in config.mk (it's SMP system). One SMB share stays mounted always, but gets rare use, some two accesses per day or so. I've discovered some kernel messages also, which occasionally appear until the share stays mounted. Any ideas? FreeBSD 5.0-CURRENT #0: Mon Feb 12 16:09:09 EET 2001 vallo@myhakas.matti.ee:/usr/src/sys/compile/Myhakas.SMP Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (501.14-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x672 Stepping = 2 Features=0x383fbff real memory = 268435456 (262144K bytes) avail memory = 257400832 (251368K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc03ab000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc03ab09c. Pentium Pro MTRR support enabled VESA: v2.0, 32768k memory, flags:0x1, mode table:0xc00c6954 (c0006954) VESA: Matrox Graphics Inc. npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard IOAPIC #0 intpin 16 -> irq 2 IOAPIC #0 intpin 18 -> irq 5 IOAPIC #0 intpin 19 -> irq 7 IOAPIC #0 intpin 17 -> irq 10 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 7.2 (no driver attached) Timecounter "PIIX" frequency 3579545 Hz pci0: at 7.3 (no driver attached) ahc0: port 0xe400-0xe4ff mem 0xfebfc000-0xfebfcfff irq 2 at device 11.0 on pci0 aic7896/97: Wide Channel A, SCSI Id=7, 32/255 SCBs ahc1: port 0xe800-0xe8ff mem 0xfebff000-0xfebfffff irq 2 at device 11.1 on pci0 aic7896/97: Wide Channel B, SCSI Id=7, 32/255 SCBs pcm0: port 0xed80-0xedbf irq 5 at device 12.0 on pci0 fxp0: port 0xee80-0xeebf mem 0xfe800000-0xfe8fffff,0xfebfd000-0xfebfdfff irq 7 at device 13.0 on pci0 fxp0: Ethernet address 00:e0:81:10:50:32 fxp1: port 0xef00-0xef3f mem 0xfea00000-0xfeafffff,0xfebfe000-0xfebfefff irq 10 at device 15.0 on pci0 fxp1: Ethernet address 00:90:27:54:57:26 ed0: port 0xef80-0xef9f irq 5 at device 18.0 on pci0 ed0: address 00:e0:29:6d:14:19, type NE2000 (16 bit) atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sc0: at flags 0x100 on isa0 sc0: VGA <9 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 BRIDGE 990810, have 4 interfaces -- index 1 type 6 phy 0 addrl 6 addr 00.e0.81.10.50.32 -- index 2 type 6 phy 0 addrl 6 addr 00.90.27.54.57.26 -- index 3 type 6 phy 0 addrl 6 addr 00.e0.29.6d.14.19 ad0: 14649MB [29765/16/63] at ata0-master tagged UDMA33 ad1: 35772MB [72680/16/63] at ata1-master tagged UDMA33 Waiting 5 seconds for SCSI devices to settle Mounting root from ufs:/dev/da0s1a da0 at ahc0 bus 0 target 1 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 4350MB (8910423 512 byte sectors: 255H 63S/T 554C) da1 at ahc0 bus 0 target 2 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing Enabled da1: 4350MB (8910423 512 byte sectors: 255H 63S/T 554C) da2 at ahc1 bus 0 target 1 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da2: 3067MB (6281856 512 byte sectors: 255H 63S/T 391C) cd0 at ahc1 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 16) cd0: Attempt to query device size failed: NOT READY, Medium not present SMP: AP CPU #1 Launched! >> now fxp0 promisc ON if_flags 0xffff8943 bdg_flags 0x5 >> now fxp1 promisc ON if_flags 0xffff8943 bdg_flags 0x5 >> now ed0 promisc ON if_flags 0xffff8943 bdg_flags 0x5 swi_net: unregistered isr number: 18. lock order reversal 1st vnode interlock last acquired @ ../../kern/vfs_vnops.c:644 2nd 0xc033ff80 mntvnode @ ../../ufs/ffs/ffs_vfsops.c:940 3rd 0xcd38e54c vnode interlock @ ../../ufs/ffs/ffs_vfsops.c:949 (pass2:ahc1:0:0:0): READ(10). CDB: 28 0 0 4 da 7e 0 0 a 0 (pass2:ahc1:0:0:0): ILLEGAL REQUEST asc:21,0 (pass2:ahc1:0:0:0): Logical block address out of range microuptime() went backwards (148891.989987 -> 148891.989956) netsmb_dev: loaded ../../kern/kern_synch.c:429: sleeping with "vnode interlock" locked from /usr/ports/net/smbfs/work/smbfs-1.3.5/kernel/modules/smbfs2/../../fs/smbfs/smbfs_vnops.c:280 lock order reversal 1st Giant last acquired @ /usr/ports/net/smbfs/work/smbfs-1.3.5/kernel/modules/smbfs2/../../netsmb/smb_iod.c:693 2nd 0xcd67492c vnode interlock @ /usr/ports/net/smbfs/work/smbfs-1.3.5/kernel/modules/smbfs2/../../fs/smbfs/smbfs_vnops.c:280 3rd 0xc0343fc0 Giant @ ../../kern/kern_synch.c:544 ../../kern/kern_synch.c:429: sleeping with "vnode interlock" locked from /usr/ports/net/smbfs/work/smbfs-1.3.5/kernel/modules/smbfs2/../../fs/smbfs/smbfs_vnops.c:280 ../../kern/kern_synch.c:429: sleeping with "vnode interlock" locked from /usr/ports/net/smbfs/work/smbfs-1.3.5/kernel/modules/smbfs2/../../fs/smbfs/smbfs_vnops.c:280 ../../kern/kern_synch.c:429: sleeping with "vnode interlock" locked from /usr/ports/net/smbfs/work/smbfs-1.3.5/kernel/modules/smbfs2/../../fs/smbfs/smbfs_vnops.c:280 ../../kern/kern_synch.c:429: sleeping with "vnode interlock" locked from /usr/ports/net/smbfs/work/smbfs-1.3.5/kernel/modules/smbfs2/../../fs/smbfs/smbfs_vnops.c:280 ../../kern/kern_synch.c:429: sleeping with "vnode interlock" locked from /usr/ports/net/smbfs/work/smbfs-1.3.5/kernel/modules/smbfs2/../../fs/smbfs/smbfs_vnops.c:280 ../../kern/kern_synch.c:429: sleeping with "vnode interlock" locked from /usr/ports/net/smbfs/work/smbfs-1.3.5/kernel/modules/smbfs2/../../fs/smbfs/smbfs_vnops.c:280 ../../kern/kern_synch.c:429: sleeping with "vnode interlock" locked from /usr/ports/net/smbfs/work/smbfs-1.3.5/kernel/modules/smbfs2/../../fs/smbfs/smbfs_vnops.c:280 ../../kern/kern_synch.c:429: sleeping with "vnode interlock" locked from /usr/ports/net/smbfs/work/smbfs-1.3.5/kernel/modules/smbfs2/../../fs/smbfs/smbfs_vnops.c:280 ../../kern/kern_synch.c:429: sleeping with "vnode interlock" locked from /usr/ports/net/smbfs/work/smbfs-1.3.5/kernel/modules/smbfs2/../../fs/smbfs/smbfs_vnops.c:280 -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 19 23:20:43 2001 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id E071937B401 for ; Mon, 19 Feb 2001 23:20:39 -0800 (PST) (envelope-from sheldonh@uunet.co.za) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 14V76A-0001Zi-00; Tue, 20 Feb 2001 09:20:34 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id JAA23101; Tue, 20 Feb 2001 09:20:34 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 22950; Tue Feb 20 09:20:13 2001 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.16 #1) id 14V75p-000PHR-00; Tue, 20 Feb 2001 09:20:13 +0200 To: "Leif Neland" Cc: freebsd-current@freebsd.org Subject: Re: Do we need a 3. level between stable and cuurent? In-reply-to: Your message of "Mon, 19 Feb 2001 17:54:53 +0100." <00d001c09a94$b280d9c0$0e00a8c0@neland.dk> Date: Tue, 20 Feb 2001 09:20:12 +0200 Message-ID: <97180.982653612@axl.fw.uunet.co.za> From: Sheldon Hearn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Feb 2001 17:54:53 +0100, "Leif Neland" wrote: > Do we need a level in between for people who just run current for the > fun of it and for testing. So after the hardcore has tested it in > -current, they commit it to all the monkeys trying to break it, and we > then try it on n^m' combinations of hardware/software. This is a great idea that nobody else has pushed very hard because of resource constraints. :-( Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 19 23:25:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id 88A3E37B4EC for ; Mon, 19 Feb 2001 23:25:26 -0800 (PST) (envelope-from vallo@myhakas.matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id 3EF302CE7B; Tue, 20 Feb 2001 09:25:21 +0200 (EET) Received: (from vallo@localhost) by myhakas.matti.ee (8.11.2/8.11.2) id f1K7PPV69200; Tue, 20 Feb 2001 09:25:25 +0200 (EET) (envelope-from vallo) Date: Tue, 20 Feb 2001 09:25:25 +0200 From: Vallo Kallaste To: Vallo Kallaste Cc: freebsd-current@FreeBSD.ORG Subject: Re: occasional filesystem corruption Message-ID: <20010220092525.A69126@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <20010220091956.A68889@myhakas.matti.ee> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.14i-ja0 In-Reply-To: <20010220091956.A68889@myhakas.matti.ee>; from vallo@matti.ee on Tue, Feb 20, 2001 at 09:19:56AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 20, 2001 at 09:19:56AM +0200, Vallo Kallaste wrote: > FreeBSD 5.0-CURRENT #0: Mon Feb 12 16:09:09 EET 2001 > vallo@myhakas.matti.ee:/usr/src/sys/compile/Myhakas.SMP [snip] Don't be fooled about kernel compile time, the system is built from sources of February 1'st, 11:00:00 GMT and stays so until -current mess will settle down. Sorry. -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 19 23:53:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-165-226-53.dsl.lsan03.pacbell.net [64.165.226.53]) by hub.freebsd.org (Postfix) with ESMTP id 25BD837B401 for ; Mon, 19 Feb 2001 23:53:53 -0800 (PST) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 4CB2266B09; Mon, 19 Feb 2001 23:53:49 -0800 (PST) Date: Mon, 19 Feb 2001 23:53:48 -0800 From: Kris Kennaway To: nnd@mail.nsk.ru Cc: current@FreeBSD.ORG Subject: Re: cvs commit: src/share/mk sys.mk Message-ID: <20010219235348.A77584@mollari.cthul.hu> References: <200102192333.f1JNXEd10589@freefall.freebsd.org> <200102200402.f1K42vr25483@wint.itfs.nsk.su> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="AhhlLboLdkugWU4S" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200102200402.f1K42vr25483@wint.itfs.nsk.su>; from nnd@mail.nsk.ru on Tue, Feb 20, 2001 at 10:02:57AM +0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --AhhlLboLdkugWU4S Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Feb 20, 2001 at 10:02:57AM +0600, nnd@mail.nsk.ru wrote: >=20 > Kris Kennaway wrote: > >=20 > > Modified files: > > share/mk sys.mk=20 > > Log: > > Remove bogus setting of MACHINE_CPU here. There is no need for it. >=20 > But there MUST be at least one setting for > MACHINE_CPU for 'make buildworld' to succeed before new 'make' > with this variable is in place. No, MACHINE_CPU is optional. If you don't have it set, you get the vanilla C code. So if you don't have it set at all, you'll get C code in OpenSSL as it's always been, then the next time you are using the updated make(1) and it will set it to i386, which will get you the i386 asm code. Or you can just set MACHINE_CPU immediately and it will build asm code on the first pass. Kris --AhhlLboLdkugWU4S Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6kiKMWry0BWjoQKURAuGnAJ9KK6Ww5c+EFO364oQvPyHXI8sDYQCg0aJR HgdPaE3l8l9A7a37wpsUBaU= =afWP -----END PGP SIGNATURE----- --AhhlLboLdkugWU4S-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 0: 6:55 2001 Delivered-To: freebsd-current@freebsd.org Received: from wint.itfs.nsk.su (wint.itfs.nsk.su [212.20.32.43]) by hub.freebsd.org (Postfix) with ESMTP id 4694737B401 for ; Tue, 20 Feb 2001 00:06:51 -0800 (PST) (envelope-from nnd@wint.itfs.nsk.su) Received: (from nnd@localhost) by wint.itfs.nsk.su (8.11.2/8.11.1) id f1K86m800310; Tue, 20 Feb 2001 14:06:48 +0600 (NOVT) (envelope-from nnd) Date: Tue, 20 Feb 2001 14:06:48 +0600 (NOVT) Message-Id: <200102200806.f1K86m800310@wint.itfs.nsk.su> From: nnd@mail.nsk.ru To: current@freebsd.org Subject: Re: cvs commit: src/share/mk sys.mk In-Reply-To: <20010219235348.A77584@mollari.cthul.hu> User-Agent: tin/1.5.8-20010204 ("Paradise Regained") (UNIX) (FreeBSD/5.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > > On Tue, Feb 20, 2001 at 10:02:57AM +0600, nnd@mail.nsk.ru wrote: >> >> Kris Kennaway wrote: >> > >> > Modified files: >> > share/mk sys.mk >> > Log: >> > Remove bogus setting of MACHINE_CPU here. There is no need for it. >> >> But there MUST be at least one setting for >> MACHINE_CPU for 'make buildworld' to succeed before new 'make' >> with this variable is in place. > > No, MACHINE_CPU is optional. If you don't have it set, you get the > vanilla C code. So if you don't have it set at all, you'll get C code > in OpenSSL as it's always been, then the next time you are using the > updated make(1) and it will set it to i386, which will get you the > i386 asm code. > > Or you can just set MACHINE_CPU immediately and it will build asm code > on the first pass. MACHINE_CPU variable MUST be DEFINED for current 'Makefile' in the 'usr/src/secure/libcrypto' be parsed by the 'make' without internall definition of that variable. (It stops at the first "${MACHINE_CPU:Mi686}" construct in the line 62). N.Dudorov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 0:15:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from white.imgsrc.co.jp (ns.imgsrc.co.jp [210.226.20.2]) by hub.freebsd.org (Postfix) with ESMTP id 01FB337B401 for ; Tue, 20 Feb 2001 00:15:08 -0800 (PST) (envelope-from kuriyama@imgsrc.co.jp) Received: from waterblue.imgsrc.co.jp (waterblue.imgsrc.co.jp [210.226.20.160]) by white.imgsrc.co.jp (8.11.2/8.11.0) with ESMTP id f1K8F1O04962; Tue, 20 Feb 2001 17:15:01 +0900 (JST) Date: Tue, 20 Feb 2001 17:14:57 +0900 Message-ID: <7mitm5n532.wl@waterblue.imgsrc.co.jp> From: Jun Kuriyama To: Kris Kennaway Cc: current@FreeBSD.ORG Subject: Re: cvs commit: src/share/mk sys.mk In-Reply-To: <20010219235348.A77584@mollari.cthul.hu> References: <200102192333.f1JNXEd10589@freefall.freebsd.org> <200102200402.f1K42vr25483@wint.itfs.nsk.su> <20010219235348.A77584@mollari.cthul.hu> User-Agent: Wanderlust/2.4.0 (Rio) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 14) (Cuyahoga Valley) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 20 Feb 2001 07:54:22 GMT, Kris Kennaway wrote: > No, MACHINE_CPU is optional. If you don't have it set, you get the > vanilla C code. So if you don't have it set at all, you'll get C code > in OpenSSL as it's always been, then the next time you are using the > updated make(1) and it will set it to i386, which will get you the > i386 asm code. > > Or you can just set MACHINE_CPU immediately and it will build asm code > on the first pass. I don't know this is local problem on my environment, but "make buildworld" with old make(1) failed if I did not set MACHINE_CPU in /etc/make.conf. So it seems invoked make(1) in src/secure/lib/libcrypto is old one... ===> secure/lib/libcrypto "/usr/src/secure/lib/libcrypto/Makefile", line 62: Malformed conditional (${MACHINE_CPU:Mi686}) "/usr/src/secure/lib/libcrypto/Makefile", line 62: Missing dependency operator "/usr/src/secure/lib/libcrypto/Makefile", line 67: if-less else "/usr/src/secure/lib/libcrypto/Makefile", line 67: Need an operator "/usr/src/secure/lib/libcrypto/Makefile", line 69: if-less endif "/usr/src/secure/lib/libcrypto/Makefile", line 69: Need an operator "/usr/src/secure/lib/libcrypto/Makefile", line 321: Malformed conditional (${MACHINE_CPU:Mi686} || ${MACHINE_CPU:Mi586}) "/usr/src/secure/lib/libcrypto/Makefile", line 321: Missing dependency operator "/usr/src/secure/lib/libcrypto/Makefile", line 323: Malformed conditional (${MACHINE_CPU:Mi386}) "/usr/src/secure/lib/libcrypto/Makefile", line 323: Missing dependency operator "/usr/src/secure/lib/libcrypto/Makefile", line 326: if-less endif "/usr/src/secure/lib/libcrypto/Makefile", line 326: Need an operator make: fatal errors encountered -- cannot continue -- Jun Kuriyama // IMG SRC, Inc. // FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 0:21:14 2001 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-165-226-53.dsl.lsan03.pacbell.net [64.165.226.53]) by hub.freebsd.org (Postfix) with ESMTP id C939037B491 for ; Tue, 20 Feb 2001 00:21:09 -0800 (PST) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 71C1A66B09; Tue, 20 Feb 2001 00:21:09 -0800 (PST) Date: Tue, 20 Feb 2001 00:21:09 -0800 From: Kris Kennaway To: Jun Kuriyama Cc: current@FreeBSD.ORG Subject: Re: cvs commit: src/share/mk sys.mk Message-ID: <20010220002109.A12114@mollari.cthul.hu> References: <200102192333.f1JNXEd10589@freefall.freebsd.org> <200102200402.f1K42vr25483@wint.itfs.nsk.su> <20010219235348.A77584@mollari.cthul.hu> <7mitm5n532.wl@waterblue.imgsrc.co.jp> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="mP3DRpeJDSE+ciuQ" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <7mitm5n532.wl@waterblue.imgsrc.co.jp>; from kuriyama@imgsrc.co.jp on Tue, Feb 20, 2001 at 05:14:57PM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --mP3DRpeJDSE+ciuQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Feb 20, 2001 at 05:14:57PM +0900, Jun Kuriyama wrote: > At 20 Feb 2001 07:54:22 GMT, > Kris Kennaway wrote: > > No, MACHINE_CPU is optional. If you don't have it set, you get the > > vanilla C code. So if you don't have it set at all, you'll get C code > > in OpenSSL as it's always been, then the next time you are using the > > updated make(1) and it will set it to i386, which will get you the > > i386 asm code. > >=20 > > Or you can just set MACHINE_CPU immediately and it will build asm code > > on the first pass. >=20 > I don't know this is local problem on my environment, but "make > buildworld" with old make(1) failed if I did not set MACHINE_CPU in > /etc/make.conf. So it seems invoked make(1) in > src/secure/lib/libcrypto is old one... Oh, hmm. It seems we do need the bootstrapping code in sys.mk after all. Kris --mP3DRpeJDSE+ciuQ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6kij0Wry0BWjoQKURAimEAJwN5OcpbgAEXcJDeD+JVa0emeeSeQCgqokN YAXdomTV7MUlmSqg8Ghe5z4= =PBCo -----END PGP SIGNATURE----- --mP3DRpeJDSE+ciuQ-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 0:32:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailhost01.reflexnet.net (mailhost01.reflexnet.net [64.6.192.82]) by hub.freebsd.org (Postfix) with ESMTP id 2C03337B491 for ; Tue, 20 Feb 2001 00:32:37 -0800 (PST) (envelope-from cjc@rfx-216-196-73-168.users.reflexcom.com) Received: from rfx-216-196-73-168.users.reflexcom.com ([216.196.73.168]) by mailhost01.reflexnet.net with Microsoft SMTPSVC(5.5.1877.197.19); Tue, 20 Feb 2001 00:30:21 -0800 Received: (from cjc@localhost) by rfx-216-196-73-168.users.reflexcom.com (8.11.1/8.11.1) id f1K8WA974361; Tue, 20 Feb 2001 00:32:10 -0800 (PST) (envelope-from cjc) Date: Tue, 20 Feb 2001 00:32:09 -0800 From: "Crist J. Clark" To: Alfred Perlstein Cc: Leif Neland , freebsd-current@FreeBSD.ORG Subject: Re: Do we need a 3. level between stable and cuurent? Message-ID: <20010220003209.V62368@rfx-216-196-73-168.users.reflex> Reply-To: cjclark@alum.mit.edu References: <20010216025147.A25002@dragon.nuxi.com> <20010216104409.A99749@enigma.whacky.net> <20010216025147.A25002@dragon.nuxi.com> <200102161703.f1GH37E29782@billy-club.village.org> <20010217101500.A10023@enigma.whacky.net> <00d001c09a94$b280d9c0$0e00a8c0@neland.dk> <20010219103017.M6641@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010219103017.M6641@fw.wintelcom.net>; from bright@wintelcom.net on Mon, Feb 19, 2001 at 10:30:17AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Feb 19, 2001 at 10:30:17AM -0800, Alfred Perlstein wrote: > * Leif Neland [010219 08:54] wrote: > > We all know: -current is bleeding edge, expect it to break at random. Don't run it if you don't know how to fix it. > > -stable is for production, it works all the time. > > > > Do we need a level in between for people who just run current for the fun of it and for testing. > > So after the hardcore has tested it in -current, they commit it to all the monkeys trying to break it, and we then try it on n^m' combinations of hardware/software. > > > > I might not be able to fix a problem, but I can report what happens, and if my -current breaks for a few days, it is no big deal. > > > > While -current is not for everybody, I believe people like me helps in quality testing before the stuff hits -stable. > > > > Perhaps not a level, just a separate file, which contained the date of the last known version without known major problems. (or "." if no known problems) > > This is a good idea, however it would take someone dedicated to > maintaining this as well as doing regression testing. Those > regression tests could easily be ported to -stable making for > happier -stable as well as -current users. > > Are you volunteering? :) IMHO, people who are not actively developing -CURRENT, those running it for fun or only occasionally hacking non-essential portions just need to realize that blindly tracking -CURRENT with a daily, weekly, or perhaps any regular make-world schedule is just not going to work. Find a reasonably stable version of -CURRENT and stick with it until you know that the current -CURRENT is also in decent shape. For example, I did a make world early in February and started getting kernel panics at boot. I tried to get some help and provide some data on freebsd-current to fix it, but I just did not have the time and tools. I ended up just CVSuping a back to a version I knew was in good shape and the box has been fine. I can use it for what I want, and I'm not upping it until I hear things have settled a bit... And I hope that's soon, I don't want it to diverge too much or else merging my changes in might get painful. What would help me and others like me is some way to actually figure out if the current -CURRENT is stable (I like that sentence). I am not saying it would be a substitute for freebsd-current and the commit list, but those can be very, very hard to follow. Rather than two versions of -CURRENT provide the data for people to fairly quickly determine if today's -CURRENT is solid enough for them. In some sense, each commit makes a new version, people need to decide up to what recent earth-shaking commit they can go to and be safe. Possibly some webpage summarizing what is broken, which essential pieces are in active development, etc. Obviously, this would take effort, but it may be worth it to those who want to track a stable -CURRENT. It is definately less work than maintaining two versions. How does it differ than reading the mailing lists? You don't need to dig through a dozen me-toos for each problem. Someone more knowledgeble on things can filter the claims that -CURRENT is broken from people who can't read UPDATING. And so on. And no, I am not volunteering. -- Crist J. Clark cjclark@alum.mit.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 0:49:27 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id B8C9C37B491 for ; Tue, 20 Feb 2001 00:49:21 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id TAA04642; Tue, 20 Feb 2001 19:49:03 +1100 Date: Tue, 20 Feb 2001 19:48:31 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Kris Kennaway Cc: Jun Kuriyama , current@FreeBSD.ORG Subject: Re: cvs commit: src/share/mk sys.mk In-Reply-To: <20010220002109.A12114@mollari.cthul.hu> 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 Tue, 20 Feb 2001, Kris Kennaway wrote: > On Tue, Feb 20, 2001 at 05:14:57PM +0900, Jun Kuriyama wrote: > > I don't know this is local problem on my environment, but "make > > buildworld" with old make(1) failed if I did not set MACHINE_CPU in > > /etc/make.conf. So it seems invoked make(1) in > > src/secure/lib/libcrypto is old one... > > Oh, hmm. It seems we do need the bootstrapping code in sys.mk after > all. No. We must fix whatever cause the wrong (old) version of make to be used. I think it is just that make doesn't actually get bootstrapped unless the old make is _very_ old (older than the one in 2.2.0). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 0:56: 7 2001 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-165-226-53.dsl.lsan03.pacbell.net [64.165.226.53]) by hub.freebsd.org (Postfix) with ESMTP id A2F1B37B491 for ; Tue, 20 Feb 2001 00:56:04 -0800 (PST) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 5702266D40; Tue, 20 Feb 2001 00:56:04 -0800 (PST) Date: Tue, 20 Feb 2001 00:56:04 -0800 From: Kris Kennaway To: Bruce Evans Cc: Jun Kuriyama , current@FreeBSD.ORG Subject: Re: cvs commit: src/share/mk sys.mk Message-ID: <20010220005604.B21695@mollari.cthul.hu> References: <20010220002109.A12114@mollari.cthul.hu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="dTy3Mrz/UPE2dbVg" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from bde@zeta.org.au on Tue, Feb 20, 2001 at 07:48:31PM +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --dTy3Mrz/UPE2dbVg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Feb 20, 2001 at 07:48:31PM +1100, Bruce Evans wrote: > On Tue, 20 Feb 2001, Kris Kennaway wrote: >=20 > > On Tue, Feb 20, 2001 at 05:14:57PM +0900, Jun Kuriyama wrote: > > > I don't know this is local problem on my environment, but "make > > > buildworld" with old make(1) failed if I did not set MACHINE_CPU in > > > /etc/make.conf. So it seems invoked make(1) in > > > src/secure/lib/libcrypto is old one... > >=20 > > Oh, hmm. It seems we do need the bootstrapping code in sys.mk after > > all. >=20 > No. We must fix whatever cause the wrong (old) version of make to be > used. I think it is just that make doesn't actually get bootstrapped > unless the old make is _very_ old (older than the one in 2.2.0). That would be better -- I checked and we don't appear to rebuild make at all as part of the bootstrap process in make world. We can remove the sys.mk hacks once that works. Kris --dTy3Mrz/UPE2dbVg Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6kjEjWry0BWjoQKURAn6sAKCi7Q+ueSlGabZ0Qgbc/VNgyvo9ZwCgxqWU CdKQWikRZ14Gy3eMRsaJUa4= =B22W -----END PGP SIGNATURE----- --dTy3Mrz/UPE2dbVg-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 1:20: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from tower.ti.com (tower.ti.com [192.94.94.5]) by hub.freebsd.org (Postfix) with ESMTP id D2BC837B401 for ; Tue, 20 Feb 2001 01:19:59 -0800 (PST) (envelope-from ntakpe@ishtar.ffab.tide.ti.com) Received: from dlep7.itg.ti.com ([157.170.134.103]) by tower.ti.com (8.11.1/8.11.1) with ESMTP id f1K9Jwr15472 for ; Tue, 20 Feb 2001 03:19:58 -0600 (CST) Received: from dlep7.itg.ti.com (localhost [127.0.0.1]) by dlep7.itg.ti.com (8.9.3/8.9.3) with ESMTP id DAA16701 for ; Tue, 20 Feb 2001 03:19:58 -0600 (CST) Received: from keithley.ffab.tide.ti.com (keithley.ffab.tide.ti.com [137.167.200.45]) by dlep7.itg.ti.com (8.9.3/8.9.3) with ESMTP id DAA16651 for ; Tue, 20 Feb 2001 03:19:51 -0600 (CST) Received: from ishtar.ffab.tide.ti.com (ishtar.ffab.tide.ti.com [137.167.222.71]) by keithley.ffab.tide.ti.com (8.9.3+Sun/8.9.3) with ESMTP id KAA29424 for ; Tue, 20 Feb 2001 10:19:49 +0100 (MET) Received: (from ntakpe@localhost) by ishtar.ffab.tide.ti.com (8.11.0/8.11.0) id f1K9Jnt07946 for freebsd-current@FreeBSD.ORG; Tue, 20 Feb 2001 10:19:49 +0100 From: Jean Louis Ntakpe Message-Id: <200102200919.f1K9Jnt07946@ishtar.ffab.tide.ti.com> Subject: make buildkernel failed To: freebsd-current@FreeBSD.ORG Date: Tue, 20 Feb 2001 10:19:49 +0100 (CET) X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I could make buildworld and installworld sucessfully but "make buildkernel" fails. (kernel is built but no modules could be compiled). CVSUP a few minutes ago. ===> 3dfx make: don't know how to make machine/lock.h. Stop *** Error code 2 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /usr/obj/usr/src/sys/SMP. *** Error code 1 Stop in /usr/src. *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 1:43:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from updraft.jp.freebsd.org (updraft.jp.FreeBSD.ORG [210.157.158.42]) by hub.freebsd.org (Postfix) with ESMTP id B77D637B491 for ; Tue, 20 Feb 2001 01:43:47 -0800 (PST) (envelope-from matusita@jp.FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by updraft.jp.freebsd.org (8.11.2+3.4W/8.11.1) with ESMTP/inet id f1K9hhW24398 for ; Tue, 20 Feb 2001 18:43:44 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) In-Reply-To: <20010217190142A.matusita@jp.FreeBSD.org> References: <20010217190142A.matusita@jp.FreeBSD.org> X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V X-User-Agent: Mew/1.94.2 XEmacs/21.2 (Poseidon) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 19 From: Makoto MATSUSHITA To: current@FreeBSD.org Subject: Building procedure of krb5 is broken Date: Tue, 20 Feb 2001 18:43:24 +0900 Message-Id: <20010220184324P.matusita@jp.FreeBSD.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry if you have seen before. I've found that current 5-current is broken, since krb5 cannot compile. Here is a typical compiler message: In file included from /usr/src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/krb5/krb5_locl.h:142, from /usr/src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi/gssapi_locl.h:39, from /usr/src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi/8003.c:34: /usr/src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/krb5/krb5.h:43:krb5_err.h: No such file or directory It seems that add 'CFLAGS+=-I${KRB5OBJDIR}' to src/kerberos5/lib/libgssapi/Makefile is required to fix this, since krb5_err.h is not in ${KRB5DIR}/lib/krb5. Any Kerberos5 gurus, would you please check this out? -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 1:55: 2 2001 Delivered-To: freebsd-current@freebsd.org Received: from mobile.wemm.org (dhcp246.osd.bsdi.com [204.216.28.246]) by hub.freebsd.org (Postfix) with ESMTP id 4AD3337B702 for ; Tue, 20 Feb 2001 01:54:52 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f1K9spo30061; Tue, 20 Feb 2001 01:54:51 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200102200954.f1K9spo30061@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Jean Louis Ntakpe Cc: freebsd-current@FreeBSD.ORG Subject: Re: make buildkernel failed In-Reply-To: <200102200919.f1K9Jnt07946@ishtar.ffab.tide.ti.com> Date: Tue, 20 Feb 2001 01:54:51 -0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Give it about an hour and re-cvsup. Once you have rev 1.94 of src/sys/conf/kmod.mk, you should be set. Or you can grab the delta by cvsweb if you are in a hurry. Jean Louis Ntakpe wrote: > Hi, > > I could make buildworld and installworld sucessfully > but "make buildkernel" fails. (kernel is built but > no modules could be compiled). CVSUP a few minutes ago. > > ===> 3dfx > make: don't know how to make machine/lock.h. Stop > *** Error code 2 > > Stop in /usr/src/sys/modules. > *** Error code 1 > > Stop in /usr/obj/usr/src/sys/SMP. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 5:43: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id CF85737B491 for ; Tue, 20 Feb 2001 05:43:02 -0800 (PST) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id OAA34272; Tue, 20 Feb 2001 14:42:50 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: mjacob@feral.com Cc: Kris Kennaway , The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: proper kernel config procedure ... References: From: Dag-Erling Smorgrav Date: 20 Feb 2001 14:42:49 +0100 In-Reply-To: Matthew Jacob's message of "Mon, 19 Feb 2001 16:06:23 -0800 (PST)" Message-ID: Lines: 10 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Jacob writes: > This doesn't work 100%. In particular if you have a sys that's not part of > /usr/src/sys it doesn't always work. Yes, it does, if your sys tree is complete. There used to be a problem building modules, but it was fixed a month or two ago. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 5:52:59 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by hub.freebsd.org (Postfix) with ESMTP id E175737B503; Tue, 20 Feb 2001 05:52:52 -0800 (PST) (envelope-from mb@imp.ch) Received: from levais.imp.ch (levais.imp.ch [157.161.4.66]) by mail.imp.ch (8.11.1/8.11.1) with ESMTP id f1KDqk065329; Tue, 20 Feb 2001 14:52:46 +0100 (CET) (envelope-from Martin.Blapp@imp.ch) Date: Tue, 20 Feb 2001 14:52:46 +0100 (CET) From: Martin Blapp To: alfred@freebsd.org, kuriyama@imgsrc.co.jp, snap-users@kame.net, Francois.Tigeot@nic.fr, ru@freebsd.org, eischen@vigrid.com, Francis.Dupont@enst-bretagne.fr, feico@pasta.cs.uit.no, dillon@earth.backplane.com Cc: asmodai@freebsd.org, freebsd@dohd.org, freebsd-current@freebsd.org Subject: TI-RPC and NFS6 status (100% done) In-Reply-To: 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 Hi, I have finished now my work here with TI-RPC, and I'm only doing bug-fixing now before this gets comitted. I'd like that many people test these changes and send me bugreports back. This is a port from NetBSD, and as in NetBSD, it uses Unix Domain Sockets instead of TLI/XLI stuff. I'v taken the credential checking stuff from our previous RPC implementation, thanks to Bill Paul for the work he has done there. There are still some little things to do in future: - Fix manpages - Fix 'bind to ip' for nfsd which is broken at the moment - Upgrade locking stuff in rpc.library to latest version (ti-rpc2.3) Here are the patches: http://home.teleport.ch/freebsd/rpc.diff_02202001.tgz http://home.teleport.ch/freebsd/before-patch.sh To patch the CURRENT source-tree and to install these changes, do the following steps: 1. cd /usr/src 2. run ./before-patch.sh 3. patch -I -E -p < rpc.diff_02202001 4. make world 5. Run mergemaster With these patches applied, all rpc dependent programms in FreeBSD still work and compile, nfsd(8) and mountd(8) and the mount utilities (mount_nfs, umount, prc.umntall) have been patched to support IPv6, and I'm using here NFS over UDP6 on localhost sucessfully. This is an output of rpcinfo(8), which also has been updated: # rpcinfo program version netid address service owner 100000 4 tcp 0.0.0.0.0.111 rpcbind superuser 100000 3 tcp 0.0.0.0.0.111 rpcbind superuser 100000 2 tcp 0.0.0.0.0.111 rpcbind superuser 100000 4 udp 0.0.0.0.0.111 rpcbind superuser 100000 3 udp 0.0.0.0.0.111 rpcbind superuser 100000 2 udp 0.0.0.0.0.111 rpcbind superuser 100000 4 tcp6 ::.0.111 rpcbind superuser 100000 3 tcp6 ::.0.111 rpcbind superuser 100000 4 udp6 ::.0.111 rpcbind superuser 100000 3 udp6 ::.0.111 rpcbind superuser 100000 4 unix /var/run/rpcbind.sock rpcbind superuser 100000 3 unix /var/run/rpcbind.sock rpcbind superuser 100000 2 unix /var/run/rpcbind.sock rpcbind superuser 100005 1 udp 0.0.0.0.3.252 mountd superuser 100005 3 udp 0.0.0.0.3.252 mountd superuser 100005 1 tcp 0.0.0.0.3.254 mountd superuser 100005 3 tcp 0.0.0.0.3.254 mountd superuser 100005 1 udp6 ::.3.251 mountd superuser 100005 3 udp6 ::.3.251 mountd superuser 100005 1 tcp6 ::.3.253 mountd superuser 100005 3 tcp6 ::.3.253 mountd superuser 100003 2 udp 0.0.0.0.8.1 nfs superuser 100003 3 udp 0.0.0.0.8.1 nfs superuser 100003 2 udp6 ::.8.1 nfs superuser 100003 3 udp6 ::.8.1 nfs superuser And I can do: # mount -v ::1:/usr/ports/ /mnt ::1:/usr/ports on /mnt (nfs) # ls -l /mnt total 1353 -rw-r--r-- 1 root wheel 19 Jul 14 1997 .cvsignore drwxr-xr-x 2 root wheel 512 Dec 25 1999 CVS [...] # umount -v ::1:/usr/ports/ ::1:/usr/ports: unmount from /mnt Now to the other changes which are included in this patch: - Portmapper(8) has been replaced by the son of portmap, rpcbind. - There is also a fix included for ypbind, to not to sent 10000ends of requests out, if the yp-server is away for a little time. - Umount(8) is also fixed to unmount pathnames longer than 80 chars, which are currently truncated by the Kernel statfs structure. - In rc.network, all rpc dependent programms and servers are only started if ${portmap_enable} is set to "YES". In defaults/rc.conf there are some comments about this. This should prevent some hangs for rpc dependent programms (rpc.umntall, nfsd, ypbind etc.) - Because I was to lazy to fix our rpc.lockd(8), I've included the working NetBSD rpc.lockd(8) implementation, wich uses TI-RPC and works fine for server side locking, client side locking is not implemented yet. Im doing some patch splits now, so all necessary parts will hopefully be commited by Alfred Perlstein in the next few days. Martin Martin Blapp, mb@imp.ch ------------------------------------------------ Improware AG, UNIX solution and service provider Zurlindenstrasse 29, 4133 Pratteln, Switzerland Phone: +41 79 370 26 05, Fax: +41 61 826 93 01 ------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 7:29:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from mout0.freenet.de (mout0.freenet.de [194.97.50.131]) by hub.freebsd.org (Postfix) with ESMTP id D68BF37B4EC for ; Tue, 20 Feb 2001 07:29:40 -0800 (PST) (envelope-from netchild@leidinger.net) Received: from [194.97.50.138] (helo=mx0.freenet.de) by mout0.freenet.de with esmtp (Exim 3.22 #1) id 14VEjS-0006YU-00 for current@freebsd.org; Tue, 20 Feb 2001 16:29:38 +0100 Received: from a2f2a.pppool.de ([213.6.47.42] helo=Magelan.Leidinger.net) by mx0.freenet.de with esmtp (Exim 3.22 #1) id 14VEjR-0006Bl-00 for current@FreeBSD.ORG; Tue, 20 Feb 2001 16:29:37 +0100 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.11.2/8.11.2) with ESMTP id f1KCNgW03357; Tue, 20 Feb 2001 13:23:43 +0100 (CET) (envelope-from netchild@Leidinger.net) Message-Id: <200102201223.f1KCNgW03357@Magelan.Leidinger.net> Date: Tue, 20 Feb 2001 13:23:41 +0100 (CET) From: Alexander Leidinger Subject: Re: name resolution problems To: morganw@chemikals.org Cc: current@FreeBSD.ORG In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19 Feb, Wesley Morgan wrote: > Since the big shake-up with -current, I find that mozilla and galeon can > no longer function (both up to date), but lynx has no problems. Mozilla [...] > Is anyone else seeing this? Yes (galeon-0.9b3 + mozilla-0.7). Netscape 4.76 works. Bye, Alexander. -- ...and that is how we know the Earth to be banana-shaped. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 8:26:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by hub.freebsd.org (Postfix) with ESMTP id E714837B491 for ; Tue, 20 Feb 2001 08:26:50 -0800 (PST) (envelope-from mi@aldan.algebra.com) Received: (from root@localhost) by aldan.algebra.com (8.11.2/8.11.2) id f1KGRLa20988 for current@freebsd.org; Tue, 20 Feb 2001 11:27:21 -0500 (EST) (envelope-from mi) From: Mikhail Teterin Message-Id: <200102201627.f1KGRLa20988@aldan.algebra.com> Subject: as segfaulting during world-build To: current@freebsd.org Date: Tue, 20 Feb 2001 11:27:17 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL88 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG No, I don't think it is hardware. It died on the same spot for the third time in a row: tail -15 /var/tmp/w.log* ==> /var/tmp/w.log <== cd /opt/src/lib/csu/i386-elf; make _EXTRADEPEND cc -O -pipe -march=i686 -elf -Wall -fkeep-inline-functions -I/opt/src/lib/csu/i386-elf/../common -I/usr/obj/opt/src/i386/usr/include -c /opt/src/lib/csu/i386-elf/crt1.c -o crt1.o cc -I/opt/src/lib/csu/i386-elf/../common -I/usr/obj/opt/src/i386/usr/include -c /opt/src/lib/csu/i386-elf/crti.S -o crti.o cc -I/opt/src/lib/csu/i386-elf/../common -I/usr/obj/opt/src/i386/usr/include -c /opt/src/lib/csu/i386-elf/crtn.S -o crtn.o cc: Internal compiler error: program as got fatal signal 11 *** Error code 1 cc: Internal compiler error: program as got fatal signal 11 *** Error code 1 2 errors *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error ==> /var/tmp/w.log.11 <== cd /opt/src/lib/csu/i386-elf; make _EXTRADEPEND cc -O -pipe -march=i686 -elf -Wall -fkeep-inline-functions -I/opt/src/lib/csu/i386-elf/../common -I/usr/obj/opt/src/i386/usr/include -c /opt/src/lib/csu/i386-elf/crt1.c -o crt1.o cc -I/opt/src/lib/csu/i386-elf/../common -I/usr/obj/opt/src/i386/usr/include -c /opt/src/lib/csu/i386-elf/crti.S -o crti.o cc -I/opt/src/lib/csu/i386-elf/../common -I/usr/obj/opt/src/i386/usr/include -c /opt/src/lib/csu/i386-elf/crtn.S -o crtn.o cc: Internal compiler error: program as got fatal signal 11 cc: Internal compiler error: program as got fatal signal 11 *** Error code 1 *** Error code 1 2 errors *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error ==> /var/tmp/w.log.11-2 <== cd /opt/src/lib/csu/i386-elf; make _EXTRADEPEND cc -O -pipe -march=i686 -elf -Wall -fkeep-inline-functions -I/opt/src/lib/csu/i386-elf/../common -I/usr/obj/opt/src/i386/usr/include -c /opt/src/lib/csu/i386-elf/crt1.c -o crt1.o cc -I/opt/src/lib/csu/i386-elf/../common -I/usr/obj/opt/src/i386/usr/include -c /opt/src/lib/csu/i386-elf/crti.S -o crti.o cc -I/opt/src/lib/csu/i386-elf/../common -I/usr/obj/opt/src/i386/usr/include -c /opt/src/lib/csu/i386-elf/crtn.S -o crtn.o cc: Internal compiler error: program as got fatal signal 11 cc: Internal compiler error: program as got fatal signal 11 *** Error code 1 *** Error code 1 2 errors *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error This is my regular home machine, it usually runs SETI@Home, when I'm not here and is a NON-overclocked dual Pentium-II 300MHz. It has 320Mb of RAM and 390Mb of swap: Device 1K-blocks Used Avail Capacity Type /dev/rda0b 393088 36 393052 0% Interleaved I tried building the elf/as manually, and it chokes on this file just the same. Here are my attempts to issue the same commands make and cc issue: # /usr/libexec/cpp0 -lang-asm -v -I/opt/src/lib/csu/i386-elf/../common -I/usr/obj/opt/src/i386/usr/include -$ -Di386 -Dunix -D__FreeBSD__=5 -D__FreeBSD_cc_version=500002 -D__i386__ -D__unix__ -D__FreeBSD__=5 -D__FreeBSD_cc_version=500002 -D__i386 -D__unix '-Acpu(i386)' '-Amachine(i386)' '-Asystem(unix)' '-Asystem(FreeBSD)' -D__ASSEMBLER__ '-Acpu(i386)' '-Amachine(i386)' -Di386 -D__i386 -D__i386__ -D__ELF__ /opt/src/lib/csu/i386-elf/crtn.S crtn.s # wc -l crtn.s 33 crtn.s # /usr/libexec/elf/as -v -o crtn.o crtn.s GNU assembler version 2.10.1 (i386-unknown-freebsdelf5.0) using BFD version 2.10.1 Segmentation fault - core dumped The crtn.s is rather simple: ---------------------- # 1 "/opt/src/lib/csu/i386-elf/crtn.S" [.... empty lines ....] .section .init,"ax",@progbits ret .section .fini,"ax",@progbits ret ---------------------- Yours, -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 8:49:20 2001 Delivered-To: freebsd-current@freebsd.org Received: from sol.cc.u-szeged.hu (sol.cc.u-szeged.hu [160.114.8.24]) by hub.freebsd.org (Postfix) with ESMTP id 5032537B401 for ; Tue, 20 Feb 2001 08:49:14 -0800 (PST) (envelope-from sziszi@petra.hos.u-szeged.hu) Received: from petra.hos.u-szeged.hu by sol.cc.u-szeged.hu (8.9.3+Sun/SMI-SVR4) id RAA18455; Tue, 20 Feb 2001 17:49:10 +0100 (MET) Received: from sziszi by petra.hos.u-szeged.hu with local (Exim 3.12 #1 (Debian)) id 14VFyP-0008Gx-00 for ; Tue, 20 Feb 2001 17:49:09 +0100 Date: Tue, 20 Feb 2001 17:49:09 +0100 From: Szilveszter Adam To: current@freebsd.org Subject: Re: as segfaulting during world-build Message-ID: <20010220174909.F22771@petra.hos.u-szeged.hu> Mail-Followup-To: Szilveszter Adam , current@freebsd.org References: <200102201627.f1KGRLa20988@aldan.algebra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200102201627.f1KGRLa20988@aldan.algebra.com>; from mi@aldan.algebra.com on Tue, Feb 20, 2001 at 11:27:17AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 20, 2001 at 11:27:17AM -0500, Mikhail Teterin wrote: > No, I don't think it is hardware. It died on the same spot for the > third time in a row: <...> What date is the -CURRENT you are attempting the build on from? There were problems with as failing for a while not long ago. Check your version of src/lib/libc/stdio/findfp.c (the installed one...) to see if it is revision 1.15 or later. If not, you will have to get a working as (and as reported by Martin Blapp, the other binutiles in /usr/bin/ and /usr/libexec/elf too) from somwhere like an ftp snapshot... if this is not the problem, I dunno, I did not have any such problems even though I have just finished a buildworld... -- Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 9:12:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 6E15F37B4EC for ; Tue, 20 Feb 2001 09:12:50 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id JAA10939; Tue, 20 Feb 2001 09:12:41 -0800 Date: Tue, 20 Feb 2001 09:12:41 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Dag-Erling Smorgrav Cc: Kris Kennaway , The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: proper kernel config procedure ... In-Reply-To: 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 20 Feb 2001, Dag-Erling Smorgrav wrote: > Matthew Jacob writes: > > This doesn't work 100%. In particular if you have a sys that's not part of > > /usr/src/sys it doesn't always work. > > Yes, it does, if your sys tree is complete. There used to be a problem > building modules, but it was fixed a month or two ago. No, make clean doesn't work 100% always. I don't remember the details, but indeed it still was a problem. I sent mail to David && Peter after this happened (because they both had last been involved) and never heard back. Oh, wait- Peter muttered something about module To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 10:17:59 2001 Delivered-To: freebsd-current@freebsd.org Received: from blizzard.sabbo.net (smtp.sabbo.net [193.193.218.18]) by hub.freebsd.org (Postfix) with ESMTP id 843AC37B491; Tue, 20 Feb 2001 10:16:56 -0800 (PST) (envelope-from sobomax@FreeBSD.org) Received: from vic.sabbo.net (root@vic.sabbo.net [193.193.218.112]) by blizzard.sabbo.net (8.10.1/8.10.1) with ESMTP id f1KICMD07362; Tue, 20 Feb 2001 20:13:22 +0200 Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vic.sabbo.net (8.11.2/8.11.2) with ESMTP id f1KICVm84900; Tue, 20 Feb 2001 20:12:31 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Message-ID: <3A92B380.5625879B@FreeBSD.org> Date: Tue, 20 Feb 2001 20:12:16 +0200 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Soren Schmidt , current@FreeBSD.org, sos@FreeBSD.org, jhb@FreeBSD.org, "Alexander N. Kabaev" Subject: Re: Kernel panic in irq14: ata0 References: <200102121550.QAA99855@freebsd.dk> <3A8809E5.117E884D@FreeBSD.org> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maxim Sobolev wrote: > Soren Schmidt wrote: > > > It seems Maxim Sobolev wrote: > > [Charset koi8-r unsupported, filtering to ASCII...] > > > Hi, > > > > > > I'm not sure whether it's related to ata driver, but starting from several days > > > ago (my previous kernel was from 30 January) my kernel panices on every more or > > > less active ad0 usage (for example, dd if=/dev/ad0 of=/dev/null kills it > > > perfectly). The system in question is Toshiba Satellite Pro 445CDX with > > > isa-based ATA controller. Following is relevant dmesg, kernel config and > > > backtrace of crash dump. > > > > Try to go back to -current from about feb. 8 or there abouts... > > Reverting sys/i386/isa/ithread.c to r1.13 did the trick (credit goes to Alexander N. > Kabaev). Just to let you know that the problem in question is still here (r1.17 of ithread.c). -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 10:21:18 2001 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id E45EC37B503; Tue, 20 Feb 2001 10:21:14 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id TAA76890; Tue, 20 Feb 2001 19:21:13 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200102201821.TAA76890@freebsd.dk> Subject: Re: Kernel panic in irq14: ata0 In-Reply-To: <3A92B380.5625879B@FreeBSD.org> from Maxim Sobolev at "Feb 20, 2001 08:12:16 pm" To: sobomax@FreeBSD.org (Maxim Sobolev) Date: Tue, 20 Feb 2001 19:21:13 +0100 (CET) Cc: current@FreeBSD.org, sos@FreeBSD.org, jhb@FreeBSD.org, ak03@gte.com (Alexander N. Kabaev) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Maxim Sobolev wrote: > > Soren Schmidt wrote: > > > It seems Maxim Sobolev wrote: > > > [Charset koi8-r unsupported, filtering to ASCII...] > > > > Hi, > > > > > > > > I'm not sure whether it's related to ata driver, but starting from several days > > > > ago (my previous kernel was from 30 January) my kernel panices on every more or > > > > less active ad0 usage (for example, dd if=/dev/ad0 of=/dev/null kills it > > > > perfectly). The system in question is Toshiba Satellite Pro 445CDX with > > > > isa-based ATA controller. Following is relevant dmesg, kernel config and > > > > backtrace of crash dump. > > > > > > Try to go back to -current from about feb. 8 or there abouts... > > > > Reverting sys/i386/isa/ithread.c to r1.13 did the trick (credit goes to Alexander N. > > Kabaev). > > Just to let you know that the problem in question is still here (r1.17 of ithread.c). Well, I cant reproduce this problem and I havn't heard from others with this problem.... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 10:24:19 2001 Delivered-To: freebsd-current@freebsd.org Received: from blizzard.sabbo.net (ns.sabbo.net [193.193.218.18]) by hub.freebsd.org (Postfix) with ESMTP id 07C0637B4EC; Tue, 20 Feb 2001 10:24:12 -0800 (PST) (envelope-from sobomax@FreeBSD.org) Received: from vic.sabbo.net (root@vic.sabbo.net [193.193.218.112]) by blizzard.sabbo.net (8.10.1/8.10.1) with ESMTP id f1KIO2D07541; Tue, 20 Feb 2001 20:24:02 +0200 Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vic.sabbo.net (8.11.2/8.11.2) with ESMTP id f1KIO9m84966; Tue, 20 Feb 2001 20:24:09 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Message-ID: <3A92B63B.B308C616@FreeBSD.org> Date: Tue, 20 Feb 2001 20:23:55 +0200 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Soren Schmidt Cc: current@FreeBSD.org, sos@FreeBSD.org, jhb@FreeBSD.org, "Alexander N. Kabaev" Subject: Re: Kernel panic in irq14: ata0 References: <200102201821.TAA76890@freebsd.dk> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt wrote: > It seems Maxim Sobolev wrote: > > > Soren Schmidt wrote: > > > > It seems Maxim Sobolev wrote: > > > > [Charset koi8-r unsupported, filtering to ASCII...] > > > > > Hi, > > > > > > > > > > I'm not sure whether it's related to ata driver, but starting from several days > > > > > ago (my previous kernel was from 30 January) my kernel panices on every more or > > > > > less active ad0 usage (for example, dd if=/dev/ad0 of=/dev/null kills it > > > > > perfectly). The system in question is Toshiba Satellite Pro 445CDX with > > > > > isa-based ATA controller. Following is relevant dmesg, kernel config and > > > > > backtrace of crash dump. > > > > > > > > Try to go back to -current from about feb. 8 or there abouts... > > > > > > Reverting sys/i386/isa/ithread.c to r1.13 did the trick (credit goes to Alexander N. > > > Kabaev). > > > > Just to let you know that the problem in question is still here (r1.17 of ithread.c). > > Well, I cant reproduce this problem and I havn't heard from others with > this problem.... It's not an ata specific problem, but rather a problem of all ISA devices (I have an ISA based ata controller). -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 10:25:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id D306A37B401; Tue, 20 Feb 2001 10:25:16 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id TAA77867; Tue, 20 Feb 2001 19:25:16 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200102201825.TAA77867@freebsd.dk> Subject: Re: Kernel panic in irq14: ata0 In-Reply-To: <3A92B63B.B308C616@FreeBSD.org> from Maxim Sobolev at "Feb 20, 2001 08:23:55 pm" To: sobomax@FreeBSD.org (Maxim Sobolev) Date: Tue, 20 Feb 2001 19:25:15 +0100 (CET) Cc: current@FreeBSD.org, sos@FreeBSD.org, jhb@FreeBSD.org, ak03@gte.com (Alexander N. Kabaev) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Maxim Sobolev wrote: > > > > Well, I cant reproduce this problem and I havn't heard from others with > > this problem.... > > It's not an ata specific problem, but rather a problem of all ISA devices (I have an ISA > based ata controller). Well, seems -current is broken in yet another way.... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 10:53: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id DCC0E37B401; Tue, 20 Feb 2001 10:52:58 -0800 (PST) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id TAA35414; Tue, 20 Feb 2001 19:52:58 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Maxim Sobolev Cc: Soren Schmidt , current@FreeBSD.ORG, sos@FreeBSD.ORG, jhb@FreeBSD.ORG, "Alexander N. Kabaev" Subject: Re: Kernel panic in irq14: ata0 References: <200102201821.TAA76890@freebsd.dk> <3A92B63B.B308C616@FreeBSD.org> From: Dag-Erling Smorgrav Date: 20 Feb 2001 19:52:57 +0100 In-Reply-To: Maxim Sobolev's message of "Tue, 20 Feb 2001 20:23:55 +0200" Message-ID: Lines: 17 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maxim Sobolev writes: > It's not an ata specific problem, but rather a problem of all ISA > devices (I have an ISA based ata controller). I don't think it has anything to do with ISA. I've had similar problems on a PCI-only system (actually, PCI+EISA motherboard with no EISA cards) with no ATA devices (disks, CD-ROM and streamer are all SCSI). Considering that backing out rev 1.14 of ithread.c eliminates the panics, and that that revision is supposed to enable interrupt thread preemption, and that the crashed kernels show signs of stack smashing, I'd say the cause is probably a bug in the preemption code. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 11: 0:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 3C77637B401; Tue, 20 Feb 2001 11:00:28 -0800 (PST) (envelope-from mb@imp.ch) Received: from levais.imp.ch (levais.imp.ch [157.161.4.66]) by mail.imp.ch (8.11.1/8.11.1) with ESMTP id f1KJ0R087698; Tue, 20 Feb 2001 20:00:27 +0100 (CET) (envelope-from Martin.Blapp@imp.ch) Date: Tue, 20 Feb 2001 20:00:26 +0100 (CET) From: Martin Blapp To: asmodai@freebsd.org, freebsd@dohd.org, freebsd-current@freebsd.org Subject: Re: TI-RPC and NFS6 status (100% done) 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 Hi, I've found some inconsistency in my CVS tree, and sbin/mountd/mountd.c was not the version it should have been. That's fixed now and world just finished on my box sucessfully. Thanks to Ruslan (new man-pages are included in second patch today). Location is still the same, I've just updated the patch to include the changes. http://home.teleport.ch/freebsd/rpc.diff_02202001-1.tgz Thanks to everybody who sent me email about bugs or just comments. Martin Blapp, mb@imp.ch ------------------------------------------------ Improware AG, UNIX solution and service provider Zurlindenstrasse 29, 4133 Pratteln, Switzerland Phone: +41 79 370 26 05, Fax: +41 61 826 93 01 ------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 11:18:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.rdc1.kt.home.ne.jp (ha2.rdc1.kt.home.ne.jp [203.165.9.243]) by hub.freebsd.org (Postfix) with ESMTP id 0EED437B4EC for ; Tue, 20 Feb 2001 11:18:17 -0800 (PST) (envelope-from knu@iDaemons.org) Received: from daemon.local.idaemons.org ([203.165.161.10]) by mail.rdc1.kt.home.ne.jp (InterMail vM.4.01.02.00 201-229-116) with ESMTP id <20010220191815.FNIV19464.mail.rdc1.kt.home.ne.jp@daemon.local.idaemons.org> for ; Tue, 20 Feb 2001 11:18:15 -0800 Received: by daemon.local.idaemons.org (8.11.1/3.7W) id f1KJIFv37887; Wed, 21 Feb 2001 04:18:15 +0900 (JST) Date: Wed, 21 Feb 2001 04:18:15 +0900 Message-ID: <8666i588p4.wl@archon.local.idaemons.org> From: "Akinori MUSHA" To: current@FreeBSD.org Subject: find(1) -regex/-iregex User-Agent: Wanderlust/2.5.4 (Smooth) SEMI/1.14.2 (=?ISO-8859-1?Q?Daish=F2?= =?ISO-8859-1?Q?ji?=) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 MULE XEmacs/21.1 (patch 14) (Cuyahoga Valley) (i386--freebsd) Organization: Associated I. Daemons X-PGP-Public-Key: finger knu@FreeBSD.org X-PGP-Fingerprint: 081D 099C 1705 861D 4B70 B04A 920B EFC7 9FD9 E1EE MIME-Version: 1.0 (generated by SEMI 1.14.2 - =?ISO-8859-1?Q?=22Daish=F2ji=22?=) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have implemented -regex and -iregex options for find(1): http://people.FreeBSD.org/~knu/misc/find_regex.diff They are meant to be compatible with those of GNU's and NetBSD's: -regex : True if the whole path of the file matches using basic regular expression. To match a file named ``./foo/xyzzy'', you can use the regular expression ``.*/[xyz]*'' or ``.*/foo/.*'', but not ``xyzzy'' or ``/foo/''. -iregex : Like -regex, but the match is case insensitive. I'd like to commit it after reviews if there is no convincing objection against it. Any suggestion is welcome. Thanks, -- / /__ __ Akinori.org / MUSHA.org / ) ) ) ) / FreeBSD.org / Ruby-lang.org Akinori MUSHA aka / (_ / ( (__( @ iDaemons.org / and.or.jp "We're only at home when we're on the run, on the wing, on the fly" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 11:54: 3 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id B861337B4EC for ; Tue, 20 Feb 2001 11:54:00 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f1KJrSW90599; Tue, 20 Feb 2001 12:53:29 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200102201953.f1KJrSW90599@harmony.village.org> To: Peter Wemm Subject: Re: make buildkernel failed Cc: Jean Louis Ntakpe , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Tue, 20 Feb 2001 01:54:51 PST." <200102200954.f1K9spo30061@mobile.wemm.org> References: <200102200954.f1K9spo30061@mobile.wemm.org> Date: Tue, 20 Feb 2001 12:53:28 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200102200954.f1K9spo30061@mobile.wemm.org> Peter Wemm writes: : Give it about an hour and re-cvsup. Once you have rev 1.94 of : src/sys/conf/kmod.mk, you should be set. Or you can grab the delta by : cvsweb if you are in a hurry. find . -name .depend -delete also works. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 12:44:13 2001 Delivered-To: freebsd-current@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 9967437B401; Tue, 20 Feb 2001 12:44:07 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac2.wam.umd.edu (IDENT:root@rac2.wam.umd.edu [128.8.10.142]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id PAA11707; Tue, 20 Feb 2001 15:44:02 -0500 (EST) Received: from rac2.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac2.wam.umd.edu (8.9.3/8.9.3) with SMTP id PAA29792; Tue, 20 Feb 2001 15:43:55 -0500 (EST) Received: from localhost (culverk@localhost) by rac2.wam.umd.edu (8.9.3/8.9.3) with ESMTP id PAA29788; Tue, 20 Feb 2001 15:43:55 -0500 (EST) X-Authentication-Warning: rac2.wam.umd.edu: culverk owned process doing -bs Date: Tue, 20 Feb 2001 15:43:55 -0500 (EST) From: Kenneth Wayne Culver To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: -stable build of kernel fails 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 With the recent commits to -STABLE (I'm assuming these are MFC that's why I sent to both freebsd-current and freebsd-stable) having to do with the ipfw code, I have had a problem compiling the kernel. These are the errors. cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 vers.c linking kernel ip_fw.o: In function `ip_fw_chk': ip_fw.o(.text+0xff7): undefined reference to `INADDR_TO_IFP' ip_fw.o(.text+0x1017): undefined reference to `INADDR_TO_IFP' *** Error code 1 Before anyone asks, I did a make depend first, and I used config -r instead of config when config'ing my kernel. Did I miss a message or something saying that I need something new in my kernel for firewalls? Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 13: 1:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id B645B37B401; Tue, 20 Feb 2001 13:01:37 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f1KL1Nx95135; Tue, 20 Feb 2001 22:01:26 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Kenneth Wayne Culver Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: -stable build of kernel fails In-Reply-To: Your message of "Tue, 20 Feb 2001 15:43:55 EST." Date: Tue, 20 Feb 2001 22:01:23 +0100 Message-ID: <95133.982702883@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry, my bad. I forgot an #include. In sys/netinet/ip_fw.c add this #include: @@ -48,6 +47,7 @@ #include #include #include +#include #include #include #include I have committed it. Poul-Henning In message , Kenneth Wayne Culver writes: >With the recent commits to -STABLE (I'm assuming these are MFC that's why >I sent to both freebsd-current and freebsd-stable) having to do with the >ipfw code, I have had a problem compiling the kernel. These are the >errors. > >cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes >-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual >-fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include >-D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 vers.c >linking kernel >ip_fw.o: In function `ip_fw_chk': >ip_fw.o(.text+0xff7): undefined reference to `INADDR_TO_IFP' >ip_fw.o(.text+0x1017): undefined reference to `INADDR_TO_IFP' >*** Error code 1 > >Before anyone asks, I did a make depend first, and I used config -r >instead of config when config'ing my kernel. > >Did I miss a message or something saying that I need something new in my >kernel for firewalls? > >Ken > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 13: 8:43 2001 Delivered-To: freebsd-current@freebsd.org Received: from web2904.mail.yahoo.com (web2904.mail.yahoo.com [128.11.68.47]) by hub.freebsd.org (Postfix) with SMTP id C6C0937B491 for ; Tue, 20 Feb 2001 13:08:39 -0800 (PST) (envelope-from mengtrading@rocketmail.com) Received: (qmail 25652 invoked by uid 60001); 20 Feb 2001 21:08:39 -0000 Message-ID: <20010220210839.25651.qmail@web2904.mail.yahoo.com> Received: from [63.203.73.95] by web2904.mail.yahoo.com; Tue, 20 Feb 2001 13:08:39 PST Date: Tue, 20 Feb 2001 13:08:39 -0800 (PST) From: Herman Tan Subject: Re: updating from 12/25/1999 -current? To: Kris Kennaway Cc: current@FreeBSD.ORG In-Reply-To: <20010219031823.A42403@mollari.cthul.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --- Kris Kennaway wrote: > On Mon, Feb 19, 2001 at 01:19:13AM -0800, Herman Tan > wrote: > > Greetings everyone: > > > > Will I run into any problems doing a make world > from a > > 12/25/1999 version of -CURRENT to the latest > -current? > > I noticed on -RELEASE machines when I went from > > 3.3-R to 4.1-R, I had problems because the loaded > > kernel doesn't have the modules and I had to use > the > > Generic kernel in 4.1R and reboot the machine. > Any > > suggestions? Thanks. > > It can probably be done, perhaps with a bit of > hoop-jumping (see > /usr/src/UPDATING), but you may find a binary > upgrade to be easier. > > Kris Wouldn't there be a problem after the world build since the currently loaded kernel won't support certain calls and there would be no way out? I know a binary upgrade would work but it would mess up the /etc directory which I plan to update manually... HT __________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail - only $35 a year! http://personal.mail.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 13:12: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 1C61937B491 for ; Tue, 20 Feb 2001 13:12:04 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f1KLC3N02195 for current@freebsd.org; Tue, 20 Feb 2001 13:12:03 -0800 (PST) Date: Tue, 20 Feb 2001 13:12:03 -0800 From: Alfred Perlstein To: current@freebsd.org Subject: vinum fix take 2 Message-ID: <20010220131203.V6641@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-all-your-base: are belong to us. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Now that I've broken all you non-devfs users of vinum, I have a patch that may get it working again. Please let me know if: http://people.freebsd.org/~alfred/vinum2.diff (you'll need to be -current as of today) works, otherwise I'll be committing tonight or tomorrow as this patch _still_ works for my config. thanks, -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 13:24:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 3D9F537B491 for ; Tue, 20 Feb 2001 13:24:28 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f1KLOQa02561; Tue, 20 Feb 2001 13:24:26 -0800 (PST) Date: Tue, 20 Feb 2001 13:24:26 -0800 From: Alfred Perlstein To: Akinori MUSHA Cc: current@FreeBSD.ORG Subject: Re: find(1) -regex/-iregex Message-ID: <20010220132426.X6641@fw.wintelcom.net> References: <8666i588p4.wl@archon.local.idaemons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <8666i588p4.wl@archon.local.idaemons.org>; from knu@iDaemons.org on Wed, Feb 21, 2001 at 04:18:15AM +0900 X-all-your-base: are belong to us. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Akinori MUSHA [010220 11:19] wrote: > Hi, > > I have implemented -regex and -iregex options for find(1): > Sounds good, just make sure the regex engine matches the one that the other find(1)'s use. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 13:35: 2 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 0FA2C37B491 for ; Tue, 20 Feb 2001 13:35:01 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA12162 for ; Tue, 20 Feb 2001 13:35:00 -0800 Date: Tue, 20 Feb 2001 13:35:00 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: current@freebsd.org Subject: latest alpha breakage 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 ===> libcrypto ( echo "#ifndef MK1MF_BUILD"; echo " /* auto-generated by crypto/Makefile.ssl for crypto/cversion.c */"; echo " #define CFLAGS \"cc\""; echo " #define PLATFORM \"`uname -s`-`uname -m`\""; echo " #define DATE \"`LC_TIME=C date`\""; echo "#endif" ) > buildinf.h make: don't know how to make bn-alpha.pl. Stop *** Error code 2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 13:56:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.rdc1.kt.home.ne.jp (ha2.rdc1.kt.home.ne.jp [203.165.9.243]) by hub.freebsd.org (Postfix) with ESMTP id 6518237B401 for ; Tue, 20 Feb 2001 13:55:55 -0800 (PST) (envelope-from knu@iDaemons.org) Received: from daemon.local.idaemons.org ([203.165.161.10]) by mail.rdc1.kt.home.ne.jp (InterMail vM.4.01.02.00 201-229-116) with ESMTP id <20010220215554.GMAT19464.mail.rdc1.kt.home.ne.jp@daemon.local.idaemons.org>; Tue, 20 Feb 2001 13:55:54 -0800 Received: by daemon.local.idaemons.org (8.11.1/3.7W) id f1KLtsv41569; Wed, 21 Feb 2001 06:55:54 +0900 (JST) Date: Wed, 21 Feb 2001 06:55:54 +0900 Message-ID: <863dd981ed.wl@archon.local.idaemons.org> From: "Akinori MUSHA" To: current@FreeBSD.org Cc: Craig Carey Subject: Re: find(1) -regex/-iregex In-Reply-To: <5.0.2.1.2.20010221083646.03aaf540@pop.qsi.net.nz> References: <8666i588p4.wl@archon.local.idaemons.org> <5.0.2.1.2.20010221083646.03aaf540@pop.qsi.net.nz> User-Agent: Wanderlust/2.5.4 (Smooth) SEMI/1.14.2 (=?ISO-8859-1?Q?Daish=F2?= =?ISO-8859-1?Q?ji?=) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 MULE XEmacs/21.1 (patch 14) (Cuyahoga Valley) (i386--freebsd) Organization: Associated I. Daemons X-PGP-Public-Key: finger knu@FreeBSD.org X-PGP-Fingerprint: 081D 099C 1705 861D 4B70 B04A 920B EFC7 9FD9 E1EE MIME-Version: 1.0 (generated by SEMI 1.14.2 - =?ISO-8859-1?Q?=22Daish=F2ji=22?=) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Wed, 21 Feb 2001 08:42:19 +1300, Craig Carey wrote: > What about the -iname option?. > > I recently installed GNU 'find' just to get that -iname problem fixed. > > Can you do -iname too?. Thanks for the info. It's added now. I'm ashamed to say that I couldn't resist implementing -E option to allow extended regexps. ;) The traditional and POSIX compliant basic regexp is so hard to handle that you can't even say ".+\.S?o" but "..*\.S{0,1}o".. (see re_format(7) for details) Also, I revised the manpage to describe them in detail. Please check it out: http://people.FreeBSD.org/~knu/misc/find_regex.diff > >I'd like to commit it after reviews if there is no convincing > >objection against it. Any suggestion is welcome. > > > > I would object if it is a new variant of regexp. I'd say it ought > be between egrep and perl, in its functionality. I don't think I grasp your meaning.. GNU find(1)'s -regexp uses the "basic regexp" that is _not_ the "extended regexp" which egrep(1) uses nor the one perl(1) uses. Anyway, here lists the facts: - I implemented -regexp/-iregexp using FreeBSD's standard regex library which is supposed to be compliant with POSIX.2 - The match is executed with REG_BASIC, which behavior is compatible with GNU find(1) and NetBSD find(1) - I, however, added -E so we can use extended regexp ;) - Perl's regexp is known to be a unique variant that is different from the "basic regexp" nor the "extended regexp" ;P > It sounds like a regexp would be nice. Me too. :) -- / /__ __ Akinori.org / MUSHA.org / ) ) ) ) / FreeBSD.org / Ruby-lang.org Akinori MUSHA aka / (_ / ( (__( @ iDaemons.org / and.or.jp "We're only at home when we're on the run, on the wing, on the fly" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 15:47:20 2001 Delivered-To: freebsd-current@freebsd.org Received: from Stalker.alfacom.net (Stalker2.Alfacom.net [212.26.133.81]) by hub.freebsd.org (Postfix) with ESMTP id 07D2437B491 for ; Tue, 20 Feb 2001 15:47:14 -0800 (PST) (envelope-from vkushnir@Alfacom.net) Received: from kushnir1.kiev.ua (dup-57.alfacom.net [62.244.36.57]) by Stalker.alfacom.net (8.9.3/8.9.3) with ESMTP id BAA02252 for ; Wed, 21 Feb 2001 01:47:04 +0200 (EET) Received: from localhost (volodya@localhost) by kushnir1.kiev.ua (8.11.2/8.11.1) with ESMTP id f1KNkwQ31035 for ; Wed, 21 Feb 2001 01:47:00 +0200 (EET) (envelope-from volodya@kushnir1.kiev.ua) Date: Wed, 21 Feb 2001 01:46:58 +0200 (EET) From: Vladimir Kushnir Reply-To: Vladimir Kushnir To: Subject: Slightly OT: XMMS on -CURRENT? 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 Hi all, Does anybody run xmms on -CURRENT? For some reason it hungs here on "poll". Any other (multithread included) program runs flawlessly. The only possibility I can see right now is plugin system (i.e. dl* functions) but there haven't been eny changes in ld-elf.so.1 as of lately. I'm really puzzled :-( Any clues? "uname -a" output: FreeBSD kushnir1.kiev.ua 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Sun Feb 18 09:50:07 EET 2001 root@kushnir1.kiev.ua:/usr/obj/usr/src/sys/KUSHNIR i386 -- ===========================|======================= Vladimir Kushnir | vkushnir@Alfacom.net | Powered by FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 16:14: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from casa.encontacto.net (adsl-63-205-16-202.dsl.mtry01.pacbell.net [63.205.16.202]) by hub.freebsd.org (Postfix) with ESMTP id 786A237B4EC for ; Tue, 20 Feb 2001 16:14:03 -0800 (PST) (envelope-from eculp@EnContacto.net) Received: from EnContacto.net (adsl-63-205-16-203.dsl.mtry01.pacbell.net [63.205.16.203]) by casa.encontacto.net (8.11.2/8.11.2) with ESMTP id f1L0E1L00558 for ; Tue, 20 Feb 2001 16:14:01 -0800 (PST) (envelope-from eculp@EnContacto.net) Message-ID: <3A93084B.3FACCCA5@EnContacto.net> Date: Tue, 20 Feb 2001 16:14:02 -0800 From: Edwin Culp X-Mailer: Mozilla 4.75C-CCK-MCD {C-UDP; EBM-APPLE} (Macintosh; U; PPC) X-Accept-Language: en MIME-Version: 1.0 To: Current@FreeBSD.Org Subject: Re: What goes at the boot prompt References: <3A9306AC.36AF1BE@EnContacto.net> Content-Type: text/plain; charset=us-ascii; x-mac-type="54455854"; x-mac-creator="4D4F5353" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have a kernel that hangs at boot, so when I try to boot kernel.old, I > have a problem. At the Default: F1 prompt, I give it an F1 and then the > space key give me > > >> FreeBSD/i386 BOOT > Default: 0:wd(o,a)/boot/loader > boot: _ > > What do I put at the boot prompt. I think the changes of the last few > days have left me a little punchy. I thought that I always put > kernel.old or /boot/kernel.old. > > I appologize for such a dumb question. I did check the boot manual and > it says: > > >> FreeBSD/i386 BOOT > Default: 0:ad(0,a)/kernel > boot: > > bios_drive:interface(unit,part) filename [-aCcDdghPrsv] > > filename > The pathname of the file to boot (relative to the > root > directory on the specified partition). Defaults to > > /kernel. Symbolic links are not supported (hard > links > are). > > I still don't get it. > > TIA, > > ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 18: 0:23 2001 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 53A8637B503 for ; Tue, 20 Feb 2001 18:00:19 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id VAA12331; Tue, 20 Feb 2001 21:00:17 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.2/8.9.1) id f1L1xlX37822; Tue, 20 Feb 2001 20:59:47 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14995.8467.513983.760143@grasshopper.cs.duke.edu> Date: Tue, 20 Feb 2001 20:59:47 -0500 (EST) To: mjacob@feral.com Cc: current@freebsd.org Subject: Re: latest alpha breakage In-Reply-To: References: X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Jacob writes: > > ===> libcrypto > ( echo "#ifndef MK1MF_BUILD"; echo " /* auto-generated by > crypto/Makefile.ssl for crypto/cversion.c */"; echo " #define CFLAGS > \"cc\""; echo " #define PLATFORM \"`uname -s`-`uname -m`\""; echo > " #define DATE \"`LC_TIME=C date`\""; echo "#endif" ) > buildinf.h > make: don't know how to make bn-alpha.pl. Stop > *** Error code 2 This looks like the libcrypto breakage that I was complainging about. I thought this was fixed last night -- have you cvsup'ed recently? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 18: 6:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id CD4B937B401; Tue, 20 Feb 2001 18:06:40 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id SAA13301; Tue, 20 Feb 2001 18:06:38 -0800 Date: Tue, 20 Feb 2001 18:06:38 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Andrew Gallatin Cc: current@freebsd.org Subject: Re: latest alpha breakage In-Reply-To: <14995.8467.513983.760143@grasshopper.cs.duke.edu> 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 cvsup every day in periodic/daily- maybe I just missed this one. This has been dead for several days- sorryu I guess I missed your mail about it.... Umm... yup... sorry for the noise > > Matthew Jacob writes: > > > > ===> libcrypto > > ( echo "#ifndef MK1MF_BUILD"; echo " /* auto-generated by > > crypto/Makefile.ssl for crypto/cversion.c */"; echo " #define CFLAGS > > \"cc\""; echo " #define PLATFORM \"`uname -s`-`uname -m`\""; echo > > " #define DATE \"`LC_TIME=C date`\""; echo "#endif" ) > buildinf.h > > make: don't know how to make bn-alpha.pl. Stop > > *** Error code 2 > > This looks like the libcrypto breakage that I was complainging about. > I thought this was fixed last night -- have you cvsup'ed recently? > > Drew > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 19: 0:53 2001 Delivered-To: freebsd-current@freebsd.org Received: from lamborghini.indocyber.com (lamborghini.indocyber.com [202.180.0.86]) by hub.freebsd.org (Postfix) with SMTP id 806CD37B698 for ; Tue, 20 Feb 2001 19:00:42 -0800 (PST) (envelope-from john@office.naver.co.id) Received: (qmail 6778 invoked from network); 21 Feb 2001 02:55:13 -0000 Received: from unknown (HELO dante.naver.co.id) (postfix@202.155.86.83) by lamborghini.indocyber.com with SMTP; 21 Feb 2001 02:55:13 -0000 Received: by dante.naver.co.id (Postfix, from userid 1000) id 3BCE2BDEB9; Wed, 21 Feb 2001 10:00:35 +0700 (JAVT) Date: Wed, 21 Feb 2001 10:00:35 +0700 From: John Indra To: Vladimir Kushnir Cc: current@FreeBSD.ORG Subject: Re: Slightly OT: XMMS on -CURRENT? Message-ID: <20010221100034.A510@office.naver.co.id> Mail-Followup-To: Vladimir Kushnir , current@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: ; from vkushnir@Alfacom.net on Wed, Feb 21, 2001 at 01:46:58AM +0200 X-Mailer: Mutt 1.2.5i on FreeBSD 5.0-20010210-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 21, 2001 at 01:46:58AM +0200, Vladimir Kushnir wrote: >Does anybody run xmms on -CURRENT? For some reason it hungs here on Yes I run XMMS on 20010210-CURRENT. It's fine... >"poll". Any other (multithread included) program runs flawlessly. The only >possibility I can see right now is plugin system (i.e. dl* functions) but >there haven't been eny changes in ld-elf.so.1 as of lately. I'm really >puzzled :-( Any clues? > >"uname -a" output: >FreeBSD kushnir1.kiev.ua 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Sun Feb 18 >09:50:07 EET 2001 root@kushnir1.kiev.ua:/usr/obj/usr/src/sys/KUSHNIR >i386 I noted that your version of -CURRENT is "after Feb 10" This could be -CURRENT in mess :) BTW all my KDE or Qt 2.2.4 related apps segfault immediately after startup on 20010210-CURRENT. /john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 19:38:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 503F237B491 for ; Tue, 20 Feb 2001 19:38:28 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p06-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.71]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id MAA13745; Wed, 21 Feb 2001 12:37:56 +0900 (JST) Message-ID: <3A93376D.B371FCD1@newsguy.com> Date: Wed, 21 Feb 2001 12:35:09 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: Akinori MUSHA , current@freebsd.org Subject: Re: find(1) -regex/-iregex References: <8666i588p4.wl@archon.local.idaemons.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Akinori MUSHA wrote: > > Hi, > > I have implemented -regex and -iregex options for find(1): > > http://people.FreeBSD.org/~knu/misc/find_regex.diff I'm not familiar with find sources, but it seems to me you execute regcomp() for each file name to be compared? If so... change that! :-) Regcomp() does expensive setup so that regexec() can be run inexpensively many times over. > They are meant to be compatible with those of GNU's and NetBSD's: > > -regex : > > True if the whole path of the file matches using > basic regular expression. To match a file named > ``./foo/xyzzy'', you can use the regular expression > ``.*/[xyz]*'' or ``.*/foo/.*'', but not ``xyzzy'' or > ``/foo/''. > > -iregex : > > Like -regex, but the match is case insensitive. You forgot -E (use extended regexp syntax), and the example you show above is extended regexp syntax, not basic regexp syntax. > I'd like to commit it after reviews if there is no convincing > objection against it. Any suggestion is welcome. Well, I expressed my concerns above. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@the.fashionable.bsdconspiracy.net "Too bad sentience isn't a marketable commodity." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 19:40:14 2001 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 23D4537B67D for ; Tue, 20 Feb 2001 19:40:10 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p06-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.71]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id MAA14400; Wed, 21 Feb 2001 12:39:51 +0900 (JST) Message-ID: <3A9337E0.A51A3E8B@newsguy.com> Date: Wed, 21 Feb 2001 12:37:04 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: Alfred Perlstein Cc: Akinori MUSHA , current@FreeBSD.ORG Subject: Re: find(1) -regex/-iregex References: <8666i588p4.wl@archon.local.idaemons.org> <20010220132426.X6641@fw.wintelcom.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > > * Akinori MUSHA [010220 11:19] wrote: > > Hi, > > > > I have implemented -regex and -iregex options for find(1): > > > > Sounds good, just make sure the regex engine matches the one that > the other find(1)'s use. It won't. GNU find certainly uses GNU regexp library, which has lots of extra stuff. Naturally, our find will be using our library instead. Nothing we can do about it. It is the way of the Gnu to extend and embrace. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@the.fashionable.bsdconspiracy.net "Too bad sentience isn't a marketable commodity." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 19:42:47 2001 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id EA77F37B401 for ; Tue, 20 Feb 2001 19:42:42 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p06-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.71]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id MAA15294; Wed, 21 Feb 2001 12:42:32 +0900 (JST) Message-ID: <3A933882.212928AF@newsguy.com> Date: Wed, 21 Feb 2001 12:39:46 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: Akinori MUSHA Cc: current@FreeBSD.ORG, Craig Carey Subject: Re: find(1) -regex/-iregex References: <8666i588p4.wl@archon.local.idaemons.org> <5.0.2.1.2.20010221083646.03aaf540@pop.qsi.net.nz> <863dd981ed.wl@archon.local.idaemons.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Akinori MUSHA wrote: > > > I would object if it is a new variant of regexp. I'd say it ought > > be between egrep and perl, in its functionality. ... > > - Perl's regexp is known to be a unique variant that is different > from the "basic regexp" nor the "extended regexp" ;P For that matter, anyone talking about "standard" regexp of any kind I invite to take a look at the include file for gnu regexp, to see just how many slightly different variants of regexp there are out there in various utilities. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@the.fashionable.bsdconspiracy.net "Too bad sentience isn't a marketable commodity." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 20: 0:48 2001 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id E705737B401 for ; Tue, 20 Feb 2001 20:00:45 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p06-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.71]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id NAA19955; Wed, 21 Feb 2001 13:00:41 +0900 (JST) Message-ID: <3A933CC2.33032273@newsguy.com> Date: Wed, 21 Feb 2001 12:57:54 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: Edwin Culp Cc: Current@FreeBSD.ORG Subject: Re: What goes at the boot prompt References: <3A9306AC.36AF1BE@EnContacto.net> <3A93084B.3FACCCA5@EnContacto.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Edwin Culp wrote: > > > I have a kernel that hangs at boot, so when I try to boot kernel.old, I > > have a problem. At the Default: F1 prompt, I give it an F1 and then the > > space key give me > > > > >> FreeBSD/i386 BOOT > > Default: 0:wd(o,a)/boot/loader > > boot: _ > > > > What do I put at the boot prompt. I think the changes of the last few > > days have left me a little punchy. I thought that I always put > > kernel.old or /boot/kernel.old. On -current, /boot/kernel.old is a directory containing both kernel and modules. /boot/kernel.old/kernel would do, but why skip the loader phase? Let loader proceed, interrupt the ten second count and then type: boot kernel.old (or boot-conf kernel.old, if you are using loader to get some modules loaded) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@the.fashionable.bsdconspiracy.net "Too bad sentience isn't a marketable commodity." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 21:12:59 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.rdc1.kt.home.ne.jp (ha2.rdc1.kt.home.ne.jp [203.165.9.243]) by hub.freebsd.org (Postfix) with ESMTP id 8075237B401 for ; Tue, 20 Feb 2001 21:12:52 -0800 (PST) (envelope-from knu@iDaemons.org) Received: from daemon.local.idaemons.org ([203.165.161.10]) by mail.rdc1.kt.home.ne.jp (InterMail vM.4.01.02.00 201-229-116) with ESMTP id <20010221051251.KZGM19464.mail.rdc1.kt.home.ne.jp@daemon.local.idaemons.org>; Tue, 20 Feb 2001 21:12:51 -0800 Received: by daemon.local.idaemons.org (8.11.1/3.7W) id f1L5Cpv07590; Wed, 21 Feb 2001 14:12:51 +0900 (JST) Date: Wed, 21 Feb 2001 14:12:51 +0900 Message-ID: <863dd8r54c.wl@archon.local.idaemons.org> From: "Akinori MUSHA" To: "Daniel C. Sobral" Cc: current@freebsd.org Subject: Re: find(1) -regex/-iregex In-Reply-To: <3A93376D.B371FCD1@newsguy.com> References: <8666i588p4.wl@archon.local.idaemons.org> <3A93376D.B371FCD1@newsguy.com> User-Agent: Wanderlust/2.5.4 (Smooth) SEMI/1.14.2 (=?ISO-8859-1?Q?Daish=F2?= =?ISO-8859-1?Q?ji?=) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 MULE XEmacs/21.1 (patch 14) (Cuyahoga Valley) (i386--freebsd) Organization: Associated I. Daemons X-PGP-Public-Key: finger knu@FreeBSD.org X-PGP-Fingerprint: 081D 099C 1705 861D 4B70 B04A 920B EFC7 9FD9 E1EE MIME-Version: 1.0 (generated by SEMI 1.14.2 - =?ISO-8859-1?Q?=22Daish=F2ji=22?=) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Wed, 21 Feb 2001 12:35:09 +0900, Daniel C. Sobral wrote: > I'm not familiar with find sources, but it seems to me you execute > regcomp() for each file name to be compared? If so... change that! :-) > Regcomp() does expensive setup so that regexec() can be run > inexpensively many times over. Indeed. I'll do it soon, thanks. > You forgot -E (use extended regexp syntax), and the example you show > above is extended regexp syntax, not basic regexp syntax. Noted. -- / /__ __ Akinori.org / MUSHA.org / ) ) ) ) / FreeBSD.org / Ruby-lang.org Akinori MUSHA aka / (_ / ( (__( @ iDaemons.org / and.or.jp "We're only at home when we're on the run, on the wing, on the fly" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 21:15:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-165-226-53.dsl.lsan03.pacbell.net [64.165.226.53]) by hub.freebsd.org (Postfix) with ESMTP id 3399237B65D for ; Tue, 20 Feb 2001 21:15:28 -0800 (PST) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id BB1C066F2E; Tue, 20 Feb 2001 21:15:27 -0800 (PST) Date: Tue, 20 Feb 2001 21:15:27 -0800 From: Kris Kennaway To: Herman Tan Cc: Kris Kennaway , current@FreeBSD.ORG Subject: Re: updating from 12/25/1999 -current? Message-ID: <20010220211527.A44890@mollari.cthul.hu> References: <20010219031823.A42403@mollari.cthul.hu> <20010220210839.25651.qmail@web2904.mail.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="dDRMvlgZJXvWKvBx" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010220210839.25651.qmail@web2904.mail.yahoo.com>; from mengtrading@rocketmail.com on Tue, Feb 20, 2001 at 01:08:39PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --dDRMvlgZJXvWKvBx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Feb 20, 2001 at 01:08:39PM -0800, Herman Tan wrote: > Wouldn't there be a problem after the world build > since the currently loaded kernel won't support > certain calls and there would be no way out? I know a > binary upgrade would work but it would mess up the > /etc directory which I plan to update manually... Not if you follow the documented buildkernel etc. procedure. Kris --dDRMvlgZJXvWKvBx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6k07vWry0BWjoQKURAmMdAJwN7I1o6CjJaMgzGUkZF3pfrQlrMwCg5nH5 /OCx2ERh3k7rZM8H6wYBHxw= =DboT -----END PGP SIGNATURE----- --dDRMvlgZJXvWKvBx-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 21:17: 0 2001 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-165-226-53.dsl.lsan03.pacbell.net [64.165.226.53]) by hub.freebsd.org (Postfix) with ESMTP id 19EEF37B503 for ; Tue, 20 Feb 2001 21:16:58 -0800 (PST) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id CAD3166F2E; Tue, 20 Feb 2001 21:16:57 -0800 (PST) Date: Tue, 20 Feb 2001 21:16:57 -0800 From: Kris Kennaway To: Edwin Culp Cc: Current@FreeBSD.Org Subject: Re: What goes at the boot prompt Message-ID: <20010220211657.B44890@mollari.cthul.hu> References: <3A9306AC.36AF1BE@EnContacto.net> <3A93084B.3FACCCA5@EnContacto.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="yEPQxsgoJgBvi8ip" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A93084B.3FACCCA5@EnContacto.net>; from eculp@EnContacto.net on Tue, Feb 20, 2001 at 04:14:02PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --yEPQxsgoJgBvi8ip Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Feb 20, 2001 at 04:14:02PM -0800, Edwin Culp wrote: > > I still don't get it. Should you really be running -current? This kind of support question isn't appropriate for this list, IMO. Kris --yEPQxsgoJgBvi8ip Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6k09JWry0BWjoQKURApOnAJsFH+jTKnC3kh3i+Jng6srkILKirgCbB7Es cAr4BMoWqOdTWhSpR3d3mpo= =leSW -----END PGP SIGNATURE----- --yEPQxsgoJgBvi8ip-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 21:51: 0 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.rdc1.kt.home.ne.jp (ha2.rdc1.kt.home.ne.jp [203.165.9.243]) by hub.freebsd.org (Postfix) with ESMTP id 285B937B401 for ; Tue, 20 Feb 2001 21:50:57 -0800 (PST) (envelope-from knu@iDaemons.org) Received: from daemon.local.idaemons.org ([203.165.161.10]) by mail.rdc1.kt.home.ne.jp (InterMail vM.4.01.02.00 201-229-116) with ESMTP id <20010221055056.LJKG19464.mail.rdc1.kt.home.ne.jp@daemon.local.idaemons.org>; Tue, 20 Feb 2001 21:50:56 -0800 Received: by daemon.local.idaemons.org (8.11.1/3.7W) id f1L5ouv08209; Wed, 21 Feb 2001 14:50:56 +0900 (JST) Date: Wed, 21 Feb 2001 14:50:56 +0900 Message-ID: <861yssr3cv.wl@archon.local.idaemons.org> From: "Akinori MUSHA" To: "Daniel C. Sobral" Cc: current@FreeBSD.ORG Subject: Re: find(1) -regex/-iregex In-Reply-To: <863dd8r54c.wl@archon.local.idaemons.org> References: <8666i588p4.wl@archon.local.idaemons.org> <3A93376D.B371FCD1@newsguy.com> <863dd8r54c.wl@archon.local.idaemons.org> User-Agent: Wanderlust/2.5.4 (Smooth) SEMI/1.14.2 (=?ISO-8859-1?Q?Daish=F2?= =?ISO-8859-1?Q?ji?=) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 MULE XEmacs/21.1 (patch 14) (Cuyahoga Valley) (i386--freebsd) Organization: Associated I. Daemons X-PGP-Public-Key: finger knu@FreeBSD.org X-PGP-Fingerprint: 081D 099C 1705 861D 4B70 B04A 920B EFC7 9FD9 E1EE MIME-Version: 1.0 (generated by SEMI 1.14.2 - =?ISO-8859-1?Q?=22Daish=F2ji=22?=) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Wed, 21 Feb 2001 14:12:51 +0900, I wrote: > At Wed, 21 Feb 2001 12:35:09 +0900, > Daniel C. Sobral wrote: > > I'm not familiar with find sources, but it seems to me you execute > > regcomp() for each file name to be compared? If so... change that! :-) > > Regcomp() does expensive setup so that regexec() can be run > > inexpensively many times over. > > Indeed. I'll do it soon, thanks. Updated. http://people.FreeBSD.org/~knu/misc/find_regex.diff > > You forgot -E (use extended regexp syntax), and the example you show > > above is extended regexp syntax, not basic regexp syntax. Well, it was added after I had posted the original article. The latest one's find.1 mentions it. .It Fl E Interpret regular expressions followed by .Ic -regex and .Ic -iregex options as extended (modern) regular expressions rather than basic regular expressions (BRE's). The .Xr re_format 7 manual page fully describes both formats. As for the syntax my examples conform to, I think they are valid both for basic and extended. True if the whole path of the file matches .Ar pattern using regular expression. To match a file named ``./foo/xyzzy'', you can use the regular expression ``.*/[xyz]*'' or ``.*/foo/.*'', but not ``xyzzy'' or ``/foo/''. Thanks for your suggestions. -- / /__ __ Akinori.org / MUSHA.org / ) ) ) ) / FreeBSD.org / Ruby-lang.org Akinori MUSHA aka / (_ / ( (__( @ iDaemons.org / and.or.jp "We're only at home when we're on the run, on the wing, on the fly" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 21:58:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from drone5.qsi.net.nz (drone5-svc-skyt.qsi.net.nz [202.89.128.5]) by hub.freebsd.org (Postfix) with SMTP id 766FB37B503 for ; Tue, 20 Feb 2001 21:58:41 -0800 (PST) (envelope-from research@ijs.co.nz) Received: (qmail 36912 invoked by uid 0); 21 Feb 2001 05:58:36 -0000 Received: from unknown (HELO bipod.ijs.co.nz) ([202.89.144.250]) (envelope-sender ) by 0 (qmail-ldap-1.03) with SMTP for ; 21 Feb 2001 05:58:36 -0000 Message-Id: <5.0.2.1.2.20010221184120.036e43b0@pop.qsi.net.nz> X-Sender: research@pop.qsi.net.nz X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Wed, 21 Feb 2001 18:53:26 +1300 To: current@freebsd.org From: Craig Carey Subject: Re: find(1) -regex/-iregex Cc: Akinori MUSHA In-Reply-To: <863dd8r54c.wl@archon.local.idaemons.org> References: <3A93376D.B371FCD1@newsguy.com> <8666i588p4.wl@archon.local.idaemons.org> <3A93376D.B371FCD1@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can an -iname option be provided. Then the FreeBSD find would be more like GNU find, and lines like this could be written: find /msdos-disk -iname "*txt" | xargs -n 1 ls -l I am doubtful that the -regexp needs to be inferior to the the -egrep option. What software would break: it was said that there is no regexp?. There are opinions around saying that egrep is better than grep. What is the -E option: perhaps this?: -eregex Suppose it is case sensitive. Then it could be -eiregex or -ieregex or -eregexi I hope for no regex if there is no '-iname' feature. [It would be nice if the advanced regexes settled onto the Perl regex, e.g. perhaps throughout all utilities. -pregex ] At 21-02-01 14:12 +0900 Wednesday, Akinori MUSHA wrote: >At Wed, 21 Feb 2001 12:35:09 +0900, >Daniel C. Sobral wrote: >> I'm not familiar with find sources, but it seems to me you execute >> regcomp() for each file name to be compared? If so... change that! :-) >> Regcomp() does expensive setup so that regexec() can be run >> inexpensively many times over. > >Indeed. I'll do it soon, thanks. > >> You forgot -E (use extended regexp syntax), and the example you show >> above is extended regexp syntax, not basic regexp syntax. > >Noted. > ... What about improving 'ls' too?: can there be an option so that it refuses to list any information about directories (useful in the above example). Also, is there any plan to stop the wastage of space in the central columns of "ls"'s output, where it lists uninteresting information. Maybe a '-p' option, like GNU 'ls' has. E-mail: Craig Carey (backup terratope@yahoo.com) Auckland, NZ. | Snooz Metasearch: http://www.ijs.co.nz/info/snooz.htm To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 22: 9:17 2001 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id EC17D37B401 for ; Tue, 20 Feb 2001 22:09:14 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p06-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.71]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id PAA23646; Wed, 21 Feb 2001 15:09:10 +0900 (JST) Message-ID: <3A935ADE.21C1F6EC@newsguy.com> Date: Wed, 21 Feb 2001 15:06:22 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: Akinori MUSHA Cc: current@FreeBSD.ORG Subject: Re: find(1) -regex/-iregex References: <8666i588p4.wl@archon.local.idaemons.org> <3A93376D.B371FCD1@newsguy.com> <863dd8r54c.wl@archon.local.idaemons.org> <861yssr3cv.wl@archon.local.idaemons.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Akinori MUSHA wrote: > > > > I'm not familiar with find sources, but it seems to me you execute > > > regcomp() for each file name to be compared? If so... change that! :-) > > > Regcomp() does expensive setup so that regexec() can be run > > > inexpensively many times over. > > > > Indeed. I'll do it soon, thanks. > > Updated. > > http://people.FreeBSD.org/~knu/misc/find_regex.diff You might have done it, but the version above is not it. :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@the.fashionable.bsdconspiracy.net "Too bad sentience isn't a marketable commodity." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 22:17:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.rdc1.kt.home.ne.jp (ha2.rdc1.kt.home.ne.jp [203.165.9.243]) by hub.freebsd.org (Postfix) with ESMTP id 08EB337B503 for ; Tue, 20 Feb 2001 22:17:49 -0800 (PST) (envelope-from knu@iDaemons.org) Received: from daemon.local.idaemons.org ([203.165.161.10]) by mail.rdc1.kt.home.ne.jp (InterMail vM.4.01.02.00 201-229-116) with ESMTP id <20010221061747.LRCY19464.mail.rdc1.kt.home.ne.jp@daemon.local.idaemons.org>; Tue, 20 Feb 2001 22:17:47 -0800 Received: by daemon.local.idaemons.org (8.11.1/3.7W) id f1L6Hlv08602; Wed, 21 Feb 2001 15:17:47 +0900 (JST) Date: Wed, 21 Feb 2001 15:17:47 +0900 Message-ID: <86zofgpnjo.wl@archon.local.idaemons.org> From: "Akinori MUSHA" To: Craig Carey Cc: current@freebsd.org Subject: Re: find(1) -regex/-iregex In-Reply-To: <5.0.2.1.2.20010221184120.036e43b0@pop.qsi.net.nz> References: <3A93376D.B371FCD1@newsguy.com> <8666i588p4.wl@archon.local.idaemons.org> <863dd8r54c.wl@archon.local.idaemons.org> <5.0.2.1.2.20010221184120.036e43b0@pop.qsi.net.nz> User-Agent: Wanderlust/2.5.4 (Smooth) SEMI/1.14.2 (=?ISO-8859-1?Q?Daish=F2?= =?ISO-8859-1?Q?ji?=) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 MULE XEmacs/21.1 (patch 14) (Cuyahoga Valley) (i386--freebsd) Organization: Associated I. Daemons X-PGP-Public-Key: finger knu@FreeBSD.org X-PGP-Fingerprint: 081D 099C 1705 861D 4B70 B04A 920B EFC7 9FD9 E1EE MIME-Version: 1.0 (generated by SEMI 1.14.2 - =?ISO-8859-1?Q?=22Daish=F2ji=22?=) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Wed, 21 Feb 2001 18:53:26 +1300, Craig Carey wrote: > Can an -iname option be provided. Then the FreeBSD find would be > more like GNU find, and lines like this could be written: Yes, it's already implemented as I wrote in the previous mail. > I am doubtful that the -regexp needs to be inferior to the the > -egrep option. What software would break: it was said that there is > no regexp?. There are opinions around saying that egrep is better > than grep. We are not aiming to be that GNU'ish. Being compatible with NetBSD is a good thing in a sense. > What is the -E option: perhaps this?: -eregex > > Suppose it is case sensitive. Then it could be > -eiregex or -ieregex or -eregexi I don't like it somehow.. I chose -E because it is consistent with (our) grep(1) and sed(1). > What about improving 'ls' too?: can there be an option so that it > refuses to list any information about directories (useful in the > above example). Also, is there any plan to stop the wastage of > space in the central columns of "ls"'s output, where it lists > uninteresting information. Maybe a '-p' option, like GNU 'ls' > has. Interesting, but it would be done at some other time. I'd like to focus on regex this time. -- / /__ __ Akinori.org / MUSHA.org / ) ) ) ) / FreeBSD.org / Ruby-lang.org Akinori MUSHA aka / (_ / ( (__( @ iDaemons.org / and.or.jp "We're only at home when we're on the run, on the wing, on the fly" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 20 23: 1:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.rdc1.kt.home.ne.jp (ha2.rdc1.kt.home.ne.jp [203.165.9.243]) by hub.freebsd.org (Postfix) with ESMTP id DDFA737B401 for ; Tue, 20 Feb 2001 23:01:07 -0800 (PST) (envelope-from knu@iDaemons.org) Received: from daemon.local.idaemons.org ([203.165.161.10]) by mail.rdc1.kt.home.ne.jp (InterMail vM.4.01.02.00 201-229-116) with ESMTP id <20010221070107.MDNA19464.mail.rdc1.kt.home.ne.jp@daemon.local.idaemons.org>; Tue, 20 Feb 2001 23:01:07 -0800 Received: by daemon.local.idaemons.org (8.11.1/3.7W) id f1L716v09210; Wed, 21 Feb 2001 16:01:06 +0900 (JST) Date: Wed, 21 Feb 2001 16:01:06 +0900 Message-ID: <86wvakpljh.wl@archon.local.idaemons.org> From: "Akinori MUSHA" To: "Daniel C. Sobral" Cc: current@FreeBSD.ORG Subject: Re: find(1) -regex/-iregex In-Reply-To: <3A935ADE.21C1F6EC@newsguy.com> References: <8666i588p4.wl@archon.local.idaemons.org> <3A93376D.B371FCD1@newsguy.com> <863dd8r54c.wl@archon.local.idaemons.org> <861yssr3cv.wl@archon.local.idaemons.org> <3A935ADE.21C1F6EC@newsguy.com> User-Agent: Wanderlust/2.5.4 (Smooth) SEMI/1.14.2 (=?ISO-8859-1?Q?Daish=F2?= =?ISO-8859-1?Q?ji?=) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 MULE XEmacs/21.1 (patch 14) (Cuyahoga Valley) (i386--freebsd) Organization: Associated I. Daemons X-PGP-Public-Key: finger knu@FreeBSD.org X-PGP-Fingerprint: 081D 099C 1705 861D 4B70 B04A 920B EFC7 9FD9 E1EE MIME-Version: 1.0 (generated by SEMI 1.14.2 - =?ISO-8859-1?Q?=22Daish=F2ji=22?=) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Wed, 21 Feb 2001 15:06:22 +0900, Daniel C. Sobral wrote: > > http://people.FreeBSD.org/~knu/misc/find_regex.diff > > You might have done it, but the version above is not it. :-) Oh, would you please reload it? When you see a function named do_c_regex(), that's it. :) -- / /__ __ Akinori.org / MUSHA.org / ) ) ) ) / FreeBSD.org / Ruby-lang.org Akinori MUSHA aka / (_ / ( (__( @ iDaemons.org / and.or.jp "We're only at home when we're on the run, on the wing, on the fly" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 21 3:23:47 2001 Delivered-To: freebsd-current@freebsd.org Received: from webcom.it (brian.inet.it [213.92.4.195]) by hub.freebsd.org (Postfix) with SMTP id 0513A37B401 for ; Wed, 21 Feb 2001 03:23:44 -0800 (PST) (envelope-from andrea@webcom.it) Received: (qmail 18026 invoked by uid 1000); 20 Feb 2001 00:50:28 -0000 Date: Tue, 20 Feb 2001 01:50:23 +0100 From: Andrea Campi To: freebsd-current@freebsd.org Subject: -CURRENT slowdown in last 2 weeks Message-ID: <20010220015012.B5116@webcom.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am noticing a severe slowdown on my -CURRENT system. It actually started after Feb [3-5] changes in intrupt handling, but I didn't really notice until I run a make world (which I delayed doing because of, well you guess, the libc breakage). When I say severe I mean make buildworld takes x3 longer. Am I alone in this, or is it well known (even though I didn't see it discussed, but I might have overlooked)? Could it be related instead to all the lock reversal messages I've been getting ever since? I know it's an interrupt issue because it only happens when I'm exercising my HD. I guess it's time to put /usr/src and maybe even /usr/obj on an NFS server, I'm sure it can't be slower... *grin* I'm not complaining, I'm offering to debug! Bye, Andrea -- Give a man a fish and you feed him for a day; teach him to use the Net and he won't bother you for weeks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 21 5: 6:41 2001 Delivered-To: freebsd-current@freebsd.org Received: from white.imgsrc.co.jp (ns.imgsrc.co.jp [210.226.20.2]) by hub.freebsd.org (Postfix) with ESMTP id 523C837B401; Wed, 21 Feb 2001 05:06:37 -0800 (PST) (envelope-from kuriyama@imgsrc.co.jp) Received: from waterblue.imgsrc.co.jp (waterblue.imgsrc.co.jp [210.226.20.160]) by white.imgsrc.co.jp (8.11.2/8.11.0) with ESMTP id f1LD6ZT22349; Wed, 21 Feb 2001 22:06:35 +0900 (JST) Date: Wed, 21 Feb 2001 22:06:29 +0900 Message-ID: <7m66i4kwx6.wl@waterblue.imgsrc.co.jp> From: Jun Kuriyama To: Assar Westerlund To: Mark Murray Cc: current@FreeBSD.org Subject: Re: Building procedure of krb5 is broken In-Reply-To: <20010220184324P.matusita@jp.FreeBSD.org> References: <20010217190142A.matusita@jp.FreeBSD.org> <20010220184324P.matusita@jp.FreeBSD.org> User-Agent: Wanderlust/2.4.0 (Rio) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 14) (Cuyahoga Valley) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: multipart/mixed; boundary="Multipart_Wed_Feb_21_22:06:29_2001-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --Multipart_Wed_Feb_21_22:06:29_2001-1 Content-Type: text/plain; charset=US-ASCII At 20 Feb 2001 09:44:01 GMT, Makoto MATSUSHITA wrote: > It seems that add 'CFLAGS+=-I${KRB5OBJDIR}' to > src/kerberos5/lib/libgssapi/Makefile is required to fix this, since > krb5_err.h is not in ${KRB5DIR}/lib/krb5. In my environment, buildworld was finished with attached patch. I don't know KRB4 should be defined in this file or not. But in crypto/heimdal/kdc/headers.h, krb.h (this file is not exist in heimdal distribution) is included if KRB4 is defined. So if MAKE_KERBEROS5=YES is set in /etc/make.conf, buildworld is failed because krb.h is not found. Any ideas? -- Jun Kuriyama // IMG SRC, Inc. // FreeBSD Project --Multipart_Wed_Feb_21_22:06:29_2001-1 Content-Type: application/octet-stream; type=patch Content-Disposition: attachment; filename="krb.diff" Content-Transfer-Encoding: 7bit Index: config.h =================================================================== RCS file: /home/ncvs/src/kerberos5/include/config.h,v retrieving revision 1.4 diff -u -r1.4 config.h --- config.h 2001/02/13 16:56:46 1.4 +++ config.h 2001/02/21 06:17:31 @@ -1008,7 +1008,7 @@ /* #undef KASERVER_DB */ /* Define if you have the krb4 package. */ -#define KRB4 1 +/* #define KRB4 1 */ /* Enable Kerberos 5 support in applications. */ #define KRB5 1 --Multipart_Wed_Feb_21_22:06:29_2001-1-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 21 5:11:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from gw.nectar.com (gw.nectar.com [208.42.49.153]) by hub.freebsd.org (Postfix) with ESMTP id AEE9337B491; Wed, 21 Feb 2001 05:11:34 -0800 (PST) (envelope-from nectar@nectar.com) Received: by gw.nectar.com (Postfix, from userid 1001) id 0E12118C92; Wed, 21 Feb 2001 07:11:34 -0600 (CST) Date: Wed, 21 Feb 2001 07:11:33 -0600 From: "Jacques A. Vidrine" To: Jun Kuriyama Cc: Assar Westerlund , Mark Murray , current@FreeBSD.org Subject: Re: Building procedure of krb5 is broken Message-ID: <20010221071133.B7576@spawn.nectar.com> References: <20010217190142A.matusita@jp.FreeBSD.org> <20010220184324P.matusita@jp.FreeBSD.org> <7m66i4kwx6.wl@waterblue.imgsrc.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <7m66i4kwx6.wl@waterblue.imgsrc.co.jp>; from kuriyama@imgsrc.co.jp on Wed, Feb 21, 2001 at 10:06:29PM +0900 X-Url: http://www.nectar.com/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 21, 2001 at 10:06:29PM +0900, Jun Kuriyama wrote: > At 20 Feb 2001 09:44:01 GMT, > Makoto MATSUSHITA wrote: > > It seems that add 'CFLAGS+=-I${KRB5OBJDIR}' to > > src/kerberos5/lib/libgssapi/Makefile is required to fix this, since > > krb5_err.h is not in ${KRB5DIR}/lib/krb5. > > In my environment, buildworld was finished with attached patch. I > don't know KRB4 should be defined in this file or not. But in > crypto/heimdal/kdc/headers.h, krb.h (this file is not exist in heimdal > distribution) is included if KRB4 is defined. > > So if MAKE_KERBEROS5=YES is set in /etc/make.conf, buildworld is > failed because krb.h is not found. Last I looked (before assar's import), MAKE_KERBEROS5=yes required that you also have MAKE_KERBEROS4=yes due to such dependencies. Cheers, -- Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 21 5:19:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from assaris.sics.se (assaris.sics.se [193.10.66.234]) by hub.freebsd.org (Postfix) with ESMTP id 332CA37B401; Wed, 21 Feb 2001 05:19:35 -0800 (PST) (envelope-from assar@assaris.sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.9.3) id OAA38184; Wed, 21 Feb 2001 14:19:30 +0100 (CET) (envelope-from assar) From: Assar Westerlund To: "Jacques A. Vidrine" Cc: Jun Kuriyama , Mark Murray , current@FreeBSD.org Subject: Re: Building procedure of krb5 is broken References: <20010217190142A.matusita@jp.FreeBSD.org> <20010220184324P.matusita@jp.FreeBSD.org> <7m66i4kwx6.wl@waterblue.imgsrc.co.jp> <20010221071133.B7576@spawn.nectar.com> From: Assar Westerlund Date: 21 Feb 2001 14:19:28 +0100 In-Reply-To: "Jacques A. Vidrine"'s message of "Wed, 21 Feb 2001 07:11:33 -0600" Message-ID: <5lelwsrx5r.fsf@assaris.sics.se> Lines: 12 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.6 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jacques A. Vidrine" writes: > On Wed, Feb 21, 2001 at 10:06:29PM +0900, Jun Kuriyama wrote: > > So if MAKE_KERBEROS5=YES is set in /etc/make.conf, buildworld is > > failed because krb.h is not found. > > Last I looked (before assar's import), MAKE_KERBEROS5=yes required > that you also have MAKE_KERBEROS4=yes due to such dependencies. Which is bogus. I think Jun Kuriyama's patch is correct and I'm trying it now, but buildworld takes a little while to complete :-) /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 21 5:25: 2 2001 Delivered-To: freebsd-current@freebsd.org Received: from white.imgsrc.co.jp (ns.imgsrc.co.jp [210.226.20.2]) by hub.freebsd.org (Postfix) with ESMTP id 6E64137B491; Wed, 21 Feb 2001 05:24:57 -0800 (PST) (envelope-from kuriyama@imgsrc.co.jp) Received: from waterblue.imgsrc.co.jp (waterblue.imgsrc.co.jp [210.226.20.160]) by white.imgsrc.co.jp (8.11.2/8.11.0) with ESMTP id f1LDOtT22575; Wed, 21 Feb 2001 22:24:56 +0900 (JST) Date: Wed, 21 Feb 2001 22:24:50 +0900 Message-ID: <7m4rxokw2l.wl@waterblue.imgsrc.co.jp> From: Jun Kuriyama To: Assar Westerlund Cc: "Jacques A. Vidrine" , Mark Murray , current@FreeBSD.org Subject: Re: Building procedure of krb5 is broken In-Reply-To: <5lelwsrx5r.fsf@assaris.sics.se> References: <20010217190142A.matusita@jp.FreeBSD.org> <20010220184324P.matusita@jp.FreeBSD.org> <7m66i4kwx6.wl@waterblue.imgsrc.co.jp> <20010221071133.B7576@spawn.nectar.com> <5lelwsrx5r.fsf@assaris.sics.se> User-Agent: Wanderlust/2.4.0 (Rio) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 14) (Cuyahoga Valley) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 21 Feb 2001 14:19:28 +0100, Assar Westerlund wrote: > Which is bogus. I think Jun Kuriyama's patch is correct and I'm > trying it now, but buildworld takes a little while to complete :-) Just FYI, I've tested buildworld with that patch in environments below. :-) (1) MAKE_KERBEROS4=YES (2) MAKE_KERBEROS4=YES and MAKE_KERBEROS5=YES (3) MAKE_KERBEROS5=YES (4) No MAKE_KERBEROS* -- Jun Kuriyama // IMG SRC, Inc. // FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 21 5:27:55 2001 Delivered-To: freebsd-current@freebsd.org Received: from assaris.sics.se (assaris.sics.se [193.10.66.234]) by hub.freebsd.org (Postfix) with ESMTP id D72A037B6CA; Wed, 21 Feb 2001 05:27:50 -0800 (PST) (envelope-from assar@assaris.sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.9.3) id OAA38228; Wed, 21 Feb 2001 14:27:46 +0100 (CET) (envelope-from assar) To: Jun Kuriyama Cc: "Jacques A. Vidrine" , Mark Murray , current@FreeBSD.org Subject: Re: Building procedure of krb5 is broken References: <20010217190142A.matusita@jp.FreeBSD.org> <20010220184324P.matusita@jp.FreeBSD.org> <7m66i4kwx6.wl@waterblue.imgsrc.co.jp> <20010221071133.B7576@spawn.nectar.com> <5lelwsrx5r.fsf@assaris.sics.se> <7m4rxokw2l.wl@waterblue.imgsrc.co.jp> From: Assar Westerlund Date: 21 Feb 2001 14:27:46 +0100 In-Reply-To: Jun Kuriyama's message of "Wed, 21 Feb 2001 22:24:50 +0900" Message-ID: <5lu25oqi7h.fsf@assaris.sics.se> Lines: 12 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.6 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jun Kuriyama writes: > Just FYI, I've tested buildworld with that patch in environments > below. :-) > > (1) MAKE_KERBEROS4=YES > (2) MAKE_KERBEROS4=YES and MAKE_KERBEROS5=YES > (3) MAKE_KERBEROS5=YES > (4) No MAKE_KERBEROS* Thanks for your testing. I've commited the fix. /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 21 5:45:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from updraft.jp.freebsd.org (updraft.jp.FreeBSD.ORG [210.157.158.42]) by hub.freebsd.org (Postfix) with ESMTP id 94C7B37B491 for ; Wed, 21 Feb 2001 05:45:42 -0800 (PST) (envelope-from matusita@jp.FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by updraft.jp.freebsd.org (8.11.2+3.4W/8.11.1) with ESMTP/inet id f1LDjcW82187 for ; Wed, 21 Feb 2001 22:45:39 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) In-Reply-To: <7m66i4kwx6.wl@waterblue.imgsrc.co.jp> References: <20010217190142A.matusita@jp.FreeBSD.org> <20010220184324P.matusita@jp.FreeBSD.org> <7m66i4kwx6.wl@waterblue.imgsrc.co.jp> X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V X-User-Agent: Mew/1.94.2 XEmacs/21.2 (Poseidon) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 13 From: Makoto MATSUSHITA To: current@freebsd.org Subject: Re: Building procedure of krb5 is broken Date: Wed, 21 Feb 2001 22:45:22 +0900 Message-Id: <20010221224522E.matusita@jp.FreeBSD.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG kuriyama> In my environment, buildworld was finished with attached kuriyama> patch. I don't know KRB4 should be defined in this file or kuriyama> not. Sorry I should say when building of krb5 is failed; make buildworld seems OK, but 'make release' will fail during 'release.2' target; there is no MAKE_KERBEROS* variable definition. Anyway, I'll wait until tomorrow's job starts at current.jp.FreeBSD.org :-) -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 21 5:48:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.icomtek.csir.co.za (zibbi.icomtek.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 73E1C37B401; Wed, 21 Feb 2001 05:48:32 -0800 (PST) (envelope-from jhay@zibbi.icomtek.csir.co.za) Received: (from jhay@localhost) by zibbi.icomtek.csir.co.za (8.11.1/8.11.1) id f1LDmIX17944; Wed, 21 Feb 2001 15:48:18 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200102211348.f1LDmIX17944@zibbi.icomtek.csir.co.za> Subject: Re: Building procedure of krb5 is broken In-Reply-To: <5lu25oqi7h.fsf@assaris.sics.se> from Assar Westerlund at "Feb 21, 2001 02:27:46 pm" To: assar@FreeBSD.ORG (Assar Westerlund) Date: Wed, 21 Feb 2001 15:48:17 +0200 (SAT) Cc: kuriyama@imgsrc.co.jp (Jun Kuriyama), n@nectar.com (Jacques A. Vidrine), markm@FreeBSD.ORG (Mark Murray), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Jun Kuriyama writes: > > Just FYI, I've tested buildworld with that patch in environments > > below. :-) > > > > (1) MAKE_KERBEROS4=YES > > (2) MAKE_KERBEROS4=YES and MAKE_KERBEROS5=YES > > (3) MAKE_KERBEROS5=YES > > (4) No MAKE_KERBEROS* > > Thanks for your testing. I've commited the fix. > Ahhhh, maybe this will also fix "make release". It has been dying in the kerberos area the last few days. John -- John Hay -- John.Hay@icomtek.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 21 9:39:21 2001 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 54B8737B503 for ; Wed, 21 Feb 2001 09:39:16 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f1LHdDD03948; Wed, 21 Feb 2001 09:39:13 -0800 (PST) Date: Wed, 21 Feb 2001 09:39:13 -0800 From: Alfred Perlstein To: "Daniel C. Sobral" Cc: Akinori MUSHA , current@FreeBSD.ORG Subject: Re: find(1) -regex/-iregex Message-ID: <20010221093913.J6641@fw.wintelcom.net> References: <8666i588p4.wl@archon.local.idaemons.org> <20010220132426.X6641@fw.wintelcom.net> <3A9337E0.A51A3E8B@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A9337E0.A51A3E8B@newsguy.com>; from dcs@newsguy.com on Wed, Feb 21, 2001 at 12:37:04PM +0900 X-all-your-base: are belong to us. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Daniel C. Sobral [010220 19:39] wrote: > Alfred Perlstein wrote: > > > > * Akinori MUSHA [010220 11:19] wrote: > > > Hi, > > > > > > I have implemented -regex and -iregex options for find(1): > > > > > > > Sounds good, just make sure the regex engine matches the one that > > the other find(1)'s use. > > It won't. GNU find certainly uses GNU regexp library, which has lots of > extra stuff. Naturally, our find will be using our library instead. > Nothing we can do about it. It is the way of the Gnu to extend > and embrace. Well a subset or superset is fine, as long as it's the same type of regex. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 21 13:56:27 2001 Delivered-To: freebsd-current@freebsd.org Received: from tao.org.uk (genesis.tao.org.uk [194.242.131.94]) by hub.freebsd.org (Postfix) with ESMTP id 9708737B491 for ; Wed, 21 Feb 2001 13:55:24 -0800 (PST) (envelope-from joe@tao.org.uk) Received: by tao.org.uk (Postfix, from userid 100) id A98E631B6; Wed, 21 Feb 2001 21:55:22 +0000 (GMT) Date: Wed, 21 Feb 2001 21:55:22 +0000 From: Josef Karthauser To: Kirk McKusick Cc: current@freebsd.org Subject: Problems syncing disks in recent -current (since 19th) Message-ID: <20010221215522.D2022@tao.org.uk> Mail-Followup-To: Josef Karthauser , Kirk McKusick , current@freebsd.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="jCrbxBqMcLqd4mOl" Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --jCrbxBqMcLqd4mOl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi Kirk, A number of us have problem reliably syncing disks with softupdates in recent -current from about the 19th. Is it possible that you broke something with your recent commit? Cheers, Joe --jCrbxBqMcLqd4mOl Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjqUOUkACgkQXVIcjOaxUBZ1KgCglRwbRAy80TPQGsrg8pW/B1OK CV8AnRp3DtPYPdLVgaZuSV5k1dq7Nbq6 =45kb -----END PGP SIGNATURE----- --jCrbxBqMcLqd4mOl-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 21 14:21:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from localhost.westmarsh.com (orion.westmarsh.com [193.195.76.57]) by hub.freebsd.org (Postfix) with ESMTP id 2041737B491 for ; Wed, 21 Feb 2001 14:21:06 -0800 (PST) (envelope-from pierre.dampure@westmarsh.com) Received: from westmarsh.com (mailgate.westmarsh.com [193.195.76.50]) (authenticated) by localhost.westmarsh.com (8.11.2/8.11.1) with ESMTP id f1LMKki24780; Wed, 21 Feb 2001 22:20:46 GMT (envelope-from pierre.dampure@westmarsh.com) Message-ID: <3A943F3D.FDF05029@westmarsh.com> Date: Wed, 21 Feb 2001 22:20:46 +0000 From: "Pierre Y. Dampure" X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Andrea Campi Cc: freebsd-current@freebsd.org Subject: Re: -CURRENT slowdown in last 2 weeks References: <20010220015012.B5116@webcom.it> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrea Campi wrote: > I am noticing a severe slowdown on my -CURRENT system. It actually started > after Feb [3-5] changes in intrupt handling, but I didn't really notice > until I run a make world (which I delayed doing because of, well you guess, > the libc breakage). When I say severe I mean make buildworld takes x3 longer. Hmmm. Buit world yesterday evening on a 733 VAIO, UDMA ATA drive, took around 1h15mn, which is fairly much what I would expect... U using SCSI? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 21 14:31:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from postoffice.aims.com.au (advanc2.lnk.telstra.net [139.130.119.73]) by hub.freebsd.org (Postfix) with ESMTP id 966A337B491 for ; Wed, 21 Feb 2001 14:31:17 -0800 (PST) (envelope-from chris@aims.com.au) Received: from postoffice.aims.com.au (nts-ts1.aims.private [192.168.10.2]) by postoffice.aims.com.au with ESMTP id JAA27915 for ; Thu, 22 Feb 2001 09:31:09 +1100 (EST) (envelope-from chris@aims.com.au) Received: from ntsts1 by aims.com.au with SMTP (MDaemon.v3.5.3.R) for ; Thu, 22 Feb 2001 09:30:23 +1100 Reply-To: From: "Chris Knight" To: Cc: Subject: RE: Problems syncing disks in recent -current (since 19th) Date: Thu, 22 Feb 2001 09:30:21 +1100 Message-ID: <01a601c09c55$e1238ad0$020aa8c0@aims.private> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <20010221215522.D2022@tao.org.uk> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Return-Path: chris@aims.com.au X-MDaemon-Deliver-To: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Howdy, I think this is unrelated. I'm getting the same thing happening on a system I built prior to Kirk's recent commit - I haven't yet had time to find the cause. Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au > -----Original Message----- > From: owner-freebsd-current@FreeBSD.ORG > [mailto:owner-freebsd-current@FreeBSD.ORG]On Behalf Of Josef > Karthauser > Sent: Thursday, 22 February 2001 8:55 > To: Kirk McKusick > Cc: current@FreeBSD.ORG > Subject: Problems syncing disks in recent -current (since 19th) > > > Hi Kirk, > > A number of us have problem reliably syncing disks with softupdates in > recent -current from about the 19th. Is it possible that you broke > something with your recent commit? > > Cheers, > Joe > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 21 15:17:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id C2BCF37B491 for ; Wed, 21 Feb 2001 15:17:50 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f1LNDGl66901; Wed, 21 Feb 2001 15:13:16 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010220015012.B5116@webcom.it> Date: Wed, 21 Feb 2001 15:15:03 -0800 (PST) From: John Baldwin To: Andrea Campi Subject: RE: -CURRENT slowdown in last 2 weeks Cc: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 20-Feb-01 Andrea Campi wrote: > I am noticing a severe slowdown on my -CURRENT system. It actually started > after Feb [3-5] changes in intrupt handling, but I didn't really notice > until I run a make world (which I delayed doing because of, well you guess, > the libc breakage). When I say severe I mean make buildworld takes x3 longer. Hmm, Feb 3-5 (looks). You mean the preemptive scheduling committed on Feb 1? Can you try updating to early this week to see if it goes away? -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 21 17:42:47 2001 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 81CB737B503 for ; Wed, 21 Feb 2001 17:42:40 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from daniel.sobral (p23-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.152]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id KAA03509 for ; Thu, 22 Feb 2001 10:42:39 +0900 (JST) Received: (from dcs@localhost) by daniel.sobral (8.9.3/8.9.3) id KAA71691 for current@freebsd.org; Thu, 22 Feb 2001 10:39:48 +0900 (JST) (envelope-from dcs) From: "Daniel C. Sobral" Message-Id: <200102220139.KAA71691@daniel.sobral> Subject: kernfs X-ELM-OSV: (Our standard violations) hdr-charset=ISO-8859-1 To: current@freebsd.org Date: Thu, 22 Feb 2001 10:39:47 +0900 (JST) Disclaimer: Klaatu Barada Nikto! X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems the error for kernfs is activating a couple of other warnings: WARNING: unknown option `KERNFS' removed from /usr/obj/home/src/sys/DCS/opt_dont use.h WARNING: option `FFS' moved from opt_ffs.h to opt_dontuse.h WARNING: unknown option `FFS_ROOT' removed from /usr/obj/home/src/sys/DCS/opt_ff s.h -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@there.is.no.bsdconspiracy.net You'll never see all the places, or read all the books, but fortunately, they're not all recommended. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 21 20:52:38 2001 Delivered-To: freebsd-current@freebsd.org Received: from rina.r.dl.itc.u-tokyo.ac.jp (cvsup2.r.dl.itc.u-tokyo.ac.jp [133.11.199.247]) by hub.freebsd.org (Postfix) with ESMTP id 5691B37B491; Wed, 21 Feb 2001 20:52:35 -0800 (PST) (envelope-from tanimura@r.dl.itc.u-tokyo.ac.jp) Received: from rina.r.dl.itc.u-tokyo.ac.jp (localhost [127.0.0.1]) by rina.r.dl.itc.u-tokyo.ac.jp (8.11.1+3.4W/3.7W-rina.r-0.1-11.01.2000) with ESMTP id f1M4qSg63873; Thu, 22 Feb 2001 13:52:29 +0900 (JST) Date: Thu, 22 Feb 2001 13:52:28 +0900 Message-ID: From: Seigo Tanimura To: "Cameron Grant" , John Baldwin Subject: MP-safe midi(4) and sequencer callout priority Cc: Seigo Tanimura , current@FreeBSD.org User-Agent: Wanderlust/1.1.1 (Purple Rain) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 14) (Cuyahoga Valley) (i386--freebsd) Organization: Digital Library Research Division, Information Techinology Centre, The University of Tokyo MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The patch at http://people.FreeBSD.org/~tanimura/patches/midimutex.diff.gz makes midi(4) MP-safe. With this patch, my kernel with WITNESS and INVARIANTS plays my favorite midi tunes just fine, except that the callout used by the midi sequencer gets delayed under a heavy load. As the sequencer uses callout in order to wait until the next midi message is ready to be transmitted, the callout should run at PI_AV so that a tune will not sound messy. John, have you got any plan to modify the priority of a callout? Cameron, as pcm(4) interacts with few of the other subsystems in the kernel like midi(4), why don't you start making pcm(4) MP-safe? Multimedia devices should benefit very much from kernel execution in parallel. The only one thing to note is to not access a device in parallel to mess it up. We have to add a mutex to a device and share the mutex between the pcm part and the midi part of the driver. Could you please let me know when pcm(4) gets MP-safe, and we will see how we can share device mutexes between pcm(4) and midi(4). -- Seigo Tanimura To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 21 22: 0:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from white.imgsrc.co.jp (ns.imgsrc.co.jp [210.226.20.2]) by hub.freebsd.org (Postfix) with ESMTP id DDF2537B491 for ; Wed, 21 Feb 2001 22:00:28 -0800 (PST) (envelope-from kuriyama@imgsrc.co.jp) Received: from waterblue.imgsrc.co.jp (waterblue.imgsrc.co.jp [210.226.20.160]) by white.imgsrc.co.jp (8.11.2/8.11.0) with ESMTP id f1M60RT31904 for ; Thu, 22 Feb 2001 15:00:27 +0900 (JST) Date: Thu, 22 Feb 2001 15:00:23 +0900 Message-ID: <7mofvvjlzc.wl@waterblue.imgsrc.co.jp> From: Jun Kuriyama To: current@FreeBSD.ORG Subject: Re: Building procedure of krb5 is broken In-Reply-To: <20010221224522E.matusita@jp.FreeBSD.org> References: <20010217190142A.matusita@jp.FreeBSD.org> <20010220184324P.matusita@jp.FreeBSD.org> <7m66i4kwx6.wl@waterblue.imgsrc.co.jp> <20010221224522E.matusita@jp.FreeBSD.org> User-Agent: Wanderlust/2.4.0 (Rio) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 14) (Cuyahoga Valley) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 21 Feb 2001 13:45:55 GMT, Makoto MATSUSHITA wrote: > Anyway, I'll wait until tomorrow's job starts at current.jp.FreeBSD.org :-) Hmmm, today's "make release" at current.jp failed. It seems a patch from matusita-san is required... o Last 50 lines of today's log ftp://current.jp.FreeBSD.org/pub/FreeBSD/snapshots/i386/5.0-CURRENT-20010222-JPSNAP.log o Full of today's log ftp://current.jp.FreeBSD.org/pub/FreeBSD/snapshots/i386/log/5.0-CURRENT-20010222-JPSNAP.log.gz -- Jun Kuriyama // IMG SRC, Inc. // FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 21 23: 6:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from localhost.westmarsh.com (orion.westmarsh.com [193.195.76.57]) by hub.freebsd.org (Postfix) with ESMTP id EB3EF37B65D for ; Wed, 21 Feb 2001 23:06:30 -0800 (PST) (envelope-from pierre.dampure@westmarsh.com) Received: from westmarsh.com (mailgate.westmarsh.com [193.195.76.50]) (authenticated) by localhost.westmarsh.com (8.11.2/8.11.1) with ESMTP id f1M768i28325; Thu, 22 Feb 2001 07:06:08 GMT (envelope-from pierre.dampure@westmarsh.com) Message-ID: <3A94BA60.34F2B9A@westmarsh.com> Date: Thu, 22 Feb 2001 07:06:08 +0000 From: "Pierre Y. Dampure" X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Andrea Campi Cc: freebsd-current@freebsd.org Subject: Re: -CURRENT slowdown in last 2 weeks References: <20010220015012.B5116@webcom.it> <3A943F3D.FDF05029@westmarsh.com> <20010221233143.B728@webcom.it> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrea Campi wrote: > Nope, UDMA33 (IBM-DARA-20600 on IBM Thinkpad). > > Question: you built a world yesterday, but what world did you have BEFORE? I > mean, what matters is the kernel/world which was running while you were > compiling, was that recent (< 15 days old)? Are you seeing any lock reversal > message? > The previous world and kernel where from that same day (I had been playing around with user.h and kmod.mk and rebuilt to make sure everything was still okay). I did not see any lock reversal messages. My config is pretty standard, let me know if you want a peek (the only "non-standard" bit is the fact that I'm running newcard, I doubt this would matter in this case). Best Regards, PYD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 2:20:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id A031F37B491 for ; Thu, 22 Feb 2001 02:20:33 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 22 Feb 2001 10:20:33 +0000 (GMT) Date: Thu, 22 Feb 2001 10:20:32 +0000 From: David Malone To: "Daniel C. Sobral" Cc: current@freebsd.org Subject: Re: kernfs Message-ID: <20010222102032.A83571@walton.maths.tcd.ie> References: <200102220139.KAA71691@daniel.sobral> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200102220139.KAA71691@daniel.sobral>; from dcs@newsguy.com on Thu, Feb 22, 2001 at 10:39:47AM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 22, 2001 at 10:39:47AM +0900, Daniel C. Sobral wrote: > It seems the error for kernfs is activating a couple of other warnings: I think Des retired kernfs in -current in a commit on 2000/12/28. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 3:25:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from blizzard.sabbo.net (smtp.sabbo.net [193.193.218.18]) by hub.freebsd.org (Postfix) with ESMTP id 8E56B37B491; Thu, 22 Feb 2001 03:20:53 -0800 (PST) (envelope-from sobomax@FreeBSD.org) Received: from vic.sabbo.net (root@vic.sabbo.net [193.193.218.112]) by blizzard.sabbo.net (8.10.1/8.10.1) with ESMTP id f1MAW5f11773; Thu, 22 Feb 2001 12:32:45 +0200 Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vic.sabbo.net (8.11.2/8.11.2) with ESMTP id f1MB8bS45636; Thu, 22 Feb 2001 13:08:37 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Message-ID: <3A94F335.6C858C2@FreeBSD.org> Date: Thu, 22 Feb 2001 13:08:37 +0200 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Dag-Erling Smorgrav Cc: current@FreeBSD.org, jhb@FreeBSD.org, "Alexander N. Kabaev" Subject: A possible bug in the interrupt thread preemption code [Was: Kernel panic in irq14: ata0] References: <200102201821.TAA76890@freebsd.dk> <3A92B63B.B308C616@FreeBSD.org> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav wrote: > Maxim Sobolev writes: > > It's not an ata specific problem, but rather a problem of all ISA > > devices (I have an ISA based ata controller). > > I don't think it has anything to do with ISA. I've had similar > problems on a PCI-only system (actually, PCI+EISA motherboard with no > EISA cards) with no ATA devices (disks, CD-ROM and streamer are all > SCSI). > > Considering that backing out rev 1.14 of ithread.c eliminates the > panics, and that that revision is supposed to enable interrupt thread > preemption, and that the crashed kernels show signs of stack smashing, > I'd say the cause is probably a bug in the preemption code. Update: the bug is still here, as of -current from 22 Feb. Hovewer, this time it even doesn't let to boot into single-user with following panic message: kernel trap 12 with interrupts disabled panic: mutex sched lock recursed at ../../kern/kern_synch.c:872 syncing disks... -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 4:21:20 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 87F0037B401; Thu, 22 Feb 2001 04:21:15 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f1MCJ2l86660; Thu, 22 Feb 2001 04:19:06 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3A94F335.6C858C2@FreeBSD.org> Date: Thu, 22 Feb 2001 04:20:56 -0800 (PST) From: John Baldwin To: Maxim Sobolev Subject: RE: A possible bug in the interrupt thread preemption code [Was: Cc: "Alexander N. Kabaev" , current@FreeBSD.org, Dag-Erling Smorgrav Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22-Feb-01 Maxim Sobolev wrote: > Dag-Erling Smorgrav wrote: > >> Maxim Sobolev writes: >> > It's not an ata specific problem, but rather a problem of all ISA >> > devices (I have an ISA based ata controller). >> >> I don't think it has anything to do with ISA. I've had similar >> problems on a PCI-only system (actually, PCI+EISA motherboard with no >> EISA cards) with no ATA devices (disks, CD-ROM and streamer are all >> SCSI). >> >> Considering that backing out rev 1.14 of ithread.c eliminates the >> panics, and that that revision is supposed to enable interrupt thread >> preemption, and that the crashed kernels show signs of stack smashing, >> I'd say the cause is probably a bug in the preemption code. > > Update: the bug is still here, as of -current from 22 Feb. Hovewer, this time > it even doesn't let to boot into single-user with following panic message: > kernel trap 12 with interrupts disabled > panic: mutex sched lock recursed at ../../kern/kern_synch.c:872 Errrr. That would be something that is leaking sched_lock. Hmm... Got a backtrace? What is really annoying is that preemption has been in the kernel since Feb 1. I just accidentally turned it off in the ithread code reorganization and then turned it back on. It was off for a few hours after only being on for 2 weeks, and now everyone magically has problems. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 4:39:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id BBDBA37B4EC; Thu, 22 Feb 2001 04:39:27 -0800 (PST) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id NAA44088; Thu, 22 Feb 2001 13:39:26 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: John Baldwin Cc: Maxim Sobolev , "Alexander N. Kabaev" , current@FreeBSD.org Subject: Re: A possible bug in the interrupt thread preemption code [Was: References: From: Dag-Erling Smorgrav Date: 22 Feb 2001 13:39:26 +0100 In-Reply-To: John Baldwin's message of "Thu, 22 Feb 2001 04:20:56 -0800 (PST)" Message-ID: Lines: 109 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Baldwin writes: > On 22-Feb-01 Maxim Sobolev wrote: > > Dag-Erling Smorgrav wrote: > > > >> Maxim Sobolev writes: > >> > It's not an ata specific problem, but rather a problem of all ISA > >> > devices (I have an ISA based ata controller). > >> > >> I don't think it has anything to do with ISA. I've had similar > >> problems on a PCI-only system (actually, PCI+EISA motherboard with no > >> EISA cards) with no ATA devices (disks, CD-ROM and streamer are all > >> SCSI). > >> > >> Considering that backing out rev 1.14 of ithread.c eliminates the > >> panics, and that that revision is supposed to enable interrupt thread > >> preemption, and that the crashed kernels show signs of stack smashing, > >> I'd say the cause is probably a bug in the preemption code. > > > > Update: the bug is still here, as of -current from 22 Feb. Hovewer, this time > > it even doesn't let to boot into single-user with following panic message: > > kernel trap 12 with interrupts disabled > > panic: mutex sched lock recursed at ../../kern/kern_synch.c:872 > > Errrr. That would be something that is leaking sched_lock. Hmm... I have another sched_lock-related problem which showed up over the weekend. Starting StarOffice 5.2 invariably triggers the following panic: root@aes /var/crash# gdb -k sGNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd". (kgdb) source ~des/kgdb (kgdb) kernel 0 IdlePTD 3526656 initial pcb at 2cb980 panicstr: from debugger panic messages: --- panic: mutex sched lock not owned at ../../posix4/ksched.c:215 panic: from debugger Uptime: 3m37s dumping to dev ad0b, offset 262528 dump ata0: resetting devices .. done 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 --- #0 dumpsys () at ../../kern/kern_shutdown.c:476 476 if (dumping++) { (kgdb) where #0 dumpsys () at ../../kern/kern_shutdown.c:476 #1 0xc0187a04 in boot (howto=260) at ../../kern/kern_shutdown.c:319 #2 0xc0187dd9 in panic (fmt=0xc02521b4 "from debugger") at ../../kern/kern_shutdown.c:569 #3 0xc011cdad in db_panic (addr=-1071459127, have_addr=0, count=-1, modif=0xc879cd9c "") at ../../ddb/db_command.c:433 #4 0xc011cd4b in db_command (last_cmdp=0xc0285420, cmd_table=0xc0285280, aux_cmd_tablep=0xc02b68bc) at ../../ddb/db_command.c:333 #5 0xc011ce12 in db_command_loop () at ../../ddb/db_command.c:455 #6 0xc011f07f in db_trap (type=3, code=0) at ../../ddb/db_trap.c:71 #7 0xc022d258 in kdb_trap (type=3, code=0, regs=0xc879ce9c) at ../../i386/i386/db_interface.c:164 #8 0xc023a098 in trap (frame={tf_fs = -1060962280, tf_es = -932118512, tf_ds = -1060962288, tf_edi = -1071197888, tf_esi = 256, tf_ebp = -931541272, tf_isp = -931541304, tf_ebx = 514, tf_edx = -1071149169, tf_ecx = -1070757120, tf_eax = 18, tf_trapno = 3, tf_err = 0, tf_eip = -1071459127, tf_cs = 8, tf_eflags = 70, tf_esp = -1071149185, tf_ss = -1071240285}) at ../../i386/i386/trap.c:615 #9 0xc022d4c9 in Debugger (msg=0xc0262ba3 "panic") at machine/cpufunc.h:60 #10 0xc0187dd0 in panic (fmt=0xc0261a48 "mutex %s not owned at %s:%d") at ../../kern/kern_shutdown.c:567 #11 0xc0180c89 in _mtx_assert (m=0xc02e3e20, what=1, file=0xc026d140 "../../posix4/ksched.c", line=215) ---Type to continue, or q to quit--- at ../../kern/kern_mutex.c:611 #12 0xc01f0d51 in ksched_yield (ret=0xc8712f24, ksched=0xc0a97660) at ../../posix4/ksched.c:215 #13 0xc01f100b in sched_yield (p=0xc8712dc0, uap=0xc879cf80) at ../../posix4/p1003_1b.c:225 #14 0xc023b239 in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = -1077939044, tf_esi = 706867048, tf_ebp = -1077939116, tf_isp = -931541036, tf_ebx = 714966384, tf_edx = 1, tf_ecx = 134979841, tf_eax = 158, tf_trapno = 22, tf_err = 2, tf_eip = 717073383, tf_cs = 31, tf_eflags = 514, tf_esp = -1077939144, tf_ss = 47}) at ../../i386/i386/trap.c:1191 #15 0xc022dbe3 in Xint0x80_syscall () #16 0x2a182a9e in ?? () #17 0x2a18a328 in ?? () #18 0x2a057f6b in ?? () #19 0x2a057eb5 in ?? () #20 0x28f5e2a9 in ?? () #21 0x28191db5 in ?? () #22 0x80513a3 in ?? () #23 0x28f55eab in ?? () #24 0x80512da in ?? () #25 0x2a059cf1 in ?? () #26 0x2a181e35 in ?? () ---Type to continue, or q to quit--- #27 0x2ab551eb in ?? () (kgdb) DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 4:46:27 2001 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 5F6B137B503 for ; Thu, 22 Feb 2001 04:46:24 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p57-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.122]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id VAA08888; Thu, 22 Feb 2001 21:46:14 +0900 (JST) Message-ID: <3A95096E.9511A7A5@newsguy.com> Date: Thu, 22 Feb 2001 21:43:26 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: David Malone Cc: current@freebsd.org Subject: Re: kernfs References: <200102220139.KAA71691@daniel.sobral> <20010222102032.A83571@walton.maths.tcd.ie> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Malone wrote: > > On Thu, Feb 22, 2001 at 10:39:47AM +0900, Daniel C. Sobral wrote: > > It seems the error for kernfs is activating a couple of other warnings: > > I think Des retired kernfs in -current in a commit on 2000/12/28. Let me follow up on this. Kernfs is not actually the guilty party, but the problem was _not_ the kernfs warning. The problem, as I saw it, was the two following warnings (ffs and ffs_root). Alas, the ffs warning is correct but happens only once, so it seems that the guilty one was ffs. To be more precise, it seems that when the ffs warning gets activated, the ffs_root warning also gets shown. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@the.fashionable.bsdconspiracy.net "Too bad sentience isn't a marketable commodity." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 5:21:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from webcom.it (brian.inet.it [213.92.4.195]) by hub.freebsd.org (Postfix) with SMTP id 7136037B491 for ; Thu, 22 Feb 2001 05:21:49 -0800 (PST) (envelope-from andrea@webcom.it) Received: (qmail 15975 invoked by uid 1000); 21 Feb 2001 22:31:54 -0000 Date: Wed, 21 Feb 2001 23:31:50 +0100 From: Andrea Campi To: "Pierre Y. Dampure" Cc: freebsd-current@freebsd.org Subject: Re: -CURRENT slowdown in last 2 weeks Message-ID: <20010221233143.B728@webcom.it> References: <20010220015012.B5116@webcom.it> <3A943F3D.FDF05029@westmarsh.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A943F3D.FDF05029@westmarsh.com>; from pierre.dampure@westmarsh.com on Wed, Feb 21, 2001 at 10:20:46PM +0000 X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 21, 2001 at 10:20:46PM +0000, Pierre Y. Dampure wrote: > Andrea Campi wrote: > > > I am noticing a severe slowdown on my -CURRENT system. It actually started > > after Feb [3-5] changes in intrupt handling, but I didn't really notice > > until I run a make world (which I delayed doing because of, well you guess, > > the libc breakage). When I say severe I mean make buildworld takes x3 longer. > > Hmmm. Buit world yesterday evening on a 733 VAIO, UDMA ATA drive, took around > 1h15mn, which is fairly much what I would expect... U using SCSI? Nope, UDMA33 (IBM-DARA-20600 on IBM Thinkpad). Question: you built a world yesterday, but what world did you have BEFORE? I mean, what matters is the kernel/world which was running while you were compiling, was that recent (< 15 days old)? Are you seeing any lock reversal message? Thanks anyway, bye, Andrea -- Reboot America. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 5:22: 2 2001 Delivered-To: freebsd-current@freebsd.org Received: from webcom.it (brian.inet.it [213.92.4.195]) by hub.freebsd.org (Postfix) with SMTP id 71BF937B4EC for ; Thu, 22 Feb 2001 05:21:49 -0800 (PST) (envelope-from andrea@webcom.it) Received: (qmail 18056 invoked by uid 1000); 22 Feb 2001 07:12:33 -0000 Date: Thu, 22 Feb 2001 08:12:33 +0100 From: Andrea Campi To: John Baldwin Cc: freebsd-current@FreeBSD.org Subject: Re: -CURRENT slowdown in last 2 weeks Message-ID: <20010222081232.A7793@webcom.it> References: <20010220015012.B5116@webcom.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.org on Wed, Feb 21, 2001 at 03:15:03PM -0800 X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Hmm, Feb 3-5 (looks). > > You mean the preemptive scheduling committed on Feb 1? Can you try updating > to early this week to see if it goes away? Hi John, every "recent" version I tried resulted in a slowdown so I didn't recompile very often; until tonight, I was still runninng a kernel from 20010214. Tonight I created a new kernel but I finally figured out I should take out most debugging options: options DDB # options WITNESS # options WITNESS_DDB # options MUTEX_DEBUG # options INVARIANT_SUPPORT # options INVARIANTS and now performance is very good, event with: kern.random.sys.harvest_ethernet: 1 kern.random.sys.harvest_point_to_point: 0 kern.random.sys.harvest_interrupt: 1 Later tonight (my locale) I saw a few other commits to ithreads and such, exp. your commit which should fix my issue with pccard (thanks a lot for that!), so later a will update again and start building kernels adding back the debugging options one at a time. I'll post the result. Bye, Andrea -- Actually, Microsoft is sort of a mixture between the Borg and the Ferengi. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 5:38: 0 2001 Delivered-To: freebsd-current@freebsd.org Received: from blizzard.sabbo.net (blizzard.sabbo.net [193.193.218.18]) by hub.freebsd.org (Postfix) with ESMTP id 819F737B4EC; Thu, 22 Feb 2001 05:36:38 -0800 (PST) (envelope-from sobomax@FreeBSD.org) Received: from vic.sabbo.net (root@vic.sabbo.net [193.193.218.112]) by blizzard.sabbo.net (8.10.1/8.10.1) with ESMTP id f1MDXhf15268; Thu, 22 Feb 2001 15:33:58 +0200 Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vic.sabbo.net (8.11.2/8.11.2) with ESMTP id f1MDXWS47545; Thu, 22 Feb 2001 15:33:32 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Message-ID: <3A95152B.5672D46E@FreeBSD.org> Date: Thu, 22 Feb 2001 15:33:31 +0200 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: John Baldwin Cc: "Alexander N. Kabaev" , current@FreeBSD.org, Dag-Erling Smorgrav Subject: Re: A possible bug in the interrupt thread preemption code [Was: References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Baldwin wrote: > On 22-Feb-01 Maxim Sobolev wrote: > > Dag-Erling Smorgrav wrote: > > > >> Maxim Sobolev writes: > >> > It's not an ata specific problem, but rather a problem of all ISA > >> > devices (I have an ISA based ata controller). > >> > >> I don't think it has anything to do with ISA. I've had similar > >> problems on a PCI-only system (actually, PCI+EISA motherboard with no > >> EISA cards) with no ATA devices (disks, CD-ROM and streamer are all > >> SCSI). > >> > >> Considering that backing out rev 1.14 of ithread.c eliminates the > >> panics, and that that revision is supposed to enable interrupt thread > >> preemption, and that the crashed kernels show signs of stack smashing, > >> I'd say the cause is probably a bug in the preemption code. > > > > Update: the bug is still here, as of -current from 22 Feb. Hovewer, this time > > it even doesn't let to boot into single-user with following panic message: > > kernel trap 12 with interrupts disabled > > panic: mutex sched lock recursed at ../../kern/kern_synch.c:872 > > Errrr. That would be something that is leaking sched_lock. Hmm... > > Got a backtrace? What is really annoying is that preemption has been in the > kernel since Feb 1. I just accidentally turned it off in the ithread code > reorganization and then turned it back on. It was off for a few hours after > only being on for 2 weeks, and now everyone magically has problems. Here it is (from DDB): panic(c027de93,c0297409,c027f878,368,80286) _mtx_assert(c02ea000,9,c027f878,368,80286) mi_switch(c32c5da0,3,c02cea44,c357be98) ithread_schedule(c0747c00,1) sched_ithd(e) Xresume14() --- interrupt, eip = 0xc025b60f, esp = 0x80296, ebp = 0xc357bf08 --- trap(18, 10, 10,c01597b6,20) calltrap() --- trap 0x9, eip = 0xc025a5de, esp = 0xc357bf50, ebp = 0xc357bf64 --- sw1b(c0146cbc,c0146cbc,c32c5da0,c357bf94) ithread_loop(c0747c00,c357bfa8) fork_exit(c0146cbc,c0747c00,c357bfa8) fork_trampoline() -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 5:45:20 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 7195837B401; Thu, 22 Feb 2001 05:45:16 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f1MDh6l88543; Thu, 22 Feb 2001 05:43:06 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3A95152B.5672D46E@FreeBSD.org> Date: Thu, 22 Feb 2001 05:45:02 -0800 (PST) From: John Baldwin To: Maxim Sobolev Subject: Re: A possible bug in the interrupt thread preemption code [Was: Cc: Dag-Erling Smorgrav , current@FreeBSD.org, "Alexander N. Kabaev" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22-Feb-01 Maxim Sobolev wrote: > John Baldwin wrote: > >> On 22-Feb-01 Maxim Sobolev wrote: >> > Dag-Erling Smorgrav wrote: >> > >> >> Maxim Sobolev writes: >> >> > It's not an ata specific problem, but rather a problem of all ISA >> >> > devices (I have an ISA based ata controller). >> >> >> >> I don't think it has anything to do with ISA. I've had similar >> >> problems on a PCI-only system (actually, PCI+EISA motherboard with no >> >> EISA cards) with no ATA devices (disks, CD-ROM and streamer are all >> >> SCSI). >> >> >> >> Considering that backing out rev 1.14 of ithread.c eliminates the >> >> panics, and that that revision is supposed to enable interrupt thread >> >> preemption, and that the crashed kernels show signs of stack smashing, >> >> I'd say the cause is probably a bug in the preemption code. >> > >> > Update: the bug is still here, as of -current from 22 Feb. Hovewer, this >> > time >> > it even doesn't let to boot into single-user with following panic message: >> > kernel trap 12 with interrupts disabled >> > panic: mutex sched lock recursed at ../../kern/kern_synch.c:872 >> >> Errrr. That would be something that is leaking sched_lock. Hmm... >> >> Got a backtrace? What is really annoying is that preemption has been in the >> kernel since Feb 1. I just accidentally turned it off in the ithread code >> reorganization and then turned it back on. It was off for a few hours after >> only being on for 2 weeks, and now everyone magically has problems. > > Here it is (from DDB): > panic(c027de93,c0297409,c027f878,368,80286) > _mtx_assert(c02ea000,9,c027f878,368,80286) > mi_switch(c32c5da0,3,c02cea44,c357be98) > ithread_schedule(c0747c00,1) > sched_ithd(e) > Xresume14() > --- interrupt, eip = 0xc025b60f, esp = 0x80296, ebp = 0xc357bf08 --- > trap(18, 10, 10,c01597b6,20) > calltrap() > --- trap 0x9, eip = 0xc025a5de, esp = 0xc357bf50, ebp = 0xc357bf64 --- > sw1b(c0146cbc,c0146cbc,c32c5da0,c357bf94) > ithread_loop(c0747c00,c357bfa8) > fork_exit(c0146cbc,c0747c00,c357bfa8) > fork_trampoline() *sigh* This is why enabling interrupts in trap() is such a bad idea. If we get a trap in the scheduler, then lots of bad crap starts to happen because we can get an interrupt while we are in a trap. :( Can you compile your kernel with INVARIANTS on though, as I think the kernel should've panic'd earlier if it is doing what I think it is doing. Also, if you are feeling industrious, edit sys/i386/i386/trap.c and comment out the enable_intr() call near the beginning of the trap() function right after the printf for 'kernel trap %d with interrupts disabled'. > -Maxim -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 5:45:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id D9D6F37B401; Thu, 22 Feb 2001 05:45:47 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f1MDh5l88535; Thu, 22 Feb 2001 05:43:05 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 22 Feb 2001 05:45:00 -0800 (PST) From: John Baldwin To: Dag-Erling Smorgrav Subject: Re: A possible bug in the interrupt thread preemption code [Was: Cc: current@FreeBSD.org, "Alexander N. Kabaev" , Maxim Sobolev Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22-Feb-01 Dag-Erling Smorgrav wrote: > John Baldwin writes: >> On 22-Feb-01 Maxim Sobolev wrote: >> > Dag-Erling Smorgrav wrote: >> > >> >> Maxim Sobolev writes: >> >> > It's not an ata specific problem, but rather a problem of all ISA >> >> > devices (I have an ISA based ata controller). >> >> >> >> I don't think it has anything to do with ISA. I've had similar >> >> problems on a PCI-only system (actually, PCI+EISA motherboard with no >> >> EISA cards) with no ATA devices (disks, CD-ROM and streamer are all >> >> SCSI). >> >> >> >> Considering that backing out rev 1.14 of ithread.c eliminates the >> >> panics, and that that revision is supposed to enable interrupt thread >> >> preemption, and that the crashed kernels show signs of stack smashing, >> >> I'd say the cause is probably a bug in the preemption code. >> > >> > Update: the bug is still here, as of -current from 22 Feb. Hovewer, this >> > time >> > it even doesn't let to boot into single-user with following panic message: >> > kernel trap 12 with interrupts disabled >> > panic: mutex sched lock recursed at ../../kern/kern_synch.c:872 >> >> Errrr. That would be something that is leaking sched_lock. Hmm... > > I have another sched_lock-related problem which showed up over the > weekend. Starting StarOffice 5.2 invariably triggers the following > panic: > > root@aes /var/crash# gdb -k > sGNU gdb 4.18 > Copyright 1998 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "i386-unknown-freebsd". > (kgdb) source ~des/kgdb > (kgdb) kernel 0 > IdlePTD 3526656 > initial pcb at 2cb980 > panicstr: from debugger > panic messages: > --- > panic: mutex sched lock not owned at ../../posix4/ksched.c:215 Easy enough. It seems I missed adding sched_lock around a need_resched(). I'll fix in a second.. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 5:47:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id A943F37B65D for ; Thu, 22 Feb 2001 05:47:47 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f1MDh6l88539; Thu, 22 Feb 2001 05:43:06 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010222081232.A7793@webcom.it> Date: Thu, 22 Feb 2001 05:45:02 -0800 (PST) From: John Baldwin To: Andrea Campi Subject: Re: -CURRENT slowdown in last 2 weeks Cc: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22-Feb-01 Andrea Campi wrote: >> >> Hmm, Feb 3-5 (looks). >> >> You mean the preemptive scheduling committed on Feb 1? Can you try updating >> to early this week to see if it goes away? > > Hi John, > > every "recent" version I tried resulted in a slowdown so I didn't recompile > very > often; until tonight, I was still runninng a kernel from 20010214. > Tonight I created a new kernel but I finally figured out I should take out > most > debugging options: > > options DDB ># options WITNESS ># options WITNESS_DDB ># options MUTEX_DEBUG ># options INVARIANT_SUPPORT ># options INVARIANTS Oh goodness, don't use MUTEX_DEBUG, that is the killer. You want WITNESS and INVARIANTS back on though. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 5:58:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from blizzard.sabbo.net (pop3.sabbo.net [193.193.218.18]) by hub.freebsd.org (Postfix) with ESMTP id B486037B491; Thu, 22 Feb 2001 05:57:28 -0800 (PST) (envelope-from sobomax@FreeBSD.org) Received: from vic.sabbo.net (root@vic.sabbo.net [193.193.218.112]) by blizzard.sabbo.net (8.10.1/8.10.1) with ESMTP id f1MDshf15807; Thu, 22 Feb 2001 15:54:44 +0200 Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vic.sabbo.net (8.11.2/8.11.2) with ESMTP id f1MDslS47643; Thu, 22 Feb 2001 15:54:47 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Message-ID: <3A951A25.953E2988@FreeBSD.org> Date: Thu, 22 Feb 2001 15:54:46 +0200 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: John Baldwin Cc: Dag-Erling Smorgrav , current@FreeBSD.org, "Alexander N. Kabaev" Subject: Re: A possible bug in the interrupt thread preemption code [Was: References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Baldwin wrote: > On 22-Feb-01 Maxim Sobolev wrote: > > John Baldwin wrote: > > > >> On 22-Feb-01 Maxim Sobolev wrote: > >> > Dag-Erling Smorgrav wrote: > >> > > >> >> Maxim Sobolev writes: > >> >> > It's not an ata specific problem, but rather a problem of all ISA > >> >> > devices (I have an ISA based ata controller). > >> >> > >> >> I don't think it has anything to do with ISA. I've had similar > >> >> problems on a PCI-only system (actually, PCI+EISA motherboard with no > >> >> EISA cards) with no ATA devices (disks, CD-ROM and streamer are all > >> >> SCSI). > >> >> > >> >> Considering that backing out rev 1.14 of ithread.c eliminates the > >> >> panics, and that that revision is supposed to enable interrupt thread > >> >> preemption, and that the crashed kernels show signs of stack smashing, > >> >> I'd say the cause is probably a bug in the preemption code. > >> > > >> > Update: the bug is still here, as of -current from 22 Feb. Hovewer, this > >> > time > >> > it even doesn't let to boot into single-user with following panic message: > >> > kernel trap 12 with interrupts disabled > >> > panic: mutex sched lock recursed at ../../kern/kern_synch.c:872 > >> > >> Errrr. That would be something that is leaking sched_lock. Hmm... > >> > >> Got a backtrace? What is really annoying is that preemption has been in the > >> kernel since Feb 1. I just accidentally turned it off in the ithread code > >> reorganization and then turned it back on. It was off for a few hours after > >> only being on for 2 weeks, and now everyone magically has problems. > > > > Here it is (from DDB): > > panic(c027de93,c0297409,c027f878,368,80286) > > _mtx_assert(c02ea000,9,c027f878,368,80286) > > mi_switch(c32c5da0,3,c02cea44,c357be98) > > ithread_schedule(c0747c00,1) > > sched_ithd(e) > > Xresume14() > > --- interrupt, eip = 0xc025b60f, esp = 0x80296, ebp = 0xc357bf08 --- > > trap(18, 10, 10,c01597b6,20) > > calltrap() > > --- trap 0x9, eip = 0xc025a5de, esp = 0xc357bf50, ebp = 0xc357bf64 --- > > sw1b(c0146cbc,c0146cbc,c32c5da0,c357bf94) > > ithread_loop(c0747c00,c357bfa8) > > fork_exit(c0146cbc,c0747c00,c357bfa8) > > fork_trampoline() > > *sigh* This is why enabling interrupts in trap() is such a bad idea. If we > get a trap in the scheduler, then lots of bad crap starts to happen because we > can get an interrupt while we are in a trap. :( Can you compile your kernel with > INVARIANTS on though, as I think the kernel should've panic'd earlier if it is > doing what I think it is doing. It's already have INVARIANTS, MUTEX_DEBUG, WITNESS and WITNESS_DDB. > Also, if you are feeling industrious, edit > sys/i386/i386/trap.c and comment out the enable_intr() call near the beginning > of the trap() function right after the printf for 'kernel trap %d with > interrupts disabled'. Ok, I'll try so. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 6:18:42 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id A31D537B6B0 for ; Thu, 22 Feb 2001 06:18:30 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f1MEGKl89298 for ; Thu, 22 Feb 2001 06:16:20 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Thu, 22 Feb 2001 06:18:16 -0800 (PST) From: John Baldwin To: current@FreeBSD.org Subject: HEADSUP: please don't use MUTEX_DEBUG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, just to formally state this in case people have missed all the informal announcements: Please use the following to help with debugging in -current: options DDB options INVARIANTS options WITNESS Please do _not_ use the following: options MUTEX_DEBUG # only used for debugging the mutex # implementation, and is a major # performance killer options WITNESS_DDB # we aren't quite ready to turn this # on yet options INVARIANT_SUPPORT # this isn't used, and in fact, # I just axed it -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 6:18:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 453AA37B6AA; Thu, 22 Feb 2001 06:18:30 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f1MEGJl89294; Thu, 22 Feb 2001 06:16:19 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3A951A25.953E2988@FreeBSD.org> Date: Thu, 22 Feb 2001 06:18:16 -0800 (PST) From: John Baldwin To: Maxim Sobolev Subject: Re: A possible bug in the interrupt thread preemption code [Was: Cc: "Alexander N. Kabaev" , current@FreeBSD.org, Dag-Erling Smorgrav Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22-Feb-01 Maxim Sobolev wrote: >> > Here it is (from DDB): >> > panic(c027de93,c0297409,c027f878,368,80286) >> > _mtx_assert(c02ea000,9,c027f878,368,80286) >> > mi_switch(c32c5da0,3,c02cea44,c357be98) >> > ithread_schedule(c0747c00,1) >> > sched_ithd(e) >> > Xresume14() >> > --- interrupt, eip = 0xc025b60f, esp = 0x80296, ebp = 0xc357bf08 --- >> > trap(18, 10, 10,c01597b6,20) >> > calltrap() >> > --- trap 0x9, eip = 0xc025a5de, esp = 0xc357bf50, ebp = 0xc357bf64 --- >> > sw1b(c0146cbc,c0146cbc,c32c5da0,c357bf94) >> > ithread_loop(c0747c00,c357bfa8) >> > fork_exit(c0146cbc,c0747c00,c357bfa8) >> > fork_trampoline() >> >> *sigh* This is why enabling interrupts in trap() is such a bad idea. If we >> get a trap in the scheduler, then lots of bad crap starts to happen because >> we >> can get an interrupt while we are in a trap. :( Can you compile your kernel >> with >> INVARIANTS on though, as I think the kernel should've panic'd earlier if it >> is >> doing what I think it is doing. > > It's already have INVARIANTS, MUTEX_DEBUG, WITNESS and WITNESS_DDB. Hmm, ouch, you do'nt want MUTEX_DEBUG, that'll slow your system to a crawl. >> Also, if you are feeling industrious, edit >> sys/i386/i386/trap.c and comment out the enable_intr() call near the >> beginning >> of the trap() function right after the printf for 'kernel trap %d with >> interrupts disabled'. > > Ok, I'll try so. > > -Maxim It will still panic, just hopefully a better panic. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 6:23:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 4536C37B491; Thu, 22 Feb 2001 06:23:52 -0800 (PST) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id PAA44551; Thu, 22 Feb 2001 15:23:51 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: John Baldwin Cc: Maxim Sobolev , "Alexander N. Kabaev" , current@FreeBSD.org Subject: Re: A possible bug in the interrupt thread preemption code [Was: References: From: Dag-Erling Smorgrav Date: 22 Feb 2001 15:23:50 +0100 In-Reply-To: John Baldwin's message of "Thu, 22 Feb 2001 06:18:16 -0800 (PST)" Message-ID: Lines: 14 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Baldwin writes: > On 22-Feb-01 Maxim Sobolev wrote: > > It's already have INVARIANTS, MUTEX_DEBUG, WITNESS and WITNESS_DDB. > Hmm, ouch, you do'nt want MUTEX_DEBUG, that'll slow your system to a crawl. For the same reason, you probably want WITNESS_SKIPSPIN. WITNESS_DDB is a bad idea, BTW, there's a (presumably harmless) lock order reversal in the FS code that you're practically guaranteed to to hit during boot. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 6:32: 0 2001 Delivered-To: freebsd-current@freebsd.org Received: from web12707.mail.yahoo.com (web12707.mail.yahoo.com [216.136.173.244]) by hub.freebsd.org (Postfix) with SMTP id F37FA37B4EC for ; Thu, 22 Feb 2001 06:31:58 -0800 (PST) (envelope-from hotturu@yahoo.com) Message-ID: <20010222143158.88897.qmail@web12707.mail.yahoo.com> Received: from [193.140.210.12] by web12707.mail.yahoo.com; Thu, 22 Feb 2001 06:31:58 PST Date: Thu, 22 Feb 2001 06:31:58 -0800 (PST) From: chris hopkins Subject: Kernel Compilation To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I couldn't solve a problem regarding to kernel compilation. After I edit MYKERNEL and do the /usr/sbin/config, i do the make depend. It gives this error: ../../dev/xe/if_xe.c:138: card_if.h: No such file or directory. It seems that i lack that header file. Where can I find that header file, or is my problem a different one? Thanks in advance... __________________________________________________ Do You Yahoo!? Yahoo! Auctions - Buy the things you want at great prices! http://auctions.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 6:32: 6 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 3FD4937B491; Thu, 22 Feb 2001 06:32:04 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f1METLl89625; Thu, 22 Feb 2001 06:29:21 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 22 Feb 2001 06:31:18 -0800 (PST) From: John Baldwin To: Dag-Erling Smorgrav Subject: Re: A possible bug in the interrupt thread preemption code [Was: Cc: current@FreeBSD.org, "Alexander N. Kabaev" , Maxim Sobolev Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22-Feb-01 Dag-Erling Smorgrav wrote: > John Baldwin writes: >> On 22-Feb-01 Maxim Sobolev wrote: >> > It's already have INVARIANTS, MUTEX_DEBUG, WITNESS and WITNESS_DDB. >> Hmm, ouch, you do'nt want MUTEX_DEBUG, that'll slow your system to a crawl. > > For the same reason, you probably want WITNESS_SKIPSPIN. Not really. WITNESS doesn't really bog down spin mutexes all that much. It has a very simple order checking that is nothing like the order checking for sleep mutexes. The killer for MUTEX_DEBUG is that each mtx_init() involves walking a linked list of _all_ of the mutexes in the system and checking each one with the one beign init'd to check for a duplicate init. > WITNESS_DDB is a bad idea, BTW, there's a (presumably harmless) lock > order reversal in the FS code that you're practically guaranteed to to > hit during boot. Well, they aren't necessarily harmless, but they've been around for a very long time, so if they do cause rare lockups, they are rare at least. > DES > -- > Dag-Erling Smorgrav - des@ofug.org -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 7:10:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from isris.pair.com (isris.pair.com [209.68.2.39]) by hub.freebsd.org (Postfix) with SMTP id 7FC0E37B491 for ; Thu, 22 Feb 2001 07:10:24 -0800 (PST) (envelope-from rooneg@isris.pair.com) Received: (qmail 95882 invoked by uid 3130); 22 Feb 2001 15:10:23 -0000 Date: Thu, 22 Feb 2001 10:10:23 -0500 From: Garrett Rooney To: chris hopkins Cc: freebsd-current@freebsd.org Subject: Re: Kernel Compilation Message-ID: <20010222101023.B39060@electricjellyfish.net> References: <20010222143158.88897.qmail@web12707.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010222143158.88897.qmail@web12707.mail.yahoo.com>; from hotturu@yahoo.com on Thu, Feb 22, 2001 at 06:31:58AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 22, 2001 at 06:31:58AM -0800, chris hopkins wrote: > Hi, > I couldn't solve a problem regarding to kernel > compilation. After I edit MYKERNEL and do the > /usr/sbin/config, i do the make depend. It gives this > error: > ../../dev/xe/if_xe.c:138: card_if.h: No such file or > directory. > It seems that i lack that header file. Where can I > find that header file, or is my problem a different > one? > Thanks in advance... in order to compile support for the xe driver, you need to have the pccard devices in your kernel, which will cause card_if.h to be generated. -- garrett rooney Unix was not designed to stop you from rooneg@electricjellyfish.net doing stupid things, because that would http://electricjellyfish.net/ stop you from doing clever things. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 7:18:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 4F07D37B401 for ; Thu, 22 Feb 2001 07:18:27 -0800 (PST) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id QAA44787; Thu, 22 Feb 2001 16:18:12 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: "Daniel C. Sobral" Cc: current@FreeBSD.ORG Subject: Re: kernfs References: <200102220139.KAA71691@daniel.sobral> From: Dag-Erling Smorgrav Date: 22 Feb 2001 16:18:11 +0100 In-Reply-To: "Daniel C. Sobral"'s message of "Thu, 22 Feb 2001 10:39:47 +0900 (JST)" Message-ID: Lines: 17 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Daniel C. Sobral" writes: > It seems the error for kernfs is activating a couple of other warnings: > > WARNING: unknown option `KERNFS' removed from > /usr/obj/home/src/sys/DCS/opt_dont > use.h > WARNING: option `FFS' moved from opt_ffs.h to opt_dontuse.h > WARNING: unknown option `FFS_ROOT' removed from > /usr/obj/home/src/sys/DCS/opt_ff > s.h Neither KERNFS nor FFS_ROOT exist any more. The warning about FFS is correct. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 7:32:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from blizzard.sabbo.net (smtp.sabbo.net [193.193.218.18]) by hub.freebsd.org (Postfix) with ESMTP id 5A64737B4EC; Thu, 22 Feb 2001 07:31:11 -0800 (PST) (envelope-from sobomax@FreeBSD.org) Received: from vic.sabbo.net (root@vic.sabbo.net [193.193.218.112]) by blizzard.sabbo.net (8.10.1/8.10.1) with ESMTP id f1MFStf18109; Thu, 22 Feb 2001 17:29:36 +0200 Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vic.sabbo.net (8.11.2/8.11.2) with ESMTP id f1MFSvS47973; Thu, 22 Feb 2001 17:28:57 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Message-ID: <3A953037.780CDCAB@FreeBSD.org> Date: Thu, 22 Feb 2001 17:28:55 +0200 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: John Baldwin Cc: "Alexander N. Kabaev" , current@FreeBSD.org, Dag-Erling Smorgrav Subject: Re: A possible bug in the interrupt thread preemption code [Was: References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Baldwin wrote: > On 22-Feb-01 Maxim Sobolev wrote: > > >> > Here it is (from DDB): > >> > panic(c027de93,c0297409,c027f878,368,80286) > >> > _mtx_assert(c02ea000,9,c027f878,368,80286) > >> > mi_switch(c32c5da0,3,c02cea44,c357be98) > >> > ithread_schedule(c0747c00,1) > >> > sched_ithd(e) > >> > Xresume14() > >> > --- interrupt, eip = 0xc025b60f, esp = 0x80296, ebp = 0xc357bf08 --- > >> > trap(18, 10, 10,c01597b6,20) > >> > calltrap() > >> > --- trap 0x9, eip = 0xc025a5de, esp = 0xc357bf50, ebp = 0xc357bf64 --- > >> > sw1b(c0146cbc,c0146cbc,c32c5da0,c357bf94) > >> > ithread_loop(c0747c00,c357bfa8) > >> > fork_exit(c0146cbc,c0747c00,c357bfa8) > >> > fork_trampoline() > >> > >> *sigh* This is why enabling interrupts in trap() is such a bad idea. If we > >> get a trap in the scheduler, then lots of bad crap starts to happen because > >> we > >> can get an interrupt while we are in a trap. :( Can you compile your kernel > >> with > >> INVARIANTS on though, as I think the kernel should've panic'd earlier if it > >> is > >> doing what I think it is doing. > > > > It's already have INVARIANTS, MUTEX_DEBUG, WITNESS and WITNESS_DDB. > > Hmm, ouch, you do'nt want MUTEX_DEBUG, that'll slow your system to a crawl. It doesn't really matter, because system can't even boot into single-user due to panic. > >> Also, if you are feeling industrious, edit > >> sys/i386/i386/trap.c and comment out the enable_intr() call near the > >> beginning > >> of the trap() function right after the printf for 'kernel trap %d with > >> interrupts disabled'. > > > > Ok, I'll try so. > > > > -Maxim > > It will still panic, just hopefully a better panic. I did understand that, but the panic I see after the change is exactly the same as before. Any other ideas? -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 7:54:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id ADDD537B401; Thu, 22 Feb 2001 07:54:16 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f1MFq5l92529; Thu, 22 Feb 2001 07:52:05 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3A953037.780CDCAB@FreeBSD.org> Date: Thu, 22 Feb 2001 07:54:02 -0800 (PST) From: John Baldwin To: Maxim Sobolev Subject: Re: A possible bug in the interrupt thread preemption code [Was: Cc: Dag-Erling Smorgrav , current@FreeBSD.org, "Alexander N. Kabaev" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22-Feb-01 Maxim Sobolev wrote: > John Baldwin wrote: > >> On 22-Feb-01 Maxim Sobolev wrote: >> >> >> > Here it is (from DDB): >> >> > panic(c027de93,c0297409,c027f878,368,80286) >> >> > _mtx_assert(c02ea000,9,c027f878,368,80286) >> >> > mi_switch(c32c5da0,3,c02cea44,c357be98) >> >> > ithread_schedule(c0747c00,1) >> >> > sched_ithd(e) >> >> > Xresume14() >> >> > --- interrupt, eip = 0xc025b60f, esp = 0x80296, ebp = 0xc357bf08 --- >> >> > trap(18, 10, 10,c01597b6,20) >> >> > calltrap() >> >> > --- trap 0x9, eip = 0xc025a5de, esp = 0xc357bf50, ebp = 0xc357bf64 --- >> >> > sw1b(c0146cbc,c0146cbc,c32c5da0,c357bf94) >> >> > ithread_loop(c0747c00,c357bfa8) >> >> > fork_exit(c0146cbc,c0747c00,c357bfa8) >> >> > fork_trampoline() >> >> >> >> *sigh* This is why enabling interrupts in trap() is such a bad idea. If >> >> we >> >> get a trap in the scheduler, then lots of bad crap starts to happen >> >> because >> >> we >> >> can get an interrupt while we are in a trap. :( Can you compile your >> >> kernel >> >> with >> >> INVARIANTS on though, as I think the kernel should've panic'd earlier if >> >> it >> >> is >> >> doing what I think it is doing. >> > >> > It's already have INVARIANTS, MUTEX_DEBUG, WITNESS and WITNESS_DDB. >> >> Hmm, ouch, you do'nt want MUTEX_DEBUG, that'll slow your system to a crawl. > > It doesn't really matter, because system can't even boot into single-user due > to > panic. > >> >> Also, if you are feeling industrious, edit >> >> sys/i386/i386/trap.c and comment out the enable_intr() call near the >> >> beginning >> >> of the trap() function right after the printf for 'kernel trap %d with >> >> interrupts disabled'. >> > >> > Ok, I'll try so. >> > >> > -Maxim >> >> It will still panic, just hopefully a better panic. > > I did understand that, but the panic I see after the change is exactly the > same as > before. Any other ideas? A recursive sched_lock? Erm, well, stick these options in your kernel config: options KTR options KTR_EXTEND options KTR_COMPILE=KTR_LOCK options KTR_MASK=KTR_MASK Then when it panics, use the 'show ktr' command to list the mutex operations up until that point. Hopefully you can see where it is grabbing sched lock the first time and then not releasing it. Also, hsa the backtrace changed at all? If not, then you may have commented out the wrong enable_intr(). :) > -Maxim -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 8:25: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from blizzard.sabbo.net (smtp.sabbo.net [193.193.218.18]) by hub.freebsd.org (Postfix) with ESMTP id C114837B67D; Thu, 22 Feb 2001 08:24:42 -0800 (PST) (envelope-from sobomax@FreeBSD.org) Received: from vic.sabbo.net (root@vic.sabbo.net [193.193.218.112]) by blizzard.sabbo.net (8.10.1/8.10.1) with ESMTP id f1MGOEf19363; Thu, 22 Feb 2001 18:24:14 +0200 Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vic.sabbo.net (8.11.2/8.11.2) with ESMTP id f1MGO2S48204; Thu, 22 Feb 2001 18:24:02 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Message-ID: <3A953D1F.D36D0DA8@FreeBSD.org> Date: Thu, 22 Feb 2001 18:24:00 +0200 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: John Baldwin Cc: Dag-Erling Smorgrav , current@FreeBSD.org, "Alexander N. Kabaev" Subject: Re: A possible bug in the interrupt thread preemption code [Was: References: Content-Type: multipart/mixed; boundary="------------1EAD566DA224623255275644" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------1EAD566DA224623255275644 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit John Baldwin wrote: > On 22-Feb-01 Maxim Sobolev wrote: > > John Baldwin wrote: > > > >> On 22-Feb-01 Maxim Sobolev wrote: > >> > >> >> > Here it is (from DDB): > >> >> > panic(c027de93,c0297409,c027f878,368,80286) > >> >> > _mtx_assert(c02ea000,9,c027f878,368,80286) > >> >> > mi_switch(c32c5da0,3,c02cea44,c357be98) > >> >> > ithread_schedule(c0747c00,1) > >> >> > sched_ithd(e) > >> >> > Xresume14() > >> >> > --- interrupt, eip = 0xc025b60f, esp = 0x80296, ebp = 0xc357bf08 --- > >> >> > trap(18, 10, 10,c01597b6,20) > >> >> > calltrap() > >> >> > --- trap 0x9, eip = 0xc025a5de, esp = 0xc357bf50, ebp = 0xc357bf64 --- > >> >> > sw1b(c0146cbc,c0146cbc,c32c5da0,c357bf94) > >> >> > ithread_loop(c0747c00,c357bfa8) > >> >> > fork_exit(c0146cbc,c0747c00,c357bfa8) > >> >> > fork_trampoline() > >> >> > >> >> *sigh* This is why enabling interrupts in trap() is such a bad idea. If > >> >> we > >> >> get a trap in the scheduler, then lots of bad crap starts to happen > >> >> because > >> >> we > >> >> can get an interrupt while we are in a trap. :( Can you compile your > >> >> kernel > >> >> with > >> >> INVARIANTS on though, as I think the kernel should've panic'd earlier if > >> >> it > >> >> is > >> >> doing what I think it is doing. > >> > > >> > It's already have INVARIANTS, MUTEX_DEBUG, WITNESS and WITNESS_DDB. > >> > >> Hmm, ouch, you do'nt want MUTEX_DEBUG, that'll slow your system to a crawl. > > > > It doesn't really matter, because system can't even boot into single-user due > > to > > panic. > > > >> >> Also, if you are feeling industrious, edit > >> >> sys/i386/i386/trap.c and comment out the enable_intr() call near the > >> >> beginning > >> >> of the trap() function right after the printf for 'kernel trap %d with > >> >> interrupts disabled'. > >> > > >> > Ok, I'll try so. > >> > > >> > -Maxim > >> > >> It will still panic, just hopefully a better panic. > > > > I did understand that, but the panic I see after the change is exactly the > > same as > > before. Any other ideas? > > A recursive sched_lock? Erm, well, stick these options in your kernel config: > > options KTR > options KTR_EXTEND > options KTR_COMPILE=KTR_LOCK > options KTR_MASK=KTR_MASK > > Then when it panics, use the 'show ktr' command to list the mutex operations up > until that point. Hopefully you can see where it is grabbing sched lock the > first time and then not releasing it. Ok, I'll do it and send results later. > Also, hsa the backtrace changed at all? > If not, then you may have commented out the wrong enable_intr(). :) Did what you have suggested. Please see attached diff. -Maxim --------------1EAD566DA224623255275644 Content-Type: text/plain; charset=koi8-r; name="trap.c.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="trap.c.diff" --- src/sys/i386/i386/trap.c 2001/02/22 16:20:12 1.1 +++ src/sys/i386/i386/trap.c 2001/02/22 16:20:58 @@ -264,7 +264,7 @@ * We should walk p_heldmtx here and see if any are * spin mutexes, and not do this if so. */ - enable_intr(); +/* enable_intr();*/ } } --------------1EAD566DA224623255275644-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 8:48:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from blizzard.sabbo.net (pop3.sabbo.net [193.193.218.18]) by hub.freebsd.org (Postfix) with ESMTP id A338137B67D; Thu, 22 Feb 2001 08:47:40 -0800 (PST) (envelope-from sobomax@FreeBSD.org) Received: from vic.sabbo.net (root@vic.sabbo.net [193.193.218.112]) by blizzard.sabbo.net (8.10.1/8.10.1) with ESMTP id f1MGitf19820; Thu, 22 Feb 2001 18:45:16 +0200 Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vic.sabbo.net (8.11.2/8.11.2) with ESMTP id f1MGiiS48322; Thu, 22 Feb 2001 18:44:44 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Message-ID: <3A9541F9.68EDF8D5@FreeBSD.org> Date: Thu, 22 Feb 2001 18:44:41 +0200 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: John Baldwin Cc: Dag-Erling Smorgrav , current@FreeBSD.org, "Alexander N. Kabaev" Subject: Re: A possible bug in the interrupt thread preemption code [Was: References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Baldwin wrote: > On 22-Feb-01 Maxim Sobolev wrote: > > John Baldwin wrote: > > > >> On 22-Feb-01 Maxim Sobolev wrote: > >> > >> >> > Here it is (from DDB): > >> >> > panic(c027de93,c0297409,c027f878,368,80286) > >> >> > _mtx_assert(c02ea000,9,c027f878,368,80286) > >> >> > mi_switch(c32c5da0,3,c02cea44,c357be98) > >> >> > ithread_schedule(c0747c00,1) > >> >> > sched_ithd(e) > >> >> > Xresume14() > >> >> > --- interrupt, eip = 0xc025b60f, esp = 0x80296, ebp = 0xc357bf08 --- > >> >> > trap(18, 10, 10,c01597b6,20) > >> >> > calltrap() > >> >> > --- trap 0x9, eip = 0xc025a5de, esp = 0xc357bf50, ebp = 0xc357bf64 --- > >> >> > sw1b(c0146cbc,c0146cbc,c32c5da0,c357bf94) > >> >> > ithread_loop(c0747c00,c357bfa8) > >> >> > fork_exit(c0146cbc,c0747c00,c357bfa8) > >> >> > fork_trampoline() > >> >> > >> >> *sigh* This is why enabling interrupts in trap() is such a bad idea. If > >> >> we > >> >> get a trap in the scheduler, then lots of bad crap starts to happen > >> >> because > >> >> we > >> >> can get an interrupt while we are in a trap. :( Can you compile your > >> >> kernel > >> >> with > >> >> INVARIANTS on though, as I think the kernel should've panic'd earlier if > >> >> it > >> >> is > >> >> doing what I think it is doing. > >> > > >> > It's already have INVARIANTS, MUTEX_DEBUG, WITNESS and WITNESS_DDB. > >> > >> Hmm, ouch, you do'nt want MUTEX_DEBUG, that'll slow your system to a crawl. > > > > It doesn't really matter, because system can't even boot into single-user due > > to > > panic. > > > >> >> Also, if you are feeling industrious, edit > >> >> sys/i386/i386/trap.c and comment out the enable_intr() call near the > >> >> beginning > >> >> of the trap() function right after the printf for 'kernel trap %d with > >> >> interrupts disabled'. > >> > > >> > Ok, I'll try so. > >> > > >> > -Maxim > >> > >> It will still panic, just hopefully a better panic. > > > > I did understand that, but the panic I see after the change is exactly the > > same as > > before. Any other ideas? > > A recursive sched_lock? Erm, well, stick these options in your kernel config: > > options KTR > options KTR_EXTEND > options KTR_COMPILE=KTR_LOCK > options KTR_MASK=KTR_MASK Bah, it even doesn't compile with these options: cc -c -pipe -O -march=pentium -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../dev -I../../../include -I../../contrib/dev/acpica/Subsystem/Include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../kern/kern_ktr.c ../../kern/kern_ktr.c: In function `__Tunable_ktr_mask': ../../kern/kern_ktr.c:95: `KTR_MASK' undeclared (first use in this function) ../../kern/kern_ktr.c:95: (Each undeclared identifier is reported only once ../../kern/kern_ktr.c:95: for each function it appears in.) *** Error code 1 1 error -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 8:56:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id D285437B401; Thu, 22 Feb 2001 08:56:11 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f1MGrxl94441; Thu, 22 Feb 2001 08:53:59 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3A9541F9.68EDF8D5@FreeBSD.org> Date: Thu, 22 Feb 2001 08:55:57 -0800 (PST) From: John Baldwin To: Maxim Sobolev Subject: Re: A possible bug in the interrupt thread preemption code [Was: Cc: "Alexander N. Kabaev" , current@FreeBSD.org, Dag-Erling Smorgrav Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22-Feb-01 Maxim Sobolev wrote: > John Baldwin wrote: >> >> A recursive sched_lock? Erm, well, stick these options in your kernel >> config: >> >> options KTR >> options KTR_EXTEND >> options KTR_COMPILE=KTR_LOCK >> options KTR_MASK=KTR_MASK > > Bah, it even doesn't compile with these options: > cc -c -pipe -O -march=pentium -Wall -Wredundant-decls -Wnested-externs > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline > -Wcast-qual > -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../dev > -I../../../include -I../../contrib/dev/acpica/Subsystem/Include -D_KERNEL > -include > opt_global.h -elf -mpreferred-stack-boundary=2 ../../kern/kern_ktr.c > ../../kern/kern_ktr.c: In function `__Tunable_ktr_mask': > ../../kern/kern_ktr.c:95: `KTR_MASK' undeclared (first use in this function) > ../../kern/kern_ktr.c:95: (Each undeclared identifier is reported only once > ../../kern/kern_ktr.c:95: for each function it appears in.) > *** Error code 1 > 1 error Oh, whoops, that should be: options KTR_MASK=KTR_LOCK > -Maxim -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 11:13: 1 2001 Delivered-To: freebsd-current@freebsd.org Received: from blizzard.sabbo.net (pop3.sabbo.net [193.193.218.18]) by hub.freebsd.org (Postfix) with ESMTP id 78CE637B491; Thu, 22 Feb 2001 11:12:52 -0800 (PST) (envelope-from sobomax@FreeBSD.org) Received: from vic.sabbo.net (root@vic.sabbo.net [193.193.218.112]) by blizzard.sabbo.net (8.10.1/8.10.1) with ESMTP id f1MJCeC22253; Thu, 22 Feb 2001 21:12:41 +0200 Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vic.sabbo.net (8.11.2/8.11.2) with ESMTP id f1MJChS48915; Thu, 22 Feb 2001 21:12:43 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Message-ID: <3A9564A2.463789C3@FreeBSD.org> Date: Thu, 22 Feb 2001 21:12:36 +0200 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: John Baldwin Cc: Dag-Erling Smorgrav , current@FreeBSD.org, "Alexander N. Kabaev" Subject: Re: A possible bug in the interrupt thread preemption code [Was: References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Baldwin wrote: > On 22-Feb-01 Maxim Sobolev wrote: > > John Baldwin wrote: > > > >> On 22-Feb-01 Maxim Sobolev wrote: > >> > >> >> > Here it is (from DDB): > >> >> > panic(c027de93,c0297409,c027f878,368,80286) > >> >> > _mtx_assert(c02ea000,9,c027f878,368,80286) > >> >> > mi_switch(c32c5da0,3,c02cea44,c357be98) > >> >> > ithread_schedule(c0747c00,1) > >> >> > sched_ithd(e) > >> >> > Xresume14() > >> >> > --- interrupt, eip = 0xc025b60f, esp = 0x80296, ebp = 0xc357bf08 --- > >> >> > trap(18, 10, 10,c01597b6,20) > >> >> > calltrap() > >> >> > --- trap 0x9, eip = 0xc025a5de, esp = 0xc357bf50, ebp = 0xc357bf64 --- > >> >> > sw1b(c0146cbc,c0146cbc,c32c5da0,c357bf94) > >> >> > ithread_loop(c0747c00,c357bfa8) > >> >> > fork_exit(c0146cbc,c0747c00,c357bfa8) > >> >> > fork_trampoline() > >> >> > >> >> *sigh* This is why enabling interrupts in trap() is such a bad idea. If > >> >> we > >> >> get a trap in the scheduler, then lots of bad crap starts to happen > >> >> because > >> >> we > >> >> can get an interrupt while we are in a trap. :( Can you compile your > >> >> kernel > >> >> with > >> >> INVARIANTS on though, as I think the kernel should've panic'd earlier if > >> >> it > >> >> is > >> >> doing what I think it is doing. > >> > > >> > It's already have INVARIANTS, MUTEX_DEBUG, WITNESS and WITNESS_DDB. > >> > >> Hmm, ouch, you do'nt want MUTEX_DEBUG, that'll slow your system to a crawl. > > > > It doesn't really matter, because system can't even boot into single-user due > > to > > panic. > > > >> >> Also, if you are feeling industrious, edit > >> >> sys/i386/i386/trap.c and comment out the enable_intr() call near the > >> >> beginning > >> >> of the trap() function right after the printf for 'kernel trap %d with > >> >> interrupts disabled'. > >> > > >> > Ok, I'll try so. > >> > > >> > -Maxim > >> > >> It will still panic, just hopefully a better panic. > > > > I did understand that, but the panic I see after the change is exactly the > > same as > > before. Any other ideas? > > A recursive sched_lock? Erm, well, stick these options in your kernel config: > > options KTR > options KTR_EXTEND > options KTR_COMPILE=KTR_LOCK > options KTR_MASK=KTR_MASK > > Then when it panics, use the 'show ktr' command to list the mutex operations up > until that point. Hopefully you can see where it is grabbing sched lock the > first time and then not releasing it. Got the following: 724: REL (spin) sched lock [0xc030c820] r=0 at ../../kern/kern_clock.c:438 723: GOT (spin) sched lock [0xc030c820] r=0 at ../../kern/kern_clock.c:350 722: REL (spin) sched lock [0xc030c820] r=0 at ../../kern/kern_clock.c:438 721: GOT (spin) sched lock [0xc030c820] r=0 at ../../kern/kern_clock.c:350 680: REL (spin) sched lock [0xc030c820] r=0 at ../../kern/kern_clock.c:438 679: GOT (spin) sched lock [0xc030c820] r=0 at ../../kern/kern_clock.c:350 569: REL (spin) sched lock [0xc030c820] r=0 at ../../kern/kern_clock.c:438 568: GOT (spin) sched lock [0xc030c820] r=0 at ../../kern/kern_clock.c:350 546: REL (spin) sched lock [0xc030c820] r=0 at ../../kern/kern_clock.c:438 545: GOT (spin) sched lock [0xc030c820] r=0 at ../../kern/kern_clock.c:350 544: REL (spin) sched lock [0xc030c820] r=0 at ../../kern/kern_clock.c:438 543: GOT (spin) sched lock [0xc030c820] r=0 at ../../kern/kern_clock.c:350 515: REL (spin) sched lock [0xc030c820] r=0 at ../../kern/kern_clock.c:438 366: REL (spin) sched lock [0xc030c820] r=0 at ../../kern/kern_clock.c:438 365: GOT (spin) sched lock [0xc030c820] r=0 at ../../kern/kern_clock.c:350 317: REL (spin) sched lock [0xc030c820] r=0 at ../../kern/kern_clock.c:438 254: REL (spin) sched lock [0xc030c820] r=0 at ../../kern/kern_clock.c:438 253: GOT (spin) sched lock [0xc030c820] r=0 at ../../kern/kern_clock.c:350 252: REL (spin) sched lock [0xc030c820] r=0 at ../../kern/kern_clock.c:438 251: GOT (spin) sched lock [0xc030c820] r=0 at ../../kern/kern_clock.c:350 194: REL (spin) sched lock [0xc030c820] r=0 at ../../kern/kern_clock.c:438 193: GOT (spin) sched lock [0xc030c820] r=0 at ../../kern/kern_clock.c:350 182: REL (spin) sched lock [0xc030c820] r=0 at ../../kern/kern_clock.c:438 181: GOT (spin) sched lock [0xc030c820] r=0 at ../../kern/kern_clock.c:350 46: GOT (spin) sched lock [0xc030c820] r=0 at ../../kern/kern_clock.c:350 1020: REL (spin) sched lock [0xc030c820] r=0 at ../../kern/kern_clock.c:438 1019: GOT (spin) sched lock [0xc030c820] r=0 at ../../kern/kern_clock.c:350 -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 13: 2: 0 2001 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-165-226-53.dsl.lsan03.pacbell.net [64.165.226.53]) by hub.freebsd.org (Postfix) with ESMTP id 335D037B491 for ; Thu, 22 Feb 2001 13:01:57 -0800 (PST) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id F286866C34; Thu, 22 Feb 2001 13:01:56 -0800 (PST) Date: Thu, 22 Feb 2001 13:01:56 -0800 From: Kris Kennaway To: Andrea Campi Cc: freebsd-current@freebsd.org Subject: Re: -CURRENT slowdown in last 2 weeks Message-ID: <20010222130156.A6818@mollari.cthul.hu> References: <20010220015012.B5116@webcom.it> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="YiEDa0DAkWCtVeE4" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010220015012.B5116@webcom.it>; from andrea@webcom.it on Tue, Feb 20, 2001 at 01:50:23AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --YiEDa0DAkWCtVeE4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Feb 20, 2001 at 01:50:23AM +0100, Andrea Campi wrote: > I am noticing a severe slowdown on my -CURRENT system. It actually started > after Feb [3-5] changes in intrupt handling, but I didn't really notice > until I run a make world (which I delayed doing because of, well you guess, > the libc breakage). When I say severe I mean make buildworld takes x3 longer. Do you have MUTEX_DEBUG in your kernel? Kris --YiEDa0DAkWCtVeE4 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6lX5EWry0BWjoQKURAi3yAJ4jjdgtjtHL3NjTW6BEY2LewrhgKwCfUHBC lsdNCyA8K042tlZ9a5iESfk= =2M+T -----END PGP SIGNATURE----- --YiEDa0DAkWCtVeE4-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 13:15:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailout02.sul.t-online.com (mailout02.sul.t-online.com [194.25.134.17]) by hub.freebsd.org (Postfix) with ESMTP id D7EDF37B491 for ; Thu, 22 Feb 2001 13:15:55 -0800 (PST) (envelope-from D.Rock@t-online.de) Received: from fwd01.sul.t-online.com by mailout02.sul.t-online.com with smtp id 14W35e-00061Z-02; Thu, 22 Feb 2001 22:15:54 +0100 Received: from server.rock.net (340029380333-0001@[62.226.190.146]) by fmrl01.sul.t-online.com with esmtp id 14W35X-1IEQjYC; Thu, 22 Feb 2001 22:15:47 +0100 Received: from t-online.de (server [172.23.7.1]) by server.rock.net (8.11.2/8.11.2/Rock) with ESMTP id f1MLFaX17923 for ; Thu, 22 Feb 2001 22:15:36 +0100 (MET) Message-ID: <3A958178.380C85B6@t-online.de> Date: Thu, 22 Feb 2001 22:15:36 +0100 From: Daniel Rock X-Mailer: Mozilla 4.76 [de] (X11; U; SunOS 5.8 i86pc) X-Accept-Language: de, en MIME-Version: 1.0 Cc: current@FreeBSD.ORG Subject: Re: as segfaulting during world-build References: <200102201627.f1KGRLa20988@aldan.algebra.com> <20010220174909.F22771@petra.hos.u-szeged.hu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: 340029380333-0001@t-dialin.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Szilveszter Adam schrieb: > > On Tue, Feb 20, 2001 at 11:27:17AM -0500, Mikhail Teterin wrote: > > No, I don't think it is hardware. It died on the same spot for the > > third time in a row: > <...> > > What date is the -CURRENT you are attempting the build on from? There were > problems with as failing for a while not long ago. Check your version of > > src/lib/libc/stdio/findfp.c > > (the installed one...) to see if it is revision 1.15 or later. If not, you > will have to get a working as (and as reported by Martin Blapp, the other > binutiles in /usr/bin/ and /usr/libexec/elf too) from somwhere like an ftp > snapshot... if this is not the problem, I dunno, I did not have any such > problems even though I have just finished a buildworld. I did have the same problem. But just rebuilding binutils didn't help either. Trying to rebuild libc resulted in above SEGV from as. Some sort of Catch 22 I didn't have a working libc.so.5, so I just did the following: % cp /usr/lib/libc.so.4 /tmp/libc.so.5 [Maybe it's in /usr/lib/compat - I even found a libc.so.3 in /usr/lib. Hasn't been reinstalled since Mid 1998] % cd /usr/src/lib/libc; LD_LIBRARY_PATH=/tmp make all install -- Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 13:31:10 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailout03.sul.t-online.com (mailout03.sul.t-online.com [194.25.134.81]) by hub.freebsd.org (Postfix) with ESMTP id 6FF6E37B401 for ; Thu, 22 Feb 2001 13:31:07 -0800 (PST) (envelope-from D.Rock@t-online.de) Received: from fwd02.sul.t-online.com by mailout03.sul.t-online.com with smtp id 14W3KM-0000S5-00; Thu, 22 Feb 2001 22:31:06 +0100 Received: from server.rock.net (340029380333-0001@[62.226.190.146]) by fmrl02.sul.t-online.com with esmtp id 14W3KD-1cfH3AC; Thu, 22 Feb 2001 22:30:57 +0100 Received: from t-online.de (server [172.23.7.1]) by server.rock.net (8.11.2/8.11.2/Rock) with ESMTP id f1MLUkX18228; Thu, 22 Feb 2001 22:30:53 +0100 (MET) Message-ID: <3A958505.6EBDF1F4@t-online.de> Date: Thu, 22 Feb 2001 22:30:45 +0100 From: Daniel Rock X-Mailer: Mozilla 4.76 [de] (X11; U; SunOS 5.8 i86pc) X-Accept-Language: de, en MIME-Version: 1.0 To: Jake Burkholder Cc: freebsd-current@FreeBSD.ORG Subject: Re: HEADS UP Re: cvs commit: src/sys/alpha/alpha trap.c src/sys/dev/acpica/Osd OsdSchedule.c src/sys/i386/i386 genassym.c swtch.s trap.c src/sys/ia64/ia64 trap.c src/sys/kern init_main.c kern_condvar.c kern_idle.c kern_intr.c kern_mib.c kern_mutex.c kern_proc.c ... References: <20010212002426.088CFBABD@cr66388-a.rchrd1.on.wave.home.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: 340029380333-0001@t-dialin.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jake Burkholder schrieb: [...] > As I mentioned in the commit message, this changes the size and layout > of struct kinfo_proc, so you'll have to recompile libkvm-using programs. > > As always, make world is your friend. You may have forgotten to also change KINFO_PROC_SIZE in src/sys/user.h I'm now getting bootup warning all the time: ... real memory = 197066752 (192448K bytes) avail memory = 187293696 (182904K bytes) Preloaded elf kernel "kernel" at 0xc0450000. WARNING: size of kinfo_proc (648) should be 644!!! Pentium Pro MTRR support enabled ... BTW What is the purpose of KINFO_PROC_SIZE? Why not simply using sizeof()? -- Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 14:26:48 2001 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 339E037B491 for ; Thu, 22 Feb 2001 14:26:45 -0800 (PST) (envelope-from jhb@foo.osd.bsdi.com) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f1MMQYK01844 for ; Thu, 22 Feb 2001 14:26:34 -0800 (PST) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.1/8.11.1) id f1MMPru60224 for current@FreeBSD.org; Thu, 22 Feb 2001 14:25:54 -0800 (PST) (envelope-from jhb) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Thu, 22 Feb 2001 14:25:53 -0800 (PST) Organization: BSD, Inc. From: John Baldwin To: current@FreeBSD.org Subject: Release b0rked.. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ===> lib/libgssapi rm -f .depend mkdep -f .depend -a -I/usr/src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi -I/usr/src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/krb5 -I/usr/src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/asn1 -I/usr/src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/roken -I/usr/src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/des -I/usr/src/kerberos5/lib/libgssapi/../../../crypto/heimdal/include -I/usr/obj/usr/src/kerberos5/lib/libgssapi/../../lib/libasn1 -I/usr/src/kerberos5/lib/libgssapi/../../include -I/usr/src/kerberos5/lib/libgssapi/../../include -DHAVE_CONFIG_H -DINET6 /usr/src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi/8003.c ... In file included from /usr/src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/krb5/krb5_locl.h:14 2, from /usr/src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi/gssapi_locl. h:39, from /usr/src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi/8003.c:34: /usr/src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/krb5/krb5.h:43: krb5_err.h: No such file or directory /usr/src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/krb5/krb5.h:44: heim_err.h: No such file or directory In file included from /usr/src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi/gssapi_locl. h:39, from /usr/src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi/8003.c:34: /usr/src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/krb5/krb5_locl.h:14 3: krb5_err.h: No such file or directory ... (repeat about 50 times) mkdep: compile failed *** Error code 1 Stop in /usr/src/kerberos5/lib/libgssapi. *** Error code 1 Stop in /usr/src/kerberos5/lib. *** Error code 1 Stop in /usr/src/kerberos5. *** Error code 1 Stop in /usr/src/release. *** Error code 1 Stop in /usr/src/release. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 15:20:13 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 64E8037B491 for ; Thu, 22 Feb 2001 15:20:11 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id PAA22651 for ; Thu, 22 Feb 2001 15:20:11 -0800 Date: Thu, 22 Feb 2001 15:20:10 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: current@freebsd.org Subject: dirty buffers on reboot again? 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 guring syscons:. Additional ABI support:. Starting local daemons:. Local package initialization: Networker Samba. Additional TCP options:. Thu Feb 22 11:38:43 PST 2001 FreeBSD/i386 (quarm.feral.com) (ttyd0) login: (da0:ahc0:0:0:0): tagged openings now 16 Feb 22 15:17:31 quarm rebootWaiting (max 60 seconds) for system process `bufdaemon' to stop...stopped Waiting (max 60 seconds) for system process `syncer' to stop...stopped syncing disks... 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 giving up on 3 buffers Uptime: 3h44m4s I'm seeing a lot of this again. Anyone else? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 15:27:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from mobile.hub.org (SHW39-29.accesscable.net [24.138.39.29]) by hub.freebsd.org (Postfix) with ESMTP id 1AE6837B4EC; Thu, 22 Feb 2001 15:27:30 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by mobile.hub.org (8.11.1/8.11.1) with ESMTP id f1MNRSF28571; Thu, 22 Feb 2001 19:27:29 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: mobile.hub.org: scrappy owned process doing -bs Date: Thu, 22 Feb 2001 19:27:28 -0400 (AST) From: The Hermit Hacker To: John Baldwin Cc: Subject: RE: System hangs with -current ... In-Reply-To: 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 Okay, I have to pick up a NULL modem cable tomorrow and dive into this ... finally ... The various KTR_ that you mention below, these are kernel settings that I compile into the kernel? On Tue, 2 Jan 2001, John Baldwin wrote: > > On 02-Jan-01 The Hermit Hacker wrote: > > > > Over the past several months, as others have reported, I've been getting > > system hangs using 5.0-CURRENT w/ SMP ... I've got DDB enabled, but > > ctl-alt-esc doesn't break me to the debugger ... > > > > I'm not complaining about the hangs, if I was overly concerned, I'd run > > -STABLE, but I'm wondering how one goes about providing debug information > > on them other then through DDB? > > Not easily. :( If you can make the problem easily repeatable, then you can try > turning on KTR in your kernel (see NOTES, you will need KTR_EXTEND), setting up > a serial console that you log the output of, create a shell script that runs > the following commands: > > #!/bin/sh > > # Turn on KTR_INTR, KTR_PROC, and KTR_LOCK > sysctl -w debug.ktr_mask=0x1208 > sysctl -w debug.ktr_verbose=2 > > run_magic_command_that_hangs_my_machine > > and run the script. You probably want to run it over a tty or remote login so > tthat the serial console output is just the logging (warning, it will be very > verbose!). Also, you probably want to use > http://www.FreeBSD.org/~jhb/patches/mtx_quiet.patch to shut up most of the > irrelevant and cluttery mutex trace messages. Note that having this much > logging on will probably slow the machine to a crawl as well, so you may have > to just start this up and go off and do something else until it hangs. :-/ > Another alternative is to rig up a NMI debouncer and use it to break into the > debugger. Then you can start poking around to see who owns sched_lock, etc. > > > Thanks ... > > -- > > John Baldwin -- http://www.FreeBSD.org/~jhb/ > PGP Key: http://www.baldwin.cx/~john/pgpkey.asc > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 15:33:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from c1030098-a.wtrlo1.ia.home.com (c1030098-a.wtrlo1.ia.home.com [24.11.39.39]) by hub.freebsd.org (Postfix) with ESMTP id 6D76D37B503 for ; Thu, 22 Feb 2001 15:33:44 -0800 (PST) (envelope-from mdharnois@home.com) Received: by c1030098-a.wtrlo1.ia.home.com (Postfix, from userid 1001) id 3E19214A59; Thu, 22 Feb 2001 17:34:01 -0600 (CST) To: Matthew Jacob Cc: current@FreeBSD.ORG Subject: Re: dirty buffers on reboot again? References: From: Michael Harnois Date: 22 Feb 2001 17:33:59 -0600 In-Reply-To: (Matthew Jacob's message of "Thu, 22 Feb 2001 15:20:10 -0800 (PST)") Message-ID: <863dd61ee0.fsf@mharnois.workgroup.net> Lines: 14 User-Agent: Gnus/5.090001 (Oort Gnus v0.01) XEmacs/21.2 (Thalia) 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, 22 Feb 2001 15:20:10 -0800 (PST), Matthew Jacob said: > syncing disks... 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 giving > up on 3 buffers > I'm seeing a lot of this again. Anyone else? Yup. -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mdharnois@home.com aa0bt@aa0bt.ampr.org Where ignorance is our master, there is no possibility of real peace. -- the Dalai Lama To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 16:31:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from web12803.mail.yahoo.com (web12803.mail.yahoo.com [216.136.174.38]) by hub.freebsd.org (Postfix) with SMTP id 1F71637B491 for ; Thu, 22 Feb 2001 16:31:30 -0800 (PST) (envelope-from swliucn@yahoo.com) Message-ID: <20010223003130.13754.qmail@web12803.mail.yahoo.com> Received: from [202.98.16.1] by web12803.mail.yahoo.com; Thu, 22 Feb 2001 16:31:30 PST Date: Thu, 22 Feb 2001 16:31:30 -0800 (PST) From: Liu Siwei Subject: How could I do with my sound card? To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, My question is: My sound card is CS423X, FreeBSD supports it. It says: pcm1: at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 on isa0 . But my system is FreeBSD-current, the /dev file system I can't write, can't use sh MAKEDEV snd0, and all software to look for /dev/mixer0 .. So how could to now? my dmesg: Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Wed Feb 21 19:57:08 GMT 2001 root@bigbear.com:/usr/home/src-cur/sys/compile/bigbear Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 300685261 Hz CPU: AMD-K6tm w/ multimedia extensions (300.69-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x570 Stepping = 0 Features=0x8001bf AMD Features=0x400<> real memory = 67108864 (65536K bytes) avail memory = 61530112 (60088K bytes) Preloaded elf kernel "kernel" at 0xc03b5000. seq0-15: Midi sequencers. Using $PIR table, 4 entries at 0xc00fdc10 npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xe000-0xe00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 7.2 (no driver attached) pci0: at 7.3 (no driver attached) ed0: port 0xe800-0xe81f irq 10 at device 10.0 on pci0 ed0: address 00:e0:4c:dd:a0:ec, type NE2000 (16 bit) pci0: at 12.0 (no driver attached) atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources pcm1: at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 on isa0 ad0: 4112MB [8912/15/63] at ata0-master UDMA33 ad1: 2014MB [4092/16/63] at ata0-slave UDMA33 acd0: CDROM at ata1-master using PIO4 Mounting root from ufs:/dev/ad0s1a cd9660: RockRidge Extension my dev: acd0a dsp1.0 ppi0 sequencer9 ttyv5 acd0c dsp1.1 psm0 sndstat ttyv6 ad0 dspW1.0 random stderr ttyv7 ad0s1a dspW1.1 sequencer0 stdin ttyv8 ad0s1b fd sequencer1 stdout ttyv9 ad0s1e fd0 sequencer10 sysmouse ttyva ad1 io sequencer11 tty ttyvb audio1.0 kbd0 sequencer12 ttyd0 ttyvc audio1.1 klog sequencer13 ttyd1 ttyvd bpsm0 kmem sequencer14 ttyid0 ttyve console log sequencer15 ttyid1 ttyvf consolectl lpt0 sequencer2 ttyld0 urandom cuaa0 lpt0.ctl sequencer3 ttyld1 vga cuaa1 mdctl sequencer4 ttyv0 zero cuaia0 mem sequencer5 ttyv1 cuaia1 mixer1 sequencer6 ttyv2 cuala0 null sequencer7 ttyv3 cuala1 pci sequencer8 ttyv4 my df: Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad0s1a 228207 98219 111732 47% / devfs 1 1 0 100% /dev/ /dev/ad0s1e 3460132 1892196 1291126 59% /usr procfs 4 4 0 100% /proc /dev/acd0a 659010 659010 0 100% /cdrom __________________________________________________ Do You Yahoo!? Yahoo! Auctions - Buy the things you want at great prices! http://auctions.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 16:51:34 2001 Delivered-To: freebsd-current@freebsd.org Received: from volatile.chemikals.org (ci391991-a.grnvle1.sc.home.com [24.6.40.144]) by hub.freebsd.org (Postfix) with ESMTP id 8095337B401 for ; Thu, 22 Feb 2001 16:51:30 -0800 (PST) (envelope-from morganw@chemikals.org) Received: (from morganw@localhost) by volatile.chemikals.org (8.11.2/8.11.1) id f1N0p8689056; Thu, 22 Feb 2001 19:51:08 -0500 (EST) (envelope-from morganw) Date: Thu, 22 Feb 2001 19:51:08 -0500 (EST) From: Wesley Morgan To: Matthew Jacob Cc: Subject: Re: dirty buffers on reboot again? In-Reply-To: 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 am, it keeps screwing up my gnome desktop. On Thu, 22 Feb 2001, Matthew Jacob wrote: > > guring syscons:. > Additional ABI support:. > Starting local daemons:. > Local package initialization: Networker Samba. > Additional TCP options:. > > Thu Feb 22 11:38:43 PST 2001 > > FreeBSD/i386 (quarm.feral.com) (ttyd0) > > login: (da0:ahc0:0:0:0): tagged openings now 16 > Feb 22 15:17:31 quarm rebootWaiting (max 60 seconds) for system process > `bufdaemon' to stop...stopped > Waiting (max 60 seconds) for system process `syncer' to stop...stopped > > syncing disks... 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 > giving up on 3 buffers > Uptime: 3h44m4s > > I'm seeing a lot of this again. Anyone else? > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- _ __ ___ ____ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ morganw@chemikals.org _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 17: 6:18 2001 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 960FE37B401 for ; Thu, 22 Feb 2001 17:06:11 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id LAA11991; Fri, 23 Feb 2001 11:36:04 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010223003130.13754.qmail@web12803.mail.yahoo.com> Date: Fri, 23 Feb 2001 11:36:04 +1030 (CST) From: "Daniel O'Connor" To: Liu Siwei Subject: RE: How could I do with my sound card? Cc: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 23-Feb-01 Liu Siwei wrote: > Hello, My question is: > My sound card is CS423X, FreeBSD supports it. It > says: pcm1: at port > 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 on > isa0 > . But my system is FreeBSD-current, the /dev file > system I can't write, can't use sh MAKEDEV snd0, and > all software to look for /dev/mixer0 .. > So how could to now? try MAKEDEV snd1 I'm fairly sure there is a FAQ or handbook entry on this. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 17:57:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.numachi.com (numachi.numachi.com [198.175.254.2]) by hub.freebsd.org (Postfix) with SMTP id C52FB37B401 for ; Thu, 22 Feb 2001 17:57:54 -0800 (PST) (envelope-from reichert@natto.numachi.com) Received: (qmail 20858 invoked by uid 3001); 23 Feb 2001 01:57:50 -0000 Received: from natto.numachi.com (198.175.254.216) by numachi.numachi.com with SMTP; 23 Feb 2001 01:57:50 -0000 Received: (qmail 84143 invoked by uid 1001); 23 Feb 2001 01:57:50 -0000 Date: Thu, 22 Feb 2001 20:57:50 -0500 From: Brian Reichert To: Liu Siwei Cc: freebsd-current@freebsd.org Subject: Re: How could I do with my sound card? Message-ID: <20010222205750.E79987@numachi.com> References: <20010223003130.13754.qmail@web12803.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010223003130.13754.qmail@web12803.mail.yahoo.com>; from swliucn@yahoo.com on Thu, Feb 22, 2001 at 04:31:30PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 22, 2001 at 04:31:30PM -0800, Liu Siwei wrote: > Hello, My question is: > My sound card is CS423X, FreeBSD supports it. It > says: pcm1: at port > 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 on > isa0 > . But my system is FreeBSD-current, the /dev file > system I can't write, can't use sh MAKEDEV snd0, and > all software to look for /dev/mixer0 .. Are you trying to run MAKEDEV as root? > So how could to now? > -- Brian 'you Bastard' Reichert 37 Crystal Ave. #303 Daytime number: (603) 434-6842 Derry NH 03038-1713 USA Intel architecture: the left-hand path To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 18: 4:53 2001 Delivered-To: freebsd-current@freebsd.org Received: from vilnya.demon.co.uk (vilnya.demon.co.uk [158.152.19.238]) by hub.freebsd.org (Postfix) with ESMTP id A7A1037B491 for ; Thu, 22 Feb 2001 18:04:47 -0800 (PST) (envelope-from gandalf@vilnya.demon.co.uk) Received: from haveblue (haveblue.rings [10.2.4.5]) by vilnya.demon.co.uk (Postfix) with SMTP id F30FAD9B8; Fri, 23 Feb 2001 02:04:32 +0000 (GMT) Message-ID: <003e01c09d3c$fd1c1ad0$0504020a@haveblue> From: "Cameron Grant" To: "Liu Siwei" , References: <20010223003130.13754.qmail@web12803.mail.yahoo.com> Subject: Re: How could I do with my sound card? Date: Fri, 23 Feb 2001 02:04:30 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > says: pcm1: at port > 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 on > isa0 you have a bogus device pcm0. you probably have a mistake in your hints file. -cg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 18:12:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 95CA637B401 for ; Thu, 22 Feb 2001 18:12:07 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f1N29gl12834; Thu, 22 Feb 2001 18:09:42 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 22 Feb 2001 18:11:46 -0800 (PST) From: John Baldwin To: The Hermit Hacker Subject: RE: System hangs with -current ... Cc: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22-Feb-01 The Hermit Hacker wrote: > > Okay, I have to pick up a NULL modem cable tomorrow and dive into this ... > finally ... > > The various KTR_ that you mention below, these are kernel settings that I > compile into the kernel? Yes. You want this: options KTR options KTR_EXTEND options KTR_COMPILE=0x1208 The mtx_quiet.patch is old and won't apply to current now I'm afraid. > On Tue, 2 Jan 2001, John Baldwin wrote: > >> >> On 02-Jan-01 The Hermit Hacker wrote: >> > >> > Over the past several months, as others have reported, I've been getting >> > system hangs using 5.0-CURRENT w/ SMP ... I've got DDB enabled, but >> > ctl-alt-esc doesn't break me to the debugger ... >> > >> > I'm not complaining about the hangs, if I was overly concerned, I'd run >> > -STABLE, but I'm wondering how one goes about providing debug information >> > on them other then through DDB? >> >> Not easily. :( If you can make the problem easily repeatable, then you can >> try >> turning on KTR in your kernel (see NOTES, you will need KTR_EXTEND), setting >> up >> a serial console that you log the output of, create a shell script that runs >> the following commands: >> >> #!/bin/sh >> >> # Turn on KTR_INTR, KTR_PROC, and KTR_LOCK >> sysctl -w debug.ktr_mask=0x1208 >> sysctl -w debug.ktr_verbose=2 >> >> run_magic_command_that_hangs_my_machine >> >> and run the script. You probably want to run it over a tty or remote login >> so >> tthat the serial console output is just the logging (warning, it will be >> very >> verbose!). Also, you probably want to use >> http://www.FreeBSD.org/~jhb/patches/mtx_quiet.patch to shut up most of the >> irrelevant and cluttery mutex trace messages. Note that having this much >> logging on will probably slow the machine to a crawl as well, so you may >> have >> to just start this up and go off and do something else until it hangs. :-/ >> Another alternative is to rig up a NMI debouncer and use it to break into >> the >> debugger. Then you can start poking around to see who owns sched_lock, etc. >> >> > Thanks ... >> >> -- >> >> John Baldwin -- http://www.FreeBSD.org/~jhb/ >> PGP Key: http://www.baldwin.cx/~john/pgpkey.asc >> "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ >> > > Marc G. Fournier ICQ#7615664 IRC Nick: > Scrappy > Systems Administrator @ hub.org > primary: scrappy@hub.org secondary: > scrappy@{freebsd|postgresql}.org > -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 18:50:10 2001 Delivered-To: freebsd-current@freebsd.org Received: from mobile.hub.org (SHW39-29.accesscable.net [24.138.39.29]) by hub.freebsd.org (Postfix) with ESMTP id 333D337B65D; Thu, 22 Feb 2001 18:50:02 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by mobile.hub.org (8.11.1/8.11.1) with ESMTP id f1N2o0U29597; Thu, 22 Feb 2001 22:50:01 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: mobile.hub.org: scrappy owned process doing -bs Date: Thu, 22 Feb 2001 22:50:00 -0400 (AST) From: The Hermit Hacker To: John Baldwin Cc: Subject: RE: System hangs with -current ... In-Reply-To: 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, 22 Feb 2001, John Baldwin wrote: > > On 22-Feb-01 The Hermit Hacker wrote: > > > > Okay, I have to pick up a NULL modem cable tomorrow and dive into this ... > > finally ... > > > > The various KTR_ that you mention below, these are kernel settings that I > > compile into the kernel? > > Yes. You want this: > > options KTR > options KTR_EXTEND > options KTR_COMPILE=0x1208 okay, just so that I understand ... I compile my kernel with these options, and then run the two sysctl commands you list below? the KTR_COMPILE arg looks similar to the ktr_mask one below, which is why I'm confirming ... > > The mtx_quiet.patch is old and won't apply to current now I'm afraid. > > > On Tue, 2 Jan 2001, John Baldwin wrote: > > > >> > >> On 02-Jan-01 The Hermit Hacker wrote: > >> > > >> > Over the past several months, as others have reported, I've been getting > >> > system hangs using 5.0-CURRENT w/ SMP ... I've got DDB enabled, but > >> > ctl-alt-esc doesn't break me to the debugger ... > >> > > >> > I'm not complaining about the hangs, if I was overly concerned, I'd run > >> > -STABLE, but I'm wondering how one goes about providing debug information > >> > on them other then through DDB? > >> > >> Not easily. :( If you can make the problem easily repeatable, then you can > >> try > >> turning on KTR in your kernel (see NOTES, you will need KTR_EXTEND), setting > >> up > >> a serial console that you log the output of, create a shell script that runs > >> the following commands: > >> > >> #!/bin/sh > >> > >> # Turn on KTR_INTR, KTR_PROC, and KTR_LOCK > >> sysctl -w debug.ktr_mask=0x1208 > >> sysctl -w debug.ktr_verbose=2 > >> > >> run_magic_command_that_hangs_my_machine > >> > >> and run the script. You probably want to run it over a tty or remote login > >> so > >> tthat the serial console output is just the logging (warning, it will be > >> very > >> verbose!). Also, you probably want to use > >> http://www.FreeBSD.org/~jhb/patches/mtx_quiet.patch to shut up most of the > >> irrelevant and cluttery mutex trace messages. Note that having this much > >> logging on will probably slow the machine to a crawl as well, so you may > >> have > >> to just start this up and go off and do something else until it hangs. :-/ > >> Another alternative is to rig up a NMI debouncer and use it to break into > >> the > >> debugger. Then you can start poking around to see who owns sched_lock, etc. > >> > >> > Thanks ... > >> > >> -- > >> > >> John Baldwin -- http://www.FreeBSD.org/~jhb/ > >> PGP Key: http://www.baldwin.cx/~john/pgpkey.asc > >> "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > >> > > > > Marc G. Fournier ICQ#7615664 IRC Nick: > > Scrappy > > Systems Administrator @ hub.org > > primary: scrappy@hub.org secondary: > > scrappy@{freebsd|postgresql}.org > > > > -- > > John Baldwin -- http://www.FreeBSD.org/~jhb/ > PGP Key: http://www.baldwin.cx/~john/pgpkey.asc > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 18:59:13 2001 Delivered-To: freebsd-current@freebsd.org Received: from mobile.hub.org (SHW39-29.accesscable.net [24.138.39.29]) by hub.freebsd.org (Postfix) with ESMTP id BD48637B503; Thu, 22 Feb 2001 18:59:06 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by mobile.hub.org (8.11.1/8.11.1) with ESMTP id f1N2x5R29671; Thu, 22 Feb 2001 22:59:05 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: mobile.hub.org: scrappy owned process doing -bs Date: Thu, 22 Feb 2001 22:59:05 -0400 (AST) From: The Hermit Hacker To: John Baldwin Cc: Subject: RE: System hangs with -current ... In-Reply-To: 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, 22 Feb 2001, John Baldwin wrote: > > On 22-Feb-01 The Hermit Hacker wrote: > > > > Okay, I have to pick up a NULL modem cable tomorrow and dive into this ... > > finally ... > > > > The various KTR_ that you mention below, these are kernel settings that I > > compile into the kernel? > > Yes. You want this: > > options KTR > options KTR_EXTEND > options KTR_COMPILE=0x1208 okay, just so that I understand ... I compile my kernel with these options, and then run the two sysctl commands you list below? the KTR_COMPILE arg looks similar to the ktr_mask one below, which is why I'm confirming ... > > The mtx_quiet.patch is old and won't apply to current now I'm afraid. > > > On Tue, 2 Jan 2001, John Baldwin wrote: > > > >> > >> On 02-Jan-01 The Hermit Hacker wrote: > >> > > >> > Over the past several months, as others have reported, I've been getting > >> > system hangs using 5.0-CURRENT w/ SMP ... I've got DDB enabled, but > >> > ctl-alt-esc doesn't break me to the debugger ... > >> > > >> > I'm not complaining about the hangs, if I was overly concerned, I'd run > >> > -STABLE, but I'm wondering how one goes about providing debug information > >> > on them other then through DDB? > >> > >> Not easily. :( If you can make the problem easily repeatable, then you can > >> try > >> turning on KTR in your kernel (see NOTES, you will need KTR_EXTEND), setting > >> up > >> a serial console that you log the output of, create a shell script that runs > >> the following commands: > >> > >> #!/bin/sh > >> > >> # Turn on KTR_INTR, KTR_PROC, and KTR_LOCK > >> sysctl -w debug.ktr_mask=0x1208 > >> sysctl -w debug.ktr_verbose=2 > >> > >> run_magic_command_that_hangs_my_machine > >> > >> and run the script. You probably want to run it over a tty or remote login > >> so > >> tthat the serial console output is just the logging (warning, it will be > >> very > >> verbose!). Also, you probably want to use > >> http://www.FreeBSD.org/~jhb/patches/mtx_quiet.patch to shut up most of the > >> irrelevant and cluttery mutex trace messages. Note that having this much > >> logging on will probably slow the machine to a crawl as well, so you may > >> have > >> to just start this up and go off and do something else until it hangs. :-/ > >> Another alternative is to rig up a NMI debouncer and use it to break into > >> the > >> debugger. Then you can start poking around to see who owns sched_lock, etc. > >> > >> > Thanks ... > >> > >> -- > >> > >> John Baldwin -- http://www.FreeBSD.org/~jhb/ > >> PGP Key: http://www.baldwin.cx/~john/pgpkey.asc > >> "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > >> > > > > Marc G. Fournier ICQ#7615664 IRC Nick: > > Scrappy > > Systems Administrator @ hub.org > > primary: scrappy@hub.org secondary: > > scrappy@{freebsd|postgresql}.org > > > > -- > > John Baldwin -- http://www.FreeBSD.org/~jhb/ > PGP Key: http://www.baldwin.cx/~john/pgpkey.asc > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 20:29:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.icomtek.csir.co.za (zibbi.icomtek.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 066F337B503; Thu, 22 Feb 2001 20:29:30 -0800 (PST) (envelope-from jhay@zibbi.icomtek.csir.co.za) Received: (from jhay@localhost) by zibbi.icomtek.csir.co.za (8.11.1/8.11.1) id f1N4TN172703; Fri, 23 Feb 2001 06:29:23 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200102230429.f1N4TN172703@zibbi.icomtek.csir.co.za> Subject: Re: Release b0rked.. In-Reply-To: from John Baldwin at "Feb 22, 2001 02:25:53 pm" To: jhb@FreeBSD.ORG (John Baldwin) Date: Fri, 23 Feb 2001 06:29:23 +0200 (SAT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ===> lib/libgssapi > rm -f .depend > mkdep -f .depend -a ... > /usr/src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/krb5/krb5.h:43: > krb5_err.h: No such file or directory > /usr/src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/krb5/krb5.h:44: > heim_err.h: No such file or directory You can get past this error with this patch, but it will just die a little later in another part of kerberos. You should have better luck by building a release with NOKERBEROS=YES. I was able to build one yesterday. John -- John Hay -- John.Hay@icomtek.csir.co.za Index: kerberos5/lib/libgssapi/Makefile =================================================================== RCS file: /home/ncvs/src/kerberos5/lib/libgssapi/Makefile,v retrieving revision 1.1 diff -u -r1.1 Makefile --- kerberos5/lib/libgssapi/Makefile 2001/02/13 16:56:50 1.1 +++ kerberos5/lib/libgssapi/Makefile 2001/02/17 15:13:38 @@ -7,7 +7,8 @@ -I${KRB5DIR}/lib/roken \ -I${KRB5DIR}/lib/des \ -I${KRB5DIR}/include \ - -I${ASN1OBJDIR} + -I${ASN1OBJDIR} \ + -I${KRB5OBJDIR} SRCS= \ 8003.c \ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 20:48:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from moby.geekhouse.net (moby.geekhouse.net [64.81.6.36]) by hub.freebsd.org (Postfix) with ESMTP id BD89837B491 for ; Thu, 22 Feb 2001 20:47:57 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@dhcp151.geekhouse.net [192.168.1.151]) by moby.geekhouse.net (8.11.0/8.9.3) with ESMTP id f1N4oYc73292; Thu, 22 Feb 2001 20:50:34 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 22 Feb 2001 20:47:39 -0800 (PST) From: John Baldwin To: The Hermit Hacker Subject: RE: System hangs with -current ... Cc: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 23-Feb-01 The Hermit Hacker wrote: > On Thu, 22 Feb 2001, John Baldwin wrote: > >> >> On 22-Feb-01 The Hermit Hacker wrote: >> > >> > Okay, I have to pick up a NULL modem cable tomorrow and dive into this ... >> > finally ... >> > >> > The various KTR_ that you mention below, these are kernel settings that I >> > compile into the kernel? >> >> Yes. You want this: >> >> options KTR >> options KTR_EXTEND >> options KTR_COMPILE=0x1208 > > okay, just so that I understand ... I compile my kernel with these > options, and then run the two sysctl commands you list below? the > KTR_COMPILE arg looks similar to the ktr_mask one below, which is why I'm > confirming ... Yes. KTR_COMPILE controls what KTR tracepoints are actually compiled into the kernel. The ktr_mask sysctl controls a runtime mask that lets you choose which of the compiled in masks you want to enable. I have manpages for this stuff, but they are waiting for doc guys to review them. >> The mtx_quiet.patch is old and won't apply to current now I'm afraid. >> >> > On Tue, 2 Jan 2001, John Baldwin wrote: >> > >> >> >> >> On 02-Jan-01 The Hermit Hacker wrote: >> >> > >> >> > Over the past several months, as others have reported, I've been >> >> > getting >> >> > system hangs using 5.0-CURRENT w/ SMP ... I've got DDB enabled, but >> >> > ctl-alt-esc doesn't break me to the debugger ... >> >> > >> >> > I'm not complaining about the hangs, if I was overly concerned, I'd run >> >> > -STABLE, but I'm wondering how one goes about providing debug >> >> > information >> >> > on them other then through DDB? >> >> >> >> Not easily. :( If you can make the problem easily repeatable, then you >> >> can >> >> try >> >> turning on KTR in your kernel (see NOTES, you will need KTR_EXTEND), >> >> setting >> >> up >> >> a serial console that you log the output of, create a shell script that >> >> runs >> >> the following commands: >> >> >> >> #!/bin/sh >> >> >> >> # Turn on KTR_INTR, KTR_PROC, and KTR_LOCK >> >> sysctl -w debug.ktr_mask=0x1208 >> >> sysctl -w debug.ktr_verbose=2 >> >> >> >> run_magic_command_that_hangs_my_machine >> >> >> >> and run the script. You probably want to run it over a tty or remote >> >> login >> >> so >> >> tthat the serial console output is just the logging (warning, it will be >> >> very >> >> verbose!). Also, you probably want to use >> >> http://www.FreeBSD.org/~jhb/patches/mtx_quiet.patch to shut up most of >> >> the >> >> irrelevant and cluttery mutex trace messages. Note that having this much >> >> logging on will probably slow the machine to a crawl as well, so you may >> >> have >> >> to just start this up and go off and do something else until it hangs. >> >> :-/ >> >> Another alternative is to rig up a NMI debouncer and use it to break into >> >> the >> >> debugger. Then you can start poking around to see who owns sched_lock, >> >> etc. >> >> >> >> > Thanks ... -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 21: 1: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from white.imgsrc.co.jp (ns.imgsrc.co.jp [210.226.20.2]) by hub.freebsd.org (Postfix) with ESMTP id 5F92C37B503; Thu, 22 Feb 2001 21:01:00 -0800 (PST) (envelope-from kuriyama@imgsrc.co.jp) Received: from waterblue.imgsrc.co.jp (waterblue.imgsrc.co.jp [210.226.20.160]) by white.imgsrc.co.jp (8.11.2/8.11.0) with ESMTP id f1N50xT45670; Fri, 23 Feb 2001 14:00:59 +0900 (JST) Date: Fri, 23 Feb 2001 14:00:55 +0900 Message-ID: <7mu25mhu2g.wl@waterblue.imgsrc.co.jp> From: Jun Kuriyama To: Assar Westerlund Cc: current@FreeBSD.ORG Subject: Re: Release b0rked.. In-Reply-To: <200102230429.f1N4TN172703@zibbi.icomtek.csir.co.za> References: <200102230429.f1N4TN172703@zibbi.icomtek.csir.co.za> User-Agent: Wanderlust/2.4.0 (Rio) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 14) (Cuyahoga Valley) (i386--freebsd) Cc: Jun Kuriyama MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Assar, can you review and commit this? At 23 Feb 2001 04:31:06 GMT, John Hay wrote: > Index: kerberos5/lib/libgssapi/Makefile > =================================================================== > RCS file: /home/ncvs/src/kerberos5/lib/libgssapi/Makefile,v > retrieving revision 1.1 > diff -u -r1.1 Makefile > --- kerberos5/lib/libgssapi/Makefile 2001/02/13 16:56:50 1.1 > +++ kerberos5/lib/libgssapi/Makefile 2001/02/17 15:13:38 > @@ -7,7 +7,8 @@ > -I${KRB5DIR}/lib/roken \ > -I${KRB5DIR}/lib/des \ > -I${KRB5DIR}/include \ > - -I${ASN1OBJDIR} > + -I${ASN1OBJDIR} \ > + -I${KRB5OBJDIR} > > SRCS= \ > 8003.c \ -- Jun Kuriyama // IMG SRC, Inc. // FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 21:34:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from C456086-A.bllvu1.wa.home.com (c456086-a.bllvu1.wa.home.com [65.0.111.16]) by hub.freebsd.org (Postfix) with ESMTP id 7E82B37B491 for ; Thu, 22 Feb 2001 21:34:47 -0800 (PST) (envelope-from kargl@C456086-A.bllvu1.wa.home.com) Received: (from kargl@localhost) by C456086-A.bllvu1.wa.home.com (8.11.1/8.11.2) id f1MLYF545604 for freebsd-current@freebsd.org; Thu, 22 Feb 2001 21:34:15 GMT (envelope-from kargl) From: "Steven G. Kargl" Message-Id: <200102222134.f1MLYF545604@C456086-A.bllvu1.wa.home.com> Subject: USER_LDT gone? To: freebsd-current@freebsd.org Date: Thu, 22 Feb 2001 21:34:12 +0000 (GMT) X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With the great libc debacle of 2001, I have not tried to update my system for about 2 weeks. In that time I may have missed the commit message that said that USER_LDT, which was needed for at least wine, was removed. root[221] cd /usr/src/ root[222] setenv KERNCONF `hostname -s` root[223] make buildkernel -------------------------------------------------------------- >>> Kernel build for C456086-A started on Thu Feb 22 21:28:18 GMT 2001 -------------------------------------------------------------- ===> C456086-A mkdir -p /usr/obj/usr/src/sys cd /usr/src/sys/i386/conf; PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin config -d /usr/obj/usr/src/sys/C456086-A C456086-A C456086-A: unknown option "USER_LDT" *** Error code 1 root[224 find /sys/ -type f | xargs grep USER_LDT /sys/i386/conf/C456086-A:options USER_LDT #allow user-level control of i386 ldt /sys/i386/i386/swtch.s.orig:#ifdef USER_LDT /sys/i386/linux/linux_machdep.c: printf("linux: modify_ldt needs kernel option USER_LDT\n"); /sys/i386/svr4/svr4_machdep.c:#if 0 /* USER_LDT */ /sys/i386/svr4/svr4_machdep.c:#if 0 /* USER_LDT */ /sys/i386/svr4/svr4_machdep.c:#warning "USER_LDT doesn't work - are you sure you want this?" /sys/modules/svr4/TO-DO: * VM86 and USER_LDT are currently disabled (low-priority) So, is USER_LDT no longer needed, and will wine work? -- steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 21:37:38 2001 Delivered-To: freebsd-current@freebsd.org Received: from isris.pair.com (isris.pair.com [209.68.2.39]) by hub.freebsd.org (Postfix) with SMTP id B5A9237B491 for ; Thu, 22 Feb 2001 21:37:36 -0800 (PST) (envelope-from rooneg@isris.pair.com) Received: (qmail 87877 invoked by uid 3130); 23 Feb 2001 05:37:35 -0000 Date: Fri, 23 Feb 2001 00:37:35 -0500 From: Garrett Rooney To: "Steven G. Kargl" Cc: freebsd-current@freebsd.org Subject: Re: USER_LDT gone? Message-ID: <20010223003735.A83651@electricjellyfish.net> References: <200102222134.f1MLYF545604@C456086-A.bllvu1.wa.home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200102222134.f1MLYF545604@C456086-A.bllvu1.wa.home.com>; from kargl@C456086-A.bllvu1.wa.home.com on Thu, Feb 22, 2001 at 09:34:12PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 22, 2001 at 09:34:12PM +0000, Steven G. Kargl wrote: > With the great libc debacle of 2001, I have not tried > to update my system for about 2 weeks. In that time I > may have missed the commit message that said that USER_LDT, which was needed > for at least wine, was removed. according to the commit message i saw, it is now turned on by default, so the next gen pthreads libs can use it. -- garrett rooney Unix was not designed to stop you from rooneg@electricjellyfish.net doing stupid things, because that would http://electricjellyfish.net/ stop you from doing clever things. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 21:39:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id D8FB437B401 for ; Thu, 22 Feb 2001 21:39:52 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f1N5dpM08819; Thu, 22 Feb 2001 21:39:51 -0800 (PST) Date: Thu, 22 Feb 2001 21:39:51 -0800 From: Alfred Perlstein To: "Steven G. Kargl" Cc: freebsd-current@FreeBSD.ORG Subject: Re: USER_LDT gone? Message-ID: <20010222213951.A8663@fw.wintelcom.net> References: <200102222134.f1MLYF545604@C456086-A.bllvu1.wa.home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200102222134.f1MLYF545604@C456086-A.bllvu1.wa.home.com>; from kargl@C456086-A.bllvu1.wa.home.com on Thu, Feb 22, 2001 at 09:34:12PM +0000 X-all-your-base: are belong to us. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Steven G. Kargl [010222 21:35] wrote: > With the great libc debacle of 2001, I have not tried > to update my system for about 2 weeks. In that time I > may have missed the commit message that said that USER_LDT, which was needed > for at least wine, was removed. Why are you using -current and not reading commit messages? :P Peter Wemm made it the default and it's no longer optional. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 21:46:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id 21E8A37B401 for ; Thu, 22 Feb 2001 21:46:31 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.11.2/8.11.2) id f1N5kOt08213; Thu, 22 Feb 2001 21:46:24 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <200102230546.f1N5kOt08213@troutmask.apl.washington.edu> Subject: Re: USER_LDT gone? In-Reply-To: <20010222213951.A8663@fw.wintelcom.net> from Alfred Perlstein at "Feb 22, 2001 09:39:51 pm" To: Alfred Perlstein Date: Thu, 22 Feb 2001 21:46:24 -0800 (PST) Cc: "Steven G. Kargl" , freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > * Steven G. Kargl [010222 21:35] wrote: > > With the great libc debacle of 2001, I have not tried > > to update my system for about 2 weeks. In that time I > > may have missed the commit message that said that USER_LDT, which was needed > > for at least wine, was removed. > > Why are you using -current and not reading commit messages? :P > > Peter Wemm made it the default and it's no longer optional. > I do read the commit messages, but I don't remember one about USER_LDT. A search of the mailing list archive at www.freebsd.org didn't turn up an obvious commit. PS: I've been running current longer than you have been involved in the project. Yes, I had 386BSD 0.0 floppy disk until I tossed them because the floppy were damaged. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 21:53:20 2001 Delivered-To: freebsd-current@freebsd.org Received: from ohm.physics.purdue.edu (ohm.physics.purdue.edu [128.210.146.32]) by hub.freebsd.org (Postfix) with ESMTP id 1055537B503 for ; Thu, 22 Feb 2001 21:53:18 -0800 (PST) (envelope-from will@physics.purdue.edu) Received: (from will@localhost) by ohm.physics.purdue.edu (8.9.3/8.9.3) id AAA81029; Fri, 23 Feb 2001 00:53:09 -0500 (EST) (envelope-from will@physics.purdue.edu) X-Authentication-Warning: ohm.physics.purdue.edu: will set sender to will@physics.purdue.edu using -f Date: Fri, 23 Feb 2001 00:53:09 -0500 From: Will Andrews To: Steve Kargl Cc: Alfred Perlstein , "Steven G. Kargl" , freebsd-current@FreeBSD.ORG Subject: Re: USER_LDT gone? Message-ID: <20010223005308.Z1163@ohm.physics.purdue.edu> Reply-To: Will Andrews References: <20010222213951.A8663@fw.wintelcom.net> <200102230546.f1N5kOt08213@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="wiiWofWi8Et/oezL" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200102230546.f1N5kOt08213@troutmask.apl.washington.edu>; from sgk@troutmask.apl.washington.edu on Thu, Feb 22, 2001 at 09:46:24PM -0800 X-Operating-System: FreeBSD 4.1-RELEASE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --wiiWofWi8Et/oezL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Feb 22, 2001 at 09:46:24PM -0800, Steve Kargl wrote: > I do read the commit messages, but I don't remember one about > USER_LDT. A search of the mailing list archive at www.freebsd.org > didn't turn up an obvious commit. It was committed less than 2 hours ago. > PS: I've been running current longer than you have been involved > in the project. Yes, I had 386BSD 0.0 floppy disk until I=20 > tossed them because the floppy were damaged. Girls, girls, let's not get in a piss-war here. :) --=20 wca --wiiWofWi8Et/oezL Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.3 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6lfrEF47idPgWcsURAjk0AKCPx0KSzNxwvBHQz1bCiO2dHZbM4wCdHCmo WN47wcTpTpbQRTGjIfiFYB0= =i58o -----END PGP SIGNATURE----- --wiiWofWi8Et/oezL-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 21:55: 7 2001 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id CF7EA37B4EC for ; Thu, 22 Feb 2001 21:55:04 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.11.2/8.11.2) id f1N5svl08291; Thu, 22 Feb 2001 21:54:57 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <200102230554.f1N5svl08291@troutmask.apl.washington.edu> Subject: Re: USER_LDT gone? In-Reply-To: <20010223005308.Z1163@ohm.physics.purdue.edu> from Will Andrews at "Feb 23, 2001 00:53:09 am" To: Will Andrews Date: Thu, 22 Feb 2001 21:54:57 -0800 (PST) Cc: Alfred Perlstein , "Steven G. Kargl" , freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Will Andrews wrote: > On Thu, Feb 22, 2001 at 09:46:24PM -0800, Steve Kargl wrote: > > I do read the commit messages, but I don't remember one about > > USER_LDT. A search of the mailing list archive at www.freebsd.org > > didn't turn up an obvious commit. > > It was committed less than 2 hours ago. > Actually, 4 hours :-) I won't see this commit message until tomorrow. Revision 1.146 / (download) - annotate - [select for diffs], Fri Feb 23 01:24:59 2001 UTC (4 hours, 24 minutes ago) by peter Branch: MAIN CVS Tags: HEAD Changes since 1.145: +1 -2 lines Diff to previous 1.145 (colored) Activate USER_LDT by default. The new thread libraries are going to depend on this. The linux ABI emulator tries to use it for some linux binaries too. VM86 had a bigger cost than this and it was made default a while ago. Reviewed by: jhb, imp -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 22:19:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from tomts7-srv.bellnexxia.net (tomts7.bellnexxia.net [209.226.175.40]) by hub.freebsd.org (Postfix) with ESMTP id 10FE437B491 for ; Thu, 22 Feb 2001 22:19:49 -0800 (PST) (envelope-from kfarmer@sympatico.ca) Received: from tristal ([209.226.117.14]) by tomts7-srv.bellnexxia.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with SMTP id <20010223061947.OFFQ757.tomts7-srv.bellnexxia.net@tristal> for ; Fri, 23 Feb 2001 01:19:47 -0500 Message-ID: <000701c09d60$b23f7ba0$0100a8c0@sympatico.ca> From: "Kelvin Farmer" To: Subject: known problem with certain programs freezing in state "poll"? Date: Fri, 23 Feb 2001 01:20:12 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just wondering if the following is a known problem, or if I can provide any more useful info? After updating from a pre-Feb 10 current, i'm now seeing Licq freezing on exit, with top showing it to be in state "poll". (and has to be kill'ed to exit it) Xmms is worse, after playing an mp3 for a short while, FreeBSD freezes solid, (no panic) top running in another window shows it to be in state "poll" when this happens. Cheers Kelvin. Kfarmer@sympatico.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 22:26:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from cnrcimc1.cnrc.navy.mil (mail0.cnrc.navy.mil [138.141.100.73]) by hub.freebsd.org (Postfix) with ESMTP id 20B0D37B6A6 for ; Thu, 22 Feb 2001 22:26:28 -0800 (PST) (envelope-from sysad2_la@cnrc.navy.mil) Received: by mail0.cnrc.navy.mil with Internet Mail Service (5.5.2653.19) id ; Fri, 23 Feb 2001 00:25:16 -0600 Message-ID: <1326C56882DED211A3E50008C75D2CD2885DE9@mail2.cnrc.navy.mil> From: sysad2_la To: "'current@freebsd.org'" Subject: unsubscribe Date: Fri, 23 Feb 2001 00:25:08 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG unsubscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 23:32:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from lamborghini.indocyber.com (lamborghini.indocyber.com [202.180.0.86]) by hub.freebsd.org (Postfix) with SMTP id 94D8637B491 for ; Thu, 22 Feb 2001 23:32:33 -0800 (PST) (envelope-from john@office.naver.co.id) Received: (qmail 2783 invoked from network); 23 Feb 2001 07:27:03 -0000 Received: from unknown (HELO dante.naver.co.id) (postfix@202.155.86.83) by lamborghini.indocyber.com with SMTP; 23 Feb 2001 07:27:03 -0000 Received: by dante.naver.co.id (Postfix, from userid 1000) id 3F8F5BDEAA; Fri, 23 Feb 2001 14:03:24 +0700 (JAVT) Date: Fri, 23 Feb 2001 14:03:24 +0700 From: John Indra To: freebsd-current@freebsd.org Subject: How is -CURRENT? Message-ID: <20010223140324.A55387@office.naver.co.id> Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Mailer: Mutt 1.2.5i on FreeBSD 5.0-20010210-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks... Now I am running 20010210-CURRENT. I was wondering, how is the state of -CURRENT? I've checked current.freebsd.org, but there are no newer snapshots than 20010210. Is it safe to make world right now? Do KDE2 apps work flawlessly on newest -CURRENT? If there are people that can say yes to that answer, than I am ready to blow away all my /usr/X11R6 and /usr/local and build everything from scratch, thank you... /john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 23:36:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id A353637B491 for ; Thu, 22 Feb 2001 23:36:41 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f1N7adB11809; Thu, 22 Feb 2001 23:36:39 -0800 (PST) Date: Thu, 22 Feb 2001 23:36:39 -0800 From: Alfred Perlstein To: Steve Kargl Cc: "Steven G. Kargl" , freebsd-current@FreeBSD.ORG Subject: Re: USER_LDT gone? Message-ID: <20010222233639.B8663@fw.wintelcom.net> References: <20010222213951.A8663@fw.wintelcom.net> <200102230546.f1N5kOt08213@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200102230546.f1N5kOt08213@troutmask.apl.washington.edu>; from sgk@troutmask.apl.washington.edu on Thu, Feb 22, 2001 at 09:46:24PM -0800 X-all-your-base: are belong to us. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Steve Kargl [010222 21:46] wrote: > Alfred Perlstein wrote: > > * Steven G. Kargl [010222 21:35] wrote: > > > With the great libc debacle of 2001, I have not tried > > > to update my system for about 2 weeks. In that time I > > > may have missed the commit message that said that USER_LDT, which was needed > > > for at least wine, was removed. > > > > Why are you using -current and not reading commit messages? :P > > > > Peter Wemm made it the default and it's no longer optional. > > > > I do read the commit messages, but I don't remember one about > USER_LDT. A search of the mailing list archive at www.freebsd.org > didn't turn up an obvious commit. > > PS: I've been running current longer than you have been involved > in the project. Yes, I had 386BSD 0.0 floppy disk until I > tossed them because the floppy were damaged. Hence the ":P". :) -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 22 23:40:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id DCAB837B503 for ; Thu, 22 Feb 2001 23:40:49 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f1N7emh11966; Thu, 22 Feb 2001 23:40:48 -0800 (PST) Date: Thu, 22 Feb 2001 23:40:48 -0800 From: Alfred Perlstein To: Kelvin Farmer Cc: freebsd-current@FreeBSD.ORG Subject: Re: known problem with certain programs freezing in state "poll"? Message-ID: <20010222234048.C8663@fw.wintelcom.net> References: <000701c09d60$b23f7ba0$0100a8c0@sympatico.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <000701c09d60$b23f7ba0$0100a8c0@sympatico.ca>; from kfarmer@sympatico.ca on Fri, Feb 23, 2001 at 01:20:12AM -0500 X-all-your-base: are belong to us. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Kelvin Farmer [010222 22:20] wrote: > > Just wondering if the following is a known problem, or if I can provide any > more useful info? > After updating from a pre-Feb 10 current, i'm now seeing Licq freezing on > exit, with top showing it to be in state "poll". (and has to be kill'ed to > exit it) > Xmms is worse, after playing an mp3 for a short while, FreeBSD freezes > solid, (no panic) top running in another window shows it to be in state > "poll" when this happens. There was a patch committed a couple of hours ago that ought to fix this. You should cvsup then rebuild and reinstall libc and libc_r. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 0:26:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id E982037B491; Fri, 23 Feb 2001 00:26:05 -0800 (PST) (envelope-from keichii@peorth.iteration.net) Received: by peorth.iteration.net (Postfix, from userid 1001) id 35FDC59525; Fri, 23 Feb 2001 02:26:16 -0600 (CST) Date: Fri, 23 Feb 2001 02:26:16 -0600 From: "Michael C . Wu" To: current@freebsd.org Cc: fs@freebsd.org Subject: FFS snapshot with today's CURRENT freezes and reboots. Message-ID: <20010223022616.A28598@peorth.iteration.net> Reply-To: "Michael C . Wu" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, I hate to do an 'as title' post. However, I did a make world about 6 hours ago. And when I execute mount snapshot -u -o /xxx/snap1 /xxx The machine always freezes for about 15 seconds and reboots without warning. This is a Sony VAIO laptop z505js with ATA disk. (if that is even of relevance). Since I discovered the problem at 1am, I really have no other debug information to be put up, just a heads up. I am wondering if this is just me, or is anybody having the same problem? If this problem is repeatable for others, I'll generate a bug report that will make Bill Paul smile. :) -- +------------------------------------------------------------------+ | keichii@peorth.iteration.net | keichii@bsdconspiracy.net | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 0:59: 1 2001 Delivered-To: freebsd-current@freebsd.org Received: from updraft.jp.freebsd.org (updraft.jp.FreeBSD.ORG [210.157.158.42]) by hub.freebsd.org (Postfix) with ESMTP id 1F74E37B503; Fri, 23 Feb 2001 00:58:59 -0800 (PST) (envelope-from matusita@jp.FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by updraft.jp.freebsd.org (8.11.2+3.4W/8.11.1/smtpfeed 1.11) with ESMTP/inet id f1N8wgW77951; Fri, 23 Feb 2001 17:58:43 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) Cc: jhay@icomtek.csir.co.za, kuriyama@imgsrc.co.jp (Jun Kuriyama), n@nectar.com (Jacques A. Vidrine), markm@FreeBSD.ORG (Mark Murray), current@FreeBSD.ORG In-Reply-To: <200102211348.f1LDmIX17944@zibbi.icomtek.csir.co.za> References: <5lu25oqi7h.fsf@assaris.sics.se> <200102211348.f1LDmIX17944@zibbi.icomtek.csir.co.za> X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V X-User-Agent: Mew/1.94.2 XEmacs/21.2 (Poseidon) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 30 From: Makoto MATSUSHITA To: assar@FreeBSD.ORG (Assar Westerlund) Subject: Re: Building procedure of krb5 is broken Date: Fri, 23 Feb 2001 17:58:21 +0900 Message-Id: <20010223175821T.matusita@jp.FreeBSD.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG jhay> Ahhhh, maybe this will also fix "make release". It has been jhay> dying in the kerberos area the last few days. Unfortunately, it does NOT fix "make release" breakage (already reported by kuriyama-san). I've checked why, and make a patch to fix this. --- src/kerberos5/lib/libgssapi/Makefile.dist Wed Feb 14 01:56:50 2001 +++ src/kerberos5/lib/libgssapi/Makefile Fri Feb 23 17:32:26 2001 @@ -7,7 +7,8 @@ -I${KRB5DIR}/lib/roken \ -I${KRB5DIR}/lib/des \ -I${KRB5DIR}/include \ - -I${ASN1OBJDIR} + -I${ASN1OBJDIR} \ + -I${KRB5OBJDIR} SRCS= \ 8003.c \ Some header files of libgssapi require krb5_err.h but there is no krb5_err.h in source repository. krb5_err.h only lives under /usr/obj, since krb5_err.h is *generated* from krb5_err.et. Adding -I${KRB5OBJDIR} should fix the problem. If you want to reproduce what's the problem, try: cd /usr/src/kerberos5; make bootstrap -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 2:10:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from tao.org.uk (genesis.tao.org.uk [194.242.131.94]) by hub.freebsd.org (Postfix) with ESMTP id 86DF537B401 for ; Fri, 23 Feb 2001 02:10:03 -0800 (PST) (envelope-from joe@tao.org.uk) Received: by tao.org.uk (Postfix, from userid 100) id A7F17311F; Thu, 22 Feb 2001 08:24:06 +0000 (GMT) Date: Thu, 22 Feb 2001 08:24:06 +0000 From: Josef Karthauser To: Kirk McKusick , current@freebsd.org Subject: Re: Problems syncing disks in recent -current (since 19th) Message-ID: <20010222082406.B535@tao.org.uk> Mail-Followup-To: Josef Karthauser , Kirk McKusick , current@freebsd.org References: <20010221215522.D2022@tao.org.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="LpQ9ahxlCli8rRTG" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010221215522.D2022@tao.org.uk>; from joe@tao.org.uk on Wed, Feb 21, 2001 at 09:55:22PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --LpQ9ahxlCli8rRTG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Feb 21, 2001 at 09:55:22PM +0000, Josef Karthauser wrote: > Hi Kirk, >=20 > A number of us have problem reliably syncing disks with softupdates in > recent -current from about the 19th. Is it possible that you broke > something with your recent commit? I forgot to mention that the syncing problem is when the O/S is being shutdown; not syncing in general. We get a 'syncing buffers: 15 15 15 15 15 15 15 15 15 ', etc, until it gives up. Regards, Joe. --LpQ9ahxlCli8rRTG Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjqUzKUACgkQXVIcjOaxUBaV2gCcDbe/zRIgTkZk/aED7HRlgGnG StcAoOgCOMAzXqib591cN6MxY6oHtzvs =hNue -----END PGP SIGNATURE----- --LpQ9ahxlCli8rRTG-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 4:33:18 2001 Delivered-To: freebsd-current@freebsd.org Received: from webcom.it (brian.inet.it [213.92.4.195]) by hub.freebsd.org (Postfix) with SMTP id D97FE37B491 for ; Fri, 23 Feb 2001 04:33:13 -0800 (PST) (envelope-from andrea@webcom.it) Received: (qmail 1132 invoked by uid 1000); 22 Feb 2001 21:40:50 -0000 Date: Thu, 22 Feb 2001 22:40:50 +0100 From: Andrea Campi To: Kris Kennaway Cc: freebsd-current@freebsd.org Subject: [Solved] Re: -CURRENT slowdown in last 2 weeks Message-ID: <20010222224049.A1105@webcom.it> References: <20010220015012.B5116@webcom.it> <20010222130156.A6818@mollari.cthul.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010222130156.A6818@mollari.cthul.hu>; from kris@obsecurity.org on Thu, Feb 22, 2001 at 01:01:56PM -0800 X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Do you have MUTEX_DEBUG in your kernel? > Sorry guys, my bad. As John and Kris reminded me, the slowdown was because of this - should have checked again the archive, I remember it had been mentioned before. Bye, Andrea -- It is easier to fix Unix than to live with NT. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 4:37:25 2001 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 659C737B491 for ; Fri, 23 Feb 2001 04:37:23 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.2/8.11.1) id f1NCbG004308; Fri, 23 Feb 2001 04:37:16 -0800 (PST) (envelope-from obrien) Date: Fri, 23 Feb 2001 04:37:16 -0800 From: "David O'Brien" To: Matthew Jacob Cc: current@freebsd.org Subject: Re: dirty buffers on reboot again? Message-ID: <20010223043716.E2539@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from mjacob@feral.com on Thu, Feb 22, 2001 at 03:20:10PM -0800 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 22, 2001 at 03:20:10PM -0800, Matthew Jacob wrote: > login: (da0:ahc0:0:0:0): tagged openings now 16 ... > syncing disks... 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 > giving up on 3 buffers ... > I'm seeing a lot of this again. Anyone else? Yep. ahc controller also. By chance is that the commonality to this problem? -- -- David (obrien@FreeBSD.org) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 4:45:48 2001 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 6163537B65D; Fri, 23 Feb 2001 04:45:45 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id NAA25884; Fri, 23 Feb 2001 13:45:21 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200102231245.NAA25884@freebsd.dk> Subject: Re: dirty buffers on reboot again?' In-Reply-To: <20010223043716.E2539@dragon.nuxi.com> from "David O'Brien" at "Feb 23, 2001 04:37:16 am" To: obrien@FreeBSD.ORG Date: Fri, 23 Feb 2001 13:45:21 +0100 (CET) Cc: mjacob@feral.com (Matthew Jacob), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems David O'Brien wrote: > On Thu, Feb 22, 2001 at 03:20:10PM -0800, Matthew Jacob wrote: > > login: (da0:ahc0:0:0:0): tagged openings now 16 > ... > > syncing disks... 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 > > giving up on 3 buffers > ... > > I'm seeing a lot of this again. Anyone else? > > Yep. ahc controller also. By chance is that the commonality to this > problem? No, its generically broken... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 4:56:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from mta5.snfc21.pbi.net (mta5.snfc21.pbi.net [206.13.28.241]) by hub.freebsd.org (Postfix) with ESMTP id 4999337B401 for ; Fri, 23 Feb 2001 04:56:50 -0800 (PST) (envelope-from jazepeda@pacbell.net) Received: from zippy.pacbell.net ([207.214.149.128]) by mta5.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0G97003SCNP7LS@mta5.snfc21.pbi.net> for current@freebsd.org; Fri, 23 Feb 2001 04:51:08 -0800 (PST) Received: by zippy.pacbell.net (Postfix, from userid 1000) id A39731826; Fri, 23 Feb 2001 04:50:37 -0800 (PST) Date: Fri, 23 Feb 2001 04:50:37 -0800 From: Alex Zepeda Subject: Re: How is -CURRENT? In-reply-to: <20010223140324.A55387@office.naver.co.id>; from john@office.naver.co.id on Fri, Feb 23, 2001 at 02:03:24PM +0700 To: current@freebsd.org Message-id: <20010223045037.A547@zippy.mybox.zip> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <20010223140324.A55387@office.naver.co.id> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Feb 23, 2001 at 02:03:24PM +0700, John Indra wrote: > Is it safe to make world right now? Do KDE2 apps work flawlessly on newest > -CURRENT? If there are people that can say yes to that answer, than I am > ready to blow away all my /usr/X11R6 and /usr/local and build everything > from scratch, thank you... Define flawlessly? I haven't noticed any problems yet with KDE2, other than the usual mixing of threaded and non threaded (that glorious hack called mpeglib, and mpeglib_artsplug) bits breaking arts.. grr. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 7:11:55 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id A10D237B401; Fri, 23 Feb 2001 07:11:52 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id HAA25512; Fri, 23 Feb 2001 07:11:52 -0800 Date: Fri, 23 Feb 2001 07:11:51 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "David O'Brien" Cc: current@FreeBSD.ORG Subject: Re: dirty buffers on reboot again? In-Reply-To: <20010223043716.E2539@dragon.nuxi.com> 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 Hmm... Good question. On Fri, 23 Feb 2001, David O'Brien wrote: > On Thu, Feb 22, 2001 at 03:20:10PM -0800, Matthew Jacob wrote: > > login: (da0:ahc0:0:0:0): tagged openings now 16 > ... > > syncing disks... 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 > > giving up on 3 buffers > ... > > I'm seeing a lot of this again. Anyone else? > > Yep. ahc controller also. By chance is that the commonality to this > problem? > > -- > -- David (obrien@FreeBSD.org) > GNU is Not Unix / Linux Is Not UniX > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 7:14:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from volatile.chemikals.org (ci391991-a.grnvle1.sc.home.com [24.6.40.144]) by hub.freebsd.org (Postfix) with ESMTP id 11F1937B67D; Fri, 23 Feb 2001 07:14:49 -0800 (PST) (envelope-from morganw@chemikals.org) Received: (from morganw@localhost) by volatile.chemikals.org (8.11.2/8.11.1) id f1NFEbY96344; Fri, 23 Feb 2001 10:14:37 -0500 (EST) (envelope-from morganw) Date: Fri, 23 Feb 2001 10:14:37 -0500 (EST) From: Wesley Morgan To: Matthew Jacob Cc: "David O'Brien" , Subject: Re: dirty buffers on reboot again? In-Reply-To: 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 Not here. Just using ad and friends. On Fri, 23 Feb 2001, Matthew Jacob wrote: > > Hmm... Good question. > > On Fri, 23 Feb 2001, David O'Brien wrote: > > > On Thu, Feb 22, 2001 at 03:20:10PM -0800, Matthew Jacob wrote: > > > login: (da0:ahc0:0:0:0): tagged openings now 16 > > ... > > > syncing disks... 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 > > > giving up on 3 buffers > > ... > > > I'm seeing a lot of this again. Anyone else? > > > > Yep. ahc controller also. By chance is that the commonality to this > > problem? > > > > -- > > -- David (obrien@FreeBSD.org) > > GNU is Not Unix / Linux Is Not UniX > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- _ __ ___ ____ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ morganw@chemikals.org _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 7:42:42 2001 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 8748637B491; Fri, 23 Feb 2001 07:42:36 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p10-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.139]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id AAA19002; Sat, 24 Feb 2001 00:42:34 +0900 (JST) Message-ID: <3A968441.D66F6D5F@newsguy.com> Date: Sat, 24 Feb 2001 00:39:45 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: obrien@FreeBSD.ORG Cc: Matthew Jacob , current@FreeBSD.ORG Subject: Re: dirty buffers on reboot again? References: <20010223043716.E2539@dragon.nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien wrote: > > On Thu, Feb 22, 2001 at 03:20:10PM -0800, Matthew Jacob wrote: > > login: (da0:ahc0:0:0:0): tagged openings now 16 > ... > > syncing disks... 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 > > giving up on 3 buffers > ... > > I'm seeing a lot of this again. Anyone else? > > Yep. ahc controller also. By chance is that the commonality to this > problem? MMmmmmm... I have an aic, though I'm fairly certain I got unsynced buffers on ide. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@kzinti.bsdconspiracy.net Acabou o hipismo-arte. Mas a desculpa brasileira mais ouvida em Sydney e' que nao tem mais cavalo bobo por ai'. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 8:35:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from VL-MS-MR001.sc1.videotron.ca (relais.videotron.ca [24.201.245.36]) by hub.freebsd.org (Postfix) with ESMTP id 343C337B503 for ; Fri, 23 Feb 2001 08:35:52 -0800 (PST) (envelope-from amyfoub@videotron.ca) Received: from guillaume ([24.200.37.38]) by VL-MS-MR001.sc1.videotron.ca (Netscape Messaging Server 4.15) with SMTP id G97Y3Q01.F2G for ; Fri, 23 Feb 2001 11:35:50 -0500 Message-ID: <005101c09db6$62e94f80$0a0110ac@guillaume> From: "Guillaume" To: Subject: unknown: can't assign resources Date: Fri, 23 Feb 2001 11:33:42 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I'm running FreeBSD 5.0-CURRENT since 2 days. When I boot FreeBSD I get this error: Feb 22 23:21:13 unix /boot/kernel/kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Feb 22 23:21:13 unix /boot/kernel/kernel: unknown: can't assign resources Feb 22 23:21:13 unix /boot/kernel/kernel: unknown: can't assign resources Feb 22 23:21:13 unix /boot/kernel/kernel: unknown: can't assign resources Feb 22 23:21:13 unix /boot/kernel/kernel: unknown: can't assign resources Feb 22 23:21:13 unix /boot/kernel/kernel: unknown: can't assign resources What is that and how can I fix this error? Guillaume amyfoub@videotron.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 9:30:18 2001 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.icomtek.csir.co.za (zibbi.icomtek.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 6AE6237B491; Fri, 23 Feb 2001 09:30:10 -0800 (PST) (envelope-from jhay@zibbi.icomtek.csir.co.za) Received: (from jhay@localhost) by zibbi.icomtek.csir.co.za (8.11.1/8.11.1) id f1NHTv190734; Fri, 23 Feb 2001 19:29:57 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200102231729.f1NHTv190734@zibbi.icomtek.csir.co.za> Subject: Re: Release b0rked.. (libgssapi) In-Reply-To: <200102230429.f1N4TN172703@zibbi.icomtek.csir.co.za> from John Hay at "Feb 23, 2001 06:29:23 am" To: assar@FreeBSD.ORG Date: Fri, 23 Feb 2001 19:29:57 +0200 (SAT) Cc: jhb@FreeBSD.ORG (John Baldwin), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It looks like I was wrong. This patch fix a "make release" for me. The other problems must have been fixed with the other krb fixes over the past few days. Any reason not to commit it? John -- John Hay -- John.Hay@icomtek.csir.co.za > > ===> lib/libgssapi > > rm -f .depend > > mkdep -f .depend -a > ... > > /usr/src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/krb5/krb5.h:43: > > krb5_err.h: No such file or directory > > /usr/src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/krb5/krb5.h:44: > > heim_err.h: No such file or directory > > You can get past this error with this patch, but it will just die a little > later in another part of kerberos. You should have better luck by building > a release with NOKERBEROS=YES. I was able to build one yesterday. > > John > -- > John Hay -- John.Hay@icomtek.csir.co.za > > > Index: kerberos5/lib/libgssapi/Makefile > =================================================================== > RCS file: /home/ncvs/src/kerberos5/lib/libgssapi/Makefile,v > retrieving revision 1.1 > diff -u -r1.1 Makefile > --- kerberos5/lib/libgssapi/Makefile 2001/02/13 16:56:50 1.1 > +++ kerberos5/lib/libgssapi/Makefile 2001/02/17 15:13:38 > @@ -7,7 +7,8 @@ > -I${KRB5DIR}/lib/roken \ > -I${KRB5DIR}/lib/des \ > -I${KRB5DIR}/include \ > - -I${ASN1OBJDIR} > + -I${ASN1OBJDIR} \ > + -I${KRB5OBJDIR} > > SRCS= \ > 8003.c \ > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 9:44:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from syncopation-01.iinet.net.au (syncopation-01.iinet.net.au [203.59.24.37]) by hub.freebsd.org (Postfix) with SMTP id 79ED737B4EC for ; Fri, 23 Feb 2001 09:44:15 -0800 (PST) (envelope-from julian@elischer.org) Received: (qmail 16367 invoked by uid 666); 23 Feb 2001 17:55:41 -0000 Received: from i080-250.nv.iinet.net.au (HELO elischer.org) (203.59.80.250) by mail.m.iinet.net.au with SMTP; 23 Feb 2001 17:55:41 -0000 Message-ID: <3A96A14B.EC358111@elischer.org> Date: Fri, 23 Feb 2001 09:43:39 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Guillaume Cc: freebsd-current@freebsd.org Subject: Re: unknown: can't assign resources References: <005101c09db6$62e94f80$0a0110ac@guillaume> Content-Type: multipart/mixed; boundary="------------3D9775A515A540D3E431EDB0" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------3D9775A515A540D3E431EDB0 Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Guillaume wrote: > > Hello, > > I'm running FreeBSD 5.0-CURRENT since 2 days. > > When I boot FreeBSD I get this error: > > Feb 22 23:21:13 unix /boot/kernel/kernel: vga0: at port > 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > Feb 22 23:21:13 unix /boot/kernel/kernel: unknown: can't assign > resources > Feb 22 23:21:13 unix /boot/kernel/kernel: unknown: can't assign > resources > Feb 22 23:21:13 unix /boot/kernel/kernel: unknown: can't assign > resources > Feb 22 23:21:13 unix /boot/kernel/kernel: unknown: can't assign > resources > Feb 22 23:21:13 unix /boot/kernel/kernel: unknown: can't assign > resources > > What is that and how can I fix this error? The BIOS's PNP table i sreporting devices that you are also mentionning in either your kernel config hints file, or in /boot/device.hints. (or maybe even PCI devices). In either case, the one you mention in your config gets allocated the ports and interrupts etc. so when the kernel tries to allocate them for the PNP device, it can't. Since they are refering to the same device, this doesn;t matter, in fact it's good. (Or you'd have two driver instances pointing at teh same hardware). if you remove the entries in /boot/device.hints that refer to the same device, and let the PNP table be used instead to attach drivers (for those that are recognised) you'll get less of these. Msmith mailed me a PNP device list. I include it here for your assistance in identifying these. > > Guillaume > amyfoub@videotron.ca > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v --------------3D9775A515A540D3E431EDB0 Content-Type: text/plain; charset=iso-8859-15; name="devids.txt" Content-Transfer-Encoding: 8bit Content-Disposition: inline; filename="devids.txt" This document is the ultimate source for Windows Generic Device IDs and Plug and Play BIOS device type codes. CONTENTS: Plug and Play Vendor IDs and Device IDs Generic Device IDs Device Type Codes ====================================================================== PLUG AND PLAY VENDOR IDs AND DEVICE IDs All non-BIOS enumerated devices must not use "PNP" in their Vendor and Device codes. The vendor must register with EISA and have a vendor code assigned (for example, CTL for Creative Labs). The "PNP" vendor code is reserved for Microsoft and can only be used when defining a device’s CompatibleID after indicating the device’s HardwareID in the Plug and Play header. Use of CompatibleIDs is strongly recommended for devices that use device drivers provided with Microsoft Windows 95, such as a "Standard PC COM Port" (PNP0500) or "Sound Blaster 16 Sound Device" (PNPB003). The following example output from ISOLATE.EXE of a Plug and Play header is provided for your reference: Vendor ID: XXXFFFF Serial Number: 00000001 Checksum (reported): 0x5E PNP Version: 1.0 Vendor Ver.: 10 Device Description: IDE Port Device ID: XXX0001 Doesn't Support I/O Range Checking Vendor Defined Logical Device Control Registers: None Compatible Device ID: PNP0600 Device Description: IDE Dependent Function 0 ... Dependent Function 1 ... End of Dependent Functions When the user is installing devices that use this method, a dialog box appears at the beginning of the enumeration sequence to suggest use of the default driver provided with Windows 95. Windows 95 also provides the option for using a disk from the manufacturer, in case the user wants to choose a manufacturer-supplied driver. For multifunction adapters, you should supply an INF file that chooses the appropriate drivers (including default drivers) for all the adapter’s devices. This prevents additional dialog boxes from again requesting the default driver or a manufacture’s disk for the rest of the devices on the adapter. When an INF file is used in this manner for default driver selection, it must link the HardwareID (XXX0000) to the appropriate compatible device driver from the Windows 95 distribution compact disc or installation disks. If this is not done, Windows 95 will continue to query the user for either the default driver or a new driver, thus defeating the purpose of using the INF file in this way. ====================================================================== WINDOWS GENERIC DEVICE IDs ---------------------------------------------------------------------- Many devices have no standard EISA ID, such as the interrupt controller or keyboard controller. Also, a set of compatible devices, such as VGA and Super VGA, are not actually devices, but define a compatibility hardware subset. Yet another set of IDs needs to be used to identify buses. Microsoft has reserved an EISA prefix of "PNP" to identify various devices that do not have an existing EISA ID, as well as defining compatibility devices. The IDs are defined in the following tables. DEVICE ID RANGES ID range Category -------- ------------- PNP0xxx System devices PNP8xxx Network adapters PNPAxxx SCSI, proprietary CD adapters PNPBxxx Sound, video capture, multimedia PNPCxxx - Dxxx Modems The following device ID is provided only for compatibility with earlier device ID lists: Device ID Description -------- ------------- PNP0802 Microsoft Sound System-compatible device (obsolete; use PNPB0xx instead) --------------------------------------------------------------------------- Device ID Description -------- ------------- ***** System Devices - PNP0xxx ************************** --Interrupt Controllers-- PNP0000 AT Interrupt Controller PNP0001 EISA Interrupt Controller PNP0002 MCA Interrupt Controller PNP0003 APIC PNP0004 Cyrix SLiC MP interrupt controller --Timers-- PNP0100 AT Timer PNP0101 EISA Timer PNP0102 MCA Timer --DMA-- PNP0200 AT DMA Controller PNP0201 EISA DMA Controller PNP0202 MCA DMA Controller --Keyboards-- PNP0300 IBM PC/XT keyboard controller (83-key) PNP0301 IBM PC/AT keyboard controller (86-key) PNP0302 IBM PC/XT keyboard controller (84-key) PNP0303 IBM Enhanced (101/102-key, PS/2 mouse support) PNP0304 Olivetti Keyboard (83-key) PNP0305 Olivetti Keyboard (102-key) PNP0306 Olivetti Keyboard (86-key) PNP0307 Microsoft Windows(R) Keyboard PNP0308 General Input Device Emulation Interface (GIDEI) legacy PNP0309 Olivetti Keyboard (A101/102 key) PNP030A AT&T 302 keyboard PNP030B Reserved by Microsoft PNP0320 Japanese 106-key keyboard A01 PNP0321 Japanese 101-key keyboard PNP0322 Japanese AX keyboard PNP0323 Japanese 106-key keyboard 002/003 PNP0324 Japanese 106-key keyboard 001 PNP0325 Japanese Toshiba Desktop keyboard PNP0326 Japanese Toshiba Laptop keyboard PNP0327 Japanese Toshiba Notebook keyboard PNP0340 Korean 84-key keyboard PNP0341 Korean 86-key keyboard PNP0342 Korean Enhanced keyboard PNP0343 Korean Enhanced keyboard 101b PNP0343 Korean Enhanced keyboard 101c PNP0344 Korean Enhanced keyboard 103 --Parallel Devices-- PNP0400 Standard LPT printer port PNP0401 ECP printer port --Serial Devices-- PNP0500 Standard PC COM port PNP0501 16550A-compatible COM port PNP0502 Multiport serial device (non-intelligent 16550) PNP0510 Generic IRDA-compatible device PNP0511 Generic IRDA-compatible device --Disk Controllers-- PNP0600 Generic ESDI/IDE/ATA compatible hard disk controller PNP0601 Plus Hardcard II PNP0602 Plus Hardcard IIXL/EZ PNP0603 Generic IDE supporting Microsoft Device Bay Specification PNP0700 PC standard floppy disk controller PNP0701 Standard floppy controller supporting MS Device Bay Spec --Compatibility with early device ID list-- PNP0802 Microsoft Sound System compatible device (obsolete, use PNPB0xx instead) --Display Adapters-- PNP0900 VGA Compatible PNP0901 Video Seven VRAM/VRAM II/1024i PNP0902 8514/A Compatible PNP0903 Trident VGA PNP0904 Cirrus Logic Laptop VGA PNP0905 Cirrus Logic VGA PNP0906 Tseng ET4000 PNP0907 Western Digital VGA PNP0908 Western Digital Laptop VGA PNP0909 S3 Inc. 911/924 PNP090A ATI Ultra Pro/Plus (Mach 32) PNP090B ATI Ultra (Mach 8) PNP090C XGA Compatible PNP090D ATI VGA Wonder PNP090E Weitek P9000 Graphics Adapter PNP090F Oak Technology VGA PNP0910 Compaq QVision PNP0911 XGA/2 PNP0912 Tseng Labs W32/W32i/W32p PNP0913 S3 Inc. 801/928/964 PNP0914 Cirrus Logic 5429/5434 (memory mapped) PNP0915 Compaq Advanced VGA (AVGA) PNP0916 ATI Ultra Pro Turbo (Mach64) PNP0917 Reserved by Microsoft PNP0918 Matrox MGA PNP0919 Compaq QVision 2000 PNP091A Tseng W128 PNP0930 Chips & Technologies Super VGA PNP0931 Chips & Technologies Accelerator PNP0940 NCR 77c22e Super VGA PNP0941 NCR 77c32blt PNP09FF Plug and Play Monitors (VESA DDC) --Peripheral Buses-- PNP0A00 ISA Bus PNP0A01 EISA Bus PNP0A02 MCA Bus PNP0A03 PCI Bus PNP0A04 VESA/VL Bus PNP0A05 Generic ACPI Bus PNP0A06 Generic ACPI Extended-IO Bus (EIO bus) -- Real Time Clock, BIOS, System board devices-- PNP0800 AT-style speaker sound PNP0B00 AT Real-Time Clock PNP0C00 Plug and Play BIOS (only created by the root enumerator) PNP0C01 System Board PNP0C02 General ID for reserving resources required by Plug and Play motherboard registers. (Not specific to a particular device.) PNP0C03 Plug and Play BIOS Event Notification Interrupt PNP0C04 Math Coprocessor PNP0C05 APM BIOS (Version independent) PNP0C06 Reserved for identification of early Plug and Play BIOS implementation. PNP0C07 Reserved for identification of early Plug and Play BIOS implementation. PNP0C08 ACPI system board hardware PNP0C09 ACPI Embedded Controller PNP0C0A ACPI Control Method Battery PNP0C0B ACPI Fan PNP0C0C ACPI power button device PNP0C0D ACPI lid device PNP0C0E ACPI sleep button device PNP0C0F PCI interrupt link device PNP0C10 ACPI system indicator device PNP0C11 ACPI thermal zone PNP0C12 Device Bay Controller PNP0C13 Plug and Play BIOS (used when ACPI mode cannot be used) --PCMCIA Controller Chipsets-- PNP0E00 Intel 82365-Compatible PCMCIA Controller PNP0E01 Cirrus Logic CL-PD6720 PCMCIA Controller PNP0E02 VLSI VL82C146 PCMCIA Controller PNP0E03 Intel 82365-compatible CardBus controller --Mice-- PNP0F00 Microsoft Bus Mouse PNP0F01 Microsoft Serial Mouse PNP0F02 Microsoft InPort Mouse PNP0F03 Microsoft PS/2-style Mouse PNP0F04 Mouse Systems Mouse PNP0F05 Mouse Systems 3-Button Mouse (COM2) PNP0F06 Genius Mouse (COM1) PNP0F07 Genius Mouse (COM2) PNP0F08 Logitech Serial Mouse PNP0F09 Microsoft BallPoint Serial Mouse PNP0F0A Microsoft Plug and Play Mouse PNP0F0B Microsoft Plug and Play BallPoint Mouse PNP0F0C Microsoft-compatible Serial Mouse PNP0F0D Microsoft-compatible InPort-compatible Mouse PNP0F0E Microsoft-compatible PS/2-style Mouse PNP0F0F Microsoft-compatible Serial BallPoint-compatible Mouse PNP0F10 Texas Instruments QuickPort Mouse PNP0F11 Microsoft-compatible Bus Mouse PNP0F12 Logitech PS/2-style Mouse PNP0F13 PS/2 Port for PS/2-style Mice PNP0F14 Microsoft Kids Mouse PNP0F15 Logitech bus mouse PNP0F16 Logitech SWIFT device PNP0F17 Logitech-compatible serial mouse PNP0F18 Logitech-compatible bus mouse PNP0F19 Logitech-compatible PS/2-style Mouse PNP0F1A Logitech-compatible SWIFT Device PNP0F1B HP Omnibook Mouse PNP0F1C Compaq LTE Trackball PS/2-style Mouse PNP0F1D Compaq LTE Trackball Serial Mouse PNP0F1E Microsoft Kids Trackball Mouse PNP0F1F Reserved by Microsoft Input Device Group PNP0F20 Reserved by Microsoft Input Device Group PNP0F21 Reserved by Microsoft Input Device Group PNP0F22 Reserved by Microsoft Input Device Group PNP0F23 Reserved by Microsoft Input Device Group PNP0FFF Reserved by Microsoft Systems ***** Network Adapters - PNP8xxx *********************** PNP8001 Novell/Anthem NE3200 PNP8004 Compaq NE3200 PNP8006 Intel EtherExpress/32 PNP8008 HP EtherTwist EISA LAN Adapter/32 (HP27248A) PNP8065 Ungermann-Bass NIUps or NIUps/EOTP PNP8072 DEC (DE211) EtherWorks MC/TP PNP8073 DEC (DE212) EtherWorks MC/TP_BNC PNP8078 DCA 10 Mb MCA PNP8074 HP MC LAN Adapter/16 TP (PC27246) PNP80c9 IBM Token Ring PNP80ca IBM Token Ring II PNP80cb IBM Token Ring II/Short PNP80cc IBM Token Ring 4/16Mbs PNP80d3 Novell/Anthem NE1000 PNP80d4 Novell/Anthem NE2000 PNP80d5 NE1000 Compatible PNP80d6 NE2000 Compatible PNP80d7 Novell/Anthem NE1500T PNP80d8 Novell/Anthem NE2100 PNP80dd SMC ARCNETPC PNP80de SMC ARCNET PC100, PC200 PNP80df SMC ARCNET PC110, PC210, PC250 PNP80e0 SMC ARCNET PC130/E PNP80e1 SMC ARCNET PC120, PC220, PC260 PNP80e2 SMC ARCNET PC270/E PNP80e5 SMC ARCNET PC600W, PC650W PNP80e7 DEC DEPCA PNP80e8 DEC (DE100) EtherWorks LC PNP80e9 DEC (DE200) EtherWorks Turbo PNP80ea DEC (DE101) EtherWorks LC/TP PNP80eb DEC (DE201) EtherWorks Turbo/TP PNP80ec DEC (DE202) EtherWorks Turbo/TP_BNC PNP80ed DEC (DE102) EtherWorks LC/TP_BNC PNP80ee DEC EE101 (Built-In) PNP80ef DECpc 433 WS (Built-In) PNP80f1 3Com EtherLink Plus PNP80f3 3Com EtherLink II or IITP (8 or 16-bit) PNP80f4 3Com TokenLink PNP80f6 3Com EtherLink 16 PNP80f7 3Com EtherLink III PNP80f8 3Com Generic Etherlink Plug and Play Device PNP80fb Thomas Conrad TC6045 PNP80fc Thomas Conrad TC6042 PNP80fd Thomas Conrad TC6142 PNP80fe Thomas Conrad TC6145 PNP80ff Thomas Conrad TC6242 PNP8100 Thomas Conrad TC6245 PNP8105 DCA 10 MB PNP8106 DCA 10 MB Fiber Optic PNP8107 DCA 10 MB Twisted Pair PNP8113 Racal NI6510 PNP811C Ungermann-Bass NIUpc PNP8120 Ungermann-Bass NIUpc/EOTP PNP8123 SMC StarCard PLUS (WD/8003S) PNP8124 SMC StarCard PLUS With On Board Hub (WD/8003SH) PNP8125 SMC EtherCard PLUS (WD/8003E) PNP8126 SMC EtherCard PLUS With Boot ROM Socket (WD/8003EBT) PNP8127 SMC EtherCard PLUS With Boot ROM Socket (WD/8003EB) PNP8128 SMC EtherCard PLUS TP (WD/8003WT) PNP812a SMC EtherCard PLUS 16 With Boot ROM Socket (WD/8013EBT) PNP812d Intel EtherExpress 16 or 16TP PNP812f Intel TokenExpress 16/4 PNP8130 Intel TokenExpress MCA 16/4 PNP8132 Intel EtherExpress 16 (MCA) PNP8137 Artisoft AE-1 PNP8138 Artisoft AE-2 or AE-3 PNP8141 Amplicard AC 210/XT PNP8142 Amplicard AC 210/AT PNP814b Everex SpeedLink /PC16 (EV2027) PNP8155 HP PC LAN Adapter/8 TP (HP27245) PNP8156 HP PC LAN Adapter/16 TP (HP27247A) PNP8157 HP PC LAN Adapter/8 TL (HP27250) PNP8158 HP PC LAN Adapter/16 TP Plus (HP27247B) PNP8159 HP PC LAN Adapter/16 TL Plus (HP27252) PNP815f National Semiconductor Ethernode *16AT PNP8160 National Semiconductor AT/LANTIC EtherNODE 16-AT3 PNP816a NCR Token-Ring 4 Mbs ISA PNP816d NCR Token-Ring 16/4 Mbs ISA PNP8191 Olicom 16/4 Token-Ring Adapter PNP81c3 SMC EtherCard PLUS Elite (WD/8003EP) PNP81c4 SMC EtherCard PLUS 10T (WD/8003W) PNP81c5 SMC EtherCard PLUS Elite 16 (WD/8013EP) PNP81c6 SMC EtherCard PLUS Elite 16T (WD/8013W) PNP81c7 SMC EtherCard PLUS Elite 16 Combo (WD/8013EW or 8013EWC) PNP81c8 SMC EtherElite Ultra 16 PNP81e4 Pure Data PDI9025-32 (Token Ring) PNP81e6 Pure Data PDI508+ (ArcNet) PNP81e7 Pure Data PDI516+ (ArcNet) PNP81eb Proteon Token Ring (P1390) PNP81ec Proteon Token Ring (P1392) PNP81ed Proteon ISA Token Ring (1340) PNP81ee Proteon ISA Token Ring (1342) PNP81ef Proteon ISA Token Ring (1346) PNP81f0 Proteon ISA Token Ring (1347) PNP81ff Cabletron E2000 Series DNI PNP8200 Cabletron E2100 Series DNI PNP8209 Zenith Data Systems Z-Note PNP820a Zenith Data Systems NE2000-Compatible PNP8213 Xircom Pocket Ethernet II PNP8214 Xircom Pocket Ethernet I PNP821d RadiSys EXM-10 PNP8227 SMC 3000 Series PNP8228 SMC 91C2 controller PNP8231 Advanced Micro Devices AM2100/AM1500T PNP8263 Tulip NCC-16 PNP8277 Exos 105 PNP828A Intel '595 based Ethernet PNP828B TI2000-style Token Ring PNP828C AMD PCNet Family cards PNP828D AMD PCNet32 (VL version) PNP8294 IrDA Infrared NDIS driver (Microsoft-supplied) PNP82bd IBM PCMCIA-NIC PNP82C2 Xircom CE10 PNP82C3 Xircom CEM2 PNP8321 DEC Ethernet (All Types) PNP8323 SMC EtherCard (All Types except 8013/A) PNP8324 ARCNET Compatible PNP8326 Thomas Conrad (All Arcnet Types) PNP8327 IBM Token Ring (All Types) PNP8385 Remote Network Access Driver PNP8387 RNA Point-to-point Protocol Driver PNP8388 Reserved for Microsoft Networking components PNP8389 Peer IrLAN infrared driver (Microsoft-supplied) PNP8390 Generic network adapter ***** SCSI, Proprietary CD Adapters - PNPAxxx ********** PNPA002 Future Domain 16-700 compatible controller PNPA003 Panasonic proprietary CD-ROM adapter (SBPro/SB16) PNPA01B Trantor 128 SCSI Controller PNPA01D Trantor T160 SCSI Controller PNPA01E Trantor T338 Parallel SCSI controller PNPA01F Trantor T348 Parallel SCSI controller PNPA020 Trantor Media Vision SCSI controller PNPA022 Always IN-2000 SCSI controller PNPA02B Sony proprietary CD-ROM controller PNPA02D Trantor T13b 8-bit SCSI controller PNPA02F Trantor T358 Parallel SCSI controller PNPA030 Mitsumi LU-005 Single Speed CD-ROM controller + drive PNPA031 Mitsumi FX-001 Single Speed CD-ROM controller + drive PNPA032 Mitsumi FX-001 Double Speed CD-ROM controller + drive ***** Sound/Video-capture, multimedia - PNPBxxx ******** PNPB000 Sound Blaster 1.5 sound device PNPB001 Sound Blaster 2.0 sound device PNPB002 Sound Blaster Pro sound device PNPB003 Sound Blaster 16 sound device PNPB004 Thunderboard-compatible sound device PNPB005 Adlib-compatible FM synthesizer device PNPB006 MPU401 compatible PNPB007 Microsoft Windows Sound System-compatible sound device PNPB008 Compaq Business Audio PNPB009 Plug and Play Microsoft Windows Sound System Device PNPB00A MediaVision Pro Audio Spectrum (Trantor SCSI enabled, Thunder Chip Disabled) PNPB00B MediaVision Pro Audio 3D PNPB00C MusicQuest MQX-32M PNPB00D MediaVision Pro Audio Spectrum Basic (No Trantor SCSI, Thunder Chip Enabled) PNPB00E MediaVision Pro Audio Spectrum (Trantor SCSI enabled, Thunder Chip Enabled) PNPB00F MediaVision Jazz-16 chipset (OEM Versions) PNPB010 Auravision VxP500 chipset - Orchid Videola PNPB018 MediaVision Pro Audio Spectrum 8-bit PNPB019 MediaVision Pro Audio Spectrum Basic (no Trantor SCSI, Thunder chip Disabled) PNPB020 Yamaha OPL3-compatible FM synthesizer device PNPB02F Joystick/Game port ***** Modems - PNPCxxx-Dxxx**************************** PNPC000 Compaq 14400 Modem (TBD) PNPC001 Compaq 2400/9600 Modem (TBD) ====================================================================== DEVICE TYPE CODES ----------------------------------------------------------------------- Base Type = 0: Reserved Base Type = 1: Mass Storage Device Sub-Type = 0: SCSI Controller Sub-Type = 1: IDE Controller (Standard ATA compatible) Interface Type = 0: Generic IDE Sub-Type = 2: Floppy Controller (Standard 765 compatible) Interface Type = 0: Generic Floppy Sub-Type = 3: IPI Controller Interface Type = 0: General IPI Sub-Type = 80h: Other Mass Storage Controller Base Type = 2: Network Interface Controller Sub-Type = 0: Ethernet Interface Type = 0: General Ethernet Sub-Type = 1: Token Ring Controller Interface Type = 0: General Token Ring Sub-Type = 2: FDDI Controller Interface Type = 0: General FDDI Sub-Type = 80h: Other Network Interface Controller Base Type = 3: Display Controller Sub-Type = 0: VGA Controller (Standard VGA compatible) Interface Type = 0: Generic VGA compatible Interface Type = 1: VESA SVGA Compatible Controller Sub-Type = 1: XGA Compatible Controller Interface Type = 0: General XGA Compatible Controller Sub-Type = 80h: Other Display Controller Base Type = 4: Multi-media Controller Sub-Type = 0: Video Controller Interface Type = 0: General Video Sub-Type = 1: Audio Controller Interface Type = 0: General Audio Controller Sub-Type = 80h: Other Multi-media Controller Base Type = 5: Memory Sub-Type = 0: RAM Interface Type = 0: General RAM Sub-Type = 1: FLASH Memory Interface Type = 0: General FLASH Memory Sub-Type = 80h: Other Memory Device Base Type = 6: Bridge Controller Sub-Type = 0: Host Processor Bridge Interface Type = 0: General Host Processor Bridge Sub-Type = 1: ISA Bridge Interface Type = 0: General ISA Bridge Sub-Type = 2: EISA Bridge Interface Type = 0: General EISA Bridge Sub-Type = 3: MicroChannel Bridge Interface Type = 0: General Micro-Channel Bridge Sub-Type = 4: PCI Bridge Interface Type = 0: General PCI Bridge Sub-Type = 5: PCMCIA Bridge Interface Type = 0: General PCMCIA Bridge Sub-Type = 80h: Other Bridge Device Base Type = 7: Communications Device Sub-Type = 0: RS-232 Device (XT-compatible COM) Interface Type = 0: Generic XT-compatible Interface Type = 1: 16450-compatible Interface Type = 2: 16550-compatible Sub-Type = 1: AT-Compatible Parallel Port Interface Type = 0: Generic AT Parallel Port Interface Type = 1: Model-30 Bidirectional Port Interface Type = 2: ECP 1.? compliant port Sub-Type = 80h: Other Communications Device Base Type = 8: System Peripherals Sub-Type = 0: Programmable Interrupt Controller (8259 Compatible) Interface Type = 0: Generic 8259 PIC Interface Type = 1: ISA PIC (8259 Compatible) Interface Type = 2: EISA PIC (8259 Compatible) Sub-Type = 1: DMA Controller (8237 Compatible) Interface Type = 0: Generic DMA Controller Interface Type = 1: ISA DMA Controller Interface Type = 2: EISA DMA Controller Sub-Type = 2: System Timer (8254 Compatible) Interface Type = 0: Generic System Timer Interface Type = 1: ISA System Timer Interface Type = 2: EISA System Timers (2 Timers) Sub-Type = 3: Real Time Clock Interface Type = 0: Generic RTC Controller Interface Type = 1: ISA RTC Controller Sub-Type = 80h: Other System Peripheral Base Type = 9: Input Devices Sub-Type = 0: Keyboard Controller Interface Type = 0: Not applicable Sub-Type = 1: Digitizer (Pen) Interface Type = 0: Not applicable Sub-Type = 2: Mouse Controller Interface Type = 0: Not applicable Sub-Type = 80h: Other Input Controller Base Type = 0Ah: Docking Station Sub-Type = 0: Generic Docking Station Interface Type = 0: Not applicable Sub-Type = 80h: Other type of Docking Station Base Type = 0Bh: CPU Type Sub-Type = 0: 386-based processor Interface Type = 0: Not applicable Sub-Type = 1: 486-based processor Interface Type = 0: Not applicable Sub-Type = 2: Pentium-based processor Interface Type = 0: Not applicable --------------3D9775A515A540D3E431EDB0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 9:44:43 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id C504537B684 for ; Fri, 23 Feb 2001 09:44:37 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id JAA25957 for ; Fri, 23 Feb 2001 09:44:37 -0800 Date: Fri, 23 Feb 2001 09:44:36 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: current@freebsd.org Subject: woo hoo! vm panic! 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 panic: vm_page_insert: already inserted syncing disks... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 9:56:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 9579937B503 for ; Fri, 23 Feb 2001 09:56:20 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f1NHuAX83112; Fri, 23 Feb 2001 09:56:10 -0800 (PST) (envelope-from dillon) Date: Fri, 23 Feb 2001 09:56:10 -0800 (PST) From: Matt Dillon Message-Id: <200102231756.f1NHuAX83112@earth.backplane.com> To: Kirk McKusick Cc: current@freebsd.org Subject: Re: Any Ideas References: <200102231206.EAA12234@beastie.mckusick.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Are you aware of any recent changes that would have caused this :problem? I do not believe that the soft updates changes would :have caused this problem since they were all related to `under :stress' conditions which are not applicable here. : : ~Kirk I haven't made any commits to -current for a while, like several weeks. It's possible that the specfs fsync fixes I did few weeks ago could be involved, but the syncing problem seems to have come up recently... long after I had made those changes. It seems more likely that the problems are related to scheduler and interrupt subsystem changes in -current. If someone were to generate a core during the failing synchronization attempt I'd be happy to look at it. It can only be one of a few possibilities: (1) The buffer cannot be synced because a background write is in progress and the background write never finishes (not likely), (2) the I/O for the buffer synchronization is initiated but interrupts are winding up being disabled by the halt code due to holding Giant and not sleeping (more likely). That all I can think of. We've hit the interrupt disablement problem before in -current, it's probably something simliar. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 9:57:53 2001 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.icomtek.csir.co.za (zibbi.icomtek.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id E904237B4EC for ; Fri, 23 Feb 2001 09:57:17 -0800 (PST) (envelope-from jhay@zibbi.icomtek.csir.co.za) Received: (from jhay@localhost) by zibbi.icomtek.csir.co.za (8.11.1/8.11.1) id f1NHuTq91448 for current@FreeBSD.org; Fri, 23 Feb 2001 19:56:29 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200102231756.f1NHuTq91448@zibbi.icomtek.csir.co.za> Subject: tail -f kernel panic To: current@FreeBSD.org Date: Fri, 23 Feb 2001 19:56:28 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I found it is quite easy to panic a -current kernel with 2 login windows. In window 1 do a "tail -f /tmp/world.out" In window 2 do a "tail -f /tmp/world.out" In window 2 do "^C" to break out of tail -f In window 1 do "^C" to break out of tail -f The box panic immediately. I can't get a coredump at the moment because the kernel just stops while doing the "syncing disks... 7 7"... Maybe it is related to kern/25309? Fatal trap 12: page fault while in kernel mode cpuid = 1; lapic.id = 00000000 fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:0xc023175a stack pointer = 0x10:0xc8fe5db4 frame pointer = 0x10:0xc8fe5dc0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 347 (tail) trap number = 12 panic: page fault cpuid = 1; lapic.id = 00000000 boot() called on cpu#1 syncing disks... 7 7 c02312e8 t ufs_advlock c0231310 T ufs_vinit c02313bc t ufs_makeinode c023159c t ufs_missingop c02315b4 t ufs_kqfilter c02316d4 t filt_ufsdetach c02317dc t filt_ufsread c0231808 t filt_ufsvnode c023182c T ufs_vnoperate John -- John Hay -- John.Hay@icomtek.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 10:15:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id 0AC3037B65D for ; Fri, 23 Feb 2001 10:15:45 -0800 (PST) (envelope-from DougB@gorean.org) Received: from gorean.org (Studded@master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id KAA28740 for ; Fri, 23 Feb 2001 10:15:44 -0800 (PST) (envelope-from DougB@gorean.org) Message-ID: <3A96A8D0.EFDE1CDE@gorean.org> Date: Fri, 23 Feb 2001 10:15:44 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Panic with last night's -current Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gang, I cvsup'ed last night as of green's latest update of src/lib/libc/stdio/_flock_stub.c. I had a weird panic this morning, after the machine was up overnight (although not really doing anything). I have 'tail -f $HOME/.xsession-errors > /dev/console &' in my .xsession file, and when I logged out of windowmaker to replace it with the latest version, for some reason the script that's supposed to run that kills that job on the way out didn't run. When I started the new wm I noticed that I had two tail's running, so I tried to kill one. As soon as I typed 'kill ' in the xterm the system locked up, and eventually panic'ed and rebooted. To add to the excitement I changed my kernel debugging options last night to include WITNESS. I now have WITNESS and INVARIANTS, no DIAGNOSTIC. I have a UP system, Celeron 300A on an Asus P2B motherboard. Here's what I got from kgdb, I have the core and debug kernel if anyone wants more data. Enjoy, Doug -- "Pain heals. Chicks dig scars. Glory . . . lasts forever." -- Keanu Reeves as Shane Falco in "The Replacements" Do YOU Yahoo!? IdlePTD 4222976 initial pcb at 361980 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:0xc02815de stack pointer = 0x10:0xc8b28db4 frame pointer = 0x10:0xc8b28dc0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 342 (tail) trap number = 12 panic: page fault syncing disks... 16 16 16 16 16 16 16 16 16 16 16 fxp0: device timeout 16 16 16 16 16 16 16 16 16 giving up on 16 buffers Uptime: 8h19m3s dumping to dev da1s1b, offset 262168 dump 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 --- #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:476 476 if (dumping++) { (kgdb) bt #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:476 #1 0xc01a6667 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:319 #2 0xc01a6a31 in panic (fmt=0xc02fcd8f "page fault") at /usr/src/sys/kern/kern_shutdown.c:569 #3 0xc02b1756 in trap_fatal (frame=0xc8b28d74, eva=0) at /usr/src/sys/i386/i386/trap.c:993 #4 0xc02b14a5 in trap_pfault (frame=0xc8b28d74, usermode=0, eva=0) at /usr/src/sys/i386/i386/trap.c:907 #5 0xc02b0af8 in trap (frame={tf_fs = 24, tf_es = -1070727152, tf_ds = 16, tf_edi = -928237472, tf_esi = -927731776, tf_ebp = -927822400, tf_isp = -927822432, tf_ebx = -927801408, tf_edx = 0, tf_ecx = -928237072, tf_eax = -1056946176, tf_trapno = 12, tf_err = 0, tf_eip = -1071114786, tf_cs = 8, tf_eflags = 66051, tf_esp = -927731776, tf_ss = 0}) at /usr/src/sys/i386/i386/trap.c:454 #6 0xc02815de in filt_ufsdetach (kn=0xc8b3efc0) at /usr/src/sys/ufs/ufs/ufs_vnops.c:2226 #7 0xc0194803 in kqueue_close (fp=0xc1000680, p=0xc8ac3860) at /usr/src/sys/kern/kern_event.c:702 #8 0xc019351d in fdrop (fp=0xc1000680, p=0xc8ac3860) at /usr/src/sys/sys/file.h:216 #9 0xc0193463 in closef (fp=0xc1000680, p=0xc8ac3860) at /usr/src/sys/kern/kern_descrip.c:1213 #10 0xc01931d0 in fdfree (p=0xc8ac3860) at /usr/src/sys/kern/kern_descrip.c:1052 #11 0xc0195f6d in exit1 (p=0xc8ac3860, rv=15) at /usr/src/sys/kern/kern_exit.c:194 #12 0xc01a97ca in sigexit (p=0xc8ac3860, sig=15) at /usr/src/sys/kern/kern_sig.c:1599 #13 0xc01a9520 in postsig (sig=15) at /usr/src/sys/kern/kern_sig.c:1500 #14 0xc02affc3 in userret (p=0xc8ac3860, frame=0xc8b28fa8, oticks=1) at /usr/src/sys/i386/i386/trap.c:178 #15 0xc02b20dc in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 4, tf_esi = 1, tf_ebp = -1077937168, tf_isp = -927821868, tf_ebx = 672174336, tf_edx = 0, tf_ecx = 0, tf_eax = 4, tf_trapno = 12, tf_err = 2, tf_eip = 671772464, tf_cs = 31, tf_eflags = 663, tf_esp = -1077937388, tf_ss = 47}) at /usr/src/sys/i386/i386/trap.c:1239 #16 0xc02a4883 in Xint0x80_syscall () #17 0x8049e68 in ?? () #18 0x8048b8d in ?? () To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 10:44:10 2001 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 1022937B491 for ; Fri, 23 Feb 2001 10:44:07 -0800 (PST) (envelope-from jhb@foo.osd.bsdi.com) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f1NIhqK27761; Fri, 23 Feb 2001 10:43:53 -0800 (PST) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.1/8.11.1) id f1NIhCc76165; Fri, 23 Feb 2001 10:43:12 -0800 (PST) (envelope-from jhb) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200102230429.f1N4TN172703@zibbi.icomtek.csir.co.za> Date: Fri, 23 Feb 2001 10:43:07 -0800 (PST) Organization: BSD, Inc. From: John Baldwin To: John Hay Subject: Re: Release b0rked.. Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 23-Feb-01 John Hay wrote: >> ===> lib/libgssapi >> rm -f .depend >> mkdep -f .depend -a > ... >> /usr/src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/krb5/krb5.h:43: >> krb5_err.h: No such file or directory >> /usr/src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/krb5/krb5.h:44: >> heim_err.h: No such file or directory > > You can get past this error with this patch, but it will just die a little > later in another part of kerberos. You should have better luck by building > a release with NOKERBEROS=YES. I was able to build one yesterday. Hrm, I already got release fixed here locally with this patch which looks more like what the other libraries do: Index: kerberos5/lib/libgssapi//Makefile =================================================================== RCS file: /host/ares/usr/home/ncvs/src/kerberos5/lib/libgssapi/Makefile,v retrieving revision 1.1 diff -u -r1.1 Makefile --- kerberos5/lib/libgssapi//Makefile 2001/02/13 16:56:50 1.1 +++ kerberos5/lib/libgssapi//Makefile 2001/02/23 02:34:46 @@ -7,7 +7,8 @@ -I${KRB5DIR}/lib/roken \ -I${KRB5DIR}/lib/des \ -I${KRB5DIR}/include \ - -I${ASN1OBJDIR} + -I${ASN1OBJDIR} \ + -I${.OBJDIR} SRCS= \ 8003.c \ @@ -49,8 +50,10 @@ wrap.c \ address_to_krb5addr.c -INCLUDES=${KRB5DIR}/lib/gssapi/gssapi.h +INCLUDES=${KRB5DIR}/lib/gssapi/gssapi.h heim_err.h krb5_err.h .include .PATH: ${KRB5DIR}/lib/gssapi + +beforedepend all: heim_err.h krb5_err.h Oops, and I've already committed this. I'm sure it will get backed out if it isn't correct. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 10:45:49 2001 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id DE18E37B503; Fri, 23 Feb 2001 10:45:47 -0800 (PST) (envelope-from jhb@foo.osd.bsdi.com) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f1NIjYK27856; Fri, 23 Feb 2001 10:45:34 -0800 (PST) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.1/8.11.1) id f1NIir176198; Fri, 23 Feb 2001 10:44:53 -0800 (PST) (envelope-from jhb) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200102231245.NAA25884@freebsd.dk> Date: Fri, 23 Feb 2001 10:44:53 -0800 (PST) Organization: BSD, Inc. From: John Baldwin To: Soren Schmidt Subject: Re: dirty buffers on reboot again?' Cc: current@FreeBSD.ORG, (Matthew Jacob) , obrien@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 23-Feb-01 Soren Schmidt wrote: > It seems David O'Brien wrote: >> On Thu, Feb 22, 2001 at 03:20:10PM -0800, Matthew Jacob wrote: >> > login: (da0:ahc0:0:0:0): tagged openings now 16 >> ... >> > syncing disks... 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 >> > giving up on 3 buffers >> ... >> > I'm seeing a lot of this again. Anyone else? >> >> Yep. ahc controller also. By chance is that the commonality to this >> problem? > > No, its generically broken... Hmm, I must have Magic Boxes(tm) becaues none of them exhibit this problem. > -Søren -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 10:54:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 8FA8437B4EC; Fri, 23 Feb 2001 10:54:06 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA26215; Fri, 23 Feb 2001 10:54:06 -0800 Date: Fri, 23 Feb 2001 10:54:06 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: John Baldwin Cc: current@FreeBSD.ORG Subject: Re: dirty buffers on reboot again?' In-Reply-To: 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 > > No, its generically broken... > > Hmm, I must have Magic Boxes(tm) becaues none of them exhibit this problem. You might keep that in mind when you say, "oh, yes, it worked for me!" :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 10:54:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 8BBD337B503 for ; Fri, 23 Feb 2001 10:54:08 -0800 (PST) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f1NIrM788285; Fri, 23 Feb 2001 12:53:22 -0600 (CST) (envelope-from jlemon) Date: Fri, 23 Feb 2001 12:53:22 -0600 (CST) From: Jonathan Lemon Message-Id: <200102231853.f1NIrM788285@prism.flugsvamp.com> To: jhay@icomtek.csir.co.za, current@freebsd.org Subject: Re: tail -f kernel panic X-Newsgroups: local.mail.freebsd-current In-Reply-To: Organization: Cc: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >I found it is quite easy to panic a -current kernel with 2 login windows. > >In window 1 do a "tail -f /tmp/world.out" >In window 2 do a "tail -f /tmp/world.out" >In window 2 do "^C" to break out of tail -f >In window 1 do "^C" to break out of tail -f >The box panic immediately. Hmm. I reproduced this here; the panic is in SLIST_REMOVE() when it is removing the second event. Funny enough, this does not happen on -stable. Did something change in the list macros recently that would cause this? -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 11:21:34 2001 Delivered-To: freebsd-current@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 78D1437B401 for ; Fri, 23 Feb 2001 11:21:32 -0800 (PST) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f1NJKkP89364; Fri, 23 Feb 2001 13:20:46 -0600 (CST) (envelope-from jlemon) Date: Fri, 23 Feb 2001 13:20:46 -0600 (CST) From: Jonathan Lemon Message-Id: <200102231920.f1NJKkP89364@prism.flugsvamp.com> To: jhay@icomtek.csir.co.za, current@freebsd.org Subject: Re: tail -f kernel panic X-Newsgroups: local.mail.freebsd-current In-Reply-To: Organization: Cc: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >I found it is quite easy to panic a -current kernel with 2 login windows. > >In window 1 do a "tail -f /tmp/world.out" >In window 2 do a "tail -f /tmp/world.out" >In window 2 do "^C" to break out of tail -f >In window 1 do "^C" to break out of tail -f >The box panic immediately. I just commited a fix for this. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 11:23: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-57.dsl.lsan03.pacbell.net [63.207.60.57]) by hub.freebsd.org (Postfix) with ESMTP id EF73137B4EC for ; Fri, 23 Feb 2001 11:23:05 -0800 (PST) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id B813066F1F; Fri, 23 Feb 2001 11:23:05 -0800 (PST) Date: Fri, 23 Feb 2001 11:23:05 -0800 From: Kris Kennaway To: Guillaume Cc: freebsd-current@freebsd.org Subject: Re: unknown: can't assign resources Message-ID: <20010223112305.A73037@mollari.cthul.hu> References: <005101c09db6$62e94f80$0a0110ac@guillaume> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="/04w6evG8XlLl3ft" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <005101c09db6$62e94f80$0a0110ac@guillaume>; from amyfoub@videotron.ca on Fri, Feb 23, 2001 at 11:33:42AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --/04w6evG8XlLl3ft Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Feb 23, 2001 at 11:33:42AM -0500, Guillaume wrote: > Hello, >=20 > I'm running FreeBSD 5.0-CURRENT since 2 days. >=20 > When I boot FreeBSD I get this error: >=20 > Feb 22 23:21:13 unix /boot/kernel/kernel: vga0: at port > 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > Feb 22 23:21:13 unix /boot/kernel/kernel: unknown: can't assign > resources > Feb 22 23:21:13 unix /boot/kernel/kernel: unknown: can't assign > resources > Feb 22 23:21:13 unix /boot/kernel/kernel: unknown: can't assign > resources > Feb 22 23:21:13 unix /boot/kernel/kernel: unknown: can't assign > resources > Feb 22 23:21:13 unix /boot/kernel/kernel: unknown: can't assign > resources >=20 > What is that and how can I fix this error? Check the archives so someone doesn't have to answer this question all over again. Kris --/04w6evG8XlLl3ft Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6lriZWry0BWjoQKURAkk5AKDI5a7r5rabxjbHzmSB74J2f2VeYQCgij8U 2wz876wKVHWgzonTsrbw7yM= =92QY -----END PGP SIGNATURE----- --/04w6evG8XlLl3ft-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 11:23:26 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 291C837B491 for ; Fri, 23 Feb 2001 11:23:24 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA26362 for ; Fri, 23 Feb 2001 11:23:24 -0800 Date: Fri, 23 Feb 2001 11:23:23 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: current@freebsd.org Subject: whither libtermcap? (fallout of libc dance) 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 It seems that libtermcap went away. Fine and dandy, okay... The problem is that libtermcap.so, still hanging around, is used by things that don't usually get rebuilt in a buildworld/installworld run (like X11 tools like xterm)- and attempts to use such things yield: farrago.feral.com > xterm /usr/libexec/ld-elf.so.1: /usr/lib/libtermcap.so.2: Undefined symbol "__stderr" (this also nukes ports like bash, etc., until they get rebuilt) d'ya suppose we can have libtermcap back, or some kind of compat thingie? Would this be a 4.X compat thingie? How is this supposed to work? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 11:25:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-57.dsl.lsan03.pacbell.net [63.207.60.57]) by hub.freebsd.org (Postfix) with ESMTP id 51AF437B401 for ; Fri, 23 Feb 2001 11:25:34 -0800 (PST) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 217DA66F1F; Fri, 23 Feb 2001 11:25:34 -0800 (PST) Date: Fri, 23 Feb 2001 11:25:34 -0800 From: Kris Kennaway To: Matthew Jacob Cc: current@freebsd.org Subject: Re: whither libtermcap? (fallout of libc dance) Message-ID: <20010223112533.B73037@mollari.cthul.hu> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="1UWUbFP1cBYEclgG" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from mjacob@feral.com on Fri, Feb 23, 2001 at 11:23:23AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --1UWUbFP1cBYEclgG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Feb 23, 2001 at 11:23:23AM -0800, Matthew Jacob wrote: > The problem is that libtermcap.so, still hanging around, is used by things > that don't usually get rebuilt in a buildworld/installworld run (like X11 > tools like xterm)- and attempts to use such things yield: lrwxr-xr-x 1 root wheel 12 Feb 23 00:55 /usr/lib/libtermcap.a -> libncurses.a lrwxr-xr-x 1 root wheel 13 Feb 23 00:55 /usr/lib/libtermcap.so -> libncurses.so -r--r--r-- 1 root wheel 15160 Apr 24 2000 /usr/lib/libtermcap.so.2 l Remove your stale libraries - this one went away before 4.0-REL. Kris --1UWUbFP1cBYEclgG Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6lrktWry0BWjoQKURAgdSAJ9z+o9nKkZABYNujje80ormUd3cEQCfRbXR BB78qk+SRiG4IfM1CkvrApk= =N8CO -----END PGP SIGNATURE----- --1UWUbFP1cBYEclgG-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 11:26:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 5EBD937B4EC for ; Fri, 23 Feb 2001 11:26:31 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA26379; Fri, 23 Feb 2001 11:26:29 -0800 Date: Fri, 23 Feb 2001 11:26:28 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Kris Kennaway Cc: current@freebsd.org Subject: Re: whither libtermcap? (fallout of libc dance) In-Reply-To: <20010223112533.B73037@mollari.cthul.hu> 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 Fri, 23 Feb 2001, Kris Kennaway wrote: > On Fri, Feb 23, 2001 at 11:23:23AM -0800, Matthew Jacob wrote: > > > The problem is that libtermcap.so, still hanging around, is used by things > > that don't usually get rebuilt in a buildworld/installworld run (like X11 > > tools like xterm)- and attempts to use such things yield: > > lrwxr-xr-x 1 root wheel 12 Feb 23 00:55 /usr/lib/libtermcap.a -> libncurses.a > lrwxr-xr-x 1 root wheel 13 Feb 23 00:55 /usr/lib/libtermcap.so -> libncurses.so > -r--r--r-- 1 root wheel 15160 Apr 24 2000 /usr/lib/libtermcap.so.2 > l > > Remove your stale libraries - this one went away before 4.0-REL. > *smack*... oh, yeah! sorry! I *do* have some 3.X stuff still there. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 11:29:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 700EA37B491 for ; Fri, 23 Feb 2001 11:29:14 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA26408; Fri, 23 Feb 2001 11:29:12 -0800 Date: Fri, 23 Feb 2001 11:29:12 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Kris Kennaway Cc: current@FreeBSD.ORG Subject: btw - Re: whither libtermcap? (fallout of libc dance) In-Reply-To: <20010223112533.B73037@mollari.cthul.hu> 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 Fri, 23 Feb 2001, Kris Kennaway wrote: > On Fri, Feb 23, 2001 at 11:23:23AM -0800, Matthew Jacob wrote: > > > The problem is that libtermcap.so, still hanging around, is used by things > > that don't usually get rebuilt in a buildworld/installworld run (like X11 > > tools like xterm)- and attempts to use such things yield: > > lrwxr-xr-x 1 root wheel 12 Feb 23 00:55 /usr/lib/libtermcap.a -> libncurses.a > lrwxr-xr-x 1 root wheel 13 Feb 23 00:55 /usr/lib/libtermcap.so -> libncurses.so > -r--r--r-- 1 root wheel 15160 Apr 24 2000 /usr/lib/libtermcap.so.2 > l > > Remove your stale libraries - this one went away before 4.0-REL. ...Which then also begs the question- if I put this all into /usr/lib/compat- and libtermcap.so still whines about missing __stderr- is this a "we don't care- it's too old"? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 11:40:21 2001 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-57.dsl.lsan03.pacbell.net [63.207.60.57]) by hub.freebsd.org (Postfix) with ESMTP id F259E37B401 for ; Fri, 23 Feb 2001 11:40:17 -0800 (PST) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id B649266F1F; Fri, 23 Feb 2001 11:40:17 -0800 (PST) Date: Fri, 23 Feb 2001 11:40:17 -0800 From: Kris Kennaway To: Matthew Jacob Cc: Kris Kennaway , current@FreeBSD.ORG Subject: Re: btw - Re: whither libtermcap? (fallout of libc dance) Message-ID: <20010223114017.A73524@mollari.cthul.hu> References: <20010223112533.B73037@mollari.cthul.hu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="45Z9DzgjV8m4Oswq" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from mjacob@feral.com on Fri, Feb 23, 2001 at 11:29:12AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --45Z9DzgjV8m4Oswq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Feb 23, 2001 at 11:29:12AM -0800, Matthew Jacob wrote: > On Fri, 23 Feb 2001, Kris Kennaway wrote: >=20 > > On Fri, Feb 23, 2001 at 11:23:23AM -0800, Matthew Jacob wrote: > >=20 > > > The problem is that libtermcap.so, still hanging around, is used by t= hings > > > that don't usually get rebuilt in a buildworld/installworld run (like= X11 > > > tools like xterm)- and attempts to use such things yield: > >=20 > > lrwxr-xr-x 1 root wheel 12 Feb 23 00:55 /usr/lib/libtermcap.a -> = libncurses.a > > lrwxr-xr-x 1 root wheel 13 Feb 23 00:55 /usr/lib/libtermcap.so ->= libncurses.so > > -r--r--r-- 1 root wheel 15160 Apr 24 2000 /usr/lib/libtermcap.so.2 > > l > >=20 > > Remove your stale libraries - this one went away before 4.0-REL. >=20 > ...Which then also begs the question- if I put this all into /usr/lib/com= pat- > and libtermcap.so still whines about missing __stderr- is this a "we don't > care- it's too old"? You shouldn't be building new binaries which link against libtermcap (i.e. this should never happen) - it's only there for existing binaries which would be linked against libc.so.3 also (both of which are under compat/) and should continue to work. Kris --45Z9DzgjV8m4Oswq Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6lryhWry0BWjoQKURAmx2AJ9M9UZ9GtiLQLSkdvJHq+MPwxVrfwCg0MTK cY5pTW845OF8U41HBI+UZJc= =FUqw -----END PGP SIGNATURE----- --45Z9DzgjV8m4Oswq-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 11:45: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 21E1737B65D for ; Fri, 23 Feb 2001 11:44:59 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA26474; Fri, 23 Feb 2001 11:44:57 -0800 Date: Fri, 23 Feb 2001 11:44:56 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Kris Kennaway Cc: current@FreeBSD.ORG Subject: Re: btw - Re: whither libtermcap? (fallout of libc dance) In-Reply-To: <20010223114017.A73524@mollari.cthul.hu> 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 Fri, Feb 23, 2001 at 11:29:12AM -0800, Matthew Jacob wrote: > > On Fri, 23 Feb 2001, Kris Kennaway wrote: > > > > > On Fri, Feb 23, 2001 at 11:23:23AM -0800, Matthew Jacob wrote: > > > > > > > The problem is that libtermcap.so, still hanging around, is used by things > > > > that don't usually get rebuilt in a buildworld/installworld run (like X11 > > > > tools like xterm)- and attempts to use such things yield: > > > > > > lrwxr-xr-x 1 root wheel 12 Feb 23 00:55 /usr/lib/libtermcap.a -> libncurses.a > > > lrwxr-xr-x 1 root wheel 13 Feb 23 00:55 /usr/lib/libtermcap.so -> libncurses.so > > > -r--r--r-- 1 root wheel 15160 Apr 24 2000 /usr/lib/libtermcap.so.2 > > > l > > > > > > Remove your stale libraries - this one went away before 4.0-REL. > > > > ...Which then also begs the question- if I put this all into /usr/lib/compat- > > and libtermcap.so still whines about missing __stderr- is this a "we don't > > care- it's too old"? > > You shouldn't be building new binaries which link against libtermcap > (i.e. this should never happen) - it's only there for existing > binaries which would be linked against libc.so.3 also (both of which > are under compat/) and should continue to work. Yeah, okay- thanks! apparently the symlink to libncuruses works- so old X11 binaries work with libc.so.3 in /usr/lib/compat.... Whew! THanks! I didn't wanna have to rebuild all that goop... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 11:57:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.icomtek.csir.co.za (zibbi.icomtek.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id C508437B491 for ; Fri, 23 Feb 2001 11:57:28 -0800 (PST) (envelope-from jhay@zibbi.icomtek.csir.co.za) Received: (from jhay@localhost) by zibbi.icomtek.csir.co.za (8.11.1/8.11.1) id f1NJvEo94420; Fri, 23 Feb 2001 21:57:14 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200102231957.f1NJvEo94420@zibbi.icomtek.csir.co.za> Subject: Re: tail -f kernel panic In-Reply-To: <200102231920.f1NJKkP89364@prism.flugsvamp.com> from Jonathan Lemon at "Feb 23, 2001 01:20:46 pm" To: jlemon@flugsvamp.com (Jonathan Lemon) Date: Fri, 23 Feb 2001 21:57:14 +0200 (SAT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In article you write: > >I found it is quite easy to panic a -current kernel with 2 login windows. > > > >In window 1 do a "tail -f /tmp/world.out" > >In window 2 do a "tail -f /tmp/world.out" > >In window 2 do "^C" to break out of tail -f > >In window 1 do "^C" to break out of tail -f > >The box panic immediately. > > I just commited a fix for this. Yes, no more panic. Thanks. John -- John Hay -- John.Hay@icomtek.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 13:20:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id C3A0237B401 for ; Fri, 23 Feb 2001 13:20:46 -0800 (PST) (envelope-from null@pozo.com) Received: from dual.pozo.com (dual.pozo.com [216.101.162.51]) by pozo.com (8.11.2/8.11.2) with ESMTP id f1NLKie00468 for ; Fri, 23 Feb 2001 13:20:44 -0800 (PST) (envelope-from null@pozo.com) Message-Id: <5.0.2.1.2.20010223131843.00a6a9c8@pozo.com> X-Sender: null@pozo.com X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Fri, 23 Feb 2001 13:20:44 -0800 To: current@FreeBSD.ORG From: Manfred Antar Subject: What ?? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dmesg: ---===> Happy Birthday Peter!!! <===--- :) Happy Birthday !!!! Manfred ================================== || null@pozo.com || || Ph. (415) 681-6235 || ================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 14:45:38 2001 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id AECFD37B491; Fri, 23 Feb 2001 14:45:35 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.1/8.11.1) with SMTP id f1NMj4h70648; Fri, 23 Feb 2001 17:45:08 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Fri, 23 Feb 2001 17:45:04 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: "Daniel C. Sobral" Cc: obrien@FreeBSD.ORG, Matthew Jacob , current@FreeBSD.ORG Subject: Re: dirty buffers on reboot again? In-Reply-To: <3A968441.D66F6D5F@newsguy.com> 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 Hmm. I've been getting this on an ATA box as well. Don't seem to get it when softupdates is not set on the root partition, but that's just an observation from a couple of boxes. (Sample size == 2 -> confidence level = 0). Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services On Sat, 24 Feb 2001, Daniel C. Sobral wrote: > David O'Brien wrote: > > > > On Thu, Feb 22, 2001 at 03:20:10PM -0800, Matthew Jacob wrote: > > > login: (da0:ahc0:0:0:0): tagged openings now 16 > > ... > > > syncing disks... 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 > > > giving up on 3 buffers > > ... > > > I'm seeing a lot of this again. Anyone else? > > > > Yep. ahc controller also. By chance is that the commonality to this > > problem? > > MMmmmmm... I have an aic, though I'm fairly certain I got unsynced > buffers on ide. > > -- > Daniel C. Sobral (8-DCS) > dcs@newsguy.com > dcs@freebsd.org > capo@kzinti.bsdconspiracy.net > > Acabou o hipismo-arte. Mas a desculpa brasileira mais ouvida em Sydney > e' que nao tem mais cavalo bobo por ai'. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 15:49:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 2988A37B4EC for ; Fri, 23 Feb 2001 15:49:42 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f1NNncW84029; Fri, 23 Feb 2001 16:49:39 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200102232349.f1NNncW84029@harmony.village.org> To: Daniel Rock Subject: Re: as segfaulting during world-build Cc: current@FreeBSD.ORG In-reply-to: Your message of "Thu, 22 Feb 2001 22:15:36 +0100." <3A958178.380C85B6@t-online.de> References: <3A958178.380C85B6@t-online.de> <200102201627.f1KGRLa20988@aldan.algebra.com> <20010220174909.F22771@petra.hos.u-szeged.hu> Date: Fri, 23 Feb 2001 16:49:38 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3A958178.380C85B6@t-online.de> Daniel Rock writes: : I did have the same problem. But just rebuilding binutils didn't help either. : Trying to rebuild libc resulted in above SEGV from as. Some sort of Catch 22 Find a libc from before Feb 10th or after Feb 21 and put it on your system. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 15:54:49 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 7F9A537B4EC; Fri, 23 Feb 2001 15:54:46 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f1NNsDW84076; Fri, 23 Feb 2001 16:54:25 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200102232354.f1NNsDW84076@harmony.village.org> To: Wesley Morgan Subject: Re: dirty buffers on reboot again? Cc: Matthew Jacob , "David O'Brien" , current@FreeBSD.ORG In-reply-to: Your message of "Fri, 23 Feb 2001 10:14:37 EST." References: Date: Fri, 23 Feb 2001 16:54:13 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Wesley Morgan writes: : Not here. Just using ad and friends. I've disabled soft updates on my partitions and it seems to get rid of these. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 16:21:18 2001 Delivered-To: freebsd-current@freebsd.org Received: from assaris.sics.se (dhcp115.iss.kth.se [130.237.7.115]) by hub.freebsd.org (Postfix) with ESMTP id E626C37B491 for ; Fri, 23 Feb 2001 16:21:15 -0800 (PST) (envelope-from assar@assaris.sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.9.3) id BAA04149; Sat, 24 Feb 2001 01:21:06 +0100 (CET) (envelope-from assar) From: Assar Westerlund To: Jun Kuriyama Cc: current@FreeBSD.ORG Subject: Re: Release b0rked.. References: <200102230429.f1N4TN172703@zibbi.icomtek.csir.co.za> <7mu25mhu2g.wl@waterblue.imgsrc.co.jp> Date: 24 Feb 2001 01:21:06 +0100 In-Reply-To: Jun Kuriyama's message of "Fri, 23 Feb 2001 14:00:55 +0900" Message-ID: <5lelwpszgt.fsf@assaris.sics.se> Lines: 6 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.6 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jun Kuriyama writes: > Assar, can you review and commit this? This is ok, but jhb has already fixed this. /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 17:32:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from camel.avias.com (camel.avias.com [195.14.38.87]) by hub.freebsd.org (Postfix) with ESMTP id 15DC737B491 for ; Fri, 23 Feb 2001 17:32:54 -0800 (PST) (envelope-from camel@avias.com) Received: from 192.168.2.2 ([192.168.2.2]) by camel.avias.com (8.11.2/8.11.1) with ESMTP id f1O1Wgx38079 for ; Sat, 24 Feb 2001 04:32:43 +0300 (MSK) (envelope-from camel@avias.com) Date: Sat, 24 Feb 2001 04:34:51 +0300 From: Ilya Naumov X-Mailer: The Bat! (v1.48d) Educational Reply-To: Ilya Naumov X-Priority: 3 (Normal) Message-ID: <9220809782.20010224043451@avias.com> To: current@freebsd.org Subject: Re: name resolution problems In-reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello Wesley, Tuesday, February 20, 2001, 1:26:29 AM, you wrote: WM> Since the big shake-up with -current, I find that mozilla and galeon can WM> no longer function (both up to date), but lynx has no problems. Mozilla WM> seems stuck resolving hostnames, yet tcpdump shows no traffic and truss WM> indicates that it is simply looping around a poll(). The biggest WM> difference between lynx and mozilla in terms of name resolution is that WM> mozilla is linked against libc_r... Could there be some problem here? WM> Is anyone else seeing this? yes, i see that too. but i experience the problem even with statically linked linux-opera from ports. very strange.. -- Best regards, Ilya mailto:camel@avias.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 20:24:13 2001 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id B296D37B503 for ; Fri, 23 Feb 2001 20:24:10 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.11.2/8.11.2) id f1O4NuN20483 for freebsd-current@freebsd.org; Fri, 23 Feb 2001 20:23:56 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <200102240423.f1O4NuN20483@troutmask.apl.washington.edu> Subject: is src/tools mandatory for buildworld? To: FreeBSD Current Date: Fri, 23 Feb 2001 20:23:56 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have never popluated src/tools in my local tree and I've not experienced a problem with "make buildworld" because src/tools was empty. In fact, I had a successful "make buildworld && make installworld" last night at 2231 PST. Tonight I get, ain.o mkpar.o output.o reader.o skeleton.o symtab.o verbose.o warshall.o sh /usr/src/tools/install.sh -c -o root -g wheel -m 555 /usr/src/usr.bin/\ yacc/yyfix.sh /usr/obj/usr/src/i386/usr/bin/yyfix /usr/src/tools/install.sh: Can't open /usr/src/tools/install.sh: No such\ file or directory *** Error code 2 Stop in /usr/src/usr.bin/yacc. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 A search through the tree at http://www.FreeBSD.org/cgi/cvsweb.cgi doesn't turn up a obvious commit. And yes, Alfred, I read the cvs-all mailing list, and again missed the commit that makes src/tools mandatory. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 21: 8:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-57.dsl.lsan03.pacbell.net [63.207.60.57]) by hub.freebsd.org (Postfix) with ESMTP id 00D0637B401 for ; Fri, 23 Feb 2001 21:08:13 -0800 (PST) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 7FA3266F1F; Fri, 23 Feb 2001 21:08:07 -0800 (PST) Date: Fri, 23 Feb 2001 21:08:07 -0800 From: Kris Kennaway To: Steve Kargl Cc: FreeBSD Current Subject: Re: is src/tools mandatory for buildworld? Message-ID: <20010223210807.A4036@mollari.cthul.hu> References: <200102240423.f1O4NuN20483@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="xHFwDpU9dbj6ez1V" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200102240423.f1O4NuN20483@troutmask.apl.washington.edu>; from sgk@troutmask.apl.washington.edu on Fri, Feb 23, 2001 at 08:23:56PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --xHFwDpU9dbj6ez1V Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Feb 23, 2001 at 08:23:56PM -0800, Steve Kargl wrote: > I have never popluated src/tools in my local tree and > I've not experienced a problem with "make buildworld" > because src/tools was empty. In fact, I had a successful > "make buildworld && make installworld" last night at 2231 PST. AFAIK, the tools collection has been mandatory for a long time for just the reason you show. Dunno how you got away without it. Kris --xHFwDpU9dbj6ez1V Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6l0G1Wry0BWjoQKURAoYnAJ9XVB9ctyh63KtW2DekjaDYV5/pLgCcDRE0 eb5vY9MzsBjudxaMCQTJ8E0= =ZJ/9 -----END PGP SIGNATURE----- --xHFwDpU9dbj6ez1V-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 21:38:20 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id AE79937B491 for ; Fri, 23 Feb 2001 21:38:16 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id QAA32390; Sat, 24 Feb 2001 16:38:07 +1100 Date: Sat, 24 Feb 2001 16:29:06 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Daniel Rock Cc: Jake Burkholder , freebsd-current@FreeBSD.ORG Subject: Re: HEADS UP Re: cvs commit: src/sys/alpha/alpha trap.c src/sys/dev/acpica/Osd OsdSchedule.c src/sys/i386/i386 genassym.c swtch.s trap.c src/sys/ia64/ia64 trap.c src/sys/kern init_main.c kern_condvar.c kern_idle.c kern_intr.c kern_mib.c kern_mutex.c kern_proc.c ... In-Reply-To: <3A958505.6EBDF1F4@t-online.de> 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, 22 Feb 2001, Daniel Rock wrote: > Jake Burkholder schrieb: > [...] > > As I mentioned in the commit message, this changes the size and layout > > of struct kinfo_proc, so you'll have to recompile libkvm-using programs. > > > > As always, make world is your friend. > > You may have forgotten to also change KINFO_PROC_SIZE in src/sys/user.h Yes, rev.1.31 of src/sys/sys/user.h leaves it as an exercise to change KINFO_PROC_SIZE. > > I'm now getting bootup warning all the time: > > ... > real memory = 197066752 (192448K bytes) > avail memory = 187293696 (182904K bytes) > Preloaded elf kernel "kernel" at 0xc0450000. > WARNING: size of kinfo_proc (648) should be 644!!! This is normal if you haven't done the exercise. It is just a warning. > Pentium Pro MTRR support enabled > ... > > > BTW What is the purpose of KINFO_PROC_SIZE? Why not simply using sizeof()? It is to inhibit changes in the size of the struct. Such changes would break the interface. The struct must have a certain fixed size (and layout) for binary compatibility. sizeof() would give the current size, not necessarily the size that is required for compatibility. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 21:51: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id AAC3437B401 for ; Fri, 23 Feb 2001 21:51:01 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f1O5p0W85583 for ; Fri, 23 Feb 2001 22:51:01 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200102240551.f1O5p0W85583@harmony.village.org> To: current@freebsd.org Subject: Today's panic :-) Date: Fri, 23 Feb 2001 22:51:00 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've added INVARIANTS and WITNESS to my kernel. Today I get a random panic on boot sometimes: lock order reseral (this doesn't cause the panic, but does seem to happen all the time) 1st vnode interlock last acquired @ ../../usr/ffs/ffs_fsops.c:396 2nd 0xc04837a0 mntvnode @ ../../ufs/ffs/ffs_vfsops.c:457 3rd 0xc80b9e8c vnode interlock @ ../../kern/vfs_subr.c:1872 kernel trap 12 with interrupts disabled panic: runq-add: proc 0xc7b28ee0 (fsck_ufs) not SRUN Debugger("panic") Stopeed at Debugger+0x44: pushl %ebx db> trace Debugger(c03d3c03) at Debugger+0x44 panic(c03d4040,c7b28ee0,c7b290a5,282,c7b2b960) at panic+0x70 runq_add(c046ae20,c7b28ee0,c8a4bcra4,c0221ee5,c7b28ee0) at runq_add+0x40 setrunqueue(c7b28ee0) at setrunqueue+0x10 ithread_schedule(c0f0a00,1) at ithread_schedule+0x129 sched_ithd(e) at sched_ithrd+0x3f Xresume14() at Xresume14+0x8 --- interrupt, eip = 0xc03830fb, esp = 0x286, ebp = 0xc8a4bd34 --- trap(18,10,10,73b152,0) at trap+0x9b calltrap() at calltrap+0x5 --- trap 0xc, eip = 0xc03822e9, esp = 0xc8a4bd7c, ebp = 0xc8a4bd90 --- sw1b(0,...) at sw1b+0x6b msleep(...) at msleep+0x588 physio(...) at physio+0x30d spec_read(...) at spec_read+0x71 ufsspec_read(...) at ufsspec_read+0x20 ufs_noperatespec(...) at ufs_noperatespec+0x15 vn_read(...) at vn_read+0x128 dofileread(...) at dofileread+0xb0 read(...) at read+0x36 syscall(...) at syscall+0x551 Xint0x80_syscall() at Xint0x80_syscall+0x23 --- syscall 0x3, eip = 0x8054770, esp = 0xbfbfef60, ebp = 0xbfbfef9c --- db> Anything that I can do to help? I don't have a core dump of this, but it is happening often enough to be a pain. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 22:31:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from mta04.mail.mel.aone.net.au (mta04.mail.au.uu.net [203.2.192.84]) by hub.freebsd.org (Postfix) with ESMTP id E283937B503 for ; Fri, 23 Feb 2001 22:31:46 -0800 (PST) (envelope-from thyerm@camtech.net.au) Received: from camtech.net.au ([203.55.242.67]) by mta04.mail.mel.aone.net.au with ESMTP id <20010224063143.KQXK17033.mta04.mail.mel.aone.net.au@camtech.net.au> for ; Sat, 24 Feb 2001 17:31:43 +1100 Message-ID: <3A975604.30F12BBB@camtech.net.au> Date: Sat, 24 Feb 2001 17:04:44 +1030 From: Matthew Thyer X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.org Subject: find / -fstype local traverses non-local filesystems Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > rlogin olde > sudo find / -fstype local -name UPDATING > ls -l /usr/src/UPDATING -rw-r--r-- 1 me wheel 20477 Feb 18 21:48 /usr/src/UPDATING > df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad0s2a 198399 150632 31896 83% / /dev/ad0s2e 2622211 1497532 914903 62% /usr procfs 4 4 0 100% /proc linprocfs 4 4 0 100% /usr/compat/linux/proc /dev/ad0s1 1050164 428128 622036 41% /C /dev/ad0s3a 2055042 1 1890638 0% /scratch /dev/acd0c 647152 647152 0 100% /cdrom new:/usr/ports 8024556 3265929 4116663 44% /usr/ports new:/usr/src 8024556 3265929 4116663 44% /usr/src new:/usr/obj 8024556 3265929 4116663 44% /usr/obj new:/usr/sup 8024556 3265929 4116663 44% /usr/sup This looks fine I know. The problem is that the find took forever and the disk on host new was thrashing away most of the time. find seems to be traversing all file systems (local and non-local) but just not reporting the found file when its on a non-local filesystem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 22:51:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id AFA2937B491 for ; Fri, 23 Feb 2001 22:51:05 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id RAA02820; Sat, 24 Feb 2001 17:50:58 +1100 Date: Sat, 24 Feb 2001 17:41:40 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: Today's panic :-) In-Reply-To: <200102240551.f1O5p0W85583@harmony.village.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 Fri, 23 Feb 2001, Warner Losh wrote: > I've added INVARIANTS and WITNESS to my kernel. Today I get a random > panic on boot sometimes: > > lock order reseral (this doesn't cause the panic, but > does seem to happen all the time) > 1st vnode interlock last acquired @ ../../usr/ffs/ffs_fsops.c:396 > 2nd 0xc04837a0 mntvnode @ ../../ufs/ffs/ffs_vfsops.c:457 > 3rd 0xc80b9e8c vnode interlock @ ../../kern/vfs_subr.c:1872 > kernel trap 12 with interrupts disabled > panic: runq-add: proc 0xc7b28ee0 (fsck_ufs) not SRUN > Debugger("panic") > Stopeed at Debugger+0x44: pushl %ebx > db> trace > Debugger(c03d3c03) at Debugger+0x44 > panic(c03d4040,c7b28ee0,c7b290a5,282,c7b2b960) at panic+0x70 > runq_add(c046ae20,c7b28ee0,c8a4bcra4,c0221ee5,c7b28ee0) at runq_add+0x40 > setrunqueue(c7b28ee0) at setrunqueue+0x10 > ithread_schedule(c0f0a00,1) at ithread_schedule+0x129 > sched_ithd(e) at sched_ithrd+0x3f > Xresume14() at Xresume14+0x8 > --- interrupt, eip = 0xc03830fb, esp = 0x286, ebp = 0xc8a4bd34 --- > trap(18,10,10,73b152,0) at trap+0x9b > calltrap() at calltrap+0x5 > --- trap 0xc, eip = 0xc03822e9, esp = 0xc8a4bd7c, ebp = 0xc8a4bd90 --- > sw1b(0,...) at sw1b+0x6b > msleep(...) at msleep+0x588 > physio(...) at physio+0x30d > spec_read(...) at spec_read+0x71 > ufsspec_read(...) at ufsspec_read+0x20 > ufs_noperatespec(...) at ufs_noperatespec+0x15 > vn_read(...) at vn_read+0x128 > dofileread(...) at dofileread+0xb0 > read(...) at read+0x36 > syscall(...) at syscall+0x551 > Xint0x80_syscall() at Xint0x80_syscall+0x23 > --- syscall 0x3, eip = 0x8054770, esp = 0xbfbfef60, ebp = 0xbfbfef9c --- > db> > > Anything that I can do to help? I don't have a core dump of this, but > it is happening often enough to be a pain. It seems to be another trap while holding sched_lock. This should be fatal, but the problem is only detected because trap() enables interrupts. Then an interrupt causes bad things to happen. Unfortunately, the above omits the critical information: the instruction at sw1b+0x6b. There is no instruction at that address here. It is apparently just an access to a swapped-out page for the new process. I can't see how this ever worked. The page must be faulted in, but this can't be done while sched_lock is held (not to mention after we have committed to switching contexts). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 22:58:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id F02CB37B65D for ; Fri, 23 Feb 2001 22:58:47 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f1O6wiW85748; Fri, 23 Feb 2001 23:58:44 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200102240658.f1O6wiW85748@harmony.village.org> To: Bruce Evans Subject: Re: Today's panic :-) Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sat, 24 Feb 2001 17:41:40 +1100." References: Date: Fri, 23 Feb 2001 23:58:44 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Bruce Evans writes: : It seems to be another trap while holding sched_lock. This should be : fatal, but the problem is only detected because trap() enables : interrupts. Then an interrupt causes bad things to happen. Unfortunately, : the above omits the critical information: the instruction at sw1b+0x6b. : There is no instruction at that address here. It is apparently just an : access to a swapped-out page for the new process. I can't see how this : ever worked. The page must be faulted in, but this can't be done while : sched_lock is held (not to mention after we have committed to switching : contexts). sw1b+0x6b is ltr %si I note that this doesn't happen when the disks are clean on boot, but does happen when they are dirty. The kernel is as of a cvsup 3pm MST today. The kernel from 1am last night doesn't seem to have this problem. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 23 23: 4:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id 74F8937B401 for ; Fri, 23 Feb 2001 23:04:54 -0800 (PST) (envelope-from dima@unixfreak.org) Received: from hornet.unixfreak.org (hornet [63.198.170.140]) by bazooka.unixfreak.org (Postfix) with ESMTP id 975C33E02; Fri, 23 Feb 2001 23:04:54 -0800 (PST) To: Matthew Thyer Cc: current@FreeBSD.org Subject: Re: find / -fstype local traverses non-local filesystems In-Reply-To: Message from Matthew Thyer of "Sat, 24 Feb 2001 17:04:44 +1030." <3A975604.30F12BBB@camtech.net.au> Date: Fri, 23 Feb 2001 23:04:54 -0800 From: Dima Dorfman Message-Id: <20010224070454.975C33E02@bazooka.unixfreak.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The problem is that the find took forever and the disk on host > new was thrashing away most of the time. > > find seems to be traversing all file systems (local and non-local) > but just not reporting the found file when its on a non-local > filesystem. See PR bin/23906. In short, the solution is to use: find . \( -fstype local -o -prune \) -print (obviously you should still put in the directives for what you want to find) Dima Dorfman dima@unixfreak.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 24 0:55:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (grouter.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id B5E5437B491; Sat, 24 Feb 2001 00:55:10 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (root@gratis.grondar.za [196.7.18.133]) by gratis.grondar.za (8.11.1/8.11.1) with ESMTP id f1O8nY129418; Sat, 24 Feb 2001 10:49:48 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <200102240849.f1O8nY129418@gratis.grondar.za> To: Andrea Campi Cc: John Baldwin , freebsd-current@FreeBSD.ORG Subject: Re: -CURRENT slowdown in last 2 weeks References: <20010222081232.A7793@webcom.it> In-Reply-To: <20010222081232.A7793@webcom.it> ; from Andrea Campi "Thu, 22 Feb 2001 08:12:33 +0100." Date: Sat, 24 Feb 2001 10:50:17 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > and now performance is very good, event with: > > kern.random.sys.harvest_ethernet: 1 > kern.random.sys.harvest_point_to_point: 0 > kern.random.sys.harvest_interrupt: 1 You mean "even with"? If so, then I am very pleased indeed! M -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 24 2:25: 3 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailout04.sul.t-online.com (mailout04.sul.t-online.com [194.25.134.18]) by hub.freebsd.org (Postfix) with ESMTP id 5BEDF37B401; Sat, 24 Feb 2001 02:24:35 -0800 (PST) (envelope-from D.Rock@t-online.de) Received: from fwd01.sul.t-online.com by mailout04.sul.t-online.com with smtp id 14WbsO-0006zK-00; Sat, 24 Feb 2001 11:24:32 +0100 Received: from server.rock.net (340029380333-0001@[62.226.180.86]) by fmrl01.sul.t-online.com with esmtp id 14WbsA-0vGqXYC; Sat, 24 Feb 2001 11:24:18 +0100 Received: from t-online.de (server [172.23.7.1]) by server.rock.net (8.11.2/8.11.2/Rock) with ESMTP id f1OANbX57657; Sat, 24 Feb 2001 11:24:16 +0100 (MET) Message-ID: <3A978BA9.7D1A1B01@t-online.de> Date: Sat, 24 Feb 2001 11:23:37 +0100 From: Daniel Rock X-Mailer: Mozilla 4.76 [de] (X11; U; SunOS 5.8 i86pc) X-Accept-Language: de, en MIME-Version: 1.0 To: current@freebsd.org, isdn@freebsd.org Subject: Unstable ISDN with interrupt preemption? Content-Type: multipart/mixed; boundary="------------74C1EE39D62317C0F9597B9B" X-Sender: 340029380333-0001@t-dialin.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dies ist eine mehrteilige Nachricht im MIME-Format. --------------74C1EE39D62317C0F9597B9B Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, I just noticed very unstable ISDN connections since the introduction of preempted interrupt threads (Jan 31st). Most errors are uncritical though, an active connection continues to work, sometimes I have to restart isdnd, and sometimes I even have to reboot the machine. The "i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout!" seem to have been introduced by the SMPng code, but with interrupt preemption they appear more often (I switched th SMPng on Jan 25th) As you can also see on the output: On Feb 9th I rebooted the machine with a newly built kernel. All other errors besides the one mentioned above suddenly disappeared. A quick look at the change logs revealed: preemption was accidently removed for interrupt threads on Feb 9th - and reintroduced a few hours later. It seems I was running such a kernel for a week (Feb 9th - 18th) Anyone else having the same problem? -- Daniel --------------74C1EE39D62317C0F9597B9B Content-Type: text/plain; charset=us-ascii; name="messages" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="messages" Jan 27 18:24:08 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Jan 28 06:26:32 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 3 00:26:13 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 3 12:23:38 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 3 12:33:38 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 3 12:35:38 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 3 14:53:38 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 3 15:05:00 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 3 15:26:08 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 6 00:26:15 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 6 12:14:49 gate /boot/kernel/kernel: i4b-L2 i4b_rxd_ack: ((N(R)-1)=115) != (UA=116) !!! Feb 7 00:19:47 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 7 06:21:56 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 7 06:27:56 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 7 12:24:55 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 7 21:54:51 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 8 00:24:50 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 8 00:31:50 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 9 20:53:51 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 9 20:53:51 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 9 21:07:33 gate /boot/kernel/kernel: i4b-L1 isic_isac_exir_hdlr: EXIRQ Rx Frame Overflow Feb 9 21:13:56 gate /boot/kernel/kernel: i4b-L2 i4b_T200_timeout: unit 0, RC = 0 Feb 9 21:14:25 gate /boot/kernel/kernel: i4b-L3 T305_timeout: DISC not answered, cr = 126 Feb 9 21:14:26 gate /boot/kernel/kernel: i4b-L3 T308_timeout: REL not answered, cr = 126 Feb 9 21:14:36 gate /boot/kernel/kernel: i4b-L3 T303_timeout: SETUP not answered, cr = 108 Feb 9 21:17:44 gate /boot/kernel/kernel: i4b-L2 i4b_T200_timeout: unit 0, RC = 0 Feb 9 21:17:44 gate /boot/kernel/kernel: i4b-L2 F_ILL: FSM function F_ILL executing Feb 9 21:17:44 gate /boot/kernel/kernel: i4b-L2 i4b_next_l2state: FSM illegal state, state = ST_TEI_UNAS, event = EV_T200EXP! Feb 9 21:17:49 gate /boot/kernel/kernel: i4b-L2 i4b_i_frame_queued_up: ERROR, mbuf NULL after IF_DEQUEUE Feb 9 21:17:49 gate /boot/kernel/kernel: i4b-L2 i4b_i_frame_queued_up: ERROR, mbuf NULL after IF_DEQUEUE Feb 10 18:24:22 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 13 18:20:48 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 16 18:21:03 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 18 00:24:59 gate /boot/kernel/kernel: i4b-L1 isic_isac_exir_hdlr: EXIRQ Rx Frame Overflow Feb 18 00:25:59 gate /boot/kernel/kernel: i4b-L1 isic_isac_exir_hdlr: EXIRQ Rx Frame Overflow Feb 18 02:05:00 gate /boot/kernel/kernel: i4b-L1 isic_isac_exir_hdlr: EXIRQ Rx Frame Overflow Feb 18 02:05:00 gate /boot/kernel/kernel: i4b-L1 isic_isac_exir_hdlr: EXIRQ Rx Frame Overflow Feb 18 02:23:05 gate /boot/kernel/kernel: i4b-L1 isic_isac_exir_hdlr: EXIRQ Rx Frame Overflow Feb 18 02:23:05 gate /boot/kernel/kernel: i4b-L2 i4b_mdl_error_ind: unit = 0, location = F_MF07 Feb 18 02:23:05 gate /boot/kernel/kernel: i4b-L2 i4b_mdl_error_ind: error = MDL_ERR_F: peer initiated re-establishment - SABME Feb 19 00:27:30 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 19 23:35:50 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 20 18:25:00 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 21 12:16:08 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 21 12:56:08 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 22 12:26:37 gate /boot/kernel/kernel: i4b-L1 isic_isac_exir_hdlr: EXIRQ Rx Frame Overflow Feb 23 20:51:57 gate /boot/kernel/kernel: i4b-L1 isic_isac_exir_hdlr: EXIRQ Rx Frame Overflow Feb 23 20:51:57 gate /boot/kernel/kernel: i4b-L2 i4b_mdl_error_ind: unit = 0, location = F_MF07 Feb 23 20:51:57 gate /boot/kernel/kernel: i4b-L2 i4b_mdl_error_ind: error = MDL_ERR_F: peer initiated re-establishment - SABME Feb 23 22:29:54 gate /boot/kernel/kernel: i4b-L1 isic_isac_exir_hdlr: EXIRQ Rx Frame Overflow Feb 23 23:59:30 gate /boot/kernel/kernel: i4b-L1 isic_isac_exir_hdlr: EXIRQ Rx Frame Overflow Feb 24 00:05:25 gate /boot/kernel/kernel: i4b-L2 i4b_T200_timeout: unit 0, RC = 0 Feb 24 00:06:01 gate /boot/kernel/kernel: i4b-L3 T305_timeout: DISC not answered, cr = 80 Feb 24 00:06:01 gate /boot/kernel/kernel: i4b-L3 next_l3state: FSM illegal state, state = ST_U10 - Active, event = EV_T305EXP - T305 timeout! Feb 24 00:47:20 gate /boot/kernel/kernel: i4b-L1 isic_isac_exir_hdlr: EXIRQ Rx Frame Overflow Feb 24 00:47:20 gate /boot/kernel/kernel: i4b-L2 i4b_mdl_error_ind: unit = 0, location = F_MF07 Feb 24 00:47:20 gate /boot/kernel/kernel: i4b-L2 i4b_mdl_error_ind: error = MDL_ERR_F: peer initiated re-establishment - SABME Feb 24 02:22:57 gate /boot/kernel/kernel: i4b-L1 isic_isac_exir_hdlr: EXIRQ Rx Frame Overflow Feb 24 02:28:54 gate /boot/kernel/kernel: i4b-L2 i4b_T200_timeout: unit 0, RC = 0 Feb 24 02:29:23 gate /boot/kernel/kernel: i4b-L3 T305_timeout: DISC not answered, cr = 105 Feb 24 02:29:23 gate /boot/kernel/kernel: i4b-L3 T308_timeout: REL not answered, cr = 105 Feb 24 02:29:34 gate /boot/kernel/kernel: i4b-L3 T303_timeout: SETUP not answered, cr = 75 Feb 24 10:02:08 gate /boot/kernel/kernel: i4b-L2 i4b_T200_timeout: unit 0, RC = 0 Feb 24 10:02:08 gate /boot/kernel/kernel: i4b-L2 F_ILL: FSM function F_ILL executing Feb 24 10:02:08 gate /boot/kernel/kernel: i4b-L2 i4b_next_l2state: FSM illegal state, state = ST_TEI_UNAS, event = EV_T200EXP! Feb 24 10:02:08 gate /boot/kernel/kernel: i4b-L2 i4b_i_frame_queued_up: ERROR, mbuf NULL after IF_DEQUEUE Feb 24 10:02:08 gate /boot/kernel/kernel: i4b-L2 i4b_i_frame_queued_up: ERROR, mbuf NULL after IF_DEQUEUE Feb 24 10:26:19 gate /boot/kernel/kernel: i4b-L1 isic_isac_exir_hdlr: EXIRQ Rx Frame Overflow Feb 24 10:32:16 gate /boot/kernel/kernel: i4b-L2 i4b_T200_timeout: unit 0, RC = 0 Feb 24 10:32:45 gate /boot/kernel/kernel: i4b-L3 T305_timeout: DISC not answered, cr = 1 Feb 24 10:32:45 gate /boot/kernel/kernel: i4b-L3 T308_timeout: REL not answered, cr = 1 Feb 24 10:32:56 gate /boot/kernel/kernel: i4b-L3 T303_timeout: SETUP not answered, cr = 125 Feb 24 10:42:35 gate /boot/kernel/kernel: i4b-L2 i4b_T200_timeout: unit 0, RC = 0 Feb 24 10:42:35 gate /boot/kernel/kernel: i4b-L2 F_ILL: FSM function F_ILL executing Feb 24 10:42:35 gate /boot/kernel/kernel: i4b-L2 i4b_next_l2state: FSM illegal state, state = ST_TEI_UNAS, event = EV_T200EXP! Feb 24 10:43:17 gate /boot/kernel/kernel: i4b-L2 i4b_i_frame_queued_up: ERROR, mbuf NULL after IF_DEQUEUE Feb 24 10:43:17 gate /boot/kernel/kernel: i4b-L2 i4b_i_frame_queued_up: ERROR, mbuf NULL after IF_DEQUEUE --------------74C1EE39D62317C0F9597B9B Content-Type: text/plain; charset=us-ascii; name="dmesg" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dmesg" Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #525: Sat Feb 24 01:12:00 CET 2001 root@gate.rock.net:/usr/src/sys/compile/ROCK Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6(tm) 3D processor (300.68-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x580 Stepping = 0 Features=0x8001bf AMD Features=0x80000800 real memory = 67043328 (65472K bytes) avail memory = 61329408 (59892K bytes) Preloaded elf kernel "kernel" at 0xc03e3000. WARNING: size of kinfo_proc (648) should be 644!!! VESA: v2.0, 8192k memory, flags:0x1, mode table:0xc0367b20 (1000060) VESA: Number Nine Visual Technology Corporation - REVOLUTION(tm) 3D Using $PIR table, 8 entries at 0xc00fdef0 apm0: on motherboard apm0: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 agp0: mem 0xe2000000-0xe2ffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 (no driver attached) ohci0: mem 0xe7101000-0xe7101fff irq 11 at device 2.0 on pci0 usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: AcerLabs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered isab0: at device 7.0 on pci0 isa0: on isab0 sym0: <815> port 0xe000-0xe0ff mem 0xe7102000-0xe71020ff irq 10 at device 8.0 on pci0 sym0: Symbios NVRAM, ID 7, Fast-10, SE, parity checking sym0: open drain IRQ line driver sym0: using NCR-generic firmware. pci0: at 9.0 (no driver attached) fxp0: port 0xe400-0xe41f mem 0xe7000000-0xe70fffff,0xe7100000-0xe7100fff irq 12 at device 10.0 on pci0 fxp0: Ethernet address 00:a0:c9:ef:69:8d atapci0: port 0xf000-0xf00f irq 0 at device 15.0 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x0> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 isic0: at port 0x100-0x107 irq 3 on isa0 isic0: passive stack unit 0 unknown: can't assign resources pca0: at port 0x61 on isa0 unknown: can't assign resources fdc0: at port 0x3f2-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: at port 0x378-0x37f,0x778-0x77a irq 7 drq 3 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/1 bytes threshold lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 unknown: can't assign resources i4bctl: ISDN system control port attached DUMMYNET initialized (010124) i4btrc: 2 ISDN trace device(s) attached IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to accept, unlimited logging i4b: ISDN call control device attached i4btel: 2 ISDN telephony interface device(s) attached i4brbch: 2 raw B channel access device(s) attached ad0: 4103MB [8894/15/63] at ata0-master UDMA33 ad1: 1221MB [2482/16/63] at ata1-master WDMA2 Waiting 2 seconds for SCSI devices to settle (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. Mounting root from ufs:/dev/ad0a da1 at sym0 bus 0 target 2 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 8) da1: 995MB (2039283 512 byte sectors: 64H 32S/T 995C) da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da0: 2150MB (4404489 512 byte sectors: 255H 63S/T 274C) cd0 at sym0 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 8) cd0: Attempt to query device size failed: NOT READY, Medium not present WARNING: / was not properly dismounted --------------74C1EE39D62317C0F9597B9B Content-Type: text/plain; charset=us-ascii; name="kernel.config" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="kernel.config" machine i386 ident ROCK hints "ROCK.hints" maxusers 8 cpu I486_CPU cpu I586_CPU options COMPAT_43 options SYSVSHM options SYSVSEM options SYSVMSG options KTRACE #kernel tracing options UCONSOLE options INET device ether device sppp device loop 1 device bpf device tun options IPFIREWALL options IPFIREWALL_VERBOSE options IPFIREWALL_FORWARD options IPFIREWALL_DEFAULT_TO_ACCEPT options IPDIVERT options DUMMYNET options FFS options NFS options PROCFS options DEVFS options SOFTUPDATES options FFS_EXTATTR options QUOTA device md options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L options HZ=1000 device pty device snp options MSGBUF_SIZE=40960 device isa options AUTO_EOI_1 device atkbdc 1 device atkbd options ATKBD_DFLT_KEYMAP makeoptions ATKBD_DFLT_KEYMAP="german.iso" options KBD_INSTALL_CDEV device vga options VGA_WIDTH90 options VESA device splash device sc 1 options SC_DFLT_FONT makeoptions SC_DFLT_FONT=iso options SC_PIXEL_MODE device npx device ata device atadisk options ATA_ENABLE_ATAPI_DMA options ATA_ENABLE_TAGS device fdc device sio options BREAK_TO_DEBUGGER device pca device apm device pmtimer device joy device pci device agp device miibus device rl device fxp device isic options SEDLBAUER device "i4bq921" device "i4bq931" device "i4b" device "i4btrc" 2 device "i4bctl" device "i4brbch" 2 device "i4btel" 2 device ppc options PPC_PROBE_CHIPSET device ppbus device lpt device ppi device random device scbus device da device sa device cd device pass device sym device amd options SCSI_DELAY=2000 device aic device ohci device usb device ugen device uhid device ukbd device umass device ums device smbus device alpm device smb options COMPAT_LINUX options NETGRAPH options NETGRAPH_ASYNC options NETGRAPH_BPF options NETGRAPH_ETHER options NETGRAPH_IFACE options NETGRAPH_KSOCKET options NETGRAPH_MPPC_ENCRYPTION options NETGRAPH_PPP options NETGRAPH_PPPOE options NETGRAPH_PPTPGRE options NETGRAPH_SOCKET options NETGRAPH_TEE options NETGRAPH_TTY options NETGRAPH_UI options NETGRAPH_VJC --------------74C1EE39D62317C0F9597B9B-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 24 4: 2: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from syncopation-03.iinet.net.au (syncopation-03.iinet.net.au [203.59.24.49]) by hub.freebsd.org (Postfix) with SMTP id 6E72C37B503 for ; Sat, 24 Feb 2001 04:02:05 -0800 (PST) (envelope-from julian@elischer.org) Received: (qmail 24304 invoked by uid 666); 24 Feb 2001 12:14:18 -0000 Received: from i076-112.nv.iinet.net.au (HELO elischer.org) (203.59.76.112) by mail.m.iinet.net.au with SMTP; 24 Feb 2001 12:14:18 -0000 Message-ID: <3A97A299.34B2EF7B@elischer.org> Date: Sat, 24 Feb 2001 04:01:29 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Warner Losh Cc: current@freebsd.org Subject: Re: Today's panic :-) References: <200102240551.f1O5p0W85583@harmony.village.org> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > > I've added INVARIANTS and WITNESS to my kernel. Today I get a random > panic on boot sometimes: > > lock order reseral (this doesn't cause the panic, but > does seem to happen all the time) > 1st vnode interlock last acquired @ ../../usr/ffs/ffs_fsops.c:396 > 2nd 0xc04837a0 mntvnode @ ../../ufs/ffs/ffs_vfsops.c:457 > 3rd 0xc80b9e8c vnode interlock @ ../../kern/vfs_subr.c:1872 I keep dropping into ddb with: ad1: 99MB [216/15/63] at ata0-slave WDMA2 Mounting root from ufs:/dev/ad0s1a lock order reversal 1st lockmgr last acquired @ ../../kern/kern_lock.c:239 2nd 0xc085d654 ucred @ ../../kern/kern_prot.c:1177 3rd 0xc02b65e0 lockmgr @ ../../kern/kern_lock.c:239 lock order reversal 1st vnode interlock last acquired @ ../../kern/vfs_vnops.c:625 2nd 0xc02d0a60 mntvnode @ ../../ufs/ffs/ffs_vfsops.c:940 3rd 0xc3d7186c vnode interlock @ ../../ufs/ffs/ffs_vfsops.c:949 lock order reversal 1st lockmgr last acquired @ ../../kern/kern_lock.c:239 2nd 0xc02b8620 uidinfo hash @ ../../kern/kern_resource.c:765 3rd 0xc02b65e0 lockmgr @ ../../kern/kern_lock.c:239 lock order reversal 1st lockmgr last acquired @ ../../kern/kern_lock.c:239 2nd 0xc08d321c uidinfo struct @ ../../kern/kern_resource.c:819 3rd 0xc02b65e0 lockmgr @ ../../kern/kern_lock.c:239 hitting 'c' (for continue) allows me to go on.... This with a kernel CVSUP'd in the last day. I'll CVsup again as I vaguely remember a commit message that may affect this. -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 24 7:30:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 9B1E237B503 for ; Sat, 24 Feb 2001 07:30:49 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id KAA46174; Sat, 24 Feb 2001 10:30:45 -0500 (EST) (envelope-from wollman) Date: Sat, 24 Feb 2001 10:30:45 -0500 (EST) From: Garrett Wollman Message-Id: <200102241530.KAA46174@khavrinen.lcs.mit.edu> To: Matthew Thyer Cc: current@FreeBSD.ORG Subject: find / -fstype local traverses non-local filesystems In-Reply-To: <3A975604.30F12BBB@camtech.net.au> References: <3A975604.30F12BBB@camtech.net.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > find seems to be traversing all file systems (local and non-local) > but just not reporting the found file when its on a non-local > filesystem. As has been discussed many times before, this is correct behavior. If you want `find' to not traverse a directory, use the `-prune' primary. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 24 8:43:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 6F82F37B491; Sat, 24 Feb 2001 08:43:17 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p20-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.149]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id BAA27986; Sun, 25 Feb 2001 01:43:04 +0900 (JST) Message-ID: <3A97E3EF.2E204C3F@newsguy.com> Date: Sun, 25 Feb 2001 01:40:15 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: Robert Watson Cc: obrien@FreeBSD.ORG, Matthew Jacob , current@FreeBSD.ORG Subject: Re: dirty buffers on reboot again? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robert Watson wrote: > > Hmm. I've been getting this on an ATA box as well. Don't seem to get it > when softupdates is not set on the root partition, but that's just an > observation from a couple of boxes. (Sample size == 2 -> confidence level > = 0). I don't have softupdates on root (but I do have elsewhere... which reminds me I need to turn it on on a recently created partition :). -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@kzinti.bsdconspiracy.net Acabou o hipismo-arte. Mas a desculpa brasileira mais ouvida em Sydney e' que nao tem mais cavalo bobo por ai'. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 24 10:24:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailout01.sul.t-online.com (mailout01.sul.t-online.com [194.25.134.80]) by hub.freebsd.org (Postfix) with ESMTP id 2873937B491 for ; Sat, 24 Feb 2001 10:24:50 -0800 (PST) (envelope-from D.Rock@t-online.de) Received: from fwd02.sul.t-online.com by mailout01.sul.t-online.com with smtp id 14WjN2-00049U-06; Sat, 24 Feb 2001 19:24:40 +0100 Received: from server.rock.net (340029380333-0001@[62.226.203.211]) by fmrl02.sul.t-online.com with esmtp id 14WjMq-0oUOlEC; Sat, 24 Feb 2001 19:24:28 +0100 Received: from t-online.de (server [172.23.7.1]) by server.rock.net (8.11.2/8.11.2/Rock) with ESMTP id f1OIOIX91317 for ; Sat, 24 Feb 2001 19:24:25 +0100 (MET) Message-ID: <3A97FC51.A9E3491@t-online.de> Date: Sat, 24 Feb 2001 19:24:17 +0100 From: Daniel Rock X-Mailer: Mozilla 4.76 [de] (X11; U; SunOS 5.8 i86pc) X-Accept-Language: de, en MIME-Version: 1.0 Cc: current@FreeBSD.ORG Subject: Re: as segfaulting during world-build References: <3A958178.380C85B6@t-online.de> <200102201627.f1KGRLa20988@aldan.algebra.com> <20010220174909.F22771@petra.hos.u-szeged.hu> <200102232349.f1NNncW84029@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: 340029380333-0001@t-dialin.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh schrieb: > > In message <3A958178.380C85B6@t-online.de> Daniel Rock writes: > : I did have the same problem. But just rebuilding binutils didn't help either. > : Trying to rebuild libc resulted in above SEGV from as. Some sort of Catch 22 > > Find a libc from before Feb 10th or after Feb 21 and put it on your > system. Yes I know, I already posted another solution: Just use another /usr/lib/libc.so.4 for rebuilding libc.so.5 Sometimes you just have at this time no working internet connection - and you simply cannot find your backup tapes you never made. So I came around the trick with an older libc.so.4, which seems to be "compatible enough" to let me rebuild libc. -- Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 24 10:31:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailout04.sul.t-online.com (mailout04.sul.t-online.com [194.25.134.18]) by hub.freebsd.org (Postfix) with ESMTP id CAF0337B65D for ; Sat, 24 Feb 2001 10:31:41 -0800 (PST) (envelope-from D.Rock@t-online.de) Received: from fwd03.sul.t-online.com by mailout04.sul.t-online.com with smtp id 14WjTo-0007Ar-02; Sat, 24 Feb 2001 19:31:40 +0100 Received: from server.rock.net (340029380333-0001@[62.226.203.211]) by fmrl03.sul.t-online.com with esmtp id 14WjTY-0e9Pl2C; Sat, 24 Feb 2001 19:31:24 +0100 Received: from t-online.de (server [172.23.7.1]) by server.rock.net (8.11.2/8.11.2/Rock) with ESMTP id f1OIVNX91486 for ; Sat, 24 Feb 2001 19:31:23 +0100 (MET) Message-ID: <3A97FDFA.3291CB26@t-online.de> Date: Sat, 24 Feb 2001 19:31:22 +0100 From: Daniel Rock X-Mailer: Mozilla 4.76 [de] (X11; U; SunOS 5.8 i86pc) X-Accept-Language: de, en MIME-Version: 1.0 Cc: freebsd-current@FreeBSD.ORG Subject: Re: HEADS UP Re: cvs commit: src/sys/alpha/alpha trap.c src/sys/dev/acpica/Osd OsdSchedule.c src/sys/i386/i386 genassym.c swtch.strap.c src/sys/ia64/ia64 trap.c src/sys/kern init_main.c kern_condvar.ckern_idle.c kern_intr.c kern_mib.c kern_mutex.c kern_proc.c ... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: 340029380333-0001@t-dialin.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans schrieb: > > On Thu, 22 Feb 2001, Daniel Rock wrote: > > > You may have forgotten to also change KINFO_PROC_SIZE in src/sys/user.h > > Yes, rev.1.31 of src/sys/sys/user.h leaves it as an exercise to change > KINFO_PROC_SIZE. I hate doing such exercises, since it will be followed by some nasty other exercises: Clean up your conflicting cvs files... > > WARNING: size of kinfo_proc (648) should be 644!!! > > This is normal if you haven't done the exercise. It is just a warning. This seems to be a "non required" exercise, since even if you fail solving it, your machine continues working... > > BTW What is the purpose of KINFO_PROC_SIZE? Why not simply using sizeof()? > > It is to inhibit changes in the size of the struct. Such changes would > break the interface. The struct must have a certain fixed size (and > layout) for binary compatibility. sizeof() would give the current size, > not necessarily the size that is required for compatibility. But: Since the introduction of KINFO_PROC_SIZE (rev. 1.27(?) of src/sys/sys/user.h) there have been two modifications which still required to rebuild libkvm, ... Maybe many people won't use the spare entries at the end of the structure but put their additions somewhere besides some other related variables for aesthetical purposes? Which value does libkvm use? KINFO_PROC_SIZE or sizeof()? It seems it uses sizeof() since ps/top/w still work besides the warning message. -- Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 24 12: 9:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 37F5637B67D for ; Sat, 24 Feb 2001 12:09:53 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f1OK9qW91972 for ; Sat, 24 Feb 2001 13:09:52 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200102242009.f1OK9qW91972@harmony.village.org> Subject: Re: Today's panic :-) To: current@FreeBSD.ORG In-reply-to: Your message of "Fri, 23 Feb 2001 23:58:44 MST." <200102240658.f1O6wiW85748@harmony.village.org> References: <200102240658.f1O6wiW85748@harmony.village.org> Date: Sat, 24 Feb 2001 13:09:52 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200102240658.f1O6wiW85748@harmony.village.org> Warner Losh writes: : I note that this doesn't happen when the disks are clean on boot, but : does happen when they are dirty. The kernel is as of a cvsup 3pm MST : today. The kernel from 1am last night doesn't seem to have this : problem. Doesn't seem to have this problem that badly. I just got a very similar crash from it. Maybe I'm just lucky with the older one. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 24 12:11:41 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 2C45B37B4EC; Sat, 24 Feb 2001 12:11:37 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f1OKBVW92002; Sat, 24 Feb 2001 13:11:33 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200102242011.f1OKBVW92002@harmony.village.org> To: "Daniel C. Sobral" Subject: Re: dirty buffers on reboot again? Cc: Robert Watson , obrien@FreeBSD.ORG, Matthew Jacob , current@FreeBSD.ORG In-reply-to: Your message of "Sun, 25 Feb 2001 01:40:15 +0900." <3A97E3EF.2E204C3F@newsguy.com> References: <3A97E3EF.2E204C3F@newsguy.com> Date: Sat, 24 Feb 2001 13:11:31 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3A97E3EF.2E204C3F@newsguy.com> "Daniel C. Sobral" writes: : I don't have softupdates on root (but I do have elsewhere... which : reminds me I need to turn it on on a recently created partition :). It still seems to happen for me on a box that has softupdates disabled. But its frequency is far far less (1 in 20 reboots rather than 19 in 20) than the box that used to have softupdates turned on. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 24 14:36: 1 2001 Delivered-To: freebsd-current@freebsd.org Received: from ns.altadena.net (ns.altadena.net [206.126.144.2]) by hub.freebsd.org (Postfix) with ESMTP id 906FB37B401 for ; Sat, 24 Feb 2001 14:35:58 -0800 (PST) (envelope-from pete@ns.altadena.net) Received: (from pete@localhost) by ns.altadena.net (8.11.2/8.8.8) id f1OMXN475561 for current@freebsd.org; Sat, 24 Feb 2001 14:33:23 -0800 (PST) (envelope-from pete) From: Pete Carah Message-Id: <200102242233.f1OMXN475561@ns.altadena.net> Subject: Panic in today current To: current@freebsd.org Date: Sat, 24 Feb 2001 14:33:23 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=iso8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I got a panic today on a fresh kernel... Compiled with netgraph but non of the netgraph modules. Immediately after the memory probe, a message about sequencers 0-15, then: Panic: spinlock ng_worklist not in order list Before these was WARNING: size of kinfo_proc (648) should be 644!!! -- Pete To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 24 15:44:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-57.dsl.lsan03.pacbell.net [63.207.60.57]) by hub.freebsd.org (Postfix) with ESMTP id D4E3C37B401 for ; Sat, 24 Feb 2001 15:44:09 -0800 (PST) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 9194B66F1F; Sat, 24 Feb 2001 15:44:09 -0800 (PST) Date: Sat, 24 Feb 2001 15:44:09 -0800 From: Kris Kennaway To: Pete Carah Cc: current@freebsd.org Subject: Re: Panic in today current Message-ID: <20010224154409.A56032@mollari.cthul.hu> References: <200102242233.f1OMXN475561@ns.altadena.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="WIyZ46R2i8wDzkSu" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200102242233.f1OMXN475561@ns.altadena.net>; from pete@ns.altadena.net on Sat, Feb 24, 2001 at 02:33:23PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --WIyZ46R2i8wDzkSu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Feb 24, 2001 at 02:33:23PM -0800, Pete Carah wrote: > I got a panic today on a fresh kernel... >=20 > Compiled with netgraph but non of the netgraph modules. >=20 > Immediately after the memory probe, a message about sequencers 0-15, > then: > Panic: spinlock ng_worklist not in order list >=20 > Before these was WARNING: size of kinfo_proc (648) should be 644!!! I reported this a few days ago..Julian committed something earlier today which claims to address it, I'm about to check it out. Kris --WIyZ46R2i8wDzkSu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6mEdJWry0BWjoQKURAn33AJ9wzGL9CCwkLGaQSf39w94hrL3YiQCgnluj 6fWdkNdfG2VscErky7lNXdk= =dDue -----END PGP SIGNATURE----- --WIyZ46R2i8wDzkSu-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 24 15:56:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from moby.geekhouse.net (moby.geekhouse.net [64.81.6.36]) by hub.freebsd.org (Postfix) with ESMTP id 18BFA37B699 for ; Sat, 24 Feb 2001 15:56:01 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@dhcp152.geekhouse.net [192.168.1.152]) by moby.geekhouse.net (8.11.0/8.9.3) with ESMTP id f1ONu6181833 for ; Sat, 24 Feb 2001 15:56:06 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200102241936.f1OJaEf71655@freefall.freebsd.org> Date: Sat, 24 Feb 2001 15:55:44 -0800 (PST) From: John Baldwin To: current@FreeBSD.org Subject: RE: cvs commit: src/sys/kern kern_mutex.c Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 24-Feb-01 John Baldwin wrote: > jhb 2001/02/24 11:36:13 PST > > Modified files: > sys/kern kern_mutex.c > Log: > ... > - Make the _mtx_assert() function be compiled in if INVARIANTS_SUPPORT is > defined rather than if INVARIANTS is defined so that a KLD compiled > with INVARIANTS that uses mtx_assert() can be used with a kernel that > just has INVARIANT_SUPPORT compiled in. With this, building a kernel with INVARIANTS is back to requiring INVARIANT_SUPPORT to be present in the kernel. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 24 15:56:35 2001 Delivered-To: freebsd-current@freebsd.org Received: from moby.geekhouse.net (moby.geekhouse.net [64.81.6.36]) by hub.freebsd.org (Postfix) with ESMTP id 0669C37B698 for ; Sat, 24 Feb 2001 15:56:01 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@dhcp152.geekhouse.net [192.168.1.152]) by moby.geekhouse.net (8.11.0/8.9.3) with ESMTP id f1ONu2181813; Sat, 24 Feb 2001 15:56:03 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3A97A299.34B2EF7B@elischer.org> Date: Sat, 24 Feb 2001 15:55:41 -0800 (PST) From: John Baldwin To: Julian Elischer Subject: Re: Today's panic :-) Cc: current@FreeBSD.org, Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 24-Feb-01 Julian Elischer wrote: > Warner Losh wrote: >> >> I've added INVARIANTS and WITNESS to my kernel. Today I get a random >> panic on boot sometimes: >> >> lock order reseral (this doesn't cause the panic, but >> does seem to happen all the time) >> 1st vnode interlock last acquired @ ../../usr/ffs/ffs_fsops.c:396 >> 2nd 0xc04837a0 mntvnode @ ../../ufs/ffs/ffs_vfsops.c:457 >> 3rd 0xc80b9e8c vnode interlock @ ../../kern/vfs_subr.c:1872 > > I keep dropping into ddb with: Don't use WITNESS_DDB and you won't drop into ddb. We're not far enough along to make that very livable yet. :( -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 24 15:56:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from moby.geekhouse.net (moby.geekhouse.net [64.81.6.36]) by hub.freebsd.org (Postfix) with ESMTP id 542A137B69B for ; Sat, 24 Feb 2001 15:56:04 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@dhcp152.geekhouse.net [192.168.1.152]) by moby.geekhouse.net (8.11.0/8.9.3) with ESMTP id f1ONu4181817; Sat, 24 Feb 2001 15:56:04 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200102240658.f1O6wiW85748@harmony.village.org> Date: Sat, 24 Feb 2001 15:55:42 -0800 (PST) From: John Baldwin To: Warner Losh Subject: Re: Today's panic :-) Cc: current@FreeBSD.org, Bruce Evans Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 24-Feb-01 Warner Losh wrote: > In message Bruce > Evans writes: >: It seems to be another trap while holding sched_lock. This should be >: fatal, but the problem is only detected because trap() enables >: interrupts. Then an interrupt causes bad things to happen. Unfortunately, >: the above omits the critical information: the instruction at sw1b+0x6b. >: There is no instruction at that address here. It is apparently just an >: access to a swapped-out page for the new process. I can't see how this >: ever worked. The page must be faulted in, but this can't be done while >: sched_lock is held (not to mention after we have committed to switching >: contexts). > > sw1b+0x6b is ltr %si > > I note that this doesn't happen when the disks are clean on boot, but > does happen when they are dirty. The kernel is as of a cvsup 3pm MST > today. The kernel from 1am last night doesn't seem to have this > problem. Other people have reported this and I can't reproduce this. The one case I managed to track down so far involved proc0 having pcb_ext bogusly set, resulting in cpu_switch() setting up a bogus GDT entry for a TSS and thus generating a GPF which is the trap you see. The enable_intr() in trap() then sends things downhill fast. I'm not sure yet why processes are having pcb_ext bogusly set. Hmm. Make sure you have rev 1.35 or later of pcb.h. Also, try build a kernel from scratch from fresh sources.. > Warner -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 24 20:26:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from urban.iinet.net.au (urban.iinet.net.au [203.59.24.231]) by hub.freebsd.org (Postfix) with ESMTP id 617B037B401 for ; Sat, 24 Feb 2001 20:26:08 -0800 (PST) (envelope-from julian@elischer.org) Received: from muzak.iinet.net.au (muzak.iinet.net.au [203.59.24.237]) by urban.iinet.net.au (8.8.7/8.8.7) with ESMTP id MAA22118; Sun, 25 Feb 2001 12:26:05 +0800 Received: from elischer.org (i080-119.nv.iinet.net.au [203.59.80.119]) by muzak.iinet.net.au (8.8.5/8.8.5) with ESMTP id MAA04890; Sun, 25 Feb 2001 12:23:11 +0800 Message-ID: <3A988938.16F4123F@elischer.org> Date: Sat, 24 Feb 2001 20:25:28 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Pete Carah Cc: current@freebsd.org Subject: Re: Panic in today current References: <200102242233.f1OMXN475561@ns.altadena.net> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Pete Carah wrote: > > I got a panic today on a fresh kernel... > > Compiled with netgraph but non of the netgraph modules. > > Immediately after the memory probe, a message about sequencers 0-15, > then: > Panic: spinlock ng_worklist not in order list > > Before these was WARNING: size of kinfo_proc (648) should be 644!!! netgraph didn;t have 'WITNESS' support. I added it yesterday so maybe a resup may fix it. > > -- Pete > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 24 20:28:27 2001 Delivered-To: freebsd-current@freebsd.org Received: from syncopation-01.iinet.net.au (syncopation-01.iinet.net.au [203.59.24.37]) by hub.freebsd.org (Postfix) with SMTP id 79E5837B4EC for ; Sat, 24 Feb 2001 20:28:23 -0800 (PST) (envelope-from julian@elischer.org) Received: (qmail 11696 invoked by uid 666); 25 Feb 2001 04:39:45 -0000 Received: from i080-119.nv.iinet.net.au (HELO elischer.org) (203.59.80.119) by mail.m.iinet.net.au with SMTP; 25 Feb 2001 04:39:45 -0000 Message-ID: <3A9889C3.58BDC139@elischer.org> Date: Sat, 24 Feb 2001 20:27:47 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Pete Carah Cc: current@freebsd.org Subject: Re: Panic in today current References: <200102242233.f1OMXN475561@ns.altadena.net> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Pete Carah wrote: > > I got a panic today on a fresh kernel... > > Compiled with netgraph but non of the netgraph modules. > > Immediately after the memory probe, a message about sequencers 0-15, > then: > Panic: spinlock ng_worklist not in order list argh, ignore that last message.. maybe I don;t understand how witness is supposed to work. what are your CONFIGs? I'll try duplicate them here. A Winess kernel booted fine here (dammit) > > Before these was WARNING: size of kinfo_proc (648) should be 644!!! that's ps having a fit about something else. > > -- Pete > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 24 20:38:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from syncopation-03.iinet.net.au (syncopation-03.iinet.net.au [203.59.24.49]) by hub.freebsd.org (Postfix) with SMTP id 79F6837B491 for ; Sat, 24 Feb 2001 20:38:43 -0800 (PST) (envelope-from julian@elischer.org) Received: (qmail 32754 invoked by uid 666); 25 Feb 2001 04:50:51 -0000 Received: from i080-119.nv.iinet.net.au (HELO elischer.org) (203.59.80.119) by mail.m.iinet.net.au with SMTP; 25 Feb 2001 04:50:51 -0000 Message-ID: <3A988C2D.8E5377DA@elischer.org> Date: Sat, 24 Feb 2001 20:38:05 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Pete Carah , current@freebsd.org Subject: Re: Panic in today current References: <200102242233.f1OMXN475561@ns.altadena.net> <3A9889C3.58BDC139@elischer.org> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer wrote: > > Pete Carah wrote: > > > > I got a panic today on a fresh kernel... > > > > Compiled with netgraph but non of the netgraph modules. > > > > Immediately after the memory probe, a message about sequencers 0-15, > > then: > > Panic: spinlock ng_worklist not in order list > > argh, this is 'post change' because the name ng_worklist was added with the change. > ignore that last message.. > maybe I don't understand how witness is supposed to work. obviously I don't, as the same patch that changed the name to ng_worklist also added it (I thought) to the order list. > what are your CONFIGs? I'll try duplicate them here. > -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 24 20:50:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from cr66388-a.rchrd1.on.wave.home.com (cr66388-a.rchrd1.on.wave.home.com [24.114.165.24]) by hub.freebsd.org (Postfix) with ESMTP id A2DC037B4EC for ; Sat, 24 Feb 2001 20:50:19 -0800 (PST) (envelope-from jburkholder0829@home.com) Received: from cr66388-a.rchrd1.on.wave.home.c (localhost [127.0.0.1]) by cr66388-a.rchrd1.on.wave.home.com (Postfix) with ESMTP id A6CEDBACA; Sat, 24 Feb 2001 23:50:18 -0500 (EST) X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Julian Elischer Cc: Pete Carah , current@FreeBSD.ORG Subject: Re: Panic in today current In-Reply-To: Message from Julian Elischer of "Sat, 24 Feb 2001 20:38:05 PST." <3A988C2D.8E5377DA@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 24 Feb 2001 23:50:17 -0500 From: Jake Burkholder Message-Id: <20010225045018.A6CEDBACA@cr66388-a.rchrd1.on.wave.home.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Julian Elischer wrote: > > > > Pete Carah wrote: > > > > > > I got a panic today on a fresh kernel... > > > > > > Compiled with netgraph but non of the netgraph modules. > > > > > > Immediately after the memory probe, a message about sequencers 0-15, > > > then: > > > Panic: spinlock ng_worklist not in order list > > The problem is probably that you put them inside of an ifdef SMP. The ifdef is there for locks that only exist for SMP. Move them after the #endif, like: /* * leaf locks */ #ifdef SMP #ifdef __i386__ "ap boot", "imen", #endif "smp rendezvous", #endif "ng_node", "ng_worklist", NULL To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 24 20:57:38 2001 Delivered-To: freebsd-current@freebsd.org Received: from syncopation-03.iinet.net.au (syncopation-03.iinet.net.au [203.59.24.49]) by hub.freebsd.org (Postfix) with SMTP id 7B5D137B491 for ; Sat, 24 Feb 2001 20:57:32 -0800 (PST) (envelope-from julian@elischer.org) Received: (qmail 1097 invoked by uid 666); 25 Feb 2001 05:09:41 -0000 Received: from i080-119.nv.iinet.net.au (HELO elischer.org) (203.59.80.119) by mail.m.iinet.net.au with SMTP; 25 Feb 2001 05:09:41 -0000 Message-ID: <3A989094.A93A18A6@elischer.org> Date: Sat, 24 Feb 2001 20:56:52 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Pete Carah Cc: current@freebsd.org Subject: Re: Panic in today current References: <200102242233.f1OMXN475561@ns.altadena.net> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Pete Carah wrote: > > I got a panic today on a fresh kernel... > > Compiled with netgraph but non of the netgraph modules. > > Immediately after the memory probe, a message about sequencers 0-15, > then: > Panic: spinlock ng_worklist not in order list > > Before these was WARNING: size of kinfo_proc (648) should be 644!!! > > -- Pete > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message duh. it was commented out for UP. resup to verion 1.51 ---- Checking in kern_mutex.c; /home/ncvs/src/sys/kern/kern_mutex.c,v <-- kern_mutex.c new revision: 1.51; previous revision: 1.50 done I'll pay COD for the pointy hat.. -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 24 21: 7:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from urban.iinet.net.au (urban.iinet.net.au [203.59.24.231]) by hub.freebsd.org (Postfix) with ESMTP id 4831737B401 for ; Sat, 24 Feb 2001 21:07:40 -0800 (PST) (envelope-from julian@elischer.org) Received: from elischer.org (i080-119.nv.iinet.net.au [203.59.80.119]) by urban.iinet.net.au (8.8.7/8.8.7) with ESMTP id NAA24035; Sun, 25 Feb 2001 13:07:30 +0800 Message-ID: <3A9892EF.FE2EBDF3@elischer.org> Date: Sat, 24 Feb 2001 21:06:55 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Jake Burkholder Cc: Pete Carah , current@FreeBSD.ORG Subject: Re: Panic in today current References: <20010225045018.A6CEDBACA@cr66388-a.rchrd1.on.wave.home.com> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jake Burkholder wrote: > > > Julian Elischer wrote: > > > > > > Pete Carah wrote: > > > > > > > > I got a panic today on a fresh kernel... > > > > > > > > Compiled with netgraph but non of the netgraph modules. > > > > > > > > Immediately after the memory probe, a message about sequencers 0-15, > > > > then: > > > > Panic: spinlock ng_worklist not in order list > > > > > The problem is probably that you put them inside of an ifdef SMP. > The ifdef is there for locks that only exist for SMP. already done thanks.. > > Move them after the #endif, like: > > /* > * leaf locks > */ > #ifdef SMP > #ifdef __i386__ > "ap boot", > "imen", > #endif > "smp rendezvous", > #endif > "ng_node", > "ng_worklist", > NULL -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 24 22:38:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id E876F37B503 for ; Sat, 24 Feb 2001 22:38:26 -0800 (PST) (envelope-from wes@softweyr.com) Received: from [127.0.0.1] (helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 14WuzC-0002FS-00; Sat, 24 Feb 2001 23:48:50 -0700 Message-ID: <3A98AAD2.A35582A5@softweyr.com> Date: Sat, 24 Feb 2001 23:48:50 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Garrett Wollman Cc: Matthew Thyer , current@FreeBSD.ORG Subject: Re: find / -fstype local traverses non-local filesystems References: <3A975604.30F12BBB@camtech.net.au> <200102241530.KAA46174@khavrinen.lcs.mit.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garrett Wollman wrote: > > < said: > > > find seems to be traversing all file systems (local and non-local) > > but just not reporting the found file when its on a non-local > > filesystem. > > As has been discussed many times before, this is correct behavior. If > you want `find' to not traverse a directory, use the `-prune' primary. Or -x to keep it on a single device/filesystem. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message